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

Update CLA and License agreement #438

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from

Conversation

palemieux
Copy link
Contributor

@palemieux palemieux commented Apr 4, 2018

The idea is for the CLA to require upfront a commitment from contributors that is compatible with Rec Track documents.

dwsinger
dwsinger previously approved these changes Apr 9, 2018

This repository is being used for work in the Web Media Text Tracks Community Group, governed by the [W3C Community License
Agreement (CLA)](http://www.w3.org/community/about/agreements/cla/). To contribute, you must join
Copy link
Member

Choose a reason for hiding this comment

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

I disagree with removing the CLA and CG reference. It encourages people that cannot join the W3C to participate.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As a W3C specification on the REC track, I do not see why WebVTT should be subject to a CLA different than other W3C specifications on the REC track. The CG can create a separate repo if it wants to work on something other then the specification on the REC track.

This repository is being used for work in the Web Media Text Tracks Community Group, governed by the [W3C Community License
Agreement (CLA)](http://www.w3.org/community/about/agreements/cla/). To contribute, you must join
the CG.
Contributions to this repository are intended to become part of Recommendation-track documents governed by the W3C Patent Policy and Document License. To contribute, you must either participate in the [Timed Text Working Group](https://www.w3.org/AudioVideo/TT/) or make a non-member patent licensing commitment.
Copy link
Member

Choose a reason for hiding this comment

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

You don't have to participate in the TTWG to make a contribution and the CLA above already makes a non-member patent licensing commitment.

There is far less legal conflict between the way that the CG works and the way the WGs work than you think. I disagree with making this a TTWG-only repository.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You don't have to participate in the TTWG to make a contribution and the CLA above already makes a non-member patent licensing commitment.

The same is true for IMSC: anyone can make a contribution, bound to the W3C CLA.

@dwsinger dwsinger dismissed their stale review April 9, 2018 09:44

we need to identify that a common repo is used for both CG and WG

@silviapfeiffer
Copy link
Member

The non-member patent licensing requirements that you are requesting people to make is already sorted in the CG. Why would we make it harder for others to contribute when it has worked well in the past? Other Working Groups are embracing this style of working also. In fact, you might want to consider introducing this for other TTWG work also, seeing as some new work is happening in CGs.

@silviapfeiffer
Copy link
Member

silviapfeiffer commented Apr 24, 2018

The key here is to avoid creating forks, since that has caused trouble in other WGs. We should not go backwards on a model that has worked well and make it worse.

Copy link
Member

@silviapfeiffer silviapfeiffer left a comment

Choose a reason for hiding this comment

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

I strongly object to this PR.

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.

3 participants