Python Software Foundation

2013 Google Summer of Code Proposal Template

NOTE: Things marked with an * are *REQUIRED*. Failure to provide the requested information may result in your application being rejected.

It is HIGHLY RECOMMENDED that you submit your proposal early and make changes as you refine it with your mentors. You can make changes in Melange up until the final deadline on May 3rd. No late proposals will be accepted by Google, even if there is a technical problem with the system, so submit early to avoid problems! You may indicate at the top that the current version is a draft or otherwise let us know if you don't want us to look at it yet.

Sub-organization information

• Sub-organization with whom you hope to work(*):

  (e.g. GNU Mailman, OpenHatch, etc. See SummerOfCode/2013 for the list of valid sub-organizations)

Student Information

• Name(*):
• Email(*):
• Telephone(*):
• IRC handle including network(*):

  • (e.g. valid_nickname_here@irc.network.tld)

• Source control username(s)(*):
  • Provide your user id on Launchpad, Github, Sourceforge, or whatever system your project uses
• IM information:
• Skype:
• Twitter:
• Any other ways we can reach you:
• Home Page(s):
• Blog(s)(*):

  (Note: blogging about your progress for GSoC will be required. 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.)

• Other personal information you think we would find relevant:

University Information

• University(*):
• Major(*):
• Current Year and Expected Graduation date(*):
• Degree(*) (e.g. BSc, PhD):

Project Proposal Information

• Proposal Title (*)

  • (The name of your proposal. This should explain in a few words what you plan to do and include the name of your sub-org. e.g. "Mailman: OpenPGP Integration" or "SunPy: Improvements to Mapcube and Image Registration.")

• Proposal Abstract (*)
  • (A short description of your proposed project)
• Proposal Detailed Description (*)

  • (please include timeline with milestones, preferably weekly ones. You may wish to read http://www.booki.cc/gsocstudentguide/ which includes several examples of good proposals with timelines, or our own information at http://wiki.python.org/moin/SummerOfCode/Application)

• Link to a patch/code sample, preferably one you have submitted to your project (*)
  • (Note: this does not need to be accepted and merged into your project, but it does need to be online and available for potential mentors to inspect.)
• 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. Google expects you to work 40h/week for the entire GSoC period, so consider how you will make up any lost time.

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. You may wish to check with your sub-organization to see if they have any additional requirements.

We strongly recommend that you join the respective IRC channels for the sub-organizations you are applying to, and any relevant development mailing lists to the projects you are interested in working on 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.

*PLEASE DO NOT CONTACT THE GSoC ADMINISTRATORS ABOUT YOUR PROPOSALS* Students should be contacting the mentors and the sub-organizations about projects and proposals. Mentors are often available on IRC, as well as the respective sub-organizations mailing lists. The mailing list for each sub-org is listed here: SummerOfCode/2013. As a reciprocal courtesy students are expected to also be regularly available on IRC and available via e-mail and reasonably responsive to information. Students helping other students with proposals, helping answer questions in IRC or the mailing lists, etc is highly encouraged.

If for any reason you have not been able to find a mentor who can help you with your proposal, or you have a question that you think will be relevant to more than just your sub-organization, you can direct your questions to the soc2013-general@python.org mailing list. You may sign up here: http://mail.python.org/mailman/listinfo/soc2013-general/