www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cédric Champeau (JIRA) <j...@apache.org>
Subject [jira] [Commented] (INFRA-9562) Excessive moderation of Groovy mailing list?
Date Fri, 01 May 2015 09:32:06 GMT

    [ https://issues.apache.org/jira/browse/INFRA-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522985#comment-14522985

Cédric Champeau commented on INFRA-9562:

Awesome, thank you Gavin, you saved me a lot of time! I did receive emails this morning without
having to moderate, that's a relief! Actually I understand that I didn't get the "reply-all"
correctly. It was "reply-all" to the *moderate* email, not reply-all to the email that users
send, right? That explains why I didn't see why it would be relevant to my issue.

Thanks again!

> Excessive moderation of Groovy mailing list?
> --------------------------------------------
>                 Key: INFRA-9562
>                 URL: https://issues.apache.org/jira/browse/INFRA-9562
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Cédric Champeau
>            Assignee: Gavin
>         Attachments: mailinglists.png
> Hi!
> I am sincerely wondering if there's not something wrong with the way the dev@ list for
Groovy is configured. Basically I have to validate *all* messages that come to the list, independently
of the fact I was the sender or not, or if any of the senders is a member of the PMC.
> There's interestingly good traffic on the dev@ list (much more than users@, which is
kind of expected now that everybody seeks support on StackOverflow) but it also means I'm
getting tons of notifications.
> I wonder if we can disable moderation at all. I've been told about HTML emails that could
cause trouble, but we're in 2015, I simply cannot tell everybody who is sending a message
to send a plain text one (and GMail doesn't make it easy anyway).
> The thing that makes me wonder is that I don't seem to have the problem on the user@

This message was sent by Atlassian JIRA

View raw message