[pypy-svn] r3495 - pypy/trunk/doc/funding/negotiations
alastair at codespeak.net
alastair at codespeak.net
Mon Mar 29 16:28:01 CEST 2004
Date: Mon Mar 29 16:27:58 2004
New Revision: 3495
Added an explantion of the dynamic role of the PBF.
--- pypy/trunk/doc/funding/negotiations/email-eu-1.txt (original)
+++ pypy/trunk/doc/funding/negotiations/email-eu-1.txt Mon Mar 29 16:27:58 2004
@@ -3,13 +3,14 @@
based currently on an earlier draft from Jacob and some work from Holger.
-Dear Mr van Roy, Dear Mr. Lacroix,
+Dear Mr van Rooy, Dear Mr. Lacroix,
-During the meeting on 16th of March 2004 the PyPy consortium was told
-that the cost model and budget of the PBF is not acceptable within the
-sixth framework program. Originally the PBF was to take on two
-responsilibites: deploying certain people for core work and connecting
-the project to open source and business communities.
+During the meeting on 16th of March 2004 the PyPy consortium was told that
+the cost model and budget of the PBF is not acceptable within the sixth
+framework program. Originally the PBF was to take on three
+responsilibites: deploying certain people for core work, connecting the
+project to open source and business communities, and bringing in new people
+from the external developer community to cope with unforseen eventualities.
For the first part we can substitute by bringing in three of the
individuals as consortium partners. The fourth person is to be employed
@@ -18,11 +19,16 @@
because it seems to be harder now to bring in specific experts
-But the second responsibility and role should stay with the PBF:
-connecting and disseminating to open source and business communities.
-Please note that implementing an industrial strength beyond-state-of
-the-art language platform means we have to collaborate with as many
-experts as possible to reduce the risk of failing.
+The second responsibility and role should stay with the PBF: connecting and
+disseminating to open source and business communities. Please note that
+implementing an industrial strength beyond-state-of the-art language
+platform means we have to collaborate with as many experts as possible to
+reduce the risk of failing.
+The third responsibility, acting as a means to bring known developers into
+the project if, for example, of the core developers were to fall ill, is
+going to be hard to duplicate with the same flexibility and we may have use
+more bureaucratic instruments such as a contract amendment.
As a result, all partners agree to the following consortium shape:
More information about the Pypy-commit