On 2015-02-04 12:07 PM, Michael Comella wrote:
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?
While you're thinking about this, keep in mind that there will be people
who are interested in being part of the mission for the mission's sake,
and there will be people who are interested in being part of the mission
for the "being part of"'s sake.
I don't have numbers for this, but don't overlook the possibility that
people are more interested in working _with you_ than they are in
working on any specific bug, and that the most motivating part of "I'd
be happy to work with you on bug X" is not really about the technical
challenges of bug X.
- mhoye
_______________________________________________
mobile-firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/mobile-firefox-dev
