Code sprints: Difference between revisions

From Joomla! Documentation

Wilsonge (talk | contribs)
Add JUX code sprint
No edit summary
Line 35: Line 35:
* '''Joomla 4 UX and Architecture Sprint''', October 10-12, Athens, Greece.</translate>
* '''Joomla 4 UX and Architecture Sprint''', October 10-12, Athens, Greece.</translate>
<translate><!--T:9-->
<translate><!--T:9-->
* '''Joomla! Automated Testing Code Sprint''', October 28th - November 2nd, Karlsruhe, Germany.</translate>
* '''Joomla! Automated Testing Code Sprint''', October 28th - November 2nd, Karlsruhe, Germany. More info at: https://magazine.joomla.org/issues/issue-december-2015/item/2912-the-joomla-automated-testing-code-sprint-2015</translate>
<translate>
<translate>
<!--T:5-->
<!--T:5-->
[[Category:Events]]
[[Category:Events]]
</translate>
</translate>

Revision as of 07:16, 25 May 2016

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: