Google Summer of Code
What’s Google Summer of Code?
GSoC is Google program to sponsor and help students around the world contribute to Free Software projects during their Summer (or Winter in the South hemisphere). The GSoC page is here. An important reading is the GSoC FAQ.
List of Ideas
Our list of ideas is here. See the contact information to talk about them with the mentors.
Contact Information
The primary are the mailing list and the irc channels but you can also get in touch with the mentors (in the list we the name, email, nick on IRC and timezone):
Claudio Takahasi claudio.takahasi@gmail.com – krau (UTC-3)
Gustavo F. Padovan gustavo@padovan.org – padovan (UTC-3)
João Paulo Rechi Vita jprvita@gmail.com – jprvita (UTC-3)
Johan Hedberg johan.hedberg@gmail.com – jhe (UTC+2)
Luiz Augusto von Dentz luiz.dentz@gmail.com -Vudentz (UTC+2)
Vinicius Gomes vcgomes@gmail.com – vcgomes (UTC-3)
Application Guidelines
Your submission have to include an abstract for you project, project milestone/timeline and answer some questions about yourself. If you have any doubt ask the mentors. Next topic will help you on how to fill your application properly:
Abstract
- Write briefly about the project you are applying for. Don’t write much about Bluetooth technology. Most of the abstracts contain information about how Bluetooth is evolving or how Bluetooth is making its mark in the wireless world. This does not help much in your evaluation
- Once you have decided which project to apply for, do a little study/research on it.
Lets say you want to apply for the HFP emulation project.
- First you need to understand the problem statement correctly. If you find that you are not able to understand the scope of the project, or you do not understand the definition or a part of it, ask the mentors to clarify it (IRC/Mail). It is very important that you understand what is to be done. Remember “well planned is half done”.
- Once you know whats the project is all about, do a bit of “googling”. For example: what is a profile? what is a HFP? How do Bluetooth devices advertise services? There are a lot of simple tutorials available on the internet. In case of doubt, ask.
- You don’t need to go in-depth.You just need to have a general idea. If you have any confusion or doubts, ask us. We are here to help. This information will help you in understanding how you will go about the project.
- Now you are ready to write the abstract.
The abstract should answer some basic questions. For Example:
- What do you understand about the project definition?
- Any Ideas about how you want to do the project?
- Why you want to do this particular project?
- Please take a look at a sample abstract here and here on the GSoC page. Its a excellent example.
Project Milestones/Timeline
If you have identified the major milestones in the project or chalked out a plan (weekwise) then we will be very happy to know! It’s not necessary that we have to strictly follow it, but its good to know if you have some sort of plan.
Questions
Have you worked on a Linux system before?
The experience of working on a linux system is different than working on a Windows or any other system. Mention which distribution you have been working on and for how long. Also mention for what purpose you are using a linux system. We want to know if you are comfortable with Linux (any distribution).
Have you contributed to a open source project? if yes, please provide the details.
It is not necessary that you must have a open source contribution. There are no extra points for students who have contributed to open source prior to the application. We want to know if you are aware of how open source projects work. Its not necessary because you are now going to be a part of one, so you’ll learn about it anyway. But if you have done any contribution (filing bugs, testing, documentation, etc.) it’s cool to mention it. Also mention any open source projects you are interested in or using just for fun (just going through the bug list or mailing lists).
What is your educational Qualification (grad/under-grad)?
This question is a bit confusing. We have seen students write a lot about their Grades/GPA. Some of you have also written a lot about your schools/Colleges. We are not running any merit based scholarship here Mention about your school/College briefly. Mention if you are a Under-grad, Grad or PhD student. Don’t worry! There is no precedence in this. Mention the courses you have taken in college. Also mention your area (Computer Science, Electrical Engineering, Mechanical, etc.). Mention the interesting programming projects you have done. If you have put them on your site or on your univ’s site please provide links. Please don’t mention achievements which do not concern GSoC. (i.e. sports achievements).
Why do you want to do a project involving Bluetooth/BlueZ?
This is a pretty straight forward question. But be precise
If your application is accepted will it be a part of your graduation process or it will it be just for hobby?
We are interested to know if this project will be part of your curriculum. We are not questioning your commitment! Students doing projects for hobby tend to be less committed is a wrong notion 
Some general points
- Expressing in English is not easy. If you are weak, use smaller and simple sentences.
- Instead of writing in paragraphs, write in points. That makes reading simpler.
- Be truthful in your application.
- Mention your contact information (IM networks, IRC nicks, etc) in the application.
- Be around #bluez (IRC channel) whenever possible. you will get a lot of hints there.
Abstract
- Write briefly about the project you are applying for. Don’t write much about Bluetooth technology. Most of the abstracts contain information about how Bluetooth is evolving or how Bluetooth is making its mark in the wireless world. This does not help much in your evaluation
- Once you have decided which project to apply for, do a little study/research on it.
Lets say you want to apply for the HFP emulation project.
- First you need to understand the problem statement correctly. If you find that you are not able to understand the scope of the project, or you do not understand the definition or a part of it, ask the mentors to clarify it (IRC/Mail). It is very important that you understand what is to be done. Remember “well planned is half done”.
- Once you know whats the project is all about, do a bit of “googling”. For example: what is a profile? what is a HFP? How do Bluetooth devices advertise services? There are a lot of simple tutorials available on the internet. In case of doubt, ask.
- You don’t need to go in-depth.You just need to have a general idea. If you have any confusion or doubts, ask us. We are here to help. This information will help you in understanding how you will go about the project.
- Now you are ready to write the abstract.
The abstract should answer some basic questions. For Example:
- What do you understand about the project definition?
- Any Ideas about how you want to do the project?
- Why you want to do this particular project?
- Please take a look at the sample abstract here on the GSoC page. Its a excellent example.
Detailed Description
We have given you a template to fill in. Its available here. There you can find some hints on how to answer these questions.
Have you worked on a Linux system before?
The experience of working on a linux system is different than working on a Windows or any other system. Mention which distribution you have been working on and for how long. Also mention for what purpose you are using a linux system. We want to know if you are comfortable with Linux (any distribution).
Have you contributed to a open source project? if yes, please provide the details.
It is not necessary that you must have a open source contribution. There are no extra points for students who have contributed to open source prior to the application. We want to know if you are aware of how open source projects work. Its not necessary because you are now going to be a part of one, so you’ll learn about it anyway. But if you have done any contribution (filing bugs, testing, documentation, etc.) it’s cool to mention it. Also mention any open source projects you are interested in or using just for fun (just going through the bug list or mailing lists).
What is your educational Qualification (grad/under-grad)?
This question is a bit confusing. We have seen students write a lot about their Grades/GPA. Some of you have also written a lot about your schools/Colleges. We are not running any merit based scholarship here Mention about your school/College briefly. Mention if you are a Under-grad, Grad or PhD student. Don’t worry! There is no precedence in this. Mention the courses you have taken in college. Also mention your area (Computer Science, Electrical Engineering, Mechanical, etc.). Mention the interesting programming projects you have done. If you have put them on your site or on your univ’s site please provide links. Please don’t mention achievements which do not concern GSoC. (i.e. sports achievements).
Why do you want to do a project involving Bluetooth/BlueZ?
This is a pretty straight forward question. But be precise
If your application is accepted will it be a part of your graduation process or it will it be just for hobby?
We are interested to know if this project will be part of your curriculum. We are not questioning your commitment! Students doing projects for hobby tend to be less committed is a wrong notion
Project Milestones/Timeline
If you have identified the major milestones in the project or chalked out a plan (weekwise) then we will be very happy to know! It’s not necessary that we have to strictly follow it, but its good to know if you have some sort of plan.
Some general points
- Expressing in English is not easy. If you are weak, use smaller and simple sentences.
- Instead of writing in paragraphs, write in points. That makes reading simpler.
- Be truthful in your application.
- Mention your contact information (IM networks, IRC nicks, etc) in the application.
- Be around #bluez (IRC channel) whenever possible. you will get a lot of hints there.