Working on a Public Forum for Chat

[bnb]

Having a centralized, official community forum for instant chat. This is something that would be helpful long-term for communication and for monitoring.

• Slack - historically limited, based on free tier.
  • Solution: IRC bot for listening to history and logging.
• Discord: free, open registration (signup with link)
• Others?

Ref: #250

[julianduque]

I would be interested in helping in this area

[yasinaydinnet]

What about http://www.discourse.org/ ?

[bnb]

@yasinaydin I like Discourse a lot - only hard part is that it either needs to be hosted and maintained, or purchased. Would love to hear any ideas on how we can make this easily sustainable for the project.

[vdeturckheim]

Could we try Slack + http://slackarchive.io/ ? Or should we develop our own bot ?

[julianduque]

The only limitation of Slack is logging, but is the same for IRC, we can have our own bot storing logs to http://logs.nodejs.org/channels

[fforres]

Is gitter not al option?
https://gitter.im/

[vdeturckheim]

We have a gitter room, however there is no (AFAIK) moderation possible there.

[bnoordhuis]

Not that I ever visit it but isn't that what #node.js is for? Yet another channel when IRC, SO, nodejs/help and the mailing list already exist just leads to more fragmentation.

[MylesBorins]

two things to keep in mind here

first is moderation. how will this channel be moderated and who will be moderating

second is buy in. there is an established chat on irc for both support and development. I think you will find push back from a good chunk of the core team with moving to a closed platform like slack.

the biggest question I have is what is the goal here? to me I think we should work on better supporting the currently managed channels and increasing visibility.

[bnb]

I believe this has been discussed at length in the Community Committee (ref: nodejs/community-committee#11) and can be closed. If the issue does need further discussion, please don't hesitate to create a new issue or re-open this one with the context of nodejs/community-committee#11 in mind.