https://www.writethedocs.org/Blog - Posts tagged vilnius-20192026-01-01T21:13:56.131548+00:00ABloghttps://www.writethedocs.org/conf/vilnius/2019/news/thanks-recap/Conference highlights and thanks to the community!2019-06-12T00:00:00+00:00Write the Docs Team<section id="conference-highlights-and-thanks-to-the-community">
<p>Hey folks,</p>
<p>The Write the Docs team is now emerging from the post-conference
recovery period, and we wanted to send out a quick message to thank
everyone for attending Write the Docs Vilnius.</p>
<section id="conference-recap">
<h2>Conference recap</h2>
<p>Around 50 people attended from over 15 countries, a diverse and enthusiastic crowd.
We had some excellent speakers, some new folks giving lightning talks, an active writing day, and a social.</p>
<p>Overall, we were excited to our awesome community come together in a lovely venue.
Lots of knowledge was shared, and we had a great time.</p>
</section>
<section id="code-of-conduct-transparency-report">
<h2>Code of Conduct transparency report</h2>
<p>As with any Write the Docs event, this conference was covered by our <a class="reference external" href="https://www.writethedocs.org/code-of-conduct/">community Code of Conduct</a>.
We aim to be as transparent with CoC incidents and enforcement as we can.</p>
<p>To ensure that our CoC was visible and accessible, we took a number of specific steps:</p>
<ul class="simple">
<li><p>Every participant agreed to the Code of Conduct in advance during registration.</p></li>
<li><p>The CoC, or a summary, was included on the conference website, conference booklet, and in posters around the conference venue.</p></li>
<li><p>The CoC was repeatedly mentioned in announcements on the stage.</p></li>
<li><p>We specifically stressed that the CoC applies to all conference spaces including the social event.</p></li>
<li><p>We encouraged all attendees to report any incident, even if they were not sure whether it was a violation.</p></li>
</ul>
<p>We had one single CoC event reported, involving a discussion on acceptable ways to address a mixed crowd of people, and an inappropriate example of what isn’t. The incident was resolved on-site.</p>
<p>If there was any personal conduct or other aspect of the conference experience that did not meet the expectations of behavior set out in the CoC, please email us at <a class="reference external" href="mailto:conduct%40writethedocs.org">conduct<span>@</span>writethedocs<span>.</span>org</a>.</p>
</section>
<section id="ready-for-more">
<h2>Ready for more?</h2>
<p>Don’t forget our <a class="reference external" href="https://www.writethedocs.org/conf/prague/2019/">Prague conference</a> in
September, and our <a class="reference external" href="https://www.writethedocs.org/conf/australia/2019/">Australia conference</a> in
November. Tickets are on sale for Prague. The CFP and tickets for the
Australia conference will open soon.</p>
<p>Our Slack network has really grown more this last year. Our general
Slack channel has been extra busy in the days and weeks leading up to
the conference, and we hope that y’all continue the conversations
throughout the year. If you haven’t joined, now’s the time! Check out
the <a class="reference external" href="http://www.writethedocs.org/slack/">Write the Docs Slack</a>.</p>
<p>We’re also looking for more sponsors to make our events just as magical
as this year’s event. You can see our prospectus for
<a class="reference external" href="http://www.writethedocs.org/conf/prague/2019/sponsors/prospectus/">Prague</a>.
Get in touch if you have any questions.</p>
</section>
<section id="thanks-again">
<h2>Thanks again</h2>
<p>We’re so grateful to our sponsors, speakers, volunteers, and attendees
for making this conference possible.</p>
</section>
</section>
Hey folks,2019-06-12T00:00:00+00:00