From: David Kastrup <dak@gnu.org>
To: Jeff King <peff@peff.net>
Cc: Scott Chacon <schacon@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
Shawn Pearce <spearce@spearce.org>,
Michael J Gruber <git@drmicha.warpmail.net>,
Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: git-scm.com website
Date: Mon, 09 Mar 2015 21:18:50 +0100 [thread overview]
Message-ID: <878uf5lyad.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20150309192409.GA4733@peff.net> (Jeff King's message of "Mon, 9 Mar 2015 15:24:10 -0400")
Jeff King <peff@peff.net> writes:
> If people don't like git-scm.com and want to have an alternate site,
I think that's the basic problem here. As long as people want to _have_
an alternate site rather than want to _write_ and _maintain_ an
alternate site, any site will only be as representative of the Git
community as the person(s) working on the site feel they are
representative of the Git community.
Scott says that he tried his best to create a neutral site, and that's
what the site is. When a guardian votes instead of his ward in an
election, he might vote different from his own vote in order to better
reflect the interest of his ward. It may still well be different from
who the ward would have voted for.
For me, the Git-scm site has the air of a third-party site, and that's
what it is essentially. I don't see that Scott could do any better here
when basically left on his own and it seems pointless to complain to him
about that.
That is one case where the "central repository" approach has at least
some psychological advantage over the "one personal repository is what
is considered canonical" approach used by the Linux kernel, Git, the
Git-scm site and possibly by most of the GitHub hosted projects: with a
central repository, there is somewhat less of a feeling that one person
"owns" the project (even admin rights come into play only for
exceptional circumstances rather than everyday work). Possibly that
makes it a bit harder to say "not my field of responsibility".
--
David Kastrup
next prev parent reply other threads:[~2015-03-09 20:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 15:51 git-scm.com website (was: Promoting Git developers) Shawn Pearce
2015-03-09 16:06 ` git-scm.com website David Kastrup
2015-03-09 16:19 ` Shawn Pearce
2015-03-09 16:37 ` David Kastrup
2015-03-09 17:12 ` Christian Couder
2015-03-09 17:52 ` Scott Chacon
2015-03-09 19:24 ` Jeff King
2015-03-09 20:18 ` David Kastrup [this message]
2015-03-09 21:07 ` Jonathan Nieder
2015-03-09 17:14 ` Scott Chacon
2015-03-09 17:30 ` Stefan Beller
2015-03-09 17:49 ` David Kastrup
2015-03-09 17:54 ` Stefan Beller
2015-03-09 18:02 ` David Kastrup
2015-03-10 9:07 ` Michael J Gruber
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=878uf5lyad.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=christian.couder@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=schacon@gmail.com \
--cc=spearce@spearce.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).