Add Node Slack Community to scope

[hackygolucky]

Adds the Node.js Slack Community to the list of Moderation Team scope. Admins from the Slack community have agreed to posting and upholding the CoC and collaborating with the Moderation Team to uphold the guidelines. cc @alextes @ljharb

To note: would like to try this as well with #nodejs on Freenode IRC, but it takes a bit more work. So it stays listed in 'unofficial' on the Node.js community resources until/if we're able to confirm the same and have an admin team with bandwidth to support the existing community.

NOTE: DO NOT MERGE THIS UNTIL https://github.com/nodejs/getting-started/pull/10/files lands. Then link to it for anyone wanting further info on the group and finding it.

[jasnell]

Before bringing this into the scope of the moderation team, it would be good to have the community committee weigh in on it. The admins of the slack channel should, at the very least, be members of the community committee.

Otherwise, I'm +1 on this.

[ljharb]

@jasnell while I'm happy to join the community committee, I think if the goal is to onboard existing communities, requiring that there be a 1:1 correlation between the community committee and the admins of an existing community just doesn't make much sense (requiring that there be nonzero overlap absolutely make sense, of course).

[jasnell]

On the core side of things, we have a separation between Collaborator and TSC member... if the Community Committee had something similar, I'd say that the admins should at, the very least, be in that CommComm idea of a "collaborators" group :-) ... (I hope that at least made a little bit of sense)

[mhdawson]

As opposed to making members of the existing group become a member of the CommComm would it make sense to ask that a designate from the CommComm committee be added as an admin?

[ljharb]

@mhdawson @hackygolucky is already an admin.

[mhdawson]

I think as long as we have CommComm representatives with admin access that seems good enough to me.

[alextes]

Am actually already looking into what joining the commcomm would take 😄 . Would be open to it in any case. Seems there may be no need 👍 .

[mcollina]

Do we have a link to that Slack organization? How do someone join? Can we refer from that to this document?

[hackygolucky]

@mcollina you want us to link to https://github.com/nodejs/getting-started/pull/10/files when it lands? We've got it in the Getting Started

[mcollina]

@hackygolucky yes, that would be perfect.

[hackygolucky]

I'll put it as a next step on the description @mcollina

[alextes]

@Fishrock123 can you clarify what you mean by management resources? Perhaps there are meeting notes I can read 😁 ?

[hackygolucky]

@Fishrock123 given comments, are you still -1 on this?

[mhdawson]

Having just going to the main page to log in to the channel, it seems to list a number of places you already need to be a member of to be able to create an account. The list is @freebird.com.hk, @webofwork.com, @mindbodygreen.com, @cedarville.edu, @upjers.com, @smartdev.vn, or @tripmap.me. It seems pretty strange to be that joining is limited to already having an acount on these. What is the onbording process for other people, and can we get that documented on the main page having to join one of those makes no sense to me.

[ghost]

@mhdawson I believe that shouldn't affect your ability to join, it hasn't for me.

[WaleedAshraf]

Visit nodeslackers.com to register
.

Maybe we can include this ^ here also, like in getting-started guide.

[mhdawson]

@oe so what were the steps you used to join if you did not already have one of those emails?

The page might already have been updated, but now I just see Contact the workspace administrator for an invitation. If the registration flow is to go to the link @WaleedAshraf pasted in then having that shown when you try to login would be good.

My main concern is that if we have a reference here that it is easy and clear how anybody can join.

[mhdawson]

As more context I've already had one person tell me they thought the channel was dead from what they'd seen. When I suggested that was not the case (since we are talking about it here), they looked at it again and sugested it was quite suspect that you would have to get an email from one of those emails listed.

[ljharb]

Can you clarify where you’re seeing that list? I don’t see it for the slack channel, and no such limitation should exist.

[WaleedAshraf]

@ljharb I also saw the same message as @mhdawson, but right now it says "Contact the workspace administrator for an invitation."

I'm not sure between these:

• It has been updated by someone
• It was a bug at the Slack end
• It's not showing because I'm a member now

[Trott]

since we don't have consensus this issue needs to be sent to a vote in both the TSC and CommComm

This is about @Fishrock123's objection only, right? The one that is in their one-and-only comment on this issue six weeks ago. (#49 (review))

There have now been 3 unanswered pings over 6 weeks to see if the objections have been adequately addressed. (#49 (comment), #49 (comment), #49 (comment)).

I may propose an update to README.md to address this kind of thing without a vote. (To be clear, no shame in this not being a priority for someone and/or someone having a lot on their plate. But there's also no need for a vote when the only objection is from someone who is not participating in the consensus-seeking process, even if they have an excellent reason for not participating.)

[Trott]

On the other hand, I think it's fair to say that this has not attracted the attention it deserves in terms of LGTMs vs. -1s from @nodejs/tsc and @nodejs/community-committee, so there, I just @-mentioned them. :-D

[Fishrock123]

To be clear: are the owners of the slack handing it over to us? If not, what purpose does this serve?

I still am not really in favor of it. I think this will probably signal a move to slack and I've already stated in great detail in #53 why I don't think that it is the correct tool / approach.

See the notes from nodejs/TSC#520

[fhinkel]

@hackygolucky, we discussed in today's TSC meeting, nodejs/TSC#520, that we'd need an admin account for the Node Foundation for that slack. Would that be possible?

[ljharb]

@fhinkel it definitely would, and @dshaw is already an admin as well.

Dismissing my own review. Things eventually got set straight I think...Sorry for the noise.

[mhdawson]

I had an action to add comments to capture one of the things I said in the discussion in the TSC meeting today. Here it goes:

1. The slack channel is already active
2. The slack channel admins have agreed to follow our moderation policy
3. While it might be nice if we could have our moderation team do the moderation, we don't have unlimited resources so that's not a possibility (at least that is my understanding)
4. It's worth seeing if we can rely on the moderation team for external resources to moderate in accordance with our policy as it only improves the situation versus the status quo. In these cases, we should support those efforts which and one way we are doing that is the content of this PR.

[benjamingr]

While it might be nice if we could have our moderation team do the moderation, we don't have unlimited resources so that's not a possibility (at least that is my understanding)

As far as I understand several team members are actively engaged in the Node Slack Community (including OP) and are overseeing that this is indeed the case. I think this could be an interesting experiment.

[mhdawson]

Since objections have been removed and there are a good number of approvals, we'll plan to land this in 48hrs unless there are new objections before then.

[mhdawson]

Landed as 7d9a8b1