Hi team, I've been thinking about how we can help new contributors work their way up to more substantial coding contributions, and I'd like to see if we can experiment with grouping our mentor bugs into small mentor projects. This doesn't need to be a large project broken into chunks, like "Implement XYZ API", but rather a set of bugs that focus on one area of the code base, or one goal (e.g. reduce the number of drawable resources in the tree). Ideally these would be bugs that wouldn't require too much guidance or back-and-forth to get started on.
I'm not sure of the best way to implement this idea, but I feel like using meta bugs would be an easy way to do it. Ideally each meta bug would have a few [good first bugs], a few [good next bugs], and maybe some [advanced] or [challenge] bugs. Multiple people could work on any given meta bug, but it would give motivated individuals an easy way to find new bugs to work on. What do you all think? Does anyone know of any good candidates for this off the top of your head? We could add a new wiki Bugzilla query to our Get Involved page [1] to list these meta bugs. Or if we're feeling fancy, we could make a PR for bugsahoy [2]. Margaret [1] https://wiki.mozilla.org/Mobile/Get_Involved [2] http://www.joshmatthews.net/bugsahoy/
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
