Open gdt opened 1 year ago
@gdt Thanks for the feedback! I hear you, stale bot can certainly be annoying. However, whether or not it's harmful I think depends on it's use with the project, which depends on the project maintainers. I personally use it to help gauge community interest in specific issues, especially those that are typically lower priority or require bandwidth that I don't have. For example, I know which issues you're continually interested in based on you keeping them alive :). It's also a reminder to me about specific issues, which I will occasionally update with new information that I obtained since the issue was opened (and mark it not stale).
Also, I personally don't consider a closed issue to be permanently closed - they can always be re-opened. If it's closed by stalebot, that means that it's gone 400 days without comment (200 for warning and another 200 then close). To me that's a reasonable gauge that there isn't anyone interested in that feature anymore. And if someone misses the window to comment, again, we will just re-open.
That all being said, I'd certainly welcome additional feedback from others on stalebot.
My perception is that I can't reopen an issue; only maintainers can. I guess the big problem is that there are incomplete bug reports that nobody cares about and ones that we all agree are valid and it's just going to take ~forever to deal with them. But it's your repo, your effort and your call.
tl;dr: The stale bot is fundamentally a wrong thing. It should be de-configured.