Close Inactive Issues

[AhmedMousa-ag]

I've been trying to find an issue to contribute to, but it's taking very long time to find an issue that no one is working on, or not already solved. Most issues already solved but still open on github.

I can see a lot of open PRs for long time and even many of them doesn't have the closes issue tag.

My suggestion is to add inactive bot checker to close issues with no activity for 3, 6 months or any period you see fit in addition to force Closes #10 to close issues.

Also I believe the contribution guide is outdated.

It really would help me to contribute fast to locate real issues instead of spending hours trying to identify an issue that is still an issue.

Thank you.

[maxdeviant]

Thank you, we are doing our best to stay on top of the issue backlog and close out issues, as we can.

We do already have a stale issue bot running in the repo.

[AhmedMousa-ag]

Thank you @maxdeviant , I needed to communicate with someone to be able to help and thought it might be helpful if I provide feedback as I highly believe in the saying "Negative feedback is better than no feedback".
Thank you again for your polite response. and I apologize if I bothered you.

[maxdeviant]

No problem at all!

Kirill also had a more detailed response, so want to make sure you saw that one: #37369 (comment)

[SomeoneToIgnore]

To comment a bit more and answer the rest:

Most issues already solved but still open on github.

As the person who spends a lot of time looking at those issues, I disagree fully in the context of this repo.
From my point of view, it's the reverse — most of the issues open here are not solved.

I can see a lot of open PRs for long time

That is very sad indeed.

and even many of them doesn't have the closes issue tag.

and that is sort of "ok" as indeed, many of them do not create an issue before fixing something.

My suggestion is to add inactive bot checker to close issues with no activity

Some examples of the bot's work:

• https://github.com/zed-industries/zed/issues?q=is%3Aissue%20state%3Aopen%20label%3Astale
• Very slow vue language server in large project #22231 (comment)

I've been trying to find an issue to contribute to

In my opinion, it's better not to "just" induce good things.

Instead, find something practical that you, yourself, have a good context on and what you do not like — only then search for the issue that might cover that and contain more context.

For example:

Also I believe the contribution guide is outdated.

is a much better idea to fix (depends on the implementation, of course) than any random issue you'll select.

If you insist on finding an issue, there's also https://github.com/zed-industries/zed/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22help%20wanted%22 label and #6953 (pinned so people can notice that easily)

If that is not something you'd like to work on, just do not work on anything, it's also fine (sometimes, even better than a bad, lengthy PR).