Last updated November 3, 2015.

Google Code-In is a program to get 13-17 year old students involved in open source. We need lots of mentoring help, so please read on to find out how to get involved!

There are many ways to get involved. Here are a few:

Proposing tasks

We need people to think up tasks for GCI. Good tasks should take students about 2 hours to complete, and should not require any previous Drupal knowledge or experience. GCI is not only about code! Tasks can be about other things, such as outreach, marketing, translation, research, documentation, usability, etc. Also, please try to avoid wildcard tasks (like "choose a bug and fix it"). Tasks can be for Drupal core or for any contributed module or theme, or for the Drupal community as a whole.

Here is the full list of guidelines to register as a mentor and add tasks. Use the Task Idea List to propose new tasks; add your tasks at the bottom of the spreadsheet. If you feel you cannot mentor the task for some reason, leave the mentor field blank. Make sure that you follow the Task template and the task complies with the Task Guidelines.

Reviewing and revising tasks

The Idea list contains a list of tasks that currently are not posted to the official Google application. If you notice a task that currently does not has a mentor and you feel you can mentor the task, feel free to add your name in the mentor column and also register on Melange as a mentor.

Mentoring

We need people to mentor tasks! Basically, just make yourself available, through IRC, IM, Email, or other means, to a student for help. Join Google Code-In group for further updates.

To mentor a task, one needs to be signed up on Melange, Google's GCI application, and apply to be a mentor for the Drupal project. Once your application is approved by admin, you can add the task and assign yourself as a mentor.

Work reviewing / Melange monitoring

We need people to review tasks, one must sign up for Melange, and apply to be a mentor. Once that's done, you can go to URL and see all the tasks that have been claimed for Drupal. Two things, mainly, need to be done:

  1. Approving people's claim requests -- in Melange, students must to request to claim a task, and then the claim must be approved.
  2. Reviewing tasks -- to review a task, ensure that it meets community standards (like the coding standard for code etc) and it meets the task deliverables. If the task passes, close that task. If not, leave it open.

To get involved, feel free to just pick up any of these tasks -- we'd love your help. You can also stop by in #drupal-google, which is our IRC channel for GCI.