A Sprint is a focused development session lasting anywhere from a day to a week, in which developers pair off together and focus on building a particular subsystem of Plone.

Sprinting Explained

A sprint is a three to five day focused development session, in which developers pair up and focus on building a particular subsystem.

Sprints helps accomplish the goal of getting Plone developed. Additionally, it establishes leadership in the community by sharing development approaches, intense sessions of focused communication on a topic, and explaining in person the Plone development model.

A sprint is often organized with a coach leading the session. The coach sets the agenda, uses the whiteboard to track activities, and keeps the development moving. The developers usually work in pairs or small teams similar to the pair programming approach. Some sprints are focused on a specific topic, like internationalization or educational systems.

The sprint approach works best when the first few hours are spent getting oriented. This means having a plan up front, agreeing on who does what, getting everyone's computers working with the SVN server, etc.

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 or wi-fi.

At the end of the sprint, code is produced and Plone moves forward. This by definition means that sprinters need to sign the Plone Contributor Agreement to work on Plone. This is to make sure the Plone Foundation and Plone itself has sufficient legal protection, something we take very seriously.

How can you help?

At this point I'm sure you're asking, "How can I help if I'm not a Plone or Python coder?". There are two main options:

  1. Particpate in the ways you can. People are needed to test, write documentation or simply to report to the rest of the world what is happening at the sprint.
  2. Contribute financially. Sponsoring sprints help cover costs for the sprinting or for participants' costs getitng there. Sponsoring Plone sprints is one of the best ways to contribute to Plone's development if you dont have the skills/time do the work yourself.

If you would like to organise a sprint, please contact Plone Core Developers.

This explanation taken from the original Zope 3 explanation and modified somewhat to fit Plone's version. Thanks, guys :)

Upcoming Sprints

Zidanca sprint 2014 from Aug 09, 2014 09:00 AM to Aug 12, 2014 11:00 PM Krsko, Slovenia,
A strategic sprint focusing on Plone 5, from 9th to 12th August 2014 in Slovenia.
Zurich Sprint 2014 from Aug 11, 2014 10:00 AM to Aug 15, 2014 05:00 PM
This sprint is open to any plone- and python-related topic and everyone interested getting to know people in that field.
Berlin Plone Social Sprint 2014 from Sep 08, 2014 09:30 AM to Sep 12, 2014 08:00 PM Jacob-und-Wilhelm-Grimm-Zentrum at the Humboldt-Universität - Berlin,
This sprint will be mainly focused on two specific projects: plonesocial and ploneintranet and all its components. Especially welcome are front-end gurus. Getting a polished UX is high priority.
Plone Conference 2014, Bristol, UK from Oct 27, 2014 09:00 AM to Nov 02, 2014 05:00 PM Thistle Grand Hotel, Bristol, UK,
Plone Conference 2014: Bristol, UK - October 29–31st. Training, Conference, Sprints all over one week.
Alpine City Sprint 2015, Innsbruck from Jan 21, 2015 09:00 AM to Jan 25, 2015 06:00 PM Innsbruck, Austria,
Developer Sprint focused on Plone and Snow