Closed foolip closed 1 year ago
This is a big RFC, so I'd like to call out some things worth looking at:
FWIW, I'm not totally sure it makes sense to actually have one of these RFCs annually at this point; I think there's broad agreement across the Core team that we should keep on doing this as long as there's cross-vendor interest.
I'd be more interested in an RFC that acts closer to a charter for the Interop team going forward, and leave it down to that team what happens (potentially with an explicit limitation where it only holds as long as it has a similar coverage of browser vendors to the Core Team).
In a sense, I suggest we focus on the governance section here, and define the scope of what we believe Interop should be.
I like that direction if others in the core team and interop-2022 team are on board with it.
Maybe a setup like this?
charter.md
which is created by the RFC process and can be amended by itinterop_2022.md
Alright, I've pushed two changes:
I think that resolves all feedback, except the decision making process which I suggest we do in a coming interop team governance RFC.
Everyone please take another look.
I still need to change this to no longer refer to a 2023 repo or team, to instead say that we'll rename the existing ones.
Alright, those updates now made as well. I'm not aware of any more changes that need to be made, but I might have missed something. Please review :)
I've addressed all the remaining feedback now. @web-platform-tests/wpt-core-team please review, for the final time?
Thanks for the review and fixes, @sideshowbarker!
I've now renamed the repo and the team, as per the RFC.
Rendered