[openstreetmap/openstreetmap-website] Let's adopt the Contributor Covenant code of conduct (#1299)
notifications at github.com
Mon Oct 3 09:30:47 UTC 2016
2016-10-02 20:02 GMT+02:00 migurski <notifications at github.com>:
> There’s another reason to adopt a CoC in the absence of demonstrated
> abuse: people looking to join new projects or attend new conferences are
> starting to cite one’s existence as a minimal bar to clear, and in many
> cases skipping participation.
This seems again culturally dependent. Just put your favorite CoC here
https://openstreetmap.us/community/ in a visible way, and people looking
for it can see how mature OSM is. People I have talked to about OSM were
always measuring the maturity of OSM by the quality of our data, not the
bureaucracy created around it.
> Just things you do because they’re what serious projects do now
+1 to Matt here: popularity doesn't mean something is good
> “Sexualized language”? So basically even something as harmless as saying
> “Fuck!” is outruled?
> Whether it’s harmless depends on the context. Saying “Fuck!” when
> frustrated is common enough that it’s lost its sexualized meaning. Using
> the term to describe actual sexual imagery is inappropriate.
I tend to agree, although there's not so much if not almost no sex at all
in OSM, as far as I am aware of. The only ever sexually connected topic I
can remember is a short exchange about this:
And it is only sexually explicit if you adhere to certain practises,
otherwise it could be seen as simple brand humiliation ;-)
> Writing this down in a document makes it possible to have a conversation
> about whether something qualifies. Currently, the Powers That Be have
> decided that any form of direct discourse is acceptable, which has the
> effect of turning away valuable potential participants before they even
> make it into our various discussion forums.
can you give any real examples where this happened, from our lists,
especially the international ones (talk, dev, tagging)? Can you explain how
a CoC would have helped to deal with these occasions better than how it was
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