[legal-discuss] License for design specifications (blueprints)

Russell Bryant rbryant at redhat.com
Fri Mar 21 18:52:41 UTC 2014


On 03/21/2014 11:58 AM, Jonathan Bryce wrote:
> On Mar 20, 2014, at 12:12 PM, Russell Bryant <rbryant at redhat.com> wrote:
> 
>> On 03/20/2014 01:06 PM, Russell Bryant wrote:
>>> The Nova project is looking to move the content of design specifications
>>> to a git repository for the Juno development cycle [1].  The contents of
>>> this repository will not be code.  It will primarily be documentation.
>>>
>>> Right now we put the Apache 2 LICENSE file in the repository and have
>>> the same license header in the template used for specifications.
>>>
>>>  http://git.openstack.org/cgit/openstack/nova-specs/tree/LICENSE
>>>  http://git.openstack.org/cgit/openstack/nova-specs/tree/template.rst
>>>
>>> Is this licensing the proper choice here?  If not, what should we use
>>> instead?
>>>
>>> Thanks,
>>>
>>> [1]
>>> http://lists.openstack.org/pipermail/openstack-dev/2014-March/030576.html
>>>
>>
>> To possibly answer my own question ...
>>
>> I found in a previous thread that the board officially approved using
>> CC-BY for documentation here:
>>
>> https://wiki.openstack.org/wiki/Governance/Foundation/15Oct2012BoardMinutes#Approval_of_the_CCBY_License_for_Documentation.
>>
>> So perhaps we should be using that since this is effectively
>> documentation?  I also expect that this content be used heavily when
>> developing the official project documentation based on the features
>> described in these specifications.
> 
> Correct. Since this is new documentation, not embedded in source code, it falls under that Board resolution and can go out with CC-BY. Thanks,

Thanks for the clarification.

One more point: which version of CC-BY?

  http://creativecommons.org/licenses/by/4.0/

  http://creativecommons.org/licenses/by/3.0/us/

-- 
Russell Bryant



More information about the legal-discuss mailing list