You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would people be interested if I set up a slack group for jstransformers? I think it mgiht be useful for some slightly more ad-hoc discussion around the project. It would also be somewhere we could send notifications of failed builds (only failed master builds, I don't see any point in notifying on failed branch builds).
P.S. I'm looking to get a bit more actively involved in this project and plan to carve out at least an hour per fortnight to spend on maintaining it.
The text was updated successfully, but these errors were encountered:
Uses your GitHub login, so there's no additional login to keep track of.
Integration with GitHub out of the box.
Doesn't require a weird invite app to make a public chatroom
Unlimited chat history for free, unlike Slack
BTW, not affiliated with Gitter in any way, just have used it on other projects and like it for open-source project chats. Slack is a bit more full-featured for large teams, channel management, threads, etc. but for the volume I'd expect from this project, Gitter will work great.
@RyanZim My experience of Gitter is that it almost always ends up not being used. I won't be logged in to it because I don't use it for work. It doesn't have anywhere near as good a system for notifications, channels, threads etc. as slack has. I've also done all the work to integrate build flows etc. into slack, and could just copy-paste those in to our CI workflows. Setting up the equivalent for gitter would require setup from scratch.
I'm also primarily thinking this would be a place for core contributors to hang out, so I'm not too worried if it's a little clunky for other people to join.
Would people be interested if I set up a slack group for jstransformers? I think it mgiht be useful for some slightly more ad-hoc discussion around the project. It would also be somewhere we could send notifications of failed builds (only failed master builds, I don't see any point in notifying on failed branch builds).
P.S. I'm looking to get a bit more actively involved in this project and plan to carve out at least an hour per fortnight to spend on maintaining it.
The text was updated successfully, but these errors were encountered: