Google Summer of Code 2012 Administrative
- Back to the main OSGeo Google Summer of Code 2012 @ OSGeo wiki page.
This is the central page for OSGeo administrative information in Google Summer of Code 2012.
- 1 Contacts
- 2 2012
- 3 Previous years
- 4 Guides, FAQ and mentors information
- 5 How to register as a mentor
- 6 Slot assignments
- 7 Accepted students
- Anne Ghisla will act as Administrative contact, with support from Hamish Bowman, Dustan Adkins, and Wolf Bergenheim. 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 mailinglist right now. 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.
- OSGeo Google Summer of Code Application 2012
- The 2012 OSGeo home at Melange is http://www.google-melange.com/gsoc/org/show/google/gsoc2012/osgeo
- SoC involvement: 2008, 2009, 2010, 2011
- There is a 2011 version of the OSGeo SoC flyer to look at and post in appropriate places. (TODO: update to 2012)
- OSGeo GSoC wiki pages: 2008, 2009, 2010, 2011
- OSGeo Applications: 2009, 2010, 2011)
Guides, FAQ and mentors information
GSoC general information: timeline, program site, FAQ
- The official timeline
- The official Google Summer of Code 2012 program site
- Google's FAQ on the program
- There is also a Google Wiki page about the program
Guides for mentors
- The GSoC Mentoring Guide -- READ THIS eBOOK
- Same thing, different colors
- Mentoring HOWTO
- Advice for Mentors from the Google Wiki
Melange guides and issue tracker
How to register as a mentor
Please apply to become a mentor today!
The registration procedure requires you to visit three sites:
- OSGeo soc mailing list
- Google Melange soc site
- a Google form for OSGeo mentor registration
Some of the steps are optional (you can be already registered to soc list, and/or have a linkID in Melange from past years). The only step that actually enables you to be an official mentor is the last one, the Melange request. The other steps ensure that we will accept only people interested in mentoring OSGeo GSoC, and that meet the mentoring requirements - therefore, we will reject Melange requests that are not supported by appropriate information on contribution to the OSGeo projects.
Here is the complete procedure:
- Read the 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.
- Sign up to the OSGeo SoC mailinglist.
- Present yourself on email@example.com. Here are some suggested topics:
- Project you want to/can mentor for
- Area(s) of interest
- Feel free to tell more about yourself
- If you don't have a linkID from past years, register yourself at the Melange site to obtain it.
- Fill in the Mentor form
- Apply to become a mentor in Melange:
- Go to Melange homepage. Below the picture of happy programmers and the big "Students: apply now" there is a smaller link to apply as mentor. [screenshot?] Click it and follow the procedure to create the profile.
- As the green box on top of profile page tells you that profile is saved, follow the link "You can now apply to Google Summer of Code". Pick up OSGeo from the list of accepted organisations, or follow this direct link.
- Fill up the request form with a short message, referring to the mail you sent on soc mailing list.
- 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 osgeo-gsoc-mentors mailing list.
The procedure is the same as previous years. The 5 stars scoring on Melange is not used.
April 10th - April 17th
Mentors are still able to register in this time frame.
Mentors are invited to make comments in Melange and put forward their willingness to mentor any proposal which they'd take on using the button Wish to Mentor. Admins start assigning the mentors to the proposals, with the Assign mentor function.
Administrators communicate the amazing (minimum) and desired (maximum) number of slots for OSGeo. See Notes on Student Allocations from Google. The deadline for slot request is April 10th, 19:00 UTC.
Each OSGeo project has to decide which (if any) of the applications for their particular project they like, and rank the viable ones. The ranking should be done privately, as Google expects students to know about acceptation only after April 23rd. Usually, a mail exchange among the project's mentors does the job. From 2012 on, the mentors can discuss on the private osgeo-gsoc-mentors list.
A mentor representative for his/her OSGeo project sends the project's ranking and primary mentor selections by private mail to Anne, Wolf and Hamish, or send a summary mail to the private osgeo-gsoc-mentors list.
Google notifies the number of slots assigned to OSGeo.
April 18th - April 20th
Administrators complete the assignment of mentors to the projects they express preference for, and assign the slots using the following procedure: the first proposal from each OSGeo project is selected, then the second, and so forth until all slots are assigned.
Mentor registration deadline: only emergency mentor assignments will be performed in these two days. Appropriate discussion on soc mailing list will support any last minute mentor assignment.
April 20th, 19:00 UTC
Deduplication meeting for admins. As it can happen that a student submits more proposals and gets accepted by multiple organisations, this meeting handles the cases one by one. The involved admins decide which org accepts the student, possibly asking the student about his/her preference. Then, a few slots will be freed, and be reassigned to previously not accepted students.
Accepted students are announced by Google.
|Camilo Polymeris||Victor Olaya||Orfeo Toolbox backend for the Sextante framework in QGIS||QGIS|
|Ramón Carrillo||Marco Bernasocchi||QGIS for Mobile Devices||QGIS|
|Arunmozhi||Martin Dobias||Symbology Usability Improvments for QGIS||QGIS|
|Eugenpaul||Alexander Bruy||Vector Layer Generalization for QGIS||QGIS|
|Pietro Zambelli||Sören Gebbert||Python high level map interaction for GRASS GIS||GRASS GIS|
|Stepan Turek||Martin Landa||GRASS GIS WxGui front end for vector analysis modules||GRASS GIS|
|Eric Momsen||Markus Metz||Image Segmentation in GRASS GIS||GRASS GIS|
|Carlos Sánchez Periñán||Alberto Romeu||adding GPS survey capabilities to gvSIG Mini and shapefile driver||gvSIG|
|Nadal||César Ordiñana||Add tests and educational games support to gvSIG Educa/Batoví||gvSIG|
|Sergio Izquierdo||Nacho Brodín||gvSIG Desktop plugin for change detection from multi-temporal sequence of satellite images using principal component analysis.||gvSIG|
|David Pinheiro||Francisco José Peñarrubia||Solver for the TSP and VRP for gvSIG Desktop||gvSIG|
|Qing Liu||Pierre Racine||Distance Analysis Tools 2012 for PostGIS Raster||PostGIS|
|Jinfu||Daniel Kastl||Integrate a New Shortest Path Algorithm to pgRouting||pgRouting|
|Khondoker Md. Razequl Islam||Steve Woodbridge||Implementation of Bidirectional Search Algorithm for pgRouting||pgRouting|
|Michal Kepka||Tisham Dhar||Geoserver: Publishing hierarchical spatial data in form of dynamically loaded KML||Geoserver|
|Andrea Nascetti||Tisham Dhar (whatnick)||Opticks - Basic SAR Processing Tools: Geocoding and stereo measurement||Opticks|
|Mohit Kumar||Dustan Adkins||Object Based Image Analysis Tools for Opticks||Opticks|
|Himanshu Singh||Nate||Spectral Algorithm Development for Opticks||Opticks|
|Mohammed Rashad||Massimo di Stefano||Complex Image Processing Chain and Under Water Image Processing using pyossim||OSSIM|
|Andrew Migal||Frank Wamerdam||Correlator in GDAL||GDAL|
|Marco Foi||Mauricio Pazos||Porting discontinued Axios Spatial Tools into uDig core 1.3||uDig|
|Carol Hansen||Davide Savazzi||Implementing route analysis of OSM data within uDig, using Neo4j-Spatial graph database||uDig|