GNOME Bugzilla – Bug 686529
Pickup ownCloud accounts from GOA
Last modified: 2013-09-14 16:56:15 UTC
ownCloud accounts offer CardDAV endpoints whose URI is available as the Uri property on the account's org.gnome.OnlineAccounts.Contacts DBus interface. It would be good if Evolution picked up ownCloud accounts. I understand that EDS does not have a CardDAV backend at the moment. So, maybe, this should also depend on another enhancement request to add such a backend.
Well we have a WebDAV backend, which is just a less efficient way of dealing with address books since you have to GET/PUT the whole book at once. It still works though. What we really need is an API to scan the WebDAV server for available address books, and then populate the E-D-S account with equivalent ESources. Similarly for calendars. The CalDAV setup dialog has a "Find Calendars" dialog that can already do this interactively. We just need to extract some bits from there so it can be used non-interactively by E-D-S for both calendars and address books. This is also needed for Google and Yahoo! accounts.
(In reply to comment #1) > The CalDAV setup dialog has a "Find Calendars" dialog that can already do this > interactively. We just need to extract some bits from there so it can be used > non-interactively by E-D-S for both calendars and address books. > > This is also needed for Google and Yahoo! accounts. Google CalDAV doesn't support server browsing, I'm not sure if you even tried that when you removed calendar pickup based on libgdata (aka it had its meaning why it was done that way). Thus users in 3.6.0+ cannot subscribe to other Google-server-side-subscribed calendars anymore. Not that the old way was the best on the world, but it was any at least. That means, you cannot rely on WebDAV support on the servers, it can be blocked for many reason, same as you will not be able to reach shared calendars of other users for the privacy reasons, and so on. Anyway, I do not think that the above blocks this in any way. You probably didn't mean it that way, I guess.
Let's deal with the two bugs in one only, in the older. *** This bug has been marked as a duplicate of bug 686528 ***