Page tree
Skip to end of metadata
Go to start of metadata

#acl AdminGroup:read,write,admin,revert,delete All:read

NOTE: This proposal was approved on 2011-06-13. We are no longer collecting "proposed committers" in this wiki page. Volunteers who wish to get involved in the Apache OpenOffice project should join the project's mailing list and introduce themselves and their interests.

You can subscribe to the mailing list by sending an email to: - An open productivity environment

Abstract is comprised of six personal productivity applications: a word processor (and its web-authoring component), spreadsheet, presentation graphics, drawing, equation editor, and database. is released on Windows, Solaris, Linux and Macintosh operation systems, with more communities joining, including a mature FreeBSD port. is localized, supporting over 110 languages worldwide.


Apache will continue the mission pursued by the project while under the sponsorship of Sun and Oracle, namely:

"To create, as a community, the leading international office suite that will run on all major platforms and provide access to all functionality and data through open-component based APIs and an XML-based file format."

In addition to to building the product, as an end-user facing product with many existing individual and corporate users, this project will also be active in supporting end-users via tutorials, user forums, document template repositories, etc. The project will also work to further enable to be used as a programmable module in document automation scenarios.

Background was launched as an open source project by Sun Microsystems in June 2000. was originally developed under the name of StarOffice by Star Division, a German company, which was acquired by Sun Microsystems in 1999. Sun released this as open source in 2000. is the leading alternative to MS-Office available. Its most recent major version, the 3.x series saw over 100 million downloads in its first year. The most recent estimates suggest a market share on the order of 8-15%.

The OpenOffice source is written in C++ and delivers language-neutral and scriptable functionality. This source technology introduces the next-stage architecture, allowing use of the suite elements as separate applications or as embedded components in other applications. Numerous other features are also present including XML-based file formats based on the vendor-neutral OpenDocument Format (ODF) standard from OASIS and other resources.

Rationale core development would continue at Apache following the contribution by Oracle, in accordance with Apache bylaws and its usual open development processes. Both Oracle and ASF agree that the development community, previously fragmented, would re-unite under ASF to ensure a stable and long term future for ASF would enable corporate, non-profit, and volunteer stakeholders to contribute code in a collaborative fashion.

Supporting tooling projects will accompany the contribution, providing APIs for extending and customizing

Both and the related tooling projects support the OASIS Open Document Format, and will attract an ecosystem of developers, ISVs and Systems Integrators. ODF ensures the users of and related solutions will own their document data, and be free to choose the application or solution that best meets their requirements.

The implementation will serve as a reference implementation of the Open Document Format standard.

Current Status


We understand the intention and value of meritocracy at Apache. We are particularly gratified to learn, during the discussion on this proposal, that there is a strong role for non-coders to participate in this meritocracy and as they demonstrate their sustained commitment and merit, to take on additional community responsibilities.

The initial developers are very familiar with open source development, both at Apache and elsewhere. Apache was chosen specifically because Oracle as contributor, and IBM as Sponsor, as well as the initial developers, want to encourage this style of development for the project. A diverse developer community is regarded as necessary for a healthy, stable, long term project.


The project, over its 10+ years of existence has spawned a diverse set of derived applications, each associated with its own set of communities. Some of the more prominent applications built on include:

  • LibreOffice
  • OOo4Kids / OOoLight
  • IBM Lotus Symphony
  • RedFlag China 2000 RedOffice
  • NeoOffice
  • EurOffice

A fuller picture of the range of customizations of is illustrated in this time line:

Each of these products has one more more associated communities, which might include:

  1. a user community
  2. a developer community
  3. a community of supporter, promoters, trainers, consultants, e.g., an extended ecosystem

In some cases the development effort for the derived project consists of repackaging the core code with additional plugins, fonts, clipart, in other cases an additional language translation is added bundled with additional language tools (spell checking dictionaries, grammar proofers), and in other cases the development work involves changes of the core components.

In some cases the communities coordinate closely with the parent projects, in other cases they have effectively "forked" into independent projects, and in some cases we really have no idea who they are or what they are doing. For example, screen shots of the secretive North Korean "Red Star" computer system indicate that it is likely using a customized version of OpenOffice.

The above community relations are as much social as business. The annual Conference has, for many years, been an important event on the calendar for community members, a "gathering of the clans" and generally brings in the "extended family" of projects, often including based projects that interoperate with via the OpenDocument Format (ODF) document format, e.g., Google Docs, Microsoft Office, AbiWord, Calligra Suite/KOffice. We want to continue this tradition with members of any eventual Apache OpenOffice TLP, in conjunction with the extended community of derived projects.

One of our goals with this incubation project will be to rationalize and formalize the coordination of these upstream and downstream contribution, basing it on the Apache 2.0 license, which should help us disseminate enhancements to the core more easily, since this license is easily consumed by all derivatives, even those with copyleft licenses. We need to identify which functions performed by the broader network of communities are a good fit for an eventual Apache TLP, and which things fit better outside of Apache.We also need to respect that the maintainers of these derivatives of have a lot of pride in their distributions and value their independent names and websites. So it is not reasonable to expect that they will wish to be folded into a single "vanilla" Apache However, we must do what is possible to encourage and further develop a thriving ecosystem around this project.

One possible outcome is that we encourage the core development of the editors to occur in Apache, while making it easy, via a modular extension mechanism, a modular install, etc. for others to customize and redistribute as permitted by the Apache 2.0 license.

Collaboration with LibreOffice

The LibreOffice project is an important partner in the community, with an established focus on the GNU/Linux community as well as on Windows and Mac consumer end-users. The Apache OpenOffice project will seek to build a constructive working and technical relationship so that the source code developed at Apache can be readily used downstream by LibreOffice, as well as exploring ways for their upstream contributions to be integrated.

There will be other ways we will be able to collaborate, including jointly sponsored events, interoperability 'plugfests', standards development, shared build management infrastructure, shared release mirrors, coordination of build schedules and version numbers, defect lists, and other downstream requirements. We will make this relationship a priority early in the life of the podlet.

Core Developers

The initial set of committers include developers and other contributors to, as well members of other derived products, open source and commercial, including Symphony, RedOffice, LibreOffice, EducOOo, etc. These committers have varying degrees of experience with Apache-style open source development, ranging from none to ASF Members.


Since its origins, has had a healthy group of volunteers committed to marketing with "MarCons" in many countries. There are existing initiatives that combine marketing with the possibility of raising independent funds, for example through EU grant applications related to the Life Long Learning programme, the certification project and developing the selling of marketing collateral around the brand. There is potential to independently raise money to substantially improve the quality and take up of the code that was not realised previously.


Create a strong bridge between and the Educational World :

  • Provide a place for users, in Education context: discuss about adapt to your pedagogy, your needs ..etc (all levels of Education are concerned )
  • Provide and promote tools adapted to pedagogical use, around
  • Write code together : train students to source code, create new features, experiment and reverse the best code to be integrated, following the Education Project model and the EducOOo effort.
  • has also maintained various mentoring projects and efforts and are in demand


The developers of will want to work with the Apache Software Foundation specifically because Apache has proven to provide a strong foundation and set of practices for developing standards-based infrastructure and related components. Additionally, the project may evolve to support cloud and mobile platforms from its starting point of desktop operating systems.

Known Risks

Orphaned products

We are encouraged by the strong initial response that news of this proposal has attracted, quickly growing from two to over 80 proposed committers. Among those names are individuals who have been involved with this project for 10 years or more. In addition to the individual volunteers, there is a significantcorporate committment. The risk, as in most projects, is to grow the project and maintain diversity. This is a priority that is keenly desired by the community.

Inexperience with Open Source

The initial developers include long-time open source developers, including Apache Members. Although the vast majority of proposed committers do not have Apache experience, they do have open source experience. For example, the names from * addresses were involved with the project previously.

The inexperience risk is also mitigated by the strong list of mentors who have signed up to support this project.

Homogeneous Developers for many years was managed by Sun, who provided the majority of its engineering resources as well as its direction. Moving this project to Apache enables a new start and provide a broad framework. We intend to engage in strong recruitment efforts in order to further strengthen and diversify this project.

In terms of geographic diversity, the project has strong European participation. This reflects the historical core of the development effort in this project. We wish to diversify this more, especially encouraging greater participation from CJK, India and South America.

Reliance on Salaried Developers

The initial group of proposed committers does not appear to be dominated by a single company. However, when we look at sponsored developers, with the ability to work on this project full time, IBM clearly has more committers. We beleive that this situation will change, as the project developers. The value of this code under a the permissive Apache 2.0 license will attract and encourage opportunities, not only for existing software vendors, but also for new ventures. This is a new opportunity, not previously permitted to the same degree by the project's previous license. This combined with a strong recruitment effort will help remove the project reliance on developers from any single company.

Relationships with Other Apache Products

Several potential areas for collaboration with other Apache projects have been suggested, including:

Apache POI potentially, if POI extends to support ODF, the default file format of (and initial discussions on this have been promising)

Apache Tika is a generic toolkit for extracting text and metadata from various file formats. Improving ODF support with tools from OOo is an obvious area of interest for Tika.

Apache PDFBox is a Java library for working with PDF documents. If not direct code sharing over the Java / C++ divide, then at least sharing of PDF know-how and perhaps things like test cases between these projects would be great.

Apache XML Graphics for SVG related libraries

Community Development

We are interested in further exploring these options.

A Excessive Fascination with the Apache Brand in itself is a very strong brand. Our primary interest is in the processes, systems, and framework Apache has put in place around open source software development more than any fascination with the brand.


Additional reading on can be found at the existing project's website.


This part is mandatory, and an important step in the organization.

Initial Source

The initial source will consist of a collection of files as specified in Oracle's submitted SGA.

During incubation, we will seek a grant to the following additional items:

External Dependencies

OpenOffice has external dependencies, including source and binary, required and optional, under a variety of licenses. A list of these dependencies can be found here.

We acknowledge that it is a podling graduation requirement to review these dependencies and to get the product into conformance with Apache requirements. The details will vary on a case-by-case basis, but options available to us include:

  • Substitute an external dependency with one having a compatible license
  • Contact the owner of a dependency and asking for a compatible license
  • Replace a source dependency with an unmodified binary dependency
  • Make a feature be optional, or user-installed
  • Rewrite a feature to avoid the external dependency
  • Remove a feature along with its external dependencies

Note: This task will be aided by the help of project members who work on IBM Lotus Symphony, who are familiar with many of these issues from a similar effort done on that product.

Cryptography supports digital signatures and encryption of documents. The project will complete any needed export control paperwork related to these features.

Required Resources

Note: It is recommended that after this proposal is accepted, that there be a consultation with ASF Legal Affairs on the trademark *before* any project infrastructure is created.

Mailing Lists

The following mailing lists:

  • - for developer discussions
  • - for Subversion commit messages
  • - for JIRA change notifications
  • - for continuous build/test notifications

Note: a users mailing is not being requested at this time. It is anticipated that users will interact with the community through existing systems, which are forums, based on phpBB.

Other resources

A subversion repository

A JIRA issue tracker: short code "OOo"

Pootle server (suggested for localization centralization)

phpBB end-user forums

Download site

TBD: some idea of how much build infrastructure measured in hardware.

Oracle will assist in the transition and migration from All of the content has already been archived and is ready for the ASF infrastructure group to act on.

Initial Committers

Note: Now that the proposal has been approved, we are no longer collecting initial committers in this wiki. Please see the instructions at the top of this page for how to join the project's mailing list and how to get involved.

In order to help encourage the creation of a broad and diverse project built upon merit, as required of an Apache project, we have not loaded the initial committer list with contributors from a single company. Our intention is for the initial committer list to be representative of the various users of OOo code. It is perfectly all right to have your name on this list if you contribute in another way than to commit program code (please maintain alphabetical ordering).





Kai Ahrens

ka at openoffice dot org



Eric Bachard

ericb at openoffice dot org

EducOOo,Education Project


Mathias Bauer

mba at openoffice dot org



Stephan Bergmann



Raphael Bircher

Individual QA, and Infrastructure


Ben Bois

benbois at ooo4kids dot org

EducOOo / OOo4Kids / OOoLight designer


Andy Brown

andy at the-marin-byrd dot net



Simon Brouwer

simonbr at openoffice dot org

Dutch Native Language Project


Alexandro Colorado

Education Project


Fred-Juan DIAZ

fred-juan.diaz at educoo dot org

EducOOo tester


Robert Burrell Donkin



Herbert Duerr



Olaf Felka

of at

individual, QA, Framework


David Fisher



Marcelo Horacio Fortino



Jaime R. Garza




Roman Gelbort

Spanish and Marketing project


Luis E. Vasquez



Christian Grobmeier

grobmeier AT apache dor org



Wolf Halton


Dennis E. Hamilton

Individual (orcmid)


Ivo Hinkelmann

ihi at openoffice dot org



Kazunari Hirano

individual self-intro


Eric Hoch

Co-Lead German Native Language Project, MacPorting Project


Martin Hollmichel

Release Manager, OOo external project lead



EducOOo Taiwan, Traditional Chinese


Jim Jagielski



Christoph Jopp



Peter Korn



Marcus Lange



Steve Lee

Individual (a11y)


Christian Lippka



Dieter Loeschky

Individual OOo Performance, OOo ESC


Ian Lynch

Marketing Project/TLM


Carl Marcum



Patrick Maupin



Ingrid von der Mehden

iha at openoffice dot org

OOo chart development


<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="59db169c-f942-4e19-9b40-b0fe8ed16dad"><ac:plain-text-body><![CDATA[

Stephane Quenson

stephane.quenson [at] gmail [dot] com




Eike Rathke

ooo AT erack DOT de



Manfred Reiter

fredao at openoffice dot org

Marketing Project/TLM


Zoltán Reizinger

Individual qa user forum


Phillip Rhodes

Fogbeam Labs


Andrew Rist



Lawrence Rosen



Juergen Schmidt

jsc at openoffice dot org

Individual API, Extensions


Jomar Silva

homembit at gmail

Individual (homembit)


Kai Sommerfeld

kso at openoffice dot org



Mechtilde Stehmann

qa officer


Michael Stehmann



Greg Stein

gstein at gmail



Michael Stahl

mst at openoffice dot org



Carl Symons



Stefan Taxhet

stx123 at gmail



Malte Timmermann

Individual, Security and Accessibility


Rob Weir



Yong Lin Ma

IBM, Symphony Architect


Lei Wang

IBM, Spreadsheet


Drew Jensen

Individual TDF OpenOffice


Graham Lauder MarCon (Marketing Contact) New Zealand


Florent André



Allen Pulsifer

pulsifer at



Kent Åberg




ja/qa project lead, FBSD porting


Miguel Á. Ríos

mariosv@miguelangel dot mobi



Dave McKay



Louis Suárez-Potts



Fernand Vanrie



Arthur Buijs

Dutch Native Language Project


Dave Barton

Tutorials For OpenOffice


Jian Fang Zhang

IBM, Symphony Chief Programmer, G11N, Security


Zhe Wang

IBM, Impress


Don Harbison



Jian Hong Cheng

IBM, Writer, Impress


Chao Sun



Heng Lee



Shu Wang Han



Hong Yun An



Xiao Hong Dong



Jin Hua Chen

IBM, Symphony Presentation


Yegor Kozlov



Juan C. Sanz

Spanish documentation


Peter Junge



Cyril Beaussier

oooforum at free dot fr

French forum admin,French Project webmaster


Damjan Jovanovic



Fernando Cassia



Jean Hollis Weber

Co-lead, OOo Documentation




Sam Ruby, Apache Foundation

Nominated Mentors

Because of the scope and complexity of this proposed project, we believe that the incubation process would benefit from multiple mentors, especially ones willing to be the "point person" for each of the following disciplines:

  1. IP review
  2. infrastructure
  3. release management
  4. community development

Mentors (these are all Members of the Foundation):

  • Jim Jagielski
  • Sam Ruby
  • Danese Cooper
  • Shane Curcuru
  • Nóirín Plunkett
  • Joe Schaefer
  • Christian Grobmeier
  • Ross Gardler

Sponsoring Entity

The Apache Incubator

  • No labels