git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: sverre@rabbelier.nl
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 13:19:20 +0200	[thread overview]
Message-ID: <200805121319.37512.jnareb@gmail.com> (raw)
In-Reply-To: <bd6139dc0805120319s5ad37867k392eff88616b689e@mail.gmail.com>

On Mon, 12 May 2008 12:19, Sverre Rabbelier wrote:
> On Mon, May 12, 2008 at 12:16 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>>
>> One comment: did you take a look at 'owners.sh' script posted some
>> time ago by (IIRC) spearce to check who "owns" egit/jgit and relevant
>> git code?  This is one interesting, and useful, statistics.

First I have to admit that I haven't read your email carefully.
One note: why not provide HTML version in addition to PDF?

> Ah, yes, I did see it, and something similar to that I intend to
> include. I reckon his script would fall under the "Finding a
> Contributor that is active in a specific bit of content" use case.

I don't agree.

This is "Finding the owner of the code" (i.e. something like
non-existent 'git blame --summary') with the goal of "Find who
needs to be contact about changing (or adding) license / relicensing".

This is similar, but not exactly the same as "Find maintainer of given
subsystem", or "Who is responsible for this part of code".


A few use cases I thought about (perhaps repeating what you have wrote,
see note above):

* Maintainer: how close should I examine provided patch?
* Contributor: who is maintainer of the code / whom should I contact
  and send copy of a patch?
* Bug-fixer: who is responsible about this part of code? Who might have
  introduced the bug?
* Contributor: what happened with my code?
* Searching where to contribute: what are oldest part of code dealing
  with error messages (find ancient code)?

HTH
-- 
Jakub Narebski
Poland

  reply	other threads:[~2008-05-12 11:21 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 [this message]
2008-05-12 11:49         ` Sverre Rabbelier
2008-05-12 12:40           ` Jakub Narebski
2008-05-12 13:01             ` Sverre Rabbelier
     [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=200805121319.37512.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=dsymonds@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=spearce@spearce.org \
    --cc=sverre@rabbelier.nl \
    /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).