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
Investigate switching from Gitter to another chat option #13039
Comments
I could see it working very well for team chats. I have it open all day already, and it works well for other teams I'm on. My primary concern would be about the community chatroom. With Gitter, anyone can sign in with GitHub OAuth, but having to sign up for a hypothetical ESLint Slack channel might introduce friction. @kaicataldo has the Babel team noticed that being an issue? |
I haven’t personally noticed any issues, but I wonder if others on the Babel team might be willing to chime in. @hzoo @nicolo-ribaudo Slack is a much nicer experience all around, and while signing up for a separate account is a little more overhead, I don’t think it’s a significant one. If anything, it might increase the quality of conversations we can have. Do we know how we want to handle the limit for the free tier? Does Slack so open source plans/pricing? |
We have never received any complaint about the need to create an account, and no one ever asked for help about how to do it. However, this is something that it's hard to receive feedback about. We currently have the plus plan (https://babeljs.slack.com/plans/plus), but I don't know if they give it to all the OSS communities or if it's something custom for us. Probably @hzoo knows. |
If we leverage the Open JS Foundation Slack, they already have a way to self-invite to the organization. |
I agree Gitter has been going downhill. They now support threading but it wasn't very well implemented, and it's hard to read items in a thread (especially on mobile). I'm 👍 to at least trying Slack. Just in case Slack accessibility proves to be an issue, it may be worth emphasizing that we also have a mailing list and other options for getting support. |
The friction for creating a Slack account can be a barrier. There are groups I was never able to join because their slack auto-invite didn't work properly. Also, if you think the Gitter threads are bad (they are), you won't be much more pleased with Slack threads. The big advantage of Slack is that the clients are much more reliable than Gitter (though you'll have to figure out the best way to handle the GitHub integrations since just dumping issues and PR's into the main channel will choke conversation. That's one thing that Gitter does well for GitHub projects). |
Another alternative is Discord. They’ve embraced being a platform for open source projects, and it looks like a number of well-established open source communities are using them. It would also solve the issue of worrying about payments/message limits, as well as being a low barrier for entry (though it is another service to create an account with). |
Oh cool, Discord looks like a good option. I’m going to play around with it. FWIW, we could setup Slack channels on the OJSF account and not need to worry about payments or message limits. |
This sounds like a good way to test out Slack! My only concern with that is that it might be difficult for people to find, given the larger org and all the channels. |
Even I would back the discord option. they do have a rich voice channel features. Their interface is much cleaner than slack and gitter . |
I and @kaicataldo have been playing with Discord and it does seem like a good option. The one thing we still need to figure out is how to get a transcript of a text channel so we can publish TSC meeting proceedings easily. |
I dont have much solid experience with this case but discord support bots so I think that can fix it. not sure though, never tried creating one! |
I haven’t found an existing tool that does this, but it definitely seems doable. Discord’s API has an endpoint for obtaining messages in a given channel. I wonder if the simplest way for us to implement an automated version of this would be to have a GitHub Action that triggers when a PR is merged in We could also shoot for something much lower tech to begin with and have a generator that one of us can run locally and commit the results. I’d be happy to work on this after I finish my current task. |
Oh cool. My gut tells me having a tool we can run manually is the best starting point (we can always look at integrating with GitHub Actions later) |
That sounds good to me! |
Found in my travels: |
Ah, that looks great 👍 Nice that they have a Docker image to use and everything. Once we can verify that works, I think we could be ready to make the switch. Thoughts? |
I agree. Maybe we should start by moving the private team chats over first to try it out? |
TSC Summary TSC Question |
We decided on the 2020-03-26 meeting to start by moving our private team chats to Discord. |
Now that we have the Discord server set up, should we move the general chat over? This would involve updating all of our docs, too. |
Sounds good to me! Want to also note that I'd love to have a place where we can write down guidelines/a code of conduct for the chat. I've seen other Discord servers solve this by creating a locked |
Please don't use discord :-/ the UX is terrible. Slack or IRC is much more preferable to me. |
@kaicataldo do you consider that a blocker? If not, can you open a separate issue to discuss? @ljharb we’ve been testing out Discord the past couple weeks and it’s been a pleasure to use, especially compared to Gitter. It’s a better fit for us than Slack or IRC, so I hope you’ll join us. |
@nzakas Sorry, I should have been clearer. I do consider this a blocker before advertising the public channels. I think it’s important to set these expectations from the get-go so that everyone can feel safe and we are able to moderate effectively. I’ll come up with some language and share it with the team. In the meantime, I think it’s fine to start getting those rooms set up! |
Sounds good. 👍 Is there a reason we can’t just link to our current code of conduct? |
I’d be 👍🏼 for using that to begin with and iterating as we go along. I just want to make sure it’s visible to folks who join. |
Looks like the old CoC links don’t forward to the new one. All of our links are broken. :( Here’s the current location: I think we should try to stick with that rather than trying to add on later. It seems pretty comprehensive. |
I actually hadn’t realized that changed and so hadn’t seen the new one. It does look quite comprehensive. SGTM! |
@nzakas I maintain DiscordChatExporter and also use eslint. Let me know if you guys have questions or need help. |
@Tyrrrz thanks! I think the biggest question is if there's some way to automate exporting chat text? And if there's a way to filter what is exported (just one day of text instead of everything that's ever been typed)? |
There is a CLI (also containerized), so you can use it for automation scenarios. The simplest thing is probably create a cron job that runs an export every once in a while, but I'm not sure what do you have in mind. There's some info on automating exports on the wiki: https://github.com/Tyrrrz/DiscordChatExporter/wiki/Troubleshooting#how-can-i-set-DCE-to-export-automatically-at-certain-times Also, the wiki has loads of helpful information (kudos to @renanyudi).
Yes, you can limit the export to a certain time period, down to milliseconds if you want to. |
Awesome, thanks I’ll dig into wiki. I think ideally we want to automatically run an export through a GitHub action the day after each TSC meeting (or triggered by a pull request merge...still TBD) |
Both should be fairly easy to do 👍 |
I think at this point it makes sense to make the move to shut down our Gitter and move everything to Discord. One big thing is we will need to update our docs to mention Discord everywhere Gitter is currently mentioned. |
Documentation updates are complete on the website and in this repo. Leaving this open until we complete the automation piece for TSC meetings. |
For people who want to stick with Gitter or IRC, perhaps a chat bridge could be set up. |
Closing this since we now have the ability to generate TSC Meeting transcripts in Discord. |
We currently use Gitter for a lot things in the ESLint project:
While it has worked reasonably well, recently the quality of Gitter has dropped considerably. Our most recent TSC meeting saw members needing to refresh the entire page just to see what other people have written. The mobile app doesn't work particularly well, either. It's time to consider if the lost productivity is enough to warrant switching to Slack.
(It's worth noting that the Open JS Foundation uses Slack and would be able to help us set it up.)
We'd like some feedback from the community on this. Are there pros and cons for switching to Slack?
The text was updated successfully, but these errors were encountered: