ruby-core

nobu@ruby-lang.org wrote:

sgharms@stevengharms.com wrote:

shibata.hiroshi@gmail.com wrote:

shibata.hiroshi@gmail.com wrote:

On Sun, Jan 10, 2016 at 5:26 PM, <git@chuckremes.com> wrote:

I can't seem to reproduce the problem with array_bug.git on my end.

I haven't found this behaviour surprising at all. Maybe it痴 because I'm

git@chuckremes.com wrote:

tenderlove@ruby-lang.org wrote:

I always recommend pointing stderr to a regular file using

coraline@idolhands.com wrote:

A code of conduct is totally reasonable (personally I dislike the idea),

I invite everyone to read this blog post, which is about the topic on hand:

bascule@gmail.com wrote:

Alternative patch which is stronger to help the case where I have

pat@freelancing-gods.com wrote:

naruse@airemix.jp wrote:

log:

On Wed, Jan 20, 2016 at 11:45 AM, <fred_h@bootstrap.me.uk> wrote:

> About the CoC text, he definition of "Project maintainers" is not clear in the Ruby project yet.

On 21/01/2016 8:38 PM, <ka8725@gmail.com> wrote:

On Thu, Jan 21, 2016 at 7:34 AM, <nekocat432@yahoo.com> wrote:

On Thu, Jan 21, 2016 at 8:26 AM, <git@chuckremes.com> wrote:

Regarding r53642, how about we limit the symbols to just :r/:w/:rw?

matz@ruby-lang.org wrote:

merch-redmine@jeremyevans.net wrote:

naruse@airemix.jp wrote:

naruse@airemix.jp wrote:

merch-redmine@jeremyevans.net wrote:

Matz, I respectfully disagree. Enforcement should be written in a CoC to be

I think that the Code of Conduct that Jeremy wrote is great. I like it so