Licensing issues
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 232
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 60
Description
in this comment @briansmith mentions that docs.rs isn't following licenses properly.
https://github.com/briansmith/ring/blob/master/LICENSE is *ring*'s license.
I would imagine that it'd be a good idea to turn off generation for any crate that has something like this in its Cargo.toml.
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 linked pull request comment, ring's LICENSE, and ring's Cargo.toml entry referenced in the issue. Trace how docs.rs decides whether to generate documentation from Cargo.toml license metadata; done means crates with incompatible licensing metadata are handled according to the project's licensing policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100