Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Merge into W3C repo and archive the WICG repo #16

Closed
tidoust opened this issue Jun 17, 2020 · 3 comments
Closed

Merge into W3C repo and archive the WICG repo #16

tidoust opened this issue Jun 17, 2020 · 3 comments

Comments

@tidoust
Copy link

tidoust commented Jun 17, 2020

The feature described in this repo is now in scope of the Media Working Group.

It would be good to merge relevant spec updates back into the main w3c/encrypted-media repo (at least as a pull request) so that we can point people at the right place and archive this repository. @joeyparrish, how would you like to proceed?

@joeyparrish
Copy link
Member

This proposal has already been merged into w3c/encrypted-media. What's the procedure to archive this and point people back to the main spec? I'm not very experienced in the W3C yet.

@tidoust
Copy link
Author

tidoust commented Jun 17, 2020

Good! The way I would do it:

  • Add a warning at the beginning of the README along the lines of "This proposal has been integrated into the parent Encrypted Media Extensions specification, developed by the Media Working Group."
  • Add a redirect in WICG/wicg.github.io to redirect the spec at wicg.github.io to the one at w3c.github.io.
  • Ask WICG chairs to review and to archive the repository.

Happy to take care of it.

tidoust added a commit to tidoust/encrypted-media-encryption-scheme that referenced this issue Jun 17, 2020
tidoust added a commit to tidoust/wicg.github.io that referenced this issue Jun 17, 2020
Proposal has now been integrated in the parent EME spec, under development in
the Media WG. See:
WICG/encrypted-media-encryption-scheme#16
marcoscaceres pushed a commit to WICG/wicg.github.io that referenced this issue Jun 18, 2020
Proposal has now been integrated in the parent EME spec, under development in
the Media WG. See:
WICG/encrypted-media-encryption-scheme#16
@joeyparrish
Copy link
Member

The README has been updated, and issues have been transferred to the main spec issue tracker. I appear to have rights to archive this repo myself, so I'll go ahead and do that. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants