Move to OpenJS Foundation Slack?

[mmarchini]

The OpenJS Foundation has a paid Slack server available for projects to use (invite), which means we have access to more features (more integrations etc) as well as infinite chat history. Does anyone oppose to moving the #build channel from NodeSlackers to OpenJS Foundation Slack? I tried using Slack Connect but both organizations need to be paid tier for it to work.

[mhdawson]

+1 to move top the OpenJS Slack. I need to be active there anyway so it would be easier for me.

[BethGriggs]

Is there an update or any more feedback on this?

It just I find myself and others end up cross-posting about the same issues across both workspaces. With #nodejs-release and #nodejs-dev in the OpenJS Slack, it might be nice for #nodejs-build to be in there too so we can more easily share/link messages across channels.

[sxa555]

Like you I'm in both of them, so I can't think of a good reason not to shift it across especially if it gains the benefit of permanent history, so I'm +1.

…

On Tue, 12 Apr 2022, 21:45 Bethany Nicolle Griggs, ***@***.***> wrote: Is there an update or any more feedback on this? It just I find myself and others end up cross-posting about the same issues across both workspaces. With #nodejs-release and #nodejs-dev in the OpenJS Slack, it might be nice for #nodejs-build to be in there too so we can more easily share/link messages across channels. — Reply to this email directly, view it on GitHub <#2875 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APDJLOAOSEHY73LYY5ROL5LVEXOH3ANCNFSM5O3CB7MA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mhdawson]

@nodejs/build one more ping to see if there are any concerns on moving over.

[sxa]

(Have pinged the slack channel to see if there are any extra views from people who aren't watching this issue)

[AshCripps]

+1 on the move, But when we make can we post a message pointing people to the new channel and then lock the old channel to stop people posting where we will miss it?

[richardlau]

I've gone ahead and created #nodejs-build in the OpenJS Foundation Slack. I have no idea if it's possible to lock the channel in NodeSlackers.

[Trott]

I have no idea if it's possible to lock the channel in NodeSlackers.

In Slack parlance, the thing to do is probably to archive that channel. It will still be searchable, but people won't be able to join or post. I'll see if I can find out who an admin for that Slack is and if they would be willing to archive the channel after posting an @channel message to everyone gets notified about the move. (I don't think unprivileged users can post @channel messages in that Slack.)

[Trott]

I have no idea if it's possible to lock the channel in NodeSlackers.

In Slack parlance, the thing to do is probably to archive that channel. It will still be searchable, but people won't be able to join or post. I'll see if I can find out who an admin for that Slack is and if they would be willing to archive the channel after posting an @channel message so everyone gets notified about the move. (I don't think unprivileged users can post @channel messages in that Slack.)

@ljharb You are one of the admins in Nodeslackers, right?

[ljharb]

Yep, I am. I can certainly archive it, and do my best to leave a redirect message that survives the 10K message limit.

[ljharb]

Done. Let me know if any further changes are needed.

[richardlau]

Doc updates: #2928