Skip to content

doc: adding labels doesn't require commit rights #92941

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.

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

Closed

Conversation

philandstuff
Copy link
Contributor

Motivation for this change

As of RFC 39, package maintainers are members of the NixOS github
organization who don't have commit rights. However, they do have what
GitHub calls Triage rights, which means that package maintainers
are able to add labels to PRs. The documentation should make this
clear.

I don't know the right way to phrase this in the docs, but the current
text of "Requires commit rights" is definitely incorrect.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

Sorry, something went wrong.

Verified

This commit was signed with the committer’s verified signature.
eadwu Edmund Wu
As of [RFC 39][1], package maintainers are members of the NixOS github
organization who don't have commit rights.  However, they *do* have what
GitHub calls [Triage rights][2], which means that package maintainers
are able to add labels to PRs.  The documentation should make this
clear.

I don't know the right way to phrase this in the docs, but the current
text of "Requires commit rights" is definitely incorrect.

[1]: https://discourse.nixos.org/t/join-the-package-maintainer-team/3751
[2]: https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level
@@ -49,7 +49,7 @@
<itemizedlist>
<listitem>
<para>
Add labels to the pull request. (Requires commit rights)
Add labels to the pull request. (Requires maintainer rights)
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That might be the case, but I think the language of github permissions is too low-level for this doc. Users shouldn’t need to understand the low level github permissions system, and how that maps on to teams in the NixOS org. The important question is, “what governs whether a user can add labels to PRs in the NixOS org?”, in language the user understands and can take action on.

I think it might be as simple as “all package maintainers” or “all NixOS org members” (“but who gets to be an org member?” is the natural question arising here)

Copy link
Contributor

Choose a reason for hiding this comment

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

Why not both? That way, we can keep a high level user facing explanation ("NixOS org terminology"), and make it clear to people who know about GitHub rights exactly what's going on. 😃

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The nixpkgs manual is already way too long and unfocused. I don’t want to add to that.

We should maybe document the GitHub permissions thing somewhere, but this isn’t the doc section to do it.

@ofborg ofborg bot added 8.has: documentation This PR adds or changes documentation 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux labels Jul 11, 2020
@philandstuff
Copy link
Contributor Author

Thought: now that OfBorg automatically adds labels, do we even need documentation encouraging reviewers to do it? Could we just get rid of those lines?

@stale
Copy link

stale bot commented Jan 8, 2021

I marked this as stale due to inactivity. → More info

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jan 8, 2021
@SuperSandro2000 SuperSandro2000 added the 2.status: merge conflict This PR has merge conflicts with the target branch label Jan 18, 2021
@stale stale bot removed the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jan 18, 2021
@stale
Copy link

stale bot commented Jul 19, 2021

I marked this as stale due to inactivity. → More info

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jul 19, 2021
@asymmetric asymmetric added the 6.topic: documentation Meta-discussion about documentation and its workflow label Jan 12, 2024
@stale stale bot removed the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jan 12, 2024
@wegank wegank added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Mar 19, 2024
@wegank wegank marked this pull request as draft March 20, 2024 15:34
@Aleksanaa Aleksanaa closed this Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.status: merge conflict This PR has merge conflicts with the target branch 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md 6.topic: documentation Meta-discussion about documentation and its workflow 8.has: documentation This PR adds or changes documentation 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants