GNOME Bugzilla – Bug 230297
Add support for WebDAV/FTP push/pull of calendar events
Last modified: 2012-02-19 17:20:17 UTC
Until CAP is released as an RFC and implemented, there is no opensource calendar server available.. One way to circumvent this problem would be to implement FTP/WebDAV support for storing and retrieving CAL events.. This is already done in Apple iCal (http://www.apple.com/ical/ )and in Mozilla Calendar (http://www.mozilla.org/projects/calendar/ ).. Therefore, we would have a full Free Software solution for Calendar, until CAP is widely deployed (and it would also add interoperability with iCal. Since soup already supports FTP and WebDAV, implementation should not be too long..
*** bug 230501 has been marked as a duplicate of this bug. ***
Grabbing this one.
Yeah. This is definately going into 1.6 I think. After looking at the webcal stuff that Apple's iCal does, and seeing how it works. This should be easy to do also. There is a request for the webcal support that I am making depend on this.
This is now a bounty. See http://www.gnome.org/show_bug.cgi?id=127538 Targetting this accordingly.
This is actually a feature addition at this point and should probably go to post 2.0, but I'll make it 1.5.3 for further review down the road.
The read part of webcal is done, but we aren't going to get to the push/write part for 2.0, but its a good 2.2 project.
*** bug 236255 has been marked as a duplicate of this bug. ***
For push, it should be defined that confidential and private should be handled appropriately. I have long tried to figure out how these should be dealt with. I do not believe that confidential should be published at all. Private may be appropriate to publish in a free/busy way without any information on what it is, just that you are busy. Public, well is public. Any ides on this?
*** bug 270077 has been marked as a duplicate of this bug. ***
Confidential should be published only to a server you've marked as being Ok for confidential appointments and tasks. Public ones can go to any and all of them, and private ones should not be published at all. Confidential appointments may be, for instance, published to the company intranet server, and public ones to the publicly visible one, perhaps at icalx.com... Of course the 'free/busy' publish setup allows you to set what calendar you are publishing from also. The combination of all of these should give very good configurability that ought to cover just about any situation.
retargetting this and reassigning, this is work in progress. evolution 2.5.4 includes a "publish calendar" plugin, so perhaps this could be closed as fixed already. :-/
*** Bug 271360 has been marked as a duplicate of this bug. ***
(In reply to comment #11) > retargetting this and reassigning, this is work in progress. > > evolution 2.5.4 includes a "publish calendar" plugin, so perhaps this could be > closed as fixed already. :-/ > It's not exactly the same. I can subscribe to my remote calendar using evolution and publish a local one to that location. But they remain two distinct calendars. What most of us would like is to have a calendar on a remote store and read/Write to it from evolution.
Bumping version to a stable release.
"What most of us would like is to have a calendar on a remote store and read/Write to it from evolution." Yeah, that would be so cool ;-)
It works quite well now with Davical.
Rough ancient patch available in bug 127538 comment 19.
*** Bug 127538 has been marked as a duplicate of this bug. ***
I think CalDAV satisfies what's desired here. Closing this as OBSOLETE.