As soon as Oracle announced they were offering OpenOffice.org to The Apache Software Foundation, there went up a collective sigh of relief from the FOSS community. Some, no doubt, would have preferred the project to be turned over to the folks at The Document Foundation, whose members had worked with the code for the better part of a decade and who’d already done a bang-up job improving OOo with their fork LibreOffice, but you don’t always get what you want, and Apache is an open source organization not lacking in credibility. At least now OpenOffice is out of the hands of Larry Ellison, who is a friend to open source the same way that a fox is a friend to a chicken.
Along with that sigh of relief, however, red flags began to fly in the FOSS blogosphere because IBM had a hand in Oracle’s decision. Experience has taught open sourcers to be suspicious, and there was plenty of fodder here to make one wary of Big Blue’s possible motives, mostly revolving around IBM Lotus Symphony, the freeware suite that utilizes OpenOffice code. Since the permissive open source Apache License allows a commingling with proprietary code in a way strictly forbidden by the GPL and its derivatives, it was feared that OOo would be neglected as IBM and Oracle focused their efforts on proprietary add-ons to create non-free versions of OpenOffice.
This assumption was problematic. IBM has a history of being a pretty good FOSS player, having dropped more than a billion dollars into Linux development and who-knows-how-many bucks into other open source projects. Besides, it doesn’t matter. All indications are that development at LibreOffice, licensed under the LGPLv3, will quickly leave OOo in the dust, even if development does continue with the free version of OpenOffice.
However, when IBM announced last Wednesday that they were not only lining-up behind OpenOffice, but were throwing the code from Symphony into Apache’s lap and would be helping to fold some of it into OOo, it might have been easy to assume that predictions were coming true, that Oracle and IBM were teaming up to slap the FOSS community in the face.
You know what they say about assumptions.
I very certainly could be wrong, but it appears to me that this is about the the best possible move IBM could make. It’s good for their own interests, good for FOSS and good for the casual computer user who only wants to be able to write a term paper and/or balance a checkbook.
When the OpenOffice/LibreOffice fork occurred last September, IBM was noticeably MIA, even as practically every important FOSS player was bending over backwards to come-out in support of The Document Foundation. Novell, Red Hat, Canonical and Google immediately jumped on board, and soon afterward nearly all Linux distros dropped OpenOffice to proclaim LibreOffice as the new standard bearer open source office productivity suite.
IBM was about the only exception.
Big Blue was in what I imagine to be a very uncomfortable position. They sell servers almost exclusively to businesses, many of which are purchased to run Oracle’s stack. For obvious reasons, pissing Ellison off by publicly choosing LibreOffice over OpenOffice wouldn’t be a good business move. Falling in line to support OOo would seem to be the only next move they could make. Quite frankly, it seems to be a move that will benefit everybody.
True, if they’d thrown their lot in with The Document Foundation they would’ve become instant open source heroes. Just as true however, by supporting OpenOffice instead, and by making the Symphony code available under the Apache license, they are actually maximizing the amount of support they’re giving to the open source community as a whole, even if it doesn’t make them popular heroes like Pancho and Lefty. The Apache License will allow LibreOffice to use the code and relicense it under the LGPL. If IBM had taken the other route, giving Symphony to The Document Foundation, OpenOffice would not be able to benefit from the Symphony code, only LibreOffice would gain.
This move helps both projects. It also allows IBM to keep things cool with Oracle, which is necessary for their business, and it keeps Symphony under a license that allows them to use practically any proprietary add-on they want, which is good for them even if you and I have mixed feelings about it. In other words, it would seem to be a win-win solution.
Unless they do something that proves me wrong, I’m impressed with how IBM has handled this.
Latest posts by Christine Hall (see all)
- SuperTux Returns, Proprietary Open Source & More… - May 27, 2016
- Unixstickers Gives Back to FOSS Projects - May 25, 2016
- Ubuntu’s Got Tablet, Fedora’s Kernel Decision & More… - May 21, 2016