# \[RFC\] Solving Slack's lack of history

**URL:** https://discourse.julialang.org/t/rfc-solving-slacks-lack-of-history/33360
**Category:** Community
**Tags:** proposal
**Created:** [January 14, 2020, 7:59pm UTC](https://discourse.julialang.org/t/rfc-solving-slacks-lack-of-history/33360 "2020-01-14T19:59:39Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![yakir12](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/yakir12/32/297_2.png) [@yakir12](https://discourse.julialang.org/u/yakir12)
#### Post date: [January 15, 2020, 10:51am UTC](https://discourse.julialang.org/t/rfc-solving-slacks-lack-of-history/33360/11 "2020-01-15T10:51:46Z")

</div>

> [@swissr](#):
>
> I don’t see the proprietary Slack app as a good place to store such messages.

I must have been unclear: the messages (with the questions and answers that are worth saving) are gonna be auto packed into a PR to a FAQ page of the package/s that these Q&A pertain to. As in, the `doc` folder in the package online (git- hub/lab or whatnot). So this app will just pipe the info to the package/s’ documentation. It won’t retain anything.

> [@swissr](#):
>
> With Zulip, Julia can apply for open source hosting and wouldn’t need to host themself. From Hacker News I get the impression that Zulip is well liked (but as said no personal experience). Maybe it needs a little bit more time, but I see it as a potential nice Julia chat environment.

If Zulip (or any other alternative) is significantly better then great. I was under the impression though that agreeing on an alternative and moving there was difficult (telling from the [last survey](https://discourse.julialang.org/t/slack-the-chat-tool-we-love-to-hate/14021)).

BTW, with migration I only mean moving the users there, not the history.

---

_[View the full topic](https://discourse.julialang.org/t/rfc-solving-slacks-lack-of-history/33360)._