Modules Scratchpad

Author: Mitchell Baker

Background

I've got an open bug to explore the extent to which we can use the principles of code modules and module ownership for non-coding activities -- https://bugzilla.mozilla.org/show_bug.cgi?id=363541.

Recently Stuart did a massive clean-up and reorg of our code modules and module owners. (The list of current code modules is at http://www.mozilla.org/owners.html). As part of this Stuart compiled a list of potential non-code modules that we might think about. That list is below. Many, *many* thanks to Stuart for this work (the bug is mine, but Stuart did the initial work -- how great is that?)

This is a preliminary brainstorming list. Some items on it might not make sense. There are undoubtedly other items which should be here but aren't. If you see something where you think you're the obvious owner, don't get upset if there's no owner; Stuart did a bit of initial work, this isn't intended to be everything we know. It's a starting point.

The purposes of this list are:

• to have some concrete examples to use when we start to evaluate application of code module ownership principles
• to get an idea of the scope of non-coding activities
• to think about which activities make sense as "modules,"
• to start thinking about the granularity of non-code modules - which might mimic the toolkit example of one large module with sub-modules, which if any very specific activities should be separately identified; and
• to improve the list.

The list below actually contains some suggested code modules where we didn't have any ("tinderbox webtool code"), some non-code modules and some that fall in between. Some of these modules are big areas while some are more specific so it's possible to know the correct contact; the tinderbox modules are an example of specificity. We may also want to have modules that contain submodules. The list is not in any particular order. Alphabetizing it might be helpful but I haven't done that yet.

Feel free to note things you believe could be a module, who might own it and a description of what you believe that module covers. For now I suggest aiming at big chunks of activities that might be missing.

[Update April 2008: I took out all the various theoretical owners names. Enough time has passed that a lot didn't make sense any more, even if we do end up creating some of the potential modules.]

Modules

• Tinderbox config/release config
  • Owners:
  • Notes:
  • Directories: mozilla/tools/tinderbox, mozilla/tools/tinderbox-configs

• Tinderbox webtool code
  • Owners:
  • Notes: There are three versions of Tinderbox...
  • Directories: mozilla/webtools/tinderbox

• Build machines
  • Owners:
  • Notes:
  • Directories:

• Product l10n
  • Owners:
  • Notes:

• PR
  • Owners:
  • Notes: (maybe merge with Press)

• mozilla.com website
  • Owners:
  • Notes:
  • Directories:

• mozilla.org website
  • Owners:
  • Notes: has despot module already
  • Directories:

• MPL
  • Owners:
  • Notes:
  • Directories:

• Press
  • Owners:
  • Notes: (maybe merge with PR)

• Community marketing
  • Owners:
  • Notes:

• Website localizations
  • Owners:
  • Notes:
  • Directories:

• Partner relations
  • Owners:
  • Notes:

• Mozilla store
  • Owners:
  • Notes: run by the foundation
  • Directories: http://store.mozilla.org

• Firefox/Thunderbird branding
  • Owners:
  • Notes: logos, branding guidelines, agreements, permissions
  • Directories:

• SpreadFirefox
  • Owners:
  • Notes:
  • Directories:

• developer.mozilla.org
  • Owners:
  • Notes:
  • Directories: http://developer.mozilla.org/

• addons.mozilla.org
  • Owners:
  • Notes:
  • Directories:

• mozilla-europe.org
  • Owners:
  • Notes:
  • Directories:

• mozilla-japan.org
  • Owners:
  • Notes:
  • Directories: http://www.mozilla-japan.org/

• foxkeh.jp
  • Owners:
  • Notes: Mozilla Japan character mascot website
  • Directories: http://foxkeh.jp/

• Community giving
  • Owners:
  • Notes: providing resources to community to remove barriers to make peoples work easier
  • Directories:

• Build
  • Owners:
  • Notes:
  • Directories:

• Firefox product management
  • Owners:
  • Notes:
  • Directories:

• Thunderbird product management
  • Owners:
  • Notes:
  • Directories:

• QA
  • Owners:
  • Notes:
  • Directories:

• Release testing
  • Owners:
  • Notes:
  • Directories:

• Manual testing
  • Owners:
  • Notes:
  • Directories:

• Automated testing
  • Owners:
  • Notes:
  • Directories:

• Testing infrastructure
  • Owners:
  • Notes:
  • Directories:

• Release management
  • Owners:
  • Notes:
  • Directories:

• Product security
  • Owners:
  • Notes:
  • Directories:

• Security communication
  • Owners:
  • Notes:
  • Directories:

• Documentation
  • Owners:
  • Notes:
  • Directories:

• Developer tools
  • Owners:
  • Notes: dom inspector, etc
  • Directories:

• Webtools (general)
  • Owners:
  • Notes: Is there a single person that looks over all webtools or should they just all be their own toplevel module?
  • Directories:

• Branches: 1.5, 1.8
  • Owners:
  • Notes:
  • Directories:

• Linux distros
  • Owners:
  • Notes:
  • Directories:

• Antiphishing
  • Owners:
  • Notes:
  • Directories:

• Platform (windows, mac, etc) owners
  • Owners:
  • Notes:

• Mobile
  • Owners:
  • Notes:
  • Directories:

• Labs
  • Owners:
  • Notes:
  • Directories:

• IT/sysadmins
  • Owners: Justin
  • Notes:

• Demos
  • Owners:
  • Notes: Person responsible for building cool new demos

• Design
  • Owners:
  • Notes: UI/architecture

• Graphics
  • Owners:
  • Notes: application graphics, icons, etc., Might have an internal component.

• Developer days
  • Owners: shaver
  • Notes:
  • Directories:

• Speaker's bureau
  • Owners:
  • Notes:
  • Directories:

• Certification authorities
  • Owners:
  • Notes: Evaluation of CAs for inclusion in Mozilla, represent Foundation on CA/Browser Forum
  • Directories: http://www.mozilla.org/projects/security/certs/