ParticipationSystems: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (Commented out template bar thing because it's not working yet.)
 
(45 intermediate revisions by 8 users not shown)
Line 1: Line 1:
This team is part of Mozilla's [[Innovation|Open Innovation]] Team.
<!-- {{ParticipationSystems}} -->
<!-- {{ParticipationSystems}} -->


== Vision ==
== 🌅 3 Year Vision ==


This program strives to create a Mozilla that is understandable, approachable, collaborative, satisfying to work with, well managed and diverse.  
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.


If we do this work right
# 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


We will have facilitated diversity and inclusion at Mozilla. We will become a benchmark for how to harness the collective intelligence of thousands of people to achieve an ambitious vision
== 👍 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


Community participation will be a core muscle available to all parts of Mozilla. It will be well run and programs will be routinely build in participation because they will provide real value
== ✅ Strategic Objectives for Participation ==
# Enable Mozilla ID
# Deliver volunteer management systems
# Evolve collaboration systems


High value contributions will result because Mozilla is knowable and understandable, and its pursuits are compelling. People are attracted to the project, see where they can contribute and how to do so
== 🚩 Collaboration model ==
The program will be developed in close collaboration between IT and Participation.


When interacting with Mozilla, people will naturally locate themselves in the right context and altitude, and they will be able to naturally and appropriately connect with staff
# Participation and IT teams will co-design solutions
# Joint steering committee to oversee program
# Co-ownership at program and product level


Their work is enjoyable, they get value out of working on Mozilla projects and they become confident that their efforts are impactful and recognized
= Execution =


Mission aligned contributors and leaders will effectively work with us to invent, shape and defend the internet
== 👥 Who is the team? ==
'''As of Q2 2018'''


== Current Challenges ==
[[File:ParSys_Q1_2017.jpg|500px|thumb|right|Participation Systems team in early February 2017]]


We have a legacy to clean up: Mozilla is too messy & complicated to engage with all volunteers.  
* [https://mozillians.org/u/hmitsch/ Henrik Mitsch], Senior Manager Participation Systems
Our leadership is unified, but the organization and its “operating system” isn’t yet. We have vestigial walls that need to be taken down, and some new systems that need to get built.
** [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


== Identified pain points ==
== ❤️❤️ 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


# At a time of massive strategic change, boundaries between people are getting in the way of making headway
A big shout out to all the people at [[MCWS]] and [[Community Ops|Community Ops]]. You are doing an awesome job!
#* no layered collaboration with different audiences
# Systems of participation do not allow us to be strategic
#* no tracking of who is doing what
# The volunteers we need often find it unrewarding and unnecessarily difficult to contribute to Mozilla
#* current enterprise habits provide friction in interactions with non-staff
#* current practice hampers community & reduces impact
#* fragmented relationship for Mozilla and the volunteers
# Past approaches to solving this have been ad hoc across Mozilla
#* bespoke, unconnected systems for different teams and areas


== How do we plan to provide change ==
== 🙌🏼 How to get involved ==


# Generate Momentum/Create Demand
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.
#* Close collaboration with groups that want to work together, on “low hanging” or urgent projects.
#* 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


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'''


== Program goals ==
And of course we also respond to a number of Bugzilla Products/Components.
# Evolve collaboration systems
# Design and implement contributor management systems
# Evolve contributor compute infrastructure
# Enable Mozilla identity (non-LDAP)


== Who is the team ==
== 🚀 Current Projects ==
{| 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
=== 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.


Arielle Kilroy
=== Volunteer Management Systems ===
|rowspan="3" style="height:100px; text-align:center;" |Simon Wex
[[ParticipationSystems/volunteersystems|'''Project Wiki page''']]
REPS Council
|rowspan="3" style="height:100px; text-align:center;" |Katharina Borchert - CIO
Sylvie Veilleux - VP IT
 
Mark Surman - MoFo ED
 
Mitchell Baker - Executive Chair
 
|-
| style="height:100px; text-align:center;" |'''Engineering - Participation'''
Pierros Papadeas


John Giannelos (Nemo)
=== Reps Portal ===
[[ParticipationSystems/RepsPortal|'''Project Wiki page''']]


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


Nikos Roussos
[[ParticipationSystems/Particiption_Metrics|'''Old Project Wiki page''']] (Participation Metrics)
|-
| style="height:100px; text-align:center;" |'''Engineering IT'''
Corey Shields
Team to TBC
|}


Communication channels
=== Discourse 💬 ===
Irc channel: #parsol
[[ParticipationSystems/Discourse|'''Discourse''']] microsite
Team mailing list: to be created
Team vidyo room: to be created


Program docs
[[ParticipationSystems/discourse_evolution|Discourse Evolution]] project wiki page
Participation Systems – v4


 
=== Participation Infrastructure ===
== Projects ==
 
 
=== Contributor compute infrastructure plan ===
Subproject: Community website migration
Subproject: Community website migration


Project Wiki page
[[ParticipationSystems/ComputeInfrastructure|'''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;" |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 ===
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;" |George Roter
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Bitergia -development
Lucy Harris
 
Ruben Martin
 
Konstantina Papadea
| style="height:100px; text-align:center;" |Adam Lofting
 
John Jensen
 
Dominik Strohmeier
 
Rosana Ardila
| style="height:100px; text-align:center;" |David Ascher
|}
 
 
=== 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
 
|}
 
 
=== Volunteer Management Systems ===
 
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
|}


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


=== Discourse functionality ===
=== Communication & Collaboration (c24n / CoCo) Tools List ===
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;" |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"