Open Stack

Well, as I said earlier, I believe that the spirit of the Apache license 
is that you ALWAYS say yes, to any request to reuse, remix, repurpose, 
re-whatever your documentation content.

If we believe that the Apache license expresses our wishes about our 
project, and if we understand what the license says, then we have no 
reason ever to say no when someone asks to quote from, paraphrase, or 
copy our docs wholesale.

Or our source code, for that matter.

On 01/14/2014 02:54 PM, Nermina Miller wrote:
> Hence my questions :) How DO you deal with such requests?
>
> On Jan 14, 2014, at 2:47 PM, Rich Bowen <rbowen at redhat.com 
> <mailto:rbowen at redhat.com>> wrote:
>
>>
>> On 01/14/2014 02:41 PM, Nermina Miller wrote:
>>> 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.
>>
>> Absolutely, but I presume that none of those products were Open 
>> Source. That changes the game.
>>
>> We're not a software company. We're an Open Source project.
>>
>> -- 
>> Rich Bowen -rbowen at redhat.com
>> OpenStack Community Liaison
>> http://openstack.redhat.com/
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org 
>> <mailto:Openstack-docs at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>

-- 
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/927c4fd3/attachment-0001.html>