[openstreetmap/openstreetmap-website] Let's adopt the Contributor Covenant code of conduct (#1299)
notifications at github.com
Mon Oct 3 17:41:43 UTC 2016
Since there are a few folks in this thread looking for evidence of existing harm, I thought I should address that. The specific harm I’m trying to head off is not some sexually-charged abuse incident on the lists, because that would be a sign we’ve already missed the boat. I’m worried about a harm that’s harder to perceive, the non-participation of people who look for a CoC as a sign of maturity when deciding whether to get involved. We already have CoC’s for in-person events, and [there’s plenty of evidence of people who treat it as a minimal bar to clear, such as John Scalzi’s 2013 campaign](http://geekfeminism.wikia.com/wiki/CoC_Pledge).
Reputations are a pain to change. I rang the bell on this topic a few months ago because I believe that there is strong indication that OSM as an organization is on the wrong path, and that its decisions have rendered it incapable of perceiving this or reasoning about it. Adapting the CoC we already use for in-person events to virtual spaces like code repositories and hopefully other forums would be an important signal that we don’t tolerate the kinds of incidents common to the tech industry in our world-changing, critical project. There is _nothing else_ like OSM; people can’t just pick another conference or worldwide street-scale dataset to contribute to.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rails-dev