mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge #8483

Browse Source 
8483: internal: clarify who a rls-2.0 wg r=edwin0cheng a=matklad



Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
This commit is contained in:
bors[bot] 2021-04-12 16:29:56 +00:00 committed by GitHub
commit 9f25676f0c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/dev/README.md
View File

@ -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.