Close or set to "Stale" Issues that have not received an update in the previous 12 months

Hello all.
Shouldn't this issue be closed as it is over its own timeout ?
This means that this action is not ready to be executed.
What are we waiting for to begin the general process ?

Shouldn't this issue be closed as it is over its own timeout ?

There is nothing like a timeout for issues at the moment.

Although, given the many feedback in this issue, it's possible to close this as won't fix. Although this might be the issue to continue the discussion in the future once we land on GitLab issues. It's also discussed in #30 and #31.

I'm also a strong believer that it should be a human person closing issues. I'm working with a company where they do this after 7 days of no reply. It's really dreadful to get the "your ticket has been closed because of inactivity" email every time. It gives you the impression, we heard your issue, but you didn't reply in time, so we don't care -> closed.

Personally I do not like the idea of closing old issues just becase of an inactivity. There are tons of valuable issues which are old, but there is still a potential that someday these will be addressed (these also contains valuable information collected by various contributors during that timeframe). This is specific for the Drupal community. And hiding these from the default search will cause that other duplicate issues will be created sometime in the future.

It's also habitually better to start a fresh new issue when the "original" one is 2 years old. You can close link the two issue anyway and copy any relevant information in the new one.

I disagree. Imagine that you have an old issue with progress, but suddenly inactive for a longer period. The issue will be closed with all valuable information, credits, etc and you will need to create a new issue where you need to copy everything? And what if this happens 10 times for one specific problem? One issue will be duplicated multiple times, which will distract users / harm SEO / ... It can have an opposite effect and create more work that the current system. Yes, there are issues with 100+ comments, which can be difficult to read, but I still think that it is better than having these information fragmented in multiple issues.

It gives you the impression, we heard your issue, but you didn't reply in time, so we don't care -> closed.

This. Unfixed issues should stay open unless these qualify for one of the Closed statuses (like Won't fix, Works as designed, ...). Maybe a different could be considered for Support requests, but not for Bug fixes.

But all of this was already mentioned in multiple comments above, so +1 from me, to closing this as Won't fix.

I agree - let's close as "won't fix".

I'm always happy to try out ideas for them not to "stick".