[infinispan-dev] Replacing IRC

Dan Berindei dan.berindei at gmail.com
Wed Oct 18 11:24:37 EDT 2017


Discourse [1] is more of a forum replacement than a chat, but I'd
still like to suggest it. I hate it how in IRC you never know when a
user has finished their idea and it's safe to start replying, and
typing notifications don't really work for me :)

Dan

[1]: https://meta.discourse.org/



On Wed, Oct 18, 2017 at 10:52 AM, Sebastian Laskawiec
<slaskawi at redhat.com> wrote:
> +1 to Slack. All JUG communities I know are using it. It is also worth to
> mention that Slack was also adopted by Kubernetes folks.
>
> On Mon, Oct 16, 2017 at 4:17 PM Katia Aresti <karesti at redhat.com> wrote:
>>
>> Hi all,
>>
>> I'm a strong adopter of slack and I really like it. I've used it since it
>> came out with Duchess (we started with an internal use for the team, and we
>> have a community slack now with more that 150 people there that is little by
>> little replacing our google group). I've use it in different communities,
>> startups and big company client's teams. As far as I know, other open-source
>> projects have already adopted it successfully.
>> What is cool about it is that joining any team and switching from one team
>> to another is very easy. If people want to join the community, and they are
>> already using slack, is very easy.
>>
>> I agree with Sanne, being able to use it from the smartphone is important
>> and could be considered as a high requirement. I use slack on my phone, and
>> it helps quit a lot. Most of the time I use it from my laptop, but there are
>> cases where mobile has really helped us (specially in Duchess France slack).
>> I use the native slack client on my mac and works very well.
>>
>> I haven't tested Stride or Gitter.
>>
>> Katia
>>
>>
>>
>>
>>
>> On Mon, Oct 16, 2017 at 11:29 AM, Tristan Tarrant <ttarrant at redhat.com>
>> wrote:
>>>
>>> HipChat is being replaced by Stride.
>>> I have dimissed HipChat in the past because it did not allow for a
>>> single account to be shared across multiple groups. I believe this will
>>> be solved by Stride.
>>>
>>> Tristan
>>>
>>> On 10/16/17 11:16 AM, Wolf Fink wrote:
>>> > Why not use Hipchat as EAP/Wildfly to prevent from too many different
>>> > platforms ?
>>> >
>>> > On Mon, Oct 16, 2017 at 10:27 AM, Tristan Tarrant <ttarrant at redhat.com
>>> > <mailto:ttarrant at redhat.com>> wrote:
>>> >
>>> >     Dear all,
>>> >
>>> >     last week we discussed the possibility of abandoning IRC in favour
>>> > of a
>>> >     more modern alternative.
>>> >
>>> >     Hard requirements:
>>> >     - free (as in beer)
>>> >     - hosted (we don't want to maintain it ourselves)
>>> >     - multi-platform client: native (Linux, MacOS, Windows), browser
>>> >     - persistent logs
>>> >     - distinction between channel operators and normal users
>>> >     - guest access (without the need for registration)
>>> >     - integration with Jira for issue lookup
>>> >     - integration with GitHub for PR lookup
>>> >     - IRC bridge (so that users can connect with an IRC client)
>>> >     - ability to export data in case we want to move somewhere else
>>> >     - on-the-fly room creation for mini-teams
>>> >
>>> >     Optionals:
>>> >     - Free (as in freedom)
>>> >     - offline notifications (i.e. see if I was notified while away)
>>> >     - mobile client: Android and iOS
>>> >     - proper native client (as most Electron clients are quite fat)
>>> >     - chat logs accessible without a client (it is acceptable if this
>>> > is
>>> >     achieved via a bot)
>>> >     - integration with Jenkins for CI status
>>> >     - XMPP bridge (so that users can connect with an XMPP client)
>>> >
>>> >     Not needed:
>>> >     - file sharing, audio/video
>>> >
>>> >     Here is a list of candidates:
>>> >     - IRC (i.e. no change)
>>> >     - Slack
>>> >     - Stride (Atlassian's upcoming replacement for HipChat)
>>> >     - Matrix (Matrix.org, unfortunately with funding issues)
>>> >     - Gitter
>>> >     - Discord
>>> >     - Rocket.chat (unfortunately hosting is paid)
>>> >
>>> >     If you have any other suggestions/recommendations, they are more
>>> > than
>>> >     welcome.
>>> >
>>> >     Tristan
>>> >
>>> >     --
>>> >     Tristan Tarrant
>>> >     Infinispan Lead
>>> >     JBoss, a division of Red Hat
>>> >     _______________________________________________
>>> >     infinispan-dev mailing list
>>> >     infinispan-dev at lists.jboss.org
>>> > <mailto:infinispan-dev at lists.jboss.org>
>>> >     https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>> >     <https://lists.jboss.org/mailman/listinfo/infinispan-dev>
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > infinispan-dev mailing list
>>> > infinispan-dev at lists.jboss.org
>>> > https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>> >
>>>
>>> --
>>> Tristan Tarrant
>>> Infinispan Lead
>>> JBoss, a division of Red Hat
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev


More information about the infinispan-dev mailing list