MozillaWiki

Contribute/What makes a pathway: Difference between revisions

Page Discussion

Contribute/What makes a pathway (view source)

Revision as of 22:43, 13 May 2014

2,544 bytes added ,  13 May 2014
→‎Steps to building a healthy pathway
(Created page with "{{Contribute_nav_bar}} <section begin=summary />{{RoadmapSummary |icon=Logo_0002_68.png‎ |64 px |pagelocation=Contribute/whatmakesapathway |pagetitle=What Makes A Pathway? ...")
 
 
(18 intermediate revisions by 3 users not shown)
Line 11: Line 11:


<div style="display:block;-moz-border-radius:10px;background-color:#0066CC;padding:20px;margin-top:20px;">
<div style="display:block;-moz-border-radius:10px;background-color:#0066CC;padding:20px;margin-top:20px;">
<h1 style="color:#FFFFFF;">What Makes a Pathway at Mozilla?</h1> {{anchor|whatmakesapathway}}
<h1 style="color:#FFFFFF;"><center>What Makes a Pathway at Mozilla?</center></h1> {{anchor|whatmakesapathway}}
<div style="display:block;background-color:#FFFFFF;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;margin-top:30px;">
<div style="display:block;background-color:#FFFFFF;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;margin-top:30px;">
<div style="width:100%;display:block;">
<div style="width:100%;display:block;">
Line 18: Line 18:
<span style="center"><span style="font-size:150%">'''[[Contribute|Community Building Contribute Main Page.]]'''</span></span>
<span style="center"><span style="font-size:150%">'''[[Contribute|Community Building Contribute Main Page.]]'''</span></span>
</div>
</div>
  {| align="left"
  | __TOC__
  |}
=<center>What is a pathway?</center>=
A pathway is defined as a way of getting involved at any level, from beginning contribution to superstar contributor. A pathway is a healthy way for people to get involved and stay involved cross-functionally and at all levels. The pathways working group is committed to defined and innovative pathways to support our inter-organizational goal of 10x Mozillians by the end of this year and 1,000,000 Mozillians at the end of ten years.
Pathways invite and delight, and pathways can be broken down into 3 types:
*Functional area pathways
*Regional pathways
*Product specific "lenses"
This page tracks the successful pathways at Mozilla. This is a draft, and please add as necessary.


=<center>Healthy Pathways Have</center>=
=<center>Healthy Pathways Have</center>=
===Automated Response/Tracking===
===Automated Response/Tracking===
**Automated responding, systems for initial reponse to incoming potential community members
*Automated responding, systems for initial reponse to incoming potential community members
===Dedicated filtering of incoming folks===
===Dedicated filtering of incoming folks===
**Team of people who respond, triage, and help people get started
*Team of people who respond, triage, and help people get started
===Support Structure===
===Support Structure===
**Assigned supports for new contributors
*Assigned supports for new contributors
**Can be simple or complex, in order from least to most complex
*Can be simple or complex, in order from least to most complex
===BootCamp: curriculum of initial things people need to understand and do===
===BootCamp===
**For example: http://www.joshmatthews.net/trainingmontage/
Curriculum of initial things people need to understand and do
*For example: http://www.joshmatthews.net/trainingmontage/
 
==<center>Mentoring</center>==
==<center>Mentoring</center>==
==Mentored bugs==
==Mentored bugs==
Line 38: Line 54:
**https://webmaker.org/en-US/mentor
**https://webmaker.org/en-US/mentor
==Documentation==
==Documentation==
**How to get started/a "clear ask"
*How to get started/a "clear ask"
**Get Involved Page: https://support.mozilla.org/en-US/get-involved
*Get Involved Page: https://support.mozilla.org/en-US/get-involved
**Developer Getting Started Page: https://developer.mozilla.org/en-US/docs/MDN/Getting_started
*Developer Getting Started Page: https://developer.mozilla.org/en-US/docs/MDN/Getting_started
***Proposed/recommended wiki structure for contributor pages
**Proposed/recommended wiki structure for contributor pages
****Levels/achievements/next steps
***Levels/achievements/next steps
****Keep this simple
***Keep this simple
 
==Tutorials==
==Tutorials==
**Embedded, like new SUMO Knowledge Base tutorial
*Embedded, like new SUMO Knowledge Base tutorial
**Video, like Code Firefox
*Video, like Code Firefox
**Webby, like Josh's training missions
*Webby, like Josh's training missions
**Webmaker makes can be used well here
*Webmaker makes can be used well here
 
==<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)
*Ready To Contribute (Qualifying)
**Casual Contribution (1-6? contributions)
*Casual Contribution (1-6? contributions)
**Milestones between badges
*Milestones between badges
**Active Contribution (GOAL!)
*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
**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
*Work out ways your pathway can recognize
**Recognize consistently in a structured way
*Recognize consistently in a structured way
**pay attention to how people like to be recognized
*pay attention to how people like to be recognized
**Badge at conversion points and beyond
*Badge at conversion points and beyond
=<center>Steps to finding a healthy pathway</center>=
 
1. Starting point, minimum viable contribution
=<center>Steps to building a healthy pathway</center>=
*Clear conversion points
== A. Getting Started ==
**Ready to contribute
# Begin with the end in mind
**First contribution
#*What are your project's goals?
**"Casual contributor"needs better name?
#*How will scaling volunteers support these goals
**"Active contributor"
#*Turn that into deliverables
**"Superstar"
#*Turn deliverables into tasks
2. Mentor or buddy support program
#*Plan iteratively (utilize agile)
3. Localized resources
#*Check in with community and stakeholders frequently and on a schedule
4. Breaking down work
# Identify minimum viable contribution
5. Begin with the end in mind
#* document the steps a contributor must take to make this minimum viable contribution
**What are your project's goals?
#** what are the prerequisite skills?
**How will scaling volunteers support these goals
#** what are the prerequisite tasks?
**Turn that into deliverables
#** what are the required materials?
**Turn deliverables into tasks
#* in that documentation, identify and address any roadblocks (e.g. requires access to staff-only resources or require a high-level of undocumented knowledge)
**Plan iteratively (utilize agile)
# Define clear conversion points:
**Check in with community and stakeholders frequently and on a schedule
#*'''Ready to contribute:''' contributor has prerequisite skills and completed prerequisite tasks
**Document everything
#*'''First contribution:''' contributor has submitted first contribution successfully
6. Recognition program (best practices for badges are coming soon)
#*'''Active contributor:''' contributor is making regular and/or high-impact contributions
*Utilizing the recognition guide from the recognition working group including but not limited to
#*'''Privileged contributor:''' contributor, through regular, on-going activity, has earned sufficient trust and can now contribute via privileged activities (e.g. approving pull requests)
**Building levels of recognition
== B. Project Communication and Documentation ==
**Increasing levels of privilige and responsibility over time
# Identify communication channels:
**Increasing access to resources and events
#* irc
==<center>Mozilla unified badge system</center>==
#* 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)
2. Minimum viable contribution: a very small first step they can take, specific things, one task.
2. Minimum viable contribution: a very small first step they can take, specific things, one task.
3. Casual contributor: this seems to mean two small contributions or one larger one - a few hours spent
3. Casual contributor: this seems to mean two small contributions or one larger one - a few hours spent
4.  Active contributor - this of course is also people who would count  toward our organizational goal - substantive contribution,  maybe when  they host a successful event or finish a small set of bugs/makes?
4.  Active contributor - this of course is also people who would count  toward our organizational goal - substantive contribution,  maybe when  they host a successful event or finish a small set of bugs/makes?
5. Super star - some series of further badges for outstanding contributors :)
5. Super star - some series of further badges for outstanding contributors :)


Line 102: Line 153:
*Product specific "lenses"
*Product specific "lenses"


=<center>Examples of Best Practices/Pathway Success Stories</center>
=<center>Examples of Best Practices/Pathway Success Stories</center>=
==Functional==
==Functional==
===SUMO===
===SUMO===
Line 184: Line 235:
===L10N===
===L10N===
Talk to Jeff
Talk to Jeff
=Best Practices=
=Best Practices=
*Issues and Challenges:
*Issues and Challenges:
Line 231: Line 283:


<div style="-moz-border-radius: 10px;background-color:white;border:3px dashed;display:block;padding:20px;margin-top:20px;">
<div style="-moz-border-radius: 10px;background-color:white;border:3px dashed;display:block;padding:20px;margin-top:20px;">
Anything else to add?
</div>
Ckoehler
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,698

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/966391...976652"