incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (398J)" <>
Subject Re: Moderation of report reminders
Date Sat, 13 Jul 2013 18:10:43 GMT
Hey Marvin,

Thanks for the background -- my vote would be for the allow list approach.


Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA

-----Original Message-----
From: Marvin Humphrey <>
Reply-To: "" <>
Date: Saturday, July 13, 2013 10:57 AM
To: "" <>
Subject: Moderation of report reminders

>This report cycle, I audited the report reminders sent out by "Marvin"[1].
>After waiting a couple of days for moderation to clear, I used a web
>to check the dev list archives for each podling in the report cycle to see
>whether the message had arrived.  Reminders did not made it through for
>podlings: Celix, Tajo, and VXQuery.
>For each of the three, I subscribed to the dev list to sidestep
>sent a manual reminder, then promptly unsubscribed.  The nudging worked:
>eventually filed reports.
>Report reminders not getting moderated through has been a problem for
>and it's time we solved it once and for all.  Obviously, the
>approach I took this month is not sustainable -- we need something
>One possibility would be to set up a script to trawl the mbox archives
>scanning for report reminders a couple days after they were sent out, then
>mail general@incubator with a report enumerating which reminders didn't go
>through.  This may sound like a large project, but we would be able to
>leverage a lot of code which Brane wrote for the vote scan:
>We might also gather other information during the same trawl and generate
>more rich report:
>*   Generate message counts for each podling mailing list, as a rough
>    barometer of activity.
>*   Scan for Mentor email addresses in recent messages, as a crude
>    aid.
>*   (Suggestions?)
>A second possibility might be to consolidate `-allow` lists.  (I'm not
>whether this is technically feasible -- it came up yesterday on the infra
>list, but the discussion was not conclusive.  Perhaps one of the
>Infrastructure people on this list could comment.)
>The idea is that instead of having dedicated `-allow` lists for each
>dev list, we would have one omnibus public-allow@incubator list.  Once we
>approve `Marvin <>` by adding it to that list, then
>reminders will always go through, even for new podlings.
>Marvin Humphrey
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message