Can you please try to somehow concretize your milestone-plan with some dates?
I know, it is always hard to tell “when” in software-development but you once mentioned to hopefully reach milestone 0.6 in January 2014 and now it’s May and it doesn’t look anywhere near 0.6. Waiting for tasks and therefore 0.8 I am wondering if I have to get an in-between-solution for the next 2 months or for the next two years.

Hi rfc2822,
As far as I can see, VTODO sync is already implemented in the fork by Mirakel at https://github.com/MirakelX/davdroid. So the “only” things left would be to review and merge the changes.

Are there any steps you need help with? Are there any open issues with their code? I’d really like to see this feature happen, so if there is any work we can take off you, I’d be more than glad to help.

Are there any steps you need help with? Are there any open issues with their code? I’d really like to see this feature happen, so if there is any work we can take off you, I’d be more than glad to help.

Yes. Do you know whether their code supports and correctly handles CardDAV collections that contain both VEVENTs and VTODOs, which seems to be a common use case?

Calendars containing both, VEVENTs and VTODOs, are handled as two virtual collections, which only contains VEVENTs or VTODOs.

Do you fetch the resources with “REPORT only VTODO” and “REPORT only VEVENT” instead of PROPFIND, or do you use PROPFIND and then sort all resources into the collections? When in the code can I find these virtual collections? I hadn’t time to look into the code yet.