Bugzilla:Owners

Module Owners

What is a module owner?

In order to speed up development on Bugzilla, distinct modules are created and each module has an owner based on his expertise in this specific field. Outside freezing periods (i.e. outside periods preceding a release) and on the trunk only, module owners do not require reviews to land their own patches in their specific module. They are also able to commit reviewed patches from other developers in their specific fields without requesting approval first.

On branches as well as during freezing periods, reviews and approvals are mandatory in all cases.

Components and owners

Here is the list of modules for Bugzilla, sorted alphabetically, and the name of their owners and peers.

Module	Description	Owner	Peers
Administration	Pages related to the administration of a Bugzilla installation, features oriented.
Attachments, Flags and Requests	Flag system, attachment creation and management
Authentication	Authentication API, communication and interactions between Bugzilla installations
Bug creation and modification	Creating, changing, and viewing bugs
Charting system	Old and new chart systems
Databases	Interface with databases, database support
Documentation	Bugzilla documentation
Email notifications	Emails sent during bug changes, including flags
Exporting and Importing	Importing and exporting data with another Bugzilla installation, including bugs and user profiles
Installation and Upgrading	Installing a fresh copy of Bugzilla, or upgrading from an older installation
Search system and Queries	Mostly include Search.pm code and the way data are passed to it and returned
Security (?)	Security related stuff
User Interface	Design of Bugzilla pages, as well as workflow