FOSS4G2007 CodeSprint

From OSGeo
Revision as of 02:00, 1 June 2007 by Ajolma (talk | contribs) (added SWIG bindings sprint)
Jump to navigation Jump to search

Back to FOSS4G2007...

Organizing Contacts

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:

To participate, start a section below for your project.

GeoTools

Attending

Goals

  • To flesh out issue X until it works right.

GRASS

Attending

Goals

  • Hack session

GDAL / Mapserver

Attending

Goals

GeoNetwork / Metadata Madness

Goals

Building crawler/harvester/aggregator applications on top of the GeoNetwork metadata catalog network and similar interfaces. Plugging client stuff like gvSIG and uDig into it.

Attending

Jo Walsh

OpenLayers

Attending

Goals

Hack, hack, hack. I think this will be OpenLayers 2.6 or 2.7?

QGIS

Attending

Goals

Here are some goals/wishes/ideas for the code sprint:

1. I would love to get some traction on expanding the "Tim Tutorials" into a more generic and robust framework for stand alone apps. Focusing on the Python bindings would be my preference. (Aaron Racicot)

2. Build an all-in-one data browser:

  • Display a tree of all QGIS supported types, including PostGIS and WMS
  • Support drag and drop from the browser to the QGIS map canvas
  • Include file/layer management tools

SWIG Bindings

SWIG bindings are increasingly used and could be used by many projects. GDAL uses them, and this sprint will focus in them but more general discussion, goal setting, and talk on integration is very much hoped for.

Attending

Goals

  • develop a vision of how we integrate tools and create common look and feel high-level programming interfaces with SWIG bindings

Specifically for GDAL (from Tamas Szekeres' email):

  • harmonize the typemap usage between the various bindings (and update the README.typemaps accordingly)
  • determine which of the gdal/ogr features should be added to (or perhaps removed from) the SWIG interface.
  • look over the possibilities to automate the creation of the code-comment-documentation for the various languages.
  • construct the expected object model diagram to follow by the various languages (and publish the model itself)
  • discuss the language specific issues and the expected treatments.