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 #1

Open
dacmot opened this issue Oct 23, 2022 · 6 comments · May be fixed by #2
Open

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

dacmot opened this issue Oct 23, 2022 · 6 comments · May be fixed by #2

Comments

@dacmot
Copy link

dacmot commented Oct 23, 2022

Following a pending change by Pavel, SokolovPavel#11, would you please consider changing the licensing terms accordingly?

@Desour
Copy link
Owner

Desour commented Oct 23, 2022

IIRC, when I rewrote this mod, only trivial code of Pavel was left. So I can probably just drop his license all together.
I still haven't chosen a license for my code though. (I will probably choose something like Apache or MIT.)

@dacmot
Copy link
Author

dacmot commented Oct 23, 2022

I'm not a lawyer, so take my opinion with a grain of salt. That being said, I would question the legality of changing the license of a derivative work. In the case where you have to maintain the license of the original work, you would need to wait for Pavel to change it first.

About using the Apache License from the GPL v2

Please note that this license is not compatible with GPL version 2, because it has some requirements that are not in that GPL version. These include certain patent termination and indemnification provisions. The patent termination provision is a good thing, which is why we recommend the Apache 2.0 license for substantial programs over other lax permissive licenses.

And be careful about using the Expat license:

Some people call this license “the MIT License,” but that term is misleading, since MIT has used many licenses for software. It is also ambiguous, since the same people also call the X11 license “the MIT License,” failing to distinguish them. We recommend not using the term “MIT License.”

@dacmot
Copy link
Author

dacmot commented Oct 24, 2022

Upon further research, going from GPL to Apache doesn't seem possible for derivative work. The question still remains: is it derivative work?

For copyright purposes, there's something called a clean room design that could allow you to claim full copyright of the mod. I don't know if it would be possible to claim that, given that the repository was explicitly forked.

At this point, for a hobby project such as a minetest mod, it might just be simpler to just ask Pavel to re-license to something more permission than GPL.

I hope any of this is useful...

@Desour
Copy link
Owner

Desour commented Oct 24, 2022

For copyright purposes, there's something called a clean room design that could allow you to claim full copyright of the mod. I don't know if it would be possible to claim that, given that the repository was explicitly forked.

IIRC, I haven't looked much into the code of the old mod (it was too broken anyway). I've just reimplemented it. But I haven't started from scratch, which makes things harder now for copyright.

At this point, for a hobby project such as a minetest mod, it might just be simpler to just ask Pavel to re-license to something more permission than GPL.

I agree. However, Pavel isn't active anymore, afaik.
I've also asked him to license his media, but there is still no answer after 3 years: SokolovPavel#8 (The whynot helicopter fork still uses all of that media.)

@Lazerbeak12345
Copy link

In upstream, Pavel just changed license from GPLv2-only to GPLv2-or-later

@Lazerbeak12345
Copy link

Forgot to mention, licences were also added to the images.

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.

3 participants