From: "Jim C. Brown" <jma5@umd.edu>
To: "Qemu-Devel (E-mail)" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Documentation for Windows host - is a QEMU wiki the way forward ?
Date: Wed, 5 Jul 2006 20:07:38 -0400 [thread overview]
Message-ID: <20060706000738.GA31240@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <A69CFE5B2F49D91186C1000BCD9DBD03E2AAA0@otausminexs.au.otis.com>
On Wed, Jul 05, 2006 at 07:55:14PM -0400, Armistead, Jason wrote:
> I know there is the "Unofficial #qemu Wiki" on
> http://kidsquid.com/cgi-bin/moin.cgi/
>
> How about an official (rather than unofficial) QEMU Wiki where we can ALL
> contribute to the documentation process ? I think there are lots of things
> the collective geniuses on this list could contribute - and a wiki is often
> a lot nicer way to summarize knowledge than trawling through and endless
> number of mail archive postings. If people want to contribute to the
> documentation, they can. If they want to just lurk and watch selected
> pages, they can. If they want to add screen-shots, they can. If they want
> to ask questions about particular documentation, there is always the
> Discussion pages associated with each article. I've always been a big fan
> of MediaWik as used on Wikipedia for all these reasons.
>
> How about it ?
>
You can already do this with the unofficial wiki. I don't see any difference
between an "official" and an "unofficial" wiki other than its title.
Lots of people contribute to the wiki. If you have something to say, just stick
it in there. A wiki wouldn't be viable unless it was completely open.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2006-07-06 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 23:55 [Qemu-devel] Documentation for Windows host - is a QEMU wiki the way forward ? Armistead, Jason
2006-07-06 0:07 ` Jim C. Brown [this message]
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=20060706000738.GA31240@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=qemu-devel@nongnu.org \
/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).