While this is a neat idea, it seems to fall to the same problem I've seen elsewhere, little to no transparency as to where a project is going. For example, I was suggested Shumway (JS flash emulator). I'm sent to the github page for it (https://github.com/mozilla/shumway). They give a small summary and a little info on getting an installation working. Nothing however I can see on where a new contributor would start with helping out. No road-map, no "we need this feature and no one has claimed to work on it yet", this bug needs to be fixed for the next release, etc.
I'll admit I've never contributed to FOSS so maybe a veteran can fill me in but I see this a lot with projects. Some have decent issue/bug tracking, but I often find it very difficult to determine how a project is supposed to progress, what features are needed for the next release, where do they stand currently, etc. I assume a lot is decided out-of-band through e-mails and IRC.
To be fair, shumway has not as many people as Gecko or other big Mozilla projects to do triage and things for the newcomers, the shumway team being minuscule and the project an ongoing effort.
If you want to contribute to a Mozilla project, but can't figure out how you can help, please come on irc (irc.mozilla.org), usually on #nameoftheproject (here #shumway), or in #introduction if you want something more generic.
I'll admit I've never contributed to FOSS so maybe a veteran can fill me in but I see this a lot with projects. Some have decent issue/bug tracking, but I often find it very difficult to determine how a project is supposed to progress, what features are needed for the next release, where do they stand currently, etc. I assume a lot is decided out-of-band through e-mails and IRC.