Hey Marvin, Thanks for the background -- my vote would be for the allow list approach.
Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Marvin Humphrey <mar...@rectangular.com> Reply-To: "general@incubator.apache.org" <general@incubator.apache.org> Date: Saturday, July 13, 2013 10:57 AM To: "general@incubator.apache.org" <general@incubator.apache.org> Subject: Moderation of report reminders >Greets, > >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 >browser >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 >three >podlings: Celix, Tajo, and VXQuery. > >For each of the three, I subscribed to the dev list to sidestep >moderation, >sent a manual reminder, then promptly unsubscribed. The nudging worked: >all >eventually filed reports. > >Report reminders not getting moderated through has been a problem for >years, >and it's time we solved it once and for all. Obviously, the >labor-intensive >approach I took this month is not sustainable -- we need something >automatic. > >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: > > https://svn.apache.org/repos/asf/incubator/public/trunk/voter/ > >We might also gather other information during the same trawl and generate >a >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 >shepherding > aid. >* (Suggestions?) > >A second possibility might be to consolidate `-allow` lists. (I'm not >sure >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 >podling >dev list, we would have one omnibus public-allow@incubator list. Once we >approve `Marvin <no-re...@apache.org>` by adding it to that list, then >reminders will always go through, even for new podlings. > >Thoughts? > >Marvin Humphrey > >[1] >https://svn.apache.org/repos/infra/infrastructure/trunk/tools/board_remind >ers > >--------------------------------------------------------------------- >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
