Ask yourself:
* 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 )
* Do your old bugs welcome some testing?
* Does your user interface have some small design issues?
* Does the Outreachy/GSoC project you finished welcome small tweaks?
* Would you enjoy helping someone port your template to Lua?
* Does your gadget use some deprecated API calls?
* Do you have some tasks that welcome some research?
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. And Wikimedia will
apply again to take part in GCI!
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
Wikimedia has more than 600 "easy" tasks available:
https://phabricator.wikimedia.org/maniphest/query/609oZQR8EpOH/#R
Can you imagine helping someone fix one of these tasks?
Please ask if you have questions.
Thank you!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/