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

If we do this work right:

• 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
• 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
• 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
• 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
• Their work is enjoyable, they get value out of working on Mozilla projects and they become confident that their efforts are impactful and recognized
• Mission aligned contributors and leaders will effectively work with us to invent, shape and defend the internet

Current Challenges

We have a legacy to clean up: Mozilla is too messy & complicated to engage with all volunteers.

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.

Identified pain points

1. At a time of massive strategic change, boundaries between people are getting in the way of making headway
   • no layered collaboration with different audiences
2. Systems of participation do not allow us to be strategic
   • no tracking of who is doing what
3. 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
4. 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

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: #parsol Team mailing list: to be created Team vidyo room: to be created

Program docs Participation Systems – v4

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	George Roter	Bitergia -development Lucy Harris Ruben Martin Konstantina Papadea	Adam Lofting John Jensen Dominik Strohmeier Rosana Ardila	David Ascher

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 Keylly (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

Discourse Evolution

Project Wiki

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