[Openstack-docs] Copyright statements in docs source files

Nick Chase nchase at mirantis.com
Tue Jan 14 19:23:12 UTC 2014


I've been working with the lawyer on this. If there is interest in a
session on docs licensing I would be happy to put it together,  unless
someone else wants to.
On Jan 14, 2014 1:45 PM, "Colin McNamara" <colin at 2cups.com> wrote:

> So, on one hand we have a perceived reticence to contribute to copyrighted
> works (which I believe is a valid point)
>
> On the other hand, we have the reality that clearly stating copyright on a
> file helps to protect the contributors in the community (by clearly
> demonstrating who holds copyright)
>
> This may be a good opportunity for an article on OpenStack.org as well a
> session at the design summit.
>
> Regards,
>
> Colin
> *Colin McNamara*
> People | Process | Technology
> --------------------------------------------
> *Mobile*:  858-208-8105
> *Twitter: *@colinmcnamara <http://www.twitter.com/colinmcnamara>
> *Linkedin*: www. <http://www.linkedin.com/colinmcnamara>
> linkedin.com/in/colinmcnamara <http://www.linkedin.com/colinmcnamara>
> *Blog*: www.colinmcnamara.com
> *Email*: colin at 2cups.com <//colin at 2cups.com>
>
>
>
>
>
>
>
> On Jan 14, 2014, at 11:30 AM, Rich Bowen <rbowen at redhat.com> wrote:
>
>
> On 01/14/2014 01:23 PM, Steve Gordon wrote:
>
> ----- Original Message -----
>
> Maybe I'm reading this incorrectly, but my interpretation is that
> there's one big copyright page where this information should go, versus
> on individual pages, which is what I think the original question is about.
>
> I believe it refers to the page being edited, if you can find a central
> page listing all the copyright attributions currently present in OpenStack
> I'll be impressed (there's 200+ variations in Nova alone). What I believe
> Rich was referring to is this type of attribution which is (very) prevalent
> in the OpenStack code base - including in the developer documentation
> within those repos:
>
>
> http://git.openstack.org/cgit/openstack/ceilometer/tree/doc/source/install/dbreco.rst
>
>
>
> That was in fact the actual file I was editing as I sent that email.
>
> I've actually had people ask me, when looking at files like this, if they
> have to ask the author for permission to submit patches against that file.
> If we can avoid making people even think that thought, we've done a good
> thing for the community.
>
> See also
> http://producingoss.com/en/managing-volunteers.html#territoriality for
> another take on this issue, just in case Karl's voice carries more weight
> than mine.
>
> --
> Rich Bowen - rbowen at redhat.com
> OpenStack Community Liaison
> http://openstack.redhat.com/
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140114/aeab5c21/attachment-0001.html>


More information about the Openstack-docs mailing list