Bug 235719 - Code review statistics
Summary: Code review statistics
Status: New
Alias: None
Product: Services
Classification: Unclassified
Component: Code Review (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Only Me
Assignee: Phabric Admin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-13 18:59 UTC by John Baldwin
Modified: 2019-03-26 20:17 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Baldwin freebsd_committer freebsd_triage 2019-02-13 18:59:38 UTC
Can we get access to some kind of code review stats with per-user breakdowns?  Here are some suggested queries developers might be interested in from a recent thread on developers@

- number of reviews reviewed in last week/month/year
- number of comments in last week/month/year
- number of reviews created in last week/month/year
- number of reviews accepted
- number of reviews closed

Either a way a user can see their own stats or maybe stats that show the rank users.  It might also be nice to be able to split them up by repository (src vs ports, etc.).

From some web searches online it seems phabricator includes a "Facts" application that provides some stats (but it's not clear which ones), but that application is currently disabled on our instance since it is marked as a prototype.
Comment 1 Kurt Jaeger freebsd_committer 2019-02-13 19:33:58 UTC
Before we play with the production system, would it work to load the database of the prod system into the dev system, enable facts there and verify it does not toast the system ?
Comment 2 John Baldwin freebsd_committer freebsd_triage 2019-02-13 21:24:23 UTC
(In reply to Kurt Jaeger from comment #1)
Sure.  I don't know yet if Facts will actually give us all that we want, it's just the only thing I've found via Google so far.  I'd be happy to look at it on the dev setup to see if it looks useful or not.
Comment 3 John Baldwin freebsd_committer freebsd_triage 2019-03-13 19:47:48 UTC
Ping
Comment 4 John Baldwin freebsd_committer freebsd_triage 2019-03-26 16:19:21 UTC
Ping
Comment 5 Kurt Jaeger freebsd_committer 2019-03-26 20:17:49 UTC
Status: I have to find time to dig into this.