https://bugzilla.wikimedia.org/show_bug.cgi?id=53485

--- Comment #58 from Quim Gil <[email protected]> ---
(In reply to comment #57)
> Can we get some KPIs on the smaller stuff ?

Just a bit of background: we agreed to focus our work on five KPIs described at
https://www.mediawiki.org/wiki/Community_metrics#Key_performance_indicators .
Here we are working on the first one, related to code contributions. In
addition to this http://korma.wmflabs.org offers more data.

The answers below refer to the data provided by the metrics dashboard in Korma
alone.

> How about:
> 
> What repositories get the least contribs/reviews

Contributions: http://korma.wmflabs.org/browser/scm-repos.html?page=24 and up.

Reviews: http://korma.wmflabs.org/browser/scr-repos.html?page=24 and up.

> Who contributes/reviews most of the code that no on else contributes/reviews
> (who takes care of the orphan projects)

Currently we are not displaying authors per repo, and we don't have a way to
distinguish the repositories an author or a reviewer contributes to. Is this
what you mean? It is a good point, and it would be great if you could open a
new report to cover it.

> Who makes the most changes to the fields of a ticket (who does triage?)

Do you mean triage in Bugzilla? There is not much now
http://korma.wmflabs.org/browser/its.html but we want to work more on this when
we address the KPI Bugzilla response time:
https://www.mediawiki.org/wiki/Community_metrics#Bugzilla_response_time


> Which repo's have the longest time between first and last patch
> Which repo's have the longest time between first/last patch and merge ?

Do you mean first and last patch in the review queue? We are measuring the time
to review patches by repository at
http://korma.wmflabs.org/browser/scr-repos.html If you need something different
not covered in the currently planned KPIs then please open a report.

> Usually I find these kinds of things more interesting than 'top performance'
> indicators.

Yes, in these KPI we attempt to look not only at top performers but also at
bottlenecks or neglected areas. For instance, when looking at times to review
at the Gerrit queue we sort the lists starting by those repos with larger time
to review. See Bug 37463 - Key performance indicator: Gerrit review queue

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to