||10-14-2010 02:11 PM
After reading about Eric's travails building LibreOffice, and my own grustrtions with Go-OO several months back (until somebody posted a good SlackBuild for it), I have to wonder why the source code isn't organized in a way that makes it easier to build.
Okay, it looks like the LibreOffice team are on it based on the interview posted above
(thanks for the link, Sahko):
Mr Meeks says:
For developers, we are open for business - we have a realistic view of the code-base and as such we are interested in including people's fixes and improvements quickly. When we can get people working to clean up the code, translate German comments, remove dead code, fix ergonomic nits, write unit tests and so on - we are optimistic that we can produce a far better product, and one that (as developers) we can be proud of.
Linux distributions should find LibreOffice easier to package, as the development team has a vast amount of Linux distribution experience.
All of that of course leads to getting a better, more stable, and featureful office suite into users' hands.
The other thing I wonder about is where things are going with the OO.org user interface update project
. There was a lively debate around that project on how to update the user interface to make things better and whether or not to mimic Microsoft Office's new UI.
With all of that as background, and with LibreOffice being a fork, I have to wonder just how much of Open Office's code they're going to use in the future.