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.
Canonical and ubuntu ran a train on the gnome guys and then were surprised gnome didn't want help from the same people who had just screwed them over? Well I'll be dipped....
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?
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 know at least one .png has floated a png showing unity as a design inspiration. This is not true, the screenshots are undated for a reason!
http://www.markshuttleworth.com/archives/611/comment-page-1#comment-345769
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
From what I've seen of Canonical's strategic direction, it is little wonder that GNOME doesn't want their help.
I can't say that I blame them really.
To a considerable degree, Ubuntu succeeds in spite of itself.
A Pirate and a Puritan look the same on a balance sheet.
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.
No interest in taking sides in this, but certainly my *perception* of GNOME, and especially "GNOME on Ubuntu" is a long way from flattering towards either.
File a bug against a GNOME component in Ubuntu, and 99.9% of the time you know what BOTH parties' responses are going to be: Ubuntu will push it upstream and ignore it; and the GNOME devs will either reject it and pretend it's deliberate, or ignore it if that's too brazen even for them.
I don't mean "I want Thing X to be Color Y" non-bugs; but real, crystal-clear, user-facing, "even the app itself says this is a bug" bugs.
Given that sort of attitude to bugs, I can see features being cared about even less (regardless of any merit they might actually have, which appindicator is a pretty weak claimant to, especially since the design is mediocre and the scope/impact so unbounded; but the same would hold even if it *did* have merit) so when such a feature is the pet project of someone "senior" at Canonical, it's not really surprising that both sides will try and spin things to blame the other.
In an ecosystem like that, collaboration is next to impossible. So yet again, an entire desktop gets thrown away rather than fixed / improved, and Something Else is started from scratch so one side has the level of control they want, condeming us to another 5 years of a half-assed front end, and the never-ending chant of "NEXT year will be the year of Linux On The Desktop (tm)".
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.
A neutral observation and a summary of the whole GNOME vs Canonical, freedesktop.org is available at:
http://psankar.blogspot.com/2011/03/gnome-vs-canonical-freedesktoporg.html
Covers about the blog posts from Dave Neary, Aaron Seigo and Mark Shuttleworth and adds the Author's opinions in the end.
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.
Yeah AC and you are coming off as a former user with a vendetta.
What's your game? Can we have one tech-related story that does not have a Microsoft Apologia as the first post from you?
I'm also deeply suspicious of the moderation your comment received. Aside from being wrong and ill-informed, your comment is waaaaay off-topic and should have been modded that way.
Lemmee guess... New hire? Still impressed by the cafeteria? Brownie points for "developer outreach"? It's really just one step away from spam, and unless you start your comments with "As a Microsoft employee...", it's dishonest.
Spam away, but at least put your cards on the table as the other Microsoft-employed slashdotters do.
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.
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
A lot of people have discussed the time and effort wasted in having two desktop environments for Linux. They were especially vocal when KDE 4 was unstable.
I've been using Linux as my primary desktop since Redhat 7.2, so about a decade. For most of that time I have preferred Gnome. I find myself more productive under it, and I like the customisation Compiz offers me.
But the looming advent of Gnome 3 and Unity has had me spending a lot more time in KDE. And I'm really liking it. Scrolling the mouse wheel on the wallpaper in Unity does not switch desktops in Unity, but it does in KDE. I even have my familiar cube. I feel quite at home. And of course no stability issues.
My nine-year-old daughter likes Unity, but my PC has a dual-head display and having a window on one monitor and it's File menu on the other doesn't work for me. So from April I expect I'll be dual-booting KDE 4 and Gnome 3, and I won't be disappointed if most of my time is spent in KDE.
but... but.... my entitlement!
Having multiple competing platforms is not a problem per se, even within a single company; failing to execute and deliver on all of them in a timely fashion is a problem.
Or, you know, like someone who expects his software packages to be signed...
(And before you say anything, I don't think I have even been closed to an Arch package much less used the thing)
Any blog post purporting to be a "neutral observation" from a person with an obvious vested interest in the topic he discusses is dismissible on it's face. It's just the same hokum advancing an agenda from the one side that the author supports.
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.
I've never understood the appeal. Installed it a year or so ago and went running straight back to Slackware.
That's so true. Someone in the tech press really needs to probe the agendas of the small cabal of people calling the shots for Gnome at the expense of the larger community of users and developers.
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 on the other hand AM a former Arch user who got burned by their complete and utter disregard for stability and security. I run Debian now.
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.
At last. Ayatana Indicators, now I know the name of my enemy. Those ghostly things are irritating like hell.
Since introduced in Ubuntu, those buggers have annoyed me to no mean. They provide, usually, cryptic messages and you can't click on them to get more details, and you can't copy the message and do a web-search for it (wouldn't do much good either in my case, my desktop is in "Swedish", or at least that horrible, retarded, mess that GNU gettext claim is Swedish(*), the chance that someone from the small Swedish language user base to have posted something relevant is near non-existing, I would prefer some kind of complementary inter-lingual message codes, Microsoft do this right, then I wouldn't have to try web searches in several different translation (possibly using the wrong wording) to several different languages, to find if someone has posted something useful on the web about my particular predicament). Sometimes the applications that pop up those messages provide an icon in the system tray, that you can click to get actual helpful information, the trouble is you don't know which icon, if any, is related to that damned elusive Ayatana message, there are no clues provided.
May I propose an improvement to the Ayatana indicators. Provide a clue to where to find more information about what they mean. You could have some kind of message log application (one whose icon pop up in the system tray when an ghostly Ayatana message appear) that can provide more information about what just happened, perhaps the same icon could appear in both the ghost-message and in the log entry. to provide a visual clue.
(*) Unlike what the creators of GNU gettext think. You can't translate an application, word by word, or sentence by sentence, often enough not even paragraph by paragraph, without any context. Other natural languages are not carbon copies of English in structure and word meaning, they are not like Pig Latin (thankfully, English is a horrible language, the only language I really hate (if you're curios of my taste in languages, I have also a dislike for French, Plattdüütsch (and all dialects in other languages to much influenced by the, now thankfully not used, Hanseatic German (the only other language I understand that is as, inexpressive, pointless and without any good qualities as English)) and spoken Danish, but I acknowledge that even those languages have, unlike English, some very strong points)). A translation of a word, sentence or paragraph doesn't change meaning, when moved between contexts, exactly the same as the English counterpart. In a perfect world (that would actually be Apple's Cocoa) you would be able to not just translate words of an application, but also adjust functionally and visual appearance to fit the logic and strong points of a local language.
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!