[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Detail Reporting tool for Subversion

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 13 Aug 2008 13:00:50 -0400

On Wed, Aug 13, 2008 at 12:46, Phil Pinkerton <pcpinkerton_at_gmail.com> wrote:
> Anyone know of a detail reporting tool for subversion ? Preferably
> Open Source flavor ?
> We would like to get some stats on items like how many lines of code
> were modified , how many times a file was modified, how many
> checkouts/ins, who did the checkout/in etc.

I'm curious what can actually be gained by attempting to measure these
sorts of things.

Shamelessly quoting myself from 2 weeks ago (July 28) when someone
else asked about this [1]:

"Commits per developer is a really bad metric. If you're evaluating
developers on the number of commits, you're just going to push them to
perform more commits. Moreover, no two commits are "equal" - you could
have one commit that touches half the files in your project that
brings it crashing down, and then a second commit that changes one
value in a config file which brings it back."

But I prefer Karl Fogel's more succinct summary in that same thread:

"Measure the quality of a programmer by the number of commits she
makes is like measuring the quality of a legislature by the number of
laws it passes."

A more humorous take on it: http://thedailywtf.com/Articles/Productivity-20.aspx

1: http://svn.haxx.se/users/archive-2008-07/1108.shtml

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-13 19:01:21 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.