Differences between revisions 22 and 23
Revision 22 as of 2005-12-19 20:05:18
Size: 5085
Editor: 70
Comment:
Revision 23 as of 2006-01-04 19:46:33
Size: 4912
Editor: tmcb-u110-3N10E-CE1
Comment: Can't come anymore. Little interest on the scipy-dev list...
Deletions are marked like this. Additions are marked like this.
Line 93: Line 93:
== Array Interface in Python ==
  
  Goal: add the array interface to Python
  
  Coach: Travis Oliphant (only there Feb. 27)
  
  Details: /ArrayInterfaceSprint

For more information about PyCon 2006, see the main conference site at [http://us.pycon.org/].

The following sprints are planned for the four days after the conference.

To register a new sprint, just edit this page and add your sprint, listing yourself as the sprint coach. If you won't be around for all four days, please specify the days you'll be present.

If you have any questions about sprinting at PyCon, please send email to the Sprint Coordinator, [mailto:goodger@python.org David Goodger].

Logistics

  • Rooms: To be decided. Time: Starting 8 am Monday (intro session from 3:30 pm Sunday) Date: Monday February 27 through Thursday March 2 inclusive. Cost to attend: Free! Bring: Your laptop and a wireless card. IRC: #pycon-sprints on irc.freenode.net, or as listed below

Preparations

Because the sprints are after the formal conference, all the sprint attendees will likely be present at the start of the sprints. Sprint coaches should plan for an introductory session on Sunday afternoon or Monday morning, where you can help attendees get started. This might involve helping them to get SVN or CVS installed, find the development tree, talk about the software's architecture, or planning what the four-day sprint will try to accomplish.

If the introductory session is on Sunday, you should plan to begin around 3:30PM.

Sprints

Django

  • Goal: Same thing we do every night, Pinky Coach: Jacob Kaplan-Moss

    Details: /DjangoSprint

Zope

Stackless

  • Goal: to port Stackless to Python 2.4.2 Coach: Christian Tismer

    Details: /StacklessSprint

Docutils (reStructuredText)

Python Core

  • Goal: add functionality, fix bugs, and facilitate applications Coach: someone please adopt me!

    Details: /PythonCore

TurboGears

  • Goal: add functionality, resolve tricky bugs and facilitate applications Coach: Kevin Dangoor

    Details: /TurboGearsSprint

PyPy

  • Goal: work in any area of interest of PyPy Coach: Armin Rigo

    Details: /PyPySprint

Introduction

What is a sprint?

A sprint is a focused development session, in which developers pair in a room and focus on building a particular subsystem. A sprint is organized with a coach leading the session. The coach sets the agenda, tracks activities, and keeps the development moving. The developers often work in pairs using XP's pair programming approach.

The sprint approach works best when the first few hours are spent getting oriented -- presenting a tutorial for the development material, laying out the stories to tackle for the day, getting everyone a CVS or SVN checkout to work with.

[http://www.zopemag.com/Guides/miniGuide_ZopeSprinting.html ZopeMag's miniGuide to Zope Sprinting] is a good introductory article; just mentally remove every "Zope" from the article to make it generic.

Why sprint at PyCon?

The sprints are intended to benefit various projects, and to encourage more people to take part in development. They will also be a good place to see ExtremeProgramming or other AgileMethods in action, and to work closely with experienced Python developers.

PyCon will always have a core Python sprint. Other topics will come and go each year.

If you wish to participate in a sprint, please contact the sprint organizers in advance, or add your name to the list of participants for a given sprint.

What equipment/supplies will sprints get?

PyCon will supply the following:

  • Room. Multiple sprints will share the same room; different sprints will presumably occupy different tables.
  • Wireless networking.
  • Easels, a tablet of paper, and markers.
  • Writing paper and pens (for notes, sketches, etc.).
  • Ice water.

PyCon does not supply food for the sprint days. Participants will have to go to ["PyCon2006/NearbyRestaurants"], or have food delivered to the hotel.

Who makes this possible?

The [http://www.python.org/psf Python Software Foundation ] sponsors the sprints at ["PyCon2006"]. Please consider making a [http://www.python.org/psf/donations.html donation] to support this vital community activity!

IRC

If you cannot attend the sprints in person but would still like to follow the progress and/or participate, you can, via IRC (irc.freenode.net) or other means, as listed above. The #pycon-sprints channel can be used for general sprint-related traffic.


CategoryPyCon2006

PyCon2006/Sprints (last edited 2008-11-15 14:01:14 by localhost)

Unable to edit the page? See the FrontPage for instructions.