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

Add a "Review: too late" label and corresponding guidance #29

Open
LeaVerou opened this issue Feb 9, 2023 · 0 comments
Open

Add a "Review: too late" label and corresponding guidance #29

LeaVerou opened this issue Feb 9, 2023 · 0 comments
Assignees

Comments

@LeaVerou
Copy link
Member

LeaVerou commented Feb 9, 2023

This comes from two breakouts today, one with @cynthia @rhiaro and me and one with @plinss and me.

The TAG does valuable work, but it is always a struggle for TAG members to fit our large workload in the limited cycles we have available for (essentially) volunteer work. Therefore, it's highly suboptimal to be spending time doing reviews of mature specs that have shipped in every major browser, and nothing we say cannot make a difference at all anymore.
We should be taking steps to maximize the ratio of impact to time spent, and I think a way to do that is closing some reviews as "too late".

This would involve having a "too late" label, and guidance that basically says "if a feature has shipped in every major browser, it's too late for TAG review, the ship has sailed", but in a nice/equitable way 😁

It was pointed out that mature reviews like w3ctag/design-reviews#658 or w3ctag/design-reviews#657 are required as part of wide review.
However, for TAG reviews to actually make an impact, these features should come to us earlier, when their design can still change.
So, even if we drop (most) late reviews, TAG review could still be a part of wide review, but as a list of URLs to previous TAG reviews. When a spec reaches the point of wide review, it should already have a bunch of closed TAG reviews, it shouldn't be sent to TAG review at that point.

@LeaVerou LeaVerou transferred this issue from w3ctag/tag.w3.org Feb 9, 2023
@torgo torgo self-assigned this Feb 9, 2023
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