-
Notifications
You must be signed in to change notification settings - Fork 17
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
Relicense to Ecma #136
Relicense to Ecma #136
Conversation
I talked with Aki -- let's present this as in progress to the committee and wait until I get written confirmation from Google&Firefox. |
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.
This was approved by Google and Mozilla. The license/copyright text is now the same as in the ECMA-262 spec.
debc2ff
to
1982b1d
Compare
1982b1d
to
94abd57
Compare
SHA: eb4a5fc Reason: push, by nicolo-ribaudo Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: 9b1d5a8 Reason: push, by nicolo-ribaudo Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
The README.md still references the CC license. |
This PR changes the license of the specification to match Ecma's requirements. We can do it because:
For (2), there is a 60 days period during which Ecma members can say "actually, we are not ok with this". If that happens (hopefully not!), we will need to ask to the Ecma General Assembly for an exception to be able to publish under the old license.
cc @littledan @gesa @SaminaHusain