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

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

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Mon, 07 Oct 2019 10:43:41 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-503370954-1570445019-sysbot+gh@w3.org>
henbos has just created a new issue for https://github.com/w3c/webrtc-pc:

== Move features at risk to an extension spec ==
I've [created a repository](https://github.com/henbos/webrtc-extensions) for [WebRTC Extensions](https://henbos.github.io/webrtc-extensions/). Currently it's on my github and it's a bit "Hello World"-like.

I just merged [webrtc-timing](https://henbos.github.io/webrtc-timing/) into it and me and @eladalon1983 are working on moving [adaptivePtime](https://github.com/w3c/webrtc-pc/pull/2309) there.

[Comment](https://github.com/w3c/webrtc-pc/pull/2309#issuecomment-538463368) by @jan-ivar :

> Since `ptime` is already a feature at risk, having both in the same extension spec would make sense.

Perhaps we want to move "ptime" to webrtc-extensions too?

Should we migrate features at risk to that spec?
Or should the spec not be listed on my personal github? If this remains a spec not officially recognized by any working group, perhaps @foolip can help me with incubation ([WICG](https://www.w3.org/community/wicg/)).

Trying to figure out what formalities I should go through

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2323 using your GitHub account
Received on Monday, 7 October 2019 10:43:42 UTC

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