I think it's finally working! I haven't seen any new moderation emails
in a while.
On Thu, 23 Jan 2020 at 09:58, Matt Sicker wrote:
>
> 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
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 wrote:
>
> On Wed, 15 Jan 2020 at 12:49, Mingshen Sun wrote:
> >
> > The original GitBox notifications go to the notificat
On Wed, 15 Jan 2020 at 12:49, Mingshen Sun 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 notification
Wired, let me report this to the ticket I submitted to INFRA. Seems
that the people responsible for this is too busy to work on this
ticket.
On Mon, Jan 20, 2020 at 11:17 AM Matt Sicker wrote:
>
> Damn, it still didn't work. I wonder if it's because they generate
> unique reply-to addresses to b
Damn, it still didn't work. I wonder if it's because they generate
unique reply-to addresses to bridge email to comments?
For future reference, the "admin" page for this is here:
https://whimsy.apache.org/committers/moderationhelper
This is mostly just a web UI to generate the appropriate email
I just closed an issue on GitHub. There should be a notification sent
to the dev list from notificati...@github.com, but it didn't appear.
On Mon, Jan 20, 2020 at 9:50 AM Matt Sicker wrote:
>
> I found some feature of the mailing list to subscribe the
> notifications github email address. Let's
I found some feature of the mailing list to subscribe the
notifications github email address. Let's see if the next GitHub
notification makes it through.
On Thu, 16 Jan 2020 at 23:51, Mingshen Sun wrote:
>
> Ok, let me check with the INFRA team to see what's wrong.
>
> On Thu, Jan 16, 2020 at 9:4
Ok, let me check with the INFRA team to see what's wrong.
On Thu, Jan 16, 2020 at 9:49 PM Matt Sicker wrote:
>
> Still getting moderation mail for notifications. I wonder what’s wrong with
> the config? Do we need to add the email to a whitelist somewhere? I’ve
> never tried setting up GH notific
Still getting moderation mail for notifications. I wonder what’s wrong with
the config? Do we need to add the email to a whitelist somewhere? I’ve
never tried setting up GH notifications like this before.
On Thu, Jan 16, 2020 at 20:08 Matt Sicker wrote:
> I’ll watch for more moderation messages
I’ll watch for more moderation messages as new GitHub notifications come
through.
On Thu, Jan 16, 2020 at 20:08 Mingshen Sun wrote:
> INFRA said that emails from `notificati...@github.com` are whitelisted
> 11 hours ago [1]. Do our moderators still need to approve the email
> from GitHub? If not
INFRA said that emails from `notificati...@github.com` are whitelisted
11 hours ago [1]. Do our moderators still need to approve the email
from GitHub? If not, I'll ask INFRA for help.
[1]
https://issues.apache.org/jira/browse/INFRA-19621?focusedCommentId=17017001&page=com.atlassian.jira.plugin.s
That works well enough I think. Thanks for the explanation!
On Thu, Jan 16, 2020 at 19:16 Mingshen Sun 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.archi
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
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@:
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 wrote:
>
> That would just lead to double notifications still, wouldn't it?
>
>
That would just lead to double notifications still, wouldn't it?
On Wed, 15 Jan 2020 at 12:49, Mingshen Sun 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
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
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 wrote:
>
> I'm also noticing that some of the GitHub notifications being filtered
> by the list are already being sent from ano
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 wrote:
>
> Still getting flooded with moderation messages for filt
Still getting flooded with moderation messages for filtered messages.
On Sun, 12 Jan 2020 at 18:53, Mingshen Sun 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.a
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 wrote:
>
> Sure, I have submitted tic
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 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
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 wrote:
>
> Thanks. I have notice this issue. One extra step is to put `
> notificati...@github.com` into the dev list's whitelis
Thanks. I have notice this issue. One extra step is to put `
notificati...@github.com` 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 wrote:
> Seems that some sort of archival service isn't actually subsc
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
-
25 matches
Mail list logo
