What's next for Apache OpenOffice
What's next for Apache OpenOffice
Posted Sep 8, 2016 20:57 UTC (Thu) by jimjag (guest, #84477)Parent article: What's next for Apache OpenOffice
1. The whole issue was an open and honest DISCUSSION. Many people took this as an indication that AOO was dead. I fear that my own response to Dennis' post on-list went a bit too far in reinforcing that (mis)belief but the lack of (perceived) developer energy was the basis for the whole discussion. Dennis did not say "AOO is dead, what should we do" but rather that the AOO community should discuss, as a contingency plan what a retirement would look like.
I may plan or discuss my funeral (or final wishes), but that does not mean I am dead or dying. :-)
But think about this: what other project would be so open and candid? Such openness, and the true appreciation that discussion be done in public is a core part of the Apache Way. It's also a core part of what open source work.
2. Because of this "publicity", the AOO has been overwhelmed by lots and lots of offers of support, which have been graciously and thankfully accepted.
3. People have also forgotten that choices, even in FOSS, are a Good Thing. LibreOffice is very successful, and they should be congratulated for their success. But certainly there is room for other players in this game, and certainly room for one (or more) that are under a permissive license. The thing is is that they don't have to be clones; they can have different audiences, different "missions" so-to-speak.
4. It is sad when we in the FOSS community degrade ourselves to simple, base license-wars. There are good, solid reasons for permissive, weak copyleft and strong copyleft, and I've contributed to them all.
IMO, what's next for Apache OpenOffice is what the Apache OpenOffice community decides; it sounds as if this whole kerflunkle has served as a kick-in-the-arse to the AOO team: they see how important AOO still is to numerous people, and they have loads of new volunteers offering to help. A 4.1.3 release is forthcoming so that is good news and a step in the right direction.
Posted Sep 8, 2016 21:22 UTC (Thu)
by ovitters (guest, #27950)
[Link]
Whenever I go to some conference I get the positive energy. I go back, then fail to do anything that I really want to do.
Regarding your points:
At least AOO finally stopped attacking LO in the LWN comments.
Posted Sep 8, 2016 22:21 UTC (Thu)
by glaubitz (subscriber, #96452)
[Link]
We are not talking about a small text editor here that can be maintained by 1-2 developers easily, we are talking about an office suite, one of the most complex and largest software projects currently imaginable and unless a miracle happens and a huge amount of very talented and motivated developers is suddenly going to join AOO, there is absolutely no chance that a project of that size can be successfully maintained and developed in the future.
As the old saying goes, "Rather a calamitous end than an endless calamity."
Adrian
Posted Sep 8, 2016 22:46 UTC (Thu)
by pr1268 (guest, #24648)
[Link]
Agreed, but having a choice implies there are two (or more) actively supported and admired competitors. This applies to both FLOSS and proprietary software. (Case in point: Remember how MS stalled IE at version 6 for five years? Firefox [and a few other web browsers] emerged victorious.) AOO's reticence (or outright lack of resources) to fixing security flaws speaks volumes about its "active support" (or lack thereof), and, IMO, LO won admiration from many more users than AOO after the fork, especially for its aggressive release/update schedule (acrimonious flame wars and berating by a certain few individuals notwithstanding). Also agreed. But, FLOSS license wars are nothing new here. In fact, having witnessed the whole debacle from the sidelines, I wasn't aware that this was a serious bone of contention with regards to AOO vs. LO. I will even defend AOO here in saying that there is no reason to assume a licensing row has anything to do with LO's greater success (or perception thereof). Quite often, having a different, incompatible license is a feature (as some have pointed out here regarding AOO).What's next for Apache OpenOffice
1. Other people joined the discussion and hoped AOO would finally stop/merge with LO
2. "Soon we will do something" is what AOO had said years
3. You cannot even put out a security fix
4. That's specific to AOO itself
What's next for Apache OpenOffice
What's next for Apache OpenOffice
3. People have also forgotten that choices, even in FOSS, are a Good Thing.
4. It is sad when we in the FOSS community degrade ourselves to simple, base license-wars.
Posted Sep 9, 2016 1:09 UTC (Fri)
by bunk (subscriber, #44933)
[Link] (4 responses)
What "audiences" and "missions" do you have in mind for AOO, that would differ significantly from what LO is currently doing?
> 4. It is sad when we in the FOSS community degrade ourselves to simple, base license-wars. There are good, solid reasons for permissive, weak copyleft and strong copyleft, and I've contributed to them all.
Jim, you are the only one who is harping the license topic all the time.
The only "license-war" seems to be AOO people complaining that the AOO license change makes it impossible to take code from LO to AOO.
The AOO license change was after LO was started, so for me as bystander this doesn't look like something where anyone could blame the LO developers.
Posted Sep 9, 2016 14:38 UTC (Fri)
by jimjag (guest, #84477)
[Link]
Even a cursory review of the various related thread show that this is simply untrue.
Posted Sep 9, 2016 15:26 UTC (Fri)
by smurf (subscriber, #17840)
[Link] (2 responses)
This dicsussion is not about the license. Not primarily, anyway.
> Jim, you are the only one who is harping the license topic all the time.
Wrong.
That being said, as of today the permissiveness of the license is (IMHO) the only reason somebody would decide to participate in AOO instead of LO … assuming there's a material advantage of doing so, which I doubt when considering AOO's shortcomings.
Posted Sep 9, 2016 16:27 UTC (Fri)
by cesarb (subscriber, #6266)
[Link]
In the HN thread (https://news.ycombinator.com/item?id=12456071) I saw another reason: the developer already being used to and comfortable with how the ASF works.
Posted Sep 10, 2016 3:45 UTC (Sat)
by zorro (subscriber, #45643)
[Link]
Posted Sep 9, 2016 8:58 UTC (Fri)
by moltonel (guest, #45207)
[Link]
But until they do (and it'll take them years to get back on track even in the most optimist projections), having average users directed to AOO is really irresponsible. The users who are not savvy enough to switch projects are also the ones most vulnerable to security issues in their software. And if those users get bitten by an AOO bug hard enough that they look for alternatives, chances are that they'll switch to MS Office rather than LO. It's currently one of the greatest thorn in FOSS's side.
For 5 years people have been waiting for AOO to either suceed (and make the trademark proud) or die off (and return the trademark to LO). Neither has happened or look likely to happen soon, and many people's patience is exhausted. It's really sad when the third option (give/share the trademark to/with LO, and compete on merit without Oracle's spitefull choice of successor mess up the popularity numbers) is technically easy.
Posted Sep 9, 2016 11:19 UTC (Fri)
by niner (subscriber, #26151)
[Link]
With that single step, you could remove all the bad blood and the basis for all the criticism and all the ranting. And you'd show how you care about your users and about free software. And most of all you'd gain the time needed to re-build your development team. It's a win-win-win.
Posted Sep 15, 2016 13:16 UTC (Thu)
by HelloWorld (guest, #56129)
[Link]
> Because of this "publicity", the AOO has been overwhelmed by lots and lots of offers of support, which have been graciously and thankfully accepted.
> But certainly there is room for other players in this game, and certainly room for one (or more) that are under a permissive license. The thing is is that they don't have to be clones; they can have different audiences, different "missions" so-to-speak.
IOW, perhaps AOO *could* have some sort of mission that is distinct from LO's, but I don't see it, and you haven't presented one. If permissive licensing was one, then hordes of ASL2 fans should rush towards OpenOffice right now and commit tons of useful code. But they don't, meaning that apparently they care more about the technical improvements (build system, code cleanup etc.) that LO made. And I don't see any reason for that to change.
> they see how important AOO still is to numerous people
Anyway, I honestly hope that you'll be able to stop deluding yourself soon. It's dead, Jim.
What's next for Apache OpenOffice
What's next for Apache OpenOffice
What's next for Apache OpenOffice
What's next for Apache OpenOffice
What's next for Apache OpenOffice
What's next for Apache OpenOffice
What's next for Apache OpenOffice
What's next for Apache OpenOffice
Sure, but it doesn't mean you're not dying either. And AOO clearly is dying, the numbers are unambiguous. Fyi, I am not and never was affiliated to LO or AOO in any way other than as an occasional user.
How many lines of code (or translation, artwork etc.) were committed as a result?
So what is AOO's mission compared to LO's? I'll quote myself from here: https://lwn.net/Comments/699409/
In order to justify the existence of a fork with that sort of argument you show some feature that
- cannot be implemented in LibreOffice because of technical reasons, or the direction the project is meant to take, or maintainability concerns etc.
- can be implemented in AOO in principle as the reason doesn't apply there
- can be implemented in practice, i. e. there's somebody willing to do the work
Sometimes that is the case, see for instance the fork of DragonFlyBSD from FreeBSD. But for AOO I haven't seen any such reason.
I suppose that depends on your definition of “numerous”. It certainly doesn't have a meaningful amount of developer mindshare, and while it might be important to some users, that is most likely because they know the brand and haven't realised yet that all meaningful development is done in LO.