Difference between revisions of "Google Summer of Code Application 2017"
Jump to navigation
Jump to search
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<center> | <center> | ||
| − | [[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] <font size="+3"> @ </font> [[Image: | + | [[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] <font size="+3"> @ </font> [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]] |
</center> | </center> | ||
== Application Status == | == Application Status == | ||
| − | ''''' | + | '''''Completed''''' (OSGeo's application is due 9 February [https://www.timeanddate.com/worldclock/fixedtime.html?year=2017&month=02&day=09&hour=16&min=0&sec=0%2016.00UTC 16:00 UTC]) |
: Timeline: https://developers.google.com/open-source/gsoc/timeline | : Timeline: https://developers.google.com/open-source/gsoc/timeline | ||
| Line 19: | Line 19: | ||
* '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/images/7/74/OSGeo_logo_750_317.png | * '''Logo''': compass+text, minimum height of 256px - use https://wiki.osgeo.org/images/7/74/OSGeo_logo_750_317.png | ||
* '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0) | * '''Primary Open Source License''': GNU General Public License version 2.0 (GPL-2.0) | ||
| − | * '''Organization Category''': | + | * '''Organization Category''': Other |
* '''Technology Tags (5 max)''': C++, standards, python, C, sql | * '''Technology Tags (5 max)''': C++, standards, python, C, sql | ||
* '''Topic Tags''': gis cartography maps science geospatial (were: gis, live-disc, algorithm, graph, mapping, maps, geospatial, geo, 3d, osm, openstreetmap, cartography, science) | * '''Topic Tags''': gis cartography maps science geospatial (were: gis, live-disc, algorithm, graph, mapping, maps, geospatial, geo, 3d, osm, openstreetmap, cartography, science) | ||
| Line 25: | Line 25: | ||
* '''Short Description''': OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community. | * '''Short Description''': OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community. | ||
* '''Long Description''': | * '''Long Description''': | ||
| − | + | using the recommended "Limited Markdown" syntax: | |
<pre> | <pre> | ||
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: | 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: | ||
| Line 59: | Line 59: | ||
We host regional and international FOSS4G conferences with typical attendance of 500-1000+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 28,600 unique subscribers. | We host regional and international FOSS4G conferences with typical attendance of 500-1000+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 28,600 unique subscribers. | ||
</pre> | </pre> | ||
| + | * '''Application Instructions''': | ||
| + | using the recommended "Limited Markdown" syntax: | ||
| + | <pre> | ||
| + | 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). | ||
| + | </pre> | ||
| + | * '''Proposal Tags''': New Feature,Optimization,Web Mapping,Desktop,Geospatial Libraries,Metadata Catalogue,Content Management,Incubating Project,Other Project | ||
| + | * '''Chat Contact Method''': https://wiki.osgeo.org/wiki/IRC | ||
| + | * '''Mailing List''': http://www.osgeo.org/content/faq/mailing_lists.html#discuss | ||
| + | * '''General email''': gsoc-admin(at)osgeo(dot)org | ||
| + | * '''Google+ url''': https://plus.google.com/communities/105969056638310510633 | ||
| + | * '''Twitter url''': https://twitter.com/osgeo | ||
| + | * '''Blog url''': http://planet.osgeo.org/ | ||
== Questionnaire == | == Questionnaire == | ||
| − | * '''Why does your org want to participate in Google Summer of Code?''': OSGeo is now a veteran GSoC organisation, and | + | * '''Why does your org want to participate in Google Summer of Code?''': OSGeo is now a veteran GSoC organisation (2017 will be our 11th 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 167 students in total through the GSoC program). 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?''' 20+ | * '''How many potential mentors have agreed to mentor this year?''' 20+ | ||
| − | * '''How will you keep mentors engaged with their students?''': Normally our mentors have served in the role also in the past. However we require at least 2 mentors for each project. We 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 keep personally in touch with each mentor to make sure communication with the student is effective. | + | * '''How will you keep mentors engaged with their students?''': Normally our mentors have served in the role also in the past. However we require at least 2 mentors for each project. 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_2017_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. | + | * '''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. | * '''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. | ||
| − | * '''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 | + | * '''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 | * '''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 | * '''Which years did your org participate in GSoC?''': from 2007 onwards | ||
| Line 84: | Line 96: | ||
* '''Are you part of a foundation/umbrella organization?''' OSGeo is a non-profit foundation | * '''Are you part of a foundation/umbrella organization?''' OSGeo is a non-profit foundation | ||
| − | * '''What year was your project started?''' The OSGeo foundation | + | * '''What year was your project started?''' The OSGeo foundation began in 2006, and we celebrated our 11th year as a foundation on 4 February (http://www.osgeo.org/node/1766). |
| + | |||
| + | * '''Anything else we should know?''' The OSGeo foundation is very appreciative of the GSoC program, to help give 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 each year all around the world. We believe the future leaders of the geospatial industry are these students. | ||
[Back to [[Google Summer of Code 2017]] @ OSGeo] | [Back to [[Google Summer of Code 2017]] @ OSGeo] | ||
Latest revision as of 05:50, 7 September 2017
@ 
Application Status
Completed (OSGeo's application is due 9 February 16:00 UTC)
Old applications
Profile
- Website URL: http://osgeo.org
- Tagline: The Open Source Geospatial Foundation
- Logo: compass+text, minimum height of 256px - use https://wiki.osgeo.org/images/7/74/OSGeo_logo_750_317.png
- Primary Open Source License: GNU General Public License version 2.0 (GPL-2.0)
- Organization Category: Other
- Technology Tags (5 max): C++, standards, python, C, 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: https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_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-1000+ geospatial developers, industry and government leaders, and researchers. Our mailing lists collectively go out to ~ 28,600 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).
- Proposal Tags: New Feature,Optimization,Web Mapping,Desktop,Geospatial Libraries,Metadata Catalogue,Content Management,Incubating Project,Other Project
- Chat Contact Method: https://wiki.osgeo.org/wiki/IRC
- Mailing List: http://www.osgeo.org/content/faq/mailing_lists.html#discuss
- General email: gsoc-admin(at)osgeo(dot)org
- Google+ url: https://plus.google.com/communities/105969056638310510633
- Twitter url: https://twitter.com/osgeo
- Blog url: http://planet.osgeo.org/
Questionnaire
- Why does your org want to participate in Google Summer of Code?: OSGeo is now a veteran GSoC organisation (2017 will be our 11th 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 167 students in total through the GSoC program). 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? 20+
- How will you keep mentors engaged with their students?: Normally our mentors have served in the role also in the past. However we require at least 2 mentors for each project. 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_2017_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.
- 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
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
- Are you part of a foundation/umbrella organization? OSGeo is a non-profit foundation
- What year was your project started? The OSGeo foundation began in 2006, and we celebrated our 11th year as a foundation on 4 February (http://www.osgeo.org/node/1766).
- Anything else we should know? The OSGeo foundation is very appreciative of the GSoC program, to help give 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 each year all around the world. We believe the future leaders of the geospatial industry are these students.
[Back to Google Summer of Code 2017 @ OSGeo]