What does this have to do with the discussion, unless as an illustration of what an "opposing view" could be, which surely no-one had trouble imagining?
The consensus seems to have gelled (few years ago, give or take a few years?) around every single open source project needing to have a specific "community guidelines" document - it was the new vogue established over the past few years by the body politic, and this lead to various promoters of new social paradigms to rename things that were taken at face value, i.e. "master-slave" in the context of database client-server architectures, or "master" branch as primary branch, etc.
These changes are trivial in retrospect, but contextually, the reversion of "participants will be tolerant of opposing views" seems to validate the notion that maybe excessive discourse around social mores aren't appropriate within the substructure of "writing new code that works, backporting features that are useful for others, etc"
The conflating of social justice goal-setting and software development is a swing and a miss, and if that's not completely clear by the context then I just want to apologize for stating what seems obvious to an external observer.
I understood what you meant and agree. I believe many social justice obsessed individuals have become their own worst enemy as they view every unrelated topic an attack on their personal perspective.