<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 20, 2014 at 1:31 PM, Richard Fontana <span dir="ltr"><<a href="mailto:rfontana@redhat.com" target="_blank">rfontana@redhat.com</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Thu, Mar 20, 2014 at 01:12:16PM -0400, Russell Bryant wrote:<br>
> On 03/20/2014 01:06 PM, Russell Bryant wrote:<br>
> > The Nova project is looking to move the content of design specifications<br>
> > to a git repository for the Juno development cycle [1].  The contents of<br>
> > this repository will not be code.  It will primarily be documentation.<br>
> ><br>
> > Right now we put the Apache 2 LICENSE file in the repository and have<br>
> > the same license header in the template used for specifications.<br>
> ><br>
> >   <a href="http://git.openstack.org/cgit/openstack/nova-specs/tree/LICENSE" target="_blank">http://git.openstack.org/cgit/openstack/nova-specs/tree/LICENSE</a><br>
> >   <a href="http://git.openstack.org/cgit/openstack/nova-specs/tree/template.rst" target="_blank">http://git.openstack.org/cgit/openstack/nova-specs/tree/template.rst</a><br>
> ><br>
> > Is this licensing the proper choice here?  If not, what should we use<br>
> > instead?<br>
> ><br>
> > Thanks,<br>
> ><br>
> > [1]<br>
> > <a href="http://lists.openstack.org/pipermail/openstack-dev/2014-March/030576.html" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2014-March/030576.html</a><br>
> ><br>
><br>
> To possibly answer my own question ...<br>
><br>
> I found in a previous thread that the board officially approved using<br>
> CC-BY for documentation here:<br>
><br>
> <a href="https://wiki.openstack.org/wiki/Governance/Foundation/15Oct2012BoardMinutes#Approval_of_the_CCBY_License_for_Documentation" target="_blank">https://wiki.openstack.org/wiki/Governance/Foundation/15Oct2012BoardMinutes#Approval_of_the_CCBY_License_for_Documentation</a>.<br>


><br>
> So perhaps we should be using that since this is effectively<br>
> documentation?  I also expect that this content be used heavily when<br>
> developing the official project documentation based on the features<br>
> described in these specifications.<br>
<br>
</div>Perhaps something that the Foundation staff should decide as part of<br>
implementing the CC BY policy for documentation.<br></blockquote><div><br></div><div>+1</div><div><br></div><div>I know a draft memo is started but it hasn't made it on a Board meeting agenda to my knowledge.</div><div>

<br></div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
 - RF<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
legal-discuss mailing list<br>
<a href="mailto:legal-discuss@lists.openstack.org">legal-discuss@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss</a><br>
</div></div></blockquote></div><br></div></div>