[Kolab-devel] Horde roadmap

[Richard Bos]

Op Friday 27 July 2007 16:55:24 schreef Gunnar Wrobel:
> > Can you say something about horde for non openpkg installations?
> > What is horde's current status?  Will they release a new versions
> > of concerned horde applications with kolab patches, do you know this?
>
> In general the Horde situation is actually not too complex anymore (at
> least I hope so).
>
> 1) Releases
>
>  - The next Horde release will be 3.2
>
>    Don't ask me for a specific release date there. So far the main
>    Horde devs responded with "It is done when it is done." :)
>
>    But you may look for progress on this wiki page:
>
>    http://wiki.horde.org/ShowStoppersThreeTwo

Thank you for the link.  As you stated it doesn't say much, as one does not 
know when it is done.


>    This should give you some hints when it might happen.
>
>    Horde-3.2 will contain a lot of Kolab specific improvements that
>    are already available in Horde CVS.
>
>    Once 3.2 has been released my current horde packages within Kolab
>    CVS will be switched to use the stable 3.2 release.
>
>  - Currently you can use Horde CVS snapshots. They are available here:
>
>    http://ftp.horde.org/pub/snaps/
>
>    This is also what I'm doing at the moment for both the OpenPKG and
>    Gentoo packages. Both are based on these snapshots.
>
> 2) Patches
>
>    Many improvements went into Horde CVS already. There are still some
>    patches necessary and you find them *ALL* in the server/horde
>    subdirectory within Kolab CVS. There are only five patches left.

For completeness I'll include references to these patches, so they are easy to 
look up.
Horde-framework patches:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/horde/horde-framework/Kolab-Kolab-IMAP-cclient.php.patch?rev=HEAD&content-type=text/vnd.viewcvs-markup
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/horde/horde-framework/Prefs-Prefs-kolab.php.patch?rev=HEAD&content-type=text/vnd.viewcvs-markup

Horde-turba patches:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/horde/horde-turba/config-sources.php.dist.patch?rev=HEAD&content-type=text/vnd.viewcvs-markup
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/horde/horde-turba/lib-Turba.php.patch?rev=HEAD&content-type=text/vnd.viewcvs-markup
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/horde/horde-turba/lib-Driver-ldap.php.patch?rev=HEAD&content-type=text/vnd.viewcvs-markup

>    These patches did not make it into Horde yet because they are not
>    clean enough for Horde or need to be rewritten to match Horde
>    structures.

Fortenately the patch are not big, 2 of them are only changing 3 lines or 
less.

>    During the next months several of those patches will hopefully be
>    cleaned up and integrated into Horde so that we arrive at zero
>    patches for the Horde web client. Whether this will happen before
>    or after 3.2 is something I cannot say at the moment.
>
> 3) Configuration
>
>    You can currently get configuration hints from both the
>    Kolab2/Gentoo repository as well as from Kolab CVS though I think
>    the configuration in Kolab CVS needs to see a few more fixes. In
>    any case you will need to adapt it to your system in any case.

Can you refer to these configuration hints?  In kolab cvs, I don't see the 
hint under the horde directory.  Is it located somewhere else?

> So I would say it is definitely possible to already provide a working
> Horde configuration on any "native" Kolab system by using the
> snapshots and the patches in Kolab CVS. There is no "hidden magic" you
> need to invoke in order to make it work :)
>
> Cheers,
>
> Gunnar

Thanks a lot for your concise answer, and all the effort you put in kolab and 
horde to make them work toghether.


-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.