Cracking Google Summer of Code 101
Google Summer of Code or famously known as “GSoC” is an initiative by Google to enhance the Open Source culture and projects. Open source softwares are at the core of every thing related to computer science. If you are a computer science student and are not using any open source tool/application/software/framework/platform/library and language then there’s something really wrong with you.
Even though the importance of open source projects being gigantic, most of this projects are made out of hobby or fun by their respective project leads, and as there is no direct incentive of monetization of this projects and they lack the pace of development like proprietary or enterprise softwares. To eradicate this, every year Google organizes the GSoC under-which the potential(which have better impact and use-case) open source projects and students work for enhancing the projects.
As you can see, its a great initiative where you being a student contribute to some great project which actually enhances people’s lives, productivity, pace of invention and makes this world a better place. LOL !
Note : Do yourself a favor and watch Silicon Valley and Mr.Robot if you haven’t already.
Every year thousands of student apply for GSoC from around the world and only nearly a thousand student(1, 264 in 2018) get accepted. Lots of Competition. There wasn’t any proper guide when last time I checked which elaborates on how to properly apply and maximize the chance of acceptance. As I have completed GSoC 2018 successfully, I have some insights to share.
If you are planning to apply for GSoC or don’t have anything productive to do right now, Read along 🙂
- Proper knowledge of any VCS(Version Control System).
Mostly projects use git as their primary VCS and Github or Bitbucket as their VCS hosting service, so I would recommend learning Git and collaboration on Github.
- Any one of the following language :
Projects which use other languages are also present but for a fresher this are the easy and mandatory ones to know. Also if you know more languages you will have more options to choose from.
- Couple of relevant personal open sourced projects (not mandatory, but why not ?)
- Hunger for knowledge
- Before even thinking about applying to GSoC you should be using atleast some open source software and must have interest in some sub-field (Machine/Deep learning, Artificial Intelligence, Algorithms–DS, Operating Systems, Database Systems, Networking, Security, Development etc.) of computer science. The below preparation must start before 2-3 months of official GSoC start date.
- Head over to previous year’s GSoC Archives (These projects are most likely to come again) and search for the project/organization you would like to contribute to according to your interest.
- Use the software as normal user is supposed to and enumerate each and every way of using it.
- Align your learning of tech stack and knowledge as required for that project or preferably choose the one that aligns with yours.
- Head over to that project’s source code repository, setup the Dev-environment, read the docs and other relevant terial extensively.
- Get totally familiar with source code(will be intimidating at first but can get really easy if you do second step thoroughly).
- Contact the project lead/Community on given communication channel, ask them doubts, bugs to fix, feature enhancements etc.
- Ask them to assign any task to you and Start Contributing.
After selected organizations get announced(mostly in month of February) and if your selected projects and organizations are there then no worries as at this point of time you would have contributed much to the project. If they aren’t then start the preparation for the selected ones again.
Applying to GSoC consists of writing a detailed proposal of your project which highlights the purpose of project, each and every enhancement you will add during coding phase of GSoC and reasons that make you fit for the project. This needs not to be in some formal format but also should not be very informal. Proposal writing can be daunting and hard if you have not done the proper preparation as mentioned above and will not reflect the experience. This will lead to project rejection very easily. In my case the application phase of GSoC was just a formality because I had contributed and had bonded with the community of my project in a very good way. Also there aren’t many successful proposal templates shared openly. If you are not able to decide the structure of your proposal, you can have a look at mine here.
Learnings during GSoC can vary person to person depending on their prior experience. But for me the learning and experience gain curve was very steep. The software development concepts like Test writing, Collaborated development, working with large code-bases, Maintainable coding etc. are not just concepts for me anymore as I had thorough hands-on. Also the computer science/technology concepts on which your project is based on will become your expertise. 😉
Mention of successful completion of Google Summer of Code on your resume depicts that you know how to work on code-bases of softwares which have actual user bases unlike the personal projects. GSoC is much more prestigious than internship in any low tier startup/company. So I would recommend to students of freshmen and sophomore year to apply for GSoC. Its a win-win situation for everybody involved. Students get valuable experience and hefty stipend. Open Source projects get enhanced. Google’s incentive of making this world a better place LOL X) gets completed.
If you haven’t already read my GSoC project report, read it here.
Hope you picked up some tips.. Keep Contributing, Keep Hacking !!!
Signing off..Shoeb Patel a.k.a. CaptainFreak