zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: justindorfman@gmail.com
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Logo
Date: Thu, 27 Jun 2019 13:23:47 -0700	[thread overview]
Message-ID: <CAH+w=7bDqRtDx1_uzxh+OkhYzEo+6fqLUMSMVFAG323BVg-Cog@mail.gmail.com> (raw)
In-Reply-To: <CAEjOAVqtQ-sVDsyiZg0ZWmCwYLp-==wvvRCRZ69ffu+YNSddrg@mail.gmail.com>

My take ...

For idea #1, the stylized Z% looks too flowing/serif-y to go with the
typewriter font "sh".  They end up looking like separate pieces rather
than a unified logo.  Either the % should be less loopy or something
else should be done with the "sh".  Also the baseline of the "sh"
looks too low, perhaps push it up just a bit so that the center line
of the "s" aligns with the center of the lower circle of the %.

I'm not excited by idea #2.  It might be better if the break in each
circle were above the horizontal lines of the Z, rather than below,
but I'm not sure.  Maybe what bothers me is the way things sort of
bubble outside the "box" defined by the corners of the Z; aside from
the font clash in #1 I like the way its circles fit inside the angles.

On Thu, Jun 27, 2019 at 10:14 AM Justin Dorfman <justindorfman@gmail.com> wrote:
>
> Hey all,
>
> Got some initial design ideas in and wanted to share the progress. Before
> moving forward I would love to get some input from you all.
>
> https://cl.ly/0e2cdb6af228
>
> Apologies if anyone got multiple messages. The other 2 messages
> bounced *"**fatal:
> Sorry, I don't accept messages larger than 80000 bytes (#5.2.3)"* which is
> why I added a link to the graphic instead.
>
> Regards,
>
> Justin Dorfman
> @jdorfman <http://www.twitter.com/jdorfman>
>
>
> On Sat, Jun 15, 2019 at 2:33 AM Jérémie Roquet <jroquet@arkanosis.net>
> wrote:
>
> > Hi Justin,
> >
> > Le ven. 14 juin 2019 à 22:56, Justin Dorfman <justindorfman@gmail.com> a
> > écrit :
> > > Got an update: my employer said they will sponsor the design! I assigned
> > a
> > > Trello task to our design team and will follow up with them next week. At
> > > the moment I don't have an ETA but I will keep everyone posted once I
> > have
> > > more info. =)
> >
> > Awesome news, thank you!
> >
> > --
> > Jérémie
> >

  reply	other threads:[~2019-06-27 20:24 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 23:37 Logo Justin Dorfman
2019-06-04 23:56 ` Logo Jérémie Roquet
2019-06-05  0:09   ` Logo Justin Dorfman
2019-06-05  0:13     ` Logo Andrew J. Rech
2019-06-05  0:43       ` Logo Justin Dorfman
2019-06-05  7:56 ` Logo Oliver Kiddle
2019-06-05 15:52   ` Logo Bart Schaefer
2019-06-05 16:50     ` Logo Justin Dorfman
2019-06-06 20:12       ` Logo Peter Stephenson
2019-06-07  0:26         ` Logo Justin Dorfman
2019-06-14 20:55           ` Logo Justin Dorfman
2019-06-15  9:39             ` Logo Jérémie Roquet
2019-06-27 17:13               ` Logo Justin Dorfman
2019-06-27 20:23                 ` Bart Schaefer [this message]
2019-06-27 20:34                   ` Logo Bart Schaefer
2019-06-27 21:13                 ` Logo Sebastian Gniazdowski
2019-06-27 21:35                   ` Logo Bart Schaefer
2019-06-27 22:51                   ` Logo Oliver Kiddle
2019-06-27 23:20                     ` Logo Bart Schaefer
2019-06-28 10:12                       ` Logo Stephane Chazelas
2019-06-28 19:58                         ` Logo Justin Dorfman
2019-07-02 16:54                         ` Logo Sebastian Gniazdowski
2019-07-12  2:45                           ` Logo Justin Dorfman
2019-07-12 18:21                             ` Logo Philippe Troin
2019-07-12 18:46                               ` Logo Bart Schaefer
2019-07-13 12:01                                 ` Logo Oliver Kiddle
2019-07-15 21:07                                 ` Logo Justin Dorfman
2019-07-15 21:30                                   ` Logo Bart Schaefer
2019-07-16  9:55                                   ` Logo Daniel Shahaf
2019-07-16 10:05                                     ` Logo Daniel Shahaf
2019-07-19 20:15                                       ` Logo Justin Dorfman
2019-07-19 21:07                                         ` Logo Daniel Shahaf
2019-07-19 21:14                                           ` Logo Bart Schaefer
2019-07-19 21:17                                         ` Logo Bart Schaefer
2019-07-19 21:30                                           ` Logo Daniel Shahaf
2019-07-19 21:33                                             ` Logo Bart Schaefer
2019-07-20  8:58                                         ` Logo Oliver Kiddle
2019-07-15 20:56                               ` Logo Justin Dorfman
2019-07-12 19:12                             ` Logo Sebastian Gniazdowski
2019-07-13 12:33                               ` Logo Sebastian Gniazdowski
2019-07-13 13:09                                 ` Logo Bart Schaefer
     [not found]               ` <CAEjOAVooT9+U8Cp4FrU7Qo95-AzzyFuF-XxDMGFVWuCC5z-7Qg@mail.gmail.com>
2019-06-27 21:38                 ` Logo Jérémie Roquet

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='CAH+w=7bDqRtDx1_uzxh+OkhYzEo+6fqLUMSMVFAG323BVg-Cog@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=justindorfman@gmail.com \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).