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">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>
<div><br></div><div><a href="http://bugs.winehq.org/show_bug.cgi?id=22845">http://bugs.winehq.org/show_bug.cgi?id=22845</a></div><div>- arethusa26@ unexpectedly mentioned that the bug should be fixed by somebody else's specific patch.</div>
<div><br></div><div>Notice both are marked as FIXED, but none of them have been assigned!</div><div><br></div><div>Let'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><div>Or is it fine to just announce, in the bug page, that you'll work on that bug? See, for example, this comment: <a href="http://bugs.winehq.org/show_bug.cgi?id=22264#c9">http://bugs.winehq.org/show_bug.cgi?id=22264#c9</a></div>
<div><br></div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div><br></div><meta http-equiv="content-type" content="text/html; charset=utf-8"><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>
<div><br></div><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's plate vs how many are on somebody's plate. Data! :) At the moment, there are 15 assigned bugs (ignored 11 assigned to wine-bugs@), vs <span class="Apple-style-span" style="font-family: 'bitstream vera sans', verdana, arial, helvetica, sans-serif; font-size: 13px; ">5580 unconfirmed/new/reopened bugs, for the Wine component.</span></div>
<meta http-equiv="content-type" content="text/html; charset=utf-8"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div><br></div><div>Thanks,</div><div>Alex</div><div><br></div><div><br><div class="gmail_quote">
On Thu, May 27, 2010 at 20:00, Paul Vriens <span dir="ltr"><<a href="mailto:paul.vriens.wine@gmail.com">paul.vriens.wine@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 05/27/2010 07:48 PM, belnac wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What about dev work, is any available?<br>
</blockquote>
<br></div>
Did you ever have a look at our bugzilla ;)<br>
<br>
There is plenty of stuff to do besides fixing bugs of course. What you want to do depends on many things like skills, interest, the amount of time you have etc..<br>
<br>
Remember that we are in code freeze now so looking at bugs and trying to figure out what could be wrong or even providing information that could lead to fixing the bugs is welcome.<br>
<br>
-- <br>
Cheers,<br><font color="#888888">
<br>
Paul.<br>
<br>
<br>
</font></blockquote></div><br></div>