- From: Nigel Megitt <nigel.megitt@bbc.co.uk>
- Date: Thu, 18 Feb 2021 16:58:10 +0000
- To: TTWG <public-tt@w3.org>
- Message-ID: <958EC790-78F3-49C0-9646-BFFC5C1D9A49@bbc.co.uk>
Thanks all for attending today's TTWG meeting. Minutes can be found in HTML format at https://www.w3.org/2021/02/18-tt-minutes.html
In text format:
[1]W3C
[1] https://www.w3.org/
Timed Text Working Group Teleconference
18 February 2021
[2]Previous meeting. [3]Agenda. [4]IRC log.
[2] https://www.w3.org/2021/02/04-tt-minutes.html
[3] https://github.com/w3c/ttwg/issues/174
[4] https://www.w3.org/2021/02/18-tt-irc
Attendees
Present
Atsushi, Cyril, Glenn, Nigel
Regrets
Andreas, Gary
Chair
Nigel
Scribe
nigel
Contents
1. [5]This meeting
2. [6]TTML2 Publication of updated CR
3. [7]2021 Workplan
4. [8]Switching master to main branch names
5. [9]Meeting close
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
[10]Latest published Process doc
[10] https://www.w3.org/2020/Process-20200915/
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> [11]https://www.w3.org/2020/
Process-20200915/#w3c-recommendation-track
[11] https://www.w3.org/2020/Process-20200915/#w3c-recommendation-track
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.
[12]Update Request
[12] https://www.w3.org/2020/Process-20200915/#update-requests
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> [13]ttml1 PR
[13] https://github.com/w3c/ttml1/pull/377
<atsushi> [14]TTML3
[14] https://github.com/w3c/ttml3/pull/36
<atsushi> [15]https://himorin.github.io/w3c-memo/github/
listrepo.html
[15] https://himorin.github.io/w3c-memo/github/listrepo.html
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]
Minutes manually created (not a transcript), formatted by
[16]scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).
[16] https://w3c.github.io/scribe2/scribedoc.html
----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
---------------------
Received on Thursday, 18 February 2021 16:58:30 UTC