Fwd: [PyCON-Organizers] Intro to Sprints sessions

From: Edward Cherlin <echerlin_at_gmail_dot_com>
Date: Wed Feb 06 2008 - 16:10:59 CST

Will any of our Python coders be at PyCon next month? I would like to
organize an Open Voting code sprint, not only to get some work done,
but to introduce the rest of the Python community to what we are
doing.

http://www.python.org/community/pycon/

---------- Forwarded message ----------
From: Facundo Batista <facundobatista@gmail.com>
Date: Feb 6, 2008 9:20 AM
Subject: [PyCON-Organizers] Intro to Sprints sessions
To: brett@python.org, brian@dorseys.org, chrism@plope.com,
tseaver@palladion.com, david@dawninglight.net,
doug.napoleone@gmail.com, fwierzbicki@gmail.com, jacob@jacobian.org,
john@arbash-meinel.com, pacopablo@pacopablo.com,
lucio.torre@gmail.com, mark.ramm@gmail.com, CarterMichael@gmail.com,
mcfletch@vrplumber.com
Cc: "Pycon-Organizers@Python.Org" <pycon-organizers@python.org>

Hi all!

There will be two pre-sprint sessions that will be run on Sunday
afternoon, after the end of the conference talks.

- Intro to Sprinting (60 minutes, at 3:20 pm)

This will be a plenary session, and will begin with a talk explaining
what sprints are and how we do them at PyCon, followed by a panel
discussion where the sprint leaders will answer questions.

Brett Cannon will lead this session; I'm sure he will distribute us
some hints regarding these questions, so you sprint leaders can be
prepared before. If you have any problem to participate in this
session, please tell me ASAP.

- Sprint Tutorials (90 minutes to 3 hours, at 4:40 pm)

After a break, participating sprint leaders will gather the sprinters
of their projects, go to different rooms, and the project will be
explained. Everything from code walkthroughs to granting repository
access can be presented here. This way, you'll be able to start
working on the sprints effectively on Monday morning, without a long
setup delay.

You should really prepare this in advance. This is a great opportunity
to start the sprints already running, and not from a cold start.

As maybe people will participate in your sprints by IRC, you should
make public any material you prepare, and make it enough explicit so
remote developers can understand it.

Any question, feel free to ask me.

Thank you!! And happy coding, :)

--
.    Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
_______________________________________________
Pycon-organizers mailing list
Pycon-organizers@python.org
http://mail.python.org/mailman/listinfo/pycon-organizers
-- 
Edward Cherlin
End Poverty at a Profit by teaching children business
http://www.EarthTreasury.org/
"The best way to predict the future is to invent it."--Alan Kay
_______________________________________________
OVC-discuss mailing list
OVC-discuss@listman.sonic.net
http://lists.sonic.net/mailman/listinfo/ovc-discuss
By sending email to the OVC-discuss  list, you thereby agree to release the content of your posts to the Public Domain--with the exception of copyrighted material quoted according to fair use, including publicly archiving at  http://gnosis.python-hosting.com/voting-project/
==================================================================
= The content of this message, with the exception of any external 
= quotations under fair use, are released to the Public Domain    
==================================================================
Received on Fri Feb 29 23:17:04 2008

This archive was generated by hypermail 2.1.8 : Fri Feb 29 2008 - 23:17:08 CST