# What about Zulip?

**URL:** https://discuss.python.org/t/what-about-zulip/197
**Category:** Discourse Feedback
**Created:** [October 8, 2018, 11:21pm UTC](https://discuss.python.org/t/what-about-zulip/197 "2018-10-08T23:21:44Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![vstinner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/vstinner/32/15130_2.png) [@vstinner](https://discuss.python.org/u/vstinner)
#### Post date: [October 8, 2018, 11:21pm UTC](https://discuss.python.org/t/what-about-zulip/197/1 "2018-10-08T23:21:44Z")

</div>

Do we plan to keep Discourse+Zulip?

---

<div class="post-metadata">

### Author: ![ammaraskar](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ammaraskar/32/32_2.png) [@ammaraskar](https://discuss.python.org/u/ammaraskar)
#### Post date: [October 8, 2018, 11:38pm UTC](https://discuss.python.org/t/what-about-zulip/197/2 "2018-10-08T23:38:27Z")

</div>

According to

> [@Python-committers is dead, long live discuss.python.org](https://discuss.python.org/t/python-committers-is-dead-long-live-discuss-python-org/30):
>
> Hello committers, since this got pretty long, here’s the tl;dr: we’re at the point where it is hard to make mailing lists work for us; we’re switching to Discourse; it’s better in many ways; go to [https://discuss.python.org/](https://discuss.python.org/) and create your account there; please do not post to python-committers for the remainder of the year to give Discourse a real shot. And now the long version. What’s the issue? During the core sprint in Redmond we discussed how we discuss. The overwhelming feel is that …

Zulip will act as a replacement for IRC whereas discourse is for the mailing lists.

---

<div class="post-metadata">

### Author: ![ambv](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ambv/32/25884_2.png) [@ambv](https://discuss.python.org/u/ambv)
#### Post date: [October 9, 2018, 8:37am UTC](https://discuss.python.org/t/what-about-zulip/197/3 "2018-10-09T08:37:47Z")

</div>

I don’t think dropping Zulip or not needs to be an edict. If people keep using it and it serves a unique role then fine. If Discourse fills it well enough and Zulip stops being used organically, that’s also fine.

---

<div class="post-metadata">

### Author: ![vstinner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/vstinner/32/15130_2.png) [@vstinner](https://discuss.python.org/u/vstinner)
#### Post date: [October 9, 2018, 10:21am UTC](https://discuss.python.org/t/what-about-zulip/197/4 "2018-10-09T10:21:13Z")

</div>

> [@ammaraskar](#):
>
> Zulip will act as a replacement for IRC whereas discourse is for the mailing lists.

I dislike Zulip. Me and others still use IRC 🙂 You cannot fully replace a communication channel, only promote it enough to make sure that the critical mass moves to the new shiny one 🙂

---

<div class="post-metadata">

### Author: ![vstinner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/vstinner/32/15130_2.png) [@vstinner](https://discuss.python.org/u/vstinner)
#### Post date: [October 9, 2018, 10:21am UTC](https://discuss.python.org/t/what-about-zulip/197/5 "2018-10-09T10:21:51Z")

</div>

> [@ambv](#):
>
> If Discourse fills it well enough and Zulip stops being used organically, that’s also fine.

Ok. We will see. I agree that there is no need to decide it right now. But I had to ask the question.

---

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/erlend_sh/32/147_2.png) [@erlend\_sh](https://discuss.python.org/u/erlend_sh)
#### Post date: [October 14, 2018, 10:33am UTC](https://discuss.python.org/t/what-about-zulip/197/6 "2018-10-14T10:33:00Z")

</div>

Another Discourse team member here 👋

Just for the record, we think of chat & forum platforms as highly complementary. One does not replace the other:

> **[Effectively using Discourse together with group chat](https://blog.discourse.org/2018/04/effectively-using-discourse-together-with-group-chat/)**
>
> Most modern businesses and organisations today are using some kind of team chat application. The usual suspects are Slack, HipChat, Discord, Mattermost, Rocket Chat, Riot, and Gitter, to name a few. While chat is immediate and primarily synchronous,...

---

<div class="post-metadata">

### Author: ![esbeeb](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/esbeeb/32/550_2.png) [@esbeeb](https://discuss.python.org/u/esbeeb)
#### Post date: [February 9, 2019, 5:00pm UTC](https://discuss.python.org/t/what-about-zulip/197/7 "2019-02-09T17:00:06Z")

</div>

I just installed Zulip yesterday [from a Docker container](https://github.com/zulip/docker-zulip) (for my own testing purposes).

I love it so far, but be warned it’s CPU hungry. If a giant community were to all pile onto Zulip, that had better be a beefy Zulip server (or server **s** , say maybe splitting out the DB onto a second server).

---

<div class="post-metadata">

### Author: ![Mariatta](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/mariatta/32/30581_2.png) [@Mariatta](https://discuss.python.org/u/Mariatta)
#### Post date: [February 9, 2019, 8:57pm UTC](https://discuss.python.org/t/what-about-zulip/197/8 "2019-02-09T20:57:15Z")

</div>

The good thing is we’re using the hosted zulip, (not running our own servers) so I don’t think we need to worry about the infrastructure part.
