Page History

Issue Tracking

http://openoffice.org/bugzilla/

Migrate legacy BZ database to Apache Infrastructure. 

The new issue tracker can be found here.
 
Existing accounts were preserved, but users will need to reset their passwords per these instructions.

Source code

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

Migrate DEV300 trunk to Apache Subversion.

Code can be downloaded per these instructions.

User support forums

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.

Extensions

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

All extension packages are hosted here.

Wiki

http://wiki.services.openoffice.org

The plan is to continue using MediaWiki and to preserve the existing wiki content, but on Apache-operated servers.   Migrate to Apache server, starting no later than Friday, 2011-10-28 , likely Wed/Thur

Templates

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

All extension packages are hosted here.

Archives

Download Archives

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

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/

Short term:
With the shutdown of the *.services.openoffice.org domain this host will go away. This should b 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/

When we do not save this service we will loose our download system how it is currently working. The 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 somewhere else that could be used for the service and copy over the VM. Then we just need to point the download website to this host and the download system is up and running again.

Short term:
Switch the download system to the backup server and backup the VM with the original instance

Long term:
Buildup a new and one instance.

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 ASF Infra are looking at what is needed for a general all projects pootle server. Chase them up next week.

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

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