Code of Merit: A meritocratic approach to project management (2016)
github.com
github.com
People who are ostracized by projects with a Code of Conduct.
Or, to put it another way, if you're a jerk and you argue with other contributors about an on-topic issue in a jerky way, then under a Code of Merit, you still come out on top as long as you're technically correct (the best kind of correct!), even if it leaves other contributors feeling put down.
Granted, there is some overlap. For example, both the Code of Merit and most codes of conduct disallow disparaging remarks based on protected characteristics. But the Code of Merit disallows them because they're considered irrelevant to the project, whereas codes of conduct disallow them because they're affronts to dignity.
I do take issue with many codes of conduct in the tech space, because I think they tend to be written in a bubble world where everyone assumes that everyone else thinks just like them, but a Code of Merit sounds like it's even more problematic.
There are a lot of very intelligent people who see problems with society and critique society, but society doesn't like that much. Intelligent people do very good work and tend to get along with other people who think deeply.
If an affront to dignity is simply a well thought out critique or parody of society, I can see Code of Merit projects doing very well indeed...
Nobody. That doesn't even seem to be the intent; it's not so much something to be adopted on its own merit as it is a passive-aggressive critique of real codes of conduct. Note how it repeatedly addresses what one may not do to address any kind of conflict or bad behavior, but it doesn't spell out any mechanisms to enforce even its own rules. Contrary to another commenter who says this can and should exist alongside a code of conduct, I interpret this as (intentionally) undermining any such companion.
It's just a not-so-clever way to imply that people who believe in codes of conduct don't believe in meritocracy (paragraph 4), lack technical prowess (para 6), seek disruption and deviation (paras 7 and 14) - all without actually having the guts to come out and say so. Thus it falls afoul of its own injunction to "discuss or debate the idea" (paragraph 9) because it doesn't even mention - let alone address - the arguments in favor of what it seeks to destroy.
But it happens!
There are people rage-quitting stackoverflow/stackexchange communities expressly because of they can't abide with the new initiatives/CoC that say one has to be nice and get along with others.
I guess this is yet another manifestation of that impulse. Maybe someday someone will write up a psychological analysis of this kind of behavior. I sure don't understand it.
I would like to read that; both what's driving the thinking behind adoption, and the responses.
You could apply it to any organisation that requires you to sign up to its rules before joining.
> It seems insane to me that someone would profoundly object to guidelines that effectively say "don't be an asshole".
Does this help? https://news.ycombinator.com/item?id=18075200
> Does this help? https://news.ycombinator.com/item?id=18075200
But I still can't fathom a _real_ situation where CoC would cause me to reconsider participation, let-alone quit and look for alternatives which serve up something like that "Code of Merit".
In the high-profile spaces which have implemented CoC's, they've been a reaction to long-established patterns of bad behavior (I am thinking specifically about stackoverflow). It remains to be seen whether the CoC in stackoverflow helps, but I don't think it hurts.
In general, I think online communities are much more prone by being overrun with assholes than face-to-face communities. In the case of stackoverflow, they've game-ified the interactions to such an extent that it has become a very weird place to ask a question. In their quest for quantifiable objectivity, they've attracted personality types that think it's OK to be hostile in order to satisfy what they think "the mission" of stackoverflow is. It has gotten bad enough that people are reacting and their new CoC is their attempt at making amends.
Offered as a possible explanation without taking a side: it is because the author of the CoC is perceived as asserting their moral superiority over the others, and the others don’t recognise that person as having earned the right to do so, such as by being a long-standing member of the community with an exemplary track record themselves. The actual content of the CoC isn’t the issue.
In the specific case of SO, it’s probably that certain behaviours were actively encouraged by the owners of the site via points and badges, then suddenly they changed their minds. People feel stabbed in the back.
I haven’t ragequit anything, this is all just a theory, not direct experience
Or to put it more succinctly: People see a bait and switch. The superficial language doesn't really seem all that objectionable, but if you look into the ideology behind it, you might find they have a very specific idea of what "don't be an asshole" means that maybe doesn't quite match what you'd expect.
> you might find they have a very specific idea of what "don't be an asshole" means that maybe doesn't quite match what you'd expect.
For some, that means finding bizarre loopholes far outside any reasonable intention of the rules. For others, it means attempting to enforce the rules with such rigidity that almost anything can be seen as a violation.
I think a healthy community will realize that it is not their rules that makes them resilient, but rather their ability to use sound judgement and be flexible about problems and solutions. Linux will not be destroyed by a CoC that tries to be more inclusive even if there are attempts at abusing that CoC.
If the leadership interpreting those rules are reasonable then they wouldn't need these rules in the first place, if they are not reasonable then the rules are useless.
Especially since CoC are most often applied in a very Hypocritical way. The CoC states "Being respectful of differing viewpoints and experiences" which is however only true if you have one of the approved viewpoints. Which we are seeing right now with the Linux CoC. Of course no one does anything about all the slanderous accusations that get made to oust someone with the CoC even though those accusations themselves are violating the CoC.
It is also especially worrisome that these pushes for CoC or language policing come mostly from the outside and try to dictate the rules you need to follow and the rules that you need to make people in your project follow.
What exactly do you believe that this CoC addresses by the way? I am generally unconvinced that a CoC does anything positive at all, but what is it that you believe that it does?
It is also suspicious to me how this change was seemingly not discussed in any way prior and that it was a very sudden change for him.
The way a CoC would work, I think, is hard to quantify.
Sure, it may mean that some folks rage-quit on principle, some will continue bad conduct and get themselves kicked out, some will subvert the intent of it one way or another.
But if a CoC is "successful", it will mean that gradually you'll start to see folks who were previously under-represented start to contribute. You'll see more diversity and less fear and loathing. Is that a worthy goal? Yes, for many.
"Worthy Goal" Has that worked anywhere in practice? Who is underrepresented right now and why? Do we know?
The type of diversity archived by a CoC like this is litteraly skin deep anyways and might cost you diversity of thought. We already see "wrong" think beeing excluded.
> Linux will not be destroyed by a CoC that tries to be more inclusive even if there are attempts at abusing that CoC.
Also, apart from the fact that this isn't an argument in favor: How do you know that?
Also, how does it try to be more inclusive by declaring more behavior off limits? I mean, it's a set of rules that mostly specifies what you can be banned for. Now, you might also dislike those things that are declared unacceptable ... but that doesn't really make it more inclusive, does it?
And mind you I am not saying that being more exclusive is necessarily a bad thing, but I very much dislike this kind of newspeak because it seems manipulative to me.
For example, it says "Examples of unacceptable behavior by participants include: The use of sexualized language or imagery [...]". That is codifying a very specific value, namely one of sex negativity. If you are sex positive, you are at risk of being labeled an asshole for that. (And mind you, that quote continues "[...] and unwelcome sexual attention or advances", so it is clearly in addition to what could be reasonably considered a neutral "respect others' personal boundaries" sort of "don't be an asshole").
Then, there is this whole problem of not considering people who have deficiencies of sorts with regards to social interaction, and it seems to me that that is very much part of the ideology. Try to read the kernel CoC from the viewpoint of an autist, and try to reflect on how included you feel from that perspective when you are essentially told "because we want to have a welcoming environment for everyone, we shun people like you".
And more broadly, not necessarily directly tied to the specific authors (I just don't know the specific authors well enough to be sure), occurrences like this come to my mind: https://www.berkeleyside.com/2017/07/21/kpfa-cancels-richard...
"Inappropriate" and "offensive" are so subjective that you could argue the "code" doesn't really codify anything, it just is a tool to use and to interpret as you see fit if you have the power to do so, while claiming that it's somehow a more objective judgement that you arrive at based on "rules that have to be followed".
Which parts of the code do you think are unwelcoming to people with autism? Most that I know are neutral about it or are pleased that neurotypicals have started to recognize the benefits of explicit rules. I know of a couple of organizations where someone on the spectrum led the adoption of a similar code.
Well, yeah, sure. But someone else can be sex positive and feel like using sexualized language, can't they? I mean, I am obviously not saying that the CoC should say that everyone should be forced to use sexualized language. And the fact that you can be a sex positive person and still feel like sexual things are more of a personal thing for you, say, doesn't change the fact that banning people from using sexualized language is sex negative, does it? Some sex positive people feel like anal sex isn't their thing. Making a law against anal sex is still sex negative, isn't it?
If you don't feel like using sexualized language, sure, more power to you as far as you expressing yourself is concerned. And really, as far as expressing myself publicly I'd generally be among those, it's not really my thing, at least not currently. What I object to is the authoritarian style of enforcing a particular set of values that have no direct relation to the goal of the project. And even moreso if it's done supposedly in the name of "being more inclusive".
If you are suggesting that someone could be sex positive and think that sexualized language should be banned in a "public global all-ages quasi-professional environment", really, I don't think so. Sex positivism in a nutshell is the view that there is nothing bad or shameful about sex per se. It's a thing many people do and enjoy, just as many people do and enjoy eating ice cream (and others don't, and that's fine, too). If that's your view, I don't really see how you could go from there to supporting a ban on using related language, pretty much no matter what the context. Either you think sex should be a taboo or you don't!?
> Which parts of the code do you think are unwelcoming to people with autism? Most that I know are neutral about it or are pleased that neurotypicals have started to recognize the benefits of explicit rules. I know of a couple of organizations where someone on the spectrum led the adoption of a similar code.
Do they prefer rules over no rules or explicit rules over implicit rules? If there is a rule that is enforced against you anyway, it's probably better to have it spelled out explicitly (than to be surprised by the enforcement of a rule you hadn't picked up on). But that does not justify introducing any particular new rule, only writing down what's already there anyway. And even then writing down what's already there does not justify those rules, it at best creates the opportunity to reflect on the appropriateness of those rules, and to possibly throw some of them out for good. I would think the objection is to being held accountable to rules they aren't aware of, not so much to not having rules.
Also, I'd be curious how similar that code really was. For example, "other behaviors that they deem inappropriate, threatening, offensive, or harmful" is very much the opposite of "explicit". It's so vague that if you think about it you realize there isn't actually any rule there. The only thing that's really there is the "rule" that the maintainer gets to decide the actual rules on the spot.
Edit: As for something not actually being a rule, I think this is a good test: Could you possibly use it to defend yourself against an accusation? No matter what you did, you could never justify your behaviour by saying "What I did was not deemed inappropriate, threatening, offensive, or harmful by the maintainer(s)".
The people I know on the autistic spectrum understand that there are never "no rules". With respect to language like "other behaviors", they understand the concepts of loopholes and judgment calls. They also understand that the people in charge can always make new rules even if the rules don't say so.
I don't think I said anything about sex being "just like ice cream", because that doesn't really mean anything. I specifically pointed to treating it as a taboo subject, and in that regard I would think the general consensus is that sex positivity implies considering sex to be just as non-taboo as ice cream.
> Is it also authoritarian to allow only one of them in the office?
Yes?
Just to remind you, none of this is about getting on people's nerves with topics they don't want to discuss or intentionally making people uncomfortable for the sake of making them uncomfortable or anything of that sort. This is about a ban on a certain kind of language, and only that particular kind. Isn't it strange that there is no ban on talking about death? Also a taboo for many people, also something you can make people really uncomfortable with, and also something some people don't mind. But for some reason, sex is banned explicitly, death is not.
> The people I know on the autistic spectrum understand that there are never "no rules".
I think you misunderstood my point. When I wrote "no rules" that was meant as "within a given scope", not as a global qualifier of "a world without rules".
> With respect to language like "other behaviors", they understand the concepts of loopholes and judgment calls.
The problem isn't the "other behaviors", it's the "deem[ed] inappropriate, threatening, offensive, or harmful". Those are highly subjective criteria. It's like writing criminal law that says "The judge can sentence the defendant if they don't like what the defendant did". And doubly so for autistic people, given that your best chance at avoiding punishment is to guess what the other person finds inappropriate, threatening, or offensive.
> They also understand that the people in charge can always make new rules even if the rules don't say so.
Which is besides the point. First of all, it's trivially true that people who do have power can use it, but that doesn't automatically justify their actions. But more importantly, none of what I wrote is about whether new rules can be made, but about the fact that applying new punishment rules retroactively is unfair, and that non-rules such as "[...] or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful" are necessarily de-facto applied retroactively as the rule itself does not specify the offence.
Proper criminal law specifies in the law itself what the offence is and how it is going to be punished. The point is (a) that it's up to public consensus to decide what is punishable and what is not, not to some judge, and (b) you are supposed to be able to look into the law to find out whether what you want to do is forbidden or not. None of that precludes new laws being added. But you cannot be punished for things that weren't forbidden yet when you did them.
I take issue with them because a Codes of Conduct doesn't make a space safe. And also because if we need a written list of what behaviour is tolerated, we have a much greater problem than a code of conduct will solve.
I've seen people write about the former; I haven't about the latter. I find a CoC offputting because it equates me with the lowest of the low. It says I can't be trusted to behave like a decent human being and need to be told what's right and what's wrong, like being back at school.
I also see it as darker than "assumes that everyone else thinks just like them". Some - not all - are about controlling the world into the form the CoC proponent(s) want it to be. The CoC goes beyond its words and into society.
Neither do I support the Meritocracy thing, as I've had it used on me too many times by people who are super-smart and see that as a reason to be jerks.
Do you leave your door unlocked and your keys in your car? If not, aren't you assuming that there are some people out there who can't be trusted? If I come to your house and find it locked, should I be insulted that you've not "trusted me to behave like a decent human being"?
Are you meaning to equate those who don't follow CoC's to criminals?
My response would be that those are societal norms, we define the transgressors as law breakers, and have a criminal system to deal with them. People take precautions against them.
In the same way I expect to walk into a pub and not get punched in the face, I expect to take part in an open source project and not shit all over someone / be shat on.
Do you have the same reaction to automated linters or being told to write unit tests? What about the enforcement sections of the GPL? I mean, you, not being the lowest of the low, aren't going to write buggy code or reuse software unfairly, right? Isn't it an insult for people to imply that you might?
There's a huge difference between technical processes that have gone through extensive peer-review processes and survived decades-long debates until a technical community reached the consensus that the practices indeed produce better software and brand-new social practices that are difficult to universally enforce. Making the statement "I don't need a list of unprofessional conduct to maintain a professional community" must be true, since you could never enumerate all unprofessional conduct anyway. You'll either leave something out (so the trolls can say "na na na, you can't get me!", in which case the method didn't work) or you'll encompass too many behaviors, which means different trolls can selectively enforce the terms of the CoC. Either way, it seems like a losing scenario.
>What about the enforcement sections of the GPL?
The terms of the GPL are criticized by many; that's why some projects choose different licenses.
I'm curious - I've seen debates about test-driven development, or how to appropriately test things, but never debates about whether testing or automated linting itself produced better software.
> The terms of the GPL are criticized by many; that's why some projects choose different licenses.
Sure, but I've never heard anyone criticize it on the grounds that it insulted them or called them untrustworthy, and be taken seriously. Same with testing, come to think of it. There are lots of serious debates; "Are you calling me a bad coder" is not one of them. I'm happy to see debate about different forms of codes of conduct, but why are we taking "I am insulted by this" as a legitimate argument?
This is totally outside the scope of your specific point, but I think it is important to note that the objective "a better community" is difficult to measure. My question: is a CoC an evidence-based response? Many software communities have moved to adopt CoCs, but what are the effects? Is there selection bias in studying a community with a CoC because (by virtue of accepting the CoC) the community is more likely to reject unprofessional behavior? How do CoCs function in a global society where actions that are appropriate in one culture might be taboo in another? Who/What is the arbiter of cultural disagreements - NAP? But the understanding of violence/aggression once again falls apart in the wake of cultural differences.
Ultimately, the answers to these questions are decided by the CoC, but who are the authors and evangelizers? The contributor covenant first appeared in 2014, and rapidly (e.g. within 1 year) saw Google (for example, there were many other large tech companies) adopt it for public projects. I believe that we should consider what the motivations are for these multi-national companies to so quickly adopt these rules.
Who the hell chooses a project to contribute to based on its "code of conduct" (the notion which didn't even exist for much of history of open source)? I thought people write code to solve actual technical problems, not just to flame each other on the Internet.
This sounds good, but a clause like this can easily backfire. What happens if a high ranking member is (whether they know it or not) a bigot or sexist? Anytime someone tries to challenge them calling out their behavior, they're likely to point to this Code and say "stop making this about gender/race as that violates the code of merit". They can use the very rules meant to stop them as a weapon to silence those who would criticize.
The document presumes good intentions by all those participating. Good intentions don't work- mechanisms do. I see no mechanisms here.
It certainly does not sound to me like this Code of Merit is specifically for supporting sexism like you imply here. It is just specifically against the Idea that Merit or Meritocracy is "dead" which is a common view of those pushing for the usual Code of Conduct stuff.
Where is this happening? The CoM says it can't happen on the project mailing list, or the project forum, or the project issues page ... Doing it on Twitter? Not within the project and fair game.
Also, why is "fair game" a concept that applies to whether misbehavior can be challenged and not to the misbehavior itself? If the contributor tweets, "Ew, all these incompetent purples keep making trash PRs," why should that itself not be considered outside the bounds of "fair game"?
People are free to express their dislike of the Greens or Purples on Twitter. And they'll catch the fallout on Twitter. Why should these conversations pollute the project documentation?
If the lead maintainer shows its true colors and refuses to become a decent human being, people will leave the project. If the project is truly important, someone will fork it and create a new project with a new community.
Personally (and selfishly), it comes down to this: years later, when I'm looking for a solution to a problem and $SEARCH_ENGINE returns an email thread, I don't want to sift through dozens of messages about the drama between the Greens and the Purples to find exactly the single line of script that solves my problem.
"Also, why is "fair game" a concept that applies..." I don't understand. Either you've misread me, or you're bringing in topics that I didn't address so I don't know what this is about.
What do you think gives you the right to demand inclusion?
It would require them to specifically search for information about the author, which I can’t imagine anyone doing. That, unlike posting something on twitter, would indeed be indecent.
I’ve seen many instances of project contributors being flamed because of their “bad” behavior on twitter or elsewhere, but have not seen anyone accused not judging a specific contribution based on its merit.
Then we can avoid having an HR department for every open source project.
These are different goals, and the former is sufficient if you don't necessarily want a community (e.g. it's a corporate code drop) or you see some reason why people will produce patches regardless. But it's the wrong priority for major open-source projects created by decentralized, often volunteer teams. Those projects need active bug reporting, design review, thinking about future goals, feedback on existing designs, shared visions, etc. A process that simply lets you accept correct patches, should they somehow show up, won't get you there.
This is the process that Rust core team member Aaron Turon calls "pluralism and positive-sum thinking" https://aturon.github.io/2018/06/02/listening-part-2/ , and former Linux kernel contributor Valerie Aurora calls, interestingly, "feminist" https://blog.valerieaurora.org/2014/10/03/operating-systems-... . But whatever you call it, it's very different from a process that just answers "is this patch being reviewed with sound reasoning." Such a process would have soundly rejected v1 of the patches implementing all the things requested in those articles and likely discouraged contributors (again, for sound reasons, not out of bigotry), and not produced technically better and more meritorious work.
but to get to your point: on a merit based system every reason to decline a contribution should be based on the contribution, not on the contributer. everyone should be able to validate those reasons. if you got a sexist and he declines your contribution with a sexist reason that should lead to consequences for him. thats what your quoted line entails. the high ranking member violated it because he took your sex/gender into account when considiering your contribution. did he decline with racist remarks? he violated it again because he took your race into account. for me that would be a far better system because it does not put the control in the hands of the few maintainers, it puts the control in the hands of the whole community.
> Is [...] telling [...] women that they're shrill and need to tone it down and be less emotional, a sexist remark?
if it targets all women i would say yes. if its in a discussion and alice IS too emotional and shrill i would say no (but its badly phrased).
everyone should be able to take a step back from a discussion and reflect. am i too emotional? did i maybe take a wrong turn? dont take everything personal. sometimes text does sound angry and agressive, but wasn't meant to be. people are not good at communication. allow some room for misinterpretation.
Why not just replace the code with "No one can possibly behave poorly for the project, just believe everyone" and be done with it? Seems equally effective.
https://en.wikipedia.org/wiki/The_Rise_of_the_Meritocracy
> "It is good sense to appoint individual people to jobs on their merit. It is the opposite when those who are judged to have merit of a particular kind harden into a new social class without room in it for others."
Here are the two key criteria from the Code of Merit governing how contributors are rewarded:
> 4. Authority or position in the project will be proportional to the accrued contribution. Seniority must be earned.
> 5. Software is evolutive: the better implementations must supersede lesser implementations. Technical advantage is the primary evaluation metric.
However, these are inherently subjective measures, dependent on who is among the project's "managing members" and thus in a position to propose candidates and render judgement. At the very least it is an unstable system in the absence of formal governance mechanisms (e.g. 2/3 majority rule on proposed candidates) and committed leadership.
Ultimately, it is frighteningly difficult to avoid calcifying into an exclusive group, fulfilling the satirical prophesies of "meritocracy".
It is difficult for _any_ group to not calcify into a leadership position, but I'd rather have the calcified remnants of those who produced something at some time, instead of having an arbitrary committee based on modern liberal ideals and pushed by an external group.
This type of code will be chosen by the kind of people that were angry about the linux CoC. So sadly even though this document has nothing obviously wrong with it, it will be a huge red flag on a project.
Sure, though note that this description could just as easily apply to "Black Lives Matter".
It is something, but it is clearly not about inclusion or anything. Not that harassment was ever a significant problem in any repository or mailing list I visited.
I think a general request for being polite is always a good thing. Mandatory behavior expectations are not. And this CoC reeks like it.
I beg to differ. It's innocuous only at the most superficial level. Even a moment's reflection on how it focuses on what one may not do to address any kind of conflict, without providing alternatives, makes it pretty darn clear that this is not intended as an honest complement or critique of codes of conduct. It's more an instrument of sabotage, and that's pretty objectionable.
So, the meritocratic option is to adopt the Contributor Covenant and the incident-handling practices it comes with, which empirically help produce great projects. The only reason to adopt the Code of Merit is ideological attraction to its worldview outweighing the desire for a better technical project.
That escalated pretty quickly.
There's no need to draw the line. As long as Hitler writes good code and behaves well on project's mailing lists, issue trackers etc., I would have no problem with him being a project member.
Why should we prevent someone from contributing something good, thus hurting ourselves in the process, because they otherwise do something bad?
It doesn't help to shun people just because you don't like them or what they do instead of helping them, persuading them, and encouraging them to grow.
If Hitler wanted to join my code project, I'd try to help steer him in the right direction and teach him to contribute something worthwhile.
I imagine you would have no worries about what might happen if Hitler's PRs are rejected and he gets angry about that?
If what you're alluding to is "Hitler will call for genocide if his PRs are rejected", then we already have something for that.
It's called "The Law".
There is nothing morally wrong with Hitler contributing code to a project, provided there's nothing morally wrong with the impact that code has.
Most of the argument around CoCs is along the lines of "Hitler wants to exterminate people like me, therefore I don't feel safe being associated with this community, therefore Hitler should be excluded to make the community more inclusive."
Maybe the answer is that there should be less "community" around a project, and the work should speak for itself.
(I wonder how quickly someone will misinterpret my words as a defence of bigotry or National Socialism…)
Rejects must be justified.
Pedophilia is not criminal (in "civilized" countries), it's just a sexual orientation. What you might be thinking of is child abuse. Please don't confound those two, because being a pedophile is neither a choice nor does it make you a child abuser, nor is all child abuse done by pedophiles.
edit: lol, downvotes for this? Really? I'd really be curious how those downvotes correlate with support for CoCs.
>This establishes that nothing outside of the project has an impact on the project itself. 1. Clause 11 does. Let's abstract the example of the social pariah you gave, since as you pointed out, Godwin's already got your number. Let's say we were talking about the sub-human degenerates, the utter voids of moral thought and character, the unforgivable scum, that are pro-skub. Now, while I hate them as much as any upstanding conscientious person does, I have to grant that this code of merit does not give them a remit to advance their hideous philosophy through the use of the software (as long as the society they are in is civilized enough to ban all of the actions we hate these people for).
2. It is not a given that a private or open-source software project has the social duty to ferret out secret pro-skubists. If I, for example, were to allow my neighbors the use of my lawn for social events, am I responsible for validating that none of the, in their heart of hearts, secretly desires the spread of that plague upon our species? Should I conduct a personality test on a fellow before holding the door for him, to ensure that I never help one of these vile cretins?
3. Even if this "person" is known to be pro-skub, are we obligated to refuse them any access to our community? If one of them, like the proverbial monkey at the typewriter, can cease his endless spewing of nauseating ideology to write valid helpful code, am I under a moral obligation to refuse it? If so, why? As long as they keep their disgusting opinions out of the professional space in which said code is offered and judged, I can isolate them in my mind as a code fountain and think nothing more of them. And if they do so dare to proselytize their villainy, this code of merit gives us the authority to remove the post-haste.
4. On a strategic anti-skub level, I disagree that total shunning accomplishes a useful objective. Ideally, we want the to understand that they are wrong people with bad opinions. Refusing any interaction with them will not accomplish this, as they will simply be led into more extreme pro-skub echo chambers that reinforce this twisted, amoral world view. How will they ever be led to the righteous path, if every guide shuts the door in their faces?
The alternative is probably the "tyranny of the outside majority". You can't do things _other_ people, unrelated to your work, don't like.