git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sverre Rabbelier" <srabbelier@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>,
	"David Symonds" <dsymonds@google.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [RFC] Use cases for 'git statistics'
Date: Mon, 12 May 2008 15:01:14 +0200	[thread overview]
Message-ID: <bd6139dc0805120601k45ab762eq78c7d6a4927059f6@mail.gmail.com> (raw)
In-Reply-To: <200805121440.12836.jnareb@gmail.com>

On Mon, May 12, 2008 at 2:40 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>  This is, IMHO, the most complex example (at least to do properly).
>  It begins with: does given author have code touching given subsystem
>  (i.e. is it for him/her new contribution wrt. subsystem)? How many
>  commits he/she has affecting given subsystem? How often he/she rewrites
>  code? How many bugs were introduced?

Ah, there is a lot more to this example than I thought. Perhaps this
data could all be shown and then, using some "importance" metric per
item a "grade" can be calculated?

>  Details I think need to be provided by maintainer...
>
>
>  > >  * Contributor: what happened with my code?
>  >
>  > Do you mean a "track my code" like feature? Showing the movement of a
>  > particular piece of code through the code? (Displaying information
>  > like "moved from foo.c to bar.c in commit 0123456789abcd"?)
>
>  I was thinking there about "git blame --reverse".
>
>
>  > >  * Searching where to contribute: what are oldest part of code dealing
>  > >   with error messages (find ancient code)?
>  >
>  > In other words, find the lines with the oldest modification time stamp
>  > from 'git blame'?
>
>  Or find the lines with oldest modification stamp with "die" or "warn",
>  or find which messages are oldest, even if wrapper have changed.
>
>
>  P.S. I wonder how hard to be to plug-in such SCM statistic system
>  into something like project management, see
>   "Joel On Software: Evidence based scheduling" (of programming tasks)
>   http://www.joelonsoftware.com/items/2007/10/26.html
>
>  --
>  Jakub Narebski
>  Poland
>



-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2008-05-12 13:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 15:51 [RFC] Use cases for 'git statistics' Sverre Rabbelier
2008-05-12  9:38 ` Sverre Rabbelier
2008-05-12 10:16   ` Jakub Narebski
2008-05-12 10:19     ` Sverre Rabbelier
2008-05-12 11:19       ` Jakub Narebski
2008-05-12 11:49         ` Sverre Rabbelier
2008-05-12 12:40           ` Jakub Narebski
2008-05-12 13:01             ` Sverre Rabbelier [this message]
     [not found]             ` <bd6139dc0805120604m349b1fbbr39c6dcb8d893e771@mail.gmail.com>
2008-05-13 13:07               ` Jakub Narebski
2008-05-13 13:37                 ` Sverre Rabbelier
2008-05-14 20:34                   ` Jakub Narebski
2008-05-15 12:21                     ` Andreas Ericsson
2008-05-17  0:02                   ` Junio C Hamano
2008-05-18  1:01                     ` Sverre Rabbelier
2008-05-21 17:30                     ` Junio C Hamano
2008-05-21 20:52                       ` Sverre Rabbelier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bd6139dc0805120601k45ab762eq78c7d6a4927059f6@mail.gmail.com \
    --to=srabbelier@gmail.com \
    --cc=dsymonds@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).