W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2019

Re: [webrtc-pc] Move features at risk to an extension spec (#2323)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Thu, 10 Oct 2019 09:07:13 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-540475221-1570698433-sysbot+gh@w3.org>
> - features that can reasonably easily be separated out into a different spec - for those, we should create one repo per spec and move the relevant spec section there

I think this makes sense for a substantial chunk, like a new interface, or several related methods. Like we did with identity, ice transport extensions, etc.

> - features for which creating a separate spec would be impractical (either because they're deeply intertwined in the rest of the spec, or because they're a small addition that doesn't really make sense on its own); for these, I'm thinking of creating a convention whereby they can be put into our editors draft, but would only appear when picking a "webrtc 1.1" view of the spec via the ReSpec pill (the same way test annotations can be toggled on and off at the moment).

This was what I had in mind, things like small mostly standalone additions to existing interfaces. the kind of stuff where you don't want to assemble a new working group, but priorities and commitments are uncertain because they're "1.1" type of things. If it was possible to do a ReSpec annotation to show or hide these features that would be great.

GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2323#issuecomment-540475221 using your GitHub account
Received on Thursday, 10 October 2019 09:07:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:29 UTC