Modules: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Mozilla operates under a [http://www.mozilla.org/hacking/module-ownership.html 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. | Mozilla operates under a [http://www.mozilla.org/hacking/module-ownership.html 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 [[Modules/Activities#Module_Ownership_System|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 [[Modules/Core|Core]], [[Modules/Activities|Activities]] and [[Modules/Other|Other]]. The controlling module is the first one listed on the page. Please contact that person about getting new modules created. | |||
=== | For Core modules, Activities (non-code) modules, or in cases of uncertainty, your enquiry should be directed to the owner and peers of the [[Modules/Activities#Module_Ownership_System|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. | These pages list the owners and their peers for all Mozilla modules, broken down by different areas of the project. | ||
Revision as of 19:50, 26 July 2011
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, Activities (non-code) modules, or in cases of uncertainty, your enquiry should be directed 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.
- 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)