Define “touching GPLv3 code”. If you mean using someone else’s work which creates a derived work, that is a big no-no. This would cause your CL
If it’s a fresh implementation, then USE ASL2.0. This creates a transitive dependency that taints the module on instantiation, however, since we use Ansible via popen rather than an import ansible line in our python code, the module taints as GPLv3 (even though the module may be licensed under ASL 2.0). This does not run afoul of the GPLv3. Regards -steve From: Michał Jastrzębski <[email protected]> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Date: Friday, November 4, 2016 at 9:42 AM To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: [openstack-dev] [tc][kolla] Ansible module with GPLv3 Hello, As you could see in [1], ansible is notorious with it's GPL v3 license. I have question about having single module in Kolla-ansible project that will be GPL v3. Kolla is licensed as Apache v2 all across the board today. To implement one of highly requested features we would need to develop so-called strategy plugin for ansible, and I can't see any reasonable way to do it without touching GPL v3 code. While I wouldn't mind having single GPL v3 licensed module in Kolla, and this particular use case doesn't seem to affect licensing of other parts of our project, I would like to ask for second opinion before we run into legal issues. [1] http://lists.openstack.org/pipermail/openstack-dev/2016-May/095489.html __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]<mailto:[email protected]>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
