Also, if you're not already a moderator for the lists, please
volunteer to do so: https://issues.apache.org/jira/browse/INFRA-19758

On Thu, 23 Jan 2020 at 09:52, Matt Sicker <[email protected]> wrote:
>
> On Wed, 15 Jan 2020 at 12:49, Mingshen Sun <[email protected]> wrote:
> >
> > The original GitBox notifications go to the notification@teaclave for
> > archive: 
> > http://mail-archives.apache.org/mod_mbox/teaclave-notifications/202001.mbox/browser.
>
> This makes sense.
>
> > Right now, we are trying to setup GitHub notifications forwarding to
> > dev@teaclave.
>
> I already see all those messages going to notifications@ and commits@
> where applicable. This should not be duplicated on dev@. Development
> discussions should happen on the mailing list which can easily refer
> to a URL to the corresponding issue or pull request (and those
> comments are mirrored to notifications@). I'd suggest taking a look at
> some other Apache dev@ lists to see how mailing list traffic is
> separated into categories like this to make things easier for users
> (we on the PPMC, of course, are subscribed to all the lists, so it
> might not be as obvious how this can be useful).
>
> Unless I'm missing something, I think we can disable this dev@
> subscription for now.
>
>
> --
> Matt Sicker <[email protected]>



-- 
Matt Sicker <[email protected]>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to