Open Stack

When I worked on manuals for an international association, I used to check the copyright policy of each company whose material we used for support. They varied. In some cases, you could paraphrase, in some only quote. They also had specific notes you were required to use whether in text, footnote, or reference list. So, there are some specifics that are important to state for those who want to write tutorials, blog posts, and larger bodies of work.

On Jan 14, 2014, at 2:33 PM, Rich Bowen <rbowen at redhat.com> wrote:

> 
> On 01/14/2014 02:13 PM, Nermina Miller wrote:
>> Rich, I'd be curious to know what constitutes fair use or the amount of material permitted to be used without an explicit permission request. And, secondly, which entity would be responsible to addressing those requests? Thanks! - Nermina
> 
> The answer to the first question is defined by Copyright law, and I don't have the answer on the tip of my fingers, and it may vary from country to country. Which is why we should sidestep the question entirely by having our documentation licensed in such a way to make the question moot. Which ... I think we do, right? The docs, like the code, are licensed under the Apache license.
> 
> The answer to the second question is "The OpenStack Foundation", and the answer should those requests should always be yes, up to and including someone taking the whole body of documentation and producing a printed version for sale. (See http://www.amazon.com/dp/1596821930/ for an example of just that - the docs for another Apache-licensed project.) This is the spirit of the Apache license, and if we believe that the Apache license is the right one, then that's the only conclusion we can arrive at.
> 
> (Note that I'm an Apache zealot, so take anything I say with that grain of salt.)
> -- 
> Rich Bowen - rbowen at redhat.com
> OpenStack Community Liaison
> http://openstack.redhat.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140114/949e72f9/attachment.html>