ParticipationSystems

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

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

1. 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)
2. 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.
3. We have a set of useful components such as Mozillians, LDAP, etc, but they’re not yet integrated.
4. 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.
5. 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

1. Generate Momentum/Create Demand
   • 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.
2. Scale to “new” areas
   • Build on infrastructure to facilitate new pan-Mozilla projects #* that leverage participation.
   • When: by EOY, ongoing
3. Replace legacy systems
   • Identifying legacy systems for participation and migrating them.
   • When: TBD

Program goals

1. Evolve collaboration systems
2. Design and implement contributor management systems
3. Evolve contributor compute infrastructure
4. Enable Mozilla identity (non-LDAP)

Who is the team

Responsible	Accountable	Support	Consulted	Informed
George Roter Sean Rich	David Ascher	Product/Program Management Hermina Condei Lyre Calliope Arielle Kilroy	Simon Wex REPS Council	Katharina Borchert - CIO Sylvie Veilleux - VP IT Mark Surman - MoFo ED Mitchell Baker - Executive Chair
		Engineering - Participation Pierros Papadeas John Giannelos (Nemo) Tasos Katsoulas Nikos Roussos
		Engineering IT Corey Shields Team to TBC

Communication channels

• IRC channel: #participationsystems (Mibbit)
• Forum: Participation Systems Discourse Category

• Team Vidyo room: (to be created)

Projects

Contributor compute infrastructure plan

Subproject: Community website migration

Project Wiki page

Responsible	Accountable	Support	Consulted	Informed
Pierros Papadeas	George Roter	Tanner Filip John Giannelos (Nemo) Yousef Alam	Corey Shields	David Ascher

Participation Metrics - org-level dashboards and data

Project Wiki page

Responsible	Accountable	Support	Consulted	Informed
George Roter Konstantina Papadea Pierros Papadeas	George Roter	Lucy Harris Ruben Martin	Adam Lofting John Jensen Rosana Ardila David Ascher REPS Council	Mitchell Baker Mark Surman Katharina Borchert

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

Project Wiki page

Responsible	Accountable	Support	Consulted	Informed
David Ascher Pierros Papadeas IT TBD	David Ascher	Hermina Condei Josh Howard (IT)	Ryan Kelly (FxA) Jeff Bryner (IT) Josh Howard (IT)	George Roter

Volunteer Management Systems

Project Wiki page

Responsible	Accountable	Support	Consulted	Informed
Arielle Kilroy	George Roter	Hermina Condei	REPS Council MoFO	David Ascher

Reps Portal

Project Wiki page

Responsible	Accountable	Support	Consulted	Informed
Arielle Kilroy	George Roter	Nemo Tasos Youseff Simon Wex Sean Rich More TBD	Pierros George Rosana Ruben Konstantina Guillermo Hannah Kane Lucy Harris	David Ascher

Discourse Evolution

Project Wiki page

Responsible	Accountable	Support	Consulted	Informed
Lyre Calliope	George Roter	Hermina Condei	Community Ops REPS Council	David Ascher