Disagree. Issue trackers are used for all sorts of things in all kinds of projects. Go look around, plenty of examples out there. Unless the maintainers have explicitly specified how issue trackers are supposed to be used, (reasonable) discussions are usually allowed on issue trackers, especially GitHub Issues.

And focusing on that after the fact does nothing to resolve the situation or advance the discussion, which should be the goal now.

During an emergency situation where an issue is running out of control, the priority is to evaluate and contain the problem then address it, it is not the time to assign blame and quote regulations which weren’t followed. That’s for later, when everything is stable, together with understanding why the rules weren’t followed and if you can improve that process for the future.

If issues with the program are caused by behavior of the maintainer, it doesn’t seem inappropriate.