# Choosing a developer chat platform

**URL:** <https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380>\
**Category:** Development\
**Created:** [April 7, 2019, 4:33pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380 "2019-04-07T16:33:29Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![adrian](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/adrian/32/4_2.png) [@adrian](https://discourse.beets.io/u/adrian)\
**Post date:** [April 7, 2019, 4:33pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/1 "2019-04-07T16:33:29Z")

</div>

> [@Forming a beets "core team"](https://discourse.beets.io/t/forming-a-beets-core-team/639/7):
>
> On practical matters I think a communication channel would be a great starting point, whether it’s a separate area here on discourse or something more like IRC or its more modern equivalents.

Yeah, I’ve been thinking about a communication channel as well. Here’s a bit of a confession: I used to use IRC a lot more, but in the era of Slack and its open-source equivalents, I’ve found my patience for IRC’s well-known limitations (even when mediated by a bouncer) have severely decreased. I’d be interested to see how far we can bend this Discourse forum for that purpose, or possibly exploring a more chat-oriented alternative (e.g., Slack itself or [Matrix](https://matrix.org/blog/home/) or [Spectrum](https://spectrum.chat)).

---

<div class="post-metadata">

**Author:** ![arcresu](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/arcresu/32/222_2.png) [@arcresu](https://discourse.beets.io/u/arcresu)\
**Post date:** [April 7, 2019, 11:45pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/2 "2019-04-07T23:45:57Z")

</div>

I never got into IRC myself, I just mentioned it since I saw you (used to?) use it for beets already. I suspect that a Slack-like format will work better than a threaded forum style for a small team. If you don’t mind adopting a new service and there are hosted options that are easy to set up, then anything sounds fine to me! I’m also aware of Gitter but I’ve only really used Mattermost (not really an option for beets though).

---

<div class="post-metadata">

**Author:** ![anotherhowie](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/anotherhowie/32/215_2.png) [@anotherhowie](https://discourse.beets.io/u/anotherhowie)\
**Post date:** [April 12, 2019, 11:51am UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/3 "2019-04-12T11:51:58Z")

</div>

I’m on the edge of a few teams that use Discord, which seems quite nice, and people (well, gamers) often have it already. The Slack client is pretty heavy to leave running all the time (my work one is regularly 1GB+ RAM footprint).

---

<div class="post-metadata">

**Author:** ![arcresu](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/arcresu/32/222_2.png) [@arcresu](https://discourse.beets.io/u/arcresu)\
**Post date:** [April 19, 2019, 7:20am UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/4 "2019-04-19T07:20:57Z")

</div>

Spectrum and Gitter look pretty similar at first glance. Both support signing in via GitHub and seem to be pretty easy to get up and running. Gitter seems to support natural discovery by linking chat rooms to GitHub orgs. Gitter has native clients for all common platforms, but Spectrum is Mac-only. I think to me Gitter is sounding like the best fit so far.

---

<div class="post-metadata">

**Author:** ![adrian](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/adrian/32/4_2.png) [@adrian](https://discourse.beets.io/u/adrian)\
**Post date:** [April 20, 2019, 6:19pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/5 "2019-04-20T18:19:35Z")

</div>

Alright, let’s give that a try! I initialized a public room just to try things out:

> **[beetbox/beets](https://gitter.im/beetbox/beets)**
>
> Where developers come to talk.

---

<div class="post-metadata">

**Author:** ![adrian](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/adrian/32/4_2.png) [@adrian](https://discourse.beets.io/u/adrian)\
**Post date:** [June 28, 2020, 8:39pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/6 "2020-06-28T20:39:39Z")

</div>

> [@Forming a beets "core team"](https://discourse.beets.io/t/forming-a-beets-core-team/639/15):
>
> Hopefully a dev chat room can start to gain some traction and we can get a couple of willing developers 🙂
> 
> Speaking of… I was looking into gitter some more as I hadn’t used it before, and it seems like it [relies on a web-based platform for mobile apps](https://gitter.im/apps) i.e. deprecating their current android/ios apps. May be something to consider if you aren’t hard set on gitter already. I personally like discord, it’s more widespread and has more features, but I can see its propensity towards gaming being offputting… [someone broke down a nice set of pros/cons here](https://github.com/neuecc/UniRx/issues/327#issuecomment-407329488)
> 
> edit: discord also supports [bots for github](https://gist.github.com/jagrosh/5b1761213e33fc5b54ec7f6379034a22) which could be useful
> 
> If you want, I could setup/handle the admin stuff of the discord but obviously have you as a full permissions owner.

That’s too bad about Gitter and their mobile apps! I thought their iOS app was pretty good.

I have never used Discord before, although I use a billion Slack workspaces every day for work stuff and its GitHub integration is awesome. I’m down to give either a try for beets. It seems like one major advantage mentioned in the thread is that Discourse is easier to set up for open signups—but that was in 2018. Looks like [a few options have cropped up now](https://www.quora.com/Is-there-a-way-to-enable-anyone-to-join-a-Slack), although I have not tried any of them.

Does anyone on this thread happen to have strong opinions about chat apps? It does seem like Gitter may not be the thing, but I’m happy to try anything.

---

<div class="post-metadata">

**Author:** ![out-of-range](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/out-of-range/32/428_2.png) [@out-of-range](https://discourse.beets.io/u/out-of-range)\
**Post date:** [June 30, 2020, 12:11pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/7 "2020-06-30T12:11:09Z")

</div>

I think one thing to consider in relation to chat/discussion platforms is sticking with open-source tools (i.e. not using Discord or Slack) because I know use of proprietary platforms can put off possible contributors. Other than Gitter I know of Matrix, RocketChat and Mattermost.

---

<div class="post-metadata">

**Author:** ![jtpavlock](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/jtpavlock/32/443_2.png) [@jtpavlock](https://discourse.beets.io/u/jtpavlock)\
**Post date:** [July 3, 2020, 5:45pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/8 "2020-07-03T17:45:03Z")

</div>

If going for open-source options only, Matrix gets my vote. Lots of different client options and has bridge integrations between slack, irc, discord, etc.

Mattermost, rocket.chat, and I think Matrix too (for certain features) require the ability to self-host as well. Something @adrian may or may not be interested in.

---

<div class="post-metadata">

**Author:** ![out-of-range](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/out-of-range/32/428_2.png) [@out-of-range](https://discourse.beets.io/u/out-of-range)\
**Post date:** [July 3, 2020, 10:28pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/9 "2020-07-03T22:28:19Z")

</div>

Yep I’ve been running a very small matrix server for a while, just for family and friends. Been working great apart from the encryption UX isn’t quite polished yet, but that isn’t an issue for public chats.  
I haven’t used any bridges myself, so I’m not sure how well they work, but I like the idea.

On the other hand, going back to something @adrian said a year ago:

> I’d be interested to see how far we can bend this Discourse forum for that purpose

Is another platform needed?

---

<div class="post-metadata">

**Author:** ![jtpavlock](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/jtpavlock/32/443_2.png) [@jtpavlock](https://discourse.beets.io/u/jtpavlock)\
**Post date:** [July 3, 2020, 11:57pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/10 "2020-07-03T23:57:45Z")

</div>

> [@out-of-range](#):
>
> Is another platform needed?

Good question. In the spirit of playing along…

If the goal is just a place to chat about meta-development related things between the “core team” then you could use [github teams](https://docs.github.com/en/github/building-a-strong-community/about-team-discussions) or an access restricted forum on discourse.

If another goal is to give a place for new or potential contributors to ask questions, they could also just be directed to discourse or the applicable issue or PR.

---

<div class="post-metadata">

**Author:** ![adrian](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/adrian/32/4_2.png) [@adrian](https://discourse.beets.io/u/adrian)\
**Post date:** [July 7, 2020, 1:03pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/11 "2020-07-07T13:03:58Z")

</div>

I have no objections to any particular chat platform, but I do have an objection to being the sysadmin for a self-hosted option. 😃 I kind of think the natural choices are probably Slack, an open-source option if someone steps up to host, or perhaps a private category on this Discourse, if async seems to suffice to everybody.

---

<div class="post-metadata">

**Author:** ![jtpavlock](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/jtpavlock/32/443_2.png) [@jtpavlock](https://discourse.beets.io/u/jtpavlock)\
**Post date:** [July 7, 2020, 5:04pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/12 "2020-07-07T17:04:47Z")

</div>

Perhaps a poll is in order to decide between those?

---

<div class="post-metadata">

**Author:** ![jtpavlock](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/jtpavlock/32/443_2.png) [@jtpavlock](https://discourse.beets.io/u/jtpavlock)\
**Post date:** [July 7, 2020, 5:41pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/13 "2020-07-07T17:41:53Z")

</div>

## What is your preferred developer communication platform?

_Poll ([view on site](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/13))_

- Note I’m not a big fan of a non-maintainer hosted solution, but will add it if needed.

---

<div class="post-metadata">

**Author:** ![jtpavlock](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/jtpavlock/32/443_2.png) [@jtpavlock](https://discourse.beets.io/u/jtpavlock)\
**Post date:** [July 11, 2020, 3:10am UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/14 "2020-07-11T03:10:08Z")

</div>

I will add I think the best use case for a developer chat is just as an informal communication line between the “core-team” (and also contributors). That is the main reason I am preferring slack over a private discourse forum, as I believe it lends itself more to informal chat, coordination, and certain social aspects that allow the team to feel more like a team.

I think any formal or more in-depth discussion regarding development of `beets` belongs in discourse, and obviously any PR or issue specific related discussion belongs on github.

I also looked into this some more, and found some good reads: [1](https://blog.discourse.org/2018/04/effectively-using-discourse-together-with-group-chat/), [2](https://meta.discourse.org/t/discourse-and-slack-or-other-group-chat-apps-like-irc-hipchat-gitter-etc/39630)

---

<div class="post-metadata">

**Author:** ![adrian](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/adrian/32/4_2.png) [@adrian](https://discourse.beets.io/u/adrian)\
**Post date:** [July 11, 2020, 5:53pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/15 "2020-07-11T17:53:48Z")

</div>

Yeah, I tend to agree—there is a more low-overhead, less formal valence to a chat option that makes this a good choice.

I don’t want to prolong the decision-making, but one other option that has been pointed out to me elsewhere as being popular in open-source communities is [Zulip](https://zulipchat.com). It has a free hosted option but is open-source and has a few nifty features missing from other systems. I continue not to have a strong feeling about specific services but it seems like this would at least be preferable to Discord. 😃

---

<div class="post-metadata">

**Author:** ![RollingStar](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/rollingstar/32/728_2.png) [@RollingStar](https://discourse.beets.io/u/RollingStar)\
**Post date:** [July 11, 2020, 6:59pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/16 "2020-07-11T18:59:11Z")

</div>

I’m suspicious of closed-source platforms that don’t have archives visible on Google. Would this be a private forum regardless? If so, I don’t have much preference. I like Discord better than Slack.

---

<div class="post-metadata">

**Author:** ![jtpavlock](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/jtpavlock/32/443_2.png) [@jtpavlock](https://discourse.beets.io/u/jtpavlock)\
**Post date:** [July 11, 2020, 7:03pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/17 "2020-07-11T19:03:05Z")

</div>

> [@adrian](#):
>
> one other option that has been pointed out to me elsewhere as being popular in open-source communities is [Zulip](https://zulipchat.com). It has a free hosted option but is open-source and has a few nifty features missing from other systems

I’ll have to admit, Zulip looks pretty sweet. Does that mean you’re interested in hosting now? 😃

---

<div class="post-metadata">

**Author:** ![jtpavlock](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/jtpavlock/32/443_2.png) [@jtpavlock](https://discourse.beets.io/u/jtpavlock)\
**Post date:** [July 11, 2020, 7:06pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/18 "2020-07-11T19:06:46Z")

</div>

I believe the idea of the chat is to have it open to everyone, but perhaps write access restricted or moderated as far as who/what should go in which chat platform. In a perfect world, there would be a one size fits all solution.

---

<div class="post-metadata">

**Author:** ![adrian](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/adrian/32/4_2.png) [@adrian](https://discourse.beets.io/u/adrian)\
**Post date:** [July 11, 2020, 7:14pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/19 "2020-07-11T19:14:18Z")

</div>

Well, fortunately, Zulip has a free hosted option! We could get started with that and self-host down the line if we really like it.

---

<div class="post-metadata">

**Author:** ![jtpavlock](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/jtpavlock/32/443_2.png) [@jtpavlock](https://discourse.beets.io/u/jtpavlock)\
**Post date:** [July 13, 2020, 8:33pm UTC](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380/20 "2020-07-13T20:33:08Z")

</div>

As an aside, is it possible that the upcoming [github discussions](https://github.blog/2020-05-06-new-from-satellite-2020-github-codespaces-github-discussions-securing-code-in-private-repositories-and-more/) ([example](https://github.com/vercel/next.js/discussions)) could replace these forums? In that case, maybe moving away from discourse for this chat would be the right idea…

[Next page](https://discourse.beets.io/t/choosing-a-developer-chat-platform/1380.md?page=2)