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

[hpk at codespeak.net]

Author: hpk
Date: Tue Oct  7 00:11:57 2003
New Revision: 1600

Modified:
   pypy/trunk/doc/funding/B4.5_resources.txt
Log:
smore more glory talk about sprints and pypy. 
didn't have enough time and am too tired now to continue. 
maybe more tommorow morning (laura asked for some
more details). 



Modified: pypy/trunk/doc/funding/B4.5_resources.txt
==============================================================================
--- pypy/trunk/doc/funding/B4.5_resources.txt	(original)
+++ pypy/trunk/doc/funding/B4.5_resources.txt	Tue Oct  7 00:11:57 2003
@@ -7,6 +7,8 @@
 but the above sentence seems to indicate that a lot of more stuff should go here. 
 Please feel free to enhance/modify!
 
+Coding Sprints are the key to PyPy's technical development 
+----------------------------------------------------------
 
 Key to PyPy's technical development and research are so called "sprints".  These publically 
 announced one-week meetings serve as an intense working forum to rapidly discuss 
@@ -17,22 +19,26 @@
 avoided. If something seems too hard to test or to pin down explicitely this is 
 taken as an indication of an underlying design problem.  
 
-Note that more traditional approaches even in the free software world usually follow a model 
-where developers work alone and only meet to talk.  Instead with sprint-driven development 
-talking and actually implementing resulting ideas ensures a more focused approach with fast 
-feedback cycles.  Moreover, while coding in pairs developers educate each other which leads 
-to a broader common understanding of PyPy.  During a sprint multiple pairs want to work in 
-parallel which adds pressure on design decisions so that independent development of components 
-of the system is possible.  Thus sprints not only deepen the communication and understanding 
-among researchers and developers but they imply a working process which enhances the software 
-design in multiple ways. 
-
-It is helpful to understand that with a very-high-level-language like Python 
-rapid development in coding-sprints becomes especially effective.  A VHLL-language allows to 
-focus on ideas rather than on low-level language details.  In combintation with pervasive 
-test-driven development this eases high-quality rapid evolution towards the intendent 
-goals.  Obviously, the PyPy developers are very experienced with Python and bigger applications
-in general. Thus the full potential of coding-sprints is unvealed during PyPy sprints. 
+Note that more traditional approaches usually follow a model where developers work alone 
+and only meet to talk.  Instead with sprint-driven development talking and actually 
+implementing resulting ideas ensures a more focused approach with fast feedback cycles.  
+While the free software community is successful especially because of it's open 
+communication model sprints are an accelerator to this process.  While coding in pairs 
+developers educate each other which leads to a broader common understanding of the project.  
+During a sprint multiple pairs want to work in parallel which adds pressure on design 
+decisions so that independent development of components of the system is possible.  
+Thus sprints not only deepen the communication and understanding among researchers and 
+developers but they imply a working process which enhances the software design in multiple ways. 
+
+With a very-high-level-language like Python rapid development in coding-sprints becomes 
+especially effective.  A VHLL-language generally allows to focus on ideas rather than on low-level 
+language details.  In combintation with pervasive test-driven development this eases high-quality 
+rapid evolution towards the intendent goals.  Obviously, the PyPy developers are very experienced 
+with Python and bigger applications in general. Thus the full potential of coding-sprints is 
+unvealed during PyPy sprints. In less than five weeks worth of development (during four sprints) 
+the group produced a working prototype which is a big success not only in the eyes of its
+developers.  
+
 
 FIXME LAURA: <holger> should i add more about the involvement of the Python community here? 
 and something about the python-sprint-culture (Zope3, Plone, twisted) in general?