Contribute/Accessibility
Steward
David Bolter and Ken Saunders
Accessibility Contribute Group
Meetings every other Monday at 10 am pacific
- Next meeting: Contribute/Accessibility/Group_02_20_12
- Notes from previous meetings
Action Plan
Goals
Determine where contributors are needed and prioritize.
Assess current or create a new (if needed) documentation and communications system (on-ramp resources?) to guide new contributors into the areas that they're interested in.
Create new contribution opportunities where they don't currently exist or are not being covered. For example, end user support, marketing, contributor recruiting, all pertaining to Mozilla accessibility of course.
Make sure that there are opportunities for anyone to get involved and help out regardless of what skills they may or may not have. It could be as simple as someone helping out with awareness, and it could eventually lead someone deeper into contributing (that's my story -Ken).
Channels
Existing Channels
Audit existing channels where potential contributors find information (or should be able to find information) about how to get involved and then optimize to make sure the channels are effective.
- http://www.mozilla.org/access/
- https://wiki.mozilla.org/Accessibility
- https://wiki.mozilla.org/Accessibility/Contribute
- http://www.mozilla.org/contribute/areas.html
- https://developer.mozilla.org/en/Accessibility
Legacy Channels
Non-Mozilla 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).
Mozillians Accessibility Group
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.