History of Software Forks Favors LibreOffice
jfruhlinger writes "The forking of LibreOffice from the OpenOffice.org project, followed by Oracle's donation of OpenOffice.org to the Apache Software Foundation, has been something of a bumpy road. But if history is any guide, it's the fork, LibreOffice, that might have the brighter future."
LibreOffice has already undertaken massive cleanups of OpenOffice.org code. It's pretty obvious which one will survive. Also one doesn't have a stupid TLD in the name (although the other is a bit freetard for my tastes).
1. If they were going to release it into the wild at the end, they should have done so at the beginning.
2. They fail to understand the advantage that MS Office integration brings in MS's SQL Server and other server strategy.
OpenOffice is the one thing that MS sales reps really hate. A few million investment can have a big impact on MS's bottom line.
I'm not a lawyer, but I play one on the Internet. Blog
Why is that same article linked twice?
I think every company that acquires an open source project could learn something from how Oracle handled openoffice.org
The uncertainty and the lack of commitment by Oracle practically forced the community to fork the project. And even after that, Oracle had a chance of do the right think and donate the name to the Open Document Foundation, but they just sat down and done nothing, LibreOffice became a strong fork, and in the end they realized an "asset" that they bought from Sun was basically worthless.
I moved to LibreOffice months ago. No regrets.
If I suggest OpenOffice to the average user, I have a good chance of swaying them.
If I suggest "LibreOffice", they're likely to think I'm trying to pawn off some cheap mexican knock-off product on them.
If a project were like a rocket ship, then a fork might cause the parent to accelerate based on Newton's third law. I think the author was trying to find a geek-friendly metaphor for a zero-sum game.
When you have two competing projects like this, with no parent corporation to throw its weight or resources behind one or the other, then the side with the better technical leadership wins. Technical leadership is not just one skill and doesn't have to be provided by just one person. It includes, among other things, technical and business vision, architectural and design ability, coding and quality control, communication and organizational ability, recruiting, conflict resolution, responsiveness, ability to overcome obstacles and adapt to changing conditions. When we hear of a "name" open source project imploding in a morass of discontent and/or apathy, most likely several of those things were not being provided by the project leadership.
MariaDB is an entirely different issue, but the outcome is very similar. OpenOffice.org had a community, but when it changed directorship to a new company, it had a thumb that didn't want to do much with outsiders. FORK! Libre Office came about based on an existing extant codebase. The community moved on. There are more code developers in the world not working for Oracle, than there are code developers working for Oracle (imagine that!). I understand that there is a strategic interest in killing Mysql for Oracle, they have successfully killed off components of it before (SleepyCat was not critical, but it was a nice 'extra' and Oracle bought it and killed it just as quickly as microsoft killed FoxPro in the '90s). MariaDB is a code fork. There will be no going back. Its imperative for Oracle that MySQL dies on the vine. With LibreOffice, its one less thing they have to look after, so I would suggest their attitude toward it is 'Meh'.
Apache will provide the LibreOffice folks with a copy of the OpenOffice code base that is under a license which removes any possible obligation they might ever have to Oracle regarding the code, unless they do something incredibly stupid (like failing to attribute or reproduce the license at all as Katzer did in Jacobsen v. Katzer). LibreOffice can choose to use that code base or not.
If we really want to lay blame, it's not just Oracle's. Sun Microsystems didn't ever achieve a viable community for OpenOffice. There were operational and technical reasons, but the one that might have been most important was the requirement to sign your copyright over to a company that might take the work private the next day, with no quid-pro-quo at all.
In 1999 or so, Danise Cooper called me to explain what Sun would do with OpenOffice. I explained at that time that they needed to have some sort of quid-pro-quo for code donors, even if it was only a covenant that Sun would keep their own development available under a free software license for some time or remove the contribution from their version. This was not implemented. It was difficult for independent developers to see a reason to work with Sun.
Bruce Perens.
OpenOffice was unanimously dropped like a hot plate. Where exactly is the uncertainty?
I've always had OpenOffice installed on my machines, although I default to MS Office for the usual reasons.
When I upgraded Ubuntu to Natty it installed LibreOffice, and I have to say that I'm very impressed. In a nutshell, it feels finished, something that OO never achieved.
LO is still not entirely MS Office compatible, but for many things where that compatibility isn't essential it's my first choice.
Three Squirrels
So, OO is more MS Office compatible?
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
Selective quoting of history can be used to predict whatever future a magazine thinks will sell the most ads.
LibreOffice is superior to Open Office in my experience. It is faster, It opens complex M$ Office documents and complex power point presentations more cleanly (assuming you have fonts installed.) It is a definite upgrade from OO.org. One problem. OO.org has brand recognition. Big time. It established itself as a market force. LibreOffice will need to establish that all over again.
The software or all the users who now need to play the real guessing game on when/how to switch? How long until the next fork after this one?
Someone needs to write up a blog article drawing random conclusion from handpicked examples of the success of forked projects, based on their names. Since both project names are retarded, I wonder what effect we can extrapolate that project names have on project success.
Write your article with flair and with, and /. will link to it, driving add dollars^H^H^H^H^H^H^H^H^Hmonetization your way. And we the /. community can discuss an even more inane correlation.
One man's pink plane is another man's blue plane.
I hate to fill a spot on somebody's buzzword bingo card, but this strikes me as an excellent opportunity for coopetition. If Libre Office and OpenOffice follow relatively similar development paths, but compete on implementation and refinement, it would be an excellent opportunity for exploring alternative solution strategies while cross-pollinating the results.
The fundamentals of OOo/LOo are pretty solid. The major components are well established -- the biggest wins on the horizon are about optimization, handling new formats, and UI enhancements. Development in those areas is easier to inherit across projects than if major project direction changes were still under way.
Without a doubt, splitting the available development pool across two projects has some costs -- but it is not necessarily all down side. LibreOffice thinks they have better ideas for the future of OOo. OpenOffice thinks the same. I hope they are both right; I'd like to see them each throw down some serious code, hold it up with pride to the other project, then do what comes naturally in Open Source world: Steal each other's code.
Not sure about LGPL/ASL compatibility -- but I figure between pluggable libraries, re-implementation, and maybe some special case license grants, they could work it out.
Just seems like it shouldn't be too difficult for a sharing-oriented community to figure out how to have their cake and eat it too. The developers are all after the same thing in the end -- a good F/LOSS office suite. By virtue of each person's contribution to their preferred project, they earn the right to choose their own paths. No need to minimize one or the other project when our very foundational principle is sharing and learning from each other (and showing off our coding chops). They can simply turn our greatest strength into our greatest strength.
Stop-Prism.org: Opt Out of Surveillance
What if they were still lost in the hall of mirrors and bought sun to KILL the open innovations?
They couldn't legally nuke forking options so they made the OSS community do extra work to re-spread mindshare etc. I'll leave it to my betters to decide where Java and friends stand.
What if they bought Sun to kill a threat to the entire Proprietary model?
My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
That would be pretty dumb to try. People don't typically walk into work and find OpenOffice or now LibreOffice installed, they typically went looking for it and are likely aware of what was going on. Not to mention all the installs that came with Linux distros that had already migrated away from Openoffice in favor of the previous fork.
Once you've gotten folks away from MS, it's trivial to get them to the more stable, reliable and current fork. Especially if the older one is dying out.
Many technical students write their papers with a modern distribution of LaTeX.
It's robust, generates beautiful typography and you can easily manage your work with version control systems which also allows for collaborative work.
XFree86 died when the community got up and left. Even with free hosting, the remaining XFree86 partisans couldn't keep it alive and lost interest.
Before that, the X Consortium - backed by the might of industry - died when no-one could be found to participate in it ... because XFree86 was where the action (i.e., community) was.
Citizendium forked from Wikipedia, recruited a pile of academics, then Larry Sanger drove them away. (And then the cranks moved in.) When someone said "chaps, CZ is dead" and tried another fork, they called him ... a "traitor". This from the project that was a fork itself.
XOrg is under the MIT X11 licence, but seems to get plenty of contributions back - because it's where the community is. An open source licence with centripetal force from the gravitational pull of the community.
Wayland's lead developers and all the people pushing for it in Fedora are X.Org developers. They're not "traitors" to X, they're people with their eye on the target: a good open source desktop.
EGCS won by the community getting up and leaving GCC.
LibreOffice won when the community got up and left Oracle. Oracle and IBM's approach in trying to claw it back is gibberingly, hilariously misconceived. (And Rob Weir blew his cred irretrievably lying about what the FSF had said and directing abuse at the FSF rep who tried to correct his lie. Once a shill equals a shill.)
OOo=XFree86 with a sponsor. Yay sponsors. Can IBM employ enough contributors to single-handedly make up for the enthusiasm to be found at LibreOffice? I really doubt it.
http://rocknerd.co.uk
...because frankly, this isn't an excuse if there in fact still are such bugs in OpenOffice. But really:
Students may use OpenOffice, but only until they encounter some serious bug that threatens their paper (which will occur on the last night before submission date.)
If this is really a problem for you, you've already fucked up. You've waited until the last night before the submission date without having something viable. You allow one software bug to threaten "your paper", suggesting you only have one copy in one place...
It's not like this only happens with OpenOffice, and it seems to rarely happen, period. Supposing it does, any decent university is going to have multiple computer labs which are going to have some form of office installed -- my university does, in fact, have some Linux machines with OpenOffice, as well as plenty of Windows/Mac machines with MS Office. I've also never had a problem getting an instructor to accept PDF.
So, while none of this excuses OpenOffice if this kind of crap is still happening -- and if it is, in fact, an OpenOffice bug and not, say, an OS bug or hardware issue -- if something goes screwy with a paper I'm working on (or with my whole machine), I walk over to a computer lab, log in, and find a recent copy of my paper on the network storage. I lose maybe half an hour, and I still get the thing in on time.
Oh, and I get it done well before the night before it's due.
Don't thank God, thank a doctor!
What The Doc Foundation needs to do is to adopt Google Chrome, and now Mozilla's and originally (?) Debian's stable-testing-unstable development model. Keep the releases coming in a way that doesn't break the program or lets the user fall back to an unborken version.
Older versions of OOo had enough bugs and compatibility issues with MSOffice that most people I pushed OOo on did not like it. From my point of view OOo had bad press, carried along from older versions. I often heard "OOo" and "argh" in the same sentence. LibreOffice has a brand shiny name, icons and has everything early OOo versions lacked (obviously). It's get adopted by my collegues - who rarely know it's a OOo fork - more then OOo ever did, because it does not come with a lot of preconceptions.
So how about Emacs/XEmacs, which was arguably the first great open source fork? Both projects are still around, but I don't get the impression that the fork (XEmacs) has run away with the ball by any stretch of the imagination.
Virtually serving coffee
ODF is a zipped XML format, that is, it is some XML files in a .zip file. Office Open XML is Microsoft's binary .doc format with some XML wrappers for show. The 6000 page (and still incomplete!) spec is for the binary junk.
It is not that well known, but IBM have been maintaining and improving a fork of OpenOffice for years now, under the Lotus brand. It's called Lotus Symphony. I've been using it for some time and find it very capable and polished, at least compared to the mess of a UI that I remember OpenOffice to be.
How does LibreOffice compare to Symphony? Anyone tried both?
If you recall, MS Word (before 1995) was "one of them" - on par with WP and Lotus [Excel] and AmiPro. But then MS did something that created a lot of value to the user - they created an office suite. Now you could insert Excel into Word (and everything into everything, as long as they are OLE-enabled.)
Well, that created positive value in a way. But they decided to use OLE for embedding all sorts of things which should have been part of the document itself. Example: equations. Why are these embedded as OLE objects? It's impossible to do a global search across equations for a particular expression. It's impossible to do a search and replace if you need to rename a subscripted variable in both text and equations. Oh, it's also a challenge to even refer to variables in equations within the document text in a way that matches the appearance of the variable in the equation (subscript+superscript? caret above letter?), unless you embed it as a one-character equation. And on and on...
Relying on OLE instead of providing an in-document support for equations added a lot of negative value. It's why some of us use LaTeX for any scientific or mathematical authoring, and why support for in-line LaTeX equations was one of the most sought-after modifications to OpenOffice. I predict it will be a common request for LibreOffice also (why did OpenOffice have to re-invent another square wheel instead of adopting LaTeX form for equations).
Those who can make you believe absurdities can make you commit atrocities. - Voltaire
Am I the only one that still thinks LibreOffice is a terrible name?
At this point, I care much less about which of the two code bases survives than I do the name. PLEASE lose the damn "Libre" name! We spent many years getting people to use, understand, trust, and remember the name "OpenOffice". Throwing it away, if there is ANY possibility of using it, is incredibly stupid. Believe it or not, the [horrible] name "LibreOffice" is already causing more damage to the credibility of the software in the eyes of non-technical users than any bug or fork has ever done.
Oh, and if possible, see if you can lose the ".org" in "OpenOffice.org" too...
Yup. Part of the standards process for any data format is to have a cleanroom implementation done that supports at least 90% of the specs within, I dunno, three months.
I figured out how to create a primitive ODF document from the specs in an afternoon. There are holes in the standard, but at least it's not the nightmare that OOXML is.
The world's burning. Moped Jesus spotted on I50. Details at 11.
TFA mentions the descent of Slackware from SoftLanding Linux System as an example to illustrate his point, but I'm not sure it really applies in this case. IIRC, the principal difference between SLS and Slack was originally the choice between a.out and ELF binaries. Although history has favoured the latter, the difference doesn't seem that significant in the light of the X.org/XFree86 or Open/LibreOffice shenanigans.
Don't get me wrong - I still love Slackware, and it is by far my first choice for any Linux server. In fact, until a year or two ago, it was still my first choice as a desktop platform too, but more recently Arch Linux has taken that position, since it has all of the elegant simplicity of Slackware in combination with a more modern (but still simple) package system.
The history of OpenOffice has been utterly depressing in so far as they've just aped Microsoft Office. Maybe that had to happen if OO was to gain any of MSO's user base, but I hope that LO will break out of the cloud of crap that is MSO.
For example, there is no reason whatsoever to default to throwing away your work. The convention of opening up a new document and THEN having to save it is utterly ridiculous! In fact, there is no reason to have a "save" command at all. All user input should be sacred, and every keypress should be saved. Another example is the crazy arrangement of menu items (made worse by the "ribbon bar" in MSO) that attempts to cram every command into a menu structure. A word processor is for most people a tool of reasonably frequent use, yet even after many years of using MSO, I still can't remember where the word-count is, because I use it hardly ever. I also constantly forget how to bring up the styles library or insert a picture. Instead of a labyrinthine menu, why not have a search (with command completion), and leave the menu for those who want to browse?
This comment is way OT though, so I'll stop.
"And the meaning of words; when they cease to function; when will it start worrying you?"
OpenOffice (OO) should be renamed to Oracle Office to avoid disorder.
Recipes for USA bankrupt - http://tinypaste.com/0d66f dd = dollar deluge (printed in the infinity)