<div dir="ltr"><div dir="auto"><div><br></div><div><br>On Mar 24, 2015, at 4:57 PM, Radcliffe, Mark <<a href="mailto:Mark.Radcliffe@dlapiper.com" target="_blank">Mark.Radcliffe@dlapiper.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I am not sure that I understand the question about source/output. Is this code?</span></p></div></div></blockquote><div><br></div><div>It is marked up text or image content that is then built from the simple source to styled html or PDF. Generally, the OpenStack documentation consists of:</div><div>- text that is embedded in the software code: <a href="http://docs.openstack.org/developer/nova">http://docs.openstack.org/developer/nova</a></div><div>- text that is scraped from the software code via an automated process such as <a href="http://docs.openstack.org/cli-reference/content/">http://docs.openstack.org/cli-reference/content/</a></div><div>- text that is created separately from the code (but still in a git repository with "builds" from source to output) such as <a href="http://docs.openstack.org/openstack-ops/content/">http://docs.openstack.org/openstack-ops/content/</a></div><br><blockquote type="cite"><div><div><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I think that we need to keep ASL2 for code in the guides since the bylaws require it.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p></div></div></blockquote><div><br></div><div>Yes, for actual code snippets we plan to keep and indicate Apache 2. </div><div><br></div><div>However in an October 2012 board meeting they approved use of CC- by for content. </div><div><a href="https://wiki.openstack.org/wiki/Governance/Foundation/15Oct2012BoardMinutes">https://wiki.openstack.org/wiki/Governance/Foundation/15Oct2012BoardMinutes</a><br></div><div><br></div><div>So I'm trying to find out how to provide a consistent licensing display.</div><div><br></div><div>Hope that clarifies -</div><div>Thanks,</div><div>Anne</div><div><br></div><div><br></div><br><blockquote type="cite"><div><div>
<p class="MsoNormal"><b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"> Anne Gentle [<a href="mailto:annegentle@justwriteclick.com" target="_blank">mailto:annegentle@justwriteclick.com</a>]
<br>
<b>Sent:</b> Tuesday, March 24, 2015 2:34 PM<br>
<b>To:</b> <a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.openstack.org</a>; <a href="mailto:legal-discuss@lists.openstack.org" target="_blank">legal-discuss@lists.openstack.org</a><br>
<b>Subject:</b> [legal-discuss] docs licenses: current state and desired state<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hi all, <u></u><u></u></p>
<div>
<p class="MsoNormal">As promised I investigated the current state of our community guides license indicators and added to the wiki page at <a href="https://wiki.openstack.org/wiki/Documentation/ContentSpecs" target="_blank">https://wiki.openstack.org/wiki/Documentation/ContentSpecs</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Current states:<br>
OpenStack Architecture Design Guide: Apache 2.0 and CC-by-sa 3.0<br>
OpenStack Cloud Administrator Guide: Apache 2.0 and CC-by-sa 3.0<br>
<br>
OpenStack Install Guides (all): Apache 2.0<br>
OpenStack High Availability Guide: Apache 2.0<br>
OpenStack Configuration Reference: Apache 2.0<br>
<br>
OpenStack Security Guide: CC-by 3.0<br>
Virtual Machine Image Guide: CC-by 3.0<br>
OpenStack Operations Guide: CC-by 3.0<br>
OpenStack End User Guide: CC-by 3.0<br>
OpenStack Admin User Guide: CC-by 3.0<br>
Command-Line Interface Reference: CC-by 3.0<br>
<br>
Contributor dev docs (<a href="http://docs.openstack.org/developer/" target="_blank">docs.openstack.org/developer/</a><projectname>): none indicated in output; Apache 2.0 in repo<br>
OpenStack API Quick Start: none indicated in output; Apache 2.0 in repo<br>
API Complete Reference: none indicated in output; Apache 2.0 in repo<br>
<br>
Infrastructure User Manual: none indicated in output; CC-by 3.0 in repo<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Desired state:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">CC-by 3.0 indicated in the output for all guides.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Apache 2.0 also indicated in the output for guides containing code and content.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Tasks:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Change first five listed guides to CC-by 3.0 in source and output.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Change API Quick Start to RST so that cc-by 3.0 can be easily indicated.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Questions:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">On guides where the output doesn't indicate a license but the source does; is that sufficient?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks for the help -- I can take the tasks on myself, but would like guidance on whether a license indicator on output is required.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Anne<u></u><u></u></p>
</div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<p class="MsoNormal">Anne Gentle<br>
<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
<span style="font-size:11px"><font style="font-size:11px" color="#008000">Please consider the environment before printing this email.</font></span><font style="font-size:11px" color="#008000">
<br>
<br>
<font color="#808080" size="1" face="Verdana">
The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to <a href="mailto:postmaster@dlapiper.com" target="_blank">postmaster@dlapiper.com</a>. Thank you.
<br>
</font></font>
</div><div><font style="font-size:11px" color="#008000"><font color="#808080" size="1" face="Verdana"><br></font></font></div></blockquote></div></div>