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

CVS (cvs.mozilla.org)

/cvsroot

• Official Policy: http://www.mozilla.org/hacking/committer/
  • Two (2) vouchers who are module owners/peers of modules where the account requester has submitted patches
  • One (1) SR not associated with the modules of which the account requester has been primarily working
  • One (1) of the people involved (among the requester and vouchers) must not be employed by the same organization
• All vouchers must have had their access for at least three (3) months before being permitted to vouch

/l10n

• 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

/www

• One (1) voucher
• All vouchers must have had their access for at least three (3) months before being permitted to vouch

Hg (hg.mozilla.org)

comm-central

• Official Policy: http://www.mozilla.org/hacking/committer/
  • Two vouchers who are module owners/peers of modules where the account requester has submitted patches
  • One SR (required for SeaMonkey and Thunderbird) not associated with the modules of which the account requester has been primarily working
  • 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
• All vouchers must have had their access for at least three (3) months before being permitted to vouch

incubator/*

• Official Policy: http://www.mozilla.org/hacking/incubator-repository.html
  • Two vouchers who are module owners and who vouched in the original incubator creation request

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 who are module owners/peers of modules where the account requester has submitted patches
  • One SR not associated with the modules of which the account requester has been primarily working
  • One of the people involved (among the requester and vouchers) must not be employed by the same organization
• All vouchers must have had their access for at least three (3) months before being permitted to vouch