Google Code-in/2013

Google Code-In is a contest to introduce pre-university students (ages 13-17) to the many kinds of contributions that make open source software development possible. Students must complete tasks (see examples), one at a time. The Google Code-in 2013 contest runs from November 18, 2013 to January 6, 2014.
 * 2013-11-01: Mentoring Organizations for Google Code-in 2013 are announced (Google's announcement)
 * 2013-11-01: Wikitech-l: Google Code-in: YES, WE ARE IN! (our community annoucement)

Instructions for GCI students
These instructions are common to all the GCI tasks. Each category of tasks has further instructions.

Feedback and support
Each GCI task specifies a public community channel for related questions and comments that might be more efficient than Google Melange. Identifying yourself as a GCI student may help you getting more/faster help from other contributors in addition to your mentor(s). For feedback not tied to a specific task you can use more generic channels like IRC or mailing lists. Avoid private email or support requests in our social media channels. Please be patient when asking questions. Learn more at Communication.
 * Sometimes the channel is a bug report. See Bugzilla (except for Kiwix tasks which use Sourceforge instead).
 * Sometimes the channel is a wiki discussion page. See Help:Talk pages.

The code of MediaWiki, its extensions, and Wikimedia's server configuration is located in Git repositories. You are expected to provide your work (patches etc.) in both Google Melange and Wikimedia Gerrit for review. See Developer_access and Gerrit/Tutorial for more information. In case you have problems with Gerrit, providing your work in the corresponding bug report in Wikimedia Bugzilla is an acceptable workaround.

Tasks
This selection shows the variety of tasks available. The descriptions of the tasks are not final, and we are still polishing them. Added tasks should clearly identify a mentor (or instead added to . As a reference, currently we have identified about 240 annoying little bugs.

Mentors: Please add new tasks directly in Google Melange instead of this wikipage after reading the Mentor's corner section below.

Code
(Mentors: please add here the common instructions for the tasks under this category)

Tasks related to writing or refactoring code.

Kiwix for Android
''All tasks have been imported into Google Melange. Mentors: Please add further tasks directly in Google Melange (feel free to check already imported tasks) after reading the "Mentors' corner" at the bottom of this page.'' --AKlapper (WMF) (talk) 15:27, 6 November 2013 (UTC)

Lua templates

 * 1) Wikipedia and other Wikimedia projects have dozens of old Wikitext-based templates waiting to be rewritten in Lua. We can list many more here. There is also Wikipedia:Lua requests.
 * 2) * en:Template:Taxobox / zh:Template:Taxobox (not exactly the same thing as the one in English Wikipedia)
 * 3) ** Currently the scope feels unclear, this needs to become a more specific task. Please list templates that you would like to see ported, or how a student would find these templates. How many templates should get ported for one GCI task? --AKlapper (WMF) (talk) 16:42, 12 November 2013 (UTC)
 * 4) Bibliographic data on Wikipedia/Wikidata.
 * 5) * Create a new template based on en:Template:Infobox book that can retrieve bibliographic information from wikidata according to the data model (d:Wikidata:Books task force). Initially only for the work item only. --Micru (talk)
 * 6) ** asked Micru to please register as mentor on his talkpage --AKlapper (WMF) (talk) 14:39, 12 November 2013 (UTC)
 * 7) * Enhance the template so it can show information belonging to a featured edition. It can be the first edition, the original, a translation, a contemporary version, etc. Example fr:Des souris et des hommes --Micru (talk)
 * 8) ** asked Micru to please register as mentor on his talkpage --AKlapper (WMF) (talk) 14:39, 12 November 2013 (UTC)

JavaScript gadgets
This program is perfect for fixing and updating gadgets written in JavaScript. We are harvesting tasks from Gadget kitchen/Requests and Bugzilla.

Documentation/Training
(Mentors: please add here the common instructions for the tasks under this category)

Tasks related to creating/editing documents and helping others learn more. How can these students help fixing Bug #1?


 * Review and polish browser test automation docs for newcomers.--Qgil (talk) 22:27, 22 October 2013 (UTC)
 * Sort out Category:Tutorials.--Qgil (talk) 22:27, 22 October 2013 (UTC)
 * More tasks to be extracted from Technical communications/What you can do added to Melange. guillom 08:45, 14 November 2013 (UTC)
 * List the Lua modules active on various Wikisources here. Modules on French Wikisource, Modules on English Wikisource Rtdwivedi 14:00, 4 November 2013 (UTC)

Outreach/Research
(Mentors: please add here the common instructions for the tasks under this category)

(I have started moving these tasks to Melange.--Qgil (talk) 00:02, 9 November 2013 (UTC))

Tasks related to community management, outreach/marketing or studying problems and recommending solutions.


 * How to get volunteers involved in Operations / sysadmin tasks. See Sysadmin hub & wikitech-l thread.--Qgil (talk) 22:34, 22 October 2013 (UTC)
 * Self-help guide to organize events. See Events kit and how WordPress does it.--Qgil (talk) 22:34, 22 October 2013 (UTC)
 * Plan a Guided Tour at mediawiki.org.--Qgil (talk) 22:34, 22 October 2013 (UTC)
 * Improve the confirmation email sent to new registered users and sync Template:Welcome.--Qgil (talk) 22:34, 22 October 2013 (UTC)
 * What to do with the social media stats being collected at Talk:Community metrics?--Qgil (talk) 22:34, 22 October 2013 (UTC)

Quality Assurance
(Mentors: please add here the common instructions for the tasks under this category)

Tasks related to testing and ensuring code is of high quality.

''All tasks have been imported into Google Melange. Mentors: Please add further tasks directly in Google Melange (feel free to check already imported tasks) after reading the "Mentors' corner" at the bottom of this page.'' --AKlapper (WMF) (talk) 15:27, 6 November 2013 (UTC)

User Interface
(Mentors: please add here the common instructions for the tasks under this category)

Tasks related to user experience research or user interface design and interaction.

''All tasks have been imported into Google Melange. Mentors: Please add further tasks directly in Google Melange (feel free to check already imported tasks) after reading the "Mentors' corner" at the bottom of this page.'' --AKlapper (WMF) (talk) 11:34, 7 November 2013 (UTC)

Tasks searching for a (co-)mentor
This section lists potential GCI tasks which were either proposed by community members who cannot mentor their proposed tasks, or tasks for which the mentor would like to see a co-mentor before making them available to students, or tasks added for which the creator has not been successfully been contacted and hence also look for a potential (co-)mentor.

Do you spot a task that you could mentor? Go ahead, add your name, and read !

Code

 * [] Make the Parser Functions extension deliver correct instead of guessed results of incomplete dates and make this behaviour configurable. Krabina (talk) 08:18, 4 November 2013 (UTC)
 * Mentor wanted. --AKlapper (WMF) (talk) 14:28, 12 November 2013 (UTC)

Lua templates

 * Improvements to LUA modules: commons:Module:Languages needs cleanup: All template-constructions (e.g. in,  ,  ) should be substituted by calls to MW's LUA API,   should not use   (because it's too expensive), documentation must be added, ... Rillke (talk) 13:39, 2 November 2013 (UTC)
 * Co-mentors wanted. --AKlapper (WMF) (talk) 14:44, 12 November 2013 (UTC)
 * Improvements to LUA modules: Compare and evaluate different documentation approaches for LUA modules in different Wikis and port the best elements to Commons. Rillke (talk) 13:43, 2 November 2013 (UTC)
 * Co-mentors wanted. --AKlapper (WMF) (talk) 14:44, 12 November 2013 (UTC)

JavaScript gadgets
Co-mentors wanted for the following tasks:


 * Write and promote a module that detects both, usage deprecated JavaScript functions as well as extremely bad coding style and syntax errors in JavaScript files. This might be a good template. Rillke (talk) 14:11, 2 November 2013 (UTC)
 * Write a module using the above (deprecation checker) to iterate over all JavaScript files in a wiki's MediaWiki-namespace creating a report. Rillke (talk) 14:11, 2 November 2013 (UTC)
 * Identify gadgets at Wikimedia Commons and other scripts that still make use of deprecated functions and make suggestions how to replace them. Rillke (talk) 14:11, 2 November 2013 (UTC)
 * Create a script capable "packaging" gadgets so they can be shared with other wikis using ResourceLoader. Rillke (talk) 14:11, 2 November 2013 (UTC)
 * Bug fixes and new features for the slideshow
 * Fix the positioning/sizing-bug for the "main picture"
 * Toggle keyboard-observers when slideshow is closed/opened (so it does not interfere with other gadgets when closed)
 * Add option to hide the caption/info-container
 * Use thumbnails that are available on page (and thus do not have to be loaded again) for the thumbnail preview bar, if possible
 * Add Touch&Swipe support, for both the thumbnail-bar and the "main picture" for touch and mice (where it is actually drag&drop-like).
 * Create and document an API so external tools may a) provide a list of images asynchronously b) add jQuery-Objects or DOM-Elements to the caption/info-container (e.g a button for votes). Rillke (talk) 14:11, 2 November 2013 (UTC)
 * Apply MediaWiki's coding-style to Common's Stockphotot gadget, outsource style (maybe create a sprite for all the images), make it modular: Input: HTML-string; Output: An object containing all the links -- this allows us to re-use this gadget inside other tools. Rillke (talk) 14:17, 2 November 2013 (UTC)
 * Activate the gadget ImageAnnotator on Swedish Wikipedia so that annotations on Commons can be seen there. There has been community consensus since long ago to have it (not enabled for everbody to start with) and the work has started, but for some reason it does not work. --Jan Ainali (WMSE) (talk) 14:08, 14 November 2013 (UTC)

Mentors' corner
First things first:
 * 1) Become an official mentor in Google's Melange.
 * 2) List above the tasks you want to create at the GCI site.
 * 3) Before starting creating tasks, please contribute to the common boilerplate text.
 * 4) Watch this page for more instructions, or ask for them.
 * 5) Be ready to learn with the rest of us along the way.  :)

Become a Wikimedia GCI mentor
Register as mentor. Afterwards, inform Quim and Andre of your username in Google Melange so you can be invited to become a mentor for Wikimedia. (Tasks can not be imported before you have been marked as a mentor for Wikimedia.)

Requirements of a task
All the tasks listed on this wikipage must be also listed in Google Melange well before November 17, since that is the interface that students will use. A basic boilerplate task description pointing to bug reports should be added below.

Please add new tasks directly in Google Melange instead of this wikipage. Mentors can add tasks at any time, also after GCI has started. Usually this is what happens when students are finishing tasks, they have already learned about a specific area, and they want more tasks related to it.
 * Tasks are supposed to take 2-3 hours to an experienced contributor. It is fine if the first task takes even 2-3 days to a student because they must understand many concepts and setup their environment first. And it is also ok if students specialize in a type of task, so every new task takes less time to complete until they are also able to complete them in a couple of hours.
 * Tasks are self-contained. Students must be able to complete it without much knowledge of the context, or the background.
 * By default, tasks are described in a bug report with the keyword "easy" and 1-2 mentors CCed and volunteering explicitly in the comments.

A list of potential candidate bugs is available as the GCI candidate bugs saved search on Bugzilla (MediaWiki and extensions, +easy, -gci2013, no patches pending).

Candidate bug reports in Wikimedia Bugzilla should have " gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks " added to their Whiteboard field to make it easy to track them. See the current list:

Org admins Quim Gil and Andre Klapper go through proposed tasks and confirm them. CC us in the bug reports.
 * Bug description. Detailed explanation with full URL link to corresponding bug report and links to any information that could be helpful. Hours that it takes to complete the task (be generous!). Arbitrary tags that can be searched for (e.g. programming language). Name of the mentor(s): ~

Common instructions for tasks
We want to use common texts in tasks wherever it makes sense to simplify the process of creating good task descriptions. Let's draft different levels of common texts: generic for all, specific to a category, specific to a type of task. When creating a task, use the levels that make sense. Let's link to on-wiki instructions and background as much as possible. This gives us freedom to improve content without having to edit multiple tasks.

For all tasks
The last sentence of each task description in Google Melange must be: Students are required to read Wikimedia's general instructions first.

Kiwix for Android
Kiwix is a Wikipedia offline reader. These are tasks related to the new release of its Android app. Instructions to compile the app can be found here (Android section). This requires knowledge of the Java programming language.

User Interface: SVG Graphics
This task requires existing graphics skills working with a Vector graphics application (e.g. Inkscape). Links to SVG file(s) that you have created are welcome. Basic knowledge of CSS might also be helpful for integration.

Pywikibot
PyWikibot is a Python-based framework to write bots for MediaWiki. Patches can be submited through the gerrit uploader (you need a MediaWiki.org account). More documentation on gerrit can be found here. After you have successfully claimed this task in Google Melange please do use the bug report in Bugzilla for communication instead of Google Melange. This allows more PWB developers to be reached! General development questions can be asked on the Pywikibot mailing list and the #pywikipediabot IRC channel.