Contribute/Pathways: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(120 intermediate revisions by 12 users not shown)
Line 1: Line 1:
<noinclude>
{{Contribute_nav_bar}}
<section begin=summary />{{RoadmapSummary
|icon=Logo_0002_68.png‎ |64 px
|pagelocation=pathways_roadmap
|pagetitle=Pathways Working Group Page
|owner=Pathways Team
|updated=Jan 28, 2014
|description=Vision: The Pathways working group seeks to remove the barriers to contribution so that participation, however it is defined, is beautifully simple.
}}<section end=summary />
<div style="display:block;-moz-border-radius:10px;background-color:#FF9966;padding:20px;margin-top:20px;">
<h1 style="color:#FFFFFF;"><center>Pathways Community Building Working Group</center></h1> {{anchor|Pathways}}
<div style="display:block;background-color:#FFFFFF;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;margin-top:30px;">
__TOC__
__TOC__


The following people answer contribution inquiries from the [http://www.mozilla.org/contribute Get Involved] page.
=Goal=
 
Pathways is focused on [http://www.mozilla.org/contribute contribution pathways] for functional and regional areas as a way to [[Contribute/Workshops/Onboarding|identify, qualify and onboard]] new volunteers.  
 
=Vision=
The Pathways working group seeks to remove the barriers to contribution so that participation, however it is defined, is beautifully simple.
 
=Strategies and Goals=
 
 
<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<b><center><span style="font-size:120%">'''[[Pathways_roadmap| The Pathways Working Group's 2014 Roadmap can be found here. For 2014 goals and deliverables, please add to this document!]]'''</span></center></b>
</div>
 
 
 
*'''Systems:''' Establish a discoverable, scaleable, brand-consistent online hub where contributors can intuitively find opportunites to participate.
*'''Mentorship:''' Make 1:1 mentorship a measurable requirement for all Mozillians.
*'''Motivation:''' Understand  the motivations that drive participation in the Mozilla Project so  that  we create processes and programs that make all contributors'  experiences as rich and gratifying as possible.
*'''Build Pathways:''' Establish a rigorous process that continuously pushes us to expand and evolve our definition of "contribution" and to design clear contribution pathways that support those proving most effective. This includes both improving and reinventing our existing contribution paths, and developing new opportunities for Mozillians to contribute.
 
==What Makes a Pathway?==
 
(collaborative document here: https://cbt.etherpad.mozilla.org/what-makes-a-pathway)
 
*Breaking down work
* Begin with the end in mind
* What are your project's goals?
** How will scaling volunteers support these goals?
** Turn these goals into deliverables
** Turn deliverables into tasks
** Plan iteratively (agile)
** Check in with community and stakeholders frequently and on a schedule
** Document everything
 
===Kinds of Pathways===
* Functional area pathways
* Regional pathways
* Product specific pathways
 
=How to Participate=
</noinclude>
== Meetings ==
 
See [[Contribute#Joint Recognition/Pathways/Education Working Groups meeting]]
 
== Discussion Forum ==
Pathways communicates via [https://discourse.mozilla-community.org/ Discourse] and the CBT discussion list #pathways
 
== Meeting Notes ==
{{:Pathways/meetings}}
 
 
<noinclude>
=Etherpads=
 
'''''Updated February 2014'''''


=By Functional Area=
* [https://cbt.etherpad.mozilla.org/2013-meetup-actionplan-pathways| Action plan from 2013 Community Meetup]
* [https://cbt.etherpad.mozilla.org/pathways-2014-meeting-notes| 2014 Meeting Notes]
* [https://cbt.etherpad.mozilla.org/2013-meetup-track-pathways| 2013 Meetup Planning Notes]
==Get Involved Details==


These are the people handling inquiries in different functional areas for the en-US/contribute page.
Information about how the Get Involved page works to put contributors on to contribution pathways.


{| border="1"
* https://wiki.mozilla.org/Contribute/Get_Involved_Details
! Functional Area !! Point Person !! Auto or Manual response
|-
| Support
| [https://mozillians.org/en-US/u/42062df727 Jay], [https://mozillians.org/en-US/rosana Rosana] and [https://mozillians.org/en-US/madasan Madalina]
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/support.txt Auto]
|-
| QA
| Various QA staff
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/qa.txt Auto]
|-
| Coding
| [https://mozillians.org/en-US/jdm jdm]
| [[Contribute/Canned_responses#Coding|Manual]]
|-
| Marketing
| [https://mozillians.org/en-US/chelsea Chelsea]
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/marketing.txt Auto]
|-
| Localization
| [https://mozillians.org/en-US/rosana Rosana], [https://mozillians.org/en-US/gueroJeff Jeff] and [https://mozillians.org/en-US/arky Arky]
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/localization.txt Auto]
|-
| Webdev
| [https://mozillians.org/en-US/groovecoder Luke]
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/webdev.txt Auto]
|-
| Addons
| [https://mozillians.org/en-US/amyt Amy]
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/addons.txt Auto]
|-
| Visual Design
| [https://mozillians.org/en-US/matej Matej]
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/design.txt Auto]
|-
| Documentation
| [https://mozillians.org/en-US/jms Janet]
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/documentation.txt Auto]
|-
| Education
| [https://mozillians.org/en-US/benjaminsimon Ben]
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/education.txt Auto]
|-
| Other
| [https://mozillians.org/en-US/davidwboswell David]
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/other.txt Auto]
|-
| Firefox Suggestions
| [https://mozillians.org/en-US/u/42062df727 Jay]
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/suggestions.txt Auto]
|-
| Firefox Issues
| [https://mozillians.org/en-US/u/42062df727 Jay]
| [https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/mozorg/emails/issue.txt Auto]
|}


=Contributor Conversion Points=


''Note: You can see the full list of [[Contribute/Resources|all functional areas]] on the wikiNot all functional areas are included in the form for a variety of reasons (eg, some teams aren't ready to be hooked up to the form and others have contribution opportunities that are a better fit for people after they've started contributing in other areas.)''
In 2012, community builders decided upon a set of "conversion points" (or levels of participation) [[Contribute/Conversion_points|'''''(found here)''''']] to provide information about the contributor lifecycle for the [http://www.arewegrowingyet.com Grow Mozilla dashboard]See [https://bugzilla.mozilla.org/show_bug.cgi?id=736109 bug 736109] for details about implementing this and see [http://davidwboswell.wordpress.com/2012/05/03/creating-a-superstar-radar/ The SuperStar Radar] blog post for information about why this is helpful for community building.


=By Locale=
=Capacity=
Capacity is a measure of the community building potential of pathways. Knowing the capacity of a pathway helps us provide support through programs and guides that are appropriate to their current situation.
'''[[Contribute/Capacity | How do I determine my community's capacity?]]'''


These are the people handling inquiries in different locales for localized versions of the page.
=Missions=
Training missions are a scalable way to onboard new contributors to help them gain experience and develop skills that will allow them to successfully get involved in projects at Mozilla.


''Note: Content to be localized can be found at http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/locales/en-GB/mozorg/contribute.lang?view=markup''
* '''[http://www.joshmatthews.net/trainingmontage/ Firefox development training mission]''' -- Walks someone through how to turns the tabs of Firefox green by editing Firefox's CSS files
* '''[http://www.tizianasellitto.it/trainingmontage/bugzilla-triage-tutorial.html Bug triage tutorial]''' -- Walks someone through the basics of Bugzilla triage on test data
* '''[http://www.whatcanidoformozilla.org What can I do for Mozilla?]''' This walks through various languages and skills in which people may want to contribute!
* '''[http://www.codefirefox.org Learn to code by hands on coding Firefox!]'''


{| border="1"
</div>
! Locale !! Point Person !! Auto or Manual response !! Tracking bug !! Status
</div>
|-
</noinclude>
| ar
| haitham
|
|
|-
| bn-BD
| [[User:maktrix|mak]]
|
|
|-
| bn-IN
| [https://mozillians.org/en-US/Swarnava Swarnava]
|
|
|-
| bs
| [https://mozillians.org/en-US/kerminator Kerim Kalamujic]
|
| {{bug|795779}}
|-
| en-GB
| leo
|
|
|-
| es
| Mozilla Hispano participation team (participa at mozilla-hispano dot org)
|
| {{bug|760820}}
| [https://www-dev.allizom.org/b/es-ES/contribute/ on stage]
|-
| fr
| pascalc and archaf
|
| {{bug|797839}}
| [https://www-dev.allizom.org/b/fr/contribute/ on stage]
|-
| fy-NL
| [https://mozillians.org/en-US/moZes Wim Benes]
|
| {{bug|796401}}
|-
| ga-IE
| Brian King (:kinger)
|
|
|-
| he
| [https://mozillians.org/en-US/tomer tomer]
|
| {{bug|795130}}
|-
| hi-IN
| [https://mozillians.org/en-US/Faisalaziz Faisal]
|
| {{bug|795364}}
|-
| hr
| nikola
|
| {{bug|760823}}
|-
| id
| Benny Chandra (Benny)
|
|
|-
| lt
| [https://mozillians.org/en-US/RQ rimas]
|
| {{bug|792107}}
|-
| ms
| aidid
|
|
|-
| nl
| Tonnes and contribute at mozilla dash nl dot org
|
| {{bug|796406}}
|-
| nepal
| avash
|
|
|-
| philippines
| bob reyes (:Bobreyes)
|
|
|-
| pt-br
| [https://mozillians.org/en-US/marceloaraldi marcelo]
|
| {{bug|760821}}
| [https://www-dev.allizom.org/b/pt-BR/contribute/ on stage]
|-
| ro
| [https://reps.mozilla.org/u/ioana_chiorean/ Ioana]
|
| {{bug|799273}}
|
|-
| sl
| smo (aka Vito)
|
|
|-
| sq
| Besnik_b
|
| {{bug|795033}}
|-
| sr
| [https://mozillians.org/en-US/icecold Oskar Ivanić (:icecold)]
|
| {{bug|796066}}
|-
| sw
| [[User:stephenwanjau|Stephen]]
|
| {{bug|795488}}
|-
| ta
| [https://mozillians.org/en-US/gautha91  Gauthamraj Elango ]
|
| {{bug|796062}}
|-
| tr
| [https://mozillians.org/u/selim  Selim Sumlu  ]
|
| {{bug|819557}}
|-
| zh-cn
| [https://mozillians.org/en-US/rachelz Rachel Zhang] and cn dash community at mozilla dot com
|
| {{bug|795546}}
|-
| zh-tw
| [https://reps.mozilla.org/u/Irvin/ Irvin] and [https://reps.mozilla.org/u/petercpg/ petercpg] ([http://moztw.org MozTW]), [http://reps.mozilla.org/u/bobchao Bob Chao]
|
| {{bug|795304}}
|}

Latest revision as of 23:07, 9 September 2014

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


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

Pathways Community Building Working Group

Goal

Pathways is focused on contribution pathways for functional and regional areas as a way to identify, qualify and onboard new volunteers.

Vision

The Pathways working group seeks to remove the barriers to contribution so that participation, however it is defined, is beautifully simple.

Strategies and Goals


  • Systems: Establish a discoverable, scaleable, brand-consistent online hub where contributors can intuitively find opportunites to participate.
  • Mentorship: Make 1:1 mentorship a measurable requirement for all Mozillians.
  • Motivation: Understand the motivations that drive participation in the Mozilla Project so that we create processes and programs that make all contributors' experiences as rich and gratifying as possible.
  • Build Pathways: Establish a rigorous process that continuously pushes us to expand and evolve our definition of "contribution" and to design clear contribution pathways that support those proving most effective. This includes both improving and reinventing our existing contribution paths, and developing new opportunities for Mozillians to contribute.

What Makes a Pathway?

(collaborative document here: https://cbt.etherpad.mozilla.org/what-makes-a-pathway)

  • Breaking down work
  • Begin with the end in mind
  • What are your project's goals?
    • How will scaling volunteers support these goals?
    • Turn these goals into deliverables
    • Turn deliverables into tasks
    • Plan iteratively (agile)
    • Check in with community and stakeholders frequently and on a schedule
    • Document everything

Kinds of Pathways

  • Functional area pathways
  • Regional pathways
  • Product specific pathways

How to Participate

Meetings

See Contribute#Joint Recognition/Pathways/Education Working Groups meeting

Discussion Forum

Pathways communicates via Discourse and the CBT discussion list #pathways

Meeting Notes

Next Meeting

Previous Meetings



Etherpads

Updated February 2014

Get Involved Details

Information about how the Get Involved page works to put contributors on to contribution pathways.

Contributor Conversion Points

In 2012, community builders decided upon a set of "conversion points" (or levels of participation) (found here) to provide information about the contributor lifecycle for the Grow Mozilla dashboard. See bug 736109 for details about implementing this and see The SuperStar Radar blog post for information about why this is helpful for community building.

Capacity

Capacity is a measure of the community building potential of pathways. Knowing the capacity of a pathway helps us provide support through programs and guides that are appropriate to their current situation. How do I determine my community's capacity?

Missions

Training missions are a scalable way to onboard new contributors to help them gain experience and develop skills that will allow them to successfully get involved in projects at Mozilla.