[compiz] Move KDE Plasma Integration to KDE Git Infrastructure

[Danny Baumann]

Hi,

>> I don't agree with this conclusion, though: Releasing KWD with KDE just
>> moves the code-is-broken-due-to-unsynced-release problem from 'KWD is
>> broken when KDE code is changed' to 'KWD is broken when Compiz code is
>> changed'. I'm not sure how that improves things, especially given that
>> Compiz 0.8 (which is still widely used) and Compiz 0.9 have different
>> decoration APIs (to accomodate non-composited rendering and reparenting
>> in 0.9).
> The question is whether Compiz can provide BC. KWin provides BC for the
> decoration API, but the problem is that KWD is not a decoration, but "plays
> KWin" ;-)  From a release point of view it seems easier to just also release
> the KDE integration when Compiz does a release. From what we have seen KDE has
> more releases with significant changes to API than Compiz has.

So you want to do a release whenever something significant in Kwin _or_ 
in Compiz changes? And do two releases (0.8, 0.9), at least as long as 
0.8 is widely used? Fine with me then, as long as I don't have to go 
through hoops to commit ;-)

>>> Concerning better support for changes in Plasma/KWin integration and
>>> decoration API, there is the chance that KWin developers will directly
>>> port changes to Compiz if it is in the same repository. Especially the
>>> decoration API is that small that we can add support to Compiz directly.
>>
>> With the current state of things you could provide a patch and we could
>> do our best to do a new release ;-)
> True but it is a difference whether it's part of our product or your product.

Yes, but as breaking changes can be made on both sides, it doesn't 
matter really which product KWD is part of.

>> Taking aside the point that Alt+Tab is implemented in the plugins, not
>> the decorator (which only renders the tabbox frame), I must say that
>> personally the look of Kwin's Alt+Tab implementation is one of the
>> things that makes me use compiz on KDE ;-)
> I forgot to mention that I was talking about the "classic" tabbox and not one
> of our effects. Our classic Tabbox is more like a framework to create tabboxes
> ;-)

I was talking about the classic, but composited tabbox. Not sure whether 
that one counts as effect.

Regards,

Danny