git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Christian Couder <christian.couder@gmail.com>,
	David Kastrup <dak@gnu.org>, Junio C Hamano <gitster@pobox.com>,
	git <git@vger.kernel.org>
Subject: Re: git-scm.com website (was: Promoting Git developers)
Date: Mon, 9 Mar 2015 08:51:02 -0700	[thread overview]
Message-ID: <CAJo=hJsbbfK-_qX6sg3Azk30Kz5ebLfyMbVF98VzHZe8YyaLcQ@mail.gmail.com> (raw)

On Mon, Mar 9, 2015 at 6:57 AM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
>
> 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".

Yes, git-scm.com is a place to point people.

Before it was created by Scott Chacon (and others) there was no
landing page for users looking for information on Git.

After it was created, nobody else stepped up with a better alternative.

Writing a website is hard. I have been struggling to make a better
landing page for Gerrit Code Review[1,2]. I really do understand why
Git C hackers aren't interested in sitting down to write prose, HTML
and CSS.

Many of the folks that have contributed to git-scm.com don't usually
contribute C code, but their contribution to the project has still
been beneficial by providing a landing page.


git-scm.com is controlled by the Git project through its membership
with the Conservancy. It could be redirected to another site if
another site existed that better served end-users and the project
better.


[1] http://code.google.com/p/gerrit
[2] https://gerrit.googlesource.com/homepage/+doc/HEAD/

             reply	other threads:[~2015-03-09 15:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 15:51 Shawn Pearce [this message]
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
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='CAJo=hJsbbfK-_qX6sg3Azk30Kz5ebLfyMbVF98VzHZe8YyaLcQ@mail.gmail.com' \
    --to=spearce@spearce.org \
    --cc=christian.couder@gmail.com \
    --cc=dak@gnu.org \
    --cc=git@drmicha.warpmail.net \
    --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).