From nobody Sun Feb 8 17:41:21 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) client-ip=170.10.133.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1646927582; cv=none; d=zohomail.com; s=zohoarc; b=OXuIETFf530biaji8flc/nhuyRCsJ9LZS+qXROwe3J7hen/3/ajm4Z1k5RaqF9qS6RXwuO+bAc30bDZU8VwoaDsSDRF64gnaR/vZM8XfQ6mThX3JUCacQfnkA0l06ujMuL8Cg/aE0COA0qmIJT46Byc4lYgjzEvxD+jfkldB5IQ= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1646927582; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=j3l/2RJUUBbGgaD66TQF+ObO6DnjJIy1JpVG0c9y5BE=; b=nhZmWtKhMCIo6tsELwwqMQVddavnie+uQXJYLKHGJsqVjTMbC7KlTDcIgLuHAY6/xouNuxlkt+2R0I2R+CryoWkPiOfDhNtB4hmJ9FcugOh1GqI+DnA0sVxJUR7HGPB89gbnG+gjriM9wlUPSdZneprEm9tnQfzmqkdtWfJanDU= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.zohomail.com with SMTPS id 1646927582951473.18881013869395; Thu, 10 Mar 2022 07:53:02 -0800 (PST) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-633-jezM43u8Pz-KDj-NG4u6Nw-1; Thu, 10 Mar 2022 10:51:54 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D2AD5805F5C; Thu, 10 Mar 2022 15:51:44 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id A580B1457F07; Thu, 10 Mar 2022 15:51:44 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 4DC3A1966347; Thu, 10 Mar 2022 15:51:44 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id B41211953576 for ; Thu, 10 Mar 2022 15:51:43 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 869527C029; Thu, 10 Mar 2022 15:51:43 +0000 (UTC) Received: from speedmetal.redhat.com (unknown [10.40.208.30]) by smtp.corp.redhat.com (Postfix) with ESMTP id CA2217C02A for ; Thu, 10 Mar 2022 15:51:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1646927582; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=j3l/2RJUUBbGgaD66TQF+ObO6DnjJIy1JpVG0c9y5BE=; b=WZ1Zx+j7NodFfG4LK9bJn0tGOMopqFF+HumUyk4OtWdhQ5BzjRksWf7KwmTf/EPXAkGfoh XeNAyMvJCdrydqP7DxdAG+w0JOy0O677Vxg6mLK/nE0CtrRL4JkUigFCplQqFIIzw8aKKt BUa/eef3K/W5n8txuxF3SI+LTFm5/4A= X-MC-Unique: jezM43u8Pz-KDj-NG4u6Nw-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 2/8] docs: Convert 'contact' page to rST Date: Thu, 10 Mar 2022 16:51:24 +0100 Message-Id: In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 2.85 on 10.11.54.7 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1646927584901100001 Content-Type: text/plain; charset="utf-8" Preserve the 'irc' and 'email' anchors. Signed-off-by: Peter Krempa --- docs/contact.html.in | 116 ------------------------------------------- docs/contact.rst | 94 +++++++++++++++++++++++++++++++++++ docs/meson.build | 2 +- 3 files changed, 95 insertions(+), 117 deletions(-) delete mode 100644 docs/contact.html.in create mode 100644 docs/contact.rst diff --git a/docs/contact.html.in b/docs/contact.html.in deleted file mode 100644 index ad95800b1b..0000000000 --- a/docs/contact.html.in +++ /dev/null @@ -1,116 +0,0 @@ - - - - -

Contacting the project contributors

- -
    - -

    Security Issues

    - -

    - If you think that an issue with libvirt may have security - implications, please do not publicly - report it in the bug tracker, mailing lists, or irc. Libvirt - has a dedicated process for handlin= g (potential) security issues - that should be used instead. So if your issue has security - implications, ignore the rest of this page and follow the - security process instead. -

    - -

    Mailing lists

    - -

    - There are three mailing-lists: -

    - -
    -
    = libvir-list@redhat.com (for development)
    -
    - Archives at https://www.redhat.com/archives/libvir-list -
    -
    - This is a high volume mailing list. It is a place for discussions - about the development of libvirt. -
    -
    - Topics for discussion include: -
      -
    • New features for libvirt
      • -
    • Bug fixing of libvirt
      • -
    • New hypervisor drivers
      • -
    • Development of language bindings for libvirt API
      • -
    • Testing and documentation of libvirt
      • -
    -
    - -
    libvirt-users@redhat.com (for users)
    -
    - Archives at https://www.redhat.com/archives/libvirt-users -
    -
    - This is a moderate volume mailing list. It is a place for discuss= ions - involving libvirt users. -
    -
    - Topics for discussion include: -
      -
    • Usage of libvirt / virsh
      • -
    • Administration of libvirt
      • -
    • Deployment of libvirt with hypervisors
      • -
    • Development of applications on top of / using the libvirt AP= I(s)
      • -
    • Any other topics along these lines
      • -
    -
    - -
    libvirt-announce@redhat.com (for release notices)
    -
    - Archives at https://www.redhat.com/archives/libvirt-announce -
    -
    - This is a low volume mailing list, with restricted posting, for - announcements of new libvirt releases. -
    -
    - Subscribe to just this if you want to be notified of new releases, - without subscribing to either of the other mailing lists. -
    - -
    - -

    - It is recommended but not required that you subscribe before posting - to the user and development lists. Posts from non-subscribers will = be - subject to manual moderation delays. You can subscribe at the linked - web pages above. -

    -

    - Patches with explanations and provided as attachments are really - appreciated, and should be directed to the development mailing list - for review and discussion. - Wherever possible, please generate the patches by using - git format-patch in a git repository clone. Further - useful information regarding developing libvirt and/or contributing = is - available on our Contributor Guidelines - page. -

    - -

    IRC discussion

    - -

    - Some of the libvirt developers may be found on IRC on the OFTC IRC - network. Use the settings: -

    -
      -
    • server: irc.oftc.net
      • -
    • port: 6667 (the usual IRC port)
      • -
    • channel: #virt
      • -
    -

    - NB There is no guarantee that someone will be watching or able to re= ply - promptly, so use the mailing-list if you don't get an answer on the = IRC - channel. -

    - - - diff --git a/docs/contact.rst b/docs/contact.rst new file mode 100644 index 0000000000..75b1239301 --- /dev/null +++ b/docs/contact.rst @@ -0,0 +1,94 @@ +.. role:: anchor(raw) + :format: html + +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +Contacting the project contributors +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D + +.. contents:: + +Security Issues +--------------- + +If you think that an issue with libvirt may have security implications, **= please +do not** publicly report it in the bug tracker, mailing lists, or irc. Lib= virt +has `a dedicated process for handling (potential) security +issues `__ that should be used instead. So if your i= ssue +has security implications, ignore the rest of this page and follow the `se= curity +process `__ instead. + +:anchor:`` + +Mailing lists +------------- + +There are three mailing-lists: + +**libvir-list@redhat.com** (for development) + Archives + https://www.redhat.com/archives/libvir-list + List info + https://www.redhat.com/mailman/listinfo/libvir-list + + This is a high volume mailing list. It is a place for discussions about= the + **development** of libvirt. + Topics for discussion include: + + - New features for libvirt + - Bug fixing of libvirt + - New hypervisor drivers + - Development of language bindings for libvirt API + - Testing and documentation of libvirt + +**libvirt-users@redhat.com** (for users) + Archives + https://www.redhat.com/archives/libvirt-users + List info + https://www.redhat.com/mailman/listinfo/libvirt-users + + This is a moderate volume mailing list. It is a place for discussions + involving libvirt **users**. + Topics for discussion include: + + - Usage of libvirt / virsh + - Administration of libvirt + - Deployment of libvirt with hypervisors + - Development of applications on top of / using the libvirt API(s) + - Any other topics along these lines + +**libvirt-announce@redhat.com** (for release notices) + Archives + https://www.redhat.com/archives/libvirt-announce + List info + https://www.redhat.com/mailman/listinfo/libvirt-announce + + This is a low volume mailing list, with restricted posting, for announc= ements + of new libvirt releases. + Subscribe to just this if you want to be notified of new releases, with= out + subscribing to either of the other mailing lists. + +It is recommended but not required that you subscribe before posting to th= e user +and development lists. Posts from non-subscribers will be subject to manual +moderation delays. You can subscribe at the linked web pages above. + +Patches with explanations and provided as attachments are really appreciat= ed, +and should be directed to the development mailing list for review and +discussion. Wherever possible, please generate the patches by using +``git format-patch`` in a git repository clone. Further useful information +regarding developing libvirt and/or contributing is available on our +`Contributor Guidelines `__ page. + +:anchor:`` + +IRC discussion +-------------- + +Some of the libvirt developers may be found on IRC on the `OFTC +IRC `__ network. Use the settings: + +- server: irc.oftc.net +- port: 6667 (the usual IRC port) +- channel: #virt + +NB There is no guarantee that someone will be watching or able to reply +promptly, so use the mailing-list if you don't get an answer on the IRC ch= annel. diff --git a/docs/meson.build b/docs/meson.build index c1d4072cf7..aaafa7d8e1 100644 --- a/docs/meson.build +++ b/docs/meson.build @@ -20,7 +20,6 @@ docs_assets =3D [ docs_html_in_files =3D [ '404', 'cgroups', - 'contact', 'csharp', 'dbus', 'docs', @@ -81,6 +80,7 @@ docs_rst_files =3D [ 'coding-style', 'committer-guidelines', 'compiling', + 'contact', 'contribute', 'daemons', 'developer-tooling', --=20 2.35.1