git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Andrew Ardill <andrew.ardill@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
	Junio C Hamano <gitster@pobox.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 07:40:18 -0400	[thread overview]
Message-ID: <20140411114017.GC28858@sigill.intra.peff.net> (raw)
In-Reply-To: <CAH5451kNoXobbh3-WBkewvKvNeFkV0P14Z55=qDN+Ak2WGkHSA@mail.gmail.com>

On Thu, Apr 10, 2014 at 10:24:24AM +1000, Andrew Ardill wrote:

> It's normal for an organisation to have a collection of logos to
> choose from, with one 'official' version. For example, a black and
> white version is useful for print. Similarly, it's useful to have a
> couple of different contrast level/colours that can be used in the
> appropriate situations.

There are a few options at

  http://git-scm.com/downloads/logos

for matching the logo to the background.

> There is nothing wrong with having alternates that have been approved
> for various situations.

I'm not sure if this is how you meant it, but I want to emphasize that
there is no "approval" necessary for using alternate logos. Saying
"let's recognize this one as an official logo" is not meant to shut down
the use of others. It is only meant to say "when people ask for an
official logo (e.g., GSoC does so), this one is a good answer".

That is not to say that proliferation of logos is a good idea either.
The point of a logo is recognizability, and if there are dozens of git
logos, chances are that most of them are not recognizable.

> I recommend creating a git repository called git-resources,
> git-marketing, or git-assets, to contain the various approved logos.
> If there is not another location, or a more appropriate one,
> https://github.com/git would be a good place to put this.

I think the logo page above is a good start for variations of that
particular logo. I'd prefer not to put other random logos there unless
they also get wide enough use that they are recognized by the project.
But I have no objection to a repository of random logos.

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.

-Peff

  parent reply	other threads:[~2014-04-11 11:40 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 [this message]
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
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=20140411114017.GC28858@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=andrew.ardill@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --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).