Below are 2-3 example tasks from each of the 5 task categories for Google Code-in. Tasks can vary greatly from organization to organization. For GCI 2013 the organizations will make the tasks equally weighted so each task should take approximately the same amount of time for the normal pre-university student with some computer science background.

Sample GCI Tasks

Below are some tasks that were completed in last year’s Google Code-in contest. Each task for 2013 will also be labeled with a descriptor so you know which type of task(s) it is, coding, documentation, quality assurance, etc. The description will also have languages or skills that may be required to complete the task (Tags).

Coding

Task: MAP: Group Overlays into Folders Description: Want the overlays for the map to be grouped into different "folders" in the UI. That is, want them shown in a widget like a file tree. Ideally, would like an arbitrary depth of nested folders. For GCI, one layer is ok, but try for folders and subfolders. Tags: Python, GIS, JS

Task: Port a Dancer Plugin to Dancer2 (5) Description: Whilst Dancer2 is striving for backwards compatibility, some existing plugins on CPAN may require minor changes, especially if they do anything lower-level with the core of Dancer. Identify a plugin which require changes, and submit required changes to the author for inclusion. Tags: Dancer, CPAN

Task: Email Verification for Account Creation We need (optional) email verification for new accounts. Currently we let a user enter an email address for user creation but we don't verify if that email address exists. This needs to be changed to: when a user wants to create an account, we send an email to the email address the user has given; when receiving the email, there will be a link in it, the user has to visit that url to activate his account; make sure we can get rid of not activated accounts, make sure the method is secure / not easily to abuse; use same code as for password / account recovery (the difference is that for new users we set should set a random password and then send the recovery token) should be configurable, so it can also work without email sending/verification. Tags: Python, HTML, JINJA2, CSS

Documentation/Training

Task: Document Kate’s Build Plugin Many of Kate's plugins are currently undocumented, so users are potentially missing out on some awesome features because they don't know how to use them. Among these plugins are ones that interface with some powerful tools used by developers to make programming easier. Kate's build plugin allows developers to easily build their projects as they write them. Your task is to document this plugin. Expected results: A section of the plugins chapter describing the Build Plugin. It should include a basic introduction that explains how to use the plugin, a list of the menu options provided by the plugin, a description of all the elements in the plugin's user interface, and possibly screenshots. The File Templates plugin documentation is an excellent example of complete plugin documentation. You don't have to know DocBook?, the XML language KDE documentation is written in; just use plain text or your favorite word processor. Prerequisites: A good command of the English language, a working Kate installation, the ability and desire to try things out, see how they work, and explain it to others, and some knowledge of the tools involved in the plugin, such as make, CMake, or gcc. If you're not familiar with these tools, you might find the Kate snippets plugin easier. Tags: Kate Plugin

Task: Example KWin Script An example KWin script should be implemented and added to the kde-examples repository. The script could make a window follow the active desktop, so that it is always on the active desktop but not set on all desktops. This could be useful for e.g. a chat client and is a feature provided by other window managers. Expected results: Example KWin Script implemented. Prerequisites: JavaScript? knowledge Tags: KWIN

Task: Help Create Documentation for glChess Create topic-based help for users of glChess (part of gnome-games). Propose additional topics that you may think would be useful to users. Fill in stub pages with user help, and/or write your own from scratch. Existing stubs that need content include introduction, rules, how to play, save and resume, change board orientation, change promotion type, keyboard shortcuts, and more. Expected results: 5 or more topics fully documented (and attached to the bug in the form of a git format-patch: one patch per topic is preferred). Existing topics reviewed and other topics proposed, if need be. Requirements: install gnome-games and gnome-games-extra, understand the game, a good-command of English and ability to write and explain concepts clearly. An understanding of Mallard, gnome bugzillaand Git is a great asset. Tags: XML, GNOME, Documentation, Games, Linux, Sudoku

Outreach/Research

Task: Research the QEMU and recommended settings to get Haiku to run on it Description: Take screenshots and document how to set it up and such. Tags: Haiku

Task: Boxes: Start a Home Page Boxes is a simple GNOME 3 application to access remote or virtual systems. There is no homepage yet. However there are mockups, goals and non-goals. Boxes needs a nice homepage with content to market it. Boxes code is in GNOME Git. Boxes' design planning page is in GNOME's wiki. Expected results: a set mockups or web pages with materials: text, images, videos ... Requirements: familiarity with GNOME projects and virtualization (VMWare, VirtualBox?, VirtualPC) Tags: Boxes, HTML, VM, Virtualization

Quality Assurance

Task: Test Project for OI File Manager The task is to create a Robotium test project for OI File Manager. This test project can be similar to the existing test projects for OI Shopping List or OI Safe in the main trunk of the repository (e.g. trunk/ShoppingList?/ShoppingListTest?). Your solution should be a patch or a ZIP file containing the new test project. It should include at least 8 tests for various aspects of the application (user interface, menu and context menu, database, intents, ...). Prerequisites: Download the Android SDK (instructions) Requirements for completed entry: Send a patch or a ZIP file containing the new test project. The code must follow our StyleGuide?. There should be at least 8 test cases covering various aspects of the application. Tags: Android, Java

Task: Take the first 100 bug reports and verify they have been fixed Tags: Bugs

Task: Test GNOME Shell on Multiple Monitors GNOME 3 has been extensively tested on single monitor systems and somewhat on dual monitor systems. Further testing of multiple monitors is required to identify issues. You will need to be able to run openSUSE 12.1 on a machine with at least 2 (ideally more) monitors. You will be testing GNOME shell with multiple monitors, looking for both bugs and usability issues. You learn how to investigate complex issues that blend both technical and UX elements. Any issues found will need to be documented and possible workarounds/solutions proposed. Tags: GNOME3, Linux

User Interface

Task: Create User Scenarios for Plasma Active We use user scenarios ( wikipedia:Scenario(computing) ) to guide the development of Plasma Active. These scenarios describe where, when, by whom and how a device with Plasma Active might be used (e.g. "Import photos of a trip from your camera to your tablet, organize them, and show a selection of them to your friends"). The task is to imagine new user scenarios for a device running Plasma Active including people involved, contexts, goals, tasks etc.) Expected results: At least three complete user scenarios. Prerequisites: None. Experience with creating user scenarios or user stories would be helpful. Tags: Plasma Active

Task: Create a new set of buttons for the user interface of tuxpaint Create a functional set of icons for the user interface of Tuxpaint. The icons you have to create are those in the data/images and subdirectories of the tuxpaint source tree. See getting CVS for instrucctions on getting the source code of tuxpaint. If you have any doubts about tuxpaint not specific to this task you can ask in the tuxpaint-devel mailing list. Remember to suscribe before mailing or your mail will be delayed until the mail admin has time to aprove it. Tags: graphics