it's not the way to build an inclusive community
I'm genuinely curious where the fetishization of inclusion has come from. Everywhere I look it's is relatively homogenous groups, irrespective of the generalized identity of those groups, that actually start something and grow it to significance.
For small contrived tasks that will required minimal time to complete, I can see diversity and inclusion being more effective, but when a task is daunting, stressful, challenging, etc. the benefits of a strong in-group with a similar identity provides a foundation for sticking together through trying/difficult times that you would not find in a diverse group with few social ties around identity. Inclusion is valuable, but only when it can be achieved while also mitigating the group from becoming its own worst enemy when diversity of individual interests compete against shared interests.
Linus imparts a very very strong and visceral distaste for bad code. These strong opinions attract those that agree and repel those that don't agree. It's decidedly not inclusion of people who would be tolerant of mediocre code and that is generally a good thing for a critical codebase that is the foundation of so much other code in the world. A group of people that place quality of code at a greater importance over pleasant human interactions is going to produce quality code and sometimes create shitty human interactions. The don't package up and ship the shitty human interactions, but they do package up an ship the codebase. Feels like appropriate prioritization to me.
Anyways, I'm not saying inclusion is bad. I'm just saying that inclusion like exclusion has both positive and negative side effects there is no silver bullet when it comes to the makeup of a group that has come together to solve a problem.
relevant reading:
https://www.nczonline.net/blog/2015/05/14/the-bunny-theory-o...
http://www.shirky.com/writings/herecomeseverybody/group_enem...