Skip to content
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

Expand org owner authority #60

Closed
wants to merge 1 commit into from
Closed

Expand org owner authority #60

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 3 additions & 4 deletions doc/github-org-owners.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,10 +29,9 @@ All org owners can individually take care of implementing:

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 to permissions of teams and people
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we want this to be non-controversial, perhaps this should be worded as something like "with the team's approval?" Unless that's implied.

- Maintenance on otherwise unmaintained repositories
- Archival or deletion of resources that aren't needed anymore
- 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).
Expand Down
Loading