Open tony opened 9 years ago
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- Beerware considered harmful- https://romanrm.net/beerware
FreeBSD recommends to use standard BSD license, wherever possible https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/pref-license.html
Beerware is not recognized by many https://en.wikipedia.org/wiki/Beerware
thanks @mzs114 for the nudge. i really want to clean this up and do 'the right thing™'...
This code may be GPLv3.
https://github.com/ployground/bsdploy/blob/7fc3e0498b9c29bff8401b0ad5b9c3b7ba0df126/setup.py#L15
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.