Republishing WebVTT as CR with features at risk (CfC)

The proposal from today's call is to update the WebVTT in /TR as a CR 
with the following list of features at:
[[
collision avoidance with snap-to-lines false
::cue-region pseudo-element
:past and :future pseudo-classes
]]

The draft document prepared by Gary is at:
 
https://raw.githack.com/w3c/webvtt/90265659a7b01fafba5e464f40ccbf781c6fdaa3/archives/2019-03-06/Overview.html

If anyone objects to update the draft, please speak up before the TT 
call on March 28.

Thank you,

Philippe

On 3/14/2019 1:20 PM, Nigel Megitt wrote:
> WebVTT Implementation Report
> 
>     Gary: I sent out an update last week. I started working on
>     STYLE block implementation for vtt.js so with Safari's
>     implementation
>     ... and that then the feature will no longer be at risk.
>     ... I made a pull request against the repo marking a couple of
>     things at risk so we can move forward with getting those
>     ... things out as a new CR. Then hopefully we can remove those
>     features, move that to a PR and create a new CR with
>     ... those features put back in.
> 
>     Nigel: Can we do that or do we have to go back to WD?
> 
>     Philippe: You can do it if you can demonstrate wide review and
>     the Director approves. That would need a transition request.
> 
>     Gary: That part can be done at another meeting. Is the marking
>     things at risk something that everyone is in agreement
>     ... on, removing those features and moving that version
>     forward?
>     ... I got a comment from Eric saying he was in agreement with
>     that assuming we put the features back in later.
> 
>     Nigel: We have a Chairing vacuum here which as ever I'm
>     reluctant to step in to.
>     ... We need consensus on this and a CfC for publishing a CR.
> 
>     Philippe: Is there any objection?
> 
>     Nigel: Our Decision Policy is 2 weeks. The pull request
>     decision policy began when the pull was opened, arguably.
>     ... We still need a document to review with a proposal to
>     publish as an updated CR.
> 
>     Gary: I believe the updated snapshot is what we want to
>     publish.
>     ... We don't need to remove the at risk features yet.
> 
>     Philippe: I guess we need a separate CfC email sent to the list
>     to start the 2 weeks period.
> 
>     Nigel: That's what we normally do.
> 
>     Philippe: The proposal is to update the document as per the
>     pull request. Can we have a link to the document generated
>     ... by the pull request?
> 
>     Gary: No
> 
>     Philippe: We need pr preview enabled.
> 
>     Nigel: Will you take that offline to send a proposal to the WG
>     Philippe?
> 
>     Philippe: Yes I will do
> 
>     Nigel: Thank you
> 
> TTWG Charter 2019
> 
>     Nigel: Please do review the pull requests on the Charter repo
> 
>     <plh>
>     [15]https://raw.githack.com/w3c/webvtt/90265659a7b01fafba5e464f
>     40ccbf781c6fdaa3/archives/2019-03-06/Overview.html
> 
>       [15] https://raw.githack.com/w3c/webvtt/90265659a7b01fafba5e464f40ccbf781c6fdaa3/archives/2019-03-06/Overview.html
> 
>     [16]Charter pull requests
> 
>       [16] https://github.com/w3c/charter-timed-text/pulls
> 
> Meeting close
> 
>     group: [discussion about enabling PR preview on VTT repo]
> 
>     Nigel: We're out of time for today, thank you everyone.
>     [adjourns meeting]
> 
> Summary of Action Items
> 
> Summary of Resolutions
> 
>     [End of minutes]
>       __________________________________________________________
> 
> 
>      Minutes manually created (not a transcript), formatted by
>      David Booth's [17]scribe.perl version 1.154 ([18]CVS log)
>      $Date: 2019/03/14 17:15:50 $
> 
>       [17] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
>       [18] http://dev.w3.org/cvsweb/2002/scribe/
> 
> 
> 
> 
> 
> 
> ----------------------------
> 
> 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, 14 March 2019 17:52:25 UTC