On Fri, Jun 14, 2013 at 6:50 PM, Scott Kitterman <email@example.com> wrote:
> On Friday, June 14, 2013 06:41:33 PM Thomas Voß wrote:
>> On Fri, Jun 14, 2013 at 6:27 PM, Jonathan Riddell <firstname.lastname@example.org> wrote:
>> > On Fri, Jun 14, 2013 at 11:47:43PM +0800, Ma Xiaojun wrote:
>> >> KDE, this one is interesting. The one even tries to support
>> >> proprietary OS. The same also claim their CI has very limited distro
>> >> coverage so they cannot support distro specific feature. Maybe we
>> >> replace Kwin with something else then problem solved (KDE run on
>> >> proprietary OS without Kwin)
>> > KDE having some applications running on Windows and Mac is irrelevant
>> > to this conversation.
>> > We're not going to drop KDE's compositor and window manager.
>> I wouldn't have assumed that. But from a technical perspective, I'm
>> trying to understand why kwin couldn't be integrated with Mir. Judging
>> from the recent development with respect to a Wayland backend in KWin,
>> I got the impression that kwin's overall architecture is meant to be
>> pluggable to different windowing systems/compositors. I would be happy
>> to start looking into this if someone from the KDE/kwin team could
>> work together with me and guide me through the code.
>> Do you think that makes sense?
> It could be technically. What we've lacked is someone with the time and
> skills to do the work. Upstream kwin have said that as long as Mir is a
> single distro solution, they aren't going to integrate it (which I think it
> quite reasonable). I think providing assistance to someone else who's going
> to do the work would be a different question, so we can ask.
Fair enough, let's work together to find a solution here. Out of
curiosity: Wayland is not shipping in a distro thus far (as far as I
know), what is KDE's /kwin's integration model there? Do you get help
from the Wayland community (would be my assumption here)?
>> >> I believe that there is nothing technically wrong with Mir or it is
>> >> fixable. If upstreams have political problems, what can we do?
>> > It's not a case of technical problems it's a case of Mir being
>> > different for no paticular advantage. It's a political problem of
>> > Canonical's making not KDE's. And the question is indeed what can we
>> > do in Ubuntu.
>> I cannot give a political answer here but would like to resort to the
>> technical help offered before and evaluate how we could support KDE
>> (or more specifically kwin) best on Mir.
> I think we're all after a good technical solution for which there are
> resources to implement. I know it won't happen upstream KDE and I'm almost as
> confident the Kubuntu team is lacking the right skills to do it, so your offer
> to look into it is most appreciated.
Great, feel free to point people into my direction and we can get
started as early as next week!
Looking forward to it and thanks for starting the discussion. Do you
need anything else from my side to get the conversations going?
> Scott K
> ubuntu-devel mailing list
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
ubuntu-devel mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel