Blog - Posts tagged announcementshttps://www.writethedocs.org/blog/archive/tag/announcements/atom.xml2019-02-11T00:00:00ZABlogImproved Community Code of Conducthttps://www.writethedocs.org/blog/new-community-coc-2019/2019-02-11T00:00:00Z2019-02-11T00:00:00ZWrite the Docs Team<div class="section" id="improved-community-code-of-conduct">
<p>We aim to make Write the Docs an incredibly diverse, friendly, and inclusive community. As part of that effort, we have a community <a class="reference internal" href="../../../../code-of-conduct/"><span class="doc">Code of Conduct</span></a>. We have refactored and improved our existing Code of Conduct, based on improvements and lessons in our own and other communities. In this post, we list some of the more significant changes.</p>
<p>We have added:</p>
<ul class="simple">
<li>An explanation of the fundamental goals we have with a CoC.</li>
<li>Clarification on cases where the CoC can apply during conferences, even for events not on the conference agenda.</li>
<li>A short guideline on reporting. Community members are now more strongly encouraged to report incidents, even if they are unsure whether it is a violation or not. This is also reflected in the CoC in other places.</li>
<li>Clarification on who to report to in which spaces, how a report can be escalated, and which people are in which response team.</li>
<li>An explicit policy regarding venue security or law enforcement involvement. They should not be involved without consent of the affected person(s), except if there is no other reasonable option given significant safety risks.</li>
</ul>
<p>We’ve updated:</p>
<ul class="simple">
<li>The list of examples of harassment and exclusionary behaviour, to provide more clarity on what can fall under this.</li>
<li>The <a class="reference internal" href="../../../../code-of-conduct-response/"><span class="doc">Code of Conduct Response Guide</span></a> to provide better guidance to people in CoC response teams in different community spaces, how to work as a team, deal with conflicts of interest, handling public statements, and how to decide on a response.</li>
</ul>
<p>All Write the Docs meetups are now required to adopt the Write the Docs community <a class="reference internal" href="../../../../code-of-conduct/"><span class="doc">Code of Conduct</span></a>. A <a class="reference internal" href="../../../../code-of-conduct-shortform-meetups/"><span class="doc">short form CoC is available for meetups</span></a>, which needs to be included in the Meetup description in full. Organisers are the first point of contact for reports of Code of Conduct incidents at meetups, should read the <a class="reference internal" href="../../../../code-of-conduct-response/"><span class="doc">Code of Conduct Response Guide</span></a> carefully, and use it as a reference when an incident is reported.</p>
<p>Please take a moment to review the <a class="reference internal" href="../../../../code-of-conduct/"><span class="doc">Code of Conduct</span></a>. As with any of our community documentation, we welcome feedback and contributions. We’d also like to thank the <a class="reference external" href="https://2018.djangocon.eu/conduct-response/">Djangocon Europe 2018 team</a> for inspiring a large portion of our updated code of conduct.</p>
<p>If you have any questions about these changes or CoC processes in general, feel free to contact <a class="reference external" href="mailto:conduct%40writethedocs.org">conduct<span>@</span>writethedocs<span>.</span>org</a>.</p>
</div>
New and Improved Community Code of Conducthttps://www.writethedocs.org/blog/new-community-coc/2017-02-22T00:00:00Z2017-02-22T00:00:00ZWrite the Docs Team<div class="section" id="new-and-improved-community-code-of-conduct">
<p>Greetings documentarians! As you know, Write the Docs is an incredibly diverse, friendly, and inclusive community. We continually encourage and support safe spaces in our events and online platforms.</p>
<p>To that effect, we recently refactored and expanded our <a class="reference internal" href="../../../../code-of-conduct/"><span class="doc">Code of Conduct</span></a> to accommodate for the increased interaction that our community members have with each other and with folks outside our community when communicating on behalf of Write the Docs.</p>
<p>This updated code of conduct aims not only to deliver a more accurate definition of the principles which we believe in, but also to establish which spaces are considered official community spaces, what might be considered a violation, and what to do in case you need to report a violation.</p>
<p>In addition to the expanded code of conduct, we included a reporting guide with guidelines on how to submit a report and what to expect after submitting a report.</p>
<p>And lastly, we refactored our <a class="reference internal" href="../../../../code-of-conduct-response/"><span class="doc">Code of Conduct Response Guide</span></a> to cover handling reports in all of our community spaces, and to make sure that we follow a consistent and transparent approach in handling these reports.</p>
<p>Please take a moment to review the <a class="reference internal" href="../../../../code-of-conduct/"><span class="doc">Code of Conduct</span></a>. As with any of our community documentation, we welcome feedback and contributions. We’d also like to thank the <a class="reference external" href="https://www.djangoproject.com/conduct/">Django Project Code of Conduct</a> for inspiring a large portion of our updated code of conduct.</p>
<p>And remember - Be excellent to each other!</p>
</div>