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: Dominique Hazael-Massieux via GitHub <sysbot+gh@w3.org>
Date: Wed, 09 Oct 2019 08:42:03 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-539901521-1570610522-sysbot+gh@w3.org>
I think there are 2 cases to distinguish:
* 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
* 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).

How does that sound?

GitHub Notification of comment by dontcallmedom
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2323#issuecomment-539901521 using your GitHub account
Received on Wednesday, 9 October 2019 08:42:05 UTC

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