Comment 44 for bug 329659

> However, when you depend on an open source product in a productive
> environment and you have to deal not only with one but several time
> consuming "regression or feature problems" again and again - it is no
> funny situation either. And it makes the release policy within a company
> very complicated. Therefore, I can e.g. very well understand the points
> Martin Lüchem describes.

Hi, this comment makes me thing again about a consideration I've done in the
past. Maybe it could be the start of an interesting discussion (not a flame):

being KDE, like all other free software projects, a community driven software,
where the satisfaction of the end user is not directly proportional with an
economical earning, so the "customer satisfaction" is not the main target, _ a
big, big, big warning should be printed on the home page of all the free
software projects informing end users that the software is not intended to be
installed and used in a company unless who use it doesn't exactly know what
he's doing. _
The warning should be given unless my hypothesis (customer satisfaction and
other suffs) is not right, for example due to an explicit decision made by the
developers and mantainers of that specific project which could be
intentionally developed for being used in a working enviroment.

What do you think about my old thoughts?

> I, too, ran into the Akonadi related problems with the adressbook - it took
> me hours to understand what happened why and how to resolve the problems
> with the adress book.
> [...]

This is why I really hope that KDE SC 4.5 will not break the PIM and, if it
wouldn't be a smooth transition, a huge warning should appear on the KDE
webiste :-) :-) :-)

Anyway this time I'm quite OT... :-p :-p :-p

Regards.