<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>turquoisevar</author><text>Wouldn’t it be more reasonable for projects with few maintainers, or even run solo, to have the individuals who reported a bug to each spend 10-15 minutes to validate if the issue still exists instead of the sole maintainer having to spend days if not weeks to do the validation?&lt;p&gt;Especially considering that the reporter is likely better attuned to observing the bug if it’s a bit more fickle or complex than the maintainer who may or may not be able to reproduce it on their end to begin with?&lt;p&gt;This might shift a bit when there’s a bigger team involved or when it’s a companion project to a commercial service.&lt;p&gt;What I tend to see with many (F)OSS projects is that very few are willing to roll up their sleeves while simultaneously spending significant amount of time to make it known how essential the project is to them, making demands and giving copious suggestions.&lt;p&gt;The vast majority just create new issues to make their wishlist known and&amp;#x2F;or supply a very vague bug report.&lt;p&gt;A subset of them might bother to submit a decent bug report and that’s about the extent their willingness to contribute goes.&lt;p&gt;Personally I don’t have the character to maintain a project simply due to not having the will to handle most of the comments I often see in a diplomatic manner.&lt;p&gt;That said, I do always try to track down the cause of an issue and submit a PR to fix the issue I’m reporting in an effort to do my part.</text><parent_chain><item><author>erik_seaberg</author><text>As jwz put it&lt;p&gt;&amp;gt; This is, I think, the most common way for my bug reports to open source software projects to ever become closed. I report bugs; they go unread for a year, sometimes two; and then (surprise!) that module is rewritten from scratch—and the new maintainer can’t be bothered to check whether his new version has actually solved any of the known problems that existed in the previous version.</text></item></parent_chain></comment><story><title>Lodash just declared issue bankruptcy and closed every issue and open PR</title><url>https://twitter.com/danielcroe/status/1703127430523703432</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>neilv</author><text>And a variation on that: the issue was reported against one major release, but a new major release (just incremental changes, not rewrite) is coming out, so close all issues against the old release, because the problem &lt;i&gt;might&lt;/i&gt; no longer exist.</text><parent_chain><item><author>erik_seaberg</author><text>As jwz put it&lt;p&gt;&amp;gt; This is, I think, the most common way for my bug reports to open source software projects to ever become closed. I report bugs; they go unread for a year, sometimes two; and then (surprise!) that module is rewritten from scratch—and the new maintainer can’t be bothered to check whether his new version has actually solved any of the known problems that existed in the previous version.</text></item></parent_chain></comment><story><title>Lodash just declared issue bankruptcy and closed every issue and open PR</title><url>https://twitter.com/danielcroe/status/1703127430523703432</url></story>