They will never provide any numbers because they are not engineers and they
can't even fetch them.

On Wed, Jan 27, 2016 at 12:05 AM, <git / chuckremes.com> wrote:

> Issue #12004 has been updated by Chuck Remes.
>
>
> #433 Kurtis Rainbolt-Greene wrote:
> <i>Done. See: Backlog.</i>
>
> No. NOT done. I've read this entire thread and I haven't seen any
> proponent of a CoC provide a single, solid shred of evidence that a CoC
> will improve the project. There have been plenty of heated opinions flying
> around but very little data.
>
> For it to make sense for the Core team to take on MORE WORK, there should
> be a DEFINED BENEFIT for that choice. And it should be MEASURABLE. We
> apparently have over a dozen projects that have adopted a CoC so there
> should be plenty of data available to make this case.
>
> If you think this Is "done" and has been answered, then I look forward to
> your list of message numbers that lay out this proof.
>
> ----------------------------------------
> Misc #12004: Code of Conduct
> https://bugs.ruby-lang.org/issues/12004#change-56712
>
> * 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 adopted
> by the Ruby community at large, I think it's time that we consider adopting
> 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 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 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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
>
(supressed text/html)
Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>