Difference between revisions of "OSGeo Code Sprints Initiative"
| (2 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
* [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidence.pdf OSGeo Financial Guidance] provides application process | * [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidence.pdf OSGeo Financial Guidance] provides application process | ||
* [https://wiki.osgeo.org/w/index.php?title=Code_Sprint_Guidelines&redirect=no Code Sprint Guidelines] (Archived) | * [https://wiki.osgeo.org/w/index.php?title=Code_Sprint_Guidelines&redirect=no Code Sprint Guidelines] (Archived) | ||
| + | |||
| + | [[Category:Code_Sprints]] | ||
| + | [[Category:Initiative]] | ||
Latest revision as of 08:20, 6 April 2023
A codesprint is an in-person gathering of developers for doing some serious coding, writing documentation, and having face-to-face project collaboration. (It is not aimed at training, presentations, workshops, etc.)
The OSGeo Board manages a code-sprint initiative to help provide funding for these valuable community building events. For details on applying see OSGeo Financial Guidance document.
Update: During the Pandemic the OSGeo community has experimented with remote code sprints; which can be effective if participants are truly isolated with dedicated time for participation. The environmental impact and funding requirements for a remote event are low (take-out for participant meal of video chat, t-shirts for the event, ...).
References:
- OSGeo Financial Guidance provides application process
- Code Sprint Guidelines (Archived)