Red Hat fails to take WeMakeFedora.org

If we look at the incident in Pycon 2013, the problem wasn't the CoC reporter, the people who were reported nor the organisers. All was managed correctly on the CoC side. The organisers said "you shouldn't do that", people agreed, and that's it. However, because the reporter posted something on twitter (a picture), it became viral and attracted a online group that jumped on her. Virality wasn't intended, and the reaction was disproportionate. It snowballed and resulted in, if I am not wrong, everybody fired and receiving death threats, etc, etc. Tweets do not become viral by magic, mob do not assemble by themselves, someone has to push for that. This was pre gamergate (who started in 2014), and yet, no one ever seems to go look deeper on that side of the issue.

The controversy is mostly linked to that type of mob. I do not say CoC wouldn't be controversial by itself, but the discussions around them are a order of magnitude more controversial due to some forces that are under discussed most of the time. That's like with systemd. You would think a init system change wouldn't result in someone sending a threat on the answering machine of his main developer, and yet, it happened.

You can see that for almost every high visibility cases. There is lots of time where CoC violations are handled without trouble, but we almost never discuss them because they are not high visibility. If you look at the stats provided by projects, such as Fedora ( https://communityblog.fedoraproject.org/fedora-code-of-co... ), you can see the majority of tickets are not resulting in anyone being banned. And that 1 lone ban is likely Daniel Pocock, whose story have been already told.