Confirmed users
4,378
edits
Contribute/QA: Difference between revisions
Jump to navigation
Jump to search
→Establish Goals and Metrics
| Line 57: | Line 57: | ||
* (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. | * (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. | ||
** addendum: also having a search in litmus for test cases or test runs. | ** addendum: also having a search in litmus for test cases or test runs. For webqa, potentially pushes to selenium tests may be checked. | ||
* (marcia) Bugzilla probably would provide the most metrics, since many QA contributors file bugs. Next year I was thinking about having a membership drive - if we had something like that we track entry for newcomers. I also think another way to track contributors might be getting them to join the community phonebook and have a field for the date they joined the project. | * (marcia) Bugzilla probably would provide the most metrics, since many QA contributors file bugs. Next year I was thinking about having a membership drive - if we had something like that we track entry for newcomers. I also think another way to track contributors might be getting them to join the community phonebook and have a field for the date they joined the project. | ||
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. | ||