> Not trying to be tongue in cheek but isn't it easier for everyone just to reject the bad PRs like that? Sure, especially if your (meta) goal is minimizing in

> Not trying to be tongue in cheek but isn't it easier for everyone just to reject the bad PRs like that? Sure, especially if your (meta) goal is minimizing individual maintainer effort. But if you want instead to maximize maintainer and contributor return on effort (counting both the originator and the polisher as contributors), a different approach may be called for. Maintainers "just" need to figure out for themselves not just how much work they are willing to put in, but what sort of work, and what work (if any) they are able and willing to delegate or offload onto others. For a maintainer who isn't willing or able to do the work of polishing contributions or handholding potential contributors, and doesn't have anyone they trust that is willing or able to do that work, rejecting most PRs (and even issues, for that matter) outright can be an entirely valid approach. Open source success and sustainability don't look the same for every project or for every maintainer.