News for hackers. Stuff that matters.

A comment on How to get an open source community to be interested in helping you.

Re:How to get an open source community to be interested in h... by sverhagen on Tuesday October 24, 2017 @05:29AM (#15540331)
"I'm going to have to strip off the extraneous bits until I'm staring the problem in the face. Why should I spend my time doing that, when you—the person asking for help—could be?"

Oh, the dozens and dozens of times I solved my own problem while making it reproducible, before actually filing the report!

[ Parent | on HN ]
Re:How to get an open source community to be interested in h... by npsimons on Tuesday October 24, 2017 @10:29AM (#15541789)
Much like Rubber Ducking: https://en.wikipedia.org/wiki/Rubber_duck_debugging
[ Parent | on HN ]
Re:How to get an open source community to be interested in h... by Doxin on Thursday October 26, 2017 @08:28AM (#15558219)
On the other hand, If I as a user run into some trivial bug and go "hey feature XYZ is obviously broken" I get rather annoyed at repo maintainers who think I am then somehow required to debug the problem for them.
[ Parent | on HN ]
Re:How to get an open source community to be interested in h... by nerdponx on Tuesday October 24, 2017 @07:30PM (#15546106)
This, or the report template itself suggests troubleshooting steps that I hadn't considered, and solved my problem that way.
[ Parent | on HN ]