I just received my first ever warning of a stale issue from Meteor’s Github repo by stale-bot.
@filipenevola, I personally think
stale-bot is a mistake and a recipe for a lot of frustration. Valuable issues, created for a reason, are being buried six feet under.
For example, the one about to be closed, was created by Ben himself.
Just thought I’d say this before the damage is done.
I think github bots like
stale-bot can be useful, but it would have been nicer to introduce it, and the process that issues will follow first before marking all our issues as stale.
At least it’s easy to unmark issues as stale with a fresh comment.
It did give me an extra 20 min of work to go through the notifications and mark some as not stale
Agree with the above. Closing an issue doesn’t make it go away. Even if there’s no time for fixing them, they are filled with discussion and possible workarounds which become harder to find. Especially once people start opening duplicates for the closed issues.
as someone also maintaining a bit of open source projects, i see the value of stale bot. It can be annoying, but it helps maintainers to
1.) decrease issue count, which helps to
- focus on important stuff
- reduce noise
- increase trust in the repo
2.) increase activity from users
- if the issue is still relevant, they will probably answer and unstale the issue
- or the issue is already resolved or not relevant anymore and they maybe will close the issue by themself or let the stale bot close it
i also received some notifcations from the stalebot now and most of them are indeed not relevant for me anymore, so i closed them or added a message why i think it is still relevant
Valuable issues, created for a reason, are being buried six feet under.
this is already the case if more issues are filed that are beeing close.
Hi, stale bot is not going to close every issue, I just added this to issue triage explaining the settings that are in place.
The idea is just to have confirmed issues in the repo, otherwise it’s only going to grow, we want to have a list of actionable items or items being classified yet. If in the end this cause more pain than benefits we can change it but I would like to try.
BTW, we need to update the people here https://github.com/meteor/meteor/blob/devel/CONTRIBUTING.md#project-roles
Issue Triagers is one of the roles.
If you want to have any of these roles let me know.
I see two problems currently with stale bot:
- It seems it marks stale after a month of inactivity. I have commented on an issue one month ago and now I got a message that it is again marked as stale. That is pretty low. Maybe three months?
- It doesn’t count upvotes or subscribing to the issue as activity. So if somebody is just upvoting instead of commenting because they see issue still relevant, which is generally seen as best practice, this does not count. So stale bot encourages +1 comments.
I’m willing to help out with triaging. I’m usually reading all the issues anyways so I would be happy to review the filed issues when I can and ask clarifying questions if they are necessary and try some reproductions provided.
I’ve been fighting with the stale bot in other OSS projects, notably Gatsby. After people repeatedly reply to an issue in order to unstale it, the comments are littered with old stale-bot warnings. When I attempted to delete that clutter, I was threatened to be kicked out of the org.