As a phrase, this is often more of a conversation killer rather than encouragement for collaboration.
The delivery method of this popular phrase is paramount, and the audience needs to be genuinely considered when we say “patches welcome” to those that come forth with recommendations for our products.
Let’s use an example
Let’s say I have a popular plugin, and a user (not a developer) comes to me with a feature request. I may have feelings about their request – I may “know” that that request wouldn’t work, and tell them so. When the user comes back and says, “well why can’t it do this [miraculous thing] by default?” Our too frequent response of “patches welcome” isn’t very welcoming.
This phrase is easy to say when someone encounters us with a difficult problem to solve. I’d argue that sometimes we use this phrase in areas where the feedback is much inline with where we see our own weaknesses in our product. But that’s unfortunate.
Creating avenues for feedback and collaboration takes effort
It’s really hard to provide an avenue for simple and frictionless feedback. It takes work. I certainly know that I crave feedback on my writing and methods of delivering content, but creating ways to receive good feedback takes considerable effort in itself. I’d need to have non-intrusive but noticeable forms and surveys to receive it. I’d have to analyze and filter the feedback. Then I’d have to respond. And finally I may implement some of the changes.
But this process is important, and one I intend to do better at than my basically invisible contact form. Especially with products and services that we sell. Any feedback we can get from real users is extremely valuable, positive or negative (but probably even more so when negative).
One of the primary things I hear from product makers is they don’t know who (as in what type of person) is using their product and they often don’t know how they are using it. Those that bring feedback help us solve these mysteries.
What is a patch, even?
“Patches welcome” delivered to someone that isn’t a developer is in itself a barrier. Many users of our plugins, that are perfectly capable of providing outstanding feedback, probably don’t even know what a patch is, much less how to make one.
When we receive feedback (good or bad), our first and immediate response should be a big, “Thank you!” Second, we should consider our audience.
Ain’t nobody got time for that
Even if the person offering feedback is a developer, they may be doing as much as they can time-wise just in offering the initial feedback.
