Sparked by a recent NodeJS culture conflict
Curiously, there are also quite a few that do not mention anything about “conduct” in their repos, examples being ThreeJS, Bluebird, and Grunt. Perhaps they’ve never considered or had a problematic conduct but there’s also the more worrying possibility that it is a result of apathy of willful resistance (though I would think less likely).
The issue isn’t with those that advocate, the issue is with those that just don’t care. This mentality whereby a person’s conduct is not meaningful if they are productive and commit good code just isn’t good for a healthy community. Poor behavior allowed to persist will only help to exclude those that it targets. The output of the troublemaker in question is not the issue here, but the community that surrounds it.
Though I personally haven’t had to deal with any gender specific barriers in my career (because I’m just a normal guy), it’s not really hard to see how others face issues. From my inquiries into friends’ experiences, to specific internet findings like the so-called “Feminist Software Foundation”, a satirical but also hateful account who would try to characterize very left feminists by making ridiculous pull requests to popular repositories and arguing when they failed, to a general but hushed air of sexism in a few workplaces I’ve worked in, to the recent “manifesto” released by a Google employee, to the online comments mentioned in The Outline’s article, it isn’t hard to see how these issues persist even with awareness and advocacy. The issue isn’t that non-males output is unfairly decided to be worse; a narrow view of the issue. There issue is instead systematic and based in society. A few bad actors (intentional or otherwise) and many mostly-indifferent bystanders keep certain groups from entering tech whether at interviews, in academics, in childhood development, or other aspects of life/social development. It’s not always explicit yet it’s just behind every door.