<div dir="ltr"><div dir="ltr"><div>Interestingly, the DevTools team was discussing this specific point a week or 2 ago, and decided the do the exact opposite:</div><div>assigning the good-first-bug as soon as someone claims it, so as to "secure" it and avoid people working on the same thing at the same time.</div><div>The team also agreed to go and check assigned bugs on a regular basis, and unassign any that haven't actually been worked on.</div><div>There's a feature in bugzilla that can help with that: whine: <a href="https://bugzilla.mozilla.org/editwhines.cgi">https://bugzilla.mozilla.org/editwhines.cgi</a></div><div><br></div><div>I actually set it for myself to receive a weekly email containing the list of assigned DevTools bugs that haven't been touched in a month (I would like to reduce this to 1 or 2 weeks, but the initial list of bugs that matched was too long, so while I'm cleaning it up, I left the duration to 1 month).</div><div><br></div><div>I totally agree though with Gijs' comments about checking a contributor's profile and making sure they are, indeed, a first-time contributor.<br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 18, 2019 at 8:29 PM Jared Wein <<a href="mailto:jaws@mozilla.com">jaws@mozilla.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Thanks Gijs, I'd like to reiterate your point.</div><div><br></div><div>I just came across a new contributor that is assigned to 11 open bugs. Of these, the contributor has patches on 4 of them. This contributor often comments on bugs saying that they would like to work on the bug and can it be assigned to them. Many of these bugs have had no activity on them for about since they were assigned, about 8 to 9 days ago.</div><div><br></div><div>This is unfair to other new contributors who want to find a good-first-bug or a mentored bug, as this person has taken a large number of them. Further, as Gijs pointed out, after someone has fixed one or two good-first-bugs, they should start working on harder bugs.</div><div><br></div><div>When a new contributor asks if they can work on a bug, please do not assign them to the bug until a patch is attached. It is simple enough to say, "Thanks for your interest. I will assign this bug when a patch is attached. Until then, it is fair game for anyone to work on this bug."</div><div><br></div><div>This should help reduce confusion as some contributors are afraid to work on a bug in fear of upsetting another contributor who "might" be working on the bug.</div><div><br></div><div>Thanks,</div><div>Jared<br></div><div><div class="gmail-m_4767927333373016628gmail-comment-text gmail-m_4767927333373016628gmail-markdown-body" id="gmail-m_4767927333373016628gmail-ct-3">
</div>
</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 12, 2019 at 10:46 AM Gijs Kruitbosch <<a href="mailto:gijskruitbosch@gmail.com" target="_blank">gijskruitbosch@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>While we're on the subject, I'd also like to encourage people to
not blindly assign people to mentored and good first bugs when
requested, but check user profiles first (click their username on
bugzilla, then click 'profile' in the dropdown).</p>
<p>good-first-bug and mentored bugs are meant to provide new people
a straightforward way to "find their feet", get used to bugzilla
and phabricator, etc. They're not meant for people to repeatedly
prove they can fix trivial bugs in 5 minutes once they're used to
the systems.<br>
</p>
<p>I don't want (and it's not my place) to impose hard limits here,
so use your own judgment - but when a contributor wants to be
assigned what would be their 5th or 10th bug, it's probably a good
idea to have a conversation about more difficult/interesting work
that they could be doing, whether there are particular parts of
the codebase that they want to get to know better, etc. This
hopefully helps that contributor do more meaningful work, it helps
free us up, and it helps other new people who can then take the
gfb/mentored bugs instead.<br>
</p>
<p>Thanks,<br>
Gijs<br>
</p>
<div class="gmail-m_4767927333373016628gmail-m_2533534536698262307moz-cite-prefix">On 11/03/2019 20:08, Sam Foster wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi all, <br>
</div>
<div><br>
</div>
<div>With Outreachy and GSoC kicking off, we are currently
running very low on good-first-bugs for potential Firefox
desktop contributors. Could I ask you to spend a few minutes
this week to identify and tag a few in your module or areas of
interest? <br>
</div>
<br>
<div>Thanks, <br>
</div>
<div>/Sam</div>
<div><br>
</div>
</div>
<br>
<fieldset class="gmail-m_4767927333373016628gmail-m_2533534536698262307mimeAttachmentHeader"></fieldset>
<pre class="gmail-m_4767927333373016628gmail-m_2533534536698262307moz-quote-pre">_______________________________________________
firefox-dev mailing list
<a class="gmail-m_4767927333373016628gmail-m_2533534536698262307moz-txt-link-abbreviated" href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>
<a class="gmail-m_4767927333373016628gmail-m_2533534536698262307moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/firefox-dev" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a><br>
</blockquote></div>
_______________________________________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a><br>
</blockquote></div>