#10 Can’t disable notification email
Closed: Fixed None Opened 5 years ago by mitr.

Hello,
Looking at https://admin.fedoraproject.org/pkgdb/package/openssh/ , I’m a “committer” to openssh, but ''not'' in the watchers list. Nevertheless I have recently started receiving notification email for every commit:

To: openssh-owner@fedoraproject.org, scm-commits@lists.fedoraproject.org
From: plautrba plautrba@fedoraproject.org

I can’t see any way to opt out of these emails, except maybe by giving up all commit access, which I don’t really want to do. (Client-side filtering is of course an option but overall a waste.)

What am I missing?


This is true and was by design.

The idea is that, if you have commit rights you get the notification by default, you are one of the person that can act on the package if something goes south, so you should know what's going on.

I'm against this "feature" of "you have commit rights => you'll be auto-CC'ed in bugs". I have commit rights only to be able to rebuild the package when I release my package with soname version change, thus I can save time to the right maintainers and rebuild the package for them. This doesn't mean at all that I'm able to fix any random bug report filled for the package.

The increased mail transfer is also waste of resources. The implicit implication "you have commit rights => you'll be auto-CC'ed in bugs" should be avoided, as long as the package ACL contains separate fields for commit rights, commit watch and bugs watch. I want to have the system under control, not it having under control me.

By the way, are you CC'ing every proven packager to each filled bug report? Proven packagers have automatic commit rights to all packages, thus the idea of "you can commit => you can fix any random bug report filled" applies to them too (I understood the idea for this "feature" being motivated exactly by this assumption).

Please revert back to the previous behavior. I'm now getting duplicate bug mail for every kernel bug. This change doesn't take into account packages that are maintained by a group account (e.g. kernel-maint for kernel), which means I now get an email to the group account and to my personal account.

Yeah, I think we should revert this behavior... there's several use cases (above) that depend on the old behavior and if we want to change it we probibly need to announce it loudly beforehand. ;(

Login to comment on this ticket.

Metadata