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

[Nikolay Sivov]

On 6/1/2010 02:56, Alexandru Băluț wrote:

    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.


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.
You're overestimating a value of this tracking process. Currently a 
really long bug list is available, all you need is to choose a bug that 
fits your interests, put a note and start to fix it.

Thanks,
Alex