From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Shawn Pearce <spearce@spearce.org>,
git@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: git as an sfc member project
Date: Sat, 23 Oct 2010 11:52:26 +0000 [thread overview]
Message-ID: <AANLkTikxMtdvppLur4kuXffRn0G29NFv6ameTpaeY46G@mail.gmail.com> (raw)
In-Reply-To: <20101022231820.GB25520@sigill.intra.peff.net>
On Fri, Oct 22, 2010 at 23:18, Jeff King <peff@peff.net> wrote:
> On Fri, Oct 22, 2010 at 03:59:36PM -0700, Junio C Hamano wrote:
>
>> Shawn Pearce <spearce@spearce.org> writes:
>>
>> > I think a committee of at least 3 people and at most 5, any of whom
>> > can be a benevolent SFC liasion, is fine. As far as selection goes,
>> > the committee can elect or remove a member through a majority vote,
>> > and should base its decisions based on surviving contributions to the
>> > code base, but shouldn't be tied to that (just in case someone
>> > contributes a lot of good code and then becomes a jerk).
>>
>> Just a datapoint from quick "blame -C -C -w" run as of 1.7.3.2, counting
>> surviving lines, 7 top from each area, excluding Documentation/RelNotes.
>>
>>
>> ** Everything else **
>>
>> 77212 Junio C Hamano
>> 41388 Shawn O. Pearce
>> 32676 Linus Torvalds
>> 28618 Johannes Schindelin
>> 22120 Ævar Arnfjörð Bjarmason
>> 20190 Paul Mackerras
>> 15518 Marius Storm-Olsen
>
> How did you calculate this? I don't see how it could be right. For
> example, Ævar's contribution, while being impressively large lately, is
> only 12877 lines total over all commits, let alone surviving lines:
>
> $ git log --pretty=format: --numstat --author=Bjarmason |
> perl -ne '/^\d+/ and $total += $&; END { print "$total\n"; }'
> 12877
Either way it doesn't matter, since I'm not interested in being a SFC
liasion. I just want to hack, not deal with issues like these (but
more power to people who want to).
But I think picking people for anything based on the number of lines
that git-blame thinks people "own" is a bad criteria. My contributions
to Git are relatively small, but I've happened to pick projects (the
test suit, gettext) that have touched a lot of lines of code.
But other people who've done 10x more work than I have (both in time &
importance) probably have 10x less lines of code assigned to them.
If I keep it up I'll probably "own" more lines of code than Linus, but
I think any criteria that brings me within an order of magnitute of
importance of him and Junio is pretty much broken by defintion :)
next prev parent reply other threads:[~2010-10-23 11:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 18:30 git as an sfc member project Jeff King
2010-10-22 19:19 ` Shawn Pearce
2010-10-22 19:35 ` Jeff King
2010-10-22 20:06 ` Shawn Pearce
2010-10-22 20:59 ` Sverre Rabbelier
2010-10-22 21:48 ` Junio C Hamano
2010-10-22 22:59 ` Junio C Hamano
2010-10-22 23:18 ` Jeff King
2010-10-22 23:21 ` Brandon Casey
2010-10-22 23:26 ` Junio C Hamano
[not found] ` <hh0bQq8TcM0saDTuJo6qVdOMgn-14aysvhF_S70syB678Of7zQOsY9jLajG2WpeGXid8jtG4kVA@cipher.nrlssc.navy.mil>
2010-10-23 0:09 ` Brandon Casey
2010-10-23 1:30 ` Brandon Casey
2010-10-23 22:48 ` Brandon Casey
2010-10-22 23:22 ` Junio C Hamano
2010-10-23 11:52 ` Ævar Arnfjörð Bjarmason [this message]
2010-10-23 13:39 ` Jeff King
2010-10-23 16:03 ` A Large Angry SCM
2010-10-26 22:39 ` Jeff King
2010-10-27 7:03 ` Tait
2010-10-27 11:08 ` Jeff King
2010-11-02 23:03 ` Bradley M. Kuhn
-- strict thread matches above, loose matches on Subject: below --
2010-02-24 15:44 Jeff King
2010-02-24 16:07 ` Jakub Narebski
2010-02-26 12:39 ` Jeff King
2010-02-26 15:56 ` Jakub Narebski
2010-03-01 10:58 ` Jeff King
2010-02-24 16:22 ` Shawn O. Pearce
2010-02-26 12:49 ` Jeff King
2010-02-24 17:44 ` Christian Couder
2010-02-26 12:25 ` Jeff King
2010-02-24 18:12 ` Junio C Hamano
2010-02-26 12:29 ` Jeff King
2010-02-26 12:37 ` Jeff King
2010-02-26 12:59 ` Jeff King
2010-02-26 13:14 ` Julian Phillips
2010-03-01 10:53 ` Jeff King
2010-02-27 6:35 ` Eric Wong
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=AANLkTikxMtdvppLur4kuXffRn0G29NFv6ameTpaeY46G@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
--cc=torvalds@linux-foundation.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).