Infrastructure/arc
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Styling fixes

Browse source 
Signed-off-by: Michal Konečný <mkonecny@redhat.com>
This commit is contained in:
Michal Konečný 2022-05-12 13:33:06 +02:00
parent 2b596656cc
commit 9754fa374f
1 changed files with 6 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/fmn/april2022/index.rst
View file

@ -12,9 +12,9 @@ Issues to solve
---------------
message delivery lag
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.
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
~~~~~~
@ -23,8 +23,9 @@ The current version of FMN was implemented uses the deprecated fedmsg bus, not t
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:
---
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.
@ -49,7 +50,7 @@ This work requires all applications to use Fedora Messaging Message
Schemas, because the triage component will rely on schemas to extract
information from the messages.
Later on, whe we refer to artifacts, we mean artifacts produced by the
Later on, when we refer to artifacts, we mean artifacts produced by the
Fedora infrastructure: packages, containers, modules, flatpaks.
Stakeholders