Open zcorpan opened 4 years ago
@zcorpan I came across this issue because it has no label, but I'm also unsure what label to add. Are you planning to send out any more emails for this issue?
I'm not currently planning to send more emails. Though someone else is of course welcome to do so. If so, I'd suggest removing some of the questions from the template, and make it a simpler decision "yes I can help" vs "no thanks" and clarify how to revoke (submit PR editing META.yml
).
I wonder if some tooling would be able to automatically include (and remove) appropriate spec editors through PRs.
At TPAC 2019 we set out some priorities for 2020, which include increasing PR review velocity and reduce the number of stale PRs.
In order to get contributions to wpt reviewed in a more timely manner, it seems useful to ask people who are editing the corresponding spec or are reviewers or module owners or otherwise appropriate reviewers within downstream projects (Gecko/Servo, WebKit, Chromium - e.g.
OWNERS
files) to be added tosuggested_reviewers
and review PRs in GitHub.As a start, I've sent email to 3 people for the
svg
folder, which resulted in two new suggested_reviewers. (1, 2)Here's a template to send:
Apart from adding them to
suggested_reviewers
, they would also need to be invited to the reviewers team.Below are all top-level paths in wpt, and one level down for
html
andcss
.