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

Licensing and the inclusison of boilerplate notices #7

Open
tretherington opened this issue Nov 24, 2019 · 0 comments
Open

Licensing and the inclusison of boilerplate notices #7

tretherington opened this issue Nov 24, 2019 · 0 comments

Comments

@tretherington
Copy link
Member

tretherington commented Nov 24, 2019

There is some confusion I think around exactly where to put the license information. The current emphasis is on including a LICENSE file in the repository, but we should also be including a 'boilerplate notice' in every script file - as is outlined by the GNU in their description of How to Apply These Terms to Your New Programs and How to use GNU licenses for your own software.

Choose a license also provides guidance for how to apply each licence, and while MIT does not suggest using a boilerplate notice, both GNU GPL and the Mozilla Public License do. So there is some inconsistency here that could do to be resolved.

@tretherington tretherington changed the title Where to put license information Licensing and the inclusison of boilerplate notices Nov 24, 2019
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

1 participant