Modules

Mozilla operates under a module ownership governance system. A module is a discrete unit of code or activity. An owner is the person in charge of a module or sub-module. A peer is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.

The system is overseen by the owner and peers of the Module Ownership module. Owners may add and remove peers from their modules as they wish, without reference to anyone else.

Creating A New Module

Ideally, a Module should exist for all significant chunks of work or code in the Mozilla project. Who you talk to about this depends on the area of the project concerned.

For many areas, the ability to create, alter ownership of and destroy sub-modules has been delegated to the owner of the module whose broad scope covers that area. This is true for Firefox, Thunderbird, and all of the other areas listed below except for Core, Activities and Other. The controlling module is the first one listed on the page. Please contact that person about getting new modules created.

For Core modules and Activities (non-code) modules, please post your enquiry in the mozilla.governance newsgroup, CCing the owner and peers of the Module Ownership module. If there is something sensitive about your enquiry that you aren't comfortable writing in the newsgroup, or in case of uncertainty, please send it to the owner and peers of the Module Ownership module.

Module Lists

These pages list the owners and their peers for all Mozilla modules, broken down by different areas of the project.

• All in one big list

• Firefox
• Thunderbird
• SeaMonkey
• Calendar
• Boot2Gecko

• Toolkit
• Core
• MailNews Core

• Bugzilla - the Bugzilla software itself
• bugzilla.mozilla.org - the particular Bugzilla installation run by the Mozilla project
• Other (code modules which aren't in any of the above categories)
• Activities (non-code)