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

From: Jarmo.Tikka at nokia.com Jarmo.Tikka at nokia.com
Date: Thu May 13 16:43:32 EEST 2010
HI again,

>Date: Tue, 11 May 2010 13:29:51 +0100
>From: Andrew Flegg <andrew at bleb.org>
>Subject: Re: Cannot import docs directly into wiki.maemo.org
>To: List for community development <maemo-community at maemo.org>
>       <AANLkTimUqZ0_yCrOxFYzTm4LoHW3ac_fzjVB8TJFUz-l at mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1
>On Tue, May 11, 2010 at 12:19,  <Jarmo.Tikka at nokia.com<mailto: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?

I would also be interested if you have found any problems from our MediaWiki import?


I now have PreFinal2 version published for the toolchain and I soon need to know do I need to fix something for Final release (like removing dependency to the MediaWiki Debian packages from wiki import, BTW which I would not like to do as I explained earlier).

>>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.

We have done normal testing we do for all our releases to verify they work as we document them to work.

a)      history wil noe be destroyed with new imports but wiki pages just get updated
b)      you define where in MediaWiki page hierarchy you do the import and it is done there
c)      if you change image name (file name for image that need to be updated) new file gets updated, if file with same name already exists it gets updated (no history is reserved as MedisWikid is not able to do that)

>>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

Maemo MediaWiki import supports any standard MediaWiki installation (Ubuntu/Debian). If you install your MediaWiki from tar ball from upstream project (usually not allowed for production systems as you will have maintenance problems on your server if packaging systems is not used).

>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.

Let me know if you find any problems in MediaWiki import.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.maemo.org/pipermail/maemo-community/attachments/20100513/43f1432e/attachment.htm>
More information about the maemo-community mailing list