Detail Reporting tool for Subversion

[Phil Pinkerton <pc...@gmail.com>]

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.

thanks

Phil


-- 
" The fundamental principle here is that the justification for a
physical concept lies exclusively in its clear an unambiguous relation
to the facts it can be experienced" AE

Please Feed and Educate the Children... it's the least any of us can do.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Detail Reporting tool for Subversion

[Gaurav Kothiyal <ko...@gmail.com>]

http://www.statsvn.org/ (open source)
http://www.atlassian.com/software/fisheye/


On 8/13/08, Phil Pinkerton <pc...@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.
>
> thanks
>
> Phil
>
>
> --
> " The fundamental principle here is that the justification for a
> physical concept lies exclusively in its clear an unambiguous relation
> to the facts it can be experienced" AE
>
> Please Feed and Educate the Children... it's the least any of us can do.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>


-- 
Gaurav Kothiyal

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Detail Reporting tool for Subversion

[Quinn Taylor <qu...@mac.com>]

>> 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:
>
> "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

To begin with, I agree with these statements. Blindly assuming that a  
given metric is equivalent to a developer's productivity is asinine,  
and the stuff of legend.

However, I think it's humorous that people are so quick to opine that  
such metrics are worthless. Consider this: since you're on the  
Subversion users mailing list, odds are that you know what you're  
doing and that (if you write code) you're a reasonably productive  
programmer. However, we all know that not everyone is so productive.

I was in a group last year that had several contracted employees (I  
was an intern) whose productivity was hit-and-miss. It was hard for  
the manager to keep tabs on everyone, and he had to double-check that  
they were actually accomplishing what they claimed they were.  
Obviously, even the coders who wrote lots of lines and committed  
frequently had errors that needed to be corrected.

Statistics provided by StatSVN were just one piece of the puzzle. Say  
what you will, but the graphs clearly demonstrated that certain people  
were doing almost nothing in the repository. They contributed almost  
no lines of code, committed extremely infrequently, etc. The point of  
statistics is that they give you numbers which you can interpret  
(hopefully intelligently) to help solve a problem. My boss was a smart  
guy, and was able to better manage his deadlines when he had a better  
idea of what was actually happening. By no means was reward based on  
LOC or commits—he just knew where to keep an eye out. (Linking such  
statistics with results from BuildBot or something similar can further  
improve the results.)

The funny thing is that all the information that StatSVN provides is  
cleaned from the SVN repository itself; it just puts it in forms that  
are easier to interpret. For example, I wouldn't want to scan through  
logs to see what authors' commit patterns are like, or add up how many  
lines changed, or try to figure out if people are working on the  
modules they're assigned to. Stats are not infallible, but they're  
also not useless. In commercial development situations, metrics such  
as these are more important than when developing OSS, like it or not.

My 2¢,
   - Quinn

Re: Detail Reporting tool for Subversion

[Ryan Schmidt <su...@ryandesign.com>]

On Aug 13, 2008, at 12:00, Andy Levy wrote:

> 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

And let's not forget:

http://folklore.org/StoryView.py? 
project=Macintosh&story=Negative_2000_Lines_Of_Code.txt


I don't usually care how many commits someone does, rather what  
changes they make. I try to review every commit that comes across the  
commit mailing list for the MacPorts project (with exceptions for  
some areas of the code I'm not familiar with) and sometimes I spot  
coding errors or style issues and can reply immediately and let the  
committer know. I'm more of a programmer than a manager; maybe a  
manager would have a tougher time knowing whether the stuff flying by  
in the commit emails is good or bad. Nevertheless, simply enabling  
commit mails provides a manager with some level of overview over the  
progress of the project.

I admit that it doesn't necessarily make it easier to see what  
*isn't* being done. Reading the commit mails gives me a good handle  
on the fact that for example Paul and George have been working on  
their GSoC projects and that Matthew and Eric and Markus have been  
working on their ports, but it doesn't make it immediately obvious  
that for example James and Juan Manuel haven't made any commits in  
awhile. A reporting tool could be useful for that. Especially if it's  
integrated with your office calendar such that you can say "Oh, yes,  
Bob hasn't made any commits in two weeks, but that's ok because I see  
he's on vacation" vs. "Billy hasn't made any commits in two weeks but  
I see him at lunch every day and come to think of it I hear World of  
Warcraft coming from his cubicle right now."



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Detail Reporting tool for Subversion

[Andy Levy <an...@gmail.com>]

On Wed, Aug 13, 2008 at 12:46, Phil Pinkerton <pc...@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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org