April 17, 2011
"Oracle Corporation (NASDAQ: ORCL) today is announcing its intention to move OpenOffice.org to a purely community-based open source project and to no longer offer a commercial version of Open Office."

From Trond’s Opening Standard.

This is after Oracle’s management of the OpenOffice.org community led to a successful fork of the project: LibreOffice. Oracle, you’re doing it definitely wrong.

March 1, 2011
Brilliant Future Ahead for LibreOffice

LibreOffice contributions
Copyright © 2010 Linux Journal. All rights reserved.

I think this chart from Who Contributes the Most to LibreOffice? summarizes it all: 133 new coders and 55 localizers since the fork!

This is good news, to add to LibreOffice obtaining the 50,000€ needed for The Document Foundation. Go LibreOffice!

September 28, 2010
"LibreOffice is going to be a fun place for developers to live, and strike their blow for freedom - without a doubt. Get involved now, and help to shape the software and the social life for the next decade."

From The story behind the story behind the news today by Michael Meeks, regarding The Document Foundation.

Good news! (and about time!)

July 31, 2010
Making Reports in CVS from SQL

Sometimes I need to query a database, using SQL for that, and get the results to process them with OOo Calc o any other data analysis tool (for example GNU Plot).

The most easy way to import data into OOo Calc is using CSV, but the SQL clients I usually have at hand doesn’t support that output format and I always end using some AWK magic to get a correct CSV.

It’s not a big deal, but last week I had a different problem at work: what if you have to do different queries in different databases depending on a main table?

In fact, it was a multi-tenant application with one database for each instance, that can be in any of machine in our backend cluster, so having the list of the databases wouldn’t help.

Due to this I had to execute a query to get the database name and the connection information for each instance, and then run the query I actually needed for my report.

I did the work, and the report it’s being generated automatically as the customer requested, but I wasn’t satisfied with the resulting code (you know what happens when you don’t have enough time to do your work), so I’ve spent some of my spare time programming a tool to make easier this kind of reports: YAML Simple SQL Reports (yes, I know… what a fancy name!).

The idea is to specify the report in a YAML file. For example:

report:
    name: first report
    connect:
        type: mysql
        database: dbname
        username: user
        password: secret
    query: select foo, foo2 as whatever from bar
    output: file.csv

This will generate a CSV file into file.csv, with foo, whatever header and one line for each row resulting of the query.

At this point, al least, I got rid of the AWK post-processing. But, what about the multi-database problem? Easy peasy with subreports!

report:
    name: first report
    connect:
        type: mysql
        database: dbname
        username: user
        password: secret
    query: select dbname, dbhost, dbpasswd, dbuser from masterdb
    report:
        name: sub report
        connect:
            type: mysql
            dabase: {dbname}
            hostname: {dbhost}
            username: {dbuser}
            password: {dbpasswd}
        query: select * from table
    output: file.xml

The query in first report is executed, and for each row in the result, the report named sub report is executed (after replacing the {KEY} stuff in each loop with the value from the result row). The result of all the queries in sub report are concatenated and used as output (in this example as XML).

It’s not the ultimate tool to make reports, but it will work for me next time I’m asked to do a report ASAP from any SQL database.

Update: you can get the stable versions from the downloads section of github. PostgreSQL it’s being tested, and will be version 0.3.

July 8, 2010
"Why would StarDivision want to draw attention to their traditional feature gap, by making noise about shipping multimedia support four+ years late? while simultaneously alienating valuable contributors and continuing to tear down its developer community (that would love to help close OO.o’s feature gap)?"

From OpenOffice & GStreamer, by Michael Meeks.

Very good question, and a worth reading post.

I really enjoyed the quality argument part, because you know how pleased I am with OpenOffice.org’s quality (just in case: I’m being sarcastic).

June 22, 2010
"The number one reason why Sun bought StarDivision in 1999 was because, at the time, Sun had something approaching forty-two thousand employees. Pretty much every one of them had to have both a Unix workstation and a Windows laptop. And it was cheaper to go buy a company that could make a Solaris and Linux desktop productivity suite than it was to buy forty-two thousand licenses from Microsoft."

OpenOffice at the crossroads, a conversation with Michael Meeks by Richard Hillesley.

The quote is from Simon Phipps, an ex-Sun employee.

June 20, 2010
Ubuntu Lucid and OpenOffice.org 3.2 Instability

This is a rant. You have been warned.

About a month ago, Alex upgraded her netbook to Ubuntu Lucid, and the results have been quite disappointing.

The main issue of the previous version was fixed (poor pulseaudio support), but fresh and new problems appeared, resulting in a worse experience.

Canonical people changed some aspects of the UI in the Ubuntu Netbook Edition, that forced Alex to change her way of doing things in different day-to-day tasks (for example, removing the left quick access to bookmarked directories it’s a small failure, if you’re a teacher and you can’t afford the extra clicks to move to different directories with a class of year 7 kids waiting any kind of distraction to make noise and take over your lesson).

It may sound like overreaction, but it’s important when the computer it’s just a tool in your work and you have to suffer changes that (apparently) are just for the sake of change, and you can’t change this new behaviour back to the old that works for you!

Anyway, I was willing to talk about OpenOffice.org 3.2 release, that is the one that comes packaged with Lucid.

The main problem seems some kind of incompatibility with the Ubuntu Netbook Edition desktop, that makes the mouse buttons to stop working randomly, and we haven’t figured out how to workaround it (besides restarting the desktop session); so we had to fall back to the “classic” Gnome desktop.

Although the problem happens in the Gnome desktop too, we can workaround it (sometimes pressing ESC will fix it, other times you have to open a Nautilus browser and then go back to Writer, there’s not a clear pattern).

Needless to say this makes Alex work harder and painful, and added to the other changes in Lucid, she’s almost convinced that upgrading was a mistake.

And finally, to make things even worse, she’s filling job applications for next year, and all of them are Microsoft Word documents. Guess what: OpenOffice.org crashes with most of them.

OK, I think we can live with visualization problems. After all, I expect this kind of problem between different Microsoft Office versions (I guess so, I’m not Microsoft user). But crashing constantly it’s frustrating, and crashing on save with data loss it’s a nightmare.

So we’re thinking about moving to another distribution. Filling a bug report now with Ubuntu it’s useless now, because the problem will be fixed most likely in next release, and… who can afford a system that doesn’t work for 6 months?

I don’t know what happened in Lucid, but from my experience, that’s the worst Ubuntu release so far. We’re suffering bugs that make feel unpolished and low quality, with an unpleasant user experience, and that’s the first time ever I have that feeling with Ubuntu.

December 22, 2009
OpenOffice.org announces "end-of-life" for version 2.x of its productivity suite

Via OpenOffice 2.x End Of Life at Hellow’s Blog.

I’ve found pretty interesting the FAQ part:

What does end-of-life status mean? Is the software unusable now?

So, can I go on using the old version?

I’m a Linux user, and my copy of OpenOffice.org comes from my distributor’s repository. Am I affected?

Why can’t the community support older releases for a longer period of time?

Check it, because it’s very interesting. The End Of Life concept it’s very often misunderstood, because people tend to not get the difference between vendor support (also called upstream), and the distributor support.

April 24, 2009
"For some reason people like to ask me what Oracle’s acquisition of Sun means for OO.o - luckily I don’t know […]. What I do know is that if Sun had acted, as advised, in a truly open fashion, and built a project that other companies, large and small could invest in and work with fairly: things would be better. […] As a side effect, that would have made individual developers with OO.o skills, and the project itself very much more secure against uncertainty at any single company."

From Stuff Michael Meeks is doing. I agree with Michael.

Shame on you Sun!