Google Code-in 2012 digest
It is GCI in a few words without pretension to be comprehensive, so if something is not clear read pages with more details.
Google published following categories for Code-in:
- Code: Tasks related to writing or refactoring code
- Documentation/Training: Tasks related to creating/editing documents
- Outreach/Research: Tasks related to community management and outreach/marketing
- 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
Any task should be created with this in mind:
In other words:
- Tasks must be suitable for 13-17 years old participants that have no educational background to solve complex tasks.
- It must be possible to accomplish one or more tasks from Nov 21st 2011 to Jan 16th 2012. This includes:
- time to analyze problem, and contact mentor for details
- learn about tools and methods used to solve similar problems, and
- actually solve a problem.
One very useful resources for task ideas can be found at Junior jobs. However it is not good for tasks that suit GCI participants, as described in above digest. First and foremost it must be split in tasks that 13-17 years old students can work with.
This 4 points are mandated by Google.
- identify the problem
- give general background
- set time frame to complete
- set requirements to consider task completed
Each task carries one point.