Services/Process/Code Review: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 38: Line 38:
* [mailto:tarek@mozilla.com Tarek Ziade]
* [mailto:tarek@mozilla.com Tarek Ziade]
* [mailto:telliott@mozilla.com Toby Elliott]
* [mailto:telliott@mozilla.com Toby Elliott]
* [mailto:jconlin@mozilla.com JR Conlin]
* [mailto:ianb@mozilla.com Ian Bicking]
* [mailto:ianb@mozilla.com Ian Bicking]


=== Key Exchange Server (Python) ===
=== Key Exchange Server (Python) ===

Revision as of 15:03, 11 January 2011

Code Review Policy for Mozilla Services Code

Code review prior to landing is now required for _all_ changes to all production-oriented Mozilla Services code. This includes the Firefox Sync client code, the various pieces of server code, and anything else living in http://hg.mozilla.org/services.

Code Areas

Firefox Sync (add-on and library code)

Repositories Sync Client

Reviewers

Server Code (PHP)

Repositories

Reviewers

Primary Server Code (Python)

Repositories

Reviewers

Key Exchange Server (Python)

Repositories

Reviewers

System-review

System-review (similar to super-review in core Mozilla code) is designed to ensure the overall coherence and stability of the Weave ecosystem. Changes to any Weave code covered under this policy that impacts APIs, scalability, or client performance may require system-review, in addition to primary review. This review will generally not cover the details of the code, but will focus on the overall system performance aspects of the patches.

Mike Connor (mconnor@mozilla.com) is the only current system-reviewer