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

License Confusion #52

Closed
patrickplynch opened this issue May 23, 2024 · 2 comments
Closed

License Confusion #52

patrickplynch opened this issue May 23, 2024 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@patrickplynch
Copy link

Hello cssutils team,

I just want to make sure that this project is indeed licensed under the LGPL v3.0. As such, is there any reason to include the GPL license (via the /COPYING file) in the source code?

Thanks for your time!

@jaraco jaraco added the question Further information is requested label Jun 1, 2024
@jaraco
Copy link
Owner

jaraco commented Jun 1, 2024

cssutils is dual-licensed, covered by both licenses. Therefore, yes, the project is indeed licensed under the LGPL v3.0.

As such, is there any reason to include the GPL license (via the /COPYING file) in the source code?

Although I am not a lawyer, my understanding is that a user of the project may elect any suitable license for their use. That is, for this project, a user may use it under the GPL or the LGPL license. I don't know if that means the GPL is entirely subsumed by the LGPL.

Thought about another way, does the LGPL license grant the right to remove the GPL license? I think it does.

More importantly, when the license files were added by the original author (f106612), their prose indicated "cssutils is published under the LGPL 2.1 or later", suggesting that the GPL license was superfluous from the start.

I'll remove the GPL license.

@jaraco jaraco self-assigned this Jun 1, 2024
@jaraco jaraco closed this as completed in 21ab9c9 Jun 1, 2024
jaraco added a commit that referenced this issue Jun 1, 2024
Renamed to LICENSE to align with the convention from jaraco/skeleton.

Closes #52
@jaraco
Copy link
Owner

jaraco commented Jun 1, 2024

Note that I force-pushed c77a435 over 21ab9c9 (which was a mistake).

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

No branches or pull requests

2 participants