Not Logged In
Frequently Asked Questions about Google Code-in
For questions about how to use the Google Code-in site, please see the new GCI Melange User’s Guide.
- What is Google Code-in?
- What are the goals of this contest?
- How does it work?
- When does the contest begin?
- When can I register for the contest?
- What are the eligibility requirements for the contest?
- If I’m homeschooled can I participate in Google Code-in?
- What are the prizes?
- How were the participating open source projects chosen?
- How do students choose which organizations to work with?
- How do I decide what task to work on?
- How do I claim and complete a particular task?
- How are individual contest entries judged?
- How are the Grand Prize Winners chosen?
- What does comprehensive body of work mean for picking Grand Prize Winners?
- I have already been working with one of the open source projects; am I allowed to work on their tasks for the contest?
- What is a task?
- What kinds of tasks will I have to choose from?
- What do the values in the "Status" column of the task list mean?
- Can I work on more than one task at a time?
- Is there a limit to the number of tasks I can complete?
- Can I work on a task as part of a team?
- Can I get help from the open source project's community and still take credit for completing a task?
- I started working on a task and I've realized that I don't know enough to get the work done. What should I do?
Forms and Payments
- What forms will be required from student contestants?
- Where do I find the required forms?
- How will I receive my prizes?
- Is there anything else I should plan to do as a participant in the contest?
- What can I do to get ready for the contest before it starts on November 18th?
- How do I get help when I have a question?
- I am 17 years old and 11 months, can I compete in the contest?
- I am enrolled in a university and am only 17, can I participate?
- Where can I find the GCI logo?
- I have a question that is not answered in this FAQ. Where can I find more information?
Google Code-in (GCI) is a contest for pre-university students (e.g., high school and secondary school students) with the goal of encouraging young people to participate in open source. We work with open source organizations, each of whom will provide a list of tasks to be completed by student contestants. Tasks can be anything an organization needs help with, from bug fixes, to writing code, to user experience research, to writing documentation. The contest takes place entirely online.
Google Code-in is intended to help students who may have wanted to get involved in open source but didn't know where to start. By working through the tasks created by participating open source organizations, contestants will be given the opportunity to engage with the open source community and get involved. The participating open source organizations gain the benefit of additional contributions to their project, often in important areas that may get overlooked for whatever reason. It is Google's not so secret hope that the student contestants of today will be long-term contributors to these and other open source projects in the future.
Participating open source organizations create a list of tasks and other contest information pages on www.google-melange.com.
Students claim ownership of a particular task and submit their work for assessment according to the instructions for each task.
Representatives from the open source organization evaluate the work submitted.
If the work is accepted, the task is closed.
If the work needs polishing, the task remains open and the organization representative may give the student additional time and guidance on improving their work.
If the work does not meet expectations, the task can be reopened for another student participant to claim and work on.
The contest begins at 9:00 AM Pacific Time (17:00 UTC) on November 18, 2013. Make sure that you take the time to read through the Contest Rules and familiarize yourself with the introductory information provided by a particular open source project before starting work on a task. Please have your parent or legal guardian read the Contest Rules as well as they will need to provide their consent before you can participate in the contest. Review the full Contest timeline, too.
You can register on the Google Code-in contest site once the contest begins on November 18, 2013 at 9AM PT (17:00 UTC). At that time you will complete these three steps:
- fill in your student profile
- upload the Parental Consent form that your parent/legal guardian initialed, filled out and signed (available in multiple languages on the Downloads page on this site and on the Google Code-in wiki).
- upload your proof of enrollment in a pre-university program.
Once you have completed the three steps above you can claim your first task.
The contest is open to all students who are at least thirteen (13) years of age and no older than seventeen (17) years of age on November 18, 2013. Students must be enrolled in a pre-university program, e.g. high school, secondary school, or educational institution. All contestants will need to have their parent or guardian's consent to participate and submit a complete Parental Consent form. We also require proof of enrollment in a pre-university program before you can claim any tasks. For full details, see the Contest Rules. Remember, by participating in the contest you are agreeing to abide by these rules, so please take a few minutes now to carefully read through them.
Yes. When you create your profile you will need to submit your signed parental consent form and proof of enrollment in a home school program (certificate, transcript, etc.). If you have questions regarding this requirement you can contact the program administrators at firstname.lastname@example.org
At the conclusion of the contest, contestants will receive a certificate for completing at least one task (maximum of one certificate per contestant). For completing three tasks students will receive a t-shirt (maximum one t-shirt per contestant).
Additionally, there will be twenty (20) grand prize winners - two (2) per organization. Each Grand Prize Winner will receive round-trip coach air transportation for himself/herself and one parent or legal guardian to Google’s Mountain View, California, USA Headquarters for 4 nights where they will attend an award ceremony, have an opportunity to talk to Google engineers and have a fun day touring San Francisco. For full details, see the Contest Rules.
We choose open source projects from a pool of applications submitted directly to Google. The open source organizations have all participated in Google Summer of Code and some have also participated in previous Google Code-in programs. We choose organizations that are accustomed to mentoring students online and across time zones. The participating projects will be announced on November 1, 2013.
Students can work with one organization or with multiple organizations during the contest. Look at the home page of each organization to find an organization that interests you.
Take a look at the participating open source projects on the Google Code-in contest page and decide which one(s) are doing work that is interesting to you. Click on the name of the open source project and you'll be taken to its individual contest page, which will give you information about the project and resources for learning more. You can then browse available tasks in the “Open Tasks” section of the project's contest page.
Each task will be labeled with descriptors like "documentation" or "code," which will further help you narrow down your choices of tasks. Take a look at the requirements for an individual task and, if you're up to that particular challenge, claim the task and start working on it.
- Sign in to your Google Account. If you do not have a Google Account, you can create one without charge from Google. If you already have a Gmail address, you can just sign in to your Gmail account.
- Next you will create your student profile. You can click the red “Register As Student” button from the homepage or click the “Login” button on the left-hand navigation bar.
- After creating your profile, you will need to navigate to the “Upload Forms” page from your dashboard and attach your signed parental consent form and proof of enrollment in a pre-university program. After your forms have been successfully uploaded you can then claim your first task.
- To get started, click on the red “Search for tasks” button from the contest home page.
- You can then view all available tasks. There are columns showing:
- the Title of the task
- the Mentoring Organization
- the Category of task (Code, Quality Assurance, etc)
- Tags to help show which coding languages may be needed - Python, C++, etc. or other helpful descriptors about the task
- if the task is Open or Reopened (someone else claimed it but decided to move on to a different task).
- This locks down both the task and the you to the task, meaning:
- No other student can request to claim the same task.
- You cannot request to claim another task, you will need to wait for a Mentor to assign the task to you. If you are already working on a task, you cannot request to claim any other task. Note: It can take a Mentor up to 36 hours to assign the task to you.
- Approve the request. The task will then say “Task Assigned” and state your username in the comment thread. You will also receive an email notification that the task has been assigned to you.
- Reject the request if the request is invalid, irrelevant or a spam. The task moves to Reopened state.
- Once you have marked a task as complete the mentors will receive a notification to review your work. When the work is submitted for review by the mentor, “Ready for Review” will appear in the comment thread.
- One of the Mentors of the task will review your submitted work within 36 hours and take one of the following actions:
- If the mentor is satisfied with your submitted work they will accept the work and "Task Closed" will appear in the comment thread. You can then claim another task if you’d like.
- If the mentor is not satisfied with your work but thinks that it requires a rework and you can fix it, they will post a comment describing what needs to be fixed or added. At this juncture the mentor has the option to extend the deadline for you. The cycle goes back to the point where you have to submit your work again.
- If the Mentor is completely unsatisfied with your work they can reopen the task. The task changes the state to Reopened. The new cycle with another student requesting to claim the task begins.
- If you fail to submit the work before the extended deadline, the task will be automatically re-opened and the task status will be set to Reopened for another student to claim the task.
Each entry is judged by mentors from the participating open source projects. Entries must meet the requirements for completion specified in each task write up. Google's contest administrators will make the final judgment on all entries.
Two (2) Grand Prize Winners will be chosen by each open source organization based on their pool of entries. Judges of the Open Source organization will evaluate the work of the five (5) highest scoring Participants for their Open Source organization and will determine the two (2) Participants with the most comprehensive body of work and name those two (2) Participants the Grand Prize Winners for their Open Source organization. For full details, see the Contest Rules.
When deciding on the Grand Prize Winners, the Judges from each Open Source organization will review all of the work the five (5) students with the highest number of tasks completed during the seven (7) week contest with their particular Open Source organization.
Because some tasks are more involved than others just by the nature of the type of task (example: heavy coding versus a bug fix), it is entirely possible that someone who completed 15 tasks could be chosen as a Grand Prize winner over someone who completed 35 tasks. If they are both among the top five (5) point earners for that organization, they are eligible to be a Grand Prize Winner. The comprehensive or overall work product, including quality of work, is more important than simple quantity of tasks completed.
Additionally, Judges appreciate when a student, in the process of completing the task, goes a step further and finds fixes or additional features to the current task that weren’t explicitly stated and make their work even more useful for the organization. Involvement in the community is always a plus whether that includes being active on their IRC channel or on a group discussion list, etc. Judges like to see students who are involved in the project beyond just completing more tasks than their peers.
As long as you or a family member do not hold an official position in the open source project, such as core developer, documentation working group member or sit on the board of the project, you are welcome to participate in the contest. If you are not sure, please contact Google's contest administrators for help in deciding whether your participation violates the contest rules.
A chunk of work in one of the task categories below, suitable for a 13-17 year old student.
Tasks are divided into the following categories:
- Code: Tasks related to writing or refactoring code
- Documentation/Training: Tasks related to creating/editing documents and helping others learn more
- Outreach/research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
- Quality Assurance: Tasks related to testing and ensuring code is of high quality.
- User Interface: Tasks related to user experience research or user interface design and interaction
Each task will be labeled with at least one of these categories to help you choose which tasks to complete.
Tasks will be available when the contest opens on November 18, 2013 at 9AM PT (17:00 UTC).
- Open: This task has not yet been claimed.
- ClaimRequested: Someone has requested to claim this task.
- Claimed: This task has been claimed and someone is working on it.
- NeedsWork: This work on this task needs a bit more brushing up. This state is followed by a mentor review.
- NeedsReview: Student has submitted work for this task and it should be reviewed by a mentor.
- Unapproved: When the task has been suggested by the mentor but not approved by the organization administrator.
- Unpublished: When the task has been suggested by the mentor and approved by the organization administrator, but not published.
- Reopened: If the task has been rejected by the mentor or organization administrator because it is invalid, irrelevant, or spam.
- ActionNeeded: When the work for the task has not been submitted and the deadline to complete the task has been extended for 24 hours.
- AwaitingRegistration: If a student has completed a task but has not registered.
- Invalid: If the task is marked as invalid, irrelevant, or spam.
- Closed: Work on this task has been successfully completed.
No, you can only claim one task to work on at a time.
You can complete as many tasks as you would like, but the maximum prize to be shipped is a certificate and a t-shirt. Two (2) Grand Prize Winners will be chosen by each participating Open Source Organization based upon the complete body of work submitted to their organization by students. See the Contest Rules for more details.
While we encourage you to get help where you need it, only one person will receive credit per task. Participation as a team is not possible.
Absolutely! We want you to get to know each project's community members and to understand their processes and requirements. It's totally fine to ask for help if you're stuck, but remember that you should try to solve the problem yourself before getting assistance.
To put it a different way, you've taken responsibility for accomplishing something, so it's perfectly acceptable to get it done in a collaborative fashion - that's how open source works! Just make sure the people you collaborate with are not other contestants.
You can withdraw from a task at any time by selecting the “Unclaim task” button from the task page. Don't get discouraged - find something else you're interested in working on that is a better fit for your skills and experience and try again!
Tuesday, October 8, 2013 - Contest announced
Friday, November 1, 2013 - Participating Organizations Announced
Monday, November 18, 2013 (9:00 AM PT / 17:00 UTC) - Contest opens for entries by student participants
Sunday, January 5, 2014 (9:00 AM PT / 17:00 UTC) - Deadline for students to claim their final task.
Monday, January 6, 2014 (9:00 AM PT / 17:00 UTC) - All student work stops.
Wednesday, January 8, 2014 (9:00 AM PT) - Participating Orgs complete all evaluations of student’s work
Monday, January 20, 2014 - Winners announced on Google Open Source Blog
Spring 2014: Grand Prize Trip
All student contestants will be required to send in 2 forms to be able to participate in the Google Code-in contest. These forms must be uploaded prior to the student claiming their first task.
a) an official Google Code-in 2013 signed Parental Consent form demonstrating that they have parental consent to participate in the contest (available in multiple languages on the Downloads page of the Contest site and on the GCI wiki.)
b) proof of enrollment in a pre-university program (any 1 of these will be accepted: photocopy of student ID, letter from school administrator on school letterhead, or copy of current school transcript). There are examples of the acceptable proofs of enrollment on the GCI wiki.
Grand Prize Winners will be required to submit additional paperwork. Please see the Contest Rules for more information.
The parental consent form will be available in 17 languages on the contest site in the Downloads section after November 1 and on the GCI wiki. Find the appropriate language for your parent and have them read the consent form, initial each page, fill out the form and sign it, giving their consent for you to participate in the contest.
Examples of the types of acceptable proof of enrollment in a pre-university program that students must submit are available on the GCI wiki.
The certificates and t-shirts (where appropriate) will start being shipped to the address the student provides in their profile in February 2014.
Subscribe to the contest announcement mailing list for updates about the contest.
If you are looking for help, you can always subscribe to the contest discussion list. If you do subscribe to the discussion list, keep in mind that many people may be sending email to it, you may want to subscribe only for a daily digest email or choose to only browse the group online.
If you need help with Google Groups, check out the documentation.
There is a new, helpful User Guide for the program site available if you have questions on how to get started on the site.
You should read through the contest rules.
You can print the parental consent form from the contest site or the wiki (after November 1st) in the appropriate language for your parent to read over and to sign, giving their consent for you to participate in the contest and have it scanned to your computer so you can easily upload it once the contest starts.
Decide which form of proof of enrollment in a pre-university program you wish to upload (photocopy of school identification card, letter from school administrator or copy of current school transcript) and scan it so that you can upload it once the contest begins.
Finally, you can read through the descriptions of the participating organizations (after November 1st) to see the type of work they do so that you can know which ones you might be interested in working with during the contest.
Each open source project participating in the contest will include information about where to go to ask questions, either on the individual task page or on one of their contest pages. If you still aren't sure where to ask for help, send a message to the contest discussion mailing list. Some projects use an email list, others use IRC or chat, etc.
Yes, you are considered 17 from the day of your 17th birthday through the day before your 18th birthday.
You are not eligible to participate if you have already graduated grade 12 (high school) and are in between high school and university. You are also not eligible to participate if you are in a university, even if you are only 17.
You are not eligible to participate if you are enrolled in a pre-university program but are 18 years old or older.
Once you turn 18 and are enrolled in university you can apply to participate in our university program, Google Summer of Code.
It’s on our wiki.
First of all, make sure you have read the Contest Rules. Each open source project's contest page will have more information about where to ask questions, so also check there for additional information. If you still do not have an answer to your question, please send email to the contest discussion mailing list and one of the contest administrators will be happy to point you in the right direction. You can also find more information on the GCI wiki.