-
Notifications
You must be signed in to change notification settings - Fork 30
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
License issue #76
Comments
damn, this is a real pickle... normally this wouldn't be a problem, but since ploy_ansible uses ansible as library (which is actually not even supported by ansible) it seems indeed, that we are limited in our choice of licensing... i'm not sure how re-licensing works but my personal preference would be to make ploy_ansible optional and simply limit ploy_ansible's license to GPLv3. thanks for reporting and i'll keep this issue open as a reminder |
I would request the project stake holders to re-license this under the standard licenses like the MIT or the three clause BSD license, and commit a file listing the license in the repository to make it clear. References- FreeBSD recommends to use standard BSD license, wherever possible Beerware is not recognized by many |
thanks @mzs114 for the nudge. i really want to clean this up and do 'the right thing™'... |
This code may be GPLv3.
bsdploy/setup.py
Line 15 in 7fc3e04
The
license
insetup.py
should reflect this is Beerware license by the copyright holder, but it's dependent on a gplv3 library. This has to be removed for the project to be permissive Beerware.#75 seems to be an alternative.
The text was updated successfully, but these errors were encountered: