Talk:Extension health

korma
Thanks for working on development statistics. Note, korma already calculates such averages for all gerrit repositories, for instance http://korma.wmflabs.org/browser/repository.html?repository=gerrit.wikimedia.org_mediawiki_extensions_MobileFrontend I guess the added value of this page is that it focuses on a single metric and provides it for all repositories in a single page. There is also http://koti.kapsi.fi/~federico/crstats/extensions.txt which instead focuses on reviewers (but includes self-merges). --Nemo 21:22, 29 January 2015 (UTC)

Yup i'm aware of these and these are definitely more complete in many ways. What I'm most interested in is
 * 1) a top level for all projects (e.g. how does MobileFrontend compare to Echo for example)
 * 2) pointing out actionable steps - e.g. neglected patchsets urls
 * 3) Which people commit more code than they review? How can we get code reviewed to code merged to a 1:1 ratio for our +2 commiters?

Would be great if some of these features could be folded into korma. Jdlrobson (talk) 21:27, 29 January 2015 (UTC)

I came here to ask about the possibility of switching to a sortable table, but then I remembered we have Gerrit/Reports/Changesets by project. Extensions are just a subset of all Gerrit projects, of course. I'd forgotten that we also have the Korma reports. I agree that folding additional data points into either/both of them would be a good idea here. --MZMcBride (talk) 01:23, 30 January 2015 (UTC)


 * That's cool! I hadnt seen that page. Would be great to add columns for average patch review time to it. Jdlrobson (talk) 01:41, 30 January 2015 (UTC)


 * I've already made the report tabular earlier. For gerrit reports, we still need to distinguish self-merges there. --Nemo 06:35, 30 January 2015 (UTC)