Open Stack

On Thu, Jul 2, 2015 at 10:58 PM, Alison Holloway <alison.holloway at oracle.com
> wrote:

>  Anne,
>
> Thanks for your super fast response. Our Legal team won't give me approval
> unless the licensing information is crystal clear. I'll see what they say
> with this email from you as to whether that's enough for them.
>

I'd be happy to get the Legal teams connected. I'll send a separate email
now.


>
> Just to clarify, the clouddocs-maven-plugin docs are the DocBook based
> ones, right? All new and updated content is going into the RST-based docs?
>

Yep, that's right.

Thanks,
Anne


>
>
> Alison
>
>
> On 03/07/15 13:44, Anne Gentle wrote:
>
>
>
> On Thu, Jul 2, 2015 at 10:35 PM, Alison Holloway <
> alison.holloway at oracle.com> wrote:
>
>>  Hi all,
>>
>> I would like to reuse some of the upstream doc content, but the licensing
>> seems to vary for each of the core books. This is what I each book is
>> currently licensed under:
>>
>> OpenStack High Availability Guide
>> - Apache License, Version 2.0
>>
>> OpenStack Networking Guide
>> - Creative Commons Attribution 3.0 License
>>
>> OpenStack Operations Guide
>> - Creative Commons Attribution 3.0 License
>>
>> OpenStack Security Guide
>> - Creative Commons Attribution 3.0 License
>>
>> OpenStack Virtual Machine Image Guide
>> - Creative Commons Attribution 3.0 License
>>
>> OpenStack Architecture Design Guide
>> - Apache License, Version 2.0
>> - Creative Commons Attribution 3.0 License
>>
>> OpenStack Cloud Administrator Guide
>> - Apache License, Version 2.0
>> - Creative Commons Attribution 3.0 License
>>
>> From my reading of the related bug on this issue, the code should be
>> under the Apache 2 license and the docs should be under the Creative
>> Commons 3 license.
>>
>> https://bugs.launchpad.net/openstack-manuals/+bug/1433868
>>
>> This bug is on the wishlist, and doesn't look like it's going to be
>> attended to any time soon. How can I expedite this fix? Is this a fix that
>> I might be able to take on as my first OpenStack doc bug fix, or is this
>> something one of the XSLT experts should take on?
>>
>
>  Hi Alison,
> I've discussed this item with the OpenStack Foundation, and we want people
> to feel free to reuse the docs as long as you're not using the OpenStack
> logo in the branding of the re-used doc.
>
>  We don't plan to do another release of clouddocs-maven-plugin for
> another year (or never if we keep the RST migrations moving along).
>
>  So please feel free to find another bug to work on, and re-use the docs
> as you see fit.
>
> Thanks,
> Anne
>
>
>>
>> Alison
>>
>> --
>>  Alison Holloway | Consulting Technical Writer | +61 3 8616 3717
>> <%2B61%203%208616%203717>
>> Oracle VM, and Oracle OpenStack for Linux Product Development
>> Melbourne, Australia
>>
>> _______________________________________________
>> OpenStack-docs mailing list
>> OpenStack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>>
>
>
>  --
>  Anne Gentle
> Rackspace
> Principal Engineer
> www.justwriteclick.com
>
>
> --
>  Alison Holloway | Consulting Technical Writer | +61 3 8616 3717
> Oracle VM, and Oracle OpenStack for Linux Product Development
> Melbourne, Australia
>



-- 
Anne Gentle
Rackspace
Principal Engineer
www.justwriteclick.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20150702/17213ffe/attachment.html>