Abstract: This presentation examines the state of the project after eight years of continued extraordinary growth and activity. The focus is on work that has been done in the last year, in particular, OpenOffice.org 3.0, and our ambitions for the coming year. Briefly: OpenOffice.org 3.0 represents both a cumulative accomplishment by the community, a peak reached after years not just of coding but of organization, and a point of departure. At this point, OpenOffice.org has reached, I believe, a status in the world that places it not just on equal footing with any other productivity suite but above. OpenOffice.org 3.0, equipped with the ODF, goes well beyond any single productivity suite or application; rather, it functions a primary star in a constellation of applications that are giving all users the tools and reach to do what they want, what they dream of. With this exuberant moment reached, what then for the coming year? Should we expect new features, new code? Perhaps a new look? This presentation will look at some suggestions, but as with all such presentations, the focus will be on honouring those who have taken us to where we are now and whose vision will take us even farther.

Abstract: The OpenOffice.org user experience team runs several activities to get direct usability feedback from our users and works on a community based usability improvement process to increase community participation in the project. Beside a report on the state of the project we will also give an overview about our activities towards OpenOffice.org 3.1. The panel will end with an extended QA session.

Abstract: The OpenOffice.org documentation project is a community effort focused on creating and maintaining all aspects of the documentation for OpenOffice.org. We will report on the current status of the documentation project and outline the trends, opportunities, and challenges for the upcoming year. A focus will be put on importance of the OpenOffice.org community effort, how to increase community participation in the project, and how to consolidate the documentation efforts across OpenOffice.org.

Abstract: The presentation gives an overview of the technology behind OpenOffice.org Portable. Which different portable storage devices are able to run this special version of OpenOffice.org and what's to keep in mind when using this special version. The presentation will also inform about the benefits of OpenOffice.org Portable, especially for marketing OpenOffice.org

Abstract: The Mozilla Calendar project is an Open-Source project that drives the development of the standalone application ?Sunbird? and its counterpart ?Lightning? that can be added as an extension to the popular email client ?Thunderbird?. In this presentation I'd like to talk about the capabilities of Sunbird and Lightning - also in comparison to competitive applications-, about the current status of the project and its future perspective. Being a perfect appendix to OpenOffice.org I want to present ideas how the two projects could be linked together more tightly in the future as calendaring is not offered by the office suite. But this presentation should also address developers or other people who are interested in getting involved in a comparatively manageable and somehow ?familial? Open-Source project that yet has found a worldwide broad distribution. Therefore I'd like to introduce the underlying technologies XUL, XBL, JavaScript and explain how the Mozilla community is organized and what is the best way to get started.

Abstract: In this presentation I would share our experience in migrating from MS Office to OpenOffice in my company. We Start it with IT Regulation, and then build an awareness to all of the employee. Trained them to work with the new environment. And implement it. With full commitment of the Board of Directors, we get a successful result.

Abstract: OOo deployments by big companies and local governments, and perspective of OOo professional support services On May 12th Sumitomo Electric Industries Ltd announced they will use OpenOffice.org company-wide.[1] On May 28th, Mayor Ichiro Kanke announced the city government will introduce OpenOffice.org into all its offices.[2] They bought Ashisuto Co's [3] support services such as training, FAQ and e-learning. They also build inhouse support tools such as an original installer, Help Desk, Intranet Web support pages. Good-Day Inc., a long-time OOo supporter, has a big client, NTT Group [5], who is planning massive OOo deployment and seeking sustainable and efficient OOo support services professional. Why did they adopt OpenOffice.org? What kind of support they want? What is sustainable and efficient support? My presentation will try to answer these questions. [1] http://openoffice.exblog.jp/7104488/ [2] http://openoffice.exblog.jp/7168127/ [3] http://www.ashisuto.co.jp/english/index.html [4] http://www.good-day.jp/en/index_html [5] http://www.ntt.co.jp/index_e.html

Abstract: We have been facing startup, document loading/saving performance challenges, which have great impact to user experiences. In this session, we would like to introduce what we have done to improve Symphony performance in above areas, e.g. asynchronous loading, saving performance improvement by saving modified content only and preload etc. We see the big performance improvement through the work above. Most of those techniques, solution or method could be applied to OpenOffice.org base application performance as well. We also will share our practices - performance benchmark design, and automated performance testing, tools and methodology used to analyze and identify Symphony performance problems.

Abstract: What are the needs and the musts in the QA project and why the 'stupid' QA work is very important for the whole OOo project and for the product itself. Also I will present which QA metrics are used to give a Go/No-go for a release. Information about the QA processes and the collaboration between the Sun QA team and the QA community will be given.

Abstract: QUASTe is collecting, validating and comparing all test results created by VCL-Testtool while testing OpenOffice.org builds and creates easy to read results pages. Everyone interested in quality of a specific build of OpenOffice.org has the ability to check the results of automated and of course manual tests. If one is familiar in running/writing automated tests you should create an account in QUASTe to administrate your tests or upload test results of your personal test runs of a specific build. See Web page (http://quaste.services.openoffice.org) for details

Abstract: This presentation introduces the QA at Redflag, mainly the people, their responsibilities and the processes they use for testing. It will both feature the achievements of the past and our plans for the future. As well, we will take a look at existing difficulties we have in joining the OOo QA and our ideas to resolve the problems. Last but not least, we also want to express our appreciation to all the people who helped us to join the OOo community so far and in the future.

Abstract: Adventures into building and packaging have caused OpenOffice.org 3 to change substantially in shape (though not in user-visible functionality). The infamous Three Layer Office was borne, received by developers with mixed reactions. Change!? For better? For worse? For what reason at all, if the user does not notice it, anyway? I will try to recap how and why we got where we currently are, and how we can and should move into the future. I will talk about the disasters (so we can avoid them next time) as well as the things that really worked and helped bring us forward. Maybe that will allow some of you to reconsider your love-hate relationship with OOo 3. So that, ultimately, those adventures can be brought to a happy ending – for all of us.

Abstract: The presentation will shed some light on the way how OpenOffice.org is distributed and what tools are used to release OpenOffice.org to the community by using the mirror network. Aspects of the release process in coordination with the QA project and QA teams of native language teams are shown. The following items will be presented: o Why using a distribution network? o Some numbers (platforms, languages, downloads, etc.) o What is a distribution network? o QUASTE o QATrack o mirror network + regular mirror network + extended mirror network + archive mirror network o Bouncer o Product Update Notification

Abstract: Demonstrate an ODF Wiki and show how this approach may be extended to enable advanced use cases such as collaboration and compound documents, extending ODF's reach to the server. See also: http://blogs.sun.com/GullFOSS/entry/odf_www_an_odf_wiki

Abstract: OOo3 now has a server! People increasingly need to work connected. They need to get their document reviewed, annotated, shared, approved by people, peers and superiors with whom they are working with. Yet there's no server mechanism exist today which would enable people to do that quickly, easily and conveniently. As a result, people are still working semi off-line. They compose their document online using OpenOffice, then they process it across manually, or ? at best ? circulate it via email. Such approach doesn't provide the complete feature nor integrated ?working assembly? mechanism that would make tracking, managing, sharing, filing, measuring and digital tracing work that has been done quickly, easily nor conveniently. Through its ?digital workdesk? and unique ?work-processing? functionality, Woorknet ? the OpenOfficeServer -- try to provide such seamless working assembly mechanism, integrated seamlessly with OOo as the ?digital paper? front-end. Developed and enhance further together, this, we feel -- perhaps could be one of the major differentiator of OpenOffice.org in the future compared with what Microsoft can offer with their MS-Office offerings. This also could be the source of advancement whereby OpenOffice.org and its underlying ODF transform from being a "traditional" document word processor and spreadsheet, to become a true "digital paper" for social and business -- an integral and integrated part of new and future digital office system and work-processing systems that people will need to help them work-connected, around the globe.

Abstract: The interest in OpenOffice.org and its file format, called Open Document Format (ODF), has been growing in the past few years. This has resulted in increased demand to integrate OpenOpen into DMS/CMS systems. As the growing number of DMS vendors offering a proprietary in interface to gain access to their underlying content repository the integration of them gets more complicated. The presentation is going to show how all these Systems could be integrated into OpenOffice by using a single extension. The Content Repository for Java technology API is used to establish the communication between OpenOffice and the DMS system. The presentation will demonstrate the Integration and the communication by using the "jackrabbit" project.

Abstract: The presentation will reflect the extensions repository after 1 year. The session will highlight the most popular extensions, will present the current status, future plans etc. The presentation will also summarize the latest extension infra-structure features that can be used to integrate best in OpenOffice.org and that improve the overall usability of extensions like the new extensions manager UI.

Abstract: This presentation introduces the OpenOffice.org Java based scripting framework and how it allows to add a scripting language of your choice to OpenOffice.org. Using the open source scripting framework "Bean Scripting Framework (BSF)", version 2.4, from the Apache Software Foundation (ASF), it becomes possible to bridge any of the many BSF supported scripting languages with the OpenOffice.org scripting framework. In effect, the combination of both Java-based frameworks allows to employ additional scripting languages as macro languages for OpenOffice.org, like Groovy, Jython (Python in Java), Jacl (TcL in Java), JLog (Prolog in Java) and the like. This presentation will use the open source scripting language "Open Object Rexx (ooRexx)" as a proof of concept. Using ooRexx is interesting for different reasons, one being, that it is implemented in C++ yet allows to be used via Java. Hence, the audience will learn that practically any scripting language could be used for OpenOffice.org. There will be a few, easy to understand scripting examples given, which demonstrate how one becomes able to remote control all of OpenOffice.org from any scripting language that takes advantage of the OpenOffice.org scripting framework. The presentation concludes with a possible outlook to incorporate BSF 3.0 (currently in beta) to OpenOffice.org. BSF 3.0 is an open source implementation of the JSR-223 Java standard for the Java scripting framework as introduced with Java 6 (1.6) by Sun. Goal: the audience should be able to conceptually understand the OOo Java based scripting framework, the BSF 2.4 scripting framework and become able to assess and implement new scripting languages for OpenOffice.org, including of how easy it is to employ those scripting languages thereafter by exploiting the respective OOo APIs.

Abstract: Open Source brings us the possibility to join existing programs for our needs. The advantages of each can boost usability and work-flow. But do we really need to study the source code of large projects to fit the parts together in every case? The OpenOffice.org-API enables us to write gluing-code in form of extensions. This session will show an example how extensions help making a publishing framework like Apache Forrest becoming a little but powerful "Documentation Management System" with a GUI that is well known - OpenOffice.org. The example extension will be downloadable from the OpenOffice.org Extension Repository by the date of the OpenOffice.org Conference 2008. You can see the extension in action and have a look at the code - if you want.

Abstract: The current accelerator configuration, which is XML based, cannot be extended by packages. In order to support extensions, we move the accelerator configuration to an XCS/XCU based configuration. Now an extension can define it's own set of accelerators.

Abstract: Lotus Symphony leverages OpenOffice.org technology and rich client platform form Lotus Expeditor, resulting a more flexible and extensible offering for extension and business integration. OpenOffice.org provides the capability to access and manipulate document content directly. Lotus Expeditor delivers the higher level programming interfaces for customizing the user interface (for example toolbars, menus, side shelves, status bars) and a plug-in framework to extend with other applications. More ever, lots of advanced features from Lotus Expeditor can be integrated for solution development, for example composite application, enterprise content management, account framework, etc.

Abstract: The OpenOffice.org plug-in for Netbenas has been around for a while now. The download numbers show that it is very popular and the feedback by users is huge. Unfortunately, the resonance regarding the actual project has been sparse, although it has been an open source project from the beginning on. I will give some insight on how the plug-in is constructed and what the challenges in making it were. A large part will be the changes that had to be done regarding NetBeans 6 on one side and OpenOffice 3 on the other. I will also give an outlook on what is planned in future versions ? and the possibilities a closer interlocking with NetBeans will offer.

Abstract: The presentation will give an overview on features provided by the framework project which can be used by developers to integrate their extension seamlessly into the OpenOffice.org user interface. The presentation is a guideline to understand the purpose of the features, possible use cases and provide examples. The following features will be presented: o Complex Toolbar Controller o Popup Menu Controller o Context Menu Interceptor o Merging of menu and toolbar items o Custom images for menu and toolbar items o Keyboard shortcuts

Abstract: Adding a new dynamic scripting language to OpenOffice.org is possible by exploiting the Java based OpenOffice.org scripting framework. However, programming and remote-controlling OpenOffice.org with the "Unified Network Objects (UNO)" framework can be quite challenging. As a result, it is quite difficult to teach/train end-user programmers to automate (remote-control) the different OpenOffice.org document types. Therefore, OpenOffice.org dynamic scripting languages like OOo Basic or Python provide support for easing programming of OOo, e.g. by implicitly carrying out queryInterface()-calls and as such alleviating the (end-user) programmer from this sometimes pesky task. Introducing new dynamic scripting languages to OOo will most likely challenge the implementer for creating an appropriate scripting language support specifically for OpenOffice.org. This presentation will use the "Open Object Rexx (ooRexx)" dynamic scripting language as an example and discusses the many fold possibilities of creating support for OOo. As the author of such an OOo supporting infrastructure who also has been gaining experiences with end-user type of programmers (students at the Vienna University of Economics and Business Administration) for more than two years by now, the most important pros and cons of such a specific support will be talked and discussed about. Goal: the audience will learn the most important areas of OpenOffice.org programming for which specific support could and should be created for new scripting languages. However, it also should become aware of thinking about trade-offs between creating too much and too few such support.

Abstract: The Translate Toolkit and Pootle are powerful tools for translation and translation management. The tools are widely used in the open source world and notably by OpenOffice.org. We discuss new language specific quality checks and demonstrate improvements specific to OpenOffice.org. In this session, we also discuss current roadmaps, learn about tool development, and listen to feedback from users and localizers. This is your chance to learn about new features and to influence the future of Pootle.

Abstract: OpenOffice is normally localized using PO format files. The amount of process or meta information that is possible to code into this files is quite restricted. XLIFF files are designed to include most of the information needed to facilitate and improve computer assisted localization. In particular, the two major advantages of XLIFF files are 1) that it is possible to store in them specific glossary and translation memory (TM) information that will be useful for the translator to translate the messages in that file, 2) that it is possible to follow the localization workflow, so that reviewers and those who need to approve the translations know exactly the status of each message (if it was reviewed after its translation or not, etc.) largely reducing the amount of work that they have to do. Localization editors that use all the information stored in XLIFF files can help provide homogeneous translations produced by less experienced translators (glossary control), and workflow management, without having to install and maintain glossaries and TM for each translator, but just sending to them self-contained XLIFF files that can be processed by an XLIFF localization editor. These editors - with differentiated interfaces for translating, reviewing and approving messages - can help manage and simplify the localization workflow, and reduce the amount of work necessary for the localization process.

Abstract: Many languages require complex font support for correct rendering and non-space based line breaking. The presentation will demonstrate Graphite complex fonts working in OpenOffice, including basic support for Graphite's font features and ideas for how features could be included into the User Interface and the OpenDocument format. The publication of Unicode 5.1 in April 2008 opened the way for Burmese and most of the other languages in Myanmar to be encoded in Unicode for the first time. The examples will show how many of these languages require reordering and context specific glyph substitutions. Font features allow language specific tailoring of glyphs for the same code sequences within a single font. Line breaking will also be discussed, since neither space nor syllable based solutions give a good results in Burmese.

Abstract: BrOffice.org Zine is an old dream of the Brazilian community that, following the same line of other free software user groups in Brazil, has the intention to provide high quality material, with tutorials, use tips and news about OpenOffice.org on Brazil and around the world, besides the news about ODF. This work presents the success case of our fanzine, explaining steps we took while developing the project, like the study made about the tools to be used, the visual communication, search and content classification part of the work and the team management. As a basis for the BrOffice.org Zine's work there is a clipping, research and content classification process to the BrOffice.org web portal, that is responsible to collect informations about BrOffice.org, OpenOffice.org and ODF on several languages like Brazilian Portuguese, Portuguese, English, Spanish and galician. Beyond the work of developing the BrOffice.org Zine in Brazilian Portuguese, the fanzine was used as an anchor to bring together different communities like Galician and Spanish communities, which resulted in the creation of BrOffice.org Zine - Galicia and from starting point, became the idea of expanding the fanzine to other languages like French and German. After the project was restructured, new perspectives appeared. One of them was the partnership with institutions that are already using BrOffice.org to publish advertisements and articles, always related to BrOffice.org and ODF, generating financial sustainability to the Brazilian community and the other one is the idea to create a high quality graphical material to help in the process of support and promote Br/OpenOffice.org and ODF around the world.

Abstract: I propose the formal creation of regional groups able to undertake and conduct marketing, user-group events, and developer and other contributor meetings. These groups would operate like Linux User Groups and tie into the existing MarCon network as well as the Native Language Confederation. The difference would be that these groups would not be based on language but region. Thus, as has already been discussed on the dev@native-lang list as well as the project_leads list, an Indian Regional group would coordinate development as well as events regardless of language. In the case of India, this is an especially important point, as there are 22 official languages. But India is not the only locale for such groups, and I propose setting up African, Scandinavian, Latin American, and Native North and Central American groups as a start. Similar groups in Europe, where such already exist in Spain, Germany, France, is welcomed. The focus, again, would encompass both marketing and developmental efforts. The obvious drawback of any such group would be coordinating their activity with the Web project. At present, we already see such difficulties arising from the Brazilian group BrOffice, and there are no doubt other instances. But by formalizing the idea, I anticipate we would be able to better address precisely this and other, related, problems. Right now, little is actually done beyond personal emails, and each of those takes time. How would these groups be established and who would lead them? These and other points will be discussed in the presentation.

Abstract: Learn how IBM IT designed and initiated its worldwide deployment of Lotus Symphony. IBM's document interchange policy is based on ODF, with Lotus Symphony becoming the preferred personal productivity suite for most employees. This talk will detail the methodology and deployment experiences of IBM's large scale deployment of Lotus Symphony. Open Document Format extends our Open Computing strategy which is centred on the value of open standards, open source software and open architectures.

Abstract: OpenOffice.org 3.0 will be a remarkable milestone after long-term development of OpenOffice.org. However, which direction will be good for OpenOffice.org to go after that? One option for such consideration would possibly be: Lightweight, Specialized, Diversified and Individualized. Lightweight accounts for the isolation among modules, more logical classifications of fundamental and extended functions,and separation between system's running core and interface; Specialization encourages the research of deeper exploitation of each module for its corresponding application field and intensifOpenOffice.org's value in the data processing capacity for structured semi-structured data. Diversification stands for the grand support for multiple hardware platforms, various document format standards and additionally, some specific data processing standards, XBML, for instance. Individualization favors users to be dominant to choose any function sets, usage pattern and even differentof OpenOffice.org at their will.

Abstract: Since OOoCon 2007 in Barcelona, the Engineering Steering Committee held several face to face meetings to discuss and address issues which hindered contributes within their work on OOo. Focus of the ESC were especially infrastructure issues, such as version control, process issues and build infrastructure. Beside the charter of the ESC, a presentation will give a overview about the different items on the ESC dashboard and will reflect the current status as well as the achievements of the ESC over the last year. Afterwards, there will be the chance for open discussion with the ESC members.