Repository navigation
Bring existing compiler team repositories up-to-code. #65
Description
Activity
Having a quick look, I think these are the relevant repositories:
- rust-lang/rust
- rust-lang/rustc-guide
- rust-lang/miri
- rust-lang/compiler-team
- rust-lang/measureme
- rust-lang/chalk
- rust-lang/polonius
- rust-lang/rustc-rayon
- rust-lang/rustc-hash
- rust-lang/wg-traits
- rust-lang/datafrog
- rust-lang/llvm (archived)
- rust-lang/lldb (archived)
- rust-lang/rust-forge (maybe?)
- rust-lang/llvm-project (maybe?)
- rust-lang/rls (maybe?)
- rust-lang/gll (maybe?)
And these are the relevant labels that would need to be on each repo:
P-high,P-med,P-low,T-compilerandI-nominated. Not sure about these, might just be relevant for rust-lang/rust:regression-from-stable-to-beta,regression-from-stable-to-beta,beta-nominatedandstable-nominated.- changed the title
[-]Unify labels across compiler team repositories.[/-][+]Bring existing compiler team repositories up-to-code.[/+]on May 9, 2019 We want to make sure that all compiler team maintained repositories match the out-of-tree crates policy, that means making sure that the repositories on this list have the following:
- GitHub permissions (
Compilerteam with write,Assigneeswith read) -
READMEdescribing intended purpose of the crate, who maintains it and intended level of stability and maintenance. -
LICENSE-MITandLICENSE-APACHE -
CODE_OF_CONDUCT - Labels for triage:
P-high,P-med,P-low,T-compilerandI-nominated. -
@rust-highfive
Reacted by Linwei Shang and Jean Mertz- GitHub permissions (
This issue originally only aimed to unify the labels across compiler team crates, but was generalized to list all of the things listed in the out-of-tree crates policy. The original description is below.
In order to perform triage in the weekly meeting across nominated issues in all compiler-team maintained repositories, we should make sure that there are a consistent set of labels that are used and that we update the triage meeting agenda to point to these searches.