Hello everybody,
I've created a Asciidoctor team on slack, let me know if you want to be invite. https://asciidoctor.slack.com/ and the password is very complicated: "asciidoctor". Cheers, Guillaume |
Actually the following link we allow you to auto sign-up
https://asciidoctor.signup.team/ |
Administrator
|
Guillaume, I appreciate you putting in the effort to setup the channel on Slack. My preference, however, is to use the channel on Gitter {1}, which we've been using for a while. I'm willing to reconsider that commitment if there's something that Slack gives us that Gitter doesn't. Generally, I prefer to use this list or the issue tracker to discuss topics because those mediums encourage asynchronous communication. I've always felt very stressed out by chat (a feeling that Jason Fried captures well in this post {2}). Putting my opinions aside, if others in the community find Gitter or Slack worthwhile for realtime communication, then I certainly support it being used. I just encourage anyone using realtime chat to bring topics to the list or issue tracker so they are captured for everyone to review. I'm interested to hear what others think about $subject. Feel free to chime in. Helpful? Not helpful? Cheers, -Dan On Tue, Mar 29, 2016 at 9:40 AM, Guillaume [via Asciidoctor :: Discussion] <[hidden email]> wrote: Actually the following link we allow you to auto sign-up Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen |
I didn't know about Gitter.
On the feature support, do you have anything specific in mind ? An interesting point about Slack, which doesn't seem to exist in Gitter, is the ability to create topic rooms rather putting everything in the main rooms therefore it, of course, has benefits and drawbacks. |
Administrator
|
On Tue, Mar 29, 2016 at 2:20 PM, Guillaume [via Asciidoctor :: Discussion] <[hidden email]> wrote: An interesting point about Slack, which doesn't seem to exist in Gitter, is the ability to create topic rooms rather putting everything in the main rooms therefore it, of course, has benefits and drawbacks. True. I kind of see that as useful for scheduled discussions, much in the same way as you grab a meeting room in an office. If the topic room stays open indefinitely, I think it leads to the stress that Jason Fried talks about. |
Administrator
|
In reply to this post by Guillaume
On Tue, Mar 29, 2016 at 2:20 PM, Guillaume [via Asciidoctor :: Discussion] <[hidden email]> wrote: I didn't know about Gitter. Thanks to @mogztter, the Gitter link is now in the footer of asciidoctor.org (a recent change). -Dan |
In reply to this post by mojavelinux
El Tuesday 29 March 2016, escribió:
> I appreciate you putting in the effort to setup the channel on Slack. My > preference, however, is to use the channel on Gitter {1}, which we've been > using for a while. I'm willing to reconsider that commitment if there's > something that Slack gives us that Gitter doesn't. I wasn't aware of that channel at all. Actually, I've been in the #asciidoctor channel on freenode.net since a while, and it's mostly silent. If you need the web-based, permanently archived chat, and would like to have more than one channel, I suggest you to give a look to https://matrix.org. It's also a way to promote an open source project instead. ;) -- Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2 http://barnacity.net/ | http://disperso.net |
Administrator
|
On Fri, Apr 1, 2016 at 2:22 PM, suy [via Asciidoctor :: Discussion] <[hidden email]> wrote:
I kind of gave up on the IRC channel because it's a) too geeky/low-level for a general audience and b) doesn't support things like highlighted code snippets (as Gitter does) and c) doesn't have integration with GitHub (again, like Gitter does). I generally feel like Gitter is more comfortable and convenient. |
I use IRC, but between Slack and Gitter my vote is for Gitter. |
Wondering how this has fared after 4 years.
Gitter is good enough but hasn't added much to the table. And lately that the activity in Gitter has been growing, I miss many Slack features like "proper" threaded conversations or being able to add an emoji answer to a comment. The latest seems silly but it's a great way to say things like "I see that", "you are right", "same as X person" without adding lines to the conversation. Note I am biased since I use Slack for work and other communities, in my computers and phone. |
Administrator
|
Abel, You're absolutely right that we are outgrowing Gitter. It simply lacks the tools to manage multiple, busy conversations, which makes them hard to follow and even harder to catch up on what you missed. The discussion on the table is to evaluate Zulip (https://zulipchat.com/). We like it because it is open source (https://github.com/zulip) and favored by a number of communities who have selected it. I'm looking for an analysis that would help us make the decision to switch to it. I'm staunchly opposed to Slack. I've used it to participate in a number of communities and I just don't like it. The main problem I have with it is that unlike Gitter (and GitHub, etc), it partitions communities into different websites that require different accounts. I already have enough accounts. I don't need more. I also think it's too cluttered. While Gitter lacks some important functionality like quality threads, Slack seems to do too much. And it becomes a mess. Slack is also a walled garden with history limits that we'd likely hit over time. For me, Slack is a non-starter. I don't want to bring it into this community. I'm hopeful that Zulip will provide the space we are looking for. Best Regards, -Dan On Wed, Jul 29, 2020 at 1:44 PM abelsromero [via Asciidoctor :: Discussion] <[hidden email]> wrote: Wondering how this has fared after 4 years. -- Dan Allen (he, him, his) | @mojavelinux | https://twitter.com/mojavelinux |
Free forum by Nabble | Edit this page |