Manage CalDAV calendardata growth via OCC
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
When using the CalDAV backend, oc_calendarobjects grows indefinitely.
I's probably not a good idea to indiscriminately delete events for the past, whether it be for compliance or simply to preserve the events for posterity.
We should allow admins to run an occ command to clean up historic calendar data.
Careful of RECURRENCEs here, they shouldn't be deleted so we can accurately display the scheduling data for each recurrence.
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 from the CalDAV backend and the proposed occ command, then inspect how historic data is stored in oc_calendarobjects and how RECURRENCE data is represented. Done means admins can invoke a cleanup command without deleting recurrence data or indiscriminately removing events needed for scheduling history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cli, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100