July 2017 - legal-discuss - lists.openstack.org

[tc][kolla] Distribute Ansible module with Kolla
by duonghq＠vn.fujitsu.com 02 Aug '17

02 Aug '17

Hello everyone, I'm looking for legal advice about distribute Ansible module within Kolla. In order to implement one feature in Kolla, I need developing one Ansible strategy plugin, which in turn need to include and inherit from a couple of modules of Ansible. Kolla does not use the plugin directly, Kolla will invoke Ansible (through popen) and Ansible uses this plugin. The question is, can I distribute this plugin along with Kolla-Ansible deliverable? Thanks, Ha Quang Duong (Mr.) IRC duonghq PODC - Fujitsu Vietnam Ltd.

3 2

License issue & Need help
by HoangCX＠vn.fujitsu.com 27 Jul '17

27 Jul '17

Hi, We are recently trying to propose a Netlink solution [1] in order to improve performance for Neutron's Security Group. Almost the thing is ready to go except for license issue as we are not so familiar with this area. The problem is come from some parts of code we used that based on MIT license (not Apache 2 license). So need to get help for the following points: 1. Can we mix MIT license and Apache 2 license in a same file like [2]? 2. We have LICENSE file at the top directory. Is it okay to have a file with some different license under the tree and publish it as part of neutron distribution? Any feedback and help are really appreciated. [1] https://review.openstack.org/#/c/470911/ [2] https://review.openstack.org/#/c/470911/20/neutron/privileged/agent/linux/n… Thanks, Hoang

2 1

Hosting a non-official GPLv3 OpenStack project
by David Moreau Simard 25 Jul '17

25 Jul '17

Hi, I'm the author of ARA [1] which is not an official OpenStack project: - It is not governed by the OpenStack foundation or the technical committee - It does not require the OpenStack CLA/ICLA for contributions - It is not a deliverable of any OpenStack project For me, ARA falls in the same category of software that was created by the OpenStack community as Jenkins Job Builder [2] and git-review [3]. >From the licensing requirements documentation [4]: > Projects run as part of the OpenStack Infrastructure (in order to produce OpenStack software) may be licensed under any OSI-approved license. > This includes tools that are run with or on OpenStack projects only during validation or testing phases of development (e.g., a source code linter). It would likely fit in what was previously known as "stackforge". While ARA is currently labelled with an Apache 2.0 license, some components of it are coupled to Ansible which is GPLv3. For the purpose of simplicity and avoid headaches around dual licensing (worry about what we are importing where, etc.), I am currently considering re-licensing ARA as GPLv3. Doing this re-licensing now rather than later is desirable before ARA gets too many contributors from different companies which may complicate a re-licensing. My question is the following: Would this re-licensing mean that ARA could no longer be hosted by the OpenStack community infrastructure ? What are other ramifications I might be missing ? Thanks, [1]: https://gihtub.com/openstack/ara [2]: https://github.com/openstack-infra/jenkins-job-builder [3]: https://github.com/openstack-infra/git-review [4]: https://governance.openstack.org/tc/reference/licensing.html David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter]

3 2

GPLv2 dependency in puppet-neutron?
by ZZelle 12 Jul '17

12 Jul '17

Hi everyone, While working on puppet-neutron, i discovered that puppet-neutron depends on the sysctl puppet module[1] which is GPLv2 (be careful to not confuse it with another sysctl module[2] which is apache2). This dependency has been added a long time ago (in juno or before). It seems we have a license issue (ie: apache2 code depends on GPLv2 code)? [1] https://github.com/duritong/puppet-sysctl [2] https://github.com/thias/puppet-sysctl Cédric/ZZelle@IRC

2 1