<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 3/18/2015 4:51 PM, Anne Gentle
wrote:<br>
</div>
<blockquote
cite="mid:CAD0KtVEk3fAxj==KPA-+ypQvUBpWV1onSCKzV31iFUBeUNiuXA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Mar 18, 2015 at 12:42 PM,
Steve Gordon <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:sgordon@redhat.com" target="_blank">sgordon@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<div class="HOEnZb">
<div class="h5">
> Are we saying here that current contributors to
the project have not signed<br>
> the CLA? I know this is potentially the case for
authors who contributed to<br>
> books written in sprints using external tools
(Ops Guide, Design Arch Guide)<br>
> but ultimately to get into e.g. openstack-manuals
someone who has signed the<br>
> CLA has to contribute the patch(es) and in doing
so grants copyright to the<br>
> "Project Manager" no? Maybe I am missing
something but I don't understand<br>
> why we would need a second CLA here as the
existing one doesn't specify a<br>
> license either, yet isn't it the mechanism we're
using to distribute using<br>
> Apache 2.0 today?<br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
First off, I can't speak to the Ops Guide but the Design Arch Guide
was all people who'd signed the CLA, I believe, though that's by
happenstance and not by any causation.<br>
<br>
As far as what I remember about the previous expedition:<br>
<br>
In order for us to officially change the license, we needed to find
a way to:<br>
<br>
a) Add the new license to the overall CLA and get everyone to sign
it<br>
b) Get everyone to sign a separate new CLA that specified the new
license<br>
or<br>
c) Find a way to ensure that new contributors knew that their
content was going under a different license than the code.<br>
<br>
Making things further complicated was the fact that some books (the
API Guide?) have substantial amounts of code and need to ALSO have
the ASL, even if we add the CC-BY for the prose part.<br>
<br>
And of course any license changes needed to be approved by the
board, which is, I think, where we eventually ran aground.<br>
<br>
That, and I think the final question was, "Why do we need to do
this, again?"<br>
<br>
---- Nick<br>
<br>
<br>
<br>
<br>
<br>
<br>
<blockquote
cite="mid:CAD0KtVEk3fAxj==KPA-+ypQvUBpWV1onSCKzV31iFUBeUNiuXA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb">
<div class="h5">
><br>
> > The desired outcomes are:<br>
> > - every reader knows the license<br>
> > - all people (corporate contributors,
publishers) know if and how to reuse<br>
> > the docs<br>
><br>
> To be honest from previous discussions (which I
believe kicked off Nick's<br>
> expedition) I thought we had this nailed but now
I'm more confused than when<br>
> we started as it seems like we remain in complete
limbo on this. Currently<br>
> we have:<br>
><br>
> - Some books reporting ASL 2.0: E.g.<br>
> <a moz-do-not-send="true"
href="http://docs.openstack.org/high-availability-guide/content/"
target="_blank">http://docs.openstack.org/high-availability-guide/content/</a><br>
> - Some books reporting CC-BY-SA: E.g.<br>
> <a moz-do-not-send="true"
href="http://docs.openstack.org/openstack-ops/content/"
target="_blank">http://docs.openstack.org/openstack-ops/content/</a><br>
> - Some books reporting BOTH: E.g.<br>
> <a moz-do-not-send="true"
href="http://docs.openstack.org/admin-guide-cloud/content/"
target="_blank">http://docs.openstack.org/admin-guide-cloud/content/</a><br>
><br>
> ...and I have no idea which ones are correct. The
earlier replies seemed to<br>
> indicate we should be displaying both, but more
recent ones seem to indicate<br>
> we should be only displaying ASL 2.0. So in both
my roles, as a downstream<br>
> and as a contributor I can now count myself as
thoroughly confused.<br>
><br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>So sorry Steve, it _is_ confusing. </div>
<div><br>
</div>
<div>I'll give this my full attention when I'm back next
week. Feel free to get more clarification here though!
It's completely possible I'm not remembering everything.</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">
<div class="HOEnZb">
<div class="h5">
> -Steve<br>
><br>
> > - every contributor knows their rights when
they write upstream docs<br>
> > - contributors are not held liable if the
docs are wrong<br>
> > - use of the OpenStack brand and logo still
go through normal brand<br>
> > guidelines<br>
> ><br>
> > That's all I can think of for now. Let me
know if there are additional<br>
> > questions or difference in opinion on the
outcomes we need.<br>
> ><br>
> > Anne<br>
> ><br>
> >
_______________________________________________<br>
> > OpenStack-docs mailing list<br>
> > <a moz-do-not-send="true"
href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
> > <a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
> ><br>
><br>
> --<br>
> Steve Gordon, RHCE<br>
> Sr. Technical Product Manager,<br>
> Red Hat Enterprise Linux OpenStack Platform<br>
><br>
> _______________________________________________<br>
> OpenStack-docs mailing list<br>
> <a moz-do-not-send="true"
href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
> <a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
><br>
<br>
--<br>
Steve Gordon, RHCE<br>
Sr. Technical Product Manager,<br>
Red Hat Enterprise Linux OpenStack Platform<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-docs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a>
</pre>
</blockquote>
<br>
</body>
</html>