You're going to have to have a filter regardless. Why change now? Also, if you do change it, be sure to update all of the tracking sites such as markmail (etc...), I find this invaluable.
Regards, Patrick On Fri, May 10, 2019 at 1:18 AM Lars Francke <[email protected]> wrote: > INFRA can do it all :) > > See for example this: > <https://issues.apache.org/jira/browse/INFRA-17915> for Jira > <https://issues.apache.org/jira/browse/INFRA-18296> for Github > > The necessary mailing lists can be created here < > https://selfserve.apache.org/> > > I'd be happy to file the issues myself but it's better if it comes from a > PMC member. > > Cheers, > Lars > > On Fri, May 10, 2019 at 10:00 AM Andor Molnar <[email protected]> > wrote: > > > Hi Lars, > > > > Thank you for the hands, yes, indeed we are interested! > > Currently I'm using all kind of magic filters to separate signal from > > noise. > > > > What do we need to do? > > > > Regards, > > Andor > > > > > > > > On Fri, May 10, 2019 at 9:51 AM Lars Francke <[email protected]> > > wrote: > > > > > Hi, > > > > > > I've recently subscribed to the dev mailinglist but am overwhelmed by > the > > > number of github notifications and about to unsubscribe again. > > > > > > But maybe you're interested in moving the github & jira notifications > to > > a > > > different mailing list? I did a quick search for on the mailing list > > > archives but couldn't find another thread about it. > > > > > > The way we've done it at the Apache Training project now for example is > > to > > > send all Github notifications to notifications@ and all Jira messages > to > > > issues@ we only send Jira open and close mails to dev@ > > > > > > This lowers the volume significantly and works just fine. > > > > > > Is this something you'd be interested in? > > > > > > Cheers, > > > Lars > > > > > >
