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

[hpk at codespeak.net]

Author: hpk
Date: Thu Apr  1 15:47:56 2004
New Revision: 3634

Modified:
   pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt
Log:
- some small enhancements and corrections regarding 
  the mail-date 
  
Alastair, please check that 29th is indeed the day you
sent the PBF/consortium proposal



Modified: pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt
==============================================================================
--- pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt	(original)
+++ pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt	Thu Apr  1 15:47:56 2004
@@ -20,10 +20,12 @@
 
 **Action: the involvement and funding mechanism of PBF should be fully described**
 
-The project coordinator sent a mail on the 31th of March detailing the
+The project coordinator sent a mail on the 29th of March detailing the
 future role of the PBF within the PyPy research project.  At the same
 time, participants formerly supposed to work through the PBF are now to
-enter the consortium.  
+enter the consortium.  We presume until further feedback that this is
+a viable model and have allocated resources and partners in the DoW
+accordingly. 
 
 **Action: in first instance no workpackages should be removed 
 as savings should be obtained through economizing the work planning.**
@@ -42,13 +44,12 @@
 **Action: provide fully completed and quality checked CPFs.**
 
 We have completed and greatly improved the CPFs.  The project office's
-responses to our consortium-proposal (sent by the PyPy project
-coorindator on 29th of March) may still make further changes neccessary. 
+feedback to our consortium-proposal may still make further changes neccessary. 
 
 **Action: Also the reduction of the end-user involvement represents already 
 a reduction in work and required budget.**
 
-We still plan to involve language end-users by on various levels. 
+We still plan to involve language end-users on various levels. 
 Note that end-users of the PyPy STREP are mainly 
 
 a) language integrators who want to port and leverage their domain