Update members’ permissions for key Fellowship repos

[anaelleltd]

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:

Repos	Permissions	Rank 1	Rank 2	Rank 3+
Runtimes	Create projects	N	Y	Y
-	Create/delete labels	N	Y	Y
-	Add/remove labels	Y	Y	Y
-	Assign PRs/issues	Y	Y	Y
-	Review PRs (for approval)	Y	Y	Y
-	Merge PRs	N	N	Y
-	Trigger releases	?	?	Y
-	Close PRs/issues	N	N	Y
-	-	-	-	-
RFCs	Create projects	N	Y	Y
-	Add/remove labels	Y	Y	Y
-	Assign PRs/issues	Y	Y	Y
-	Merge PRs (on-chain only)	N	N	Y
-	Close PRs/issues	N	?	Y
-	-	-	-	-

Please check if this makes sense from a top-down perspective. Your advice is needed on how we should proceed where there is a ?.

[kianenigma]

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

[anaelleltd]

I agree that Merge PRs should be only for Rank 3+.

Thank you! I have updated the table accordingly.

[bkchr]

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.

[anaelleltd]

Reviews in general are permissionless. So anyone can do them, maybe rename it to "do they count for approvals"?

I have done this, thanks.

For the RFCs, merge rights should be only via the on chain process.

I have specified this. Thank you!