The Signpost


The (Universal) Code of Conduct

Contribute  —  
Share this
By Wugapodes
This essay is adapted from "The Code of Conduct" by Jesse Noller under the Creative Commons By-SA 4.0 license. Originally written in 2012 regarding the Python Software Foundation, it has been edited to reflect the Universal Code of Conduct debate within the Wikimedia movement.


By now, editors are likely aware of the Wikimedia Foundation's efforts to draft and implement a Universal Code of Conduct (UCC) for Wikimedia spaces. The first phase of the process was recently completed, with the board of trustees ratifying an initial policy on 2 February 2021. The second phase involves consultations across projects on how the UCC would apply to individual communities with the goal of developing appropriate mechanisms for enforcing the code globally. As part of this second phase, the English Wikipedia is holding a local consultation to provide feedback on how the code of conduct would fit into this project's community.

While a universal code of conduct is new territory for the Wikimedia Foundation, the debate is not. Arguments around codes of conduct have been active in the free and open source community for years. In 2014 Coraline Ada Ehmke released the Contributor Covenant which has served as the model code of conduct for many free software projects such as the Linux Kernel, Mozilla Webmaker, and Node.js as well as open source branches of major corporations like Facebook and Google. While projects were adopting codes of conduct, organizations were likewise incentivizing more projects to adopt them. For example, in 2012 the Python Software Foundation required that any conference it sponsors will be required to publish a code of conduct for the event. This was, partly, in response to questions the foundation had received from potential sponsors who were starting to require that their sponsored partners publish codes of conduct.

The following essay makes the case for a Universal Code of Conduct in the Wikimedia movement based on similar arguments from the Python community in 2012. Like the Python community then, the Wikimedia community is vibrant, diverse, and growing. Originally written by Jesse Noller to explain the Python Software Foundation's resolution requiring a code of conduct, the piece has been edited to reflect the parallels between the concerns then and those of the Wikimedia community now.


Community is a broad term. In the case in which I refer to it—I refer to is as the constantly growing and evolving and diversification of the global Wikimedia community. The community is growing at an astounding pace. The number of Wikimedia related conferences and events is also growing at a pace which frankly floors me. We have edit-a-thons popping up all over the world almost monthly. Wikimedians who are speakers of the Dagbani language this year had their m:Wikimedia user group recognized by the affiliations committee for the first time.

Most, if not all of these events are put together by small teams of dedicated, passionate and kind teams of largely unpaid volunteers. This is both amazing, and heartwarming. The level of love and passion shown by so many in this community amazes me on a daily basis.

This passion I have, this love for the community, its ever-growing diversity and what it has done for me is exactly why the Wikimedia Foundation should establish a Universal Code of Conduct. It's not because the global community is broken. It's not because we've had a "trigger event", although administrative abuses stick in my mind like a road flare when thinking about this.

So no: I don't think our community is "broken" or has performed ill—but nor has it been perfect, nor shall it ever be. I am proud of it, I spend countless hours working on behalf of it, and I would not trade it for the world. It has made me feel welcome, it has supported me in my times of need. It has allowed and empowered me to do amazing things.

Oh yeah, and I'm totally in love with the encyclopedia, even if I cheat on it sometimes.

But, like with code—there's a smell in the community—but it's the larger Programming community and its conferences and events as a whole.

D stands for Diversity

We've seen enormous growth in the diversification and inclusion of the vast non-majority within our communities thanks to the hard work of many—this includes the Art+Feminism movement, Women in Red WikiProject, m:Wiki Loves Africa and Wiki Loves Monuments contests, m:Wikipedia Asian Month, and many, many others.

What we are seeing is a fundamental shift in the awareness that we need to be more welcoming, more open to those who do not make the majority of our community. We need to have workshops, we need to be more inviting. We need to lower the barrier of entry of contribution. We need to make safe havens for those who want to contribute but who are scared and intimidated by the status quo. This includes men, women—everyone.

Part of this effort is the social realization of one of the Zen of Python rules:

What I mean is this: no more unwritten rules or expectations. No more assumptions that we're living in a utopian meritocracy. We don't. Sure, the free and open source software movement has been defined as "they with the best code and who does the work, wins"—but that ignores the frequent corollary of "those with the thickest hide, and ability to fight win". Look at any mailing list—look at the discussions on the relative merit of a given feature, bug fix, etc. You will see things that would make your hair turn grey. You will see people shouted down for naivety, you will see that even the most meritorious idea may not win against the establishment.

This happens everywhere. This is why I say "explicit is better than implicit" when it comes to social norms and expectations.

The idea that there's some unwritten guide on how to behave in society, at a conference, at a meetup, or anywhere is fundamentally absurd. Look around you for examples.

But what does this mean in the Wikimedia Community? It means we can do better! We already are on so many fronts—but just because we're seeing positive changes doesn't mean we should stop the movement.

Back to Code of Conduct

That simple, right? Well, yes, actually. When it comes to a code of conduct for a mailing list or group or for a community such as Ubuntu and Fedora or for a conference it all boils down to the same thing. A set of rules that don't dictate what you can do, or who you must be, but what is not acceptable.

It's sort of like laws. Laws don't generally dictate your personal freedoms—what they do normally do is dictate where, given unlimited freedom, your "right to do whatever you want" ends. Laws are there not to stop crime. They are there to set rational expectations for rational people—they tell the rational actors in our story what they can count on. They set in place the rules of societal engagement and put in place punishments for when those rules are broken.

A code of conduct is no different—it is an explicit set of rules on what isn't acceptable! It's not there to take away your rights—unless you feel your rights include sexual harassment, putting pornography in talk slides, or making sexist or racist jokes in a large group of people. It's there to show everyone what is not acceptable behavior, and to show what repercussions there are if anyone violates this behavior.

Quoting Jacob Kaplan-Moss on this (re: Code of Conducts/anti-harassment policies):

Just like laws; a code of conduct or anti-harassment policy is not going to stop bad actors. It won't. It can't. It might convince a person who acts in bad faith, or intends to do so to not attend the event—it is, after all, a signal they are not welcome, and there are consequences. Really though—again just like laws—it won't stop a determined bad actor. If I, a Wikipedia administrator choose to slip a bit of porn onto the Main Page, I can. No one is going to know until they see it ala Fight Club.

However, should I choose to do so, instead of unspoken, unwritten rules about what's acceptable, or what consequences there would be (social shame, etc), we have a lovely document that outlines precisely what will happen to me.

I will, simply put, be kicked out. As an administrator, I will be asked to leave the encyclopedia, I will not be given a refund. I will, in addition to this, probably be publicly shamed by all of those people who I knowingly and willingly abused, I will lose my administrator bit, etc. I would, in fact, support being asked not to return to the project, or other projects for a period of no less than 1-2 years.

If you read our policies, you'll note something interesting: there are protections in there for victims, and protections for alleged harassers/Code of Conduct violators. This is meant to protect everyone involved in the situation from false allegations, or knee jerk reactions.

This Code, this Guide, provides the explicit declaration of what is expected so that when violations occur we will know when and how to react.

But Everyone is nice, we've always been cool

I know. Honestly, I do. Except for minor incidents that I recall, the English Wikipedia has largely been free of issues. Every meetup, conference, etc I have been to has been filled with nice, kind people and largely jerk-free. This is a testament to the community as a whole.

So, you ask: if we're all chill cool people, and nothing bad has happened, why have one?

Because it won't always be that way.

If we continue to expand and grow (and we will), and if we continue to grow even more diverse - in sex, race, creed and geography - the chances of "an incident" will grow. In fact, I know incidents have happened and been dealt with.

So no, the unspoken rule of "don't be a jerk" doesn't scale very well. And that's what we're talking about—a scalability problem. The social norms and rules of a group of five people, or one hundred people may float. What about 200? 500? 800? How about 40 thousand people (the average number of active editors on the English Wikipedia each month)? No. "Don't be a Jerk" may be our unspoken, unwritten community motto; but its not enough for those on the outside looking in.

Those outside of these circles want clear lines on behavioral expectations. They want to know that not only are there unwritten rules about not being a jerk—they want to know what will happen if a Jerk Occurs. A Universal Code of Conduct sets their expectations, and it gives them comfort. It makes them feel more welcome, more safe. Especially when they're part of a group who has been put under constant objectification and harassment for decades in our industry.

The Social Signal Flare

A Code of Conduct is, in fact a social signal flare to "others"—it's a message to them on what to expect, that they can feel welcome and safe and most of all that someone cares. I have the emails and phone calls thanking me and the PyCon team for the Code of Conduct to show it. They all carry the common theme: "Thank you. Thank you for showing me you care, and that you are thinking of me."

What has the Python software Foundation's adoption of a Code of Conduct triggered? Combined with this guide, and outreach, we have drastically increased the number of (for example) female speakers at our event. We have more female and varied attendees. We have people bringing their families with them. Not just because of a single document. But because they know that because of that document and the history and people within the Python community they can feel safe, and welcome.

This social signal flare; this written set of guidelines matters to them. And the Python community is not the only one realizing this. OSCON, Ruby Conferences, JS Conferences and other events—all of them are realizing that having rules and expectations set out for all to see makes it better for everyone.

So why the Foundation?

Now we get to the beginning: why an "edict" from the Foundation board that states this is a must for any project they are hosting. Well, if you read this far, hopefully you're convinced of the basic case of having a document such as this in place.

Let's look at it from a brand perspective.

For PyCon 2013 I was asked by no less than four different sponsors if I had a Code of Conduct / Anti-harassment guide in place. If I did not, they would not become sponsors. Conference attendees are demanding conferences have one, or they will not attend, or speak.

For example, I applaud Caktus Consulting Group for taking a hardline, zero tolerance stand:

Let us assume that the Wikimedia foundation is no different than a sponsor (it is, sorta): we provide you money, we give you our name and logo, and provide servers and a tech team to handle the back end. We are, by our participation and funding, implicitly and explicitly endorsing your project.

This means that should something happen, the "Wikimedia brand"—which to many, is synonymous with "Wikipedia" (duh)—would be tarnished. We would be seen as endorsing a community project which did not deal with a situation or incident. We would be lobbied to pull our funding/sponsorship (and I would vote for it). We would probably, via social pressure, be required to distance ourselves from the project and the organizers and probably even issue an apology of our own.

So. Starting for the idea that these documents, these guidelines benefit us as a community, and help us grow more diverse and inclusive, that they help in some way to make events more safe and welcoming—we end up in a place where from a pure business perspective it is in our best interest to put these guidelines in place.

These guidelines provide social good; they are also smart business. Yes—it is a sign that we are growing up, but that's a good thing.


In closing, all I can say is this—no one is trying to be a fascist, or a nanny state. No one is trying to say you can't cuss like a sailor (I do, but mostly behind closed doors). No one is trying to censor you, or tell you you are not welcome.

Quite the opposite. We, the global Wikimedia Community, are trying to tell people who are scared, or who feel alienated that they are in fact welcome. That they belong. That the community, the foundation and everyone cares about them. That we want to provide a safe place for collaboration and the free exchange of ideas.

We want to show everyone what they hopefully already know by now—that the Wikipedia community, despite its quirks, is welcoming, supportive and open to all.

In this issue
+ Add a comment

Discuss this story

We need to have workshops, we need to be more inviting. We need to lower the barrier of entry of contribution. We need to make safe havens for those who want to contribute but who are scared and intimidated by the status quo. This includes men, women—everyone."
We've been doing this for years. We have endless amounts of workshops for diversity or specific subjects or just general wikipedia editing. Saying "we need to have workshops" feels like a slap in the face. Then there's some vague lines about how "we need to lower the barrier of entry of contribution" and how "we need to make safe havens". Why do you think VisualEditor exists and there's so much effort put into improving it? Why do you think we have the WP:TEAHOUSE? Sure, you could probably write something about how we need to improve on our existing systemes and how VisualEditor needs to support templates better or how more workshops are needed in non-Western countries but you didn't because it's easier to just copy and paste what some guy said for a totally different organization back in 2015 and not bother to make any substantial changes to it.
It's also hilarious how the essay constantly operates under the assumption that we have no code of conduct or any rules regarding conduct whatsoever. Like we don't have WP:CIVILITY or WP:AGF or WP:COURTESY or WP:BITE. Or like WMF events don't already have a code of conduct at meta:Friendly space policies.
Additionally, for what it's worth, I bet if an admin actually did post porn on the main page they wouldn't necessarily get indeff'd for long from Wikipedia. There's a decent chance the admeme could just say "lol I got hacked sorry guys" and WP:SUPERMARIO outta the block.
"I know. Honestly, I do. Except for minor incidents that I recall, the English Wikipedia has largely been free of issues. Every meetup, conference, etc I have been to has been filled with nice, kind people and largely jerk-free. This is a testament to the community as a whole."
I'm going to assume that you included this by accident and that you didn't actually read your own essay and think "yep, there hasn't really been any major behavioural issues on enwiki". Chess (talk) (please use {{reply to|Chess}} on reply) 06:45, 26 April 2021 (UTC)[reply]
@Chess: I'm sorry if you feel personally disrespected, obviously that wasn't my goal. In the preface, I tried to be clear about the goal of this work: "the piece has been edited to reflect the parallels between the concerns then and those of the Wikimedia community now." The goal was not to write an exhaustive policy proposal or reproduce the research done by the foundation on these issues. So yes, this piece utterly fails as an essay arguing for the UCC on its own merits. I tried to make clear that that was not the goal, but it seems I could have explained that better.
Secondly, the minimal changes were an intentional choice. The goal was to prompt the reader to consider the parallels between the Python community Noller wrote about and the wiki community we currently have, so I wanted to keep as much of the source material intact so that the reader can make those parallels themselves. I could have just asked the Signpost to run the original essay verbatim, but I also wanted to take advantage of the unique medium provided by the wiki software and license. Collaboratively written essays are not uncommon around here (check out any policy page) and while not every edit changes the content of the essay entirely, the collaboration can take the form of changing anecdotes, examples, and phrasing to better reflect the contemporary readership. The goal was to use bricolage to evoke new insights by tinkering with existing media, but clearly it could have been done better.
Finally, to touch on your last point, you're coming from a completely different perspective than the one the essay was writing for. If you read this already believing the community is a cesspool then of course you're going to miss the point. The essay contains the following line which was pull quoted: "If we're all chill cool people, and nothing bad has happened, why have [a code of conduct]?" The essay is addressing people who believe the first part of the conditional. If you don't believe "we're all chill cool people, and nothing bad has happened" then the essay, quite explicitly, isn't addressing you. Whether that is a reasonable belief is debatable, but of course you're going to be unsatisfied by an argument when you reject one of the core assumptions.
Regardless, the criticism is well taken: the choices I made did not convey the intent I had hoped. Wug·a·po·des 02:58, 27 April 2021 (UTC)[reply]
I'm not saying your goal was wrong or that it's wrong to remix an essay to try to make it apply to the Wikipedia community. You're right a lot of our essays are written collaboratively and I imagine it could hypothetically be possible to remix an existing essay and apply it to Wikipedia. I would say you succeeded in prompting me to consider the parallels between the Python community back in 2012 and the English Wikipedia community. The problem is that those parallels simply don't exist beyond Wikipedia and Python both being from the wider free knowledge/FOSS community (in a sense) and both having the general attitude of being a meritocracy (kind of) and having the problem that oftentimes contributors are just those who are able to stick around and fight for a while. That and some of the "why the foundation" section (aside from the part about business sense). But beyond that the similarities end and the truth is that Wikimedia is such a colossal beast of a organization with so many distinct projects with differing requirements or necessities that it's a sui generis organization in the FOSS community. Many of the points in this essay simply aren't applicable to the English Wikipedia. I didn't mean for my comments to imply that this community is a cesspool but come on nobody who's been here for a while can seriously believe that we haven't had any issues. Look at WP:AN/I for just an endless stream of behavioural issues 24/7 that fills over a thousand pages of archives. If you want the "heavy-hitter" bigname Wikipedians go look at Wikipedia:Arbitration/Index/Cases/All for an admin who was literally deadminned last month for behavioural issues. Chess (talk) (please use {{reply to|Chess}} on reply) 05:51, 28 April 2021 (UTC)[reply]
No worries, it's not my first tough review. The flipside of drawing parallels is also identifying disconnects. You name some very substantial similarities: shared beliefs in meritocracy, shared FOSS ideology, major volunteer workforce loosely organized underneath an umbrella legal entity. Leaving aside whether they're few or many, they also highlight major differences. Others on this page have pointed out a lot of them---I think Nosebagbear did a good job of that above. You also point out the difference in number or scale of issues. The line you brought up wasn't lost on me, but I kept it because it unsettles a more pessimistic narrative. Obviously I know of the major incidents, but how major were they? Unlike the Scots Wikipedia, we never discovered that our content was gibberish. Unlike other wikis, we've never had global requests for all or most of our sysops to be removed. It's not to minimize the severity of our incidents, but to try and consider how someone could look at our wiki and be optimistic.
The point of editing it like I did was because not only did it make the similarities more obvious, it makes the differences more obvious too. The places where the analogy doesn't work or where the specifics don't match become more jarring precisely because they break the analogical thread. I wanted people to think not only about what Wikimedia is but also what it's not, and to prompt readers to think about those aspects in new ways through literary collage and juxtaposition. Even the less charitable responses show that it prompted people to consider what defines "the community"; I just did a bad job making clear to the reader that this wasn't meant to be a traditional essay. You did say it best: "adapted" is an understatement and I think people would have responded better if that were more accurate. Don't go full gonzo, got it. Wug·a·po·des 08:25, 28 April 2021 (UTC)[reply]

Secondly, the minimal changes were an intentional choice. The goal was to prompt the reader to consider the parallels between the Python community Noller wrote about and the wiki community we currently have, so I wanted to keep as much of the source material intact so that the reader can make those parallels themselves. I could have just asked the Signpost to run the original essay verbatim

...And you should have, full stop. Sorry, but by (poorly-)adapting the essay — which based on how you explain it was your goal, to have it not be a good fit for the Wikipedia community in terms of specifics of issues and concerns — by maladapting it to sound like it's about Wikipedia while being about something completely different, you managed to also rob it of whatever value the original, unaltered essay might've had, as an example/analogy/food-for-thought. -- FeRDNYC (talk) 03:27, 29 April 2021 (UTC)[reply]
@FeRDNYC: If you're going to give me unsolicited advice on how to improve my writing, at least understand the literary devices I've described. If you want to do something other than condescend, I recommend learning about pastiche, intertextuality, and the 2010 essay on the topic Reality Hunger. If you still don't understand, the deconstruction framework might help you understand how dialectics can create symbols that convey contradictory ideas simultaneously; you might also find the history of gonzo journalism and the New Journalism movement useful context. Of course, why learn about creative non-fiction when you can give people advice on stuff you've only been thinking about for a couple minutes? I appreciate your perspective on whether I got the response I wanted, but I couldn't care less about your opinions on what I should write. If you would have done it differently, then go do it—this is a wiki and the content is freely licensed. That, of course, would be harder than just complaining about how others do things. Food for thought. Wug·a·po·des 06:31, 29 April 2021 (UTC)[reply]
@Wugapodes: Explaining after the fact the intentions behind your essay is a questionable justification; these ideas should probably be communicated within the text of the essay which judging by the reactions of the people reading it was not done. It also seems incompatible to both advocate for judging the essay based on the intentions of the author (you) while also advocating for a deconstructivist (?) view on literature; one often based around the idea that authorial intent is irrelevant to judging a work. It also comes off as someone trying to cover for their mistakes after the fact rather than admitting they probably messed up in a few places. Are you really claiming that leaving in sentences like "I have the emails and phone calls thanking me and the PyCon team for the Code of Conduct to show it." or "For PyCon 2013 I was asked by no less than four different sponsors if I had a Code of Conduct / Anti-harassment guide in place. " was intentional?
If so, I'd like to end this by saying that "to be fair, it takes a VERY high IQ to understand a Wugapodes signpost essay..." Chess (talk) (please use {{reply to|Chess}} on reply) 08:06, 30 April 2021 (UTC)[reply]
Wugapodes, every time I see the words "intertextuality", or "deconstruction" -- or "dialectics" outside of a Marxist context -- I sense a little bit of someone's soul has just died. -- llywrch (talk) 21:28, 3 May 2021 (UTC)[reply]
Wugapodes, I've generally found you to be pretty thoughtful, but I think this should have been written from scratch, rather than trying to (rather poorly) adapt something from somewhere else by changing some words. To start with, the English Wikipedia had a code of conduct long before Python did. And that's why you're seeing pushback against the "UCOC" here—we already have our own code of conduct, developed by our own community through long experience, and with our own processes for updating and modifying it if need be. We don't need any advice from Python, thanks, but maybe they could have taken some from us. And also, the WMF uses Wikipedia's name, not the other way around. Wikipedia existed first, and founded the WMF. It does not belong to the WMF, and they are not in charge of it or some type of controlling authority. And they'd do well to remember that. Now, that being said, there might still be some use for such a framework for smaller and less-established projects, but trying to force it onto projects that already have well-developed policies and enforcement mechanisms, developed with the input of thousands of people based upon countless man-years of experience, will cause nothing but grief. We don't need anyone from a San Francisco office telling us how to run things; we've already figured that out, thanks very much. Their job is to keep the lights on and the servers humming, and that's it. Seraphimblade Talk to me 08:19, 26 April 2021 (UTC)[reply]
@Seraphimblade: Firstly, Wikipedia, the trademark, does belong to the WMF (not the other way around). If you scroll to the bottom of this page, you will see "Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc". We can fork the project, but the name "Wikipedia" stays behind with the Foundation. So we can yell about who owns whom until we're blue in the face, but philosophical beliefs aren't going to help much when the trademark paperwork comes out. Secondly, your point that a UCC "will cause nothing but grief" is pulled out of thin air. Why? The essay argues that even in a community with no problems, having a centralized body implement a code of conduct is a net positive (see sections "But Everyone is nice, we've always been cool" and "So why the Foundation?"). You can disagree with that argument, but simply saying "no it isn't" won't get us far. Wug·a·po·des 03:15, 27 April 2021 (UTC)[reply]
Well, like I said: We know from experience where that road leads. WMF is not competent to make day to day decisions about the operation of the projects; they're not there in the middle of it and could never hire enough people to be kept up to date on all the details. Projects are run by their editor communities, not by people in San Francisco who may or may not have ever made a single edit, according to our code of conduct, not whatever they cook up. (Note that that does not mean there isn't a code of conduct at all! So unlike Python, they can tell people "Yes, there most certainly is a code of conduct for the English Wikipedia", and have that be 100% truthful, even in the absence of the UCOC.) And while the WMF may legally own the trademark—well, I won't put lengthy Shakespeare quotes here, but people do not come here to check out the puzzle globe, even though it is a neat logo and I have always liked it. They come here for the encyclopedia. And that, we own, we maintain, and we can stop doing so and move it elsewhere. Obviously, that is not a desirable outcome, but well, the possibility of Framgate 2 is not a desirable outcome either. Once was quite enough there. Seraphimblade Talk to me 09:42, 27 April 2021 (UTC)[reply]
I get that it's rhetorical, but railing against San Francisco reflects your imagination and not reality. The WMF board that voted on the UCC had members from Israel, Poland, Argentina, and Ukraine. Most of the board isn't even in San Francisco. Like I said, I get that it's meant to drive home the point, but it's a completely inaccurate way of depicting the WMF. It also is not a good idea to invite the comparison. "San Francisco" is useful because it makes the WMF seem like a group of out-of-touch elites in a monoculture​ making decisions for large and diverse groups of workers (see "urban elites​"). Meanwhile, you are raving about how the English Wikipedia owns the whole WMF. There are people in this world who don't read or write English. Many of them contribute to WMF projects. This number has been growing. If you want an example of out-of-touch elites making decisions for a vast and diverse group of people, how you described the English Wikipedia would be a good one.
You also seem to misunderstand how community forks go. Sure, people come for the encyclopedia, but much of that has been built. Since everything is irrevocably CC By-SA licensed, the 6 million articles already written will stick around. So they've got trademark and the content, unless there is a complete community exodus they will also have maintainers. Those maintainers will still call themselves Wikipedians, and the organizations trying to recruit new editors will keep pumping new Wikipedians to Wikipedia. Meanwhile CitizendiumTwo is trying to convince Google to rewrite their software to pull from them and not EnWiki or Wikidata.
All of that because T&S overstepped once? Because we want to avoid them doing it a second time (nevermind our still growing list of long-standing hoaxes​)? They handle requests other than TheBigOne, and sometimes, dare I say it, they make the right call! All of this is moot, of course, since we're still deciding how projects and the foundation will handle enforcement so the foundation is currently, actively seeking your input on how to craft this so that another Fram situation can be avoided. Wug·a·po·des 08:25, 28 April 2021 (UTC)[reply]
It's a shame we can't vote to distance ourselves from the WMF in the same way the author speculates the WMF could be "forced" to distance itself from the entity that generates its content and (by extension) its revenue. Intothatdarkness 13:59, 26 April 2021 (UTC)[reply]
We can vote to write a letter which may or may not be read. If all else fails, LibreOffice voted with its feet when the masters of became less benevolent. I hope Wikipedia is not forced down a similar route, but it is an option. Certes (talk) 14:15, 26 April 2021 (UTC)[reply]
True. I must say, though, that I'm finding the tone of some of the author's responses here interesting. Intothatdarkness 14:03, 29 April 2021 (UTC)[reply]
Secondly: A code of conduct is [...] not there to take away your rights [...] It's there to show everyone what is not acceptable behavior, and to show what repercussions there are if anyone violates this behavior. I'd like to reiterate that we already have rules and behavioral expectations. I'd also like to point at out that universal codes, constitutions, charters etc. are not intrinsically incapable of taking away rights, so the assertion means little. To be suspicious of WMF's decision to go for this "legitimizing" strategy after the community accused them of overreach during the FRAMBAN does not mean I support harassment. It means I support fair investigation and fair punishment for alleged instances of harassment. The WMF has given itself (community consultation doesn't matter, the code was coming whether we wanted it to or not) all this power to enforce the rules unilaterally, and for what good? FRAMBAN demonstrates they aren't quite sure what to do with that power.
Thirdly: In closing, all I can say is this—no one is trying to be a fascist Actually yes, the crowd that took over Croatian Wikipedia is trying very hard to be fascist, and only a few months ago has the WMF actually bothered trying to do something about it. Sadly, I think that the UCOC will only be used to address such dumpster fire areas as those as an afterthought, when those should be the primary cases.

-Indy beetle (talk) 07:19, 27 April 2021 (UTC)[reply]


The Signpost · written by many · served by Sinepost V0.9 · 🄯 CC-BY-SA 4.0