On Mon, 25 Apr 2016 19:46:23 +0000 Patrick Uiterwijk <puiterwijk@xxxxxxxxxx> wrote: > On Mon, Apr 25, 2016 at 7:37 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > Greetings. > > > > Right now we send fedmsgs for most lists. There's a small few lists > > that we don't want to send any messages for as they might have > > sensitive items discussed on them. > > > > There's pretty much no way I can think of to tell this trait from > > mailman (we have 'advertised', but thats not at all the same thing). > > > > See tickets: > > https://fedorahosted.org/fedora-infrastructure/ticket/5030 > > https://fedorahosted.org/fedora-infrastructure/ticket/5258 > > > > So, the best we can do is maintain a list of these and update it on > > request. (Thanks to decause for the initial patch which I expanded > > on). > > > > I'd like to apply the following patch and run the mailman playbooks: > > > > diff --git a/roles/mailman/files/fedmsg-plugin-conf.py > > b/roles/mailman/files/fedmsg-plugin-conf.py index 3ee3567..e1f7732 > > 100644 --- a/roles/mailman/files/fedmsg-plugin-conf.py > > +++ b/roles/mailman/files/fedmsg-plugin-conf.py > > @@ -1,8 +1,10 @@ > > config = { > > - # These are mailing lists that we don't publish to fedmsg > > (because spam) > > + # These are mailing lists that we don't publish to fedmsg > > (because spam or privacy) 'mailman.excluded_lists': [ > > - 'scm-commits', > > - #'i18n-bugs',isable this eventually > > - #'fonts-bugs', # disable this eventually > > + 'scm-commits', # too much traffic > > This is already on the bus anyway. Yes, but we don't want to _also_ create a new fedmsg for each mailing list post. In addition to each pkgdb fedmsg, each scm commit fedmsg, etc, etc. The patch doesn't change this, if you look up it's already been the only thing in this mailing list blacklist. ;) kevin
Attachment:
pgp8j45zWOBvt.pgp
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
