git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Scott Chacon <schacon@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
	David Kastrup <dak@gnu.org>, 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, 9 Mar 2015 15:24:10 -0400	[thread overview]
Message-ID: <20150309192409.GA4733@peff.net> (raw)
In-Reply-To: <CAP2yMaJWLppUw2QY3rL7dZPaqVUf6G-UYVrvi35A_t03ow6E_w@mail.gmail.com>

On Mon, Mar 09, 2015 at 10:52:34AM -0700, Scott Chacon wrote:

> > * some of the pull request can be rejected even if the developers want
> > them, like this pull request to add back a list of contributors was:
> >
> > https://github.com/git/git-scm.com/pull/216
> >
> > (By the way this pull request talks about bugs in
> > https://github.com/git/git/graphs/contributors that are still not
> > fixed...)
> >
> 
> It should be noted that Peff has write access to this repository and I
> think the SFC manages the DNS for the site as well, so technically it
> is maintained "by us". If he had felt strongly about the addition, I
> easily could have been convinced to do it, but I didn't think it was
> helpful in a larger sense.

Yes, this. It was _my_ pull request, and as I noted in my final comment,
I agreed with closing it. That is not "rejected", but "withdrawn".

If somebody wants to open their own pull request, they can. But it has
been over 2 years, and I haven't seen anybody talk about this, let alone
offer to work on it.

If people don't like git-scm.com and want to have an alternate site,
especially one targeted at Git _developers_, I don't see a reason not
to. http://git.github.io is where I have been collecting GSoC materials,
and any community member who asks is welcome to have push access (and I
have offered to apply patches for people who do not want to use GitHub).
But aside from that GSoC content, there is nothing there (and the design
is awful; any takers?).

There is also the wiki at http://git.wiki.kernel.org. I prefer the
git.github.io site, because it is easier to manipulate using git, but if
having both is fracturing things, I'd be happy to shut it down.

So if anyone wants to contribute to Git's web presence, it seems there
are quite a few opportunities to do so.

-Peff

  reply	other threads:[~2015-03-09 19:24 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 [this message]
2015-03-09 20:18             ` David Kastrup
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=20150309192409.GA4733@peff.net \
    --to=peff@peff.net \
    --cc=christian.couder@gmail.com \
    --cc=dak@gnu.org \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).