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

Helge Hess evolution@opengroupware.org
Thu, 17 Aug 2006 13:13:37 +0200


On Aug 17, 2006, at 12:50, Robert de Geus wrote:
> I guess so, we are now testing in our office on 2.6, but it is also in
> our plan to do an upstream merge a.s.a.p. to the main evolution tree.

Nice! :-)

> It is not in our plan to do this. I think it is a matter of trying to
> compile it in 2.4, it is not part of our testing scheme.

OK.

>> Hm. You based your work on the Noodle trunk branch? I've tried to
>> replace all "opengroupware" references with "GroupDAV" in my branch.
>> While I don't mind OGo publicity, I really think we should make this
>> a "GroupDAV" connector.
>>
> I don't know what you mean, I am not programming, Shreyas is. Are you
> refering to the naming of objects?

Function names and stuff in the connector itself, plus the labels in  
the UI.

> We are however trying to make an
> implementation of groupdav for opengroupware. Our users are going  
> to be
> using both the web interface and evolution, so we want as many  
> features
> available in evolution as in opengroupware as well as a data  
> consistency
> between the two client interfaces.

OK, do you plan to extend Evolution UI to access OGo features not  
available in Evo itself?

> So maybe you could explain us where are the differences between
> opengroupware.org and groupdav... We might be able to take some issues
> in account.

Hm, "differences"? Those are different entities :-) GroupDAV is a  
protocol which works against several servers, including OGo.  
Obviously it doesn't address features which are unique to OGo.

> It would be very nice indeed if this implementation is fully
> groupdav compliant, but I hope you also understand that we need
> something that works and that our users understand.

OK. The point of GroupDAV (as with any standard ...) is that the  
incident for other people to help with the connector gets raised. If  
its "just" an OGo connector, only OGo people are interested to fix bugs.

Of course an OGo specific connector can integrate better with OGo  
which is also nice ;-)

> Because we are only testing against opengroupware we wont find any
> issues concerning other server implementations.

Ack.

Greets,
   Helge
-- 
Helge Hess
http://docs.opengroupware.org/Members/helge/