Python Software Foundation

2015 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. (And yes, you should discuss your proposal with mentors and get their help to improve it!) You can make changes in Melange up until the final deadline on March 27, 2015 19:00 UTC (note the time and time zone). 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.

It is also recommended that you discuss your proposal with your prospective mentors before the deadline. They are allowed (and encouraged!) to help you make the best possible proposal.

Sub-organization information

You must also put your sub-org information in the title of your proposal, as it makes it easier for mentors to find proposals for their sub-orgs in the melange system.

Student Information

University Information

Project Proposal Information

Other Schedule Information

Sub-organization specific information

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.

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 respective sub-organizations mailing lists. The mailing list for each sub-org is listed here: SummerOfCode/2015. 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.

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 soc2015-general@python.org mailing list. You should sign up here before you post: http://mail.python.org/mailman/listinfo/soc2015-general/ If you absolutely need to get in touch with the Python org admins, you can do so using the mail alias soc2015-general-owner@python.org

SummerOfCode/ApplicationTemplate2015 (last edited 2015-03-16 09:58:56 by TerriOda)

Unable to edit the page? See the FrontPage for instructions.