You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's the second time that the charter introduces a case-by-case basis. While I understand that this is a way to give a bit of grease to the process, this is also an opportunity for having endless discussions.
TODO: Open an issue about this case by case notion. What do we mean? What are the precedents? Was it needed? And Why? Was the group too constrained?
The text was updated successfully, but these errors were encountered:
These case-by-case exceptions would be made by consensus, so a way to stop the discussion immediately would be for someone to object.
The case most likely to come up is wanting to include some features tested in Test262 or WebGL. For standards organizations it's not as easy to say what a plausible case might be. ISO is the only one that's crossed my mind, but I don't think we should include it right now, since we don't have any test suites for it in WPT.
To change the charter we'd use the WPT RFC process. If we want the interop team to be able to make this decision internally, we should move these lists out of the charter. I'd prefer to keep it simple though.
It's the second time that the charter introduces a case-by-case basis. While I understand that this is a way to give a bit of grease to the process, this is also an opportunity for having endless discussions.
TODO: Open an issue about this case by case notion. What do we mean? What are the precedents? Was it needed? And Why? Was the group too constrained?
The text was updated successfully, but these errors were encountered: