Code sprints/en: Difference between revisions

From Joomla! Documentation

FuzzyBot (talk | contribs)
Importing a new version from external source
FuzzyBot (talk | contribs)
Importing a new version from external source
Line 6: Line 6:


Code Sprints in 2013:
Code Sprints in 2013:
* '''JUX Sprint''', July 8-9, More info: http://developer.joomla.org/cms/user-experience/610-jux-code-sprint-report.html
* '''Rapid Application Development Code Sprint''', July 2013, Pistoia, Italy
* '''Rapid Application Development Code Sprint''', July 2013, Pistoia, Italy
* '''Code stability and bug triage Code Sprint''', Aug 2013, Nashville, Tennessee, USA. More info:  http://community.joomla.org/blogs/leadership/1757-call-for-participants-for-code-sprint.html
* '''Code stability and bug triage Code Sprint''', Aug 2013, Nashville, Tennessee, USA. More info:  http://community.joomla.org/blogs/leadership/1757-call-for-participants-for-code-sprint.html

Revision as of 10:05, 24 April 2017

A code sprint is a dedicated session in which a group of volunteers come together at a geographic location to work on code for the Joomla project. Examples of code sprint sessions could include UI/UX improvements, working on new features, or long term planning and architecture work. Typically, six to ten experienced individuals will be brought together for two days for these events. If you wish to form your own sprint then read the policy

The code sprints are organised by the Joomla community together with the Production Leadership Team. These events are supported by the OpenSourceMatters and other sponsors.

Code Sprints in 2013:

Code Sprints in 2014:

Code Sprints in 2015: