theupdateframework / theupdateframework/rust-tuf
factoring out Repository implementations into separate crates
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 198
- Forks
- 39
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
We haven't quite figured out our rust https story on fuchsia, but one of the options we are considering is to have a dedicated service managing web requests. If that's the case, we won't necessarily need hyper+some tls in the tuf repo. If that's the case, it'd be nice if we could build the core tuf library without it.
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 by mapping the Repository implementations and their dependencies on hyper and TLS in the rust-tuf crate. Determine how the core TUF library can build without those dependencies and how the implementations should be separated into dedicated crates; done means the core builds independently and the repository implementations remain usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100