[pypy-svn] rev 1884 - pypy/trunk/doc/funding
alastair at codespeak.net
alastair at codespeak.net
Tue Oct 14 07:14:13 CEST 2003
Author: alastair
Date: Tue Oct 14 07:14:13 2003
New Revision: 1884
Modified:
pypy/trunk/doc/funding/B5.0_manage_bea.txt
Log:
Added info on the coordinator and mentioned the consortium agreement
Modified: pypy/trunk/doc/funding/B5.0_manage_bea.txt
==============================================================================
--- pypy/trunk/doc/funding/B5.0_manage_bea.txt (original)
+++ pypy/trunk/doc/funding/B5.0_manage_bea.txt Tue Oct 14 07:14:13 2003
@@ -292,6 +292,11 @@
Alastair Burt, DFKI
+He has participated in several European projects, was the coordinator of
+the EU-funded ASWAD free software project, and is in the coordinating team
+of the EUTIST-AMI cluster. The DFKI itself has over a decade of experience
+of working with the EU's financial and reporting procedures.
+
The responsibilities of the project coordinator will include:
- to manage negotiations regarding proposal
@@ -539,23 +544,6 @@
method will only by required when the project reaches the point where
users begin to rely on aspects of our implementation.
-Consortium
-----------
-
-The consortium consists of the following members:
-
-FIXME ALASTAIR: More details? Addresses, organisation numbers....?
-
-- DFKI, Germany
-- Python Business Forum, International
-- University of Southampton, UK
-- Max Planck Institut, Germany
-- AB Strakt, Sweden
-- Logilab, France
-- Changemaker, Sweden
-
-FIXME ALASTAIR: - something we should mention here about the agreement?
-
Management of Knowledge and Intellectual Property
--------------------------------------------------
@@ -580,3 +568,13 @@
also a necessity to allow PyPy to become a reference implementation of
the Python language specification.
+Consortium Agreement
+--------------------
+
+In the case that the proposal is accepted by the EU, the coordinator and
+the project management team will draw up a consortium agreement that
+formalises the license policy outlined above. As all technical deliverables
+will be fully public, for general modification and reuse, all partners, and
+indeed the rest of the world, are free to exploit the results as they
+choose.
+
More information about the Pypy-commit
mailing list