<?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 David Eads on Medium]]></title>
        <description><![CDATA[Stories by David Eads on Medium]]></description>
        <link>https://medium.com/@davideads?source=rss-21b0970c881b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*RLCcC5a2N_28kuas.jpeg</url>
            <title>Stories by David Eads on Medium</title>
            <link>https://medium.com/@davideads?source=rss-21b0970c881b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:46:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@davideads/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[Coding Standards #3: Taking harm seriously]]></title>
            <link>https://medium.com/@davideads/coding-standards-3-an-over-abundance-of-assumptions-c03981fee10f?source=rss-21b0970c881b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c03981fee10f</guid>
            <category><![CDATA[code-of-conduct]]></category>
            <dc:creator><![CDATA[David Eads]]></dc:creator>
            <pubDate>Mon, 25 Apr 2016 13:06:52 GMT</pubDate>
            <atom:updated>2016-04-25T13:12:55.299Z</atom:updated>
            <content:encoded><![CDATA[<p>We are all going to do or say stupid and hurtful things. Sometimes, we simply don’t know any better. Sometimes, we’re being jerks. These actions — whether they are intentional or not — harm others in all kinds of ways.</p><p>There are all kinds of harm. Careless, stupid talk or actions. Mean-spirited talk or actions. Harassment of all kinds. Threats of violence and physical violence.</p><p>These forms of harm often overlap — incidents of harassment, like being followed or photographed, are often accompanied by physical threats. The difference between malice and stupidity can be impossible to ascertain. Intent might matter in how your community addresses an incident, but intent doesn’t magically transform the harm done.</p><p>There are infinite combinations of intentions, actions, and harms, but one thing is certain: <strong>If someone says “that hurts”, you need to take them seriously. </strong>When someone reports an incident, it is your community’s job to investigate the allegation fully, carefully, and fairly.</p><p>To do that, people need a way to express the details of how they were hurt. That means you need to be asking questions and explaining the actions you will take, not making assumptions or jumping to conclusions right off the bat.</p><p>Questions like “What happened exactly? What did he say to you?” and clear actions like “we’re going to ask [alleged harasser] to leave for the day, then we’re going to take a look into this and have a response in the next week” are good replies when someone reports a harmful incident. This type of reaction demonstrates respect for the person who is alleging harm and gives you the space and time to better understand what happened and formulate a response.</p><p>On the other hand, comments like “Well, I’m sure he didn’t mean it like <em>that</em>” are a terrible and terribly common response to everyday racism and sexism. You’re not treating someone who is in pain seriously if you start addressing their concerns by minimizing or disregarding the hurt they’re expressing. If you go there, you are likely to diminish or destroy your ability to talk with that person about what happened.</p><p>Some kinds of problematic behavior like microaggressions and dismissive responses share a root cause: an over-abundance of assumptions. Too many assumptions aren’t the only reason people are jerks, but it’s one reason why people are jerks without meaning to be.</p><p>This was true when I teased a Mexican teen at FreeGeek about doing poorly in his Spanish class. Why the hell would I assume a kid who grew up in Chicago and could speak Spanish would magically be good at reading and writing it? I grew up speaking English but can barely write it. But I was that clueless white guy in that moment and managed to hurt my friend’s feelings.</p><p>Similarly, “but they didn’t mean any offense” is the sort of knee-jerk response that assumes good intent on the part of the person doing the harm. It assumes the victim’s hurt is insignificant or a figment of their imagination.</p><p>The <a href="https://www.ruby-lang.org/en/conduct/">Ruby Code of Conduct</a> says “when interpreting the words and actions of others, participants should always assume good intentions.” This is a completely silly assumption — there’s ample evidence from Twitter and the history of humanity that not everyone has good intentions.</p><p>At least it seems silly until you realize it is also a dangerous assumption. The people you perceive to have good intentions are quite likely to be people who look like you and share your culture. It minimizes your ability to see the harm done to others because hey, that totally transphobic comment might have been hurtful, but the guy who said it didn’t mean any harm.</p><p>Yet even small harms can be a form of violence. This is why the language of “micro-aggression” has been so helpful in coming to terms with the everyday violence of cultural assumptions and casual actions. The word manages to convey both the small scale and the violent nature of these “small” forms of harm. The assumptions we all make about others that deny their particularity and agency are a form of violence.</p><p>If you’re enforcing a code of conduct, your job is to take every person’s harm seriously, to assume as little as possible, to investigate as carefully as possible, to listen as closely as possible.</p><p><em>You might notice it’s been awhile since the last Coding Standards post. I started teaching a class, traveled to the NICAR conference which prompted me to start this blog to begin with, got a nasty head cold, and covered a bunch of elections. I make no promises about how quickly I can write these, and appreciate your patience.</em></p><p><em>Next time we’ll be diving into the list from </em><a href="https://medium.com/@davideads/welcome-to-coding-standards-f17cce657868#.nmx21cx2n"><em>the first post</em></a><em> and looking at where and when your code should apply.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c03981fee10f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coding Standards #2: FreeGeek Chicago]]></title>
            <link>https://medium.com/@davideads/coding-standards-2-origin-stories-f079439ff23a?source=rss-21b0970c881b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f079439ff23a</guid>
            <category><![CDATA[free-geek]]></category>
            <category><![CDATA[code-of-conduct]]></category>
            <dc:creator><![CDATA[David Eads]]></dc:creator>
            <pubDate>Fri, 26 Feb 2016 22:14:04 GMT</pubDate>
            <atom:updated>2016-02-26T22:35:08.065Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cAmOLZ0NNRlHeyK3." /><figcaption>Software Freedom Day 2013. Photo by Jonathan Gibby.</figcaption></figure><p>The first real case of harassment at <a href="http://freegeekchicago.org/">FreeGeek Chicago</a> happened some time in 2006, and it made us realize just how much we needed some of kind of code of conduct. First, let me tell you a little about FreeGeek Chicago (FGC), where I was a community member and leader from 2005 to 2014.</p><p>FGC was conceived in the spring of 2005 and started operations in the fall of the same year. The founders (I was one of them) were a group of seven tech people. We were all in our 20s and all working in the nonprofit world. We were disappointed with the organizations we worked for, whose noble ideals were often compromised by the funding rat race and distance from the lives of normal people.</p><p>The founders all connected for the first time at a nonprofit tech conference, went out to a dive bar, watched one of the <a href="https://www.youtube.com/watch?v=XTbE4eC-AIc">greatest comebacks in NCAA history</a>, and decided to do something about our frustrations. One of the founders had met people from an organization in Portland, Oregon. It was called <a href="http://www.freegeek.org/">FreeGeek</a> and had a fascinating model built around self-sustainability and community. We could use their name, provided we were committed to ethical recycling, open source software, and community governance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QxlY2e_S2uaYQXUQ." /><figcaption>Janet at the QA station, fall 2015. Photo by Evelyn Lopez.</figcaption></figure><p>Today, there are 13 independently operated FreeGeeks around the U.S and Canada. The model is simple, though the programs and policies vary from place to place. In FreeGeek Chicago’s main program, volunteers put in 24 hours and learn to tear down old computers, test the parts, put them back together, and install Linux. At the end of the program, they get enough store credit to buy a basic desktop or laptop system or get other components they might want. Many volunteers stay after completing the program to keep learning or teach others. FGC is <a href="https://github.com/freegeekchicago/fgc-docs/blob/master/constitution.md">governed by its community</a> and anyone who puts in a few hours volunteering has a say in what happens. FGC doesn’t categorically reject grant and foundation funding, but does have <a href="https://github.com/freegeekchicago/fgc-docs/blob/master/statement_funding.md">strong safeguards against philanthropic influence</a>. Most of the budget comes from selling scrap to ethical recyclers and selling refurbished computers and parts in the thrift store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*dACCAlR1udq3Ah0i." /><figcaption>A volunteer with her computer in 2011. Photo by David Eads.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yLB9sTazijdXwgA-." /><figcaption>Teardown, fall 2015. Photo by Evelyn Lopez.</figcaption></figure><p>Every year, FGC serves 600–700 volunteers, sells nearly as many desktop and laptop computers, and recycles 25–35 tons of electronics. There are paid employees — most of the budget goes to pay them — with a budget that is well under $150,000 a year.</p><p>FGC is an experiment in coexistence. The organization attracts a diverse crowd of mostly poor and working class people along with some middle class professionals. It’s a very intergenerational space, from teens to folks in their 70s. FGC doesn’t keep diversity statistics (I proposed it but the community rejected my proposal for good reasons), but I’d guess the community is roughly 40% black, 30% white, 20% Latino, and 10% everybody else. FGC has always skewed more towards men — probably about a 60/40 split, which is better than the tech industry but still isn’t great. The statistics, as approximate as they are, don’t entirely capture how diverse, complicated, funky, and wonderful the community is.</p><p>Wander into FGC’s basement space and you might find a Dominican Sister tearing down a computer alongside a Gangster Disciple, overhear a conversation about why the space has a gender neutral bathroom, or meet someone who got their masters degree in prison. You might run into an anime-obsessed Mexican college student who has been volunteering for years or a homeless person who can tell you everything there is to know about the Linux command line. You can get a free flu shot along with that cheap USB cable you came to buy.</p><p>This is by design. Just about everyone is afflicted by technology. For all the talk of “digital empowerment” and “bridging the digital divide”, knowing your way around the Internet is fundamentally a survival skill in modern life. That’s why FGC operates as something like an Apple store for the rest of us. If technology is the 21st century religion, FGC is a storefront church. FGC is a community of people working together to serve their own basic technological needs as best they can.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a7FALIxYDGco-H2B." /><figcaption>Volunteers, fall 2015. Photo by Evelyn Lopez.</figcaption></figure><p>Back to 2006, a time when our young organization was just starting to attract volunteers interested in earning a free computer or teaching others.</p><p>Several of the leaders had been introduced to the idea of a code of conduct at the Nonprofit Developer’s Summit, which had a well-considered code for the event. The summit’s code and facilitation style was in turn inspired by radical organizing groups like the Ruckus Society. At the time, I was intrigued but also a bit dismissive of all that hippie stuff. I was coming from libertarian open source tech culture, where the idea of setting rules for behavior is seen as a serious infringement on freedom.</p><p>My thinking at the time was basically: what’s the big deal, anyway? Some people are going to be jerks, but who am I to tell them what to do? If people are offended, maybe they just need to deal. I suspect several of the leaders subscribed to some version of this, though not everyone was so naive. It didn’t take long for all of us to understand how shallow, risky, and counter to FGC’s mission that philosophy is.</p><p>There was a man who had been coming around who had trouble written all over him. He often said vaguely (and occasionally blatantly) inappropriate things. He was pushy and impolite. He didn’t participate in the program so much as just kind of hang around. He became more rude over time. A couple of the other leaders and I talked about him a bit. We decided that unless he did something really bad, we should let him stay.</p><p>One day, a woman came in to volunteer. In a brief conversation, I learned she was in her 20s, a veteran of the Iraq war, and an expert at computer networks who was struggling to find work after returning to civilian life. We desperately needed a networking pro to help us, so I was very excited she’d made her way to FGC.</p><p>At some point, the man we’d been worried about showed up, wandered over to the networking expert, and came on to her in ugly, highly racial terms (she was black, he was was white). We kicked out the guy and made sure he never came back, but the damage was done. The woman left, angry and clearly shaken. She never came back either.</p><p>That’s when we knew our whole framework for thinking about how people behaved in the space was off-base. We didn’t need to shrug and feel like there was nothing we could do when someone said something inappropriate but not necessarily or immediately worthy of more drastic action. We realized that we needed to be proactive about creating a safe space.</p><p>A code of conduct might not have prevented the man from being there that day or doing what he did, but it certainly would have lowered the odds. FGC’s code is a tool that helps everyone in the community know how to identify and politely shut down the micro-aggressions and bad behavior that led up to that moment. In my experience, the serial aggressors will typically increase their disruptive and dangerous behavior over time. If there’s pushback, they’ll get tired of hearing about it pretty quickly and move on to spaces that tolerate their bullshit. If there’s no pushback, things are liable to get much, much worse at some point.</p><p>Having a code in place might not have kept the woman from leaving forever, but I’m certain it would have helped. As it was, despite kicking the harasser out, we were clearly not prepared to deal with that kind of situation. The woman might have thought we were unable to maintain a safe space, and if so, she would have been 100% correct. Once we had a code, we were able to curtail most of the kind of harassment the woman experienced and were able to act quickly and decisively when it did happen.</p><p>Today, the code and the spirit animating it are deeply embedded in day-to-day operations. Volunteers hear the code in the mandatory orientation when they start the program and learn how to report incidents if they happen. The code is read out loud in its entirety at the beginning of every community council meeting and every event held in the space. It is posted on the wall where everyone can read it, right above the incident report forms. If there are incidents, they are reported and discussed at the community meetings. The code is pillar of FGC’s community. It is both a social contract and a tool that helps people of wildly different backgrounds and walks of life able coexist while respecting their personhood.</p><p><em>A few notes:</em></p><p><em>Next time, I’ll be discussing harm, harassment, and healing. I hope to publish these once a week. That might be a little optimistic in the middle of primary season, so I appreciate your patience.</em></p><p><em>In my last post, I should have linked to the </em><a href="https://github.com/eads/generic-code-of-conduct/blob/master/code-of-conduct.md"><em>generalized version of FGC’s Code of Conduct</em></a><em>. FGC’s current code is tightly tied with other organizational policies and practices, which means it doesn’t entirely match the points I mentioned in my first post, which are covered by other organizational policies and practices at FGC.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f079439ff23a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to Coding Standards]]></title>
            <link>https://medium.com/@davideads/welcome-to-coding-standards-f17cce657868?source=rss-21b0970c881b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f17cce657868</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[David Eads]]></dc:creator>
            <pubDate>Wed, 10 Feb 2016 14:09:25 GMT</pubDate>
            <atom:updated>2016-02-10T15:34:14.872Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*JepDdvwrrGTsM8gxR1wWCw.jpeg" /></figure><p>Last week, people in my wider professional circle had a little Internet explosion in response to a message sent to NICAR-L, an important and popular professional email list. (You can<a href="https://po.missouri.edu/cgi-bin/wa?A2=ind1602&amp;L=nicar-l&amp;D=0&amp;F=P&amp;P=5643&amp;F="> read it here</a> if you register for the list. Honestly though, you’ve probably seen this kind of thing before.)</p><p>I’ve had some practice dealing with situations like this and I’ve been thinking about what goes into a good code of conduct. Here’s what I’ve got:</p><p><strong>Define the community and environment:</strong></p><ul><li>Mission and goals for the space.</li><li>Where and when the code is in effect.</li></ul><p><strong>Set expectations:</strong></p><ul><li>Types of interaction that are healthy and encouraged.</li><li>Types of interaction that are unacceptable.</li><li>Levels of response.</li></ul><p><strong>Develop a reporting process:</strong></p><ul><li>Safe ways to report incidents.</li><li>Reporting back to the community about how incidents were handled.</li></ul><p><strong>Develop a response process:</strong></p><ul><li>A diverse and representative group of trustworthy people to handle enforcement.</li><li>Tools for de-escalating and stopping incidents.</li><li>A response process for serious incidents.</li></ul><p>Software developers have coding standards that help avoid common mistakes and response protocols for catastrophic problems. Journalists have professional ethics that help reporters practice the craft with integrity and deal with those who don’t.</p><p>The spaces where we work together, ask questions, support each other and debate important topics need similar codes.</p><p>How many people saw the blow-up on NICAR-L and thought “welp, that’s why I shouldn’t post anything” or simply unsubscribed? That doesn’t have to happen. But it will happen without tools to prevent it.</p><p>A good code of conduct isn’t about policing thought or suppressing debate. A good code gives your community tools for reducing harm, making sure harms don’t accumulate, and dealing with the really traumatic situations. It’s about giving people a fair shake — even the people with crazy ideas, because at the end of the day, that’s all of us. It’s about re-writing the unwritten rules that alienate and drive away good people into common ground for healthy and productive interactions.</p><p>In the coming weeks, I’ll expand on the points above. I’ll draw on my experience at <a href="http://www.freegeekchicago.org/">FreeGeek Chicago</a>, a radically inclusive space where I helped develop a <a href="https://github.com/freegeekchicago/fgc-docs/blob/master/code-of-conduct.md">Code of Conduct</a> and helped enforce it for almost a decade.</p><p>I’m going to tell some stories, and that’s going to be hard. I saw everything from ignorant comments to physical violence at FreeGeek. I’m proud of how we handled these situations and how hard we worked for restorative justice. But these are tough situations without easy answers and often bittersweet endings. As my friend Jamie Kalven says, there are large acts of violence but only small acts of healing.</p><p>Sometimes people are going to be behave poorly towards each other. Is your community ready to deal with it?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f17cce657868" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>