-
Notifications
You must be signed in to change notification settings - Fork 96
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
timeout for old issues #112
Conversation
Interesting idea, is that scripted or manual? Do you post the closure policy anywhere and refer to it? |
no automation I monitor all the issues and do post something like:
you can add note about it to CONTRIBUTING.md, I can do the closing as it's part of what I do for RVM. |
I like that. I think I will recommend it at work. |
What do you think about making the window a bit longer? Like 4 weeks? |
as long as there is one I'm fine with it, even a year would be acceptable as I have seen issues open with no feedback on both sides for years. |
Yea, I would be ok with 2 months. Anything past 2 months I would say is a definite close. |
@georgeyacoub for #54 it should be easy to add support for the check but then maybe we should change the approach and start creating gem plugins so we get usage stats via rubygems gems downloads |
I can start draft for CONTRIBUTING.md and open it as a PR (unless one of you wants a take at it) |
Thank you @mpapis. Go for it :) |
let me know what do you think, link to this will be shown above the title box for new issues |
Looks good, I'm open to moving the "need info" time if we need to also. |
@jish for RVM I have a rule of closing issues with no response in two weeks, having a timeout prevents old issues laying around even when there is no feedback form the creator of the issue, you can pick any other timeout then two weeks, but having one would help to keep order in the tickets.