All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Andrew Ardill <andrew.ardill@gmail.com>,
	Felipe Contreras <felipe.contreras@gmail.com>,
	"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Our official home page and logo for the Git project
Date: Fri, 11 Apr 2014 12:25:17 -0700	[thread overview]
Message-ID: <xmqqr453sm76.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140411114017.GC28858@sigill.intra.peff.net> (Jeff King's message of "Fri, 11 Apr 2014 07:40:18 -0400")

Jeff King <peff@peff.net> writes:

> The git-scm.com page is mostly targeted at end users: what is it, how do
> I get it, where is the documentation. Things like a logo repository, or
> developer information is spread across various wikis and other sites.
> If there's interest, we can make "dev.git-scm.com" for such things, or
> host repositories under http://github.com/git. But we would first need
> content to put there, and somebody would need to step forward to
> organize and maintain that content.

The mention of "dev.git-scm.com" gives me a mixed feeling.  The
chasm between the developer community and casual end-users who know
about Git primarily via their perusal of git-scm.com is one of the
root causes of this confusion.  

The pages at https://git.wiki.kernel.org/index.php/Main_Page are
done primarily by developers, and between the two logos on that
page, the one that appears inside the page under "Main Page" header
has long been the logo that Git people immediately recognised as the
Git logo.  That logo originally appeared on gitweb, I think, and is
in my tree (on the other hand, the logo in question on the motion
does even appear anywhere in my tree).  We didn't feel a need to
declare it was the official logo.  That was from back when Git
community did not have strong needs for "branding".

The one on the left-top corner was one of the alternatives that
received favorable reactions from multiple people (I am not sure if
there was a clear "majority" though) submitted when we briefly had a
poll to come up with an updated logo.

https://git.wiki.kernel.org/index.php/GitRelatedLogos has many other
"Git related" logos, many of which I do not even recognise and are
nowhere near "official".

In any case, this motion is not about "let's declare the logo we see
on git-scm.com today as _the_ official one".  It is not about "that
logo on git-scm.com sucks; let's come up with a better one".  People
are welcome to do that discussion elsewhere, and I do not mind a
repository of contestants created somewhere, but personally I think
the project is too mature for that and it is too late, even though
the "bleeding-red fork" logo may not be my favorite.

The motion is about this:

    Outside people, like the party who approached us about putting
    our logo on their trinket, seem to associate that logo we see on
    git-scm.com today with our project, but we never officially said
    it was our logo (we did not endorse that git-scm.com is our
    official home page, either, for that matter).

    It is silly for us to have to say "Ehh, that is a logo that was
    randomly done and slapped on git-scm.com which is not even our
    official home page, and the logo is licensed CC-BY by somebody
    else.  Go talk to them.", every time such a request comes.

    Please help us by letting us answer "Yup, that is a logo (among
    others) that represents our project, and we are OK with you
    using it to help promote our project" instead.

That is what I meant by "our official logo" in the first message.

So,... seconds?

  parent reply	other threads:[~2014-04-11 19:25 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 18:44 Our official home page and logo for the Git project Junio C Hamano
2014-04-09 14:54 ` Matthieu Moy
2014-04-09 16:43 ` Felipe Contreras
2014-04-10  0:24   ` Andrew Ardill
2014-04-10  7:32     ` David Kastrup
2014-04-11 11:32       ` Javier Domingo Cansino
2014-04-11 16:58         ` Tim Chase
2014-04-11 11:40     ` Jeff King
2014-04-11 12:39       ` Max Horn
2014-04-11 13:29         ` Felipe Contreras
2014-04-11 15:02           ` Max Horn
2014-04-11 15:21             ` Felipe Contreras
2014-04-11 18:37               ` Max Horn
2014-04-11 18:56                 ` Felipe Contreras
2014-04-11 19:24                   ` Max Horn
2014-04-11 20:26                     ` Felipe Contreras
2014-04-11 15:39             ` Philippe Vaucher
2014-04-11 15:48               ` Philippe Vaucher
2014-04-11 16:52               ` Holger Hellmuth
2014-04-11 17:21                 ` Felipe Contreras
2014-04-11 18:35               ` Max Horn
2014-04-11 13:24       ` Felipe Contreras
2014-04-11 13:44         ` David Kastrup
2014-04-11 14:09         ` Vincent van Ravesteijn
2014-04-11 15:22           ` Felipe Contreras
2014-04-12 12:34         ` Jeff King
2014-04-12 14:02           ` Felipe Contreras
     [not found]             ` <CALZVapkdr5R8h3XWwmo3LHEXnMrOQhzVCw2LwP5oRbJ=MVnbUg@mail.gmail.com>
2014-04-13  8:53               ` Javier Domingo Cansino
2014-04-14  8:28                 ` Stefan Beller
2014-04-20 17:53                   ` Felipe Contreras
2014-04-11 19:25       ` Junio C Hamano [this message]
2014-04-11 19:38         ` Jonathan Nieder
2014-04-11 19:45         ` Ronnie Sahlberg
2014-04-11 21:25         ` Brandon McCaig
2014-04-12  4:28         ` Michael Haggerty
2014-04-12 12:05         ` Jeff King
2014-04-14 13:39         ` Erik Faye-Lund
2014-04-11 16:24   ` Michael Haggerty
2014-04-11 17:07   ` Karsten Blees
2014-04-11 17:20     ` David Kastrup

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=xmqqr453sm76.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=andrew.ardill@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.