One of the best things about working at Discourse is that we practice what we preach: we run our 100+ employee company entirely on our own platform. From chatting with coworkers and planning features to tracking bugs, looking up documentation, and even scheduling time off, everything happens in one place. I genuinely believe our culture and success as a 100% remote company stems from using our own collaboration tool, and I want to share how we use Discourse to build Discourse so you can create a similar setup for your team.
I have a few little questions about differences between what you each emphasized. Are you all still using the Discourse Assign plugin to manage task assignments? Do you still use topic timers to help manage topic status once tasks are complete? Are you still using Discourse as a private email support portal? If you’ve moved away from these strategies, would you be willing to sketch your reasoning?
I was surprised to read about the incident response: does that mean you actually open at least three topics for the same incident? It seems to follow the Product/Todo split though.
A follow-up question maybe. Since you’re hosting quite a lot of free software project forums, do you ever share runbooks with them, or get inspired by some of them?