Re: State of FMN (FedMSG Notifications) and Replacement

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Wed, 26 Feb 2020 at 09:17, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote:
On Wed, 2020-02-26 at 08:26 +0100, Clement Verna wrote:
> Hi all,
>
> FMN (https://apps.fedoraproject.org/notifications) is currently one of the
> main blocking point for dropping fedmsg in favour of fedora-messaging.
> FMN is quite important to the community and the composition of Fedora
> because it gives emails and notifications on commits, composes, builds and
> updates via email and other tools.
>
> However, the code base is written in Python 2.7 and not maintained anymore.
> Currently the service has to run on a Fedora 28 system to continue running.
> This causes multiple problems and concerns, and needs to be addressed
> before the datacenter move in June.
>
> In order to start putting together a specification for a replacement, we
> should try to look at the minimum requirements for a notification system.
> For example the current system supports sending notifications to IRC,
> emails and SSE (Server Sent Event), Can we live without SSE ? Can we live
> without IRC ? Do we need it to monitor everything it does currently or just
> a subset of items that the community has found useful.
>
> Let's use this thread to brainstorm ideas on what we need.

I'd note that a key feature of FMN is that it provides human-readable
summaries of messages. For fedmsg this is achieved through the fedmsg
metadata system, and the Fedora providers for it:

https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/

for fedora-messaging, the intended way to do approximately the same
thing is with message schemas:

https://fedora-messaging.readthedocs.io/en/latest/messages.html#schema

as part of modernizing FMN and rewriting it on fedora-messaging, we
might well need to get fedora-messaging schema coverage up to a similar
level as we have fedmsg meta coverage. We may want to see if we can
come up with an automated or semi-automated process for converting
fedmsg meta providers to fedora-messaging schemas, even...

Yes this also part of this thread to identify which messages we really care about, so that we can focus on providing schema for these first. Messages that are a little bit less important would come later.
 
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux