For the Good of the Code
An introduction to the inner workings of the Mozilla Project
When Netscape established the Mozilla Project in 1998, they also formed mozilla.org (the virtual Mozilla Organization), headed by an independent staff@mozilla.org (Mozilla Staff), to guide the project. Jamie Zawinski drafted a mission statement for mozilla.org that laid out the module ownership model and meritocratic principles that form the basis of the project's leadership structure even today. Chief Lizard Wrangler Mitchel Baker later wrote an overview of the Mozilla Project and mozilla.org to further clarify the interaction of the Mozilla Organization, Mozilla Staff, and the Mozilla Community.
Leadership within the Mozilla Project is based on merit: the more worthy your contributions, the more respect you get. Formal authority in the project derives from staff@mozilla.org, who are ultimately responsible for stewarding the Mozilla source code, and is delegated to contributors who fill official roles in the Mozilla Organization. Internal conflicts and other leadership problems are (or should be) directed to staff@mozilla.org for resolution. Roles within the organization are not tied to any employment requirements and all Mozilla contributors are subject to the same rules and review requirements. As jwz points out, corporate employees must remember to wear their Mozilla Organization hat, not their corporate hat, when making decisions under their Mozilla Organization role.
The Mozilla Project welcomes contributors of every background and skill level. Our development communication channels are open to everyone. Eeep in mind that the more involved contributors in the Mozilla Project tend to be extremely busy and overworked, so it may take a long time to get a response from them. If you're asking a question or requesting review, be persistent (sometimes people forget to respond and need a reminder), but be patient, too.