[pypy-svn] rev 1864 - pypy/trunk/doc/funding

[jacob at codespeak.net]

Author: jacob
Date: Mon Oct 13 19:06:58 2003
New Revision: 1864

Modified:
   pypy/trunk/doc/funding/B3.impact.txt
Log:
Removed FIXMEs

Modified: pypy/trunk/doc/funding/B3.impact.txt
==============================================================================
--- pypy/trunk/doc/funding/B3.impact.txt	(original)
+++ pypy/trunk/doc/funding/B3.impact.txt	Mon Oct 13 19:06:58 2003
@@ -1,8 +1,5 @@
 .. include:: crossreferences.asc
 
-.. FIXME_NICO FIXME_ALASTAIR : proof-read it
-.. FIXME think about where to include Logilab and DFKI references
-
 Potential impact
 ---------------------------------------------------------------------------
 
@@ -156,10 +153,11 @@
 huge amount of memory to achieve the highest performance speed.
 
 Python with greater speed will seamlessly improve the offerings of
-those European Companies who already develop using Python.  Moreover, 
-some companies resist using Python because of speed concerns.  If 
-execution speed, rather than development speed is of paramount importance, then Python is currently not a very good language choice. A faster Python
-would thus have more appeal.
+those European Companies who already develop using Python.  Moreover,
+some companies resist using Python because of speed concerns.  If
+execution speed, rather than development speed is of paramount
+importance, then Python is currently not a very good language
+choice. A faster Python would thus have more appeal.
 
 Strategic Impact of Open Source
 ================================
@@ -223,29 +221,32 @@
 Source language, just so that they can have control over their own destiny
 and indicate their displeasure with Microsoft at the same time.
 
-This is a tremendous opportunity for us. Every Java and VB user that 
-switches to Python does not pay license fees to Sun or Microsoft and helps the European balance of Trade.  
+This is a tremendous opportunity for us. Every Java and VB user that
+switches to Python does not pay license fees to Sun or Microsoft and
+helps the European balance of Trade.
 
 Of course, all the PBF members are predicting that an improved Python
 will improve their sales, both domestic and foreign.  The dominance of
-the PBF by European companies means this can only improve Europe's trade balance.
+the PBF by European companies means this can only improve Europe's
+trade balance.
 
 European Dimension
 ===================
 
 PyPy is an extremely high-profile project, as is only right since we
-intend to utilize the estimated 175,000 Python users as our 
-user-base.  Consequently, it is essential that we have the full
-support of the International Python community.  Our success in that
-regard was more fully spoken about in B3.1, International Standards,
-but suffice to say that the only possible dimensions for this project
-is 'Europe wide' or 'World Wide'.  We could not find the expertise
-needed in a single country, and nor could we attain 
-international acceptance without involving the top members of the
-Python community.  Working at a smaller (single-country) scale would 
-only 'fork the project' -- make a local version which is of limited use, while the main line project continued to develop in another direction. 
-At best we would have a ghetto.  At worst, we would have two hostile 
-camps slinging insults at each other over which 'was the real Python'.  
+intend to utilize the estimated 175,000 Python users as our user-base.
+Consequently, it is essential that we have the full support of the
+International Python community.  Our success in that regard was more
+fully spoken about in B3.1, International Standards, but suffice to
+say that the only possible dimensions for this project is 'Europe
+wide' or 'World Wide'.  We could not find the expertise needed in a
+single country, and nor could we attain international acceptance
+without involving the top members of the Python community.  Working at
+a smaller (single-country) scale would only 'fork the project' -- make
+a local version which is of limited use, while the main line project
+continued to develop in another direction.  At best we would have a
+ghetto.  At worst, we would have two hostile camps slinging insults at
+each other over which 'was the real Python'.
 
 We have avoided all of these problems by carefully making the PyPy project
 sufficiently international, by discussing this proposal for nearly a year at
@@ -349,12 +350,6 @@
   updated on project process and development progress. The assistant
   project manager will be responsible for this.
 
-* The commercial activities need to be divided into 'techie' 'financial' and
-  'other' and WP 10 is about making these things. So Project Management can    
-  see that it is done, but can only help in making the stuff.
-
-.. FIXME coordinate with Alex on this point.
-
 * to ensure that interested external parties will be able to use knowledge
   acquired in the PyPyproject we will host two workshops during the
   project, one after 6 months and the first review workshop and one at the
@@ -373,7 +368,7 @@
 FOSDEM (Free and Open Source Developer European Meeting),
 ECOOP (European Conference for Object Oriented Programming)
 
-.. FIXME: add more conferences
+More conferences will be added once the project gets started.
 
 Exploitation
 +++++++++++++
@@ -500,5 +495,5 @@
 
 
 .. [PEP1]  http://www.python.org/peps/pep-0001.html
-.. FIXME grab it for appendix inclusion
+