Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <E0D1BF4F-1897-4639-97C2-1A6BC13F295A@comcast.net>
References: 
 <CAO4+hqPu-R1E-1MeB4h6N53LFGiHgPP3O-WVdGyx-XPz84MJQw@mail.gmail.com>
	<4F7AAE00.9080908@googlemail.com>
	<CAP-ksogfZshPaXv_b-pWXQ2F71LJW_=5gO+SZaUMYCBsBsezZA@mail.gmail.com>
	<E0D1BF4F-1897-4639-97C2-1A6BC13F295A@comcast.net>
Date: Tue, 3 Apr 2012 14:19:33 -0400
Message-ID: 
 <CAP-ksoiN+BJXn4okQW4NKvQfahj4Kc6qD=_yJzeqRg1hrf8ygw@mail.gmail.com>
Subject: Re: logo source files
From: Rob Weir <robweir@apache.org>
To: ooo-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8f3bac5b4202d204bcca5980

--e89a8f3bac5b4202d204bcca5980
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 3, 2012 at 1:33 PM, Dave Fisher <dave2wave@comcast.net> wrote:

>
> On Apr 3, 2012, at 10:10 AM, Rob Weir wrote:
>
> > On Tue, Apr 3, 2012 at 4:00 AM, J=C3=BCrgen Schmidt
> > <jogischmidt@googlemail.com>wrote:
> >
> >> On 4/3/12 9:41 AM, Kevin Grignon wrote:
> >>
> >>> @Drew
> >>>
> >>> Where do we keep the source files for the logos?
> >>>
> >>>
> >> I would like to suggest that we should create a new place for this kin=
d
> of
> >> stuff besides trunk
> >>
> >>
> > +1.  Getting it into SVN makes it easy to get to from the build and the
> > website.
>
> The logo is used in the build and is part of the release. We have the
> difficult question here about distributing logos that are trademarks. The=
y
> are included in our convenience binaries and installers and distributions
> go out, etc. A corporation might make internal changes and re-roll the
> package, these may be slight or be drastic.
>
>
The logo files may be included in a the release, but Clause 6 of the ALv2
gives only limited use of those trademarks,  So if someone did take the
code and make significant changes to it, they do not necessarily have the
rights to still use the logos.   They certainly have the rights to change
the logo to one of their own.


> At what point does the name and logo have to change? How do we make it
> easy for the downstream provider to fulfill any requirement like this?
>
>
I think that is the key question -- how do we make it easy to rebrand?

With Symphony, for example, we made this very easy.  Not need to rebuild at
all. We did it with a plugin, so making a RobOffice or DaveOffice would be
within reach of anyone:

http://www-03.ibm.com/software/lotus/symphony/plugin.nsf/web_DisplayPlugin?=
openform&unid=3D22E742258B098B2A852577C30027A24D&category=3DMiscellaneous&f=
orm=3Dhome


> For AOO 4.0 do we need a build switch that will replace all AOO graphics
> with "AOO inside" / user provided graphics?
>
>
Build option or something easier if possible.


> Should there be an ODF conformance test?
>
>
Whatever the rules are they must be easy to explain and easy to implement.
> The rules must translate to many languages without becoming ambiguous.
>
> Rob and I did a thought experiment a couple of months ago on what is AOO
> and what is not. I think that we should revisit when the current
> discussions on general@i.a.o reach a conclusion. Dennis has cataloged
> many (all?) of the logo's appearances in the UI.
>
> Regards,
> Dave
>
> >
> >
> >> Juergen
> >>
>
>

--e89a8f3bac5b4202d204bcca5980--