> > 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'd like to take a slight tangent from this. Thanks for the inspiration, Mike! :D One of the problems we face with fatfennec and other big projects is that it's difficult for volunteers (and paid contributors, for that matter!) to make the jump from [good-first-bug]s to the harder/less well specified/less approachable bugs. That's compounded by over-committed senior folks not finding the time to do enough work to break own those big hairy bugs. We also tend to take an all-or-nothing approach to fixing bugs, so those difficult projects tend to sit. I'd like to get to a place where 'success' wasn't synonymous with 'RESOLVED': where we can leverage our contributor base to incrementally move some of these bugs forward, whether that's by doing investigation (almost triage!), breaking down meta bugs, or even writing up better summaries. That is: can our contributors help our contributors?
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
