Open Source Is Not a Democracy
itwbennett writes "A recent kerfuffle within the Ubuntu community serves as a reminder of an inconvenient truth: open source is not a democracy, writes blogger Brian Proffitt. 'The discussion started innocuously enough, within Bug #532633 in light-themes (Ubuntu) on Launchpad, where the order of the window controls within the Light theme were requested to be re-arranged to be on the upper right side of any given window. Light, it seemed, now placed the buttons on the left side, similar to the Mac OS X interface.' The discussion turned into an argument and culminated in this exchange in which Mark Shuttleworth lays down the law:
'It's fair comment that this was a big change, and landed without warning. There aren't any good reasons for that, but it's also true that no amount of warning would produce consensus about a decision like this... No. This is not a democracy. Good feedback, good data, are welcome. But we are not voting on design decisions.'"
Open source is utterly a democracy.
Each of us may have our own source tree. If we can convince others to come join us in it, isn't that fun. Those who come and join you are always there voluntarily, either because they feel like it, or you are payiong them to be there. And maybe no one feels like it. And maybe you don't feel like paying anyone. Maybe you are alone there. Maybe you didn't bother to make your tree at all. But you have that right to, at any moment. And this is utterly democratic, and it is at the heart of why open source exists. In fact, this is why it works so much better.
Shuttleworth has a very big, popular tree. He pays many participants and many others join him for free. He gets to make the decisions in his own tree, because it's his. He can't tell anyone else what to do in theirs.
Now if it's a Bill Gates product, and you do not like where those buttons got moved to, or i.e. you have a critical bug derailing years of your work, or whatever your issue may be, you will be ignored, or if you are very lucky, someone may even explicitly take a moment to personally tell you, "fuck off, peon." Your only real option is not to be so foolish as to use a Bill Gates product again in the future.
But in open source, if you so choose, you, or anyone, from the youngest child to Bill Gates himself, can fork Shuttleworth's tree, right then and there. Then you can have it your way. And if you are right, and people care, then people will join you and leave Shuttleworth out in the cold. It's happened many times before. And if not, then maybe your idea just wasn't that great, or that important, after all. Happens all the time. But the result, as with any democracy, is that leadership is largely consensual and generally merit-driven.
(All those who have never lived under a monarch, dictator, or cabal, please identify yourselves now with cynical comments about your democratic government.)
So I reiterate, as stories go, this is pure -1 Troll. IT World and Proffitt look like an 8 year old trying to say something "controvertial" about global warming by noting that it's snowing outside. I'm a bit sad that Taco rewarded them by sending them some traffic.
Tired of Political Trolls? Opt Out!
Is doomed to fail.
It is a Thoroughbred designed by a committee, or in this case a huge community. Good for Mark. Inputs are important but final design decisions should not be subject to a vote.
"TV, a medium as it is neither rare nor well done." Ernie Kovacs
Some time back, gaim had a UI redesign where they replaced protocol-specific icons with generic ones, in the decision that hiding the protocol is the right thing to do. A lot of us thought that was boneheaded, and some people forked GAIM, others wrote plugins to undo the change, and a lot of us offered harsh criticism of the developers responsible. If it were a democracy, we probably would've voted it undone. Right decision? Wrong decision? We didn't like it, but most of us decided not to walk away from it (either to the forks or further away).
Opensource provides new possibilities for governance - the ability to fork is something we don't really have in nations (splitting into bits really isn't the same), and with the exception of protocol decisions we generally can reshape our environment as we like (local patches, greasemonkey, etc). By having so much local variance possible, we no longer have our elbows so close to our neighbours and so there's less hazard for technocratic or autocratic decision styles (provided they use licenses that sustain this type of environment - some developers like Tuomo Valkonen prove to be batshit insane and play license games to compound their boneheaded technical decisions).
With licensing messes out of the way and the ability to fork, the most precious thing for us is mostly time/attention. If we want to fork a project, we're balancing our time and attention versus how much we care over the relevant issue. It's the easiest thing in the world to follow a path paved by the actual developer, while maintaining patches of any size (or starting a parallel community for a true fork) is an ongoing burden. If it's for an important enough reason, we'll do it. If that reason turns out to be not important enough to be worth the bother, all we can do is complain and hope to convince whomever is already doing that work to pave our path.
For every problem, there is at least one solution that is simple, neat, and wrong.
You make a lot of assumptions.
"The vast majority of users are right handed, and mouse right handed. Thus, the scrollbar is on the right side,"
Why do you assume mouse side on the right determines that putting scroll bars on the right is the most effecient thing to do?
And no 'It's obvious' doesn't cut it. Data only.
Why do you assume if the scroll bar is on the right , then windows on the right is more efficient?
"Putting it on the left for no good reason* just makes you have to mouse farther to accomplish the same task."
First, you are simple stating 'no good reason' without any backing. Strawman.
Second, what do you base where the mouse is most likely to be at any moment?
"* And no, "because Mac does it" is not a good reason."
No, but why Mac does it may be a good reason.
~~~ About your sig ~~~~~
heh, I love stuff like that. While they may have a good reason for doing it that way, claiming it's green for marketing reason crack me up.
After they give you your coffee, you should pout it from your mug into a paper cup. To make a point.
The Kruger Dunning explains most post on
The old metaphor is: if someone builds a nuclear reactor, it is left to the most qualified engineers. But if you build a bike shed everyone wants to have their opinion heard. I.e. if you want to change the way an IO scheduler or a pagefault handler works, only experienced kernel hackers will bother discussing it, but if you move around two buttons, everyone understand what you've done and wants to weigh in.
But honestly if you are an specialist in building bikesheds, you can never expect to be taken as seriously as those who build nuclear reactors. Someone just reconfigured Metacity to switch some buttons because they thought it was better that way, surely this feat proves that they are the experts here and their judgement should be deferred to.
Back when I regularly contributed to Gnome they switched the button order on dialog boxes, I actually liked the new layout but it was just personal taste, their was no objective improvement to be worth the enormous amount of bitching from the community. And in the end this will be the same, I will get used to this new layout, all that will change is a few indignant people will stop using Ubuntu and it will mainly serve to piss off anyone who borrows my computer.
In a way, the new button order makes more sense, maximise is the opposite of close and should be on the opposite side, but ultimately, it's just not all that important but it serves to attract a lot of attention and impact a lot of people's habits. Surely a software developer who has nothing better to change than this is hardly worth taking seriously.
When Argumentum ad Hominem falls short, try Argumentum ad Matrem