-
Notifications
You must be signed in to change notification settings - Fork 0
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 members’ permissions for key Fellowship repos #11
Comments
I agree that Merge PRs should be only for Rank 3+. Ideally, triggering a release should also only be Rank 3+, or even 4+. Rest LGTM |
Thank you! I have updated the table accordingly. |
Reviews in general are permissionless. So anyone can do them, maybe rename it to "do they count for approvals"? For the RFCs, merge rights should be only via the on chain process. |
I have done this, thanks.
I have specified this. Thank you! |
@Bullrich Are you or your team available to implement these suggested changes? 👀 |
Hi @anaelleltd, I no longer work in Parity. Try contacting @lovelaced, she may be able to guide you in the correct direction. |
To help onboard candidates and engage new members as Fellowship contributors, Kian suggested a couple of months ago that we provide certain access rights for all existing members in the Runtimes repo.
Earlier on, Bryan had recommended that we give basic labelling rights to members/contributors for tracking the implementation of all approved PRs in the RFCs repo.
These new setups could be implemented through the existing Fellowship automation system.
I have summarised what these changes could look like in the table below:
Please check if this makes sense from a top-down perspective. Your advice is needed on how we should proceed where there is a ?.
The text was updated successfully, but these errors were encountered: