<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sasha Romijn on Medium]]></title>
        <description><![CDATA[Stories by Sasha Romijn on Medium]]></description>
        <link>https://medium.com/@mxsash?source=rss-601be8399b48------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Sasha Romijn on Medium</title>
            <link>https://medium.com/@mxsash?source=rss-601be8399b48------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:12:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mxsash/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What network engineers need to know about software engineering]]></title>
            <link>https://medium.com/swlh/what-network-engineers-need-to-know-about-software-engineering-8eb98e11ae1?source=rss-601be8399b48------2</link>
            <guid isPermaLink="false">https://medium.com/p/8eb98e11ae1</guid>
            <category><![CDATA[network-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Sasha Romijn]]></dc:creator>
            <pubDate>Mon, 09 Dec 2019 11:55:51 GMT</pubDate>
            <atom:updated>2019-12-10T16:56:14.621Z</atom:updated>
            <content:encoded><![CDATA[<p>With the increasing use of automation and overlap between roles, many network engineers will end up writing software, or likely already have. If you write a bash script to automate something, you are a developer and that means you can benefit from learning how to do it right.</p><p><em>Originally written for </em><a href="https://labs.ripe.net/Members/sasha_romijn/what-network-engineers-need-to-know-about-software-engineering"><em>RIPE Labs</em></a><em> and the </em><a href="https://blog.apnic.net/2019/12/09/what-network-engineers-need-to-know-about-software-engineering/"><em>APNIC blog</em></a><em>, based on my </em><a href="https://ripe79.ripe.net/archives/video/167/"><em>RIPE 79 presentation</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xLGseClxRwNopy5t" /></figure><p>I have seen plenty of cases where some person wrote some code ages ago, left the organization — leaving nobody knowing how the code works — and it became a business-critical component, that nobody dares to touch.</p><p>Good development practices will reduce dependencies on poorly written code, make it easier to adapt to changes, and make you less dependent on individual people. Here are few places to get started. I also covered all of these points in more detail in my <a href="https://ripe79.ripe.net/archives/video/167/">RIPE 79 presentation</a>.</p><h3>Use version control</h3><p>The first step towards better coding practices is to use version control. It allows you to track changes to the code over time, which is essential when someone needs to do some software archeology.</p><p>Common choices today are git or mercurial. Older choices, that I do not recommend, are subversion, CVS or RCS.</p><p>Git, mercurial and RCS can be used offline, so you don’t even need a network connection or any kind of server. If you don’t know what to learn, learn Git — it’s wide use in open source makes it an incredibly useful skill.</p><p>If you use Git, you can consider hosting your code on GitHub, as it gives you a lot of integration options. There are other hosting platforms as well, such as GitLab, and they all allow you to keep your code private.</p><p>Git only requires you to know a few commands to get started:</p><pre>#set the right author name/email (once)<br>git config --global user.name &quot;full name&quot;<br>git config --global user.email &quot;name@example.com&quot;</pre><pre>git init        # make a git repo<br>git add .       # add all current files<br>git commit -a   # commit all changes (editor opens)<br>git push   # if you want to push changes (not required)</pre><p>Now you’re using version control! You can continue to use Git add/commit/push when you make changes. Just remember to write commit messages that are useful in the future.</p><p>Tools such as Git have a lot of useful but complex other features, like rebasing, commit amending, and undoing commits. You don’t need to know these when you get started. The above is all you need to have a project in version control.</p><h3>Write tests</h3><p>Second, and perhaps most important, is to write tests. Having tests will save time in development, reduce the amount of errors, and give you confidence with making changes.</p><p>Big projects sometimes have complex test suites — one of my current projects, <a href="https://github.com/irrdnet/irrd4">IRRDv4</a>, has almost 5,000 lines of code just for tests. But you can start small, for example, with a single integration test. Most languages have built-in or third-party libraries that help you to build a test suite. You can even write tests for your bash scripts.</p><p><em>Integration tests</em> essentially cover how the system works as a whole. This is opposed to <em>unit tests</em>, which test smaller individual parts. You may not need unit tests to start with. In larger projects, the distinction is helpful because in small fast tests, it’s cheap to run through lots of different scenarios, and only test the fundamentals in integration tests. Note: not everyone uses exactly the same definitions for test scope.</p><h4>Tests should cover weird scenarios</h4><p>A classic pitfall in testing is to only cover the ‘happy path’ — the scenario that occurs if everything goes well. For IRRDv4, the tests I wrote included:</p><ul><li>What if someone submits a PGP signed message but includes additional content that is not part of the signed content?</li><li>What if someone submits an inetnum object, which can only have IPv4 data, but the key mixes IPv4 and IPv6 addresses?</li><li>What feedback does the user get if the parser encounters an internal error somehow, and what log messages are generated?</li></ul><p>If you discover a bug, write a failing test for it, then fix it. You can have more confidence that you have fixed the bug, and you can be sure it can’t reoccur in the same way.</p><p>In small projects and scripts, a single test may be all you need. Once things grow, you may need a bit more work to design your tests. But even a single test can make an enormous difference. For IRRDv4, my 10,000-line project that was deployed early this year, only two actual bugs were found after deploying into production, in part because I wrote rigorous tests.</p><h3>Work on readability</h3><p>Most code is read more often than it is written, so a little extra time to improve it while writing will save you and others time in the end.</p><p>In general, ask yourself how clear this code will be in a year to yourself or someone else, even if you think this script will only be used for a few months. In the last decade of doing this work, I’ve never seen “it’s just for a few months” hold up.</p><p>A good example is one letter variable names. These are absolutely awful — recently I spent half an hour trying to decode how something worked, because someone had used multiple one letter variable names without context, with the variables’ meanings changing at different places in the same function. A few minutes of work when it was written would have improved this.</p><p>Software engineers can have differing opinions about comments in code. I like to use the rule that comments are useful for the how or why, but not the what. For example, explaining that some unusual behaviour is needed to work around a browser bug can be very helpful. But if I find myself wanting to comment what something does, I should probably make the code clearer, which is possible in almost all cases.</p><h3>Refactor</h3><p>In software engineering, refactoring means to restructure something without changing the behaviour. Sometimes you do it because you made a bad decision in the past, or because business requirements changed. It happens in short cycles, where I review and often slightly refactor all code right after writing it, but also happens in longer cycles, when you are expanding to support new features years later.</p><p>Refactoring is an essential part of the lifecycle of software, exponentially so as software gets larger or more complex. As an example, in IRRDv4 I chose a framework to handle process management and socket handling, and it turns out it’ll create problems with future development. I’m going to have to take that out and replace it with something new, initially having the same functionality.</p><p>Again, tests are essential for refactoring, because you can only make large internal changes if you are not afraid of changing things. This is another reasons why tests are a hard requirement for me when writing code — the need for refactoring is inevitable. And especially with larger refactoring projects, things can break in unexpected ways in unexpected places — which is not a problem, as long as you know.</p><h3>Don’t get attached</h3><p>Being able to refactor also means you can’t get too attached to your own code. I often see this in newer developers; people being too attached results in seeing code like this:</p><pre># XXX We don&#39;t use this function anymore<br># &lt;300 line function from 4 years ago&gt;</pre><p>or:</p><pre># I think this is broken so I&#39;ve disabled it<br># &lt;10 lines of gibberish with syntax errors&gt;</pre><p>Nobody will ever benefit from leaving things like that in the code.</p><p>Recently I worked for two full days on a feature and then threw everything away because my approach was entirely wrong, and I got stuck. That’s not fun, but on the way, I did realize what was the right approach, and this is a normal part of writing code — sometimes this happens a year after you wrote the original code.</p><h3>Write documentation</h3><p>All software needs documentation. Even the tiny script that generates some statistics, or just translates one data format to another. Key questions that the documentation should answer are:</p><ul><li>What does this do?</li><li>What problem does it solve? Why did we write it?</li><li>Who wrote it?</li><li>How does it interact with other components?</li><li>What are the known limitations?</li><li>Is there more documentation, and if so, where?</li></ul><p>A good place to start, which is often enough for tiny projects, is a README that answers those questions. If you want to learn more about writing good documentation, I recommend watching ‘<a href="http://preview.pyvideo.org/djangocon-europe-2019/docs-or-it-didnt-happen-with-qa.html">Docs or it didn’t happen</a><a href="http://preview.pyvideo.org/djangocon-europe-2019/docs-or-it-didnt-happen-with-qa.html">‘</a>.</p><h3>Know your limitations</h3><p>Even with all these tips, if you have limited experience or mentoring, there are limits to what projects you can execute successfully. In the same way that I have enough network engineering experience to set up BGP peering, if I were in charge of a large network everyone would have a bad time.</p><p>Recently, a client reported a bug and submitted a patch to fix it. The patch changed one line in one file. It fixed the bug in the right place, in the best way, and was entirely correct. But the fix I ended up applying changed 17 lines in 3 files. I looked for other places where the same issue may exist and found one other potential issue. Because it was a bug, I felt it should have a test to ensure the correct behaviour. And as its behaviour had changed, that required a sentence in the documentation.</p><p>The key to these kinds of differences — that show even in a very simple patch — is experience.</p><p>There is more to this than I can cover in one post, but we’ve covered important fundamentals, which I think will give you a good start. If you have more questions about any of these tips, or other questions, feel free to contact me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8eb98e11ae1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/what-network-engineers-need-to-know-about-software-engineering-8eb98e11ae1">What network engineers need to know about software engineering</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build a better alcohol culture at your tech conferences and events]]></title>
            <link>https://medium.com/@mxsash/how-to-build-a-better-alcohol-culture-at-your-tech-conferences-and-events-9e1cce7179c0?source=rss-601be8399b48------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e1cce7179c0</guid>
            <category><![CDATA[alcohol]]></category>
            <category><![CDATA[code-of-conduct]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[alcoholism]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Sasha Romijn]]></dc:creator>
            <pubDate>Mon, 25 Jun 2018 08:12:46 GMT</pubDate>
            <atom:updated>2024-06-08T09:31:33.537Z</atom:updated>
            <content:encoded><![CDATA[<h4>Most events in tech involve alcohol at a social event. Although it can be a social lubricant, it’s also a catalyst for bad behaviour, Code of Conduct violations, harm, and exclusion. How do you build a better alcohol culture at your event?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0i-Iaz-fWjfM_Q_f" /></figure><p><strong><em>Content warning: this article talks about excessive alcohol consumption and subsequent harassment, assault, addiction and similar concepts — though without great detail on individual occurrences.</em></strong></p><p>Travelling to many conferences, I go to quite a few social events and speaker dinners. As far as I can remember, 100% of them involved alcohol. I do enjoy drinking moderately from time to time, and I see how alcohol can make social interactions between strangers a little bit easier. But at the same time, excessive alcohol consumption is fairly common. The consequences can range from harassment to creating a space that is only enjoyable if you happen to be rather drunk yourself.</p><p>Concerns about these behaviours <strong>scare people away</strong> from these events, and conferences as a whole. And at an average 300 person conference, you will also have ~<strong>30 people with a history of alcohol or other substance abuse. </strong>In the end, events with alcohol aren’t always a bad thing, but creating a space where alcohol is allowed, but excessive consumption is discouraged, and people who drink barely or not at all (whatever the reason) feel welcome, requires specific effort.</p><p>If you’d like to understand more about alcohol addiction, recovery, and alcohol culture in tech, I strongly recommend Tim Allen’s stellar DjangoCon US 2016 talk: <a href="https://www.youtube.com/watch?v=lyVHKTGjivo">It is Darkest Before Dawn</a>.</p><h3>What we are trying to achieve</h3><p>There are a number of goals with a good alcohol policy:</p><ol><li>Make people who do not drink alcohol feel welcome, and feel like this can be a fun event for them. They may not drink due to current or past addictions, pregnancy, medical reasons, because they just don’t like it, or anything else.</li><li>Make people who have poor experiences with being around drunk people feel like this event is safe.</li><li>Reduce the amount of attendees who get drunk, as they more often cross boundaries of acceptable behaviour.</li><li>Be able to act against drunk people.</li></ol><p>These goals all complement each other. Having non-drinkers in a group, or people who at some point decide to stop drinking, can significantly reduce the total alcohol consumption. Having a single person in a group that orders a non-alcoholic drink, makes it much easier in a social context for others to switch to non-alcoholic drinks as well. And avoiding factors that push people towards getting drunk, can make recovering alcoholics feel a bit more welcome.</p><h3>When I consider someone “drunk”</h3><p>In this article, I am defining drunk as a person who has consumed alcohol to the point that they are no longer a <strong>reasonable functional human with reasonable acceptable behaviour</strong>. That includes people who talk without understanding their words have impact, or who have no filter for their words, but also people that can no longer function physically.</p><p>Over the years, I’ve experienced drunk attendees that just shouted really loud and were impossible to talk to, people that passed out, people making awful jokes about minorities and marginalised groups (really common), and one recent time an attendee appeared to try to set another attendee on fire. These situations were all caused by excessive alcohol consumption.</p><p>In general, <strong>drunk people are only fun to spend time with if you are at least somewhat drunk yourself</strong>, and often just really annoying if you’re sober — at best.</p><h3>The easiest solution</h3><p>The simplest solution is often easy to implement: <strong>do not allow any alcohol at your event</strong>. This is difficult if you’re in a public bar, but in almost any other venue you can easily organise a non-alcoholic event.</p><p>However, some people feel that would be pushing too far, or think their community would respond very poorly. So in the remainder of this article, I’m going to work from the assumption that you want to allow some alcohol consumption, but prevent or strongly reduce the issues that come with it.</p><h3>Inclusion comes from many angles</h3><p>The first thing you need to be aware of, is that this involves many different actions, which are all needed as part of an inclusive program. It requires <strong>consistent messaging, appearance and enforcement</strong>, from long before the event, during the day and evening, and afterwards. Adopting only a few of these recommendations may have a very limited effect.</p><h4>Reasonably sober organisers available all night</h4><p>In order to do all of the below, you need to have <strong>reasonably sober organisers available until the end of your event</strong>. Reasonably sober to me means drinking is not entirely forbidden, but it can’t impair your judgement or ability to respond to issues. A good guideline is probably the legal limit for driving a vehicle.</p><p>This does not have to apply to all organisers —<strong> you do need at least two</strong>. These two people need to deal with any incidents, and also in general keep an eye on the people at the party, and on whether people seem to be mostly comfortable.</p><p>Other organisers should also not drink excessively: <strong>all organisers are providing an example to others</strong>, and the attendees will follow their example to know what is acceptable at your event.</p><h4>Alcohol should not be the default or better drink</h4><p>Alcohol should never appear as the default, or as the fancier drink. This means that getting any non-alcoholic drink should be at least as easy as getting an alcoholic drink, and non-alcoholic drinks should be at least as varied or fancy as alcoholic drinks.</p><p>This means <strong>you can’t host at venue which has beer taps on the tables</strong>. That would make alcohol instantly accessible, whereas non-alcohol requires getting the attention of waitstaff. Similarly it means you can offer fancy cocktails, <strong>as long as you offer an equal variety of non-alcoholic cocktails</strong> (often called mocktails or virgin cocktails, but I especially dislike the latter term). And if you have a dozen fancy craft beers, offer more variation in non-alcoholic drinks than coke and water. At one party I organised, we had such fancy non-alcoholic cocktails that they were really popular, just because they looked amazing and tasted great.</p><p>The name of an event can also make it sound like alcohol is the default — and non-drinkers aren’t welcome. So names like <em>GoBeers</em> or <em>SwiftCocktails</em> are exclusionary (I made these names up).</p><h4>Make sure people eat</h4><p>People get drunk much faster if they have an empty stomach, so this enlarges all the problems with alcohol. Make sure people eat before your event, and communicate that clearly, or make sure initial food is available very shortly after people may start drinking. <strong>Offering alcohol at the end of a conference day, without food, or offering alcohol during the conference day, is a recipe for attendees getting drunk very fast.</strong></p><h4>Easy access to water</h4><p>Offer easy access to water, which means people shouldn’t have to order it at the bar. Have bottles of water with glasses on the bar, along with a sign to encourage people to take some, or have a water station somewhere else. Making water the easiest drink to access increases consumption, reducing the effects of alcohol and the amount of alcohol consumed. As a bonus, it helps against dehydration.</p><h4>No unlimited free alcohol</h4><p>Unlimited free alcohol dramatically increases consumption. And I’m counting “drinks on us until our budget runs out” as fairly unlimited, as it doesn’t include a personal limit. Here’s some alternative ideas, to both counter this problem, and shift consumption to non-alcoholic drinks in general:</p><ul><li>Give all attendees a small amount of tokens (two to four), where one token buys a soft drink, two tokens buy beer or wine. Anything more is at their own cost.</li><li>Provide free non-alcoholic drinks (probably up to a maximum budget), and have people pay on their own for alcoholic drinks.</li><li>Give all attendees a limited amount of tokens, which only work for paying for non-alcoholic drinks.</li></ul><p>You could also mix some of these options.</p><h4>On tolerance for drunkenness</h4><p>You can consider a <strong>zero tolerance policy for drunkenness</strong>. Even if a drunk person (per my definition earlier in this article) has not violated the Code of Conduct directly, they are at a seriously increased risk of causing an incident. Even if they don’t, drunk people are nearly always an annoyance to people who don’t drink, or don’t drink as much, up to the point that those people leave. For me personally, leaving an event early due to annoying drunk people is quite common.</p><p>A lighter alternative, if you feel no tolerance is too harsh, is to <strong>cut people off alcohol if you notice them being drunk</strong>. If you, being the organisers, consider a person drunk, you could tell them that they are not to drink any more alcohol, and keep an eye on them. That way, they at least won’t continue to escalate their behaviour. If they violate this and order alcohol anyways, you could make them leave the party.</p><p>Make sure your Code of Conduct has space for these scenarios. And note that you don’t have to ban a drunk person from the entire conference: an appropriate response could be that they have to leave the party, but can come back the next day, and the issue will be further discussed once they’re sobered up. If something more serious has happened already, stronger action can be appropriate.</p><h4>No tolerance for pushing others to drink</h4><p>With drinking alcohol as a social behaviour, it’s common for people to <strong>push others to drink, or drink more</strong>. This behaviour gets worse as the group gets more intoxicated, and often involves demanding reasons on why someone doesn’t drink, or pushing alcohol drinks into their hands anyways.</p><p>This makes the event extremely unwelcoming for people who don’t drink, even if it’s packaged in the form of a “joke”. Particularly when others demand to know why they don’t, as these reasons can be very personal and very sensitive. This behaviour is also a <strong>major cause for excessive drinking</strong> by people who usually drink responsibly.</p><p>If you <strong>notice someone pushing another person to drink</strong>, I recommend speaking to them and explaining them that this is unacceptable and demand they allow others to make their own choices. On repeat occurrences, removing someone from the party is warranted.</p><p>You should also communicate this to the bar staff. They should not assume people want alcohol, and not offer people a beer unless they’ve asked for it. Their question should simply be a neutral: <strong>“what can I get you?”</strong> or something like that.</p><p>If someone <strong>lies to or misleads</strong> someone about the alcohol content of a drink, in a situation where they should reasonably have known, that is (attempted) <strong>physical assault</strong>. It should be treated no differently from any other poisoning attempt, including a permanent ban for the offender. Depending on the needs and wishes of the person who was harmed, you may need to involve medical aid, and should offer to assist in involving the police.</p><h4>Get your partners and sponsors on board</h4><p>Make sure all partners (which includes the venue) and sponsors are on board with all of this. They can not advertise with <strong>“join us tonight and get drunk at our cost!”</strong>. They need to understand your approach to events and alcohol, and if needed, you must enforce that they follow along with it.</p><h3>Clear and consistent communication</h3><p>In general, your communication about all of the above must be clear, consistent and repetitive.</p><ul><li>Never use the word “drunk” in a positive or encouraging way.</li><li>Every time you say the words “drinks” or “alcohol”, or any alcoholic drink name, stress that there is a variety of non-alcoholic drinks, and pushing others to drink is not acceptable.</li><li>Stress that intoxication is never an excuse for Code of Conduct violations.</li><li>Do not give away alcohol as any gift or prize in any part of the conference.</li><li>If possible, on your website, include information about recovery meetings — <a href="https://2017.djangocon.us/venue/#accessibility">like Djangocon US</a>.</li></ul><p>Continuously stress your Code of Conduct, including policies you have about drunk behaviour. Make sure your CoC contacts are known, all your organisers are trained, and make a phone number and e-mail address available. People are often reluctant to report a situation, so keep an eye out yourself as well.</p><p>Even as someone who enjoys responsible drinking, I very often see the exact opposite of each of the points above, and it always leads to the same kind of event — like clockwork. I’ve warned organisers about this in the past, and then saw the event play out exactly like I told them would happen. Some people get very drunk, lose all sense of boundaries, and I leave with a sour feeling. For many people, this image and related issues are reasons not to attend at all in the first place, or even avoid entire conferences. This affects marginalised groups more than others, as they are more likely to be harmed.</p><p>The pervasive drinking culture in tech causes exclusion, biased towards people with less privilege. It causes harm and increases the risk of addiction. But we can do better, and you can be a part of that. If you’re organising any kind of event or conference, please consider how you <strong>have an opportunity to make this a better space for everyone</strong> by building a better alcohol culture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e1cce7179c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How and why we improved DjangoCon Europe’s Code of Conduct]]></title>
            <link>https://medium.com/@mxsash/how-and-why-we-improved-djangocon-europes-code-of-conduct-8c203eb591ee?source=rss-601be8399b48------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c203eb591ee</guid>
            <category><![CDATA[djangocon]]></category>
            <category><![CDATA[code-of-conduct]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[django]]></category>
            <dc:creator><![CDATA[Sasha Romijn]]></dc:creator>
            <pubDate>Mon, 07 May 2018 12:09:46 GMT</pubDate>
            <atom:updated>2018-05-07T12:13:31.042Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>For DjangoCon Europe 2018, we restructured our Code of Conduct in order to better reflect our intentions and values.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kYo96PQuLzRSQxXvfpU6fg.jpeg" /><figcaption><em>Image by </em><a href="https://commons.wikimedia.org/wiki/File:Heidelberg_Castle_and_Bridge.jpg"><em>Rane.abhijeet</em></a></figcaption></figure><p>For quite some time, DjangoCon Europe, along with many other conferences have used a <a href="https://2017.djangocon.eu/code-of-conduct/">similar Code of Conduct</a>. Originally based on the example from <a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy">Geek Feminism Wiki</a> and earlier versions from PyCon US, this almost identical text is <a href="http://ng-girls.org/coc/">used</a> <a href="https://www.chef.io/code-of-conduct/">very</a> <a href="https://www.pycon.it/en/code-conduct/">widely</a>. For DjangoCon Europe 2018, I felt it was time for a refresher.</p><p>The changes were initially written by me, and then refined together with the rest of the conference team. I also took a lot of inspiration from the <a href="https://www.djangoproject.com/conduct/">Django community Code of Conduct</a>, including changes that <a href="https://github.com/django/djangoproject.com/pull/757">I already pushed there</a>.</p><h3>Why was it time for change?</h3><p>In a way, I felt that our Code of Conduct (CoC) started to feel like we were just copy-pasting it year after year without thinking. Now, every conference where I was on the team, has always been very committed to upholding the CoC. This includes dealing with reports professionally, appropriately and with compassion, and not being afraid to take harsh actions when needed.</p><p>However, I felt that our values and intentions did not come across well enough in our published text. It didn’t help that almost the same text was now also being used by many other conferences, some of which managed their CoC poorly.</p><p>The essence of <a href="https://2018.djangocon.eu/conduct/">our restructured CoC</a> is still the same, but I wanted to improve on a few specific things:</p><ul><li>Lowering the barrier for reporting, as much as we can. In my view, this is one of the hardest issues for a CoC team.</li><li>Being more explicit about where the CoC applies.</li><li>Being more explicit about possible law enforcement involvement.</li><li>Explicitly listing possible CoC actions.</li><li>Expanding on the reasons for having a CoC, both with the goal of encouraging reporting, but also improve understanding among people who are more skeptical towards CoCs.</li></ul><p>One of my inspirations was Sage Sharp’s post in CoC enforcement warning signs — which were obviously signs I wanted to avoid:</p><p><a href="https://otter.technology/blog/2017/12/28/code-of-conduct-enforcement-warning-signs/">Code of Conduct Enforcement Warning Signs</a></p><h3>Lowering the reporting barrier</h3><blockquote>Please do not feel like you may be a burden to us by reporting incidents. Even if you happen to report multiple incidents during the conference. We rather consider reports an opportunity for us to act: by knowing about an incident, we can act on it, and often prevent it from continuing or repeating. But if we don’t know, we can’t take action.</blockquote><blockquote>— New DjangoCon Europe 2018 Code of Conduct</blockquote><p>At one conference, where I was not an organiser, someone approached me because she’d seen me mention CoCs in my talk. She quietly asked me “<em>so, I reported that issue I told you about, and the team handled it well, but now something else happened today — do you think it’s ok for me to report a second time?</em>”. I told her it was fine, and that I’d be happy to mediate if needed.</p><p>This is one of the experiences that made me aware of how hard it can be to report something, along with my own reporting hesitance at times. Reporting can feel like a huge step, because it sets so much process in motion. However, in a CoC team, I am nothing but grateful when people choose to report, because it gives us a chance to address the issue, and perhaps learn how to prevent similar issues in the future.</p><p>One time I was on the Code of Conduct team and someone came to me reluctantly. He wanted to bring something up that felt off to him, but didn’t think it was something he could make a CoC report about, because he wasn’t sure. In the end, we did take this through the CoC process, and found that although the CoC had not been violated, there was an important lesson that we could immediately act upon: we hadn’t been sufficiently clear on the venues where the CoC applied. So even though there was no violation, this reluctant reporter helped us see where we needed to improve. That’s why I also wanted it to be as encouraging as possible when people aren’t sure:</p><blockquote>If you are not sure whether the situation was a Code of Conduct violation, or whether it applied to that particular space, we encourage you to still report it. We would much rather have a few extra reports where we decide to take no action, rather than miss a report of an actual violation. We do not look negatively on you if we find the incident is not a violation. And knowing about incidents that are not violations, or happen outside our spaces, can also help us to improve the Code of Conduct or the processes surrounding it.</blockquote><h3>Being explicit about where the CoC applies</h3><p>The only clarity we offered about the scope of our CoC used to be:</p><blockquote>We expect participants to follow these rules at all conference venues and conference-related social events.</blockquote><p>What are the conference venues? Certainly the building where you do talks or sprints, but how about the hotel where you booked rooms for your speakers? We needed more clarity on this.</p><p>Unfortunately, this question comes with some grey areas. You’ll encounter this from time to time in your CoC processes. Sometimes it’s just hard to define exactly where the line is. Certain behaviour which is okayish in a private corner with an old friend, may be unacceptable on a stage.</p><p>Don’t let such grey areas stop you. Because a CoC is not like a law. We don’t have courtrooms where people argue for days over the meaning of a specific word, where that single fact determines the entire outcome. Sometimes we can be quite specific, and that’s nice, but sometimes we can’t. Rather, whether you’re an organiser or an attendee, try to think in the spirit and intention of the CoC — while still being clear and explicit as much as possible, where possible. This is a learning process too.</p><p>For this year’s DjangoCon Europe, we went for:</p><blockquote>This Code of Conduct applies to all conference related spaces. That includes, but is not limited to:</blockquote><blockquote>- The conference venue(s)</blockquote><blockquote>- The conference hotel(s)</blockquote><blockquote>- Any conference related social activities</blockquote><blockquote>- Slack channels, tweets with the conference hashtag, and other online media</blockquote><blockquote>The Code of Conduct does not exclusively apply to events on the conference agenda. For example, if after a scheduled social event you go to a bar with a group of fellow participants, and someone harasses you there, we would still treat that as a CoC violation.</blockquote><p>As you can see, we haven’t been able to remove all ambiguity. But by adding an example of how the CoC can even apply to an event entirely off the official agenda, we hope we encourage people to report even if something happens in such a space.</p><h3>Being more explicit about law enforcement</h3><p>As a CoC team, it is also our task to escalate if needed. If a CoC violation may also be a crime, like an assault, we should help a reporter involve law enforcement and assist with liaising and translating. This was already a part of our CoC:</p><blockquote>Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference.</blockquote><p>Not everyone has good associations with law enforcement though. People in many marginalised groups are at dramatically elevated risks of police abuse and brutality. Some people have moral issues with law enforcement policy. Whatever the reason, some attendees may prefer to avoid contact with law enforcement as much as possible, and we weren’t explicit about that before. Therefore, we added:</p><blockquote><strong>However, we will not contact security or law enforcement without your consent, except when not doing so would create significant danger for other participants.</strong></blockquote><p>The exclusion for significant danger gives us an option in case of, for example, an ongoing violent incident that we are not immediately able to contain. That creates such a severe danger for others, that their safety would likely prevail over the interests of someone who did not want law enforcement involved.</p><h3>Explicitly listing possible CoC actions</h3><blockquote>The Code of Conduct doesn’t list a range of consequences for violating the rules. This typically indicates that event organizers aren’t prepared to enforce their Code of Conduct. Vague phrases like “violators will not be welcome at the event” may mean an event doesn’t have an incident response plan that includes a tiered level of responses to deal with everything from inappropriate jokes up to interpersonal violence.</blockquote><blockquote>— <a href="https://otter.technology/blog/2017/12/28/code-of-conduct-enforcement-warning-signs/">CoC enforcement warning sign #4, Otter Tech</a></blockquote><p>Although we did mention possible actions, the old text just felt kind of weak:</p><blockquote>If a participant engages in harassing behavior, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.</blockquote><p>And so we expanded to a new text:</p><blockquote>In case of a Code of Conduct violation, some of the most common actions organisers may take are:</blockquote><blockquote>- Demanding that a participant stops their behaviour.</blockquote><blockquote>- Demanding that a participant prevents further contact with certain other participants.</blockquote><blockquote>- Not publishing the video of a conference talk.</blockquote><blockquote>- Cancelling a conference talk.</blockquote><blockquote>- Removing a participant from the conference, without refund.</blockquote><blockquote>The action taken is at the discretion of the Code of Conduct team. Participants are expected to comply immediately, and further action may be taken in case a participant does not comply. A record will be kept of all incidents.</blockquote><p>To me the new text feels more powerful, in that it comes across more that we are willing and able to take any of these actions if needed. And that firmness is important in at least part of your CoC, to make sure people take it seriously. This was heavily inspired from the <a href="https://www.djangoproject.com/conduct/reporting/">Django community CoC reporting guide</a>.</p><h3>Expanded reasoning for the CoC</h3><p>I added <a href="https://2018.djangocon.eu/conduct/">an explicit section</a> on why we have a CoC. The goal of this is to take CoC further away from a strict definition of exact rules, and to be clearer on why we do all this, and what it’s all about. In a way, it shows the values we had in mind when we decided that there should be a Code of Conduct.</p><p>This can further reduce the barrier to reporting, but it can also help to improve understanding of the CoC, even among people who are more skeptical or even negative towards CoCs.</p><p>To me, the improved DjangoCon Europe 2018 CoC reflects our intentions better than the old one, but I think there is still room for further improvement. Based on our experiences at the conference, we’ll find new things to improve. If you have thoughts on this, I’d love to hear them, so that we can continue to build inclusive, welcoming and safe communities.</p><p>In a future blog post, I’ll also take you through our <a href="https://2018.djangocon.eu/conduct-response/">response guidelines</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c203eb591ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>