Versions Compared

Old Version 16

changes.mady.by.user T. J. Frazier

Saved on

compared with

New Version 17

changes.mady.by.user T. J. Frazier

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Wiki saved, hurrah! Salvage plan obsolete. Erroneous dates fixed.

...

1.

Build of Test VM

completed 02-Aug-2011

terrye

2

Initial Build of Target VM

completed 05-Aug-2011

gmcdonald, rbircher

4

Obtain project endorsement for test migration

completed 09-Aug-2011

as per DL

5

Transfer the Current Prod MediaWiki build and available for testing at http://ooo-wiki.apache.org/wiki/Main_Page

completed 10-Aug-2011

terrye

6

terrye leaves project.

04-Sept-2011

 

7

Due to possible lack of project support for MediaWiki in the future, discussion has now turned to the possible use of Confluence (the already supported Apache wiki) for use as the Apache OpenOffice (community) wiki

06-Sept-2011

 

8

Wiki demise scheduled for Friday, 2928-SeptOct-2011. See Salvage Plan below.

21-Sep-Oct-2011

tj

9

HURRAH! The wiki will be re-hosted intact. Salvage Plan now obsolete. Current status will be maintained at https://cwiki.apache.org/confluence/display/OOOUSERS/OpenOffice.org+Migration+Status

24-Oct-2011

tj

Salvage Plan

(This plan is now obsolete.)

Background

Problem #1

The OO.o wiki is scheduled to be shut down as of Friday, 2928-SeptOct-2011.

Problem #2

Operating the live wiki here on Apache is not considered feasible. Neither Infra nor the project has been able to identify sufficient volunteers with sufficient skills to maintain a MediaWiki installation in the long term, to a level that makes everyone comfortable.
The MediaWiki wiki will be operated and maintained normally.

No problems have been reported with the static wiki copy on Apache. This suggests that an almost-static copy could be maintained for the middle-term with no insurmountable problems.

...

Capture a final dump from the live wiki, and install on Apache. This will be almost read-only, requiring only a few notices from time to time. (TJ expects to be the only writer.) Required maintenance (by Infra) should be absolutely minimal. Migration of various parts of the data can then proceed, in parallel and as time allows.
The interactive benefits of the wiki will be lost, but it will still be a source of information.

Action items:
(Later note – Except for the tone of finality, these items will still need to be accomplished.)

Andrew Rist, for Oracle

  • Promote TJFrazier to bureaucrat on the live wiki. Done.
  • Provide a date-certain for the shut-down.
  • Provide a final data dump, after shut-down.

...

  • Prepare to load that final dump. The existing test copy here can be discarded. ASSUMPTION: Terry's scripts/instructions are available and can be followed.
  • Re-activate TJFrazier account after password-scrambling. The necessary command-line MySQL command is available. Unneeded. Accounts will remain live.
  • Prepare to work DNS-magic for outside links to the wiki.
  • Provide what dates you can (dependent on shut-down move date) to TJ, for communication to users.

...

  • Post notices on live wiki, as soon as dates (and URLs?) are available, to warn users. (In progress.)
  • Fix DPL/template problems on new copy. (Minor.)
  • Ongoing: post notices like, "This manual has been moved. Please see LINK for the latest information." (Later – now depends on hosting decisions for documents.)