Skip to content

Clarify and extend org owner authority #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Clarify and extend org owner authority #61

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
25386f8
Minor cleanup to the org owner docs
infinisil Jan 22, 2025
addc735
Expand org owner authority, remove ambiguities
infinisil Jan 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 19 additions & 18 deletions doc/github-org-owners.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,43 +1,44 @@
## GitHub org owners

The following people have the GitHub "owners" permissions on the NixOS organization:
The following people have the GitHub "owners" permissions on the [NixOS organization](https://github.com/nixos):
<!-- Also keep this in sync with the members of @NixOS/org! -->
- [@infinisil](https://github.com/infinisil)
- [@lassulus](https://github.com/lassulus)
- [@tomberek](https://github.com/tomberek)
- [@winterqt](https://github.com/winterqt)
- [@zimbatm](https://github.com/zimbatm)

## How to contact the team
For any GitHub-related needs, you can reach out to the org owners by either:
- Pinging [@NixOS/org](https://github.com/orgs/NixOS/teams/org)
- [Creating an issue in this repository](https://github.com/NixOS/org/issues/new).
- Messaging in the [Github org owners help desk Matrix room](https://matrix.to/#/%23org_owners:nixos.org).

### Authority and processes
This team's role is to manage and unblock users of the github.com/NixOS GitHub organization. The @NixOS/steering gives them autonomy to handle small day-to-day tasks and expects them to escalate bigger decisions.
This team's role is to manage and unblock users of the NixOS GitHub organization.
The [Steering Committee (SC)](./governance.md) gives them autonomy to handle
small day-to-day tasks and expects them to escalate bigger decisions.
The following decision tree describes the org owners authority:

All org owners can individually take care of implementing:
- Decisions by bodies that have the authority to make GitHub org changes such as:
**Is the change impactful or controversial?**
- *Yes*: **Is the change pre-approved by a body with corresponding authority?** This includes:
- Arbitrary decisions by the Steering Committee.
- Moderation decisions by the moderation team.
- Changes from approved RFCs.
- Low-impact changes, such as:

*Yes*: Any single org owner can implement it.

*No*: Not within the org owners authority, should be escalated to the SC.

- *No*: **Is the change one of the following?**
- Adding new org members to allow review requests.
- Creating new unprivileged Nixpkgs teams for mention.
- Updating repository meta information.
- Changes requested by a repository admin that have no impact outside their repository.

Org owners need approval from at least one other org owner to take care of implementing
higher-impact changes that are _not controversial_, such as:
- Administer unmaintained repos, such as:
- Performing maintenance.
- Giving commit access to trusted people that offer maintenance.
- Archiving if appropriate.
- Changes necessary to unblock automation.
- Changes to the structure and CI of the [org repository](https://github.com/NixOS/org).
- Content updates to the [GitHub organisation documentation](./github.md).

Org owners have no authority to make other changes.
- Changes requested by a repository admin that have no impact outside their repository.

*Yes*: Any single org owner can implement it.

*No*: Approval from at least one other org owner is needed to implement it.

### Responsibilities

Expand Down
Loading