Library/Case studies/The Apache Software Foundation/Kafka
Kafka
One Apache project, Kafka, as its own developers wrote about it on the dev list and in JIRA in 2019, added to the brain Leo already had from the foundation's board minutes.
Source: Apache Kafka's public dev mailing list and JIRA
ArticleWhat Leo saw at Kafka, 1. One more channel, added to a brain Leo already hadLeo knew Apache Kafka from four board reports a year: 11 lines, 6 processes, no flows. We added the project's dev list and JIRA for 2019. In 69 minutes it held 837 lines, 28 processes and 25 flows, and had corrected what the board picture got wrong.Engineering · How Leo works · 5 min readArticleWhat Leo saw at Kafka, 2. The red build nobody ownedIn 2019 Kafka's developers filed 193 tickets for tests that fail for no reason, and the board reports never mentioned it. Leo drew the work from twelve developers' mail and JIRA. In 2024 Kafka adopted a quarantine for flaky tests, one of the ways Leo had laid out.Engineering · 5 min readArticleWhat Leo saw at Kafka, 3. The release manager's playbook, from the release managersKafka had a written release process in 2019. Leo drew the one release managers actually ran, from their own mail and JIRA, including a step about flaky tests that Kafka's release page only wrote down in January 2024.Engineering · Operations · 5 min read
Nothing here says that yet. Try fewer words, or another word for it.