Code Sprint Guidelines
Redirect to:
Latest guidance can be found on https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidence.pdf
- This article has been approved by the OSGeo Board of Directors in their 2013-10-17 Board Meeting.
- Please add comments and suggestions in the associated Talk page.
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.)
By 2013, The OSGeo community has two annual "big" sprints (annual, multiproject, multiday events of more than 20 people): the Bolsena Sprint and the C Tribe Sprint. A number of project-oriented sprints also occur, such as the one-day sprint associated with FOSS4G conferences, single-project sprints such as have been held for GRASS GIS, QGIS and uDig, and very regional (chapter-level) sprints.
Codesprints are clearly within the scope of OSGeo's mission, and the OSGeo Foundation supports them. This page provides some guidelines for deciding whether a given sprint should be supported, and if so in what fashion.
Sprint Info Required
A request for supporting a sprint by OSGeo should include the following information about the event and the funding model for it:
Basic Information
- Audience: how many people are expected?
- Region: is the sprint localized to a specific region?
- Projects: is the sprint to work on just one specific project, or is it for multiple projects?
- Length: how many days will the sprint cover?
- Venue: where will the sprint be held? will food be provided? will overnight lodging be provided?
Expected budget
- Where is the prospective budget published? Provide a link to a publicly accessible resource (e.g. wiki). The prospective budget shall list the levels/amounts of forecasted sponsorship, and show that OSGeo is providing matching funds (see Sponsorship Criteria below).
The budget shall contain the following information:
- what is the expected registration fee, if any, for each attendee?
- what is the expected amount of third-party sponsorships?
- what in-kind donations are expected (such as donated use of a conference room)?
- what is the desired amount of OSGeo sponsorship?
- what is the expected cost per attendee, for travel, lodging, and food?
- what is the expected cost for the venue (such as conference room, wifi support, snacks, etc)?
Profit / Loss / Risk
- What is the expected profit of the event, if any? where will any surplus money go?
- Under what circumstances might the event incur a loss? how will this risk be mitigated?
Submission of a funding request
Proposed workflow:
- Sprint organisers fill out the questionnaire above and submit it to Board list.
- Board adds a "Sprint support" agenda item for upcoming Board meeting, and invites sprint organiser(s) to join the meeting and provide clarification where needed.
- Board votes on the funding request.
- Upon approval, and within one month from the end of the sprint, sprint organisers provide a publicly accessible summary budget of the actual expenses. A more detailed budget shall be made available to OSGeo Treasurer. Should the final budget not be available to OSGeo, future fund requests will be with held until final budget publication.
OSGeo Sponsorship Criteria
When deciding to support a sprint, OSGeo should follow these guidelines:
- OSGeo has a limited budget, and gives priority to proposals which provide value to a wide OSGeo community. Greater value might be achieved by incorporating sprints from multiple OSGeo projects into one, or by extending the code sprint to incorporate virtual participants from around the world.
- OSGeo should not be the sole source of funding for the event. OSGeo prefers sprints to be partially funded by third-party sponsors, and may choose to provide funding "matching" the amount of sponsorship money raised for the event. OSGeo's contribution should go towards reducing the net cost for participants instead of for instance supporting a more expensive venue or setup.
- OSGeo understands that some events may require up-front costs, e.g. for deposits, and some events may present a financial risk, e.g. if the number of attendees is not met. Instead of direct funding, OSGeo may provide "back-stop" funding and assume the liability risk.