ParticipationSystems: Difference between revisions
m (→Principles for Participation: added emoji) |
m (Removed Phase 1 Staffing) |
||
| Line 1: | Line 1: | ||
<!-- {{ParticipationSystems}} --> | <!-- {{ParticipationSystems}} --> | ||
== 🌅 3 Year Vision == | |||
== 🌅 Vision == | |||
By 2020, Mozillians and participants find it easy to access, understand and collaborate on Mozilla’s projects, allowing them to be effective and feel good about contributing to the mission. | By 2020, Mozillians and participants find it easy to access, understand and collaborate on Mozilla’s projects, allowing them to be effective and feel good about contributing to the mission. | ||
| Line 26: | Line 20: | ||
* By default, paid staff and volunteers should use the same platforms and tools | * By default, paid staff and volunteers should use the same platforms and tools | ||
== | == ✅ Strategic Objectives for Participation == | ||
# | # Enable Mozilla ID | ||
# Deliver volunteer management systems | |||
# Evolve collaboration systems | |||
# | |||
# | |||
== | == 🚩 Collaboration model == | ||
# | The program will be developed in close collaboration between IT and Participation. | ||
# | |||
# | # Participation and IT teams will co-design solutions | ||
# Joint steering committee to oversee program | |||
# Co-ownership at program and product level | |||
= Execution = | = Execution = | ||
| Line 56: | Line 45: | ||
|- | |- | ||
|[https://mozillians.org/u/hmitsch/ Henrik Mitsch] | |[https://mozillians.org/u/hmitsch/ Henrik Mitsch] | ||
[https://mozillians.org/en-US/u/pierros/ Pierros Papadeas] | |||
[https://mozillians.org/u/srich/ Sean Rich] | [https://mozillians.org/u/srich/ Sean Rich] | ||
[https://mozillians.org/en-US/u/jbryner/ Jeff Bryner] | |||
|[https://mozillians.org/u/geroter/ George Roter] | |[https://mozillians.org/u/geroter/ George Roter] | ||
Josh Howard | Josh Howard | ||
[https://mozillians.org | [https://mozillians.org/u/hmitsch/ Henrik Mitsch] | ||
|'''Product Management''' | |||
[https://mozillians.org/en-US/u/arielle/ Arielle Kilroy] | [https://mozillians.org/en-US/u/arielle/ Arielle Kilroy] | ||
'''Engineering - Participation''' | |||
[https://mozillians.org/en-US/u/jgiannelos/ John Giannelos (Nemo)] | [https://mozillians.org/en-US/u/jgiannelos/ John Giannelos (Nemo)] | ||
| Line 107: | Line 68: | ||
[https://mozillians.org/en-US/u/comzeradd/ Nikos Roussos] | [https://mozillians.org/en-US/u/comzeradd/ Nikos Roussos] | ||
[https://mozillians.org/en-US/u/yalam96/ Yousef Alam] | |||
[https://mozillians.org/en-US/u/ | |||
'''Engineering IT''' | |||
Team to TBC | Team to TBC | ||
|[https://mozillians.org/en-US/u/wex/ Simon Wex] | |||
TBD | |||
|[https://mozillians.org/en-US/u/Katharina/ Katharina Borchert - CIO] | |||
[https://mozillians.org/en-US/u/sveilleux/ Sylvie Veilleux - VP IT] | |||
|} | |} | ||
== 🙌🏼 How to get involved == | == 🙌🏼 How to get involved == | ||
Revision as of 14:42, 26 September 2016
🌅 3 Year Vision
By 2020, Mozillians and participants find it easy to access, understand and collaborate on Mozilla’s projects, allowing them to be effective and feel good about contributing to the mission.
- Mozilla is a great participatory organization, welcoming to staff, volunteers, and allied community alike
- Programs see the value participation brings to their efforts, and are able to build it into their processes and workflows
- Mozilla is knowable and understandable leading people to see where and how they can make high value contributions
- Our software tools continue to evolve in ways that encourage (responsible) openness and match our aspiration for being a great participatory organization
👍 Principles for Participation
- Volunteers have access to the right data, at the right time, through the right tools
- Not all volunteers need access to all data (e.g. based on data sensitivity, NDA-status, etc.), but they do need to be able to seamlessly access what they need to execute Mozilla’s mission
- Great ideas come from everywhere
- Foster creation and collaboration, whether it originates from paid staff or from our amazing community of volunteers
- Decrease inertia while protecting Mozilla’s brand
- Low barrier for entry to get started as a volunteer and use progressively higher bars for representing Mozilla’s brand
- Appropriate cost & security controls
- By default, paid staff and volunteers should use the same platforms and tools
✅ Strategic Objectives for Participation
- Enable Mozilla ID
- Deliver volunteer management systems
- Evolve collaboration systems
🚩 Collaboration model
The program will be developed in close collaboration between IT and Participation.
- Participation and IT teams will co-design solutions
- Joint steering committee to oversee program
- Co-ownership at program and product level
Execution
👥 Who is the team?
As of SEPT 2016
| Responsible | Accountable | Support | Consulted | Informed |
|---|---|---|---|---|
| Henrik Mitsch | George Roter
Josh Howard |
Product Management
Engineering - Participation Engineering IT Team to TBC |
Simon Wex
TBD |
Katharina Borchert - CIO |
🙌🏼 How to get involved
The Participation Systems initiative is a run by a cross-organization team working on discrete, finite-duration projects. Each project has its own goals and composition of engaged stakeholders. For more information on how to get involved, click on the wiki page for each project below.
For general questions and up to date information, join us via our #participationsystems (Mibbit) IRC channel and our Participation Systems category on Discourse.
🚀 Current Projects
Volunteer Management Systems
Reps Portal
Community Analytics
Discourse 💬 Evolution
Participation Infrastructure
Subproject: Community website migration