Google Summer of Code 2013 Administrative

 @


 * Back to the main OSGeo Google Summer of Code 2013 @ OSGeo wiki page.

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

Contacts

 * Anne Ghisla will act as Administrative contact, with support from Hamish Bowman and Dustan Adkins. 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.

2013

 * OSGeo Google Summer of Code Application 2013 (submitted)
 * The 2013 GSoC home at Melange

Previous years

 * SoC involvement: 2008 (link?), 2009, 2010, 2011, 2012


 * There is a 2011 version of the OSGeo SoC flyer to look at and post in appropriate places. (TODO: update to 2013)


 * OSGeo GSoC wiki pages: 2008, 2009, 2010, 2011, 2012


 * OSGeo Applications: 2009, 2010, 2011, 2012

GSoC general information: timeline, program site, FAQ

 * The official timeline
 * The official Google Summer of Code program site
 * Google's FAQ on the program
 * There is also a Google Knowledge Base Wiki about the program

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 programming team and should at minimum keep up to date with the student's weekly developments. Life happens, stuff comes up, we have to be resilient to that. 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. These are July 29: 19:00 UTC - August 2: 19:00 UTC and September 23: 19:00 UTC - September 27: 19:00 UTC. 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

 * 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

 * Melange User's Guide
 * Melange guide for organization administrators
 * Melange issue tracker

How to register as a mentor
HANG OUT, BE PATIENT, WE HAVEN'T EVEN BEEN ACCEPTED INTO THIS YEAR'S PROGRAM YET

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:


 * 1) 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.
 * 2) Sign up to the OSGeo SoC mailinglist.
 * 3) Present yourself on soc@lists.osgeo.org. Here are some suggested topics:
 * 4) * Project you want to/can mentor for
 * 5) * Area(s) of interest
 * 6) * Feel free to tell more about yourself
 * 7) If you don't have a linkID from past years, register yourself at the Melange site to obtain it.
 * 8) Fill in the Mentor form -- still needs to be updated for 2013
 * 9) Apply to become a mentor in Melange:
 * 10) * 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.
 * 11) * 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 . (''we haven't been accepted yet...)
 * 12) * Fill up the request form with a short message, referring to the mail you sent on soc mailing list.
 * 13) * Wait for administrator's approval. Mentors will be approved after students' application period opens. Until approval, your dashboard will be empty.
 * 14) * Once you've been accepted, you can go to your dashboard (link on left sidebar) and browse the list of student applications.
 * 15) Accepted mentors will be invited to the osgeo-gsoc-mentors mailing list.

Slot assignments
The procedure is the same as previous years. The 5 stars scoring on Melange is not used.

April 8th - May 3rd
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 May 6th.

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 May 27th. Usually, a mail exchange among the project's mentors does the job. From 2012 on, OSGeo 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, Hamish, Dustan, or send a summary mail to the private osgeo-gsoc-mentors list.

May 8th
Google notifies the number of slots assigned to OSGeo.

May 22nd - May 24th
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.

May 24th

 * 0700 UTC: All mentors must be signed up and all student proposals matched with a mentor; Student acceptance choice deadline.


 * 1900 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.

May 27
Accepted students are announced by Google.