05.07.08

Gemini version available ♊︎

What Does the LGPLv3-Licensed OpenOffice.org Mean to Novell, Xandros, Linspire and Turbolinux?

Posted in Fork, GNU/Linux, Linspire, Microsoft, Novell, Office Suites, OpenOffice, Turbolinux, Xandros at 11:03 pm by Dr. Roy Schestowitz

Stuck in 2007?

FSF GNU GPLv3As stressed many times before, IANAL, but based on the consensus of opinions in Groklaw, the GPLv3 is bound to bite companies that sold out to Microsoft in the rear. Several of these companies knew very well what they were getting into, or maybe they just weren’t concerned. Here is a lovely old quote from the CEO of Xandros: (highlighted in red)

Under the third version of the General Public License, expected to be published in final form this month by the Free Software Foundation, all such deals that were not inked by March 28 are forbidden. As a result, it would appear that Xandros will not be allowed to distribute open source code licensed under GPLv3 because of its relationship with Microsoft. Typaldos said he’s not concerned. “If you are a businessperson, you can’t worry about every eventuality.

Priceless. To quote another old article which was discussing Microsoft’s scam at the time:

Then Microsoft offers the carrot of legal absolution. “Come with us” they say “We will protect you and your customers from our lawsharks” they promise. The poor scared sods believe them and sign a piece of paper that they think will protect themselves from the “Big Brother”. This of course makes Microsoft very happy and fits right in with their divide and conqueror plans.

GNOME CalcSam Varghese was a little more blunt when he advised Andy Typaldos to start selling potatoes rather than selling out. In any event, what does the licence upgrade of OpenOffice.org mean to he likes of Xandros?

It is a good time to raise this question because OpenOffice 3.0, which adopted the third version of the GNU GPL, has just been released as public beta. You can find some more details here.

The OpenOffice.org Community is pleased to announce that the public beta release of OpenOffice.org 3.0 is now available. This beta release is made available to allow a broad user base to test and evaluate the next major version of OpenOffice.org, but is not recommended for production use at this stage.

The LGPLv3, especially in the context of Novell’s OpenOffice.org controversial ‘fork’ for SUSE Ballnux, was discussed before in [1, 2, 3]. Can Novell carry on doing what it does? If so, at what cost?

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

21 Comments

  1. Gopal said,

    May 8, 2008 at 12:05 am

    Gravatar

    Michael Meeks of Novell does not seem to be concerned about the OpenOffice move to LGPLv3. See comments on his blog – http://www.gnome.org/~michael/activity.html#2008-03-06.

    I am more interested in the implications this move will have on StarOffice which shares the same codebase as OO, given that StarOffice is “protected” by the Patent Covenant agreement between Sun and MS. (see http://www.sec.gov/Archives/edgar/data/709519/000119312504155723/dex10109.htm )

  2. Gopal said,

    May 8, 2008 at 12:06 am

    Gravatar

    corrected link for Meeks
    http://www.gnome.org/~michael/activity.html#2008-03-06

  3. AlexH said,

    May 8, 2008 at 5:39 am

    Gravatar

    Novell’s “fork” isn’t a fork, and it’s not controversial; why do you keep raising this?

    Virtually all the distributions use the go-oo / GNOME hosted version, including the likes of Debian (http://packages.qa.debian.org/o/openoffice.org.html – see the “version control” links on the left).

    The only reason this different version exists is because of the cack-handed maintainership of OOo by Sun, who won’t accept LGPL’d licensed code without a copyright assignment so that they can produce a proprietary version.

    This site does seem to have a real pro-Sun bias even in areas where Sun is actively harming the free software community…

  4. Roy Schestowitz said,

    May 8, 2008 at 5:57 am

    Gravatar

    I was never pro-Sun, but I’m receptive because Sun hardly attacks Free software, not in any way that’s akin to Oracle or Microsoft. Sun also gave Free software some valuable gifts, much like the BSDs.

    There’s also the other side of the story you tell. Follow the links to our previous coverage of this ‘fork’ (mind the scare quotes, which are there for a reason). Sun got a lot of flak at the time and the story was complicated for various reasons including the involvement of Novell^H^Hrosoft, which adds stuff like OOXML because it must. Microsoft paid it to harm ODF; unsurprisingly, ODF supporters like Bruce Lowry left the company, possibly for other reasons or a combination of them.

  5. AlexH said,

    May 8, 2008 at 6:21 am

    Gravatar

    Novell isn’t adding OOXML to OpenOffice.org; it hasn’t upstreamed its changes for the XSLT filters and as far as I know it doesn’t plan to, because *Sun’s engineers are working on OOXML support*:

    http://wiki.services.openoffice.org/wiki/OOX
    http://wiki.services.openoffice.org/wiki/Documentation/FAQ/General/OpeningMSO2007Files

    This is already integrated and will be released in OpenOffice.org 3.

    Far from Novell being obligated to add OOXML support; they’ve probably spent all of a couple of weeks integrating the filters that Microsoft developed. The real work for OOXML support natively in OpenOffice.org is being done by Sun.

  6. Victor Soliz said,

    May 8, 2008 at 7:26 am

    Gravatar

    The only reason this different version exists is because of the cack-handed maintainership of OOo by Sun, who won’t accept LGPL’d licensed code without a copyright assignment so that they can produce a proprietary version.

    Note that under rules established by Novell apologists, this argument is only valid to attack Sun regarding OOo and cannot be used on Novell regarding Mono which is a totally different subject…


    The filters Sun is working on are just importers, no worries. Besides, they happen to have done it after the ISO vote, unlike Novell and Gnome which advocated OOXML during the vote. I hope the difference is noticeable…

  7. AlexH said,

    May 8, 2008 at 7:38 am

    Gravatar

    @Victor: No, I don’t advocate copyright assignment to Novell, for Mono or any other project. I treat the two exactly the same. At least with Mono’s class libraries, though, Novell aren’t reserving the right to make proprietary versions to themselves – unlike Sun.

    As for what Sun are working on – if you think they started this _after_ the ISO vote, you’re wrong. Look at the dates on any OOXML bug, eg.:

    http://www.openoffice.org/issues/show_bug.cgi?id=75573

    And indeed they are only working on opening OOXML files. Given it can save in the binary format there isn’t much value in being able to save in OOXML until they get importing working well.

  8. Roy Schestowitz said,

    May 8, 2008 at 7:37 am

    Gravatar

    Alex, I appreciate your insightful comments, but I disagree with this last one. OOo developers at Sun have been strongly objecting vigorously to OOXML (Sun still does, boycottnnovell was even cited at the front page of openoffice.org) and to say “Sun’s engineers are working on OOXML support” is only a half truth at best. What they strive to have is something that enables OOo users who receive binary/XML spew (Office 2007 documents) to translate these and store them as ODF.

  9. Roy Schestowitz said,

    May 8, 2008 at 7:41 am

    Gravatar

    Alex, it hasn’t been news. The importers go several months back. To argue that Sun supports OOXML is like arguing that I support Windows if I sometimes need to lean over and help a colleague/friend/family member with a technical glitch in Windows.

  10. AlexH said,

    May 8, 2008 at 8:30 am

    Gravatar

    I’m not saying it’s news, I’m not saying Sun support OOXML – I’m saying it’s not Novell who are the people adding OOXML support to OpenOffice.org.

    You keep missing the salient points I’m raising:

    * Novell’s OOo isn’t a “fork”, it’s a maintenance branch
    * Novell’s OOo is used by all the major distributions, it’s not a SUSE-only thing.
    * Novell’s integration of the OOXML filters was a hack, and will go away when Sun complete their support ( http://lists.go-oo.org/pipermail/dev-go-oo.org/2008-January/000279.html )

    We’ll soon see about Sun’s intentions for OOXML, anyway. The ‘unable to save as OOXML’ bug was raised in the issue tracker last month:

    http://www.openoffice.org/issues/show_bug.cgi?id=88355

    As I said before, Sun are the ones spending time on OOXML support. Novell spent only a few days or weeks on it, not months of development time.

  11. Roy Schestowitz said,

    May 8, 2008 at 9:32 am

    Gravatar

    Novell has actively supported OOXML (in the form of translators) since almost the end of 2006. Microsoft has used that as ammunition everywhere. I say this because I saw it.

  12. AlexH said,

    May 8, 2008 at 10:03 am

    Gravatar

    “Active support” should be judged in terms of actions, not words.

    Novell’s actions with regard to the translators is a. making them work on Linux (which was a trivial piece of code for reading Zip files, IIRC) and b. plugging them into OpenOffice.org (which already had facilities for XSLT import filters). Indeed, so deeply entrenched in the ODF-Converter project are Novell hackers that they don’t even seem to know which mailing list to subscribe to:

    https://sourceforge.net/mailarchive/forum.php?thread_name=46FBDE27.773E.0028.0%40novell.com&forum_name=odf-converter-devs

    It’s painfully clear that Novell are not active in the converter project, and made only the smallest effort to make them work with OpenOffice.org, and further intend to undo those efforts when the much more substantial work on *native* filters is complete for OpenOffice.org 3.

    Actions speak louder than words, and I know which of Novell and Sun have invested more in OOXML support for OpenOffice.org, by a long chalk.

  13. Dan O'Brian said,

    May 8, 2008 at 10:09 am

    Gravatar

    Roy, that’s not what Alex H is arguing. He’s not necessarily disagreeing with you that Novell supported OOXML – he’s not making any statements regarding that subject at all.

    He’s neither agreeing nor disagreeing with that assertion.

    What he is saying is that Novell is not forcing OOXML into OOo, Sun are doing all of that themselves.

    Alex H is sticking to the facts.

  14. Roy Schestowitz said,

    May 8, 2008 at 10:24 am

    Gravatar

    The original question was: who assists(/ed) Microsoft’s pursuit for the rubber stamp? Another secondary question would be about the type/level of support by Sun.

  15. Dan O'Brian said,

    May 8, 2008 at 10:25 am

    Gravatar

    Playing Devil’s Advocate for a second here, there is quite a difference between Novell requiring Copyright assignment for Mono and Sun requiring it for OpenOffice.org.

    Sun only contributes about 40% of the work on OOo while the other contributors put forth the remaining 60%.

    Novell puts forth about 99% of the work on Mono, while the remaining contributors put forth maybe 1%.

    Point is that Novell are doing nearly all of the work on Mono while the community (paid or not) does more work on OOo than Sun does.

    That said, I personally don’t care about having to assign copyright to either company were I to contribute to either project – it’s their projects and they need to make money too.

  16. Roy Schestowitz said,

    May 8, 2008 at 10:33 am

    Gravatar

    It would be interesting had OpenOffice.org become an integrated or semi-integrated part of GNOME, with all the corporate assignments that accompany it.

  17. Dan O'Brian said,

    May 8, 2008 at 10:41 am

    Gravatar

    I’m not sure I follow how that would have caused any controversy?

  18. Roy Schestowitz said,

    May 8, 2008 at 11:09 am

    Gravatar

    Well, maybe that is why you defend Mono. Would it be OK for GNOME to be Mono-dependent, in your view?

  19. Nikolas Koswinkle said,

    May 8, 2008 at 12:58 pm

    Gravatar

    Boy, NOBODY, has been defending Mono as of yet, in this discussion.

    Note: comment has been flagged for arriving from a possible incarnation of known (eet), pseudonymous, forever-nymshifting, abusive Internet troll that posts from open proxies and relays around the world.

  20. Rui Miguel Silva Seabra said,

    May 8, 2008 at 1:33 pm

    Gravatar

    Novell’s OOo is used by all the major distributions, it’s not a SUSE-only thing.

    This, at least, is quite not true.

  21. Nikolas Koswinkle said,

    May 9, 2008 at 2:04 am

    Gravatar

    Well, as even the guy who insists on ‘flagging’ all my comments with this ridiculous shit will have to agree, the use of the Novell-version by Ubuntu alone probably accounts for about 50% of all Linux users.

    Note: comment has been flagged for arriving from a possible incarnation of known (eet), pseudonymous, forever-nymshifting, abusive Internet troll that posts from open proxies and relays around the world.

DecorWhat Else is New


  1. Has the Administrative Council Belatedly Realised What Its Job in the European Patent Organisation Really Is?

    The "Mafia" which took over the EPO (the EPO's own workers call it "Mafia") isn't getting its way with a proposal, so it's preventing the states from even voting on it!



  2. [Meme] Team UPC is Celebrating a Pyrrhic Victory

    Pyrrhic victory best describes what's happening at the moment (it’s a lobbying tactic, faking/staging things to help false prophecies be fulfilled, based on hopes and wishes alone), for faking something without bothering to explain the legal basis is going to lead to further escalations and complaints (already impending)



  3. Links 24/1/2022: Scribus 1.5.8 and LXLE Reviewed

    Links for the day



  4. IRC Proceedings: Sunday, January 23, 2022

    IRC logs for Sunday, January 23, 2022



  5. [Meme] Team UPC Congratulating Itself

    The barrage of fake news and misinformation about the UPC deliberately leaves out all the obvious and very important facts; even the EPO‘s António Campinos and Breton (Benoît Battistelli‘s buddy) participated in the lying



  6. Links 24/1/2022: pgBadger 11.7 Released, Catch-up With Patents

    Links for the day



  7. The Demonisation and Stereotyping of Coders Not Working for Big Corporations (or 'The System')

    The war on encrypted communication (or secure communications) carries on despite a lack of evidence that encryption stands in the way of crime investigations (most criminals use none of it)



  8. On the 'Peak Hacker' Series

    Hacker culture, unlike Ludditism, is ultimately a movement for justice, for equality, and for human rights through personal and collective emancipation; Dr. Farnell has done a good job explaining where we stand and his splendid series has come to a close



  9. Links 23/1/2022: First RC of Linux 5.17 and Sway 1.7 Released

    Links for the day



  10. Peak Code — Part III: After Code

    "Surveillance perimeters, smart TVs (Telescreens built to Orwell's original blueprint) watched over our living rooms. Mandatory smart everything kept us 'trustless'. Safe search, safe thoughts. We withdrew. Inside, we went quietly mad."



  11. IRC Proceedings: Saturday, January 22, 2022

    IRC logs for Saturday, January 22, 2022



  12. Links 23/1/2022: MongoDB 5.2, BuddyPress 10.0.0, and GNU Parallel 20220122

    Links for the day



  13. A Parade of Fake News About the UPC Does Not Change the General Consensus or the Simple Facts

    European Patents (EPs) from the EPO are granted in violation of the EPC; Courts are now targeted by António Campinos and the minions he associates with (mostly parasitic litigation firms and monopolists), for they want puppets for “judges” and for invalid patents to be magically rendered “valid” and “enforceable”



  14. Welcome to 2022: Intentional Lies Are 'Benefits' and 'Alternative Facts'

    A crooks-run EPO, together with the patent litigation cabal that we’ve dubbed ‘Team UPC’ (it has nothing to do with science or with innovation), is spreading tons of misinformation; the lies are designed to make the law-breaking seem OK, knowing that Benoît Battistelli and António Campinos are practically above the law, so perjury as well as gross violations of the EPC and constitutions won’t scare them (prosecution as deterrence just isn’t there, which is another inherent problem with the UPC)



  15. From Software Eating the World to the Pentagon Eating All the Software

    “Software is eating the world,” according to Marc Andreessen (co-founder of Netscape), but the Empire Strikes Back (not the movie, the actual empire) by hijacking all code by proxy, via Microsoft, just as it grabbed a lot of the world’s communications via Skype, bypassing the world's many national telecoms; coders need to fight back rather than participate in racist (imperial) shams such as GitHub



  16. Links 22/1/2022: Skrooge 2.27.0 and Ray-Tracing Stuff

    Links for the day



  17. IRC Proceedings: Friday, January 21, 2022

    IRC logs for Friday, January 21, 2022



  18. Peak Code — Part II: Lost Source

    "Debian and Mozilla played along. They were made “Yeoman Freeholders” in return for rewriting their charters to “work closely with the new Ministry in the interests of all stakeholders” – or some-such vacuous spout… because no one remembers… after that it started."



  19. Links 22/1/2022: Ubuntu MATE 21.10 for GPD Pocket 3, MINISFORUM Preloads GNU/Linux

    Links for the day



  20. Computer Users Should be Operators, But Instead They're Being Operated by Vendors and Governments

    Computers have been turned into hostile black boxes (unlike Blackbox) that distrust the person who purchased them; moreover, from a legislative point of view, encryption (i.e. computer security) is perceived and treated by governments like a threat instead of something imperative — a necessity for society’s empowerment (privacy is about control and people in positions of unjust power want total and complete control)



  21. Peak Code — Part I: Before the Wars

    Article/series by Dr. Andy Farnell: "in the period between 1960 and 2060 people had mistaken what they called "The Internet" for a communications system, when it had in fact been an Ideal and a Battleground all along - the site of the 100 years info-war."



  22. Links 21/1/2022: RISC-V Development Board and Rust 1.58.1

    Links for the day



  23. IRC Proceedings: Thursday, January 20, 2022

    IRC logs for Thursday, January 20, 2022



  24. Gemini Lets You Control the Presentation Layer to Suit Your Own Needs

    In Gemini (or the Web as seen through Gemini clients such as Kristall) the user comes first; it's not sites/capsules that tell the user how pages are presented/rendered, as they decide only on structural/semantic aspects



  25. The Future of Techrights

    Futures are difficult to predict, but our general vision for the years ahead revolves around more community involvement and less (none or decreased) reliance on third parties, especially monopolistic corporations, mostly because they oppress the population via the network and via electronic devices



  26. [Meme] UPC for CJEU

    When you do illegal things and knowingly break the law to get started with a “legal” system you know it’ll end up in tears… or the CJEU



  27. Links 20/1/2022: 'Pluton' Pushback and Red Hat Satellite 6.10.2

    Links for the day



  28. The Web is a Corporate Misinformation/Disinformation Platform, Biased Against Communities, Facts, and Science

    Misinformation/disinformation in so-called 'news' sites is a pandemic which spreads; in the process, the founder of GNU/Linux gets defamed and GNU/Linux itself is described as the problem, not the solution to the actual problems



  29. Links 20/1/2022: McKinsey Openwashing and Stable Kernels

    Links for the day



  30. IRC Proceedings: Wednesday, January 19, 2022

    IRC logs for Wednesday, January 19, 2022


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts