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

Prepare for CRS #269

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Prepare for CRS #269

wants to merge 2 commits into from

Conversation

nigelmegitt
Copy link
Contributor

@nigelmegitt nigelmegitt commented Oct 16, 2024

Closes #268.

  • set specStatus to CR
  • reference implementation report
  • set crEnd
  • Update SoTD to point to implementation report and include exit criteria
  • add acknowledgments

Preview | Diff

@himorin
Copy link
Contributor

himorin commented Oct 18, 2024

just an idea, how about to have a link to WG/CGs?

@nigelmegitt nigelmegitt added the agenda Issue flagged for in-meeting discussion label Nov 5, 2024
@css-meeting-bot
Copy link
Member

The Timed Text Working Group just discussed Prepare for CRS w3c/dapt#269, and agreed to the following:

  • SUMMARY: Rebase as needed and use as the basis of the CRS transition request
The full IRC log of that discussion <nigel> Subtopic: Prepare for CRS #269
<nigel> github: https://github.com//pull/269
<cpn> Nigel: I used the draft PR feature for this, similar to how Pierre does it with IMSC
<cpn> ... Once everything is merged, I'll rebase this, and that will be the bases for the CRS
<cpn> ... No action needed. It changes the spec status, refers to implementation report, etc. End date says 1 January for Proposed Recommendation, may need to adjust
<cpn> ... CR exit criteria us almost the same wording as for IMSC
<cpn> ... I cross-checked the wording against the charter. AFAICT it's compatible with that
<cpn> ... Unless there are comments, I'll assume it's ok
<cpn> (nothing)
<cpn> ... Please LMK if anyone should be added to Acknowledgements
<nigel> SUMMARY: Rebase as needed and use as the basis of the CRS transition request

@nigelmegitt nigelmegitt force-pushed the issue-0268/prepare-crs branch 2 times, most recently from e2cf96e to 49786a5 Compare November 14, 2024 09:22
* set specStatus to CR
* reference implementation report
* set crEnd
* Update SoTD to point to implementation report and include exit criteria
* add acknowledgments
As agreed during the TTWG call 2024-11-21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda Issue flagged for in-meeting discussion editorial
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Prepare CR draft ready for publication
4 participants