Caldav interface

[q-wertz]

Is your feature request related to a problem? Please describe. Hi, I just started using pomatez resp. pomodoro at all. So I might misunderstand the concept. I would like to have a better overview of done tasks and possible tasks which are open. I also saw some feature requests about improvement/logging of the done tasks (e.g. https://github.com/roldanjr/pomatez/issues/210 or https://github.com/roldanjr/pomatez/issues/109) and I think it on your Roadmap is a tasks database.

Describe the solution you'd like It would be very nice and convenient to have access to service providers that nevertheless hosts tasks (e.g. Nextcloud, Exchange, …) and I think it should be possible to query & update (or even create) these tasks using caldav. Thus it would be possible to select/create/modify a task from the task lists that is anyway maintained by many people.

Benefits:

• Don't do work twice (maintaining two task lists)
• Probably a lot of code can be reused (there are libraries for caldav) and one does not have to reinvent the wheel
• It nicely integrates into standard workflows
• One has a database of performed tasks "for free"
• Structure is similar (there are also subtasks in the standard)
• …

Disadvantage:

• Might be a lot of work to get it running compared to now where a task is more or less only a string (might be enough for the start to only have "read" access and only mark a task as done)

Describe alternatives you've considered Copy the task description from my calendar to the pomatez interface.

Additional context None.