Today I chatted with dboswell (in CC). The Mozillians Phonebook project is going to be very useful for point 2 in comment 0. But it is still monthes away. We should carry on with the wiki page idea for now and let the Phonebook team know about our needs so we can eventually merge into it.
(In reply to Benoit Jacob [:bjacob] from comment #0) > 1. File bugs as early as we identify TODO items. Put mentor=yourbugzillaid > in the Status Whiteboard field. Take 5 min to write a detailed explanation > and give context (explain how it relates to other bugs) in the bug > description. This mentor= syntax is standard, other teams are using it > already. This is very important and I would like to see more of these from us. I've started doing this and have had interest in a few bugs. Out of the 3 people I've answered questions one posted a promising patch: https://bugzilla.mozilla.org/show_bug.cgi?id=678324
There are definitely some good ideas already in this bug (such as tagging bugs with mentor= and keeping that list up to date) so we can spin those off as separate dependent bugs. We may also want to work together with other people looking to make similar improvements. As mentioned earlier, Josh Matthews has been doing a lot with onboarding people interested in coding and several other people have also expressed interest in being a coding Steward. For reference see: https://wiki.mozilla.org/Stewards/Coding For example, if we do create a curated list of mentored Gfx bugs, that will give Josh a good list to choose from when people show up and are interested in having a specific task to start with.
From bjacob's great intro on bug 728354, I threw together https://wiki.mozilla.org/Platform/GFX/WebGL/Contribute/Extensions instead of writing similar boilerplate for the handful of other extension mentor-bug opportunities we have.