Contribute/Automation: Difference between revisions

Line 38: Line 38:


A: We track IRC communication between people not on our core list of contributors in our channel as an indication of the number and involvement of outside contributors in our projects.  It's a very rough metric, but if someone is on IRC and interacting with us, that's a very good sign. We also track the amount that our core contributors are blogging because blogging brings us more visibility across the Mozilla project.
A: We track IRC communication between people not on our core list of contributors in our channel as an indication of the number and involvement of outside contributors in our projects.  It's a very rough metric, but if someone is on IRC and interacting with us, that's a very good sign. We also track the amount that our core contributors are blogging because blogging brings us more visibility across the Mozilla project.
As a measure of success for Release Engineering, we would track how many bugs in our component get filed by/assigned to/fixed by contributors. We would also encourage blog posts by anyone who works with our code base and projects as we love having more people discussing the types of problems we work on as well as the hows & whys of the various solutions that are implemented.


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.
Confirmed users
4,467

edits