On Mon, Sep 21, 2015 at 5:18 PM, Margaret Leibovic <[email protected]> wrote:
> 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]. > I have argued in favour of this approach, have offered larger projects [1] [2], and have managed to arrange this a few times: first, with Vivek's Firefox Accounts avatars work [3]; and second, with Ahmed's Sync telemetry work [4]. (A round of applause, please, for Vivek and Ahmed.) I don't care about how the tickets are structured; it's my opinion that an overview blog post (which might be a detailed meta bug description) or a kick-off face-to-face is worth more than Bugzilla organization. I have found it extraordinarily difficult to provide enough over-arching context to make the large project approachable. But I'm still in favour. Yours, Nick [1] http://www.ncalexander.net/blog/2015/07/05/nalexander-community-update-part-the-first/ [2] http://www.ncalexander.net/blog/2015/07/15/nalexander-community-update-part-the-second/ [3] https://bugzilla.mozilla.org/show_bug.cgi?id=fennecavatars [4] https://bugzilla.mozilla.org/show_bug.cgi?id=1180321
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
