Page MenuHomeFreeBSD
Files F167277763

D58830.diff
No OneTemporary
Actions

D58830.diff
View Options

diff --git a/website/content/en/internal/resources.adoc b/website/content/en/internal/resources.adoc
--- a/website/content/en/internal/resources.adoc
+++ b/website/content/en/internal/resources.adoc
@@ -7,10 +7,18 @@
= Commit Bit and Project Resources Policy
-== Rationale
+The core team has sole authority for managing access to project resources, including granting and revoking both commit bits and user accounts.
-The core team manages access to project resources including granting and revoking both commit bits and user accounts. Core may delegate portions of these tasks to other groups or individuals at its discretion. For example, certain commit bits are managed by other groups as noted in link:{committers-guide}#committer.types[Commit Bit Types] subject to core's final approval. The core team has held this authority since its inception, but wanted to make it explicit to avoid confusion. The FreeBSD Core team approved the following commit bit and project resources policy which was posted to the Developers mailing list on August 4, 2011.
+== Delegation
-== Policy
+Under normal circumstances, the core team delegates management of repository-specific resources to link:{committers-guide}#committer.types[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.
-The core team has sole authority for managing access to project resources. This includes granting and revoking both commit bits and user accounts.
+== Guidelines
+
+A commit bit may be suspended or revoked for link:../expire-bits[inactivity], link:../code-of-conduct[conduct violations] or other link:../policies[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.

File Metadata

Mime Type
text/plain
Expires
Fri, Aug 21, 2:43 PM (10 h, 19 s)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
36969417
Default Alt Text
D58830.diff (2 KB)

Event Timeline