Contribute/Lifecycle: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
Using a series of pilots, we determined that each phase of community involvement can be linked to a lifecycle. Drawing from our pilot projects, in which we developed working groups to do specific tasks to build a stronger community, we identified the contributor lifecycle, a series of processes that walk participants through contribution.
{{draft}}
__NOTOC__
<section begin=summary />{{ContributeSummary
|icon= Logo_0002_68.png‎ |64 px
|pagelocation=Contribute_choose_your_own_adventure
|pagetitle=Contribute Wiki
|updated=Frequently
|owner=[[Contribute/Team|Community Building Team]]
|description= Whether you've been building a community for a long time or you are just getting started, these pages will help you find the information you are looking for to build vibrant, supportive communities that will have impact on your project.  
}}<section end=summary />


*[[Contribute/Pilots| Read more about contribution pilots here]]
This document seeks to define the process by which a Mozilla team becomes a community contribution area. The process is broken down into phases which, in our experience, communities go through as they develop, and includes milestones and resources for growing and supporting Mozilla communities. We expect that each client group (team?) will come to us at different phases of the lifecycle.  We will support each of them based our assessment of where in the lifecycle they are, and what structure and framework will help them reach the highest potential for contribution.
*[[contribute/lifecycle/contacts| Get in touch with people building community at every stage]]
Each phase of the lifecycle is designed to meet the client at their point of need and to provide a framework on which they can build.


=Starting=
In the community building context, an “Activator” is a dedicated community building resource from the team. This person’s work shifts in each phase of the lifecycle.


* '''Problem:''' Your project doesn't have volunteers yet and you're interested in building a community around what you're doing.
[[Contribute/Lifecycle/contribution_by_area| The stages can also be separated by functional area.]]
For explanations of the terms used in this document, please add to and draw from [[Lexicon:All| the Mozilla lexicon]]


* '''Who:''' Your project doesn't have volunteers yet and you're interested in building a community around what you're doing.
{| class="wikitable"
|-
!  !! Definition !! Measure of Success
|-
|bgcolor="orange"|[[Contribute/Lifecycle/pre_work|'''Pre-work''']] || In this stage teams are completely unfamiliar with working with contributors, do not understand the value of doing so, and have significant concerns or roadblocks to beginning the process. || We will know that the client is ready to move to the next phase when a dedicated staff resource  has been appointed to work with us. This person is known as the community coordinator or activator.
|-
|bgcolor="gray"|[[Contribute/Lifecycle/starting | '''Starting''']] || At this stage clients don't have volunteers yet and they are committed in building a community around what they are doing.  || Documented pathway with people to manage incoming contributors must be built for a partnership in this phase to be considered a success.
|-
|bgcolor="Bisque"|[[Contribute/Lifecycle/learning_and_preparing_for_growth| '''Learning and preparing for growth''']] || Clients at this stage  have connected with some volunteers and are interested in learning about how to build on what is working and laying the groundwork for scaling.  || New contributors ( roughly more than 25)  must be moving into/through the pathway and getting connected to opportunities
|-
|bgcolor="Ash grey"|[[Contribute/Lifecycle/scaling| '''Scaling''']] || Clients have volunteers involved in their project and they'd like to turn up the dial on participation. Teams in this stage, having a few core contributors and many active contributors, are ready to  steward their communities through on-going, significant growth. || Teams have established ways to sustain momentum (mentoring new contributors, developing leadership, etc.) and have demonstrated a 10x increase in active contributors. [I really want something in here about measuring leadership.]
(This stage is the minimum target for all high leverage partnerships.)
|-
|bgcolor="Asparagus"|[[Contribute/Lifecycle/sustaining| '''Sustaining''']] || At this stage community active and stable and is interested in keeping that momentum growing and retaining  key contributors.


* '''What:''' A checklist of things to be thinking/doing when you're here (watch this workshop video, fill out this template, etc).
stable and adapting
 
|| Teams will have optimized their pathways based on data and we will see contribution jump again (and we will have created a case study of the team).
* '''How:''' See how other people have approached this: David S from Firefox OS engineering, person interested in forming a local community in Australia, etc.
 
Ideal contribution jump metric is currently undefined, and will be determined by what is happening in ""scaling.""
* '''Checklist:'''
|}
** Read [[Mozilla.org/Contribute/Stories|stories from existing Mozillians about how they first got involved]] with the project as volunteers
** Watch the [[Contribute/Workshops/Designing_for_participation|Designing for participation workshop video]] (soon to be reshot into a more watchable series of short videos)
** Join the [[Grow/Meetings|Grow Mozilla call]] and introduce yourself and meet other people involved with bringing people in to their projects.
 
=Learning=
 
* '''Problem:'''
** You have connected with some volunteers and you're interested in learning about how to build on what's working so more people can join.
** Volunteers are coming to you and you are not sure how to mobilize them effectively
 
* '''Who:'''
** You're in charge of community management/engagement for your group.
** You're the person volunteers always seem to come to.
 
* '''What:''' A checklist of things to be thinking/doing when you're here (watch this workshop video, etc).
 
* '''How:''' See how other people have approached this: Ben S from WebProd, etc.
 
* '''Checklist:'''
** Read Margaret's great [http://blog.margaretleibovic.com/post/57564605991/increasing-volunteer-participation-on-the-firefox-for blog post about increasing participation on the Firefox for Android team] that has 5 helpful tips in it
** Check out the [https://badges.mozilla.org/en-US/badges/awards recently awarded Mozilla badges] to get an idea of how some teams are recognizing contributors.
** Watch a couple of these [[Contribute/Videos|videos that have been created by community builders]] for people interested in community building.
 
=Scaling=
 
* '''Who:''' You have volunteers involved in your project and you'd like to turn up the dial on participation.
 
* '''What:''' A checklist of things to be thinking/doing when you're here (watch this workshop video, etc).
 
* '''How:''' See how other people have approached this: Matej from Creative, etc.
 
* '''Checklist:'''
** Create a [[Contribute/Dashboards|contribution dashboard]] to give you insight about where you can improve the experience for volunteers
** Contact the [[Badges|Open Badges team]] and start a discussion about creating badges for your contributors
** Get involved in a [[Contribute/Working_Groups|community building working group]] to help shape the infrastructure for participation at Mozilla
 
=Sustaining=
 
* '''Who:''' You have a healthy and active community and you're interested in keeping that momentum and retaining your key contributors.
 
* '''What:''' A checklist of things to be thinking/doing when you're here (watch this workshop video, etc).
 
* '''How:''' See how other people have approached this: Rosana and Madalina from SUMO, etc.
 
* '''Checklist:'''
** Module ownership / responsibility
 
[[Category:Contribute]]

Revision as of 04:02, 3 May 2014

Draft-template-image.png THIS PAGE IS A WORKING DRAFT Pencil-emoji U270F-gray.png
The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly.
If you have any questions or ideas, please add them as a new topic on the discussion page.
Logo 0002 68.png Contribute Wiki
Owner: Community Building Team Updated: Frequently
Whether you've been building a community for a long time or you are just getting started, these pages will help you find the information you are looking for to build vibrant, supportive communities that will have impact on your project.

This document seeks to define the process by which a Mozilla team becomes a community contribution area. The process is broken down into phases which, in our experience, communities go through as they develop, and includes milestones and resources for growing and supporting Mozilla communities. We expect that each client group (team?) will come to us at different phases of the lifecycle. We will support each of them based our assessment of where in the lifecycle they are, and what structure and framework will help them reach the highest potential for contribution.

Each phase of the lifecycle is designed to meet the client at their point of need and to provide a framework on which they can build.

In the community building context, an “Activator” is a dedicated community building resource from the team. This person’s work shifts in each phase of the lifecycle.

The stages can also be separated by functional area. For explanations of the terms used in this document, please add to and draw from the Mozilla lexicon

Definition Measure of Success
Pre-work In this stage teams are completely unfamiliar with working with contributors, do not understand the value of doing so, and have significant concerns or roadblocks to beginning the process. We will know that the client is ready to move to the next phase when a dedicated staff resource has been appointed to work with us. This person is known as the community coordinator or activator.
Starting At this stage clients don't have volunteers yet and they are committed in building a community around what they are doing. Documented pathway with people to manage incoming contributors must be built for a partnership in this phase to be considered a success.
Learning and preparing for growth Clients at this stage have connected with some volunteers and are interested in learning about how to build on what is working and laying the groundwork for scaling. New contributors ( roughly more than 25) must be moving into/through the pathway and getting connected to opportunities
Scaling Clients have volunteers involved in their project and they'd like to turn up the dial on participation. Teams in this stage, having a few core contributors and many active contributors, are ready to steward their communities through on-going, significant growth. Teams have established ways to sustain momentum (mentoring new contributors, developing leadership, etc.) and have demonstrated a 10x increase in active contributors. [I really want something in here about measuring leadership.]

(This stage is the minimum target for all high leverage partnerships.)

Sustaining At this stage community active and stable and is interested in keeping that momentum growing and retaining key contributors.

stable and adapting

Teams will have optimized their pathways based on data and we will see contribution jump again (and we will have created a case study of the team).

Ideal contribution jump metric is currently undefined, and will be determined by what is happening in ""scaling.""

Retrieved from "https://wiki.mozilla.org/index.php?title=Contribute/Lifecycle&oldid=972672"