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

[Nikolay Sivov]

On 5/31/2010 20:01, Alexandru Băluț wrote:
> 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.
Unexpectedly is very questionable word here cause it was a regression.
>
> http://bugs.winehq.org/show_bug.cgi?id=22845
> - arethusa26@ unexpectedly mentioned that the bug should be fixed by 
> somebody else's specific patch.
Anyone could retest a make a note about that.
>
> Notice both are marked as FIXED, but none of them have been assigned!
ASSIGNED state isn't used too often and there's nothing wrong with that.
>
> 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?
>
Pick whatever you want, read through comments to figure out does 
somebody work on it or not and write a fix.
> 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
>
That's fine.
>
> 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. ;)
There's nothing to improve. You could search by component or any way you 
want.
>
> 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.
Why do you need this? git log/blame shows all stats on every person. 
It's a waste of time IMO to go with these ASSIGNED/VERIFIED.

P.S. also I think our bugzilla setup allows to much currently. Along 
with practically unused states I mentioned already there's a difficulty 
field that needs to be removed; it's nice to tweak CC list a bit too to 
block reporter from being CCed.


>
> Thanks,
> Alex

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20100531/39f7e904/attachment.htm>