OpenOffice.org Migration Status

Issue Tracking

http://openoffice.org/bugzilla/

https://issues.apache.org/ooo/

Migrate legacy Bugzilla database to Apache Infrastructure. Preserve existing accounts but users need to reset their passwords per these instructions.

Source code

http://hg.services.openoffice.org/

https://svn.apache.org/repos/asf/incubator/ooo/trunk

Migrate the OOO340 feature branch to Apache Subversion as new head trunk. Code can be downloaded per these instructions.

User support forums

http://user.services.openoffice.org/

http://user.services.openoffice.org/

Forums will be migrated this week, they could be made read only as early as Tues/Weds to allow for a final database dump.

Mailing lists

300+ openoffice.org project and user mailing lists

Legacy lists are using SYMPA list manager software. Apache uses ezmlm.  We will create a smaller number of ezmlm lists at Apache and assist users of the legacy lists subscribe to the new lists. Lists will be migrated in stages, starting the week of October 30th. After migration the legacy lists will be shut down. Complete archives will be preserved at MarkMail .

Details of the plan are here .

Wiki

http://wiki.services.openoffice.org/

http://wiki.services.openoffice.org/

The plan is to continue using MediaWiki and to preserve the existing wiki content, but on Apache-operated servers. See status updates here.

Extensions

http://extensions.services.openoffice.org/

All extension packages are hosted here. This is a drupal based system.

2012-02-26: With help from SourceForge, extensions.services.openoffice.org has been migrated to http://aoo-extensions.sourceforge.net and DNS entry updated

Templates

http://templates.services.openoffice.org/

All template packages are hosted here. This is a drupal based system.

Please report outages to INFRA.

Download Archives

http://archive.services.openoffice.org/pub/openoffice-archive/

tbd

Short term:
Secure all releases (binary and source tarballs) up to OOo 3.3 / 3.2.1 (latest stable), OOo 3.4 Beta (latest Beta) and DEV300m106 (latest Dev Build).
Long term:
Buildup a little mirror network with 2-4 mirrors that provide legacy releases as it done in the old OOo project. Then not the complete mirror network has to offer all builds (> 200 GB diskspace).

FTP Master Server

http://rsyncmaster.services.openoffice.org/

tbd

Short term:
With the shutdown of the *.services.openoffice.org domain this host will go away. This should be OK because as long as we don't provide any new releases there is nothing that the OOo mirror network could and should rsync to.

Long term:
Buildup a new host so that the OOo mirror network can rsync to to get all new releases that should be provided to the world.

MirrorBrain

http://download.services.openoffice.org/files/

tbd

When we do not save this service we will loose our legacy download system how it is currently working. The legacy OOo download website is not working with the Apache method. It's not predictable how much effort and time is necessary to adjust it.

Recommendation:
Secure the service as it is now, find a suitable server inside the ASF or - if not possible - somewhere else (e.g., Team OpenOffice.org e.V. ) that can maintain/host the service. Then copy over the VM, point the download website to this host and the download system is up and running again.

Short term:
Backup the VM with the original service instance and switch the download system to the backup server in case of any outage.

Long term:
Secure the legacy OOo download system as long as possible. However, new Apache OO releases will use the Apache Mirror system.

Services

http://ooo.services.openoffice.org/pub/OpenOffice.org/

EIS

http://tools.services.openoffice.org/EIS2/

This service was used to coordinate the development work of CWSs (owner, purpose, status, etc.).

QATrack

http://qatrack.services.openoffice.org/

This service was used to keep the overview about which NL team is testing / has already approved which release builds.

Pootle

http://pootle.services.openoffice.org

The new pootle server is now open for all projects to enjoy - https://translate.apache.org - Contact infra for any questions.

QUASTe

http://quaste.services.openoffice.org/

This service was used to show the current testing results of CWSs and master code.

TCM

http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo

This service was used to provide a platform to the NL teams to coordinate the feature/language specific features.

OOo website

http://www.openoffice.org and native-lang versions

http://ooo-site.apache.org/

Copy over all website files and buildup a new structure to present the same content and features when ASF is hosting the website. A staging site is being built and it will be editable via the Apache CMS.

Registration

In OOo see the menu "Help - Registration".

Product Update Service (PUS)

http://update36.services.openoffice.org/ProductUpdateService/check.Update?pkgfmt=rpm

In OOo see the menu "Help - Check for Updates".

More details in the Wiki .

Online Update for Extensions

http://updateexte.services.openoffice.org/ExtensionUpdateService/check.Update

In OOo see the menu "Help - Check for Updates".

Improvement Program

In OOo see the menu "Tools - Options - OOo - Improvement Program".

Crash Reporter

http://report.services.openoffice.org

Before OOo is crashing it tries to collect important data (e.g., Platform/OS version, OOo build ID, loaded libraries, but of course no personal data) and send it via Internet to a server. This helps the developers to analyze the crash, identify the root cause and if possible to fix it.