[pypy-sprint] vilnius sprint planning progress

holger krekel hpk at trillke.net
Fri Oct 8 12:18:44 MEST 2004


Hi sprinters and interested parties, 

I am talking to Marius Gedminas currently to fix up some
remaining issues (exact dates, rooms, accomodation) about
our envisionsed Vilnius Sprint.  I'll keep you updated. 

Meanwhile i've setup our usual bunch of Wiki-Pages 
to help us organize the meeting. 

    http://codespeak.net/moin/pypy/moin.cgi/VilniusSprint

please check if especially the 

    http://codespeak.net/moin/pypy/moin.cgi/VilniusSprintAttendants 

contains correct information so far. 

Until Marius Gedminas from the Programmers of Vilnius (POV) 
gives final approvement and fills in some details we 
can't announce the sprint.  Let's cross fingers that 
he doesn't detect any obstacles now. They are a pretty
busy company these days. 

I have offered up to 200 Euros for the sprint room 
which we would have to raise among ourselves. I hope
that's ok. 

However, we still need to determine the technical goals. 
Certainly we want the C-backend for the translator to 
translate PyPy.  Besides, we probably want to do the 
test-migration of PyPy's tests although it might be 
better to try to do that before the sprint because
at sprints the code base moves a lot faster and
makes large-scale refactorings more difficult. 

Armin, Samuele, it would be great if especially the two of you
(or at least one of you) think hard about how to split up work
for the translate-pypy goal so that multiple teams can work on
it.  If you have ideas please post them to pypy-dev.  

Currently, myself, i am pretty busy with EU funding, sprint
organization, and my daily work issues.  So i would appreciate
help planning the event especially on the technical coding 
side very much. 

cheers, 

    holger

P.S.: it seems likely we could do a sprint at Rotterdam sometime 
      next year.  i have gotten preliminary feedback from Kit Blake 
      and Martijn Faassen.  Remember, we'll probably need 14 (fourteen)     
      sprint locations in the next two years. 


More information about the pypy-sprint mailing list