On 2016-11-04 22:22:47 +0000 (+0000), Steven Dake (stdake) wrote: [...] > The first file I examine in any repository is the LICENSE file – > if its GPLv3, I look no further. I recommend everyone that has > signed the CLA follow the same pattern to keep OpenStack in good > legal health.
As I understand it, the challenge here is that plugins for Ansible will by definition be derivative works of Ansible and thus inherit their license choice. No amount of "clean room reimplementation" will solve that unless you also reimplement Ansible under a different license while you're at it. If having the ICLA enforced on a repo with GPL code in it is an issue, this could in theory be resolved by putting it in a separate repository with no CLA enforcement. If a plug-in for Ansible being under the same license as Ansible poses a problem for a repo as a deliverable of an official OpenStack project team, then perhaps it could just be distributed in an unofficial repo instead (though this seems overly proscriptive to me). -- Jeremy Stanley __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
