Innovation/Projects/Mission-Driven Mozillians Strategy: Difference between revisions
No edit summary |
|||
| Line 34: | Line 34: | ||
The strategy is generated through a series of discussions with members of Mozilla communities. | The strategy is generated through a series of discussions with members of Mozilla communities. | ||
Both proposal & strategy will be based around the following | Both proposal & strategy will be based around the following 10 topic areas: | ||
* '''Regional/local/geographic identities''': Approach, formation, visibility | * '''Regional/local/geographic identities''': Approach, formation, visibility | ||
| Line 40: | Line 40: | ||
* '''Metrics''': How do we measure activity across all areas? | * '''Metrics''': How do we measure activity across all areas? | ||
* '''Accountability''': What are the expectations around accountability in different volunteer and staff roles? | * '''Accountability''': What are the expectations around accountability in different volunteer and staff roles? | ||
* '''Volunteer Leadership''': How do we approach leadership roles? | * '''Volunteer Leadership''': How do we approach leadership roles & structures? | ||
* '''Resource Distribution''': How do we make access to resources (funding, swag, training) fair and transparent? | |||
* '''Recognition''': What’s our strategy for recognizing and motivating contributors? | * '''Recognition''': What’s our strategy for recognizing and motivating contributors? | ||
* '''Systems - tools & Comms''': What’s the strategy around the tools that enable contributions? How do we communicate with volunteers? | * '''Systems - tools & Comms''': What’s the strategy around the tools that enable contributions? How do we communicate with volunteers? | ||
* ''' | * '''Contribution Journey''': How do we welcome people to the Mozilla community? how do we surface, present and decide on opportunities to contribute? | ||
* '''Staff Support''': What’s our strategy around community-facing staff and workflows? | * '''Staff Support''': What’s our strategy around community-facing staff and workflows? | ||
=== Timeline === | === Timeline === | ||
Revision as of 22:25, 27 November 2017
What is the Mission-Driven Mozillians strategy project?
This project, driven by the Community Development Team, aims at catalyzing a Mozilla-wide decision and strategy for where and how we invest in our Mission-Driven Mozillians communities.
If you are interested in getting updates about this project, please subscribe to the mission-mozillians tag on discourse.
Background
This project is based on the Open Innovation strategy research project, and informed by the D&I community research, as well as additional interviews & research with key staff members and volunteers.
This project was formerly known as "Non-coding Enthusiast communities and contributors".
Who’s Involved
The project is being driven by - Lucy Harris & Ruben Martin (with support from George Roter)
The decision-maker is - George Roter
Agreement is to be sought from - Katharina Borchert, Patrick Finch, Chris Beard, Mitchell Baker and the Reps Module Owner
Input & Consultation- Reps Council + Peers , Reps Community Managers, SUMO Community Managers + key volunteers, L10N Community Managers + key volunteers, Haiyya, D&I Staff, Mozilla Foundation Staff.
Approach
The approach is to generate two documents
- A proposal that clearly outlines the impact of Mission-Driven Mozillians communities and proposes an a cohesive approach to investment to Mozilla Leadership
- A strategy and roadmap for implementing structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.
The proposal is generated by the input group and shared with decision makers for feedback.
The strategy is generated through a series of discussions with members of Mozilla communities.
Both proposal & strategy will be based around the following 10 topic areas:
- Regional/local/geographic identities: Approach, formation, visibility
- Diversity and Inclusion: How do we ensure D&I across everything we do?
- Metrics: How do we measure activity across all areas?
- Accountability: What are the expectations around accountability in different volunteer and staff roles?
- Volunteer Leadership: How do we approach leadership roles & structures?
- Resource Distribution: How do we make access to resources (funding, swag, training) fair and transparent?
- Recognition: What’s our strategy for recognizing and motivating contributors?
- Systems - tools & Comms: What’s the strategy around the tools that enable contributions? How do we communicate with volunteers?
- Contribution Journey: How do we welcome people to the Mozilla community? how do we surface, present and decide on opportunities to contribute?
- Staff Support: What’s our strategy around community-facing staff and workflows?
Timeline
- Q3, 2017 - Work with input group to create initial proposal
- Q4, 2017 - Leadership input to proposal & framing for initial implementation conversations (topic 1: volunteer leadership)
- Q1, 2018 - Additional implementation conversations, roadmap generation and early infrastructure and framework creation.
Stay Connected
If you are interested in getting updates about this project, please subscribe to the mission-mozillians tag on discourse.