You are currently viewing a snapshot of taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to, please file a bug.

Mozilla Roles and Responsibilities

Mozilla Community
The Mozilla community includes all those who contribute to Mozilla: writing code, testing software, writing documentation, developing web pages and applications, advocating on behalf of Mozilla, or doing any of the multitude of other things that help make Mozilla useful and successful. Some participate as individual volunteers, some through their educational institution, and others work at commercial companies. These actions ultimately determine the direction of the Mozilla project, through the contributions made and through participation in the Mozilla discussion groups and mailing lists and Internet Relay Chat channels where the day-to-day activity takes place. is the virtual organization through which the activities of the community are organized. The Mozilla organization works to make Mozilla a successful open-source project and a successful open-source product. There are a number of roles within the organization: Staff staff members provide the overall guidance for the project. This includes the development of Mozilla itself, development of a set of tools used by Mozilla contributors such as Bugzilla, maintaining a development infrastructure, building community, assisting potential new developers and creating overall policies and procedures for the project.
Drivers act as the day-to-day project managers on behalf of, focusing in particular on coordinating milestone releases.
Module Owners and Peers
A module owner is someone to whom staff delegates leadership of the development of a module of code. This includes a range of responsibilities relevant to the daily management of the module, including approving patches as ready to be checked into the module. More detail on module ownership and a list of module owners are available.
The super-reviewers are a designated group of strong hackers who review code for its effects on the overall state of the tree, use of interfaces, overall quality, API and XPCOM use, and adherence to Mozilla coding guidelines. Super-review generally follows code review by the module owner, and the approval of a super-reviewer is generally required to check code into Mozilla. More information on code review and super-review can be found in the code review FAQ.
Bugzilla Component Owners
A Bugzilla component owner is the default recipient of bugs filed against that component. When someone files a bug, he or she may specify to whom the bug will be assigned. But if no specific assignment is made by the bug reporter, the bug will go to the Bugzilla component owner. 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. In some cases the Bugzilla component owner and the related module owner may be the same person. But in many cases they will be different.
Mozilla Foundation
The Mozilla Foundation is a California not-for-profit corporation that provides organizational, legal, and financial support for the Mozilla project. Its employees have many organizational and technical roles within the Mozilla project.
Projects and Companies Using Mozilla Code
Mozilla code is used by a wide variety of open source projects and companies building commercial products. The list grows constantly. A partial list of Mozilla-based products and projects, as of July 2001 is here. Please send mail to to update this list.