-
Notifications
You must be signed in to change notification settings - Fork 11
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 org owners/admins #68
Conversation
Before merge, verify that all the following plans are correct. They will be applied as-is after the merge. Terraform plansipld
|
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.
seems reasonable as a minimal step in the process, although I want @Stebalien to be aware of this and have the possibility of objecting because he's only remaining semi-active participant being shuffled here. Some background discussion in #65 about steps to reduce permissions surface area.
@daviddias I'm @mentioning you to inform you that your ipld github "org ownership" permissions are being removed as part of a wider effort to cleanup Github permission across IPFS, libp2p, libp2p. You are still a member of the ipld github org and retain your existing direct github repo permissions or team permissions. The current plan is to merge this change on Tuesday, 2024-02-13. That said, this isn't a one-way door. If we get this wrong or you see the notification after the fact, a new PR can be created fix permissions. Thanks and let me know if you have any questions or concerns. |
Summary
This aligns with the "reduce org owners" step listed in ipfs/ipfs#511.
This is the first step of wider 2024Q1 permissions cleanup.
Why do you need this?
Github org safety. See ipfs/ipfs#511 for more info.
Timeline
Reviewer's Checklist