[OGo-Evolution] OGo - evolution connector uploaded in CVS

[Robert de Geus]

Hi Helge,
I have read the groupdav specs, in principle this is what we want to
adhere to. It would be helpfull if we have an overview of the
discrepancies between opengroupware and groupdav. I know you are in the
original group who made the draft, so my guess is that opengroupware
stays close.

We don't need to look at how the client implements the specification,
the client is always evolution. But there are difficulties, for example
zidestore implements a directory structure, evolution does not allow for
subdirectories of folders. But this is a client problem.

I just went through the groupdav specs:

Ad 3: we only implement events tasks and contacts,
missing: journals and mails

Ad 3.1 I dont understand the FREEBUSY implemntation, how does this apply
in zidestore?

Ad 3.1.1. Recurring items can be created in a new calendar item (webui),
you can change each recurring item individually, the only operation
which applies on the recurring list, is the delete all. The delete all
applies also to the changed items. Also when changing one of the items
in evolution, the zidestore server keeps the list so is still able to
delete the whole list. Do we also allow this in evolution, or can this
even be done?

Ad 3.1.2. Alarms, at this moment in the current connector implementation
we get all alarms of all calendar items stored on the zidestore server.
If I look at the specification, it says no alarm, if I think what I
would like to have is getting the alarm for my own calendar items
(centrally stored), but not of the ones created by others. 

Ad 3.2. Tasks some things work, but we have not touched tasks yet. We
have not observed users using tasks, so it is not high on our wish list.
This will be implemented in a basic way as it looks now, just to make it
working.

Ad 3.2.1. Recurring Tasks, even more exotic, I don't see this
implemented.

Ad 3.2.2. Connected Tasks in the groupware server tasks are connected in
projects, evolution has no way to display projects, so this probably
will not be implemented

Ad 3.3. Contacts high on the priority list, should support proper
caching as described by the groupdav specs, categories should be
displayed and usable. Does zidestore provide a way to see all defined
categories? Does evolution have a way to display them and store them on
the server?

Ad 3.4. Journals What are journals????

Ad 4. Handling of UIDs, this is important for meetinging? At this moment
the connector does not save the meeting names. One could think of
displaying all employees for a meeting, or, allow for arbitrary names to
be stored. What to do if users enter email addresses which dont exist in
zidestore? In most companies, you would like to schedule with employees.

I hope this give a starting point to figure out the conflicting points
between opengroupware/evolution/groupdav

It would be good to at least know them before making decisions.

gr.
Robert