-
Notifications
You must be signed in to change notification settings - Fork 40
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
Policy Change: Field of Web Technologies definition and copyright license #114
Comments
I support this change. |
A checklist of what needs updating to fully resolve this:
Most of these were identified by @annevk in #115 (comment). Thanks! |
I've cloned and grepped for "Apple, Google, Mozilla, Microsoft" across all repos in the whatwg org to see if there are any additional places missing, but I don't think there is. |
I've had a look at https://help.github.com/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository#detecting-a-license and the documentation of https://github.com/licensee/licensee to see if it's possible to have our licenses still be automatically detected. Multiple licenses appears to be unsupported by the tooling, and I've also failed to make it work with both two files ( However, the consequence of this is not very serious, if we go with a single |
This issue is going to be held up a bit to get legal input on the notice wording in #115. However, in the meantime we can prepare the pull requests for all the places that need updating, and sync wording it it changes. |
The Field of Web Technologies portion of this has landed and is now in effect. Still reviewing the copyright license portion. |
It's long overdue to close this. The Field of Web Technologies change was applied, and the licensing change was carried over to #155. |
IPR policy change, consult your legal team. These changes come into effect on May 18. 45 days notice is hereby given.
The WHATWG IPR policy is being updated. There are two pending changes:
Please refer to the associated pull request for details.
This will resolve #67.
The text was updated successfully, but these errors were encountered: