On Tue, Jan 27, 2015 at 1:19 PM, Mike Hoye <[email protected]> wrote:
> I think you're overcomplicating things with second/third bugs, tbh. We've > got good-first, good-next, diamond and experience-required as categories, > as described here: > > https://wiki.mozilla.org/Contribute/Coding/Mentoring > Thanks for the tips - I added some discussion points for our next meeting. > > ... but rather than expect users to search on and find good-Nth bugs, > you'll have far more success (and way better retention!) by pointing newish > contributors to a next bug after they've completed a first one rather than > hoping that they'll pick one up themselves. I'd like to try doing both: "I recommend bug X for front-end work, Y for back-end work, and Z if you want a challenge. But if these are uninteresting, see the full list of good second bugs!" I find that the recommended bugs are usually the chosen ones, but I wonder if some contributors have something they're extremely interested in and limiting their choices holds them back. But at the same time, I can see a counter-argument for decision paralysis. Perhaps a bug list is better for the [good third bug] (or fourth!) case?
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
