rust-lang / rust-lang/compiler-team
Review P-high issues (recurrent)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 433
- Forks
- 73
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Meeting proposal info
- Title: Recurrent Review P-high issues
- Type: technical
Summary
We hold recurrent meetings to review and re-evaluate the list of open T-compiler P-high issues (deciding if they're still a high priority or downgrading them).
About this issue
This is a tracking issue for all the meetings of this kind so it's easier to have them grouped together and schedule them more or less regularly.
Here the list of the meetings so far:
Comment policy
This issue needs no comment or announcement
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or implementation entry point is named. Start by reviewing the linked prior review issues and HackMD notes to understand the recurring meeting process; done means maintaining the grouped record of P-high reviews and their scheduling information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100