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

Clarifying the license #48

Open
confusedsushi opened this issue Oct 22, 2024 · 4 comments
Open

Clarifying the license #48

confusedsushi opened this issue Oct 22, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@confusedsushi
Copy link

Here in Github it is stated that the project is under GPL 2.0. But this seems only half of the truth. Looking deeper into the project it seems that the directory inc and lib are licensed under license found in licenses/LICENSE.efilib. Is that correct?

@gmbr3
Copy link
Collaborator

gmbr3 commented Oct 23, 2024

BSD-3-Clause parts can be licensed under GPL-2.0-or-later

@confusedsushi
Copy link
Author

The question was meant to be in the other direction. In my project I want to use the stuff from inc and lib but I cannot use GPL things.

@gmbr3
Copy link
Collaborator

gmbr3 commented Oct 23, 2024

As long as the file doesn't state otherwise, inc and lib are BSD-3-Clause

@confusedsushi
Copy link
Author

I wonder if it is then not a good idea to convert inc and lib to a submodule, e.g., efilib, then. This way licensing would be clearer and people who just want to have these could reference then only this. Specifically for it would save some time when discussing with project managers.

@gmbr3 gmbr3 added the enhancement New feature or request label Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants