Re: Raising the bar on the road to "done"

On 5/17/19 5:12 PM, youenn fablet wrote:
> I like this approach.
>
> Given we talk of finishing this version, we might have to defer some
> feature requests.
> This raises the question of how we envision working past this release
> and how we deliver deferred features.
>
> I would encourage to consider a more iterative approach like done in
> other web specs.
> The model of the fetch spec comes to mind for instance.
> This might be especially great for maintenance edits and ’small’
> feature additions to the core specs.

While the W3C has an ongoing discussion about how to incorporate a
"living document" approach in the W3C Recommendation process, we don't
have a result of that discussion yet. The Fetch spec is a WhatWG
specification, and follows that organization's processes and procedures.

We'll probably have to keep track of "small" additions in some other
fashion.

>
>
>> Le 16 mai 2019 à 10:35 AM, Bernard Aboba <Bernard.Aboba@microsoft.com
>> <mailto:Bernard.Aboba@microsoft.com>> a écrit :
>>
>> The WEBRTC WG Charter
>> <https://www.w3.org/2018/07/webrtc-charter.html> (which ends on 31
>> March 2020) includes in its Timeline the following milestones: 
>>
>>   * Media Capture and Streams: updated Candidate Recommendation in Q2
>>     2018, Proposed Recommendation in Q4 2018, Recommendation in Q1 2019
>>   * WebRTC 1.0: updated Candidate Recommendation in Q4 2018, Proposed
>>     Recommendation in Q3 2019, Recommendation in Q4 2019
>>   * MediaStream Recording: Candidate Recommendation in Q3 2018
>>   * Media Capture From DOM Element: Candidate Recommendation in Q3 2018
>>   * Screen Capture: Candidate Recommendation in Q4 2018
>>   * Identifiers for WebRTC Statistics: Candidate Recommendation in Q2
>>     2018, Proposed Recommendation in Q3 2019, Recommendation in Q4 2019
>>
>> While the WG is somewhat behind on the Charter milestones, we are
>> nevertheless serious about completing these milestones before the
>> current WG charter expires. With approximately 10 months
>> remaining, this means raising the bar on substantial changes to the
>> specifications, so as to leave sufficient time to allow implementers
>> to complete their work. 
>>
>> Currently our plan is to review Issues and PRs representing
>> substantial changes to Media Capture and WebRTC-PC at the June
>> Virtual Interim, to be held on June 11.  Once this review is
>> completed, the bar for considering changes to those specifications
>> will be considerably higher.  Future interim meetings will cover the
>> other specifications with similar goals for closing out the remaining
>> issues and making decisions on proposed changes.  
>>
>> For participants and editors the implications of the bar raising are
>> as follows:
>>
>>   * The bar for incorporation of enhancements to the specifications
>>     is very high.  Existing Issues marked as "enhancements" are being
>>     moved to the WebRTC-NV Use Cases repo, for consideration there
>>     (and potential discussion at the June 11 virtual interim if time
>>     permits). 
>>   * For issues discussed and decided upon at previous interim
>>     meetings, the time to submit PRs is *now.*  This is particularly
>>     true of the PRs that are complex and likely to require
>>     considerable review.  
>>   * For PRs with outstanding review comments, the time to incorporate
>>     the review comments and ready them for final review and potential
>>     merger is also *now. *
>>
>

-- 
Surveillance is pervasive. Go Dark.