SprintSchedule

Zope 3 Sprint Schedule

Status: IsOngoing

What is a sprint?

A sprint is a multi-day session of intense Zope 3 development organized around extreme programming (XP) ideas such as pair programming. For a more detailed description see the miniGuide to Zope Sprinting .

Sponsors needed! Help accelerate the continued development of Zope 3 by sponsoring a sprint. You need to find an experienced leader for the sprint and provide a facility for around 8 developers plus the leader. If you are interested, contact JimFulton.

Jim is generally available to help out with sprints, however, if you want him there in person, you'll need to help cover his travel expenses.

Possible Sprint Tasks

Upcoming Sprints

• January 18 - January 25, 2008, SnowSprint2008?

Previous Sprints

• November 9 - November 11, 2007, NeckarSprint2007
• October 1 - October 5, 2007, Neanderthal-Sprint
• September 24 - September 28, 2007, FoliageSprint
• April 17 - April 21, 2006, Z3ECMParisSprint2006
• April 8 - April 12, 2006, SwissEasterSprint
• March 25 - March 29, 2006, Golden Roof AGX Sprint 2006
• February 27 - March 2, 2006, PyCon2006Sprint
• October 24-26, 2005, CMF20GoldeggRedzoneSprint
• October 6-9, 2005, NeckarSprint
• Sept 23-25, AGXSprint2005
• Sept 23-25, CMF20GoldeggSprint2005
• September 1-2, 2005, RivahSprint
• March 14-20, 2005, ParisSprint2005
• October 7-14, 2004, IsarSprint
• September 16-19, 2004, CastleSprint2004
• June 10-12, 2004, Euro Python 2004 Zope Sprint
• May 3-7, 2004, Zope3CertificationStep1Sprint
• March 20-23, 2004, PyCon? 2004 Sprint, Washington, DC.
• February 4-9, 2004, Australian Summer Sprint - Melbourne
• January 12-13, 2004, SteveVisitingFredericksburgSprint
• December 4-19, 2003, BangaloreSprint
• December 4-7, 2003, RheinlandProductsSprint
• July 9-13, 2003, Australian Zope 3 Sprint.
• June 22-24, 2003, EuroPythonSprint2003
• June 21-23, 2003, Fredericksburg2003Sprint2
• May 31 - June 2, 2003, Fredericksburg2003Sprint1
• April 12-15, 2003, BristolUKSprint
• April 8-11, 2003, LouvainLaNeuveSprint. First big steps of XML integration. Some work on i18n and UI infrastructure.
• Mar 24-25, 2003, PyConSprint. Improved the i18n situation for Zope 3. Jim wrote up a nice summary of the progress.
• Mar 24-27, 2003, DZUGSprint. Developed a new product called NewsSite? which demonstrates some of the nice CMS features of Zope 3, suhc as Membership, Workflow and so on.
• Feb 3-7, 2003, Paris UI Sprint.
• Dec 10-12, 2002, Alpha1Sprint. Various bits and pieces needed for the release of !Alpha1: refactorings in service configuration, TTW adapters, views and pages, TTW Schema.
• Dec 2-6, 2002, InfraeSprintathon. The focus on the sprint was content management, documentation and user interface.
• Jun 23-25, 2002, EuroPython2002Sprint.
• April 8-10, 2002. ZopeBBQ2002Sprint, This Eurosprint is in conjunction with the Zope BBQ Europe April 11-12 in Berlin.
• Mar 22-24, 2002. This New York City Sprint will be hosted by Codeit and Netaid.org. Participants include Codeit (Scott Robertson, Forest Zachman) NetAid (Josh Kutz, Nikheel Dhekne), Gary Poster, Bruce Eckel, Chris Humpries, and R. David Murray. Cilck here for NetAid's address and a list of hotels around the area. Space is limited on Friday, please RSVP by sending an e-mail to Scott Robertson.
• March 4-6, 2002. This is the March2002WorkflowSprint, held in Saarbruecken, Germany.
• Feb 21-23, 2002. CatalogSprint. England, Chris Withers, Steve Alexander, Seb Bacon, and Matt Hamilton for cataloging.
• Feb 8-9, 2002. AfterPython10Sprint. This sprint is scheduled in conjunction with IPC10. The sprint is on Friday and Saturday. ZC is also planning an open house on Friday, Feb 8 at noon for conference attendees. Amtrak and the VRE commuter train come down early in the morning, and also a shuttle service. Coaches include Bruce Eckel (Friday only), Casey Duncan. Potential participants include Itamar Shtull-Trauring (Friday only), Anthony Baxter, tjleach@hushmail.com.
• Jan 31-Feb 2, 2002. BeforePython10Sprint. The potential topics for this sprint includes package management. Participants include Casey Duncan, Steve Alexander, and Kapil Thangavelu.
• Jan 16-19, 2002, Feb2002InternationalizationSprint. This sprint was focused on internationalization.

Sprinting Explained

For the development of Zope 3, Tres Seaver at ZC launched a concept called sprints, based on ideas from the extreme programming (XP) community. A sprint is a two or three day focused development session, in which developers pair in a room and focus on building a particular subsystem.

This model was initially used for Zope Corporation only sprints. We've since opened the sprinting to include members of the Zope community. This helps accomplish the goal of furthering Zope 3 development. Additionally, though, this establishes leadership in the community by sharing development approaches, intense sessions of focused communication on a topic, and explaining in person the Zope 3 development model.

A sprint is organized with a coach, such as Jim Fulton, leading the session. The coach sets the agenda, uses the whiteboard to track activities, and keeps the development moving. The developers work in pairs using XP's pair programming approach. One of the pairs needs to be a veteran sprinter, and both need Zope and Python experience. Some sprints are focused on a specific topic, like internationalization or cataloging.

The sprint approach works best when the first few hours are spent getting oriented. This may mean presenting a Zope 3 tutorial, getting everyone's computers working with the SVN server, etc. The need to have a veteran in each pair can be a limit on the number of pairs, which shouldn't go above four (for a total of eight sprinters). The coach can be a veteran in a pair.

Needless to say, a sprint needs a host to provide the space and connectivity. Whiteboards are usually needed. All sprinters should bring their own laptops with ethernet connections.

At the end of the sprint, code is produced and Zope 3 moves forward. This by definition means that sprinters need to sign the Zope Contributors Agreement . It is important to understand the terms of this agreement!

At this point I'm sure you're asking, "How can I help if I'm not a Zope 3 coder?" Simple: help us accelerate the schedule of sprinting by paying Jim's travel expenses and providing a sprinting facility. We travel for sprints! In exchange you can get a day with Jim or the ZC crew for consulting or a customer visit.