Earlier this week, Matthew and I were discussing the idea of a “contributor-announce” mailing list that would seem to fill a gap in the existing communication tools. You can think of it as a parallel to devel-announce, but for topics that are more broadly-applicable. It would be for “internal” announcements that don’t necessarily apply to the user community served by the announce mailing list.
Some announcements that would fit on this list:
- “Major” Council policy proposals (like the recent content license and Code of Conduct proposals)
- Upcoming contributor events (Flock/Nest, etc)
- Creation of new teams
- Service outage notifications
Like announce and devel-announce, it would be moderated and use for broadcast-only. Messages should include a pointer to the appropriate place for further discussion. The idea is to not replace existing mailing lists, this forum, or the Community Blog. It’s a way to augment those for people who don’t normally follow them.
The main challenge I see is how to initialize the recipients. We don’t have a single place to announce this list (which is why it should exist), so we can blast it to as many existing places as we can think of. Alternatively, we can get a list of every email address with an FPCA and bulk add them with an intro message that clearly states the purpose and provides instructions for opting out. The latter is more effective, but feels icky. The former I fear will mean nobody signs up for it and the list will be useless.
In either case, we should try to make sure we encourage new people to join the list (perhaps in the account creation UI). I don’t think it’s necessary to prohibit (by policy or by practice) unsubscribing from the list, but we should set the expectation that if it was announced on the list, you’re not allowed to say you weren’t informed.
I’m adding this to the agenda for tomorrow’s Council meeting, but I wanted to get the conversation started here.