01.04.11
Gemini version available ♊︎As India Picks ODF, Novell-Microsoft Influence in LibreOffice Raises Questions (the Unfortunate ‘Go-OO Factor’)
Summary: Novell staff is said to be pushing for OOXML write support in LibreOffice just when ODF becomes a standard in more and more large nations
Techrights is a supporter of LibreOffice because it is willing to believe that — as promised to us personally — the project is not steered by Novell employees. Last night in IRC one of or readers raised some concerns about what goes on at LibreOffice and its umbrella organisation. There is active discussion about it in Twitter and in Groklaw. If there are blog posts or articles about it, then we have not come across them yet. The short story is that OOXML write support becomes a controversial subject for all sorts of reasons, some more justifiable than others (and some are fictional). Charles from LibreOffice has kindly responded to us about 3 times already, denying all of the allegations (more on that in Twitter).
For those who are not familiar with this debate, start here in an IRC log from last night. This came at the same time as the news about India going with ODF, which is a fantastic development. To quote a Red Hat employee:
Here is some good news to kick off the new year. As a follow-up to the Policy on Open Standards for e-Governance, the Department of Information Technology has published the “Interoperability Framework for E-Governance in India (IFEG).”
The draft of the IFEG lists out the standards approved for e-governance in India. The last date for comments on this draft is 27th Jan 2011.
The current concern is that Novell, which was paid handsomely by Microsoft, may continue pushing for OOXML. We wrote about this last month and this question returns not just due to discussion in Groklaw but also because IBM’s Rob Weir writes that the “Document Foundation debates OOXML support in LibreOffice. With freedom it is hard to be only half pure. http://bit.ly/hjPqMU”. The FFII says: “A user is concerned about #LibreOffice #OOXML write support http://comments.gmane.org/gmane.comp.documentfoundation.discuss/3058″
As Weir added: “Half-pure is starting with the goal of being independent of a Oracle, but then doing what Microsoft is paying Novell to do.”
“Half-pure is starting with the goal of being independent of a Oracle, but then doing what Microsoft is paying Novell to do.”
–Rob Weir, IBMAs a result of this, Weir comes under another pressure offence from Microsoft, over ODF. He is having a long powwow (about 30 tweets back and forth) with Microsoft employees and also boosters like Jesper Lund Stocholm, starting with messages like this one which says: “if OSS doesn’t add support for OOXML, .NET, XPS, SilverLight , etc., then they’re “detroying your ability to choose”?”
It’s like Microsoft speaking using a peripheral person, Jesper. They spin OOXML as “choice” again. We’ll probably post a little more on this subject at a later date. A lot of it is in Twitter and in our IRC logs. Maybe it’s just a manufactured controversy, it’s still hard to tell without a lot of research and personal queries. There is more in Groklaw comments and interestingly enough, a longtime supporter of Groklaw, Brian Proffitt, opines that Groklaw should open up to more people:
The problem is that in the short term, Groklaw’s mission (stopping SCO from hurting Linux) has basically succeeded. Yes, there are pending appeals from SCO, but Jones is concerned that any efforts to continue the fight against SCO will only serve to help companies like Novell. Other suits are out there, but right now the community interest for those seems to be waning. And, I suspect, Jones’ own interest might be waning: she has been at this since 2003, while facing several personal attacks along the way. The potential for burnout has to be very real.
When one person, any person, gets so wrapped up in something and then has to deal with the lack of that issue in their lives–even if they have won–it has a profound effect.
My most constructive suggestion would be for Groklaw to become a more community-run site. Instead of being a strictly one-person show, perhaps a shift to a more collaboratively run organization is possible. There is precedent: Linus Torvalds is still leading the Linux kernel development, but over the years he has delegated a lot of responsibilities to the various kernel maintainers. Surely there are those in the Groklaw community who could step up and fill similar roles for Groklaw.
I believe this approach would enable Groklaw to dedicate more time to covering all of the different legal issues surrounding FLOSS these days. In effect, it would become a meta-blog, like Huffington Post, or Engadget, or what have you, with a focus on FLOSS legal battles.
Change isn’t easy, but it can be an opportunity to do something bigger than you had ever planned.
The whole post is very thought-provoking and it has attracted Microsoft mobbyists too (libel and crazy theories in the comments). █
Addendum: As this post comes into publication time Charles posts this rebuttal in his blog. He also told me: “I think it might be #Oracle trying run some brainfuck here. Oracle more #FOSS than #LibreOffice? Who does benefit from this?”
ᶃ Gemini Space
This post is also available in 
Content is available under CC-BY-SA
twitter said,
January 5, 2011 at 2:29 am
Mark Preston has a good write up of the choices faced. The core issue is Microsoft acting in bad faith and the futility of trying to implement anything by people who are out screw everyone else. He puts it this way:
I agree that chasing Microsoft’s tail is a waste of time. There’s not much new about this except Microsoft’s relative weakness and the fact that no one is using OOXML.
The rebuttals have a Novel/Microsoft stink. This is especially true of Charles, who defends his position by dismissing other opinions as, ” inaccuracies”, “outright bullshit”, “rumor”, “ignorance”, “the complexity of the matter [aka, you are stupid]“, and “the urge to have a soapbox” promoted by “people who do not know how to contribute to Free and Open Source Software Communities, do not even want to learn but only want to stand on their soapbox and shout whatever they will please.” Vignoli makes the point that his little club is not for people who don’t trust Microsoft, “If you share the idea of being AGAINST Microsoft, TDF and users, then we are happy if you choose the OOo community.” False choices and arrogant insults from people who assume that Microsoft is the center of the universe and that everything Microsoft does must be aped because it will be the next “standard”. This are the same talking points handed to us by the Mono people, Go-OO people and other Novell “engineers”. No thanks.
Reasonable people will simply wait and see if anyone ever starts using OOXML before wasting time and effort on it. OO.org in squeeze is greatly improved and KDE’s Office suite is also good for the purpose. Free software users have no problems in this department. It’s a truism that the free software world is so large that there’s someone who enjoys doing every task that most people hate with a passion, but implementing OOXML may be an exception to that. I can’t see anyone besides people paid by Novell bothering to implement Microsoft’s insane new file formats.
Dr. Roy Schestowitz Reply:
January 5th, 2011 at 2:48 am
I forgot to include in my original post Weir’s contention that OOXML write support is not needed because almost nobody uses ‘OOXML’ (Office 2007 pseudo-OOXML); people use Office binary formats and we need to move them towards ODF. I value Weir’s take on it as he’s not from OOo, either.
TemporalBeing said,
January 5, 2011 at 1:40 pm
I quite agree. There had been a somewhat interesting discussion on the TDF-LibreOffice mailing list. Charles came off better than the others, but they all were pretty pissy about the issue saying that write support was a must, even in the face of at least as many people (myself included) that read support should be all LibreOffice does.
There are organizations out there (like the parent of my employer) that use OOXML-based documents. However, I always convert them back to standard DOC/XLS/etc before sending any replies.