Create Means for Private Communications

[flakey5]

Currently all of the methods we have for team-wide communication (GitHub, OpenJS slack) are public. This works and is great for day-to-day ops and communications, however, sometimes we need to discuss more sensitive topics (i.e. security concerns) and there's not a great way to do so currently.

I think we should either have a private repository (such as nodejs/web-team-private) or a channel in the OpenJS slack (such as #nodejs-website-private) where we can discuss such things. Note this should only be used for sensitive topics and should not replace our current communication methods for non-sensitive topics.

I lean more towards having a private repository since there's more precedent for that.

[avivkeller]

+1 to the GitHub repository, I wonder if the TSC will allow nodejs-private/web-team and nodejs-private/web-infra repositories. If not, we can also store them in this organization.

[bmuenzenmeyer]

do we have strong use cases for this?
as a moderation team member, it's REALLY burdensome to help the community when comms becomes less open

[flakey5]

do we have strong use cases for this?

The primary use case would be for things relating to security. We historically haven't had much of these thankfully, but when they do happen this would allow us to have an immediate place that we can talk with others about it.

These would ideally also replace the one-use private channels or group chats that we currently have for these type of events as well.

it's REALLY burdensome to help the community when comms becomes less open

Definitely understand, which is why this should only be used for things that are sensitive and cannot be public (at least at the time that the thing pops up)