Confirmed users
4,378
edits
| Line 52: | Line 52: | ||
* (ashughes) We don't have a clear mapping of contributors, contributions, and metrics; nor any way to visualize that data if we had it. Our current priority is internally deciding what those metrics are. | * (ashughes) We don't have a clear mapping of contributors, contributions, and metrics; nor any way to visualize that data if we had it. Our current priority is internally deciding what those metrics are. | ||
* (juanb) We can measure participation in test days, and we can measure emails from people interested in participating. We don't have the on-ramps in place so we can get them to try something yet. | * (juanb) We can measure participation in test days, and we can measure emails from people interested in participating. We don't have the on-ramps in place so we can get them to try something yet. | ||
* (nhirata) We could potentially measure the bug count/bug verifications from MTD as well as testdays, and participation in test days. I am uncertain if that does give a clear mapping of contributors, contributions and metrics. | |||
Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want. | Suggestion: Write down what you think would be helpful to track even if it isn't possible to get that data today. We'll work on implementing dashboards when we know what data we want. | ||