Code Sprint Guidelines
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.)
Codesprints are clearly within the scope of OSGeo's mission, and so the Foundation should in general support them. This page provides some guidelines for deciding whether a given sprint should be supported, and if so in what fashion.
For the purposes of discussion, there are Big sprints and Less Big sprints.
Big sprints are typically annual, multiproject, multiday events of more than 20 people. The two big sprints we know of are the annual Bolsena Sprint and the annual North American Sprint.
Less Big sprints include the one-day sprint associated with the GOSS4G conference, single-project sprints such as have been held for GRASS and uDig, and very regional (chapter-level) sprints.
Sprint Info Required
A proposal for supporting a sprint should include the following information about the event and the funding model for it:
- Audience: how many people are expected? i
- 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?
- 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)?
- 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?
OSGeo Sponsorship Criteria
Not sole source
Prefer multiday, multiproject
prefer “independent” events? (e.g. not foss4g)
Amount proportional to size
#projects x #attendees x #days