That works well enough I think. Thanks for the explanation! On Thu, Jan 16, 2020 at 19:16 Mingshen Sun <[email protected]> wrote:
> I just tested whether I can reply the GitHub notification with email. > Yes, you can do that, but the name of the reply displayed on GitHub is > from our archiver (i.e., teaclave.archiver@gmail). > > That is, when you reply notification email from GitHub on our dev > list, the reply will be synced on behalf of the archiver. > > > On Thu, Jan 16, 2020 at 5:03 PM Mingshen Sun <[email protected]> wrote: > > > > Sorry for the late reply. > > > > Let me explain this again. > > > > Originally, GitBox will send notifications to dev@teaclave with > > issues/PRs/comments notifications, "making it seems that there is a > > lot of spam where the actual discussions get lost on the archives." > > [1] > > > > Then I propose this solution: > > > > - 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 > > > > However, 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. > > > > Then, I think TVM's dev list [2] may be a good solution - forwarding > > notifications of GitHub to dev list. This will keep the original > > discussion in thread, and not look like spam. > > > > I asked the INFRA team to redirect all GitBox notifications to > > notification@teaclave and only accept GitHub's notification in dev > > list. That's what you mentioned earlier on double notifications. > > > > I'm not sure if "responding to the dev@ thread does indeed mirror your > > comment back to GitHub". I'll try myself. > > > > Overall, here we want to solve is make the dev list looks clean and > useful. > > > > [1] > http://mail-archives.apache.org/mod_mbox/teaclave-dev/201912.mbox/browser > > [2] https://lists.apache.org/[email protected] > > > > > > On Thu, Jan 16, 2020 at 9:05 AM Matt Sicker <[email protected]> wrote: > > > > > > And I'm wondering what the purpose of mirroring notifications of any > > > kind to dev@ would do unless responding to the dev@ thread does indeed > > > mirror your comment back to GitHub. > > > > > > On Wed, 15 Jan 2020 at 13:09, Matt Sicker <[email protected]> wrote: > > > > > > > > That would just lead to double notifications still, wouldn't it? > > > > > > > > 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 > . > > > > > > > > > > Right now, we are trying to setup GitHub notifications forwarding > to > > > > > dev@teaclave. The only thing left is to setup the list to accept > > > > > notification from `[email protected]`. I have submitted the > > > > > ticket but no one take action yet. Let me ping the ticket again. > > > > > Thanks. > > > > > > > > > > > > > > > On Wed, Jan 15, 2020 at 8:09 AM Matt Sicker <[email protected]> > wrote: > > > > > > > > > > > > Ok yeah, I'm definitely seeing duplicate messages. It seems like > Infra > > > > > > enabled the notifications through a different mechanism. > > > > > > > > > > > > On Wed, 15 Jan 2020 at 10:05, Matt Sicker <[email protected]> > wrote: > > > > > > > > > > > > > > I'm also noticing that some of the GitHub notifications being > filtered > > > > > > > by the list are already being sent from another address now. > We can > > > > > > > probably remove the first notification setup now. > > > > > > > > > > > > > > On Wed, 15 Jan 2020 at 10:02, Matt Sicker <[email protected]> > wrote: > > > > > > > > > > > > > > > > Still getting flooded with moderation messages for filtered > messages. > > > > > > > > > > > > > > > > On Sun, 12 Jan 2020 at 18:53, Mingshen Sun <[email protected]> > wrote: > > > > > > > > > > > > > > > > > > Just give you guys an update on this. I have submitted the > ticket but > > > > > > > > > still haven't been setup up. Hopefully, this will resolve > this week. > > > > > > > > > Thanks. > > > > > > > > > > > > > > > > > > - > https://issues.apache.org/jira/projects/INFRA/issues/INFRA-19621 > > > > > > > > > > > > > > > > > > On Wed, Jan 8, 2020 at 11:43 AM Mingshen Sun < > [email protected]> wrote: > > > > > > > > > > > > > > > > > > > > Sure, I have submitted ticket to the INFRA team. Will > update this > > > > > > > > > > email when it's done. Thanks. > > > > > > > > > > > > > > > > > > > > On Wed, Jan 8, 2020 at 11:04 AM Matt Sicker < > [email protected]> wrote: > > > > > > > > > > > > > > > > > > > > > > I'm not really sure how that works, so I'd go the > infra route for now. > > > > > > > > > > > They might already have a service we can use for this. > > > > > > > > > > > > > > > > > > > > > > On Wed, 8 Jan 2020 at 12:12, Mingshen Sun < > [email protected]> wrote: > > > > > > > > > > > > > > > > > > > > > > > > Thanks. I have notice this issue. One extra step is > to put ` > > > > > > > > > > > > [email protected]` into the dev list's > whitelist. Should I contact > > > > > > > > > > > > INFRA team or our moderators can get it done? > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Jan 8, 2020 at 10:06 AM Matt Sicker < > [email protected]> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Seems that some sort of archival service isn't > actually subscribed to > > > > > > > > > > > > > the mailing list which is causing every > notification to be blocked. An > > > > > > > > > > > > > INFRA ticket could be helpful in configuring > notification lists here. > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > Matt Sicker <[email protected]> > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > > > > To unsubscribe, e-mail: > [email protected] > > > > > > > > > > > > > For additional commands, e-mail: > [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > Matt Sicker <[email protected]> > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > > 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] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Matt Sicker <[email protected]> > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Matt Sicker <[email protected]> > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Matt Sicker <[email protected]> > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > 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] > > > > > > > > > > > > > > > > > -- > > > > Matt Sicker <[email protected]> > > > > > > > > > > > > -- > > > Matt Sicker <[email protected]> > > > > > > --------------------------------------------------------------------- > > > 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] > > -- Matt Sicker <[email protected]>
