(incubating) | The Free and Open Productivity Suite

Announcing Apache OpenOffice 3.4

home » marketing » conference

Friday		March 21	2003
9:00	Complementing the OpenOffice.org Experience: the Chandler and Mozilla Projects, Mitchell Baker
9:45	Danese Cooper
10:30	Break

11:00	QA Processes: You Have an Issue with OpenOffice.org? Michael Bemmer	StarOffice migration within the scope of TCO and ROI Frank Sieber	OpenOffice.org on three continents - A Real Life Case Study Michael Bona

12:00	Integration with Gnome Michael Meeks	Smooth Desktop Migration to Linux and OpenOffice.org Bernd Kretschmer	User Experience (Panel) Lutz Höger, Christian Jansen, Matthias Müller-Prove, Nick Richards Audio (mp3, 20MB) Audio (mp3, 40MB)
12:45	Lunch

13:30	The Mac OS X/Darwin port of OpenOffice.org Dan Williams	Pladao Office the Thai localized version of OpenOffice.org Nusorn Photpipat	The Open ECDL: how to use opensource software - namely OpenOffice.org - for delivering ECDL courses Egidio Pentiraro

14:30	Common experiences using the OpenOffice.org API Berend Cornelius	The Japanese Native-Language Project Now and Beyond Maho Nakata, Takashi Nakamoto, Takaaki Higuchi	A Proper P2P Implementation for OpenOffice.org Sam Hiser
15:30	Townhall Meeting

Back to Top
Back to Thursday
Back to Overview

Please Note: Program content subject to change.

What is OOoCon?

Home

How to participate

Registration
Call for Papers

More information

Schedule & Slides
Location & Travel
Impressions

Audience

Attendee
Speaker
Sponsors & Exhibitors

Webmaster (conference pages)

Apache Feather

Copyright & License | Privacy | Contact Us

Apache and the Apache feather logos are trademarks of The Apache Software Foundation. OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation. Other names appearing on the site may be trademarks of their respective owners.

Apache OpenOffice is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.