Re: Reporting bugs and bisection

From: Sverre Rabbelier <alturin@gmail.com>
Date: Apr 16, 2008, 21:05 UTC
Message-ID: <bd6139dc0804161405j28470914u488568b565b68a0b@mail.gmail.com>
In-Reply-To: <20080416205333.GT1677@cs181133002.pp.htv.fi>

On Wed, Apr 16, 2008 at 10:53 PM, Adrian Bunk <bunk@kernel.org> wrote:

>  To avoid any misunderstandings:
>
>  This is not in any way meant against you personally.

Thanks for pointing it out, I wasn't quite sure, but assumed that :).

>  But saying things like " X% of your commits introduced bugs" is not a
>  friendly thing, and wrong data could be quite hurting.

Yes, it could be, and I agree that conclusions shouldn't be based on the details, but on the bigger picture. Also, I think it should (at first) be used mainly as an indicator, of where attention might be required. I mean, if it points out that one contributor almost always commits buggy code, you don't have to present them with those statistics right away. Instead you can ask the program where it bases it's conclusions on, and research them yourself. If it does indeed turn out that they are slacking that much you have good ground to have a talk with them.

>  Especially in the open source world where much motivation comes from
>  people being proud of their work.

Yes, that is very true, I very much agree with that, but on the other hand it might also point out contributors that are particularly skillful in a certain section that was previously not noted. As with all statistics, it's up to interpretation, misinterpreting statistics could -always- have bad effects.

>  Even correct data can do harm.
>
>  And bad data can have really bad effects.

True, both, but as said, if properly interpreted it could be very useful.

Cheers,

Sverre Rabbelier