I can’t run it on my x200 (neither can run Element). It’s too complex to have a source build on Nixpkgs. Its closure is massive for a chat app:
nix path-info --closure-size -h $(which zulip)
/nix/store/flhwx7b94xq21f8pvvbgzinl6gvarxkj-zulip-5.10.3 1.8G
See My resignation from freenode and a gazillion of posts wrote during this period.
Here’s the discourse thread where part of the migration has been discussed: Join us on Matrix at #nix:nixos.org (Migrating from Freenode)
To me, this is inherent with chats. They’re not bug trackers. The noise to signal edit: signal to noise (
) ratio is pretty low, they’re impossible to follow for some people (like me).
I’m using Zulip for some other orgs, from my perspective, it’s a good chat system (again, I personally greatly prefer it to Matrix and IRC), but a terrible bug tracker replacement.
You’re asking for a change requiring people to get familiar with yet another chat platform and install some new software running on their computer to interact with the NixOS folks. This is as much innovation as the migration to Matrix originally was.
Overall, I feel like you and I have different needs when it comes to chats. That’s fair. I’m not saying your needs are not relevant, I’m voicing my opinion and personal use case here 
I’m sure I’m not the only one in this situation.
Anyways, my opinion is voiced, I won’t derail this in a endless bike-shedding conversation. Overall, I’d prefer not changing the chat channel. But if we end up moving to Zulip, I’ll move there like I moved to Matrix on the first place. OFC, after ranting a bit 