W3C home > Mailing lists > Public > public-tt@w3.org > December 2017

Re: VTT, moving along, push WD and review Wide Review

From: David Singer <singer@apple.com>
Date: Thu, 07 Dec 2017 07:58:14 -0800
Cc: TTWG <public-tt@w3.org>
Message-id: <076A8547-4B64-4703-B932-182EEE4F51ED@apple.com>
To: Nigel Megitt <nigel.megitt@bbc.co.uk>
this is about the *previous* round

> On Dec 7, 2017, at 6:29 , Nigel Megitt <nigel.megitt@bbc.co.uk> wrote:
> I don't think I missed a memo, and apologies if I did, but I did not
> realise that the CG has completed draft dispositions for the WG to approve
> - indeed it seems like some of them are still being worked on. If so it's
> premature to ask for confirmation of end of review when the beginning of
> the review hasn't been flagged.
> On 06/12/2017, 20:40, "singer@apple.com on behalf of David Singer"
> <singer@apple.com> wrote:
>> Friends
>> following this message in June I received private feedback that one issue
>> was not satisfactorily closed (support of colors in non-CSS UAs) but
>> otherwise no other feedback. I think I should therefore take silence as
>> assent and mark the issues in the wide review page as having WG reflect
>> the CG status, with a note that the color issue is now resolved as part
>> of the second wide review.
>> Thank you for your consideration
>>> On Jun 28, 2017, at 3:18 , David Singer <singer@apple.com> wrote:
>>> Friends
>>> the CG has worked in email and GitHub to close out all the issues that
>>> were revealed in the previous wide review, and believes that those, and
>>> other critical issues, have been handled. I have asked the CG for
>>> confirmation of this.
>>> On the page <https://www.w3.org/wiki/WebVTT_Wide_Review>  you will find
>>> documentation of the wide review received. It was built in the days when
>>> we were using BugZilla, so alas, for bugs that were transferred to
>>> GitHub and resolved there, you¹ll need to follow forwarding pointers, to
>>> see the complete history (if you care).
>>> Thierry would like a formal status from the WG on each bug; you¹ll see
>>> the table of possible statuses at the end of the page (has this been
>>> done for other specs?). I have not yet filled in the WG column, but
>>> obviously could take the implied status from the CG column. Please let
>>> the group know if you think that is wrong.
>>> The specification is in much better shape; the test suite has been
>>> greatly improved (we hired a contractor) and does good coverage. We are
>>> working on a test report. With that in hand, we are hoping for a quick
>>> wide-review prior to a CR transition. Yes, we expect that some features
>>> will be marked Œat risk¹ in that transition; we¹ll be looking at the
>>> test report.
>>> The latest editor¹s draft is at <https://w3c.github.io/webvtt/>. I
>>> think we are badly behind on the working draft heartbeat requirement; I
>>> would like to push this as a WD. We previously asked for assent to have
>>> the editor push WDs automatically, but the WG indicated it preferred a
>>> resolution. Please consider resolving this in email or on a call (as you
>>> prefer). I cannot join the call this week.
>>> Once we have:
>>> * your acceptance of the handling of the wide review issues
>>> * the WD in place
>>> * the test suite report in hand
>>> I expect to ask for a transition to CR.
>>> Thank you for your patience and attention; it has been a long road.
>>> David Singer
>>> Manager, Software Standards, Apple Inc.
>> David Singer
>> Manager, Software Standards, Apple Inc.

David Singer
Manager, Software Standards, Apple Inc.
Received on Thursday, 7 December 2017 15:58:30 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 7 December 2017 15:58:31 UTC