Language Selection

English French German Italian Portuguese Spanish

Open Letter to Apache OpenOffice

Filed under
LibO
OOo

Today marks 20 years since the source code to OpenOffice was released. And today we say: LibreOffice is the future of OpenOffice. Let’s all get behind it!

It’s great to have a rich and diverse set of free and open source software projects. Hundreds of millions of people around the world have benefited from the choice and customisation that they bring. But sometimes, users can lose out when they’re not aware of newer alternatives, or when one brand overshadows another.

OpenOffice(.org) – the “father project” of LibreOffice – was a great office suite, and changed the world. It has a fascinating history, but since 2014, Apache OpenOffice (its current home) hasn’t had a single major release. That’s right – no significant new features or major updates have arrived in over six years. Very few minor releases have been made, and there have been issues with timely security updates too.

Read more

LibreOffice Wants Apache to Drop the Ailing OpenOffice

  • LibreOffice Wants Apache to Drop the Ailing OpenOffice and Support LibreOffice Instead

    It is a no-brainer that Apache OpenOffice is still a relevant recommendation when we think about open source alternatives to Microsoft Office for Linux users. However, for the past several years, the development of OpenOffice is pretty much stale.

    Of course, it is not a shocker, considering Abhishek wrote about the possibility of Apache OpenOffice shutting down back in 2016.

    Now, in an open letter from The Document Foundation, they appeal Apache OpenOffice to recommend users to start using better alternatives like LibreOffice. In this article, I shall mention some highlights from the blog post by The Document Foundation and what it means to Apache OpenOffice.

LWN: An open letter to Apache OpenOffice

  • An open letter to Apache OpenOffice [LWN.net]

    On the 20th anniversary of the open-sourcing of the OpenOffice.org suite, the LibreOffice has sent an open letter to the Apache OpenOffice project suggesting that it is time for the latter to recognize that the game is over. "If Apache OpenOffice wants to still maintain its old 4.1 branch from 2014, sure, that’s important for legacy users. But the most responsible thing to do in 2020 is: help new users. Make them aware that there’s a much more modern, up-to-date, professionally supported suite, based on OpenOffice, with many extra features that people need."

LibreOffice Sends Open Letter Appealing To Apache OpenOffice

Apache Software Foundation Celebrates Two Decades Of OpenOffice

  • Apache Software Foundation Celebrates Two Decades Of OpenOffice - Phoronix

    While the LibreOffice fork is much more popular than OpenOffice these days, the Apache Software Foundation does continue maintaining the OpenOffice codebase born out of Sun Microsystems' StarOffice.

    It's been twenty years already since Sun initially open-sourced the office suite as OpenOffice. While the OpenOffice 1.0 release didn't come until two years later (2002) and wasn't until 2011 that Oracle transferred OpenOffice to the Apache Software Foundation, Apache is celebrating twenty years of OpenOffice.

LibreOffice rains on OpenOffice's 20th anniversary parade

  • LibreOffice rains on OpenOffice's 20th anniversary parade, tells rival project to 'do the right thing' and die

    To mark the 20th anniversary of Apache OpenOffice, the project's main rival, LibreOffice, published a letter asking OpenOffice to tell its users to switch.

    Many people, the letter says, are unaware of LibreOffice because the OpenOffice brand is still so strong, despite the lack of significant updates over the past six years. To remedy the situation, LibreOffice is asking its competitor for an endorsement.

    "Make them aware that there’s a much more modern, up-to-date, professionally supported suite, based on OpenOffice, with many extra features that people need," says the letter, penned by the board of The Document Foundation (TDF), steward of LibreOffice. "We appeal to Apache OpenOffice to do the right thing."

    The rationale for asking OpenOffice to give up and go home arises from the Apache project's leisurely release schedule. Or as TDF's board put it, "[S]ince 2014, Apache OpenOffice (its current home) hasn’t had a single major release."

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

'This was bigger than GNOME and bigger than just this case.' GNOME Foundation exec director talks patent trolls and much, much more

Patent assertion entities: do not pick a fight with open source. It won't end well for you. This is the message from GNOME Foundation executive director Neil McGovern, who will speak on the subject at the Open Source Summit Europe next week. McGovern talked to The Register ahead of the event on patents, Microsoft, and more. The open-source outfit develops the default desktop environment on major Linux distributions including Ubuntu and Red Hat. In late August 2019, Rothschild Patent Imaging filed a lawsuit against the GNOME foundation claiming that GNOME Shotwell, a photo manager, infringed one of its patents. “We didn't receive a letter before the court documents were filed or any sort of warning, it was just filed and then within a week there was a settlement request for $75,000,” McGovern told us. Read more

Debian Janitor: Hosters used by Debian packages

The Debian Janitor is an automated system that commits fixes for (minor) issues in Debian packages that can be fixed by software. It gradually started proposing merges in early December. The first set of changes sent out ran lintian-brush on sid packages maintained in Git. This post is part of a series about the progress of the Janitor. The Janitor knows how to talk to different hosting platforms. For each hosting platform, it needs to support the platform- specific API for creating and managing merge proposals. For each hoster it also needs to have credentials. At the moment, it supports the GitHub API, Launchpad API and GitLab API. Both GitHub and Launchpad have only a single instance; the GitLab instances it supports are gitlab.com and salsa.debian.org. This provides coverage for the vast majority of Debian packages that can be accessed using Git. More than 75% of all packages are available on salsa - although in some cases, the Vcs-Git header has not yet been updated. Of the other 25%, the majority either does not declare where it is hosted using a Vcs-* header (10.5%), or have not yet migrated from alioth to another hosting platform (9.7%). A further 2.3% are hosted somewhere on GitHub (2%), Launchpad (0.18%) or GitLab.com (0.15%), in many cases in the same repository as the upstream code. Read more Also: Multiple git configurations depending on the repository path

Benchmarks and Graphics Leftovers: x86, Zink, and Navi

  • Intel Core i7 1165G7 Tiger Lake vs. AMD Ryzen 7 PRO 4750U Linux Performance

    For the Intel Tiger Lake Linux benchmarking thus far with the Core i7 1165G7 on the Dell XPS 13 9310 it's primarily been compared against the Ryzen 5 4500U and Ryzen 7 4700U on the AMD side since those are the only Renoir units within my possession. But a Phoronix reader recently provided me with remote access to his Lenovo ThinkPad X13 with Ryzen 7 PRO 4750U (8 cores / 16 threads) for seeing how the Tiger Lake performance compares against that higher-end SKU. Phoronix reader Tomas kindly provided SSH access to his ThinkPad X13 with Ryzen 7 PRO 4750U and 16GB of RAM. The Ryzen 7 PRO 4750U is quite close to the Ryzen 7 4800U with 8 cores / 16 threads but graphics capabilities in line with the 4700U. He's been quite happy with the ThinkPad X13 as a replacement to the Dell XPS 13 for business usage and has been running it with Ubuntu 18.04 LTS on the Linux 5.8 kernel.

  • Mike Blumenkrantz: Catching Up

    A rare Saturday post because I spent so much time this week intending to blog and then somehow not getting around to it. Let’s get to the status updates, and then I’m going to dive into the more interesting of the things I worked on over the past few days. Zink has just hit another big milestone that I’ve just invented: as of now, my branch is passing 97% of piglit tests up through GL 4.6 and ES 3.2, and it’s a huge improvement from earlier in the week when I was only at around 92%. That’s just over 1000 failure cases remaining out of ~41,000 tests. For perspective, a table.

  • AMD 'Big Navi' 3DMark Firestrike results shared by HW testing firm

    The Linux specialists over at Phoronix have noticed that the AMD Linux driver has been tweaked to add support for a new graphics card dubbed the "navi10 blockchain SKU". It comments that the only visible difference in support for this card vs existing Navi 1X support, from the driver perspective, is that the patches disable the Display Core Next (DCN) and Video Core Next (VCN) support - basically creating a 'headless' Navi 1X graphics card. Cryprocurrency is showing signs of a resurgence in popularity and values, and some are worried that the latest and greatest GPUs from both Nvidia and AMD will be plucked from retailers even faster if they are viable mining platforms. It has been reported that AMD is trying to make sure retailers follow certain distribution practices with its upcoming Radeon RX 6000 series products, to make sure they are distributed to gamers and enthusiasts rather than scalpers and such like. An initiative like creating appealing crypto-specific Navi 1X products might help everyday consumers get their hands on a new Navi 2X graphics card too.

Does the Snap Store Use Too Much Memory?

This week I noticed that the Snap Store app on my Ubuntu 20.10 laptop uses a tonne of memory, even when it’s not running — we’re talking more memory than the main GNOME Shell process uses, and that is always running! Naturally I assumed something in my config was to blame. I do make heavy use of Snap apps — don’t worry I use plenty of Flatpak and PPAs too. I’m pretty polyamorous when it comes to packaging formats and I did install using an Ubuntu 20.10 daily build. Therein lay bugs. I know the caveats. All good. Don’t mind. Whatever. Read more