Mozilla Governance: Module Ownership System

A key part of how the Mozilla project runs is the Module system, which breaks project activities and codebases down into discrete chunks and assigns an owner to each. The documentation of who owns what is on the Mozilla wiki. So if you want to find out who to talk to about FooBar-ing in Mozilla, that’s the place to look.

If you don’t find the owner of FooBar documented there, then you’ll need to find out who’s in charge by asking around. But once you do find out, please suggest to that person that they head over to the Modules page and get their ownership formalized by applying to create a new FooBar module. It’s not a complicated process.

2 thoughts on “Mozilla Governance: Module Ownership System

  1. It might be a good idea for someone to go through the list and remove obsolete modules? e.g. there’s a LiveConnect module listed, but liveconnect was removed from the tree in 2009 (bug 442399)

  2. Steve: Probably only the module owner who oversees the affected area (e.g. the owner of Firefox, or Thunderbird, or Brendan for Core) can do that. It would be good to do, but those people are busy, and I’d rather focus on getting new modules added and the list being made more complete in that way.

    Still, if it’s as clear-cut a case as “this well-defined bit of code was entirely removed from the tree 2 years ago”, then perhaps I might go out on a limb and remove it myself ;-) Any other examples?