(Creating a dedicated ticket, as discussed with @Dicortazar).
In T94578 we have defined the KPIs we'd like to see.
We'd like to view all those KPIs displayed on one single page: http://korma.wmflabs.org/browser/kpi_overview.html
(And for the records, @Dicortazar said that embedding charts is easier than tables.)
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | Qgil | T107562 Tech community KPIs for the WMF metrics meeting | ||
| Resolved | Aklapper | T100978 Present most basic community metrics from T94578 on one page | ||
| Resolved | Aklapper | T94578 Most basic Tech Community metrics are published and up to date | ||
| Resolved | Dicortazar | T86152 Active Gerrit users on a monthly basis | ||
| Resolved | Dicortazar | T59038 Basic metrics about contributors exercising +2/-2 permissions in Gerrit | ||
| Resolved | Acs | T92953 Migrate Korma identitites database to SortingHat | ||
| Resolved | Dicortazar | T96371 Community Metrics for IRC channels not updated since 09/2013 | ||
| Invalid | Dicortazar | T97715 Median time to review for Gerrit Changesets, per month | ||
| Resolved | Dicortazar | T97716 Gerrit changes reviewed per month (on scr.html) | ||
| Resolved | Dicortazar | T97717 Active changeset *authors* and changeset *reviewers* per month | ||
| Resolved | Dicortazar | T104176 404 for VizGrimoireJS/data/metrics.json on korma; makes certain pages unusable |
At least when it comes to our quarterly goal T94578, I think this task is a nice to have but not a blocker. I understood the "how they are presented" in the goal as how each metric is presented. If it helps taking some pressure from this month, we can leave for later how they are presented together, and keep the focus to the basic metrics themselves. It would be enough documenting a "Basic metrics" section at the top of https://www.mediawiki.org/wiki/Community_metrics where these metrics are listed as
The values themselves would not be required in that page, although since it's a monthly change easy to edit, perhaps we manage to keep those values synced manually (as we are doing with Phabricator active users).
This would be a goods enough scenario for our quarterly goal. Then, maybe we want to discuss in the next quarter about that single page.
I think this task is a nice to have but not a blocker.
That makes things more relaxing, thanks. Lowering priority.
I might give this task a shot myself.
This task is scheduled for ECT-June-2015 but is not assigned to someone. We should either assign it or we remove it from the sprint.
I'm linking this task to T107562 because both a related: we need a good place to highlight and track our KPIs. Options: a special page in Korma or https://www.mediawiki.org/wiki/Community_metrics#Reports (else?)
Also, only slightly related but just in case it serves as inspiration. Yesterday I learned about http://searchdata.wmflabs.org/metrics/ (and I'd rather post this here than forget the URL).
I'd like to give this a shot myself in September if time allows.
Time didn't.
Punting to October, plus want my two other pull requests for mediawiki-dashboard to get merged first.
I gave this a first shot in https://github.com/Bitergia/mediawiki-dashboard/pull/66 (untested!, feedback welcome) by creating a new custom page kpi_overview.html to link from the navigation.
Initial version is available now on http://korma.wmflabs.org/browser/kpi_overview.html
Followup work needed once all KPIs we want are actually available in korma itself; tracked in T116572.
Closing as resolved.