Please clarify the License of tld
Closed this issue · 7 comments
Hello, I am the maintainer of python-tld in Fedora/EPEL
Currently the licence information in the README file says:
License
MPL 1.1/GPL 2.0/LGPL 2.1
But I want to ask if this mean "MLP or GPL or LGPL" or "MPL and GPL and LGPL" of convination of those.
Regards
Reference:
It's a triple license. You choose one that is most suitable to you. For example, if GPL is too strict, you may choose LGPL (which is much less strict).
OK, I have updated the license tag acording to this info
https://src.fedoraproject.org/rpms/python-tld/c/3ab7d067c24488cddfd0646aa7c74775e2301e81
@barseghyanartur piggy backing on this question to avoid noise, several repositories of yours have a license such as __license__ = 'GPL 2.0/LGPL 2.1' .... but nowhere do you say if it is a choice or not. It could be that using an SPDX license expression instead would make you intentions crystal clear?
that would be this for instance: GPL-2.0-only OR LGPL-2.1-or-later
See https://spdx.org/ids-how
Thanks for mentioning the SPDX format. I didn't know of it. I'll fix that in future releases.
How would you put it in? Could you make a pull request with the changes proposed?
In these places
Line 51 in d421696
- https://github.com/barseghyanartur/tld/blob/d42169625c573f63364f8343c83dc9ce316ca120/README.rst#license
Line 6 in d421696
- and in all the places where you have a
__license__attribute
use:
MPL-1.1 OR GPL-2.0-only OR LGPL-2.0-or-later
Ideally use this throughout to consistent: today you are using a setup.py that does not match your readme that does not match what you have in code files or the doc.
You can also have a single clearer badge https://img.shields.io/badge/license-MPL--1.1%20OR%20GPL--2.0--only%20OR%20LGPL--2.0--or--later-blue.svg
Done, thanks!