This generic parts of this page have been updated and moved to the Community Dev website, the parts about GSoC selection process need to be moved to the GSoC section of the ComDev site
All ASF projects are invited to submit their ideas to the SummerOfCode2009 page. Any Apache member and experienced committers can submit ideas using the template on that page. We are looking for as many interesting projects as we can come up with.
ASF Members and committers can volunteer to mentor or co-mentor proposals. Please co-ordinate with existing mentors for proposals before adding your name there. When in doubt about all this, contact code-awards at apache.org (mentors are welcome to subscribe to that list anyway).
Please don't add proposals for which there are no (prospective) Apache mentors available. Please don't add proposals if you have no idea what would be a good proposal.
Interest, even by a qualified student, does not mean that any of those project will automatically go ahead. Depending on the number of projects; the number of people able to mentor and the timing we will probably have to make a smaller selection.
Please subscribe to the email@example.com mailing list to coordinate work between mentors.
Subscriptions to that list will only be accepted from addresses known to belong to ASF committers, so please use your @apache.org address to subscribe if possible, or at least an address that can be matched to your @apache.org address via the ASF's private/committers/info or private/committers/MailAlias.txt data.
How much effort is involved with being a mentor
Most mentors I have spoken to spend between 3 and 5 hours per week with their students. Most of this time is spent encouraging them.
Within the ASF we like to think that the whole project community will help the student just as they would with any other community member. If your project is supportive in this way then you may be able to get away with less time. However, as mentor you are responsible for evaluating the student and helping them deliver on their commitments.
The [GSoC Mentoring Guide|http://en.flossmanuals.net/GSoCMentoringGuide] has much more guidance for mentors.
The Selection Process
A note about eligibility
If your project has any restrictions on who can participate (as is the case with Harmony for example) please be sure to clarify these with potential students as early as possible. It causes unnecessary confusion and dissapointment if a student is awarded a slot but is later found to be ineligible. Don't rely on the fact that the student should have read details on the project web site. You must discuss their eligibility before offering to mentor them. Please also make a note in the webapp stating that you have, as far as possible, confirmed the student is eligble to contribute.
Below is a timeline of events appropriate to mentors. Google maintain a complete timeline.
March 18th - Students start engaging with project to discuss applications
March 23th - students are able to submit applications to the GSoC webapp.
April 3rd - Deadline for student applications
Google provide a spiffy webapp (powered by Melange) for ranking project proposals and applications. We use this to allow interested parties to rank applications. There is a useful guide for using the webapp.
April 4th - internal ranking commences (how this is done will be put here and announced on firstname.lastname@example.org)
April 14th - Internal RankingProcess ends
April 15th - GSoC admins* complete the resolution of any clashes in ranking, as described in the RankingProcess (this can happen internally, between mentors, and external between organizations)
April 20st - Google announces Accepted proposals and start notifying students
GSoC coding starts on May 23th, the interim period is the "Community Bonding" period.
The period between April 20th and the start of the programming (May 23th) is intended to be a period of community bonding. this is a period in which students get to know mentors, read documentation, get up to speed to begin working on their projects.
Past experience has shown that this period is very important. Creating a good relationship with your student in this time, when there is no pressure of performance, appears to be key to having a successful student.
May 23th Students begin coding for their GSoC projects
July 6th Mid term evaluations commence
August 17th Pencils down (there is actually a week to do some final polishing but this work does not count to the final evaluaton)
August 24th Final evaluations deadline
* GSoC admins are currently Luciano Resende, Ross Gardler and Bertrand Delacretaz