On Sun, Dec 30, 2012 at 6:14 AM, Peter Junge <peter.ju...@gmx.org> wrote: > Hi, > > from time to time there are requests to bundle OpenOffice with 3rd party > products. A typical case is that a publishing house wants to release a > commercial box in which they bundle an original version of Apache OpenOffice > with a handbook (either printed or electronic) and some goodies like a pack > of templates. As I'm expecting such cases will pop-up frequently (mostly at > private@, hence they're not too visible here), it would be good to have some > guidelines in place. I have drafted some, please review and comment. The > result is intended to be submitted as a proposal here and should go on our > website later. >
You need to review this with Shane as well. Remember, the PMC does not control the OpenOffice trademarks. Apache does, and Shane has delegated authority in these matters. > Happy New Year > Peter > > ----------------------------- > > === Guidelines for redistributing (an original) Apache OpenOffice with 3rd > party bundles === > > 1) You must solely use an unmodified binary version of Apache OpenOffice > that can be downloaded by anyone from > http://www.openoffice.org/download/index.html. If you build your own product > from the Apache OpenOffice sources, then you must give your product a > different name that must not be confused with Apache OpenOffice. Under > certain circumstances, you may then use 'Powered by Apache OpenOffice'. For > details, please refer: > http://www.apache.org/foundation/marks/faq/#poweredby > I think this is mixing up two different things: 1) Building exactly AOO from the source, with no additional material bundled. This would be a port, like the BSD or Solaris or OS/2 port. Are you saying that these may not be called "Apache OpenOffice"? 2) Distributing AOO bundled with other stuff. In that case the AOO portion may still be called "Apache OpenOffice", of course. But the question is what do you call the bundle as a whole? IMHO, the "powered by" name was not intended for bundling. It was intended for embedding, when an Apache program was used as a component behind the scenes for some processing, e.g., run on the server to generate PDF's, etc. But to have a bundle of AOO + templates or other content and call it "Foo Office, Powered by Apache OpenOffice" is a big fail, since the product splash screen, the title bar and the about box, not to mention the installer, will still all say "Apache OpenOffice". > 2) You must always use the proper name 'Apache OpenOffice x[.y[.z]]' (e.g. > 3.4.1) for our product. IMPORTANT: Do NOT use 'Apache Open Office' or > 'Apache OpenOffice.org' or 'OpenOffice' or 'Open Office' or 'OpenOffice.org' > etc. > ??? We just said in #2 that "you must give your product a different name that must not be confused with Apache OpenOffice". And now you are saying something (what?) must be referred to as the proper name "Apache OpenOffice 3.4.1". This doesn't work well for another reason: there is nothing that requires that someone build a bundle from exactly a released version of AOO. It might not be exactly 3.4.1. It might be pre 4.0, or 3.4.1 + fixes. How exactly it is named may cause or prevent confusing for support and bug tracking, > 3) Do not use any additions to 'Apache OpenOffice x.y.z' with the title of > your bundle that imply that you are shipping a product which is superior to > Apache OpenOffice, e.g. you must not use a title like 'Apache OpenOffice > 3.4.1 Professional'. You may rather use the title 'Apache OpenOffice 3.4.1' > with a subtitle like '{YOUR_BRAND} Professional Pack' because you have added > value to an original Apache OpenOffice. > OK. > 4) If you want to use the Apache OpenOffice logo on your bundle, you must > solely use the original, unmodified Apache OpenOffice logo: > https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/images/AOO_logos/svg/OOo_Website_v2_copy.svg > I would not favor giving any blanket permission to use the primary logo. It should be used rarely, only with explicit permission, and on a case-by-case basis. If the volume of requests is so high that it is burdensome to review them all then we should make a special logo just for just bundles. But don't give away the crown jewels without review. For example compare the vendors who may use the "Intel Inside" logo versus who is permitted to use the "Intel" logo. You make a special logo for bundling. > 5) You must attribute the Apache Software Foundation and it's trademarks > with all components of your bundle (e.g. Cover, Box, printed Book, > electronic book, CD/DVD etc.). A proper attribution is: > --- > "Apache",[ the “Apache logo”,] "Apache OpenOffice", "OpenOffice" and the > “Apache OpenOffice logo” are trademarks of the Apache Software Foundation > (http://www.apache.org) > --- > For the detailed Apache Trademark Policy, please refer: > http://www.apache.org/foundation/marks/ > > 6) You must make clear with all components of your bundle (e.g. Cover, Box, > printed Book, electronic book, CD/DVD etc.) that you are providing an > unmodified version of Apache OpenOffice with your bundle. A proper way to do > that it adding an informative statement like: > --- You are setting conditions here that are beyond ALv2. We cannot require more than the license requires. The license permits free redistribution, original or unmodified. They are free to call it "Apache OpenOffice" if it is in fact Apache OpenOffice. We have zero basis for making any additional demands. The exception would be if this was in return for us offering them something beyond what the license gives. For example, in return for use of a logo, or in return for listing them on a special "bundles" page on the website, we require adherence to these additional guidelines. > "Includes the original Apache OpenOffice 3.4.1 as provided by the Apache > Software Foundation under Apache License Version 2 at > http://www.openoffice.org/download/";. > --- > Again, we cannot demand this. > 7) Your setup routine must clearly distinguish between installing Apache > OpenOffice and the additional products of your bundle. > We cannot demand this. > 8) There may be exceptions to the guidelines as above, but they must be > explicitly permitted by the Apache Software Foundation. > Not really, unless we are offering something they want beyond what is given by ALv2. > 9) You must contact the Apache OpenOffice Project Management Committee at > priv...@openoffice.apache.org before releasing your bundle so our community > is able to review it. Please keep in mind that these are just guidelines and > granting you the privilege to use 'Apache OpenOffice' with your bundle is at > the sole discretion of the Apache Software Foundation on a case by case > basis. IMHO, you are overstating the PMC's control over the use of the name "Apache OpenOffice". See: http://en.wikipedia.org/wiki/Nominative_use I'd refocus this effort on what we, as a project, can do to help bundles, and what minimal protections we require to protect the brand in return. For example, we could define a program which bundlers could voluntarily adhere to. If they do they are given placement on our website and maybe use of a special "Includes Apache OpenOffice" logo. In return they agree to specific trademark acknowledgement requirements. And finally, let's not forget that the real abuses out there, the ones that cause our users real pain, involve distribution of old versions of OpenOffice with a "downloader" or "pre-installer" that causes bloatware to be installed on the user's system. Nothing I read above deals with that. In any case, thanks for bringing this up. I've brought the topic up several times over the last 18 months, with little success. Maybe this time we reach a critical mass of understanding of the issue and its complexities. Regards, -Rob
