Also I want to point out that I'm totally fine with quickly closing tickets with no reproduction details or without enough information. Bad tickets should get closed if they're bad, especially if there's a template in place that the person has ignored. I would say that if 10 tickets from different people are getting filed from a specific area it may be worth looking at even if all the tickets are badly specified. In general a closed ticket with an explanation is so much more valuable over time than the alternative.
> if you want to do that it would actually be better to just send that clear message in a more direct manner -- GitHub just doesn't have good tools around this yet.
Doesn't it have the ultimate tool: If you want to send the message that you don't give a shit about bug reports, just don't activate any bug-tracking tool? (Or is it mandatory?)
No, it doesn't. If you want send that message clearly, you should state in your readme: "We don't give a fuck about bug reports, especially if they're valid and relevant.".
Yes, it says that the product is popular enough that hundreds of people feel the need to post feature requests with notes like “how is this not fixed yet, it should be five minutes of work, it's a deal-breaker issue for me, I'm migrating to Chrome if this is not fixed!!!”
Also, this comment wasn't about Firefox specifically! Just about projects that do this in general.
This is bad and borderline dishonest practice, and it’s surprising that it’s allowed to be widespread. I wrote an edgy post about it which didn’t go far on HN but it’s a sentiment I don’t see repeated much (without the edge of course).
Filed issues say something about your product or it’s documentation/UX. Bots that autoclose muddy that signal.