Have you looked at Bugs Ahoy  already? This tool lists bugs and other
tasks that some mentor has promised to oversee if a new contributor
decides to undertake them. In my experience, this works extremely well –
provided the contributors stay in touch, of course.
On 3/14/13 8:46 PM, Michael Hoye wrote:
> Hi, Carey -
> I'm glad to hear about this; I've got some ideas how we can make this a good experience for you, your students and the veteran Mozilla contributors they'll be working with.
> We're still sorting out how to reliably approach a situation like yours - some of our challenges include making sure the bugs your students accept are a good fit and making sure that the professor understands the time commitment required and outcomes involved, among other things.
> One thing that's very important to us is that the professor we're working with have a degree of expertise, not just in programming, but in specifically up a work environment and getting to work on the Mozilla codebase. There's a certain amount of familiarity with the environment and the people around it that contributors and instructors really need to have before we can have an effective, rewarding relationship.
> To that end, as a first step I'd like you to try taking ownership of and resolving your own "first bug". The challenges of getting your build environment spun up and a simple fix committed for release is an exercise you should really go through, and will give you a much better sense of what your students will be doing, how you can grade it, and where they can go in the community for help.
> - mhoye
> education mailing list
David Rajchenbach-Teller, PhD
Performance Team, Mozilla