2008 Google SoC Application
This application has been sent
Don't bother to edit it any further
--Wolf 18:11, 11 March 2008 (EDT)
What is your Organization's Name?
OSGeo - Open Source Geospatial Foundation
What is your Organization's Homepage?
Describe your organization.
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general, and 14 projects in particular.
Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?
We hope to get more students involved in open source geospatial development to grow the development community, and to advance particular projects. Additionally we hope to spread the word of open source GIS in the universities.
Did your organization participate in previous GSoC years? If so, please summarize your involvement and the successes and failures of your student projects. (optional)
OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report.
OSGeo was formed in early 2006 and hadn't participated in GSoC before 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators are involved in this years OSGeo GSoC effort.
If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? (optional)
What license does your project use?
Different projects operate under a variety of OSI approved licenses, mainly GPL, LGPL, and MIT/X.
URL for your ideas page
What is the main development mailing list for your organization?
OSGeo Wide - email@example.com (http://lists.osgeo.org/mailman/listinfo/discuss)
OSGeo SoC Mentors and Students - firstname.lastname@example.org (http://lists.osgeo.org/mailman/listinfo/soc)
- GeoServer - email@example.com ( http://lists.sourceforge.net/lists/listinfo/geoserver-devel )
- GeoTools - firstname.lastname@example.org ( http://lists.sourceforge.net/lists/listinfo/geotools-devel )
- uDig - email@example.com ( http://lists.refractions.net/mailman/listinfo/udig-devel )
- MapGuide - firstname.lastname@example.org ( http://lists.osgeo.org/mailman/listinfo/mapguide-internals )
- OpenJUMP - email@example.com ( http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel )
- MapServer - firstname.lastname@example.org ( http://lists.osgeo.org/mailman/listinfo/mapserver-dev )
- GDAL - email@example.com ( http://lists.osgeo.org/mailman/listinfo/gdal-dev )
- PostGIS - firstname.lastname@example.org ( http://postgis.refractions.net/mailman/listinfo/postgis-users )
- GRASS - email@example.com ( http://lists.osgeo.org/mailman/listinfo/grass-dev )
- Mapbender - firstname.lastname@example.org ( http://lists.osgeo.org/mailman/listinfo/mapbender_dev )
- Quantum GIS - email@example.com (http://lists.osgeo.org/mailman/listinfo/qgis-developer)
Where is the main IRC channel for your organization?
Project irc channels:
Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)
Who will be your backup organization administrator? Please enter their Google Account address. We will email them to confirm, your organization will not become active until they respond. (optional)
Frank Warmerdam (2007 administrator) - fwarmerdam at gmail.com
About Your Mentors
What criteria did you use to select these individuals as mentors? Please be as specific as possible.
Mentors are selected by project steering comittees based on their reputation as skilled developers, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process.
Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional)
- fwarmerdam gmail.com (Frank Warmerdam) - GDAL, MapServer
- wolfbergenheim.net (Wolf Bergenheim) - GRASS
- crschmidt gmail.com (Christopher Schmidt) - OpenLayers
- euzuro gmail.com (Erik Uzureau) - OpenLayers
- tim.schaub gmail.com (Tim Schaub) - OpenLayers
- eric.c2c gmail.com (Eric Lemoine) - OpenLayers
- bluecarto gmail.com (Pierre Giraud) - OpenLayers
- shermange gmail.com (Gary Sherman) - QGIS
- ottens gmail.com (Steven Ottens) - Mapbuilder, OpenLayers
- cameron.shorter gmail.com (Cameron Shorter) - Mapbuilder, OpenLayers
- dmorissette gmail.com (Daniel Morissette) - MapServer, GDAL
- hobu.inc gmail.com (Howard Butler) - MapServer, GDAL
- thomas.bonfort gmail.com (Thomas Bonfort) - MapServer
- mloskot  gmail.com (Mateusz Loskot) - GDAL, GEOS
- assefay gmail.com (Yewondwossen Assefa) - MapServer
- woodbri swoodbridge.com (Stephen Woodbridge) - MapServer
- astrid_emde osgeo.org - Mapbender
- marko.samson gmail.com - Mapbender
- christoph.baudson wheregroup.com - Mapbender
- uli osgeo.org - Mapbender
- lars.beck wheregroup.com Mapbender
- vera.schulze wheregroup.com Mapbender
- arkepp gmail.com (Arne Kepp)- GeoServer / GeoTools / GeoWebcache
- andrea.aime gmail.com (Andrea Aime) - GeoServer / GeoTools
- cdwinslow gmail.com - (David Winslow) GeoServer / GeoTools
- sbenthall gmail.com - (Seb Benthall) OpenLayers
- jody.garnett gmail.com - (Jody Garnett) GeoTools / uDig
- andrea.antonello gmail.com - (Andrea Antonello) JGrass / uDig
- tbadard gmail.com (Thierry Badard) - GeOxygene, GeoKettle and GeoMondrian
- kneufeld refractions.net (Kevin Neufeld) - PostGIS
- benjubb gmail.com (Ben Jubb) - PostGIS, GEOS
- lorenzo ominiverdi.com (Lorenzo Becchi) - OpenLayers
- tkeitt gmail.com (Tim Keitt) - PostGIS, GDAL, QGIS
- szekerest gmail.com (Tamas Szekeres) - GDAL, MapServer
- ijturton  gmail.com (Ian Turton) - GeoTools
About The Program
What is your plan for dealing with disappearing students?
In order to minimize the likelyhood of disappearing students we will ensure that the OSGeo administrative contact and the mentor have full contact information (email, home phone, etc) so that we can keep in touch with them.
In addition, we will make our reporting requirements clear up front. Letting the students know that we will require weekly progress reports, participation on public IRC channels and mailing lists will all help ensure ongoing commitment to the work.
What is your plan for dealing with disappearing mentors?
Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. Where possible we also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the mentor in case of changing circumstances.
What steps will you take to encourage students to interact with your project's community before, during and after the program?
The steps taken depend on the individual projects, as example last year GeoTools project has asked for weekly attendence at IRC meetings or status email.
Further more the mentors are encouraged to actively involve the students in the community, but having the student interact with the mentor through the community channels rather then directly.
Other possibilities include:
- Having potential students work with their potential mentor to prepare a brief plan for the implementation of their project.
- Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the appropriate OSGeo or project-specific mailing list when they have reached a milestone, giving a brief description of the work completed to that date.
- Selecting students that have shown interest previously in the geospatial field.
What will you do to ensure that your accepted students stick with the project after GSoC concludes?
The steps taken depend on the individual projects, as example last year GeoTools project asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.
Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.