Calendar:Module Ownership: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 12: Line 12:
|Default<br>(stuff under /mozilla/calendar not otherwise listed here)
|Default<br>(stuff under /mozilla/calendar not otherwise listed here)
|mvl<sup>*</sup>
|mvl<sup>*</sup>
|lilmatt<sup>*</sup>, daniel, philipp, ctalbert
|daniel, philipp, ctalbert, lilmatt<sup>*</sup>
|-
|-
|colspan="3"|'''Applications/Extensions'''
|colspan="3"|'''Applications/Extensions'''
Line 18: Line 18:
|Sunbird (calendar/sunbird)
|Sunbird (calendar/sunbird)
|mvl<sup>*</sup>
|mvl<sup>*</sup>
|daniel, lilmatt<sup>*</sup>, ctalbert
|daniel,  ctalbert, lilmatt<sup>*</sup>
|-
|-
|Lightning (calendar/lightning)
|Lightning (calendar/lightning)
|mvl<sup>*</sup>
|mvl<sup>*</sup>
|daniel, philipp, lilmatt<sup>*</sup>, ctalbert
|daniel, philipp, ctalbert, lilmatt<sup>*</sup>
|-
|-
|colspan="3"|'''Components'''
|colspan="3"|'''Components'''
Line 64: Line 64:
|Timezones
|Timezones
|ctalbert
|ctalbert
|mvl<sup>*</sup>, lilmatt<sup>*</sup>, daniel
|daniel, mvl<sup>*</sup>, lilmatt<sup>*</sup>
|-
|-
|Views & Dialogs (calendar/{sunbird/}base/content)
|Views & Dialogs (calendar/{sunbird/}base/content)
Line 72: Line 72:
|iTIP
|iTIP
|ctalbert
|ctalbert
|lilmatt<sup>*</sup>, daniel
|daniel, lilmatt<sup>*</sup>
|-
|-
|Printing
|Printing
Line 90: Line 90:
|CalDAV
|CalDAV
|bbrowning
|bbrowning
|lilmatt<sup>*</sup>, daniel
|daniel, philipp, lilmatt<sup>*</sup>
|-
|-
|Composite
|Composite
Line 119: Line 119:
|-
|-
|Linux
|Linux
|philipp
|daniel
|daniel
|philipp
|-
|-
|Mac OS X
|Mac OS X
|lilmatt<sup>*</sup>
|daniel
|ctalbert
|ctalbert, lilmatt<sup>*</sup>
|-
|-
|Windows
|Windows

Revision as of 21:49, 17 November 2008

<< Back to Calendar Home Page

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* daniel, philipp, ctalbert, lilmatt*
Applications/Extensions
Sunbird (calendar/sunbird) mvl* daniel, ctalbert, lilmatt*
Lightning (calendar/lightning) mvl* daniel, philipp, ctalbert, lilmatt*
Components
Accessibility philipp ?
Alarms ? daniel, philipp
Art & Branding lilmatt* MarkCarson
Calendar Manager mvl* daniel, philipp, ctalbert
Import/Export (calendar/import-export) mvl*
Installer (calendar/installer) lilmatt* ssitter, mschroeder, rob_strong, ctalbert
i18n/l10n (calendar/locales) lilmatt* sipaq
libical (calendar/libical) mvl* daniel
Recurrence daniel mvl*, ctalbert
Timezones ctalbert daniel, mvl*, lilmatt*
Views & Dialogs (calendar/{sunbird/}base/content) philipp berend, mschroeder
iTIP ctalbert daniel, lilmatt*
Printing lilmatt* daniel
Website sipaq lilmatt*
User Interface (UI) christian mvl*
Providers
CalDAV bbrowning daniel, philipp, lilmatt*
Composite mvl* daniel
ICS mvl* daniel, sebo
Memory mvl* daniel, sebo
Storage mvl* daniel, sebo
WCAP daniel philipp
GDATA philipp daniel
Tier-1 platform-specific stuff
Linux philipp daniel
Mac OS X daniel ctalbert, lilmatt*
Windows ctalbert ssitter, daniel

* Backup reviewer. Assign to them rarely.

Legend
Reviewer Bugzilla ID
bbrowning browning at uwalumni dot com
berend berend.cornelius at sun 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
mschroeder mschroeder at mozilla dot x-home dot org
mvl mvl at exedo dot nl
philipp philipp at bugzilla dot kewis dot ch
rob_strong robert.bugzilla at gmail dot com
sebo sebo dot moz at googlemail dot com
sipaq bugzilla at babylonsounds dot com
ssitter ssitter at gmail dot com

Request Queue

When multiple reviewers come in question, you should check the Calendar Request Queue to see which reviewer has the smallest queue.

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.

Use the Bugzilla ID to identify the reviewer in the Requestee field of the Attachment form.