-
Notifications
You must be signed in to change notification settings - Fork 26
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
Reduce go-libp2p and js-libp2p admins #245
Reduce go-libp2p and js-libp2p admins #245
Conversation
The following access changes will be introduced as a result of applying the plan: Access Changes
|
ebc1180
to
540a287
Compare
18bad62
to
d60a46c
Compare
Before merge, verify that all the following plans are correct. They will be applied as-is after the merge. Terraform planslibp2p
|
d60a46c
to
fc790eb
Compare
Adding as a separate comment so people get notified. The following people will have their permissions reduced. If this is a problem (before or after the merge) open a request to modify the permissions. Below I'm explicitly calling out anyone whose permissions have dropped from admin to lower than maintain on a repo and added some explicit comments for people who I suspect might care about the permissions reduction
|
github/libp2p.yml
Outdated
admin: | ||
- aschmahmann | ||
- MarcoPolo | ||
- Stebalien |
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.
@Stebalien do you think it would still be helpful to continue to have admin here? At the moment I have you on since of the existing admin's that are not from Shipyard you're the only one whose been involved in the code at all.
If not can switch to maintain or leave you with push via Repos - Go.
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.
The only non-push thing I do is:
- Cleanup branches (should be allowed in
Repos - Go
). - Delete spam and ban spammers.
Did we ever find a way to allow everyone to do the latter? If so, Repos - Go
seems reasonable.
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.
Delete spam
IIUC it looks like spam comments is doable with just write permissions to the repo https://docs.github.com/en/communities/moderating-comments-and-conversations/managing-disruptive-comments
ban spammers
This can be done with an org-wide moderator role which you already have by virtue of being in the github-mgmt stewards group
Line 5077 in 989aed4
# 2. This team also has the org-level "moderator" and "security manager" role. |
As a result, I will downgrade to Repos Go
fc790eb
to
8f69999
Compare
Summary
Why do you need this?
The number of admin's on both of these repositories is simply too high. As described in earlier github-mgmt permissions reduction permissions are not meant as tokens of credibility, but of utility. Even the number of Admin's here may be too high, but I don't feel like I've overcut given github-mgmt is here to enable escalation.
I don't feel like I've overcut here and I've run this by @achingbrain and @MarcoPolo who are practically speaking the operating admin's of these repos (i.e. if you've used admin permissions and they don't know about it it's a problem). However, if I've overcut it seems fine to merge and re-add relevant permissions later.
What else do we need to know?
DRI: myself
Reviewer's Checklist