Dashboard!

[dlespiau]

Everyone likes dashboards!

Linaro has some neat looking ones:

• https://patches.linaro.org/
• https://git.linaro.org/infrastructure/linaro-patchmetrics.git/

Would be nice to have some metrics defined and trackable. Now that patchwork has some background tasks with celery, we can compute those metrics every hour/day/week/month, store them in the DB (or live query them if fast enough) and display them in the project page.

[belenbarrospena]

This would a nice piece to design. Step 1 is identifying potential useful metrics. Linaro ones can serve as a starting point, but your project might be interested in other things. So, which metrics would you like to see?

[dlespiau]

That's a question I'm asking people right now

[dlespiau]

After having talked to Jari, we came up with some ideas to start with:

Metrics

• number of patches per month/week
• number of series per month/week
• number of accepted/rejected patches
• time between submissions and first test result (Histogram with increments of 5mins, n/a bucket (series isn't complete, so can't be tested), CI failed to test the series bucket)
• time to the first review by human
• time to acceptance (or maybe time to "final" state like rejection/acceptance, or both)
• number of review-by tags per month/week

Some random notes:

• Have a field for the resolution date (ie when the state is final, eg. rejected/accepted)
• more interested in metrics per week
• Should start with CI related metrics, that's something we want to follow closely