On Sun, Nov 25, 2012 at 6:50 AM, jan iversen <j...@apache.org> wrote: > I am starting this thread so we have a place, to keep our decisions. I will > also a bit later make a new wiki page, "wiki planned maintenance" where I > (and hopefully also the other administrators) will keep track of the work > done, as well as the work ahead of us. > > For now, the sql scripts to: > a) remove accounts older than a year WITHOUT any contributions > b) remove all accounts from the time of the spam period > are being prepared, and will be executed when I get a little opie challenge > solved. > > I would like to seek lazy consensus on the following items: > > a) In order to keep track of all php/apache/mysql changes to wiki, I will > make a directory "wiki-maintenance" in SVN on level with "trunk". Currently > we do not really know what has been changed, and with the upgrade we have a > nice opportunity of documenting all changes, so it is easier for future > administrators. I know there is a very good page in Wiki (wiki maintenance) > but I would like to have the original files, with all changes in SVN. > > b) open for "create page" again, now that all spam users have been blocked. > Create user will have to wait at least a week and if we do not get flooded > with request, I would keep "invite only" for a longer period. > > c) When reactivation "create user" add a cooling period, like page > http://wiki.openoffice.org/wiki/Documentation/Dashboard/Wiki_Editing_Policysays > we already have. > > d) Clean database, for "deleted" pages, unused files. > > e) repair "broken redirect", "double redirect", "non categorized pages". > Remark no information will be deleted/changed. > > f) Convert all pages to UTF8 (mysql), most pages are defined as latin1, but > some have UTF8 content, this will not work after an update. > > g) Make a test.wiki.openoffice.org. This can be done with a simple alias in > apache conf, but should be done with a JIRA ticket. >
Not as urgent as the spam-related issues, but perhaps you could include this bit of deferred maintenance as well: https://issues.apache.org/ooo/show_bug.cgi?id=120301 Thanks! -Rob > Of course, before any changes to the production mysql a backup will be made. > > Jan
