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
Unclear licensing #422
Comments
It is now GPLv3 and was originally Apache I don’t think any work was done to do a formal license change so it is probably dual licensed at this point. |
Ticket can be closed |
michaellass
added a commit
to michaellass/AUR
that referenced
this issue
Jul 26, 2023
Additionally, let's add Apache to the list of licenses. It looks like the authors do not know how the code is licensed and also do not care as they do not plan to clarify this. Best guess is that it is dual licensed under GPL3 and Apache. See meshtastic/python#422
archlinux-github
pushed a commit
to archlinux/aur
that referenced
this issue
Jul 26, 2023
Additionally, let's add Apache to the list of licenses. It looks like the authors do not know how the code is licensed and also do not care as they do not plan to clarify this. Best guess is that it is dual licensed under GPL3 and Apache. See meshtastic/python#422
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The LICENSE.txt in this repository contains the Apache 2.0 license and hence this is what GitHub shows as license for this package. However, the license specified in setup.py has been changed to GPLv3 in #392. Before that, it was specified as MIT in setup.py.
So, what is the current license of this code? If GPLv3, could the LICENSE.TXT be updated? If Apache, setup.py should reflect that as well.
The text was updated successfully, but these errors were encountered: