I've also heard good things about Discourse and it's open source (written in Ruby).
It's used as a community discussion forum for popular open source projects like: Docker (https://forums.docker.com/) Meteor (https://forums.meteor.com/) OpenMRS (https://talk.openmrs.org/) Ubuntu (http://discourse.ubuntu.com/) And tech companies: New Relic (https://discuss.newrelic.com/) Twitter (https://twittercommunity.com/) There's even a plugin for Slack to post new discussion topics in Discourse to Slack channels: https://github.com/bernd/discourse-slack-plugin On Friday, August 12, 2016 at 10:36:39 AM UTC-7, Azizur Rahman wrote: > > My vote goes for Stack Overflow. Becuase it has most of what you are > asking for. Also from a developer point of view SO is the go-to-place for > technical issues. > > SO has a good governance process in regards to how people become > moderators. API docs (https://api.stackexchange.com/docs) seems > comprehensive, even if you do not create a new site via Area51 proposal we > can get started with tagging question with tags (say 'open-edx') and > questions can be spread over multiple other sites using the same tags. > > I have also seen https://www.discourse.org/ used for community support. > Probably does not have everything but it's one shiny forum. > > Just my two cents. > --- > Azizur > > On Tuesday, 2 August 2016 20:44:00 UTC+1, Shauna Gordon-McKeon wrote: >> >> Hello Open edX community! >> >> The open source team here at edX has been talking a lot recently about >> how we can do a better job of making sure community members have access to >> the resources you need to troubleshoot problems and get your questions >> answered. Right now the most common avenues for getting support are our >> mailing lists and Slack channels, but these tools don’t allow us to easily >> track frequently asked questions or see how often questions are going >> unanswered. >> >> We want to find a better tool so we can better help the community. We’ve >> brainstormed a list of requirements here: >> https://docs.google.com/document/d/1J0P2hNXH7hdyxbqi8OCndNrUoxrOXDAbvIGalG6v7qU/ >> >> Here’s where you come in: we can only see one side of the support >> experience. We don’t know what, from your perspective, the biggest >> problems are and the most appealing solutions might be. So please, feel >> free to suggest additional requirements, and to let us know which of our >> existing requirements are most important to you. You can do so by adding >> to this thread in the edx-code mailing list. >> >> If you’ve got tool suggestions as well, we’d be happy to hear them! Once >> we’ve got our requirements list set, we’re going to evaluate the most >> promising options. >> >> Looking forward to seeing your feedback! >> >> Best, >> Shauna >> > -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/3c9bd40e-2c97-48af-8216-c1babf180cf7%40googlegroups.com.
