Please remove "Stale" bot

[shaal]

Is your feature request related to a problem? Please describe

The fact that so many important bug reports and feature requests have been closed by the Stale bot is frustrating.

Users spend a significant amount of time writing feature requests and bug reports.

The Stale bot required me to follow Github notifications carefully to determine when an issue was tagged as stale, then go to that issue, and request that the meta: never-stale label be added, since closing an issue that has not yet been resolved will serve no purpose.

Describe the behaviour you'd like

As I understand it, Stale bot is used to get rid of any issues that are no longer of importance. In my personal experience, I have never submitted issues that I did not believe were significant. I wish a human would keep track of the issues that should be closed, assuming all issues are relevant.

There should be a known outcome for any issue submitted by a Gitpod user. (Please feel free to describe real outcomes, I will just provide a few examples)

• Duplicate issue (we have already addressed it elsewhere)
• Unable to replicate the problem (we need more information/data/examples to find a solution)
• Solved (🎉)
• Out of scope (The feature is not within the scope of the project)

Describe alternatives you've considered

Additional context

[rfay]

I certainly agree.

[axonasif]

Just letting you guys know that we had an discussion internally about your issue.

[svenefftinge]

I have never submitted issues that I did not believe were significant.

The question is if an issue is still important to you after some time. It could be that you have found a solution, a workaround, or just moved on. Yes, it is annoying to keep pinging things that are important to you, but it is not only a signal to stale-bot but also to the team. Also, it is super helpful to get signal from others who might have the same problem/wish and learn more about the associated use cases.

• Duplicate issue (we have already addressed it elsewhere)
• Unable to replicate the problem (we need more information/data/examples to find a solution)
• Solved (🎉)
• Out of scope (The feature is not within the scope of the project)

there is a fifth common outcome:

• In scope but priorization

This is what the state is of a lot of tickets that in principal make sense and are in scope. We keep them open to gather more signal (user cases, upvotes, etc.) so that eventually they would be prioritized or closed by stale-bot because they are not important enough for the majority of users.