From: Stefan Beller <sbeller@google.com>
To: Scott Chacon <schacon@gmail.com>
Cc: David Kastrup <dak@gnu.org>, Shawn Pearce <spearce@spearce.org>,
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, 9 Mar 2015 10:30:48 -0700 [thread overview]
Message-ID: <CAGZ79kY_Kb63C6fKeHHx52sEn8j-Ho62-dh97-J8irhjGxaBqA@mail.gmail.com> (raw)
In-Reply-To: <CAP2yMa+Bw0KCSz9YEtviZUykAp4jpdsEWSK-jRxtd9MjzjHKfg@mail.gmail.com>
On Mon, Mar 9, 2015 at 10:14 AM, Scott Chacon <schacon@gmail.com> wrote:
> >
> > It might make sense to reduce this list just to "Projects" since those
> > are actually more tangible and verifiable. Or scrap it altogether.
> Sorry, I disagree with this. I think it's helpful for people to see
> some important corporations that are using it, since many people
> coming to the page are doing research to figure out if they want to
> switch to it in their companies. It also demonstrates that these large
> companies are participating in the open source community and it may
> help them decide to open source internal corporate projects as well,
> which I think is beneficial to everyone.
Yeah I'd agree on that. I'd even go a step further and claim it would be best
to show projects and companies coming from most different branches of
business.
("Can I switch my business over to Git? Oh well only these internet hacker
companies are using it, I -as an air drier firmware writer shop-
cannot relate to,
so I keep using RCS.")
Also looking at the open source projects, most of them seem to me as
large-ish umbrella projects, so a smaller(?) project like emacs would be
huge win to show off Git can work well with all kinds of projects.
next prev parent reply other threads:[~2015-03-09 17:31 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
2015-03-09 21:07 ` Jonathan Nieder
2015-03-09 17:14 ` Scott Chacon
2015-03-09 17:30 ` Stefan Beller [this message]
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=CAGZ79kY_Kb63C6fKeHHx52sEn8j-Ho62-dh97-J8irhjGxaBqA@mail.gmail.com \
--to=sbeller@google.com \
--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).