Update org owners, define authority and responsibilities #37
There are no files selected for viewing
Validating CODEOWNERS rules …
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,50 @@ | ||
| ## GitHub org owners | ||
|
|
||
| The following people have the GitHub "owners" permissions on the NixOS organization: | ||
| <!-- 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/#/#org_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. | ||
|
|
||
infinisil marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| All org owners can individually take care of implementing: | ||
| - Decisions by bodies that have the authority to make GitHub org changes such as: | ||
| - Arbitrary decisions by the Steering Committee. | ||
| - Moderation decisions by the moderation team. | ||
| - Changes from approved RFCs. | ||
| - Low-impact changes, such as: | ||
| - Adding new org members to allow review requests. | ||
|
There was a problem hiding this comment. How do you imagine this to be used? In Nixpkgs, this is handled by commiter delegation team, and in other repos like Nix, I would expect them to have owners who would ideally self-organize. There was a problem hiding this comment. This is just for the issue of people missing the automated org invite they get after adding themselves to |
||
| - Creating new unprivileged Nixpkgs teams for mention. | ||
| - Updating repository meta information. | ||
|
|
||
| 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. | ||
| - Create GitHub apps to unblock automation. | ||
winterqt marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| - 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. | ||
|
|
||
| ### Responsibilities | ||
|
|
||
| - Receive and process requests. | ||
| - We expect org owners to be subscribed to the NixOS/org repo. | ||
| - Each request should land in at least 2 org owners inboxes of some kind. | ||
| - Ensure that all non-trivial and non-sensitive org owner actions are | ||
| publicly logged in either of the above channels. | ||
| - Escalate requests outside the given authority to the Steering Committee. | ||
| - Maintain the [GitHub organisation documentation](./github.md). | ||
| - Act as janitor for this repository. | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe something for later:
I'd like us to standardize using GitHub issues to discuss GitHub-related topics. Spreading information in two places is not optimal for transparency reasons.