[Kolab-devel] Kolab 2.0 Release Coordination

Bo Thorsen bo at sonofthor.dk
Tue Jul 6 13:14:01 CEST 2004

On Wednesday 30 June 2004 09:23, Stephan Buys wrote:
> Hello all,
> I have been burning to ask this question for a couple of weeks now...
> especially with the amount of work that is going into Proko2 at the
> moment I dont want to create a diversion.
> But, now is as good a time as any to start the Kolab 2.0 release
> discussion?
> I was thinking of doing it KDE style, with a feature freeze some period
> after Proko2 is released. And a page to coordinate the
> "features/progress". One of those Red/Yellow/Green pages...
> What do you guys think?

Sounds OK. The KDE page is generated with a script, and should be pretty 
easy to adapt to our use.

> Obviously the features I would like to see in Kolab 2.0:
> Mush haves:
> - Kolab XML format interoperability.
> - Template META_DATA handling.
> - Kolab Web Client.
> - Proko2 work... (Kontact, etc.)

Sounds good to me.

> Nice to haves:
> - Cleaning up the OpenLDAP schema and separating it into separate
> schema files.

Would you take a look at the concept paper and comment on the LDAP changes 
that have been done for proko2? I think the paper is reasonably up to 
date. You can find it on www.sonofthor.dk/~bo/kolab.

> - Completing the Bootstrap work (as per the design 
> submitted a couple of weeks ago)
> - Making Kolab easier to install. Refer to
> http://dot.kde.org/1088551278/ where the author basically says Kolab is
> a Pain In The Ass to setup :-)
> Please feed back with other suggestions.

One biggie for a lot of people: Multidomain support. I assume real virtual 
domains are not easy to set up with the kolab stuff. But how about doing 
the "soft" solution where the system can run alias domains? So if we have 
domains called foo.org and bar.org, then mails to X at foo.org and X at bar.org 
will both go to the same X account. Could this be done reasonably easy?

We have already tried this to some extent. Apache can easily do virtual 
domains by us hacking in the httpd.conf.template, but cyrus rejected 
authorizations. So we could only send mail to the foo.org account and 
bar.org mails would bounce.

If this could be included, we could put real multidomain support as a wish 
for Kolab 3.0.

> BTW - who will be the release co-ordinater? I will gladly volunteer,
> but defer the decision to the other Kolab developers.

I don't have any preferences here. At least not as long as other people do 
it :-)

> Also, we need a target for release date. (Not set in stone, but a
> milestone of sorts) I suggest 1 October 2004.

I think that's a bit close for us proko2 people. November 1st perhaps?



     Bo Thorsen                 |   Praestevejen 4
     Senior Software Engineer   |   5290 Marslev
     Klarälvdalens Datakonsult  |   Denmark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20040706/db3db778/attachment.sig>

More information about the devel mailing list