When Google's 905 accepted students officially begin coding on May 28th, 137
mentoring open-source projects will be given a serious influx of labor. As in 2005 and 2006, Google will be paying each of these university students $4500 to act as pro-tempore developers for the scores of participating open source projects. The projects are given $500 for each student they take on and mentor. Google is spending more than four million dollars on the program this year, and significant contributions are expected for projects ranging from Ubuntu and Mozilla to scientific endeavors.
The Google Summer of Code 2007
reached the second major milestone in its program timeline on April 11th by posting accepted student applications. This follows the announcement of accepted mentoring organizations and the simultaneous commencement of the student application period, the first major milestone, on March 14th.
For more information about the Summer of Code's motivation, evolution, logistics, finances, and success, the Linux Weekly News turned to Google's Open Source Program Coordinator Leslie Hawthorn:
LWN: What prompted Google to found the annual Summer of Code in 2005? What were the initial goals of the project, from Google's perspective?
Hawthorn: We were looking for a way to provide students studying computer science and IT another set of opportunities to work in their field of academic study over the summer. We were also hoping to introduce more students to open source development, as well as to increase the number of open source developers in general. Of course, the great by-product of all of these goals is that more open source code is available to everyone.
LWN: Were there any complaints or controversies from past Summers of Code that prompted logistical changes for the 2007?
Hawthorn: We'll always be working to improve the program. Payments were an area of difficulty in 2005, and also last year, though much less so. This year we're introducing a whole new method of payments which we hope will mean that disbursements go more smoothly.
We also heard from many of our students and mentors that there simply wasn't enough time during the program for students to come up to speed and get their code written, debugged and integrated back into the code base. We've reworked the timeline substantially this year and added in two months of "community bonding" to help with the time crunch.
LWN: According to a 2006 article by the Internet News, about thirty percent of students continued to work with their mentoring organization after the completion of their Summer of Code 2005 project. Are you pleased with that retention rate? What could be done or has been done to improve it?
Hawthorn: We're pleased, but we'd be ecstatic if that percentage were even higher. We're hoping the community-bonding period will encourage more students to stick around after the program ends.
LWN: Google was only able to accept less than half of the mentoring organizations which applied this year. What criteria did you use to differentiate and select these organizations?
Hawthorn: We based our decisions on several factors, but the major area was an organization's Ideas list: Did it look like a set of reasonable goals for students? Did the projects look interesting? Did the organization's Ideas list look well-organized and clearly written?
LWN: How does Google benefit from accepting mentoring organizations such as the Robert H. Lurie Comprehensive Cancer Center of Northwestern University, which seemingly have little or no relevance to Google's business?
Hawthorn: We take orgs from a wide variety of technology spaces. We benefit in the same way the rest of the world benefits: by having more code produced for everyone to use.
LWN: Both mentors and students are required to submit evaluations which Google uses to determine whether or not the participants successfully completed their project and deserve payment. What questions are on these evaluation forms? What factors does Google use to determine whether or not payment is deserved?
Hawthorn: The questions are newly determined each year. While Google makes the final determination on whether a student receives payment or not, in almost all cases we go with the mentor's judgment call. (We have not determined the questions yet for this year.)
LWN: Can you estimate the success rate in past Summers of code based on these evaluation forms?
Hawthorn: We had 89% of students pass their final evaluations for the 2005 program, and 82% for the 2006 program.
LWN: What is Google's overall budget for the Summer of Code? How has this budget increased since 2005?
Hawthorn: Our stipends budget has increased $1M each year; in 2005, we awarded $2M and in 2006 we awarded $3M. This year, our funding will increase to $4M. Our overall program costs behind the scenes will increase somewhat year by year, but not notably so.
LWN: Google pays $5000 per student project - $4500 to the student and $500 to the mentor. What other major expenses are involved in the Summer of Code, be they during planning, administration, or otherwise?
Hawthorn: Shipping internationally is incredibly expensive. We spend a decent amount of time planning for the program when it's not in session as well.
LWN: What do you find usually motivates students to participate in the Summer of Code? Surely it's not just the money.
Hawthorn: It's the t-shirt. Seriously, though, students are drawn to the program for a variety of reasons: passion for open source, desire for recognition and potential career advancement. That said, though, you would be shocked at the number of student and mentor applications that specifically mention the t-shirt.
LWN: Is it too early to announce the Google Summer of Code 2008?
Hawthorn: We have nothing to announce now. Stay tuned! :)
to read more of the interview with Leslie Hawthorn
and see what's coming with this year's Summer of Code.
to post comments)