Moving codec registry to "Registry Track"

[chcunningham]

This came up in today's WG call
https://www.w3.org/2021/11/09-mediawg-minutes.html#t03

From the call, it sounds like we need to adjust the status from NOTE-ED to something else (probably something like "registry report", but I don't find any similar status in bikeshed documentation. @tidoust also mentioned minor editorial changes. @tidoust can you outline next steps?

[chcunningham]

Also, just to be sure crystal clear, am I right that we're talking about the process changes introduced by this PR?
w3c/process#335

[tidoust]

From the call, it sounds like we need to adjust the status from NOTE-ED to something else (probably something like "registry report", but I don't find any similar status in bikeshed documentation

Bikeshed has not yet been updated to reflect the changes introduced in Process 2021. That's ongoing. We'll need to wait until that happens.

Also, just to be sure crystal clear, am I right that we're talking about the process changes introduced by this PR?
w3c/process#335

Yes, there may have been further adjustments made to the text that are not part of this PR. The result is The Registry Track section in the Process document.

[tidoust]

Status update:

• Group resolved to switch document to Registry track during TPAC's face-to-face
• Document was updated to meet process requirements related to registries, see [WebCodecs codec registry] Policy for changes to existing entries #571
• Switch requested and approved by W3C Director in DRY Request for WebCodecs Codec Registry transitions#463
• Actual publication as Draft Registry under https://www.w3.org/TR/ should take place tomorrow (13 October 2022). I'll update and close this issue once done.
• Boilerplate updated in Bikeshed so that auto-publish can resume after tomorrow's publication: Add registry track boilerplate for the Media WG speced/bikeshed-boilerplate#26

[tidoust]

Actual publication as Draft Registry under https://www.w3.org/TR/ should take place tomorrow (13 October 2022). I'll update and close this issue once done.

I failed to do that, but Draft Registry was indeed published at https://www.w3.org/TR/webcodecs-codec-registry/
Closing the issue accordingly :)