General¶

• About
• Downloads
• License
• Trademarks
• Press
• OpenOffice.org website

Community¶

• Get Involved
• Orientation
• Mailing Lists
• Social Networking
• Events
• Support
• Native Language
• Planning Wiki
• People
• Community FAQs

Development¶

• Source Code
• Bug Tracking
• Quality Assurance
• Translation
• Website
• Security Reports
• Contributing Code
• Developer FAQs

Project Management PMC¶

• Project Blog
• PMC FAQs

The Apache Software Foundation¶

• Website
• License
• Security
• Events
• Donations
• Sponsorship
• Thanks

Source Control

We use Apache Subversion for version control. You can browse our repository in your web browser.

See our Subversion Basics for more information on using subversion (svn) for the Apache OpenOffice project.

For further information see the Apache Source Code Repository page.

Getting the source code¶

Using SVN¶

This will get you everything, including the language files:

svn co https://svn.apache.org/repos/asf/openoffice/trunk aoo

Including SVN overhead, this requires approximately 4 GB of storage.

Using GIT¶

You can use our git repository for downloading source but not committing (read only): https://github.com/apache/openoffice

Source archive of the latest release¶

An archive of the source for the latest release can be obtainted from the Apache Software Foundation repository: http://www.apache.org/dyn/aoo-closer.cgi/openoffice/

Browsing/Searching Source Code¶

We have an instance of Atlassian FishEye for source browsing, searching, reporting and visualization of main trunk (main development area).

Also, AdfinisSygroup hosts an OpenGrok instance of a few of our main repository areas.

Building and Running¶

See the Apache OpenOffice Building Guide page for an overview on building.

See Development Snapshots builds for additional information on building.

Testing Developer Installation Sets¶

See Development Snapshot Builds: Full installation sets or Development Builds for complete installation sets for available platforms.

Install the "Developer Installation Set" to a new directory if you don't want to overwrite your existing Apache OpenOffice installation.

• Linux: Create a new directory for the AOO developer install. Install the RPM pack with --prefix="some new AOO directory" option.
• Windows: Use the custom install option, and choose a new directory location for the AOO developer install.
• Mac: create a new folder for AOO developer install. Download the ".dmg" file there, and install to the new directory.

Code and Contribution Statistics¶

Our SVN tree is read by the Open Hub tracker to generate some various statistics. Note that the migration from the legacy Mercurial repository to SVN at Apache has caused pre-existing files to be double-counted. But the contribution history should be intact.

Special Development Branches¶

For larger, extensive code modifications, specialized branches are created. You can find out more information on them from the Wiki Source Code page.

Legacy Source Code Repository¶

A clone of the project's legacy (pre-Apache, Hg OOO340) version control system is maintained as service to the ecosystem by a volunteer. Please note that this code is LGPL-licenced and is not maintained by the Apache OpenOffice project.

The legacy repository can be found here.