git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Our official home page and logo for the Git project

From
Jeff King <peff@peff.net>
Date
Apr 11, 2014, 11:40 UTC
Message-ID
<20140411114017.GC28858@sigill.intra.peff.net>
In-Reply-To
<CAH5451kNoXobbh3-WBkewvKvNeFkV0P14Z55=qDN+Ak2WGkHSA@mail.gmail.com>
On Thu, Apr 10, 2014 at 10:24:24AM +1000, Andrew Ardill wrote:
Show 5 quoted lines
> 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
Previous: Tim ChaseNext: Max Horn
Message 8 of 40 in “Our official home page and logo for the Git project”
  1. Junio C HamanoApr 8, 2014
  2. Matthieu MoyApr 9, 2014
  3. Felipe ContrerasApr 9, 2014
  4. Andrew ArdillApr 10, 2014
  5. David KastrupApr 10, 2014
  6. Javier Domingo CansinoApr 11, 2014
  7. Tim ChaseApr 11, 2014
  8. Jeff KingApr 11, 2014
  9. Max HornApr 11, 2014
  10. Felipe ContrerasApr 11, 2014
  11. Max HornApr 11, 2014
  12. Felipe ContrerasApr 11, 2014
  13. Max HornApr 11, 2014
  14. Felipe ContrerasApr 11, 2014
  15. Max HornApr 11, 2014
  16. Felipe ContrerasApr 11, 2014
  17. Philippe VaucherApr 11, 2014
  18. Philippe VaucherApr 11, 2014
  19. Holger HellmuthApr 11, 2014
  20. Felipe ContrerasApr 11, 2014
  21. Max HornApr 11, 2014
  22. Felipe ContrerasApr 11, 2014
  23. David KastrupApr 11, 2014
  24. Vincent van RavesteijnApr 11, 2014
  25. Felipe ContrerasApr 11, 2014
  26. Jeff KingApr 12, 2014
  27. Felipe ContrerasApr 12, 2014
  28. Junio C HamanoApr 11, 2014
  29. Jonathan NiederApr 11, 2014
  30. Ronnie SahlbergApr 11, 2014
  31. Brandon McCaigApr 11, 2014
  32. Michael HaggertyApr 12, 2014
  33. Jeff KingApr 12, 2014
  34. Erik Faye-LundApr 14, 2014
  35. Michael HaggertyApr 11, 2014
  36. Karsten BleesApr 11, 2014
  37. David KastrupApr 11, 2014
  38. Javier Domingo CansinoApr 13, 2014
  39. Stefan BellerApr 14, 2014
  40. Felipe ContrerasApr 20, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.