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

Bryan Housel notifications at github.com
Tue Sep 27 13:54:19 UTC 2016


> One thing I’d like to see is some description of who’s expected to do the enforcing. For example, does authority for this code comes from the OSMF Board, and do they appoint a moderator for community spaces?

With any code of conduct, normally the project administrators do the enforcement unless stated otherwise.  So this would fall on project admins like @tomhughes, @Firefishy, @gravitystorm, @zerebubuth  to do the enforcement.  

I think they are doing a fine job, and I don't want to force anything on them that they don't want to do..  _("if you are seated in an exit row..")_,  so here are some options:

* If they don't want to do it, or they think codes like this are a bad idea, they can close the issue and reject the PR and my feelings won't be hurt, really 😄.  
* Alternatively, they could adjust the language in the CoC to something that works for them and for this project - totally fine.
* A third option is to say "I like the idea but I'm [too busy | not the right person | uncomfortable with it] ", and maybe ask for someone to step up and take on the responsibility.  Some open source projects (e.g. [Rust lang](https://www.rust-lang.org/en-US/team.html)) split the admin responsibilities into teams where some admins code and other admins triage issues and moderate the community.

Whatever the outcome, I'm glad we're talking about it!  Given [recent requests for help](https://twitter.com/gravitystorm/status/776432549912457216) with openstreetmap-website, I would love to see more people get involved.  


-- 
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-249871569
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20160927/d330aecb/attachment.html>


More information about the rails-dev mailing list