So I'm contacting Wikimedia dev teams to please go through their list of Bugzilla tickets and mark open tickets with the "easy" keyword which are "self-contained, non-controversial issues with a clear approach which are recommended to try for new developers."

Details announced today: T764#15252

This time we need to create a Google Form to introdeuce the pre-Melange tasks. From there export to CVS. Then if/when we are accepted, we can upload the CVS.

In T561#12213, @Aklapper wrote:

So I'm contacting Wikimedia dev teams to please go through their list of Bugzilla tickets and mark open tickets with the "easy" keyword which are "self-contained, non-controversial issues with a clear approach which are recommended to try for new developers."

I'm willing to do this for issues tagged "i18n", and I'm totally committed to investing serious time in helping to made GCI a success for Wikimedia and participants.

I've made https://www.mediawiki.org/wiki/Google_Code-in a generic landing page and moved the previous page to https://www.mediawiki.org/wiki/Google_Code-in_2013

...and created an initial version of https://www.mediawiki.org/wiki/Google_Code-in_2014

• DONE: Went through all open "gci2013" tickets in Bugzilla and updated/commented on them. Now 13 tickets with gci2014: https://bugzilla.wikimedia.org/buglist.cgi?resolution=---&status_whiteboard=gci2014&status_whiteboard_type=allwordssubstr
• DONE: Created https://www.mediawiki.org/wiki/Google_Code-in_2014
• TODO: Send generic email to wikitech-l@; contact specific teams and provide Bugzilla queries (more comfortable?)
• TODO: Wikimedia organization to fill out application for GCI
• TODO: Create Google spreadsheet to copy tasks into. I'm happy to copy tasks over (but we always need a mentor defined).
• TODO: Update https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner where/how to "list GCI tasks" (well, should be in Bugzilla but not entirely sure how to identify mentors - proposing a freetext comment).

• DONE: GCI 2014 organization application form filled out for Wikimedia and submitted (It said "Data saved successfully." but I don't 100% trust Google Melange, as it also tells me "Your Student ID and/or Parental Consent forms have not been verified yet.")

• Generic announcement email sent to wikitech-l: https://lists.wikimedia.org/pipermail/wikitech-l/2014-October/079264.html

We need a #Google-Code-in tag, right?

• I've spammed several mailing lists (pywikipedia-l@lwo, mediawiki-i18n@, multimedia@, wikitext-l@, wikidata-l@, qa@, analytics@, labs-l@, mobile-l@) also providing URLs to their latest Bugzilla tickets, existing tickets marked as "easy" in their fields, and open tickets from GCI2013. Kiwix folks have contacted me via email to express interest in GCI2014 and Pywikibot folks expressed interest on the GCI2014 talk page.
• Discussed with Quim how (much) to reach out to gadget community, TemplateData, Village Pumps etc.

In T561#18057, @Qgil wrote:

We need a #Google-Code-in tag, right?

Would probably be a good idea if we define it as "GoogleCode-in tasks that are already listed on Wikimedia's Google Code-in planning page or in Google Melange" to avoid random usage as "potential candidates that have no mentor defined" (that would be pretty much covered by good first task already IMO).

Google-Code-in-2014 ?

Sounds good.

https://www.mediawiki.org/wiki/Google_Code-in_2014#Category:_Outreach.2FResearch is still empty. I wonder whether some work could be done in this direction:

• T951: Compile a List of MediaWiki Third Party Customers
• T953: Mentor Google Code-in 2014 Student(s) Who Compile a List of Top Requested Features
• T1114: Create a survey that MediaWiki users can use to provide us with information
• T1133: Identify Enterprise Wikis from List of Fortune 1000
• T1136: Extract and Sort WikiApiary Database

I'm not saying the students should complete these tasks. I'm just wondering whether subtasks with the size and complexity of Google Code-in could be extracted.

@Palexis, @MarkAHershberger, what do you think? We hope to have hundreds of potential students willing to complete a microtask or two for you.

@Qgil, this is a wonderful idea! We do have research tasks that we can use additional help with. Will work on it now.

• Organization deadline passed 30min ago. We applied (T943).
• ...and we have at least five tasks in each category which is a requirement: https://www.mediawiki.org/wiki/Google_Code-in_2014

• DONE: Google-Code-in-2014 project created in Phabricator
• TODO: Add existing GCI tasks in Phabricator to Google-Code-in-2014 project
• TODO: Send announcement email to wikitech-l@, ask for more tasks
• TODO: ask mentors to register in Melange
• TODO: Update wikipage to say that tasks should be created in Melange directly
• TODO: Import tasks fom wikipage into Melange
• TODO: After Bugzilla data import, add existing GCI tasks which were in Bugzilla to Google-Code-in-2014 project in Phabricator

• DONE: pinged again on Multimedia ml
• DONE: replied to QA asking to define mentors (private thread)
• Started trying to accept "connections" (=mentors) in Google Melange but system does not allow assigning a role (yet?)...

• DONE: Send announcement email that Wikimedia is an accepted org for GCI 2014: https://lists.wikimedia.org/pipermail/wikitech-l/2014-November/079465.html
• DONE: Update wikipage to say that tasks should be created in Melange directly
• I cannot set anybody as "Mentor" in Google Melange yet. I have asked on IRC and filed a bug report: https://code.google.com/p/soc/issues/detail?id=2418

• DONE: Sorted out how to make people Wikimedia mentors in Google Melange. Nice bug...
• DONE: Sent a "Please register in Google Melange for GCI 2014" with instructions to those mentors who have not registered in Melange yet

• DONE: Imported all tasks from wikipage into Melange

@Palexis: Please see https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner and send me a private email to aklapper@wm.o if you need any help. Thank you!

Many folks registered but we really need more tasks until December 1st.
Need to run another recruitment round.

If you have tasks or mentors in mind, don't hesitate and add them!