Slashdot Mirror
KDE and KOffice Rebuke OOXML, GNOME Dithers
Peter writes "Free Software Foundation president Richard Stallman and ITWire have praised KDE and KOffice developers for taking a principled stand against OOXML, while raising serious concerns about the GNOME Foundation's decision to give credibility to Microsoft's broken format. This comes on the heels of GNOME co-founder Miguel de Icaza's depiction of OOXML as a 'superb standard', and GNOME Foundation director Quim Gil's stonewalling of the patent-free Ogg Vorbis / Theora format on behalf of Nokia. Will the GNOME Foundation's indifferent response to Richard Stallman's appeal drive him to throw his weight behind KDE?"
No, he is on Novell's payroll.
Novell is on MS's payroll.
As was extensively explained in various GNOME places recently, Miguel is not GNOME, and has borderline zero impact or influence on GNOME at present (hence the best 'looks-serious' tag the author could find for him was "co-founder"; Woz was the co-founder of Apple, does that mean he's running iPod codec policy?) . Quim Gil is rather more directly involved in GNOME right now, but he also works for Nokia. He also clearly does not set Nokia's corporate policy. Therefore what he's doing on that bug report is reporting a corporate policy that stinks. This is obviously an uncomfortable position for him, but has sod all to do with GNOME.
Novell is on MS's payroll.
But the default desktop for SUSE Linux (owned by Novell) is KDE... So GNOME uses de Icaza who promotes Microsoft on Novell's payroll which ships KDE as the default desktop, but Microsoft has an agreement with Novell who has de Icaza on payroll and - Oh no, now I'm dizzy!
Gnome does *not* support OOXML becoming a standard. The *only* thing they are doing with it is trying to make sure that *if* and when it becomes a standard that it's good enough and open enough for Free software like Gnome apps to able to implement it. But they are *not* helping to get it passed.
Furthuremore, this crap article praises KDE for backing ODF implying that Gnome isn't. Of course Gnome backs ODF.
Finally, look for Jeff Waugh's comments in the comment section of TFA to see how it really is.
Free the Quark 3 from asymptotic confinement! Bring your charm! Don't get down! All colours and flavours welcome!
"No one likes working in a hamster wheel, and your shop smells of cedar shavings from here." - TaleSpinner
For the love of god, why don't people have balls(women excluded)? I'm getting tired of people bowing down to pressure or being bought out. Doesn't anybody stand up for what they believe in anymore? I mean, way to go KDE. But, Gnome? I mean, as a community aren't we supposed to stand up for the FREE as in FREEDOM we claim that open source is? I mean, this isn't just the Gnome community, I'm talking about the community as a whole. We need to stop OOXML. It's a big bloated piece of crap, shilled out at the last moment simply because MS saw a threat. But this rant isn't even about OOXML alone. Just now Ogg was kicked out of the HTML5 spec due to pressure from Nokia and Apple. I mean, WTF! Ogg was a great choice, good quality, free as in beer, and free as in freedom. The best of both worlds.
Anyways, I'm done talking.
With Linus preferring KDE, could Stallman's support put more weight behind KDE? I'm rather surprised that the GNOME Foundation's decision. They could at least have kept their mouths shut instead of praising OOXML, which severely damages their credibility in the GNU world.
Hydraulic pizza oven!! Guided missile! Herring sandwich! Styrofoam! Jayne Mansfield! Aluminum siding! Borax!
Not until KDE 4.1.
I am reminded of Henry Kissinger's famous quote: "Even a paranoid has some real enemies."
I appreciate RMS and his views. He is a pragmatic alarmist, he is playing the chess game that is computers several moves ahead of most people. That's why so many take his statements with a grain of salt, they don't see he has been "right," consistently, for over two decades, often years before the first real signs begin to show.
GNU/Linux and F/OSS have enemies. It is an undeniable fact. There are people working against us. One need only hop over to groklaw and see the black hand of Microsoft (and greed of course) guiding that whole thing. So, maybe we are paranoid, but even paranoids have real enemies.
I am really starting to believe that GNOME is a trojan horse, or at least some aspects of it. I don't trust Miguel de Icaza, he's either incompetent of a shill and he's potentially dangerous.
As a long time KDE user, I sincerely hope not.
My beliefs do not require that you agree with them.
I don't agree with the good job part but think about it. If MS switches over to OOXML and Linux can support it just as well as Windows who needs Windows? The same logic works with
1. KDE was good, but not free (Free? phree?) enough.
2. Gnome was established because we couldn't accept that un-free KDE?
3. KDE fixed its problems and Gnome became Microsoft's bitch
4. ???
5. Profit!!!
They want everyone to adopt to using their ooxml ball, but they keep giving it as a flat ball to everyone and only they can pump it up. Not sure what Microsoft wants, but they're not exactly playing with anyone.
Change is certain; progress is not obligatory.
Tune in next episode as exciting new revelations are unveiled!
... what Miguel de Icaza's obsession with shoving Microsoft technologies in to Gnome?
Is it to try and attract Windows developers to the Linux platform? Is it to ease transition from Windows to Linux? Is it to make it easier for Microsoft to threaten the entire community with patent infringement threats..? What is it?
THE HONOUR OF THE KNIGHTS - CC Licensed Sci-Fi Novel
Once upon a time, KDE was lambasted for using the not-Free-enough Qt libraries. There was a project to replace Qt and create a truly free KDE; but in the end, Trolltech released Qt under the GPL. And not the mealy-mouthed LGPL, like the GNOME libraries, which allows use in Caged software; but the full-on, not-sharing-is-stealing GPL. So the leeches still had to pay to use Qt in a Caged application; but if you played fair and wrote Free software, you could use Qt with the blessing of the copyright holders. (This didn't please the Windows fans. Windows users, raised on a diet of "illegally copying the Software is my way of Sticking It to the Man, and if you don't pay me $49 for this crapplication to do something petty that Unix has had since forever that I built with my pirate copy of Visual Studio, I'll turn off saving and bring up nag screens every five minutes", bitched loudly that there was no GPL Qt for Windows -- but the only thing stopping them porting it was the fact that the average Windows user would rather drown in shit than make the effort to swim.)
Now, the "freedom" to write Caged applications is a thorny issue. But I see it like this, and I'm sure RMS does too: in a nation where the ownership of slaves is forbidden, citizens tend to be freer on average than in a nation where the ownership of slaves is permitted. So KDE are actively promoting freedom, by taking a stand against OOXML. Novell and GNOME and Mono are getting rather too cosy in bed with Microsoft for comfort. It's very hard not to think about Microsoft pulling some kind of bait-and-switch operation which would put OSS users in trouble. If this happens, I think it's actually more likely that the Governments of the world would just pass Enabling Acts to annul whatever IP Microsoft are trying to abuse; but that's still a waste of taxpayers' money that doesn't have to happen, and by the time it gets to that stage the damage (in terms of unopenable public and private records) will be severe.
Not everyone is as responsible a citizen as you. Just because you're paranoid doesn't mean that they aren't out to get you, and just because you don't understand the importance of having access to Source Code doesn't mean it isn't every bit as big a deal, in its own right, as slavery.
Je fume. Tu fumes. Nous fûmes!
yes, KDE purposefully linked GPL licensed code to QPLv1 code. however, it was THEIR code which means that they were fully within their rights to do so. anyone building apps on top of those libs implicitly agreed as well.
linking someone else's code would be an issue, and in the 2 cases where that happened it was rectified as soon as it was brought up; it's also useful to note that those 2 cases were small code fragments, not significant bodies of work, and as such certainly not evidence of a willfull plot or some such thing. they were oversights, and corrected in a timely manner without fuss.
and this was what, getting to be 10 years ago now? today we have nice clean GPL'd (or "better") code on every platform we support. let's find some new issues to grind over. =)
- GNOME (and Novell) do not support the standardisation of OOXML. They are both members of the ODF alliance, both use it as the default file format, and if it was even remotely realistic to have a decent office product without OOXML support (where the Windows desktop is unfortunately in such an insane over-dominance currently), then they would of course be all for it.
- The implementation of OOXML is all about interoperability. I don't see anyone (wrongly) trashing Samba as a project, and yet its existence and the effort to implement OOXML support is virtually identical in terms of free software.
- You like software freedom and hate the software patent system? Great, so do I. Free implementations of proprietary solutions, though, are a good thing; not a single one of my friends are going to be using Linux if they can't submit their assignments to their lecturers. We need interoperability, to ease the transition for people coming from the proprietary world.
- The KDE/Koffice developers issued a statement basically saying they didn't have the resources or the time to implement OOXML, and suddenly a lot of silly talk gets thrown at GNOME. If I volunteered to implement OOXML support in Koffice I doubt (i) that they would object, and for sure that (ii) any distribution would not include it.
- Even if you dislike Jeff Waugh, it's pretty tough to find a rational basis for criticising him based on the podcast or his approach to the problem other than (i) not getting the GNOME statement (again, which you really can't fault) out soon enough, or (ii) giving Roy the publicity he wants.
- The itwire article plays Roy as some sort of victim in the podcast talk. That is ridiculous. Unfortunately -- and to the detriment of the FLOSS community -- Roy is an incredibly prolific, poisonous person willing to do or say anything that might cook up some self-publicity, and with an irrational hatred of Novell. And in fact on the contrary, Roy skipped around every question that was directly asked to him; instead opting to just give background on Microsoft's "evil" nature and talking about how bad OOXML is (both of which we palpably know).
- Finally, even if you decide to ignore all the other above facts, please tell me why you're not also staging wide protests against OpenOffice.org or your distribution for including OOXML support, as well.
To save any comments of bias, I'm an ardent KDE aficionado.Bill's married. It will never work.
My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
The problem is that what you characterize as "infighting" isn't really. Let me draw an analogy.
Suppose you have a sports team, let's say football (it doesn't matter which type). We have a game between team A and Team B. Team A is pretty decently organized, and works fairly well together. Team B has some problems, however: one player is constantly starting fights with other players on his team, and frequently recruits others on the team to his faction to help in his fights with the other factions. Consequently, the team does very poorly in the competition because they're always "infighting". But then it's discovered that that one fight-starting player is actually being paid, under the table, by Team A just to stir up trouble on his team!!! So is it really infighting? I'd call it "sabotage" instead.
This is exactly what's happening with open-source, specifically with GNOME and Miguel de Icaza. He's really an agent for Microsoft, in some way. It's not clear yet whether he's actually being paid off by them, or if he's just a willing stooge who loves them so much that he's lost his grip on reality. It doesn't matter either way, though, because the effect is the same: it factionalizes open-source and creates problems, helping MS.
Personally, I think open-source projects need to cut him off altogether. When you have gangrene in one of your limbs, you amputate it before it spreads. If GNOME isn't willing to throw him out, then GNU needs to drop support for GNOME, and all other open-source projects do too. They need to stop the cancer before it spreads.
It seems to me that a mature approach would be to simply acknowledge the differences and you what you think the best tool for the job is. And just because the support might be there doesn't mean you will have to use it.
It's not that simple: this is an issue of standards. When you're dealing with standards, and creating and promoting a standard, you're inherently rejecting the idea of letting people decide what the "best tool for the job" is, because you're trying to make them use a specific tool, so that they can interoperate. What good would it do me to make up my own graphics format and editing tools, for instance, if I can't use the resulting images anywhere or send them to anyone? I can use them for myself, of course, but for things like that, it's a lot more useful if I can also exchange them with others, and because it's a popular standard, they have no problem using these files.
There's a big fight right now between ODF and OOXML. People (especially large organizations) are finally seeing the value of open office format standards, and XML-based ones which they can view or edit with tools other than the word processor or spreadsheet which created them. The whole world has been suffering with MS Office's closed, proprietary, binary-only formats for many years now, and they're ready for a change to something more like PDF or JPG, which can be viewed or edited with lots of different, competing tools. (It's also very useful to have an XML-based standard so that information can be easily extracted, such as for web searches. Google could easily spider and index XML-based documents on the web, whereas doing that for MS's proprietary formats isn't so simple.) But MS doesn't want people to switch to an open standard; they'll lose their proprietary lock-in, and consequently many MS Office customers. So they've intentionally confused the issue by making up their own XML-based "standard", OOXML, which isn't open, and basically serves as an XML wrapper for closed, binary data so that competing software still can't be 100% compatible.
Diversity and uniqueness of different open-source projects is a good thing as you say, as people can pick what works the best, but they're not shut out of anything because it's all open (For instance, I use KDE normally, but I can still use GNOME programs because it's all open-source; I'm not locked out of either by choosing one). But that's not what we're talking about here. We're talking about an open standard vs. a closed standard. If the world chooses the closed standard, then we're right back where we were with a decade or more of MS Office dominance, and no other tool being 100% compatible, so we're all forced to use MS Office just to be compatible with everyone else. No thanks.
You are missing the big point here: open vs. closed standards. OOXML is taking a back-seat to ODF more and more, so MS is trying to screw things up and push OOXML through ECMA, etc. (which is just a rubber-stamp agency), and all the despicable things they did with the ISO trying to get it passed as an ISO standard (which finally failed when their shenanigans were exposed).
If GNOME supports OOXML, this just muddies the waters even more. It's a blatant move by MS (using covertly-paid henchmen) to fracture the open-source community.
We already have multiple national governments adopting the ODF standard (which truly is an open standard); the last thing we need is the stooges at GNOME slowing this process.
Miguel may have been a founder of the GNOME project, but he is not even on the GNOME foundation board anymore. His opinion matters no more than that of anyone else who contributes code to GNOME. Though he has written some excellent software his baffling statements probably with respect to OOXML will not likely be taken seriously.
RMS is worried about compromising on principles of Free software by putting efforts into making software that reads or writes this technically and philosophically nasty format. Since when has AVOIDING interoperability furthered the spread of Free software? Linus has yielded to pragmatism many times in the past (using BitKeeper for example, and being cautious about GPL3) whereas RMS remains steadfastly rigid in his ideals at all levels. RMS' stance is admirable, but look at where the Linux kernel is...then look at how far the HURD has come in comparison. Perhaps some pragmatism isn't always a bad thing?
Now, as far as compromising "principle" with the pragmatic decision to work on making GNOME read the OOXML format, where exactly is this a more serious concern than with countless other interoperability projects? What about the work that went into making NTFS mountable in Linux? What about the Samba project? What about the ability of OpenOffice, KOffice, AbiWord, GNUMeric, etc. to at least partially support Microsoft's legacy binary file formats already? Where do we draw the "principled" line here? Microsoft's "core dump" binary formats, NTFS file system, CIFS and the Active Directory are not proper open standards yet great effort has been made thus far to reverse-engineer and deal with them so as to break down the Microsoft lock-in. How come, all of the sudden, RMS has to chime in about OOXML and now suddenly we should all ignore it on principle?
Perhaps the KDE people should become even more principled and drop all the hooks it has with Samba to browse and be browsed on Microsoft's "network neighbourhood". Perhaps Linux-based OSes should not only all drop GNOME as the default desktop, they should also drop the ability to mount NTFS volumes too. After all, if we're gonna snub OOXML because it's crap and it's closed, then we should be consistent and do the same across the board.