# 用 Discourse 替换 Slack
**URL:** https://meta.discourse.org/t/replacing-slack-by-discourse/121104
**Category:** Community Building
**Created:** [2019年六月23日 12:58 UTC](https://meta.discourse.org/t/replacing-slack-by-discourse/121104 "2019-06-23T12:58:57Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@PackElend](https://meta.discourse.org/u/PackElend)
#### Post date: [2019年六月23日 12:58 UTC](https://meta.discourse.org/t/replacing-slack-by-discourse/121104/1 "2019-06-23T12:58:57Z")
Hi there,
in our organisation’s community, we use mainly Slack, GoogleDocs and other tools as they are freely available but we are hitting now their limits of their freemium models and reasons discussed in [Discourse and Slack (or other group chat apps like IRC, HipChat, Gitter, etc)](https://meta.discourse.org/t/discourse-and-slack-or-other-group-chat-apps-like-irc-hipchat-gitter-etc/39630), so we came to the decision that we have to replace them soon.
The core team can’t take care of it, as they are occupied by the work on the platform whos beta will go online soon. This gap is supposed to be bridge by the help of the community.
In the first step we would evaluate software (wherever possible FOSS) and write to vendors for non-profit options.
In order to do so, we need to set up an email archive so that communication can continue if someone can’t join in. So I thought about [mailman](https://www.list.org/) or [others (see List Server and Version)](http://n8.nabble.com/archive-your-mailing-list.html) plus [nabble](https://www.nabble.com/).
Mailing list needs to be simple to reach everyone where necessary without having to think about who needs to be in CC. An archive must be created so that new ones can read in as needed, or work can be transferred quickly, or the actions of the movement can be followed loosely. But the archive must be protected.
In the course of the research, I was referred to [Discourse as a private email support portal](https://meta.discourse.org/t/discourse-as-a-private-email-support-portal/34444), so I continued my research in this forum. As discourse comes with a [load of plug-ins](https://meta.discourse.org/c/plugin), I getting more and more the impression that it could replace Slack quite nicely, as it is mainly used for posting in channels, referring to external websites and documents.
Basically, we would like to be able to send Emails out of discourse and assign the resulting task(s) to community members.
Moreover, we would like to establish room for discussion as we have now by means of the channels like
That can be well covered by categories and tags. Besides this, there is for
Email
1. [Discourse as a private email support portal](https://meta.discourse.org/t/discourse-as-a-private-email-support-portal/34444)
2. [How to Use Discourse as a Private Support/Ticket System](https://meta.discourse.org/t/how-to-use-discourse-as-a-private-support-ticket-system/72268)
Tasks
1. [Task manager within Discourse?](https://meta.discourse.org/t/task-manager-within-discourse/68691)
2. [Using discourse as ticket system, so no balls are dropped woman\_juggling](https://meta.discourse.org/t/using-discourse-as-ticket-system-so-no-balls-are-dropped-woman-juggling/82698)
3. [Tickets Plugin tickets](https://meta.discourse.org/t/tickets-plugin/97914)
Feed
1. [Favorites - select your favorite categories](https://meta.discourse.org/t/favorites-select-your-favorite-categories/81959)
2. [Let users configure categories for /Latest](https://meta.discourse.org/t/let-users-configure-categories-for-latest/101314)
3. [A more social Discourse layout](https://meta.discourse.org/t/a-more-social-discourse-layout/89759)
4. [Customizable Homepage or Discussion Feed?](https://meta.discourse.org/t/customizable-homepage-or-discussion-feed/97487)
I would like to know how stable it is.
It is reliable and reasonable option to cover a workflow as below:
1. Initiate conversation with person/entity xyz
→ Create discussion in discourse
→ discourse sends email to xyz
→ email should show senders as Name.Surename@community…
2. answered will added to the discussion
→ allowing xyz to enter the discussion on our discourse would be appreciated
3. resulting task(s)
→ assign to community members
→ add to calender (meeting, due date …)
→ all tasks/tickets need to visible to all community members
Thank you, any input is highly appreciated
Stefan
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [2019年六月25日 16:43 UTC](https://meta.discourse.org/t/replacing-slack-by-discourse/121104/3 "2019-06-25T16:43:47Z")
Stefan,
> 1. [Discourse as a private email support portal](https://meta.discourse.org/t/discourse-as-a-private-email-support-portal/34444)
It’s an amazing replacement for email groups (if that’s what you mean)
Tasks
> 1. [Task manager within Discourse?](https://meta.discourse.org/t/task-manager-within-discourse/68691)
Can be done already with stable plugin
> 1. [Using discourse as ticket system, so no balls are dropped woman\_juggling](https://meta.discourse.org/t/using-discourse-as-ticket-system-so-no-balls-are-dropped-woman-juggling/82698)
Can be done already with stable plugin
> 1. [Tickets Plugin tickets](https://meta.discourse.org/t/tickets-plugin/97914)
Yes this one 🙂
Feed
> 1. [Favorites - select your favorite categories](https://meta.discourse.org/t/favorites-select-your-favorite-categories/81959)
I’m personally working on this plugin which is presently broken. Would appreciate some additional pledges to deliver this to the community.
> 1. [Let users configure categories for /Latest](https://meta.discourse.org/t/let-users-configure-categories-for-latest/101314)
See favourites above, same thing? (Sorry no time to dig on this right now)
1. [A more social Discourse layout](https://meta.discourse.org/t/a-more-social-discourse-layout/89759)
Consider the plugin I support (with @angus) - [Topic List Previews.](https://meta.discourse.org/t/topic-list-previews/101646)
> I would like to know how stable it is.
_Very_. In two years of running Discourse sites I’ve had \< 3 outages over 3 sites which didn’t last for more than 30 mins each, and those were due to an error on my part. Rock Solid.
```plaintext
It is reliable and reasonable option to cover a workflow as below:
1. Initiate conversation with person/entity xyz
-> Create discussion in discourse
-> discourse sends email to xyz
-> email should show senders as Name.Surename@community…
2. answered will added to the discussion
-> allowing xyz to enter the discussion on our discourse would be appreciated
3. resulting task(s)
-> assign to community members
-> add to calender (meeting, due date …)
-> all tasks/tickets need to visible to all community members
```
I’m pretty sure this can all be done right now.
My suggestion is … _try it_
It is _very_ low risk to spin up a sandbox in a VPS and start configuring it the way you want things to work.
Your greatest cost will be time (but getting a basic working instance up takes surprisingly little time - less than an hour?)
You can then evaluate it yourself and then with your team and stakeholders and check off all of your combined requirements.
Imho - go for it! Given what you have written I don’t see significant show stoppers, least of all for a feasibility analysis.
There is huge platform, community and dev support here and if you are well funded getting anything customised will be no problem at all.
Robert
---
### Author:  [@PackElend](https://meta.discourse.org/u/PackElend)
#### Post date: [2019年六月26日 17:29 UTC](https://meta.discourse.org/t/replacing-slack-by-discourse/121104/4 "2019-06-26T17:29:42Z")
> [@merefield](#):
>
> Imho - go for it! Given what you have written I don’t see significant show stoppers, least of all for a feasibility analysis.
thx for that statement, that is all that I needed 😌. In addition, all your comments above helping us a lot!
> [@merefield](#):
>
> It is _very_ low risk to spin up a sandbox in a VPS and start configuring it the way you want things to work.
that’s now the plan 🙂