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

From OSGeo
Jump to navigation Jump to search
Line 87: Line 87:
 
* '''What is your success/fail rate per year?'''   
 
* '''What is your success/fail rate per year?'''   
 
Year: pass/total  
 
Year: pass/total  
 +
2018: XX/XX
 
  2017: 13/15
 
  2017: 13/15
 
  2016: 20/22
 
  2016: 20/22

Revision as of 12:42, 19 January 2019

GSoC2016Logo.jpg @ Osgeo-logo.png

Application Status

On-going (OSGeo's application is due February 6 17:00 UTC)

Timeline: https://developers.google.com/open-source/gsoc/timeline

Old applications

Profile

  • Name: OSGeo
  • Website URL: https://osgeo.org
  • Tagline: The Open Source Geospatial Foundation
  • Logo: compass+text, minimum height of 256px - use https://wiki.osgeo.org/wiki/File:Osgeo-logo.png
  • Primary Open Source License: GNU General Public License version 2.0 (GPL-2.0)
  • Organization Category: Other
  • Technology Tags (5 max): C/C++, standards, python, sql, database
  • Topic Tags: Mapping, citizen science, GIS, geospatial, open science
  • Ideas List: http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019_Ideas
  • Short Description: OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community.
  • Long Description:

using the recommended "Limited Markdown" syntax: 

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

## *Web Mapping* ##

deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers

## *Desktop Applications* ##

GRASS GIS, gvSIG, Marble, QGIS

## *Geospatial Libraries* ##

FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS

## *Metadata Catalogues* ##

GeoNetwork, pycsw

## *Content Management Systems* ##

GeoNode

## *Other Incubating Projects* ##

istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project

## *Other (non-code) Projects* ##

GeoForAll (Education and Curriculum), OSGeo-Live DVD, Public Geospatial Data

We host regional and international FOSS4G conferences with typical attendance of 500-1100+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 30,000 unique subscribers.
  • Application Instructions:

using the recommended "Limited Markdown" syntax: 

For more information on how to contact potential OSGeo mentors, including an application template, please see our [Recommendations for Students wiki page](https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).

Questionnaire

  • Why does your org want to participate in Google Summer of Code?: OSGeo is now a veteran GSoC organisation (2018 will be our 12th year participating), and we look forward to supporting new students in their summer projects. Past editions of GSoC brought in new great developers, as well as GSoC mentors (we have graduated 180 students in total through the GSoC program). Several small projects received a steady input of new code and gained in stability and visibility. OSGeo acting as umbrella organisation has also tightened the connection with guest software projects (Open Source projects involved with making maps, but are not yet officially part of OSGeo). We definitely look forward for another geospatial GSoC!
  • How many potential mentors have agreed to mentor this year? 11 - 15
  • How will you keep mentors engaged with their students?: Normally most of our mentors have already served as mentors in past GSoC; however we require at least 2 mentors for each project for consistency. We welcome mentors who are regular (code) contributors and/or experts in their field, and are willing to guide students in every step of becoming open source geo developers. We keep personally in touch with each mentor to make sure communication with the student is effective. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2018_Administrative).
  • How will you help your students stay on schedule to complete their projects?: We invite them to get the clearest picture possible of their project at the beginning of GSoC, compiling a detailed timeline. To do that, they need to analyse the problem first, then split it into smaller tasks. Mentors are called to evaluate the projects based on the timeline provided. By means of weekly reports, we keep track of their progress, and let the students adjust the timeline estimating their weekly workload, with the help of their mentors. All this is summarized in an open accessible wiki page (https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students).
  • How will you get your students involved in your community during GSoC?: Each student is expected to discuss openly the proposal 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. This year we would like mentors to test the students before selecting them, by proposing small non trivial programming tasks / bug fixes, in order to see if the student is confident enough with the software and the programming environment. We aim to foster closer communication by engaging our all students and community mentors through a accessible osgeo-gsoc channel. Through this we hope to expose students to collaborative problem solving, sharing experiences, encourage different perspectives within the open source geospatial community.
  • 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. We tend to rate better the students that show genuine enthusiasm in their development project well before GSoC starts.
  • 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 

2018: XX/XX
2017: 13/15
2016: 20/22
2015: 13/13
2014: 22/23
2013: 21/22 
2012: 20/22 
2011: 19/21 
2010: 7/10 
2009: 17/20 
2008: 15/19 
2007: 13/19
  • What year was your project started? 2006
  • Anything else we should know? The OSGeo foundation is very appreciative of the GSoC program, to help giving students an introduction to the sharing, fun, and passion throughout Open Source communities. We proudly talk about the GSoC program at our various FOSS4G events and international conferences each year all around the world. Furthermore, OSGeo participated for the first time in Google Code‑in 2017. It turned out to be a success to work with young students too. We believe the future leaders of the geospatial industry are these students. And most of all: it's fun!

[Back to Google Summer of Code 2018 @ OSGeo]

Retrieved from "http://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_Application_2019&oldid=119140"