-
Notifications
You must be signed in to change notification settings - Fork 421
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
RFC: Standardize on one chat platform #2440
Comments
Due to its large community presence, and the fact it checks off most of the selection criteria, my vote would be for Gitter. I'm particularly fond of the fact that it supports SSO with GitHub and has a decent mobile interface. |
Awesome Dylan! Thanks for taking the time to address this issue... I'd be happy to ditch Slack and IRC :) Since I personally have very limited time to dedicate to synchronous chatting, I'd be in favor of anything that's well integrated within Github. So my vote would go to Spectrum or Gitter ;) |
Same for me. 👍 for Gitter |
I like Gitter, but I think the reality of the situation is that nobody is on the chat platforms. Maybe we should bow to that and force everything to go through Github issues or something. |
Yeah, that's definitely a tough issue to solve without team buy-in, which is why I hope that standardizing on one platform will encourage us all to hang out there! That being said, long term, I think the solution would be GitHub Discussions. I don't think that will roll out to us anytime soon though :( I think we've come to a consensus on Gitter, so I'm going to start adding Gitter badges to READMEs and send in a PR to add it to the website. |
We now use Gitter :) Thanks Dylan for your efforts ;) |
I won't be the only one landing here and looking for the link so here it is: https://gitter.im/Kinto/kinto Also, the docs should be updated over there: https://docs.kinto-storage.org/en/latest/community.html |
Thanks for the feedback! I opened #2544 |
Update chat info in community docs (ref #2440)
Currently, the Kinto project uses both Slack and IRC as its live chat platforms. I propose that we migrate to one single platform, and use that as the primary provider for chat. Once selected, we should add a link to the selected platform to all the repos' README files in addition to making it appear prominently on the website.
Some Stats
Just to set a baseline, here's some stats about our Slack and IRC usage over the past 90 days:
So, as you can see, we're not dealing with a great volume of messages. However, what's interesting is that there's been more activity and messages on Slack versus IRC. I think this is a result of the barrier-to-entry that IRC has. Even with the sign-up barrier of Slack, it still beats out IRC in terms of accessibility.
The Ideal Solution
A great candidate would:
In addition to the above, an excellent candidate would:
Candidates
Slack
Advantages
Disadvantages
Gitter
Advantages
Disadvantages
Discord
Advantages
Disadvantages
Matrix
Advantages
Disadvantages
Spectrum
Advantages
Disadvantages
Selection Process
Due to the low volume of messages, it's unlikely that we'd be able to run a useful-enough experiment with each platform. I think the best path forward would be to discuss our preferences here, and hopefully come to a consensus organically. As new points are made, I'm happy to keep this issue up to date so that it reflects the most up-to-date preferences of the community.
I'm not sure what a good selection process would look like, so I'd like to just get the ball rolling by getting thoughts from @leplatrem , @Natim, and @glasserc, which represent the main contributors over the past few months. If a clear winner doesn't emerge after hearing from y'all then we can figure out a more specific selection process.
The text was updated successfully, but these errors were encountered: