qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Gerlich <olig9@gmx.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Developer-to-user communication
Date: Mon, 21 Mar 2005 14:41:32 +0100	[thread overview]
Message-ID: <423ECF0C.6080603@gmx.de> (raw)

Hi,
as Qemu gets more widespread (ok, less narrowspread :) there should be
better communication between developers and end users. Qemu is already
usable, but the lack of support probably frightens off many potential
users. I don't know how many developers also read the dad-answers.com
forum but I think there are many help requests in the forum which are
also interesting for developers.

So, here are some ideas on how to improve this:
-There should be a bigger FAQ which answers also questions from the
forum; and it should also list the frequently mentioned known bugs.
-Some kind of bug tracking site / bug list would also be useful so users
can better see current development status.
-A list of unofficial patches etc. would be nice. There are several
sites with patches which solve some of the problems in the forum, but
they are difficult to find, especially for simple users ;)
-How about a Qemu Wiki? There is a qemu-related Wiki page at
http://am.xs4all.nl/phpwiki/index.php/Qemu , but it's not in good shape
and the whole Wiki is not really Qemu specific. A Wiki could help to
offload some "public relations" work from the main developers.

Some of these ideas are already realised in the mentioned Wiki, but that
site is quite unknown. I think we should concentrate these things on the
Qemu home page or a closely related site.
Does anyone have web space, time etc. to realise these ideas?

Opinions? Ideas? Improvements? Please tell me what you think about this!

Oliver Gerlich

             reply	other threads:[~2005-03-21 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21 13:41 Oliver Gerlich [this message]
2005-03-21 19:01 ` [Qemu-devel] Developer-to-user communication Jérôme Bouat

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=423ECF0C.6080603@gmx.de \
    --to=olig9@gmx.de \
    --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).