matrix-org / matrix-org/matrix-rust-sdk
Message retention implementation tracking
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 500
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 106
Description
In implementation for https://github.com/matrix-org/matrix-spec-proposals/blob/matthew/msc1763/proposals/1763-configurable-retention-periods.md, I intend to break this up into at least two PRs:
1. endpoint retrieval and event/state handling
2. execution of removing expired messages per retention policy
This issue is just for tracking the bigger task, re @stefanceriu's suggestion.
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 reading the linked MSC1763 configurable retention periods proposal. Break the investigation into the two areas named in the issue: endpoint retrieval and event/state handling, followed by removing expired messages according to the retention policy. The task is done when both implementation areas have been completed as separate PRs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100