Modules and Module Ownership

Revision as of 22:03, 27 May 2008 by Mitchell Baker (talk | contribs) (New page: Modules and Module Ownership The Mozilla project operates under the principle of distributed authority, combined with an identified ultimate decision maker should escalation be required....)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Modules and Module Ownership

The Mozilla project operates under the principle of distributed authority, combined with an identified ultimate decision maker should escalation be required. We do this through our Module Ownership system which we've used officially with code for many years. This system was initially described in early policy documents from the 1990s and remains our basic organizing and operational principle for the project.

Today the Mozilla project encompasses many activities beyond writing code. We're slowly bringing those activities into the official Module Ownership system.

The list of [Owners for code modules] is auto-generated from one of our databases known as "despot.mozilla.org".


The [list of Module Owners for Activities modules] is maintained manually.


There is also a list of[Activities Modules] that a contributor compiled in 2007. There are many activities on that list that we might decide are more like job functions than project roles, but I'm not sure yet. I'm hoping we can derive some guiding principles as we look at the early Activities Modules.