[pypy-svn] r21680 - in pypy/extradoc: sprintinfo/paris talk/22c3 talk/pypy_euworkshop_2005-12-08

[hpk at codespeak.net]

Author: hpk
Date: Tue Jan  3 22:35:21 2006
New Revision: 21680

Modified:
   pypy/extradoc/sprintinfo/paris/paris-report.txt
   pypy/extradoc/talk/22c3/slides-agility.txt
   pypy/extradoc/talk/pypy_euworkshop_2005-12-08/holger_part2_OSSdev.txt
   pypy/extradoc/talk/pypy_euworkshop_2005-12-08/pypy_alastair_part1_intro.txt
Log:
various ReST fixes in extradoc 



Modified: pypy/extradoc/sprintinfo/paris/paris-report.txt
==============================================================================
--- pypy/extradoc/sprintinfo/paris/paris-report.txt	(original)
+++ pypy/extradoc/sprintinfo/paris/paris-report.txt	Tue Jan  3 22:35:21 2006
@@ -27,6 +27,7 @@
 Nicholas Chauvat
 
 -----------------------------------------------------------------------------------------------------------------------------------------
+
 The largest PyPy sprint yet (in terms of attendants) where done in the offices of Logilab in Paris 
 2005-10-16-2005-10-16.
 
@@ -40,6 +41,7 @@
   devise a low-level model variation for this case
 
 Annotator related tasks:
+
 - support the notion of separate/external functions (and classes/PBCs)
   in preparation for separate compilations
 
@@ -85,12 +87,14 @@
 - (DONE) genc: producing multiple .h/.c files tracking Python code origin
 
 Larger whole projects:
+
 - Javascript frontend
 - support for developing C extensions for CPython with RPython code
 - writing a sort of flow object space for the llinterpreter
   to experiment with JIT work
 
 ----------------------------------------------------------------------------------------------------------------------------------------
+
 Activities during the sprint  - day-to-day:
 
 Monday-Wednesday:

Modified: pypy/extradoc/talk/22c3/slides-agility.txt
==============================================================================
--- pypy/extradoc/talk/22c3/slides-agility.txt	(original)
+++ pypy/extradoc/talk/22c3/slides-agility.txt	Tue Jan  3 22:35:21 2006
@@ -336,3 +336,4 @@
 
 .. |bullet| unicode:: U+02022
 .. footer:: Bea During, Holger Krekel |bullet| 22C3 |bullet| 29th December 2005 
+

Modified: pypy/extradoc/talk/pypy_euworkshop_2005-12-08/holger_part2_OSSdev.txt
==============================================================================
--- pypy/extradoc/talk/pypy_euworkshop_2005-12-08/holger_part2_OSSdev.txt	(original)
+++ pypy/extradoc/talk/pypy_euworkshop_2005-12-08/holger_part2_OSSdev.txt	Tue Jan  3 22:35:21 2006
@@ -8,6 +8,7 @@
 
 
 1. personal background 
+
    - worked in gaming companies, banks and car companies for
      several years
    - studied computer science 
@@ -24,10 +25,10 @@
 
 3. technical production factors 
 
-	- automated test driven development
-    - specific expertise/special interest 
-	- version control (Subversion)
-	- releases
+- automated test driven development
+- specific expertise/special interest 
+- version control (Subversion)
+- releases
 
 4. Typical aspects of the Python community?
 
@@ -38,50 +39,51 @@
 
 5. PyPy: the vision
 
-	- founders came from the Python community
-	- "sprints" were the inital factor
-	- what is PyPy/Python - one of the five most used programming
-	  languages today 
-    - grass root approach
+- founders came from the Python community
+- "sprints" were the inital factor
+- what is PyPy/Python - one of the five most used programming
+  languages today 
+- grass root approach
 	
 
 6. OSS and EU funding: PyPy as a case study
 
-	- driven by partially EU funded and non-EU funded parties 
-	- focus on avoiding friction and turning PyPy into a long 
-      term project
-    - IBM or Sun have done similarly challenging projects
-      in more time and with more funding 
-    - yet not found completely satisfying "funding" 
-      interactions with communities. 
+- driven by partially EU funded and non-EU funded parties 
+- focus on avoiding friction and turning PyPy into a long 
+  term project
+- IBM or Sun have done similarly challenging projects
+  in more time and with more funding 
+- yet not found completely satisfying "funding" 
+  interactions with communities. 
 
 7. PyPy technical status 
-    - three public releases in 2005, well received by the
-      community 
-    - core deliverables fullfilled
-    - contributors add different directions 
+
+- three public releases in 2005, well received by the
+  community 
+- core deliverables fullfilled
+- contributors add different directions 
 
 8. PyPy: It's all about communication ... 
-	- pypy-sync meetings, 30 minutes IRC 
-	- day-to-day IRC discussions
-	- "this week in PyPy" 
-    - mailing lists: pypy-svn/eu-tracking tracks code and document changes 
-    - around 20000 visitors per month on website
-    - lots of blogs and pypy-dev (developer/researcher list) 
-    - 300-500 people across the world following the project 
+- pypy-sync meetings, 30 minutes IRC 
+- day-to-day IRC discussions
+- "this week in PyPy" 
+- mailing lists: pypy-svn/eu-tracking tracks code and document changes 
+- around 20000 visitors per month on website
+- lots of blogs and pypy-dev (developer/researcher list) 
+- 300-500 people across the world following the project 
 
 9. all good and well but the main thing are: sprints 
-    - one-week intense work-meetings with one break day
-    - EU and non-EU researchers/developers get together 
-    - daily planning sessions 
-    - pair programming 
-    - evolving and adapting to more attendants 
-    - organisational/management tasks happen also on sprints 
+- one-week intense work-meetings with one break day
+- EU and non-EU researchers/developers get together 
+- daily planning sessions 
+- pair programming 
+- evolving and adapting to more attendants 
+- organisational/management tasks happen also on sprints 
 
 10. next
-    - tackling research and technical goals (challenging!) 
-    - mid-term EU review planned for 20th january  
-    - looking into adjusting some work planning 
-    - increased dissemination, attending conferences (movie features?)
-    - start talking to and interact with commercial stakeholders 
+- tackling research and technical goals (challenging!) 
+- mid-term EU review planned for 20th january  
+- looking into adjusting some work planning 
+- increased dissemination, attending conferences (movie features?)
+- start talking to and interact with commercial stakeholders 
 

Modified: pypy/extradoc/talk/pypy_euworkshop_2005-12-08/pypy_alastair_part1_intro.txt
==============================================================================
--- pypy/extradoc/talk/pypy_euworkshop_2005-12-08/pypy_alastair_part1_intro.txt	(original)
+++ pypy/extradoc/talk/pypy_euworkshop_2005-12-08/pypy_alastair_part1_intro.txt	Tue Jan  3 22:35:21 2006
@@ -208,4 +208,3 @@
   - Tensions between large commercial developers and outsiders.
 
 
----------------------------------------------------------------------------
\ No newline at end of file