21–30 of 97 posts
Maybe this means Canonical will focus more on ARM hardware now, which is kind of the point of Mir anyway - to be a lot more efficient on "lower-end" mobile hardware like ARM chips. Can't say I wouldn't like that to happen.
Or Canonical's packagers will just carry on patching the Intel drivers?
Earlier quoted context omitted.
This is not about FOSS, it is about one man's vision to circumvent the mainstream developer community. Ubuntu chose to make the transition from pre-configuring Debian and making compiz themes for Gnome to trying its hand at systems-level programming. It would be somewhat self-assured of them to assume that all hardware vendors, who are already heavily invested in Linux, as a platform, would necessarily pick up the sl…
I don't say otherwise, just that Intel as a company is a corporation like any other, with contributions to FOSS also driven by internal politics.
[1] http://www.markshuttleworth.com/archives/551 [2] https://twitter.com/olliries/status/375704285083738112
According to Phornoix, Chris Wilson of Intel wrote this in a Git commit: We do not condone or support Canonical in the course of action they have chosen, and will not carry XMir patches upstream. http://www.phoronix.com/scan.php?page=news_item&px=MTQ1NjY Phoronix's link to said commit does not work, so it is hard to infer context. But I would assume that "the course of action they have chosen" refers to working on Mi…
""the course of action they have chosen" refers to working on Mir in the first place rather than contributing to Wayland. If that's the case, can't say I really blame Intel." I absolutely blame Intel. Whatever you think about Ubuntu's decision to make their own X server, it is childish to not include working patches for purely political reasons. It's not like Ubuntu is asking Intel to do their work for them. So Canon…
Earlier quoted context omitted.
Or Canonical's packagers will just carry on patching the Intel drivers?
That works fine because Intel has open source drivers. Not so much if NVIDIA and AMD decide to only support Wayland.
What an awful move. Note that they are deliberately hurting open source software by restricting contributions for a purely political reason. Obviously it will result in an Ubuntu fork of the intel drivers, which will eventually lead to a situation where the only consequence is a more painful workflow for Ubuntu core contributers and early adopters looking for up to date drivers.
What an awful move. Note that they are deliberately hurting open source software by restricting contributions for a purely political reason. Obviously it will result in an Ubuntu fork of the intel drivers, which will eventually lead to a situation where the only consequence is a more painful workflow for Ubuntu core contributers and early adopters looking for up to date drivers.
I don't see how it's political to let Canonical keep the burden of maintaining code that only they care about...
If there are technical reasons - like the one you mentioned - let's hear them, they might be valid.
What an awful move. Note that they are deliberately hurting open source software by restricting contributions for a purely political reason. Obviously it will result in an Ubuntu fork of the intel drivers, which will eventually lead to a situation where the only consequence is a more painful workflow for Ubuntu core contributers and early adopters looking for up to date drivers.
Ubuntu is creating Mir for political reasons. There's no reason for upstream projects to maintain code that only benefits a single distribution.
Maybe this means Canonical will focus more on ARM hardware now, which is kind of the point of Mir anyway - to be a lot more efficient on "lower-end" mobile hardware like ARM chips. Can't say I wouldn't like that to happen.
It would be smart to focus on ARM as a long-term strategy. There is a huge investment and legacy in x86 but if history is right, ARM will eat up x86 from the bottom-up just like x86 did to the other ISA's.
Why would any party make such a hostile announcement in the FOSS scene? I'm not all that involved in that scene, but surely this approach is counter-productive? Especially if you can't back it with a sound technical reason.