From: Felipe Contreras <felipe.contreras@gmail.com>
To: Max Horn <max@quendi.de>, Felipe Contreras <felipe.contreras@gmail.com>
Cc: Jeff King <peff@peff.net>,
Andrew Ardill <andrew.ardill@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 15:26:37 -0500 [thread overview]
Message-ID: <53484ffd4d687_8291657308d3@nysa.notmuch> (raw)
In-Reply-To: <8BCDA559-89F0-4FD1-AA76-94CC67CB32C4@quendi.de>
Max Horn wrote:
> On 11.04.2014, at 20:56, Felipe Contreras <felipe.contreras@gmail.com> wrote:
> > Max Horn wrote:
> >> Come back when you have facts, as opposed to the illusion that you are the
> >> spokesperson of the (apparently silent) majority of Git users.
> >
> > Facts:
> >
> > 1) A hunk that removed (-) is represented in red [1]
> > 2) A hunk that added (+) is represented in green [1]
> > 3) A file that is removed is represented in red [2]
> > 4) A file that is added or modified is represented in green [2]
> > 5) A test that fails is represented in red [3]
> > 6) A test that succeeds is represented in green [3]
> > 7) The current Git logo (accordo to some people) has "-" in red, "+" in green [4]
>
> I do not dispute any of that.
>
> > Given these facts, it's reasonable to assume that to the majority of Git users
> > red is old and bad, green is new and good.
>
> This is where you are making the hasty generalization.
And you prove again you don't know what that means.
> Your facts do not suffice to prove this conclusion.
That would be an invalid argument, not a hasty generalization.
> And even if the conclusion is true (which is possible despite your flawed
> argument, although I doubt it), then you are making another implicit
> assumption: Namely that people will automatically transfer the red/green
> principle from diffs and test results to logos.
It is not only diffs, in general in the tech industry red means failure, green
means success. I can show you many many more examples if you need them.
Then you somehow think that when people see the Git logo they are not going to
asociate they countless hours they've been actually using Git, and seeing red
as bad, as if somehow the logo has nothing to do with the program. If that was
the case we might as well choose a cow for a logo, because it doesn't really
matter.
If you knew anything about logos you would know that the target audience does
matter, and the organization's use of certain colors is important as well.
Google for "how to design a logo" and you will find many references [1][2].
But didn't you say the colour didn't matter? If you really think that, then you
should agree at the very least that green is as good as red. And if you don't
care which colour is best, why are you arguing?
[1] http://www.creativebloq.com/graphic-design/pro-guide-logo-design-21221
[2] http://www.wikihow.com/Design-a-Logo
--
Felipe Contreras
next prev parent reply other threads:[~2014-04-11 20:36 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 [this message]
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=53484ffd4d687_8291657308d3@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=andrew.ardill@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=max@quendi.de \
--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 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).