canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,698
edits
Contribute/What makes a pathway: Difference between revisions
→Steps to building a healthy pathway
m (→Tutorials) |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 69: | Line 69: | ||
==<center>Conversion Points</center>== | ==<center>Conversion Points</center>== | ||
Track number of things done, over an amount of time, and whether the work is getting used to move the Mozilla project forward | Track number of things done, over an amount of time, and whether the work is getting used to move the Mozilla project forward | ||
*Ready To Contribute (Qualifying) | |||
*Casual Contribution (1-6? contributions) | |||
*Milestones between badges | |||
*Active Contribution (GOAL!) | |||
Examples of active contribution: | **Examples of active contribution: 30 hours logged, two L10N firefox contribution credits over two releases, xx number of support responses, etc | ||
*Work broken down into: | *Work broken down into: | ||
**Minimum viable first contribution followed by increasing size/complexity of contributions and increasing responsibility in the project. | **Minimum viable first contribution followed by increasing size/complexity of contributions and increasing responsibility in the project. | ||
**This maps to conversion points and recognition. | **This maps to conversion points and recognition. | ||
==<center>Recognition</center>== | ==<center>Recognition</center>== | ||
*Work out ways your pathway can recognize | |||
*Recognize consistently in a structured way | |||
*pay attention to how people like to be recognized | |||
*Badge at conversion points and beyond | |||
=<center>Steps to building a healthy pathway</center>= | =<center>Steps to building a healthy pathway</center>= | ||
== A. Getting Started == | |||
# Begin with the end in mind | |||
#*What are your project's goals? | |||
#*How will scaling volunteers support these goals | |||
#*Turn that into deliverables | |||
#*Turn deliverables into tasks | |||
#*Plan iteratively (utilize agile) | |||
#*Check in with community and stakeholders frequently and on a schedule | |||
# Identify minimum viable contribution | |||
#* document the steps a contributor must take to make this minimum viable contribution | |||
#** what are the prerequisite skills? | |||
#** what are the prerequisite tasks? | |||
#** what are the required materials? | |||
#* in that documentation, identify and address any roadblocks (e.g. requires access to staff-only resources or require a high-level of undocumented knowledge) | |||
# Define clear conversion points: | |||
#*'''Ready to contribute:''' contributor has prerequisite skills and completed prerequisite tasks | |||
#*'''First contribution:''' contributor has submitted first contribution successfully | |||
**Document everything | #*'''Active contributor:''' contributor is making regular and/or high-impact contributions | ||
#*'''Privileged contributor:''' contributor, through regular, on-going activity, has earned sufficient trust and can now contribute via privileged activities (e.g. approving pull requests) | |||
*Utilizing the recognition guide from the recognition working group including but not limited to | == B. Project Communication and Documentation == | ||
**Building levels of recognition | # Identify communication channels: | ||
**Increasing levels of privilege and responsibility over time | #* irc | ||
**Increasing access to resources and events | #* mailinglist | ||
#* vidyo | |||
#* skype | |||
#* regular meeting times | |||
#* project leads, mentors | |||
#* bug tracker details | |||
#* project files (e.g. source code) | |||
# '''Task tracking and communication.''' Identify and document the following: | |||
#* Where are tasks tracked? | |||
#* Can contributors access this? | |||
#* How do contributors pick up tasks from this system and submit their work? | |||
# '''Categorize tasks.''' Identify those tasks that differ from the minimum viable contribution in terms of required skills, knowledge and/or access. | |||
#*For each grouping of these tasks, identify and document: | |||
#** what is the prerequisite Mozilla project experience? | |||
#** what are the prerequisite skills? | |||
#** what are the prerequisite tasks? | |||
#** what are the required materials? | |||
#* in that documentation, identify and address any roadblocks (e.g. requires access to staff-only resources or require a high-level of undocumented knowledge) | |||
== C. Supporting & Scaling == | |||
# Implement a mentor or buddy support program | |||
# Localized resources (???) | |||
#Document everything | |||
#Create a recognition program (best practices for badges are coming soon) | |||
#*Utilizing the recognition guide from the recognition working group including but not limited to | |||
#**Building levels of recognition | |||
#**Increasing levels of privilege and responsibility over time | |||
#**Increasing access to resources and events | |||
=<center>Mozilla unified badge system</center>= | |||
1. Get Ready: badge folks for going through the Webmaker curriculum, setting themselves up with whatever account access they need (like Bugzilla) | 1. Get Ready: badge folks for going through the Webmaker curriculum, setting themselves up with whatever account access they need (like Bugzilla) | ||