>In case my point isn't obvious here, an explicit CoC has a number of advantages over a document like this one when it comes to actually resolving conflict, instead of trying to prevent it. It makes value judgements, but only because at some point in the conflict resolution process, leadership will be forced to make value judgements.
I disagree. Sociopaths weaponise hard and fast rules. It's better to not make rules that aren't required and stick to communicating as people rather than attempting to rule like computers. Don't choose to be a bureaucrat, choose to be a leader.
Put another way, there's no substitute for not being a horrible human being. Projects that have good people on them have no need for CoC's. Horrible people will not stop being horrible because there is a CoC there, nor will a CoC drive them away.
I don't really feel like getting into a roleplay with you about your specific Angry Project Lead scenario on hacker news, it's a bad forum for that since such discussions tend to be long and nuanced, but you should remember that when you have to tell someone their behavior is a net loss for their organization, it's never going to be a fun conversation. Obviously the person will protest, and depending on their personality that might range from pleading to outright physical aggression.
Everyone coming away from such discussions feeling unhappy is normal, what matters is that there is some form of resolution in the process. Yeah, the outcome might be a forked project, or it might be someone being asked to leave. Those are not comfortable outcomes but they are hopefully necessary, otherwise why bother to have the conversation? As long as you can bring the project to a state where you've moved past the obstacle and it's no longer at the forefront of peoples minds, you've succeeded. If people are still discussing your ruling and what it means for contributors months or years later, you've failed.
If resolution can be achieved without verbal, societal, technological or physical violence, that's the best that can be asked.
I disagree. Sociopaths weaponise hard and fast rules. It's better to not make rules that aren't required and stick to communicating as people rather than attempting to rule like computers. Don't choose to be a bureaucrat, choose to be a leader.
Put another way, there's no substitute for not being a horrible human being. Projects that have good people on them have no need for CoC's. Horrible people will not stop being horrible because there is a CoC there, nor will a CoC drive them away.
I don't really feel like getting into a roleplay with you about your specific Angry Project Lead scenario on hacker news, it's a bad forum for that since such discussions tend to be long and nuanced, but you should remember that when you have to tell someone their behavior is a net loss for their organization, it's never going to be a fun conversation. Obviously the person will protest, and depending on their personality that might range from pleading to outright physical aggression.
Everyone coming away from such discussions feeling unhappy is normal, what matters is that there is some form of resolution in the process. Yeah, the outcome might be a forked project, or it might be someone being asked to leave. Those are not comfortable outcomes but they are hopefully necessary, otherwise why bother to have the conversation? As long as you can bring the project to a state where you've moved past the obstacle and it's no longer at the forefront of peoples minds, you've succeeded. If people are still discussing your ruling and what it means for contributors months or years later, you've failed.
If resolution can be achieved without verbal, societal, technological or physical violence, that's the best that can be asked.