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

Include Licence #227

Closed
Catarina-Alves opened this issue Mar 9, 2021 · 2 comments
Closed

Include Licence #227

Catarina-Alves opened this issue Mar 9, 2021 · 2 comments
Labels
documentation Updates to documentation required pre-v2.0.0 Issues that should be completed prior to public release of v2.0.0

Comments

@Catarina-Alves
Copy link
Collaborator

Catarina-Alves commented Mar 9, 2021

For legal reasons, any repository should have a license.

GitHub created a website to help people choosing the right licence for each project.

The Guidelines for DESC Repositories (see the file with the same name in the Publication Board) suggest the BSD 3-Clause "New" or "Revised" License. I think it is a good license because it is permissive while forbidding others from using the name of the project or its contributors to promote derived products without written consent.

@Catarina-Alves Catarina-Alves added pre-v2.0.0 Issues that should be completed prior to public release of v2.0.0 documentation Updates to documentation required labels Mar 9, 2021
@MichelleLochner
Copy link
Contributor

@Catarina-Alves I agree with using BSD, I use it for all my repositories.

@Catarina-Alves
Copy link
Collaborator Author

Solved with #228

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Updates to documentation required pre-v2.0.0 Issues that should be completed prior to public release of v2.0.0
Projects
None yet
Development

No branches or pull requests

2 participants