Code sprints/en: Difference between revisions
From Joomla! Documentation
Importing a new version from external source |
Updating to match new version of source page |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<noinclude><languages /></noinclude> | <noinclude><languages /></noinclude> | ||
{{incomplete}} | |||
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 [[S:MyLanguage/Joomla:Sprint_Policy|policy]] | 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 [[S:MyLanguage/Joomla:Sprint_Policy|policy]] | ||
| 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 | ||
| Line 11: | Line 12: | ||
Code Sprints in 2014: | Code Sprints in 2014: | ||
* '''Architecture Sprint''', Feb 8-9, San Jose, California, USA. | * '''Architecture Sprint''', Feb 8-9, San Jose, California, USA. | ||
* '''Bug Clean Up Sprint''', July 26-27, More info: http://magazine.joomla.org/issues/issue-aug-2014/item/2228-joomla-bug-sprint-in-manchester | * '''Bug Clean Up Sprint''', July 26-27, More info: http://magazine.joomla.org/issues/issue-aug-2014/item/2228-joomla-bug-sprint-in-manchester | ||
* '''Code Style Code Sprint''', Oct 11-12, Madrid, Spain. More info at: http://magazine.joomla.org/issues/issue-nov-2014/item/2353-two-joomla-code-sprints | * '''Code Style Code Sprint''', Oct 11-12, Madrid, Spain. More info at: http://magazine.joomla.org/issues/issue-nov-2014/item/2353-two-joomla-code-sprints | ||
| Line 21: | Line 21: | ||
* '''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 | * '''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 | ||
[[Category:Events]] | [[Category:Events]] | ||
[[Category:Production Department]] | |||
Latest revision as of 04:45, 26 October 2018
Content is Incomplete
This article or section is incomplete, which means it may be lacking information. You are welcome to assist in its completion by editing it as well. If this article or section has not been edited in several days, please consider helping complete the content.
This article was last edited by FuzzyBot (talk| contribs) 7 years ago. (Purge)
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:
- 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
- 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 Sprints in 2014:
- Architecture Sprint, Feb 8-9, San Jose, California, USA.
- Bug Clean Up Sprint, July 26-27, More info: http://magazine.joomla.org/issues/issue-aug-2014/item/2228-joomla-bug-sprint-in-manchester
- Code Style Code Sprint, Oct 11-12, Madrid, Spain. More info at: http://magazine.joomla.org/issues/issue-nov-2014/item/2353-two-joomla-code-sprints
- Code Testing Code Sprint, Oct 14, Montabaur, Germany. More info at: http://thephp.cc/viewpoints/blog/2014/10/joomla-phpunit-code-sprint
Code Sprints in 2015:
- Joomla 4 Architecture Sprint, July 10-12, Odense, Denmark. More info at: http://volunteers.joomla.org/reports/115-joomla-4-architecture-sprint-odense-dk
- Joomla 4 UX and Architecture Sprint, October 10-12, Athens, Greece.
- 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