I am investigating using Discourse for Kubernetes. This twitter conversation caught my eye, specifically the bit about totally migrating off of Slack.
We are not (yet) investigating moving off of Slack, but I am in the middle of writing a proposal to add a community discourse forum, and the fact that you closed down your slack is very interesting so I thought I would ask how it’s going and if you have any feedback or insight in how it’s been going without Slack so far, thanks!
We’re only a couple of weeks in, so it’s still pretty fresh, but early signs are really good - Feedback has been near unanimously positive, and the format feels significantly more useful. One of the most welcome things is how mature Discourse is as a product, which makes it a real pleasure to work with. There’s so much stuff just built in automatically, eg. Every so often Discourse will detect that a post might be spam, send admins a notification, and then the UI to review it includes a button to delete the post, user, and ban their email + IP all with 1 click.
Things like this make running a forum super easy and pleasurable, as opposed to time consuming and painful. We used to have a hand-rolled forum, and it was dealing with stuff like this on a day to day basis that just made it a disaster to manage.
TLDR: Love it so far! Here are some stats if you’re curious
Only one which is a little deceiving is pageviews. I don’t know how Discourse reports that, but it’s definitely not accurate and vastly overestimated.
Any thoughts on the user support bits? One of the concerns we’re having is that we’d have another support avenue on top of stackoverflow, but from what I can tell so far it seems most discourse-using OSS projects tend to use both instead of strictly focusing on one or the other.
We looked at Stackoverflow. First we looked at Stack Exchange - for which I made an application for Ghost on 3 separate occasions, and each time it got deleted “as spam” within a few days. Ridiculous system.
Then we looked at regular Stackoverflow and just using a tag in there. Two main problems with that: First, no control over organising it, or anything else really. So you’re just kind of at the mercy of how SO works, which is… not great. Secondly, and I appreciate that different people will have different experiences here, but we found the SO ‘community’ to be pretty poisonous in most interactions. Not really something we were enthusiastic about.
The distinction in my mind is fairly clear: Use SO if you want to talk to the wider world of developers for help. Go to an OSS project’s own forum if you want to actually reach that community of people and not everyone else.
Again though, just my experience. I’m sure different approaches are suited to different communities