Calendar:Module Ownership

This is the current list of owners and peers of the calendar modules. Don't edit this file. Just don't.

Items without any owners at all are generally handled by those under "Default." However, in general, they could benefit from being their own strongly-owned modules at some point.

Module	Owner	Peers (alpha order)
Default (stuff under /mozilla/calendar not otherwise listed here)	mvl*	lilmatt*, daniel, mickey, ctalbert
Applications/Extensions
Sunbird (calendar/sunbird)	mvl*	daniel, lilmatt*, ctalbert
Lightning (calendar/lightning)	mvl*	daniel, lilmatt*, ctalbert
Components
Accessibility	?	?
Alarms	?	daniel, philipp
Art & Branding	lilmatt*	MarkCarson
Calendar Manager	mvl*	daniel, ctalbert
Import/Export (calendar/import-export)	mvl*	mickey
Installer (calendar/installer)	lilmatt*	rob_strong, ctalbert
i18n/l10n (calendar/locales)	lilmatt*	sipaq
libical (calendar/libical)	mvl*	daniel, mickey
Recurrence	daniel	mvl*, mickey, ctalbert
Timezones	ctalbert	mvl*, lilmatt*, daniel
Views & Dialogs (calendar/{sunbird/}base/content)	mickey	philipp
iTIP	ctalbert	lilmatt*, daniel
Printing	lilmatt*	daniel
Website	sipaq	lilmatt*
User Interface (UI)	christian	mvl*
Providers
CalDAV	bbrowning	lilmatt*, daniel
Composite	mvl*	daniel, mickey
ICS	mvl*	daniel, mickey
Memory	mvl*	daniel
Storage	mvl*	daniel
WCAP	daniel	?
GDATA	philipp	daniel
Tier-1 platform-specific stuff
Linux	daniel	?
Mac OS X	lilmatt*	ctalbert
Windows	ctalbert	ssitter, daniel

^* Backup reviewer. Assign to them rarely.

Legend
Reviewer Bugzilla ID bbrowning browning at uwalumni dot com christian christian.jansen at sun dot com ctalbert ctalbert at mozilla dot com daniel daniel.boelzle at sun dot com lilmatt lilmatt at flock dot com MarkCarson mark at markcarson dot com	Reviewer Bugzilla ID mickey michael.buettner at sun dot com mvl mvl at exedo dot nl philipp philipp at bugzilla dot kewis dot ch rob_strong robert.bugzilla at gmail dot com sipaq bugzilla at babylonsounds dot com ssitter ssitter at gmail dot com

Review Process

Calendar does not require super-review. The only review is needed is the review of a module owner or peer of the involved module. (If a patch spans multiple modules, you need review from an owner or peer from each module. That sounds problematic, but due to the huge overlap in owners and peers, in most cases it can be done by one person.)

If the module owner and their peers are all busy and don't have time to do a complete review, you can ask someone else to review the code. This must be 'known hacker', somebody who has done calendar work himself, but does not need to be a module owner or peer. If you have code review, you can ask a owner or peer of the module your code touches to give module-owner-approval. Giving this approval only means that the code is good from a high level point of view. Because this is a lot less work, it should be easier to get this approval.