qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] wiki.qemu.org
Date: Fri, 29 Jan 2010 16:35:01 -0600	[thread overview]
Message-ID: <4B636295.8020203@codemonkey.ws> (raw)
In-Reply-To: <4B635755.8060803@mail.berlios.de>

On 01/29/2010 03:47 PM, Stefan Weil wrote:
> Hi,
>
> it's great to have an "official" QEMU wiki.
> What will happen with http://qemu.kidsquid.com/?
>    

I don't know.  It's certainly provided a great service over the years.  
I see no reason not to continue to link to it and if people want to move 
content in either direction, that would be okay to.

> Before removing the texi documents, there should
> be solutions for these topics:
>
> * How do we get a man page for a certain qemu release?
>
> * How do we get online documentation for a certain qemu release?
>
> * How do we get offline documentation (html without internet access)?
>
> * How do we get printed documentation which looks nice?
>    

All good points.  Personally, I think there are two types of 
documentation.  There is exhaustive option documentation which covers 
things like the monitor commands and the command line options.  This 
documentation should continue to live in the git tree IMHO and we should 
continue to generate man pages and online help from this source.

Then I think there is user documentation.  This is documentation that is 
more oriented to guide a user through what they should and shouldn't do 
and most importantly, how to solve problems on their own.  This think 
this later category is where a wiki shines.

I think qemu-img-cmds.hx, qemu-monitor.hx, and qemu-options.hx 
definitely fall into the first category.  I think qemu-doc.texi and 
qemu-tech.texi fall into the second category.  I think the remaining 
texi files live in both worlds.

> The wiki provides online documentation. It can do this for
> several qemu releases, too. But maintainance of serveral
> pages which are nearly identical will be difficult.
> Applying documentation patches to qemu releases is easier.
>
> For man pages, offline or printed documentation (needed for
> distributions), the texi documents work well. I see no
> easy way to replace them.
>
> Therefore I'd keep the texi documentation.
>
> Instead of adding an external link to the wiki,
> it should be possible to create mediawiki output
> from texi. This output could be copied to the
> qemu wiki using copy+paste, or maybe it is also
> possible to create mediawiki pages automatically
> on demand.
>    

That's an interesting thought although it probably requires translating 
texi into a more friendly intermediary first.

Regards,

Anthony Liguori

  reply	other threads:[~2010-01-29 22:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29 19:44 [Qemu-devel] [RFC] wiki.qemu.org Anthony Liguori
2010-01-29 20:23 ` Scott Tsai
2010-01-29 20:29 ` Andreas Färber
2010-01-29 20:53   ` Anthony Liguori
2010-01-29 21:47 ` Stefan Weil
2010-01-29 22:35   ` Anthony Liguori [this message]
2010-02-25 13:50 ` Paul Brook

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B636295.8020203@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).