[openstreetmap/openstreetmap-website] Let's adopt the Contributor Covenant code of conduct (#1299)

[DelanoJ84]

@woodpeck In this case, I am involved and have a vested interest. I often use OSM as a reference and am working on a project which will use the API.
The problem I have with the Contributor Covenant is not just its content, but also how the CC seems to consistently be adopted and discussed within communities. While the wording of the CC suggests openness is the primary goal, almost every high-profile adoption was decided among a small number of maintainers and then [communicated to the surrounding community after the fact](https://www.phoronix.com/scan.php?page=news_item&px=FDo-Contributor-Covenant).
This is an anomaly in open source communities since most changes would go under a review of some sort where everyone could have their say, but it is also a good indication of how incongruous the adoption of a CoC can be with its stated aims. With the stated goal of becoming more inclusive and tolerant, the specific CoC that is chosen and the refusal to allow any discussion before, during, or after the fact suggest this is more a political statement than a pragmatic one. A form of this is also reflected when a new user will open a PR to merge the CoC claiming that some sort of harassment problem exists in the specific community, and then a single maintainer with full access will claim the disagreement with this specific PR are evidence that a CoC is needed and merge it. I do not suspect these methods actually help the communities and, as we've seen, not even the creator of the Contributor Covenant cares enough about the content of their CoC to abide by it.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/1299#issuecomment-301326272
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20170514/e49601ac/attachment.html>