Hacker News Reader

1. People don't follow the checklist

2. People don't understand how to fix broken tests

This piece is about is that exactly. Closing those PRs. Not responding all the time. And that being ok.

It can be very hard to find individuals who you can give commit access to `master` for any non-trivial open-source project without having them break the build or introduce serious long-term defects.

Code contribution guides and Continuous Integration systems will only get you so far.

Right...People are the problem. More so managing people. Maintainers are there to develop code and not to manage people. It takes a lot of effort to organize and keep people in check. No checklist will ever do that.