If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I bet Mark's approach will be to garner a user base that will lead to greater uptake, so don't get ahead of yourself. We are talking about Linux here, and Mark has been the only one to get it into the mainstream so far, so put some trust in him to take it further.

Without Mark and Ubuntu, Linux would be still in the dark ages. Ubuntu has brought competition by their sheer innovation, causing other players to be doing catchup.

So Martin Gräßlin thinks he owns Kubuntu or KDE based Ubuntu. Is this a case of tall poppy-syndrome of people not liking Mark's success?

Ubuntu is kicking butt. Just accept it, it's quality and vision that others are lacking.

He "owns" kwin though, he's the main kwin developer for upstream KDE. kubuntu generally doesn't do any development of KDE itself afiak, so if he says kwin won't support mir I'd say thats accurate, since he's one of the people actually coding kwin.

I bet Mark's approach will be to garner a user base that will lead to greater uptake, so don't get ahead of yourself. We are talking about Linux here, and Mark has been the only one to get it into the mainstream so far, so put some trust in him to take it further.

Without Mark and Ubuntu, Linux would be still in the dark ages. Ubuntu has brought competition by their sheer innovation, causing other players to be doing catchup.

How is Ubuntu in the mainstream? Go out to town stop 100 people and ask them what computer operating systems they know.
Haven't seen a Ubuntu fanboy in so much denial for a long time.

He "owns" kwin though, he's the main kwin developer for upstream KDE. kubuntu generally doesn't do any development of KDE itself afiak, so if he says kwin won't support mir I'd say thats accurate, since he's one of the people actually coding kwin.

My statement is still correct. If Martin plays politics then he's doing himself and KDE, a disservice.

I use Kubuntu myself. I want it moving forward, not go stale with the likes of other distributions who put little effort in concurrency and size of their repositories, or KDE versions. Canonical has also made KDE what it is today, by their support for Kubuntu.

My statement is still correct. If Martin plays politics then he's doing himself and KDE, a disservice.

I use Kubuntu myself. I want it moving forward, not go stale with the likes of other distributions who put little effort in concurrency and size of their repositories, or KDE versions. Canonical has also made KDE what it is today, by their support for Kubuntu.

My statement is still correct. If Martin plays politics then he's doing himself and KDE, a disservice.

I use Kubuntu myself. I want it moving forward, not go stale with the likes of other distributions who put little effort in concurrency and size of their repositories, or KDE versions. Canonical has also made KDE what it is today, by their support for Kubuntu.

Wake up and smell the flowers(roses) is an appropriate saying.

Starting from this point:

If there are downstream specific patches they should be applied downstream. This means at the current time there is no way to add support and even if someone would implement support for KWin on Ubuntu I would veto the patches as we don’t accept distro-specific code. If Mir becomes available on more distributions one can consider the second question.

It is evident that:
1) If he speaks about to put a "veto" on some eventualy distro-specific patch this means, to me, that he is in change for do it.
2) if you are seasoned about the space-man policy in terms of open source approach, it is your problem. Other people follow different approach about the open source community and if he say "we do not accept distro-specific patch" it means that he *does not go stale with the likes of just-one-distro*
3) KDE has made KDE what it is today, Canonical was and is busy to make many things but no one of those have something to share with KDE. Wait, maybe Wayland could be something to share with kde, but they have correct this error pretty quickly.
4) *If there are downstream specific patches they should be applied downstream* should be clear enough, isn't it?