All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
To: git@vger.kernel.org
Subject: Re: Git Branding Overview, Re: Git.or.cz Experimental Design
Date: Mon, 21 Jul 2008 14:20:39 +0200	[thread overview]
Message-ID: <g61uun$lt0$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0807211218470.8986@racer>

Johannes Schindelin venit, vidit, dixit 21.07.2008 13:20:
> Hi,
> 
> On Mon, 21 Jul 2008, Michael J Gruber wrote:
> 
>> Martin Langhoff venit, vidit, dixit 20.07.2008 23:50:
>>> On Fri, Jul 18, 2008 at 10:39 PM, Petr Baudis <pasky@suse.cz> wrote:
>>>> On Wed, Jul 02, 2008 at 11:11:02PM -0400, David Baldwin wrote:
>>>>> http://baldwindev.com/git.or.cz/
>>>> I'm not sure if this is really an improvement on the current state,
>>>> but then again, the current state pretty much matches my idea and maybe
>>>> others will agree that your proposal is better. Thus, it's better to
>>>> show this to the Git community at large. :-)
>>> FWIW, I like it. I like both the better font and whitespace layout and
>>> the 3-color-spot-merge-to-white. As Petr says, we have had the
>>> (apologies, but to me) ugly logo for a while, so it is widely used,
>>> and perhaps it has even grown on people.
>>>
>>> BazaarNG managed to grab the best concept logo of the lot, IMHO, with
>>> the 'merge' roadsign.
>>>
>>>> If you think you have a cooler logo, that's fine too, but then it's
>>>> again better to present it explicitly, I believe.
>>> Can we separate the 2 things? The better fonts and layout look like a win to
>>> me.
>>>
>>> WRT the logo, the current one is not a particularly strong image, and
>>> we haven't spent millions in plastering it over magazines or anything.
>>> So a good new logo would be something to take on.
>> I like that new logo (plusminus G), too, it's very descriptive. I just want to
>> raise one question which I can't answer myself:
>>
>> Are there any potential issues with the Helvetica license?
>>
>> In any case it may be safer do redo it with a GPL sans serif font. If one
>> wants to keep the association of the shape of "G" with a circular arrow then
>> FreeSans and Nimbus Sans L seem to be the only options.
>>
>> Alternatively, it may be easier to redo it in plain PS. I'll attach 2 KISS
>> variants. 1.5k for the eps, 3 colors only.
> 
> You could have spared yourself the trouble:

Thanks for the appreciation ;)

> 
> http://repo.or.cz/w/msysgit.git?a=blob_plain;f=share/resources/gitlogo.svg;h=c0d67e70ab31394f0635c141998e512437a138b4;hb=HEAD
> 
> Done without the use of any font at all.

I don't think that was on the wiki before. Henrik's version (which was, 
and was being discussed here) *is* based on Helvetica.

Still, the suggestion stands to replace it by something more polished.

Michael

  reply	other threads:[~2008-07-21 12:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5fb1d2400807022011w7f8d79dbk68a64dc1b8b01d98@mail.gmail.com>
2008-07-18 10:39 ` Git Branding Overview, Re: Git.or.cz Experimental Design Petr Baudis
2008-07-20 21:21   ` Matt Graham
2008-07-20 21:44   ` Jakub Narebski
2008-07-20 22:36     ` Petr Baudis
2008-07-20 21:50   ` Martin Langhoff
2008-07-21 10:59     ` Michael J Gruber
2008-07-21 11:20       ` Johannes Schindelin
2008-07-21 12:20         ` Michael J Gruber [this message]
2008-07-21 17:23           ` Jakub Narebski
2008-07-21 20:03         ` Matt Graham

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='g61uun$lt0$1@ger.gmane.org' \
    --to=michaeljgruber+gmane@fastmail.fm \
    --cc=git@vger.kernel.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 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.