ParticipationSystems: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (Minor formatting changes)
 
(35 intermediate revisions by 7 users not shown)
Line 1: Line 1:
This team is part of Mozilla's [[Innovation|Open Innovation]] Team.
<!-- {{ParticipationSystems}} -->
<!-- {{ParticipationSystems}} -->
{{draft}}
== Vision ==
This program’s purpose is to align the software and IT systems that we use to match our aspiration for being a great participatory organization, welcoming to staff, volunteers and allied communities alike.  We want work at Mozilla to, in general, not care whether you’re an employee or not.  Our software tools need to move to match that vision, and encourage (responsible) openness.
== Current Challenges ==
We have a legacy to clean up: the systems we use at Mozilla are too messy and complicated -- this makes us less engaging and less able to strategically work across employee-volunteer-community boundaries.
Our leadership is unified in wanting Mozilla to be truly open to volunteer participation, but the organization and its “operating system” needs some tweaks. We have walls that need to be taken down, and some new systems that need to get built.


== Identified pain points ==
== 🌅 3 Year Vision ==


# The most frequent information and collaboration systems need to be accessible at least to NDA’ed volunteers (specifically, google documents/slides/etc and content that is in Mana)
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.
# We don’t have an identity system for volunteers, while we know that identity can unlock access and collaboration.  This is complex given the broader need for an identity strategy for staff that is happening in parallel.
# We have a set of useful components such as Mozillians, LDAP, etc, but they’re not yet integrated.
# Volunteers who want to manage their contributions and touch-points with Mozilla have to interact with many different of systems and processes that are inconsistent and don't relate or speak to one another. This also makes it hard for them to find/understand opportunities for participation that exist.
# We have no understanding of volunteer involvement in different areas (advocacy, coding, SuMo, innovation), and limited/fragmented tools and limited systems that allow us to manage our relationship with volunteers and help them be effective.


== How do we plan to provide change ==
# 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


# Generate Momentum/Create Demand
== 👍 Principles for Participation ==
#* Close collaboration with groups that want to work together, on “low hanging” or urgent projects.
* Volunteers have access to the right data, at the right time, through the right tools
#* When: In progress w/ IT, MoFo, Participation, CD, identifying other key parties.
** 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
# Scale to “new” areas
* Great ideas come from everywhere
#* Build on infrastructure to facilitate new pan-Mozilla projects #* that leverage participation.
** Foster creation and collaboration, whether it originates from paid staff or from our amazing community of volunteers
#* When: by EOY, ongoing
* Decrease inertia while protecting Mozilla’s brand
# Replace legacy systems
** Low barrier for entry to get started as a volunteer and use progressively higher bars for representing Mozilla’s brand
#* Identifying legacy systems for participation and migrating them.
* Appropriate cost & security controls
#* When: TBD
* By default, paid staff and volunteers should use the same platforms and tools


== Program goals ==
== ✅ Strategic Objectives for Participation ==
# Enable Mozilla ID
# Deliver volunteer management systems
# Evolve collaboration systems
# Evolve collaboration systems
# Design and implement contributor management systems
# Evolve contributor compute infrastructure
# Enable Mozilla identity (non-LDAP)
== Who is the team ==
{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
|rowspan="3" style="height:100px; text-align:center;" |George Roter
Sean Rich
|rowspan="3" style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |'''Product/Program Management'''
Hermina Condei
Lyre Calliope


Arielle Kilroy
== 🚩 Collaboration model ==
|rowspan="3" style="height:100px; text-align:center;" |Simon Wex
The program will be developed in close collaboration between IT and Participation.
REPS Council
|rowspan="3" style="height:100px; text-align:center;" |Katharina Borchert - CIO
Sylvie Veilleux - VP IT


Mark Surman - MoFo ED
# Participation and IT teams will co-design solutions
# Joint steering committee to oversee program
# Co-ownership at program and product level


Mitchell Baker - Executive Chair
= Execution =


|-
== 👥 Who is the team? ==
| style="height:100px; text-align:center;" |'''Engineering - Participation'''
'''As of Q2 2018'''
Pierros Papadeas


John Giannelos (Nemo)
[[File:ParSys_Q1_2017.jpg|500px|thumb|right|Participation Systems team in early February 2017]]


Tasos Katsoulas
* [https://mozillians.org/u/hmitsch/ Henrik Mitsch], Senior Manager Participation Systems
** [https://mozillians.org/u/arielle/ Arielle Kilroy], Senior Product Manager
** [https://mozillians.org/u/jgiannelos/ John (Nemo) Giannelos], Staff Software Engineer
** [https://mozillians.org/u/akatsoulas/ Anastasios (Tasos) Katsoulas], Senior Software Engineer
** [https://mozillians.org/u/fiji/ Florian Merz], Senior Software Engineer
** [https://mozillians.org/u/viorelaioia/ Viorela Ioia], QA Engineer
** [https://mozillians.org/u/hdv/ Hidde de Vries], Frontend Engineer
** [https://mozillians.org/u/leo/ Leo McArdle], Discourse Engineer
** [https://mozillians.org/u/m_branson/ Megan Branson], UX Designer


Nikos Roussos
== ❤️❤️ Who are our volunteer contributors? ==
|-
* [https://mozillians.org/u/cwi/ Clemens Wiesinger], consultation on project management and product strategy & design
| style="height:100px; text-align:center;" |'''Engineering IT'''
* [https://mozillians.org/u/Mte90/ Daniele Scasciafratte], contributing code to [https://reps.mozilla.org Reps] and [https://mozillians.org/ Mozillians.org]
Corey Shields
* [https://mozillians.org/u/Mermi/ Manel Rhaiem], contributing insights to [https://discourse.mozilla-community.org/t/call-for-help-community-analytics/ Mozilla Community Analytics]
Team to TBC
* [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


Communication channels
A big shout out to all the people at [[MCWS]] and [[Community Ops|Community Ops]]. You are doing an awesome job!
* IRC channel: #parsol
* Forum: Participation Systems Discourse Category (to be created)
* Team Vidyo room: (to be created)


== 🙌🏼 How to get involved ==


== Projects ==
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:
* '''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'''


=== Contributor compute infrastructure plan ===
And of course we also respond to a number of Bugzilla Products/Components.
Subproject: Community website migration


'''Project Wiki page'''
== 🚀 Current Projects ==
 
{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Pierros Papadeas
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Tanner Filip
John Giannelos (Nemo)
 
Yousef Alam
| style="height:100px; text-align:center;" |Corey Shields
| style="height:100px; text-align:center;" |David Ascher
|}
 
=== Participation Metrics - org-level dashboards and data ===
[[ParticipationSystems/Particiption_Metrics|'''Project Wiki page''']]
 
{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/geroter/ George Roter]
[https://mozillians.org/en-US/u/couci/ Konstantina Papadea]
 
[https://mozillians.org/en-US/u/pierros/ Pierros Papadeas]
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/geroter/ George Roter]
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/lucyeoh/ Lucy Harris]
[https://mozillians.org/en-US/u/nukeador/ Ruben Martin]
| style="height:100px; text-align:center;" |Adam Lofting
John Jensen
 
Rosana Ardila
 
David Ascher
 
REPS Council
| style="height:100px; text-align:center;" |Mitchell Baker
Mark Surman
 
Katharina Borchert
|}
 
=== Access for non-staff mozillians to documents and collaborative tools, Mozilla identity ===
'''Project Wiki page'''
 
{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |David Ascher
Pierros Papadeas
 
IT TBD
| style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |Hermina Condei
Josh Howard (IT)
| style="height:100px; text-align:center;" |Ryan Keylly (FxA)
Jeff Bryner (IT)
 
Josh Howard (IT)
| style="height:100px; text-align:center;" |George Roter
 
|}


=== 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 ===
'''Project Wiki page'''
[[ParticipationSystems/volunteersystems|'''Project Wiki page''']]
 
{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Arielle Kilroy
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Hermina Condei
| style="height:100px; text-align:center;" |REPS Council
MoFO
| style="height:100px; text-align:center;" |David Ascher
|}


=== Reps Portal ===
=== Reps Portal ===
[[ParticipationSystems/RepsPortal|'''Project Wiki page''']]
[[ParticipationSystems/RepsPortal|'''Project Wiki page''']]


{| class="wikitable" style="width:90%;"
=== Community Analytics ===  
! scope="col"|Responsible
[[ParticipationSystems/CommunityAnalytics|'''Community Analytics''']], Mozilla's instance of [https://bitergia.com/ Bitergia]'s [http://grimoirelab.github.io/ Grimoire Lab]
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Arielle Kilroy
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Nemo
Tasos


Youseff
[[ParticipationSystems/Particiption_Metrics|'''Old Project Wiki page''']] (Participation Metrics)


Simon Wex
=== Discourse 💬 ===
[[ParticipationSystems/Discourse|'''Discourse''']] microsite


Sean Rich
[[ParticipationSystems/discourse_evolution|Discourse Evolution]] project wiki page


More TBD
=== Participation Infrastructure ===
| style="height:100px; text-align:center;" |Pierros
Subproject: Community website migration
George
 
Rosana
 
Ruben
 
Konstantina
 
Guillermo
 
Hannah Kane


Lucy Harris
[[ParticipationSystems/ComputeInfrastructure|'''Project Wiki page''']]
| style="height:100px; text-align:center;" |David Ascher


|}
=== Access for non-staff Mozillians to documents and collaborative tools, Mozilla identity ===
[[ParticipationSystems/Volunteer Identity and Document Access|'''Project Wiki page''']]


=== Discourse Evolution ===
=== Communication & Collaboration (c24n / CoCo) Tools List ===
[[ParticipationSystems/discourse_evolution|'''Project Wiki page''']]
[[ParticipationSystems/CoCo_Tools_List|'''FLOSS CoCo List''']]


{| class="wikitable" style="width:90%;"
=== ParSys Turing Days ===
! scope="col"|Responsible
ParSys [[ParticipationSystems/TuringDay|'''Turing Day''']] microsite
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Lyre Calliope
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Hermina Condei
| style="height:100px; text-align:center;" |Community Ops
REPS Council
| style="height:100px; text-align:center;" |David Ascher
|}

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"