On Tue, Nov 25, 2014 at 6:59 AM, John D. Ament <johndam...@apache.org> wrote:
> So, if in the future we wanted to do this proactively we can send > > dev-allow-tc-no-reply=apache....@some.mailing.list.apache.org > > or does it always require the first failed message? When I became IPMC chair, I worried a lot about automated report reminders getting through to new podlings, to the point of checking dev list archives and subscribing in order to send manual reminders when the automated reminders did not arrive. There's a better way. When a podling fails to report, make absolutely sure they get added to next month's queue -- and make absolutely sure that they stay in that queue until they finally come through with a report. This is why report_runbook.py includes tasks for setting and clearing the "monthly" tag in podlings.xml. Taking this approach not only addresses the problem of comatose mailing list moderators, but a number of other more general problems related to low activity. Several years ago, the IPMC typically didn't take any action when podlings failed to report, and as a result we had a number of podlings failing to report for several quarterly cycles. It was a mess. We're better now. Marvin Humphrey --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
