Maybe in another life I will eventually understand what happened to the opensource culture/ethos which has been (in) my life for such a long time: tolerance, kindness, paying forward, reciprocity/mutual aid, collaboration, learning, working & sharing (in the open, as much as possible... "a rising tide..." and such).
Apart from the sheer contempt & stereotypes received over night, some people literally don't know jack about me, yet seem hell-bent on making me part of the greater problem and throwing DYOR tantrums...
Not once was I questioning the reality of the abuse, harm & other types of oppression present in tech/opensource circles. Even though it wasn't anywhere on the radar of my own lived opensource experience, I've not been blind to these issues, the reports or the suffering in other communities and I can muster some empathy. We are in full agreement that something must change for the better, uregntly and not just in FLOSS. Having some personal questions about chosen language, tone of voice, effectiveness &implementation aspects of the currently put-forward solution (aka CoC) to the larger/deeper problem — none of this is grounds to be questioning my values or being written off as an ignoramus, non-ally or even enemy and implied part of the cause why social change is needed...
Repeating for the 3rd time in this thread: After some actual great, helpful tangible views/insights/examples from other people, adding a CoC (with the right language) for my projects seems the currently best available solution/signal I can offer to people. I'm on board. Yet, I'm also actively bracing myself about taking this step, since the actual true change here is not the publishing of some standard behavior rules, but also having to enforce them later... This leads to the other factor of uncertainty of my original questioning: I'm not sure how well equipped I'll be to deal with such arbitration/enforcement tasks, i.e. emotional(!), personal bandwidth, stress tolerance and potential lack of immediate availability to deal with any such new issues, in addition to all the other project maintenance tasks already consuming so much of my time/focus...
So whereas others are viewing these issues purely on an abstract systemic level and it's all nicely crystal clear and unquestionable what to do, to me the issue is a personal/pragmatic one, and I imagine it's similar for many other smaller projects (run by single devs, small groups) who've already been looking into CoCs, but are holding back with adoption (regardless that they're trying to achieve the right goal). No reason to give those people shit...
Assumption: We want to do right by people and not violate the trust that certain behaviors are expected and enforced. Do we signal a warm message to the world by adopting a clear set of rules with a friendly tone of voice (yet to be selected), but then later maybe end up in conflict ourselves due to not being able to effectively resolve some violations in a timely manner and getting emotionally & motivationally super drained by the whole process? Is it so hard to acknowledge that this is far from being an easy decision, taking on yet another burden of open source project management, especially if one is stretched thin already?
FWIW I'm not expecting a reply from anyone, so please don't feel pressured to provide your "free labor" here to help someone figuring this all out a bit more... Still, I'd be grateful for any answers! Thank you in advance! ✌️
#OpenSource #CoC #HumanBehavior
@29d3d747
Incompetents want to take the focus away from achievement.
Codes of Conduct are a means to that end.