Hi Nikolay,<br><br><div class="gmail_quote">On Mon, May 31, 2010 at 18:27, Nikolay Sivov <span dir="ltr">&lt;<a href="mailto:nsivov@codeweavers.com">nsivov@codeweavers.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">




  

<div bgcolor="#ffffff" text="#000000"><div class="im">
On 5/31/2010 20:01, Alexandru Băluț wrote:
<blockquote type="cite">Hi Paul,
  <div><br>
  </div>
  <div>I was wondering what is the best way to pick bugs, for a
developer aspiring to fix nonspecific Wine bugs. Normally, our hero
would look at the unassigned bugs to find one to work on. For some
bugs, a fix appeared with no notification that somebody is working on
them, for example:</div>
  <div><br>
  </div>
  <div><a href="http://bugs.winehq.org/show_bug.cgi?id=22263" target="_blank">http://bugs.winehq.org/show_bug.cgi?id=22263</a></div>
  <div>- julliard@ unexpectedly announced that the bug should be fixed
by a specific patch.</div>
</blockquote></div>
Unexpectedly is very questionable word here cause it was a regression.</div></blockquote><div><br></div><div>The bissection did pinpoint the commit that caused the bug, and its author, but you still have to read the comments to figure that out, when it would have been easier to immediately see that the bug is assigned, and just leave it alone. (I&#39;m talking from the point of view of a newbie Wine developer who is looking for a bug to fix.)</div>

<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor="#ffffff" text="#000000"><div class="im"><blockquote type="cite"><div><a href="http://bugs.winehq.org/show_bug.cgi?id=22845" target="_blank">http://bugs.winehq.org/show_bug.cgi?id=22845</a></div>


  <div>- arethusa26@ unexpectedly mentioned that the bug should be
fixed by somebody else&#39;s specific patch.</div>
</blockquote></div>
Anyone could retest a make a note about that.</div></blockquote><div><br></div><div>Yes, anyone who retests can make a note about that.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div bgcolor="#ffffff" text="#000000"><div class="im"><blockquote type="cite"><div>Notice both are marked as FIXED, but none of them have been
assigned!</div>
</blockquote></div>
ASSIGNED state isn&#39;t used too often and there&#39;s nothing wrong with that.</div></blockquote><div><br></div><div><div>I&#39;m not saying it&#39;s wrong if people don&#39;t use it, I&#39;m saying it&#39;s useful when people use it.</div>

</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor="#ffffff" text="#000000"><div class="im"><blockquote type="cite"><div>Let&#39;s say our hero picks a bug; should he ask on the bug page
whether anybody is already working on it, or ask on wine-devel, or
#wine-hackers?</div>
  <div><br>
  </div>
</blockquote></div>
Pick whatever you want, read through comments to figure out does
somebody work on it or not and write a fix.<div class="im"><br>
<blockquote type="cite">
  <div>Or is it fine to just announce, in the bug page, that you&#39;ll
work on that bug? See, for example, this comment: <a href="http://bugs.winehq.org/show_bug.cgi?id=22264#c9" target="_blank">http://bugs.winehq.org/show_bug.cgi?id=22264#c9</a></div>
  <div><br>
  </div>
</blockquote></div>
That&#39;s fine.</div></blockquote><div><br></div><div>Ok. I personally don&#39;t like to pollute the bug log with &quot;I&#39;ll work on this&quot; messages. But I guess for newbie developers, who don&#39;t have bugzilla rights to change the Assigned field, it&#39;s the only solution.</div>

<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor="#ffffff" text="#000000"><div class="im"><blockquote type="cite"><div>Any suggestions about improving this process are welcome. I
think people will show up, wanting to help, and it would be nice to
 help them find something to work on fast. ;)</div>
</blockquote></div>
There&#39;s nothing to improve. You could search by component or any way
you want.</div></blockquote><div><br></div><div>I realized while writing this email.. the process of searching a bug nobody is working on can be improved.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div bgcolor="#ffffff" text="#000000"><div class="im"><blockquote type="cite"><div>In the meanwhile, please assign the bugs, and spare others of
spending time on them. As a bonus, it would be nice to see accurate
numbers about how many bugs are on nobody&#39;s plate vs how many are on
somebody&#39;s plate. Data! :) At the moment, there are 15 assigned bugs
(ignored 11 assigned to wine-bugs@), vs <span style="font-family:&#39;bitstream vera sans&#39;,verdana,arial,helvetica,sans-serif;font-size:13px">5580
unconfirmed/new/reopened bugs, for the Wine component.</span></div>
</blockquote></div>
Why do you need this? git log/blame shows all stats on every person.
It&#39;s a waste of time IMO to go with these ASSIGNED/VERIFIED.<br></div></blockquote><div><br></div><div>The git log shows what you did. This would show how much you have to do (rough approximation, of course). btw, how exactly do you keep track of what you have to do? Having bugs assigned looks like a way of managing your todo-s.</div>

<div><br></div><div>Thanks,</div><div>Alex </div></div>