rust-lang / rust-lang/libs-team
Libs-team RFC guidelines appear to be out of date
@Amanieu is already working on this.
Since Jan 30, 2024.
- Dominant language
- Rust
- Stars
- 178
- Forks
- 28
- Avg merge
- 15m
- Merged PRs (30d)
- 1
Description
The guidance at https://github.com/rust-lang/rfcs/blob/master/libs_changes.md for filing RFCs appears to be quite old and doesn't contain all the detail about how the libs team seems to operate these days.
Primarily, it doesn't seem to recognize the ACP process, which is what I assume how you would like to process most changes these days. I actually don't understand when someone should use an RFC versus an ACP, and I don't know how to find that out. I'm also uncertain what else in that document might no longer be current.
Would someone be willing to update the guidance (at least adding a link to something describing ACP), or point the link somewhere that better reflects on how libs changes should be proposed?
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.
Assessment
This issue has not been assessed yet.