From 238e78be26521653ffad5a38f53d7cd0b12f9948 Mon Sep 17 00:00:00 2001
From: Ryan Lerch <rlerch@redhat.com>
Date: Thu, 5 May 2022 15:35:39 +1000
Subject: [PATCH] [fmn]add an intro and fill out more about current issues

Signed-off-by: Ryan Lerch <rlerch@redhat.com>
---
 docs/fmn/april2022/index.rst | 43 ++++++++++++++++++++++--------------
 1 file changed, 27 insertions(+), 16 deletions(-)

diff --git a/docs/fmn/april2022/index.rst b/docs/fmn/april2022/index.rst
index 3ef9ee8..e21e95e 100644
--- a/docs/fmn/april2022/index.rst
+++ b/docs/fmn/april2022/index.rst
@@ -1,11 +1,34 @@
 FMN Replacement (April 2022)
 ============================
 
-References
-----------
+FMN is a web application allowing users to create filters on messages sent to fedmsg
+and forward these as notifications on to email or IRC
+
+* `current deployment <https://apps.fedoraproject.org/notifications/>`__
+* `FMN source <https://github.com/fedora-infra/fmn>`__
+* `CPE initiative ticket <https://pagure.io/cpe/initiatives-proposal/issue/10>`__
+
+Issues to solve
+---------------
+
+
+message delivery lag
+~~~~~~~~~~~~~~~~~~~~
+in times of peak congestion on the message queue (e.g. during a mass rebuild) it can take **days** for messages to be delivered to users.
+
+fedmsg
+~~~~~~
+The current version of FMN was implemented uses the deprecated fedmsg bus, not the currently supported Fedora Messaging (rabbitmq) message queue.
+
+Additionally, the FMN code is deeply integrated with the fedmsg ecosystem (e.g. the configuration setup for FMN is kept in the fedmsg.d/ directory)
+
+UI
+~~ 
+after adhoc discussions with the development community one of the major issues is the FMN web UI:
+    
+* The interface for creating new filters is complicated and confusing.
+* Users have to define filters seperately for different destentations (i.e. email and IRC) This is due to how the database is designed.
 
--  `mini-initiative <https://pagure.io/cpe/initiatives-proposal/issue/10>`__
--  `ARC output <https://fedora-arc.readthedocs.io/>`__
 
 Design options
 --------------
@@ -248,18 +271,6 @@ cancel the notification
 Existing FMN
 ------------
 
-Current Issues
-~~~~~~~~~~~~~~
-
-1. **message delivery lag** in times of peak congestion on the message
-   queue (e.g. during a mass rebuild) it can take **days** for messages
-   to be delivered to users.
-2. **fedmsg**
-3. **python2**
-4. **UI** after adhoc discussions with the development community one of
-   the major issues is the fmn UI – creating new filters is cumbersome,
-   and most people keep the standard filters or just turn them off.
-
 Current FMN code and usage analysis
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~