[#72745] [Ruby trunk - Misc #11876] [Closed] Scheduled maintenance 2016/01/01 — shibata.hiroshi@...
Issue #11876 has been updated by Hiroshi SHIBATA.
4 messages
2016/01/07
[#72746] Re: [Ruby trunk - Misc #11876] [Closed] Scheduled maintenance 2016/01/01
— Eric Wong <normalperson@...>
2016/01/07
shibata.hiroshi@gmail.com wrote:
[#72824] [Ruby trunk - Bug #11973] IO#advise should raise NotImplementedError on platforms that do not support that call — git@...
Issue #11973 has been updated by Chuck Remes.
3 messages
2016/01/12
[#72954] [Ruby trunk - Feature #12010] [Assigned] Exclude dot and dotdot from Dir#each — naruse@...
Issue #12010 has been reported by Yui NARUSE.
4 messages
2016/01/20
[#72959] Re: [Ruby trunk - Feature #12010] [Assigned] Exclude dot and dotdot from Dir#each
— Eric Wong <normalperson@...>
2016/01/20
naruse@airemix.jp wrote:
[#73313] [Ruby trunk - Bug #12007] [Open] Newly added Unicode data file doesn't get downloaded — shugo@...
Issue #12007 has been updated by Shugo Maeda.
3 messages
2016/01/23
[#73372] [Ruby trunk - Misc #12004] Code of Conduct — benton@...
Issue #12004 has been updated by Benton Barnett.
4 messages
2016/01/24
[#73379] Re: [Ruby trunk - Misc #12004] Code of Conduct
— KOSAKI Motohiro <kosaki.motohiro@...>
2016/01/24
On Sun, Jan 24, 2016 at 5:13 PM, <benton@bentonbarnett.com> wrote:
[#73421] [Ruby trunk - Misc #12004] Code of Conduct — nekocat432@...
Issue #12004 has been updated by Ruby Dino.
6 messages
2016/01/25
[#73425] Re: [Ruby trunk - Misc #12004] Code of Conduct
— Austin Ziegler <halostatue@...>
2016/01/25
I’m sorry, but this, like the code of merit, is merely a derailing tactic.
[#73469] Re: [Ruby trunk - Misc #12004] Code of Conduct
— Martin J. Dürst <duerst@...>
2016/01/26
On 2016/01/26 01:32, Austin Ziegler wrote:
[#73482] Re: [Ruby trunk - Misc #12004] Code of Conduct
— Austin Ziegler <halostatue@...>
2016/01/26
On Tue, Jan 26, 2016 at 12:25 AM, Martin J. Dürst <duerst@it.aoyama.ac.jp>
[#73491] [Ruby trunk - Misc #12004] Code of Conduct — git@...
Issue #12004 has been updated by Chuck Remes.
7 messages
2016/01/26
[#73492] Re: [Ruby trunk - Misc #12004] Code of Conduct
— Andrew Kirilenko <andrew.kirilenko@...>
2016/01/26
They will never provide any numbers because they are not engineers and they
[#73494] Re: [Ruby trunk - Misc #12004] Code of Conduct
— Brandon Weaver <keystonelemur@...>
2016/01/26
Coraline is a panelist on Ruby rogues and a very well respected member of
[#73498] Re: [Ruby trunk - Misc #12004] Code of Conduct
— Andrew Kirilenko <andrew.kirilenko@...>
2016/01/26
OK, sorry for previous comment. Let's try this way.
[#73500] Re: [Ruby trunk - Misc #12004] Code of Conduct
— Austin Ziegler <halostatue@...>
2016/01/26
On Tue, Jan 26, 2016 at 5:15 PM, Andrew Kirilenko <
[#73558] [Ruby trunk - Misc #12004] Code of Conduct — andrew.kirilenko@...
Issue #12004 has been updated by Andrew Kirilenko.
5 messages
2016/01/28
[#73568] Re: [Ruby trunk - Misc #12004] Code of Conduct
— Austin Ziegler <halostatue@...>
2016/01/29
Andrew, please stop digging. Your hole is only getting deeper.
[#73573] Re: [Ruby trunk - Misc #12004] Code of Conduct
— Andrew Kirilenko <andrew.kirilenko@...>
2016/01/29
>Andrew, please stop digging. Your hole is only getting deeper.
[#73586] [Ruby trunk - Misc #12004] Code of Conduct — andrew@...
Issue #12004 has been updated by Andrew Vit.
4 messages
2016/01/29
[#73593] [Ruby trunk - Bug #12034] RegExp does not respect file encoding directive — nobu@...
Issue #12034 has been updated by Nobuyoshi Nakada.
3 messages
2016/01/30
[ruby-core:73581] Re: [Ruby trunk - Misc #12004] Code of Conduct
From:
Andrew Kirilenko <andrew.kirilenko@...>
Date:
2016-01-29 15:24:42 UTC
List:
ruby-core #73581
>So you’ll destroy Ruby’s community with open sexism and racism to save Ruby. Brilliant. It's not me who is raiding open source project with sexist and racist ideas but Coraline + SJWs. If you can't see why their ideas are sexist and/or racist, I can't help you with this, I can only give you hint - racism is not about treating black people differently, it's about treating some one by his race, no matter what it is. Same with sexism - it's not about treating women differently, it's about treating anyone differently by his gender. Also, go and explain me how these famous "women outreach programs" are not sexists? They directly imply that women are not equal to men and need different treatment. >You are wrong. What I don’t have time to do is go through the last fifteen years of the mailing list archives, but you are also artificially limiting the discussion. This is not just about explicit exclusionary tactics (e.g., person A telling person B that their code isn’t acceptable because they are in class C). This is about spaces that are hostile to different classes of people. It’s more person A regularly expressing opinions that people of class C are lesser. It’s about more subtle harassment. It’s also about (and I’ve said this before) signalling that, even if the Ruby core community has not had this problem exhibited prior to this discussion, the people behind the Ruby core community *care enough* to make it clear that such subtle harassment is not welcome. I might be wrong. Show me example(s). >Pretty much anyone who isn’t a racist themselves. One does *not* get to say that someone of a difference race is not viewed “as being fully civilized for the obvious historical reason that she is not” without *legitimately* being called a racist. One does *not* get to say that “a few acid-burned faces [of women] is a small price to pay” and claim that one isn’t sexist. Beale is a hate monger; citing him in support of your argument *harms* any argument you could possibly make (just as citing that known humanitarian J Stalin in favour of a position you hold would diminish that argument). I'm not racist and I don't share your opinion. And I'm not alone. "Pretty much everyone in USA (or ex-USA)", yes, probably, but world doesn't end with USA and Canada. And I really doubt you know anything about known humanitarian J Stalin. My country suffered due to his actions, though he had some good ideas and took some right actions. Same with another known humanitarian, Hitler. No matter what, if some ideas, they believed in, are good it doesn't make them any less good due to these guys being bad. >That’s easy. Matz has expressed concern about having to spend too much time on community management with a CoC in place. As he *is* the BDfL of Ruby, he could choose to delegate community management to other people he trusts. This isn’t about a takeover or Ruby, it is about finding things that can work. And yes, if there *were* a separate organization, I would personally want to make sure that some of the more rational opponents to CoCs in Ruby were involved in the organization so as to protect against the abuses about which they have indicated fear. There is simple solution for that. No code of conduct - no problem of matz spending time on enforcing it and solving disputes. And I have yet to see any example of people being treated differently due to their race/sex/whatever in Ruby community. On Fri, Jan 29, 2016 at 5:43 PM, Austin Ziegler <halostatue@gmail.com> wrote: > On Fri, Jan 29, 2016 at 3:40 AM, Andrew Kirilenko < > andrew.kirilenko@gmail.com> wrote: > >> >Andrew, please stop digging. Your hole is only getting deeper. >> I'd do what I see fit it this situation, thank you. And I'd do whatever >> it takes to protect things I care about (and I do care about Ruby). >> > > So you’ll destroy Ruby’s community with open sexism and racism to save > Ruby. Brilliant. > > >1. You are trying, once again, to derail the conversation with something >> (in this case, the “No Code of Conduct”) that does not actually address any >> of the *very real* problems we have seen presented in the last two weeks. >> >> These problems arrived here with Coraline and her SJW friends for the >> first time within 20 years. If I'm wrong - just show me example of someone >> being treated differently due to his/her race, skin color, sex or whatever >> else not related to technical problem in question. Don't try to fix things >> which are not broken. >> > > You are wrong. What I don’t have time to do is go through the last fifteen > years of the mailing list archives, but you are also artificially limiting > the discussion. This is not just about explicit exclusionary tactics (e.g., > person A telling person B that their code isn’t acceptable because they are > in class C). This is about spaces that are hostile to different classes of > people. It’s more person A regularly expressing opinions that people of > class C are lesser. It’s about more subtle harassment. It’s also about (and > I’ve said this before) signalling that, even if the Ruby core community has > not had this problem exhibited prior to this discussion, the people behind > the Ruby core community *care enough* to make it clear that such subtle > harassment is not welcome. > > So, no, these problems did not arrive with Coraline and her “SJW” friends. > These problems have existed for a very long time and are just now being > called out as unacceptable. Gogaruco had a situation in ’09 that > highlighted the need for Codes of Conduct in general and in specific. > > >> >2. You cited a known hate-monger, Theodore Beale. Mr Beale (aka “Vox >> Day”) has the dubious distinction of being the only person kicked out of >> the SFWA for abuse of an SFWA platform to spread a racist, misogynistic >> message about another SFWA author. All of this weakens any argument you >> might actually have. (If you doubt me, read PZ Meyers on Beale.) >> >> Known by whom? >> > > Pretty much anyone who isn’t a racist themselves. One does *not* get to > say that someone of a difference race is not viewed “as being fully > civilized for the obvious historical reason that she is not” without > *legitimately* being called a racist. One does *not* get to say that “a few > acid-burned faces [of women] is a small price to pay” and claim that one > isn’t sexist. Beale is a hate monger; citing him in support of your > argument *harms* any argument you could possibly make (just as citing that > known humanitarian J Stalin in favour of a position you hold would diminish > that argument). > > >> And please, interpret Coraline's "Thoughts on leaving technical mgmt of >> Ruby to Matz and delegating community mgmt to a separate org?" to me. Thank >> you. >> > > That’s easy. Matz has expressed concern about having to spend too much > time on community management with a CoC in place. As he *is* the BDfL of > Ruby, he could choose to delegate community management to other people he > trusts. This isn’t about a takeover or Ruby, it is about finding things > that can work. And yes, if there *were* a separate organization, I would > personally want to make sure that some of the more rational opponents to > CoCs in Ruby were involved in the organization so as to protect against the > abuses about which they have indicated fear. > > -a > -- > Austin Ziegler • halostatue@gmail.com • austin@halostatue.ca > http://www.halostatue.ca/ • http://twitter.com/halostatue > > > Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> > <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core> > > Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>