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

Barcelona Strategic Sprint 2016 from May 14, 2016 09:00 AM to May 20, 2016 06:00 PM Barcelona,
The sprint will focus on working in the Plone REST API (plone.restapi) implementation.
Berlin Strategic sprint 2016 from May 16, 2016 10:00 AM to May 20, 2016 06:00 PM Berlin,
This sprint will be a follow up of Alpine City Strategic sprint 2016 and continue the work on topics like Zope, ZCatalog improvements, Python 3 and more. For more information have a look at the coactivate-page and register there, if you want to participate.
Mephisto Sprint Leipzig 2016 from Sep 05, 2016 09:00 AM to Sep 09, 2016 05:00 PM Leipzig, Germany,
September 5 - 9, which will focus on improving the TTW flexibility & hackability of Plone
Plone Conference 2016: Boston, Massachusetts, USA from Oct 17, 2016 09:00 AM to Oct 23, 2016 05:00 PM Boston, Massachusetts, USA,
October 17-23, 2016: training, keynotes, presentations, lighting talks, and sprints