-
Notifications
You must be signed in to change notification settings - Fork 231
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
GPLv3 / LGPLv3 license? #146
Comments
Changing the license likely requires contacting every prior contributor and gaining their agreement. What is the reason you'd like to change the license? |
Actually we don't have to contact every contributor as long as we also keep the original notice. The reason I want to switch to GPL is simply because I think it's better for free software. Plain GPL disallows incorporating it into proprietary software altogether, LGPL requires publishing the source code of the library if any changes were made to it. |
Does this mean the old license would still apply in perpetuity? If so, what does the project gain by having two licenses? |
As far as I understand, MIT should only apply to the version with no GPL changes in it, which can only be extracted by looking at git log, So it should make (L)GPL the only practically applicable license. Here's an aricle, see section 2.2. |
I was thinking about switching to GPL-3.0-or-later or at least to LGPL-3.0-or-later. Do you think it would be good?
The text was updated successfully, but these errors were encountered: