From: Austin Ziegler Date: 2016-01-29T00:44:57-05:00 Subject: [ruby-core:73569] Re: [Ruby trunk - Misc #12004] Code of Conduct --===============1210361677== Content-Type: multipart/alternative; boundary=001a11c24cee3b21c7052a728aad --001a11c24cee3b21c7052a728aad Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Daniel: Codes of conduct don=E2=80=99t exist to punish, believe it or not. They exi= st to help project maintainers act *fairly* when behaviours go *off the rails*. Sometimes those behaviours are always unacceptable (direct threats against individuals, as an example=E2=80=94in this thread, the posting of anti-Semi= tic materials would *definitely* qualify). Sometimes those behaviours are best treated as a failure due to ignorance which should result in stern warnings *with* an educational approach. And yes, sometimes those behaviours will be pure misunderstanding because of the multinational/multilingual nature of the wider Ruby community. A good code of conduct recognizes these cases and provides guidance for project maintainers and community managers so that there can be clarification, education, and/or expulsion as appropriate to the nature of the offence. For those who want CoCs that don=E2=80=99t include the consideration of beh= aviour outside of the Ruby =E2=80=9Cspaces=E2=80=9D. While I am sympathetic to not= wanting random thoughts to be used to exclude me from a group, it may be appropriate to use non-=E2=80=9Cspace=E2=80=9D behaviours and evidence to help classify su= ch behaviour. I present a thought experiment based on a particularly unsavoury individual, DV (often better known as R=E2=80=94 V). If he were to all of a sudden show= up in a Ruby =E2=80=9Cspace=E2=80=9D, there would be a lot of concern by people bec= ause this person is extremely hostile to women. IMO, the adjudication of any claim of harassment by DV would need to consider DV=E2=80=99s history of hostility t= oward women *even though it happened outside of a Ruby =E2=80=9Cspace=E2=80=9D* p= recisely because it would inform whether this is a misunderstanding, ignorance, or unacceptable (and yes, his history is such that it would pretty much land on unacceptable). -a On Thu, Jan 28, 2016 at 5:14 PM, <6ftdan@gmail.com> wrote: > Issue #12004 has been updated by Daniel P. Clark. > > > Yukihiro Matsumoto wrote: > > OK, that's enough. > > > > We will set up some form of CoC in the future. Let me think for a while > which one we are going to choose. > > > > Matz. > > Thank you Matz for letting us know. > > Something I'd like people to keep in mind is that a majority of people > will contribute to projects without first reading any conduct guidelines. > So I encourage the assumption of good intent first, and possible ignoranc= e > second, before any action is considered a violation. > > If any remark seems to offend you then I ask that you first ask for > clarification and intent behind the remark before assuming ill intent. A= s > is seen in this very thread when people speak in a language that is not > their native language things can be misconstrued. > > ---------------------------------------- > Misc #12004: Code of Conduct > https://bugs.ruby-lang.org/issues/12004#change-56771 > > * Author: Coraline Ada Ehmke > * Status: Assigned > * Priority: Normal > * Assignee: Yukihiro Matsumoto > ---------------------------------------- > I am the creator of the Contributor Covenant, a code of conduct for Open > Source projects. At last count there are over 13,000 projects on Github > that have adopted it. This past year saw adoption of Contributor Covenant > by a lot of very large, very visible projects, including Rails, Github's > Atom text editor, Angular JS, bundler, curl, diaspora, discourse, Eclipse= , > rspec, shoes, and rvm. The bundler team made code of conduct integration = an > option in the gem creation workflow, putting it on par with license > selection. Many open source language communities have already adopted the > code of conduct, including Elixir, Mono, the .NET foundation, F#, and > Apple's Swift. RubyTogether also adopted a policy to only fund Ruby > projects that had a solid code of conduct in place. > > Right now in the PHP community there is a healthy debate about adopting > the Contributor Covenant. Since it came from and has been so widely adopt= ed > by the Ruby community at large, I think it's time that we consider adopti= ng > it for the core Ruby language as well. > > Our community prides itself on niceness. What a code of conduct does is > define what we mean by nice. It states clearly that we value openness, > courtesy, and compassion. That we care about and want contributions from > people who may be different from us. That we pledge to respect all > contributors regardless of their race, gender, sexual orientation, or oth= er > factors. And it makes it clear that we are prepared to follow through on > these values with action when and if an incident arises. > > I'm asking that we join with the larger Ruby community in supporting the > adoption of the Contributor Covenant for the Ruby language. I think that > this will be an important step forward and will ensure the continued > welcoming and supportive environment around Ruby. You can read the full > text of the Contributor Covenant at > http://contributor-covenant.org/version/1/3/0/ and learn more at > http://contributor-covenant.org/. > > Thanks for your consideration and I look forward to hearing your thoughts= . > > > ---Files-------------------------------- > Screen Shot 2016-01-22 at 6.45.23 PM.png (595 KB) > Ruby_Code_of_Conduct_Numbers.png (119 KB) > Ruby_Code_of_Conduct_Discussion.png (143 KB) > > > -- > https://bugs.ruby-lang.org/ > > Unsubscribe: > > --=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 --001a11c24cee3b21c7052a728aad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Daniel:

Codes of conduct don=E2=80=99t = exist to punish, believe it or not. They exist to help project maintainers = act *fairly* when behaviours go *off the rails*. Sometimes those behaviours= are always unacceptable (direct threats against individuals, as an example= =E2=80=94in this thread, the posting of anti-Semitic materials would *defin= itely* qualify). Sometimes those behaviours are best treated as a failure d= ue to ignorance which should result in stern warnings *with* an educational= approach. And yes, sometimes those behaviours will be pure misunderstandin= g because of the multinational/multilingual nature of the wider Ruby commun= ity.

A good code of conduct recognizes these cases= and provides guidance for project maintainers and community managers so th= at there can be clarification, education, and/or expulsion as appropriate t= o the nature of the offence.

For those who want Co= Cs that don=E2=80=99t include the consideration of behaviour outside of the= Ruby =E2=80=9Cspaces=E2=80=9D. While I am sympathetic to not wanting rando= m thoughts to be used to exclude me from a group, it may be appropriate to = use non-=E2=80=9Cspace=E2=80=9D behaviours and evidence to help classify su= ch behaviour. I present a thought experiment based on a particularly unsavo= ury individual, DV (often better known as R=E2=80=94 V). If he were to all = of a sudden show up in a Ruby =E2=80=9Cspace=E2=80=9D, there would be a lot= of concern by people because this person is extremely hostile to women. IM= O, the adjudication of any claim of harassment by DV would need to consider= DV=E2=80=99s history of hostility toward women *even though it happened ou= tside of a Ruby =E2=80=9Cspace=E2=80=9D* precisely because it would inform = whether this is a misunderstanding, ignorance, or unacceptable (and yes, hi= s history is such that it would pretty much land on unacceptable).

-a

On Thu, Jan 28, 2016 at 5:14 PM, <6ftdan@gmail.com> wrote:
Issue #12004 has been update= d by Daniel P. Clark.


Yukihiro Matsumoto wrote:
> OK, that's enough.
>
> We will set up some form of CoC in the future. Let me think for a whil= e which one we are going to choose.
>
> Matz.

Thank you Matz for letting us know.

Something I'd like people to keep in mind is that a majority of people = will contribute to projects without first reading any conduct guidelines.= =C2=A0 So I encourage the assumption of good intent first, and possible ign= orance second, before any action is considered a violation.

If any remark seems to offend you then I ask that you first ask for clarifi= cation and intent behind the remark before assuming ill intent.=C2=A0 As is= seen in this very thread when people speak in a language that is not their= native language things can be misconstrued.

----------------------------------------
Misc #12004: Code of Conduct
https://bugs.ruby-lang.org/issues/12004#c= hange-56771

* Author: Coraline Ada Ehmke
* Status: Assigned
* Priority: Normal
* Assignee: Yukihiro Matsumoto
----------------------------------------
I am the creator of the Contributor Covenant, a code of conduct for Open So= urce projects. At last count there are over 13,000 projects on Github that = have adopted it. This past year saw adoption of Contributor Covenant by a l= ot of very large, very visible projects, including Rails, Github's Atom= text editor, Angular JS, bundler, curl, diaspora, discourse, Eclipse, rspe= c, shoes, and rvm. The bundler team made code of conduct integration an opt= ion in the gem creation workflow, putting it on par with license selection.= Many open source language communities have already adopted the code of con= duct, including Elixir, Mono, the .NET foundation, F#, and Apple's Swif= t. RubyTogether also adopted a policy to only fund Ruby projects that had a= solid code of conduct in place.

Right now in the PHP community there is a healthy debate about adopting the= Contributor Covenant. Since it came from and has been so widely adopted by= the Ruby community at large, I think it's time that we consider adopti= ng it for the core Ruby language as well.

Our community prides itself on niceness. What a code of conduct does is def= ine what we mean by nice. It states clearly that we value openness, courtes= y, and compassion. That we care about and want contributions from people wh= o may be different from us. That we pledge to respect all contributors rega= rdless of their race, gender, sexual orientation, or other factors. And it = makes it clear that we are prepared to follow through on these values with = action when and if an incident arises.

I'm asking that we join with the larger Ruby community in supporting th= e adoption of the Contributor Covenant for the Ruby language. I think that = this will be an important step forward and will ensure the continued welcom= ing and supportive environment around Ruby. You can read the full text of t= he Contributor Covenant at http://contributor-covenant= .org/version/1/3/0/ and learn more at http://contributor-covenan= t.org/.

Thanks for your consideration and I look forward to hearing your thoughts.<= br>

---Files--------------------------------
Screen Shot 2016-01-22 at 6.45.23 PM.png (595 KB)
Ruby_Code_of_Conduct_Numbers.png (119 KB)
Ruby_Code_of_Conduct_Discussion.png (143 KB)


--
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:= ruby-core-request@ruby-lang.org?subject=3Dunsubscribe>
<http://lists.ruby-lang.org/cgi-bin/m= ailman/options/ruby-core>



--
=
Austin Ziegler =E2=80=A2 halostatue@gmail.com =E2=80=A2 <= a href=3D"mailto:austin@halostatue.ca" target=3D"_blank">austin@halostatue.= ca
http://ww= w.halostatue.ca/ =E2=80=A2 http://twitter.com/halostatue
--001a11c24cee3b21c7052a728aad-- --===============1210361677== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Unsubscribe: --===============1210361677==--