fesco

#1947 Messages from notifications@fedoraproject.org are not usable + possible fix
Closed: Invalid Opened by jwrdegoede.

Closed: Invalid
Reopen Issue

After I broke Fedora 27 today I was afraid that I had missed a message from the automatic dep checker coming from notifications@fedoraproject.org, but I checked my special "notifications" mail folder and there was no such message there.

This did make me realize though, that IMHO the current way email notifcations work is fundamentally broken.

Before we had fedmsg and the notification system, there was a small set of well defined things which would send an email, including IIRC a dep-checker running on the updates and updates-testing repo.

Now a days mails from notifications@fedoraproject.org have turned into a firehose. I know that this can all be configured, but this configuration is about as useful (and usable) as the privacy settings panel from facebook (or what I've heard about it I don't have a facebook account).

In the beginning I tried to use the filtering, but now I just have my mail client put any mails from notifications@fedoraproject.org in a mail folder, which I check maybe once a month.

The soundtouch problem has made me realize that this may very well cause me to miss an important message one day (I actually expected I did this time), but I really don't have the bandwidth to deal with this in any other way...

So now that I've hopefully clearly described the problem, I believe I also have a solution, the notifications need to be extended with a way to add a severity level or some such to them. Almost all of them would be of a severity level of "info", but e.g. koji build failures could get a level of "warning" and a dep-check failure would get a level of "error".

And then an extra option could be added to select only emails for a level of warning or higher,
and/or warning and error messages could be send with a different from, e.g. warnings@fedoraproject.org so that mail filters won't pick them up (unless modified to explicitly pick these up).

To being able to filter by a severity level seems a lot more useful / usable then being able to turn on/off every type of messages individually, esp. since new types are added regularly.

You can filter the messages you get sent in FMN. That would help the firehose aspect if you haven't done it yet.

Aside from that, I don't think this is a FESCo issue. You probably want to work with @ralph and the infrastructure team to file some RFEs.

Yes, I don't think it's something FESCo can do much about. We could express sentiment that notifications should be filterable, but we cannot provide the implementation, or even say how it should look.

I am sorry the filtering config is so arcane. It really needs a redesign with some UI folks. ;(

I agree this should be a FMN RFE if you could file it.

One issue is how do we determine what level each message is?
One persons high might be another persons low.

One other thing we can do is adjust the default packager set of things. Normal users in FMN start with a clean slate (no messages), but packagers we set with a default set of messages that should be useful to them. If this is too much of a firehose we could adjust all packagers and the initial template to not send so many.

Hi,

On 18-07-18 00:32, Kevin Fenzi wrote:

kevin added a new comment to an issue you are following:
``
I am sorry the filtering config is so arcane. It really needs a redesign with some UI folks. ;(

I agree this should be a FMN RFE if you could file it.

Sure, what is the correct pagure project to file an RFE against for this?

One issue is how do we determine what level each message is?

I would say build failures and thinks like dep-checks or other tests failing should be of higher then normal severity while almost everything else should be normal severity. But I can see how different people might have different idea here.

One persons high might be another persons low.

One other thing we can do is adjust the default packager set of things. Normal users in FMN start with a clean slate (no messages), but packagers we set with a default set of messages that should be useful to them. If this is too much of a firehose we could adjust all packagers and the initial template to not send so many.

Interesting, so this template exists today I guess? How can I
reset my settings to this template?

Regards,

Hans

Hi,

Sure, what is the correct pagure project to file an RFE against for this?

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

One issue is how do we determine what level each message is?

I would say build failures and thinks like dep-checks or other tests failing should be of higher then normal severity while almost everything else should be normal severity. But I can see how different people might have different idea here.

Additionally it would take end users adjusting their filtering to use this. If they just all put them in one folder it wouldn't help. ;(

One persons high might be another persons low.
One other thing we can do is adjust the default packager set of things. Normal users in FMN start with a clean slate (no messages), but packagers we set with a default set of messages that should be useful to them. If this is too much of a firehose we could adjust all packagers and the initial template to not send so many.

Interesting, so this template exists today I guess? How can I
reset my settings to this template?

Go to https://apps.fedoraproject.org/notifications/ , login, select email or irc, on the right down a bit is "Party Perished", click the 'reset' there and it should take you back to defaults.

RFE filed here: https://github.com/fedora-infra/fmn/issues/301

I am closing this since it's an infrastructure issue.

Metadata Update from @bowlofeggs:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.