Library/Case studies/Zulip

Zulip

The open source team chat, built in the open by a small core team and hundreds of volunteers. Leo read 20 people's public chat, issues and pull requests from early 2023, and none of Zulip's documentation, then set what it wrote beside the pages Zulip wrote later.

Source: chat.zulip.org's public channels and the zulip/zulip repository on GitHub

3 entries here

ArticleWhat Leo saw at Zulip, 1. A review playbook from nothing, in 73 minutesZulip used review labels on its pull requests for three years before anyone wrote down what they meant. Leo read 20 people's chat and GitHub, and nothing else, and wrote the playbook in 73 minutes for US$29.75, with some things the written one still leaves out.Engineering · How Leo works · 7 min read ArticleWhat Leo saw at Zulip, 2. How a report in chat becomes a tracked issueZulip's bug reports have lived in a chat channel since 2015. The page on turning them into GitHub issues was written in June 2023, and its author called it quite a project. Leo wrote one from 20 people's messages in 73 minutes.Engineering · Customer support · 7 min read ArticleWhat Leo saw at Zulip, 3. The playbook keeps up when the work changesWhen Zulip's summer contributors arrived in 2023, pull request review grew three new stages. Leo's page grew them too, from what people did, in 37 minutes for US$17. Nobody edited it.Engineering · How Leo works · 5 min read