rust-lang / rust-lang/rust-forge
Document bootstrap team's backport process
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 568
- Forks
- 253
- Avg merge
- 5h 33m
- Merged PRs (30d)
- 12
Description
It will be probably very similar to https://forge.rust-lang.org/compiler/backports.html, except bootstrap team doesn't have sync meetings (anymore) so no sync backport decisions can be made during sync meetings.
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
Start by reading the linked compiler backports documentation and compare its process with the bootstrap team's stated lack of sync meetings. Document the bootstrap team's backport process, omitting sync-meeting decisions, and consider the work complete when contributors can follow the resulting guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100