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 TR published codec registrations (fix broken registry links) #359

Closed
chcunningham opened this issue Sep 21, 2021 · 10 comments
Closed
Assignees
Labels

Comments

@chcunningham
Copy link
Collaborator

Several of the links in the https://www.w3.org/TR/webcodecs-codec-registry/ don't work.

busted: https://www.w3.org/TR/webcodecs-aac-codec-registration/
working: https://w3c.github.io/webcodecs/aac_codec_registration.html

@tidoust, can you advise on how to get the codec registrations published to TR? IIRC, something about generating echidna tokens?

@tidoust
Copy link
Member

tidoust commented Sep 22, 2021

To generate Echidna tokens, specs needs to have been published as First Public Working Drafts (FPWD) to /TR.

To publish FPWD of these specs, I need approval from the group.

In other words, that all starts with issuing a call for consensus to publish the list of WebCodecs registration specs as FPWD, noting that these specs are intended to be published as WG Notes. @chrisn, @jernoble?

@chrisn
Copy link
Member

chrisn commented Sep 22, 2021

Yes, we can send out a CfC. I noticed that the registry contains a couple of inline issues. Can we resolve these before FPWD?

@tidoust
Copy link
Member

tidoust commented Sep 22, 2021

I note that the registry itself and the AVC (H.264) WebCodecs Registration have already been published as FPWD (and /TR version gets updated whenever a push gets made to the main branch on these specs). The call for consensus would be for the other WebCodecs registrations, namely the ones for FLAC, MP3, AAC, OPUS, VORBIS I, AV1, VP8, and VP9.

@chcunningham
Copy link
Collaborator Author

Thanks guys. I've sent #367 and #368 to prepare for FPWD. When those merge we should be good to run Cfc.

@chcunningham
Copy link
Collaborator Author

@tidoust, the CfC closed (resolving to publish). Please go ahead and publish the above to FPWD. Let me know if I can do anything to help.

@tidoust
Copy link
Member

tidoust commented Dec 14, 2021

Yes, I'm on it. The transition was approved (see w3c/transitions#398). Publication should take place on Thursday. There is a broken reference in some of these specs, which I'll fix in published documents (see PR #423).

FWIW, the exact status for draft notes is not FPWD in Process 2021. These documents will be published on the Note track as Draft Group Notes.

@tidoust
Copy link
Member

tidoust commented Dec 16, 2021

All codec registrations got published to /TR today. Specref picked up the new specs and Bikeshed reference database was updated accordingly. In order to update the codec registry itself and fix the links, a gentle push to the main branch needs to happen (because spec-prod considers that it should skip publication to gh-pages and /TR if action that triggers it is not a "push" event). You could perhaps merge one of the pending bug fixing PRs (#419 or #423) or just add a space somewhere. Whatever you prefer, we just need a push!

@padenot
Copy link
Collaborator

padenot commented Dec 16, 2021

Done, thanks.

@chcunningham
Copy link
Collaborator Author

Thanks everyone! I confirmed just now that all the links are working :D

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

No branches or pull requests

4 participants