Choosing a developer chat platform

So @adrian and I talked this over, and we decided to go away from discourse for several reasons.

A big one being we thought it would blur the line too much between what deserves to be in a private forum vs publicly on discourse. We want any discussion regarding development to be public.

That said, there are a couple of goals we’d like to accomplish with the “developer chat”:

  1. Getting to know the team members
  2. Talking logistical things such as who’s going to be in charge of a given release, etc.
  3. Any informal chatter that doesn’t deserve it’s own discourse post and doesn’t belong on github.

All of these we thought would be better served outside of discourse, so we decided to spin up a zulip instance as it seems like a nice middle ground between discourse and slack, and is also open-source. We are going to test that out for now, and if it seems like things aren’t working or there may be better options, we will re-consider.

We realize this was not the result of the poll, so we didn’t take this decision lightly. If there are any concerns, feel free to reach out to us.

Now for the fun part:

Joining the chat

The chat is going to be limited to members of beetbox (the beets organization).

If you are currently a member

Just send myself or @adrian a DM and we’ll invite you.

If you are not currently a member

We’d like to keep the bar for entry somewhat low to hopefully let beets grow a little bit. In essence, you just have to make any meaningful contribution and we’ll invite you to the team. Most of the time, this is just going to be seeing a pull request all the way through without us having to step in and finish it off. If this sounds like you already, just send @adrian a DM and he’ll invite you to the team and the chat.

4 Likes