Kolab 2 hits the masses
Today the second generation of the Kolab groupware solution was released. It's incredible how far this project has come. I still remember when Martin Konold first told us about his ideas about "How to escape from the Outlook trap" at Linuxtag three years ago. We were sceptical, because it was all vaporware back then and the plans were, well, ambitious. But now with Kolab 2 we actually have a solid all Free Software groupware solution with full KDE client support through Kontact and even KDE as a project has begun to use it.
There are two aspects about Kolab which I think are particular noteworthy. First, it is an example how commercial development of Free Software can work. Most of the Kolab development was payed work. But it was done in KDE CVS and well integrated with the project. It took some time until this kind of collaboration really worked, but now it can safely be considered a success and a prototype for future commercial KDE development.
The other aspect is the design decision to access all data on the server via IMAP. This makes Kolab unique and allows for extreme scalability. It also means that a rich client is required, but this in fact is a great benefit which automatically brings nice features as offline capabilities or a rich user interface for viewing and editing calendar data. An interesting tweak is that the Kolab client not only works with the dedicated Kolab server, but with any IMAP server. So you can use your normal mail account to do server-based calendaring with Kontact.
So what will bring the future? Kontact has support for an impressive list of groupware servers, the Kolab support probably being the most stable right now. The crazy thing is that this spans such a huge variety of different technologies, from iCalendar over HTTP and WebDAV, through SOAP and XML-RPC to LDAP and IMAP. Which one is the best and will become most widely accepted only the future can tell. KDE Kontact is well equipped to be an important part of this future.
One major problem still exists, though: There are no Kolab T-Shirts yet ;-).
About the T-Shirts
Come to LinuxTag this year and get yours :)
Well done, folks
This is what happens when developers focus on project goals and user needs instead of merely trying to do a free mirror image of whatever Microsoft happens to be doing at any given time. The goal of building an "Exchange killer" isn't a realistic one, because Exchange attempts to be a "one size fits all" solution. Microsoft can get away with that; open source can't. That's why there are a half dozen credible open source groupware solutions that each focus on different needs. This is great because every organization can select the one whose feature set best matches their needs. All of them, including Kolab, have come a long way. Standard data formats and a friendly rapport between the various projects are making open source groupware an enjoyable scene to be a part of.