So while the concept is a good one, I have concerns about the execution. Lets say you had a new announcement next week, would you just post to that list, knowing that most people havn't signed up for it yet, or would you cross post every announcement to dev, docs, infra, and announcements for the next year or so? Who would have access to post to it? Anyone? Board members? sig leads?
Its the same problem lots of reddit subredits have. People find a sub list too noisy, create more specialized subs, and then both become more empty. I'm scared of that happening here Especially since dev mailing list only gets a couple posts a day.
My vote is to reach out to discourse for a sponsorship, and move all async communication there. Instead of having like 8 mailing lists, and having to know which one to use, and new users to know which ones to sign up for, it would be a single thing. And if people post to the wrong form then it could be moved to the right place, or in the case of spam outright deleted. Discourse has email support so for those who prefer email, they can still post and reply via email. Plus it would mean it wouldn't be google and we could have ldap, google, github and twitter logins like we do for.
(Full disclosure, I'd love to centralize on discourse for async and matrix for sync)
Not at all blocking this idea, just voicing concerns.
Gavin