Difference between revisions of "Google Summer of Code Application 2016"

From OSGeo
Jump to navigation Jump to search
(→‎Profile: more edits)
(→‎Profile: problem with tags for subprojects)
Line 23: Line 23:
* '''Long Description''': '''TODO''' (update past app text)
* '''Long Description''': '''TODO''' (update past app text)
* '''Application Instructions''': '''TODO''' make a wiki page and paste the text in the application
* '''Application Instructions''': '''TODO''' make a wiki page and paste the text in the application
* '''Proposal Tags''': '''TODO''' list of software projects  
* '''Proposal Tags''': '''TODO''' list of software projects - ISSUE: only 10 tags are allowed.
* '''IRC Channel, Mailing List, or Email''' done
* '''IRC Channel, Mailing List, or Email''' done

Revision as of 11:28, 11 February 2016

Application Status

ongoing, with the text below

Timeline: https://summerofcode.withgoogle.com/how-it-works/

Old applications


  • Website URL: http://osgeo.org
  • Tagline: The Open Source Geospatial Foundation
  • Logo: compass+text, square, 256px
  • Primary Open Source License: GNU General Public License (GPL)
  • Organization Category: TODO Choose between: Cloud - Data/Databases - End user apps - Graphics/Video/Audio/VR - Operating Systems - Programming languages and development tools - Science and Medicine - Security - Social/Communications - Web - Other. (We can pick only one so I would go for Other.)
  • Technology Tags (5 max): python postgresql c php javascript (were: postgres c java c# javascript c++ ajax mysql php mssql python sql)
  • Topic Tags: gis cartography maps science geospatial (were: gis, live-disc, algorithm, graph, mapping, maps, geospatial, geo, 3d, osm, openstreetmap, cartography, science)
  • Ideas List: link to Ideas wiki page
  • Short Description: TODO
  • Long Description: TODO (update past app text)
  • Application Instructions: TODO make a wiki page and paste the text in the application
  • Proposal Tags: TODO list of software projects - ISSUE: only 10 tags are allowed.
  • IRC Channel, Mailing List, or Email done

Organization description (to be reused)

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 33 code projects in particular:

Web Mapping: deegree, geomajas, GeoMoose, GeoServer, Mapbender, MapBuilder, MapFish, MapGuide Open Source, MapServer, OpenLayers, ZOO-Project, Team Engine

Desktop Applications: GRASS GIS, Quantum GIS, gvSIG, Opticks, KDE Marble

Geospatial Libraries: FDO, GDAL/OGR, GEOS, GeoTools, MetaCRS*, OSSIM, PostGIS, rasdaman

The following are sub-projects of MetaCRS: PROJ.4, GeoTIFF/libgeotiff, CS-Map, Proj4J, Proj4js, SpatialReference.org Metadata Catalogs: GeoNetwork, pycsw

Other (non-code) Projects: Public Geospatial Data, Education and Curriculum, Live Handout DVD

We host the annual FOSS4G conferences (this year two of them) with typical attendance of 500-1000+ geospatial developers, industry and government types, and researchers. Our mailing lists collectively go out to ~ 20,000 unique subscribers.

For GSoC we hope to act as an umbrella org for a number of other non-OSGeo FOSS geo projects, including pgRouting, PyWPS, istSOS, and uDig.


  • Why does your org want to participate in Google Summer of Code?: OSGeo is now a veteran GSoC organisation, and looks forward to support new students in their summer projects. Past editions of GSoC brought in new great developers, as well as GSoC mentors. Several small projects got a steady input of new code and gained in stability and visibility. OSGeo acting as umbrella organisation tightened the connection with guest software projects. We definitely look forward for another geospatial GSoC!
  • How many potential mentors have agreed to mentor this year? 16-20 (there is the option of 20+ but I don't dare choosing it as now)
  • How will you keep mentors engaged with their students?: We will welcome mentors who are regular contributors and/or experts in their field, and are willing to guide students in every step of becoming open source geo developers. We will keep personally in touch with each mentor to make sure communication with the student is efficient.
  • How will you help your students stay on schedule to complete their projects?: We will first invite them to get the clearest picture possible of their project at the beginning of GSoC. Then, with the mean of weekly reports, we'll keep track of their progress, and let them be progressively better in estimating their weekly workload.
  • How will you get your students involved in your community during GSoC?: Each student is supposed to discuss the proposal in the open with the relevant software communities even before applying on GSoC website. We ask to send weekly reports to the appropriate developer lists and get feedback there.
  • How will you keep students involved with your community after GSoC?: We ask students to include a "Future development" section in their proposal. Sometimes it is only a mind exercise, but it is often the suggestion for further work, maybe not for that student after GSoC, but also for the dev community or for a following GSoC project.
  • Has your org been accepted as a mentoring org in Google Summer of Code before? yes
  • Which years did your org participate in GSoC?: from 2007 onwards
  • What is your success/fail rate per year?

Year: pass/total

2007: 13/19 
2008: 15/19 
2009: 17/20 
2010: 7/10 
2011: 19/21 
2012: 20/22 
2013: 21/22 
2014: 22/23 
2015: 13/13
  • Are you part of a foundation/umbrella organization? no - we are one
  • What year was your project started? 2006

[Back to Google Summer of Code 2016 @ OSGeo]