Re: Resolving the TWin/KWin Fork Issue

<snip> This is so important. KDE is a large collection of separate projects with many developers. kwin is part of the KDE collection, but that doesn't mean they did exactly as most of KDE did, scrap the code. KWin is a continuation, an improvement, an developed active codebase. Martin said to me privately (I paraphrased a bit to make sure it made sense): "There is no such thing like "kde", kde is a community of developers producing different products. I assume you mean with kde our workspaces "KDE Plasma". In fact KWin is part of the KDE Plasma Workspaces but that does not mean that we are heavily integrated into it. There are three desktop shells we currently support which makes it impossible to heavily integrate into one." I see no reason why we couldn't at least make the effort to having a build of kwin that fits our needs in the long run. Calvin