Skip to content
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

Please consider changing the license from GPLv2-only to GPLv2 or any later version #11

Closed
dacmot opened this issue Oct 23, 2022 · 9 comments · Fixed by #12
Closed

Please consider changing the license from GPLv2-only to GPLv2 or any later version #11

dacmot opened this issue Oct 23, 2022 · 9 comments · Fixed by #12

Comments

@dacmot
Copy link
Contributor

dacmot commented Oct 23, 2022

Would you please consider changing the license from GPLv2-only to "GPLv2 or any later version"? Being GPLv2-only technically prevents it being included in GPLv3 code.

From, Is GPLv3 compatible with GPLv2?

No. Many requirements have changed from GPLv2 to GPLv3, which means that the precise requirement of GPLv2 is not present in GPLv3, and vice versa. For instance, the Termination conditions of GPLv3 are considerably more permissive than those of GPLv2, and thus different from the Termination conditions of GPLv2.

Due to these differences, the two licenses are not compatible: if you tried to combine code released under GPLv2 with code under GPLv3, you would violate section 6 of GPLv2.

However, if code is released under GPL “version 2 or later,” that is compatible with GPLv3 because GPLv3 is one of the options it permits.

@Lazerbeak12345
Copy link

Lazerbeak12345 commented Oct 24, 2022

As a note, along with SokolovPavel, here's the other contributors that probably also need to OK this as well, if their code is still in this project anymore.

Both of those users are more active on github than the maintainer is, and of them, antum is much more active.

@dacmot
Copy link
Contributor Author

dacmot commented Oct 24, 2022

Good point. I think it should be sufficient to reply to this thread saying "I'm ok with the license change from GPLv2-only to GPLv2 or any later version"

Reminds me, I should add a note about contributors in the readme.

@Lazerbeak12345
Copy link

Reposted (in a way) this to the forumn. Pavel's been active there within a year or so. https://forum.minetest.net/viewtopic.php?p=416902#p416902

@Lazerbeak12345
Copy link

Pavel was "Last active:Sat Jan 16, 2021 02:22"

@AntumDeluge
Copy link
Contributor

I don't have any authority for changing license in this project. But I agree that GPL2 or later would be better for users that want to fork this project.

@dacmot
Copy link
Contributor Author

dacmot commented Nov 3, 2022

Thanks @AntumDeluge. That statement is all that is needed from you.

I am not a laywer, so take this with some skepticism: as I understand it, as a contributor, you need to provide your approval to license changes... unless you publicly renounce any and all copyrights on your contributions.

@AntumDeluge
Copy link
Contributor

AntumDeluge commented Nov 7, 2022

GitHub lists me as a contributor because the developer/owner accepted a pull request from me. I am not a member of the project. @SokolovPavel currently is the only member (as far as I know) that can authorize a change to licensing.

Edit: I understand what you are saying, that for the code that I contributed, I need to give my consent. So yes, for the code that I contributed, I consent to changing to GPLv2 or later.

I generally assume that I relinquish rights to licensing to the project when I contribute code. But I can see why legally it is a good idea to get consent from each contributor.

@lightonflux
Copy link
Contributor

I also agree with the proposed changes to licensing.

@Lazerbeak12345
Copy link

Lazerbeak12345 commented Mar 1, 2023

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants