Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

readme: add link to unofficial discord #20508

Closed
wants to merge 1 commit into from

Conversation

devsnek
Copy link
Member

@devsnek devsnek commented May 4, 2018

Checklist

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label May 4, 2018
@vsemozhetbyt vsemozhetbyt added the meta Issues and PRs related to the general management of the project. label May 4, 2018
@devsnek devsnek requested a review from bnb May 4, 2018 02:30
@jasnell
Copy link
Member

jasnell commented May 4, 2018

/cc @nodejs/moderation ... any concerns with this outside of the usual It's Not Covered By Our Moderation Policy :-)

Copy link
Member

@Trott Trott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM although I'd prefer we have a self-evident reason for the ordering of the four unofficial resources.

@refack
Copy link
Contributor

refack commented May 4, 2018

"how is this night different from all other nights"
i.e. how active it this comm? How well behaved and/or valuable to new users?
/CC @nodejs/community-committee

@vcarl
Copy link

vcarl commented May 4, 2018

Hello! I just wanted to comment that me and some folks from Reactiflux spun up a Discord server for node called Nodeiflux a few weeks before this one was created. https://discord.gg/vUsrbjd I'd actually been toying with the idea of making a PR like this myself when I heard that this server was created.

We're slightly larger and slightly more active, especially if you exclude node core contributors. I've been moderating Reactiflux for several years and was one of the people who coordinated the switch from Slack, so I'm very familiar with keeping a large community healthy. I've reached out to @devsnek and @bnb in Discord and on Twitter but didn't really get much response, which is part of why I'm leaving this comment.

I'd love to avoid fragmenting the community, and would love to chat about how to get the most benefit for the community at large.

@jemjam
Copy link

jemjam commented May 4, 2018

I know there's a common misconception that Discord is "just for gaming communities", or that folks will somehow use it less than Slack (that is already default open on many desktops). However, I get a lot of value out of being on Reactiflux (and appreciate that the history isn't lost quickly). I didn't realize a node version was also out there, but I've just joined myself.

While fragmentation could be a concern, knowing there is already a sizeable subset of a community there, it doesn't hurt for people to know about it?

I might suggest that you add this after the node-slackers item though.

@devsnek
Copy link
Member Author

devsnek commented May 4, 2018

@vcarl I think there are some important differences, namely that the one created by bnb explicitly follows our CoC, moderation policy, etc and has node org staff as discord staff.

it sounds to me like you want one of these servers to disappear and you don't want it to be yours, which is understandable I'm sure you've put lots of work into it but I don't think it's inherently better because it has more people. I'm fine with both existing.

@vcarl
Copy link

vcarl commented May 4, 2018

I want a productive chatroom that is helps people find answers to their questions and welcomes developers of all skill levels. Thus far I feel that Nodeiflux better accomplishes that goal. No, we don't explicitly adhere to the moderation policy or CoC, but I think we have similar aims and a good track record in Reactiflux. I'd love to talk about ways we could make improvements if there are ways we're not living up to the CoC.

@jemjam
Copy link

jemjam commented May 4, 2018

I should note that my joining your Discord isn't necessarily an endorsement yet. We had a couple of CommComm discussions about whether or not Node Slackers was appropriate to link to, being the unofficial nature of it also. I think we might need some time to review.

There is always a concern about whether or not to point users at a community where we're unable to speak to (or inform) their moderation policies.

@nickserv
Copy link

nickserv commented May 4, 2018

Disclaimer: I've been in both servers since they were created, but I have moderation privilege in Nodeiflux and I am more active in it.

I think the best option right now is to link to both Discords and let them grow organically, especially since they have been less active since being created, unless the Node team considers them too young or unofficial in this state. Both servers have unique advantages over each other, like Nodeiflux's more frequent question and answer content or @devsnek's server's channel structure and presence of Node core contributors. They could potentially merge or replace each other in the future, though I think it's too early to make a decision at this point.

As far as ordering goes, I noticed that Node Slackers was added to the end of the list and I think we should maintain the chronological order. I'd be happy to make a PR linking both Nodeiflux and Node.js if this gets enough upvotes.

@bnb
Copy link
Contributor

bnb commented May 4, 2018

For context, I partially created the non-official Node.js discord to resolve a long-standing discussion around external official communities. I'd be entirely happy to work with or combine with the Nodeiflux discord, especially since their community is (as noted by the creator above) more active and has a team that's native and used to the Discord platform.

I'm not very opinionated around this beyond our basic community guidelines, and am happy to enable community-first solutions.

jasnell pushed a commit that referenced this pull request May 23, 2018
PR-URL: #20508
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: James M Snell <jasnell@gmail.com>
@jasnell
Copy link
Member

jasnell commented May 23, 2018

Landed in 474e94d

@jasnell jasnell closed this May 23, 2018
@devsnek devsnek deleted the discord-link-readme branch May 24, 2018 20:20
targos pushed a commit that referenced this pull request May 25, 2018
PR-URL: #20508
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: James M Snell <jasnell@gmail.com>
@MylesBorins MylesBorins mentioned this pull request May 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations. meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.