Yes. I entirely agree with you and second your suggestion.
I had the same experience a couple of times as well. I stopped contributing issues in the last year or so because I became frustrated with the maintainers decision to close issues automatically. This might have started after I pushed for more active work on the open issues. I am not sure it went in the right direction. It’s great that we have now less than 2000 issues on Github (that means 1000 less than about a year ago). Not sure if it is the right approach to make the repo seem tidier, closing issues that people haven’t had time to work on, yet. If this is done automatically, it discourages to open new issues after people realize that their issues are just closed automatically. Why should I spend the time to write a detailed description of a bug or so, if the issue is automatically closed because nobody worked on it for several months. I get it that this is a ressource-constrained environment and we might have a lot of open issues. Just closing issues automatically is not a good solution in my opinion.
2 Likes