This article convinced me away from Slack and towards Gitter. We love Slack at
Deep 6, but it really is “entreprisey”
https://www.quora.com/What-are-the-pros-and-cons-of-Gitter-vs-Slack
<https://www.quora.com/What-are-the-pros-and-cons-of-Gitter-vs-Slack>
~~~~~
May All Your Sequences Converge
> On Jan 22, 2018, at 5:00 PM, Brad Chamberlain <[email protected]> wrote:
>
>
> Hi guys --
>
> We've been (slowly) having discussions that are _somewhat_ similar to this
> within the team at Cray, motivated in part by a desire to move away from
> SourceForge mailing lists (and in part for want of something better). You can
> see some indications of this discussion (and chime in on it for aspects
> related to mailing list replacements) here:
>
> https://github.com/chapel-lang/chapel/issues/6440
>
> You're also welcome to open an issue with a more specific IRC replacement
> theme (e.g., "create a stateful alternative to IRC"). At a high level I'll
> say that I'm open to this, though also nervous about switching technologies
> too frequently (and/or continually growing the number of forums we need to
> monitor).
>
>
>> I would also be happy to utilize such a "3rd" forum if available
>> for asking questions & topics that do not fit very well with
>> StackOverflow and Github issue (e.g., asking practical experience,
>> code design, performance tips, etc..).
>
> I think, today, the IRC channels and Chapel mailing lists are that third (and
> fourth) forum, for better or worse.
>
>
>> Though I have no experience of Gitter/Slack/IRC,
>> one forum I felt convenient is Discourse because it
>> provides various features including bookmarking.
>> https://www.discourse.org/
>
> We looked into Discourse a bit (and haven't ruled it out yet). I'd say the
> two biggest negatives are a likely increase in hosting cost for our website
> and the learning curve/effort to establish it (set it up and organize it).
> There'd also be some learning curve to utilizing it (for those of us who
> haven't), though I think this is less significant.
>
>
> I'm not very familiar with Gitter (i.e., we didn't explore it as a mailing
> list alternative). Would it be accurate to say that, like a chatroom, it is
> a single logical stream of chats (i.e., no thread hierarchy or tree-based
> structure?). I.e., it'd be much more of an IRC replacement / addition than a
> mailing list replacement? Does it story history, permit tagging users and
> notifications to them when they come back online?
>
> If so, chat.stackexchange.com seems to provide a similar service (IRC with
> history, persistence, and notifications even when you're offline), and has
> the benefit of being integrated with StackOverflow. (I also happen to be
> familiar with it, so can imagine what using it is like better than Gitter...
> not that I'm ruling it out, just curious for a comparison between the two).
>
> I'm similarly unfamiliar with Slack, though I have a positive impression of
> it. That said, I don't have a sense of where it falls in this space and how
> it would be as an IRC and/or mailing list replacement.
>
> Thanks,
> -Brad
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Chapel-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/chapel-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Chapel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-users
