News for hackers. Stuff that matters.
Re:Increasing Rust’s Reach by DaiPlusPlus on Wednesday June 28, 2017 @03:42PM (#14657553)
I see it as a way of investigating possible unconscious bias or even hostility towards minorities in the Rust developer community - from easily fixable things such as male-bias in documentation (e.g. examples using male pronouns disproportionately) - to vitriolic sexist and other abuse in chat and forum groups.

Fortunately the Rust community isn't GamerGate, but if we can eliminate those attitudes sooner, then that's in Rust's long-term interests.

Re:Increasing Rust’s Reach by bauerd on Wednesday June 28, 2017 @04:31PM (#14658053)
Can you point to an instance of offensive behaviour towards minorities in the Rust community? I'm not involved in Rust, and I have no strongly held opinions on the topic at hand. However I cannot recall coming across the abuse you describe on GitHub's issue trackers, nor in the IRC channels I frequent, nor somewhere else. Sure, just because I don't notice it doesn't mean it doesn't exist. Same goes for biased wording in the docs.

A common line of argument is that "being more welcoming" will lead to more contributors and thus to more diverse perspectives. Browsing through Rust's documentation and bug tracker alone makes me skeptical of that. I can't find a thing that will turn away someone interested in Rust.

There's definitely sexism in the industry, no question. But I have yet to see someone present numbers of how e.g. their Code of Conduct lead to more contributors. I doubt that any of these undertakings do, unless the project really does have an asshole community. But Rust surely doesn't.

Re:Increasing Rust’s Reach by emilk on Wednesday June 28, 2017 @04:48PM (#14658226)
Some people will simply not engage in a project if there is no set code of conduct for it. The logic presumable being that even if there is no problem now, problem may come in the future, and a agreed upon code of conduct can nip such problems in the bud.
Re:Increasing Rust’s Reach by teacup50 on Wednesday June 28, 2017 @04:54PM (#14658286)
Or create problems, since they give a huge amount of leverage to those interested in dominating others through purely institutional/bureaucratic power games.
Re:Increasing Rust’s Reach by doomrobo on Wednesday June 28, 2017 @07:11PM (#14659390)
Can you point to an instance of this in the Rust project or another comparable community?
Re:Increasing Rust’s Reach by nickpsecurity on Wednesday June 28, 2017 @07:59PM (#14659655)
Rust draws on Coraline Ada's Code of Conduct ("Contributor Covenant") which was straight-up designed to force politics on people. She's aggressively pushed it in as many places as possible so they can ban people later for essentially saying what people like her disagree with in any forum (not just project itself). Here's one mob attack over a Twitter comment that didn't work featuring her with appearance of a Rust team member appearing to throw in some support. At one point, the political attackers set the maintainer up to look like he or she supports pedophiles. Dirty, dirty tactics pushing politics that don't even necessarily represent the beliefs of those they claim to protect. People in minority groups have a wide range of beliefs with many contradicting what these "social-justice warriors" act like they believe. They'll censor them, too, if deemed necessary.

https://github.com/opal/opal/issues/941

I don't follow the Rust conversations enough to tell you anything about what goes on there. That they adopt and enforce a Code of Conduct designed for censorship of non-believers in that cause with a few, strong supporters on the team is enough to worry anti-censorship people. Regardless of Rust project or somewhere else, we opponents block it on grounds of fighting forced compliance with political views with no consensus. Fighting political domination on forums that are supposed to be about tech. That its author has hit many places from Opal to Github means we prefer to block her CoC even more.

Rather have a Code of Merit with clauses for keeping things civil. Minimal to no politics: just project-focused code, docs, and support of people in project-related conversations. That's it.

https://github.com/rosarior/Code-of-Merit/blob/master/CODE_O...

Re:Increasing Rust’s Reach by steveklabnik on Wednesday June 28, 2017 @08:13PM (#14659732)
> Rust draws on Coraline Ada's Code of Conduct ("Contributor Covenant")

I have no idea what you're talking about. Rust's code of conduct is older than the Contributor Covenant, and we've modified it very, very slightly since its inception.

(I also disagree with the rest of your post as well, but that's offtopic and I don't particularly care to discuss it.)

Re:Increasing Rust’s Reach by nickpsecurity on Wednesday June 28, 2017 @09:32PM (#14660089)
Hmm. I may have assumed you used it because it's referenced in your Code of Conduct as source material. Googling it more gives me multiple sources:

1. Node.JS (semi-fitting of my post) and Contributor Covenant (target of my post) per current site.

2. Citizen Code of Conduct per Reddit. Looks just like Contributor with same provision that people must follow the politically-dominant group's rules on every forum or be blocked. It claims to be derived from Django Code of Conduct (partly-political/partly-good) and a feminism wiki. The latter mentions things like "Verbal comments that reinforce social structures of domination" with long list following to be subjectively evaluated according to their politics. Just like my post again.

So, even if your people did one before Contributor Covenant, it's similar to that pushed by the same kinds of people shoving politics down everyone's throat with some of the same content. My post still stands with the correction that you borrowed from different leftist, control-freak politicians initially with minimal modification from the one I mentioned. Each of the source are very clear about their political agenda and intended censorship.

Re:Increasing Rust’s Reach by steveklabnik on Wednesday June 28, 2017 @09:45PM (#14660138)
I had actually forgotten about that citation at the bottom; it was adding two words: "gender identity."
Re:Increasing Rust’s Reach by nickpsecurity on Wednesday June 28, 2017 @10:18PM (#14660286)
Ahh. That got tested on another forum I was on. Painful memory that was a good example of how a huge chunk of the U.S. and many computing pioneers would possibly be censored based on their speech alone.
Re:Increasing Rust’s Reach by Sir_Substance on Wednesday June 28, 2017 @06:12PM (#14658968)
Which is why I go out of my way to avoid projects that feel the need to wave their codes of conduct like flags.

No matter how egalitarian your code of conduct is, there's no substitute for not being a shitty person.

Re:Increasing Rust’s Reach by galangalalgol on Thursday June 29, 2017 @09:42AM (#14663196)
Yes! It is similar to how no amount of software process can protect you from one bad team member. Also, somehow that bad team/forum member always ends up being the person to use those processes or codes of conduct to crush others.
Re:Increasing Rust’s Reach by DaiPlusPlus on Wednesday June 28, 2017 @05:47PM (#14658784)
> Can you point to an instance of offensive behaviour towards minorities in the Rust community?

I cannot, because I haven't investigated to see if it exists or not - hence this exercise :)

Re:Increasing Rust’s Reach by collyw on Wednesday June 28, 2017 @04:04PM (#14657759)
Considering the vast majority of programmers are male, does it really matter if we use male pronouns. What does changing them actually solve? Are women really put off of computing because of that? It all seems so trivial.
Re:Increasing Rust’s Reach by emilk on Wednesday June 28, 2017 @04:11PM (#14657837)
Many small trivial things can add up. Also, if we cater to the status quo ("the vast majority of programmers"), the status quo is less likely to change.
Re:Increasing Rust’s Reach by teacup50 on Wednesday June 28, 2017 @05:04PM (#14658382)
Why is the status quo a problem?

I'm not saying it isn't; I don't know. I just don't see why should we assume that it is.

Re:Increasing Rust’s Reach by nickez on Wednesday June 28, 2017 @05:27PM (#14658624)
Because you don't benefit from half of your population if you only teach men to code. The same applies to other minorities. Of course it is essential that we can get everyone to code so that everyone can contribute in the future when a lot of work will require coding skills.
Re:Increasing Rust’s Reach by dhf17 on Wednesday June 28, 2017 @08:26PM (#14659794)
Frankly, the white male privledge guilt message is getting old. Programming is mostly self taught, through hours of social isolation researching and seeking it out. Short of writing politically neutral docs that focus on the subject at hand, there is no need to evangelize. It seems more arrogant than anything.
Re:Increasing Rust’s Reach by int_19h on Wednesday June 28, 2017 @09:28PM (#14660077)
It's not supposed to be about guilt. It's supposed to be about empathy towards those who don't get that privilege.

(Side note: the word "privilege" is really poorly chosen, because in practice it has a strong implication of blame and guilt assignment in our culture.)

Re:Increasing Rust’s Reach by teacup50 on Wednesday June 28, 2017 @10:37PM (#14660360)
Starting when I was twelve, I worked for multiple summers doing landscaping to buy a computer; mowing yards, hauling wood bark, dirt, laying sod, ripping up sod.

It was hard, sweaty, backbreaking labor, especially for a 12 year old; I did it because I wanted to program. I used that computer to teach myself to program, and got my first real programming job from someone who I'd never previously met in person, over IRC.

According to today's identity politics, I need to be aware of my privilege as a white male nonetheless, and my position on the coarse-grained intersectional hierarchy of privilege.

I'm not really sure what I'm supposed to do with that once aware, or why they get to decide where everyone fits on that hierarchy on the basis of traits they deem important.

Re:Increasing Rust’s Reach by int_19h on Thursday June 29, 2017 @02:46AM (#14661267)
> According to today's identity politics, I need to be aware of my privilege as a white male nonetheless

Yup. That's because as a white male, you are still "privileged".

I'm using quotes here, because, as mentioned earlier, I don't think the word is a good fit for the concept it's supposed to describe. Privilege implies something above and beyond what you are normally entitled to; something that you don't necessarily deserve (I think that's the main reason why it elicits such a strong negative emotional response in people). As a white male, you are not getting such things - you're getting normal treatment, in a sense that no-one is making negative assumptions about your intellect, your ability to learn etc on the basis of your race or gender (they may well be making them based on other traits, and you can be underprivileged on the corresponding other axes). The problem is that others do get negative points solely on account of their gender, color of their skin, or even their name alone (http://www.nber.org/digest/sep03/w9873.html).

So you don't really have a "white privilege", but rather they have a "non-white handicap". It's not your fault - but because of said privilege, you're in a better position to try to correct it somewhat.

> I'm not really sure what I'm supposed to do with that once aware

Try to do what you can to even things out. I'm not even necessarily talking about politics, but just day to day things. Have you ever seen a female colleague being talked over in a meeting in your presence? Try to steer the discussion to give her voice. Ever been on a hiring interview loop, and heard dismissive racial or cultural stereotyping of a candidate based on their name alone ("I wonder if he codes like an Indian" etc)? Point it out. And so on.

Re:Increasing Rust’s Reach by curun1r on Thursday June 29, 2017 @01:02AM (#14660910)
> the word "privilege" is really poorly chosen

The 'white' part is just as problematic. There are many other things that make life hard too. Having a mental illness, for example, or being molested/abused as a child. Yet no one talks about non-mentally-ill privilege or unmolested privilege. Just because skin color is something that can't be hidden when we go out in public doesn't elevate it above all the other difficulties or challenges in life. I've known people from all those groups and would say that depressives, schizophrenics and victims of molest have far more challenges in life than do minorities. Which is not to say that there aren't people who have more than one set of challenges, just that the focus on race and the implication that life is easy for someone who's white is not productive and frustrates people with other legitimate challenges in life.

This is, to me, why many reasonable people have a problem with identity politics. In an effort to bring awareness to the struggles of some, it actually ends up making others feel marginalized and their experiences minimized and is confrontational in nature. Empathy is about envisioning yourself in someone else's situation. The way we do identity politics today, it's the reverse. Instead of the desired, "I imagine myself in your position and I see how hard it must be" it's "I imagined myself in your position and, trust me, it's easier than mine."

I have a parent who is a psychologist. Growing up, I was taught that the right way to handle conflict was to always talk about your personal experience. Saying, "you're being insensitive" is accusatory, controversial and bound to cause an argument. Saying, "I feel unappreciated" is an unequivocally correct statement that can't be argued because no one else can know how you experience something. The only way to sort of refute that is to say, "I don't intend to make you feel that way." The problem with the term "white privilege" is that it's not a personal experience term. It's a term that encapsulates a projection of the white experience from the perspective of minorities. Anyone who doesn't feel they lead a privileged life will instinctively reject it. We need to be using terminology that's in line with the "I feel..." way of expressing oneself...terminology that helps convey the difficulties that some people face rather than the lack of difficulties everyone else faces.

Re:Increasing Rust’s Reach by int_19h on Thursday June 29, 2017 @02:35AM (#14661223)
> The 'white' part is just as problematic. There are many other things that make life hard too. Having a mental illness, for example, or being molested/abused as a child. Yet no one talks about non-mentally-ill privilege or unmolested privilege.

Actually yes, we do talk about that stuff as well. The things that you hear most - racial, gender, wealth and religious privilege - are talked about more simply because they affect proportionally more people.

Re:Increasing Rust’s Reach by nickez on Wednesday June 28, 2017 @05:49PM (#14658800)
> The claim is that only men are taught to code?

At least at the university I went to it is something like 5-10% women in computer science and electrical engineering.

Re:Increasing Rust’s Reach by goodplay on Wednesday June 28, 2017 @06:09PM (#14658942)
The university I attended had females comprise 90% of all students in computer science, and over half of all students in engineering fields. Anecdotes are fun.
Re:Increasing Rust’s Reach by duality on Wednesday June 28, 2017 @05:43PM (#14658761)
The claim is that only men are taught to code?
Re:Increasing Rust’s Reach by barrkel on Wednesday June 28, 2017 @08:54PM (#14659900)
I don't know any good programmers who were taught.
Re:Increasing Rust’s Reach by jhasse on Thursday June 29, 2017 @10:21AM (#14663506)
I would rather say: I don't know any good programmers who weren't self-taught.
Re:Increasing Rust’s Reach by sacado2 on Monday July 03, 2017 @03:55PM (#14690937)
How do you know they weren't taught ?
Re:Increasing Rust’s Reach by douche on Thursday June 29, 2017 @07:37AM (#14662362)
Maybe there's some magical place where you can actually learn how to program from someone else, but for the rest of us, there's no substitute for solitary hours grinding away actually doing the work.
Re:Increasing Rust’s Reach by jlebar on Wednesday June 28, 2017 @06:27PM (#14659081)
Why is the status quo a problem?

I'm not saying it isn't; I don't know. I just don't see why should we assume that it is.

Have a read-through on http://geekfeminism.wikia.com/wiki/Geek_Feminism_Wiki, or any of the other excellent references online.

Re:Increasing Rust’s Reach by jlebar on Wednesday June 28, 2017 @06:26PM (#14659073)
> Are women really put off of computing because [people use male pronouns for programmers, assuming they're male]?

This doesn't need to be a hypothetical question. You could find a woman programmer and ask her. (A woman might even chime in on this thread, although given the ridiculous level of toxicity on this thread, if I were anything other than a het cis white man, I'd be staying the hell away from here.)

Or you could even Google it, and find some woman programmers talking about this. Here are a few references to get you started. https://geekfeminism.org/tag/pronouns/

Re:Increasing Rust’s Reach by DaiPlusPlus on Wednesday June 28, 2017 @05:57PM (#14658852)
> What does changing them actually solve?

By itself not much: but I see it as a necessary-but-insufficient step, in much the same way it is necessary to remove public statues deifying US Civil War Confederate "heroes" (I'd prefer the term "traitor"...).

> Are women really put off of computing because of that? It all seems so trivial.

Not "because of that" directly, no - of course not, but projecting an inclusive image is important to attract people who might not otherwise be interest for fear of not being a "cultural fit" despite having the skills. (Most) people are not robots: there is a very human need to feel accepted and fit-in.

Re:Increasing Rust’s Reach by collyw on Thursday June 29, 2017 @03:18AM (#14661410)
(Assuming that you are a male) would you be in any way bothered if everything was changed to exclusively female pronouns?
Re:Increasing Rust’s Reach by DaiPlusPlus on Thursday June 29, 2017 @04:30AM (#14661635)
I imagine I would feel the same way as the first wave of male nurses would have in the postwar years - with textbooks and instructional materials, even the job titles: Sister and Matron, reflecting a strong female bias.

I quickly went through the Wikipedia article on Men in Nursing just now to write this reply and it's already having me reconsider how I perceived gender bias in industry: https://en.m.wikipedia.org/wiki/Men_in_nursing

Re:Increasing Rust’s Reach by conradev on Wednesday June 28, 2017 @04:38PM (#14658129)
> Are women really put off of computing because of that?

Yes.

Re:Increasing Rust’s Reach by geofft on Wednesday June 28, 2017 @04:43PM (#14658179)
> Considering the vast majority of programmers are male, does it really matter if we use male pronouns.

I'm not following that logic - if a reason to use male pronouns is that current programmers are male, then does it not follow that, yes, it actually matters?

(And if it doesn't matter, why care? Why not let the people who want to use other pronouns use other pronouns?)

Re:Increasing Rust’s Reach by kmicklas on Wednesday June 28, 2017 @05:58PM (#14658862)
Such logic will not convince such sexists, sadly.
Re:Increasing Rust’s Reach by curun1r on Wednesday June 28, 2017 @06:34PM (#14659128)
> a way of investigating possible unconscious bias

There's other ways to address that too. I've used https://textio.com/ in the past for job ads and it's really interesting to see examples of how seemingly minor word choices can land depending on the reader. It'd be a relatively simple task to run documentation, RFCs and Github comments of core team members through such a service and automatically generate a report (which wouldn't have to be released publicly, but could be sent to authors to aid in using more inclusive language going forward).

The thing that's really difficult to do is to be inclusive in a way that doesn't feel exclusive towards people who aren't in the target demographics. Using these types of automated tools doesn't have that downside. Has anything like this been suggested/done by the people working on Rust?