We need to rethink how we cleanup auditlog
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
There's a lot of data that isn't needed a few weeks after the meeting was closed (like invites)
Additional data contains things that might be unnecessary.
We don't need to retain changelog info, but maybe markers that something was done.
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 locating the auditlog cleanup and meeting-closure entry points, then review how invites, changelog information, and completion markers are stored. Clarify which data should be removed a few weeks after a meeting closes and what must remain. Done means an agreed retention policy and an implementation plan, since the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100