-
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
Update rust-libp2p access #252
Conversation
The following access changes will be introduced as a result of applying the plan: Access Changes
|
4bbc545
to
892eb8c
Compare
Before merge, verify that all the following plans are correct. They will be applied as-is after the merge. Terraform planslibp2p
|
Thanks for the PR @AgeManning. Before merging the PR, we need to update the permissions for libp2p crates on crates.io since they depend on the existing Github teams. IMO it would make sense to create a maintainers team to be owner of the libp2p crates, and generally manage the repos settings. |
github/libp2p.yml
Outdated
- w3dt-stewards | ||
maintain: | ||
- rust-libp2p Maintainers | ||
- sigma-prime |
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.
@AgeManning Thanks for creating this PR but my 2 cents is that I like the abstraction that rust-libp2p Maintainers preserves. If a new full time rust-libp2p maintainer is at Shipyard or other org that's not Sigma Prime, it wouldn't be correct to add that new maintainer to the sigma-prime user group; and because they are a full time maintainer, it wouldn't be correct to add them to rust-libp2p-contributors either.
Wdyt about keeping rust-libp2p Maintainers and having that group consist solely of sigma-prime 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.
Yeah for sure.
We are adding new people from sigp in the near future. I thought it might be useful to group them under a sigma-prime
banner so it was easier to identify people and change if we no longer become maintainers.
More than happy just to keep it general and rename to rust-libp2p-maintainers
.
Thanks! I'm assuming these changes need to be done by someone with ownership on crates.io. Not sure how to make those changes. |
@AgeManning, would it be possible to add me to the |
Yep, added you @guillaumemichel |
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.
This PR should be good to be merged since the Github team url for rust-libp2p-maintainers
doesn't change, so it shouldn't affect access on crates.io.
Summary
I think the access for the rust-libp2p repository is quite out of date and there are various teams scattered in the configuration which are applied inconsistently to various rust-libp2p repositories. Further, Sigma Prime has become a maintainer of the rust-libp2p repository, and this PR updates the github access to reflect this. This is akin to: #245
In summary, this PR
sigma-prime
team which has admin rights of the rust-libp2p repositoryrust-libp2p-contributors
team keeping the active users as membersrust-libp2p-contributors
team to rust repositoriesWhy do you need this?
The access for the rust-lib2p repository is out-dated and there are various parties with more access than needed. In order to make this repository secure, and potentially move some CI into Sigma Prime's self-hosted ecosystem, the permissions for this repository need to be tightened to those who actually need them.
What else do we need to know?
This should only effect rust-libp2p and access rights that rust-libp2p maintainers currently posses.
cc @guillaumemichel - You have write access to all rust-libp2p repos. Happy to make a new team of maintainers if you needed higher privileges than write.
cc @jxs - I think I've maintained all current contributors access and removed out-dated contributors, but it might be worth double checking.
DRI: myself
Reviewer's Checklist