> which makes your "despite having a dickbag in charge" completely irrelevant So not having a CoC and having a dickbag in charge is OK? Cool! QED! > Being abl

> which makes your "despite having a dickbag in charge" completely irrelevant So not having a CoC and having a dickbag in charge is OK? Cool! QED! > Being able to communicate effectively - and that generally excludes "aggressively" It doesn't. Aggressivity doesn't exclude efficiency. Aggressivity is a human interaction with a purpose. If used correctly it can express emphasis with amazing efficiency. > Ironic that you call it "bike-shedding" when that was coined from a project that wasn't "overly-inclusive". Bike-shedding is a reality in non-inclusive project like FreeBSD. Now imagine in "inclusive" projects where every word has to be carefully weighted in order to not offend anyone. People fighting not only over the color of the bike shed, but also on the political undertones of supporting bikes, on the percentage of male and/or white bike riders, all while constantly accusing each other of being threatening. Exponential bullshitting and no work done :) > It's clear your only argument is "I don't like inclusivity" Actually, I like it. But, in a technical project, it should always come after the actual "getting shit done" part. > you're on the wrong side of history and doomed to fail. Am I? I was there in the 90s, when riot grrrls were all the shit and PC peaked. I wasn't terribly impressed back then and I'm not impressed now :)