KOffice Developers At The First ODF Plugfest
The first ODF Plugfest was held on the 15th and 16th of June 2009 in the Royal Library in the Netherlands. The meeting was initiated by the Dutch government and the OpenDoc Society. Jos van den Oever, brand new employee of KO GmbH and Sven Langkamp, proud developer, went on behalf of the KOffice team. With over forty organisations and a total of sixty representatives from businesses, public sector organizations, open source projects and research institutions, the meeting was an incredible success.
Read on for an impression of the event.
Dutch minister for Foreign Trade Frank Heemskerk held an opening speech, outlining why the Dutch government pushes the usage of the three Os: Open Standards, Open Content and Open Source Software. Interoperability brings a better market and thus leads to better quality, lower prices, more innovation and vendor independence. The Netherlands wants to join the Scandinavian countries in becoming one of the leading countries in adopting ODF and Open Source software. Unfortunately, as we learned later on, the adoption of ODF is progressing very slowly. Fabrice Mous, one of the organizing members of NOIV (Netherlands Open In Connection) outlined the current rather unfortunate situation. ODF adoption has a very low priority in local government throughout the Netherlands, in part because they feel they have little use for it. The work by NOIV might change this during the coming years.
Further talks went into subjects such as adoption and innovation. The work by various organizations was put into the spotlight, ending with OfficeShots. Officeshots offers application developers a way to test their ODF compatibility. You can upload a document and receive the output (in the form of screenshots, PDF or roundtrip ODF files) from various office suites. KOffice developers value OfficeShots as a valuable tool for improving the upcoming version 2.1. Currently, Google Docs and Microsoft Office are missing from this service, and while the attendants asked the Google and Microsoft representatives, it is not sure they will be available soon.
Microsoft’s Doug Mahugh gave a talk (using OpenOffice) explaining what Microsoft has been doing with their ODF implementation. They provided notes on the implementation and their interpretation of the specifications. During the Plugfest it was agreed among the participants to follow this example and share notes on the specific implementations. Later Doug was found talking to Sven – he was interested in the state of the KOffice installer on Windows. Apparently Redmond has had a look at KOffice… Doug’s blogpost about the Plugfest is worth a read. You can watch the rest of the talks at vimeo
The value of the meeting, however, lies not only in the talks, but also in the informal chatter and the hard work being put in the common test scenarios. The organisation initiated scenario-based testing, where specific parts of the ODF standard were tested by following instructions to create a document. Several bugs impeding greater interoperability between and among ODF-supporting software were uncovered and discussed, including one interoperability issue simultaneously present in KOffice, OpenOffice and Microsoft Office. In response to the positive reception from participants, a website will be developed where virtual "Plugfests" can be conducted online.
The event felt like ‘everybody’ was there, with ‘corporate dudes’ from Sun, IBM and Microsoft, to government agencies like the Munich city government, research institutes like Fraunhofer and of course members from communities like Abiword, KOffice and OpenGOO. Putting so many people with so many different perspectives and ideas together leads to an interesting atmosphere, competition and cooperation hand in hand. All in all, it turned out to be two productive and challenging days.
The KOffice team thanks Fabrice Mous and Michiel Leenaars, the OpenDoc society, the Dutch government and all the other sponsors for organizing the workshop.
Some pictures of the event can be found on Picasaweb and Flickr.