Earlier quoted context omitted.
> I've never seen one have this effect. 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 ver…
Presumably the code of conduct was introduced to solve a problem. So I'd be interested in hearing about an example of a community that had problems with their social fabric, and then introduced a code of conduct, and then could demonstrate that those issues in their social fabric were addressed.
Heavy codes of conduct are unnecessary for open source projects
161–170 of 270 posts
Re: Heavy codes of conduct are unnecessary for open source projects
#162> DHH condemned detailed and strict CoC like the Contributor Covenant as a “trojan horse” that should be purged from projects. ESR went even further, asserting that CoC are nothing more than a “tool for troublemakers” and that the best course of action is to delete them entirely from projects. At this point, in 2025, does anybody seriously doubt that they're a "tool for troublemakers"? A lot of people who would other…
Let's restate your points a bit, but using the words "ethics" rather than CoC. 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 doin…
Re: Heavy codes of conduct are unnecessary for open source projects
#163Earlier quoted context omitted.
No, typically this issue is focused around spaces like female-only refuges and safe spaces, locker rooms and changing rooms, prisons, sports competitions, and so on. The divisive point being whether males who say they are female should be refused or granted access. That you have chosen to characterise this with wording like "anti-human bias" and "demanding human rights apply" further illustrates my point.
No, that's not the typical focus of the issue, and repeating that over and over won't make it so.
In the UK, where I am from, the counter to the trans ideological position tends to be from a feminist-influenced perspective, emphasising women's sex-based rights.
Re: Heavy codes of conduct are unnecessary for open source projects
#164The thing is that codes of conduct do not help honest actors “regulate” and deal with troublemakers. 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 pu…
> 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. Has it occurred to you that's actually exactly why they exist? :)
There are people who will attempt to exploit any system.
Re: Heavy codes of conduct are unnecessary for open source projects
#165Earlier quoted context omitted.
This is one of those things that falls apart on the actual content. If you have a trans contributor and someone who comes in with trans-eliminationist rhetoric, you can't then turn round and say the trans person is being "inflexible" for refusing to work with them.
Likely more than 50% of the world's population agrees with viewpoints that some would label "trans-eliminationist rhetoric". So if you are saying anyone who ever expresses such viewpoints–even in forums completely unrelated to the project–is barred from contributing to it, you are potentially excluding more than half of contemporary humanity.
Re: Heavy codes of conduct are unnecessary for open source projects
#166Earlier quoted context omitted.
That would be covered under the next part of the Ruby CoC: > 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.
Holy moly, what kind of open source projects are y'all working on? I don't even understand how these topics could come up in a Pull Request. Are people writing and reviewing code in these projects?
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.
Re: Heavy codes of conduct are unnecessary for open source projects
#167Earlier quoted context omitted.
Likely more than 50% of the world's population agrees with viewpoints that some would label "trans-eliminationist rhetoric". So if you are saying anyone who ever expresses such viewpoints–even in forums completely unrelated to the project–is barred from contributing to it, you are potentially excluding more than half of contemporary humanity.
A community doesn't exist for "the majority of the world". It exists for its community. If a community doesn't want bigots (as they shouldn't), they absolutely should exclude them.
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.
Re: Heavy codes of conduct are unnecessary for open source projects
#168Earlier quoted context omitted.
> The way I see it, the people who would cause friction anyway won't be stopped by a CoC. > 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.
I think if someone needs to be told to be nice... it's time to grow up. Open source projects are not your mother and we shouldn't have to treat people like children, nor get chastised for having that (IMO very reasonable) stance.
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.
Re: Heavy codes of conduct are unnecessary for open source projects
#169Re: Heavy codes of conduct are unnecessary for open source projects
#170The thing is that codes of conduct do not help honest actors “regulate” and deal with troublemakers. 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 pu…
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