canmove, Confirmed users
841
edits
Contribute/Recognition Roadmap: Difference between revisions
→2014 Priorities
| Line 47: | Line 47: | ||
What are we SHIPPING to support community members and community leaders in deepening recognition in a consistent and meaningful way? | What are we SHIPPING to support community members and community leaders in deepening recognition in a consistent and meaningful way? | ||
== Priority 1 == | == Priority 1: Visualize contribution pathways data == | ||
* Description: Create reports that measure conversion points along pathways | |||
* Goal served: Alignment around contribution stages; diagnostic tool to inform best practices | |||
* Time frame | |||
** Q3: Scope the project (what would a visualization show?) | |||
** Q4: Launch a data visualization | |||
** 2015: Move from vouching to recognition model ("testimonial")? | |||
* Stakeholders/Dependencies: | |||
** Business Intelligence resources | |||
** Pierros and the Systems & Data working group | |||
** Community Building Team | |||
** Contribution Area experts | |||
== Priority 2: Vouching for impact == | |||
* Description: Get vouching to become recognition by "vouching for impact" in 2014. Have vouch descriptions serve as recognition in addition to documenting a person's contributions. | |||
* Goal served: Support mozillians.org as a vehicle for recognition | |||
* Time frame | |||
** Q3: | |||
*** Document how to and when to write a "testimonial vouch" | |||
** Q4: | |||
*** Socialize and drive to 1/3 of new vouches are "testimonials" | |||
*** Create an opt in privacy setting around vouching so that vouches can be shared publicly | |||
* Stakeholders/Dependencies: | |||
** Community Tools team and William R | |||
** Privacy team | |||
** SUMO, MDN, and Webmaker teams for evangelism | |||
== Priority | == Priority 3: Get recognition preferences == | ||
* Description: | |||
** List of all ways we recognize contributors | |||
** Get preferences added to Mozillians.org, with visibility/privacy settings) | |||
** Allow personal opt out of any type of recognition | |||
** Share with project with goal of 25% of vouched Mozillians expressing preferences | |||
* Goal served: Support mozillians.org as a vehicle for recognition | |||
* Time frame | |||
** Q3: Create list of preferences; create requirements and designs for mozillians.org | |||
** Q4: Launch recognition preferences and get 25% adoption | |||
** 2015: Add the ways that a contributors has already been recognized? | |||
* Stakeholders/Dependencies: | |||
** Community Tools team and William R | |||
** Gear Store (Andrea) | |||
== Priority 4: Display badges on mozillians.org == | |||
* Description: Support integration of badges on Mozillians.org and support the adoption of Mozilla badges by Mozilla contributors | |||
* Goal served: | |||
** Support mozillians.org as a vehicle for recognition | |||
** Create a culture of recognition | |||
* Time frame | |||
** Q3: Design the way that badges will be displayed; create awareness and excitement about badges coming to mozillians.org profiles | |||
** Q4: Launch on mozillians.org; execute adoption efforts with a goal that 10% of vouched Mozillians have badges on their profiles | |||
* Stakeholders/Dependencies: | |||
** Badges team | |||
** Community Building team | |||
** Community Builders support for advocacy | |||
** UX designers | |||
== Priority 5: Frictionless story surfacing == | |||
* Description: Making stories on Mozillians.org easier to discover via feeds, filtering and search | |||
== Priority | * Goal served: | ||
** Support mozillians.org as a vehicle for recognition | |||
** Create a culture of recognition | |||
* Time frame | |||
** Q3: Design what surfacing looks like; define the scope; create requirements | |||
** Q4: Launch a view of surfaced stories | |||
* Stakeholders/Dependencies: | |||
** Community Tools team | |||
** Better vouches as recognition | |||
Support | |||
=Timeline= | =Timeline= | ||