FOSS4G2008 CodeSprint

Back to FOSS4G2008...

Date and Organizing Contacts
Date: Sat 4 October 2008 (moved from Fri 3 to avoid overlapping with workshops).

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

If you are planning to attend the code sprint, please add your name to the relevant project sprint section below.

All sprint attendees it will be a good idea to subscribe to this page by ticking the 'watch this page' box at the bottom of the page so that you can be updated if there are any changes in arrangements.

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.

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

 * Andrea Antonello
 * Silvia Franceschi

Goals
To be defined...

Attending

 * Tim Sutton

Goals

 * Hack session: fix bugs, new features
 * Maybe invite power users to get in touch?
 * Remote users via IRC channel