-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Shall we have a policy about stale issues? #128
Comments
Oh, one more thing. We could totally start by marking "stale" as 1 year, then reduce to 6 months, then reduce to 3 months, and then finally (if we think it's useful/necessary), reduce to 1 month. We don't have to jump straight to the most extreme. |
I had also started using Zenhub Board to start going through them as well, placing some in backlog. It has been a while since I have been able to do that though. |
One of the things that appeals to me about closing (rather than putting it in a backlog) is that it gives us a sanity check about how important it is: if nobody brings it up again, maybe it's not important. I have a tendency to save ALL the ideas out of fear of losing anything. |
That and the backlog is not viewable by those that aren't using zenhub. |
@kytrinyx Closing issues that are stale seems like an excellent idea, for all the reasons you already mentioned. |
I like this idea. Sometimes I find it overwhelming combing through all the open issues looking to help out. When looking through the older issues, It's tough to know what is really "important" or perhaps not valid anymore. |
This discussion reminds me of the notion of "inventory" in Lean thinking. Our contributors'/maintainers' time is a limited treasure. People like @treiff burning time as he described is pure waste (i.e. we get nothing for the effort). It's doubly positive when we consider how much more inviting it is to engage with a lean project (where nearly all issues have import) than those that have apparent clutter. |
This is an excellent point. OK, based on the discussion so far, I am convinced that this will be a good thing. How do you all feel about starting with 6 months as the "stale" threshold? |
Sounds reasonable. |
The next step on this is to draft an issue that can be submitted to every single Exercism repository that describes:
Then, on the deadline I will install probot/stale integration on the Exercism org, for all repositories. |
Here's my draft:
I didn't put the arguments for doing this directly in the issue draft, but rather link back to the original discussion. |
To get the list of repo names in the org:
Then we can loop through the repos in repos.txt and submit issues using hub. |
OK, I've done this. Since turning it on doesn't affect repositories that have not added a |
Just confirming, this will also close stale pull requests? |
Yepp, that's correct: https://github.com/exercism/exercism.io/blob/master/.github/stale.yml#L21 |
TODO
original issue
The exercism/exercism.io has a lot of very old issues.
A colleague of mine recently built a GitHub integration that will automatically close stale issues (well, it first adds a comment, then closes it if there's no activity in the N days after the comment).
https://github.com/integration/probot-stale
I would like to suggest that we do this for the exercism/exercism.io repository.
The argument for this is that:
My goal for the project is for every issue to be actionable. Eventually that will mean doing better at labeling (some issues might be worth keeping open even if they are stale), but I think it would be helpful to start by defaulting to "close" and then when we run into things where we don't like that, we can discuss it to see what we should be doing instead.
The text was updated successfully, but these errors were encountered: