Contribute/Accessibility: Difference between revisions

← Older edit

Contribute/Accessibility (view source)

Revision as of 20:55, 22 September 2014

2,765 bytes added , 22 September 2014

no edit summary

Jennierose

canmove, Confirmed users

868

edits

@@ Line 1: / Line 1: @@
 =Steward=
-David Bolter
+David Bolter and Ken Saunders
-=Identify Community=
+=Accessibility Contribute Group=
+No regularly scheduled meetings
+* Next meeting: [[Contribute/Accessibility/Group_03_12_12]] (Date TBD)
+* Notes from [[Contribute/Accessibility/Group_Meeting_Notes|previous meetings]]
+=Action Plan=
+===Goals===
+Determine where contributors are needed and prioritize.
+(please add to the list)
+* [https://wiki.mozilla.org/Contribute/Accessibility/Opportunities#Coding Coding]
+* [https://wiki.mozilla.org/Contribute/Accessibility/Opportunities#Mozilla_A11y_Social_Media Social media manager(s)]
+* [https://wiki.mozilla.org/Contribute/Accessibility/Opportunities#Accessibility_Web_Mess_Cleanup Web mess cleanup]
+* [https://wiki.mozilla.org/Contribute/Accessibility/Opportunities#Accessibility_Content_on_MDN MDN accessibility docs cleanup]
+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'''
+http://www-archive.mozilla.org/access/
+'''Non-Mozilla Channels'''
+* http://www.accessfirefox.org/
+===Tools===
+'''Coding Specific Tools'''
+* '''Register''' an account on [https://bugzilla.mozilla.org/ Bugzilla].
+* '''Find a mentored bug:''' Find a task to work on. [http://www.joshmatthews.net/bugsahoy/?a11y=1 Use this search] to find a mentored bug to work on.
+* '''Patch review:''' Once you have made a patch for a bug, attach it to the bug and [https://developer.mozilla.org/En/Developer_Guide/How_to_Submit_a_Patch#Getting_Reviews request review] for it. It's just a matter of setting 'review?' on it and selecting an appropriate reviewer.
+* '''Make your own build''' of Firefox, from the source code of the development version (mozilla-central). [https://developer.mozilla.org/En/Simple_Firefox_build This page] explains how to do that.
+===Potential Contributors===
+* Create a clear and simple breakdown of contribution opportunities with the fewest amount of clicks as possible to get potential contributors started right away.
+* Create on-ramp resources to guide new contributors into the areas that they're interested in. Include personal interactions to welcome them in and give them the opportunity to introduce themselves to the community.
+===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:
+A: Many, but not all (yet).
-Suggestion: Use the [http://www.mozillians.org mozillians.org contributor directory] to help.  Communicate through your team's channels and encourage people to sign up and group themselves with a common team tag.
+[https://wiki.mozilla.org/Accessibility/People Mozillians Accessibility Group]
-=Define Contribution Opportunities=
+==Define Contribution Opportunities==
 Q: Can you point someone interested in contributing to your project to a list of available contribution opportunities?
-A:
+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]]
-Suggestion: Look at what your team's needs are and what gaps you have in staffing to come up with a list of contribution opportunities.  Capture those on a wiki page, in bugs, as role descriptions in Jobvite or whatever makes sense for your community.
+==Map Contribution Paths==
-=Map Contribution Paths=
 Q: Are there clearly understood steps someone can follow to go from knowing nothing about your project to successfully contributing?
-A:
+A: [[Accessibility/Contribute]] but that is engineering specific.
-Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.
-=Establish Goals and Metrics=
+==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:
+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.
-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.
+[[Category: Contribute]] [[Category: Accessibility]]