[Kolab-devel] Horde Development - call for co-ordination

[Gunnar Wrobel]

Stephan Buys <stephan at impi.org.za> writes:

> Hi All/Martin,
>
> On Wednesday 07 February 2007 10:56, Martin Konold wrote:
>> Please note that there is major work being done on our side to get a
>> working webclient soon. Actually internally the kolab xml addressbook is
>> already working with 10.000 entries very well. The calendar is also
>> progressing well and currently a Horde developer got contracted to enhance
>> some UI elements.
>
> I get the impression that a lot of companies are working on Horde and that it 
> is one of the major outstanding components. We are also working on Horde...
>
> Impi Linux can contribute both development and packaging resources to Horde.
>
> Would it be possible to combine efforts?
> - I know that Gunnar Wrobel is active with some activities
> - From what I can gather Erfrakon has some developers on it
> - Horde developers themselves are busy

As far as I know both Univention and intra2net are also working on or
with Horde.

> Perhaps getting concensus on the bug-tracking, patch submission process. Also, 
> making sure that everyone is developing against the same CVS branch, or Horde 
> release...

I think it is currently necessary to use the Horde HEAD revision from
cvs since the main idea of the recent changes was a new way of using
Shares (groupware folders) with Horde. The old way of synchronizing
the Horde Datatree backend with the Kolab groupware folders never
really worked and the new Share driver should fix that.

Patching against cvs HEAD also helps significantly in getting the
changes included upstream :)

This is certainly no long term solution since we wish to provide
stable packages to the kolab users. But the Horde roadmap suggest that
the Horde framework packages will be released as version 3.2 rather
soon (http://www.horde.org/horde/roadmap/). It would then be possible
to prepare rpms based on the released version.

In the meantime I am starting to prepare rpms from the cvs source. As
already mentioned on this list, there is a publicly accessible
subversion repository at https://svn.pardus.de/kolab-horde-tmp that
provides a first draft of Horde rpm specs. The resulting package rpms
are currently available at
http://build.pardus.de/downloads/kolab-horde-tmp. They can be
installed now and I will post instructions here and on the wiki later
today.

Concerning bug tracking:

I would suggest to add a new "horde" topic to the kolab bug
tracker. p at rdus currently collected horde specific bugs at
http://bug.pardus.de but this is suboptimal since it is no central
place. Another option would be the "Kolab" queue on the horde
bugtracker (http://bugs.horde.org) but I think this is less obvious
for the kolab users and also removes the Kolab devs as a filter for
bugs. 

Is anyone of the kolab devs opposed to adding a "horde" topic to the
bug tracker?

We could also collect and discuss patches there before submitting them
to the Horde team.

Cheers,

Gunnar

-- 
____ http://www.pardus.de _________________ http://gunnarwrobel.de _

    >> Mail at ease - Rent a kolab groupware server at p at rdus <<

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium