zsh-users
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Zsh Users' List <zsh-users@zsh.org>,
	Justin Dorfman <justindorfman@gmail.com>
Subject: Re: New Zsh Logo
Date: Sat, 15 Jan 2022 14:00:36 +0000	[thread overview]
Message-ID: <20220115140036.GA30217@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <dcd6d3b4f2260bd18c49a20a65721b088df9e837.camel@ntlworld.com>

Peter Stephenson wrote on Wed, Jan 12, 2022 at 19:56:36 +0000:
> Hi all,
> 
> Justin Dorfman has offered to produce a new logo for zsh for use on the website
> etc.  Because this needs to be sorted out quickly for project management reasons,
> Bart Schaefer, Oliver Kiddle, Daniel Shahaf and I have been looking at this,
> however, I'm sure a lot more people are interested.
> 

I haven't actually been looking at the logos.  I was invited to, but
I declined.

And I'd like to add that if anyone has other drafts/sketches of a logo,
or even just ideas, do feel free to share them on the -workers@ part of
this thread.

Daniel


> Rather than post the near final set of choices here, I'll put them on the
> higher bandwidth zsh-workers list, so look out there if you're interested.
> To my untrained eye, it seems to be down to quite minor details, but I'm sure
> you'll let us know if you don't trust us!
> 
> To be quite clear: this doesn't actually affect the shell itself at all,
> it's just for visual effects in documentary material.  The only way it would
> affect the shell that I can see would be if we decided to change the Windows
> icon.  The current one was drawn by me many years ago, I think in Microsoft
> Paint, so that sounds like a possibility, but that would be an entirely
> separate decision with its own consultation.
> 
> Cheers
> pws
> 
> 
> 


  parent reply	other threads:[~2022-01-15 14:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 19:56 Peter Stephenson
2022-01-13 16:50 ` Ray Andrews
2022-01-13 16:54   ` Roman Perepelitsa
2022-01-13 18:18     ` Ray Andrews
2022-01-15 14:03     ` Daniel Shahaf
2022-01-13 17:03   ` Peter Stephenson
2022-01-15 14:06     ` Daniel Shahaf
2022-01-15 14:00 ` Daniel Shahaf [this message]
     [not found] <CANLP0SoveC_z+D2oDOwsfMnKv66ztZJmnKwMn2_KT8uandi4Xg@mail.gmail.com>
2022-01-13 16:55 ` Amir Ish-Hurwitz

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=20220115140036.GA30217@tarpaulin.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=justindorfman@gmail.com \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=zsh-users@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).