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 C402E9AF9 for ; Tue, 14 Feb 2012 19:04:57 +0000 (UTC) Received: (qmail 26069 invoked by uid 500); 14 Feb 2012 19:04:57 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 25905 invoked by uid 500); 14 Feb 2012 19:04:57 -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 25897 invoked by uid 99); 14 Feb 2012 19:04:57 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Feb 2012 19:04:57 +0000 Received: from localhost (HELO mail-vw0-f47.google.com) (127.0.0.1) (smtp-auth username robweir, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Feb 2012 19:04:57 +0000 Received: by vbbff1 with SMTP id ff1so272012vbb.6 for ; Tue, 14 Feb 2012 11:04:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.22.46 with SMTP id a14mr9723614vdf.27.1329246296078; Tue, 14 Feb 2012 11:04:56 -0800 (PST) Received: by 10.220.179.193 with HTTP; Tue, 14 Feb 2012 11:04:55 -0800 (PST) In-Reply-To: References: <4F39793B.7040308@wtnet.de> Date: Tue, 14 Feb 2012 14:04:55 -0500 Message-ID: Subject: Re: http://www.openoffice.org/ From: Rob Weir To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Feb 14, 2012 at 1:58 PM, Dave Fisher wrote: > > On Feb 14, 2012, at 8:55 AM, Armin Le Grand wrote: > >> =C2=A0 =C2=A0 =C2=A0 Hi Wolf and Dave, >> >> On 14.02.2012 17:23, Wolf Halton wrote: >>> On Tue, Feb 14, 2012 at 10:35 AM, Armin Le Grand= =C2=A0wrote: >> [..] >>> Hi Armin, >>> Now I understand. =C2=A0You're right, It should say Apache OpenOffice, >>> since that ended up being the name we chose. =C2=A0I went and looked at= the >>> Hadoop site http://hadoop.apache.org/ where the Apache part of the >>> name is prominent. =C2=A0Drew made up the logo currently there, I belie= ve. >>> Just changing the logo and maybe a couple of additions to the name in >>> a few text blocks would be good. >> >> Thanks for clarification, and sorry, I just re-checked and indeed I did = not mention that I wanted it to be 'Apache OpenOffice'. Sigh. I'll try to b= e more clear next time. >> >> I cannot remember all of that discussion when to change the branding, bu= t wouldn't people be surprised when we publish an 'Apache OpenOffice 3.4' a= nd they expected an 'OpenOffice.org 3.4' due to the naming conventions on t= he web pages...? Also we already changed the logos in the program and the i= nstallers, AFAIK. > > We have changed the source code. We have changed the graphics - although = more are coming. We may have developer builds. > > We do not have an AOO release. The download button on www.openoffice.org = provides the user with OpenOffice.org 3.3. > > IMO we should wait to change the logo until we have the release. If the c= onsensus is to change now then I think that both the main landing page and = the download pages need some work. > I think we want to start changing in advance of the release. Why? Because we want to ensure legacy OOo users are familiar with the new brand. Otherwise, when we do release, they'll be confused. I understand your point about legacy users being confused if they start seeing new new brand now. But that just argues for doing this intelligently. It does not argue for not doing it yet. We need to communicate the new brand. So we could have a mini-campaign like "OpenOffice.org is now Apache OpenOffice". Blog, announce list, social media, website, etc., do it two weeks before the release is made, say when we have a solid RC ready to vote on (probably not our first RC). Do it along with an "AOO 3.4 is coming soon" tease. > The plan could be: > > (1) Since there is a thread about it. Wait for a final logo treatment fro= m Drew. If not in the next few days then use the one in the podling site as= a placeholder. > > (2) Change the ooo-site header to use the new image. Warning this will be= a "sledgehammer" CMS build, all files are touched. > > (3) If we have one, we should add the contact us link / page in the same = commit / build as (2) I think it belongs on the bottom next to "Copyright &= License". > > (4) Rework www.openoffice.org so the buttons are not so big. Kay has brou= ght this up in another thread. > > (5) Rework www.openoffice.org so that the download experience better sets= user expectations. > > I'll play with some ideas for (4) and (5) this week. > > Regards, > Dave > >> >>> Wolf >>> >>> >> >> Sincerely, >> =C2=A0 =C2=A0 =C2=A0 Armin >> -- >> ALG >> >