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

Bryan Housel notifications at github.com
Wed Dec 6 14:26:26 UTC 2017

> I do have one question - who exactly would count as the "community" that any CoC would apply to?

The CoCs all have a "Scope" section.  It will say something like "This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples include blah blah".

_Community_ in this case means everyone who interacts with the `openstreetmap-website` repo in some way.  For example:  It does apply to everyone who opens a PR or an issue.  It doesn't apply to random shouty people on the HOT mailing list or the person who gets too drunk at a mapathon (those spaces should have their own CoCs).

> I mean we're quite unusual in that there's only really two of us currently with any power and who are permanent fixtures capable of having a CoC enforced against them?

I don't think that's unusual, but certainly anybody is capable of having a CoC enforced against them.  Again, CoC is for future abuses, not to deal with anybody currently.  

It's like _unit tests for the community_.  Person A calls person B a racist name? Fail. A is dealt with swiftly and booted.  Having the test in place is useful, even if racist name calling is not currently a problem.  (If your community grows 10x, will it be?)

> the problem is that I don't feel it's up to me to unilaterally impose a particular CoC but I equally don't know how to determine what (if any) we should use.

I would far prefer for you to be a leader and unilaterally impose a CoC that works for you and @gravitystorm than to just wait indefinitely for someone to tell you what to do.  

It's leadership's job to impose it, and then to enforce it once in place.  These are easy but important jobs that you will need to do rarely, compared to the daily grind of writing code and repo gardening.

Not everything in OSM is a democracy.  We don't need to have a working group or a survey to give everyone their input on how much name calling is allowed on a mailing list, or how much ass grabbing is allowed at a conference.

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...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20171206/314353c1/attachment-0001.html>

More information about the rails-dev mailing list