Contribute/Accessibility: Difference between revisions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
===Channels=== | ===Channels=== | ||
===Tools=== | |||
===Potential Contributors=== | ===Potential Contributors=== | ||
Revision as of 21:56, 8 February 2012
Steward
David Bolter and Ken Saunders
Accessibility Contribute Group
Action Plan
Goals
Channels
Tools
Potential Contributors
Active Contributors
Core Contributors
Background Information
Identify Community
Q: Can you identify all of the contributors on your team (both paid-staff and volunteer-staff)?
A: Many, but not all (yet).
Define Contribution Opportunities
Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?
A: Yes, right now we are scoped to engineering work, but I'd like to broaden the accessibility contribution space. In particular I think we need someone to help with our web presence. Accessibility/Contribute
Map Contribution Paths
Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?
A: Accessibility/Contribute but that is engineering specific.
Establish Goals and Metrics
Q: Can you measure participation or contributors today? If so, what metrics can you track? What goal or metric would you like to achieve for Q1? Alternatively, what metrics would you like to get in place for Q1?
A: Bug and mercurial activity provide our simplest metrics. I'd like input from metrics into how we can get a better picture of contribution for Q1/Q2.