[pypy-svn] r3609 - pypy/trunk/doc/funding/negotiations
hpk at codespeak.net
hpk at codespeak.net
Thu Apr 1 11:43:22 CEST 2004
Author: hpk
Date: Thu Apr 1 11:43:21 2004
New Revision: 3609
Added:
pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt
- copied, changed from r3608, pypy/trunk/doc/funding/negotiations/reponses_2nd_april.txt
Removed:
pypy/trunk/doc/funding/negotiations/reponses_2nd_april.txt
Log:
- renamed the typoed filename
- another try at getting the cross-references right
(if it fails i will just ask christian :-)
Deleted: /pypy/trunk/doc/funding/negotiations/reponses_2nd_april.txt
==============================================================================
--- /pypy/trunk/doc/funding/negotiations/reponses_2nd_april.txt Thu Apr 1 11:43:21 2004
+++ (empty file)
@@ -1,159 +0,0 @@
-.. include:: ../crossreferences.asc
-
-========================================================================
-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. But the consortium has now revisited each work package description
-and thus provides a much better and more consistent work plan. We were
-able to retain all Workpackages and tasks by beeing more specific
-about the exact deliverables and tasks. Also each of the partners
-in the consortium now has to accept a much higher risk and responsbility
-for producing all deliverables with the reduced resources.
-
-The consortium intends to interact early and often with specific
-communities and individuals. This should generally 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 language end-users by on various levels.
-Note that end-users of the PyPy STREP are mainly
-
-a) language integrators who want to port and leverage their domain
- specific extensions to PyPy.
-
-b) researchers who want to explore and understand new optimization
- and language techniques
-
-In particular the following deliverables will serve involvement
-of those end-users:
-
-- D03.3 will help developers to port existing C-extensions to PyPy
-- D04.4 will help researchers to do innovative language research
-- D11.1 and D11.2 provide reports and a useful implementation to
- 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 Zuerich
-
-**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.
-
-TOBECOMPLETED
-
-
-**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).**
-
-The appropriate chapter of B1.0 in the TA has been extended accordingly.
-Summarizing we mainly have the following theoretically new approaches
-and solutions:
-
-- Separation of Bytecode interpretation and manipulation of objects,
- using a Very-High-Level language to specify semantics
-
-- "Abstract interpretation" to enable an efficient new way to
- close the gap between a VHLL and efficient low-level code,
- including advanced JIT-Compilers
-
-- "Translation aspects" will - among other things - encapsulate
- Multithreading and memory mangagement models which today
- have to be manually coded all over a language implementation.
-
-The practical implementation leverages an *industrial-strength*
-language implementation (Python) thus connecting the STREP to a
-large user base. There even is a chance that PyPy will form
-the fundation of the "next generation" Python implemention
-commonly refered to as Python3000. Once we have reports and
-specific versions of PyPy we will reach out to non-python
-communities (see WP14_).
-
-**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".
-
-**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.
-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.
-
-**Action: The DoW will be modified to make it clearer what type of tests we are
-referring to.**
-
-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.
-
-
-**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
-performance and practicality of introducing aspects to the language
-level. The WP09_ and WP10_ have also 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.
-
-**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 GPL. While
-all consortium partners commit to produce source code always under an MIT
-license the project explicitely reserves the right to include GPLed software.
-In the latter case some versions of PyPy might have to be released under
-a GPL license due to its viral nature.
-
-**Action: The DoW will be modified to avoid this [user] confusion.**
-
-The complete DoW has been clarified accordingly. Mainly end-users
-of the PyPy STREP will be language integrators and researchers.
-Please note especially, that Users of Applications running on top of PyPy
-are not refered to as "End users" but - if neccessary - as "application users".
Copied: pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt (from r3608, pypy/trunk/doc/funding/negotiations/reponses_2nd_april.txt)
==============================================================================
--- pypy/trunk/doc/funding/negotiations/reponses_2nd_april.txt (original)
+++ pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt Thu Apr 1 11:43:21 2004
@@ -1,5 +1,19 @@
-.. include:: ../crossreferences.asc
+.. _WP01: ../B6.7.wp01_management.html
+.. _WP02: ../B6.7.wp02_maintenance.html
+.. _WP03: ../B6.7.wp03_synchronisation.html
+.. _WP04: ../B6.7.wp04_core.html
+.. _WP05: ../B6.7.wp05_translation.html
+.. _WP06: ../B6.7.wp06_core_optimisations.html
+.. _WP07: ../B6.7.wp07_translator_optimisations.html
+.. _WP08: ../B6.7.wp08_dynamic_optimisation.html
+.. _WP09: ../B6.7.wp09_search_and_logic.html
+.. _WP10: ../B6.7.wp10_aspects_and_contracts.html
+.. _WP11: ../B6.7.wp11_embed_in_hardware.html
+.. _WP12: ../B6.7.wp12_validations.html
+.. _WP13: ../B6.7.wp13_integration_config.html
+.. _WP14: ../B6.7.wp14_documentation.html
+.. |e| unicode:: 0x20 .. doesn't work with plain spaces
========================================================================
Responses to Actions put up in the Meeting notes from 16th of March 2004
========================================================================
More information about the Pypy-commit
mailing list