You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

On this page let's outline the layout the current OpenOffice.org infrastructure and determine the requirements for migration.

It turns out that much of the OpenOffice.org infrastructure was converted to the project Kenai site on February 21, 2011.

http://kenai.com/projects/ooo-migration/pages/Home

Kenai to Apache Migration Topics are:

  • bugtracking
  • mailing lists and forwarders.
  • Downloads (We have a download area for each project who we can put files on it)
  • web content
  • Domain "openoffice.org"
  • DNS entries

Satellite to Apache Migration topics include:

Name

URL

Description

user forums

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

User support web forums using phpBB

extensions

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

Extension repository running drupal

Wiki

http://wiki.services.openoffice.org

OOo wiki running in mediawiki

Templates

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

Templates repository running drupal

Archives

 

 

Services

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

 

EIS

 

(I don't know, if this is a Open Source Tool)

MirrorBrain

 

Tracks the downloads per language and site

QATrack

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

Release manager to schedule QA period in PHP

Pootle

http://pootle.services.openoffice.org

Localization management of strings in Pootle Python

QUASTe

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

QA CWS management of workflow

TCM

 

Test case management tool

Other Apache Migration Topics include:

  • openoffice.org email addresses and mailboxes

I'm sure we have more, but atm that's all that I know

Note: There is also a page on the Dev wiki that folks may want to either use as well or (better yet) fold into this page: https://cwiki.apache.org/confluence/display/OOODEV/Infrastructure

  • No labels