How, if at all, should `rustup` display the licence terms for Rust etc?
Open
Nobody has claimed this yet.
help wanted
question
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Should Rustup include license text and copyright notices for the Rust toolchain and its internal dependencies, to be installed alongside the binaries? Or do the binaries have command-line options to output this info? Should license info be displayed at install time also?
Contributor guide
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 reviewing the issue's questions about installing or displaying license terms and the linked Rust issue 67014. Define the expected rustup behavior and completion criteria before identifying implementation entry points; the payload names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100