I think that UNIX-y "do one thing" projects kind of solve the problem. It's easy to reject a contribution as being out of scope: "This little program prints out

I think that UNIX-y "do one thing" projects kind of solve the problem. It's easy to reject a contribution as being out of scope: "This little program prints out contents of a file. Your patch that sends it via email is nice, but you should rather make it a separate project built on top of the existing one."