From Usenet Big-8 Management Board
  • Administration
    • news.newusers.questions news.newusers.questions on Google Groups and news.announce.newusers news.announce.newusers on Google Groups
      • RL still in the process of setting up STUMP for news.announce.newusers news.announce.newusers on Google Groups, as some procmail recipes need debugging. (The existing rules mistakenly allowed two test messages to be posted to the group despite being rejected by STUMP.)
      • RL has posted the charters and signing keys for these groups on the wiki
      • Revising the FAQs still TBD
    • comp.os.linux.announce comp.os.linux.announce on Google Groups
      • TM and Salahuddin were unable to reproduce the problem when posting from Google Groups. PS wrote to indicate that the issue may be linked to a recent flooding attack, as a result of which Google Groups made several groups read-only or gated behind a (possibly buggy) CAPTCHA.
    • rec.radio.broadcasting rec.radio.broadcasting on Google Groups
      • TM still to prepare a final MVI for posting this month.
  • Infrastructure
    • Procmail
      • RL discovered some posts for comp.ai comp.ai on Google Groups, all from the same poster, had been mistakenly put in the Board's Panix inbox rather than being forwarded to the moderator. The meeting examined the .procmailrc file and log but couldn't determine the cause of this. It was agreed that RL would remove the obsolete spam-reporting rules from the .procmailrc file. RL will continue to study and revise the file to get the news.announce.newusers news.announce.newusers on Google Groups rules working. TM to thereafter check the comp.ai comp.ai on Google Groups rules.
  • (Web)STUMP
    • TM: No update yet on GPG signing best practices on Savannah
  • Publicity
  • Misc