Hi, Tom! if it would be really just the color issue your suggestion looks straighforward.
But did you ever noticed that bad press was stopped by a reply? Especially when a larger part of readers probably thinks there's some truth in the critic? A reply doesn't change behaviour so it doesn't fix the problem if there's one. And, on the internet, it will make people believe their comments will be read, and used. If that doesn't happen, it will just lead to more frustration. For example, the editor mail reads "I have ideas if you're interested." Cool. If we don't ask for his ideas we're just a bunch of idiots that won't listen. If we ask for his suggestion, but don't implement them, we're a bunch of idiots that can't fix things even if the 'obvious' solutions are given to them. A reply will also look like a weak excuse for assumed errors (true or not). The option of blogging about the critic will a) make the replier look arrogant because it changed the place of discussion, and b) will make replies inconsistant and weak. And it will trigger more (bad) press because the press likes conflicts. You can't win a discussion with a journalist. Cheers, Claus On Tue, 16 Aug 2005 00:20:06 +0100 Tom Chance <[EMAIL PROTECTED]> wrote: > > *Warning* KDE lurker jumping in... :o) > > How about just authoring a considered response or two in blogs / > elsewhere, then submitting your own story to Slashdot to the effect > of "here's a criticism of GNOME, and here's our considered response". > Be open and honest but also put the flamebaiting to rest. > > Really, if anyone can get that worked up at the lack of control over > the colour of the window title bar then an adult response from you > guys will only make the article (assuming it's similar in tenor to > the forwarded email) look like a childish spat covering some > interesting issues. > > *Back to hole from which I clambered* > > Regards, > Tom > -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list