Transitioning RelEng Status
Transitioning RelEng Status#
From time to time, folks move in and out of the Release Engineering role. As they do so, access to various systems should be granted and removed * .
When someone moves into the organization, permissions should be granted as needed to perform the various tasks. While permissions are granted only as needed, there are also minimum requirements for the permissions. For example, some permissions may only be available to someone who is both a member of the RelEng team and an employee.
The table below lists all the permissions, and which requirements are required to have that permission. When a person no longer has a specific status, all permissions which require that status need to be check and revoked. (Refer to the day one page for details on permissions.) Legend:
access to releng secrets 1
releng LDAP bits (IT bug) releng, vpn_releng, RelengWiki, & SysAdminWiki
mac signers acces
github ownership roles 4
hg.mozilla.org special access 3
github write access (review)
releng/build bugzilla group access 5
Google Drive RelEng folder access
Release google calendar
Release google group
These systems are unique, so you may need to refer to other documentation for instructions.
There are some hand maintained white lists for push permissions to certain branches. (E.g. puppet production) Changes need to be approved by a RelEng/RelOps manager.
For now, the accounts to check are mozilla & mozilla-releng, mozilla-mobile, mozilla-extensions, and mozilla-partners. Note that we’re only discussing the ownership role here on RelEng owned resources. If the person has ownership rights to repositories due to their contributor status, that does not change.
This bugzilla group can cause some confusion for folks transitioning out of MoCo but remaining a RelEng contributor. Perform on the admin page.
Unlike most of Mozilla development, some Release Engineering roles are only available to employees for various legal or contractual reasons. That leads to layers of access:
Folks directly performing tasks which require knowledge of how Release Engineering systems work and interact.
- MoCo Emp:
Folks who have a contractual arrangement with Mozilla that may be required for access to certain restricted systems and data.
Folks who have valid committer’s agreement on file.