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

Licensing mismatch #9

Open
hyandell opened this issue Nov 8, 2023 · 4 comments
Open

Licensing mismatch #9

hyandell opened this issue Nov 8, 2023 · 4 comments

Comments

@hyandell
Copy link

hyandell commented Nov 8, 2023

I wanted to flag that the repository marks its licensing as Apache-2.0, but contains the following LGPL-2.1 licensed file:

https://github.com/hibernate/quarkus-local-cache/blob/main/src/main/java/org/infinispan/quarkus/hibernate/cache/PutFromLoadValidator.java

I'm unsure if that's intended, so wanted to raise the issue.

@yrodiere
Copy link
Member

yrodiere commented Nov 9, 2023

Looks like this file was copied from Infinispan, another ASL 2 licensed project, where it also has this header.

I was able to trace back the history of this file to the Hibernate ORM project, which I guess explains the license.

Anyway, from CONTRIBUTING.md (emphasis mine):

All original contributions to this project are licensed under the
ASL - Apache License,
version 2.0 or later, or, if another license is specified as governing the file or directory being
modified, such other license
.

@Sanne We might want to relicense this file, though, both here and in Infinispan.

@gsmet
Copy link
Member

gsmet commented Nov 9, 2023

I think we need a clear license for the component as a whole. And if there is one LGPL file, it cannot be ASL, even if the rest is ASL.

So let's relicense this file.

@emmanuelbernard
Copy link
Member

For info and trivia, it is a possibility to define a component distribution under one license and have some of the files under a different one. Or so I remember from conversations with our lawyer friends.
But it tends to bring confusion so +1 to re licensing the file.

@gsmet
Copy link
Member

gsmet commented Nov 9, 2023

Highly depends on the license. With LGPL and GPL, my guess is that you have to make the whole component LGPL/GPL.

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

No branches or pull requests

4 participants