[dev] Restructuring the Kolab module

[Chuck Hagenbuch]

Quoting "Gunnar Wrobel" <wrobel at pardus.de>:

> is there anything that would prevent me from restructuring the Kolab
> module at the moment?
>
> The main point would be to clean up the Kolab Share driver mess. I
> really did not know that much about Horde and PHP when I started
> coding this and consequently a rewrite was pending for quite a while
> now.
>
> I guess there will be some bugs here and there but the whole thing
> looks much cleaner - even sane :) - now.
>
> So if nobody objects I would go ahead with the change.

Well, how will backwards compatibility be affected? You can't make  
changes to Kronolith 2.2.x that require a newer Horde version.

If what you want to do is write a new version of the Kolab package,  
you can do that either in HEAD or in a branch. It's possible the right  
thing to do is to add "kolab2" driver to applications, which uses the  
new code, and leave both versions. That way people who want/need the  
new code and have a new enough Horde version can use it, but bc is  
preserved for others.

-chuck