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

From OSGeo
Jump to navigation Jump to search
 
(66 intermediate revisions by 36 users not shown)
Line 6: Line 6:
  
 
This is the central page for OSGeo administrative information in Google Summer of Code 2016.
 
This is the central page for OSGeo administrative information in Google Summer of Code 2016.
 +
 +
== GSoC general information ==
 +
 +
* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
 +
* [https://developers.google.com/open-source/gsoc/resources/ Google's FAQ on the program]
 +
* [https://summerofcode.withgoogle.com/ Official 2016 GSoC site]
  
 
== Contacts ==  
 
== Contacts ==  
Line 22: Line 28:
 
|width=100px|'''Surname'''
 
|width=100px|'''Surname'''
 
|width=100px|'''Nickname (IRC)'''
 
|width=100px|'''Nickname (IRC)'''
−
|width=200px|'''email'''
+
|width=250px|'''email'''
−
|width=100px|'''Software'''
+
|'''Software community'''
−
|'''Project / Idea(s) you are available to mentor'''
+
|'''Idea(s) you are available to mentor'''
 
|-
 
|-
 
|1
 
|1
Line 32: Line 38:
 
|diregola AT gmail DOT com  
 
|diregola AT gmail DOT com  
 
|admin at OSGeo
 
|admin at OSGeo
−
|Administrator of GSoC at OSGeo
+
|Idea I would like to mentor
 
|-
 
|-
 
|2
 
|2
Line 40: Line 46:
 
|alexander.bruy AT gmail.com  
 
|alexander.bruy AT gmail.com  
 
|QGIS
 
|QGIS
−
|QGIS
+
|
 
|-
 
|-
 
|3
 
|3
Line 48: Line 54:
 
|volayaf AT gmail DOT com  
 
|volayaf AT gmail DOT com  
 
|QGIS
 
|QGIS
 +
|
 +
|-
 +
|4
 +
|Daniel
 +
|Kastl
 +
|dkastl
 +
|daniel AT georepublic DOT de
 +
|pgRouting
 +
|
 +
|-
 +
|5
 +
|Massimiliano
 +
|Cannata
 +
|maxi
 +
|massimiliano.cannata AT gmail DOT com
 +
|istSOS
 +
|
 +
|-
 +
|6
 +
|Milan
 +
|Antonovic
 +
|milan
 +
|milan.antonovic AT gmail DOT com
 +
|istSOS
 +
|
 +
|-
 +
|7
 +
|Jachym
 +
|Cepicky
 +
|jachym
 +
|jachym.cepicky AT gmail
 +
|PyWPS
 +
|
 +
|-
 +
|8
 +
|Andrea
 +
|Antonello
 +
|moovida
 +
|andrea.antonello AT gmail DOT com
 +
|JGrasstools, gvSIG, Geopaparazzi
 +
|
 +
|-
 +
|9
 +
|Rashad
 +
|Kanavath
 +
|rashadkm
 +
|rashadkm AT gmail DOT com
 +
|GRASS GIS, OSSIM, GDAL
 +
|
 +
|-
 +
|10
 +
|Cameron
 +
|Shorter
 +
|CameronShorter
 +
|cameronDOTs h o r ter AT gmail com
 +
|OSGeo-Live
 +
|
 +
|-
 +
|11
 +
|Stephen
 +
|Woodbridge
 +
|woodbri
 +
|woodbri AT swoodbridge DOT com
 +
|pgRouting
 +
|
 +
|-
 +
|12
 +
|Vicky
 +
|Vergara
 +
|cvvergara
 +
|vicky AT georepublic DOT de
 +
|pgRouting
 +
|
 +
|-
 +
|13
 +
|Dmitry
 +
|Baryshnikov
 +
|bishop
 +
|bishop.dev AT gmail.com
 +
|GDAL
 +
|
 +
|-
 +
|14
 +
|Luca
 +
|Delucchi
 +
|lucadelu
 +
|lucadeluge AT gmail.com
 +
|GRASS GIS
 +
|
 +
|-
 +
|15
 +
|Anna
 +
|Petrasova
 +
|
 +
|kratochanna AT gmail.com
 +
|GRASS GIS
 +
|
 +
|-
 +
|16
 +
|Stefan
 +
|Steiniger
 +
|
 +
|sstein AT geo.uzh.ch
 +
|OneBusAway, OpenTripPlanner, OpenJUMP
 +
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]
 +
|-
 +
|17
 +
|Sean
 +
|Barbeau
 +
|
 +
|barbeau AT cutr.usf.edu
 +
|OneBusAway, OpenTripPlanner
 +
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here], also there are ideas around for OpenTripPlanner Android App, and the GTFS-RT Validator
 +
|-
 +
|18
 +
|Riccardo
 +
|Rigon
 +
|abouthydrology
 +
|rccrd.rgn AT gmail DOT com
 +
|JGrasstools, gvSIG, Geopaparazzi
 +
|
 +
|-
 +
|19
 +
|Vaclav
 +
|Petras
 +
|
 +
|wenzeslaus AT gmail.com
 +
|GRASS GIS
 +
|
 +
|-
 +
|20
 +
|Oliver
 +
|May
 +
|
 +
|oliver AT dfc DOT be
 +
|Geomajas, leaflet, openlayers, geoserver, geotools
 +
|
 +
|-
 +
|21
 +
|Even
 +
|Rouault
 +
|
 +
|even dot rouault AT spatialys dot com
 +
|GDAL
 +
|
 +
|-
 +
|22
 +
|Alexandre
 +
|Dubé
 +
|
 +
|adube AT mapgears dot com
 +
|OL3-Google-Maps
 +
|
 +
|-
 +
|23
 +
|Moritz
 +
|Lennert
 +
|
 +
|mlennert AT club dot worldonline dot be
 +
|GRASS GIS
 +
|
 +
|-
 +
|24
 +
|Roberto
 +
|Marzocchi
 +
|
 +
|roberto dot marzocchi AT gmail dot com dot
 +
|GRASS GIS
 +
|
 +
|-
 +
|25
 +
|Brian M
 +
|Hamlin
 +
|darkblue_b
 +
|maplabs AT light42 DOT com
 +
|SciPy geospatial stack, PostGIS, gdal 2.0
 +
|
 +
|-
 +
|26
 +
|Jessica
 +
|Lapointe
 +
|
 +
|jlapointe AT mapgears dot com
 +
|OL3-Google-Maps
 +
|
 +
|-
 +
|27
 +
|Gérald
 +
|Fenoy
 +
|djay
 +
|gerald.fenoy AT geolabs.fr
 +
|ZOO-Project
 +
|
 +
|-
 +
|28
 +
|Massimo
 +
|Di Stefano
 +
|epifanio
 +
|epiesasha AT me DOT com
 +
|GRASS GIS
 +
| webgrass
 +
|-
 +
|29
 +
|Patrick
 +
|Hogan
 +
|
 +
|patrick.hogan AT nasa DOT gov
 +
|NASA World Wind
 +
|
 +
|-
 +
|30
 +
|Oscar
 +
|Kramer
 +
|
 +
|oscarkramer AT yahoo DOT com
 +
|OSSIM
 +
|
 +
|-
 +
|31
 +
|Jakub
 +
|Balhar
 +
|
 +
|jakub AT balhar DOT net
 +
|NASA World Wind
 +
|
 +
|-
 +
|32
 +
|Jonas
 +
|Eberle
 +
|
 +
|jonas.eberle AT gmx DOT de
 +
|PyWPS
 +
|
 +
|-
 +
|33
 +
|Martin
 +
|Landa
 +
|
 +
|landa.martin AT gmail DOT com
 +
|GRASS GIS
 +
|
 +
|-
 +
|34
 +
|Rob
 +
|Emanuele
 +
|lossyrob
 +
|rdemanuele AT gmail DOT com
 +
|GDAL
 +
|
 +
|-
 +
|35
 +
|Anita
 +
|Graser
 +
|
 +
|anitagraser AT gmx DOT at
 +
|QGIS
 +
|
 +
|-
 +
|36
 +
|Giustino
 +
|Tonon
 +
|
 +
|giustino.tonon AT unibz DOT it
 +
|JGrasstools
 +
|
 +
|-
 +
|37
 +
|Alessandro
 +
|Pasotti
 +
|
 +
|apasotti AT gmail DOT com
 
|QGIS
 
|QGIS
 +
|QGIS Symbology Repository
 +
|-
 +
|38
 +
|David
 +
|Burken
 +
|
 +
|dburken AT gmail DOT com
 +
|OSSIM
 +
|
 +
|-
 +
|39
 +
|Óg
 +
|Crudden
 +
|
 +
|og.crudden AT gmail.com
 +
|OneBusAway
 +
|see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]
 +
|-
 +
|40
 +
|Markus
 +
|Neteler
 +
|
 +
|neteler AT osgeo DOT org
 +
|GRASS GIS
 +
|-
 +
|41
 +
|Joaquin
 +
|del Cerro
 +
|
 +
|jjdelcerro AT gvsig DOT com
 +
|gvSIG
 +
|
 
|-
 
|-
 +
|42
 +
|Óscar
 +
|Mártinez
 +
|
 +
|masquesig AT gmail DOT com
 +
|gvSIG
 +
|
 +
|-
 +
|43
 +
|Mirko
 +
|Cardoso
 +
|mirko
 +
|cardoso.mirko AT gmail DOT com
 +
|istSOS
 +
|
 
|}
 
|}
−
 
−
== 2016 ==
 
−
* OSGeo [[Google Summer of Code Application 2016]]
 
−
* [https://summerofcode.withgoogle.com/ Official 2016 GSoC site]
 
−
<!--* [http://www.google-melange.com/gsoc/org2/show/google/gsoc2015/osgeo The 2015 OSGeo home at Melange] -->
 
−
 
−
== Previous years ==
 
−
 
−
* SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://www.google-melange.com/gsoc/org/google/gsoc2009/osgeo 2009], [http://www.google-melange.com/gsoc/org/google/gsoc2010/osgeo 2010], [http://www.google-melange.com/gsoc/org/google/gsoc2011/osgeo 2011], [http://www.google-melange.com/gsoc/org/google/gsoc2012/osgeo 2012], [http://www.google-melange.com/gsoc/org/google/gsoc2013/osgeo 2013], [https://www.google-melange.com/gsoc/org2/google/gsoc2015/osgeo 2015]
 
−
 
−
== Learn more ==
 
−
 
−
* OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]], [[Google Summer of Code 2011|2011]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2014|2014]], [[Google Summer of Code 2015|2015]]
 
−
 
−
* OSGeo Applications: [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]], [[Google Summer of Code Application 2011|2011]], [[Google Summer of Code Application 2012|2012]], [[Google Summer of Code Application 2013|2013]], [[Google Summer of Code Application 2014|2014]], [[Google Summer of Code Application 2015|2015]]
 
−
 
−
== Guides, FAQ and mentors information ==
 
−
 
−
=== GSoC general information ===
 
−
* [https://developers.google.com/open-source/gsoc/timeline The official timeline]
 
−
* [https://developers.google.com/open-source/gsoc/resources/ Google's FAQ on the program]
 
  
 
== A Mentor's Responsibilities ==
 
== A Mentor's Responsibilities ==
  
−
Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find :). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.
+
Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.
  
−
Every student project will also have a '''backup mentor''', this person should come from your programming team and should at minimum keep up to date with the student's weekly developments. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.
+
Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.
  
 
You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.
 
You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.
  
−
=== Guides for mentors ===
+
== Guides for mentors ==
 +
 
 
* [http://en.flossmanuals.net/GSoCMentoring/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
 
* [http://en.flossmanuals.net/GSoCMentoring/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.
 
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
 
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]
 
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]
 
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]
  
−
<!--
+
== Tips for mentors ==
−
== How to register as a mentor ==
 
  
−
''Please apply to become a mentor today!''
+
This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.
  
−
=== Before starting ===
+
=== Good ideas ===
  
−
Before starting the procedure, be sure that you know what you are committing for: read the [http://en.flossmanuals.net/GSoCMentoring/ mentoring guide], and ask previous years' mentors about their experience. Mentoring is often quite demanding in terms of time and energies, especially if you didn't work with the student before. If you are aware of that, proceed with the registration.
+
* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable. Think to a task much earlier to the timeline, and connect the task to the idea in the ideas page.
 +
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.
 +
* ...
  
−
=== Procedure ===
+
=== Bad ideas ===
  
−
* Sign up to the [http://lists.osgeo.org/mailman/listinfo/soc '''OSGeo SoC mailing list'''].
+
* ...
−
* Introduce yourself on soc@lists.osgeo.org, mentioning the project you want to/can mentor for, the area(s) of interest, more about yourself, etc.
 
−
* If you don't have a '''linkID''' from past years, register yourself [http://www.google-melange.com/ at the Melange site] to obtain it.
 
−
* '''Apply to become a mentor in Melange''':
 
−
:Go to [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 Melange homepage]. At the bottom of the page go to where it says "Mentors & Administrators Registration with participating organizations is now open." and if you had registered as a mentor last year(s) login with your old user ID (aka "link_id"), or register as a new mentor. Click the appropriate button and follow the procedure to create the profile, or update your existing one.
 
−
:As the box on the profile page tells you that profile is saved, follow the link "Start connection". Pick up OSGeo from the list of accepted organisations, or follow this [http://www.google-melange.com/gsoc/connection/pick/google/gsoc2015 link] to the accepted organisations. Select OSGeo: you will be redirected to the mentor connection form.
 
−
:Fill up the request form '''indicating in the message for GSoC admins''':
 
−
#your '''name''' and '''surname''';
 
−
#your '''project''';
 
−
#the name of the '''idea(s)''' you are mentoring;
 
−
#an '''email''' address (Google account) that you wish to use with communication with the mentoring organization. Such data will be kept private and only handled by GSoC admins.
 
−
#A plus is a '''link''' to a mail on public mailing lists, that show that communication with the prospective student has started.
 
−
* Wait for administrator's approval. Mentors will be approved after students' application period opens. Until approval, your dashboard will be empty.
 
−
* Once you've been accepted, you can go to your dashboard (link on left sidebar) and browse the list of student applications.
 
−
* Accepted mentors will be invited to the [https://groups.google.com/group/osgeo-gsoc-mentors?hl=en osgeo-gsoc-mentors] mailing list.
 
  
−
'''Note''': "Google will provide a total stipend of 6000 USD per accepted student developer, of which 5500 USD goes to the student and 500 USD goes to the mentoring organization." As previous years, OSGeo will use these money to fund community projects, such as code sprints and other initiatives.
+
== Learn more ==
  
−
-->
+
* Previous years SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://www.google-melange.com/gsoc/org/google/gsoc2009/osgeo 2009], [http://www.google-melange.com/gsoc/org/google/gsoc2010/osgeo 2010], [http://www.google-melange.com/gsoc/org/google/gsoc2011/osgeo 2011], [http://www.google-melange.com/gsoc/org/google/gsoc2012/osgeo 2012], [http://www.google-melange.com/gsoc/org/google/gsoc2013/osgeo 2013], [https://www.google-melange.com/gsoc/org2/google/gsoc2015/osgeo 2015]
−
<!--
 
−
== Project Mentors ==
 
  
−
{| class="wikitable sortable" border="1" style="margin: 1em auto 1em auto; text-align:left"
+
* OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]], [[Google Summer of Code 2011|2011]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2014|2014]], [[Google Summer of Code 2015|2015]]
−
| align="center" style="background:#f0f0f0;"|'''Mentor'''
 
−
| align="center" style="background:#f0f0f0;"|'''Project'''
 
−
|-
 
−
| --||GDAL
 
−
|-
 
−
| --||GeoServer
 
−
|-
 
−
| --||GRASS
 
−
|-
 
−
| --||gvSIG
 
−
|-
 
−
| --||[http://www.spatialytics.org Spatialytics]
 
−
|-
 
−
| --||Mapbender
 
−
|-
 
−
| --||Mapserver
 
−
|-
 
−
| --||OpenJUMP/deegree
 
−
|-
 
−
| --||[[OpenRouter]]
 
−
|-
 
−
| --||OSSIM
 
−
|-
 
−
| --||QGIS
 
−
|-
 
−
| --||uDig
 
−
|-
 
−
| [mailto:bontepaarden@gmail.com Paul Meems]<br>[mailto:amesdani@isu.edu Dan Ames]||[http://www.mapwindow.org/wiki/index.php/Google_Summer_of_Code MapWindow GIS]
 
−
|}
 
−
-->
 
−
 
 
−
<!--
 
−
= Project Milestones =
 
−
[[Google SoC Project Milestones 2012]] - todo
 
−
-->
 
−
 
 
−
<!--
 
−
= Project Pages =
 
−
Each accepted Soc Project should be listed here, and the page should be updated with information about the progress of the project.
 
  
−
<strike>The list of proposals can be found here: [[Google Summer of Code 2012 Ranking]]</strike>
+
* OSGeo Applications: [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]], [[Google Summer of Code Application 2011|2011]], [[Google Summer of Code Application 2012|2012]], [[Google Summer of Code Application 2013|2013]], [[Google Summer of Code Application 2014|2014]], [[Google Summer of Code Application 2015|2015]], [[Google Summer of Code Application 2016|2016]]  
−
-->
 
  
  
 
[[Category: Google Summer of Code]]
 
[[Category: Google Summer of Code]]

Latest revision as of 00:11, 19 April 2016

GSoC2016Logo.jpg @ OSGeo 300 127 pixel.png

This is the central page for OSGeo administrative information in Google Summer of Code 2016.

GSoC general information

Contacts

  • Margherita Di Leo acts as Administrative contact, with support from Anne Ghisla. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!
  • Would-be mentors and students: you are invited to sign up to the OSGeo SoC mailing list right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!

Mentors

If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:

Number Name Surname Nickname (IRC) email Software community Idea(s) you are available to mentor
1 Margherita Di Leo madi diregola AT gmail DOT com admin at OSGeo Idea I would like to mentor
2 Alexander Bruy alexbruy alexander.bruy AT gmail.com QGIS
3 Victor Olaya volaya volayaf AT gmail DOT com QGIS
4 Daniel Kastl dkastl daniel AT georepublic DOT de pgRouting
5 Massimiliano Cannata maxi massimiliano.cannata AT gmail DOT com istSOS
6 Milan Antonovic milan milan.antonovic AT gmail DOT com istSOS
7 Jachym Cepicky jachym jachym.cepicky AT gmail PyWPS
8 Andrea Antonello moovida andrea.antonello AT gmail DOT com JGrasstools, gvSIG, Geopaparazzi
9 Rashad Kanavath rashadkm rashadkm AT gmail DOT com GRASS GIS, OSSIM, GDAL
10 Cameron Shorter CameronShorter cameronDOTs h o r ter AT gmail com OSGeo-Live
11 Stephen Woodbridge woodbri woodbri AT swoodbridge DOT com pgRouting
12 Vicky Vergara cvvergara vicky AT georepublic DOT de pgRouting
13 Dmitry Baryshnikov bishop bishop.dev AT gmail.com GDAL
14 Luca Delucchi lucadelu lucadeluge AT gmail.com GRASS GIS
15 Anna Petrasova kratochanna AT gmail.com GRASS GIS
16 Stefan Steiniger sstein AT geo.uzh.ch OneBusAway, OpenTripPlanner, OpenJUMP for OneBusAway see here
17 Sean Barbeau barbeau AT cutr.usf.edu OneBusAway, OpenTripPlanner for OneBusAway see here, also there are ideas around for OpenTripPlanner Android App, and the GTFS-RT Validator
18 Riccardo Rigon abouthydrology rccrd.rgn AT gmail DOT com JGrasstools, gvSIG, Geopaparazzi
19 Vaclav Petras wenzeslaus AT gmail.com GRASS GIS
20 Oliver May oliver AT dfc DOT be Geomajas, leaflet, openlayers, geoserver, geotools
21 Even Rouault even dot rouault AT spatialys dot com GDAL
22 Alexandre Dubé adube AT mapgears dot com OL3-Google-Maps
23 Moritz Lennert mlennert AT club dot worldonline dot be GRASS GIS
24 Roberto Marzocchi roberto dot marzocchi AT gmail dot com dot GRASS GIS
25 Brian M Hamlin darkblue_b maplabs AT light42 DOT com SciPy geospatial stack, PostGIS, gdal 2.0
26 Jessica Lapointe jlapointe AT mapgears dot com OL3-Google-Maps
27 Gérald Fenoy djay gerald.fenoy AT geolabs.fr ZOO-Project
28 Massimo Di Stefano epifanio epiesasha AT me DOT com GRASS GIS webgrass
29 Patrick Hogan patrick.hogan AT nasa DOT gov NASA World Wind
30 Oscar Kramer oscarkramer AT yahoo DOT com OSSIM
31 Jakub Balhar jakub AT balhar DOT net NASA World Wind
32 Jonas Eberle jonas.eberle AT gmx DOT de PyWPS
33 Martin Landa landa.martin AT gmail DOT com GRASS GIS
34 Rob Emanuele lossyrob rdemanuele AT gmail DOT com GDAL
35 Anita Graser anitagraser AT gmx DOT at QGIS
36 Giustino Tonon giustino.tonon AT unibz DOT it JGrasstools
37 Alessandro Pasotti apasotti AT gmail DOT com QGIS QGIS Symbology Repository
38 David Burken dburken AT gmail DOT com OSSIM
39 Óg Crudden og.crudden AT gmail.com OneBusAway see here
40 Markus Neteler neteler AT osgeo DOT org GRASS GIS
41 Joaquin del Cerro jjdelcerro AT gvsig DOT com gvSIG
42 Óscar Mártinez masquesig AT gmail DOT com gvSIG
43 Mirko Cardoso mirko cardoso.mirko AT gmail DOT com istSOS

A Mentor's Responsibilities

Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really is in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.

Every student project will also have a backup mentor, this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. Both mentors need to appoint themselves officially. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.

You must be available at some time during the midterm and final evaluation period. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations must be filed within these dates.

Guides for mentors

Tips for mentors

This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.

Good ideas

  • Test students before selection. Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable. Think to a task much earlier to the timeline, and connect the task to the idea in the ideas page.
  • Time management tip: Try not to mentor more than one project per year. In any case, you can be primary mentor only for one project. Consider carefully the time that you can allocate on GSoC.
  • ...

Bad ideas

  • ...

Learn more

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