I am willing to explain it here, just that adding all this detail in
might be heavy to the proposal, I'll add a line or so about it to the
proposal. In fact, I had to skip a lot of detail in my proposal because
it felt too long.
Anyway, my project should allow the ability to add multiple CalDAV
servers to OM with bidirectional access. Along with this the ability to
manage the calendars. This includes saving data through openmeetings-db
to the Database.
Now to implement export and import of events from the OM calendars
including the CalDAV servers we simply put parse the events stored in
the database using iCal4j and make an ics out of them, and allow them to
save.
To import, we apply something similar, we parse the ics file provided by
the user and add those events to either the selected OM calendar or the
CalDAV servers.
I think that should satisfy the import and export of iCal Calendar to
the DB.
I'll add a couple of lines in my proposal on this detail, in a bit.
Ankush Mishra
PS: I keep forgetting to CC the mailing list.
On 25 Mar 2016 20:01, "Maxim Solodovnik" <[email protected]
<mailto:[email protected]>> wrote:
I would like to see your updated plan
Actually I believe you should drive this project :)
On Fri, Mar 25, 2016 at 8:26 PM, Ankush Mishra
<[email protected] <mailto:[email protected]>> wrote:
> Do you want me to add that detail in? I might have missed that
detail from
> the bug issue. Still have 4 hours remaining. Also, I think
Sebastian might
> have gone off to sleep if he's in NZ.
>
> Ankush Mishra
>
> On 25 Mar 2016 19:48, "Ankush Mishra" <[email protected]
<mailto:[email protected]>> wrote:
>>
>> I think that export/import of user Calendar for iCal isn't
exactly CalDAV
>> but is fairly easy to implement.
>>
>> Ankush Mishra
>>
>> On 25 Mar 2016 19:44, "Maxim Solodovnik" <[email protected]
<mailto:[email protected]>> wrote:
>>>
>>> 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] <mailto:[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
--
WBR
Maxim aka solomax
