Four Steps to Google SoC, With a Degree
Google Summer of Code is a program organized by Carol Smith at Google to fund students working on open source projects during the summer. Students from all over the world are attracted by the Google name, be they at the undergraduate or graduate level, so the admission process is somewhat competitive and quite strategic.
Step #1: Choose an organization.
Two possibilities here. You can either choose it based on who they are and your affinity for what they do, or based on the projects they offer and the kind of skills they require. The first option may require you to learn new skills on the spot for the application, while the second only needs you to get familiar with the organization.
My organization, the Privly Foundation, “makes it possible for you to control your data after posting it across the internet. You can post to Facebook without allowing Facebook access to your communications, you can even unsend emails.” I chose it because their mission is great, and because their project ideas list had an iOS app, which is my specialty.
It is also good to know that organizations that have previously participated to GSoC receive many more slots than new organizations. For example, KDE receives about 60 slots every year, while the organization I applied to is new and received only 2 slots. It means that if you choose a big organization, you will be competing for more slots, but there will be more applicants as well. I haven’t done the math, but the ratios of submitted proposals per slot should be similar.
Step #2: Choose a project.
If you chose your organization carefully, you’ve done a significant part of the work already. The same strategy applies to choosing your project. You can either choose it based on what it consists in or based on the skills it requires. Again, the first option may require you to pick up new skills in the little time you have to write your proposal, while the second one may only require you to get familiar with the project. You may be wondering why it is important to have the skills before the application deadline if you are not going to code before then, and the reason is that organizations want applicants to fix bugs or submit patches related to the selected projects, so that they know you can get up to speed quickly to start coding and that you have the required skills.
Step #3: Write a proposal and contact your organization.
Most organizations have a proposal templates with questions you must answer. Some of these templates are extensively long, while others are shorter. Make sure you look at the template early to see what kind of information you need to provide and how long it will take you to write your proposal. In general, the more specific and accurate your proposal is, the higher the chances of it getting accepted are. Additionally, I am quite certain that writing well plays a part too.
Note that while you are writing it, it is highly recommended to get in touch with your organization. Get to know your prospective mentor by following and posting in the mailing list and hanging out in the IRC channel. It should also increase your chances of getting selected.
Step #4: Wait.
There is a lot of waiting in the GSoC application process. Don’t ask your mentors whether they accepted you or not, because they’re not allowed to say it and will not say it. And as GSoC bot would say,
“patience” is very important for GSoC/GCI. Relax and go code something useful.
FAQ:
Q: I am not a student, can I still apply to Google Summer of Code?
A: Unfortunately, GSoC is only open to students. I heard, however, that this company called Google is hiring, and that they’re almost as cool as GSoC.
