From c8f48f50b330b6060f993e3ffff5a5218de5994a Mon Sep 17 00:00:00 2001 From: Aleksey Kladov <aleksey.kladov@gmail.com> Date: Mon, 12 Apr 2021 19:06:07 +0300 Subject: [PATCH] internal: clarify who a rls-2.0 wg --- docs/dev/README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/dev/README.md b/docs/dev/README.md index 9c0eb135826..f74f7d8eb74 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md @@ -235,12 +235,14 @@ We don't do "patch" releases, unless something truly egregious comes up. There are three sets of people with extra permissions: -* rust-analyzer GitHub organization **admins** (which include current t-compiler leads). +* rust-analyzer GitHub organization (**admins**)[https://github.com/orgs/rust-analyzer/people?query=role:owner] (which include current t-compiler leads). Admins have full access to the org. -* **review** team in the organization. +* (**review**)[https://github.com/orgs/rust-analyzer/teams/review] team in the organization. Reviewers have `r+` access to all of organization's repositories and publish rights on crates.io. They also have direct commit access, but all changes should via bors queue. It's ok to self-approve if you think you know what you are doing! bors should automatically sync the permissions. -* **triage** team in the organization. +* (**triage**)[https://github.com/orgs/rust-analyzer/teams/triage] team in the organization. This team can label and close issues. + +Note that at the time being you need to be a member of the org yourself to view the links.