Google Summer of Code Application 2009

Link ID
osgeo

Group Name (required)
OSGeo - Open Source Geospatial Foundation

Home Page URL (required)
http://www.osgeo.org/

Public Email (required)
soc@lists.osgeo.org

Description (required)
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 group applying to participate? What do you hope to gain by participating? (required)
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.

What is the main public mailing list for your group? (required)
Only a single line is accepted, so do we go with discuss or do we create a page somewhere to describe these lists?


 * OSGeo Wide - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
 * OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)

Project lists


 * GeoServer - geoserver-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/geoserver-devel )
 * GeoTools - geotools-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/geotools-devel )
 * uDig - udig-devel@lists.refractions.net ( http://lists.refractions.net/mailman/listinfo/udig-devel )
 * MapGuide - mapguide-internals@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapguide-internals )
 * OpenJUMP - jump-pilot-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel )
 * MapServer - mapserver-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapserver-dev )
 * GDAL - gdal-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/gdal-dev )
 * PostGIS - postgis-users@postgis.refractions.net ( http://postgis.refractions.net/mailman/listinfo/postgis-users )
 * GRASS - grass-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/grass-dev )
 * Mapbender - mapbender_dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapbender_dev )
 * Quantum GIS - qgis-developer@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/qgis-developer)

Where is the main IRC channel for your group? (required)
Same problem as above....
 * #osgeo on Freenode
 * #geoserver on Freenode
 * #geotools on Freenode
 * #udig on Freenode
 * #mapbuilder on Freenode
 * #mapguide on Freenode
 * #mapserver on Freenode
 * #openlayers on Freenode
 * #gdal on Freenode
 * #postgis on Freenode
 * #grass on Freenode
 * #mapbender on Freenode
 * #qgis on Freenode

What criteria do you use to select the members of your group? Please be as specific as possible. (required)
Mentors are selected by project steering committees 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.

Has your group participated previously? If so, please summarize your involvement and any past successes and failures.
OSGeo participated in GSoC in 2008. Eleven OSGeo projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors. See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

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.

What license does your organization use? (required)
This has changed to a drop down list...

Different projects operate under a variety of OSI approved licenses, mainly GPL, LGPL, and MIT/X.

--So do we choose GPL? --WB

What is the URL to the ideas list of your organization? (required)
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2009_Ideas

What is the main development mailing list for your group? (required)
Same problem as above with mailinglist... do we put discuss@osgeo.org here or what?

What is the application template you would like contributors to your organization to use. (required)
Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:

Describe your idea

Describe how you think that your project would benefit OSGeo

What is your plan for dealing with disappearing contributors? (required)
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

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.

Other possibilities include:
 * 1) Having potential students work with their potential mentor to prepare a brief plan for the implementation of their project.
 * 2) 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.
 * 3) Selecting students that have shown interest previously in the geospatial field.

What is your plan for dealing with disappearing members? (required)
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 contributors to interact with your community before, during, and after the program? (required)
The steps taken depend on the individual projects, as example last year we required weekly reports and encouraged the students to interact with us on the project mailinglists and IRC channels

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

What will you do to ensure that your accepted contributors stick with the project after the program concludes? (required)
The steps taken depend on the individual projects, as example last year many projects 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.