unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: new version of the proposed emacs icons
Date: Sat, 09 Feb 2008 09:41:27 +0100	[thread overview]
Message-ID: <8563wywmh4.fsf@lola.goethe.zz> (raw)
In-Reply-To: <200802082357.m18NvkTG015950@sallyv1.ics.uci.edu> (Dan Nicolaescu's message of "Fri, 08 Feb 2008 15:57:46 -0800")

Dan Nicolaescu <dann@ics.uci.edu> writes:

> Richard Stallman <rms@gnu.org> writes:
>
>   >     A number of people were questioning why are we changing icons.
>   > 
>   > I do not insist that we change.  And if we change, I do not insist
>   > we pick one of these two.
>
> OK, so let's find a way to move forward with this.
>
> One of the most sensible comments that was made about the icons was that
> we had a different icon for each major version.  We can use the proposed
> icon for emacs-23.
>
> Given that we don't really have an overabundance of artists willing to
> work on things like this, and that the proposed icons look really good,
> let's check in version 1 (it leads by one vote).

Which shows that both are bad compromises and the good solution would be
in the middle, as mentioned several times.

> We have to show some goodwill here.  There's enough time to refine the
> icon until 23.1 is released.
>
> Does this sound like a sensible plan?

If it is really impossible to give the artist the constructive feedback
about the comments voiced here, I don't see how the "goodwill" is going
to reach him either.  Have you at least _tried_ directing some of the
comments back to him or letting him read this thread?  Or is he to be
kept in the dark and we should just pick from whatever he delivers
without giving feedback?  Do you really think that this is an effective
manner of working?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum




  parent reply	other threads:[~2008-02-09  8:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200802041612.m14GCq7w003656@sallyv1.ics.uci.edu>
     [not found] ` <E1JMCYQ-0003KC-8J@fencepost.gnu.org>
     [not found]   ` <200802070442.m174gVln014478@sallyv1.ics.uci.edu>
2008-02-08 18:48     ` new version of the proposed emacs icons Richard Stallman
2008-02-08 23:57       ` Dan Nicolaescu
2008-02-09  0:37         ` Miles Bader
2008-02-09  1:46         ` Drew Adams
2008-02-09  3:08           ` Dan Nicolaescu
2008-02-09  8:43             ` David Kastrup
2008-02-09  2:58         ` Nick Roberts
2008-02-09  3:11           ` Dan Nicolaescu
2008-02-09  8:41         ` David Kastrup [this message]
2008-02-10  3:20         ` Richard Stallman
     [not found]           ` <200802100759.m1A7xXlg025221@sallyv1.ics.uci.edu>
     [not found]             ` <E1JOMLy-0001cj-LY@fencepost.gnu.org>
     [not found]               ` <200802110240.m1B2ePIw013083@sallyv1.ics.uci.edu>
     [not found]                 ` <E1JOfv1-00062o-5D@fencepost.gnu.org>
2008-03-02 18:19                   ` Dan Nicolaescu
2008-03-02 19:40                     ` Stefan Monnier
2008-03-02 19:51                       ` Jason Rumney
2008-03-02 21:06                         ` Stefan Monnier
2008-03-03 21:17                           ` Glenn Morris
2008-03-03 22:24                             ` Stefan Monnier
2008-03-03 22:29                               ` Jason Rumney
2008-03-03 22:36                                 ` Glenn Morris
2008-03-03 22:35                               ` Glenn Morris
2008-03-03 22:51                                 ` Stefan Monnier
2008-03-02 19:49                     ` Jason Rumney
2008-03-03  0:45                     ` Jason Rumney
2008-03-03  3:53                     ` Kentaro Ohkouchi
2008-03-03  7:39                     ` Jan Djärv
2008-03-03  0:22 Angelo Graziosi
2008-03-03  0:34 ` Jason Rumney
2008-03-03  8:34   ` Angelo Graziosi
2008-03-03 22:32     ` Jason Rumney

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8563wywmh4.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).