Broadly speaking, I've found two kinds of mailing lists: help-focused, and develop-the-next-version-focused. Help-focused mailing lists lead to quick boredom a

Broadly speaking, I've found two kinds of mailing lists: help-focused, and develop-the-next-version-focused. Help-focused mailing lists lead to quick boredom and burnout for anyone who isn't deeply invested in the growth of the underlying project, e.g. core maintainers who use the questions to improve the project documentation, or who is otherwise paid to respond, e.g. professional support. Development-focused mailing lists have a strong tendency to turn into bikeshedding. Everybody who joins the mailing list is entitled to voice their opinion, everybody who subscribes to the mailing list is forced to listen to that opinion, and moderators have little power (outside of bans, which are rarely employed due to reputational risk to the moderator) to coerce the topic of discussion back on track to a more productive place. So core maintainers are incentivized to move development discussion to a more private forum, which is hidden from you. Eventually, I realized that what I actually wanted was (a) use boring, battle-tested tech, where I typically don't need minute-by-minute updates since any such updates are focused on extreme edge cases that probably don't apply to me, (b) subscribe me to feature-focused + security-focused release notes that I can skim on the relatively uncommon occurrences that there is actually a new feature/security release, (c) subscribe me to bug-focused release notes on bugs that I've explicitly opted-in to be notified on, because I've encountered those bugs, (d) a private forum to discuss day-to-day development on the projects that I'm actually working on (and that my colleagues are actually working on). Everything else - straight to /dev/null.