I've had better luck with immediately assigning the bugs to new
contributors, mostly to prevent conflicts with other new contributors.
If the bug is properly opened (with a mentor identified) it shows up on
bugsahoy, and on #introduction we point a lot of people straight there.
As a result we also field a lot of questions regarding "can I work on so
and so" (typically after a "new" bug enters the mix), and the answer is
"yes, if there's no assignee".
Yes, mentors subsequently have to be attentive to abandonment, but this
is an area in which I'd like to moz improve in any case. As you also
suggest, I typically ping contributors with warnings after a week of no
activity, then pro-actively remove the assignee after the second
inactive week.
Without
On 12/19/2014 02:05 PM, Mike Hoye wrote:
On 2014-12-19 1:15 PM, Nicholas Alexander wrote:
Hi Mike, hi m-f-d,
Question: what do you (mhoye) recommend for assigning bugs to
contributors?
I do!
Because abandoned attempts at first bugs are a common occurrence and
they tie up opportunities for other contributors, I've been
recommending that a new contributor who'd like to be assigned a bug
should have a first attempt at a patch submitted for review before
they can be properly assigned the bug.
This sentence - "Once you've put up a patch we'll assign the bug to
you, and help you see it through" seems to strike the best balance
between having enthusiastic contributor stake bugs they can't or don't
complete, and making sure that contributors can feel ownership of the
product.
After that, getting back to those contributors' questions promptly is
key; people who get feedback quickly about their efforts (within 24
hours) are highly likely to be return contributors. If those patches
sit uncommented-on for a week, that person's gone.
- mhoye
_______________________________________________
mobile-firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/mobile-firefox-dev
_______________________________________________
mobile-firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/mobile-firefox-dev
