canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,698
edits
Contribute/What makes a pathway: Difference between revisions
Jump to navigation
Jump to search
→Steps to building a healthy pathway
(adding details to pathway creation steps - in progress) |
|||
| Line 85: | Line 85: | ||
=<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 | # Begin with the end in mind | ||
#*What are your project's goals? | #*What are your project's goals? | ||
| Line 107: | Line 93: | ||
#*Plan iteratively (utilize agile) | #*Plan iteratively (utilize agile) | ||
#*Check in with community and stakeholders frequently and on a schedule | #*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 | |||
#*'''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) | |||
== B. Project Communication and Documentation == | |||
# 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? | |||
* How are tasks categorized such that contributors can easily find tasks that matches their skills and available resources? | |||
== C. Supporting & Scaling == | |||
# Implement a mentor or buddy support program | |||
# Localized resources (???) | |||
#Document everything | #Document everything | ||
#Create a recognition program (best practices for badges are coming soon) | #Create a recognition program (best practices for badges are coming soon) | ||
| Line 114: | Line 121: | ||
#**Increasing access to resources and events | #**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) | ||