Commit Bit and Project Resources Policy

Under normal circumstances, the core team delegates management of repository-specific resources to the responsible team as long as the core team is kept informed of all decisions to grant, suspend, or revoke access. While the core team reserves the right to review and modify any decision, it prefers to defer to its delegated partners whenever possible.

A commit bit may be suspended or revoked for inactivity, conduct violations or other policy violations, or actions that put the integrity of a repository at risk. Unless the circumstances justify immediate action, such as a compromised account or a serious violation, a team should first engage the committer to attempt to resolve the issue before suspending or revoking access.

When a team suspends or revokes a commit bit, it should promptly inform both the committer and the core team of the reason and, for a suspension, the requirements for reinstatement. A committer may ask the core team to review any suspension or revocation decision. However, the core team generally avoids second-guessing teams that have followed these guidelines.