Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
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. A '''peer''' is a person whom the owner has appointed to help them. A module may have multiple | 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. | ||
===Who Appoints Whom=== | ===Who Appoints Whom=== | ||
The system is overseen by the owner and peers of the [[Modules/Activities#Module_Ownership_System|Module Ownership module]]. But in several 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 all of the 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. | |||
Owners may add and remove peers from their modules as they wish, without reference to anyone else. | |||
Questions about module ownership, or requests for changes to module ownership in Core, Activities and Other should be directed to the owner and peers of the [[Modules/Activities#Module_Ownership_System|Module Ownership module]]. | |||
Questions about module ownership or requests for changes to module ownership in | |||
===The Lists=== | ===The Lists=== | ||