From 967d4585656437fa804d4f90abe83463ab9e507b Mon Sep 17 00:00:00 2001
From: Rafael Fontenelle <rafaelff@gnome.org>
Date: Apr 14 2021 09:30:47 +0000
Subject: Update fedmsg homepage


http://fedmsg.com no longer fedmsg address
See https://github.com/fedora-infra/fedmsg/issues/524

Signed-off-by: Rafael Fontenelle <rafaelff@gnome.org>

---

diff --git a/UPGRADING.rst b/UPGRADING.rst
index f5defb1..c4fb50a 100644
--- a/UPGRADING.rst
+++ b/UPGRADING.rst
@@ -369,7 +369,7 @@ The release 3.11 brings some changes to the database schema.
 
 In addition, if you are deploying pagure with fedmsg support you had to set
 fedmsg to the
-`active <http://www.fedmsg.com/en/stable/publishing/#publishing-through-a-relay>`_
+`active <https://fedmsg.readthedocs.io/en/stable/publishing/#publishing-through-a-relay>`_
 mode for the workers to be able to send fedmsg messages. This is now the
 default and forced configuration.
 
diff --git a/doc/configuration.rst b/doc/configuration.rst
index df6e53d..95b4830 100644
--- a/doc/configuration.rst
+++ b/doc/configuration.rst
@@ -1316,7 +1316,7 @@ FEDMSG_NOTIFICATIONS
 ~~~~~~~~~~~~~~~~~~~~
 
 This configuration key can be used to turn on or off notifications via `fedmsg
-<http://www.fedmsg.com/>`_.
+<https://fedmsg.readthedocs.io/>`_.
 
 Defaults to: ``False``.
 
@@ -1333,7 +1333,7 @@ Defaults to: ``False``.
 ALWAYS_FEDMSG_ON_COMMITS
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-This configuration key can be used to enforce `fedmsg <http://www.fedmsg.com/>`_
+This configuration key can be used to enforce `fedmsg <https://fedmsg.readthedocs.io/>`_
 notifications on commits made on all projects in a pagure instance.
 
 Defaults to: ``True``.
diff --git a/doc/overview.rst b/doc/overview.rst
index 81af321..e732993 100644
--- a/doc/overview.rst
+++ b/doc/overview.rst
@@ -110,7 +110,7 @@ Pagure web-hook Server
 
 Sends notifications to third party services using POST http requests.
 
-This is the second notifications system in pagure with `fedmsg <http://fedmsg.com/>`_.
+This is the second notifications system in pagure with `fedmsg <https://fedmsg.readthedocs.io/>`_.
 These notifications are running on their own service to prevent blocking the
 main web application in case the third part service is timing-out or just
 being slow.
diff --git a/doc/usage/using_webhooks.rst b/doc/usage/using_webhooks.rst
index c3c7a7e..51b4282 100644
--- a/doc/usage/using_webhooks.rst
+++ b/doc/usage/using_webhooks.rst
@@ -17,7 +17,7 @@ Pagure will send a notification to this/these URL(s) for every action made
 on this project: new issue, new pull-request, new comments, new commits...
 
 .. note:: The notifications sent via web-hooks have the same payload as the
-    notifications sent via `fedmsg <http://www.fedmsg.com/en/latest/>`_.
+    notifications sent via `fedmsg <https://fedmsg.readthedocs.io/en/latest/>`_.
     Therefore, the list of pagure topics as well as example messages can be
     found in the `fedmsg documentation about pagure
     <https://fedora-fedmsg.readthedocs.io/en/latest/topics.html#id550>`_