linuxinsider.com (blog safari): Would a rose by any other name still smell as sweet? Or would it, perhaps, end up sweeter? That, essentially, is the question at the heart of the forking process. Namely: Now that we have LibreOffice, do we still need OpenOffice?
- Open Source Suites Highly Active
- When is a release not a release?
- Apache OpenOffice - Interview with Jürgen Schmidt
internetnews.com: If anyone had any real doubt, IBM is the one solid reason why OpenOffice still exits. Linux distros big and small have all left for the superior open source experience that is LibreOffice, yet IBM is stuck in the past.
infoworld.com: In its new role as steward of the OpenOffice.org open source office suite, the Apache Software Foundation expects to offer an Apache-branded version of the package for developers in 2012.
dedoimedo.com: It's been about a year and a half since I have last reviewed OpenOffice4Kids (OOo4Kids), which is a special version of OpenOffice for children aged 6-12 more or less. Now, the software has grown to version 1.2. Let's see what it can do.
pcworld.com (IDG): Despite the growing momentum of the LibreOffice fork of OpenOffice, the Apache Software Foundation (ASF) is urging the community of volunteer developers to rally around the OpenOffice code base as the canonical version of the open source software suite.
theregister.co.uk: On Wednesday a new website will be launched with many donation options, spokesperson Andreas Jäger told The Register: "The organisation will also look for a major investor, but one that fits the product."
networkworld.com: Over the weekend, LibreOffice took the Experiment award for most appreciated software at the Open World Forum in Paris. I use LibreOffice every day, so I definitely think the award is well-deserved. Here are three particularly useful add-ons to improve your office tools:
h-online.com: Michael Meeks, a LibreOffice developer at Novell, compared the codebase of LibreOffice with the OpenOffice.org sources hosted at the Apache Software Foundation (ASF). As he writes in a blog post, the differences are already so great that it will now be hard to exchange new code between the two projects.