<p>We adopted a <a href="https://github.com/gravitystorm/openstreetmap-carto/blob/master/CODE_OF_CONDUCT.md">code of conduct</a> with osm-carto. In doing so I came to the conclusion that there is no one size fits all code of conduct and the one chosen needs to fit the problems encountered, size of project, and norms of behaviour of the project. For example, we had problems with derailing of discussions so needed a code that would cover that. We ended up with one based on the Go code, with reporting modified for our small project size.</p>

<p>See <a href="https://github.com/gravitystorm/openstreetmap-carto/pull/2289" class="issue-link js-issue-link" data-url="https://github.com/gravitystorm/openstreetmap-carto/issues/2289" data-id="171815367" data-error-text="Failed to load issue title" data-permission-text="Issue title is private">gravitystorm/openstreetmap-carto#2289</a> for my thoughts at the time.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/1299#issuecomment-249624532">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLUNbZxz93i1ojoQundpd1Vlbxsa6ks5qt_T6gaJpZM4KGrKS">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABWnLREsHZT8UhhTvmpz6QTIJQY54FK5ks5qt_T6gaJpZM4KGrKS.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/openstreetmap/openstreetmap-website/issues/1299#issuecomment-249624532"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/openstreetmap-website","title":"openstreetmap/openstreetmap-website","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/openstreetmap-website"}},"updates":{"snippets":[{"icon":"PERSON","message":"@pnorman in #1299: We adopted a [code of conduct](https://github.com/gravitystorm/openstreetmap-carto/blob/master/CODE_OF_CONDUCT.md) with osm-carto. In doing so I came to the conclusion that there is no one size fits all code of conduct and the one chosen needs to fit the problems encountered, size of project, and norms of behaviour of the project. For example, we had problems with derailing of discussions so needed a code that would cover that. We ended up with one based on the Go code, with reporting modified for our small project size.\r\n\r\nSee gravitystorm/openstreetmap-carto#2289 for my thoughts at the time."}],"action":{"name":"View Issue","url":"https://github.com/openstreetmap/openstreetmap-website/issues/1299#issuecomment-249624532"}}}</script>