qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v3 4/4] Add a new doc "contacting-the-project.rst"


From: Thomas Huth
Subject: Re: [PATCH v3 4/4] Add a new doc "contacting-the-project.rst"
Date: Wed, 8 Jun 2022 07:50:31 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0

On 06/06/2022 18.43, Kashyap Chamarthy wrote:
This document slightly duplicates the "support"[1] page here, but
largely refers to the content in[1].

This is based on Peter Maydell's feedback[2] in v2: "there is some
merit in the documentation being standalone, even if it does mean a bit
of duplication with the website".

[1] https://www.qemu.org/support/
[2] https://lists.nongnu.org/archive/html/qemu-devel/2022-03/msg05178.html

Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
---
  docs/about/contacting-the-project.rst | 16 ++++++++++++++++
  docs/about/index.rst                  |  1 +
  2 files changed, 17 insertions(+)
  create mode 100644 docs/about/contacting-the-project.rst

diff --git a/docs/about/contacting-the-project.rst 
b/docs/about/contacting-the-project.rst
new file mode 100644
index 0000000000..83c1c50c48
--- /dev/null
+++ b/docs/about/contacting-the-project.rst
@@ -0,0 +1,16 @@
+.. _contacting-the-project:
+
+Contacting the project
+======================
+
+There are a multiple ways to reach out to upstream QEMU project,
+depending on what you're trying to do.
+
+If you have technical questions on QEMU usage, there are multiple
+channels for it -- mailing lists, real-time chat (IRC, etc).  Refer to
+`this web page <https://www.qemu.org/support>`__ for more precise
+details.
+
+If you think you have found a bug in QEMU, please follow the procedure
+outlined in `this document
+<https://www.qemu.org/contribute/report-a-bug>`__ on how to report it.

Could you maybe also put a direct link to https://www.qemu.org/contribute/security-process in here? ... some people still get it wrong how to report security issues, so putting this directly maybe helps a little bit...

 Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]