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

[alastair at codespeak.net]

Author: alastair
Date: Wed Mar 24 19:46:36 2004
New Revision: 3378

Modified:
   pypy/trunk/doc/funding/negotiations/negotiation_notes-1.txt
Log:
Typos and more action oriented exposition. 


Modified: pypy/trunk/doc/funding/negotiations/negotiation_notes-1.txt
==============================================================================
--- pypy/trunk/doc/funding/negotiations/negotiation_notes-1.txt	(original)
+++ pypy/trunk/doc/funding/negotiations/negotiation_notes-1.txt	Wed Mar 24 19:46:36 2004
@@ -1,33 +1,36 @@
-Additional Notes from the negotation meeting on 16th of March 
+Additional Notes from the negotiation meeting on 16th of March 
 --------------------------------------------------------------
 
-These are revised selected notes complementing Mr. van Rooys notes from 
+These are revised selected notes complementing Mr. van Rooy's notes from 
 the negotiating meeting at 16th of March 2004. He is expected to
 only select a subset of this notes and integrate it into his notes. 
 
 - Laura Crughton -> Laura Creighton 
 
-- beyond-state-of-the-art: Commission staff asked for clarification
+- Beyond-State-Of-The-Art: Commission staff asked for clarification
   regarding the first phase of the project, "reaching state of the art".
   Members of the consortium acknowledged that the title is misleading as
-  the first phase already implements a research tool which goes well
-  beyond state of the art.  It already is to provide a uniquely modular
-  and flexible very high level interpreter (VHLL) architecture
-  translated into a low level language yet maintaining compatibility
-  with an industrial strength language.  
-
-- multithreading: Clarifications were requested from the commission
-  staff regarding the goals of multithreading and massive parallelism.
-  Members of the consortium refered to complicated issues in current
+  the first phase already implements a research tool which goes well beyond
+  state of the art and the DoW already explains how the modular
+  architecture for the interpreter to be developed within the first phase
+  is a significant advance on the current approaches in that area.
+
+  Action: Rename the first phase.
+
+- Multi-Threading: Clarifications were requested from the commission
+  staff regarding the goals of multi-threading and massive parallelism.
+  Members of the consortium referred to 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 aims at providing a
-  way to allow making this decision much later and indepdently from
+  way to allow making this decision much later and independently from
   other aspects. Moreover, massive parallelism with millions of threads
   are to become both practical and easy to program. Today, this is
-  not the case with practical languages. 
+  not the case with practical languages.
 
-- tests: The PyPy projects intends to measure compliancy with the
+  Action: The DoW will be modified to clarify this issue.
+
+- Tests: The PyPy projects intends to measure compliance with the
   C-implementation of Python by passing a multitude of tests.
   However, it is not sufficiently clear which categories of tests are
   to be selected from the current C-implementation.  Members of the
@@ -37,17 +40,25 @@
   passed is a task in WP05.  In a case of doubt the original Python
   developers will be consulted.
 
+  Action: The DoW will be modified to make it clearer what type of tests we
+  are referring to and the definition of WP05 will specify the test
+  selection process.
+
 - AOP & logic programming: The commission staff requests clarifications
   and a better explanation of the work packages on aspect oriented and
   logic programming.  Small Examples of what is to be achieved should be
   given. 
 
-- broader dissemination: The commission staff remarked that the current
-  DoW does not include dissemination to organizations and people outside
+  Action: The relevant section of the DoW will be extended.
+
+- Broader Dissemination: The commission staff remarked that the current
+  DoW does not include dissemination to organisations and people outside
   the python communities.  The consortium intends to do workshops for
   outside communities but this is currently not reflected in the list of
-  tasks and deliverables.  Action: define tasks and deliverables
-  regarding dissemination to non-python communities. 
+  tasks and deliverables. 
+
+  Action: We will define tasks and deliverables that we use as vehicles for
+  dissemination to people outside the Python community.
 
 - F/OSS licenses: The consortium intends to release all source code
   under the MIT license. The commission staff remarked that this open
@@ -58,7 +69,10 @@
   with interests in the PyPy project want to be able to freely use the
   code base in commercial projects. 
 
-- "users": There is some confusion regarding the definition of "the
+  Action: The DoW will include a justification of the license
+  chosen. Compatibility with the GPL will be addressed.
+
+- "Users": There is some confusion regarding the definition of "the
   user".  The so called end user of the PyPy project is an implementor
   adapting it to domain specific environments.  Moreover, other
   researchers are likely to be users as well because the PyPy
@@ -66,3 +80,5 @@
   line between such users and contributors is set up to be easy to
   cross. However, end users of applications running on top of a PyPy
   variant will usually not know about this fact.  
+
+  Action: The DoW will be modified to avoid this confusion.