Version 10 (modified by cotto, 11 years ago)


This page lists tasks that we believe will be suitable for Google Code-In 2010.

1. What is Google Code-in?

Following on from the success of the Google Summer of Code™ program, Google is holding a contest for pre-university students (e.g., high school and secondary school students) with the aim of encouraging young people to participate in open source. We will work with open source organizations, each of whom will provide a list of tasks to be completed by student contestants. Tasks can be anything a project needs help with, from bug fixes to writing documentation to user experience research.

2. What are the goals of this contest?

Google Code-in (GCI) 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 suggested by organizations, contestants will be given the opportunity to engage with the open source community and get involved. The participating open source projects 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.


Tasks will typically fall into the following categories:

  1. Code: Tasks related to writing or refactoring code
  2. Documentation: Tasks related to creating/editing documents
  3. Outreach: Tasks related to community management and outreach/marketing
  4. Quality Assurance: Tasks related to testing and ensuring code is of high quality
  5. Research: Tasks related to studying a problem and recommending solutions
  6. Training: Tasks related to helping others learn more
  7. Translation: Tasks related to localization
  8. User Interface: Tasks related to user experience research or user interface design and interaction

Proposed tasks (more needed)

Task # 1: Make reflect current development and be more useful

Potential Mentors: ?

Background Required: Familiar with HTML, CSS, RSS

Details: The main web site is currently not dynamic enough. It is hard to see what is going on in our community right now from our main entry page. This task will make usability improvements to our site such as: List the last few commits to our codebase, giving links to relevant mailing lists and irc channels (and logs), summarizing recent blog posts from Planet Parrot, etc. PLEASE ADD MORE DETAIL.

Task # 2: Convert tests written in perl5 to pir - This could/would be multiple tasks

Potential Mentors: mikehh, ?

Background Required: some perl, read up on pir, examples to be given

Details: A lot of our tests are still written in perl5 or a combination of perl5 with pir in CODE/OUTPUT blocks. Ultimately we would like to get rid of any dependency on perl5. We will put forward a list of tests that still need converting and set them up as a tasks with one or more tests to be converted.

Task #3: Increase test coverage of PMCs - This represents several tasks.

Potential Mentors: cotto, ?

Background Required: familiarity with  PIR and C, Perl 5 in some cases.

Details: Many of our  PMCs don't have complete test coverage. Although 100% coverage may not be possible in all cases, we can do better. We will provide a list of PMCs which need increased test coverage and notes about any PMCs which may provide difficulties in reaching 100%. A task will be complete when, at the mentor's discretion, a PMC's coverage is increased as much as is practical, ideally to 100%. This task requires the use of PIR, but increasing test coverage will usually require a small and easily-learned subset of PIR.