# Discourse - Modern forum software for your community

**URL:** <https://discourse.codeforamerica.org/t/discourse-modern-forum-software-for-your-community/64>\
**Category:** Discourse\
**Created:** [May 25, 2018, 10:33pm UTC](https://discourse.codeforamerica.org/t/discourse-modern-forum-software-for-your-community/64 "2018-05-25T22:33:17Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![chris](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/chris/32/10_2.png) [@chris](https://discourse.codeforamerica.org/u/chris)\
**Post date:** [August 4, 2020, 8:02pm UTC](https://discourse.codeforamerica.org/t/discourse-modern-forum-software-for-your-community/64/20 "2020-08-04T20:02:51Z")

</div>

> [@samir.khan](#):
>
> What about the other way around? Starting a conversation in Slack and then when you think it deserves more in-depth input, create a topic in discourse and link it there. Any experience with that?

The Discourse plugin we have installed in Slack facilitates this, but it’s not really helpful. Here are a couple examples of Discourse threads that spun out from Slack convos:

> [@Stripe & OpenCollective Discussion](https://discourse.codeforamerica.org/t/stripe-opencollective-discussion/246):
>
> Continuation of slack discussion: [https://cfa.slack.com/archives/C026E1G02/p1533662702000056](https://cfa.slack.com/archives/C026E1G02/p1533662702000056) Stripe is coming up with an API that lets orgs create credit cards on the fly. Talking about better, seamless ways to raise funds for brigades, simplify reimbursement process.

> [@Survey Design Resources](https://discourse.codeforamerica.org/t/survey-design-resources/445):
>
> Capturing a Slack conversation. Reply in this thread if you have more survey design resources! @nickkauf[Mar 20th at 8:38 AM](https://cfa.slack.com/archives/C026E1G02/p1553096333422400) any resources on good survey design? From @mhorowski : [tinyurl.com/surveyCFAhandout](http://tinyurl.com/surveyCFAhandout) Validated survey questions on hundreds of topics: [https://ipip.ori.org/newIndexofScaleLabels.htm](https://ipip.ori.org/newIndexofScaleLabels.htm)[tinyurl.com/surveyCFAslides](http://tinyurl.com/surveyCFAslides) From Andrew Nelson: [“Research design: qualitative, quantitative, and mixed methods approaches” (chapter 8.1)](http://www.researchgate.net%2Ffile.PostFileLoader.html%3Fid%3D55eb95f16307d984de8b4584%26assetKey%3DAS%253A273846907670528%25401442301598571)[“Keep Online Surveys Short”](https://www.nngroup.com/articles/keep-online-surveys-short/)[“A Quant…](https://www.jstor.org/stable/3151410)

> [@Notes from Summit 2018 town hall](https://discourse.codeforamerica.org/t/notes-from-summit-2018-town-hall/126):
>
> [Originally posted in Slack by @tdooner](https://cfa.slack.com/archives/C5ER7B9MK/p1527897135000146) Things to improve for next year: Nick (btv): recordings of breakouts Sabrah: accessibility of venue Melinda (Pittsburgh): use a Google doc for documentation Barry (SF): challenging the distancing from shaping policy - move more into activism Harlan : get more lawmakers here Michelle (redwood City) : have breakouts for city planners and attorneys, get technologists on those panels around key issues get professional credits for attendance (Dave G from Open…

I think what’s important for these to be successful is that someone take ownership of creating a quality topic that sums up the Slack conversation, rather than just pasting a transcript. Slack is scattered thinking and chatting, and just pasting that into Discourse doesn’t turn it into discoverable+digestable knowledge. Of the above, I think the first is a poor example and the second two are better examples. It’s kind of akin to “reporting out” from a group brainstorming session

---

_[View the full topic](https://discourse.codeforamerica.org/t/discourse-modern-forum-software-for-your-community/64)._