Difference between revisions of "2008 Google SoC Application"

From OSGeo
Jump to navigation Jump to search
m (+cat)
 
(35 intermediate revisions by 19 users not shown)
Line 1: Line 1:
 +
'''This application has been sent'''
 +
 +
'''Don't bother to edit it any further'''
 +
 +
--[[User:Wolf|Wolf]] 18:11, 11 March 2008 (EDT)
 +
 
==What is your Organization's Name?==
 
==What is your Organization's Name?==
 
OSGeo - Open Source Geospatial Foundation
 
OSGeo - Open Source Geospatial Foundation
Line 26: Line 32:
  
 
==What is the main development mailing list for your organization?==
 
==What is the main development mailing list for your organization?==
−
discuss@lists.osgeo.org - see http://lists.osgeo.org/mailman/listinfo/discuss
+
 
 +
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 organization?==
 
==Where is the main IRC channel for your organization?==
Line 42: Line 65:
 
* irc://irc.freenode.net/#postgis
 
* irc://irc.freenode.net/#postgis
 
* irc://irc.freenode.net/#grass
 
* irc://irc.freenode.net/#grass
 +
* irc://irc.freenode.net/#mapbender
 +
* irc://irc.freenode.net/#qgis
  
 
==Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)==
 
==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)==
 
==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 - fwarmerdam
+
Frank Warmerdam (2007 administrator) - fwarmerdam at gmail.com
  
 
==About Your Mentors==
 
==About Your Mentors==
Line 57: Line 82:
 
* crschmidt []gmail.com (Christopher Schmidt) - OpenLayers
 
* crschmidt []gmail.com (Christopher Schmidt) - OpenLayers
 
* euzuro []gmail.com (Erik Uzureau) - OpenLayers
 
* euzuro []gmail.com (Erik Uzureau) - OpenLayers
−
* shemange []gmail.com (Gary Sherman) - QGIS
+
* 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
 
* ottens []gmail.com (Steven Ottens) - Mapbuilder, OpenLayers
 +
* cameron.shorter []gmail.com (Cameron Shorter) - Mapbuilder, OpenLayers
 
* dmorissette []gmail.com (Daniel Morissette) - MapServer, GDAL
 
* dmorissette []gmail.com (Daniel Morissette) - MapServer, GDAL
 +
* hobu.inc []gmail.com (Howard Butler) - MapServer, GDAL
 
* thomas.bonfort []gmail.com (Thomas Bonfort) - MapServer
 
* thomas.bonfort []gmail.com (Thomas Bonfort) - MapServer
−
* mloskot [] gmail.com (Mateusz Loskot) - GDAL
+
* mloskot [] gmail.com (Mateusz Loskot) - GDAL, GEOS
 
* assefay []gmail.com (Yewondwossen Assefa) - MapServer
 
* assefay []gmail.com (Yewondwossen Assefa) - MapServer
 
* woodbri []swoodbridge.com (Stephen Woodbridge) - 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==
 
==About The Program==
 
===What is your plan for dealing with disappearing students?===
 
===What is your plan for dealing with disappearing students?===
−
'''Plan A:'''
 
  
−
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 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.
 
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.
−
 
−
'''Plan B:'''
 
−
 
−
Leveraging Open Source software from the OSGeo stack, coupled with high-accuracy data sources, volunteers from the open source community will process the data, including student metadata, and the results will be used for the targeting instructions for high-powered space-based lasers. Results of this will be displayed on a large video wall, which will prove that the student really has disappeared, and should act as a deterrent to future student disappearances.
 
−
 
−
http://www.jasonbirch.com/files/space_lasers.jpg
 
−
([http://ossim.telascience.org/ossimdata/nhv/DSCF0129.JPG resized from] )
 
  
 
===What is your plan for dealing with disappearing mentors?===
 
===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.
+
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?===
 
===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.
 
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 throught the community channels rather then directly.
+
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:
 
Other possibilities include:
Line 97: Line 138:
  
 
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.
 
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.
 +
 +
[[Category: Google Summer of Code]]

Latest revision as of 01:53, 27 April 2008

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?

http://www.osgeo.org/

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

http://wiki.osgeo.org/wiki/Google_Summer_of_Code

What is the main development mailing list for your organization?

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

Where is the main IRC channel for your organization?

irc://irc.freenode.net/#osgeo

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
  • wolf[]bergenheim.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:

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

Retrieved from "http://wiki.osgeo.org/w/index.php?title=2008_Google_SoC_Application&oldid=24584"