-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
module_utils/cloud.py is licensed GPLv3+ #131
Labels
Comments
@abadger Thanks for bringing this up. We're not currently deviating from the general Ansible project policies so this is definitely an issue. |
ansibullbot
added
affects_2.10
bug
This issue/PR relates to a bug
has_pr
needs_triage
labels
Aug 27, 2020
To date we've gotten consent from every contributor except one (many via direct emails). As we do not have agreement from all contributors we'll be re-implementing this. |
alinabuzachis
pushed a commit
to alinabuzachis/amazon.aws
that referenced
this issue
Sep 22, 2022
goneri
pushed a commit
to alinabuzachis/amazon.aws
that referenced
this issue
Sep 23, 2022
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this issue
Sep 18, 2023
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this issue
Sep 18, 2023
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this issue
Oct 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
This module_utils file is licensed GPLv3+ rather than BSD:
https://github.com/ansible-collections/amazon.aws/blob/main/plugins/module_utils/cloud.py
This was a problem in the ansible/ansible repo as module_utils files were supposed to be licensed BSD so that third parties could use the code even if their code was licensed under an GPLv3 incompatible license. I'm not sure if the same policy exists for the amazon.aws collection. If not, you can close this (and you may want to license new contributions to the other module_utils files under the GPLv3+ so that it's easier to explain the licensing requirements).
If that policy does hold, then you'll need to do something about this file. The PR in the ansible/ansible repo never got sign off from the author and other contributors: ansible/ansible#28372 so you may need to reimplement this functionality from scratch rather than getting it relicensed.
ISSUE TYPE
COMPONENT NAME
ANSIBLE VERSION
Problem exists in current HEAD: 5cfd130
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: