Pathways roadmap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 44: Line 44:
Core, foundational work that blocks other priorities
Core, foundational work that blocks other priorities
<ul>
<ul>
<li>[https://cbt.etherpad.mozilla.org/what-makes-a-pathway|What makes a strong pathway?]</li>
<li>Working definition of a pathway that we can move forward with</li>
<li>Working definition of a pathway that we can move forward with</li>
<li>What makes a strong pathway?</li>
<li>Review all the existing pathways (functional and regional) and see what needs to be done</li>
<li>Review all the existing pathways (functional and regional) and see what needs to be done</li>
<li>Go through current requests for pathways ('''other''' section of Contribute)</li>
<li>Go through current requests for pathways ('''other''' section of Contribute)</li>

Revision as of 19:35, 30 January 2014

Grow mozilla large.png Main | Resources | Working Groups | Get Involved Main Page | Team | Maturity Model | Build Principles


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


Roadmap!

Contribution is our #1 metric

The steering committee has set a goal of ten times growth by the end of 2014.

We want to work with new and current contributors. Learn more about how their pathways to contribution

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

See a more [[ | detailed list of what our contributors do]].

2014 Priorities

What are we SHIPPING to support these goals and bring in more people? What are contributors helping us build?

Priority 1

Core, foundational work that blocks other priorities

  • makes a strong pathway?
  • Working definition of a pathway that we can move forward with
  • Review all the existing pathways (functional and regional) and see what needs to be done
  • Go through current requests for pathways (other section of Contribute)
  • Understand how regional pathways can foster and nurture volunteers
  • Initial refresh of "Get Involved" page

Priority 2

What we will tackle first.

  • Define criteria for Contributor Management System
  • Build CMS that satisfies all stakeholders
  • Make a plan for what we are going to offer for people who are building pathways
  • Continue refreshing "Get Involved" page to be more inclusive and organic for new contributors

Priority 3

  • Communicate resource kit out so that people know what they can do

Timeline

(in progress)

Q1: Jan to March: Design and build
  • Develop a set of best practices for finding pathways
  • Basic refresh of Get Involved Page (http://www.mozilla.org/en-US/contribute/)
  • Audit and understand already existing mentorship possibilities
    • Community growth focus: Design new tools, imagine the present and future

Q2: April to June: Prepare and refine

    • Community growth focus: Develop and build new tools for contribution

Q3: July to Sep: Campaign and grow

    • Community growth focus: Launch and campaign for new tools
Q4: Oct to Dec: Harvest and celebrate
    • Community growth focus: Measure and reflect


Next steps on this document

  • Refine and develop Q2-Q4 goals
  • Define quantifiable metrics for what makes a contribution pathway