[pypy-svn] r43488 - pypy/extradoc/talk/ep2007

[hpk at codespeak.net]

Author: hpk
Date: Fri May 18 16:41:40 2007
New Revision: 43488

Modified:
   pypy/extradoc/talk/ep2007/development.txt
Log:
quick refactoring 


Modified: pypy/extradoc/talk/ep2007/development.txt
==============================================================================
--- pypy/extradoc/talk/ep2007/development.txt	(original)
+++ pypy/extradoc/talk/ep2007/development.txt	Fri May 18 16:41:40 2007
@@ -1,14 +1,18 @@
-Post Mortem: development practices and infrastructure
-in the EU open source research project PyPy
+PyPy: Why and how did it (not) work? 
+-------------------------------------------------
 
-How did the development process and infrastructure of the PyPy
-project change during the period of EU-funding?  We will talk about 
-our experiences regarding the evolving development environment (version 
-control, automated test-driven development, sprints, synchronization, 
-"conceptual integrity", communication channels). We will also share our
-"learning by burnings" so that other projects can explore other
-creative problems and mistakes than maybe repeating the ones we 
-identified during the last 3 years of PyPy development. And hopefully
-we will be able to show that the OSS development style is compatible 
-with EU-funding.
+Some people have said that they have hardly seen a large
+project succeed with delivering to the original goals as much
+as the PyPy project did.  Others consider it a failure because
+it did not take over the world yet or is not usable for
+mainstream purposes.  Anyway, we'll talk about the mix of
+development processes, methods and infrastructure of the PyPy
+project.  We will summarize our experiences regarding the
+evolving development environment (version control, automated
+test-driven development, sprints, synchronization, "conceptual
+integrity", communication channels). We will also try to share
+our "learning by burnings" so that other projects can explore
+other creative problems and mistakes than maybe repeating the
+ones we explored in depth already during the last 4 years of
+PyPy development.