Change Details

== 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

== Intention == * Make sure that all basic metrics are in place that that we want to have. * 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 / discussed metrics == === Code review and changes (Gerrit/Git) === | Active Gerrit users per month | ☒ T86152 | | (?) Active changeset authors per month | subgroup of above | | (?) Active changeset reviewers per month | subgroup of above | | Changesets submitted per month | ☑ called "Submitted" on http://korma.wmflabs.org/browser/scr.html (though not sure if Patches or Changesets) | | (?) Changesets reviewed per month (depends on previous item) | ☒ only "Merged" and "Abandoned" on http://korma.wmflabs.org/browser/scr.html ? | | (?) Changesets waiting for review per month | ☑ called "Pending" on http://korma.wmflabs.org/browser/scr.html (though not sure if Patches or Changesets) | | Changesets median time to review per month | ☒ I think I saw this once but cannot find it. | //(A patch contains of 1-∞ changesets)// === Task management (Phabricator) === | Accounts per month that have performed at least one action | ☐ Currently only via SQL query in [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081421.html | monthly Phab stats email on wikitech-l ]] | | (?) Median age of open tasks per priority | ☐ Currently only via SQL query in [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081421.html | monthly Phab stats email on wikitech-l ]] | | (?) Tasks created per month | ☐ Currently only via SQL query in [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081421.html | monthly Phab stats email on wikitech-l ]] | | (?) Comments created per month | ☒ | | (?) New accounts created per month | ☐ Currently only via SQL query in [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081421.html | monthly Phab stats email on wikitech-l ]] | //Broader level (not "basic" metrics): T28// == IRC == | Users per month who have sent at least one message | ☐ http://korma.wmflabs.org/browser/irc.html but currently broken: T96371; cf. T56230 | | (?) Messages per month | ☐ http://korma.wmflabs.org/browser/irc.html but currently broken: T96371; cf. T56230 | == Mailing lists == | Users per month who have sent at least one message | ☑ on http://korma.wmflabs.org/browser/mls.html | | (?) Messages per month | ☑ on http://korma.wmflabs.org/browser/mls.html | == 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. * Users that have exercised +2/-2 in Gerrit on a given month: {T59038}

== 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 ==/ discussed metrics == === Code review and changes (Gerrit/Git) === | Active Gerrit users per month | ☒ T86152 | | (?) Active changeset authors per month | subgroup of above | | (?) Active changeset reviewers per month | subgroup of above | | Changesets submitted per month | ☑ called "Submitted" on http://korma.wmflabs.org/browser/scr.html (though not sure if Patches or Changesets) | | (?) Changesets reviewed per month (depends on previous item) | ☒ only "Merged" and "Abandoned" on http://korma.wmflabs.org/browser/scr.html ? | | (?) Changesets waiting for review per month | ☑ called "Pending" on http://korma.wmflabs.org/browser/scr.html (though not sure if Patches or Changesets) | | Changesets median time to review per month | ☒ I think I saw this once but cannot find it. | //(A patch contains of 1-∞ changesets)// === Task management (Phabricator) === | Active (havingcounts per month that have performed at least one action) accounts per month | | ☐ Currently only via SQL query in [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081421.html | monthly Phab stats email on wikitech-l ]] | | (?) Median age of open tasks per priority | ☐ Currently only via SQL query in [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081421.html | monthly Phab stats email on wikitech-l ]] | | (?) Tasks created per month | ☐ Currently only via SQL query in [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081421.html | monthly Phab stats email on wikitech-l ]] | | (?) Comments created per month | ☒ | | (?) New accounts created per month | ☐ Currently only via SQL query in [[ https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081421.html | monthly Phab stats email on wikitech-l ]] | //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 == | Users per month who have sent at least one message | ☐ http://korma.wmflabs.org/browser/irc.html but currently broken: T96371; cf. T56230 | | Active users per month who have sent at least one message (currently broken, see T96371) | | (?) Messages per month (currently broken,(?) Messages per month | ☐ http://korma.wmflabs.org/browser/irc.html but currently broken: T96371; see T96371) |cf. T56230 | == Mailing lists == | Users per month who have sent at least one message | ☑ on http://korma.wmflabs.org/browser/mls.html | | Active user| (?) Messages per month who have sent at least one message | | (?) Messages per month | | ☑ on http://korma.wmflabs.org/browser/mls.html | == 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 u* Users that have exercised +2/-2 in Gerrit on a given month : {T59038}