meta: create a low traffic mailing list for PSAs to Collaborators (and interested parties)

[refack]

• Subsystem: meta

From time to time (should be less than one a week) comes a piece of news that should be broadcasted to all Collaborators. For example tweaks to the process, improvements, or temporary perturbations.
Currently communications are fragmented between GitHub, IRC, and even Twitter, and with that there is no "formal" channel for such announcements.
I suggest creating a mailing list that will include all Collaborators (and anyone else who wants to opt in) exclusively for this purpose. In order to keep people attentive to this list I suggest it will be opt-out to all collaborators, and either be writable only to a small group, or have explicit publishing rules.

Recent examples, and FYIs:

• Tool: node-core-utils a new CLI helper for core developers (first project of the new @nodejs/automation team)
• Process: Describe breaking changes in semver-major commit Better commit message for breaking changes. #16846
• Process: fast-track label Add a new label fast-track? #16877 (comment))
• Info: Project brad to track significant flakes https://github.com/nodejs/node/projects/8
• Info: Project board to track CI & Build system incidents https://github.com/nodejs/build/projects/1

/CC @nodejs/collaborators and @nodejs/community-committee

[refack]

I volunteer to champion this if we have consensus

[seishun]

I don't see much point in this given @nodejs/collaborators.

[benjamingr]

@seishun nodejs/collaborators is really noisy and it would save me (personally) time. So I'm +1 on it.

[Tiriel]

And for those of us who are not collaborators (yet?) but wanting to get involved, it would be really cool too.
+1

[bnoordhuis]

Not a fan. Multiple communication channels lead to fragmented discussion. I remember nodejs-dev@ and that was when the project was a fraction of its current size.

[Tiriel]

Well, from what I understand, it would be an announcement list only.
That is, if it's an information list only, for dispatching informations without actually commenting them, we'd still have to come on the issues to interact.

But having a digest of some sort juste like that would be a real help IMHO. We're all being flooded by GitHub notifications I think, this could be made to stand out more and keep us well informed.

[refack]

Multiple communication channels lead to fragmented discussion.

from what I understand, it would be an announcement list only.

I agree that the goal is to defragment communication...

1. it should be announcement only (so not a mailing list in the classical sense)
2. low traffic, and no replies
3. It could be a side-band channel for announcing special labelled issues.

[MylesBorins]

I would like to see something better than @nodejs/collaborators
There is currently no way to filter specific group mentions with github notifications, so any noticiation to collaborators usually gets lost in hundreds of other notifications (for me)

[targos]

This could be one of the requirements for our future communication tool: the ability to do general announcements and make them visible.

[joyeecheung]

We can also make a weekly newsletter that grabs issues/PRs labeled with certain labels each weak and summaries those, pretty much like how the tsc-review/tsc-agenda work. If it's no-reply then a newletter looks more suitable.

[joyeecheung]

cc @nodejs/community-committee I think this is related to commcomm?

[BridgeAR]

Seems like github team discussions are the actual solution to this. Closing therefore.