prakash tiwary wrote:
> I agree commits per developer is a bad metric, but it is useful in
> extreme cases. If you use it over the long span, Its gives you an
> indication to over all performance.
> Think a case, where the average commit of a developer is very less
> than others members, say for example 3 times in a month or two months,
> where as the others have around 20 . This is an indication that work
> is not proportionally distributed as per role or some thing wrong
> happenings. This metric will be used to identify where you want to
> ask questions. This metric is proven to be useful in offshore
This isn't for performance statistics for the developer but rather to
monitor that the commits are happening. We are continually faced with
developers not checking in for days or weeks at a time and that is not
our business model.
We have commit hooks we can modify if needed and log the commits to a
database and report off of that daily but I was looking to see what
others have already done.
Again, I was looking to get a general feel for what tools/reports were
available. Sometimes you don't know what is useful until you see what
others have used / needed.
> On Mon, Jul 28, 2008 at 5:51 PM, Andy Levy <andy.levy_at_gmail.com
> <mailto:andy.levy_at_gmail.com>> wrote:
> On Mon, Jul 28, 2008 at 07:25, Eugene Vital <evital_at_egntech.com
> <mailto:evital_at_egntech.com>> wrote:
> > I was looking to see if there was anything available so I could
> get a
> > broader scope of what's out there.
> > Server statistics is one.
I guess Server Statistics is a bad term. How about Repo Statistics? Disk
usage, free space etc....
> What are "server statistics"?
> > We would also like to see general statistics like commits per
> > what code is getting the most changes etc... In general the
> basic reports
> > one would need to manage the repository on a day to day basis.
> I've heard good things about StatSVN, but have never felt much of a
> need for any of the things you describe in the course of managing the
> repository. You're really talking about trying to find metrics for
> managing your /developers/, not the repository.
> FYI, 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.
> > prakash tiwary wrote:
> >> Hi Eugene,
> >> What king of reports you are looking at? Is it svn server
> statistics? We
> >> are into the same business. Could you please give more details?
> >> Regards
> >> Prakash
> >> On Mon, Jul 28, 2008 at 4:08 PM, Eugene Vital
> <evital_at_egntech.com <mailto:evital_at_egntech.com>
> >> <mailto:evital_at_egntech.com <mailto:evital_at_egntech.com>>> wrote:
> >> Are there any good reporting packages available for Subversion?
> >> Commercial or Open Source is fine.
> >> Thanks.
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-29 11:43:11 CEST