Skip to content
This repository has been archived by the owner on May 14, 2024. It is now read-only.

Newly submitted collection hpe.nimble uses Apache-2.0 license #2

Closed
Ompragash opened this issue Mar 31, 2021 · 5 comments
Closed

Newly submitted collection hpe.nimble uses Apache-2.0 license #2

Ompragash opened this issue Mar 31, 2021 · 5 comments
Labels
collection inclusion request Include new collections into the ansible package. discussion_topic next_meeting Topics that needs to be discussed in the next Community Meeting

Comments

@Ompragash
Copy link
Member

SUMMARY

Currently the newly submitted collection hpe.nimble for inclusion uses Apache-2.0 license which MUST be changed to GPL v3 as we only allow GPLv3+ (and optionally BSD-2-clause for module_utils).

@abadger
Copy link

abadger commented Mar 31, 2021

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).

@felixfontein
Copy link
Contributor

@abadger
Copy link

abadger commented Apr 7, 2021

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!

@felixfontein
Copy link
Contributor

I've mentioned the result here: ansible-collections/ansible-inclusion#13 (comment)

@tadeboro
Copy link

We can probably close this issue since the hpe.nimble collection maintainers changed the license of the documentation fragment: hpe-storage/nimble-ansible-modules#39

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
collection inclusion request Include new collections into the ansible package. discussion_topic next_meeting Topics that needs to be discussed in the next Community Meeting
Projects
None yet
Development

No branches or pull requests

4 participants