FOSS4G 2014 Code Sprint

Code Sprint - what's that?

A code sprint is about getting a group together to work on Open Source software, sitting around a table and sharing ideas. It's not just about writing code, as you know a project has many needs including documentation, testing, and providing feedback. What a better way to give feedback and give back to the project that you love than to spend a day with the project's developers. There are roles needed to be filled, no matter what your expertise.

With such a short timeframe (one day) you should probably use this page to set a specific goal for your project. But don't worry, if all you get done is actually sitting at the same table with the project's developers and talking about the next release, that is also great :)

Who

All participants are welcome and you don't need to register or attend FOSS4G to attend the Code Sprint (registering here on the wiki is appreciated for planning purposes like coffee and food). Some projects will prefer attendees who have previously engaged with the project and already have a working development environment on their computer (i.e. not all project will welcome helping you set up your development environment).

Where & When

The day after the main conference (Saturday, September 13th 2014) has been set aside for the Code Sprint.

The sprint will be in the Eliot Center (OSM) along side WhereCampPDX.

How to get there

TBD

Questions/Comments/Ideas

• ask on the foss4g2014 mailing list (subscribe)

Additional Interested People

The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup.

• Your name: project(s)
• Jordan Winthrop: Interested in Art, Mapping & Marketing
• Kyle Shannon: GDAL(?)
• James Hiebert: ?
• Alex Mandel: SAC
• Rob Emanuele: GeoTrellis, GDAL
• Daniel Miranda: QGis, PostGIS

Workgroups

To participate, copy a project skeleton and start a section below for your project.

Project-name

Attending:

• user
• user

Goals:

• your goals

GeoMoose

Attending:

• Eli Adam
• Dan 'Ducky' Little
• Bob Basques
• Jim Klassen

Goals:

• 2.7 wrap up.
• Marketing plan - do mores?

GeoNode

Attending:

• Ian Schneider
• Ariel Nunez
• Tyler Garner
• Angelos Tzotsos
• Simone Dalmasso
• Paolo Corti
• Tom Kralidis

Goals:

• TBD

GeoServer

Attending:

• Jody Garnett
• Andrea Aime
• Mauro Bartolomeoli
• Frank Gasdorf

Goals:

• Option 1: Update Wicket to a recent version, goal wider browser compatibility. Benefit from a balance of developers and testers.
• Option 2: Update CITE tests. Benefit from collaboration with the CITE TEAM Engine project.
• Option 3: Add a "locale" switcher to UI (see Sub-Task https://jira.codehaus.org/browse/GEOS-5568 "Language Selector")

Note

• GeoServer will continue sprinting on Sunday at a different venue, (details)

GRASS GIS

Attending:

• Luca Delucchi
• Markus Neteler
• Anna Petrasova
• Vaclav Petras
• ... you! (normal and power users welcome, too)

Goals:

• for a list, see http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Portland_2014#Ideas (please update there)

MapServer

Attending:

• Michael Smith
• Jeff McKenna
• Steve Lime
• Daniel Morissette
• Thomas Bonfort

Goals:

• 7.0 Release Fixes

PostGIS

Attending:

• Regina Obe
• Leo Hsu
• Brian M Hamlin

Goals:

• Plan out PostGIS 2.2

pycsw

Attending:

• Tom Kralidis
• Angelos Tzotsos
• Jeff McKenna (buzzer sound)
• Paolo Corti (I have to split with GeoNode)

Goals:

• OSGeo Incubation
• CSW 3.0
• Roadmap
• packaging (UbuntuGIS, DebianGIS)
• i18n of codebase / messages, docs

Open Source Planning Tools

Attending:

• Nate Roth
• Critter Thompson

Goals:

• Plan EPA Smart Location Database Accessibility API
• Solicit suggestions for tools and technologies
• Get started

GeoNetwork opensource

Attending:

• Jeroen Ticheler
• Jan Skornsek
• Paul van Genuchten

Goals:

• interact with other sprints
• prepare for GeoNetwork 3
• TBD

uDig

Attending:

• Frank Gasdorf
• Jody Garnett

Goals:

• upgrade to GeoTools 11.2
• merge gt-11 branch back to master
• (reactivate tests cases)
• improve "how to build" docs
• cleanup user/developer/data docs