On Tue, 2014-11-04 at 00:44 +0330, Amir Ladsgroup wrote:

Anyone interested? please tell if you're interested :)

...and just in case there are potential mentors from countries that are not eligible by US laws (section 2 of [1]), you could add a sentence to the GCI task description that all communication must happen in the corresponding Phabricator/Bugzilla bug report instead of Google Melange and I can do the proxy work for you in Google Melange.

andre

[1] https://www.google-melange.com/gci/document/show/gci_program/google/gci2014/...

On 11/3/14, Andre Klapper aklapper@wikimedia.org wrote:

...

Hi Pywikibot crew,

Google Code-In (GCI) will soon take place again - a contest for 13-17 year old students to contribute to free software projects.

Wikimedia wants to take part again. Last year's GCI results were surprisingly good - see https://www.mediawiki.org/wiki/Google_Code-in_2013

We need your help:

1. Go to

https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner and read the information there. If something is unclear, ask!

2. Add yourself to the table of mentors on

https://www.mediawiki.org/wiki/Google_Code-in_2014#Contacting_Wikimedia_ment...

• the more mentors are listed the better our chances are that Google

accepts us.

3. Please take ten minutes and go through open recent tickets in

https://bugzilla.wikimedia.org in your area of interest. If you see self-contained, non-controversial issues with a clear approach which you can recommend to new developers and would mentor: Add the task to https://www.mediawiki.org/wiki/Google_Code-in_2014#Proposed_tasks

Until Sunday November 12th, we need at least five tasks from each of these categories (plus some less technical beginner tasks as well):

• Code: Tasks related to writing or refactoring code
• Documentation/Training: Tasks related to creating/editing documents

and helping others learn more - no translation tasks

• Outreach/research: Tasks related to community management,

outreach/marketing, or studying problems and recommending solutions

• Quality Assurance: Tasks related to testing and ensuring code is of

high quality

• User Interface: Tasks related to user experience research or user

interface design and interaction

Google wants every organization to have 100+ tasks available on December 1st. Last year, we had 273 tasks in the end.

Note that you could also create rather generic tasks, for example fixing two interface messages from the list of dependencies of https://bugzilla.wikimedia.org/show_bug.cgi?id=38638

Potentially helpful Bugzilla links:

• Reports that were proposed for GCI last year and are still open:

https://bugzilla.wikimedia.org/buglist.cgi?quicksearch=ALL%20whiteboard%3Agc...

• Open Pywikibot tickets created in the last six months (if I got your

products and components right): https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_st...

• 19 already existing Pywikibot "easy" tickets (are they still valid?):

https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_st...

Could you imagine mentoring some of these tasks?

Thank you for your help in reaching out to new contributors and making GCI a success again! Please ask if you have questions.

Cheers, andre

PS: And in a future Phabricator world, Bugzilla tickets with the 'easy' keyword will become Phabricator tasks with the 'easy' project. -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

---

Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l