The abusive behavior that was being used to manipulate Lasse Collin into bringing on more maintainers for #xz went unnoticed because abusive behavior in Open Source communities is so pervasive. In context, we can clearly see it was part of an orchestrated operation. Out of context, it looks like just another asshole complaining about stuff they have no right to complain about. https://robmensching.com/blog/posts/2024/03/30/a-microcosm-of-the-interactions-in-open-source-projects/
A Microcosm of the interactions in Open Source projects | RobMensching.com

Originally a thread on Twitter about the xz/liblzma vulnerability, when I finished typing it, I realized I had a real world slice of Open Source interaction that deserved more attention.

@swelljoe wouldn't the right thing to do if there are patches but the maintaner(s) can't include them right now, be to fork the project?

@Variety "the right thing" is situational. But, forking _is_ one of the rights one has as an Open Source user, while heaping abuse on the lone volunteer maintainer isn't.

And, in this case, if the maintainer had felt empowered to say, "I'll get to it when I can, if you can't wait, fork off." maybe this would have been prevented. But, that's not actually what people who threaten to fork want. If they were capable and really needed it for their own work, they'd just do it and merge back later.