Configure StaleBot

[thebeline]

This adds the configuration for the Stale GitHub Application.

This will keep the Issues and Pull Requests clean moving forward.

Resolves: #266

[thebeline]

Note: targeting master because this doesn't effect any Golang code, and is a Repo modification.

[JeffB42]

I like this, but there are many tickets opened which are waiting for a reply from me (paused due to an investigation needed), as well as several feature requests, and I don't want to feel pressured to get something done in an allotted time, or else risk the ticket being auto-closed. (I'm doing this for fun, here)

How about this: I just added a "Waiting for reply" label. Can you set this up so it only watches and closes tickets with a label of "Waiting for reply"? We'll limit it to just those ticket, then way off in the future (probably post 3.0) when most of the tickets are closed, this can be changed to be more aggressive.

[thebeline]

I do believe I can.

[thebeline]

That said, i think the description in the action repo is apt and worth considering.

[thebeline]

Personally: https://github.com/probot/stale#is-closing-stale-issues-really-a-good-idea

Is closing stale issues really a good idea?
In an ideal world with infinite resources, there would be no need for this app.

But in any successful software project, there's always more work to do than people to do it. As more and more work piles up, it becomes paralyzing. Just making decisions about what work should and shouldn't get done can exhaust all available resources. In the experience of the maintainers of this app—and the hundreds of other projects and organizations that use it—focusing on issues that are actively affecting humans is an effective method for prioritizing work.

To some, a robot trying to close stale issues may seem inhospitable or offensive to contributors. But the alternative is to disrespect them by setting false expectations and implicitly ignoring their work. This app makes it explicit: if work is not progressing, then it's stale. A comment is all it takes to keep the conversation alive.

That said, for what it is worth, the default stale time is 60 days, and then the removal time is 7 days after marked stale. We can add a Stale message (that notifies all participants to reach back out) as well as a close message (and anyone can re-open the issue).

Further, we can modify the tags to prevent marking as stale.

I think that is all fantastic, and should be applied by default, with perhaps a configuration to ignore things that are tagged a certain way, or have an assignee, or something of that nature.

[thebeline]

@JeffB42 - is this.... stale? :-) Should I keep this open/have further discussion? Or is this not something you are interested in?