Get those small bugs fixed by new contributors: It's Google Code-In time! - Design

2 Nov 2015

* Does some user interface have small design issues?
* Do you have some tasks that welcome some design research?
* Do your old bugs welcome some testing?
* Does your documentation need improvements?
* Do you have small, self-contained, "easy" bugs you'd love to get fixed?
  (Also see https://www.mediawiki.org/wiki/Annoying_little_bugs )

Google Code-In (GCI) will take place again in Dec+Jan: a contest for
13-17 year old students to provide small contributions to free software
projects. 
Wikimedia will apply again to take part in GCI. The more tasks we can
offer the likelier the changes Wikimedia will get accepted.

Unsure about quality of contributions and effort?
Read about tgr's post about Multimedia achievements in GCI 2014:
https://lists.wikimedia.org/pipermail/multimedia/2015-January/001009.html

In short:
* Add the project "GCI2015" + a comment to Phabricator tasks you'd mentor.
* Tasks are welcome in five areas: Code; Outreach/Research; 
  Documentation/Training; Quality Assurance; User Interface.
* Make sure the task description provides pointers to help the student.
* Add yourself to the table of mentors on the wikipage.
* "Beginner tasks" (<30 min for an experienced contributor) also welcome.
* "Generic" tasks also welcome (e.g. "Fix two user interface messages from
  the "Blocked By" list in https://phabricator.wikimedia.org/T40638 ").
For all information, check 
https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner

27 "easy" Design tasks (are they still valid? are there more?):
https://phabricator.wikimedia.org/maniphest/query/ePvtv_ahPMrx/#R

Can you imagine providing a helping hand to someone fixing tasks?

Please ask if you have questions!

Thank you!
andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/