Let khal talk to CALDAV servers directly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 233
- Avg merge
- 1h 44m
- Merged PRs (30d)
- 1
Description
Hello,
I personally like the idea of decoupling the sync functionality from the calendar client, but there are several disadvantages when the CALDAV server resides in the local network. The additional synchronisation layer is simply not necessary and leads to storing events n² times for n users.
Wouldn't it be great to let khal talk CALDAV directly? It would even obsolete the local sqlite caching database...
Best regards,
Florian
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 reviewing khal's existing synchronization functionality and how it uses the local sqlite caching database. Then investigate the requirements for direct CALDAV communication and how removing or bypassing that cache would affect calendar operations. Done means khal can communicate with CALDAV servers directly without the current synchronization layer, with the architecture and compatibility implications resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, database, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100