Google Code-in/2016

From MediaWiki.org
Jump to: navigation, search
Google Code-in logo 2016.jpg

Google Code-in 2016 is over. 424 Wikimedia tasks (100 of them "get onto IRC" tasks) were successfully completed thanks to 192 students and 46 mentors. Thanks everybody!

Google Code-in is a contest to introduce pre-university students (ages 13-17) to the many kinds of contributions that make free and open source software (FOSS) development possible. Students must complete tasks, one at a time. It is sponsored and run by Google. The Wikimedia Foundation has participated since 2013.

The Google Code-in 2016 contest runs from November 28, 2016 to January 16, 2017 (see the full timeline).

Apply as a student Mentor a task now

Google Code-in 2014 Grand Prize winners
Weekly summary of tasks.

Instructions for GCI students[edit]

Only after November 27th, when the Google Code-In contest opens for entries by student participants, come back to this wiki page to follow the instructions below. The instructions are common to all Wikimedia GCI tasks.

Register for the contest[edit]

Register on the Google Code-in site, and get a general overview of the contest provided by Google.

Choose tasks and read the related documentation[edit]

  • If you choose to work on a coding-related task, follow all the steps indicated in our “How to become a MediaWiki hacker” tutorial to setup the development environment, download our code from Git, and start submitting patches in Gerrit. Some helpful tips for the contest which are missing in the tutorial:
    • We recommend MediaWiki-Vagrant, for setting up the development environment for MediaWiki - a virtual machine that has the basic wiki software and various common extensions preconfigured.
    • Only if you have problems with Gerrit, providing your work in the corresponding task in Wikimedia Phabricator is an acceptable workaround.
    • Test your patches before submitting them for review in Gerrit! If you have submitted them without testing, clearly say so in an additional comment in Gerrit.
  • If you choose to work on any other task other than coding such as documentation, outreach, research, design, support, read our “How to Contribute” tutorial.

Ask for feedback, questions, and support[edit]

  • To communicate directly with your mentor, connect to the IRC channel they are frequently available at. See the list of mentors below. Your mentor will not always be around or awake - please just ask as other people might also be able to help.
  • If you have a specific question about a task, comment in the related Phabricator task. "What do I have to do to work on this?" is not a good question to start with. The more specific your questions are, the more likely somebody can answer them quickly. If you have no idea at all how to start working on a task - please consider finding an easier one first.
  • For general questions, refer to IRC channels, mailing lists, wiki discussion pages, or Gerrit discussion pages (if you have a problem with Gerrit).
  • Learn more at Communication.

Some general recommendations for communicating[edit]

  • Before reaching out to the members of the community with questions, do some basic research yourself first on the task and on the related issues you are facing: Look at the code, try to understand what it is supposed to do, and try to find the probable place(s) where you need to make changes in order to fix the bug.
    • Bug reports (also called "tasks") in Phabricator) have a "Tags" section in the upper right corner. There you can see the project that the problem is located in. This provides you a hint about the Git repository that the code is located in, and about the development team which you could contact if you want to discuss it in a "broader" way, as comments in bug reports should only refer to the specific problem described in the report. (Only if you work on the Kiwix project: Kiwix does not use Phabricator but instead uses Sourceforge).
  • Identifying yourself as a GCI student in our communication channels might help you get faster help from other members of our community.
  • Be patient when seeking input and comments. If you do not get an immediate response on an IRC channel, please ask on the phabricator task or wiki page related to the problem.
  • Avoid private emails or support requests in our social media channels.

List of Wikimedia mentors[edit]

Please be patient when seeking actions from mentors. Mentors are humans who eventually leave their computers to sleep, work, study. They might be in different timezones than you. It can take your mentor(s) up to 36 hours to review the work that you have submitted. You should be patient and should not ask for a review of your work after only a few hours of waiting. Google Code-In is about the quality of your contributions and learning how FOSS development works, not about the number of tasks that you have completed.

Name IRC nick IRC channel Timezone Areas of interest
Andre Klapper andre__ #wikimedia-devconnect UTC +1 User documentation, Phabricator
Florian FlorianSW #wikimedia-devconnect UTC+1 mediawiki/core, Special Pages, MobileFrontend
Mvolz Mvolz #wikimedia-servicesconnect, #mediawiki-visualeditorconnect UTC+1 citoid, VisualEditor, TemplateData
Alangi Derick d3r1ck #wikimedia-devconnect, #wikidataconnect GMT +01 Wikidata, Documentation, MobileFrontend, Wikibase, Echo
Mutante mutante #wikimedia-operationsconnect, #wikimedia-techconnect GMT -07 Puppet, Planet, Wikistats
Strainu Strainu #wikimedia-devconnect UTC+2 Gadgets, Templates, Pywikibot
Addshore Addshore #wikimedia-devconnect, #wikidataconnect GMT / UTC MediaWiki, Wikidata, Wikibase, AddWiki, PHP, PHPCS
NKohli (WMF) (talk) Niharika #wikimedia-devconnect UTC +5:30 MediaWiki, PHP, JS
Legoktm legoktm #wikimedia-devconnect, #wikimedia-techconnect, etc. UTC -08 MediaWiki (core + extensions), Pywikibot
John Vandenberg jayvdb #wikimedia-devconnect, #wikimedia-techconnect, etc. UTC +07 Pywikibot
AbdealiJK AbdealiJK #wikimedia-devconnect, #pywikibotconnect UTC +0530 Pywikibot
Samtar Myrcx #wikimedia-devconnect, #wikimedia-techconnect GMT / UTC PHP, JS, Mediawiki
Sage Ross ragesoss #wikimedia-edconnect UTC -08 Ruby, WikiEduDashboard
DrTrigon DrTrigon #wikimedia-devconnect, #pywikibotconnect, etc. UTC +02 Pywikibot
Petrb petan #huggleconnect, #wm-botconnect GMT + 1 Antivandalism stuff, API, C, C++, C#, PHP, Python, UNIX & Labs
Amir Sarabadani Amir1 #pywikibotconnect, #wikidataconnect, GMT +3 Wikidata (Wikibase), pywikibot, ORES
unicornisaurous unicornisaurous #wikimedia-devconnect UTC-5 MediaWiki, PHP, JS, API, and maintenance scripts
Evan McIntire mcintireevan #wikimedia-devconnect UTC-4 MediaWiki, JS, UI
This, that and the other tto #wikimedia-devconnect, #wikipedia-userscriptsconnect UTC+11 MediaWiki core; scripts and gadgets
Srishti Sethi srishakatux #wikimedia-devconnect UTC -8 User documentation, Phabricator
Tony Thomas tonythomas #wikimedia-devrelconnect UTC+01:00 PHP, Newsletter extension
Sumit Asthana codezee #wikimedia-devrelconnect UTC+05:30 PHP, JS, MobileFrontend, WikidataPageBanner
Benoît Evellin Trizek #wikimedia-collaborationconnect UTC +1 Communities, user documentation
Pranav Kumar pranavk #wikimedia-devconnect UTC 5+ː30 MediaWiki, PHP, JS
Isaac Hutt mhutti1 #kiwixconnect GMT Kiwix, Java, Android
Emmanuel Engelhart Kelson #kiwixconnect GMT Kiwix, Java, Android
Dan Andreescu milimetric #wikimedia-analyticsconnect UTC -5 Dashboarding, Analytics APIs (JS, python, data)
Prateek Saxena prtksxna #wikimedia-multimediaconnect UTC +5:30 Gallery, OOjs UI
Bryan Davis bd808 #wikimedia-devconnect, #wikimedia-techconnect, #wikimedia-labsconnect, etc. UTC -07 MediaWiki-Vagrant, Documentation, Tool Labs
Gergő Tisza tgr #wikimedia-devconnect, #mediawiki-coreconnect UTC-8 MediaWiki, Vagrant, Documentation, MediaViewer
Baha bmansurov #wikimedia-mobileconnect UTC-5 MobileFrontend
Jon Robson jdlrobson #wikimedia-mobileconnect UTC-8 mobile
Yann Forget yannf #wikimedia-techconnect UTC +1 Communities, User Documentation, Phabricator, HTML, i18, Commons, Wikisource
Amir E. Aharoni aharoni #mediawiki-i18nconnect UTC+2 Internationalization, translation, languages
Marko Obrovac mobrovac #wikimedia-servicesconnect UTC+1 Services
Petr Pchelko Pchelolo #wikimedia-servicesconnect UTC-7 Services
Tina Johnson tinaj1234 #wikimedia-devrelconnect, tinajohnson.1234@gmail.com UTC+05:30 Newsletter extension, JS, UI
Abhinand N abhinand_ #wikimedia-devrelconnect, #wikimedia-devconnect UTC+05:30 PHP, EditNotify extension
Haritha H haritha_ #wikimedia-devconnect UTC+05:30 PHP, JS, UI Standarization
Charlie Kritschmar Incabell #wikidataconnect, #wikimedia-de-techconnect, #wikimedia-designconnect UTC+1 Documentation, UX, Design, Wikidata
John Broughton UTC-8 UI, user instructional material, user documentation
Reedy Reedy #wikimedia-devconnect UTC MediaWiki
Husn Shujaat Husun #wikimedia-devconnect UTC +5 User documentation, Phabricator
Devi Krishnan devi__ #wikimedia-devconnect UTC +5:30 PHP, UI Standarization
Husn Shujaat Husun #wikimedia-devconnect UTC +5 User documentation, Phabricator
Léa Lacroix LeaAuregann_WMDE #wikidataconnect, #wikimedia-de-techconnect UTC+1 Wikidata, community communication, documentation
Jan Dittrich Jand_WMDE #wikidataconnect, #wikimedia-de-techconnect, #wikimedia-designconnect UTC+1 Documentation, UX, Design, Wikidata
Mr. Stradivarius MrStradivarius #wikimedia-devconnect UTC+9 Lua, JavaScript gadgets
Niklas Laxström Nikerabbit #mediawiki-i18nconnect UTC+2 Internationalization, translation, languages
Sam Wilson samwilson #wikimedia-commtechconnect #wikisourceconnect UTC+8 PHP, MediaWiki extensions, Tool Labs, Wikisource
Volker E. Volker_E #wikimedia-designconnect, #wikimedia-devconnect UTC-8 UI Standardization, OOjs UI, CSS, Accessibility
You? Add yourself above!

Wrap-up blog posts[edit]

At the end of GCI 2016, many students summarized their experience with Wikimedia:

There are also posts by mentors: