Arguments against radical inclusiveness:
Arguments for radical inclusiveness:
While the identification of outliers is much easier in societies with monopoly power over the people in question, such as a state, doubly open-ended volunteer organizations such as the vast majority of OnlineCommunities do not fit this model. These organizations are incapable of conducting a reasonable census or even identifying who wants to be involved or not. Instead, they can only react to what is visible. Disturbingly this highly skews the discussion towards the those who create the largest conflict (FlameWars)--rather than either those currently conducting themselves peaceably or, more seriously, valuable contributors who leave in silence.
While one might claim backhandedly that one very angry individual represents ten more reasonable people who left for similar reasons, that does not balance against those who left silently. In counterbalance, they not only represent ten valuable people who won't contribute, but the people who come here because of them as good people prefer to affiliate with good people. Further, the lower the quality of discussion, the quicker it lowers (cf. Wiki:FixBrokenWindows). Thus, in these cases, discussions of RadicalInclusiveness will not only shift CommunityExpectation"'s towards a race to the bottom, but it will evaporate gains faster than they are made.
Thus, unbalanced, RadicalInclusiveness is an AntiPattern as it is a lie. It only seeks to include one type of person (the maladjusted) as a weak method to alleviate conflict. Ironically, one would presume that attracting maladjusted people will only increase conflict until they can be realistically adjusted into the wider community, and the availability of quality mediators diminishes as they leave silently in response to the waste of their time.
On one hand, the fault may be ours for not being accepting. We may in fact be excluding someone with a valuable perspective even if they are generally good people who get along with others. Disagreeing with someone is not a legitimate reason to exclude someone if they sociable, amenable, conscientious, and generally are interested in BarnRaising. We must be pluralistic because that is the most valuable and therefore fun thing to be. Otherwise, we descend into GroupThink and fail.
On the other hand, those who refuse to change will naturally be excluded just from rubbing us the wrong way, or at least hopefully ignored until they discover the need for compromise and learning. We all experienced how BarnRaising has made us all have change and grow. This is central to the wiki way as using a wiki is more than learning the TextFormattingRules, it is also about growing as a person. Maintaining this perspective that we must all work towards the better answer, old timers and newcomers alike, is critical to working on a CollaborativeHypermedium.
It's also important to remember that we are the community. Our rules, style, and sensibilities attracted each of us including newcomers (even OutcastNewcomers) to join. We define ourselves by these sensibilities, so they are unlikely to change. One always has RightToLeave, which is not a specious right because it is a big Internet, but one also has the right to help. We also have a right to be ourselves, which is expected to be different than the rest of the Internet which is why we are an online community, not just a collaborative document. In short, although our rules are not set in stone, they are not to be fought over but built.
Intransigence traps us under our own egos. We are into BarnRaising, but intransigents are into themselves (as TheIndividual). Many project this perspective onto the rest of us who are into TheCollective. Collaboration is more fun. Wikis are inheritantly egoless in the sense that projecting your ego strongly into a wiki will only induce fighting and disorder; egos create invisible barriers, and as sensitivities are hidden they become buried LandMines. LandMines ruin the "arable" land of the wiki.
If you are having a hard time on an OnlineCommunity, then it isn't fun. If it isn't fun, it isn't worth it. If you are killing our fun, you aren't worth our effort either. That's the "harsh" reality of it. Like running through liquid corn starch, the only way through is to be relaxed. Make love, not war.
This extends to many different types of OnlineCommunities, but not all. It's a big Internet; somewhere out there is a space for everyone, and if there isn't, build one. (Meatball can help you with that too!)
One day, however, something changes and the community stops being inclusive. They start forcing almost all newcomers to be OutcastNewcomers. This may simply be the ossification of a number of VestedContributors. After a while, enough emotional investment is put into the community by a few that they become the de facto cabal, unwilling to let go of the space lest its changes invalidate what they have built. They might be afraid of losing the friendships they have built in the process thinking that those friendships are soley vested in the space.
In other cases, a brutal FlameWar erupted in the past, say due to a troll or an AntiAuthoritarian. This flame war usually caught TheCollective by surprise, pulling at all the fissures inherent in any social organization. This flame war might have cost a number of people's participation, as they exercise their RightToLeave, sick of the experience, chiming "If it isn't fun, it isn't worth it." The collective may spend a long time unpacking the experience, digging deep into themselves trying to find the root cause of the problem as if it were their fault. This churns more of their faults to the surface (exposes the deeper recesses of their LifeInText), making them vulnerable to future attacks. They become overly sensitive as a result, and fear newcomers as threats, especially since some will snivelly extort their exposed weaknesses to gain power (not to be confused with those who wish to explore them further in GoodFaith). Thus, they become very insular, pushing away newcomers out of fear. Slowly, the community dies as members evaporate without being replaced by new members. They may mistakingly blame this on newcomers, extrapolating from that one foggy memory where they did lose members. FlameWarriors calls this scenario the [Godzilla] creating [Xenophobes].
RadicalInclusiveness is a reaction against this radical exclusivity as members with the desire to spread their own wings (vs. VestedContributors) or those who weren't affected by the Godzilla (say they weren't around, or they already reached ForgiveAndForget) feel this closing in of the community as destructive, rightfully so. As a negotiated position, it's a good one to have, as in the end if successful it will open up the community a little bit from its currently tight situation. That may be enough to get things moving again.
But be careful. If you are unfortunate enough to encounter another Godzilla or a threat soon after the first tentative steps at opening up, the xenophobes will close up tighter than before and your opinion will no longer be trusted. Take things slowly to build up the emotional capital to deal with these difficult situations. Hopefully you won't be too late.
It seems like you are asking we be more gracious and polite. While I suppose we all know how to do this, the pertinent question is why don't we? But maybe the phrasing "RadicalInclusiveness" is not the right phrasing. Maybe WelcomingNature? or something like that. -- SunirShah
hmmm, it is not that I particularly care or want this place to be more gracious and polite. It is that I want this place to be better able to handle newbies, cryptonauts, anonymous users, etc. If we can figure out where someone is at, where they want to go, then it less energy expended for us, and hopefully a better experience for them and us. -- MarkDilley
Last night, I spent the night talking to manager of of the Green Room here in Toronto. The Green Room is one of the least expensive bars in the city, and its relative obscurity hidden behind Future's Bakery, one of the Annex's most popular venues, make it a quiet bohemian refuge in the midst of the city. Now Magazine has rated it the Best Bar for Drinking Alone in Toronto. As such, they attract the very crazy. While perhaps it would be nice to grant these people some degree of respect by allowing them to stay, if they did that, they would lose their normal, profitable customers. More to the point, it's unsafe. The manager told me her staff were reluctant to kick out anybody until one guy started throwing tables and beer bottles. The rule there is very simple. Staff are instructed to kick out anyone they would not want to share a beer with.
For a space like Meatball that is very communal, the rule is consequently very simple. If you need to know whom we need to exclude, it is anyone you do not want to work with. The WikiAsRoom is not very large. If we cannot work with someone, they have to go. After all, what's the point of them staying if they cannot work with us? This bar is not particularly well-defined, of course. We will still employ our ConflictResolution skills and LimitTemptation by being open-minded. But people who start trashing the wiki must be CommunityExiled. It's a Big Internet, and we all have the RightToLeave because we can find somewhere else to go.
But most importantly, we do not need to endlessly suffer for other people's problems. We need to draw lines, because otherwise our SelfishVolunteers will exercise their RightToLeave and then all that we have built here will be undone. If it's clear that things won't work out, there is nothing more to be gained by continuing to be in a conflict. Sane and mature people will depart without hard feelings, but not everyone is mature. We may then need to unilaterally end the conflict.
RadicalInclusiveness itself means to me to exclude only those you cannot work with. But the flipside is that we should LimitTemptation by attracting only those we want to work with. The matrix at UsAndThem speaks loudly to this. -- SunirShah
I experimented with RadicalInclusiveness on IRC. I started a channel to discuss politics. I invited some smart friends. My rule was only ban flooders. If a person repeated themself enough, I'd consider them a flooder and ban them. If they wanted to verbally abuse, no problem, so long as they could keep thinking up new insults. When they repeat too much, I'd criticize their output and warn that it might soon be considered flooding if the repetition continued.
I figured that verbally abusive right-wingers would get their fill of spewing bile and would go away. My main reason for doing this was wanting to show to the people in another channel that there was another way to handle disagreement, rather than merely banning dissenters. Anyway, no one wanted to be an Op in my channel with no bans! I eventually quit IRC except when I need to get answers to a technical question. -- PaulGaskin
I wonder if the technology of IRC with its channel Ops, disuades the kind of openess you were looking for? With the technical side of wiki being open, and the style of community we want here, professional, does the technology here persuade openess? MarkDilley
"The biggest catastrophy that could happen to MeatBall would be to attract 100 people writing here but only faintly in correspondence with the current goals." -- HelmutLeitner
"When we started we were open to anybody. That was a central value. The difference now is that the community has reached the point where it has to be very careful about how it organizes itself. TimeAndPatience?? are becoming luxuries rather than commodities." -- SunirShah
I tried to write a bit about what I see as a the tension here, as a pattern seen in a lot of places. ExperiencedInteractionWithInexperience - how much time goes into helping people become - vs - be here by doing the work, participatory community, which I see SunirShah's brilliant statement pushing for: "So edit it. I haven't reached nirvana yet; I am not transcendently detached! It's too bloody cold in Canada to wander around naked in the forest." Best, MarkDilley
FootnoteAnnotation?: The best strategy to settle unnecessary conflicts is to prevent them. Please annotate this page or be an author of this page. -- FridemarPache