[ruby-core:73580] Re: [Ruby trunk - Misc #12004] Code of Conduct

From: Austin Ziegler <halostatue@...>
Date: 2016-01-29 14:43:32 UTC
List: ruby-core #73580
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>

In This Thread