By Jonathan Corbet
January 11, 2011
The formation of the Documentation Foundation and the launch of the
LibreOffice project have created a user and developer community which has
few parallels elsewhere in the free software world. This community is huge
given the newness of the project, and it appears to include many people who
have not engaged with free software development in the past.
As a result, the
Foundation's mailing lists sometimes host conversations that wouldn't be
found in other projects. An extensive and sometimes bitter debate on
whether LibreOffice should write files in the OOXML format is a good
example of differing views of how this project (and free software in
general) should work.
OOXML, of course, is the Microsoft-driven "standard" alternative to the ODF
format. Given its sponsor and the dubious
means by which it attained
"standard" status, OOXML was always going to be controversial. The simple
fact of the matter, though, is that, if Office writes OOXML files, then
those files will proliferate. Whether we like the format or not has little
influence on the final result.
Just before the end of the year, Larry Gusaas called on the LibreOffice community to refuse
to support the writing of OOXML files. Standard OpenOffice.org is able to
read such files, but will not write them; that is, according to Larry, how
things should be. But LibreOffice is based on the Go-oo project, which is
the version of OpenOffice.org which has actually been shipped by most Linux
distributions. This version does have the ability to write OOXML files;
thus, LibreOffice does as well.
Quite a few people supported Larry's desire for read-only OOXML support in
LibreOffice; one could easily peruse the thread and come to the conclusion
that the LibreOffice community is overwhelming opposed to the idea of
writing in that format. Even so, a number of LibreOffice developers have made it
clear (repeatedly) that they have no
intention of removing the ability to write OOXML
files. There is, thus, no need to worry that we might have to go on using
Go-oo after all.
There are many reasons for LibreOffice to support this format, even if the
community has to collectively hold its nose in the process. The reality of
the situation is that many LibreOffice users will need to work with people
who send them OOXML files and will expect to get a response in the same
format. Telling collaborators that their choice of document format is
unacceptable works in some situations, but a corporate employee who talks
that way to a customer may soon end up with a great deal of unexpected free
time. A LibreOffice which cannot write OOXML files would be unsuited to
many environments, and adoption would suffer accordingly.
Beyond that, as has been pointed out in the discussion, Microsoft will,
someday, phase out support for its (equally proprietary) DOC format,
leaving OOXML as the only real option for document interchange. There
appears to be little hope that Microsoft's ODF support will be sufficient
to make ODF a viable alternative. So any office
productivity suite which aspires to millions of users, and which does not
support OOXML, will find itself scrambling to add that support when DOC is
no longer an option. It seems better to maintain (and improve) that
support now than to be rushing to merge a substandard implementation in the
future.
A number of people in the LibreOffice community seem to be under the
impression that free software is about fighting Microsoft. But free
software is really about giving freedom to its users and developers; one of
the key ways in which that freedom has been expressed since the beginning
is through a high level of interoperability. Linux systems speak most
protocols, and they handle most file formats of interest. That makes it
possible to plug in a Linux system almost anywhere and to work with almost
everybody. We should think long and hard before we walk away from that
sort of freedom.
We should also think about (1) whether a project like LibreOffice really
has the weight to affect document format use by withholding support for
those it doesn't like, and (2) whether we as a community would want to
use that power in that way if we did have it.
There is a separate message from Larry which
brought out another interesting aspect of the debate:
It should be a community decision, not one made by the
developers. Or based on LibreOffice being based on Go-OO code which
already had OOXML write support because of the Novell agreement
with Microsoft.
It is a rare free software project indeed which allows a decision of this
kind to be made by anybody but the developers involved. Most such projects
are those controlled by corporations which have no qualms about vetoing
features which do not align with The Official Product Roadmap. Debian does
allow the community to shape its distribution through its general
resolution mechanism, but those who are allowed to vote on resolutions are
almost exclusively developers, and they are all contributors. Few other
communities even have a way by which the community as a whole could attempt
to make such a decision, much less enforce it. The Document Foundation's
proposed
bylaws do envision a board of directors and an engineering steering
committee which could address such issues, but such institutions will only
override the developers in extreme situations; otherwise, they tend not to
have many developers to override.
In the free software world, the people who do the work make the decisions
about that work, and there are few who would seek to change that state of
affairs. In this discussion, developers have not been calling for the
removal of full OOXML support, and no patches to that effect have been
posted. LibreOffice is shipping with that support, and that situation
seems unlikely to change.
So, it seems, the LibreOffice developers have made the decision to continue
to support
writing the OOXML format. They are well aware that OOXML is not an ideal document
format, that its attainment of "standard" status was shadowy at best, that
it is another proprietary moving-target format, and that there is still
some patent uncertainty surrounding it. They are aware that the much more
open (though still imperfect) ODF format is preferable, and that ODF should
be the default format used by LibreOffice. But they have also concluded
that supporting OOXML gives more freedom and capability to their users and
is good for LibreOffice in the long term.
(
Log in to post comments)