GSoC 2014
Why does Haiku want to participate?
The Google Summer of Code is a wonderful opportunity for the Haiku Project. It exposes Haiku to many potential youthful and energetic minds that are interested in developing Open Source Software. Even more exciting, it provides a unique opportunity of generating income for the Project while growing a handful of carefully selected students into knowledgeable and potential long-term contributors. As an open source project that develops an operating system, our pool of active committers is relatively small and being able to embrace new contributors is literally a wonderful thing.
As a mentoring organization, we balance selecting impressive students (who display promise of becoming regular contributors) and useful projects (which can be mentored and are appropriate for Haiku).
We strive to nurture our students into talented and motivated open-source developers. This includes being able to communicate effectively on public mailing lists, provide relevant information in bug reports, continually publish code for peer-review, and perhaps most importantly, knowing when to ask for help. Those skills empower them with the confidence and ability to continue making valued contributions to Haiku (or any open source project for that matter).
Current status of the program
The Haiku developers have come up with a list of ideas for students to choose from or to base their proposals on. The candidate students need to start discussing application ideas with Haiku as soon as possible. The application period for students is March 10th to March 21st. The list of accepted students, their projects, and mentors will be announced on April 21st (19:00 UTC).
- Timeline of Google Summer of Code 2014
- Significant Dates (all times are 19:00 UTC):
- Feb 24, List of accepted mentoring organizations published on the Google Summer of Code 2014 site.
- March 10, Student application period opens.
- March 21, Student application deadline.
- April 21, Accepted student proposals announced on the Google Summer of Code 2014 site.
- May 19, Official start of the coding period (students may start earlier, if desired)
- June 9, Quarter-term report (Haiku specific milestone)
- June 23, Mentors and students can begin submitting mid-term evaluations.
- June 27, Mid-term evaluations deadline.
- July 21, Three-quarter-term report (Haiku specific milestone)
- August 11, Suggested 'pencils down' date.
- August 18, Firm 'pencils down' date. Mentors and students can begin submitting final evaluations.
- August 22, Final evaluation deadline. Students can begin submitting their code samples to Google.
- August 25, Final results of Google Summer of Code 2014 announced
- October 25 & 26, Mentor Summit at Google
Who are the Haiku mentors?
Haiku utilizes a mentor pool, as a complement to the assigned mentor (and co-mentor) for each student. The mentor pool allows additional people to provide support throughout the Google Summer of Code program. Students who utilize the mentor pool avoid bottlenecks that can happen, when responsibility would otherwise depend on a single person inside a volunteer driven project. This also helps to strengthen the students' ability and comfort with discussions on an open mailing list, which is essential in many remote software development models. A complete list of all Haiku mentors for Google Summer of Code 2014 is being compiled.
- Bruno Albuquerque (BGA)
- Stephan Aßmus (stippi)
- Andrew Bachmann (andrewbachmann)
- Adrien Destuges (PulkoMandy)
- Jérôme Duval (korli)
- Alexander von Gluck IV (kallisti5)
- Rene Gollent (AnEvilYak)
- Fredrik Holmqvist (tqh)
- Scott McCreary (scottmc)
- Urias McCullough (umccullough)
- Hamish Morrison (hamishm)
- François Revol (mmu_man)
- John Scipione (Skipp_OSX)
- Ingo Weinhold (bonefish)
How you can help Haiku in Google Summer of Code
Even as a non-mentor, you can help by providing assistance to the students on the mailing list and on the Haiku IRC channel. Making the students feel comfortable with the community is important, as it can help them do a better job at reaching their Google Summer of Code goals, and could also be the key to students staying with the project even after their Google Summer of Code assignment is over.