Good article. I work on an open source project and we try to be as friendly as possible. As someone who accepts / denies pull requests, I try to point out any c

Good article. I work on an open source project and we try to be as friendly as possible. As someone who accepts / denies pull requests, I try to point out any code issues to the author in a professional manner and to work with them to get their code into our repository if it is valuable (or if it isn't, explain why without being rude). It's worth taking the time to build that extra good will, in my experience, as they'll often come back with further free work. A little patience saves me time in the long run with free code contributions. I had an opposite experience trying to report an issue to a certain Apache project I won't mention. Gave the exact version of their program in use, all platform information, a sample file with the issue and the exact command to run. Everything to reproduce. I received an incredibly derisive response about "why nobody thinks to include a stack trace because we're not mind readers, duh" and the issue was closed promptly. Another dev re-opened the ticket and actually ran the command with the file to reproduce, but it already soured my experience. Needless to say neither I or my colleagues will ever consider contributing to that project again.