[maemo-community] Cannot import docs directly into wiki.maemo.org

[From: Andrew Flegg]

On Tue, May 11, 2010 at 12:19,  <Jarmo.Tikka at nokia.com> wrote:
>From: Dave Neary [mailto:nearyd at gmail.com] On Behalf Of ext Dave Neary
>>
>> Then we are at an impasse, and I cannot comply with your request to
>> publish the wikified documentation you have provided.
>
> Sorry to hear that. If Maemo community still wants to have them in
> Maemo.org wiki we need to find somebody else to do this.

I can understand Dave & Niels' concern about using tools directly on
the main maemo.org infrastructure; and I can understand Jarmo's
frustration at trying to get the docs deployed.

Dave/Niels, I assume that it's a general concern about running new
tools directly against the production instance rather than any
specific flaws you've found in the tools Jarmo's provided?

Jarmo, could you describe what testing you've done with the tools to
ensure that it:

  a) doesn't destroy history (you mentioned this before);
  b) doesn't impact any documents outside of the tablespace in
     question;
  c) handles conflicts with image file names etc.

That'd go some way to helping demystify the tools, I think.

Dave/Niels, would it also be possible to clone the production database
to a test instance; run the tool and check the differences are
constrained to the documents in question? This'd give another level of
comfort.

Then, when happy with the reconciliation of the changes, the
production environment could be taken down/made read-only, the changes
enacted via the tool and everything re-enabled. This'd avoid any
conflicts the tool may encounter whilst the database is being updated
by users simultaneously.

Cheers,

Andrew

-- 
Andrew Flegg -- mailto:andrew at bleb.org  |  http://www.bleb.org/
Maemo Community Council chair