<story><title>Russ Cox: Go, Open Source, Community</title><url>http://blog.golang.org/open-source</url></story><parent_chain><item><author>EdiX</author><text>I agree that a code of conduct is a great idea but I&amp;#x27;m really bummed to read that the Django CoC is going to be adopted by golang.&lt;p&gt;1. The Django CoC uses very vague language on what it is forbidden and explicitly tells you that &amp;quot;this isn’t an exhaustive list of things that you can’t do&amp;quot; just to be extra vague in what constitutes unacceptable behaviour.&lt;p&gt;2. It does not define what process will be used to address CoC violations, being ejected from an OS project for violating the CoC can be a serious thing with personal and professional ramifications but an accused is not given the right to face their accuser nor the right to an impartial jury (which would be hard to do anyway since the accusation could be something like &amp;quot;he&amp;#x27;s making me anxious&amp;quot;)&lt;p&gt;3. It overextends itself &amp;quot;violations of this code outside these spaces may affect a person&amp;#x27;s ability to participate within them&amp;quot; which means that not only you are under the scrutiny of the kangaroo court when you are posting on golang spaces but everywhere else: ycombinator, reddit, your personal blog, etc. Honestly I feel like just writing this criticism is painting a target on my forehead, talk about safe spaces.&lt;p&gt;I wouldn&amp;#x27;t be making this comment if CoCs hadn&amp;#x27;t already been used in bad faith to attempt to character assassinate OS contributors (for exmaple the Kubuntu debacle or this [1])&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;igurublog.wordpress.com&amp;#x2F;2015&amp;#x2F;06&amp;#x2F;04&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;igurublog.wordpress.com&amp;#x2F;2015&amp;#x2F;06&amp;#x2F;04&amp;#x2F;&lt;/a&gt;</text></item></parent_chain><comment><author>zurn</author><text>There are good reasons why rules regulating human social behaviour (such as legislation) are written in this &amp;quot;vague&amp;quot; way, not attempting to be formal-verification-level complete but relying upon human interpretation. It follows that to work well it needs the people doing the interpretation (judges, committees, ombudsman, etc) to be competent, and be selected so that people can have faith in them.&lt;p&gt;Regarding your [1], the GNOME code of conduct referenced therein explicitly says &amp;quot;There is no official enforcement of these principles, and this should not be interpreted like a legal document&amp;quot;. So maybe that CoC is being applied contrary to its design there.</text></comment>
<story><title>Russ Cox: Go, Open Source, Community</title><url>http://blog.golang.org/open-source</url></story><parent_chain><item><author>EdiX</author><text>I agree that a code of conduct is a great idea but I&amp;#x27;m really bummed to read that the Django CoC is going to be adopted by golang.&lt;p&gt;1. The Django CoC uses very vague language on what it is forbidden and explicitly tells you that &amp;quot;this isn’t an exhaustive list of things that you can’t do&amp;quot; just to be extra vague in what constitutes unacceptable behaviour.&lt;p&gt;2. It does not define what process will be used to address CoC violations, being ejected from an OS project for violating the CoC can be a serious thing with personal and professional ramifications but an accused is not given the right to face their accuser nor the right to an impartial jury (which would be hard to do anyway since the accusation could be something like &amp;quot;he&amp;#x27;s making me anxious&amp;quot;)&lt;p&gt;3. It overextends itself &amp;quot;violations of this code outside these spaces may affect a person&amp;#x27;s ability to participate within them&amp;quot; which means that not only you are under the scrutiny of the kangaroo court when you are posting on golang spaces but everywhere else: ycombinator, reddit, your personal blog, etc. Honestly I feel like just writing this criticism is painting a target on my forehead, talk about safe spaces.&lt;p&gt;I wouldn&amp;#x27;t be making this comment if CoCs hadn&amp;#x27;t already been used in bad faith to attempt to character assassinate OS contributors (for exmaple the Kubuntu debacle or this [1])&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;igurublog.wordpress.com&amp;#x2F;2015&amp;#x2F;06&amp;#x2F;04&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;igurublog.wordpress.com&amp;#x2F;2015&amp;#x2F;06&amp;#x2F;04&amp;#x2F;&lt;/a&gt;</text></item></parent_chain><comment><author>ta140604</author><text>Similar concerns (with more examples) have been raised in CoC discussion over on Reddit:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.reddit.com&amp;#x2F;r&amp;#x2F;golang&amp;#x2F;comments&amp;#x2F;3abyva&amp;#x2F;a_code_of_conduct_for_the_go_community&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.reddit.com&amp;#x2F;r&amp;#x2F;golang&amp;#x2F;comments&amp;#x2F;3abyva&amp;#x2F;a_code_of_co...&lt;/a&gt;</text></comment>