Difference between revisions of "FOSS4G2008 CodeSprint"
(Removed templated sprints from 2007 and only included changes added to 2008 page) |
(Added procedure section) |
||
| Line 1: | Line 1: | ||
| − | ''' | + | Back to [[FOSS4G2008]]... |
| + | |||
| + | == Date and Organizing Contacts == | ||
| + | |||
| + | '''Date:''' Friday 3rd October 2008 | ||
| − | ''' | + | '''Organising Contact:''' Tim Sutton |
| − | ''' | + | '''Contact Email:''' tim@linfiniti.com |
| − | + | == Procedure == | |
| − | + | Read the sections below which provide some background. If you would like to hold a code sprint, add your name (as coordinator) and project name below, then create a detailed project sprint section below. The project sprint section should include some or all of the following details: | |
| − | ''' | + | * '''Attending''' - a list of people who plan to attend |
| − | + | * '''Goals''' - a brief list of the things you hope to achieve and plan to work on during your sprint session | |
| + | * '''Preparation (optional)''' - a list of items that should be taken care of before the code sprint so that the appropriate groundwork is in place | ||
| + | * '''Out of scope (optional)''' - items that will not be in scope for the sprint session | ||
== Interested to organize a code sprint == | == Interested to organize a code sprint == | ||
Revision as of 12:09, 16 June 2008
Back to FOSS4G2008...
Date and Organizing Contacts
Date: Friday 3rd October 2008
Organising Contact: Tim Sutton
Contact Email: tim@linfiniti.com
Procedure
Read the sections below which provide some background. If you would like to hold a code sprint, add your name (as coordinator) and project name below, then create a detailed project sprint section below. The project sprint section should include some or all of the following details:
- Attending - a list of people who plan to attend
- Goals - a brief list of the things you hope to achieve and plan to work on during your sprint session
- Preparation (optional) - a list of items that should be taken care of before the code sprint so that the appropriate groundwork is in place
- Out of scope (optional) - items that will not be in scope for the sprint session
Interested to organize a code sprint
- Markus Neteler: GRASS GIS
- Andrea Antonello: JGrass / uDig
Code Sprint - what's that?
A code sprint is usually organized by a group that is using an open source project and wants to see something done. They fly the developers to a single location and feed them for a couple of days with the necessities of the hacking life (internet, caffeine, electricity). The communication that happens from face to face hacking usually lasts the project for a year or more. You see this a lot in projects like Drupal etc...
Motivation and Direction
A day, a code base, and your imagination?
On the Friday after the conference, a big room with internet connectivity, lots of tables and flip charts will be arranged. Projects can use the time and venue for organizational discussions, development roadmaps, and group resolution of thorny issues in their code bases.
Is this your First Sprint? Here is some background information to get you started:
- http://www.infrae.com/about/activities/sprintathon/tips
- http://www.onlamp.com/pub/a/python/2006/10/19/running-a-sprint.html
- Example Sprint (from same people who do GeoServer): http://www.openplans.org/projects/bbq-sprint
To participate, start a section below for your project.
GRASS
Attending
- Markus Neteler
- Wolf Bergenheim via IRC
- Martin Landa via IRC
- Moritz Lennert via IRC (tbc)
Goals
- Hack session: fix bugs, new features
- Maybe invite power users to get in touch?
- Remote users via IRC channel
Udig / JGrass
Cross project code sprint with the JGrass and uDig projects.
Attending
Goals
To be defined...