[pypy-svn] r3693 - in pypy/trunk/doc/funding: . negotiations
hpk at codespeak.net
hpk at codespeak.net
Fri Apr 2 08:36:53 CEST 2004
Date: Fri Apr 2 08:36:53 2004
New Revision: 3693
- went through all the responses again and traced
some things to the deliverables we added and clarified
- rephrased some bits from wp14 accordingly
--- pypy/trunk/doc/funding/B6.7.wp14_documentation.txt (original)
+++ pypy/trunk/doc/funding/B6.7.wp14_documentation.txt Fri Apr 2 08:36:53 2004
@@ -36,10 +36,10 @@
Support the dissemination process at all levels.
-- Write, disseminate and archive reports about each "development sprint"
+- Write, disseminate and archive reports about each development sprint
-- In cooperation with all other participants, present a detailed joint report
- to the commission about agile methodologies employed by the project.
+- Gathering feedback from participants, present a detailed joint report
+ about agile methodologies employed by the project.
- Ensure that all reports and publications are effectively disseminated to
python and non-python communities.
@@ -84,9 +84,10 @@
architecture. 2 specific workshops will be arranged in this manner
(during phase 1 and at the end of phase 3).
-- 3 domain specific Workshops will be organized during the course of the PyPy STREP
- to allow for adaptation of details on specific feedback issues from specific target
- groups (industrial companies, game developing companies and SME:s).
+- organize Workshops during the course of the PyPy STREP to allow for
+ adaptation of detail planning on specific feedback issues from
+ specific target groups (industrial companies, game developing
+ companies and SME:s).
.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc
@@ -100,9 +101,10 @@
- D14.5 Documentation of the development process and "Sprint driven development" in particular
- D14.6 Organize three domain specific Workshops during phase 3 with various business and research
communities. Reports about these workshops.
-- D14.7 Arrange 2 nondomain specific workshops disseminating development process
- (during phase 1 and after phase 3)
-- D14.8 Participate in conferences throughout the project process.
+- D14.7 Arrange two nondomain specific workshops disseminating development process
+ and results (during phase 1 and phase 3)
+- D14.8 Participation of PyPy researchers and developers in conferences
+ throughout the project process.
.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc
--- pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt (original)
+++ pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt Fri Apr 2 08:36:53 2004
@@ -21,11 +21,13 @@
**Action: the involvement and funding mechanism of PBF should be fully described**
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. We presume until further feedback that this is
-a viable model and have allocated resources and partners in the DoW
+future neccessary 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. We presume until further feedback that
+this is a viable model and have allocated resources and partners in the
+DoW accordingly. The PBF is to bring in experts on specific problems
+arising during the process of the project. This will decrease the risk
**Action: in first instance no workpackages should be removed
as savings should be obtained through economizing the work planning.**
@@ -33,24 +35,25 @@
The consortium has now revisited each work package description and has
provided a much better, more consistent and more detailed work plan. We
were able to retain all Workpackages but were more specific about the
-exact deliverables and tasks. It was also necessary to reduce the scope
-of some of the work packages. But primarily each of the partners in the
-consortium now has to accept a much higher risk and responsbility for
-efficiently producing all deliverables with the reduced resources.
+exact deliverables and tasks. This lead to an economized and tightened
-The consortium intends to interact early and often with specific
-communities and individuals. This should effectively mobilise our resources.
+However, each of the partners in the consortium now has to accept a
+much higher risk and responsbility for efficiently producing all
+deliverables with the reduced resources. The consortium relies now
+more heavily on interacting early and often with specific communities
+and individuals to effectively mobilise our resources.
**Action: provide fully completed and quality checked CPFs.**
-We have completed and greatly improved the CPFs. The project office's
-feedback to our consortium-proposal may still make further changes neccessary.
+We have completed and improved the CPFs. The project office's 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 on various levels.
-Note that end-users of the PyPy STREP are mainly
+Direct end-users of the PyPy STREP are mainly
a) language integrators who want to port and leverage their domain
specific extensions to PyPy.
@@ -67,10 +70,13 @@
end-users and Axis communications in particular.
- D12.1-3 will provide experimental versions of PyPy to various
groups of end-users (developers and researchers alike).
-- D13.2 will provide a tool for end-users to support customizing PyPY
- to domain specific needs.
-- D14 deliverables provide interaction with various end user communities
- including the Research center of IBM in Zurich
+- D13.2 will provide a tool for end-users to support customizing PyPy
+ to domain specific needs and D13.3 will complement this effort with a
+- all D14 deliverables will provide interaction with various end user
+ communities already including the Research center of IBM in Zurich and
+ Axis Communications in Sweden. Further contacts will be made to
+ reach out to end user in- and outside the python communities.
**Action: the body text should be preserved, and a full tracing to
workpackages should be ensured (adding tasks, subtasks, and defined
@@ -79,8 +85,8 @@
We have now fully traced especially the B1 objectives and B6.0 detailed implementation
chapters in all Workpackage descriptions and deliverables. Task descriptions
-are now more specific and detailed and according deliverables have been added.
+are now more specific and detailed and deliverables have been added according
+to the body text descriptions.
**Action: An explanation on how the envisaged work goes beyond the
state-of-the-art (both in theoretical concepts and solutions and in the
@@ -102,7 +108,7 @@
Multithreading and memory mangagement models which today
have to be manually coded all over a language implementation.
-Each one of these notions is interesting beyond the scope of Python.
+Each one of these novelties is interesting beyond the scope of Python.
Moreover, the practical implementation leverages an *industrial-strength*
language implementation (Python) thus connecting the STREP to a large user
base. It is possible that PyPy will form the fundation of the "next
@@ -112,58 +118,67 @@
**Action: the coordination and management model should be clarified.**
+The B5 chapter has been revised to clarify the management and coordination
+structure of the coordinator, the project management and technical board.
+This chapter now also reflects the new consortium structure.
**Action: Rename the first phase.**
-The first phase has been renamed to "Building a flexible interpreter".
+The first phase has been renamed to "Building a flexible interpreter".
+In particular the first phase (D04.4) will provide a Research tool and
+various reseach results on building a highly flexible and modular
+interpreter will be published on conferences (see D05.1, D05.3, D05.4).
**Action: The DoW will be modified to clarify this [multithreading] issue**.
-The B1.0 objectives chapter has been extended to clarify the issue.
-The WP07_ description and D7.3 and D7.1 in particular have been clarified.
+The B1.0 objectives chapter has been extended to clarify the issue. The
+WP07_ description, and D7.3 and D7.1 in particular, have been clarified.
Summarizing, today there are many complicated issues in current language
implementations such as Java, Perl and Python itself. All such
industrial strength language implementations usually decide early on a
-specific threading model. The PyPy project researches ways to allow
-making this decision much later and well encapsulated. Moreover, massive
-parallelism with millions of threads are to become both practical and easy to
-program without consuming operating system resources.
+specific threading and memory management model. The PyPy project
+pioneers ways to allow making this decision much later and well
+encapsulated (D05.3, D05.4). Moreover, massive parallelism with millions
+of threads are to become both practical and easy to program without
+consuming operating system resources (D07.1, D07.3, D07.4)
**Action: The DoW will be modified to make it clearer what type of tests we are
The deliverables of WP04 and WP05 now specify more clearly the test selection.
-The original Python developers will be consulted if there is a doubt whether
-something is a "language feature" or an "implementation feature" test.
+In general, we select language compliancy tests as the primary measurement
+utility and disregard testing of implementation details specific to the
+current C-Python implementation. The original Python developers will be consulted
+if there is a doubt whether something is a "language feature" or an
+"implementation feature" test.
**Action: The relevant [AOP/logic] sections of the DoW will be extended.**
-Examples are now given in B6.0 to clarify that PyPy aims at providing
-access and interception points to internals greatly improving
+Examples are now given in B6.0 to clarify that PyPy aims at researching
+and providing access and interception points to internals greatly improving
performance and practicality of introducing aspects to the language
-level. The WP09_ and WP10_ have been updated accordingly.
+level and enabling Semantic Web applications. The WP09_ and WP10_ have
+been updated accordingly.
**Action: The DoW will define tasks and deliverables that will be used as vehicles for dissemination to people outside the Python community.**
-WP14_ and WP11_ now define explicit workshops and dissmentiation activities.
-Moreover, several reports and publications have been explicitely added to all
-Work Packages. The B6.0 and B1.0 already mentioned various dissemination
-activities which are now fully traced in the DoW tasks and deliverables. Special
-care has been taken that the research report, publication and workshop deliverables will
-be disseminated to non-python communities.
+WP14_ and WP11_ now define explicit workshops and dissmentiation
+activities. Moreover, several reports and publications have been
+explicitely added to all Work Packages. The B6.0 and B1.0 already
+mentioned various dissemination activities which are now fully traced in
+the DoW tasks and deliverables. Special care has been taken that the
+research report, publication and workshop deliverables will be
+disseminated to non-python communities (see especially D14.1-8, D11.1-2).
**Action: The DoW will include a justification of the license chosen. Compatibility with the GPL will be addressed.**
-The chapter in B3.0 Impact chapter which mentioned licensing has been
-extended to cover a short discussion of choosing the MIT license over
+The license subchapter of "B3.0 Impact" has been extended to cover a
+short discussion of choosing the MIT license over the GPL.
In summary, the risk of a complete "hostile takeover" from some
commercial company is low considering the partners and the communities
-involved. However, our results and source code can be freely used from
+involved. Thus the protection that the GPL offers is not critical to the
+project. However, our results and source code can be freely used from
GPL licensed projects.
While all consortium partners commit to produce source code and results
@@ -183,5 +198,6 @@
STREP are language integrators and researchers. The line between beeing
an end-user and a contributor to the project is designed to be easy to cross
thus contributing to effective mobilization of resources. Nevertheless, The PyPy
-implementation is indirectly useful to all users running applications (especially
-novel ones) on top of PyPy.
+implementation is indirectly useful to all users running applications
+on top of PyPy especially if applications learn to exploit the performance
+and flexibility features that PyPy will offer.
More information about the Pypy-commit