Seeking new maintainer for Matomo Analytics

In #3094315: Maintainer for Piwik Momoto Analytics blockd what now? you write:

I am not a programmer and can't take over the project.

Given that, the component should not be "Maintaining offer", but "Needs maintainers".

If I've misunderstood, and you are offering to step up as the new maintainer, please say so.

A Needs mainteners issue is created from the maintainers who are looking for new maintainers.

The project owner has not left drupal.org, and even if that were the case, there isn't any action we preventively take.
If there are users who want to become maintainer/co-maintainer of the projects owned from that user, they will open an issue for each of those projects.

For the record: I do not agree with setting status of this to "Fixed".

Nothing has been "Fixed" here. The current fact is that this widely used important project is not being maintained. Users of the project should be allowed to take action in this issue queue to remedy that, without getting a bogus "Fixed" status slapped on the request.

The entire Drupal ecosystem is going to suffer if much used projects becomes unsupported and our users are barred from trying to fix it.

Until somebody offers to maintain a project (which is, IMO, the only action users can take over a module that isn't maintained), there isn't anything we can do nor do we need to do.
In the specific case, I don't find correct to look for a new maintainer when the project owner is temporary blocked. I would eventually understand a request to become co-maintainer of a project, but even in this case, I would rather get first information about the reasons for blocking the user and how much the suspension is going to last.

This issue has been closed as Fixed because it is more a support request that got an answer. It cannot be a task, since there isn't anything that needs to be done (without a user who is willing to maintain the project until the return of the project owner).

Current policy, https://www.drupal.org/node/251466, is very clear on how to deal with this situation. Creating this issue is not part of that.

It is not a fact that the project is not being maintained. Currently the owner is temporarily not available, which is not the same as the project not being maintained. Users are in no way barred from trying to fix it. They can follow the procedure for perceived abandoned projects.

Do agree that the Drupal Ecosystem is suffering due to poorly maintained/abandoned projects. Disagree on Matomo Analytics as qualifying as such. But feel free to follow proper procedure to get other opinions.