Google Code-in is a contest that introduces pre-university students (ages 13-17) to FOSS development. Students claim tasks from a pre-selected pool of "bite-sized" problems, work on them one at a time, have them approved by the mentors and repeat - the best students are awarded with t-shirts, hoodies or a trip to Google's Mountain View office. Terasology got selected to participate in the contest in 2016!
We need volunteers to think up tasks for GCI! Good tasks should take 2-8 hours to complete, and should not require any previous experience with the codebase beyond what is found in contributor manuals. Unlike GSoC, the tasks can be about things other than code - outreach & research, documentation, translation, quality assurance, usability testing are all fair game. They can be related to the engine, custom modules, non-Terasology projects (Destination Sol, Gooey etc.) or the organization as a whole - the possibilities are endless!
Mentors:
We need volunteers to think up tasks for GCI! Good tasks should take 2-8 hours to complete, and should not require any previous experience with the codebase beyond what is found in contributor manuals. Unlike GSoC, the tasks can be about things other than code - outreach & research, documentation, translation, quality assurance, usability testing are all fair game. They can be related to the engine, custom modules, non-Terasology projects (Destination Sol, Gooey etc.) or the organization as a whole - the possibilities are endless!
Mentors:
- @Cervator (org administrator)
- Skaldarnar (org administrator)
- @Rostyslav Zatserkovnyi (org administrator)
- @SkySom (mentor)
- @manu3d (mentor)
- @xtariq (mentor)
- ...your name here? Contact us on IRC or Slack to become a mentor! Do mention your e-mail address as it's required to invite new mentors to the project.
- Timeline
- Example Tasks - need at least 50-75 of these to start with (new ones can be added as the contest progresses), though the median amount for GCI organizations is >200!
- Participating organization list (Terasology's org page is found here - mostly unchanged since GSoC 2016, blue Gooey's still as awesome-lookin' as ever )
- November 7 - 27: Organizations recruit mentors, write up new "bite-sized" tasks (4-8 hours of time required to complete) and submit them to the GCI website. These tasks are categorized as Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface.
- November 28 - January 13: Students search for a task in the tracker that interests them, claim it and start working on it. Once the student is ready, they submit their work for review through the contest website. Mentors from the organization evaluate the work and either provide feedback or accept it.
- January 13 - January 18: Work is gradually wrapped up; students finish work on tasks and mentors submit final evaluations.
- January 30: Grand Prize Winners and Finalists are announced (more on what that means here)
- June: Grand prize winners get to go on a trip to Google HQ in California!
Last edited: