Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Two browser or removal requirement #51

Closed
ekr opened this issue May 15, 2018 · 1 comment
Closed

Two browser or removal requirement #51

ekr opened this issue May 15, 2018 · 1 comment

Comments

@ekr
Copy link

ekr commented May 15, 2018

The highest priority of the group in this charter period will be to
get the core recommendations progressed towards Recommendation
status. To that end, features that are not demonstrated to be>
implemented by at least two browsers withih the timeframes indicated
will be removed from the specifications. Depending on their nature,
they may be republished as extension specification, or simply
dropped.

I have three concerns about this:

  1. Procedurally, this doesn't actually have consensus in the WG. As far as I can tell, there was never any call for consensus on this point (or this proposed charter), If I'm wrong, please point me to it

  2. It reflects a reversal of the basic understanding that we would make decisions on a consensus basis. I don't have a problem with the WG deciding to remove features, but that should be a WG decision, with holding the spec until there is consensus on how to proceed as an option.

  3. This is particularly problematic in WebRTC, which is explicitly a collaboration with IETF, and thus decisions need to be made jointly.

@dontcallmedom
Copy link
Member

(clean-up, this was solved as part of the discussions of the now approved webrtc charter)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants