Firefox for Android mentor bug groups

[Mike Taylor]

Hi,

On 9/21/15 10:52 PM, Nicholas Alexander wrote:
> On Mon, Sep 21, 2015 at 5:18 PM, Margaret Leibovic
> <mleibovic at mozilla.com <mailto:mleibovic at mozilla.com>> wrote:
>     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].

As someone who isn't part of the Fennec team but likes to contribute, 
I'm always looking for new bugs to work on (if I don't have some kind of 
bug that affects compatibility in mind). A few weeks back Margaret 
emailed about the fatfennec project[1] and that's been a place I've gone 
back to more than once to find a bug I can knock out in a day or two of 
spare time. What's cool about that meta bug is there's a range of super 
easy (remove some unused images or JS files) to insane sounding if 
you're not a Gecko hacker (figure out libxul size increase), so you can 
kind of navigate where you want to go next within the project.

> 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.

+1. I like the idea of writing down context and goals, and where to go 
to for help, etc.

[1] <https://bugzilla.mozilla.org/show_bug.cgi?id=fatfennec>

-- 
Mike Taylor
Web Compat, Mozilla