From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Logo Pictograph
Date: Fri, 13 Sep 2019 22:03:28 +0200 [thread overview]
Message-ID: <20190913220328.0e10fa13@windsurf.home> (raw)
In-Reply-To: <87v9twpbah.fsf@dell.be.48ers.dk>
Hello,
On Fri, 13 Sep 2019 15:37:26 +0200
Peter Korsgaard <peter@korsgaard.com> wrote:
> > Hadas referred me to this professional looking explanation of why photograph
> > is not a good choice for a logo:
>
> > https://forums.adobe.com/thread/1270284
>
> > Hadas also collected a few hundred random logos to demonstrate the point:
>
> > http://tinkie.tkos.co.il/buildroot-logo/2616906744_a238697a95_b.jpg
>
> > SolidRun management agreed to let Hadas design an iconic pictograph version of
> > the Buildroot logo. Here is the result.
>
> > Two colored logo alternatives:
>
> > http://tinkie.tkos.co.il/buildroot-logo/colored_logo.png
> > http://tinkie.tkos.co.il/buildroot-logo/colored_logo2.png
>
> > Two monochromatic alternatives:
>
> > http://tinkie.tkos.co.il/buildroot-logo/bw_logo.png
> > http://tinkie.tkos.co.il/buildroot-logo/bw_logo2.png
>
> > Hadas can provide the vectorized SVG and PDF sources of these raster images.
>
> > What do you think?
>
> I also don't really know anything about graphics design, but I like
> them! Thanks!
>
> Anyone disagrees, otherwise please send a patch adding the SVG to the
> repo (and if you feel up to it, update the website as well).
First of all, thanks a lot Baruch for proposing those logos, and many
thanks Hadas for working on them! I understand the idea that our logo
being a photograph makes it not the best logo, so I like your proposal
of a pictograph version.
As I am not a native English speaker and not at all a graphics/design
expert, it's a bit difficult to put words on how I feel about the logo
proposal. While I like the idea, I find the design a bit "coarse",
maybe too "pictographic". I know this feeling is not very helpful as-is
because it doesn't say what needs to be fixed or improved.
In any case, this is not a very strong feeling, so I certainly won't
oppose to this new logo just because of my vague comment, and I'll be
happy to see a logo change accepted!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-13 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 12:15 [Buildroot] Buildroot Logo Pictograph Baruch Siach
2019-09-13 13:37 ` Peter Korsgaard
2019-09-13 20:03 ` Thomas Petazzoni [this message]
2019-09-17 20:28 ` Arnout Vandecappelle
2019-09-20 14:39 ` Carlos Santos
2019-10-27 11:19 ` Baruch Siach
2019-10-27 11:38 ` Carlos Santos
2019-09-22 5:53 ` Jonathan Ben Avraham
2019-09-22 14:40 ` Arnout Vandecappelle
2019-09-23 6:40 ` Jonathan Ben Avraham
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=20190913220328.0e10fa13@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.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.