Change Details

Check if we have all the really very basic metrics that we want to have, e.g. {T86152}. Stuff we have in mind that we know and influences our work. Things that show clear trends over time, like having a chart that shows a line which is a median and knowing if it's good or bad when it goes up or down and being able to remember that line so if we got asked we'd know the answer. Try to have them in place by end of June. From that point on, we could always complicate things, e.g. volunteers vs staff. Consider showing these very basic metrics on the korma frontpage. Metrics proposed (add your own) == People == * Active users of Phabricator and Gerrit on a given month (bonus point for mediawiki.org) * New accounts with activity created in Phabricator and Gerrit on a given month * Number of users that have exercised +2/-2 in Gerrit on a given month * @aklapper has defined some Maniphest related data (task creators, resolvers...) leaving this part to him == Code == * Number of changesets submitted / reviewed / merged / discarded / abandoned on a given month. * Something about the relation between changesets submitted and merged. * Gerrit review queue metrics tbd, basically showing the size and and age of the queue. == Tasks == * ...

== Intention == * Make sure that all basic metrics are in place that that we want to have (e.g. T86152). * These metrics (charts) should show clear //trends over time// (instead of an absolute snapshot number without context to compare with). It should be immediately clear and shared understanding if it's good or bad when a chart goes up or down. * These metrics should focus on engineering community related aspects. * Consider showing these very basic metrics on the korma.wmflabs.org frontpage. == Proposed metrics == === Task management (Phabricator) === | Active (having performed at least one action) accounts per month | | (?) Tasks created per month | | (?) Comments created per month | | (?) New accounts created per month | //Broader level (not "basic" metrics): T28// === Code review and changes (Gerrit/Git) === | Active changeset authors per month | | Active changeset reviewers per month (T86152) | | Changesets submitted per month | | (?) Changesets reviewed per month (depends on previous item) | | Changesets median time to review per month | //(A patch contains of 1-∞ changesets)// == IRC == | Active users per month who have sent at least one message (currently broken, see T96371) | | (?) Messages per month (currently broken, see T96371) | == Mailing lists == | Active users per month who have sent at least one message | | (?) Messages per month | == Potential followup ideas, not covered in this task == * In followup tasks, we could always complicate things, e.g. differentiating volunteers vs staff. * Changesets submitted vs merged ratio? * Gerrit review queue metrics tbd, basically showing the size and and age of the queue. * Number of users that have exercised +2/-2 in Gerrit on a given month

Check if we have all the really very basic metrics that we want to have, e.g. {T86152}.== Intention == Stuff we have in mind* Make sure that all basic metrics are in place that we know and influences our workthat we want to have (e.g. T86152). Things that show clear trends over time,* These metrics (charts) should show clear //trends over time// (instead of an absolute snapshot number without context to compare with). like having a chart that shows a line which is a median and knowingIt should be immediately clear and shared understanding if it's good or bad when it goes up or down and being able to remember that line so if we got asked we'd know the answera chart goes up or down. Try to have them in place by end of June* These metrics should focus on engineering community related aspects. From that point on, we could always complicate things, e.g. volunteers vs staff. * Consider showing these very basic metrics on the korma.wmflabs.org frontpage. Metrics p== Proposed (add your own)metrics == == People == * Active users of Phabricator and Gerrit on a given month (bonus point for mediawiki.org) * New accounts with activity created in Phabricator and Gerrit on a given month * Number of users that have exercised +2/-2 in Gerrit on a given month * @aklapper has defined some Maniphest related data (task creators, resolvers...) leaving this part to him= Task management (Phabricator) === | Active (having performed at least one action) accounts per month | | (?) Tasks created per month | | (?) Comments created per month | | (?) New accounts created per month | //Broader level (not "basic" metrics): T28// == Code= Code review and changes (Gerrit/Git) === | Active changeset authors per month | | Active changeset reviewers per month (T86152) | | Changesets submitted per month | | (?) Changesets reviewed per month (depends on previous item) | | Changesets median time to review per month | //(A patch contains of 1-∞ changesets)// == IRC == | Active users per month who have sent at least one message (currently broken, see T96371) | | (?) Messages per month (currently broken, see T96371) | == Mailing lists == | Active users per month who have sent at least one message | | (?) Messages per month | == Potential followup ideas, not covered in this task == * Number of changesets submitted / reviewed / merged / discarded / abandoned on a given month* In followup tasks, we could always complicate things, e.g. differentiating volunteers vs staff. * Something about the relation between c* Changesets submitted andvs merged. ratio? * Gerrit review queue metrics tbd, basically showing the size and and age of the queue. == Tasks == * ...* Number of users that have exercised +2/-2 in Gerrit on a given month