Bug 153591
Summary: | https://webkit.org/team should list only active committers and reviewers. | ||
---|---|---|---|
Product: | WebKit | Reporter: | Konstantin Tokarev <annulen> |
Component: | WebKit Website | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | CC: | ap, dbates, jond, simon.fraser |
Priority: | P2 | ||
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: |
https://bugs.webkit.org/show_bug.cgi?id=115387 https://bugs.webkit.org/show_bug.cgi?id=163318 |
Konstantin Tokarev
Right now https://webkit.org/team lists all contributors without any separation between active and inactive folks. It would be much more useful if team page contained only active committers and reviewers (according to current definition of "active"[1]), and create separate page, e.g. "Hall of Fame", listing inactive contributors for historical reasons.
[1] https://webkit.org/commit-and-review-policy/#inactive-committer-or-reviewer-status
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
That's a good idea. Would you be willing to work on a script that analyzes activity?
Konstantin Tokarev
Couldn't we just get away with new field in contributors.json, updated manually? If there is formal procedure of regaining active status, it shouldn't be managed by bots IMO.
Alexey Proskuryakov
I agree that it's debatable whether this should be done automatically. However we'd still need to automate gathering the data - it's not feasible to manually go over the whole list of contributors checking when their latest commit (or bugzilla comment) was.
There are lots of applications for this data, such as disabling commit access for folks who never commit, thus reducing password brute force attack target.
Any policy changes would need to be widely discussed of course.
Konstantin Tokarev
Looks like the right place of this functionality is validate-committer-lists, it already does some analysis of commit activity
Daniel Bates
(In reply to Alexey Proskuryakov from comment #3)
> I agree that it's debatable whether this should be done automatically.
> However we'd still need to automate gathering the data - it's not feasible
> to manually go over the whole list of contributors checking when their
> latest commit (or bugzilla comment) was.
>
Bug #115387 has an out-of-date patch to teach webkit-patch how to find emeritus reviewers and committers.