Why not add footnotes to this interview with *'s explaining that the features talked about as missing are available now? The shared calender and database are not the only things outdated with this interview. There are other somewhat negative comments in the interview that have since been addressed, like "For example when a process has jammed under OpenOffice so that one cannot open a new document. Unfortunately KDE is not that intelligent yet to show that by a error message"... since 3.2 KDE will notify you when an app appears to be locked up and give you the option to kill it.

If I saw a manager reading this article (on KDE Enterprise nonetheless), I would not be surprised at all if they said "oh look, KDE doesn't have any way to share calenders. Need to stick with Windows/Outlook" and stop further research. This article really needs to be footnoted to bring it up to date.

>>"For example when a process has jammed under OpenOffice so that one cannot open a new document. Unfortunately KDE is not that intelligent yet to show that by a error message"... ... since 3.2 KDE will notify you when an app appears to be locked up and give you the option to kill it.

not really, AFAIK KDE only notifies the user that a KDE Application is jammed when you try to close it.
KDE does not notice jams in non kde apps.

When Linux sites forum are awash with flames about "spatial mode", "button orders", "HIG", Walter Stolk reminds us of the sober reality. We need better documentation and a better help system. KDE has worked a lot on documentation and a lot of people have spent a lot of hours writing and translating documentation. But, there is a lot of progress to be made if we want to be on par with commercial applications. Most of the documentation is also geared to technical users. For example, if you launch Khelpcenter with this simple question in your mind "How do I configure my printer", you'll have to navigate the tree to find the Kprinter documentation (not very intuitive) and then you will be faced with the Kprinter documentation, a very fine and comprehensive documentation written by Kurt Pfeifle. The newbie will read a sentence in the first paragraph like

"KDEPrint is not a replacement for the printing subsystem itself. KDEPrint does not therefore give provision for spooling, and it does not do the basic processing of PostScript® or other print data."

And say to himself, "what is a 'printing subsystem', 'spooling', 'postscript' ? I just want to know which button to press to configure my printer"

It would be great if at some point, KDE sponsor could hire someone to help us write a layer of simple and action based help. Members of Quality Teams should also monitor that the first level of documentation should not need a BA in Computer Studies to be understood.