Hi dear people at DAVx5,
I’m also interested in a conflict handling as proposed above, i.e. creating a backup copy of conflicting CalDav and CardDav entries. Otherwise I will loose data for sure.
The [Roadmap](link url) already mentions a solution for CardDav.
Is there already a date in mind?
Will a similar method also be implemented for CalDav?
Update F-Droid repository
Are there any plans to do this?
- We can’t update the F-Droid repository. That’s the job of F-Droid people. We don’t have any influence on that.
- What we can do is to help the F-Droid people to get up-to-date information about the source code location etc.
We have already done so: https://gitlab.com/fdroid/fdroiddata/merge_requests/1023/diffs
By the way, we’re not related to F-Droid in any way and everybody can submit merge requests to fdroiddata. You can do so yourself, too