[pypy-svn] r3405 - pypy/trunk/doc/funding/negotiations

[hpk at codespeak.net]

Author: hpk
Date: Thu Mar 25 12:12:24 2004
New Revision: 3405

Modified:
   pypy/trunk/doc/funding/negotiations/email-eu-1.txt
Log:
improved the draft mail 
(hope we didnt interfere with each other, Alastair)

the main thing is that in the first paragraphs i introduced
some more explanation and reasoning about what we are going
to do.  I do think we should not just shift money and partners
around but talk about our intentions.  



Modified: pypy/trunk/doc/funding/negotiations/email-eu-1.txt
==============================================================================
--- pypy/trunk/doc/funding/negotiations/email-eu-1.txt	(original)
+++ pypy/trunk/doc/funding/negotiations/email-eu-1.txt	Thu Mar 25 12:12:24 2004
@@ -6,29 +6,27 @@
 Dear Mr van Roy, 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 according
-to the guidelines of the sixth framework program. 
-
-This doesn't impose a big problem to the project because it is - also
-contrary to our previous belief - possible that individuals enter the
-consortium.  We believe this is due to the new rule that partners are
-liable to each other. 
-
-[Moreover, we were able to get the Max Planck Institute back into the
-consortium: after more discussion they now agree to take budget cuts
-similar to those of the other partners in the consortium.]
+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.
+
+For the first part we can substitute by bringing in three of the
+individuals as consortium partners. The fourth person is to be employed
+by AB Strakt.  We didn't know before that it was possible to have
+individuals as consortium partners. It's still a bit unfortunate
+because it seems to be harder now to bring in specific experts
+later on.  
+
+But the second responsibility and role should stay with the PBF:
+connecting and disseminating to open source and business communities.
+Also 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. 
 
 As a result, we now intend to bring the consortium into its final 
 shape like follows: 
 
-1. MPI shall employ Samuele Pedroni, taking part in core work 
-   and will also bring in the end user view into the project. 
-
-   Discussion: We don't think there is any problem as MPI is
-   an acknowledged partner in many EU projects. 
-
-            -------------- or ----------------------
-
 1. The financiers of AB Strakt have promised to provide matching funding
    for Samuele Pedroni. Samuele joins AB Strakt as an employee. Previously
    he was planned to work through the MPI at core parts of the PyPy
@@ -40,7 +38,8 @@
 
 2. Christian Tismer, Alex Martelli and Holger Krekel shall enter the
    project as individual contractors using the FCF model.  All three of
-   them work as independent contractors for a long time.  They provide
+   them work as independent contractors for a long time and are active
+   in business, research and education communities.  They provide
    matching funding through savings, part time consultancy work and
    reduced income.  Their normal costs plus 20% overheads are to be 
    specified in the budget.
@@ -89,7 +88,7 @@
 specify direct costs, it does not have the means to identify indirect
 costs.
 
-The PBF is no longer responsible for core activities in the project,
+The PBF is no longer directly responsible for core activities in the project,
 and its budget is 7% of the entire project budget. We hope this will
 be reasonable from a financial control point of view.