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

[hpk at codespeak.net]

Author: hpk
Date: Wed Mar 31 23:22:10 2004
New Revision: 3593

Added:
   pypy/trunk/doc/funding/negotiations/reponses_2nd_april.txt
Log:
- a first draft of a "action->response" document. 

- i am currently thinking about incorporating the
  changelog in there

- it's really just a first draft (with lots of gaps) 
  and probably has ReST errors (to lazy to test right now) 



Added: pypy/trunk/doc/funding/negotiations/reponses_2nd_april.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/negotiations/reponses_2nd_april.txt	Wed Mar 31 23:22:10 2004
@@ -0,0 +1,109 @@
+========================================================================
+Responses to Actions put up in the Meeting notes from 16th of March 2004 
+========================================================================
+
+
+Action: the involvement and funding mechanism of PBF should be fully described
+
+The project coordinator sent a mail on 31th 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. 
+
+
+
+Action: in first instance no workpackages should be removed 
+as savings should be obtained through economizing the work planning.
+
+After the withdrawal of MPI and the budget pressure there wasn't 
+enough time to discuss the complete work-plan with all consortium
+partners.  The consortium has now revisited each work package description 
+and provides a much better and more consistent work plan, now.  We were
+able to retain all Workpackages and tasks by beeing more specific 
+about the exact deliverables and tasks.  As a result each of the partners
+in the consortium now had to accept a higher risk and responsbility 
+for producing all deliverables.  
+
+The consortium intends to interact early and often with specific
+communities and individuals. This should lead to a much better
+mobilization of resources. 
+
+
+
+Action: provide fully completed and quality checked CPFs.
+
+We have much improved and completed the CPFs.  The project office's
+responses to our consortium-proposal (sent by the PyPy project
+coorindator on 29th of March) may make further changes neccessary, 
+though. 
+
+
+
+*Action*: Also the reduction of the end-user involvement represents already 
+a reduction in work and required budget._
+
+We still plan to involve end-users on various levels. 
+
+(...)
+
+
+
+Action: the body text should be preserved, and a full tracing to
+workpackages should be ensured (adding tasks, subtasks, and defined
+output). If traceability is not clear, there may come a request to add a
+line stating the body text should be considered
+
+We have now fully traced especially the B1 objectives and B6.0 detailed implementation
+chapters in the Workpackage descriptions and deliverables.   
+
+TOBEDONE 
+
+
+
+
+Action: An explanation on how the envisaged work goes beyond the
+state-of-the-art (both in theoretical concepts and solutions and in the
+practical implementation should be provided, and how this contributes to
+development beyond the Python domain).
+
+TOBEDONE 
+
+
+
+Action: the coordination and management model should be clarified.
+
+TOBEDONE 
+
+
+Action: Rename the first phase. 
+
+The first phase has been renamed to "Providing a novel language research tool"
+
+
+TOBEDONE
+
+
+Action: The DoW will be modified to clarify this [multithreading] issue.
+
+TOBEDONE 
+
+Action: The DoW will be modified to make it clearer what type of tests we are 
+referring to
+
+The definition of WP05 specifies the test selection process.
+...
+
+
+
+Action: The relevant [AOP/logic] sections of the DoW will be extended.
+
+TOBEDONE
+
+
+Action: The DoW will define tasks and deliverables that will be used as vehicles for dissemination to people outside the Python community.
+
+
+Action: The DoW will include a justification of the license chosen. Compatibility with the GPL will be addressed.
+
+
+Action: The DoW will be modified to avoid this [user] confusion.