Text of wiki.python.org › python › soc › SummerOfCode › 2016.html as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Summer of Code / 2016 - Python Wiki

Python Wiki Python Wiki / Python Wiki / Summer of Code / Summer of Code / Summer of Code / 2016 View as Markdown Summer of Code / 2016 ¶ 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 2016 @ the Python Software Foundation ¶ Python is a popular high-level programming language.

It is a general-purpose language used by scientists, developers, and many others who want to get things done quickly and effectively. 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 an “umbrella organization” to a variety of Python-related projects, as well as sponsoring projects related to the development of the Python language.

Google has generously accepted us as a mentoring organization for the 2016 GSoC season! The 2015 PSF GSoC coordinator is TerriOda . (terri on Freenode IRC, terrioda at gmail.com, but please email gsoc-admins(at)python(dot)org if you wish to contact an admin. Students should almost always email gsoc-general(at)python(dot)org.) The other org admins include James Lopeman (meflin on IRC), Florian Fuchs (florianf on IRC), Kushal Das (kushal on IRC) and Stephen Turnbull (yaseppochi on IRC) Students are now writing code!

You can read their blog posts on the Python GSoC blog aggregator Posts are due on the following days: May 22 June 10 June 24 (midterm) July 8 July 22 Aug 5 Aug 19 (final) Dates and deadlines ¶ Please note the GSoC dates and deadlines . A few dates of note: February 8-19, 2016 . Mentoring org application period. By Feburary 19th, we should have a reasonable selection of sub-orgs and projects listed here. February 29, 2016 .

Mentoring orgs announced. We were selected! hurray! March 7, 2016 . Sub-orgs wishing to participate under the Python Software Foundation umbrella should have sent an email to gsoc-admins(at)python(dot)org by this date indicating interest. March 14-25, 2016 Student application period. April 22, 2016 Accepted students announced. June 25, 2016 Midterm evaluation deadline for PSF mentors, all midterms evals should be in by 1900 UTC. (This is 48h before Google’s deadline to allow us to resolve any issues.

Aug 27, 2016 Final evaluation deadline for PSF mentors, all final evals must be in by 1900 UTC. As with the midterm, this is 48h before Google’s deadline to allow us to resolve any issues. Students ¶ GSoC is basically an open source apprenticeship: students will be paid by Google to work under the guidance of mentors from an open source community. It’s a really great opportunity to build new skills, make connections in your community, get experience working with a larger and often distributed team, learn, and, of course, get paid.

To apply, you need to take a look at the mentoring organizations and the ideas that they are willing to sponsor . Typically, you’ll choose one of their ideas and work with a mentor to create a project proposal that’s good for both you and your chosen open source community. Sometimes, projects are open to new ideas from students, but if you propose something new make especially sure that you work with a mentor to make sure it’s a good fit for your community.

Unsolicited, undiscussed ideas are less likely to get accepted. Note that Python is an “umbrella organization” which means that our team is actually a group of python projects that work together to do Google Summer of Code. If you’re going to apply with us, you’ll need to choose from one of those teams , because that defines which mentors will be helping you with your applications. You can work with more than one sub-org while you’re figuring out what you want to do, but you can only accept one job offer.

Students are expected to work at least 40 hours a week on their GSoC project. This is essentially a full-time job. Ideally, you should not attempt to do another internship, job, or full-time schooling while you’re doing GSoC. Here’s some resources so you can read up more on how to be an awesome student: The GSoC student Guide – New students in particular might want to read the section Am I Good Enough? Google’s list of resources – Note especially the Frequently Asked Questions (FAQ) which does in fact answer 99% of the questions we get on the main GSoC IRC channel.

Python’s SummerOfCode/Expectations also talks about what Python in particular is looking for in its students. Python’s SummerOfCode/FrequentlyAskedQuestions answers the questions that we most often get about Python’s projects. You might want to see How do I choose a project or a sub-org? or How many slots does Python get? Getting Started ¶ Here’s 7 things you can do to get started in free and open source software: Choose an organization to work with.

See “ How do I choose a project or a sub-org? ” if you need help choosing. And don’t forget, you can try working with more than one organization! Experience with *any* open source group will help you prepare for GSoC. Asking mentors to choose your project for you typically leaves a bad first impression. At least try to narrow down your choices a bit on your own! Look through our list of GSoC 2016 sub-orgs . These are currently all the confirmed sub-orgs, although we expect to have more joining us through March 7th. (Last year’s is here SummerOfCode/2015 ) 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” 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. DO ask your question in public. Being able to participate in the open is a signal to developers that you’re ready to participate in open source/free software, so it can improve your chances of being accepted to GSoC. It also means others can benefit from seeing your questions and the answers you get. DON’T Ask to ask. Just get right to the point and ask your question without asking if you’re allowed to ask a question first.

See What does “don’t ask to ask?” mean? for more explanation. Set up your own development environment. This can be a lot of work the first time, so budget time for it, and don’t forget that you’re going to want to run the code you’ve written, so you’ll need some sort of test environment. This is a good time to practice asking good questions and helping improve setup instructions! Find some bugs and try to fix them.

Many projects have bugs tagged as “easy”, “bite-size”, or “beginner-friendly” that will be easier for new contributors. 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! Some projects have beginner-friendly “bite-sized” bugs listed in the OpenHatch search engine, found here: http://openhatch.org/search/ And the OpenHatch team is full of friendly helpful people who don’t mind answering questions!

Having trouble figuring out which bugs are beginner-friendly? Try searching for terms like “easy” in the bug tracker. Or just choose a bug that sounds easy to you and try to get started on it! What’s easy for you may not be easy for others, so take advantage of your own skills and experience where you can. Remember to ask for help if you get stuck for too long, “I’m a new contributor and w

The rest of this page is on the live site.