Among the jobs in need of a volunteer,  there are some big i18n tasks/projects like bugzilla:24620. These, and perhaps other similar projects, span across many areas of the code, not just a single extension where you can get someone to get +2: does this project somehow cover it, or do you have suggestions?
Some months ago I proposed, for the l10n portal which was in the works:
- «There should be a list of current projects one can be involved in:
- team's projects/specifications/whatever in need of feedback/debugging/tests (mostly pages on mw.o in need of comments and perhaps usability tests);
- long-term projects like translatewiki:Support, bug 38638, adding plural and gender support to messages and other interface elements, switching core and extensions to the new logging system, language support/CLDR improvements, cleanup of wikis' local messages, ...: actionable lists of stuff to do and relevant how-tos.»
I've added some things to Annoying large bugs but never got any of them done, wikitech-l emails are completely useless and core developers are not interested. Today I tried bugzilla:42893 and bugzilla:42892, maybe the Language Engineering team will be able to work on them. Nemo 10:39, 9 December 2012 (UTC)
Starting in 2013, every engineer or sysadmin at WMF has a quarterly goal: either to get more domain knowledge on a particular repository/codebase and become a regular code reviewer on that codebase, or to coach a particular mentee to get +2 privileges on a repo.
The Wikimedia Foundation's technical department has a fair number of employees who are neither engineers nor sysadmins: product managers, engineering directors and other management, Engineering community team, designers, researchers, etc. Since those represent almost 40% of the technical staff, it would be useful to provide some guidelines about how/whether this program will affect them. guillom 13:40, 10 January 2013 (UTC)