ParticipationSystems: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (→‎👥 Who is the team?: Updates to represent current realities.)
 
(21 intermediate revisions by the same user not shown)
Line 1: Line 1:
This team is part of Mozilla's [[Innovation|Open Innovation]] Team.
<!-- {{ParticipationSystems}} -->
<!-- {{ParticipationSystems}} -->


= Overview =
== 🌅 3 Year Vision ==
The purpose of the Participation Systems initiative is to force multiply Mozilla’s capacity to deliver our ambitious mission by aligning software and IT systems that enable staff, volunteers, and allied communities to work together in radically participatory ways.


== 🌍 Background ==
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.
While our leadership is unified in wanting Mozilla to be truly open to volunteer participation, our current organizational “operating system” makes it difficult to work strategically across employee-volunteer-community boundaries. The legacy systems we use are messy and complicated encouraging collaborative workflows that lack engagement and creating barriers to volunteer participation. We have walls that need to be taken down, and new systems that need to be built.


== 🌅 Vision ==
# 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


# Mozilla is a radically participatory organization, welcoming to staff, volunteers, and allied community alike.  
== 👍 Principles for Participation ==
# Programs see the value participation brings to their efforts, and are able to build it into their processes and workflows.
* Volunteers have access to the right data, at the right time, through the right tools
# Mozilla is knowable and understandable leading people to see where and how they can make high value contributions.
** 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
# Our software tools continue to evolve in ways that encourage (responsible) openness and match our aspiration for being a radically participatory organization.
* 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


== 😠 Identified Pain Points ==  
== ✅ Strategic Objectives for Participation ==
# Enable Mozilla ID
# Deliver volunteer management systems
# Evolve collaboration systems


# Protected resources within frequently used information and collaboration systems are not accessible to NDA’ed volunteers (specifically, google documents/slides/etc and some of the content that is currently in Mana)
== 🚩 Collaboration model ==
# We lack an identity system for volunteers that would unlock access and collaborative capacities. This is complex given the broader need for an identity strategy for staff that is happening in parallel.
The program will be developed in close collaboration between IT and Participation.
# It is difficult for volunteers to manage their contributions and touch-points with Mozilla, or even find/understand opportunities for participation that exist due to inconsistent systems and processes that don’t relate or speak to one another.
# We have a set of useful components such as Mozillians.org, LDAP, etc, but they’re not yet integrated.
# We lack understanding of volunteer involvement in different areas (advocacy, coding, SuMo, innovation), and are unable to manage our relationship with volunteers and help them be effective because of fragmented tools and limited systems.


== 🚩 Organizational Change Strategy ==
# Participation and IT teams will co-design solutions
# Generate Momentum/Create Demand
# Joint steering committee to oversee program
#* Close collaboration with groups that want to work together.
# Co-ownership at program and product level
#* When: In progress w/ IT, MoFo, Participation, CD, identifying other key parties.
# Scale to “new” areas
#* Build on infrastructure to facilitate new pan-Mozilla projects that leverage participation.
#* When: by EOY, ongoing
# Replace legacy systems
#* Identifying legacy systems for participation and migrating them.
#* When: TBD
 
== ✅ Program Goals ==
# Enable Mozilla identity (non-LDAP)
# Design and implement volunteer management systems
# Evolve collaboration and communication systems
# Evolve participation infrastructure


= Execution =
= Execution =


== 👥 Who is the team? ==
== 👥 Who is the team? ==
'''As of SEPT 2016'''
'''As of Q2 2018'''
 
{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
|[https://mozillians.org/u/hmitsch/ Henrik Mitsch]
 
[https://mozillians.org/u/srich/ Sean Rich]
|[https://mozillians.org/u/geroter/ George Roter]
 
Josh Howard
|'''Product/Program Management'''
[https://mozillians.org/en-US/u/pierros/ Pierros Papadeas]
 
[https://mozillians.org/en-US/u/arielle/ Arielle Kilroy]
|[https://mozillians.org/en-US/u/wex/ Simon Wex]


'''TBD'''
[[File:ParSys_Q1_2017.jpg|500px|thumb|right|Participation Systems team in early February 2017]]
|[https://mozillians.org/en-US/u/Katharina/ Katharina Borchert - CIO]
[https://mozillians.org/en-US/u/sveilleux/ Sylvie Veilleux - VP IT]
|}


'''Phase 1 (until mid-AUG 2016)'''
* [https://mozillians.org/u/hmitsch/ Henrik Mitsch], Senior Manager Participation Systems
{| class="wikitable" style="width:90%;"
** [https://mozillians.org/u/arielle/ Arielle Kilroy], Senior Product Manager
! scope="col"|Responsible
** [https://mozillians.org/u/jgiannelos/ John (Nemo) Giannelos], Staff Software Engineer
! scope="col"|Accountable
** [https://mozillians.org/u/akatsoulas/ Anastasios (Tasos) Katsoulas], Senior Software Engineer
! scope="col"|Support
** [https://mozillians.org/u/fiji/ Florian Merz], Senior Software Engineer
! scope="col"|Consulted
** [https://mozillians.org/u/viorelaioia/ Viorela Ioia], QA Engineer
! scope="col"|Informed
** [https://mozillians.org/u/hdv/ Hidde de Vries], Frontend Engineer
|-
** [https://mozillians.org/u/leo/ Leo McArdle], Discourse Engineer
|rowspan="3" style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/geroter/ George Roter]
** [https://mozillians.org/u/m_branson/ Megan Branson], UX Designer
[https://mozillians.org/en-US/u/srich/ Sean Rich]
|rowspan="3" style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/davida/ David Ascher]
| style="height:100px; text-align:center;" |'''Product/Program Management'''
[https://mozillians.org/en-US/u/Hermina/ Hermina Condei]


[https://mozillians.org/en-US/u/CaptainCalliope/ Lyre Calliope]
== ❤️❤️ Who are our volunteer contributors? ==
* [https://mozillians.org/u/cwi/ Clemens Wiesinger], consultation on project management and product strategy & design
* [https://mozillians.org/u/Mte90/ Daniele Scasciafratte], contributing code to [https://reps.mozilla.org Reps] and [https://mozillians.org/ Mozillians.org]
* [https://mozillians.org/u/Mermi/ Manel Rhaiem], contributing insights to [https://discourse.mozilla-community.org/t/call-for-help-community-analytics/ Mozilla Community Analytics]
* [https://mozillians.org/u/buluma_michael/ Michael Buluma], [[ParticipationSystems/ComputeInfrastructure|Participation Systems Infrastructure]] engineering, [[ParticipationSystems/Discourse|Discourse]] administration
* [https://mozillians.org/u/mkohler/ Michael Kohler], contributing code to [https://reps.mozilla.org Reps] and [https://mozillians.org/ Mozillians.org], data mining [https://discourse.mozilla-community.org/t/call-for-help-community-analytics/ Mozilla Community Analytics], frequent consultation on various matters
* [https://mozillians.org/u/KaiRo/ Robert Kaiser], consultation on project management
* [https://mozillians.org/u/IoanaChiorean/ Stefania Ioana Chiorean], consultation on various matters
* [https://mozillians.org/u/tanner/ Tanner Filip], [[ParticipationSystems/ComputeInfrastructure|Participation Systems Infrastructure]] engineering, [[ParticipationSystems/Discourse|Discourse]] administration
* [https://mozillians.org/u/Ryuno-Ki/ André Jaenisch], filing bugs and always being a helping hand on #participationsystems


[https://mozillians.org/en-US/u/arielle/ Arielle Kilroy]
A big shout out to all the people at [[MCWS]] and [[Community Ops|Community Ops]]. You are doing an awesome job!
|rowspan="3" style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/wex/ Simon Wex]
[https://wiki.mozilla.org/ReMo/Council REPS Council]
|rowspan="3" style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/Katharina/ Katharina Borchert - CIO]
[https://mozillians.org/en-US/u/sveilleux/ Sylvie Veilleux - VP IT]
 
[https://mozillians.org/en-US/u/surman/ Mark Surman - MoFo ED]
 
[https://mozillians.org/en-US/u/mitchell/ Mitchell Baker - Executive Chair]
 
|-
| style="height:100px; text-align:center;" |'''Engineering - Participation'''
[https://mozillians.org/en-US/u/pierros/ Pierros Papadeas]
 
[https://mozillians.org/en-US/u/jgiannelos/ John Giannelos (Nemo)]
 
[https://mozillians.org/en-US/u/akatsoulas/ Tasos Katsoulas]
 
[https://mozillians.org/en-US/u/comzeradd/ Nikos Roussos]
|-
| style="height:100px; text-align:center;" |'''Engineering IT'''
[https://mozillians.org/en-US/u/cshields/ Corey Shields]
 
Team to TBC
|}


== 🙌🏼 How to get involved ==
== 🙌🏼 How to get involved ==
Line 114: Line 68:
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.
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 [irc://irc.mozilla.org/%23participationsystems #participationsystems] ([http://chat.mibbit.com/?channel=%23participationsystems&server=irc.mozilla.org Mibbit]) IRC channel and our [https://discourse.mozilla-community.org/c/participationsystems Participation Systems category] on Discourse.
For general questions, urgent support requests or the casual chat, join us on:
* '''IRC''' channel [irc://irc.mozilla.org/%23participationsystems #participationsystems] ([http://chat.mibbit.com/?channel=%23participationsystems&server=irc.mozilla.org Mibbit])
* the [https://discourse.mozilla-community.org/c/participationsystems Participation Systems category] on '''Discourse'''
** '''Mozillians.org''' [https://discourse.mozilla-community.org/t/mozillians-org-frontend-triaging-mentored-bugs/13155 Mentored bugs]
* the [https://telegram.me/participationsystems participationsystems channel] on '''Telegram'''
 
And of course we also respond to a number of Bugzilla Products/Components.


== 🚀 Current Projects ==
== 🚀 Current Projects ==
=== Fireside Chat (SEPT 2016) ===
During a [https://air.mozilla.org/mozilla-weekly-project-meeting-20160926/#@11m35s Fireside Chat on Air Mozilla] in September 2016 [https://mozillians.org/u/geroter/ George Roter] (Head of Participation) and [https://mozillians.org/u/jrh/ Josh Howard] (Enterprise Architect) had a conversation on the strategic goals of the Volunteer Management Systems (VMS) initiative.


=== Volunteer Management Systems ===
=== Volunteer Management Systems ===
Line 125: Line 88:


=== Community Analytics ===  
=== Community Analytics ===  
[[ParticipationSystems/Particiption_Metrics|'''Project Wiki page''']]
[[ParticipationSystems/CommunityAnalytics|'''Community Analytics''']], Mozilla's instance of [https://bitergia.com/ Bitergia]'s [http://grimoirelab.github.io/ Grimoire Lab]


=== Discourse 💬 Evolution ===
[[ParticipationSystems/Particiption_Metrics|'''Old Project Wiki page''']] (Participation Metrics)
[[ParticipationSystems/discourse_evolution|'''Project Wiki page''']]
 
=== Discourse 💬 ===
[[ParticipationSystems/Discourse|'''Discourse''']] microsite
 
[[ParticipationSystems/discourse_evolution|Discourse Evolution]] project wiki page


=== Participation Infrastructure ===
=== Participation Infrastructure ===
Line 137: Line 104:
=== Access for non-staff Mozillians to documents and collaborative tools, Mozilla identity ===
=== Access for non-staff Mozillians to documents and collaborative tools, Mozilla identity ===
[[ParticipationSystems/Volunteer Identity and Document Access|'''Project Wiki page''']]
[[ParticipationSystems/Volunteer Identity and Document Access|'''Project Wiki page''']]
=== Communication & Collaboration (c24n / CoCo) Tools List ===
[[ParticipationSystems/CoCo_Tools_List|'''FLOSS CoCo List''']]
=== ParSys Turing Days ===
ParSys [[ParticipationSystems/TuringDay|'''Turing Day''']] microsite

Latest revision as of 21:01, 14 April 2018

This team is part of Mozilla's Open Innovation Team.


🌅 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.

  1. Mozilla is a great participatory organization, welcoming to staff, volunteers, and allied community alike
  2. Programs see the value participation brings to their efforts, and are able to build it into their processes and workflows
  3. Mozilla is knowable and understandable leading people to see where and how they can make high value contributions
  4. 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

  1. Enable Mozilla ID
  2. Deliver volunteer management systems
  3. Evolve collaboration systems

🚩 Collaboration model

The program will be developed in close collaboration between IT and Participation.

  1. Participation and IT teams will co-design solutions
  2. Joint steering committee to oversee program
  3. Co-ownership at program and product level

Execution

👥 Who is the team?

As of Q2 2018

Participation Systems team in early February 2017

❤️❤️ Who are our volunteer contributors?

A big shout out to all the people at MCWS and Community Ops. You are doing an awesome job!

🙌🏼 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, urgent support requests or the casual chat, join us on:

And of course we also respond to a number of Bugzilla Products/Components.

🚀 Current Projects

Fireside Chat (SEPT 2016)

During a Fireside Chat on Air Mozilla in September 2016 George Roter (Head of Participation) and Josh Howard (Enterprise Architect) had a conversation on the strategic goals of the Volunteer Management Systems (VMS) initiative.

Volunteer Management Systems

Project Wiki page

Reps Portal

Project Wiki page

Community Analytics

Community Analytics, Mozilla's instance of Bitergia's Grimoire Lab

Old Project Wiki page (Participation Metrics)

Discourse 💬

Discourse microsite

Discourse Evolution project wiki page

Participation Infrastructure

Subproject: Community website migration

Project Wiki page

Access for non-staff Mozillians to documents and collaborative tools, Mozilla identity

Project Wiki page

Communication & Collaboration (c24n / CoCo) Tools List

FLOSS CoCo List

ParSys Turing Days

ParSys Turing Day microsite

Retrieved from "https://wiki.mozilla.org/index.php?title=ParticipationSystems&oldid=1192342"