Calendar:Module Ownership

We need to move to a better module ownership story than what we've got currently.

Current Status

First, an attempt at documenting the state of the ownership world as it exists today. Note that this represents my best approximation of how the code-review process has been happening, there may be mistakes here.

Name before the semicolon is the owner; subsequent names are an un-ordered list of peers.

• Default (stuff under calendar/ not otherwise listed here): mvl; jminta, dmose, mostafah

• Sunbird (calendar/sunbird): mvl; jminta
• Lightning: dmose; jminta
• Mac-specific stuff: lilmatt; dmose
• Website: sipaq; ?
• Alarms: jminta; dmose, mvl
• Timezones: dmose; mvl
• ICS provider: mvl; dmose
• CalDAV provider: dmose; jminta
• Memory provider: mvl; jminta, dmose
• Import/Export: mvl; ?
• libical: mvl; dmose
• views & dialogs (base/content) : jminta; mvl, dmose
• calendar manager: dmose; mvl, jminta

Most of the things below are just treated as though they are owned by the default owners listed at the top. However, I think that in general, many (most?) of them could benefit from being their own strongly-owned modules at some point.

• Windows-specific stuff
• Linux-specific stuff
• Internationalization
• Localization
• Accessibility
• Storage provider
• Composite provider
• Recurrence
• Installer
• XPI

What's Next

(I want to have an informal discussion with a couple of MoFo / MoCo folks before I post some more concrete thoughts about options for evolving this model to something that works better for everyone. After that discussion happens; I'll post those thoughts here, along with a pointer in m.d.a.calendar).