Mozilla Roles and Leadership
The Mozilla project is governed by a virtual management team made up of experts from various parts of the community. Some people with leadership roles are employed to work on the Mozilla project and others are not. Leadership roles are primarily granted to individuals based on how active they are in the community, as well as the quality and nature of their contribution. This is a resilient and effective way to guide our global community. The different community leadership roles include:
Module Owners and Peers
Module owners are responsible for leading the development of a module of code or a community activity. This role requires a range of tasks, including approving patches to be checked into the module or resolving conflicts among community members. Lists of code module owners and non-code module owners are available.
Release drivers provide project management for milestone releases. The drivers provide guidance to developers as to which bug fixes are important for a given release and also make a range of tree management decisions.
Bugzilla Component OwnersBugzilla component owners are the default recipient of bugs filed against that component. Component owners are expected to review bug reports regularly, reassign bugs to correct owners, ensure test cases exist, track the progress toward resolving important fixes, and otherwise manage the bugs in the component. The Bugzilla component owner and the related module owner may be the same person, but in many cases they will be different.
Former Module Owners
When module owners and similar leaders pass on their leadership and authority to others we refer to them as Former Module Owners. This allows us to continue to acknowledge their contributions to our (collective) success -- mentoring new leadership and passing on authority to new leaders is an important part of maintaining a healthy project. "Former" status can apply to people who move to other roles within Mozilla, and to people who are no longer active in Mozilla. It is intended to be factual, not subjective or evaluative.
Reps are passionate Mozillians who mobilize and develop functional and local/regional Mozilla communities. They are committed to educate and empower people to support Mozilla’s mission and contribute to the project based on Mozilla’s leadership agreements. They are also creating collaborations with other local communities to expand Mozilla’s outreach in the open source ecosystem.
Mozilla Reps Mentors
Reps in this role provide coaching and guidance to ensure that Reps are successful in fulfilling their responsibilities.
Mozilla Reps Council
The Council is the program’s 9-member governing body composed of 2 permanently appointed Staff members and 7 elected volunteers who are serving 12-month terms. The Council exists to ensure that the Mozilla Reps program runs smoothly, oversees the governance and finances of the program and serves as an advisory body within the Mozilla organization. The Reps Council takes strategic decisions regarding the program with input by the rest of the leadership body.
Stewards are responsible for the growth and health of the community around functional and regional areas. Although everyone in Mozilla has a responsibility to help new people join the community, Stewards maintain the contribution pathways that connect potential contributors to teams that have contribution opportunities. Stewards also run recognition, education and metrics projects that keep those pathways functioning well.
The ultimate decision-maker is a trusted member of the community who has the final say in the case of disputes. This is a model followed by many successful open source projects, and they are sometimes called the "benevolent dictator". Mozilla has evolved in the past to have two people in this role, but only has one at present: Mitchell Baker. Mitchell has been in this role since 1999.