From: Austin Ziegler Date: 2016-01-23T20:43:36-05:00 Subject: [ruby-core:73340] Re: [Ruby trunk - Misc #12004] Code of Conduct --===============0134888277== Content-Type: multipart/alternative; boundary=047d7b2e4d34dea3c4052a0a95d8 --047d7b2e4d34dea3c4052a0a95d8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I think that the original Postgres version is better than your amended one, Jeremy. I think you=E2=80=99ve removed too much. I still think that it shou= ld be clearer about permissible actions for violations, but I also know that Matz is opposed to this (it should be clearer so that it is harder for the actions to be disclaimed as unfair when they *are* taken). -a On Sat, Jan 23, 2016 at 4:24 PM, wrote: > Issue #12004 has been updated by Jeremy Evans. > > > Since I originally posted my proposal for a CoC, based on PostgreSQL's > draft CoC, PostgreSQL has updated their draft. The current version can > be found at > http://www.postgresql.org/message-id/56A2E9C5.2040707@commandprompt.com. > I think the changes they made to some of the language improves it. As > before, I believe we should remove the parts unrelated to conduct. > Here's my updated proposed CoC: > > ~~~ > =3D=3D Ruby Community Code of Conduct (CoC) =3D=3D > > This document provides community guidelines for a safe, respectful, > productive, and collaborative place for any person who is willing to > contribute to the Ruby community. It applies to all "collaborative > space", which is defined as community communications channels (such as > mailing lists, IRC, submitted patches, commit comments, etc.). > > * Participants must ensure that their language and actions are free > of personal attacks and disparaging personal remarks. > > * Behaviour which can be reasonably considered harassment will not be > tolerated. > ~~~ > > The main changes are: > > 1) Removal of the "disrupt the collaborative space" clause, as that can > more easily lead to selective enforcement. > > 2) It makes clear that it is harassing behavior that will not be > tolerated, instead of people themselves. > > It's also shorter, which is good. > > ---------------------------------------- > Misc #12004: Code of Conduct > https://bugs.ruby-lang.org/issues/12004#change-56562 > > * 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) > > > -- > 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 --047d7b2e4d34dea3c4052a0a95d8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I think that the original Postgres version is better than = your amended one, Jeremy. I think you=E2=80=99ve removed too much. I still = think that it should be clearer about permissible actions for violations, b= ut I also know that Matz is opposed to this (it should be clearer so that i= t is harder for the actions to be disclaimed as unfair when they *are* take= n).

-a

On Sat, Jan 23, 2016 at 4:24 PM, <= ;merch-r= edmine@jeremyevans.net> wrote:
Issue #12004 has been updated by Jeremy Evans.


Since I originally posted my proposal for a CoC, based on PostgreSQL's<= br> draft CoC, PostgreSQL has updated their draft.=C2=A0 The current version ca= n
be found at http://www.postgr= esql.org/message-id/56A2E9C5.2040707@commandprompt.com.
I think the changes they made to some of the language improves it. As
before, I believe we should remove the parts unrelated to conduct.
Here's my updated proposed CoC:

~~~
=3D=3D Ruby Community Code of Conduct (CoC) =3D=3D

This document provides community guidelines for a safe, respectful,
productive, and collaborative place for any person who is willing to
contribute to the Ruby community. It applies to all "collaborative
space", which is defined as community communications channels (such as=
mailing lists, IRC, submitted patches, commit comments, etc.).

* Participants must ensure that their language and actions are free
of personal attacks and disparaging personal remarks.

* Behaviour which can be reasonably considered harassment will not be
tolerated.
~~~

The main changes are:

1) Removal of the "disrupt the collaborative space" clause, as th= at can
=C2=A0 =C2=A0more easily lead to selective enforcement.

2) It makes clear that it is harassing behavior that will not be
=C2=A0 =C2=A0tolerated, instead of people themselves.

It's also shorter, which is good.

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

* 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)


--
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
--047d7b2e4d34dea3c4052a0a95d8-- --===============0134888277== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Unsubscribe: --===============0134888277==--