From: Justin Dorfman <justindorfman@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Logo
Date: Wed, 5 Jun 2019 09:50:04 -0700 [thread overview]
Message-ID: <CAEjOAVrJFbmGjecc1qqB8z2KrXnVJmzNR3nr9kQOeveE+ErUFg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7aoydaP17Z+Xx2KXBwqVGqMPX-VTMXCxO72ExSbcoei6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
@Oliver you give me the go ahead and I'll make it happen.
@Bart
> Agree. At the risk of being pushy, maybe a few options to choose from?
Not pushy at all. That is what we did for the bash logo:
https://opensource.com/article/16/12/bash-logo-community
The logo will belong to the Zsh community, they should help choose IMO.
Regards,
Justin Dorfman
@jdorfman
<http://www.twitter.com/jdorfman>
On Wed, Jun 5, 2019 at 8:52 AM Bart Schaefer <schaefer@brasslantern.com>
wrote:
> On Wed, Jun 5, 2019 at 12:57 AM Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> >
> > Justin Dorfman wrote:
> > > I was wondering if you would be interested in a free, no strings
> attached
> > > logo. FWIW I was the art director for the Bash logo.
> >
> > Definitely. That would be great.
>
> Agree. At the risk of being pushy, maybe a few options to choose from?
>
> > > I see people using the "oh my zsh" logo as the "Zsh" logo which isn't
> correct.
> >
> > It's not correct in more ways than one
>
> In related news, nic.sh responds:
> Z is not a valid domain name for .sh. It is too short. Minimum 2 chars.
>
next prev parent reply other threads:[~2019-06-05 16:51 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 ` Justin Dorfman [this message]
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 ` Logo Bart Schaefer
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=CAEjOAVrJFbmGjecc1qqB8z2KrXnVJmzNR3nr9kQOeveE+ErUFg@mail.gmail.com \
--to=justindorfman@gmail.com \
--cc=schaefer@brasslantern.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).