-
Notifications
You must be signed in to change notification settings - Fork 370
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 clarification needed #28
Comments
The reason is because I wrote it initially prior to uploading ( hence wrote the GPL3 in the headers, which was my aim) but selected the GPL2 in github when I uploaded (since it wanted an actual file license copy by default, rather than just headers). To change it ( in my view) requires unanimous agreement of all the contributors, which we didn't get in moving away from GPL. Do you have a specific need where you want to use one, that the other won't allow ? |
Just trying to figure out which one is the real license. This issue isn't about changing the license. It's about stating specifically which license is in effect. |
My intention originally was GPLv3 - so if anyone wanted to start a legal debate on it, the lawyers would probably go to the "intent" when there are differences - so they'd probably argue for GPLv3 From a personal viewpoint exactly which isn't that important to me - unless someone has a specific requirement, then I'm happy to chat through that specific case. |
The LICENSE file is GPLv2, but individual files say GPLv3 in the header.
Are GPLv2 terms available, or only v3 and later?
The text was updated successfully, but these errors were encountered: