Skip to content

Commit a35f92e

Browse files
committed
org admin -> org owner
Use correct GitHub terminology. Owner is an entity, admin is a role. Owners have admin permissions.
1 parent 181851e commit a35f92e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

text/2872-github-access-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ This RFC was written in consultation with the Governance Working Group and the I
1111
# Motivation
1212
[motivation]: #motivation
1313

14-
Access control for the [Rust-Lang GitHub Organization](https://www.github.com/rust-lang) and repositories within that organization is currently managed either through the [rust-lang team database][db], or ad-hoc via the GitHub UI by the org administrators. We need a policy that defines how these accesses are granted and managed. This will allow us to have greater security in permissions to our GitHub org, and provide transparency and clarity on how access is managed.
14+
Access control for the [Rust-Lang GitHub Organization](https://www.github.com/rust-lang) and repositories within that organization is currently managed either through the [rust-lang team database][db], or ad-hoc via the GitHub UI by the org owners. We need a policy that defines how these accesses are granted and managed. This will allow us to have greater security in permissions to our GitHub org, and provide transparency and clarity on how access is managed.
1515

1616
[db]: https://github.com/rust-lang/team/
1717

@@ -42,7 +42,7 @@ GitHub provides several permission levels for access to a repository. Please ref
4242

4343
Repositories in the Rust-Lang organization should follow these permission guidelines:
4444

45-
* **Admin** --- No users or teams except for org admins should have this permission level.
45+
* **Admin** --- No users or teams except for org owners should have this permission level.
4646
* **Maintain** --- Teams may have this permission level at their discretion for repositories the team is responsible for.
4747
Repositories using the [bors] bot may want to consider using the *write* permission level instead in order to deactivate the "Merge" button on PRs to enforce that merges go through bors.
4848
* **Write** --- Teams that are responsible for a repository should have at least this permission level.

0 commit comments

Comments
 (0)