-
-
Notifications
You must be signed in to change notification settings - Fork 171
Closed
Labels
Description
The project as a whole appears to be migrating from Freenode: nodejs/TSC#1031
References to #node-build were removed from the core repo in nodejs/node#39047
Our README still references the channel:
Chat with us! We use IRC: #node-build at Freenode.
We should discuss whether to follow suite. I understand Freenode did a mass channel purge just over a week ago (https://www.devever.net/~hl/freenode_suicide) and all registered channels and nicknames were dropped.
I think our options are:
- Stay on #node-build on Freenode. The rest of the project is moving/has moved away.
- Move the channel to libera.chat. This is where the #node.js channel went. If we moved here it would be good to re-establish the IRC bridge.
- Move to some other IRC network. I'm not sure why we'd do this over Freenode (status quo) or libera (where the project is moving to).
- Move off IRC altogether. Options here include:
a. #build on node-js.slack.com. This still exists. This Slack is a free tier Slack so has limited preserved history (is that an issue?).
b. Move to the OpenJS Foundation Slack (openjs-foundation.slack.com). This is a paid tier Slack so preserves history. A number of other working groups (e.g. Release who are probably one of the constituents most likely to want to talk to someone from Build) have a channel in this Slack. It might be possible to use Slack Connect to bridge the channel between openjs-foundation.slack.com and node-js.slack.com so you would not need to be logged into two different Slack workspaces.
c. Something else (Discord/Gitter/Matrix/etc). Same as 3 -- I'm not sure what the benefits here would be (it would be yet another thing to have to log into). - Drop all "realtime" chat and force communication to GitHub issues (maybe enable discussions?).