You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
tretherington
changed the title
Where to put license information
Licensing and the inclusison of boilerplate notices
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.
The text was updated successfully, but these errors were encountered: