git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Scott Chacon" <schacon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-scm.com
Date: Sat, 26 Jul 2008 10:10:32 -0700	[thread overview]
Message-ID: <7vsktwfu5z.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <d411cc4a0807251759m1d83d7c4w4724806b19f7c02a@mail.gmail.com> (Scott Chacon's message of "Fri, 25 Jul 2008 17:59:58 -0700")

"Scott Chacon" <schacon@gmail.com> writes:

> On Fri, Jul 25, 2008 at 4:47 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> ...
>> I find a tabular list like this list easier to read if it were sorted like
>> this:
>>
>>        A       D       G
>>        B       E       H
>>        C       F
>> ...
>
> I fixed the things you mentioned here, except for the list ordering,
> only because I kinda think you big contributors should be at the top
> there,...

If you are going to list 30 or so top contributors in 8 rows times 4
columns, because visually the columns are much more distinct than the
rows, it makes the result look more sorted.  This is the same reasoning
hwo "git help --all" was fixed with 112d0ba (Make "git help" sort git
commands in columns, 2005-12-18).

By the way, I think this shows another issue with the "rest of us" list in
the lower half.

I have a mild suspicion that sorting that list in alphabetical order may
actually make it much better.  It all depends on the purpose of that list,
though.

The purpose of the list would most likely not to find somebody with high
activity to contact for help (you would use the top list that is sorted by
the commit count for that kind of thing).  It would primarily be to give
credit to everybody, and perhaps so that people on the contributor list
can point at their own name and say "I helped them", or find somebody else
they happen to know in the list.

When a contributor used to have 8 commits and then adds 2 commits, that
would move the name in the list by a dozen places or so with the current
set of contributors.  It would be much easier to locate one's own name
among a huge list if the names are alphabetically sorted, not by commit
count.  When more people start to contribute, your name does not move so
drastically.  If you are Adam, you are likely to find yourself near the
beginning of the list, if you are Scott, you are likely to find yourself
near one fourth from the end of the list.

And for the "giving credit" purpose, I do not think truncating the list at
5 commits or less threshold, as suggested earlier and already done, makes
much sense, either.

  reply	other threads:[~2008-07-26 17:11 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 17:35 git-scm.com Scott Chacon
2008-07-25 21:20 ` git-scm.com Sverre Rabbelier
2008-07-25 21:46   ` git-scm.com Scott Chacon
2008-07-25 21:36 ` git-scm.com Johan Herland
2008-07-25 21:49   ` git-scm.com Scott Chacon
2008-07-25 22:02 ` git-scm.com Stephan Beyer
2008-07-25 22:15   ` git-scm.com Scott Chacon
2008-07-25 23:47 ` git-scm.com Junio C Hamano
2008-07-26  0:59   ` git-scm.com Scott Chacon
2008-07-26 17:10     ` Junio C Hamano [this message]
2008-07-27  6:19       ` git-scm.com "Peter Valdemar Mørch (Lists)"
2008-07-27 11:37       ` git-scm.com Petr Baudis
2008-07-27 18:33         ` git-scm.com Junio C Hamano
2008-07-27 22:01           ` git-scm.com Junio C Hamano
2008-07-27 23:19             ` git-scm.com Martin Langhoff
2008-07-28  3:11               ` git-scm.com Tom Werner
2008-07-28 10:50                 ` git-scm.com Johannes Schindelin
2008-07-28 18:12                   ` git-scm.com Tom Werner
2008-07-31 18:39                     ` git-scm.com Jon Loeliger
2008-07-31 20:19                       ` git-scm.com Kevin Ballard
2008-07-28 21:42                   ` git-scm.com Junio C Hamano
2008-07-28 22:34                     ` git-scm.com Martin Langhoff
2008-07-28 22:39                     ` git-scm.com Pieter de Bie
2008-07-29  5:15                     ` git-scm.com Shawn O. Pearce
2008-07-26  1:38 ` git-scm.com Patrick Aljord
2008-07-26  2:28   ` git-scm.com Scott Chacon
2008-07-26  2:37     ` git-scm.com Petr Baudis
2008-07-26  2:47       ` git-scm.com david
2008-07-26  5:30         ` git-scm.com Scott Chacon
2008-07-26  5:49           ` git-scm.com Patrick Aljord
2008-07-26  8:06             ` git-scm.com Junio C Hamano
2008-07-26  6:27           ` git-scm.com david
2008-07-26 15:48           ` git-scm.com Wincent Colaiuta
2008-07-26 18:33             ` git-scm.com Scott Chacon
     [not found]               ` <alpine.DEB.1.00.0807262110140.26810@eeepc-johanness>
2008-07-26 19:13                 ` git-scm.com Scott Chacon
2008-07-26 19:20                   ` git-scm.com Johannes Schindelin
2008-07-26 19:21                     ` git-scm.com Scott Chacon
2008-07-26 23:11             ` git-scm.com Junio C Hamano
2008-07-26  2:45     ` git-scm.com Johannes Schindelin
2008-07-26  1:53 ` Official Git Homepage change? git-scm.com Petr Baudis
2008-07-26  2:09   ` Petr Baudis
2008-07-26  4:09     ` Junio C Hamano
2008-07-26  4:28       ` Johannes Schindelin
2008-07-26  4:49         ` Junio C Hamano
2008-07-26  4:54           ` Johannes Schindelin
2008-07-26 14:40           ` Petr Baudis
2008-07-26 16:37             ` Junio C Hamano
2008-07-26 16:48               ` Thomas Adam
2008-07-27 12:22               ` Petr Baudis
2008-07-27 15:53                 ` Johannes Schindelin
2008-07-27 20:12                   ` Sverre Rabbelier
2008-07-26  6:43       ` Scott Chacon
2008-07-26  7:11         ` Junio C Hamano
2008-07-26  7:27           ` Scott Chacon
2008-07-26  7:52             ` Sverre Rabbelier
2008-07-26 14:48             ` Rene Herman
2008-07-26 15:21               ` Jakub Narebski
2008-07-26 15:32                 ` Scott Chacon
2008-07-26 15:39                   ` Jakub Narebski
2008-07-26 15:15           ` Petr Baudis
2008-07-26 20:17         ` Petr Baudis
2008-07-26 20:24           ` Jakub Narebski
2008-07-26 20:32             ` Petr Baudis
2008-08-03 14:50               ` Jonas Fonseca
2008-08-03 22:00                 ` Junio C Hamano
2008-07-27 12:35       ` Petr Baudis
2008-07-26  7:07   ` Scott Chacon
2008-07-26 14:17     ` Petr Baudis
2008-07-26  2:25 ` git-scm.com Johannes Schindelin
2008-07-26  2:33   ` git-scm.com Petr Baudis
2008-07-26  2:54   ` git-scm.com Stephan Beyer
2008-07-26  3:07     ` git-scm.com Johannes Schindelin
2008-07-26  4:55       ` git-scm.com Scott Chacon
2008-07-26  7:21         ` git-scm.com Martin Langhoff
2008-07-26  8:03 ` git-scm.com Jakub Narebski
2008-07-26 13:07   ` git-scm.com Petr Baudis
2008-07-26 18:51     ` git-scm.com Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2008-10-15 17:25 git-scm.com (was Re: Git graph on GitHub) Petr Baudis
     [not found] ` <bab6a2ab0810150315l273d4ef3k95cda8f43a4745ca@mail.gmail.com>
2008-10-15 10:18   ` PJ Hyett
2008-10-15 10:34     ` Wincent Colaiuta
2008-10-15 16:21       ` Scott Chacon
2008-10-16  9:42         ` git-scm.com Nanako Shiraishi
2008-10-16  9:49           ` git-scm.com Petr Baudis
2008-10-17  1:57           ` git-scm.com Junio C Hamano
2008-10-15 18:36       ` git-scm.com (was Re: Git graph on GitHub) PJ Hyett
2008-10-15 19:26         ` git-scm.com Teemu Likonen

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=7vsktwfu5z.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=schacon@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).