How Does Team Discourse Use Discourse?


Originally published at: How Does Team Discourse Use Discourse?

As we claim on our website, we use Discourse as our primary team coordination tool to build… Discourse! That means escaping email silos and minimising the number of disparate communication channels required to manage a fully distributed team. We are able to keep distractions like calls and meetings to a minimum and focus on actual…


holy cow. this is awesome. the idea had crossed my mind to use discourse as a full-bodied business communication and project system… but hearing it from you guys really does make it seem doable.


great insight thanks @HAWK - just shows how flexible it certainly can be if you want it to be!

(Nate Mamman) #4

So, Discourse is essentially the One Ring. Sauron would be proud. :grin: I love how you guys have figured out a way to get rid of all the distractions by building most of the features you need into one app.

(Joe Buhlig) #5

I was thinking about this just last week! I remembered @HAWK saying she was working on it. Thrilled to see it come to life. :wink: Well, done.

(Eric Berry) #6

This is awesome. Thank you very much!

I have a follow up question regarding task management.

Are you tracking commits with tasks for those that have code changes through discourse? Something similar to the way Jira w/ BitBucket or Github works?

I found a couple of plugins and topics that are related:

  • Seems nice if you are/were using Github issues and want to mirror them in Discourse and use Discourse to further the conversation, but not if you don’t want to use Github issues.
  • Looks for mentions in Discourse and then adds links to GH messages.

I realize that this can be done easily by manually pasting a Github/BitBucket commit into Discourse, but I’m curious if there’s something automatic.

Thank you again for the great post!


Hey Eric,
We use Github Linkback but we don’t have anything automated.

(Bas van Leeuwen) #10

Very cool! :slight_smile:
Currently in the process of weaning people of from Hipchat in my org. and this is some very valuable input.

One question: why are you running two different instances? Wouldn’t it be possible to merge your internal one with meta and use subforums for everything?

Is it a matter of convenience? Was it set up before the tooling was ready? Don’t you trust the authentication/security model completely?


A couple of reasons.

Our internal instance sits on a different server so if Meta goes down we don’t lose all our runbooks etc.
It also allows us to have very different email and notification settings which means we’re less likely to miss important things in the noise.

(Bas van Leeuwen) #12

Fair and logical reasons :slight_smile:

That brings up painful memories :scream: (we once stored our emergency customer contact list on the wiki, in the datacenter, where all the customer were hosted…)

(Sam Saffron) #13

Yeah we do too… but we have a replica in digital ocean and an extensive encrypted backup story