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

[charter] loose-end: case by case #123

Closed
karlcow opened this issue Aug 26, 2022 · 3 comments
Closed

[charter] loose-end: case by case #123

karlcow opened this issue Aug 26, 2022 · 3 comments
Labels
meta Process and/or repo issues

Comments

@karlcow
Copy link

karlcow commented Aug 26, 2022

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?

@karlcow
Copy link
Author

karlcow commented Aug 26, 2022

Maybe we need room in the process on how to propose a new test suite, or new standard organization.

@foolip
Copy link
Member

foolip commented Aug 26, 2022

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.

@foolip
Copy link
Member

foolip commented Sep 15, 2022

Both spec and test requirements ended up in #115 and we don't have any of the "case-by-case" language any longer.

@foolip foolip closed this as completed Sep 15, 2022
@gsnedders gsnedders added the meta Process and/or repo issues label Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Process and/or repo issues
Projects
None yet
Development

No branches or pull requests

3 participants