[pypy-svn] r3843 - pypy/trunk/doc/funding

[hpk at codespeak.net]

Author: hpk
Date: Tue Apr  6 17:12:21 2004
New Revision: 3843

Modified:
   pypy/trunk/doc/funding/changelog-wp.txt
Log:
- reworded the changelog intro to name more explicitely
  and without fluff ( :-) what we have been doing and
  which risks we are taking 



Modified: pypy/trunk/doc/funding/changelog-wp.txt
==============================================================================
--- pypy/trunk/doc/funding/changelog-wp.txt	(original)
+++ pypy/trunk/doc/funding/changelog-wp.txt	Tue Apr  6 17:12:21 2004
@@ -1,27 +1,20 @@
-We have made the following modifications to our work packages to comply
-with the requests made at the negotiation meeting of <when was the thing>?
-Most notable is an increase in the number of dissemination deliverables.
-By more fully documenting our dissemination process in the
-form of produced deliverables, we trust we have satisfied the request
-that we align our work packages with the promises made in our proposal.
-These dissemination deliverables were already implicit in our tasks, but 
-now have been made explicit. This has the added advantage of making it
-easier to objectively measure our progress.
-
-We have also added reports for language users who are outside of the
-existing Python community.
-
-However, the reduction of budget has meant that the consortium has
-been exposed to an increased risk of failure.  Should our efforts to
-mobilise the Python and Open Source communities fail,  we will have
-to rack up a lot of unpaid overtime in order to complete our tasks.
-This is true even though, in response to requests, we have changed our
-emphasis from producing an extremely robust implementation of PyPy
-which is immediately suitable for industrial use, to producing a
-functional but less thoroughly tested version, and communicating our
-research to the academic, government, and industrial users who are
-our primary stakeholders.
-
+All work packages have been clarified and described in more detail --
+according to the requests of the EU Project Office.  Most notable is the
+increase in the number of dissemination deliverables.  These
+dissemination deliverables are mostly making explicit what we already
+had in the detailed work plan.  This also makes it easier to objectively
+measure our progress.
+
+We also added reports and publications for communities 
+outside of the existing Python communities. We generally
+place more emphasis on communicating our research and efforts 
+to academic, industrial and open source communities. 
+
+However, the reduction of budget makes us rely more heavily on
+contributions from other open source projects and developers.  Note that
+the consortium partners are explicitely taking the risk of receiving
+less contributions than expected and agreed to still commit to produce
+all deliverables despite the budget cuts.  
 
 WP01 -50% budget, added 3 deliverables::
     tracing B4 and B5, more detailed descriptions of pre-existing tasks