The author of the patch is in the best position to submit it.
I don't know any better than you. My best guess is the general lack of doing that in Ubuntu - "if we don't do that for anything else, why bother for these".I wonder why they have not bothered, then? (in this particular case). It's not like those are 'deal-makers/breakers' or offer Ubuntu some huge advantage (or even minor) over XYZ distro.
The patches mentioned do offer an advantage, from few hundred ms to a second or two faster boot time, depending on hw and initrd size.
Yes, the source is out there, and personally I've been using for long now.If upstream wanted them why wait for Ubuntu to submit? The source code is out there, go get them and implement them. Why does it have to be a one way street? Isn't that the whole point of the GPL?
But if you're asking why this doesn't happen in general (upstream going around checking forks if they have useful code), it's usually lack of time and interest.
The title of this article is wrong: 'Canonical "Won't Fix" GTK+ Wayland For Ubuntu'
It didn't get marked "Won't Fix" for all of Ubuntu, as the title says, it got marked "Won't Fix" only for the upcoming Raring release. If you look at the linked bug, its status is still "Confirmed" for Ubuntu.
I opened the bug. Ubuntu's request that the Wayland backend for GTK to be split out to a dynamic library before being included in one of their releases doesn't seem terribly unreasonable to me. I just wish they mentioned it six months ago, last time they said they wouldn't include it in a release.
Can't include this in Precise because it's a stable release....
Can't include this in Quantal because it's too late in the release cycle, even though the bug was open before the Precise release....
Can't include this in Raring because it would cause the GTK package to depend on a Wayland package....
This is getting old.
I wrote two different build scripts, and most of the Wayland build instructions, to make compiling from source as easy as possible, and increase testing. I still think it's a pain that far fewer people are willing to go through than those who will install a binary package from a default archive.
[I switched from Ubuntu to Debian because of Ubuntu's Amazon ads.]
Ubuntu is not "other distros" and endless "testing" is not the goal of Canonical. They are not going to sacrifice stability or distributiion size for the sake of testers' convenience.Because shipping GTK with Wayland support will make it a lot easier for a lot more people to test, making it easier to make Wayland more mature and ready for general consumption. I think the process has already provided very useful testing which has found problems I think other distros would agree should be fixed.