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.
- extensions and templates.
- Downloads (We have a download area for each project who we can put files on it)
- web content - some projects have webcontent and others are redirected to a wiki. Link to Project Mapping / Sub-Domains.
- Domain "openoffice.org"
- DNS entries
Satellite to Apache Migration topics include:
Name |
URL |
Description |
---|---|---|
user forums |
User support web forums using phpBB. There are nine separate language forums each in a sub-directory XX/forum/ where XX=en, es, fr, hu, it, ja, nl, vi, zh |
|
extensions |
Extension repository running drupal |
|
Wiki |
OOo wiki running in mediawiki |
|
Templates |
Templates repository running drupal |
|
Archives |
|
|
Services |
|
|
EIS |
EIS consists of a database keeping information about MasterWorkspaces and ChildWorkspaces |
|
MirrorBrain |
|
Tracks the downloads per language and site |
QATrack |
Release manager to schedule QA period in PHP |
|
Pootle |
Localization management of strings in Pootle Python |
|
QUASTe |
QA CWS management of workflow |
|
TCM |
http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo |
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