- (it's good to provide multiple email addresses; specify use cases such as "preferred", "emergency", "rarely checked". A "rarely checked" address is useful only if it's easy to find.)
- Time zone(*):
- IRC handle including network:
- Source control username(s)(Launchpad, Github, ...):
- Instant Messaging information:
- Any other ways we can reach you:
- Home Page(s):
Note: Blogging about your progress for GSoC will be required. You will need to blog every 2 weeks. If you do not yet have a blog or want to have one specifically for GSoC, please set one up via a service like http://blogger.com before submitting your application.
- Current Year and Expected Graduation date(*):
- Degree(*) (e.g. BSc, PhD):
Other personal information you think we would find relevant:
Project Proposal Information
- Proposal Title (*)
- The name of your proposal. This should explain in a few words what you plan to do."
- Proposal Abstract (*)
- A short description of your proposed project
- Proposal Detailed Description/Timeline (*)
Please include a timeline with milestones, preferably weekly ones. You may wish to read the GSoC student guide which includes several examples of good proposals with timelines, or our own information at SummerOfCode/Application.
Note that any pre-work such as setup and reading documentation should take place during the community bonding period (April 27-May 24). Students will be expected to start producing code starting on May 25th.
Link to a patch/code sample, preferably one you have submitted before (*)
Note: We require all students to submit a patch. This does not need to be accepted and merged, but it does need to be online and available for potential mentors to inspect. Contact your mentors if you are unsure what would be an appropriate patch to submit.
Links to additional information (e.g. other projects, resources, code you've written, relevant information. You may wish to include a link to your resume here to help mentors evaluate your experience level.)
Other Schedule Information
Please indicate any vacations or other time off that you may be taking or expecting to take over the course of the summer. Any time that you would not be expecting to work should be noted here, along with a reason. (e.g. "June 12-15th, travel for my sister's wedding" "May 30, midterm exam") Google expects you to work 40h/week for the entire GSoC period, so consider how you will make up any lost time (you may have to start coding during community bonding, for example).
- Note: We don't penalize students for needing adjustments to schedule if they're up-front about them and have a plan to mitigate any issues. However, we *have* failed students for lying about their availability and subsequently falling behind in their work. Be honest!
- Please indicate any other commitments you have that you think we should know about. (e.g. part time-jobs, large volunteer projects, summer courses)
- Have you applied with any other organizations? If so, do you have a preferred project/org? (This will help us in the event that more than one organization decides they wish to accept your proposal.)
Notes for submitting a proposal
The information requested above is generally required for us to be able to contact you and evaluate your proposal. Please feel free to add information to this template and to format it in whatever way you think will be most effective in conveying your intentions.
We strongly recommend that you join our IRC channel (#mailman on freenode.net) and mailing list (email@example.com) to learn more about the community. You may wish to get your prospective mentors to read your proposals in advance so they can help you refine them.
Students should be contacting the mentors and the sub-organizations about projects and proposals. It is ultimately the mentors for each project who select students, so they are your most valuable resource for what constitutes a great proposal.
Mentors are often available on IRC, as well as the mailing list. As a reciprocal courtesy students are expected to also be regularly available on IRC and/or available via e-mail and reasonably responsive to questions and requests for improvements. Students are encouraged to help other students with proposals and help answer questions in IRC or the mailing lists.