More informative team descriptions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 363
- Forks
- 369
- Avg merge
- 1d 54m
- Merged PRs (30d)
- 59
Description
Many teams on @rust-lang have a description (the extra text shown when I type @rust-lang/) that just says "managed by the team repository". That's not very useful when I want to figure out which is the right team to ping. Would be better to instead show a brief description of what the team is doing. :)
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 file or test is named in the issue. Start by locating where team descriptions are defined, then identify teams using the generic description and review their responsibilities before writing concise replacements. Done means the relevant teams show useful descriptions when mentioned through @rust-lang/.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100