Conversation
|
Before merge, verify that all the following plans are correct. They will be applied as-is after the merge. Terraform plansipld |
|
Cc @aschmahmann , @rvagg , @vmx since this is removing you as org owners (but still keeping you as github-mgmt stewards). The rationale and permissions exploration was done in ipfs/ipfs#511 (comment) |
| - rvagg | ||
| # Why @vmx? | ||
| # 1. Continued IPLD maintainer since the pre-2021 days of an "IPLD core team", working across both JS and Rust repos. | ||
| # 2. Owner of important IPLD community touch points like monthly community calls. |
There was a problem hiding this comment.
Update: I misunderstood how things work, now that I do, it's what I've asked for, so all good. Below is my original message which doesn't really apply anymore.
Sadly those calls are not a thing anymore.
Also I don't really need to be an admin as long as there's some easy way to get things done in case I need something (knowing who to ping is what I consider easy). I'm in favour of having as little admins as it's useful. I don't see it as something "taken away" from me, it just makes sense from an opsec perspective.
Unless you want me as a person that can be pinged and do things, I'm also happy to fill that role for IPLD.
|
@galargh : I think we're good to have you merge given there is approval here. |
galargh
left a comment
There was a problem hiding this comment.
Approving & merging since initial approvals were received - thank you @BigLep for driving the initiative.
As a reminder to everyone, any changes made through GitHub Management are always reversible - in particular, GitHub Management Stewards can always apply any change (e.g. reinstate the org admins) themselves.
Summary
Followup to #68 to further reduce org owners/admins based on where have been landing in ipfs/ipfs#511.
No worries if IPLD doesn't want to go to this extreme - this can be abandoned.
If this approved, after merging, the following steps will need to be taken:
Reviewer's Checklist