Skip to content
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

Use the W3C SOFTWARE AND DOCUMENT NOTICE AND LICENSE #433

Merged
merged 4 commits into from
Apr 25, 2018

Conversation

silviapfeiffer
Copy link
Member

This brings the spec in line with the LICENSE.md file of the WebVTT repo
https://github.com/w3c/webvtt/blob/gh-pages/LICENSE.md

This brings the spec in line with the LICENSE.md file of the WebVTT repo
https://github.com/w3c/webvtt/blob/gh-pages/LICENSE.md
@palemieux palemieux self-requested a review April 3, 2018 16:30
Copy link
Contributor

@palemieux palemieux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since WebVTT is intended to be published on the Rec Track, that CLA needs to match that at https://github.com/w3c/imsc/blob/master/CONTRIBUTING.md

@silviapfeiffer
Copy link
Member Author

@palemieux I'm confused - what are you suggesting? Can you make a new pull request for it?

@palemieux
Copy link
Contributor

palemieux commented Apr 4, 2018

@silviapfeiffer This PR suggests that "Contributions to Specifications are made under the W3C COMMUNITY CONTRIBUTOR LICENSE AGREEMENT (CLA)". I think contributions to WebVTT going forward should be made under the TTWG CLA since the contributions are intended to be integrated in a Rec Track document, which are governed by the W3C Patent Policy and Document License. The TTWG CLA require a patent licensing commitment upfront from contributors.

@palemieux
Copy link
Contributor

@silviapfeiffer See proposal at #438

@silviapfeiffer
Copy link
Member Author

OK so #438 is suggesting a change on the repository which includes use of the license that this PR is suggesting to update the spec to.
Can we please land this PR so the spec conforms to the more modern W3C document license?

@palemieux
Copy link
Contributor

palemieux commented Apr 24, 2018

@silviapfeiffer Happy to limit this PR to fixing the specification, and defer #438 to a different issue. Seemed more logical to fix all license issues together. P.S.: Did you check if the revised text passes pubrules?

@silviapfeiffer
Copy link
Member Author

Not yet. Will do before landing. 😀

@silviapfeiffer
Copy link
Member Author

Marked as non substantive for IPR from ash-nazg.

@silviapfeiffer
Copy link
Member Author

I had to mark it as non-substantive to merge, because I'm currently in the process of transferring to Invited Expert status, sigh.

@silviapfeiffer silviapfeiffer merged commit 3e42825 into w3c:gh-pages Apr 25, 2018
@silviapfeiffer silviapfeiffer deleted the documentLicense branch April 25, 2018 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants