-
Notifications
You must be signed in to change notification settings - Fork 108
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
Create Gitter Space #216
Comments
I created https://gitter.im/briantopping/argonaut in case anyone is interested in this. We can all move to the root Argonaut gitter when it gets created. |
There is an IRC channel where a bunch of us tend to be, I'm amenable to creating a Gitter space, just dubious of there being a bunch of places to talk about Argonaut. Splitting down attention and numbers even further. |
Yah good point. I forgot about the IRC, the last time I tried it, the response to my question was lost because it came after I logged off. |
I say in favor of evolution you guys should honestly consider moving towards something like Gitter versus IRC, or setup some syndication between the two services. Every single Scala top-level project worth its salt is on Gitter, and I find it hugely beneficial to pop in and out of those channels to talk with the core devs and contributors. |
@tylerjharden That somewhat assumes Gitter is better to be fair! :) I don't think we'll move away from IRC, but as the core maintainer it means it's another thing vying for my attention! |
I do see your point there and I was rather shortsighted as I made that comment. Probably best to stick with whatever is most productive for you as core, and anyone from outside the core would rightfully adapt to said workflow if they wanted to involve themselves. (seanparsons: edited by me because Outlook) |
I've created the Gitter room. |
To achieve what practical benefit?
|
@tonymorris Easier for those who don't use IRC to ask questions, I'm personally using the Gitter IRC bridge however. |
Could we get a Gitter space for users to help each other out? I think it's an easy first step to understanding common use cases such that the documentation in #89 could evolve.
The text was updated successfully, but these errors were encountered: