All of the members of the [Pocoo Team][1] seem to be white men.

[1]: http://www.pocoo.org/team/#team

Is that a reflection of your hypocrisy? Or the difficulty of recruiting people that are not white men? I'm guessing it's mostly the latter.

You wrote:

> When you start an Open Source project today, in particular one which is further disconnected from frontend technologies there is a very high chance the organic community development will be everything but diverse.

and given the following, from [this comment][2] in this thread, which seems probably true:

> Major open source projects are disproportionately managed and staffed by people with full-time jobs at major software companies, and the process of obtaining and thriving in one of those jobs is not intrinsically color and gender blind, so this argument isn't persuasive.

[2]: https://news.ycombinator.com/item?id=14488000

we should be tempering our judgements of open source projects, e.g. that they're not welcoming to people that are not white men.

I'm confused as to what principle or principles you think should actually be adopted. Should all open source projects reflect the 'diversity' of the entire world?

Consider the following, from [this comment][3] also from this thread:

> LGBT people are overrepresented - almost double their percentage in the general population in fact (7% vs 4%).

[3]: https://news.ycombinator.com/item?id=14488689

Assuming that the above is true, is this a cause for concern? Would you similarly be concerned if it were true that, say, Asian people, or even just Asian men, were over-represented in technology or open source software projects? Is that not a cause for concern for you too?

It sure seems like the only cause for concern is that there are too many white men. Would anyone ever criticize an open source project for not having 'enough white people' or 'enough men', let alone 'enough white men'?

More from your post:

> What's worse is the longer you wait to try to get people involved in the project that would naturally not try to join the harder it will be. When your team is 4 men, the first woman which joins will make a significant impact. When your team is already 20 men you need to get a lot more women on board to have the same impact.

My problem with this is that you're pretty clearly, tho implicitly, devaluing contributors that don't help your project meet your diversity quotas. Your team is six white men. Have you considered replacing your existing members with women or people of color? When someone contacts you, your team members, or other contributors to your projects, do you ask them to identify their race, ethnicity, sex, or gender so you can discourage white men from contributing? If not, don't you realize that every white man that joins your team or contributes to your projects is making your diversity problem worse? You're also implicitly bashing your team members and contributors for being the wrong kind of people because you're telling them that their homogeneity is:

1. "not healthy for a project or a community to lack diversity"
2. Contributing to an "echo chamber"
3. Increasing the difficulty of future diversity
4. Hurting the project because they are relatively bad at "de-escalating arguments in bug trackers and mailing lists"
5. Hurting the project because they are relatively bad at "[taking] care of documentation"
6. They are not "people that make software work in new cultural contexts (localization, globalization, internationalization, etc.)", i.e. they are unable to understand or work with other "cultural contexts".
7. They are not "people that care about user experience"

---

I'm sure you agree with me in thinking that everyone that wants to 'participate in technology' or contribute to an open source project should be able to do so. And moreover, people that don't even realize that they would enjoy contributing to an open source project should be given that knowledge – all else being equal of course.

But that's the key constraint on how much marginal effort should be expended to recruit people that aren't already participating and contributing – all else is not equal. Everything is costly to some degree.

De-escalating arguments in bug-trackers or mailing lists – let alone even participating in arguments – requires time and energy! And there's only a finite supply of either! And opportunity costs are real and pervasive – arguing with people can be satisfying, but it can also be incredibly aggravating!

Writing documentation – and editing it, or maintaining it, or re-organizing it, etc. – requires time and energy! Someone has to do it and for most open source projects that means someone has to voluntarily do it. And this neglects the fact that 'localizing' or 'globalizing' that same documentation isn't even possible unless one knows at least two languages pretty well!

If you're going to "artificially bring balance" to your open source team, your open source project's contributors, or your conference, you're restricting the supply of possible people and thus raising the relative cost of whatever it is that you want done, whether it be writing documentation or providing user support in your issue tracker or mailing list.

I haven't personally observed any significant and unfair obstacles preventing people that are not white men from participating in open source projects, or 'technology' generally. But I'm sure they exist. Let's get rid of them. But first, let's actually identify them, and let's be careful with implying that every group of people that doesn't near-perfectly reflect the demographics of its wider community or country or whatever is guilty of overt racism, sexism, or other discrimination.