Has GNOME Rejected Canonical Help? Shuttleworth Responds
akgraner writes "When Canonical made the decision to make Unity the default desktop, some questioned the GNOME/Canonical relationship. Adding fuel to this fire was the recent distribution split of revenue generated by Banshee. These decisions caused the Ubuntu, GNOME and even Fedora community members to ask why these things were done. In Dave Neary's 'Has GNOME rejected Canonical help?' post, he states, 'I have repeatedly read Canonical & Ubuntu people say, "We offered our help to GNOME, and they didn't want it."' Neary gives examples in his post of what others have said to back up the 'they didn't want it' claim by Canonical and Ubuntu people. Today, though, Shuttleworth responds on his blog. 'Competition is tough on the contestants, but it gets great results for everyone else.'"
Shuttleworth notes to that end, "Weâ(TM)ve failed." He adds, "Much of the language, and much of the decision making Iâ(TM)ve observed within Gnome, is based on the idea that Unity is competition WITH Gnome, rather than WITHIN Gnome."
There was a story on The Register today on why Nokia failed. They had the exact same problem - teams that should be working together are fighting against each other and in the end just losing together. That seems to be a large problem in OSS community too, and it's no wonder Nokia had it too (they had many Linux developers). But when a software company, usually proprietary, is ran good, it doesn't suffer such problems as management makes good decisions and gives orders. That is why Windows works good and why the quality is consistent.
Some of us disabled users are looking for an alternative operating system for our Windows XP netbooks. The compiz magnifier is great, but GNOME is the _only_ desktop environment that has a screen reader. The GNOME screen reader performs _very_ slowly on a netbook though. It even runs slow on a modern system sometimes.
My point? Can we stop with the political issues and try to just produce the best, stable, reliable system we possibly can? Can we stop changing the underlying components every two years? Can we stop changing things that don't make the system any better (like notification bubbles that require more daemons) and fix what we do have?
Extremely Aerogant
This is between Unity and GNOME. Leave Windows out of it!
Competition is good, infighting is bad. People need to realize then they're on the same team.
also, this is not an odd "oops, we just didn't get around to it" event on the part of GNOME: how's that job D-Bus implementation in GNOME 3 coming? you know, the one that needlessly duplicates the one KDE implements, which we actually designed with thought of cross-project use including getting some feedback from non-KDE devs? or how about the screensaver D-Bus API which we implemented specifically with collaboration with GNOME devs at SUSE, only later to have GNOME not implement it and then complain to us that it used the org.freedesktop namespace? or how about how GNOME devs specifically blocked the formation of a common git repository for fd.o specs, and then when there was finally agreement (after an in-person meeting) insist on implementing it themselves, ignoring that repo had already been started but by people with @kde.org email addresses, and then after taking months to eventually duplicate that effort not implement the most critical part of it: the metadata?
Shuttleworth suggests that building development around FreeDesktop.org specs (as suggested by Aaron Seigo) is probably a good route to take, especially since Ubuntu is NOT just GNOME, but also KDE (Kubuntu), etc.
I heartily agree with that. I want to see Unity come out and kick butt, and it sounds like as good as GNOME Shell might be, GNOME people are forcing this into a you-vs.-us fight.
(It doesn't help to see Jeff Waugh being all complainy on Mark's blog, either.)
It's pretty clear that there are some massive egos/control-freaks within those running the GNOME project.
As far as user interfaces go, it is Havoc Pennington's way or the highway. Havoc has this crazy "usability comes from crippling" approach that dumbs down GNOME for entry-level users but makes it wholly unusable for power users.
Whereas KDE keeps "entry level" defaults and makes some of the niche/advanced configuration options (such as edge flipping) harder to find, GNOME's approach is to outright remove the feature. There are only so many features you can remove before your approach becomes unusable for many.
That's why I used to be a staunch GNOME supporter and fairly anti-KDE (I'm still not a fan of how they handled the Qt/GPL license incompatibilities, the issue didn't get resolved until Qt was effectively forced to change their license. The KDE developers had a consistent attitude that there was no problem and refused to take any approach to address), but have now pretty much changed over entirely to KDE. Around the same time the KDE license incompatibility issue was resolved is when Havoc began his reign of "cripple it in the name of usability" terror. Not only did the GNOME team remove edge flipping, they made it as difficult as possible to add it in after the fact (Brightside effectively broke after every GNOME release, and eventually GNOME broke the interfaces Brightside used to the point where the Brightside maintainer gave up.) It's always been there in KDE.
Yes, the KDE team has gotten a bad rep from KDE 4.0 getting shipped too early. I don't think there was any graceful way to do things here - there always comes a time when a project has to do a major rearchitecture, and sometimes that can't be done without some user pain. Later KDE4 releases are excellent. The key here is - KDE went through some pain in order to greatly improve the flexibility of the platform and leave them room to grow. GNOME didn't - in the short term that was good for GNOME, but in the long term that inflexibility is going to hurt.
retrorocket.o not found, launch anyway?
I don't know the details of how Canonical handled communications/relationship with Gnome, but I think we need to give some leeway to a business that is trying to pursue profit.
Let's remember, the vast majority of companies out there use open-source daily and give nothing back at all. Canonical has given back tons.
I've tried them both and GNOME Shell is sooooo much better than Unity. I really have been disappointed by many UI changes in Ubuntu in recent releases. All heralded as being great usability decisions.
Cleaning up the Status panel, by adding more clicks to get to functions... Why?
The notification system I just have never gotten used to. Why must I be notified of new IM's by seeing the IM text, but when I go to try to get rid of it, it fades out.
Perhaps their just not as good as "usability" as they think they are? Hardware that just works is different, they still are the best I've found in that category.
For GNOME Shell, I'm currently testing out Fedora 15 Alpha. They also now offer nightly builds so you can test without breaking your system (http://alt.fedoraproject.org/pub/alt/nightly-composes/).
Yeah, it's not as if all the vital pieces of a FOSS operating system are mainly developed and maintained by paid developers. Oh wait...
@Lennart: "If you list this notifier spec, then I can list you the sound theming/naming specs which KDE has shown no interest in."
:)
... simply to provide compatibility. would GNOME devs do that today? doubtful, because our priorities, as you point out, are indeed different.
that's an incorrect comparison.
if we (KDE) had offered a bunch of critique on the sound theme spec, had someone come to us with an implementation in Qt and then still gone off and done our own thing instead, then it would be an adequate comparison. but that isn't what happened, is it?
we (KDE) simply haven't gotten around to implementing the sound theming spec. why? as you note, it's not a high priority for us. but i guarantee you that if someone stepped up to do some work on the event sounds infra in kdelibs, stop #1 would be that naming spec.
also, this is not an odd "oops, we just didn't get around to it" event on the part of GNOME: how's that job D-Bus implementation in GNOME 3 coming? you know, the one that needlessly duplicates the one KDE implements, which we actually designed with thought of cross-project use including getting some feedback from non-KDE devs? or how about the screensaver D-Bus API which we implemented specifically with collaboration with GNOME devs at SUSE, only later to have GNOME not implement it and then complain to us that it used the org.freedesktop namespace? or how about how GNOME devs specifically blocked the formation of a common git repository for fd.o specs, and then when there was finally agreement (after an in-person meeting) insist on implementing it themselves, ignoring that repo had already been started but by people with @kde.org email addresses, and then after taking months to eventually duplicate that effort not implement the most critical part of it: the metadata?
in contrast, we could see how KDE implemented support for the visual notificatons D-Bus protocol as implemented in GNOME, even though it has evident limitations and is a 100% subset of something we already have in the form of KNotify
what GNOME needs is not more apologists making excuses for poor behavior but people who will stand up and take ownership of their actions.
Jesus had a UNIX beard.
I find it thoroughly ironic that this commentary issues from the head of an organization named Canonical. So does this mean that Canonical will shortly be changing its name? Will there be a contest - err, competition - with a prize to choose it?
Labor 15.oo dollars an hour
if you watch 20.oo an hour
if you help 30.oo an hour
metaphorically speaking: i bet the Gnome developers had something like this in mind,
Politics is Treachery, Religion is Brainwashing
As far as user interfaces go, it is Havoc Pennington's way or the highway. Havoc has this crazy "usability comes from crippling" approach that dumbs down GNOME for entry-level users but makes it wholly unusable for power users.
I'd most definitely stick myself into the power user category. I've been a GNOME user since 1.4, anything I do more than once has been scripted or bound to custom keys and I have Kupfer for the fast access to anything I can think of, including custom plugins for work-specific tasks. GNOME stays the hell out of my way and that's the way I like it. When I need to reach for something unusual, I can normally hook it via DBus or gconf.
Anything I post is strictly my own thoughts and doesn't necessarily have anything to do with the opinions of IBM.
I use Arch, so I'll always have the choice on exactly how I set up my desktop. Personally I don't see a need for Unity. I'll just use Gnome-shell when it comes out. Although I'm starting to see why some people in the FOSS community are starting to view Canonical in a negative light.
Hmmm... Sounds as if it's Canonical that wants GNOME's help, but some of the GNOME leads don't want to give it.
In any case, Canonical will likely do better to support and work with Freedesktop.org than tying themselves to a single desktop implementation.
At the end of the day, Ubuntu will succeed because it is well funded, and because it has something similar to the great virtue of Apple; a technically involved leader who has the final say on the user experience.
With all this bickering of rival interests, here's proof it wouldn't be the 'year of the Linux desktop' any decade soon. It certainly could be the 'year of the Linux phone', with Android steadily encroaching on other platforms.
And what's all this bickering over? Gnome and KDE (bring back kicker!) weren't fancy enough it seems, so now we have this meaningless 3D eye-candy that the average user doesn't give a flying crap about. // end rant
}
There was a discussion yesterday on webOS. A functional linux environment with an intuitive touch screen interface. I'm not sure if HP is pitching for world domination here but its plan to upscale webOS to desktops could actually succeed if they can pair the card-based UI with X11. As I understand it, webOS uses directfb on phones - primarily as a technical constraint that no ARM SoC has a working gallium3D-acclerated Xorg driver. Target an X11/Wayland backend on nvidia/ati/intel and instantly you gain the entire Linux back-catalogue. :) Any 'native' app on webOS uses SDL/OpenGL for rendering, so should be trivially portable, i'd guess.
Maybe it's just me but I'd gladly take a semi-proprietary UI deployed on millions of actual devices over some over-polished hotchpotch of ideas. One consistent minimalist but intuitive interface that runs on phones, tablets and desktops sounds like a great advance.. Oh darn, I think I just described the Apple vision. :) Long live Meego!
It's ridiculous to run a distribution that doesn't have package signing. Especially one that pushes out updates as frequently as Arch does. Arch's complete disregard for basic security measures is truly amazing.
I remember when a "power user" was someone who tweaked compile time options or applied a little patch. These days it seems that if there isn't an option right there in the UI then the "power users" aren't happy. They accuse projects of "dumbing down" but in reality I think it's (self proclaimed) "power users" who have dumbed down to the point that they see having to touch anything vaguely approaching the internals (such as gconf) an outrageous hurdle.
Yes, let's ignore the fact that Canonical's distribution has brought us millions of new desktop users.
Wonderful link! Mod this AC up; all of the GNOME-haters really need to read this before they make hasty assumptions that GNOME simply doesn't want to collaborate with Canonical.
"Our country is not nearly so overrun with the bigoted as it is overrun with the broadminded." -Archbishop Fulton Sheen
Linux: For Coders, By Coders
UI testing? Marketing? Working with OEMs to get it installed on desktops? Nope, apparently that's not contributing to Linux at all.
but... but.... my entitlement!
I suppose that you could look at it that way, although I think that the Canonical devs generally had good intentions when it came to working with Gnome. Either way, Canonical put Gnome on the map, and it still provides the bulk of Gnome users. Now the Gnome leadership has pissed the Canonical folk off so badly that they have basically created a fork, and worse, they've put most of their actual users squarely in the other side's camp.
Gnome 3 may be awesome, but how is anyone going to know. The former Gnome users are all going to be running Unity.
I suppose we will soon see. All I know is that I have put stock Gnome and Canonical's Gnome in front of real live people, and there is no question which they prefer (it's not stock Gnome).
I think that it is much safer to say that Gnome owes nearly all of its success to Ubuntu, and that when Ubuntu takes its developers, and more importantly it's end users, Gnome is going to become irrelevant. Sure, there will still be *some* people that use Gnome. Then again, there are apparently still people that use AfterStep.
Ah, those were the days.
Can we dig down to the root of the problem here? and that is, Unity can't even begin to compare to Gnome. imho, it's nowhere near as intuitive.
Well, if you hate the Gnome and Ubuntu interface changes, here's another. MS(huttleworth) has announced that the next (Natty) version of Ubuntu will have disappearing scrollbars. Basically, the Natty scrollbar will be a moving scroll button that only appears when you need to vertically or horizontally pan a window.
The so-called "overlay" scrollbars will be shipped in a special "liboverlay-scrollbar" package.
To be sure, there will still be a permanent indicator to show relative position within a window. But this narrow indicator, which kind of resembles the tube in an analog thermometer, itself won't be clickable. The blog post includes a video illustrating the concept. It looks cool, but I don't know how it will work in practice (how near must you be to the scroll indicator before the scroll button appears?).
I've been using Linux as my primary desktop since Redhat 7.2, so about a decade.
Noob ;-)
I'm a minority race. Save your vitriol for white people.
I'm wondering if the fact that contributions to Unity require copyright assignment going to Canonical has anything to do with the GNOME resistance to working with them on Unity.
Mark neatly does not mention this aspect of the division in his blog post.
1. Package signing certainly isn't a silver bullet in terms of package security. You're still trusting someone.
2. If you're that bent out of shape about it, Arch makes it insanely simple to roll your own packages from upstream sources. It is a one step process.
3. They're working on it anyway, if only to shut you up.
Hey, I finally got my first freak! Took you long enough!
I think the main mistake Mark made was to use GNOME in the first place. GNOME were always a "me too" desktop group who produce an inferior product from a technical and design point of view, it was just a matter of principle, and not technical, to create something that didn't use QT because QT was closed at the time. GNOME, Canonical - learn to collaborate and stop working in your elitist silos, use fd.o and discuss with everyone when a spec doesn't quite meet your needs because at the moment, GNOME especially, is behaving just like Microsoft by going off using their own specifications/standards. Perhaps we could rename GNOME to MSGNOME
"The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)