Add link to the CLI working group's GitHub repository
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 363
- Forks
- 369
- Avg merge
- 1d 54m
- Merged PRs (30d)
- 59
Description
Currently, the page for the CLI working group does not link to a coordination repository for that working group:
https://www.rust-lang.org/governance/wgs/cli
There is a GitHub organization @rust-cli that claims to be the CLI working group and has this repository:
https://github.com/rust-cli/team
That seems to be the repository to which the working group's page on RLO should link, unless @rust-cli is fake and somehow impersonating the working group (despite appearing to have the real working group's participants).
Linking to the repository can help users trust that @rust-cli is not fake, without needing to compare the participants.
(Edited to add: I am not in a position to verify that @rust-cli is the real working group; "appearing to have the real working group's participants" reflected only a casual inspection by an outsider to the Rust team.)
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 CLI working group page at https://www.rust-lang.org/governance/wgs/cli and verify that https://github.com/rust-cli/team is the group's coordination repository. Done means the page links to that repository and the link is valid; the issue does not name the source file or a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100