http://eaves.ca/2012/08/30/community-managers-expectations-experience-and-c…
"This is why I keep saying things like code review dashboards matter. I
bet if this user could at least *see* what the average wait time is for
code review he'd have been much, much happier. Even if that wait time
were a month... at least he'd have known *what to expect.* Of course
improving the experience and community culture are harder problems to
solve... but they clearly would have helped as well."
I would love for someone to integrate that kind of wait-time indicator
into
https://toolserver.org/~bawolff/gerrit-stats.htm or
http://gerrit-stats.wmflabs.org/ . My suggested stats: the
min/median/average/maximum time between a patchset's submission and its
merge or abandonment, and the min/median/average/maximum time between
patchset submission and any +1 or -1, divided up by Gerrit repository.
Anyone who works on this will probably also want to join the FLOSS
communities metrics working group:
http://www.theopensourceway.org/mailman/listinfo/metrics-wg
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation