rust-lang / rust-lang/libs-team
Project Groups
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 178
- Forks
- 28
- Avg merge
- 15m
- Merged PRs (30d)
- 1
Description
Right now we have a lot of unstable surface area. We're starting to track that surface area in this project: https://github.com/rust-lang/libs-team/projects/2
It's a reactive list of (most) of our current RFCs and tracking issues, organized into broad feature area. Maybe we can try arrange the columns in that project roughly into areas that we think could be managed by a project group?
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 with the Rust libs-team project 2 linked in the issue and review how its RFCs and tracking issues are currently organized. Clarify the proposed project-group areas with the team; done would be an agreed arrangement of the project columns around manageable feature areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100