Summer of Code / 2015 - Python Wiki
Python Wiki Python Wiki / Python Wiki / Summer of Code / Summer of Code / Summer of Code / 2015 View as Markdown Summer of Code / 2015 ¶ Legacy Wiki Page This page was migrated from the old MoinMoin-based wiki. Information may be outdated or no longer applicable. For current documentation, see python.org . Google Summer of Code 2015 @ the Python Software Foundation ¶ Google Summer of Code is a global program that offers post-secondary students an opportunity to be paid for contributing to an open source project over a three month period.
Since 2005, the Python Software Foundation has served as as an “umbrella organization” to a variety of python-related projects, as well as sponsoring projects related to the development of the Python language. It is our intention to apply as a mentoring organization again in 2015, and this page coordinates those efforts. The 2015 PSF GSoC coordinator is TerriOda . (terri on Freenode IRC, terrioda at gmail.com) The other org admins include James Lopeman (meflin on IRC) and Florian Fuchs (florianf on IRC), Kushal Das (kushal on IRC) and Stephen Turnbull (yaseppochi on IRC) More org admins may be announced later.
If you’re interested in volunteering, contact Terri. Mailing lists, IRC, and other ways to get in touch ¶ Before you get in touch, you might want to read… The GSoC Student Guide , which includes a lot of really useful information and tips for prospective GSoC students, including a page on making first contact with prospective mentors . The Python GSoC FAQ: SummerOfCode/FrequentlyAskedQuestions Mailing list: soc2015-general @ python . org sign up here before posting This mailing list is open to students, mentors and other interested community members This is your first place to ask questions related to summer of code with Python!
IRC: #python-gsoc on irc.freenode.net . If you don’t have an IRC client set up, you can use this link to open a web chat client Org admins: 99.9% of the time, students should email soc2015-general @ python . org with questions (it reaches more people so you get an answer faster) Mentors and sub-org admins can email all the Python org admins all at once using the mail alias soc2015-general-owner(at)python.org to get more information about the program and get signed up.
Please note that Python has a Community Code of Conduct and mentors and students working with the PSF are asked to abide by it as members of the Python community. 2015 Application Template / How do I Apply? ¶ Short application checklist: Read this this wiki page – All of it! we’ve tried to give you all the information you need to be an awesome student applicant. Choose a sub-org (there’s a list below) Talk to your prospective mentors about what they expect of student applicants and get help from them to refine your project ideas.
Listening to your mentors’ recommendations is very important at this stage! Prepare a patch for that sub-org Set up a blog where you will keep track of your GSoC progress Write your application (with help from your mentors!) Template: SummerOfCode/ApplicationTemplate2015 Submit your application in Google Melange before the deadline Only applications submitted in Google melange before 1900 UTC March 27, 2015 can be considered.
Note that you need to register for melange and submit eligibility paperwork before you’ll be able to submit the your application. Python Application Template ¶ The 2015 Summer of Code Application Template for the Python Software Foundation is here: SummerOfCode/ApplicationTemplate2015 Please discuss the application with your prospective mentors, as they may prefer a slightly different template. They are also your greatest resource for making the best possible application, so ask for feedback and work with them if they suggest modifications!
Remember, the best proposals are *collaborative* works between the student and mentors. This is not like a final exam! Google Melange ¶ All applications MUST be submitted through the Google Melange System, here http://www.google-melange.com/gsoc/homepage/google/gsoc2015 You will need to set up an account and submit eligibility paperwork before you will be able to see the submission form. Only applications submitted in Google melange before 1900 UTC March 27, 2015 can be considered.
You can edit your application up until that deadline, so we recommend you submit something ASAP and then modify it as you get feedback from your mentors. Preparing for GSoC 2015 ¶ Please note the Dates and deadlines for 2015 . There should be a complete list of Python sub-orgs around March 17th. Students ¶ All prospective students are required to have completed the following to pass final screening: Demonstrate to your prospective mentor(s) that you are able to complete the project you’ve proposed Blog for their GSoC project.
You’ll be required to do this every 2 weeks throughout the GSoC period, because it helps us share your progress with the broader community, and it also helps the org admins get a sense of how you’re doing. Contribute at least one patch to the project(s) you’re applying to work with Here’s 7 steps to help you get started: Choose an organization to work with. Python has a lot of sub-projects (over 20 in 2014!), so this can be hard.
See “ How do I choose a project or a sub-org? ” if you need help. You can try out the next steps with more than one org and make your decision once you get to know them, too! Start communicating with the developers. Join the mailing list, IRC channel, or any other communication channels the developers use. Listen, get to know the people involved, and ask questions. If you want to make the best first impression, DO NOT start emails with “Dear Sir.” Python has many mentors who are female and/or prefer other forms of address.
Try “Dear developers” or “Dear mentors” if you’re sending a general email, or use whatever name they use on their email if you’re addressing a specific person. Culturally speaking, first names or chosen nicknames are fine for most open source projects. Set up your own development environment. Find some beginner-friendly bugs and try to fix them. Many projects have these tagged as “easy” “bite-size” or “beginner-friendly” Note that if you apply as a student with the PSF you will be asked to submit a code sample, generally code related to your project.
A few fixed bugs with code accepted upstream will make your application look great! Having trouble figuring out which bugs are beginner-friendly? Send an email to the project mailing list saying something like “Hi, I’m a student developer interested in getting some open source experience and I was wondering if anyone could suggest some bugs that are suitable for a beginner in this project?” Some projects have beginner-friendly “bite-sized” bugs listed in the OpenHatch search engine, found here: http://openhatch.org/search/ Find bugs and report them.
Hopefully you won’t encounter too many, but it’s always a good idea to get familiar with your project’s bug reporting process. Help with documentation. As a beginner in your project, you’re going to see things that are confusing that more experienced developers may not notice. Take advantage of your beginner mindset and make sure to document anything you think is missing! Help others. This is a great idea for a lot of reasons: explaining things can help you learn them better, demonstrating your skills as a good community member can make you more memorable when your mentors have to choose candidates, and being helpful makes your community a better place!
Not sure which projects will be participating in 2015? Well, neither are we! Many orgs won’t decide until they can get commitment from mentors, and often mentors don’t know their schedules until closer to the start of the GSoC period. But you can take a look at the list of organizations who participated in 2014 or previous years to get an idea of what projects mig
The rest of this page is on the live site.