Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0CC5E9C74 for ; Mon, 23 Jan 2012 09:34:22 +0000 (UTC) Received: (qmail 57079 invoked by uid 500); 23 Jan 2012 09:34:17 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 56713 invoked by uid 500); 23 Jan 2012 09:34:04 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 56694 invoked by uid 99); 23 Jan 2012 09:34:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jan 2012 09:34:00 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of orwittmann@googlemail.com designates 209.85.212.175 as permitted sender) Received: from [209.85.212.175] (HELO mail-wi0-f175.google.com) (209.85.212.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jan 2012 09:33:53 +0000 Received: by wiwc10 with SMTP id c10so852661wiw.6 for ; Mon, 23 Jan 2012 01:33:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=l5EcGZ11gHxnw74rG5xzoSeuiVGm0P5MEO/1m24ymR8=; b=v6+/eQ09XjjOIzfyjOeGwBEjfVxmlnhYSrTDBS5YZ/sakYJlhFxhYnlrJ9E+PM/1ZF hK02NU9uAIjhnTtiWtbUVTTyDvDA4N1Qr70HWaccraLXUNcUZdfdRMIQPzloqj/HBDg+ yfqggsMv/27FjyZ+mQ4sI5AceLalEebAZPYnY= Received: by 10.180.94.97 with SMTP id db1mr11981073wib.16.1327311213510; Mon, 23 Jan 2012 01:33:33 -0800 (PST) Received: from [9.155.131.30] (deibp9eh1--blueice3n2.emea.ibm.com. [195.212.29.180]) by mx.google.com with ESMTPS id eq5sm39181758wib.2.2012.01.23.01.33.32 (version=SSLv3 cipher=OTHER); Mon, 23 Jan 2012 01:33:32 -0800 (PST) Message-ID: <4F1D296F.6030903@googlemail.com> Date: Mon, 23 Jan 2012 10:33:35 +0100 From: Oliver-Rainer Wittmann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: New icons proposed for version 3.4 References: <4F1C91A6.8020900@apache.org> <4F1D1CE1.20804@googlemail.com> In-Reply-To: <4F1D1CE1.20804@googlemail.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 23.01.2012 09:40, J�rgen Schmidt wrote: > On 1/22/12 11:45 PM, Andrea Pescetti wrote: >> I don't know how many people monitor Bugzilla, so I'm reposting here a >> proposal for new icons for Apache OpenOffice 3.4 (I merely noticed it in >> Bugzilla, I'm not involved with it at all): >> >> https://issues.apache.org/ooo/show_bug.cgi?id=118820 >> >> The icons can be seen at >> >> http://0dd0ne.deviantart.com/gallery/?offset=24#/d2dw9dt >> >> and they look rather nice to me. They would be suitable for Apache >> OpenOffice 3.4 too, since they still use the previous design elements >> (those currently used in Apache OpenOffice trunk) but add a fresher >> look. Any thoughts? I would only discuss the six application icons for >> the time being, and only focus on the design, not licenses or >> permissions (read the issue for those, and we can investigate further if >> we decide to give the proposed icons a try). >> > > I am not sure if we should do that for 3.4. Reverting the icons back to the > former well accepted icons was ok and a necessary step. But if we intend to do > some more branding rework for a 4.0, then I would prefer to keep the current > icons. We don't have any pressure here and we can focus on such a rebranding > after the 3.4. Important from my pov is the overall goal of the rebranding and > that it is consistent in all branding elements we want to change. > I agree here with J�rgen. All the branding items of our project should be consistent. There is no need from my point of view to hurry through the rebranding for AOO 3.4. Let us aim for the release following AOO 3.4 for these rebranding tasks. Best regards, Oliver.