Assigning bugs, and how new developers can find bugs to work on

[Alexandru Băluț]

Hi Paul,

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:

http://bugs.winehq.org/show_bug.cgi?id=22263
- julliard@ unexpectedly announced that the bug should be fixed by a
specific patch.

http://bugs.winehq.org/show_bug.cgi?id=22845
- arethusa26@ unexpectedly mentioned that the bug should be fixed by
somebody else's specific patch.

Notice both are marked as FIXED, but none of them have been assigned!

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?

Or is it fine to just announce, in the bug page, that you'll work on that
bug? See, for example, this comment:
http://bugs.winehq.org/show_bug.cgi?id=22264#c9


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. ;)

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 5580 unconfirmed/new/reopened bugs, for the Wine component.

Thanks,
Alex


On Thu, May 27, 2010 at 20:00, Paul Vriens <paul.vriens.wine at gmail.com>wrote:

> On 05/27/2010 07:48 PM, belnac wrote:
>
>> What about dev work, is any available?
>>
>
> Did you ever have a look at our bugzilla ;)
>
> 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..
>
> 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.
>
> --
> Cheers,
>
> Paul.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20100531/6d86ab0a/attachment-0001.htm>