RE: [DRAFT] CfC: Handling of MSE Candidate Recommendation "at risk" features

> Aside from VPQ (which needs removal ASAP before branch, with no revert planned in VNext), we have the option of removing these other features before branch (and revert such in any VNext), or branch and then remove. Given folks' upcoming OOO, I vote for removing before branch.

The Editors should decide whether they branch first and then remove or remove the features first and then revert in VNext.

/paulc

From: Matt Wolenetz [mailto:wolenetz@google.com]
Sent: Wednesday, August 3, 2016 5:14 PM
To: Paul Cotton <Paul.Cotton@microsoft.com>; Mark Watson <watsonm@netflix.com>; Jerry Smith (WPT) <jdsmith@microsoft.com>
Cc: public-hme-editors@w3.org
Subject: Re: [DRAFT] CfC: Handling of MSE Candidate Recommendation "at risk" features


On Wed, Aug 3, 2016 at 1:16 PM, Paul Cotton <Paul.Cotton@microsoft.com<mailto:Paul.Cotton@microsoft.com>> wrote:
I still need an Editor to open an issue to track the removal of the TrackDefault feature.  This is a time critical request!!

Please see https://github.com/w3c/media-source/issues/136.

Aside from VPQ (which needs removal ASAP before branch, with no revert planned in VNext), we have the option of removing these other features before branch (and revert such in any VNext), or branch and then remove. Given folks' upcoming OOO, I vote for removing before branch.

The VideoPlaybackQuality and totalFrameDelay features are covered by ISSUE-69 [3].  The current CR text will NOT appear in MSE VNext and will be worked on in the Web Incubator Community Group [4].

This looks good to me. I have a PR (https://github.com/w3c/media-source/pull/135) out to remove the VPQ prior to any PR branching.

Matt

On Wed, Aug 3, 2016 at 1:16 PM Paul Cotton <Paul.Cotton@microsoft.com<mailto:Paul.Cotton@microsoft.com>> wrote:
The following is a revised draft CfC taking into account David’s comments about VideoPlaybackQuality and Mark’s request for explicit issue references.

I still need an Editor to open an issue to track the removal of the TrackDefault feature.  This is a time critical request!!

Comments?

/paulc

=====
The HTML Media Extensions WG is issuing a Call for Consensus to determine how to handle the "at risk" features published in the most recent MSE Candidate Recommendation [1].

The CfC proposes to remove ALL of the "at risk" features identified in [1] and they will NOT appear in the upcoming candidate Proposed Recommendation.
        The following features are at risk and may be removed:
                . The appendStream method on the sourceBuffer object and algorithm steps that are used only by it.

                . The VideoPlaybackQuality object and the HTMLVideoElement Extensions that use it.

                . The totalFrameDelay attribute on the VideoPlaybackQuality object.

                . The TrackDefault object and its related objects, attributes, methods and algorithms, including: TrackDefaultList, SourceBuffer.trackDefaults, Default track language, Default track label, and Default track kinds.
The appendStream feature is covered by ISSUE-14 [2].  The current CR text will be maintained in MSE VNext for further work and to await implementations of the Streams API and the associated parts of MSE.

The VideoPlaybackQuality and totalFrameDelay features are covered by ISSUE-69 [3].  The current CR text will NOT appear in MSE VNext and will be worked on in the Web Incubator Community Group [4].

The TrackDefault feature is covered by ISSUE-xx [5].  The current CR text will be maintained in MSE VNext for further work and to await MSE implementations of this feature.

Silence will be taken to mean there is no objection, but positive responses are encouraged.  If there are no objections by Wednesday Aug 10, this resolution will carry and we will proceed with the removal of the identified at risk features as we prepare the MSE Proposed Recommendation.


/paulc
HTML Media Extensions WG Chair

[1] http://www.w3.org/TR/2016/CR-media-source-20160705/

[2] https://github.com/w3c/media-source/issues/14

[3] https://github.com/w3c/media-source/issues/69

[4] https://wicg.github.io/media-playback-quality/

[5]  https://github.com/w3c/media-source/issues/xx


=====

From: Paul Cotton [mailto:Paul.Cotton@microsoft.com<mailto:Paul.Cotton@microsoft.com>]
Sent: Wednesday, August 3, 2016 12:53 PM
To: Mark Watson <watsonm@netflix.com<mailto:watsonm@netflix.com>>; Matthew Wolenetz <wolenetz@google.com<mailto:wolenetz@google.com>> (wolenetz@google.com<mailto:wolenetz@google.com>) <wolenetz@google.com<mailto:wolenetz@google.com>>; Jerry Smith (WPT) <jdsmith@microsoft.com<mailto:jdsmith@microsoft.com>>
Cc: public-hme-editors@w3.org<mailto:public-hme-editors@w3.org>
Subject: RE: [DRAFT] CfC: Handling of MSE Candidate Recommendation "at risk" features

> I believe the plan is to include a note linking to the CR version of VideoPlaybackQuality and the new Media Playback Quality work. I think it would be worth mentioning that in the CfC.

I agree that having an issue pointer in the CfC for each “at risk” feature would be useful.

A better reference for the VideoPlaybackQuality items is this comment on ISSUE-69: https://github.com/w3c/media-source/issues/69#issuecomment-237086776


Obviously the issue for appendStream: https://github.com/w3c/media-source/issues/14


I don’t believe there is a particular issue for removal of the TrackDefault object.  Could the Editors create one based on the implementations status so that I could reference it and flag it V1?

/paulc

From: Mark Watson [mailto:watsonm@netflix.com]
Sent: Wednesday, August 3, 2016 12:24 PM
To: Paul Cotton <Paul.Cotton@microsoft.com<mailto:Paul.Cotton@microsoft.com>>
Cc: Matthew Wolenetz <wolenetz@google.com<mailto:wolenetz@google.com>> (wolenetz@google.com<mailto:wolenetz@google.com>) <wolenetz@google.com<mailto:wolenetz@google.com>>; Jerry Smith (WPT) <jdsmith@microsoft.com<mailto:jdsmith@microsoft.com>>; public-hme-editors@w3.org<mailto:public-hme-editors@w3.org>
Subject: Re: [DRAFT] CfC: Handling of MSE Candidate Recommendation "at risk" features

Paul,

I believe the plan is to include a note linking to the CR version of VideoPlaybackQuality and the new Media Playback Quality work. I think it would be worth mentioning that in the CfC.

...Mark

On Wed, Aug 3, 2016 at 8:37 AM, Paul Cotton <Paul.Cotton@microsoft.com<mailto:Paul.Cotton@microsoft.com>> wrote:
Given that we now seem to have Editors' consensus on removal of the VideoPlaybackQuality feature (see ISSUE-69: https://github.com/w3c/media-source/issues/69) and that Firefox does not plan to implement the TrackDefault object (see https://lists.w3.org/Archives/Public/public-html-media/2016Aug/0013.html), are we ready to issue the following CfC to remove ALL the MSE at risk features?

/paulc

=====
The HTML Media Extensions WG is issuing a Call for Consensus to determine how to handle the "at risk" features published in the most recent MSE Candidate Recommendation [1].

The CfC proposes to remove ALL of the "at risk" features identified in [1] and they will NOT appear in the upcoming candidate Proposed Recommendation.  The current material will be retained in a VNext branch of MSE.

        The following features are at risk and may be removed:

                .The appendStream method on the sourceBuffer object and algorithm steps that are used only by it.

                .The VideoPlaybackQuality object and the HTMLVideoElement Extensions that use it.

                .The totalFrameDelay attribute on the VideoPlaybackQuality object.

                .The TrackDefault object and its related objects, attributes, methods and algorithms, including: TrackDefaultList, SourceBuffer.trackDefaults, Default track language, Default track label, and Default track kinds.

Silence will be taken to mean there is no objection, but positive responses are encouraged.  If there are no objections by Wednesday Aug 10, this resolution will carry and we will proceed with the removal of the identified at risk features.

/paulc
HTML Media Extensions WG Chair

[1] http://www.w3.org/TR/2016/CR-media-source-20160705/

=====

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596<tel:%28425%29%20705-9596> Fax: (425) 936-7329<tel:%28425%29%20936-7329>