Skip to content

Please add a license #51

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

Open
nicolas-raoul opened this issue Jan 4, 2022 · 4 comments
Open

Please add a license #51

nicolas-raoul opened this issue Jan 4, 2022 · 4 comments

Comments

@nicolas-raoul
Copy link

Would you mind adding a license?
For instance MIT license or just write in the README "This library is public domain" or something like this.
Without a license, it is not legal to use this library.
Thanks! :-)

@seeseemelk
Copy link

The pom.xml, the readme, and maven central do note that the library is licenced under the Apache 2.0 license. However, a small LICENSE would still be a nice addition.

@CrossVR
Copy link

CrossVR commented Mar 10, 2024

The license is already in the repo, it's just in the resources folder: https://github.com/leonbloy/pngj/blob/master/src/main/resources/LICENSE.txt

@Lonzak
Copy link

Lonzak commented Mar 11, 2024

What he meant is the following:

grafik

@nicolas-raoul
Copy link
Author

Thanks CrossVR for pointing this out, I just had not found it. So, I can start using this library. :-)

Having the license file at the root is expected by both humans and algorithms (such as GitHub metadata extractor as Lonzak points out).
A license is often understood to cover only the directory it is in (and recursively its sub-directories).

Discussion: https://opensource.stackexchange.com/questions/567/where-should-i-place-my-open-source-license-file-in-my-project

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