I have submitted a issue [1] to the infra team to change the GitBox notification setup.
For the TVM dev list, they are using a separate email to forward GitHub's notification. ``` X-Forwarded-To: [email protected] X-Forwarded-For: [email protected] [email protected] Delivered-To: [email protected] ``` I'll try to use this method to manage the notifications in dev@teaclave. [1] https://issues.apache.org/jira/projects/INFRA/issues/INFRA-19621 On Tue, Dec 24, 2019 at 12:19 PM Mingshen Sun <[email protected]> wrote: > > I found that the TVM dev list [1] looks very clean and discussions on > one topic are listed in one thread. I'll submit an ticket to infra for > help. Thanks. > > [1] http://mail-archives.apache.org/mod_mbox/tvm-dev/201912.mbox/browser > > On Mon, Dec 23, 2019 at 12:58 PM Luciano Resende <[email protected]> wrote: > > > > On Mon, Dec 23, 2019 at 12:01 PM Mingshen Sun <[email protected]> wrote: > > > > > > Hi, I just take a look at our lists. I suggest to move all auto-sent > > > GitBox mails (contain issues, PR and review comments synced with > > > GitHub for archive) to `notifications@`, and keep the `commits@` (only > > > contains commit info) list as is. > > > > > > Then, the functionality of current lists are like this: > > > > > > - dev@: general dev related discussion (by human) > > > - commits@: auto-generated emails of commits for archive > > > - notifications@: auto-generated emails of GitBox syncs and other > > > third-party notifications for archive > > > > +1 > > > > > > > > I also want to raise one concern: since we are using GitHub as our > > > main development platform, issues, feature requests and RFC will > > > normally be posted on the "GitHub Issues". People subscribed to the > > > dev list will not see these updates on the GitHub. > > > > > > > Yes, that was going to be my next question. Maybe infra has dealt with > > this before? > > > > > Best, > > > Mingshen > > > > > > On Mon, Dec 23, 2019 at 11:23 AM Mingshen Sun <[email protected]> wrote: > > > > > > > > This is because of the initial gitbox setup. We have noticed this > > > > problem and contacted the infra team to consolidate the emails [1]. > > > > But seems that the gitbox does not support it. I'll try to submit > > > > another issue to categories the emails into different lists. > > > > > > > > 1. https://issues.apache.org/jira/browse/INFRA-19604 > > > > > > > > > > > > On Mon, Dec 23, 2019 at 11:15 AM Luciano Resende <[email protected]> > > > > wrote: > > > > > > > > > > Hi All, > > > > > > > > > > I wanted to check what's going on in the project and was trying to > > > > > browse [email protected] [1] and it seems that all GitHub notifications are > > > > > going directly to the dev list, making it seems that there is a lot of > > > > > spam where the actual discussions get lost on the archives. > > > > > > > > > > Just as a suggestion, other projects have created multiple lists (e.g. > > > > > issues@, notifications@ or reviews@) for these 3rd party integrations) > > > > > > > > > > > > > > > > > > > > [1] https://lists.apache.org/[email protected] > > > > > > > > > > -- > > > > > Luciano Resende > > > > > http://twitter.com/lresende1975 > > > > > http://lresende.blogspot.com/ > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [email protected] > > > > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > -- > > Luciano Resende > > http://twitter.com/lresende1975 > > http://lresende.blogspot.com/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
