I believe it shouldn't be full featured CalDav server Minimum requirements to export full user Calendar as ical::Calendar, and import ical::Calendar into OM:DB, this should be simple until recurrent will be imported
So far there is no task no make other email clients to be able to work with OM as with the server On Fri, Mar 25, 2016 at 8:04 PM, Ankush Mishra <[email protected]> wrote: > > Hey Maxim, > > From the Bug Tracker: https://issues.apache.org/jira/browse/OPENMEETINGS-553 > The title only talks about syncing events using CalDAV and export/import of > iCal. Now, that I think about it, it could quite possibly mean that as well. > Do you want me to add that to the proposal? I still have time, and > implementing, shouldn't be very hard, having read the CalDAV RFC. Though the > libraries for exporting might change. Other than that the displaying of > custom Calendars, is mentioned in the Proposal, on the Managing of multiple > CalDAV servers part of the openmeetings-web. (Google Calendar can be used > with CalDAV, have used it before) > > Ankush Mishra > > PS: > > Just a note though, it'd be better using another library/already built > version of CalDAV Server's, here's a list of some mentioned on the official > CalDAV Servers page > <http://caldav.calconnect.org/implementations/servers.html>: > > > - Bedework (http://www.bedework.com/) [Java Based with Web UI] > This should most likely be what you need, except it might make > OpenMeetings quite heavy. But other than that, it's used by Universities > like Yale, Duke University and UChicago. > - SabreDAV(http://sabre.io/) [PHP] > - Calendar Server(http://calendarserver.org/) [Python] > > > In the end, if we are going in that direction, it'd be better to include > something like Bedework with OpenMeetings, as a CalDAV Server, because it > seems more stable and actively maintained along with the amount of features > it contains to amake it robust. > > Anyway, if necessary I can try and implement it. > -- WBR Maxim aka solomax
