A COUPLE of days ago we helped introduce LibreOffice, which contrary to what some Mono/Novell trolls are saying, is not a rebranded Go-OO. The idea is similar in the sense that copyright assignment gets changed, but here there are a lot of vendors involved and the steering committee is diverse.
I had a chance to ask Charles-H. Schultz, on the steering committee of The Document Foundation some questions I had swirling in my mind after their announcement today of LibreOffice, and he was kind enough to take time on a really busy day to answer.
I wanted to know about Mono and OOXML and all the things you are wondering about too. I had become quite worried about OpenOffice.org and Go-OO, and naturally that was on my mind, given who is involved in LibreOffice. The answers are reassuring. The Document Foundation is serious about avoiding non-free elements, and they are on the same page about that. I guess that's how they got Richard Stallman to bless the project, now that I think of it, along with so many others. And I wanted to ask him how we all can help out.
[...]
Question 2: What about Mono? What about OOXML?
Schultz: Well, that's quite easy. Mono was never really inside OOo or Go-OO to start with. What was inside Go-OO was the possibility of Mono integration, and even that sort of exists inside the "vanilla OOo". So we made sure that didn't add to this.
As for OOXML, well, we didn't take the Go-OO approach and did not include the patches developed with the "aid" of Microsoft. All in all, LibreOffice is clean, very clean, and we look forward stay that way. But enough talking on OOXML, a standard that does not exist. Let's rather focus on ODF, an existing open standard we support and promote.
I saw discussions on freenode about how to compile localized version. I saw Twitter run more than 800 tweets per hour and I have heard about Catalan hackers talk with Spanish journalists. The last thing - I have heard - doasn't happen every day.
It’s getting harder to be a monopoly these days. Microsoft owned the desktop for decades, milking its Windows platforms every step of the way. Apple, on the other hand, hadn’t even managed four years of iOS dominance before Google’s Android staked a serious claim to the mobile market.
This isn’t because Microsoft is somehow smarter than Apple, but rather because the underlying dynamics of the technology industry have fundamentally changed. In brief, the technology world is increasingly embracing “write” communities, as Jono Bacon calls them, not simply “read” communities. Open source may have kickstarted this trend, but open APIs and open data are taking it to new heights.
Which is not to say that LibreOffice will not be a success, but when it comes to forking, creating the fork is clearly just the start. It takes time, and a lot of effort, to generate the momentum for a fork to be truly successful. There is bound to be an initial spike in developer and user interest. Turning that into a meaningful and productive community will be the hard part.
Companies that develop free software and release it under the GNU GPL sometimes distribute some copies of the code in other ways. If they distribute the exact same code under a different license to certain users that pay for this, typically permitting including the code in proprietary programs, we call it "selling exceptions". If they distribute some version of the code solely in a proprietary manner, we call that releasing a purely proprietary version of the program.
What I mean by a fork, by the by, is an actual split in the code. For example, Ubuntu can be seen as a fork of Debian. No one doubts that Ubuntu is based on Debian Linux, but it's also clearly a Linux distribution in its own right. Simply changing out some trademarks and product names, which, for example, is what Oracle did with Red Hat Enterprise Linux when it created Oracle Linux, isn't the same thing. At this early point, that's all the Document Foundation has done with OpenOffice.
My expectation is that Oracle will quietly let OpenOffice gather dust, and LibreOffice will become the new open-source office suite of choice. What do you think?