Qualifying students can apply for one of our Google Summer of Code&trade 2010 project ideas between March 29th and April 9th, 2010.
Student Application Mini-FAQ
- When do I apply?
March 29th - April 9th
- How much time is left to apply?
Countdown: Student Application Deadline
- Where do I apply?
Start from the Google Summer of Code 2010 site
- What ideas can I apply for?
You can suggest your own idea(s) or check out our List of Google Summer of Code Ideas
- What info do you need in the application?
See the Application Template below for reference
- What if I still have questions?
Send a message to the Haiku Mailing List or contact Haiku's Google Summer of Code administrator (Matt Madia).
- Are there any other requirements?
We are strongly suggesting students to submit a code contribution to our bugtracker. This could either be a task marked easy, TODO commented in code, or any other unlisted task. Submitting code that relates to your project will indicate a higher level of understanding and ability. The number and difficulty of resolved issues will be taken into consideration when evaluating your application. It is suggested to include the keyword "gsoc2010" on tickets that contain submissions, as this facilitates finding them in the future.
- Why do you want a code contribution before I'm accepted?
This serves several purposes. It displays that you have the most basic skills that are required: building Haiku from source, running Haiku either natively or inside a VM, and using tools for online collaboration (bug tracker, mailing lists, IRC, etc.). More importantly, it provides our mentors with some insight into each individual student's motivation and abilities. It is an opportunity for you, the student to showcase yourself and to convince us that you are indeed the right person for the job.
Making a Positive Impression
- Submit a patch:
- that relates to your project
- is quality code that conforms to our Coding Guidelines
- feel free to submit more than one patch!
- Have a positive impact on mailing lists, bug tracker, and other public spaces
- Do your homework ; Show that you have:
- researched your project
- an understanding of what needs to be done
- a proper plan for accomplishing it, which includes quantifiable goals and timelines
- Submit an alternate proposal, as this provides our mentors with flexibility for choosing the best students, rather than the best project ideas
When applying for a project idea, please include the information shown in this template.
- Full name
- Preferred email address
- Trac username
- IRC username (optional)
- Summer Education - Are you taking any summer classes? If so, how many credits? Do any current classes end after May 24th?
- Employment - Are you employed or seeking employment with anyone other than Google Summer of Code?
- Schedule - Are there any other unlisted schedule conflicts that would prevent you from effectively participating in Google Summer of Code?
- Time Allocated - As an absolute minimum, how much time per week will you allocate for Google Summer of Code?
- Internet Accessibility - Do you have an internet connection at your home?
- Previous Years -Have you previously participated in past Google Summer of Code's? If yes, with which groups?
- Brief bio - Who are you? What development experience do you have (academic, industrial, open source)?
Project idea information
- Project title - E.g.: "Implement a complete C++ network stack class framework."
- List of project goals - These must be quantifiable results. For example:
- Implement application A.
- Implement features F, G, and H for module M.
- Write documentation for the new interfaces I and J.
- Write N unit tests for module M.
- Improve performance of module M by at least N%.
- Project description -