-
Notifications
You must be signed in to change notification settings - Fork 9
Newly submitted collection hpe.nimble uses Apache-2.0 license #2
Comments
People were hesitant to allow more licenses without legal approval but also wanted to get this question resolved in time for collections with other licenses to be included for ansible-4.0. In an attempt to move this forward, I'll make a proposal for next meeting that opens the door partially to other licenses (limited to GPLv3+ compatible licenses and modules). |
(see link in https://meetbot.fedoraproject.org/ansible-community/2021-03-31/ansible_community_meeting.2021-03-31-18.00.html for the log of the discussion) |
A new interim licensing guideline has been approved that allows GPLv3+ compatible licensing in module and module_utils code. This should remove the blocker on hpe.nimble's licensing. Thanks for bringing this issue up! |
I've mentioned the result here: ansible-collections/ansible-inclusion#13 (comment) |
We can probably close this issue since the |
SUMMARY
Currently the newly submitted collection hpe.nimble for inclusion uses
Apache-2.0
license which MUST be changed toGPL v3
as we only allowGPLv3+
(and optionally BSD-2-clause for module_utils).The text was updated successfully, but these errors were encountered: