3 ms·
It has nothing to do with the popularity of the repository, really, but more with the quality of the issues. >>> I would hate an automatic reply for filling an
by gedrap 11y ago
It has nothing to do with the popularity of the repository, really, but more with the quality of the issues.
>>> I would hate an automatic reply for filling an issue for a small library or such.
If the issue is lets say not reproducible because of lack of information provided, does it really matter if the response was typed out by hand? The response would be the same, give or take a couple of words.
- talles 11y agoThe maintainer could see that, due to the nature of the issue, maybe the user OS would matter. Or maybe there's another version on the horizon that changes completely the functionally in topic. A hand crafted reply asking some curated questions/suggestions is not the same from an automatic "not enough information". It's not about typing, it's about making a conversation.
- Bahamut 11y agoBut this is a massive waste of time. For example, this past weekend I triaged over 600 issues on a project that sees a lot of maintainer churn (ui-select for Angular) - the low quality issues is a lot of the problem, and maintainers waste a lot of mental energy when they have to focus on a lot of issues where the reporter didn't do the basic level of due diligence. If this feature was released beforehand, it probably would have saved me a couple of hours :( .
- talles 11y ago600 issues is a lot, I consider that a popular repository. I'm not against the feature, I think it's (for big repos) a necessary evil.