From: David Kastrup <dak@gnu•org>
To: Shawn Pearce <spearce@spearce•org>
Cc: Michael J Gruber <git@drmicha•warpmail.net>,
Christian Couder <christian.couder@gmail•com>,
Junio C Hamano <gitster@pobox•com>, git <git@vger•kernel.org>
Subject: Re: git-scm.com website
Date: Mon, 09 Mar 2015 17:06:53 +0100 [thread overview]
Message-ID: <87y4n6kvdu.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAJo=hJsbbfK-_qX6sg3Azk30Kz5ebLfyMbVF98VzHZe8YyaLcQ@mail.gmail.com> (Shawn Pearce's message of "Mon, 9 Mar 2015 08:51:02 -0700")
Shawn Pearce <spearce@spearce•org> writes:
> 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.
It features "Companies & Projects Using Git" at the bottom. Not
"supporting" but "using".
Linux is point 10 on that list. The first 6 items are Google, facebook,
Microsoft, Twitter, LinkedIn, and Netflix.
Even for an OpenSource project that does not buy into the Free Software
philosophy, that is a mostly embarrassing list of companies to advertise
for.
Personally, I consider the recent migration of the Emacs repository to
Git a bigger endorsement but then that's me.
It might make sense to reduce this list just to "Projects" since those
are actually more tangible and verifiable. Or scrap it altogether.
--
David Kastrup
next prev parent reply other threads:[~2015-03-09 16:07 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 ` David Kastrup [this message]
2015-03-09 16:19 ` git-scm.com website 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=87y4n6kvdu.fsf@fencepost.gnu.org \
--to=dak@gnu$(echo .)org \
--cc=christian.couder@gmail$(echo .)com \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=spearce@spearce$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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