The pages on this, the Apache OpenOffice "project", website are written in markdown syntax and stored in SVN at https://svn.apache.org/repos/asf/openoffice/site.
The migrated www.openoffice.org is stored in SVN at https://svn.apache.org/repos/asf/openoffice/ooo-site and is primarily "html".
Via integration with the Apache CMS, it is possible to edit, stage and publish website updates from the command line, or by using a web-based interface, the CMS bookmarklet.
Detailed information can be found in the How to edit the Apache OpenOffice website page.
Information on deeper website development is found on the Website Development page.
First, congratulations. Your contributions to the project have been noted and we hope that as a Committer you will be even more active.
But before you are officially given Committer permissions, there are a few administrative steps that you will need to complete.
If you were also voted as a PMC member, you should then subscribe to the PMC's private mailing list.
Finally, you should read the "Guide for new committers"
Apache OpenOffice welcomes your contributions!
If you want to contribute to either of the websites, you can do this by using subversion and submitting patches via e-mail, or for quick changes, you can use the CMS bookmarklet and use to edit a page, and submit a patch as described in the Apache CMS Reference Manual. Save your PATCH. File an issue using OpenOffice Bugzilla and select the "www" category to file it. You should then use your saved patch as an attachment to the issue. Please send a follow-up e-mail to dev and provide the issue number so we can follow-up.
Your contributions will be recognized by the committer submitting the PATCH in the log entry for the committed patch, and you will be added to the OpenOffice credits page to recognize your contribution.
Instructions can be found on the Subversion Basics page.
Please note that we are using a Subversion/Bugzilla integration, e.g. when you are committing something and mention the bugzilla issue in the commit summary, then this bugzilla issue gets automatically updated with some short info about the change. The recommended notation to mention e.g. issue 1234 is to use a #i1234# at the start of the commit message summary.
You might want to start by reviewing the legacy information on OpenOffice.org development. Or, take a look at information posted on the Apache OpenOffice wiki.
Of course, you will need the source code to do anything.
You don't have to be an actual committer to submit code. You can submit patches through the Apache OpenOffice Bugzilla issue reporting system. You simply need to file an issue and supply your patch as an attachment to the issue.
Developer builds are not official releases and may be unstable. But they can be useful to download for those who need early access to builds, but who do not want to compile their own build.
Information on buildbot builds for linux64, window7, and linux32 can be found here.
Development snapshots can be found in
Additionally --
Raphael Bircher posts occasional "developer snapshot" builds for other platforms on his personal website.
Ariel Constenla-Haile has posted a set of unofficial, unstable, untested developer builds here.
Also, please see the Planning Area of the Project Wiki for additional information on current and future releases.
Copyright © 2011-2012 The Apache Software Foundation Licensed under the Apache License, Version 2.0 | Contact Us | Terms of Use
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.