Google Summer of Code - Newbie thoughts

google summer of code 2017 logo



Google Summer of Code is a global program focused on bringing more student developers into open source software development. Students work with an open source organization on a 3 month programming project during their break from school. In this post I thought of giving you some information on my experience about getting selected in Google Summer of Code.

Brand yourself


Build your brand


To get accepted in summer of code , a good proposal is not enough.You have to interact with the community and convince the people in the society that you are capable of doing things.One thing you can do is blogging.Through your blog you can share the knowledge that you have gained through your researches on the selected product of the company.(Apache,WSo2 etc..) .In the blog you can also include the personal ideas about the product and the errors occurred during your research.You may think that they are not very useful.But actually they are the most important information to an open source company so that they can fix the errors and add enhancements to the products according to the suggestions given by the users.

Get familiar with the project

Get familiar with the project


One of the most important things when doing summer of code is that having a good understanding about the project.Without having a clear vision on the project you will not be able to prepare a good proposal.To achieve this you need to communicate with the mentors first.After they provide you with the necessary resources you have to first try the products on your own.(WSo2 ESB,Apache BloodHound etc).When you meet with the problems you should update the relevant mailing lists with them and get solutions immediately so you can continue without any confusions.

Mentors know things better than us




Mentors are the top contributors of a project. So whatever the projects you've selected the mentors assigned to those projects know things better than you.Therefore you have to respect their ideas and clarify your own thoughts with their opinions.There's no problem with presenting your ideas to the project but you should always obey the ideas provide by the mentors and if you can synchronize their opinions with yours then you are one step closer to getting accepted in the program.

Writing the proposal

The main points need to include in your proposal can be summarize as follows.

1. Introduction
2. Problem Statement
3. Project Goals
4. Implementation
5. Timeline
6. About yourself

In the implementation part you should include all the important implementations you have done prior to the proposal submission in a clear and understandable manner.This will help the mentors to make a decision about your enthusiasm and the effort you have taken in order to complete the project.The timeline part is also important.You should present a clear timeline with clear deliverables so that the mentors can get an idea about your comprehension to the project. Before the final project submission you can prepare a draft proposal and share with the community.So you can change it according to the suggestions made by the mentors and others in the mailing lists.Following you get a proposal prepared for a project called "Native inbound and connector for FTP/SFTP operations for WSo2 ESB".

https://docs.google.com/document/d/1gP66hwLtHJPgKhGWvHTnAWGinVsIz5tDmEivIdk-rRQ/edit?usp=sharing 

Comments