Open alfh opened 9 months ago
It should be clear what license is covering the code and the project
A LICENSE file should be in the top level directory of the repo. A dual license could also be used, then more than one file should be there.
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository
Could also add a SECURITY file as well, I think it is good practice to also have such a file, https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository
I really like open source, and having a license and respecting it, is a crucial part of open source
Is your feature request related to a problem? Please describe.
It should be clear what license is covering the code and the project
Describe the solution you'd like
A LICENSE file should be in the top level directory of the repo. A dual license could also be used, then more than one file should be there.
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository
Describe alternatives you've considered
Could also add a SECURITY file as well, I think it is good practice to also have such a file, https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository
Additional context
I really like open source, and having a license and respecting it, is a crucial part of open source