KDE Project Offers Kolab Groupware Services to its Contributors

At the Dutch KDE-PIM meeting in Annahoeve last weekend it was announced that the KDE project will offer groupware services to all KDE contributors using the Free Software groupware server Kolab2. This means that every KDE project or contributor can get a Kolab2 account for sharing tasks, appointments, contacts and email. Every project can manage their own groupware services and decide with which users they want to share these resources. The Kolab2 server will run under the domain and will be administered by the KDE project.

Kolab2 is a very robust groupware solution, capable of handling large scale installations. It is tightly integrated with Kontact, the PIM suite from KDE. Currently Kolab2 offers an excellent Free Software solution for providing groupware services to the GNU/Linux and Unix desktop and even to the Windows desktop through the use of the Toltec plugin.

KDE contributors who are interested in having such an account can send an email to kdemail signup. The bandwith and hardware is donated by Fruitsalad, a community that provides hosting and other services to the KDE and Kolab community.


I wonder if this will pass the Jamie Zawinski test?


By Derek Kite at Tue, 2005/05/31 - 5:00am

I know that this Jamie guy is one of the "I-know-better-than-anybody-else"-folks.

But I don't know what the Jamie Zawinski test is. Care to enlighten me, Derek?

By Anonymous at Tue, 2005/05/31 - 5:00am

gg:groupware laid.

His blog is/was the first item.


By Derek Kite at Wed, 2005/06/01 - 5:00am

That's great.

Its a pity that installing Kolab is so difficutl/strange. I've been desiring to try it since I started to actively use kaddressbook and korganizer, but my email accounts don't support sieve, so I'm still using local files and POP accounts.

I hope in the future we can see tarballs of Kolab, and more easy to install/package, instead of that strange openpkg and RPMs.

By suy at Tue, 2005/05/31 - 5:00am

I agree on the point about source tarballs, minus the rpm stuff. Unless I am mistaken (it does happen :) ), doesn't the source tarballs have to be created to make the RPMS?

As it is, it tends to either leave the source distros out in the cold or jump through a bunch of hoops just to extract the source from the rpms.

By stumbles at Tue, 2005/05/31 - 5:00am

I don't understand. I've found the Kolab setup very clean and easy: one script to launch, a few questions to answer. What strange with that?

By andrianarivony at Tue, 2005/05/31 - 5:00am

i guess it's somewhat strange to have two packaging systems side-by-side, one deb and rpm. and for most (like me) rpm isn't part of their daily work, so they have to learn that, too. it's easy, no big difference, just an other db structure, but it's a psychological barrier.
but Kolab install doesn't require any knowledge about rpm, since the scripts take care of everything.

By Andy at Wed, 2005/06/01 - 5:00am

There exist more than two systems package systems: " package management -rpm -deb -src"

By Anonymous at Wed, 2005/06/01 - 5:00am

See KDE for example. You can compile the sources, and install them wherever you like. I have KDE installed both from the standard packages of my distribution, and from source, under ~/kde/local (so they don't collide one with the other).

KDE is very easy to package (at least, applications). If you take a look at

You'll see RPMs... for Debian!

I want just a tarball with some source, and some user defined prefix for installation. The README says that the installation is going to /kolab, instead of following the FHS. Also, have in mind that you need patched versions of some applications. This is pretty ugly for packaging purposes. Why I need to download again apache?

By suy at Wed, 2005/06/01 - 5:00am

just for completeness:

The prefix is arbitrary in Kolab 2. So you may for example set it to /usr/local/kolab or /opt/kolab if you happen to prefer these paths.

By Martin Konold at Thu, 2005/06/02 - 5:00am

I wonder, does this implementation include the experimental webclient (based on Horde)? I want to migrate from Exchange 2000, but would prefer an easier installation method, and a working webclient.

By Philip Cain at Tue, 2005/05/31 - 5:00am

I think you can consider that the webclient is no longer in an experimental status.

The Kolab webpage has to be refreshed cause I use it in a production environment for one month (with a Kolab server of course) ... :)


By Mike at Tue, 2005/05/31 - 5:00am

That's good news. Now if we could just get an easy installer. Heck, I don't care if was ncurses on the CLI, just something more than editing conf files and reading man pages. (Of course, it may well have improved since the last time I tried it - downloading now!)

By Philip Cain at Tue, 2005/05/31 - 5:00am

if you follow the instructions to a T, you can get away with running two scripts (and waiting quite a few hours, depending on the speed of your machine) to have a working kolab2 server.

i made the initial mistake of using a non-FQDN for the server which led to me blowing away the install and starting again, though a /kolab/etc/kolab/kolab_bootstrap would've also done the trick it turns out (as i found out later on when i was screwing around with the configurations)

By Aaron J. Seigo at Tue, 2005/05/31 - 5:00am

> KDE contributors who are interested in having such an account can send an
> email to kdemail signup

Uhm, this means mail to and with what subject, content ..? What bot or person sits on the other end and how does the promised work?

By WakkoWillie at Tue, 2005/05/31 - 5:00am

There's a person at the other end. Mainly Matt Douhan.

By Anonymous at Tue, 2005/05/31 - 5:00am

Hey, after all these awesome KDEPim interviews -- wouldn't it be in order to publish some interviews with Kolab2 developers, administrators and users too?

I want, I want, I want....

By Anonymous at Tue, 2005/05/31 - 5:00am

Already again? Just had it four months ago:

By Anonymous at Tue, 2005/05/31 - 5:00am

> Already again?
Yes. A different one.

> Just had it four months ago:
Missed that one. Thanks for the link.

Didn't we have multiple KDEPim interviews? Each of which covered anther person involved with the project, and another perspective?

Same should happen for Kolab2. Now that it will soon be released. After all, it is not hype -- it is a very well working solution, and it scales to many thousand of users. Unlike Hula. Hula currently is not more than vaporware. However, I read more about Hula on various news sites than on Kolab2. That must change.

By Anonymous at Wed, 2005/06/01 - 5:00am

There will likely/hopefully be some press about the Kolab2 release but that's up to the Kolab people (and you?) and not the KDE developers.

By Anonymous at Wed, 2005/06/01 - 5:00am