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

From: Jarmo.Tikka at nokia.com Jarmo.Tikka at nokia.com
Date: Mon May 17 08:31:48 EEST 2010

I have nothing new to say as reply to Daves email so I just skip answering that and answer this one which is more generic.

>Date: Fri, 14 May 2010 10:53:20 +0300
>From: Quim Gil <quim.gil at nokia.com>
>Subject: Re: Cannot import docs directly into wiki.maemo.org
>To: List for community development <maemo-community at maemo.org>
>Message-ID: <4BED0170.5040204 at nokia.com>
>Content-Type: text/plain; charset=ISO-8859-1
>ext Dave Neary wrote:
>> Hi,
>> Jarmo.Tikka at nokia.com wrote:
>>> If this current guy is not able to do (or organize somebody else to do
>>> it) we need to find someone else to do it. Or do you have some other
>>> option in your mind. I would be interested to know if you have?
>To me this situation sounds like a proof that the only public
>collaborative workflow that actually works is:
>The wiki is always the master. All corrections need to happen there.
>When you are ready to ship a stable version you export a version of the
>content you need, and you publish it elsewhere in the format(s) you
>wish. Normal collaboration continues in the wiki without any disruptions.

The problem is that from wiki you do NOT get decent HTML documents out and without good quality HTML version you really cannot publish document anywhere else.

Somehow we need to be able to release Maemo docs in Info Center either in current Maemo Info Center or Forum Nokia Info Center and somehow we need to be able to integrate Maemo documents to IDEs and etc...

>This model also deals better with ownership since Nokia (or whoever) is
>always free to export when & where we wish, just following the licensing
>terms. No clash of priorities, QA criteria and "power" between Nokia and
>the maemo.org community sysadmins.

About licenses we have "wrong" license in Maemo.org wiki (creative commons) when most developer documentation is released in GNU FDL. This is why all our official documents explicitly state the license to be FDL just to be combatable with other than Maemo developer documentation. 

See https://bugs.maemo.org/show_bug.cgi?id=6294 and https://bugs.maemo.org/show_bug.cgi?id=4877

>Please find the most decent solution for the Maemo 5 documentation.
>After that comes meego.com and a process that follows exactly the
>workflow described above.

I know nothing about Meego...


More information about the maemo-community mailing list