ParticipationSystems: Difference between revisions

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.

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.

# 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)

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