-
Notifications
You must be signed in to change notification settings - Fork 68
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
chore: Update license #600
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to copy the license text or is it sufficient to provide the license name and link? W3C has persistent links, so there should be no problem in my little understanding of licensing.
@nitedog this is not just a link, I have copied over the text. |
@JKODU sorry if I was not clear -- I'm proposing to simply link to the license rather than to copy and paste the text. What is the reason for copying the license text? This creates confusion and headache in my view (people have to actually compare if it is the same license text etc.). |
The reason for copy/ pasting the text is that, if and when the original license changes, it does not change the license on this repo automagically. Any license changes will be done via a PR, which will help notify and communicate of such changes. |
Update license to match https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document