git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: David Kastrup <dak@gnu.org>, Junio C Hamano <gitster@pobox.com>,
	git <git@vger.kernel.org>
Subject: Promoting Git developers (was: Bashing freelancers)
Date: Sat, 7 Mar 2015 08:18:37 +0100	[thread overview]
Message-ID: <CAP8UFD1+rC0FjisSddDcyn1E_75wtBU9pEpUcQX5zNtd4zKYFQ@mail.gmail.com> (raw)

Hi,

On Fri, Mar 6, 2015 at 6:41 PM, David Kastrup <dak@gnu.org> wrote:

> At some point of time I think it may be worth reevaluating the toxic
> atmosphere against freelancers doing Git development.

My opinion on this is that the Git community has not been good
especially lately at promoting its own developers.

Some facts:

* There used to be an AUTHORS section in each of the git man page.
They have been removed. The rational was that they were hard to
maintain and the information about authors was easily available
elsewhere.

* There used to be a nice page on git-scm.com, the main Git web site,
listing the authors and how many commits they had contributed. It has
been removed.

* In the "A note from the maintainer" emails that Junio regularly
sends, the last section about "Other people's trees, trusted
lieutenants and credits." seems to have been truncated for some time
and doesn't show anymore the nice "credits" words it used to show.
Maybe this is a bug.

* https://www.openhub.net/p/git/contributors/summary seems to give me a
"504 Gateway Time-out" right now :-(

* On the Git Merge web site, we can see that none of the speakers
seems to have been a very active contributor to git.git

None of these facts is a big issue in itself for me, but I think the
trend is very sad, and I would be happy if we could discuss here or at
the Git Merge (or both) about ways to improve in this area.

Best,
Christian.

             reply	other threads:[~2015-03-07  7:19 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07  7:18 Christian Couder [this message]
2015-03-09 13:57 ` Promoting Git developers (was: Bashing freelancers) Michael J Gruber
2015-03-09 14:31   ` Promoting Git developers David Kastrup
2015-03-09 18:32     ` Philip Oakley
2015-03-10  7:45   ` Junio C Hamano
2015-03-10 11:51   ` Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-10 17:23     ` Promoting Git developers Junio C Hamano
2015-03-11  1:04       ` Jason St. John
2015-03-11  2:13         ` Duy Nguyen
2015-03-11  4:16           ` Junio C Hamano
2015-03-12  2:15             ` Duy Nguyen
2015-03-12  4:53               ` Junio C Hamano
2015-03-12  7:45                 ` Fredrik Gustafsson
2015-03-12 18:43                   ` Junio C Hamano
2015-03-11  2:36         ` Junio C Hamano
2015-03-11  7:31           ` Jeff King
2015-03-11  7:38             ` Junio C Hamano
2015-03-11  7:54               ` Jeff King
2015-03-11 21:28                 ` Junio C Hamano
2015-03-11 23:17                   ` Andrew Ardill
2015-03-12 22:31                   ` Jeff King
2015-03-12 22:36                     ` Junio C Hamano
2015-03-12 22:43                       ` Jeff King
2015-03-12  5:05             ` Junio C Hamano
2015-03-12 22:38               ` Jeff King
2015-03-12 22:58                 ` Junio C Hamano
2015-03-15  9:12                   ` Christian Couder
2015-03-11 13:53       ` Christian Couder
2015-03-11 20:42         ` Junio C Hamano
2015-03-15  8:46           ` Christian Couder
2015-03-15 22:18             ` Junio C Hamano
2015-03-15 22:43               ` Randall S. Becker
2015-03-16  9:10                 ` Christian Couder
2015-03-16  9:20                   ` David Kastrup
2015-03-16 17:06                     ` Stefan Beller
2015-03-17 20:08                       ` Christian Couder
2015-03-17 20:16                         ` Junio C Hamano
2015-03-16 23:39               ` David Lang
2015-03-17  5:25                 ` Junio C Hamano
2015-03-17  5:56                   ` David Lang
2015-03-17 20:15               ` Christian Couder
2015-03-17  9:43             ` Thomas Ferris Nicolaisen
2015-03-17 19:51               ` Christian Couder

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=CAP8UFD1+rC0FjisSddDcyn1E_75wtBU9pEpUcQX5zNtd4zKYFQ@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=dak@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
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).