[pypy-svn] r23640 - pypy/extradoc/talk/pycon2006

hpk at codespeak.net hpk at codespeak.net
Fri Feb 24 19:22:19 CET 2006


Author: hpk
Date: Fri Feb 24 19:22:15 2006
New Revision: 23640

Modified:
   pypy/extradoc/talk/pycon2006/method_talk.txt
Log:
small refinements and a suggestion to scrap
one slide - maybe also merge the "agile approaches
aim at and the mentioning of Zope/scrum" into one slide? 
this would bring us down to 16 slides - so up to 2 minutes
per slide max. 



Modified: pypy/extradoc/talk/pycon2006/method_talk.txt
==============================================================================
--- pypy/extradoc/talk/pycon2006/method_talk.txt	(original)
+++ pypy/extradoc/talk/pycon2006/method_talk.txt	Fri Feb 24 19:22:15 2006
@@ -41,7 +41,7 @@
 ==================================================
 
 - Identify problems/evolution by tests first 
-- Our own testing and development tools 
+- Our own testing and development tools (py.test)
 - Rule: first get the semantics and concepts right! 
   optimize later!
 - Today around 3000 tests (plus CPython regression tests)
@@ -67,9 +67,9 @@
 Balance of interests 
 ==================================================
 
-- Developers want to (continue to) drive the project
+- Developers want to/continue to drive the project
 - Companies have to co-finance 50% of all costs
-  (travel/salary), commercial interests
+  (travel/salary), match commercial interests
 - EU wants challenging research goals and tracking of goals 
 
 - **at all levels it is about finding 
@@ -146,6 +146,7 @@
    :width: 600
    :height: 450
 
+.. SCRAP THE NEXT SLIDE? 
 The different cultures of the PyPy project
 ============================================================
 
@@ -192,7 +193,7 @@
 
 - A shared and challenging vision
 - Respecting and "exploiting" strengths of the different cultures involved
-- Designing minimalistic project structures channeling work, not hindering work 
+- Designing minimalistic project structures channeling, not hindering work 
 - Room for group learning and creating change - not just reacting to change
 
 Outlook on whole project level 



More information about the Pypy-commit mailing list