Pathways roadmap: Difference between revisions

 
(22 intermediate revisions by 2 users not shown)
Line 17: Line 17:
<div style="width:100%;display:block;">
<div style="width:100%;display:block;">


= Goal =
= Pathways Areas and Drivers: A 2014 Roadmap =




<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<b>[[Contribute|More on 2014 goals and how to get involved.]]</b>
<span style="center"><span style="font-size:150%">'''[[Contribute|Community Building Contribute Main Page.]]'''</span></span>
</div>
</div>
</div>
==Contribution is our #1 metric==
==Contribution is our #1 metric==


We work with new and current contributors. Define how pathways are built. Learn more about how we build their pathways to contribution.
Through defined and innovative pathways we can reach our goal of 1,000,000 Mozillians in ten years and 10x by the end of this year.


==What constitutes a contribution pathway?==  
==Shared Goals across the Pathways Working Group:==


* '''Targeting interest:''' through get involved, a regional group, or a specific product
*'''Support each others' work:''' Subgroups work together to build together
* '''Maintaining interest:''' through systems that funnel from participant to contributor
*'''Share out resources and work in the open:''' Check in regularly and share out resources that may relate to another subgroup's work. Work in the open utilizing our shared communication tools. Follow the group decisions on how to share through defined communications pathways
* '''Following through on interest:''' developing mentorship and new opportunities that challenge and motivate contributors and participants
*'''Treat each other (contributor and staff) with respect:''' The goal of pathways is to make every form of contribution meaningful. Practice what we preach. Be respectful of each others' time and be aware of varying levels of commitment.
*'''Commit where you can:''' We are all superstars. If you cannot commit the time to a task, please do not take it on. Bite off only what you can chew.
*'''Step up, step back:''' Step up to new challenges where you think you can be of assistance. Step back if you are doing or contributing too much. Follow consensus and facilitation best practices


=2014 Priorities=
==What constitutes a contribution pathway?==  


What are we SHIPPING to support these goals and bring in more people? What are contributors helping us build?
** '''Targeting interest:''' through get involved, a regional group, or a specific product
** '''Maintaining interest:''' through systems that funnel from participant to contributor
** '''Following through on interest:''' developing mentorship and new opportunities that challenge and motivate contributors and participants


== Priority 1 ==
=Pathways Subgroups and Goals Q3-Q4=
Core, foundational work that blocks other priorities
High Level Goals:
<ul>
# Build alignment in the organization around a community contribution stages model.
<li>[https://cbt.etherpad.mozilla.org/what-makes-a-pathway| What makes a strong pathway?]</li>
# Build pathways best practices, resources, templates and tools that are both useful and beautiful, so that we make pathway building scalable and any mozillian can build a pathway.
<li>What kinds of contributions can people make in every project, at every level?</li>
# Support brand new contributors and the projects they join by building a community of mentors and a system to support them.
<li>Review all the existing pathways (functional and regional). Make a chart of contribution points across the organization.</li>
<li>Go through current requests for pathways ('''other''' section of Contribute) '''complete 2/2014'''</li>
<li>Understand how regional pathways can foster and nurture volunteers.</li>
<li>Initial refresh of "Get Involved" page.</li>
<li>Define minimum contribution across the project</li>
</ul>


== Priority 2 ==
= Next steps on this document =
What we will tackle first.
<ul>
<li>Define criteria for Contributor Management System '''2/2014: Completed. See here: https://docs.google.com/document/d/1o403WvYzoNYZ0mM-ciOLo0XFYaWAIC-3YriMvQ_q9qY/edit'''</li>
<li>Create an actionable plan of best practices and define what makes a contribution pathway through a checklist or other itemized contribution audit.</li>
<li>Discuss new contributor pathway finding tool to build and grow work. Ship one tool by Q3.</li>
<li>Define and incentivize minimum contribution across the project</li>
<li>Second refresh of "Get Involved" page to be more inclusive and organic for new contributors</li>
<li>Develop, locate, and distribute resources linked into the contributor lifecycle. '''ongoing'''</li>
<li>Develop framework for new volunteer matching system to match volunteers with relevant projects and people</li>
<li>Create a collaborative mechanism that can categorize and organize incoming Get Involved emails. Write a script that will analyze and sort existing correspondence to Get Involved page.</li>
<li>Each local community will create one resource (video, blog post, website, event) to support people looking for regional pathways.</li>
<li></li>


</ul>
=== 2014-Q3 ===
<bugzilla>
    {
        "product": "Community Building",
        "component": "Pathways",
        "target_milestone": "2014Q3",
        "include_fields": "id, severity, summary, whiteboard, priority, status"
    }
</bugzilla>
=== 2014-Q4 ===
<bugzilla>
    {
        "product": "Community Building",
        "component": "Pathways",
        "target_milestone": "2014Q4",
        "include_fields": "id, severity, summary, whiteboard, priority, status"
    }
</bugzilla>


== Priority 3 ==
<ul>
<li>Cross team analysis of best practice model</li>
<li>Run metrics on new Get Involved page</li>
<li>Implement new contributor management system</li>
<li>Implement new pathways developed from best practice finder via SUMO</li>
<li>Incentivize higher levels of participation</li>
</ul>
=Timeline=
(in progress)
'''Q1:''' <i>Jan to March</i>: <b>Design and build</b><br
/><ul><li>Develop a set of best practices for finding pathways</li>
<li>Basic refresh of Get Involved Page (http://www.mozilla.org/en-US/contribute/)</li>
<li>Audit and understand already existing mentorship possibilities</li>
<ul><li>Community growth focus: Design new tools, imagine the present and future<b></b></li></ul></ul>
<b>Q2:</b> <i>April to June</i>: <b>Continue tool development, prepare tools, and refine</b><br/>
<li>Meet with stewards and drivers to implement best practices for pathway finding into their individual efforts</li>
<li>Launch new pathway finding tool</li>
<ul><li>Community growth focus: Develop and build new tools for contribution<b></b></li></ul></ul>
<b>Q3:</b> <i>July to Sep</i>: <b>Campaign and grow</b><br/>
<ul><li></li><ul><li>Community growth focus: Launch and campaign for new tools<b></b></li></ul></ul>
<b>Q4: </b><i>Oct to Dec</i>: <b>Harvest and celebrate</b><br/>
<ul><li>Share out new materials developed</li><ul>
<li>Write a report that outlines new contributor pathways found</li>
<ul><li></li><ul><li>Community growth focus: Measure and reflect<b></b></li></ul></ul>
</div>
</div>
<div style="-moz-border-radius: 10px;background-color:white;border:3px dashed;display:block;padding:20px;margin-top:20px;">
= Next steps on this document =
*Refine and develop Q2-Q4 goals
*Define quantifiable metrics for what makes a contribution pathway
</div>
</div>

Latest revision as of 02:40, 27 August 2014


Logo 0002 68.png Pathways Roadmap 2014
Owner: Pathways Team Updated: 2014-08-27
Vision: The Pathways working group seeks to remove the barriers to contribution so that participation, however it is defined, is beautifully simple.


Roadmap!

Pathways Areas and Drivers: A 2014 Roadmap

Contribution is our #1 metric

Through defined and innovative pathways we can reach our goal of 1,000,000 Mozillians in ten years and 10x by the end of this year.

Shared Goals across the Pathways Working Group:

  • Support each others' work: Subgroups work together to build together
  • Share out resources and work in the open: Check in regularly and share out resources that may relate to another subgroup's work. Work in the open utilizing our shared communication tools. Follow the group decisions on how to share through defined communications pathways
  • Treat each other (contributor and staff) with respect: The goal of pathways is to make every form of contribution meaningful. Practice what we preach. Be respectful of each others' time and be aware of varying levels of commitment.
  • Commit where you can: We are all superstars. If you cannot commit the time to a task, please do not take it on. Bite off only what you can chew.
  • Step up, step back: Step up to new challenges where you think you can be of assistance. Step back if you are doing or contributing too much. Follow consensus and facilitation best practices

What constitutes a contribution pathway?

    • Targeting interest: through get involved, a regional group, or a specific product
    • Maintaining interest: through systems that funnel from participant to contributor
    • Following through on interest: developing mentorship and new opportunities that challenge and motivate contributors and participants

Pathways Subgroups and Goals Q3-Q4

High Level Goals:

  1. Build alignment in the organization around a community contribution stages model.
  2. Build pathways best practices, resources, templates and tools that are both useful and beautiful, so that we make pathway building scalable and any mozillian can build a pathway.
  3. Support brand new contributors and the projects they join by building a community of mentors and a system to support them.

Next steps on this document

2014-Q3

Full Query
ID Severity Summary Whiteboard Priority Status
1057122 normal Choose your own adventure manual for guides P1 NEW
1058880 normal Define Community Contribution Stages P1 NEW

2 Total; 2 Open (100%); 0 Resolved (0%); 0 Verified (0%);

2014-Q4

Full Query
ID Severity Summary Whiteboard Priority Status
1058890 normal Pathways into Community Building -- RESOLVED
1058892 normal Example Pathways and Template that is Beautiful -- RESOLVED

2 Total; 0 Open (0%); 2 Resolved (100%); 0 Verified (0%);