Commit Policy:Current Procedures

Currently, only a tiny portion of the accounts created in Mozilla's version control systems are tied to some type of official policy. Most of what actually happens is processed under some generic requirements plus specific requirements depending on what type of access is being requested. The purpose of this document is to codify all types of account requests and the current processes and policies used to govern each type. The hope is that official policies can be written that takes these separate types into account and makes the current process easier for everybody.

Global Requirements

• All account requests (except where noted) require the following:
  • SSH public key be attached to the bug
  • Committer's Agreement filled out, signed, and sent to Erica

Hg (hg.mozilla.org)

comm-central

• Official Policy: http://www.mozilla.org/hacking/committer/
  • Two vouchers
  • SR required for SeaMonkey and Thunderbird
  • SR not required for Calendar, but currently can't really enforce that technically-wise to prevent committing to SR-required areas
  • One of the people involved (among the requester and vouchers) must not be employed by the same organization

incubator/*

• Official Policy: http://www.mozilla.org/hacking/incubator-repository.html

l10n-central

• Vouch from Axel or some l10n owner that Axel delegates vouching rights to
• Requests are mostly handled by Axel, with the generic assistance of Marcia and Reed

mozilla-central

• Official Policy: http://www.mozilla.org/hacking/committer/
  • Two vouchers
  • One SR
  • One of the people involved (among the requester and vouchers) must not be employed by the same organization