[pypy-svn] r13036 - pypy/extradoc/sprintinfo

hpk at codespeak.net hpk at codespeak.net
Fri Jun 3 14:22:43 CEST 2005

Author: hpk
Date: Fri Jun  3 14:22:42 2005
New Revision: 13036

progressing towards a full sprint announcement (we really
should get this out some time soon) 

- introduction section with an explicit summer-of-code 
  reference (please check if you like this) 

- some headers and shifting around 

- XXX marks the logistics/accomodation information that
  is missing 

Modified: pypy/extradoc/sprintinfo/EP2005-announcement.txt
--- pypy/extradoc/sprintinfo/EP2005-announcement.txt	(original)
+++ pypy/extradoc/sprintinfo/EP2005-announcement.txt	Fri Jun  3 14:22:42 2005
@@ -1,17 +1,29 @@
+Post-EuroPython 2005 PyPy Sprint 1st - 7th July 2005 
-Post-EuroPython 2005 PyPy Sprint Announcement 
-Time: 1st-7th July 2005 (both days including) 
-Location: Goetheborg, Sweden (more details to follow) 
-Draft topic announcement 
-The main, though not the only, focus of the sprint will be on the
-"translation" aspect of PyPy.  We will progress towards a completely
-translated PyPy.  How much will already have been done before EuroPython
-is unknown; as a guess, we will be left with:
+The next PyPy sprint is scheduled right after EuroPython 2005
+in Gothenborg, Sweden.  It's main focus is translation to 
+lower level backends but there are also other possible topics. 
+We'll give newcomer-friendly introductions.  To learn more
+about the new PyPy Python-in-Python implementation look here: 
+    http://codespeak.net/pypy 
+On a side note, there are a number of sub projects that may be
+interesting for participating in google's summer-of-code
+event.  Apart from refining and discussing tasks, the sprint 
+could possibly serve as a good meeting and kick-off point with  
+mentors from the PyPy group.  Further down you'll find some
+first areas, but there are certainly more and bigger ones :-) 
+Goals and topics of the sprint 
+The main, though not the only, focus of the sprint will be on
+the "translation" aspect of PyPy.   The goal here is to
+progress towards a completely translated PyPy.  How much will
+already have been done before EuroPython is unknown; as a
+guess, we will be left with:
 - completing the "rtyper", the piece of code that assigns low-level
   C-like types to high-level RPython objects (lists, dicts, instances,
@@ -38,3 +50,9 @@
 - weakrefs (but this requires discussion and planning on pypy-dev
   before the sprint! feel free to start such a discussion, though.)
+Accomodation, Location and meeting points

More information about the Pypy-commit mailing list