Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove stalebot #5073

Closed
jamesgeddes opened this issue May 11, 2024 · 1 comment
Closed

Remove stalebot #5073

jamesgeddes opened this issue May 11, 2024 · 1 comment
Labels

Comments

@jamesgeddes
Copy link

jamesgeddes commented May 11, 2024

Describe the issue you are experiencing

Stalebot is bad. Let's remove it. There is no shame in having many open issues.

@agners
Copy link
Member

agners commented May 13, 2024

Stalebot is bad. Let's remove it. There is no shame in having many open issues.

Well, not entirely agreeing with this rant, e.g.

Let me offer you a different way of thinking about issues: a place for motivated users to collaborate on narrowing down the problem and planning a potential fix

I agree to think about issues that way! But how does marking stale prevent users from discussing and collaborating? I think the screenshot shows that conversation is limited to contributors immediately after it received the stale label/gets closed. That is that particular implementation of stale bot. In our implementation you can continue to collaborate once marked stale. And please feel free to continue discuss and collaborate on stale issues! Ping if you feel it went stale but shouldn't. I do monitor comments, and remove the stale label and add the pinned label, which makes them not go stale forever, if appropriate.

That said, we do lock issues after a longer period as well. Mainly to prevent folks from reviving long dead issues with a simple "me too" comment. If the same issue really appears on the latest version, it is much better for us to get a new, full report with all the logs and system information. This new issue should have a link to the old issue saying it looks similar to that older issue. Such reports have much more context, and can even help us to find a pattern by comparing the additional system information provided in the new, full report.

There are very good reasons to mark things as stale. Sometimes it is third party services which were temporarily down which caused issue (e.g. #4987 might have been such a case). Or people had a very specific setup and ultimately moved on. Sometimes the bug got fixed by some other change, but the developer didn't realize (and hence did not close) and the author did also not come back to close the issue. We also have many issues where I asked for more clarification where folks just did not respond. What is the value of keeping such an issue open forever?

With stale bot, open issues are also the ones we can consider as alive.

@agners agners closed this as not planned Won't fix, can't repro, duplicate, stale May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants