Meeting minutes
This meeting
Nigel: Today we have TTML2 CR republication, Workplan if anyone has anything to cover and master branch renaming.
… Any other business?
TTML2 Publication of updated CR
Nigel: I've had no objections to proceeding so the Decision Review Period initiated in our last call 2 weeks ago is now confirmed as a WG Decision.
… That means we can go ahead and publish an updated CR of TTML2.
… Need to check state of the Editor's Draft, and publication process and timeline.
Nigel: Glenn, you merged everything, right?
Glenn: Yes I merged everything that was outstanding.
Nigel: Thanks for doing that.
… I think the only other change we need to make is to the earliest exit date.
Glenn: I need the document publication date in it as well.
… Is it still covered by the 1 March 2019 Process document?
Nigel: No, the latest published one is 15 September 2020
Atsushi: And TTWG has moved to the newest one.
Glenn: Policy on having to update the governing process document?
Nigel: I think we have to update because we just rechartered based on Process 2020.
Glenn: Okay, so I need to update that as well.
Atsushi: Actually the pub rules have not been changed.
… We had introduced CRD and CRS but the process for updating CR has not changed so much.
… On the publishing side.
Glenn: So you're saying if we update to the new Process document we should not expect any ramifications?
Atsushi: For a CRD we could just publish after a WD decision, but I think we want to publish a CRS which should be a draft for PR.
Glenn: Pubrules will tell me what the options are for designating this as a particular document type and give me a set of options for which type to use
… I haven't done that yet because I didn't have a date.
… If I can get a date then I will run it through pubrules and see what happens.
… I may have to label it as CR2 of 2nd Ed of TTML2.
Nigel: Looking at the process now, it looks like CRS is only for substantive changes, and CRD is significant changes that benefit from review.
<atsushi> https://
Nigel: From that perspective we could defer all these changes until PR, or publish a CRD.
… I think the resolution we made was for a CRS though, despite there being no substantive change.
Atsushi: I thought we would go to a CRS.
Nigel: Me too.
Atsushi: I believe we need to go through the requirement for CRS.
Nigel: Agreed, I think we need an Update Request.
Atsushi: I believe we do not need to go through WR again.
Nigel: Same here.
Atsushi: The publication decision will be made every Friday, so the earliest is the Tuesday after that, 2nd March
Nigel: Looking at the Update request, we need to document the changes, there are no Formal Objections, we need to show wide review of the
… changes, which arise from the GitHub issues, we need to say there's no change to requirements, or dependencies.
… That's it I think.
… I think we're fine for Streamlined Publication Approval as well.
… So going back to Glenn's question, we need to say 2nd March for publication date, and 30th March for earliest CR exit, being 28 days later.
Nigel: Are you happy with that Atsushi?
Atsushi: Yes, I would like to submit a draft transition request ASAP, hopefully today (in Japan time!), tomorrow for the US.
Glenn: I can do the edits and run the pubrules this evening my time, and assuming I can resolve any issues that come up I will create a
… checkpoint with a tar file. I can do the pull request after the fact.
Atsushi: Thank you for that.
… My biggest concern is that we are fine to go without HR. All of our changes are not big so I just want to present that one, before
… completing the final document.
Glenn: With editorial changes only it seems like we shouldn't need to.
Atsushi: I believe so.
Nigel: Anything else we need to consider?
Atsushi: I don't have anything else.
Nigel: Okay, thank you all.
2021 Workplan
Nigel: Anything to discuss on this placeholder topic?
group: [nothing to discuss]
Switching master to main branch names
Nigel: What's the status on this?
Atsushi: I believe all finished.
Nigel: Great, thank you! Any issues anyone?
Atsushi: I forgot something about TravisCI integration when I merged but I've pushed new deploy keys so it seems to be working,
… so I believe all are green now.
Nigel: Is there anything left to merge?
Atsushi: Probably
Nigel: Okay, then action for Editors - please check open pull requests and merge them if you can, or highlight the problems if you cannot.
<atsushi> ttml1 PR
<atsushi> TTML3
<atsushi> https://
Nigel: Obviously we have no Gary here today but I think we have Editor presence on all the other documents than WebVTT
Atsushi: at the link I put in above, enter 34314 and it shows the list
Cyril: Thank you.
… (notes in passing that this isn't the same list of repositories as on the WG home page)
Atsushi: I see the Charter draft repo is missing. I'll fix that.
Nigel: Right, we have a little work to be done, but essentially we have moved everything from master to main. Job done!
… Thank you Atsushi.
Atsushi: You're welcome.
Meeting close
Nigel: We've completed our agenda. Let's adjourn. [adjourns meeting]