-
-
Notifications
You must be signed in to change notification settings - Fork 615
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
LICENSE? #17
Comments
Not sure if it's a must but the license text does say 'shall'. The reason I didn't include the license file is the same as why Remy did it http://remysharp.com/2011/10/18/a-public-mit-license-resource/ |
The blog post is mistaken. Other licenses, like GPL, have explicit carve outs that allow you to merely provide instructions for accessing the license (so a URL is fine in that case). While I agree that the term "shall" is somewhat ambiguous, similar uses of the word (in other software licenses) use "shall" to indicate compulsion, and there is no harm to including the license file in the repo. Useful read: http://blog.nig.gl/post/48848761220/just-saying-something-is-gpl-mit-apache-doesnt Sent from my iPhone
|
you must include license text for MIT license
The text was updated successfully, but these errors were encountered: