From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, "Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [qemu-web PATCH v2] add support page
Date: Mon, 9 Sep 2019 17:08:04 +0200 [thread overview]
Message-ID: <bfee6036-5e81-46d7-add3-e06a81c7125e@redhat.com> (raw)
In-Reply-To: <20190909135842.25469-1-alex.bennee@linaro.org>
On 09/09/2019 15.58, Alex Bennée wrote:
> This is intended to be a useful page we can link to in the banner of
> the IRC channel explaining the various support options someone might
> have.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> ---
> v2
> - add cleanups suggested by Stefan
> ---
> support.md | 40 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
> create mode 100644 support.md
>
> diff --git a/support.md b/support.md
> new file mode 100644
> index 0000000..9174bbb
> --- /dev/null
> +++ b/support.md
> @@ -0,0 +1,40 @@
> +---
> +title: Support
> +permalink: /support/
> +---
> +
> +If you have a support question that is not answered by our
> +[documentation](/documentation) you have a number of options available
> +to you.
> +
> +If the question is specifically about the integration of QEMU with the
> +rest of your Linux distribution you may be better served by asking
> +through your distribution's support channels. This includes questions
> +about a specifically packaged version of QEMU. The QEMU developers are
> +generally concerned with the latest release and the current state of
> +the [master branch](https://git.qemu.org/?p=qemu.git) and do not
> +provide support for QEMU binaries shipped by Linux distributions.
> +
> +Questions about complex configurations of networking and storage are
> +usually met with a recommendation to use management tools like
> +[virt-manager](https://virt-manager.org/) from the [libvirt
> +project](https://libvirt.org/) to configure and run QEMU. Management
> +tools handle the low-level details of setting up devices that most
> +users should not need to learn.
Maybe add a glue sentence here à la:
"To get in touch with the people from the QEMU project, you have the
following options:"
> +* There is a
> +[qemu-discuss@nongnu.org](https://lists.nongnu.org/mailman/listinfo/qemu-discuss)
> +mailing list for user focused questions<br>
> +If your question is more technical or architecture specific you may
> +want to send your question to another of [QEMU's mailing
> +lists](https://wiki.qemu.org/MailingLists)
> +
> +* A lot of developers hang around on IRC (network: irc.oftc.net,
> +channel #qemu)<br> QEMU developers tend to hold normal office hours
> +and are distributed around the world. Please be patient as you may
> +have to wait some time for a response. If you can't leave IRC open and
> +wait you may be better served by a mailing list.
> +
> +* If you think you have found a bug you can report it on [our bug
> + tracker](https://bugs.launchpad.net/qemu/)<br>
> +Please see our guide on [how to report a bug](/contribute/report-a-bug/)
Maybe add a "." before the "<br>"s ?
Apart from that, content looks fine to me, but please add a link to
_includes/footer.html or _includes/nav.html.
Thanks,
Thomas
next prev parent reply other threads:[~2019-09-09 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 13:58 [Qemu-devel] [qemu-web PATCH v2] add support page Alex Bennée
2019-09-09 14:11 ` Daniel P. Berrangé
2019-09-09 14:32 ` Paolo Bonzini
2019-09-09 15:02 ` Alex Bennée
2019-09-09 15:08 ` Thomas Huth [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-09 13:56 Alex Bennée
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=bfee6036-5e81-46d7-add3-e06a81c7125e@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--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).