Heavy Codes of Conduct Are Unnecessary for Open Source Projects
Posted3 months agoActive3 months ago
shujisado.orgTechstoryHigh profile
heatedmixed
Debate
85/100
Open SourceCodes of ConductCommunity Management
Key topics
Open Source
Codes of Conduct
Community Management
The article argues that heavy codes of conduct are unnecessary for most open source projects, sparking a debate among commenters about the role of CoCs in maintaining community standards and preventing harassment.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
37m
Peak period
74
0-6h
Avg / period
11.4
Comment distribution160 data points
Loading chart...
Based on 160 loaded comments
Key moments
- 01Story posted
Sep 30, 2025 at 3:54 AM EDT
3 months ago
Step 01 - 02First comment
Sep 30, 2025 at 4:30 AM EDT
37m after posting
Step 02 - 03Peak activity
74 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 3, 2025 at 2:42 PM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45423014Type: storyLast synced: 11/20/2025, 8:32:40 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
At this point, in 2025, does anybody seriously doubt that they're a "tool for troublemakers"? A lot of people who would otherwise contribute see a hyper-particular CoC, written by an HR type or an aspiring lawyer, and walk away. Others don't bother to read the CoC and may later be dragged through coals over something exceedingly minor, despite their contributions.
In open-source, the best policy is to avoid CoCs and avoid those who write and promote them.
They are also explicitly the type of views that CoCs are designed to protect contributors from, hence why DHH and ESR would be opposed to CoCs in general.
I don't know about ESR, but DHH has acted in ways that make it difficult to believe he is making a good-faith, unbiased argument on CoCs, which means I'm not obligated to reciprocate and treat his argument fairly. (DHH oversaw a list at 37Signals making racist fun of customer names, and overruled his employees who complained, eventually leading to a mass walkout.)
To put it in Bayesian terms, the prior that he's making a bad faith argument is higher than any random person, and should be treated as such.
Is publishing an ethical standpoint a "trouble making"? Depends, doesn't it? What if you examine the most common top ethical viewpoints you are aware of. For me, it's loud groups like say, PETA, Extinction Rebellion, etc who are fairly populist.
Are they making trouble? Sure. But for whom? Would you personally do what these people are doing? Probably no. Would you personally do what the people they are "making trouble" for are doing? (In my example, Animal harm, empowering climate change?) I am going to suggest that you would probably say "no, I don't want to harm things/people/etc; as I would probably feel bad for doing it and being personally responsible".
If thought through like this - even if your examples of ethics are not what I chose - can you see the value in a strong, clear ethical position, even if it's to warn people? Can you see that it might challenge authority (trouble making), but that is not a bad thing a lot of the time?
PETA literally funded a terrorist convicted of arson.
> A page from the 1995 annual tax return (form 990) of People for the Ethical Treatment of Animals (PETA), showing a $45,200 payment for the ``support committee'' of Rodney Coronado, a felon. Mr. Coronado was convicted of arson in federal court for the 1992 firebombing of a Michigan State University research lab.
---
> Would you personally do what the people they are "making trouble" for are doing?
Would I eat meat? Yes.
Would I keep animals as pets? Yes.
Do I think it's ethical for humans to use animals for service, e.g., guide dogs for the blind? Yes.
Do I think it's ethical to use animal models in medical research? Yes.
All of these things, PETA are against.
Further:
- https://archives.fbi.gov/archives/news/testimony/animal-righ...
- https://en.wikipedia.org/wiki/Rod_Coronado
- https://www.govinfo.gov/content/pkg/CHRG-107hhrg77615/html/C...
> animals as pets
This seems to say they are perfectly fine with pets: https://www.peta.org/about-peta/why-peta/pets/
> guide dogs
Seems to imply they are not against service animals in general: https://www.peta.org/media/news-releases/monkeys-arent-pets-...
Not trying to defend anyone, just looking for objective evidence.
Fair.
## guide dogs
> [PETA founder Ingrid Newkirk] regards the use of Seeing Eye dogs as an abdication of human responsibility and, … is wholly opposed to their use. She has had at least one dog taken from its owner.
- https://archive.is/6IIo1
## medical testing
> Medical research is immoral even it it's essential
> Even If Animal Research Resulted In A Cure For AIDS, We’d Be Against It
- https://consumerfreedom.com/press-releases/153-even-if-anima...
## animals as pets
- https://en.wikiquote.org/wiki/Ingrid_Newkirk
- https://www.naiaonline.org/articles/article/quotes-from-the-...
## Bonus fun story
- https://www.theguardian.com/us-news/2017/aug/17/peta-sorry-f...
---
I could go on, but I think you get the picture. The utter insanity of PETA is actually very well documented, so if you have an evening, grab a bottle of wine and go down that ~rabbit~ hole.
I suggest the examples work even better with the context you add - you do not have to agree with the ethics or like them!
On the "funding terrorism" insinuation...
Did PETA publish an ethical statement about: - Protecting university infrastructure - Obeying authorities - Agreeing with negative media coverage about them
I sincerely doubt it.
Their misdeed in your view is donating $45k for a guy's legal defense, who was the spokesman of the ALF, not PETA. By that logic, any government funded public defender is the taxpayer condoning murder, robbery, etc. We can both agree objectively that isn't true - guilt by association is the fallacy there; funding a legal defense is separate from the act requiring the legal defense.
I would argue you have this talking point because of a concerted media effort to brand things as "Eco-Terrorism" - https://en.m.wikipedia.org/wiki/Green_Scare - and that is a coordinated effort to change the focus.
BUT, let's assume PETA are exactly as you say.
Scenario 1: they publish no standpoint, pretending to be a local book club who have simply enjoyed the prose of Peter Singer's Animal Liberation.
Scenario 2: as above, but they publish their ethical standpoint upfront and it is easy to access.
After you have gone a few times, one day a chap stands up, say he's the Lorax; has been a member for years; is head of the Once-ler Action Committee demands everyone hijacks a plane to fly it into the nearest highrise, because he's for the trees; buildings use timber and the North American Squirrel is suffering.
In which scenario are you more surprised? In which scenario were you given the most choice about how you can interact with the group; apply your own standards of behavior or what to expect? In which scenario are you better equipped to object ("we care about the wellbeing of squirrels, but your case is driven by a flimsy ideological argument that has little to do with the shared values!") In which scenario are you more likely to seek external help from an authority; because it is trivial to identify the extremism is out of place?
This is my point - having no stated ethics or CoC is objectively worse when radical/extremist viewpoints creep in due to malicious actors; vs at least publishing a basic standard.
No it isn't. We all have to pay our taxes. PETA didn't have to pay Rod Coronado.
> I would argue you have this talking point because of a concerted media effort to brand things as "Eco-Terrorism"
They firebombed research facilities to effect ideological change.
This is the textbook definition of terrorism.
> In which scenario are you more surprised? In which scenario were you given the most choice about how you can interact with the group; apply your own standards of behavior or what to expect?
The problem is the very obvious Motte-and-bailey fallacy that you're falling for here, as so many people do.
You brought up NixOS earlier. I like NixOS. I fund some of the development. I attend some of the conferences and meetups.
Any reasonable person in the community would be against violence, I'm sure you'll agree. The last time I attended a NixOS conference, I saw many attendees with… Actually you know what, I've written about this before. You can read it if you wish, and you might then understand where I'm coming from.
https://jezenthomas.com/2024/11/I-feel-unsafe/
[1] https://www.youtube.com/watch?v=kHOr2WH7V1k
Most software projects are ethically neutral and don't need a "standpoint." In tech, those "ethical standpoints" are often tacked-on by people who want to use them as a tool to exercise social control over other contributors, including project founders and visionaries. (There tends to be, in any given Western organization over n people in size, a clique that's really into this.)
I have no idea how CoCs are used in PETA, but obviously groups that have ethics as their core focus -- which includes religions and social welfare groups -- have long lists of proscriptions, policies, etc. I don't think that any of it necessarily applies to open-source software, though. It's apples to oranges.
> If thought through like this - even if your examples of ethics are not what I chose - can you see the value in a strong, clear ethical position, even if it's to warn people?
Well, that's precisely my point: The CoC itself is the warning. It's usually bad news in itself -- an exposed surface that's weaponizable against contributors who give to the project in good faith.
Normal people shouldn't need anything more than normal morality and acceptable manners to be good project contributors.
and I have a slightly used bridge to sell.
That, and also for selective enforcement.
I used to organize meetups and I visited meetups organized by others who had code of conduct, and I just never understood what they were hoping to achieve with that.
If someone behaves poorly, you can point at a document all you want, but it doesn’t help you deal that the problematic individual. A document that you put in a markdown file is not enforceable.
And we didn’t even talk about how it is being misused. People would point to these documents to silence and shut out people they don’t like and at the same time tolerate poor behavior that are clearly in violation of code of conduct by people they do like or whose politics or opinions they share.
It is all just a charade to help you pretend that you are impartial.
Has it occurred to you that's actually exactly why they exist? :)
These people (who push for CoCs so heavily) in my experience tend to hypocritically attack and censor opinions they don’t like, while not understanding why people won’t "accept them for who they are".
They are desperate to be the center of attention and love to play the victim.
It’s like the bullied becomes the bully sort of thing. They spend more time arguing over weaponized CoCs and ideological SJW politics instead of writing code. It doesn’t help that many of them self-admittedly suffer from mental health problems.
On a completely unrelated note, you very, very rarely find real fascists in open source software projects.
And for even less favorable characters it seemed that it was just powerplay by some actors that wouldn't convince their own mother that they are the most untoxic of them all.
There are people who will attempt to exploit any system.
... I understand that's the theory, but in practice, I've never seen it working that way.
I don't see how having the CoC affects any of this. If someone is behaving poorly, first of all, a CoC will not deter them. If someone behaves so poorly that you decide you need to remove them, the community (the small portion of people who give a f) should see why you removed them, and again, a made-up "contract" will not be needed.
It's ok to stand up for yourself and simply say (without pointing to a document you put in your repo when you were bored), that: "John Doe was behaving poorly, and I don't want to deal with him, I banned him, you don't need to like it, but it's my decision".
Just my 2c... I don't want to add more procedures to my open source projects or voluntary organizing. I'm doing it because I like it, not because I want to pretend I'm at a townhall meeting.
I think you mean, "if someone is behaving poorly, the coc did not deter them".
The people who it did deter aren't behaving poorly.
None of these things happen in real life.
You are so focused on the strawman of problematic people being mustache-twirling villains trying to disrupt spaces they dislike, that you're discounting the actual purpose of CoCs, which is to make it clear who your space is for.
Code of conduct is not about that. It's about how to behave. My community is not that special that you need a user manual on how to behave, you should have learned it by age 10, latest.
Technology Z meetup / user group is a space for people who are interested in Technology Z. Repository Y is a space for people who are interested in Repository Y.
If someone needs a CoC to figure that out, bad luck.
You want to start discussion about War X, vilify everyone just by being born in that country, please do it outside my repo / user group. Plenty of spaces you can do it and there, you'll be welcome to do so. Want to talk about evil black / white / DEI / right wing people, please also leave my group out of it.
Behavior is who people are. It's the 'content of their character' that MLK spoke of.
> My community is not that special that you need a user manual on how to behave, you should have learned it by age 10, latest.
And yet different communities have vastly different concepts of acceptable behavior. CoCs let people know whether their behavior is acceptable in a community.
1) point both involved and uninvolved people to the code of conduct when you end up taking action.
2) avoid disparity of enforcement within your team
3) funnel disagreements (from both teammates or community members) by focusing them on the rule, rather than on a general debate on how should the community should be managed.
If people commit a lot of energy to a community/project then for many "I didn't like this behavior, end of discussion" won't cut it.
Of course it does. If the community/project leaders are not aligned with your ideology, it's better to find one with alignment than to attempt to corner them with a written set of rules.
I'm sorry, but that's just not true.
You're treating humanity as if it's divided into two distinct sections: Those Who Behave Well, and Those Who Behave Poorly.
In reality, different humans have different ranges of ways they prefer to act, and most are quite amenable to reasonable, clearly-stated codes of conduct for interaction in a particular space.
There is a small subset of people who are either deliberately antisocial for the sake of it (trolls/griefers/etc), and another subset that are genuinely just assholes who will, if given the leeway to do so, cause endless problems in a community.
But there are many, many more who would cause friction with others in such a community without a code of conduct not because they actively want to, but because their unstated assumptions about how people should interact clash with the unstated assumptions of other people there. Having the code of conduct lets everyone coming in in good faith align their expectations and avoid these unnecessary conflicts. They're like a Session 0 in a TTRPG in that sense.
Hard disagree... I've never seen one have this effect. IMO you don't need a CoC to suddenly understand what should already be common sense i.e. don't be a dick. Either they were already going to act that way, or they weren't.
How do you think you would see it?
Under normal circumstances, what it would look like from the outside is just...someone not causing friction, because there is a code of conduct. Or someone causing friction, because there isn't one.
The former looks identical to someone who would never have caused trouble in the first place, and the latter looks, if not identical, at least very similar to someone who would have caused trouble, no matter what.
And the people who wouldn't cause friction are already behaving so they don't need one.
Another commenter (cannot find their name now but I saved the text) said exactly what my experience has been:
> A written code of conduct can legitimize petty disputes based on interpretations of the text, even if the issue itself is something easily addressable like using the word “master” in a programming context. It can become a tool for manipulation (pushing someone out for “CoC violation” vs simply correcting the wording).
> And the people who wouldn't cause friction are already behaving so they don't need one.
Both correct. By definition, in fact.
CoCs are for the people in the middle of those. Who do, in fact, exist.
It's about setting a shared understanding of norms.
It's about whether the kinds of jokes allowed among members are "as raunchy as you please", "polite jokes only," or "none".
It's about whether you're expected to work out differences in private chats, address them in public, or bring them to a moderator.
It's about whether your comments on a code review started by another member have to be addressed by the committer before the review can go forward.
Any time you think the way you do things in the open source project (or any other kind of community) you contribute to or run is The Natural, Obvious Way Everyone Does Things, you're probably wrong, and some other people or projects do things exactly the opposite way and think that's just as natural and obvious.
Whether or not anything needs to be written down afterwards seems like it would be a separate thing.
> should see why you removed them, and again, a made-up "contract" will not be needed.
It's not a matter of the action being transparent, it's the motivations. Sometimes, it's not clear to community members why the action was taken, if there's no CoC or rules. "They're being an asshole" is a lot more subjective than "They were breaking the rules"
> It's ok to stand up for yourself and simply say, without pointing to a document you just put in your repo, that: "John Doe was behaving poorly, and I don't want to deal with him, I banned him, you don't need to like it, but it's my decision". Just my 2c.
Sure, this might work for a small community or group, but the fiasco with Nix seems to suggest this isn't the case at a certain size. Some people apparently want accountability and transparency from their moderators.
> Just my 2c... I don't want to add more procedures to my open source projects or voluntary organizing. I'm doing it because I like it, not because I want to pretend I'm at a townhall meeting.
Great! That's fine! Not every community needs such things. Some do.
This is very much so for small communities who don't have the infrastructure to litigate issues in a legalistic manner... but, even in areas like public law, the rules don't really matter, it's the perceived authority and impartiality of the courts that keep a legal system up and running. (think of any controversial Supreme Court decision -- do people really care what the law actually says and whether the legal reasoning is sound... or do they just speculate about the political leanings of the judges?)
Since most people writing up CoCs aren't good lawyers or experts in drafting (and finding loopholes in) rules... having a smaller "attack surface" actually makes a lot of sense.
That said, if the community is large or important enough that it already retains some legal advisors, then maybe yeah, make the rules more specific or something.
And beyond a certain size formalizing that makes sense. Not as a tool for punishment or to point to, but so everybody can be on the same page and you know if someone acts out of line they do so despite better knowledge.
If a code of conducts contains stuff you are within the bounds of anyways, why would you care it is there?
If it would contain stuff you're within bounds of anyways, then it's entirely unneeded. :)
What I want to say here, is that a good code of conduct deals with the stuff that is open to interpretation and defines it. So if our punk-bandmate throws the singers gear on a pile we don't have to argue about different definitions of how we expect others gear to be treated.
So it is needed precisely because everybody thinks they are just acting normal and within bounds, even when the majority thinks they are not.
Maybe he don't want to exclude people who are outside of the CoC norms, but can still be valuable contributors.
What I like about the simplicity of our CoC is that anyone can read it in a few seconds, and we can point it out to people without seeming bureaucratic or annoying.
Happy to share with others. Complicated CoC documents I've seen at other groups don't seem to do anything besides giving the organisers a feeling of power/that they're doing something. Simplicity might be key here.
1. If you can't make it, let the host know the day before or morning of the event.
2. If you're playing at a venue, try to buy food or drinks from the venue. Don't bring lots of stuff from the outside.
3. Be kind and respect other people. Don't damage their games or act mean towards other players.
We're not super strict, but people have been perma-banned for sexually suggestive remarks or being assholes. I think we've had 3 or 4 really bad cases total. Most people get temporarily kicked out for violating rule #1 a lot.
Its the agreement to argue about a topic that is struck when you make rules.
Not seeing this is how..niholists proliferats with variohs plicit ordering liks might is right
You can't write a CoC that will prevent bad behavior from bad actors in charge, so it's worthless at best and a weapon for the unscrupulous at worst. What matters is who enforces standards of behavior, and if those people are decent and honest, no written code is necessary.
Humans should be able to interact politely in any setting and if they don't, the issue needs to be settled with good old human interaction anyways.
Sure, but someone who went to the trouble to get their view enforced in writing is probably already a zealot I don't want to deal with.
Depends a lot on the group size, too - a few hundred contributors probably needs some rules written down. A few dozen? Not so much.
Not because I enjoy reading or writing hate speech or anything, but these were places that didn't tend to have any obvious problems with troublemakers, so it felt self congratulatory. And don't even get me started on the sheer amount of bikeshedding the discussions around it became, mostly from people who'd never even contributed to the project.
It suddenly made me realize there were probably more productive and less frustrating ways to spend my time.
If I have to like you in order for us not to fight, I warn you that we're going to have to fight.
"Weird people" being discriminated against and harassed is why CoCs exist.
No, CoCs - or rules in general - are not inherently bad. HN has some, which the moderators and the community enforce well, and it's generally one of the best platforms on the Internet for intelligent discussion.
Yes, heavy CoCs can be weaponized and abused, if there is little or no trust between the community and its leaders. But with or without a CoC, such a community will always be prone to such abuse. You think moderators need to establish a CoC to push their politics on people if they want? How does that even make sense? Why not just... do that, without a CoC?
I don't think this is what generally happens, or what people are wary of. I think group participants [sometimes] coerce moderators into establishing a CoC in order to have a tool to reach for in service of silencing voices they regard as "problematic".
I'm going to push past this extraordinarily bad faith framing. I'm going to assume you're referring to people who are made to feel uncomfortable or are harassed by other members of the community.
So if that community doesn't have a CoC, and those members talk to the moderators, and the moderators take action... is that coercion too? Is that the moderators or those members pushing their political views on the community? Should the moderators just not do anything?
It has been my experience that there are both members of groups typically regarded as marginalised who have been harrassed, and also members of groups typically regarded as marginalised who harass others. There are surely more variations of this too.
My most recent experience of this was a member of a group typically regarded as marginalised harassing one of my colleagues — who is also a member of a group typically regarded as marginalised, but perhaps less so if you subscribe to the legitimacy of intersectionality — at a software development conference with an established CoC.
The incident was reported, and the repercussions for the harasser amounted to exactly nil.
> So if that community doesn't have a CoC, and those members talk to the moderators, and the moderators take action... is that coercion too?
No.
> Is that the moderators or those members pushing their political views on the community?
That really depends on the circumstance.
> Should the moderators just not do anything?
Moderators should take action on CoC violations as proportionately, fairly, and impartially as they can.
> I'm going to push past this extraordinarily bad faith framing.
It is extraordinarily tiring and depressing that anything proffered that contradicts the orthodoxy of the culture that most readily endorses the establishment of CoCs is immediately dismissed as an argument in "bad faith".
> No.
Then I'm not sure why it would be coercion for them to talk to the moderators about writing down the rules.
If I had meant "everybody", I would not have written "sometimes".
I think that happens less now that people are aware of the danger; but a decade or so ago it was a real problem because no one saw it coming.
Perhaps, but I think it may make the moderator more likely to side with the abuser if they are able to point to a specific part of the CoC that is allegedly being violated, even if that requires colorful interpretation.
However, there's probably a cutoff point for core infrastructure where we should move away from having a single person in charge.
If I start a project that attracts contributors[1], I don't see anything wrong with rejecting someone's CoC "contribution" with "I am the code of conduct. We don't need another one."
==================
[1] I try not to do that, btw.
Yes, but often the projects where this happens are just big enough to where one person cannot realistically maintain their own fork to the same level that users will expect if they are looking to jump ship.
What I've seen happen more often than not, is even if the person does attempt a fork, they either get constantly attacked by existing users, or stop working on it within a year, or both.
> Participants are expected to be tolerant of opposing views.
If you can't tolerate that others will have different perspectives to you then it means you're likely to be a very difficult and inflexible person to work with.
Also it would be very off-topic for a programming language forum.
> Participants must ensure that their language and actions are free from personal attacks and disparaging remarks.
And anyway, rhetoric which advocates for killing groups of people would be very off-topic for a programming language discussion forum. Unlikely it would come up in conversation except for deliberate trolling.
1. Someone posts something on twitter that someone else finds offensive
2. Someone proposes a CoC rule banning bigots from the community, which raises the question of "who defines who is a bigot"
TFA mentions a third way; a remark at a conference is overheard.
Then someone will point out that they might have this stuff on their Github profile, or website. They're free to do so, of course. But it would be wrong to remove them for that, right? But then any trans contributor that sees this crap is what, forced to work with them anyway?
It is a tiny fraction of the people I know and have interacted with over an extended period of time who has not made a remark that could be construed as bigoted.
I have seen moderators called bigots for suspending (instead of banning) someone who made an inappropriate remark.
My wife and I have been accused (behind our back) of misgendering someone when we were using the pronouns that we had privately confirmed she preferred.
If you create a CoC with real teeth, then instead of the BDFL or core team or whatever controlling who is in the community, it's the people in the community who are most interested in accusing people of violating the CoC that have control over who is in the community.
If a project decides it won’t welcome people who believe what almost all conservative/traditionalist Orthodox Jews believe (even if they keep those beliefs to themselves in project forums), it is essentially deciding that Jews (of that kind) aren’t welcome-isn’t that antisemitic, and in itself a species of eliminationism? (not with respect to Jews in general, rather with respect to Jews of that kind)
And the same point holds for “Sunni” or “Shi’a” or “Catholic” or “Protestant” or “Eastern Orthodox”
If that stereotypical Orthodox Jew wants to be a valuable community member, they can keep their hostile opinions to themselves, and nobody will consider them troublemakers.
Obviously they won't feel welcome because they realize that the majority would despise them as bigots if they expressed intolerable opinions, but hopefully it can become a reason to question their ideology.
This is what an intolerant troublemaker would do, demonstrating that they are worse than the restrained bigot they are denouncing.
The will to hurt people is, or should be, a good indicator of which side is more wrong.
Diverse views on software development? Great. Diverse views on whether various groups deserve human rights? Not great.
It would be unreasonable to expect everyone to have the same perspective on political issues.
(As a personal preference, I'd rather not know the political views, legitimate or otherwise, of people I work with. It's not relevant.)
As to your first - if people with a strong set of ethical and moral principles "just shut up" about what they considered ethical and moral essentials ... then they wouldn't be who they are. The only people who don't show what they hold good are people who don't hold as good much of anything.
Now if we're just talking "opinions" here (about things that are not ethical and moral, merely matters of taste), then yes, a person with "strong beliefs strongly held as a universal principle" is someone who is just an ass. But if I know someone is a raving Detroit Lions fan "on the internet", what kind of a person am I if I can't work with them?
I have only ever seen CoC's abused to push out people with anti-social just views.
What matters is that people are operating in good faith.
I would also say that IF you have been accepted as a member of a community then you and your feelings must matter to that community unless and until you are ejected from the community. There needs to be a system for accepting and expelling people, and that system should rest on the judgment of people that the community has selected as trustworthy (until and unless those people are expelled).
Any asshole can claim to be acting in good faith, regardless of what they've done.
A good moderator will shut that nonsense down immediately, but a good moderator wouldn't need a CoC to do it. All the CoC does is give the troublemaker a tool to start playing rules lawyer, in the hope that the moderator will get tired of it and give in.
Some people think the answer is to have a CoC that's too simple for rules lawyering, like a one line "Be excellent to each other." But even that can be twisted, so it would be better as a project motto than as an official CoC.
Sooner or later it boils down to someone reasonable enforcing some boundaries, with or without a CoC.
This is the Trammel problem: if you want a PvP-enabled project, you discover that people are mostly interested in the part where they hurt others feelings and then go bananas when their own feelings are hurt.
> needs to be a system for accepting and expelling people
The private member's club is an old institution. But people tend to notice and object when it ends up being white guys only.
I said that a community must be a place where every member’s feelings matter. My feelings matter. Your feelings matter. But that doesn’t mean you can’t say things that annoy me (which you just did and I bet you don’t regret it).
You can say hurtful things as long as you are acting in good faith— saying what you believe is true and helpful.
You might think you are disagreeing with me. Nevertheless, you are demonstrating part of what I’m talking about: social life is unsmoothable without draining it of meaning and impact. Let’s instead develop resilience.
But what I worry about is that it may presume that the staff themselves already operate in (your interpretation of) good faith, and I don't think that is always the case.
What is a user's recourse when they disagree with the mods? And what says they will comply with any decision reached from said recourse?
You could say "we must allow disagreements", but at some point this becomes a paradox of tolerance and then you risk it devolving into pointless arguments on either side.
I think the whole "good faith" part could only be enforced by a universally trusted party, like maybe a robot. But even then, people will disagree about how it operates... so maybe this problem is impossible to solve.
I am a pluralist (a person who accepts that he must live with people he doesn’t necessarily like) not because I want to be, but because the alternative is constant rage and war.
Take any social group, anywhere, ever. Whichever one you choose: there are people who care about each other to some degree, and who hurt each other to some degree, and who have some sort of procedures and heuristics for dealing with that.
I suggest heuristics based on accepting the fact that people will behave in ways that irritate each other, even when a community is maximally healthy. Let’s accept that as normal. Then what? Then let’s work on what it means to be a member of the community. Let’s establish a protocol for membership based on a hierarchy of trust, or prestige, if you will.
Yes, if the trusted people are actually corrupt then your community is screwed. Go and make a new one.
Focus on building personal tolerance and resilience. Distinguish between matters of taste and matters of conscience.
To anyone who says this system leads to discrimination: ALL systems lead to discrimination. Yours does, too. Humans are like that. This problem can only be solved from the heart outward.
The implied subtext of "avoid topic the US finds morally objectionable and when in doubt act like an American would" is what I dislike from a theorical point of view but the truth is, it doesn't really matter on a day to day basis.
So yes, CoC seems mostly harmless but also mostly useless. I tend to agree with the article point that if this is the case, keeping them short seems optimal.
While it would be nice if all the ignorant assholes in the world lived in America... this is not the case :)
This is further proven when any attempts to discuss said rule/policy are immediately shut down with even more staunch black-and-white opinions and zero empathy... even if you wait until later to discuss it in a different setting.
Not having a CoC doesn't mean a project is going to be unsafe to work in. But it means when another community member refuses to work with you, or belittles your work constantly, there is nothing to be done. For many, why take the risk. This means that projects are starving themselves of contributors because they don't create an environment that is safe.
Ruby's "CoC" is actually a fantastic example of why you need to spell it out too. "Participants are expected to be tolerant of opposing views." is often weaponized by abusers who like to paint basic requests like "please use my chosen name" as "not being tolerant".
For software projects that are overwhelmingly conducted online the very concept of "marginalized group" is close to irrelevant and meaningless [1].
I think what happens is that some people want to be very, very vocal about whatever "group" they belong to and want to feel offended and oppressed. In recent years, arguments and campaigns against specific technical terms ('master', 'blacklist', even 'legacy code' spring to mind) are examples of this, IMHO.
[1] https://en.wikipedia.org/wiki/On_the_Internet,_nobody_knows_...
I wish this were true, but it simply isn't. If a group is full of white cis heterosexual guys and someone turns up with a random screen name and says nothing about themselves, everyone assumes they are also a white cis hetero guy even if they're not. The implication is "you have to conform, and if you don't then you don't belong".
The reality is that for many people, their mere public existence is seen as a political statement. Often times asking for the most simple of accommodations or changes is seen as "being vocal" or starting an argument.
I'll give you a hypothetical. Let's say a group of developers is all-male, and a leader starts off every meeting with "hey guys". Then, a developer who is a woman joins the project. They ask that leader "When you say it like that it implicitly excludes me, It would mean a lot to me if you said 'everyone' instead." I think that's a pretty reasonable request, it asks very little of the leader (to change one word), has no impact for everyone else, and means a lot to some. But to many, many people that would be viewed as "suppressing speech" or "weaponizing oppression".
I can agree that heavy & strict CoCs can be daunting and probably overkill for small open source projects. And they're far from flawless, as shown by the Rust mods resignation incidents. But to say they're useless and anti-meritocratic is to forget (and/or silence) these people that wanted to contribute in an environment where they wouldn't feel threatened (incidentally, sometimes despite being skillful contributors, so much so for the supposed meritocracy of the CoC-less projects).
I'm not sure strict CoCs are the answers to these real problems, but this feels like dismissing these problems altogether.
I feel that having a detailed COC, while a very good sentiment in theory, in practice must bring about people who will try their best to skirt around the edge of COC and make trouble for the maintainers - who I expect want to stay "nice", but they're forced to act harshly in the end anyway.
https://eev.ee/blog/2016/07/22/on-a-technicality/
91 more comments available on Hacker News