incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roberto Galoppini <rgalopp...@geek.net>
Subject Re: [PROPOSAL] "Get it here" community download promotion program
Date Mon, 14 May 2012 16:20:41 GMT
On Mon, May 14, 2012 at 5:55 PM, drew <drew@baseanswers.com> wrote:

> On Mon, 2012-05-14 at 10:57 -0400, Rob Weir wrote:
> > On Mon, May 14, 2012 at 9:47 AM, Roberto Galoppini <rgaloppini@geek.net>
> wrote:
> > > On Mon, May 14, 2012 at 3:27 PM, Rob Weir <robweir@apache.org> wrote:
> > >
> > >> On Sun, May 13, 2012 at 2:23 PM, Dave Fisher <dave2wave@comcast.net>
> > >> wrote:
> > >> >
> > >> > On May 13, 2012, at 7:45 AM, Rob Weir wrote:
> > >> >
> > >> >> We get regular requests from individuals and companies that want
to
> > >> >> add a link to the AOO download, and to use the logo with it. 
These
> > >> >> range from websites of individual users, to websites that aggregate
> > >> >> download links for many open source projects.
> > >> >>
> > >> >> Currently, requesting and receiving such permission requires a
> request
> > >> >> to the PMC, approval and then additional approval by the Apache
VP
> > >> >> Branding.
> > >> >>
> > >> >> I'd like to propose a streamlined approach where we can give
> blanket
> > >> >> permission, without an additional request, for using a specific
> logo
> > >> >> (the one that Drew designed) for a specific download situation.
 If
> > >> >> there are no objections from the PMC, and we get a +1 from
> > >> >> Trademarks@, I'll write this up on the website.
> > >> >>
> > >> >> =Use of the Apache OpenOffice Download Promotion Logo=
> > >> >>
> > >> >> Anyone, without additional permission from this project, may use
> the
> > >> >> following logo subject to the following conditions:
> > >> >>
> > >> >> The logo:
> > >>
> https://cwiki.apache.org/confluence/download/attachments/27834483/get-aoo-300x100-cf.png?version=1&modificationDate=1331970198000
> > >> >>
> > >> >> [NB. We should move this to a more memorable location]
> > >> >>
> > >> >> Conditions:
> > >> >>
> > >> >> 1. The logo may not be modified except to resize it.  If
> translations
> > >> >> of the "Get it here!" text are required, send a request to the
> ooo-dev
> > >> >> list and we can provide a translated version for you.
> > >> >
> > >> > There should be a minimum size.
> > >> >
> > >>
> > >> Did you have a specific size in mind?  Or would we state it more
> > >> qualitatively, like "The logo may be resized, provided it remains
> > >> legible, but may not be otherwise altered".
> > >>
> > >> >>
> > >> >> 2. The image must be linked to one of:
> > >> >>
> > >>
> > >> This should probably be wored as "The image must be directly linked to
> > >> one of..."    I don't think we want to allow use of the logo in cases
> > >> where it links to a different install program that installs adware and
> > >> then invokes the real installer.
> > >>
> > >
> > > Agree 100%, unfortunately few downloads websites add adware, tool-bars
> as
> > > well as malicious software.
> > > You might want to explicitely state that the download page can't be
> > > wrapped, though.
> > >
> >
> > To be precise:  if someone "wraps" the download, then they are not
> > eligible for this "Get it here!" program that would give automatic
> > permission to use this specific logo.  But if they have a good reason
> > for wrapping, then they are free to do that in two ways;
>
>
If they wrap you don't have any way to provide the end user with the hash,
though.


> > 1) By not using the AOO logos
> >
> > or
> >
> > 2) By requesting explicit permission to use the AOO logos.  We would
> > evaluate these requests on a case-by-case basis, just as we do now for
> > all requests.
> >
> >
> > So the point of the logo program is not to define absolute
> > prohibitions.  The idea is just to carve out an area that we are
> > comfortable allowing the use of the logo without any further review by
> > the PMC.  IMHO this should include restrictions that prevent the most
> > common abuses that we are aware of.  But this is not an absolute
> > prohibition.  It just means if you want to do something outside of
> > this particular promotion program you need to take the longer path of
> > asking explicit permission.
>
>
> Hi,
>
> Yes, I understand the details of what we are talking about, thanks.
>
> First - To my thinking there is really only one issue - do they deliver
> an unaltered copy of the official binary release package?
>
> If yes, they are in compliance and how they do so is of no concern to
> us.
>

Easiest way to be sure they don't alter is us being the download site.
Anything else need to be checked, and unfortunately sometimes things change
over time, so it's a continuous process.


>
> If no, then they are not in compliance and we should ask them to change
> or stop.ok, well actually I disagree with some of where Rob is heading
> with this
>
> However that is for the most general case.
>
> In this specific case, an expedited, no request required use, I agree
> that one adds conditions.
>
> My only real concern here is that these conditions should be kept to an
> absolute bare minimum. The vast majority of folks who will do this are
> honest agents and they will try to comply, for those who would do
> something a bit nefarious they won't care what we write.
>
> So - I would just stick with:
>
> They must acknowledge (disclose) the trademark owner (ASF) on their
> site.
>
> I would just give one link and say this is what you use:
> http://www.openoffice.org/download/
>
> Finally, I would insist that the actual link be tied to the graphic - if
> you fly the graphic then clicking on the image must take you to that
> address - i.e Get it Here!
>
> end of requirements.
>

I'm fine with this description.


>
> In the case of the particular use request before us, that site as
> currently constructed would actually fail those requirements (The logo's
> used do not link, rather they have a separate download button) - but it
> would be easy enough for them to come into compliance. (having the
> download button in addition to the image link would not be an issue)
>
> The only other question in my mind is whether to let them have the logo
> or make them reference the logo from our servers - I've set this type of
> thing up both ways and don't really have a strong preference. In this
> specific situation I would lean to the 'we dish up the image' route,
> only because the branding is in a state of flux and it makes it easy to
> execute the branding change with minimal fuss on our part down the road.
>

Good point, having it at our website makes easy to change it.

Roberto

>
> Anyway - just my thoughts.
>
> //drew
>
> >
> >
> > -Rob
> >
> > > Roberto
> > >
> > >
> > >>
> > >>
> > >> >> a) the http://www.openoffice.org webpage
> > >> >> b) one of the official Native Language pages at openoffice.org,
> e.g.,
> > >> >> http://de.openoffice.org
> > >> >> c) the download page for Apache OpenOffice:
> > >> >> http://download.openoffice.org or
> > >> >> http://www.openoffice.org/download/other.html
> > >> >>
> > >> >> 3. The logo must not link to a specific download file or mirror.
>  This
> > >> >> causes problems with load balancing and fallbacks and may prevent
> > >> >> users from getting the latest version of OpenOffice.
> > >> >>
> > >> >> 4. Any use Apache-owned logos beyond the above is not covered
by
> this
> > >> >> program an must be explicitly requested from the ASF.
> > >> >
> > >> > +1 to the proposal.
> > >> >
> > >> > Regards,
> > >> > Dave
>

-- 
====
This e- mail message is intended only for the named recipient(s) above. It 
may contain confidential and privileged information. If you are not the 
intended recipient you are hereby notified that any dissemination, 
distribution or copying of this e-mail and any attachment(s) is strictly 
prohibited. If you have received this e-mail in error, please immediately 
notify the sender by replying to this e-mail and delete the message and any 
attachment(s) from your system. Thank you.


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message