4 ms·
In the interest of full disclosure, I am a contributor to AOO, albeit one who has not been as active as I should have been in the past. Which makes me part of
by mindcrime 10y ago
In the interest of full disclosure, I am a contributor to AOO, albeit one who has not been as active as I should have been in the past. Which makes me part of the problem. But that aside...
Rumors of the demise of AOO are very premature. Some internal speculation aside, there's no particular reason to think the project will be shut down. Yes, the ASF board wants to see certain things happen, but none of them are things that all of us don't also want to see. Security fixes being released in a timely fashion? Of course we want that. Frequent releases? Yep. Awesome new features? Hell yeah!
So the question is, can we get back to a place where we can deliver those things? I think so. And here's some reason why:
1. This recent "retirement" discussion has served as something of a "call to arms" or rallying cry for some AOO contributors. Count me among their number, just to show an example. I'd been pretty slack about contributing, but this has motivated me to get off my arse and get busy doing stuff. And I don't think I'm the only one.
2. We've had a number of new contributors, or at least potential new contributors, show up in the past week or so.
3. We're starting a new, more focused recruiting effort to recruit developers to the cause. Perhaps you yourself have given some thought to working on an OSS office suite? Here's a great chance!
4. We have had a release manager volunteer step forward to manage the 4.1.3 release.
5. A lot has happened just in the last week in terms of cleaning up documentation around the build process and clarifying issues there. I think it's safe to say we want to make it as easy as possible for new (or existing) contributors to build and run AOO.
Now the realist in me demands that I acknowledge that we still face a tough slog ahead. But nobody said this stuff was easy. And I feel confident that we can get this project back on track and re-establish it as the world's most awesome office suite.
Anyway, again, please consider getting involved now if you have any interest in office suites. And this is especially true for Mac users, as we could especially use more help from people who can build and test on the Mac platform.
- Grishnakh 10y ago>We're starting a new, more focused recruiting effort to recruit developers to the cause. Perhaps you yourself have given some thought to working on an OSS office suite? Why would I want to waste my time working on a has-been office suite when I can work on the leading FOSS office suite, which is LibreOffice? Why would I want to commit my time to a project that seems to only seems to exist because of a licensing dispute? Why would I want to join a chronically understaffed project when I could instead join its competitor, which has far more development support? Why would I want to join a project which all major Linux distros have abandoned, when I could instead join its competitor, which all major Linux distros have switched to? I'm sorry, I haven't seen any good answers to these questions at all. Working on a FOSS project that is popular and stands a chance of becoming even more popular among non-techies is laudable. Working to increase FOSS fragmentation, in my opinion, is not. I haven't seen one valid argument yet about what AOO brings to the table the LibreOffice does not. The "diversity" argument isn't valid here; this isn't like, for instance, The GIMP vs. Krita, where the two products are very, very different underneath, have different UIs, even different feature sets, different strengths and weaknesses, and different tasks at which each one is better-suited for. Instead, you have one product that's a fork of the other and has all the developers, and another one that is a dying husk. This resembles the X.org vs. XFree86 situation more than anything, and I would hope everyone here remembers how that one went. What you're doing here is basically like Dawes begging for more help for XFree86 even though everyone else is perfectly happy working on and using X.org, all the distros use it, and everyone's forgotten XFree86.
- mindcrime 10y agoUltimately, if you don't want to work on AOO, there's probably not much I can say to convince you. And that's fine. No hard feelings. So the rest of this really isn't even for you, it's for other people who are reading and who don't already have their minds made up: Why would I want to waste my time working on a has-been office suite when I can work on the leading FOSS office suite, which is LibreOffice? Because you like competition and you want to knock that "leading FOSS office suite" off its perch. Why would I want to commit my time to a project that seems to only seems to exist because of a licensing dispute? 1. The license thing does matter, because it's easier for other projects to incorporate patches that are licensed under the ALv2. And even where that's not actually true, it is the perception. In either case, I'd posit that contributions to AOO stand to benefit everybody, whether they're using AOO, LO or something else. 2. The Apache Way. Some people will just find that they enjoy the style of collaboration that results from the way Apache projects operate. It won't be for everybody, and it's probably a minor point, but it matters to some people. 3. Everybody loves an underdog and here's your chance to be a hero. Contribute to other projects and you're "Just another person who contributed some patches". Help AOO (especially right now) and you get a chance to feel like you're really making a difference. Why would I want to join a chronically understaffed project when I could instead join its competitor, which has far more development support? You can probably have more impact working on AOO. There's more room to influence major technical decisions exactly because there aren't as many active developers. Want to radically re-invent how office suites work and create something truly novel? There's probably more opportunity to to that within the AOO project than others. Why would I want to join a project which all major Linux distros have abandoned, when I could instead join its competitor, which all major Linux distros have switched to? Meh... I don't see how that matters for anything. Why should someone else's decisions influence what you decide to work on? I'm sorry, I haven't seen any good answers to these questions at all. And truth be told, that's at least in part because we haven't spent a lot of time trying to come up with answers to them. We've been content to just accept that some people will want to work on AOO for their own reasons, and others will prefer to work on other projects for their reasons. We'll see if that changes in the future. I just started a thread on the AOO dev list trying to provoke some discussion around this very topic. Working on a FOSS project that is popular and stands a chance of becoming even more popular among non-techies is laudable. Yes, that's why we do it. :-)
- geofft 10y agoWhy do you contribute to AOO and not LO? On what basis should one decide to contribute to one or the other? (I'll admit I am not very likely to contribute to either, but if I do I'll probably contribute to what my Linux distro uses)
- mindcrime 10y agoWhy do you contribute to AOO and not LO? On what basis should one decide to contribute to one or the other? For me personally, it is a combination of preference for the Apache License, familiarity with the ASF (from being involved in other projects) and a general comfort level with how the ASF works. That and a little bit of wanting to support the underdog, and compete with the perceived front-runner.
- ZenoArrow 10y ago> "That and a little bit of wanting to support the underdog, and compete with the perceived front-runner." Dude, I get it, I really do, and if that's what you want to spend your free time on you should feel good about aiming to do the right thing. However, I can't help but feel we're missing out the 800-pound gorilla in the corner of the room. If you want to compete with the perceived front runner, there's only one office suite that is fit to have that title, and it's name is not LibreOffice. You know exactly what I'm talking about. The gap between the real front runner and the open source alternatives is pretty sizeable. If you're serious about wanting to compete with the perceived front runner, why not look at a AOO/LO merger? Are the project governance approaches really that different? Are the goals really that different? Why not accelerate the growth of open-source office suites rather than having two projects competing for developers? The OpenOffice name still has value, perhaps the ASF approach to project governance will be preferred too, why not bring everyone in under the same banner? The whole situation reminds me of the Amiga vs Atari wars of the late 80s/early 90s, competing over the same home computing niche whilst the PC slowly ate their lunch. Please don't let history repeat itself. Look beyond the open source world, your main competitor does not live within it.
- mindcrime 10y ago
- ploxiln 10y agoAOO IS NOT MAINTAINED. It can't do builds, it can't make releases. It can't apply a security bug fix and build a release within 9 months. For an office suite, that's not OK. LO is where all the active OpenOffice developers went to, LO is the continuation of OO.o. AOO is an old and unmaintained snapshot of OpenOffice, with an apparently long-broken release build process. I don't think there should be just one office suite, or even just one open source office suite, and I don't think everyone should just use the one with the most features. Not at all. But the AOO situation is just tricking people unfamiliar with it, to use the OO.o from 3 years ago instead of the OO.o with security and other fixes, and updates for compatibility with new operating systems (and new features which may or may not be desired). If you hate LO developers or project, maybe you have some good reasons, and you should be able to work on a competitor based on whatever open-source code base you want. But the right thing to do at this point is abandon the "OpenOffice" name. Random people looking for "OpenOffice" need to be confronted with the fact that there are now two forks, LibreOffice and something else. And, at least for today, they should definitely choose LibreOffice.
- mindcrime 10y agoit can't make releases. We're working on a 4.1.3 release right now. Yes, the project has had its issues, yes there's been adversity. But we'll fight through it and come out better in the end.
- cesarb 10y ago> > it can't make releases. > We're working on a 4.1.3 release right now. Sorry, but I saw that before. The last time people said AOO couldn't make releases, they made a herculean effort and managed to make one release (4.1.2 IIRC). And here they are again, struggling to make a release. I'll believe it not when they say "look, we made a release", but when they show the ability to do so consistently.
- zanny 10y agoThe real, non-political competitor to the OpenOffice lineage has always been Calligra[1]. It sees dramatically less development, but it is also one of the KDE related projects that has a knack for using its toolkit to dramatically reduce its own code bloat - what takes hundreds of thousands of lines of reinventing the wheel in OO/LO is several hundred lines of extremely well maintained Qt data structures. Even when the zombie AOO dies it does not mean the end to competition in the free office suite space. Even beyond Calligra there are some Gnome based efforts and third party projects (including web based ones) that provide similar tools. There is no shortage of competition, and if there were ever a slowdown in LO we would just see another fork akin to the Oracle escape. https://www.calligra.org https://www.calligra.org
- pietroalbini 10y agoIf you, as an AOO contributor, prefer the Apache license and you want to contribute to that project is fine, that's your free choice :) What I'm worried about is the end user, the one who only knows "openoffice is the alternative to ms office", and is stuck with an unmaintained product. A person I know told me a few months ago "Hey, openoffice don't render square roots in an acceptable way, should I go back to ms office?", and I had to explain he was using a mostly-abandoned software and he should switch to libreoffice because that bug was fixed months ago in there. You're maintaining a software for end users, not for the HN population: they don't care about the Apache license or the GPL, but they care to have a working piece of software :) I really hope the OOo trademark is handed to TDF, not because of license wars, but because that's the better thing for the users of AOO/LO.