Hacker News Reader

I resist telling open source developers how to run their projects, because I am one myself, and get annoyed when other people do that to me.

But oof, if I were a user who spent some non-trivial time filing an issue & helping troubleshoot, or working on a fix or new feature and submitting a pull request, I'd be feeling pretty discouraged right now.

View on HN

Most users spend trivial time filling issues however. Most bug reports are crap.

Well parent wrote about a user who took his time and put in effort.

No one wants to loose those so it is sad for both sides.

In my opinion, if a bug report is crap, it is perfectly acceptable to politely say so with a canned response and then close the issue a week later if better information is not forthcoming. Declaring 'issue bankruptcy' shows that you do not care about your users time and tells me that I should not trust your project.

The issues are closed, not lost. They can probably ask them again later if they are still pertinent

Reply on news.ycombinator.com