I've set up & moderated a Discourse instance for an open source project before and I had a very good experience with it. However Xavier's right that it's not a great fit for our use case. Discourse lets you pin topics in threads but it doesn't led you pin answers in topics, which prevents us from highlighting the best/most correct/most upvoted among multiple answers. It also doesn't distinguish between "answers" and "accepted answers", which makes it difficult for people to search for unanswered questions to help people with (and makes it difficult for the EdX team to set a goal of "answer x% of questions y days after asked"). Those are just two missing features off the top of my head. I agree though that it's a great tool, and I hope to see more projects using it.
On Mon, Aug 15, 2016 at 5:18 AM, Xavier Antoviaque <[email protected]> wrote: > I agree that I've heard great things about discourse too. That one might > even allow to also replace the MLs althogether, as it's more user-friendly > than mailing-lists, but still allow any type of conversation. I'm not sure > how well it fits the Q&A tool use-case though, there could still be a case > for keeping it separate (Stack Overflow was built on the principle that the > discussion should be secondary to the question and its answer, and that is > part of what makes it so useful). > > -- > Xavier > @OpenCraft <http://opencraft.com/> > Schedule a meeting <https://calendly.com/antoviaque> > > > On Sun, Aug 14, 2016, at 04:39, Nate Aune wrote: > > 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/docume > nt/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 > <https://groups.google.com/d/msgid/edx-code/3c9bd40e-2c97-48af-8216-c1babf180cf7%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- > 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/1471252698.2146274.695494401.6611CA95% > 40webmail.messagingengine.com > <https://groups.google.com/d/msgid/edx-code/1471252698.2146274.695494401.6611CA95%40webmail.messagingengine.com?utm_medium=email&utm_source=footer> > . > -- 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/CAHZjGXtJ8P%3Dx_jW5iK_4uHe_%3DmubrVi4J1Yrfh3y8NEYC54ZFQ%40mail.gmail.com.
