From mint-bounce@lists.fishpool.fi Mon Aug 23 10:24:21 2010 To: mint Subject: Re: [MiNT] Kernel documentation shortcomings MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Mon, 23 Aug 2010 16:20:35 +0200 From: m0n0 Reply-To: ole@monochrom.net In-Reply-To: <1282572307.28384.5.camel@jetpack.demon.co.uk> References: <0003e4f2.01c73262cce0@smtp.freeola.net> <1282571312.28384.4.camel@jetpack.demon.co.uk> <4fcd6b016704ab7114da682c4b576122-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUNBAjBTXF5bVkYJXVxoB1E6XF1XQ0AFXl1fQw==-webmailer2@server03.webmailer.hosteurope.de> <1282572307.28384.5.camel@jetpack.demon.co.uk> Message-ID: <5355d951ed48310543af68a2cf29ea88-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUNBAjBTXF5bVkYJXVxoB1E6XF1XQ0AFXFhaRQ==-webmailer2@server03.webmailer.hosteurope.de> X-Sender: ole@monochrom.net User-Agent: Host Europe Webmailer/2.0 X-HE-Access: Yes X-bounce-key: webpack.hosteurope.de;ole@monochrom.net;1282573236;a3115e9f; X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: ole@monochrom.net Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Am Montag, den 23.08.2010, 16:05 +0200 schrieb Alan Hourihane : > Sure. We want ALL the docs. I didn't meant to destroy any information ;) >> Of course we could write an converter, from wiki to man page... but >> maybe it would be better if a small script translates them to wiki >> content? > > Whatever works for you to get the stuff into the wiki. I'm easy. I'm not talking about an one time script... I'm talking about the place where the documentation should be maintained. The programmers must accept/decide how/where the kernel will be documentet... and I remember many people said that it is essential to keep documentation where the source is ;) That's also my point of view. If we can keep documents (in their current form) in the kernel - that's good. That means we don't need to import into the wiki, export them, convert them, place them into the release... We could simple take the up-to-date docs from freemint trunk ;) Importing these docs to the wiki is another part of the documentation process then... (not that much work). I vote for docs integrated into the sources. Greets, m0n0