No, it's rather "If you don't like it, fork it."
I was not interested in contributing any of our work (mostly netfilter related) back to the core precisely because I have better things to do with my emotional energy than engage with the aggressively toxic personalities of LKML.
That's one of the joys of open source, of course, doing your own thing.
In contrast I had a much better experience contributing to Postfix and Dovecot, where the benevolent dictators did not feel the urge to spew pages of vitriol in response to a blunder when a neutrally worded admonishment would do.
I've heard of plenty of people who prefer one language over another because of the nicer community. Eventually that should mean that projects with friendly communities are more successful.
Forking code essentially gives you the ability to take everything, and then move it in your own new direction. You leave behind only the parts you thought were "bad" or unprofessional or whatever.
Yes it is. Saying you can just fork it is like saying you can just move yourself and all your family and friends to another country.
You might be able to move yourself but moving any significant amount of developers is in practise impossible.
Perhaps you're saying that you can't take the community with you? That doesn't seem like a reasonable expectation. You can fork, and you can continue to pull from upstream, but you can't force people to use it.
So it's better to force that significant amount of developers to do your bidding? That sounds just a just a weee bit unreasonable, IMHO.
You're basically saying that you want the fruits of Linus's labor without Linus there to do it?