Difference between revisions of "FOSS4G2008 CodeSprint"

From OSGeo
Jump to navigation Jump to search
(cleaning up for JGrass / Udig)
 
(35 intermediate revisions by 17 users not shown)
Line 1: Line 1:
'''There WILL be code sprint on Friday 3rd Oct'''
+
Back to [[FOSS4G2008]]...
 +
 
 +
== Date and Organizing Contacts ==
 +
 
 +
'''Date:''' Saturday 4 October 2008
 +
We have decided to do this on the Saturday so 'sprinters' don't miss any workshops or socialising during the week.
 +
 
 +
'''Venue:''' Cape Town City Council offices
 +
 
 +
'''Organising Contact:''' Tim Sutton
 +
 
 +
'''Contact Email:''' tim@linfiniti.com
  
'''Note that (on 12 May) everything below is a copy of the 2007 code sprint page, waiting for Tim and others to update it for 2008'''
+
== Procedure ==
  
Back to [[FOSS4G2008]]...
+
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.
  
== Organizing Contacts ==
+
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.
  
* Tim Sutton
 
 
== Interested to organize a code sprint ==
 
== Interested to organize a code sprint ==
  
Line 16: Line 33:
  
 
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...
 
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...
 +
 +
== Rooms ==
 +
 +
[[image:RoomA.JPG]]
 +
[[image:RoomJ.JPG]]
 +
[[image:RoomG1.JPG]]
 +
[[image:RoomH.JPG]]
 +
 +
One or more of these rooms will be used for the code sprint depending on turn out.
  
 
== Motivation and Direction ==
 
== Motivation and Direction ==
Line 21: Line 47:
 
A day, a code base, and your imagination?
 
A day, a code base, and your imagination?
  
On the Friday after the conference, a [http://www.foss4g2007.org/code_sprint/ 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.
+
On the Saturday 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:
 
Is this your First Sprint? Here is some background information to get you started:
Line 31: Line 57:
 
To participate, start a section below for your project.
 
To participate, start a section below for your project.
  
== GeoTools ==
+
== OSGeo Marketing ==
  
 
=== Attending ===
 
=== Attending ===
  
* Andrea Aime
+
* Jeroen Ticheler
* [[User:Jdeolive | Justin Deoliveira]]
+
* Arnulf Christl
* [[User:Jive | Jody Garnett]]
 
* [[User:Chorner | Cory Horner]]
 
  
 
=== Goals ===
 
=== Goals ===
  
We are going to to do a cross project code sprint (with GeoServer and uDig developers) focused on changing the internals over to the new Feature model. If we run across any old Filter code we will take care of it as well. The "old" Feature interface will still be available for client code to use - this sprint is just focused on updating (and testing the heck out of) our internals.
+
* Optimize the new OSGeo logo vectors to be very precise and scalable.
 +
* Update pages with the OSGeo logo(s).
  
=== Preparation ===
+
== GRASS ==
  
We need *good* code examples of how to do the following before we start: Use SimpleFeatureTypeBuilder, use SimpleFeatureBuilder. It may also help to have a big old class diagram of the Feature model.
+
=== Attending ===
  
We expect each developer to have a working build of trunk, have read the interfaces for SimpleFeature and the above code examples.
+
* <strike>[[Markus Neteler]]</strike> (since it was moved to Saturday, just booked the flight without realizing)
 +
* [[User:Wolf|Wolf Bergenheim]] via IRC
 +
* [[User:Landa|Martin Landa]] via IRC
 +
* [[User:mlennert|Moritz Lennert]] via IRC (tbc)
  
=== Out of Scope ===
+
=== Goals ===
  
There are lots of things that are going to have to follow out of scope for this sprint. I am going to bring attention to the following explicitly. *Performance* (the implementation of SimpleFeature available here is for the transition period only - optimize on your own time after we have updated the codebase to handle it). *Javadocs* - much of the javadocs will be out of date by the time we are done, type a sentence and move on.
+
* Hack session: fix bugs, new features
 +
* Maybe invite power users to get in touch?
 +
: Remote users via IRC channel
  
During the code sprint you will be tempted - when you run into any good ideas on these topics simply fire an email off to the devel list and we will revisit it later.
+
== Udig / JGrass ==
  
== GRASS ==
+
Cross project code sprint with the JGrass and uDig projects.
  
 
=== Attending ===
 
=== Attending ===
  
* [[Markus Neteler]]
+
* [[User:Moovida | Andrea Antonello]]
 +
* [[User:silli | Silvia Franceschi]]
 +
 
  
 
=== Goals ===
 
=== Goals ===
 +
To be defined...
  
* Hack session
 
  
== GDAL Bug Squash ==
+
== Quantum GIS (QGIS) ==
  
Details at: http://trac.osgeo.org/gdal/wiki/BugSquash2007
+
=== Attending ===
  
== GeoNetwork / Metadata Madness ==
+
* [[Tim Sutton]]
 +
* Horst Duster
 +
* Marco Hugentobler
  
 
=== Goals ===
 
=== 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.
+
* Hack session: fix bugs, new features
 
+
* Maybe invite power users to get in touch?
=== Attending ===
+
: Remote users via IRC channel
 
 
* [[User:JoWalsh|Jo Walsh]]
 
* [[User:Fxp|François Prunayre]]
 
  
 
== OpenLayers ==
 
== OpenLayers ==
Line 85: Line 116:
 
=== Attending ===
 
=== Attending ===
  
* [[User:crschmidt|Christopher Schmidt]]
+
* [[Erik Uzureau]]
* [[User:aaronr|Aaron Racicot]]
 
 
* [[User:tschaub|Tim Schaub]]
 
* [[User:tschaub|Tim Schaub]]
* [[User:euzuro|Erik Uzureau]]
+
* [[Eric Lemoine]]
* [[User:ominiverdi|Lorenzo Becchi]]
 
* [[User:SchuylerErle|Schuyler Erle]]
 
* [[User:pagameba|Paul Spencer]]
 
* [[User:pgiraud|Pierre Giraud]]
 
* [[User:madair|Mike Adair]]
 
* [[User:ahocevar|Andreas Hocevar]]
 
* [[User:dzwarg|David Zwarg]]
 
* [[User:camerons|Cameron Shorter]], after lunch for a couple of hours, remotely from Australia.
 
  
 
=== Goals ===
 
=== Goals ===
Hack, hack, hack. I think this will be OpenLayers 2.6 or 2.7?
+
* OpenLayers 2.8 Release Planning
 +
* OpenLayers 3.0 Brainstorming Session
  
Some specific ideas:
+
== SEXTANTE ==
* OL Context/WMC+ - read/write support for and OWS Context style doc
 
* SLD support - edit/read/write
 
* OWS:Filter - pass & integrate with WFS Layer. (Interest to Cameron)
 
* Renderer Optimizations
 
** consider attributing geometry components with a minResolution below which the renderer doesn't deal with them
 
** clipping - svg supports clipping, we need to consider clipping or another method of dealing with geometries that extend beyond the renderer bounds
 
** add <canvas> renderer
 
* integrate emanual's animated zooming stuff
 
* client-side coordinate transformations
 
* WMS Manager - What do we do with it? :-) [[User:ominiverdi|ominiverdi]]
 
  
== QGIS ==
+
Code Sprint to integrate the SEXTANTE library with other Java-GIS projects
'''CANCELLED'''
 
 
 
== SWIG Bindings ==
 
 
 
SWIG bindings are increasingly used and could be used by many projects. GDAL uses them, and this sprint will focus in GDAL's (new generation) bindings but more general discussion, goal setting, and talk on integration is very much hoped for.
 
  
 
=== Attending ===
 
=== Attending ===
  
* [[User:ajolma|Ari Jolma]]
+
* [[User:Volaya | Victor Olaya]]
* [[User:szekerest|Tamas Szekeres]]
 
  
 
=== Goals ===
 
=== Goals ===
  
* present a short introduction to SWIG (AJ: I'll prepare this)
+
*To improve GeoTools-SEXTANTE integration
* develop a vision of how we integrate tools and create common look and feel high-level programming interfaces with SWIG bindings
+
*To discuss the integration of SEXTANTE as a base element for WPS processes.
 +
*To introduce SEXTANTE to other projects and show them how to incorporate SEXTANTE-based processes in them
  
Specifically for GDAL (from Tamas Szekeres' email):
 
  
* harmonize the typemap usage between the various bindings (and update the README.typemaps accordingly)
+
== OSGeo packaging & Repo ==
* determine which of the gdal/ogr features should be added to (or perhaps removed from) the SWIG interface.
+
=== Goals ===
* look over the possibilities to automate the creation of the code-comment-documentation for the various languages.
+
* Initiate the provision of an OSGeo run repo for packaging OSGeo projects & educational material
* construct the expected object model diagram to follow by the various languages (and publish the model itself)
+
* Tentative target platforms: Ubuntu 8.10 with a view to packages flowing into Debian Sid initially.
* discuss the language specific issues and the expected treatments.
+
* Other platforms to be supported in the future as more people resources are available
 +
* Support the continued development of the Live DVD.
 +
* Start packaging initial selection of educational material
 +
=== Attending ===
 +
[[User:Tbowden | Tim Bowden]]
  
== Udig / JGrass ==
+
== Geomajas ==
  
Cross project code sprint with the JGrass and uDig projects.
+
Code Sprint to integrate the Geomajas project with other Java-GIS projects
  
 
=== Attending ===
 
=== Attending ===
  
* [[User:Moovida | Andrea Antonello]]
+
* [[User:dirkf | Dirk Frigne]]
* [[User:silli | Silvia Franceschi]]
 
  
 +
=== Goals ===
  
=== Goals ===
+
*To improve the contents of the website
To be defined...
+
*To get into contact with other projects we want to integrate with
 +
*To share some ideas about work that can be established in common
  
  
== French translation ==
+
== GeoNetwork ==
Contact: [[User:Yjacolin|Yjacolin]], [[User:VincentP|Vincent Picavet]]
 
 
=== Attending ===
 
=== Attending ===
See [[OSGeo_fr_FOSS4G_2007_fr#Traduction_sprint|Translation sprint (in french)]]
 
=== Goals ===
 
Translate OSGeo Journal Vol. 2 into french. Some other aspects of translation/localization of OSGeo software could be discussed as well.
 
  
== Promotion Projects: Demo Videos, Website ==
+
* [[User:fxp | Francois Prunayre]]
Contact: [[User:Tmitchell|Tyler Mitchell]]
+
* Paul Hasenohr
 +
 
 
=== Goals ===
 
=== Goals ===
For at least part of the Code Sprint time, we can meet to put together various screenshot and/or video demonstrations of OSGeo software.  These will be used for future promotional purposes at conferences, online and more.
+
* To improve multilingual support (installer, documentation, GAST)
 
+
* To add support for WPS in harvesting engine
Also, we can update the OSGeo.org website for the projects' info sheet: i.e. http://osgeo.org/mapserver, etc.
 
  
== MAJAS call for participation ==
+
== OpenStreetMap ==
Contact: [[User:dfc|Dirk Frigne]]
+
* Mikel Maron
=== What is Majas ? ===
+
* Josh Livni
MAJAS is a component framework for building rich Internet applications (RIA) with sophisticated capabilities for the display, analysis and management of geographic information. It is a building block that allows developers to add maps and other geographic data capabilities to their web applications.
 
  
 
=== Goals ===
 
=== Goals ===
Finding participants for further development and maintenance of the project
 
and warming up the community for this project (and have a beer afterwards)
 
  
* Discussion about setting up collaboration MAJAS
+
Partyserver: web service to produce party render, animated GPX videos
* Q&A MAJAS
 
* Roadmap MAJAS
 
* Some technical issues like OSGI server integration
 
  
  
[[Category:FOSS4G]]
 
 
[[Category:Code Sprints]]
 
[[Category:Code Sprints]]
 
[[Category:FOSS4G2008]]
 
[[Category:FOSS4G2008]]

Latest revision as of 04:49, 12 February 2015

Back to FOSS4G2008...

Date and Organizing Contacts

Date: Saturday 4 October 2008 We have decided to do this on the Saturday so 'sprinters' don't miss any workshops or socialising during the week.

Venue: Cape Town City Council offices

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...

Rooms

RoomA.JPG RoomJ.JPG RoomG1.JPG RoomH.JPG

One or more of these rooms will be used for the code sprint depending on turn out.

Motivation and Direction

A day, a code base, and your imagination?

On the Saturday 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.

OSGeo Marketing

Attending

  • Jeroen Ticheler
  • Arnulf Christl

Goals

  • Optimize the new OSGeo logo vectors to be very precise and scalable.
  • Update pages with the OSGeo logo(s).

GRASS

Attending

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...


Quantum GIS (QGIS)

Attending

Goals

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

OpenLayers

Attending

Goals

  • OpenLayers 2.8 Release Planning
  • OpenLayers 3.0 Brainstorming Session

SEXTANTE

Code Sprint to integrate the SEXTANTE library with other Java-GIS projects

Attending

Goals

  • To improve GeoTools-SEXTANTE integration
  • To discuss the integration of SEXTANTE as a base element for WPS processes.
  • To introduce SEXTANTE to other projects and show them how to incorporate SEXTANTE-based processes in them


OSGeo packaging & Repo

Goals

  • Initiate the provision of an OSGeo run repo for packaging OSGeo projects & educational material
  • Tentative target platforms: Ubuntu 8.10 with a view to packages flowing into Debian Sid initially.
  • Other platforms to be supported in the future as more people resources are available
  • Support the continued development of the Live DVD.
  • Start packaging initial selection of educational material

Attending

Tim Bowden

Geomajas

Code Sprint to integrate the Geomajas project with other Java-GIS projects

Attending

Goals

  • To improve the contents of the website
  • To get into contact with other projects we want to integrate with
  • To share some ideas about work that can be established in common


GeoNetwork

Attending

Goals

  • To improve multilingual support (installer, documentation, GAST)
  • To add support for WPS in harvesting engine

OpenStreetMap

  • Mikel Maron
  • Josh Livni

Goals

Partyserver: web service to produce party render, animated GPX videos