How does one become a contributor of Open Source development? Some start with the wish to fix that certain annoying bug in their favorite software. Others want to extend it by a new feature. However you arrive, the path to go to get that seemingly easy task done is often not clear. Where’s the source for that button? How do I make my changes take effect in the software that is run? Finding the right path can be a frustrating journey many are not willing to endure. Google Code-In (or GCI for short) aims to help out: Pairing prospective contributors with mentors from established open source organizations builds a path to successful contributions. KDE has participated in GCI as a mentoring organization since its start in 2010, and did so again in the most recent 2013 edition.
GCI is all about cakes^w tasks.
To increase motivation GCI is organized as a contest. Pre-university students in the age of 13-17 years from most (not all) countries of the world may choose from a large pool of code, documentation, research, quality assurance and user interface tasks. Where does this pool come from in the first place? It is created by the mentors of all ten participating open source organizations who also maintain it during the whole contest. A task is a set of work in one of the five categories that takes a student a couple of hours or days to complete. Besides self-contained tasks often task series are created where either similar work is split into several tasks or related work is split into subsequent tasks. This way all sort of work can be converted into manageable pieces.
Nevertheless GCI is not meant to be a way of distributing work. Indeed it’s much more a communicative event where lots of small teams emerge — students and mentors exchange ideas, collaborate and task after task gets closed. Each successfully completed task earns you a point. In the core of the contest said procedure of choosing a task and completing it is repeated for seven weeks in a row. Afterwards the number of successfully completed tasks is summed up: One earns you a certificate. Three or more a groovy T-shirt to make your friends jealous. And if you are among the twenty top performers you win a trip to Google Headquarters in Mountain View, California!
All 20 GCI 2013 Grand Prize Trip winners in front of the famous Android lawn statues.
Getting there means finishing tasks, but fortunately they’re fun to work on. Maybe even addicting, or why else would you work on them from dusk till dawn? The never-sleeping KDE students added documentation videos for all sorts of KWin effects, updated KGeography for recent changes of regions and polished KStars features. A new touch typing course for the US english keyboard layout and keyboard layout files for more languages were created for KTouch. The Python support of KDevelop was extended in a series of tasks and Amarok got several new testers to verify bugs. The email client Trojitá got a couple of usability improvements and all sorts of new features found their way into Marble. Among them are extensions of its KML support, polishing of the new ownCloud integration and initial support for tours. Inner and outer planets of our solar system are now shown as well as the moon with its phase. New map themes were created, the interactive legend enhanced, the handbook and Python binding documentation extended, routing support improved and a screencast recording feature added. The Marble tasks alone sum up to 115, a considerable amount of the 259 KDE tasks closed in total. At the end of the contest Mikhail Ivchenko from Russia (47 tasks) and Benjamin Kaiser from Australia (46 tasks) ranked top among the KDE students. They joined the lucky twenty who visited Googleplex from April 13th to 17th. For the first time each organization could send a mentor to the trip as well; I was the happy one from KDE to go to Mountain View as well.
Mikhail, myself and Benjamin in the awards ceremony. Photo by Sergej Ivchenko.
The trip was an amazing experience for all of the 50 participants (20 students accompanied by a parent each and 10 mentors), lovingly organized by Stephanie Taylor and other members of the Google Open Source Programs Office. It started off with a meet-and-greet event in San Francisco to get to know everyone, followed by a day around Googleplex in Mountain View, a fun day in San Francisco and a farewell day in the Google San Francisco Office. Group activities like the Google campus tour, a Segway tour in San Francisco, a visit to Alcatraz, a Yacht cruise and a visit to the California Academy of Sciences were varied with lots of food, swags and interesting talks by Googlers. A great experience that all participants will keep in happy memory for a long time! Stephanie summarized it nicely:
This week we had the 20 grand prize winners and 1 mentor from each org here in Northern California for the Grand Prize trip and it was an amazing experience for all of us. Being able to watch the students literally glow with excitement at meeting their mentors was very heartwarming.
As a bystander watching all of the conversations and hacking going on between students and mentors for 4 days was incredible. Students were not just chatting with the mentors from their orgs they were also involved in highly technical conversations with mentors and students from other orgs. At every meal and break I would look around and there would be groups of 4-8 people huddled together deep in conversation. I’m sorry we can’t have every one of you attend the trip, but trust me, if you witnessed what I saw you would know that all of those long hours and sleepless nights you put into the 7 week contest helping teenagers learn about open source and your projects was worth it. : ) Kudos to all of you.
We hope that these students will continue to be contributors with your orgs and maybe even mentors and or GSoC students in the years to come.