From: Austin Ziegler Date: 2016-01-25T10:57:42-05:00 Subject: [ruby-core:73423] Re: [Ruby trunk - Misc #12004] Code of Conduct --===============2124083791== Content-Type: multipart/alternative; boundary=089e0141a794422870052a2aa2e6 --089e0141a794422870052a2aa2e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Jan 25, 2016 at 2:22 AM, wrote: > Issue #12004 has been updated by Ruby Amateur. > > The more I contemplate the [revised code of conduct (or "community > guidelines") by Caroline Ada Ehmke]( > https://bugs.ruby-lang.org/issues/12004#note-347), on one hand I like the > idea of allowing confidential addressing of grievences. However, I don't > fully understand how the moderation of the Ruby community can be handled. > First of all it requires infrastructure and policy to implement even the > most basic grievence handling. Furthermore, I feel if left to Matz and hi= s > Japanese delegates (due to enforcing local laws), either side of a > complaint can skillfully feign ignorance due to language barrier. It also > places a lot of mental burden deciding and judging what complies with the > code of conduct and what doesn't. **Lastly, I feel like code of conducts > with enforcement and punitive measures is like giving delegates of a > community firearms when the community was safe and peaceful for 20 years.= ** > I can see your point here, but I disagree. 1) There are several people in the community who have gained Matz=E2=80=99s trust over the years who could= *also* assist with handling conduct complaints. 2) The biggest complaint against codes of conduct is that they *can* be enforced unfairly. I see the enforcement/measures bits as reducing the opportunity for rules to be applied unfairly. > On the other hand, [Jeremy Evan's proposed Code of Conduct in #329]( > https://bugs.ruby-lang.org/issues/12004#note-329) is far simpler, easier > to understand, and doesn't burden the project and community. I also think > we can consider addressing grievences, punitive measuers, and enforcement > at a later time. I just don't see the need to future proof these policies > today, especially during a heated discussion where people are upset. I > think if the community has proper data points collected to warrant > enforcement and punitive measures, we should consider it. > I don=E2=80=99t agree, especially on the matter of having *somewhere* to ma= ke confidential reports. Having guidelines and/or enforcement limits (=E2=80=9Csanctions up to and including temporary or permanent exclusion fr= om=E2=80=A6=E2=80=9D) reduces the ability to apply community standards or rules unfairly. IMO. -a --=20 Austin Ziegler =E2=80=A2 halostatue@gmail.com =E2=80=A2 austin@halostatue.c= a http://www.halostatue.ca/ =E2=80=A2 http://twitter.com/halostatue --089e0141a794422870052a2aa2e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Mon, Jan 25, 2016 at 2:22 AM, <rubyamateur@wbml.ne= t> wrote:
Issue #12004 has been updated by Ruby = Amateur.

The more I contemplate the [revised code of conduct (or "community gui= delines") by Caroline Ada Ehmke](https://bugs.r= uby-lang.org/issues/12004#note-347), on one hand I like the idea of all= owing confidential addressing of grievences. However, I don't fully und= erstand how the moderation of the Ruby community can be handled. First of a= ll it requires infrastructure and policy to implement even the most basic g= rievence handling. Furthermore, I feel if left to Matz and his Japanese del= egates (due to enforcing local laws), either side of a complaint can skillf= ully feign ignorance due to language barrier. It also places a lot of menta= l burden deciding and judging what complies with the code of conduct and wh= at doesn't. **Lastly, I feel like code of conducts with enforcement and= punitive measures is like giving delegates of a community firearms when th= e community was safe and peaceful for 20 years.**

=
I can see your point here, but I disagree. 1) There are several = people in the community who have gained Matz=E2=80=99s trust over the years= who could *also* assist with handling conduct complaints. 2) The biggest c= omplaint against codes of conduct is that they *can* be enforced unfairly. = I see the enforcement/measures bits as reducing the opportunity for rules t= o be applied unfairly.
=C2=A0
On the other hand, [Jeremy Evan's proposed Code of Conduct in #329](https://bugs.ruby-lang.org/issues/12004#note-329) i= s far simpler, easier to understand, and doesn't burden the project and= community. I also think we can consider addressing grievences, punitive me= asuers, and enforcement at a later time. I just don't see the need to f= uture proof these policies today, especially during a heated discussion whe= re people are upset. I think if the community has proper data points collec= ted to warrant enforcement and punitive measures, we should consider it.
=C2=A0
I don=E2=80=99t agree, especially on t= he matter of having *somewhere* to make confidential reports. Having guidel= ines and/or enforcement limits (=E2=80=9Csanctions up to and including temp= orary or permanent exclusion from=E2=80=A6=E2=80=9D) reduces the ability to= apply community standards or rules unfairly. IMO.
-a
--
--089e0141a794422870052a2aa2e6-- --===============2124083791== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Unsubscribe: --===============2124083791==--