This document is intended to describe a refinement of the current code ownership and review process in calendar/. For a similar proposal for toolkit/, see this newsgroup thread.
Within Mozilla, code-ownership and the review process are closely tied. In order to maintain consistency, clarity, and quality in the code in CVS, the code owner and a small group of peers act as a filter for incoming code through the review process. The number of people involved in this filtering has, of necessity, remained small due to the need for each of them to be trusted by all to make similar/compatible decisions. This, however, has resulted in a rather long wait for reviews, which leads to frustration and slow patch development.
In order to try to avoid this bottle-neck, as well as to encourage interested contributors to rise within the Mozilla system, the review/ownership process is going to be changed, as follows:
- The calendar/ code will be broken up into several smaller modules
- At least one review will be needed for every patch
When the reviewer signs off on a patch, it should be because he/she believes that the patched code meets the Mozilla standards. At a minimum the review should ensure that the code:
- fixes the identified problem
- gives no unintended errors or warnings
- is properly documented/commented
- does not contain unjustified 'hacks' or 'work-arounds'
- conforms to the style of the surrounding code
- is consistent with the rest of the module's code
- is consistent with the direction/vision of the project
For more information on what to look for in a review, see these guidelines.
This process is not intended to be set-in-stone. Should you notice problems or ways to improve this process, please bring them to the attention of the calendar developers.