Review Request: include KolorManager in kdegraphics

[Matthias Klumpp]

Hi!
Colord - just to mention that - is also not a GNOME project, it's a
FreeDesktop project. (Doesn't mean it's "standard", but does mean that
it's not GNOME) So everyone is free to contribute to it, and the
maintainer is interested in collaborating with KDE. (which he already
does very nicely)

There's one thing about Oryanos I'd like to mention: I wanted to find
out why Oryanos is not packaged yet on many distributions. Reasons are
the strange build system it uses (looks like a custom thing to me),
which makes it difficult to build it on multiple architectures. It
also has dependencies like Elektra, which looks dead to the public.
(But is still developed, as it's maintainer says) Oryanos requires a
special version of Elektra packaged. There's also some other stuff
going on which needs to be clearified before Oryanos can be shipped in
distributions easily. It also has some legacy stuff, like Compiz
plugins - a KWin plugin would be better for KDE, IMHO ;-)

On the other hand, colord has a clean codebase, less dependencies and
it "just works" for GNOME. Although I don't have experience in color
management, seeing the younger project replacing the older one so fast
shows me that colord at least provides enough and well-working
functionality for color management on Linux.
Therefore, it might be a good thing for KDE to choose it.
(Maybe do some tests with it first)

I also want to point you to this comparison colord against Oryanos:
 => http://www.freedesktop.org/software/colord/faq.html#oyranos
Maybe also interesting, this comment of the Oryanos maintainer
(regarding the FAQ):
 => http://blog.tenstral.net/2012/02/wanted-kde-color-management-kcm.html/comment-page-1#comment-48661

Kind regards,
    Matthias Klumpp

2012/3/14 Thomas Zander <zander at kde.org>:
> Quoting Kai-Uwe Behrmann <ku.b at gmx.de>:
>>>
>>> I'm actually targeting KDE SC 4.9 as gnome-color-manager is very mature
>>> and I am
>>> pretty much just rewriting it with Qt/KDE libs.
>>
>>
>> OpenICC colour experts have then a different view of maturity.
>
>
> Kai,
>
> the two projects clearly have a different set of ideas about what they
> should do. Which is fine.
> What is not fine is write statements like the one I quoted above, you imply
> bad things about Daniel personally (his view of what is mature) which makes
> this a personal attack.
>
> In KDE we want to focus on the facts. We talk about merit.
> While its fine to give an opinion on a (technical) idea, the above is not
> acceptable.
>
> Please respect these values we hold dear here in KDE :)
> --
> Thomas Zander