matrix-org / matrix-org/matrix-rust-sdk
Move `matrix-sdk::encryption::backups` to matrix-sdk-crypto so that it can be used by clients using that crate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 500
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 106
Description
We have a useful module called `matrix-sdk::encryption::backups` ([documentation](https://matrix-org.github.io/matrix-rust-sdk/matrix_sdk/encryption/backups/index.html), [code](https://github.com/matrix-org/matrix-rust-sdk/tree/main/crates/matrix-sdk/src/encryption/backups)) which is responsible for managing server-side key backup. It would be useful to move that module to `matrix-sdk-crypto`, so that it can be used by clients like Element Web which depend on that library (and currently have to duplicate the backup-management code).
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 with crates/matrix-sdk/src/encryption/backups and compare its public API with the matrix-sdk-crypto crate and its documentation. Trace how server-side key backup is exposed and consumed, then verify that clients using matrix-sdk-crypto can use the moved functionality without duplicating backup-management code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100