docs: update docs pointing to old mailing list addrs

Reviewed-by: Ján Tomko <jtomko@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

README.rst

@@ -64,8 +64,8 @@ Contact
 
 The libvirt project has two primary mailing lists:
 
-* libvirt-users@redhat.com (**for user discussions**)
-* libvir-list@redhat.com (**for development only**)
+* users@lists.libvirt.org (**for user discussions**)
+* devel@lists.libvirt.org (**for development only**)
 
 Further details on contacting the project are available on the website:
 

docs/bindings.rst

@@ -58,6 +58,6 @@ For information on using libvirt on **Windows** `please see the Windows
 support page <windows.html>`__.
 
 Support, requests or help for libvirt bindings are welcome on the
-`mailing list <https://listman.redhat.com/mailman/listinfo/libvir-list/>`__,
+`devel mailing list <https://lists.libvirt.org/admin/lists/devel.lists.libvirt.org/>`__,
 as usual try to provide enough background information and make sure you
 use recent version, see the `help page <bugs.html>`__.

docs/contact.rst

@@ -19,11 +19,11 @@ Mailing lists
 
 There are three mailing-lists:
 
-**libvir-list@redhat.com** (for development)
+**devel@lists.libvirt.org** (for development)
    Archives
-     https://listman.redhat.com/archives/libvir-list
+     https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/
    List info
-     https://listman.redhat.com/mailman/listinfo/libvir-list
+     https://lists.libvirt.org/admin/lists/devel.lists.libvirt.org/
 
    This is a high volume mailing list. It is a place for discussions about the
    **development** of libvirt.
@@ -35,11 +35,11 @@ There are three mailing-lists:
    -  Development of language bindings for libvirt API
    -  Testing and documentation of libvirt
 
-**libvirt-users@redhat.com** (for users)
+**users@lists.libvirt.org** (for users)
    Archives
-     https://listman.redhat.com/archives/libvirt-users
+     https://lists.libvirt.org/archives/list/users@lists.libvirt.org/
    List info
-     https://listman.redhat.com/mailman/listinfo/libvirt-users
+     https://lists.libvirt.org/admin/lists/users.lists.libvirt.org/
 
    This is a moderate volume mailing list. It is a place for discussions
    involving libvirt **users**.
@@ -51,11 +51,11 @@ There are three mailing-lists:
    -  Development of applications on top of / using the libvirt API(s)
    -  Any other topics along these lines
 
-**libvirt-announce@redhat.com** (for release notices)
+**announce@lists.libvirt.org** (for release notices)
    Archives
-     https://listman.redhat.com/archives/libvirt-announce
+     https://lists.libvirt.org/archives/list/announce@lists.libvirt.org/
    List info
-     https://listman.redhat.com/mailman/listinfo/libvirt-announce
+     https://lists.libvirt.org/admin/lists/announce.lists.libvirt.org/
 
    This is a low volume mailing list, with restricted posting, for announcements
    of new libvirt releases.

docs/downloads.rst

@@ -336,7 +336,7 @@ And there are also read-only mirrors on libvirt.org:
 
 Note that for most repositories, development happens via merge requests
 on GitLab. However, for the main `libvirt.git` repository all patch review and
-discussion only occurs on the `libvir-list <contact.html>`__ mailing list.
+discussion only occurs on the `devel <contact.html>`__ mailing list.
 
 The GitHub repository is read-only and pull requests and issues there are ignored.
 

docs/newreposetup.rst

@@ -41,7 +41,7 @@ required under the **Settings** page:
 
   * **Pipelines emails**
 
-    * *Recipients*: ``libvirt-ci@redhat.com``
+    * *Recipients*: ``ci@lists.libvirt.org``
 
 * **Repository**
 

docs/securityprocess.rst

@@ -20,7 +20,7 @@ address:
 
 ::
 
-   libvirt-security@redhat.com
+   security@lists.libvirt.org
 
 NB. while this email address is backed by a mailing list, it is invitation only
 and moderated for non-members. As such you will receive an auto-reply indicating

docs/submitting-patches.rst

@@ -35,7 +35,7 @@ When you want to post your patches:
   $ git pull --rebase
   (fix any conflicts)
   $ git send-email --cover-letter --no-chain-reply-to --annotate \
-                   --confirm=always --to=libvir-list@redhat.com master
+                   --confirm=always --to=devel@lists.libvirt.org master
 
 For a single patch you can omit ``--cover-letter``, but a
 series of two or more patches needs a cover letter.
@@ -51,13 +51,13 @@ to your SMTP server with something like:
 
   $ git config --global sendemail.smtpServer stmp.youremailprovider.net
 
-If you get tired of typing ``--to=libvir-list@redhat.com`` all
+If you get tired of typing ``--to=devel@lists.libvirt.org`` all
 the time, you can configure that to be automatically handled as
 well:
 
 ::
 
-  $ git config sendemail.to libvir-list@redhat.com
+  $ git config sendemail.to devel@lists.libvirt.org
 
 Avoid using mail clients for sending patches, as most of them
 will mangle the messages in some way, making them unusable for
@@ -65,8 +65,8 @@ our purposes. Gmail and other Web-based mail clients are
 particularly bad at this.
 
 If everything went well, your patch should show up on the
-`libvir-list
-archives <https://listman.redhat.com/archives/libvir-list/>`__ in a
+`devel list
+archives <https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/>`__ in a
 matter of minutes; if you still can't find it on there after an
 hour or so, you should double-check your setup. **Note that, if
 you are not already a subscriber, your very first post to the

docs/testapi.rst

@@ -30,5 +30,5 @@ For more details you can look at:
 
 Libvirt-test-API is maintained using `a GIT
 repository <https://gitlab.com/libvirt/libvirt-test-API>`__, and comment,
-patches and reviews are carried on the `libvir-list <contact.html>`__
-development list.
+patches and reviews are carried on the `devel <contact.html>`__
+mailing list.