Google Summer of Code Application 2017 - Revision history

Jmckenna at 13:50, 7 September 2017

2017-09-07T13:50:04Z

Madi: /* Application Status */

2017-07-15T12:32:01Z

Application Status

Madi: /* Profile */

2017-02-08T16:02:59Z

Profile

Jmckenna: /* Questionnaire */

2017-02-07T22:58:29Z

Questionnaire

Jmckenna: /* Profile */

2017-02-07T20:15:04Z

Profile

Jmckenna: /* Profile */

2017-02-07T20:13:22Z

Profile

Jmckenna: /* Profile */

2017-02-07T20:12:35Z

Profile

Jmckenna: /* Profile */

2017-02-07T20:06:47Z

Profile

Jmckenna: /* Profile */

2017-02-07T20:05:29Z

Profile

Jmckenna: /* Profile */

2017-02-07T20:02:27Z

Profile

@@ Line 1: / Line 1: @@
 <center>
-[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
+[[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>

@@ Line 5: / Line 5: @@
 == Application Status ==
-'''''DRAFT stage''''' (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])
+'''''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

@@ Line 19: / Line 19: @@
 * '''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''': 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.)
+* '''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)

@@ Line 74: / Line 74: @@
 == Questionnaire ==
-* '''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!
+* '''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 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 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, also well before GSoC starts.
+* '''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
@@ Line 96: / Line 96: @@
 * '''Are you part of a foundation/umbrella organization?''' OSGeo is a non-profit foundation
-* '''What year was your project started?''' The OSGeo foundation officially began back in 2006, and we celebrate our 11th year as a foundation on 4 February.
+* '''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).
 [Back to [[Google Summer of Code 2017]] @ OSGeo]

@@ Line 68: / Line 68: @@
 * '''Mailing List''': http://www.osgeo.org/content/faq/mailing_lists.html#discuss
 * '''General email''': gsoc-admin(at)osgeo(dot)org
 == Questionnaire ==

@@ Line 65: / Line 65: @@
 </pre>
 * '''Proposal Tags''': New Feature,Optimization,Web Mapping,Desktop,Geospatial Libraries,Metadata Catalogue,Content Management,Incubating Project,Other Project
 == Questionnaire ==

@@ Line 64: / Line 64: @@
 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>
 == Questionnaire ==

@@ Line 25: / Line 25: @@
 * '''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:
+using the recommended "Limited Markdown" syntax:
 <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:
@@ Line 58: / Line 58: @@
 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>

@@ Line 24: / Line 24: @@
 * '''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''': 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:
+* '''Long Description''':
-Web Mapping: deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers
+## *Web Mapping* ##
-Desktop Applications: GRASS GIS, gvSIG, Marble, QGIS
+deegree, geomajas, GeoMOOSE, GeoServer, Mapbender, MapFish, MapGuide Open Source, MapServer, OpenLayers
-Geospatial Libraries: FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS
+## *Desktop Applications* ##
-Metadata Catalogues: GeoNetwork, pycsw
+GRASS GIS, gvSIG, Marble, QGIS
-Content Management Systems: GeoNode
+## *Geospatial Libraries* ##
-Other incubating projects include: istSOS, MetaCRS, Opticks, Orfeo ToolBox (OTB), PyWPS, Team Engine, ZOO-Project
+FDO, GDAL/OGR, GEOS, GeoTools, OSSIM, PostGIS
-Other (non-code) Projects: GeoForAll (Education and Curriculum), OSGeo-Live DVD, Public Geospatial Data
+## *Metadata Catalogues* ##
-We host regional and international FOSS4G conferences 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.
+GeoNetwork, pycsw
 == Questionnaire ==