-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
maintainers: make email optional #209165
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
Merged
Merged
maintainers: make email optional #209165
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
4e39849
maintainers: make `email` optional
ncfavier c165d8d
maintainers: remove "noreply" email addresses
ncfavier 93dc2de
maintainers: disallow `noreply.github.com` emails
ncfavier 0288ee5
maintainers: clarify what fields are required
ncfavier File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 hidden or 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
Oops, something went wrong.
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.
There's no way to reach out to arbitrary GitHub users
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.
Can't you just @ them?
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.
Note that this change would make 62 maintainers invalid.
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.
You can't reach out to GitHub users privately though (unless I guess you create a private repository, invite the desired users to it, then create an issue and ping them). Also when you see a GitHub users profile and they have no public email address this might be their way of saying that they don't want to be contacted privately.
I guess the question is: Do we want nixpkgs maintainers to be contactable privately? While that would be nice, I don't think it's actually needed. How about just requiring them to have a GitHub account instead, ideally with the requirement that that very GitHub user makes the PR that adds them as a maintainer. Since nixpkgs is entirely public, there shouldn't be a reason to contact people privately. If you have a question regarding a package you can file an issue and ping the maintainers.
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.
Hell no. We already have a security team for disclosures.
I'm kinda :| on that. Ideally you should be able to submit patches to nixpkgs by email. I guess there's little sense in having only a matrix ID specified though.
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.
Turns out there's only one person without an associated GitHub account:
And that looks like it might be a mistake when @LoveIsGrief added themselves in #209769 (there is an obviously associated GitHub account)
While this makes this check here more strict, it wouldn't be a problem because of that
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.
I'm not sure I understand the mistake. The file header says that email and name are required https://github.com/NixOS/nixpkgs/blob/master/maintainers/maintainer-list.nix#L4 . I followed what it says.
IMO, this PR isn't complete if
maintainers-list.nixkeep the header with the email+name requirements, if the email is rendered optional.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.
Thanks for pointing that out, that comment should indeed be updated to stay in sync with whatever check we decide to settle on.
Regardless, we should also mention that setting a GitHub ID allows ofborg to request your review automatically when a package you maintain is modified.
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.
Regardless of the other ideas here, I think this check in this PR is good as is. The only thing to do is to update the comment in the maintainer listing
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.
That's because they have all been removed in #178656
Famously, there was @volth that received a full damnatio memoriae by github but contributed patches using the discourse forum, I think.