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

timeout for old issues #112

Merged
merged 1 commit into from
Jan 15, 2014
Merged

timeout for old issues #112

merged 1 commit into from
Jan 15, 2014

Conversation

mpapis
Copy link
Collaborator

@mpapis mpapis commented Jan 15, 2014

@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.

@jish
Copy link
Owner

jish commented Jan 15, 2014

Interesting idea, is that scripted or manual? Do you post the closure policy anywhere and refer to it?

@mpapis
Copy link
Collaborator Author

mpapis commented Jan 15, 2014

no automation I monitor all the issues and do post something like:

there was no feedback in two weeks, closing the issue, please let me know if you can provide any feedback and I will reopen

you can add note about it to CONTRIBUTING.md, I can do the closing as it's part of what I do for RVM.

@gy
Copy link

gy commented Jan 15, 2014

I like that. I think I will recommend it at work.

@jish
Copy link
Owner

jish commented Jan 15, 2014

What do you think about making the window a bit longer? Like 4 weeks?

@mpapis
Copy link
Collaborator Author

mpapis commented Jan 15, 2014

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.

@gy
Copy link

gy commented Jan 15, 2014

@mpapis I think a year is too long.
@jish Looking at this #54 which hasn't had any activity for almost a year I would say close it we can't reproduce it.

@jish
Copy link
Owner

jish commented Jan 15, 2014

Yea, I would be ok with 2 months. Anything past 2 months I would say is a definite close.

@mpapis
Copy link
Collaborator Author

mpapis commented Jan 15, 2014

@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

@gy
Copy link

gy commented Jan 15, 2014

@mpapis yeah that sounds like a good use case.
@jish 2 month since the last comment/activity. Correct?

@mpapis
Copy link
Collaborator Author

mpapis commented Jan 15, 2014

I can start draft for CONTRIBUTING.md and open it as a PR (unless one of you wants a take at it)

@gy
Copy link

gy commented Jan 15, 2014

Thank you @mpapis. Go for it :)

@mpapis
Copy link
Collaborator Author

mpapis commented Jan 15, 2014

let me know what do you think, link to this will be shown above the title box for new issues

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 48a3e63 on features/CONTRIBUTING.md into 6ba41b8 on master.

@jish
Copy link
Owner

jish commented Jan 15, 2014

Looks good, I'm open to moving the "need info" time if we need to also.

jish added a commit that referenced this pull request Jan 15, 2014
@jish jish merged commit a9fe08a into master Jan 15, 2014
@jish jish deleted the features/CONTRIBUTING.md branch January 15, 2014 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants