GSoC/Application

GSoC Project proposal guidelines

Requirements

• Applicants meet Google's requirements for participation in Summer of Code.
• Applicants are in regular and close contact with their mentors and the community (IRC).
• Applicants know their target programming language.
• Applicants have successfully upstream'd a simple patch to demonstrate they know the process.
• Applicants are willing to blog (or use social media) weekly and interact with the community (failure to do so will result in a fail at the next review)

Proposal Outline

• Name and Contact Information
• Title
• A short summary.
• Benefits to the Community.
• Deliverables. Give a brief, clear work breakdown structure with milestones and deadlines.
• Biographical Information:
  • Summarize your education, work, and open source experience.
  • List your skills and give evidence of your qualifications.
  • Please list any non-Summer-of-Code plans you have for the Summer, especially employment and class-taking. Be specific about schedules and time commitments.

General Notes

Your proposal should be around 1500-4000 words in plain text and should clearly state what you intend to do and the necessary steps to get there. There is no limit on the number of submitted proposals, if you have several ideas, please submit several proposals. Do include URLs pointing to information that would help convince us of your chances of success: preliminary project plans or progress, other projects you've been involved with that were successful, code samples, etc.

It is better if your project is under-scoped and sure to complete; as opposed to a largish project which may not get done.

See GSoC for project ideas.