Yesterday marked the start of the 7th year of Google Code-in (GCI), our pre-university contest introducing students to open source development. GCI takes place entirely online and is open to students between the ages of 13 and 17 around the globe.
Open source software makes up the backbone of the internet, from servers and routers to the phone in your pocket, but it’s a community-driven effort. Google Code-in serves a dual purpose of encouraging young developers and ensuring that open source communities continue to grow.
The concept is simple: students complete bite-sized tasks created by 17 participating open source organizations on topic areas of their choice, including:
-
Coding
-
Documentation/Training
-
Outreach/Research
-
Quality Assurance
-
User Interface
Tasks take an average of 3-5 hours to complete and include the guidance of a mentor to help along the way. Complete one task? Get a digital certificate. Three tasks? Get a Google t-shirt. Mentor organizations pick finalists and grand prize winners from among the 10 students who contributed most to that organization. Finalists get a hoodie and Grand Prize winners get a trip to Google headquarters in California where they meet Googlers, mentors and fellow winners.
Google Code-in began with 361 students from 45 countries and has grown to include, in 2015, 980 students from 65 countries. You can read about the experiences of past participants on the Google Open Source blog. Over the last 6 years, more than 3,000 students from 99 countries have successfully completed tasks in GCI.
Student Ahmed Sabie had this to say, “Overall, Google Code-in was the experience of a lifetime. It set me up for the future by teaching me relevant and critical skills necessary in software development.”
Know of a student who might be interested? Learn more about GCI by checking out our rules and FAQs. And please visit our contest site and read the Getting Started Guide. Teachers, you can find additional resources here to help get your students started.
from The Official Google Blog http://ift.tt/2gXu3cy
via IFTTT
Comentários
Enviar um comentário