In our organization we are looking for Stack exchange / Reddit / HN like clone that can used for "discussion threads on some technical topics". Any suggestions. We use Teams chat but UI for this purpose is not useful.
I tried that. Containerized setup require running a custom script of theirs using root. The Docker image is a monolith running multiple servers and database within it. Those are a dealbreaker for many sysadmins, unluckily.
I explored this a bit and found there is a threshold of "too many tools" where people won't follow things on yet another thing that sends them notifications.
I think the magic number is 4: email, chat, wiki, tickets - we don't do much email so more like 3. The problem is none of those are good at longer technical discussions. With chat, threads beyond a day or so in the past are clunky to revive and follow. Wiki is better at finalized docs, tickets are short lived and any technical discussion should be settled by the time someone is working an item.
I route all notifications into email. And I don't install apps. But most tools have a link in their notification email and a click takes me into the WebUI.
Teams I work with use GDocs for editing group knowledge things, then export to Runbook.
Are you looking for something hosted by another organization? I'd say just use the old version of Reddit from when it was still open source as long as you're willing to self-host (https://github.com/reddit-archive/reddit/wiki/Install-guide). I believe that is what Less Wrong originally did. The features that Reddit has added since don't seem useful to me anyway.
For a Stack Exchange-alike, the ROS project hosts one at https://answers.ros.org which is powered by Askbot (https://askbot.com/), which says it is an open source Django app, but I didn’t see the code at a quick glance.
Readit News
The largest public instance of it that I know of is codidact.com; codidact.org is the sponsoring organization.
https://github.com/codidact/qpixel
https://www.discourse.org/
I think the magic number is 4: email, chat, wiki, tickets - we don't do much email so more like 3. The problem is none of those are good at longer technical discussions. With chat, threads beyond a day or so in the past are clunky to revive and follow. Wiki is better at finalized docs, tickets are short lived and any technical discussion should be settled by the time someone is working an item.
Really curious if others have found solutions.
Teams I work with use GDocs for editing group knowledge things, then export to Runbook.