On Mon, 2013-08-19 at 13:05 -0700, Quim Gil wrote:
Out of code contributions, the only candidate to
become a KPI that came
to mind was the effectiveness responding to Bugzilla reports. Maybe you
are right the priority of this one is higher than the age of code
contributors. Thoughts?
Refering to Bugzilla only:
As listed on
http://www.mediawiki.org/wiki/Talk:Community_metrics ,
I'd be interested in two things:
Average time to resolve a ticket: Delta between creation of a report and
setting the status RESOLVED.
Preferably separately for "real" bugs and severity=enhancement.
Might also make sense to have a specific one for setting the status
RESOLVED && resolution FIXED, to only cover code fixes.
And average time to response to new tickets: Delta between creation of a
report and any next change (setting priority, adding an initial comment,
etc.) which is NOT done by the original reporter. If that's possible.
All in all, the proposed metrics look really good to me, great work!
Looking forward to seeing most of that implemented!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/