lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 17 Apr 2008 21:57:06 +0200
From:	"Sverre Rabbelier" <>
To:	"Ray Lee" <>
Cc:	"Rafael J. Wysocki" <>,
	"David Newall" <>,
	"Jesper Juhl" <>,,
	linux-kernel <>,
	"James Morris" <>,
	"Al Viro" <>,
	"Andrew Morton" <>,
	"Willy Tarreau" <>,,
	"Stephen Clark" <>,
	"Evgeniy Polyakov" <>,
	"Tilman Schmidt" <>,,
	"Mark Lord" <>, "David Miller" <>,,,
Subject: Re: Reporting bugs and bisection

On Thu, Apr 17, 2008 at 9:35 PM, Ray Lee <> wrote:
> On Thu, Apr 17, 2008 at 12:09 PM, Rafael J. Wysocki <> wrote:
>  >  > Finger-pointing, in these extreme cases, gives incentive to improve
>  >  > quality.  It's a positive thing.
>  >
>  >  Sorry, but I have to disagree.  Negative finger-pointing is never a good thing.
>  Correct, but let's be careful here. The original suggestion was,
>  effectively, to get better metrics on the quality of contributions.
>  Those metrics *could* be used for finger pointing, or (my preference)
>  they could be used to direct and allocate our scarce resources: code
>  reviews and mentoring.


>  There's no way to know what the metrics will tell us until we have
>  them. Arguing against metrics because they *may* be used to point
>  fingers at people is a silly argument; anything can be subverted to do
>  that.

Thank you, that should have been said before, you worded it perfectly.

>  Let's get some measurements and see what they say. In the meantime,
>  try to believe that they could be put to good purposes, such as
>  identifying code areas that are tricky for contributors to get right
>  (independent of contributor), or contributors that could benefit from
>  code reviews, etc.

This especially is an area that I plan to focus on and should be very
reliable when finished. As can be read in my application, I plan to
look at how often a piece of code is changed, in what timespan and by
how many different authors.

Thanks for the reply!


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists