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

Clarify license #46

Open
Shachar opened this issue Feb 3, 2024 · 2 comments
Open

Clarify license #46

Shachar opened this issue Feb 3, 2024 · 2 comments

Comments

@Shachar
Copy link

Shachar commented Feb 3, 2024

The project does not declare an open source (or any other) license. This makes it impossible to know whether I can use it inside my own project.

Ideally, the project's root should have a license file, and each file in the project should have a short header declaring that this file is governed by that license. This would avoid confusion about whether the project can be used.

Adding a license can only be done by the actual copyright holder.

@Shachar
Copy link
Author

Shachar commented Feb 3, 2024

To clarify, the project has two license files (and very similar licenses, while at it), no reference to license in the files themselves, and no declaration in the project's github metadata. It is unclear whether it's under MIT, Apache, either, some files are 1 and some the other, or whether these files are just part of some template and don't apply to the project.

@sameer
Copy link
Member

sameer commented Feb 3, 2024

Hi Shachar, the project is dual licensed under MIT and Apache-2.0. This gives upstream projects the flexibility to use it under either, depending on requirements.

I'll look into why GitHub isn't showing that, thanks for bringing this up.

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

2 participants