How to make reviewing pull requests a better experience - OpenSource.net
When an Open Source project is first getting started, as a maintainer you’re probably excited to see any community interest in contributing. But as the community grows, it’s typical to feel swamped by incoming pull requests. Even if the volume is manageable, reviewing low-quality pull requests can feel like a drag. And that can lead to putting off community pull request (PR) reviews in favor of other priorities. Even promising work may sit unreviewed for weeks if maintainers aren’t able to review it all.
There is a better way, however. As Open Source maintainers, we ought to continually assess the code-contribution and review processes for our projects, and deliberately work to make them better. In this post, we focus on a specific area of investment that in our experience can pay huge dividends: teaching communication skills.
Zulip is an Open Source team chat application designed for seamless remote work. The Zulip project moves forward by routinely merging contributions to the core product from the community.
