From: Michael J Gruber <git@drmicha.warpmail.net>
To: Christian Couder <christian.couder@gmail.com>,
David Kastrup <dak@gnu.org>, Junio C Hamano <gitster@pobox.com>,
git <git@vger.kernel.org>
Subject: Re: Promoting Git developers (was: Bashing freelancers)
Date: Mon, 09 Mar 2015 14:57:09 +0100 [thread overview]
Message-ID: <54FDA6B5.8050505@drmicha.warpmail.net> (raw)
In-Reply-To: <CAP8UFD1+rC0FjisSddDcyn1E_75wtBU9pEpUcQX5zNtd4zKYFQ@mail.gmail.com>
Christian Couder venit, vidit, dixit 07.03.2015 08:18:
> 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.
>
I guess we have at least 3 kinds of people here:
A) Paid to do Git development, at least as part of their job.
B) Freelancers who don't get paid directly for "doing git" but hope to
profit from their git efforts directly or indirectly.
C) Doing it in their freetime (or as minor, inofficial part of their
non-programming job).
I'm in camp C and honestly wasn't aware of camp B until now.
I consider camp A to be beneficial for all of us, and I don't think
specific employer interests have pushed the project in specific
directions, or specific features (OK, maybe one, but not as a rule).
I do see that remuneration is an issue for camp B.
> 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.
I'd say it's difficult to do this in a fair manner, since most pages are
a community effort now in the best sense.
> * 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.
It was out of date again and again, and pull-requests took forever. The
problem here still seems to be the old dis-connectedness between that
website and the developers' community. But it's the only one "we" have.
Since we're talking business: git-scm.com still looks a bit like a
ProGit/Github promotion site. I don't have anything against either, and
git-scm.com provides a lot of the information that users are looking
for, and that are hard to find anywhere else; it's a landing page. It
just does not look like a "project home".
> * 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.
Being in camp C, that entry in "credits" was my remuneration, so-to-say,
and I missed it when it was gone. OTOH, I do understand how tedious it
is to keep that up to date and fair. (And if, I should probably have
been removed at some point...)
There still is "git rev-list --count --author=Mickey origin/master" :)
> * https://www.openhub.net/p/git/contributors/summary seems to give me a
> "504 Gateway Time-out" right now :-(
I thought there is ohloh, but that one is the new ohloh... Anyways,
Junio's repo on github is "official" in a sense and has this:
https://github.com/git/git/graphs/contributors
> * 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
Yeah, that's more an "outside business window into git". In fact, while
that doesn't quite intrigue me, I would think it's a great chance for
freelancers to get in touch with people doing business with git.
And maybe they'll be talking about what they're using git for, and which
technical and non-technical challenges they meet in doing so? Edward was
fun to listen to in Berlin :)
Git merge itself is organized and sponsored by businesses with business
interests. But there's also the contributors summit. Git merge Berlin
was great and generous in that respect.
> 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.
There should be a good occasion, after we see how it went, and hopefully
also to sort out any apparent misunderstandings from the past that have
resurfaced in this thread.
Maybe, all we need is badges? [1]
Michael
[1] https://badges.fedoraproject.org/
next prev parent reply other threads:[~2015-03-09 13:57 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 7:18 Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-09 13:57 ` Michael J Gruber [this message]
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
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=54FDA6B5.8050505@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=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.
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).