The free and open productivity suite

Abstract: In this talk we will give a brief introduction the OpenOffice.org buildbot as well as discuss and demonstrate several exciting new features. Buildbot is a system similar in purpose to tinderbox for the automatic generation of builds on multiple platforms. However, buildbot very flexible and we have bent it into new shapes for OpenOffice.org. Our improvements scratch several old itches such as change-triggered builds, easier client-side config, and ready-for-qa triggered install-set generation. We have also added several exciting new features such as the "try" facility, which allows a developer to build from just a patch. Additionally, we will demonstrate the new arbitrary data regression system, which enables the regression testing and tracking of nearly any kind of data. This system is quite powerful because it allows one to track based on groupings such as a cws vs the milestone is based off or the relative memory performance per arch relative to the milestone, etc.

Abstract: Panel discussion focused on the impact of the ODF standard and multiple supporting implementations within the I/T industry and governments worldwide.

Abstract: odftoolkit.openoffice.org is all about leveraging existing OOo technology to produce a chest of lightweight tools that let you do about everything related to ODF document handling. And odftoolkit is hot. That's one good reason to sit down and re-think how OOo is built, assembled, shipped, and installed. It should be much easier than it is today to take just those parts of OOo that are relevant for a task, combine them with whatever else is missing, and deliver your cool ODF tool to the waiting world. The OOo monolith is not quite there, yet. And there are more good reasons: faster builds, less quality control effort, smaller downloads, you name it. I will show you where this endeavor has brought us thus far, and where we are heading next. OOo on the whole should definitely benefit from this streamlining. Get into shape, fatty!

Abstract: Our paper is about Free Software Galician Initiative promoted by regional goverment of Galicia and our experience translating (including help) and promoting OpenOffice.org. More than 45.000 people acceded to Ooo through our portal (http://www.mancomun.org). Our version includes a Spellchecker and a Grammarchecker and improvements in Hunspell.

Abstract: This session discusses changes to the OpenOffice.org child workspace development process due to a change of the OpenOffice.org Source Control Management (SCM) system.

Abstract: This presentation brings a concept/standard/tool of realizing the interoperation between OpenOffice and MS office by UOML. Main points as following: a. Interoperation problem blocks Open Office b. Shortcoming of current solutions c. An effective and reliable interoperation way d. brief intoduction of UOML (Unstructured Operation Markup Language) e. Implement interoperation by UOML d. Benifits and value

Abstract: This presentation provides an overview of the OpenOffice.org Toolkit project. It is divided into two parts. The first part starts with an explanation of what an ODF toolkit is in general, and what the relation of an ODF toolkit is to ODF on the one hand, and to office desktop applications on the other hand. It continues with an overview of the OpenOffice.org Toolkit project itself, and its purpose. The second part of the presentations explains the technical details of the ODF Toolkit project. It provides on overview of the components and sub tasks of the project, and explains what the technical relation of the ODF Toolkit project to the OpenOffice.org productivity suite is. The presentation closes with an overview of what has been achieved since the project start in January 2007.

Abstract: The Catalan Translation team is one of oldest and most successful native language teams. Over seven years, this small band of enthusiasts have distributed over 2 million copies of OpenOffice.org in Catalan to the estimated 10 million Catalan speakers worldwide. In this session, we will try to explain the reason of that success.

Abstract: CVS is old, and it does not suite the OpenOffice.org development for quite some time. There is a lot of discussions what to use next. Subversion? Is it really an improvement over CVS considering the OpenOffice.org development cycle? And what about git? I am convinced that git is the right choice, that it has everything what CWS tooling provides these days, and a lot more. git is fast and efficient in branching, merging and resyncing, which are the operations that are essential in the OpenOffice.org development cycle. git is fast evolving, so if you miss a feature today, it might be introduced tomorrow; and still the fileformat does not change, the repositories are compatible from the first release of git. This talk will introduce git as a source code manager, it's application for OpenOffice.org, and the operations you might need. I will show a live OpenOffice.org git tree and the speed of the operations on that. I will also discuss the gains for the projects like ooo-build for which the upstreaming would become a very easy operation.

Abstract: OOo will support importing Microsoft Office 2007 OpenXML documents. But implementing the 6000+ pages specification is not without challenges. More than ever, OpenOffice.org must take the lead in interoperability and provide support for the format to allow migrating from Microsoft Office to OpenOffice.org. This will happen even before Microsoft Office for Macintosh does it. Novell has taken the Microsoft-sponsored open source ODF to OpenXML converter; a converter that they inverted and released with their version of OpenOffice to provide support in Writer. This is a temporary solution - as the whole spectrum of converters is being worked on - to import and export from Writer, Impress, Draw and Calc. This is the Sun & Novell joint endeavour, currently ongoing in both the 'oox' module and the writer filter rewrite. I will review the difficulties faced to implement perfect conversion from Office Open XML to OpenDocument and vice-versa. I will also give an overview of the technical choices made and the new infrastructure provided as part of the OOo API to parse these files. And I will finish with the state of the filters as they are in the current milestones.

Abstract: AODL is the .NET module of the ODF Toolkit. The .NET library is written in C# and will give developers the opportunity to extend their .NET based software to handle documents in the OpenDocument Format. Main focus of AODL is to offer ODF manipulation capabilities for developers without deep experience in the OO.o API.

Abstract: Migration to OpenOffice.org has just started in Japan. It is several years behind Europe. The reason of the delay comes from several aspects, especially functionalities that inadequately meet Japanese user's requirements. >From the three different migration cases we helped, we will try to shed some light on the reason. - A town office that migrates to Linux PC. - A company that migrates to OpenOffice.org running on Windows PC - A town office that migrates to StarSuite on SunRay and OpenOffice.org on Windows servers Additionally, the movement of the Japanese government towards open source software and open standard should be mentioned. The Ministry of Internal Affairs and Communication (MIC) has heard public comments on the new guideline of procurement. The Ministry of Economy, Trade and Industry (METI) has been promoting OSS. As one of its activities, the Seagull Research Team 2006 studied Japanese user's requests to OpenOffice.org and delivered them to core development team in Hamburg, Germany. This session will share information on migration with people from other countries and areas that are in the similar situation.

Abstract: First,Aimed at weakness QA in community development model,disscuss about how to unite professional team through providing complete and system QA for the product of OOo to make it to be more mature.Second,compare the difference of ODF and UOF,discuss about how to merge the two standard and in the process,what QA can be act as.

Abstract: This session will highlight one of Calc's lesser-known features, the DataPilot. Similar to Excel's PivotTable feature, it's a useful tool to summarize and analyze tabular data. I will give a short overview of the feature, show the DataPilotSource API which allows a UNO component to supply its own results into the DataPilot user interface, talk about recent improvements like the GETPIVOTDATA function, and give an outlook on future development.

Abstract: The session will explain what is meant with an UNO based ODF Toolkit API and where we see the advantages of such an UNO based toolkit. Identified ODF Toolkit use-cases are analyzed in consideration of the existing office API to reuse as much as possible of the existing code base. Potential missing API's are identified as well as improvements or even replacements of existing API's are suggested. Improvements will be suggested with focus on more intuitive and simpler API's where the UNO ease of use features will play a central role.

Abstract: tba

Abstract: The Department of Software Engineering at the University of Szeged, MultiRacio Ltd. and FrontEndART Ltd. recently accomplished a large project for analyzing, improving and monitoring the quality of OpenOffice.org source code. The project was 26 months long and had a volume of 0.54 million Euros (supported with 0.4 million Euros by the European Union). We developed technologies and tools for measuring the quality of the source code. The applied methods included the automatic analysis of the source code and the extraction of information from which we calculated standard metrics like cohesion and coupling. Our tools scanned the source code of OpenOffice.org releases and stored the measured values in an SQL database. The results can be accessed and queried through a web-based interface. Using the extracted information our tools also audited the code to detect bugs and identify design problems in the code. The problematic code fragments were refactored by the developers of MultiRacio Ltd. to obtain better quality code and the resulting patches were contributed back to the OpenOffice.org community. The source code of OpenOffice.org will be scanned regularly also in the future (http://www.frontendart.com/ooomo.php). It is also possible to apply this quality assessment and monitoring system to other projects developed in C/C++/C#/Java languages. The web site of the project contains more details about the results (http://oopp.multiracio.com/).

Abstract: Last year at OOCon we hinted at greater co-operation between Novell & Sun with respect to the VBA Interoperability incubator project. Things have moved forward and this year we'd like to do a presentation updating the community or where we are now. We'd like to talk about the interoperability project and whats happened since last year, the recent announcement of collaboration between Sun and Novell, the rational behind that decision. We'd like to talk about what that means for the project, how it's changed the direction, architecture, structure and implementation or the original solution. We'd like also to give an update as to what currently is supported, whats coming next, what are problem areas and do some demos. We'd also like to talk about how YOU can help.

Abstract: OpenDocument Format (ODF) is a an open XML based file format for office productivity applications. The specification of which is maintained by the OASIS OpenDocument Technical Committee The OASIS membership has recently ratified revision 1.1 of the specification and revision 1.0 is also available as an ISO/IEC standard. The open nature of the ODF specification has spurred adoption of the format by multiple applications. Furthermore, ODF is well suited for being processed outside of end-user applications. This paper explains the basic structure of ODF and how standard XML processing tools can be used to create applications beyond the scope of traditional office productivity applications.

Abstract: As part of a government drive towards technology accessibility and inclusivity for all in South Africa, the CSIR (Council for Scientific and Industrial Research) initiated a project to migrate the organisation to only use Open Source Software. The first phase of this project included the development of a customised, Linux-based CSIR desktop as well as a adoption of ODF (open document format) as document standard within the organisation of approximately 2000 employees. The experience of the CSIR with regards to the adoption of ODF as standard within the organisation is discussed in this presentation. In addition, this presentation contains a motivation for, as well as a discussion on, the aspects to consider with the adoption of ODF as document standard, specifically with regards to the South African public sector.

Abstract: Brief introduction of Lotus Productivity Tools from a technical point of view, will demonstrate the high level architecture of Lotus Productivity Tools, the features we have added on top of OOo code base, and will introduce its programming model. We'll also describe the code which we are initially contributing to OpenOffice.org,

Abstract: We will report on the current status of the documentation project and outline trends, opportunities, and challenges for the upcoming year. A focus will be put on how to increase participation in the project and how to consolidate documentation efforts across OpenOffice.org.

Abstract: OpenDocument Format 1.2 will feature a new, RDF-based metadata model. Metadata is simply data about data. RDF-based metadata leverages all the work done for the Semantic Web onto ODF applications and documents. The enhancement of ODF metadata with the RDF model will: * Enable enrichment of content in ODF based documents * Enable seamless integration with other RDF-based metadata * Enable ODF documents to work with semantically "aware" applications * Provide a foundation for the next generation of ODF plugins Support for RDF-based metadata is expected in OpenOffice 3.0! Component developers and users can catch a peek at the future! This presentation provides a technical introduction into the RDF-based metadata model. Examples of the future made possible for OpenOffice.org components will be covered.

Abstract: In this session, the complete localization process of three Chinese minority languages - Mongolian, Tibetan and Uighur – in OpenOffice.org is discussed. Unlike Latin and Chinese, Mongolian, Tibetan and Uighur are all so-called complex script, and they exhibit very sophisticated features during the text output process. It can not help but take some special technologies such as smart font and complex text layout engine to render these languages. In order to meet the requirement of Mongolian text layout direction, OpenOffice.org is extended to support another text direction – vertical, from top to bottom, from left to right. Backed by OpenOffice.org i18n framework, locale data for Mongolian, Tibetan and Uighur is added to the i18npool module. The Tibetan GUI translation is migrating from OpenOffice.org 1.1.x to the latest version to be submitted it to the community.

Abstract: An informal roundtable where distinguished guests will speak to the future of ODF, OpenOffice.org, and FOSS.