[Qemu-devel] [Webpage PATCH] add support page

[Qemu-devel] [Webpage PATCH] add support page

[Alex Bennée]

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>
---
 support.md | 37 +++++++++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 support.md

diff --git a/support.md b/support.md
new file mode 100644
index 0000000..b9f4aa6
--- /dev/null
+++ b/support.md
@@ -0,0 +1,37 @@
+---
+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 distribution you may be better served by asking through
+your distribution's support channels. This includes questions about a
+specifically packaged versions of QEMU. The developers are generally
+concerned with the latest release and the current state of the [master
+branch](https://git.qemu.org/?p=qemu.git).
+
+Questions about complex configurations of networking and storage are
+usually met with a recommendation to use management tool like
+[virt-manager](https://virt-manager.org/) from the [libvirt
+project](https://libvirt.org/) to configure and run QEMU.
+
+* 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/)
-- 
2.20.1

Re: [Qemu-devel] [Webpage PATCH] add support page

[Marc-André Lureau]

On Mon, Aug 19, 2019 at 2:58 PM Alex Bennée <alex.bennee@linaro.org> 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>

May be you should remove "bug reporting" and "contact" sections from
README, and link to this file instead?

anyway lgtm,
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>

> ---
>  support.md | 37 +++++++++++++++++++++++++++++++++++++
>  1 file changed, 37 insertions(+)
>  create mode 100644 support.md
>
> diff --git a/support.md b/support.md
> new file mode 100644
> index 0000000..b9f4aa6
> --- /dev/null
> +++ b/support.md
> @@ -0,0 +1,37 @@
> +---
> +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 distribution you may be better served by asking through
> +your distribution's support channels. This includes questions about a
> +specifically packaged versions of QEMU. The developers are generally
> +concerned with the latest release and the current state of the [master
> +branch](https://git.qemu.org/?p=qemu.git).
> +
> +Questions about complex configurations of networking and storage are
> +usually met with a recommendation to use management tool like
> +[virt-manager](https://virt-manager.org/) from the [libvirt
> +project](https://libvirt.org/) to configure and run QEMU.
> +
> +* 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/)
> --
> 2.20.1
>
>


-- 
Marc-André Lureau

Re: [Qemu-devel] [Webpage PATCH] add support page

[Stefan Hajnoczi]

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]

On Mon, Aug 19, 2019 at 11:57:53AM +0100, Alex Bennée wrote:

Good idea!

> +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 distribution you may be better served by asking through

s/distribution/Linux distribution/

> +your distribution's support channels. This includes questions about a
> +specifically packaged versions of QEMU. The developers are generally

s/versions/version/

s/developers/QEMU developers/

> +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 tool like

s/tool/tools/

> +[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."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]