Knowledge (XXG):Requests for comment/Content dispute resolution

3910:. I think we also need to establish better practises for teh definition of "no consensus" and what it means. I'd certainly like to see some sort of return to "open polls" on issues. This was a system where we used to leave polls open for a long time, and I think we could return to that with some sort of arb-com input. Take date-autoformatting. Even though the poll is closed, there is nothing to be lost from leaving the poll open, and reviewing it periodically to see if consensus has changed. This also would allow a funnel for frustration. If we had a list of such open polls at the bottom of cent and other areas, this would allow community memebers to have their voice heard and in a sense act as a "petition". Take for example WP:N, which is typically a cause of issue. If we had a page where people could sign their support or opposition to the very principle notability enshrines, we could quite quickly defuse a vast number of debates. We could simply point people to the appropriate section of the open poll or petition. Obviously we fall into accusations of "not a democracy", but the obvious retort is "not a battleground". This system has been used on Knowledge (XXG) before so it isn't outlandish, it formed the basis for a number of naming conventions. All we'd be doing is marrying it up to actual arbitration. Food for thought. I certainly think this is an area arb-com/mediators could become more useful, in a role akin to election observers or peacemakers. 1887:

skills at Knowledge (XXG), and relative emotional stability under pressure. To the extent that our decisions are to be based on the attempt to find a correctly neutral position, not internal and external politics, those factors are not relevant. What they favor is the established editors, who have throughly learned the rules and have to some extent been selected by time for self-restraint, and whatever may be the positions they happen to hold. fortunately, their positions are not uniform, but it's a haphazard way of doing things. We do have biases. I share some of them. NPOV is a wonderful principle, but almost nobody can actually apply it to anything they really care about, and experience shows that anyone who edits where they do not actually care will inevitably come to favor one or another position. This creates certain difficulties in how to do things better, so I am not immediately proposing a solution. One that I am quite sure will not work is letting arb com handle it; they have difficulty enough with their current role. Maybe there is not one, but that doesn't mean we should pretend there is no problem.

3886:

to talk to regarding setting up a process through which to manage such polls and rfc's. I think he'd agree he learnt a lot regarding having an agreed end-game before launching, and also tight rules on canvassing and opening and closing. Many of these tasks can be automated, certainly the opening and closing and the canvassing. The end-game needs to be looked at more closely, but I think it is not beyond the means of arb-com to simply state that in certain binary issues a consensus can be determined by a certain %, the % variable depending on the issue, and also having a requirement for a quorom; I'd say the date delinking and the current poll at plot show that you're likely to get between 150 and 500 respondents depending upon where the issue is advertised. I think there is a viable process here which would help ease tensions: the input of arbitrators/mediators in settling what the issue is and composing a question or questions for the community, and providing solutions in the format of if

3942:

would be that a formal and explicit mechanism be crafted for the MedCom to draw on the active Wikiprojects themselves. IMO, the projects are usually the best places to resolve reliable source issues on their topic area – and once consensus is achieved to maintain it. They are likewise usually a good source for neutral, uninvolved subject-matter experts (SMEs) – and in my experience content disputes most often arise among somewhat knowledgeable but non-expert editors (and often in places where these SMEs aren’t watching); theirs would be a sort of “friend of the court” role – not as advocates or decisionmakers, but to develop a professionally informed advisory recommendation to the MedCom. However, where the content dispute is tied to an honest disagreement on interpretation of policies, guidelines and such – which are rarely completely clear as they are usually in a state of flux – then the community active on those pages need to be requested to develop a clarification.

1452:

stick. So the key point in any dispute, be it a content dispute or a behaviour dispute, is the attitude of those involved. ArbCom's role is to look at the behaviour of users to see if they are unreasonable and unwilling to negotiate - and to put remedies in place to prevent unreasonable and unwilling users from disrupting the project. There is no need for ArbCom to look into content issues - that is a different process. Mediation is not about issuing sanctions or making rulings, it's about helping people in dispute to reach a solution that all parties agree to. A committee is not needed for that - mediation is best done by a calm, patient and detached individual that the people involved can trust.

2480:

corrective behavioral solutions in order to allow the disrupted dispute resolution process to resume in a proper manner. Ergo, in practice a decision is rendered, and usually it does help, more or less - but in theory there should ensue a process of fruitful content dispute resolution that is made possible because of the corrective arbcom decision. But in practice this rarely happens for various reasons, (one of them because that the parties still lack basic practical education with Knowledge (XXG) policies and mediation skills, another is because there is simply a lack of participation on the article).

2273:

compromise, could just lead to the problem continuing, without a result that solves the issues. Basically, with user conduct issues, binding resolution can be made, solving the problem, however with content issues, if a party is not satisfied with the outcome, regardless of consensus, they can continue stonewalling/edit warring/hampering consensus, etc. This is why I feel, an additional component, binding mediation, used in rare cases, where all other methods of resolving a content dispute, have failed, yet there still are inadequate user conduct issues for the case to proceed to ArbCom.

896:

filter out to the wider internet community en mass but can flame up quickly and escalate very fast. Content disputes conversely are likely to filter out to the wider internet community and thus Knowledge (XXG) needs strong support and by in on content from the community as a whole. In other words efficiency with respect to personality disputes and correctness with respect to content is probably the best overall theme. Further, If arbcom had positions on content it would be more difficult for those to evolve with time. So I definitely do not believe arbcom should rule on content.

3583:(4) Community involvement through RfC or similar procedures to determine which of the various proposals if any, or perhaps some combination of proposals, receive sufficient support to become enacted as policy, guideline, or essay, and, also, how to specifically address the issue which prompted the creation of this specific ad hoc group. It might even be possible to make very specific rules for such discussions, similar to those of XfDs, alloting only a limited amount of time for discussion before a solution of some sort is arrived at. 1682:

thus as a dispute that has to be taken seriously among the community. As we all know, editors are prone to warring and hardening into opposing groups. On occasion (maybe even more-often-that-not), so-called "content" disputes before the arbitration committee are more a case of these kinds of "hardened" disputes between editors, rather than genuinely about content. Prudence should be exercised by the committee so as to not legitimise superficial "content" disputes but to resolve the underlying warring and tribalism.

3600:) 14:13, 11 May 2009 (UTC) One advantage to having such a system would be that it would allow ArbCom cases which do involve intractible policy disagreements to be addressed by an ad hoc committee created to deal with the matter, possibly simultaneously with the starting of the ArbCom, to allow the arbitrators to deal only with the specific conduct issues they face, while allowing the other matters of policy and such to be brought before the ad hoc committee created to deal with it. 1186:: we look at all the same policies, and in good faith read them in different ways. A case for mediation resulted in a user with about 1/10th our combined edits trying to adjudicate--he was, through no fault of his own, out of his depth. We could really use a "court" of people who're familiar enough with nuances of policy to make such calls--or propose a novel and previously unconsidered compromise--when good faith efforts between earnest and civil yet disagreeing editors fail. 530:

couldn't be solved with our current mechanisms when there were no underlying conduct problems. I think the Arbitration Committee would be best served looking at earlier methods of conduct dispute resolution - streamlining the conduct RfC process and perhaps developing a few others would really help solve many content disputes. What we don't need at this time is a new committee dictating content - that goes against many of our key editing philosophies.

2586:

To take the position that all disputes should be resolvable in a final sense is to imply that there must be a side that is more correct than the other, or to say that we are in fact more interested in ending the dispute than in treating all viewpoints evenly. This contradicts behavior in academic circles, where experts may respect each other in a field and yet disagree vehemently. It would be unwise to force agreement or outcome in such cases.

176:

toward the "nuclear option", sanctioning more aggressively--and perhaps indiscriminately. Neither is a workable alternative to sanctioning primary aggressors; the more recent trend runs the risk of validating and rewarding mudslinging campaigns. This risks a chilling effect in which productive editors fear to contribute to controversial topics in any way at all, lest their wiki-reputations be ruined despite their best efforts to be helpful.

2255: 2579:-a distinct "them" which is easy to attack both on and off-wiki. I believe that the existance of such a body, capable of making authoritative and lasting content decisions would disrupt Knowledge (XXG)'s guiding principle of consensus. Knowledge (XXG) itself would be described to have a POV on certain topics, and I believe this would weaken and discredit the project. 1573:

editors and also the other processes of DR (including ArbCom, MedCab, Projects, etc). Such a group can then present their independent findings to the various DR bodies who can then incorporate them in their processes. In a case where there is no issue of conduct problems, such a body could be the final venue of purely content dispute resolution.

2666:

for the opposite reason. Hardly anyone is interested, so a consensus cannot be established. RfCs tend to produce little response in many cases. Note that what a number of people say above about dealing with behaviour doesn't seem to apply in this sort of case. Both ArbCom & RFC/U, as far as I understand the rules, require

2117:

Unfortunately this is always going to be the case as long as the majority of the admin corps has no intellectual heft. It is easier to recognize incivility than to recognize someone making uninformed edits. Easier to evaluate a dispute based off whether or not someone is part of the Wiki-mainstream

1782:

Many conduct disputes are the result of prolonged content disputes, in which the existing dispute resolution has failed. The current arbcom can not resolve those issues, as they are limited to conduct issues. To adequately deal with content issues, a separate ArbCom needs to be created, with specific

1451:

When I have mediated disputes and those involved were reasonable and willing to negotiate, the dispute would be resolved quickly and, so far as I am aware, permanently; when one or more of those involved were unreasonable and unwilling to negotiate, the dispute would linger and any solution would not

960:

Yes, in process. However, DR is currently understaffed; there are many disputes but not many mediators. To compound the problem, a huge amount of content disputes end up at AN/I and other sinkholes where it's difficult (if not impossible) to control the structure of the discussion. There are not many

179:

If "content dispute resolution" is to become a new attempt to circumvent the Committee's central function of identifying and remedying primary aggressors, then I strongly discourage the experiment. Fundamentally disruptive individuals are talented at subverting processes; this is why they wind up at

175:

For about the last year and a half the Committee has strayed away from its former practice of identifying and remedying primary aggressors. Last year it substituted discretionary sanctions, which were often ineffective and sometimes created new problems of their own. More recently ArbCom has tended

3932:

I am in concurrence with the majority of commentators here and for most of the reasons they give for ArbCom not taking up responsibility for content disputes. It’s really much wiser to keep the venues for addressing editor behavior and content disputes separate and distinct in their purposes. I do

3885:

We just had one in the date delinking case, which, although it had issues with management, proved useful. Content issues are the communities to solve not arb-coms, but that doesn't mean arb-com can't guide and manage a path for teh community to find consensus. I think Ryan would be a useful person

3813:

The Knowledge (XXG) community may wish to explore options for presenting that outcome in the article. This would be a break from the style of traditional encyclopedias, but could reflect one of the strengths of wikipedia - community produced content. I believe it would be desireable for such cases

3580:(3) Details of the duties of the ad hoc group. These would likely be limited to noting the specific questions needing to be addressed and proposing a number of alternative solutions to the problem, with the intention of arriving at the "draft proposal" stage relatively quickly, perhaps a month or so. 2596:

Continuing to devote large amounts of energy to such disputes is a waste of our most precious resource - the time of good editors. Ideally "disagreement" could be a stable state that did not require great effort to maintain. It is undesirable to have situations where the editor who gets frustrated

2578:

Official, binding content decisions from a small body of decision makers is deeply problematic. The existence of such an authority would shift responsibility for the most highly disputed content from the community as a whole - a nebulous "us" which is difficult to attack - to the authoritative body

1744:

How should the Committee approach allegations of improper use of sources? Should the Committee rule on the reliability of particular sources, or place additional restrictions on the sources which may be used to resolve a dispute? Would the creation of a body dedicated to ruling on source reliability

3537:

That's why I said "relatively". The point is that it cannot be settled by the same people who were arguing about the matter of substance - that just leads to an endless spiral. Of course the call might be difficult, and might require discussion among admins, and between admins and participants, but

2585:

While it is true that there are disputes in which well-informed, well-behaved good faith editors are unable to disagree, this is not necessarily unacceptable. When the dispute is so difficult that no compromise can be agreed upon between good editors, how can we presume to choose a single answer?

2542:

I think one of the biggest hurdles in the debate is the widespread misconception that consensus should be the ultimate reference for proper content. Policy should be the ultimate reference for proper content. Policy should supercede consensus. Hence the need to have a responsible group that rules

1216:

This is the heart of the limitation of the current ArbCom system; two opposing views expressed civilly and with good faith and supporting references will keep an article in a constant state of flux, with no stable/definitive (yeah, I know it is a Wiki) version and no means in which to resolve it. A

1014:

In the first case: Getting people to understand the legitimate use of sources works on a case-by-case basis; often, mentorship will help, but I plead to the committee not to dictate the terms between the mentor and the mentoree. Mentorship is rare enough, and imposing anything adds pressure counter

975:

Content disputes should be kicked down to MedCom. However, ArbCom needs to bear in mind that the primary reason for RFAR is user conduct that has exhausted attempts at resolution through consensus. Disputes that haven't been through DR should go through DR first. When that fails as a result of user

895:

I'm not sure our current system works for content dispute works well enough. But I think having arbcom maintain its no content review policy is excellent for separation of powers reasons. Further the goals of the two types of dispute resolution are different. Personality disputes are unlikely to

2665:

I want to expand on something mentioned by Jclemens above. A lot of the discussion here seems to be thinking in terms of cases like the Israel/Palestine dispute, where you have endless armies going at it indefinitely. What Jclemens mentioned above is the sort of case where a dispute is intractable

2514:

2- It is very complicated to effectively enforce blocks and bans in a system that is internet-based, anonymous, and with free registration. Therefore it isn't really that practical to have an approach that focuses on sanctions based on user behavior, i.e. sanctions that are inherently difficult to

2479:

Because Arbitration openly professes to focus on behavior over content issues, it is therefore in practice not the final step in the dispute resolution process -the content problem usually remains essentially unchanged after an arbitration decision. Therefore in theory it serves primarily to apply

2356:

I completely agree on how editors can game the system - essentially stonewalling and not compromising. If we accept that *not* compromising is a right - that some disputes *are* split along white and black lines, then this project currently has no process or policy or enforcement procedure.... I

1886:

I think it is not correct that the present situation works well. The total situation works by the two sides trying to maneuver (or bully) until the key representative of one position commits an unforgivable conduct error, at which point that person can be removed. What is selected for is relative

1193:

issued from "on high". When consensus breaks down in ways that prevent the entire encyclopedia from moving forward, the community could really benefit from a logjam-breaking group who would, much like ArbCom, be composed of senior, respected folks who can hear the arguments, make a pronouncement,

3941:

As structured, MedCom is a small organization of members who are good at mediating; they are, however, too few to be even semi-expert in all areas of knowledge. (The same can also likely be said of those editors who actively watch and participate in any neutral capacity.) What I would recommend

1681:

More effort needs to be put into establishing the genuine nature of disputes among the relevant community of editors, rather that taking statements of involved editors at face value. Once the Arbitration committee gets involved in a "content" dispute, they legitimise it as a "genuine dispute" and

1266:

I'd like to see it sooner, too. We have to evolve a little beyond the extreme ends of the spectrum that we currently have. On one end, we have ArbCom, which involves itself in conduct issues (pov, conduct and socking) and is in effect the nuclear option. It also moves about as fast as molasses in

99:

I personally believe having a dedicated body to work on content- and sourcing-related questions would be very beneficial. There may be some difficulty in selecting people for such a body, but I think those difficulties may well likely be less problematic than the problems that are faced and often

3518:

I think that it not correct that debates about whether we have in fact reached consensus on resolution of a dispute are something that "can be settled relatively quickly by admins" -- rather, it's the hardest sticking point of all--especially when we have no real rules for how much consensus is

2510:

1-To state that arbitration is the final step in a dispute resolution process with the caveat that the focus is on user behaviour and not content isn't necessarily an effective approach because a) most serious disputes are ultimately inherently content-based; b) in theory, the end of the dispute

2272:

easily, and can stonewall, block the consensus of many editors, and hamper mediation processes, while doing so civilly. Additionally, while mediation is voluntary, the fact there is no binding mediation means long, drawn out attempts at resolving disputes, if met with users who aren't willing to

529:

I'm truly of the impression that if you sort the conduct issues, you solve the content dispute. If there's no conduct issues, then content RfC's, third opinions and mediation almost always solve the issues at hand. I'm finding it hard to think of any content dispute that was so egregious that it

4026:

principle to ask those people to comment on specific third opinion / RFC requests. This would increase third party involvement in disputes, increase randomness of involvement (less self-selection might mean more neutrality, on average) and help resolve smaller ones. The big ones (like political

2592:

Mediation is the appropriate way to deal with prolonged good-faith disputes. Ideally non-binding, and with the understanding that a resolution may not be reached, and that this is not necessarily failure but may be indicative of a topic about which it is appropriate for reasonable people to be

2283:

The committee shouldn't have any role in solving content disputes, I feel the Committee is struggling enough already handling the current open RFARs, and has enough of a load already. I also think there should be a separation of power, and I'm uncomfortable with delegaing even more power to the

1572:

There appears to be the need for a body that can make judgements on the validity of sources, the interpretation of such references, the primacy of a viewpoint referenced by such sources, the application of WP:Due weight of other viewpoints, etc. that is independent of the actions of the various

1131:

That said, for articles under an active Project, that project turns into the de facto "dedicated body for ruling on content disputes/source reliability". It's how something like the mass-merging of Pokemon articles can actually happen without editors kicking and screaming the whole way through.

899:

Where I do think there is potential for enhancement in dispute would be enhance the authority and scope of medcom. Medcom members should stand for election the same as arbcom. Pages can be sent to Medcom for binding mediation (essentially what article probation means today) and that failure to

525:

I believe that our current content dispute resolution works well. The problem in just about any large dispute is mostly not about content, it's user conduct. Although on the surface the content issues look to be causing the problems, when you look deeper into it you see that it is in fact users

426:

arbs need to change aspects of their approach, by spending more time and effort being receptive to the community criticism & feedback they receive, and putting aside their personal nonsensical issues/vendettas that revolve on perception & systematic bias (we're not interested in them) -

2690:

There's been a suggestion on this page somewhere of a special role for projects. Here I can be a bit more specific without naming names. Most of my WP work has been in the field of Buddhism. Most of the WP editors in the field are, unsurprisingly, Buddhists. More to the point, though, they are

3096:

Keep the content side of dispute resolution as is. Focus more time and effort on streamlining and promoting the current conduct dispute resolution methods and find ways of developing more. Hopefully this will allow the content to fall into place with fewer conduct issues disrupting processes.

2284:

Arbitration Committee. I would recommend that the Mediation Committee either be modified to allow them to make binding decisions at mediation, or separate panel of experienced mediators be set up, in the case that other prior forms of dispute resolution fail, and binding resoltion is required.

1459:

ArbCom could work more effectively for the community if they ignored the content and other issues of a dispute, and simply examined the evidence of disruptive, unreasonable and unwilling behaviour, and then acted swiftly to sanction those who are preventing the community from working toward a

2040:

I've seen too many instances of the polite POV pushers who goad the editor trying to present neutral, policy-compliant article edits into bad contact; the neutral editor gets sanctioned and effectively removed from the debate, and the POV pushers get the article to look the way then want it.

1231:

Endorse the view of the problem; how to constitute a suitable deciding body is a little more complicated. If there were a "court" there would typically be only one or two people with competence in any one subject, and their views would decide the issue in an arbitrary way. I'd prefer binding

171:

Although most Wikipedians are reasonable and collaborative, few ones who aren't tend to come to the attention of site administration and eventually--in some instances--to arbitration. In nearly all occasions where the Committee becomes involved, unreasonable individuals also violate conduct

89:

I would hope that the Arbitration Committee refrain from involving itself too much in determining content disputes. This is in no way any sort of criticism or denigration of the Committee, but I don't think the committee have ever necessarily been elected on the basis of their having editors

3821:

be templated as having had a prolonged and intractable dispute over its content. A brief description of the nature of the dispute might be written by a 3rd party (perhaps the mediator) with each side approving the accuracy of the description of their viewpoint in the matter. I propose this

996:

49:

3828:

Such a system should leave open the option for the community to resurrect discussion if there is no longer a consensus on intractability. (As a matter of principle, there should always be room for consensus to change - one the reasons I fundamentally disagree with the notion of a content

2132:

This is an accurate summary of the current situation. We have no final authority on content disputes, so we put the parties through a test of bureaucracy and patience until one of them breaks and behaves badly. I'm not sure what the solution is, but the current system is not adequate.

2691:

Western(ized) Buddhists. They represent a particular type of Buddhism overwhelmingly. They often argue that Buddhist writers are more reliable sources than outside scholars. That has a certain measure of plausibility to it, until you realize that what it actually means in practice is

2695:

Buddhist writers, the ones who write in English & are published because they're popular in the West. Downplaying scholars who've studied untranslated literature or carried out anthropological field studies downplays most of the Buddhism that actually exists in the real world.

172:

policies. This is useful because it allows the Committee to sanction conduct (misrepresentation of sources, forum shopping etc.) which in turn removes uncollaborative individuals from the discussion. If this is done properly the remaining editors can usually collaborate.

2737:

is an interesting comment by a longstanding editor (now retired). Although similar things happen in real life, it might be considered that a system that results in people considering it advances their cause to misbehave & be punished must have something wrong with it.

1455:

The question of sourcing and POV issues is the same. ArbCom should only get involved to deal with individuals who are unreasonable and unwilling to negotiate. Take away the unreasonable and unwilling individuals and the community can generally work toward solutions.

2181:

I agree that the current system is broken - the idea that you can solve issues of Truth merely by finding out which side is being impolite is Wrong, even if it often works on practice. Also, Arbcomm should remember that it isn't a court and wiki isn't a bureaucracy

191:. At present ArbCom is having difficulty addressing its core mission, which renders this an inopportune moment for an RfC that presumptively expands ArbCom's scope and function radically. The community need not seek ArbCom's stamp of approval to manage content. 1523:

broadly agree with this. There are situations where ArbCom could be involved in content decisions to the extent of suggesting formal mediation, a content RfC, or a poll for a naming dispute, however in general, ArbCom should avoid ruling on content or sources.

2511:

resolution process should be the resolution of the dispute (which as stated in a, is essentially a content problem, of arriving at a formulation of an article, or part of article that is deemed of encyclopedic quality and acceptable to all parties involved.)

1127:

As much fun as it would be to get certain longstanding content disputes finally resolved from "on high" (thinking specifically of Episodes and Characters here) I fear it would politicize the process and turn policy into a kind of majority-rules by proxy vote.

1173:

If there's one thing lacking in our current system, it's a centralized body that can authoritatively pick a "winner" and "loser" when all other options have been exhausted. While bureaucracy is to be avoided at all costs, it would be very nice to have a

2546:

If Knowledge (XXG) is an encyclopedia, then let the final resolution process be editorial-based and rational; an article, in theory, is more amenable to rational and collective analysis than the internet edit-trail of an anonymous, changeable identity.

2686:

doing anything about it. This allows POV pushers to get away with murder in less-frequented articles, & then add or redirect links to their propaganda. I've seen quite a bit of this, though of course I can't name names without violating AGF.

3506:(I've argued all this many times; this would be a start towards making a logical system that would actually work, and would make Knowledge (XXG) a nice place to be; in place of the confused, easily manipulated, non-system we have at the moment.) 2263:

I somewhat agree with Xavexgoem that the existing processes are somewhat adequate, however I do think there is a key component missing, and several weaknesses along the way to arbitration, as well as a great shortage of experienced mediators.

3937:

and others that having a dedicated body to work on content- and sourcing-related questions would be very beneficial; however, it may be that what is needed is to give some new procedural tools to MedCom rather than create a new organization.

421:

Indeed, clearly they are having difficulties, and enacting the nuclear approach was entirely avoidable. I think it comes back to what I've put plainly and indirectly on many occasions - good judgement is needed; though not applicable to all,

1685:

The the committee should retain their current boundary of not adjudicating content disputes - but also need to be careful not to implicitly legitimise such "content" disputes. In sum, the committee should stay away from content altogether.

3763:. Simple, straightforward, use the same skeleton structure of the AC itself. People can consensus out, poll out, vote out, anything that they'd like, all they like--but this puts final content and policy arbiters selected by the community 3569:

The structure for creation of ad hoc groups to deal with specific matters of policy interpretation and application, which are the instances which prove most problematic here, be created. This structure might include the following options:

1056:

that drastic. Creating further DR processes will just confuse matters, and putting mediators in that spot will have drastic effects on other mediatorial bodies (from claims of the system being broken, claims of mediators being partial,

3574:(1) Possible creation of an ad hoc group to deal with any specific related issues of policy problems by either the Mediation Committee, the Arbitration Committee, or possibly by the community at large by some sort of referendum system. 2153:

On contentious topics, the current system selects editors not for their knowledge or neutrality, but for their strength of will / endurance / willingness to game the system and battle through the dispute resolution bureaucracy, etc.

1973:

I would add that, in addition to people finding it difficult to be neutral, there really are cases of irreconciliable, equally valid, good-faith readings of policy. We do ourselves no favors by pretending the problem doesn't exist.

3631:

I'm generally sympathetic to the idea of having subject-specific ad hoc decision task groups authorized by the community or the Arbitration Committee as a tie-breaking mechanism in some of the more intractable conflict situations.

1267:

Chicago winter. On the other hand, we have MedCab or mediation, which is either staffed with well-intentioned but woefully inexperienced editors who have niether the time nor the understanding to resolve complex content issues. -

2600:

I believe the absence of a way for disagreement to be a stable, low-maintenance state is one of the fundamental problems we face. The community would benefit from a way of agreeing to disagree, if such a thing could be found.

1796:

The commission chooses three independent and uninvolved experts knowledgeable to the field of dispute who make a purely content based judgement based on the evidence presented, with the freedom to add obvious sources that are

85:

The current methods work well enough in most all cases. There are unfortunately a few where, for whatever reason, they don't seem to work so well. It may make sense, in those instances, to have some other means of resolving

3340:

That this ArbCom led RfC be closed, and a new community led Requests for comment/Content dispute resolution be opened. This will reduce potential drama over issues related to ArbCom, and allow a more focussed discussion.

2289:

However, I agree that any process set up should be set up via community discussion and proposals, rather than a mandate from the Arbitration Committee, and it would be better if this RFC was re-opened and conducted by the

3809:

Consideration might be given to the notion that an outcome of high-level mediation might be agreement that the dispute is "officially" intractable - as agreed to by both parties in the dispute as well as the mediator.

1771: 1846:

Provided that the judgment might be that neither side is entirely right and the article should hedge its bets. A key difficulty here, of course, is the bias of topic experts in topics such as pseudoscience. — Carl

3486:(i) That disruptive behaviour must be dealt with firmly when and where it happens, and never rewarded in any way (for example by gaining attention or being considered evidence of an absence of consensus). 900:

participate in good faith in a mediation process can result in disciplinary action. Mediation cabal should handle non binding voluntary mediations. Right now the two groups are too similar in their function.

1139:

does that job for sources. To me, source reliability is like Verifiability in practice: if someone asks "What makes this source reliable?" you need to have a good answer, without which the source goes away.

3973:

This user has made no WP contributions since 15th April, so very likely hasn't heard of this RfC, so I'm acting as proxy here on my own initiative. The user was working on a proposal, which can be found at

1004:

No DR process is designed to impose, and that is as it should be. If someone is using sources improperly, it is a result of either a lack of clue (V, SYNTH, RS, and ultimately CONSENSUS) or gaming of the

427:

frankly, it's often a case of choice, not one of incapability. Overall, very little I can disagree with in this view that I would echo (nearly) all of it - hopefully, firmer attempts to resolve the

1024:

In the second case: It is at ArbCom's discretion whether an editor is gaming the system (lawyering, filibustering, etc). If they are, the matter should be dealt with as any disruption would be.

180:

arbitration. If an exceptionally well-designed process were established with incorruptible volunteers, the disruptive editors would set about ruining the wiki-reputations of its volunteers.

2278:

What role should the Committee play in resolving content disputes? Should the Committee rule on content directly, or impose special procedures for resolving long-standing content disputes?

968:

What role should the Committee play in resolving content disputes? Should the Committee rule on content directly, or impose special procedures for resolving long-standing content disputes?

46:

What role should the Committee play in resolving content disputes? Should the Committee rule on content directly, or impose special procedures for resolving long-standing content disputes?

1397:

I think we do need a form of authoritative content dispute resolution, but it should be reserved for the most serious and intractable problems. Otherwise, bureaucracy replaces discussion.

2268:

I've done a diagram of the User Conduct / Content Disputes dispute resolution processess, and the weakness that I see in regards to solving user conduct issues, primarialy that users can

3834:

Another outcome would be "not resolved, but not yet deemed intractable either". In this case the dispute would continue to exist in the sense that we are all already familiar with.

4057:

How about an automated way of seeing a view of RfCs showing how many people have commented so far on each one, so that people can comment on the ones most needing more comments.

39:

All editors are invited to present comments or proposals concerning any aspect of content dispute resolution. The Committee is especially interested in the following questions:

3264:) 02:06, 24 May 2009 (UTC) I do not like needing to agree that there is nothing we can do at a more basic level, but we do not seem to have a proposal that has enough support. 184: 1770:

Generally, the conduct arbcom does not have sufficient knowledge of each and every field to render meaningful content decisions. A obvious example was the ruling that

3193:

Be willing to deal with the biggest abusers, even if they are popular with other admins or have an active tag team willing to attack administrators who sanction them.

2582:

Consensus can and does change. I believe that some of the flexibility inherent to that principle would be lost in a model where official content decisions were made.

1178:

to which content disputes can be taken, policy-based decisions rendered, and results published and considered normative until changed. In one recent content dispute

4078:

I thought of that too (finding some way to show how many people have responded, in one central list for all RfCs), but thought it would be hard to do automatically.

3461:(b) That admins and other potential mediators play an active part in steering the consensus process when it's off the rails, whether invited by the parties or not. 3699:

Probably the most flexible of the current specific proposals, and therefore the best way to start--if we are going to try to do something specific at this point.

989:

The structure is already in place with MedCom/MedCab and ArbCom, but back and forth between the two is rare. I don't think there is need for additional structures.

90:

knowledgable about the entire range of wikipedia's content, and any such rulings made without such expertise would likely be called into question by some parties.

1715:

No, if it was adequate, we would not have this RFC, and the most difficult cases would actually be solved in a reasonable time frame, and not continue for years.

2118:

than if they are making intellectually sound arguments and edits. I think we'd need a pretty significant culture change to make much progress on this issue. --

2250:

Are the current methods available for resolving disputes over article content adequate? What changes could be made to improve this aspect of Knowledge (XXG)?

953:

Are the current methods available for resolving disputes over article content adequate? What changes could be made to improve this aspect of Knowledge (XXG)?

43:

Are the current methods available for resolving disputes over article content adequate? What changes could be made to improve this aspect of Knowledge (XXG)?

187:

opened on 12 December 2008 and is the longest arbitration in site history. Content dispute resolution is outside ArbCom's mandate: content is the realm of

2597:

and goes away first, loses. We want our best to be out there editing constructively, and not imprisoned by the need to provide counterweight in a dispute.

1930:

Though I'm not quite as concerned that those with self-restraint "win" regardless of merit or argument, this is an apt summation of the state of play.

2246:, and I, as well, will respond to the commmitte's questions in a point-by-point form, with some follow up after that. I hope that my input will help. 1136: 1052:

I think it's far too early to tell whether a binding content solution is a good option. At any rate, the burden should fall on ArbCom to ever impose

96:

Ruling on POV would be very difficult, unless it could be reasonably sure that all relevant POVs have been represented, with is itself probably hard.

4000:

Editors, especially those with experience in content disputes, should help out in disputes about content of which they don't have a strong opinion.

2589:

The state of disagreement has meaning in its own right, and is a form of information that should not be erased by ending the argument artificially.

3685:

Endorse in principal - Assuming that this includes content dispute resolution and is integrated into the dispute resolution process as a whole.--

1038:

Absolutely not. It should be treated exactly as the sourcing problem above. ArbCom was not elected to represent anything or anybody content-side.

2055:

This. The only way to "win" a content dispute is to turn it into a conduct dispute and wait for the editor you disagree with to be sanctioned.—

3825:

Such an outcome should, ideally, free the editors to agree to disagree and move on to other encyclopedic matters in which progress is possible.

3724: 3050: 2435: 1964: 1787:

A small groups of chosen editors who oversee the general procedures and are very familiar with WikiPedia policies, especially content policies.

1257: 2196:

Very well put, DGG. Though I would add that this does not mean that sanctioning users with conduct problem is not a good thing. It's just not

574:

I tend to agree with this, the main thing arbcom can do better is point folks the right directin to sort it out and maybe give a time frame.

1761:

Would the creation of a dedicated body for ruling on content disputes, or a dedicated body for ruling on source reliability, be beneficial?

3538:

it's a call that needs to be definitively made. It's just like at AfD etc. (where one of the weaknesses is that the call is sometimes made

1045:

Would the creation of a dedicated body for ruling on content disputes, or a dedicated body for ruling on source reliability, be beneficial?

56:

Would the creation of a dedicated body for ruling on content disputes, or a dedicated body for ruling on source reliability, be beneficial?

3759: 3636: 2782:

in theory, "Knowledge (XXG) aims to present competing views in proportion to their representation in reliable sources on the subject." (

2342:

I'd be interested in seeing more definition in how to determine which cases need binding mediation, but overall I agree with this view.

1753:

How should the Committee approach allegations of POV-pushing? Should the Committee rule on the proper weight of certain points of view?

1675: 1217:

method of final DR might be needed in such cases, to determine how WP:Due weight should permit which viewpoint should be of precedence.

1031:

How should the Committee approach allegations of POV-pushing? Should the Committee rule on the proper weight of certain points of view?

53:

How should the Committee approach allegations of POV-pushing? Should the Committee rule on the proper weight of certain points of view?

1723:

All possible tools are available for voluntary content dispute resolution. The problem is when that conflict cannot be solved amicable.

28: 2758:

The problem of disputes that few are interested in, and RfCs garnering no or almost no responses is huge and frequently overlooked.

2143: 17: 3577:(2) Specific procedures to appoint the members of the ad hoc group, possibly by some sort of mutual selection by MedCom and ArbCom 3467:(d) That admins be permitted to use good judgement to effect a suitable interim solution while consensus is still being reached. 3414: 2066: 1736:

Should the ArbCom Committee rule on content directly, or impose special procedures for resolving long-standing content disputes?

3474:

be recognized as clearly distinct from either content disputes and conduct issues, and be settled relatively quickly by admins.

188: 3782: 1183: 3633: 2187: 585: 2158:

could hardly be a worse way to select who gets to win contentious content disputes - and surely we can do better than that.

1414:

Agree with Sandstein. We need to address content. Else content is decided by the person who can nicely handout the longest.

4116: 4082: 4069: 4052: 4039: 4022:

procedures by setting up a list of editors willing to comment (categorised by topic); and then using a bot operating on a

3987: 3959: 3919: 3872: 3843: 3794: 3741: 3728: 3710: 3694: 3680: 3667: 3653: 3639: 3626: 3609: 3551: 3530: 3503: 3480:(g) That any decision, action or inaction by admins be appealable first to the wider admin community, and then to ArbCom. 3442: 3421: 3398: 3375: 3364: 3323: 3310: 3294: 3275: 3250: 3237: 3226: 3213: 3204: 3190: 3176: 3163: 3150: 3137: 3126: 3116: 3080: 3054: 3037: 3024: 3011: 2982: 2972: 2929: 2914: 2901: 2892: 2879: 2866: 2853: 2842: 2823: 2767: 2747: 2725: 2707: 2648: 2635: 2610: 2560: 2528: 2493: 2465: 2452: 2439: 2421: 2407: 2382: 2366: 2351: 2337: 2309: 2226: 2212: 2191: 2176: 2162: 2148: 2127: 2112: 2091: 2073: 2050: 2035: 2021: 1998: 1984: 1968: 1951: 1938: 1925: 1898: 1873: 1859: 1841: 1828: 1665: 1652: 1633: 1620: 1608: 1589: 1556: 1543: 1533: 1518: 1507: 1494: 1481: 1435: 1409: 1392: 1379: 1364: 1351: 1337: 1324: 1307: 1282: 1261: 1243: 1226: 1211: 1157: 1111: 1090: 1077: 929: 914: 879: 866: 853: 840: 824: 808: 789: 764: 743: 727: 704: 691: 682: 669: 661: 648: 634: 616: 603: 589: 569: 560: 549: 509: 496: 480: 461: 440: 416: 401: 385: 362: 349: 341: 333: 320: 307: 289: 276: 257: 244: 231: 220: 205: 155: 142: 129: 109: 3483:(h) That there is no need for ArbCom to accept disputes between editors in any circumstances except as described in (g). 4108: 3072: 1427: 949:(MedCab). I'll copy and paste the questions and answer. By "DR", I mean all processes aside from ArbCom for brevity. 1132:

Unfortunately, that void is very difficult to fill for content disputes because of the subject knowledge required.

3720: 3046: 2431: 1960: 1253: 2183: 4112: 3076: 2965: 2835: 2412:

Endorse as a valid general view of the situation and the need to encourage emphasis on the mediation process.--

1864:

I personally see serious questions regarding points 1 and 2, but if they can be overcome it might be workable.

1604: 1585: 1431: 1222: 269: 294:

Yes. "remove uncollaborative individuals from the discussion the remaining editors can usually collaborate."

3983: 3978:. I've no idea whether the user would in fact consider it sufficiently finished to be worth proposing here. 3107: 3090: 2743: 2721: 2703: 1994: 1388: 540: 519: 211: 3234: 3186: 741: 657: 399: 329: 3975: 3955: 3716: 3605: 3597: 3200: 3042: 2980: 2888: 2461: 2427: 2222: 2139: 2031: 1956: 1869: 1661: 1629: 1552: 1333: 1249: 1086: 912: 835: 678: 491: 436: 358: 127: 105: 151: 1811:

Content decisions most often are nuanced and balanced, not black-white, although the later can happen.

980:

to DR, as the basic content dispute usually remains. This immediate return to DR is not common enough.

4065: 3868: 3690: 3435: 3411: 3306: 3146: 3008: 2992: 2862: 2645: 2642: 2631: 2556: 2524: 2489: 2417: 2400: 2105: 2063: 1825: 1702: 1529: 1375: 820: 782: 454: 3734: 1783:

procedure on how to deal with this kind of content disputes. A general outline I envision would be:

3788: 3645: 3543: 3495: 3452: 3168: 3159: 2958: 2939: 2875: 2828: 1814:

At times, conduct and content issues are mixed and procedures for these cases need to be developed.

1600: 1581: 1566: 1503: 1218: 1073: 599: 262: 253: 3391: 2946: 2330: 2302: 2243: 2014: 946: 720: 565:

The Committee must be the end of a functional dispute resolution system, not its sole component.

378: 147: 3979: 3737:?), but due to its vagueness, not necessarily any specific proposal that might come out of that. 3676: 3663: 3649: 3547: 3499: 3382: 3361: 3222: 3172: 3020: 2910: 2739: 2717: 2699: 2656: 2362: 2347: 2321: 2293: 2236: 2123: 2046: 2005: 1982: 1947: 1837: 1800:

The commission then applies the applicable Knowledge (XXG) policies and renders the final ruling.

1490: 1478: 1384: 1360: 1347: 1207: 1104: 757: 711: 631: 612: 579: 526:

failing to work collaboratively and not fully embracing our current dispute resolution methods.

369: 316: 304: 285: 138: 2357:

believe that it needs one. In some cases, this will mean making rulings related to content. --

3839: 3246: 3231: 3182: 2763: 2606: 2448: 2087: 1645: 1613: 1300: 1275: 875: 734: 653: 644: 392: 325: 183:

This RfC opens at a time when the site's longest arbitration case is nearly five months old.

3477:(f) That complaints about conduct are made to admins and dealt with quickly and effectively. 2269: 2079: 1248:

This will happen at some point. I'd like to see it sooner, but it will probably be later. -

1190: 36:

in order to gauge community opinion on the subject and to gather potential ideas for reform.

4104: 4048: 3951: 3934: 3926: 3915: 3601: 3593: 3563: 3372: 3319: 3287: 3196: 3134: 3068: 2977: 2884: 2850: 2457: 2254: 2218: 2172: 2134: 2027: 1921: 1865: 1657: 1625: 1548: 1515: 1423: 1329: 1232:

arbitration, for in any particular case it might be possible to find someone acceptable.

1153: 1082: 909: 889: 862: 849: 830: 801: 674: 557: 505: 486: 473: 432: 354: 240: 228: 124: 101: 78: 4092: 4019: 2783: 2778:

The result of the system of haggling to reach "consensus" is, I think, fairly predictable:

1182:

and I agree that we have fundamentally incompatible views on the use of primary sources in

4061: 3967: 3864: 3686: 3430: 3404: 3326:

Particularly, the part about "finding ways of developing more" dispute resolution methods.

3302: 3142: 3033: 2858: 2627: 2552: 2536: 2520: 2501: 2485: 2473: 2413: 2395: 2100: 2056: 1808:

Insights change, so does content. A mechanism to amend these rulings need to be developed.

1525: 1371: 1342:

This should be used rarely, but there are definitely cases where a higher body is needed.

816: 777: 449: 4015: 2217:

Agree - we need a committee, whether Arbcom or other, to solve certain content disputes.

1712:

Are the current methods available for resolving disputes over article content adequate?

3776: 3751: 3155: 3121: 2925: 2871: 2789:

in practice, it tends to present competing views in proportion to their representation

2378: 2203: 1931: 1538: 1499: 1400: 1069: 939: 925: 700: 595: 412: 249: 2574:(Numbering below is done for organization only, and not related to question numbers.) 3994: 3706: 3672: 3659: 3621: 3526: 3354: 3334: 3271: 3261: 3218: 3210: 3016: 2906: 2898: 2358: 2343: 2119: 2042: 1976: 1943: 1894: 1854: 1833: 1486: 1471: 1445: 1356: 1343: 1319: 1239: 1203: 1167: 1098: 751: 688: 666: 624: 608: 575: 566: 346: 312: 297: 281: 134: 3835: 3802: 3464:(c) That consensus, once reached, be enforceable until a new consensus is reached. 3242: 2759: 2602: 2568: 2444: 2083: 1793:

Each case is presented by the parties, with focus exclusively on the content issue.

1638: 1289: 1268: 1179: 871: 640: 2507:

2 reasons why the current approach of arbcom is not as effective as it could be-

93:

Ruling of reliability of sources has the same problems as ruling on content above.

34:

request for comment regarding the dispute resolution process for content disputes

4096: 4044: 3911: 3369: 3315: 3282: 3131: 3060: 2847: 2818: 2803: 2168: 1990: 1917: 1913: 1512: 1415: 1149: 1121: 858: 845: 796: 709:

Definitely. If the conduct issues are solved, content issues can be solved too.

554: 501: 468: 236: 225: 200: 165: 4079: 4036: 4008: 3738: 3029: 2159: 338: 2945:

ArbCom should focus on its original mandate, conduct issues. It should allow

2920: 2373: 2155: 1912:

ArbCom's current role in content resolution is functionally equivalent to a

976:

conduct (often), it goes to ArbCom. Once that's done, the dispute should go

920: 696: 407: 2662:

First of all, I do think something should be done, but I don't know what.

2949:

to make more binding decisions, and start referring more things to there.

4023: 3701: 3617: 3521: 3266: 3256: 2258:

A diagram showing the weakness of the current dispute resolution process.

1889: 1850: 1315: 1234: 2266:

Mediating isn't that bad, and I'd encourage everyone to give it a shot.

1720:

What changes could be made to improve this aspect of Knowledge (XXG)?

1194:

and that pronouncement would be the "new normal" for Knowledge (XXG).

2371:

Certainly worthwhile to have a community discussion about this idea.

60:

Editors presenting specific proposals for reform should do so in the

100:

much more difficult to resolve without the presence of such a body.

3458:(a) That content be decided by consensus as it is (in theory) now. 2096:

Well articulated, and probably the most accurate view I've seen. —

1728:

What role should the Committee play in resolving content disputes?

3644:

Sounds a bit too bureaucratic as phrased, but good general idea.--

2712:

PS Imagine the Christianity project almost entirely consisting of

2253: 2543:

on questions of content in reference to Knowledge (XXG) policy.

2078:

Ding. As a matter of fact, some outside analysis of wikipedia's

1577: 3179:, but subject to the fleshing-out I've proposed at #6 below. 2200:

if our purpose is to build a good, neutral encyclopedia.

4095:

and people who are willing to summarize the discussion.

2998:

Establish an explicit Content ArbCom as outlined above

2735: 2716:

Christians. that's the sort of analogy to think about.

4027:

choices over place names, say) need something else.

3733:

Endorse developing this proposal in more detail (via

185:

Knowledge (XXG):Requests for arbitration/Scientology

3767:the community as a final wall to settle disputes. 431:issues can be made so that everyone moves forward. 1790:A large pool of topic experts (credentials needed) 1916:. It tilts the dispute using unrelated criteria. 1370:Endorse. It could prevent a lot of headaches. -- 961:administrators with mediation experience, either. 3822:tentatively, as it is not well thought through. 8: 1367:The end of the road should be a destination. 3760:Knowledge (XXG):Knowledge (XXG) Committees 4003:No new policy or bureaucracy is needed. 64:. Other comments should be made in the 2082:concurs (at least in part) with this. 1015:to the friendly teacher/student setup. 3472:about what consensus has been reached 621:Yes. "Solve conduct, solve content." 7: 3881:Arbitrator/Mediator managed RFC/poll 1576:Now, if anyone can find this actual 18:Knowledge (XXG):Requests for comment 1731:None. ArbCom is for conduct issues. 2242:I, like Xavexgoem, mediate at the 24: 1739:No. ArbCom is for conduct issues. 2791:among the editors of the article 1189:Frankly, I'd also like to see a 4031:Users who endorse this proposal 3966:Possible proposal on behalf of 3946:Users who endorse this proposal 3771:Users who endorse this proposal 3588:Users who endorse this proposal 3490:Users who endorse this proposal 3345:Users who endorse this proposal 3101:Users who endorse this proposal 3002:Users who endorse this proposal 2953:Users who endorse this proposal 2813:Users who endorse this proposal 1708:To answer the questions first: 1184:Daybreak (Battlestar Galactica) 2003:Agree with Nifboy completely. 1774:, which underscore the issue. 1772:Science is not a point of view 1756:No, it cannot rule on content. 1748:No, it cannot rule on content. 594:Solve conduct, solve content. 61: 1: 4117:04:08, 25 January 2011 (UTC) 3081:04:05, 25 January 2011 (UTC) 2682:article before they'll even 2670:users to complain about the 1764:Yes, but only if done right. 1436:04:13, 25 January 2011 (UTC) 4091:Yes we need more people at 3850:Users who endorse this view 2809:Mark this page historical. 2753:Users who endorse this view 2617:Users who endorse this view 2315:Users who endorse this view 1907:Users who endorse this view 1819:Users who endorse this view 1690:Users who endorse this view 1595:Users who endorse this view 1464:Users who endorse this view 1198:Users who endorse this view 1144:Users who endorse this view 1064:Users who endorse this view 904:Users who endorse this view 534:Users who endorse this view 195:Users who endorse this view 119:Users who endorse this view 4135: 2774:Another additional comment 997:reliability be beneficial? 65: 50:reliability be beneficial? 2768:20:07, 22 June 2009 (UTC) 2748:10:34, 22 June 2009 (UTC) 2649:18:57, 10 July 2009 (UTC) 2466:15:46, 23 June 2009 (UTC) 2227:15:44, 23 June 2009 (UTC) 1666:15:38, 23 June 2009 (UTC) 880:21:01, 10 June 2009 (UTC) 4083:08:39, 2 June 2009 (UTC) 4070:23:10, 31 May 2009 (UTC) 4053:02:25, 26 May 2009 (UTC) 4040:15:36, 24 May 2009 (UTC) 3988:10:19, 23 May 2009 (UTC) 3960:03:53, 20 May 2009 (UTC) 3920:10:15, 19 May 2009 (UTC) 3873:23:10, 31 May 2009 (UTC) 3844:04:51, 19 May 2009 (UTC) 3795:22:33, 19 May 2009 (UTC) 3742:15:27, 24 May 2009 (UTC) 3729:16:13, 19 May 2009 (UTC) 3711:21:39, 18 May 2009 (UTC) 3695:03:14, 18 May 2009 (UTC) 3681:20:18, 15 May 2009 (UTC) 3668:16:08, 11 May 2009 (UTC) 3658:I could live with this. 3654:16:05, 11 May 2009 (UTC) 3640:15:57, 11 May 2009 (UTC) 3627:14:54, 11 May 2009 (UTC) 3610:14:13, 11 May 2009 (UTC) 3552:06:19, 25 May 2009 (UTC) 3531:02:05, 24 May 2009 (UTC) 3504:12:04, 11 May 2009 (UTC) 3443:23:43, 16 May 2009 (UTC) 3426:yes, as stated above. — 3422:23:23, 15 May 2009 (UTC) 3399:03:38, 14 May 2009 (UTC) 3376:15:29, 11 May 2009 (UTC) 3365:10:12, 11 May 2009 (UTC) 3324:21:39, 2 June 2009 (UTC) 3311:23:10, 31 May 2009 (UTC) 3295:10:23, 24 May 2009 (UTC) 3276:02:06, 24 May 2009 (UTC) 3251:20:39, 23 May 2009 (UTC) 3238:21:45, 21 May 2009 (UTC) 3227:07:00, 13 May 2009 (UTC) 3214:02:14, 13 May 2009 (UTC) 3205:11:07, 12 May 2009 (UTC) 3191:15:43, 11 May 2009 (UTC) 3177:12:05, 11 May 2009 (UTC) 3164:01:15, 11 May 2009 (UTC) 3151:21:22, 10 May 2009 (UTC) 3138:20:01, 10 May 2009 (UTC) 3127:18:48, 10 May 2009 (UTC) 3117:18:45, 10 May 2009 (UTC) 3055:01:02, 18 May 2009 (UTC) 3038:23:57, 14 May 2009 (UTC) 3025:22:37, 10 May 2009 (UTC) 3012:17:11, 10 May 2009 (UTC) 2983:19:31, 14 May 2009 (UTC) 2973:17:09, 10 May 2009 (UTC) 2930:19:43, 15 May 2009 (UTC) 2915:07:00, 13 May 2009 (UTC) 2902:02:14, 13 May 2009 (UTC) 2893:11:07, 12 May 2009 (UTC) 2880:01:15, 11 May 2009 (UTC) 2867:21:22, 10 May 2009 (UTC) 2854:20:01, 10 May 2009 (UTC) 2843:17:09, 10 May 2009 (UTC) 2824:17:06, 10 May 2009 (UTC) 2726:16:04, 22 May 2009 (UTC) 2708:16:01, 22 May 2009 (UTC) 2636:23:10, 31 May 2009 (UTC) 2611:04:46, 19 May 2009 (UTC) 2561:14:25, 18 May 2009 (UTC) 2529:14:25, 18 May 2009 (UTC) 2494:14:25, 18 May 2009 (UTC) 2453:17:49, 18 May 2009 (UTC) 2440:03:33, 18 May 2009 (UTC) 2422:03:01, 18 May 2009 (UTC) 2408:23:42, 16 May 2009 (UTC) 2383:19:40, 15 May 2009 (UTC) 2367:17:08, 15 May 2009 (UTC) 2352:19:56, 14 May 2009 (UTC) 2338:01:41, 14 May 2009 (UTC) 2310:01:48, 14 May 2009 (UTC) 2213:20:20, 2 June 2009 (UTC) 2192:21:51, 1 June 2009 (UTC) 2177:02:25, 26 May 2009 (UTC) 2163:17:44, 21 May 2009 (UTC) 2149:16:22, 21 May 2009 (UTC) 2128:02:38, 18 May 2009 (UTC) 2113:23:40, 16 May 2009 (UTC) 2092:20:44, 16 May 2009 (UTC) 2074:00:44, 15 May 2009 (UTC) 2051:19:54, 14 May 2009 (UTC) 2036:19:27, 14 May 2009 (UTC) 2022:21:50, 13 May 2009 (UTC) 1999:09:05, 13 May 2009 (UTC) 1985:04:05, 12 May 2009 (UTC) 1969:16:41, 11 May 2009 (UTC) 1952:16:09, 11 May 2009 (UTC) 1939:14:56, 11 May 2009 (UTC) 1926:02:30, 11 May 2009 (UTC) 1899:02:15, 11 May 2009 (UTC) 1874:00:15, 15 May 2009 (UTC) 1860:06:05, 11 May 2009 (UTC) 1842:22:36, 10 May 2009 (UTC) 1829:16:11, 10 May 2009 (UTC) 1653:17:09, 15 May 2009 (UTC) 1634:19:25, 14 May 2009 (UTC) 1621:13:53, 11 May 2009 (UTC) 1609:10:51, 10 May 2009 (UTC) 1590:10:51, 10 May 2009 (UTC) 1557:11:06, 12 May 2009 (UTC) 1544:18:49, 10 May 2009 (UTC) 1534:16:08, 10 May 2009 (UTC) 1519:14:53, 10 May 2009 (UTC) 1508:10:24, 10 May 2009 (UTC) 1495:10:19, 10 May 2009 (UTC) 1482:09:26, 10 May 2009 (UTC) 1410:20:25, 2 June 2009 (UTC) 1393:15:21, 22 May 2009 (UTC) 1380:02:47, 18 May 2009 (UTC) 1365:16:53, 15 May 2009 (UTC) 1352:19:50, 14 May 2009 (UTC) 1338:19:26, 14 May 2009 (UTC) 1325:02:05, 13 May 2009 (UTC) 1308:16:50, 12 May 2009 (UTC) 1283:19:51, 12 May 2009 (UTC) 1262:16:36, 11 May 2009 (UTC) 1244:01:56, 11 May 2009 (UTC) 1227:10:40, 10 May 2009 (UTC) 1212:03:00, 10 May 2009 (UTC) 1158:01:39, 10 May 2009 (UTC) 1112:18:05, 14 May 2009 (UTC) 1091:11:05, 12 May 2009 (UTC) 1078:01:50, 10 May 2009 (UTC) 930:19:38, 15 May 2009 (UTC) 867:21:33, 2 June 2009 (UTC) 854:20:43, 2 June 2009 (UTC) 841:20:31, 2 June 2009 (UTC) 825:23:10, 31 May 2009 (UTC) 809:10:18, 24 May 2009 (UTC) 790:23:32, 16 May 2009 (UTC) 765:18:02, 14 May 2009 (UTC) 744:22:09, 13 May 2009 (UTC) 728:22:01, 13 May 2009 (UTC) 705:19:21, 13 May 2009 (UTC) 692:02:03, 13 May 2009 (UTC) 683:11:04, 12 May 2009 (UTC) 670:00:24, 12 May 2009 (UTC) 662:23:55, 10 May 2009 (UTC) 649:11:19, 10 May 2009 (UTC) 635:09:29, 10 May 2009 (UTC) 617:08:21, 10 May 2009 (UTC) 604:01:22, 10 May 2009 (UTC) 510:20:42, 2 June 2009 (UTC) 497:20:29, 2 June 2009 (UTC) 481:10:11, 24 May 2009 (UTC) 462:23:30, 16 May 2009 (UTC) 441:16:20, 16 May 2009 (UTC) 417:19:39, 15 May 2009 (UTC) 402:22:08, 13 May 2009 (UTC) 386:21:55, 13 May 2009 (UTC) 363:11:03, 12 May 2009 (UTC) 350:00:23, 12 May 2009 (UTC) 342:01:57, 11 May 2009 (UTC) 334:23:55, 10 May 2009 (UTC) 321:10:36, 10 May 2009 (UTC) 308:09:31, 10 May 2009 (UTC) 290:08:20, 10 May 2009 (UTC) 277:02:07, 10 May 2009 (UTC) 258:01:21, 10 May 2009 (UTC) 156:07:26, 10 May 2009 (UTC) 1135:Near as I can tell the 915:23:27, 9 May 2009 (UTC) 590:23:53, 9 May 2009 (UTC) 570:23:21, 9 May 2009 (UTC) 561:23:09, 9 May 2009 (UTC) 550:23:00, 9 May 2009 (UTC) 245:23:13, 9 May 2009 (UTC) 232:23:09, 9 May 2009 (UTC) 221:23:02, 9 May 2009 (UTC) 206:22:56, 9 May 2009 (UTC) 143:23:47, 9 May 2009 (UTC) 130:23:27, 9 May 2009 (UTC) 110:21:03, 9 May 2009 (UTC) 2515:enforce effectively. 2259: 1778:Content dispute ArbCom 945:I'm a coordinator for 3976:User:FimusTauri/RfCwO 2426:Sounds good to me. - 2257: 29:Arbitration Committee 4014:Strengthen existing 3801:Vague suggestion by 2184:William M. Connolley 2026:The problem exists. 4020:request for comment 947:the mediation cabal 3715:Let's try this. - 3470:(e) That disputes 3091:Ryan Postlethwaite 2731:Additional comment 2657:User:Peter jackson 2260: 1981: 520:Ryan Postlethwaite 3958: 3918: 3817:An article could 3625: 3441: 3009:Kim van der Linde 2674:behaviour of the 2406: 2391:point for now. — 2387:perhaps the best 2211: 2147: 2111: 1975: 1858: 1826:Kim van der Linde 1650: 1408: 1323: 1280: 1110: 839: 788: 763: 495: 460: 4126: 4101: 4060: 4007:Proposal #14 by 3954: 3925:Proposal #11 by 3914: 3863: 3791: 3785: 3779: 3717:Peregrine Fisher 3615: 3440: 3438: 3427: 3419: 3409: 3397: 3394: 3393:Help us mediate! 3385: 3363: 3357: 3301: 3292: 3290: 3285: 3124: 3113: 3110: 3065: 3043:Peregrine Fisher 2968: 2838: 2821: 2626: 2428:Peregrine Fisher 2405: 2403: 2392: 2336: 2333: 2332:Help us mediate! 2324: 2308: 2305: 2304:Help us mediate! 2296: 2210: 2208: 2201: 2137: 2110: 2108: 2097: 2071: 2061: 2020: 2017: 2016:Help us mediate! 2008: 1979: 1957:Peregrine Fisher 1936: 1935: 1848: 1649: 1646: 1643: 1618: 1541: 1480: 1474: 1420: 1407: 1405: 1398: 1313: 1306: 1303: 1297: 1279: 1276: 1273: 1250:Peregrine Fisher 1109: 1107: 1096: 833: 815: 806: 804: 799: 787: 785: 774: 762: 760: 749: 737: 726: 723: 722:Help us mediate! 714: 633: 627: 546: 543: 489: 478: 476: 471: 459: 457: 446: 395: 384: 381: 380:Help us mediate! 372: 367:Yes, certainly. 306: 300: 272: 217: 214: 203: 62:proposal section 32:has opened this 4134: 4133: 4129: 4128: 4127: 4125: 4124: 4123: 4097: 4058: 4012: 3998: 3971: 3968:User:FimusTauri 3930: 3883: 3861: 3806: 3789: 3783: 3777: 3755: 3750:Proposal #8 by 3567: 3562:Proposal #7 by 3456: 3451:Proposal #6 by 3436: 3428: 3418: 3415: 3405: 3396: 3392: 3383: 3381: 3355: 3352: 3338: 3333:Proposal #5 by 3299: 3288: 3283: 3281: 3122: 3111: 3108: 3094: 3089:Proposal #4 by 3061: 2996: 2991:Proposal #3 by 2966: 2943: 2938:Proposal #2 by 2836: 2819: 2807: 2802:Proposal #1 by 2799: 2776: 2733: 2660: 2624: 2572: 2540: 2505: 2477: 2401: 2393: 2335: 2331: 2322: 2320: 2307: 2303: 2294: 2292: 2270:game the system 2244:Mediation Cabal 2240: 2204: 2202: 2106: 2098: 2070: 2067: 2057: 2019: 2015: 2006: 2004: 1977: 1933: 1932: 1884: 1804:A few remarks: 1780: 1745:be beneficial? 1706: 1679: 1647: 1639: 1614: 1570: 1539: 1472: 1469: 1449: 1416: 1401: 1399: 1301: 1290: 1287: 1277: 1269: 1171: 1125: 1105: 1097: 943: 893: 813: 802: 797: 795: 783: 775: 773:of the time. — 758: 750: 735: 725: 721: 712: 710: 625: 622: 544: 541: 523: 474: 469: 467: 455: 447: 393: 383: 379: 370: 368: 298: 295: 270: 215: 212: 201: 169: 82: 74: 22: 21: 20: 12: 11: 5: 4132: 4130: 4122: 4121: 4120: 4119: 4088: 4087: 4086: 4085: 4073: 4072: 4055: 4042: 4032: 4011: 4005: 3997: 3991: 3970: 3964: 3963: 3962: 3948: 3947: 3929: 3923: 3882: 3879: 3878: 3877: 3876: 3875: 3852: 3851: 3847: 3846: 3832: 3831: 3830: 3826: 3823: 3815: 3805: 3799: 3798: 3797: 3773: 3772: 3754: 3752:User:Rootology 3748: 3747: 3746: 3745: 3744: 3731: 3713: 3697: 3683: 3670: 3656: 3642: 3629: 3612: 3589: 3585: 3584: 3581: 3578: 3575: 3566: 3560: 3559: 3558: 3557: 3556: 3555: 3554: 3534: 3533: 3510: 3509: 3508: 3507: 3491: 3455: 3449: 3448: 3447: 3446: 3445: 3424: 3416: 3401: 3390: 3378: 3367: 3347: 3346: 3337: 3331: 3330: 3329: 3328: 3327: 3313: 3297: 3278: 3253: 3240: 3229: 3216: 3207: 3194: 3180: 3166: 3153: 3140: 3129: 3119: 3102: 3093: 3087: 3086: 3085: 3084: 3083: 3057: 3040: 3027: 3014: 3003: 2995: 2989: 2988: 2987: 2986: 2985: 2975: 2954: 2942: 2940:NuclearWarfare 2936: 2935: 2934: 2933: 2932: 2917: 2904: 2895: 2882: 2869: 2856: 2845: 2826: 2814: 2806: 2800: 2798: 2795: 2794: 2793: 2787: 2775: 2772: 2771: 2770: 2755: 2754: 2732: 2729: 2659: 2653: 2652: 2651: 2640: 2639: 2638: 2619: 2618: 2614: 2613: 2598: 2594: 2590: 2587: 2583: 2580: 2571: 2565: 2564: 2563: 2539: 2533: 2532: 2531: 2504: 2498: 2497: 2496: 2476: 2470: 2469: 2468: 2455: 2442: 2424: 2410: 2385: 2369: 2354: 2340: 2329: 2317: 2316: 2301: 2286: 2285: 2280: 2279: 2275: 2274: 2252: 2251: 2239: 2233: 2232: 2231: 2230: 2229: 2215: 2194: 2179: 2165: 2151: 2130: 2115: 2094: 2076: 2068: 2053: 2038: 2024: 2013: 2001: 1987: 1971: 1954: 1941: 1928: 1908: 1903: 1883: 1880: 1879: 1878: 1877: 1876: 1862: 1844: 1831: 1820: 1816: 1815: 1812: 1809: 1802: 1801: 1798: 1794: 1791: 1788: 1779: 1776: 1768: 1767: 1766: 1765: 1759: 1758: 1757: 1751: 1750: 1749: 1742: 1741: 1740: 1734: 1733: 1732: 1726: 1725: 1724: 1718: 1717: 1716: 1705: 1699: 1698: 1697: 1696: 1695: 1691: 1678: 1672: 1671: 1670: 1669: 1668: 1655: 1636: 1623: 1611: 1601:LessHeard vanU 1596: 1582:LessHeard vanU 1569: 1567:LessHeard vanU 1563: 1562: 1561: 1560: 1559: 1546: 1536: 1521: 1510: 1497: 1484: 1465: 1448: 1442: 1441: 1440: 1439: 1438: 1412: 1395: 1382: 1368: 1354: 1340: 1327: 1310: 1285: 1264: 1246: 1229: 1219:LessHeard vanU 1214: 1199: 1170: 1164: 1163: 1162: 1161: 1160: 1145: 1137:RS noticeboard 1124: 1118: 1117: 1116: 1115: 1114: 1093: 1080: 1065: 1061: 1060: 1059: 1058: 1047: 1046: 1042: 1041: 1040: 1039: 1033: 1032: 1028: 1027: 1026: 1025: 1019: 1018: 1017: 1016: 1009: 1008: 1007: 1006: 999: 998: 993: 992: 991: 990: 984: 983: 982: 981: 970: 969: 965: 964: 963: 962: 955: 954: 942: 936: 935: 934: 933: 932: 917: 905: 892: 886: 885: 884: 883: 882: 869: 856: 843: 827: 811: 792: 767: 746: 730: 719: 707: 694: 685: 672: 664: 651: 637: 619: 606: 592: 572: 563: 552: 535: 522: 516: 515: 514: 513: 512: 499: 483: 464: 443: 419: 404: 388: 377: 365: 352: 344: 336: 323: 310: 292: 279: 260: 247: 234: 223: 208: 196: 168: 162: 161: 160: 159: 158: 145: 132: 120: 115: 113: 112: 97: 94: 91: 87: 81: 75: 73: 70: 58: 57: 54: 51: 47: 44: 23: 15: 14: 13: 10: 9: 6: 4: 3: 2: 4131: 4118: 4114: 4110: 4106: 4102: 4100: 4094: 4090: 4089: 4084: 4081: 4077: 4076: 4075: 4074: 4071: 4067: 4063: 4056: 4054: 4050: 4046: 4043: 4041: 4038: 4035: 4034: 4033: 4030: 4029: 4028: 4025: 4021: 4017: 4016:Third Opinion 4010: 4006: 4004: 4001: 3996: 3992: 3990: 3989: 3985: 3981: 3980:Peter jackson 3977: 3969: 3965: 3961: 3957: 3953: 3950: 3949: 3945: 3944: 3943: 3939: 3936: 3928: 3924: 3922: 3921: 3917: 3913: 3909: 3905: 3901: 3897: 3893: 3889: 3880: 3874: 3870: 3866: 3859: 3858:Vague support 3856: 3855: 3854: 3853: 3849: 3848: 3845: 3841: 3837: 3833: 3827: 3824: 3820: 3816: 3812: 3811: 3808: 3807: 3804: 3800: 3796: 3792: 3786: 3780: 3775: 3774: 3770: 3769: 3768: 3766: 3762: 3761: 3753: 3749: 3743: 3740: 3736: 3732: 3730: 3726: 3722: 3718: 3714: 3712: 3708: 3704: 3703: 3698: 3696: 3692: 3688: 3684: 3682: 3678: 3674: 3671: 3669: 3665: 3661: 3657: 3655: 3651: 3647: 3643: 3641: 3638: 3635: 3630: 3628: 3623: 3619: 3613: 3611: 3607: 3603: 3599: 3595: 3592: 3591: 3590: 3587: 3586: 3582: 3579: 3576: 3573: 3572: 3571: 3565: 3561: 3553: 3549: 3545: 3541: 3536: 3535: 3532: 3528: 3524: 3523: 3517: 3516: 3514: 3513: 3512: 3511: 3505: 3501: 3497: 3494: 3493: 3492: 3489: 3488: 3487: 3484: 3481: 3478: 3475: 3473: 3468: 3465: 3462: 3459: 3454: 3450: 3444: 3439: 3433: 3432: 3425: 3423: 3420: 3412: 3410: 3408: 3402: 3400: 3395: 3389: 3386: 3384:Steve Crossin 3379: 3377: 3374: 3371: 3368: 3366: 3362: 3359: 3358: 3351: 3350: 3349: 3348: 3344: 3343: 3342: 3336: 3332: 3325: 3321: 3317: 3314: 3312: 3308: 3304: 3298: 3296: 3293: 3291: 3286: 3279: 3277: 3273: 3269: 3268: 3263: 3259: 3258: 3254: 3252: 3248: 3244: 3241: 3239: 3236: 3233: 3230: 3228: 3224: 3220: 3217: 3215: 3212: 3208: 3206: 3202: 3198: 3195: 3192: 3188: 3184: 3181: 3178: 3174: 3170: 3167: 3165: 3161: 3157: 3154: 3152: 3148: 3144: 3141: 3139: 3136: 3133: 3130: 3128: 3125: 3120: 3118: 3115: 3114: 3112:Postlethwaite 3105: 3104: 3103: 3100: 3099: 3098: 3092: 3088: 3082: 3078: 3074: 3070: 3066: 3064: 3058: 3056: 3052: 3048: 3044: 3041: 3039: 3035: 3031: 3028: 3026: 3022: 3018: 3015: 3013: 3010: 3006: 3005: 3004: 3001: 3000: 2999: 2994: 2990: 2984: 2981: 2979: 2976: 2974: 2971: 2969: 2962: 2961: 2957: 2956: 2955: 2952: 2951: 2950: 2948: 2941: 2937: 2931: 2927: 2923: 2922: 2918: 2916: 2912: 2908: 2905: 2903: 2900: 2896: 2894: 2890: 2886: 2883: 2881: 2877: 2873: 2870: 2868: 2864: 2860: 2857: 2855: 2852: 2849: 2846: 2844: 2841: 2839: 2832: 2831: 2827: 2825: 2822: 2817: 2816: 2815: 2812: 2811: 2810: 2805: 2801: 2796: 2792: 2788: 2785: 2781: 2780: 2779: 2773: 2769: 2765: 2761: 2757: 2756: 2752: 2751: 2750: 2749: 2745: 2741: 2740:Peter jackson 2736: 2730: 2728: 2727: 2723: 2719: 2718:Peter jackson 2715: 2710: 2709: 2705: 2701: 2700:Peter jackson 2697: 2694: 2688: 2685: 2681: 2677: 2673: 2669: 2663: 2658: 2654: 2650: 2647: 2644: 2641: 2637: 2633: 2629: 2623: 2622: 2621: 2620: 2616: 2615: 2612: 2608: 2604: 2599: 2595: 2591: 2588: 2584: 2581: 2577: 2576: 2575: 2570: 2566: 2562: 2558: 2554: 2550: 2549: 2548: 2544: 2538: 2534: 2530: 2526: 2522: 2518: 2517: 2516: 2512: 2508: 2503: 2499: 2495: 2491: 2487: 2483: 2482: 2481: 2475: 2471: 2467: 2463: 2459: 2456: 2454: 2450: 2446: 2443: 2441: 2437: 2433: 2429: 2425: 2423: 2419: 2415: 2411: 2409: 2404: 2398: 2397: 2390: 2386: 2384: 2380: 2376: 2375: 2370: 2368: 2364: 2360: 2355: 2353: 2349: 2345: 2341: 2339: 2334: 2328: 2325: 2323:Steve Crossin 2319: 2318: 2314: 2313: 2312: 2311: 2306: 2300: 2297: 2295:Steve Crossin 2291: 2282: 2281: 2277: 2276: 2271: 2267: 2262: 2261: 2256: 2249: 2248: 2247: 2245: 2238: 2237:Steve Crossin 2234: 2228: 2224: 2220: 2216: 2214: 2209: 2207: 2199: 2195: 2193: 2189: 2185: 2180: 2178: 2174: 2170: 2167:Very true. — 2166: 2164: 2161: 2157: 2152: 2150: 2145: 2141: 2136: 2131: 2129: 2125: 2121: 2116: 2114: 2109: 2103: 2102: 2095: 2093: 2089: 2085: 2081: 2077: 2075: 2072: 2064: 2062: 2060: 2054: 2052: 2048: 2044: 2039: 2037: 2033: 2029: 2025: 2023: 2018: 2012: 2009: 2007:Steve Crossin 2002: 2000: 1996: 1992: 1988: 1986: 1983: 1980: 1972: 1970: 1966: 1962: 1958: 1955: 1953: 1949: 1945: 1942: 1940: 1937: 1929: 1927: 1923: 1919: 1915: 1911: 1910: 1909: 1906: 1905: 1904: 1901: 1900: 1896: 1892: 1891: 1881: 1875: 1871: 1867: 1863: 1861: 1856: 1852: 1845: 1843: 1839: 1835: 1832: 1830: 1827: 1823: 1822: 1821: 1818: 1817: 1813: 1810: 1807: 1806: 1805: 1799: 1795: 1792: 1789: 1786: 1785: 1784: 1777: 1775: 1773: 1763: 1762: 1760: 1755: 1754: 1752: 1747: 1746: 1743: 1738: 1737: 1735: 1730: 1729: 1727: 1722: 1721: 1719: 1714: 1713: 1711: 1710: 1709: 1704: 1700: 1694: 1693: 1692: 1689: 1688: 1687: 1683: 1677: 1676:89.101.220.70 1673: 1667: 1663: 1659: 1656: 1654: 1651: 1644: 1642: 1637: 1635: 1631: 1627: 1624: 1622: 1619: 1617: 1612: 1610: 1606: 1602: 1599: 1598: 1597: 1594: 1593: 1592: 1591: 1587: 1583: 1579: 1574: 1568: 1564: 1558: 1554: 1550: 1547: 1545: 1542: 1537: 1535: 1531: 1527: 1522: 1520: 1517: 1514: 1511: 1509: 1505: 1501: 1498: 1496: 1492: 1488: 1485: 1483: 1479: 1476: 1475: 1468: 1467: 1466: 1463: 1462: 1461: 1457: 1453: 1447: 1443: 1437: 1433: 1429: 1425: 1421: 1419: 1413: 1411: 1406: 1404: 1396: 1394: 1390: 1386: 1385:Peter jackson 1383: 1381: 1377: 1373: 1369: 1366: 1362: 1358: 1355: 1353: 1349: 1345: 1341: 1339: 1335: 1331: 1328: 1326: 1321: 1317: 1311: 1309: 1304: 1298: 1296: 1294: 1286: 1284: 1281: 1274: 1272: 1265: 1263: 1259: 1255: 1251: 1247: 1245: 1241: 1237: 1236: 1230: 1228: 1224: 1220: 1215: 1213: 1209: 1205: 1202: 1201: 1200: 1197: 1196: 1195: 1192: 1187: 1185: 1181: 1177: 1169: 1165: 1159: 1155: 1151: 1148: 1147: 1146: 1143: 1142: 1141: 1138: 1133: 1129: 1123: 1119: 1113: 1108: 1102: 1101: 1094: 1092: 1088: 1084: 1081: 1079: 1075: 1071: 1068: 1067: 1066: 1063: 1062: 1055: 1051: 1050: 1049: 1048: 1044: 1043: 1037: 1036: 1035: 1034: 1030: 1029: 1023: 1022: 1021: 1020: 1013: 1012: 1011: 1010: 1003: 1002: 1001: 1000: 995: 994: 988: 987: 986: 985: 979: 974: 973: 972: 971: 967: 966: 959: 958: 957: 956: 952: 951: 950: 948: 941: 937: 931: 927: 923: 922: 918: 916: 913: 911: 908: 907: 906: 903: 902: 901: 897: 891: 887: 881: 877: 873: 870: 868: 864: 860: 857: 855: 851: 847: 844: 842: 837: 836:My narrowboat 832: 828: 826: 822: 818: 812: 810: 807: 805: 800: 793: 791: 786: 780: 779: 772: 768: 766: 761: 755: 754: 748:Well said. -- 747: 745: 742: 739: 738: 731: 729: 724: 718: 715: 713:Steve Crossin 708: 706: 702: 698: 695: 693: 690: 686: 684: 680: 676: 673: 671: 668: 665: 663: 659: 655: 652: 650: 646: 642: 638: 636: 632: 629: 628: 620: 618: 614: 610: 607: 605: 601: 597: 593: 591: 587: 584: 581: 577: 573: 571: 568: 564: 562: 559: 556: 553: 551: 548: 547: 545:Postlethwaite 538: 537: 536: 533: 532: 531: 527: 521: 517: 511: 507: 503: 500: 498: 493: 492:My narrowboat 488: 484: 482: 479: 477: 472: 465: 463: 458: 452: 451: 444: 442: 438: 434: 430: 425: 420: 418: 414: 410: 409: 405: 403: 400: 397: 396: 389: 387: 382: 376: 373: 371:Steve Crossin 366: 364: 360: 356: 353: 351: 348: 345: 343: 340: 337: 335: 331: 327: 324: 322: 318: 314: 311: 309: 305: 302: 301: 293: 291: 287: 283: 280: 278: 275: 273: 266: 265: 261: 259: 255: 251: 248: 246: 242: 238: 235: 233: 230: 227: 224: 222: 219: 218: 216:Postlethwaite 209: 207: 204: 199: 198: 197: 194: 193: 192: 190: 186: 181: 177: 173: 167: 163: 157: 153: 149: 146: 144: 140: 136: 133: 131: 128: 126: 123: 122: 121: 118: 117: 116: 111: 107: 103: 98: 95: 92: 88: 84: 83: 80: 76: 71: 69: 67: 66:views section 63: 55: 52: 48: 45: 42: 41: 40: 37: 35: 31: 30: 19: 4098: 4013: 4002: 3999: 3993:Proposal by 3972: 3940: 3931: 3907: 3903: 3899: 3895: 3891: 3887: 3884: 3857: 3818: 3764: 3758: 3756: 3700: 3568: 3539: 3520: 3485: 3482: 3479: 3476: 3471: 3469: 3466: 3463: 3460: 3457: 3429: 3406: 3387: 3353: 3339: 3280: 3265: 3255: 3232:Renaissancee 3183:CarolMooreDC 3106: 3095: 3062: 2997: 2963: 2959: 2944: 2919: 2833: 2829: 2808: 2790: 2777: 2734: 2713: 2711: 2698: 2692: 2689: 2683: 2679: 2678:user on the 2675: 2671: 2667: 2664: 2661: 2573: 2551:Proposed. -- 2545: 2541: 2519:Proposed. -- 2513: 2509: 2506: 2484:Proposed. -- 2478: 2394: 2388: 2372: 2326: 2298: 2288: 2287: 2265: 2241: 2205: 2197: 2099: 2058: 2010: 1902: 1888: 1885: 1803: 1781: 1769: 1707: 1684: 1680: 1640: 1616:PirateSmackK 1615: 1575: 1571: 1470: 1458: 1454: 1450: 1417: 1402: 1292: 1291: 1270: 1233: 1188: 1180:User:Arcayne 1175: 1172: 1134: 1130: 1126: 1099: 1053: 977: 944: 919: 898: 894: 794: 776: 770: 752: 736:Juliancolton 733: 716: 654:CarolMooreDC 623: 582: 539: 528: 524: 466: 448: 428: 423: 406: 394:Juliancolton 391: 374: 326:CarolMooreDC 296: 267: 263: 210: 182: 178: 174: 170: 114: 59: 38: 33: 27: 25: 3952:Askari Mark 3935:John Carter 3933:agree with 3927:Askari Mark 3829:authority.) 3814:to be rare. 3602:John Carter 3594:John Carter 3564:John Carter 3542:quickly).-- 3519:necessary. 3197:Jasy jatere 2978:jbolden1517 2885:Jasy jatere 2535:View #3 by 2500:View #2 by 2472:View #1 by 2135:Josiah Rowe 2028:John Carter 1914:penalty box 1882:view by DGG 1866:John Carter 1626:John Carter 1549:Jasy jatere 1460:solution. 1330:John Carter 1083:Jasy jatere 910:jbolden1517 890:Jbolden1517 831:RegentsPark 675:Jasy jatere 487:RegentsPark 433:Ncmvocalist 355:Jasy jatere 125:jbolden1517 102:John Carter 79:John Carter 4062:Coppertwig 3865:Coppertwig 3735:WP:PROJPOL 3687:Scott Free 3407:S Marshall 3303:Coppertwig 3143:PhilKnight 2993:KimvdLinde 2859:PhilKnight 2628:Coppertwig 2553:Scott Free 2537:Scott Free 2521:Scott Free 2502:Scott Free 2486:Scott Free 2474:Scott Free 2414:Scott Free 2290:community. 2206:Sandstein 2198:sufficient 2059:S Marshall 1934:Skomorokh 1703:KimvdLinde 1526:PhilKnight 1403:Sandstein 1372:Scott Free 817:Coppertwig 4099:Doc James 3778:rootology 3634:Fut.Perf. 3515:Comments 3156:Xavexgoem 3123:Skomorokh 3063:Doc James 2872:Xavexgoem 2797:Proposals 2156:Sortition 2080:DR system 1540:Skomorokh 1500:Xavexgoem 1418:Doc James 1070:Xavexgoem 940:Xavexgoem 596:Xavexgoem 250:Xavexgoem 86:disputes. 4109:contribs 4024:cab rank 3995:Ashley Y 3819:possibly 3725:contribs 3673:Karanacs 3660:Jclemens 3646:Kotniski 3544:Kotniski 3496:Kotniski 3453:Kotniski 3356:SilkTork 3335:SilkTork 3219:Davewild 3211:Ashley Y 3169:Kotniski 3073:contribs 3051:contribs 3017:Jclemens 2907:Davewild 2899:Ashley Y 2684:consider 2655:View by 2593:divided. 2567:View by 2436:contribs 2389:starting 2359:HighKing 2344:Karanacs 2235:View by 2144:contribs 2120:JayHenry 2043:Karanacs 1989:Indeed. 1965:contribs 1944:Jclemens 1834:Jclemens 1797:lacking. 1701:View by 1674:View by 1565:View by 1487:Davewild 1473:SilkTork 1446:SilkTork 1444:View by 1428:contribs 1357:HighKing 1344:Karanacs 1258:contribs 1204:Jclemens 1168:Jclemens 1166:View by 1120:View by 1100:Kanonkas 1054:anything 938:View by 888:View by 753:Kanonkas 689:Ashley Y 667:Ynhockey 626:SilkTork 609:Davewild 586:contribs 576:Casliber 518:View by 347:Ynhockey 313:Apoc2400 299:SilkTork 282:Davewild 164:View by 135:AndrewRT 77:View by 3836:Mishlai 3803:Mishlai 3614:— Carl 3243:Crum375 2760:Dlabtot 2714:liberal 2603:Mishlai 2569:Mishlai 2458:Laurent 2445:Dlabtot 2219:Laurent 2084:Protonk 1658:Laurent 1641:Arcayne 1312:— Carl 1271:Arcayne 1191:WP:FICT 1005:system. 872:Locke9k 641:Rebecca 148:Ceedjee 4093:WP:RFC 4045:Avenue 3956:(Talk) 3912:Hiding 3906:we do 3898:we do 3890:we do 3370:Anomie 3316:Sunray 3284:hmwith 3235:(talk) 3132:Anomie 2947:MedCom 2848:Anomie 2820:Durova 2804:Durova 2784:WP:DUE 2169:Avenue 1991:Stifle 1918:Nifboy 1513:Anomie 1295:dokter 1150:Nifboy 1122:Nifboy 859:Sunray 846:John Z 798:hmwith 555:Anomie 502:John Z 470:hmwith 429:actual 237:Nifboy 226:Anomie 202:Durova 189:MedCom 166:Durova 4113:email 4080:Rd232 4037:Rd232 4009:Rd232 3902:, if 3894:, if 3757:See: 3739:Rd232 3380:Yep. 3077:email 3030:Cla68 2693:their 2668:three 2646:Adler 2160:Rd232 1432:email 1176:court 1106:Talk 1057:etc). 769:yea, 759:Talk 639:Yes. 339:Rd232 72:Views 16:< 4105:talk 4066:talk 4049:talk 4018:and 3984:talk 3869:talk 3840:talk 3721:talk 3707:talk 3691:talk 3677:talk 3664:talk 3650:talk 3622:talk 3606:talk 3598:talk 3548:talk 3527:talk 3500:talk 3431:Ched 3417:Cont 3320:talk 3307:talk 3272:talk 3262:talk 3247:talk 3223:talk 3201:talk 3187:talk 3173:talk 3160:talk 3147:talk 3109:Ryan 3069:talk 3047:talk 3034:talk 3021:talk 2967:Talk 2926:talk 2921:Cirt 2911:talk 2889:talk 2876:talk 2863:talk 2837:Talk 2764:talk 2744:talk 2722:talk 2704:talk 2680:same 2676:same 2672:same 2643:Hans 2632:talk 2607:talk 2557:talk 2525:talk 2490:talk 2462:talk 2449:talk 2432:talk 2418:talk 2396:Ched 2379:talk 2374:Cirt 2363:talk 2348:talk 2223:talk 2188:talk 2173:talk 2140:talk 2124:talk 2101:Ched 2088:talk 2069:Cont 2047:talk 2032:talk 1995:talk 1961:talk 1948:talk 1922:talk 1895:talk 1870:talk 1855:talk 1838:talk 1662:talk 1630:talk 1605:talk 1586:talk 1580:... 1578:wand 1553:talk 1530:talk 1504:talk 1491:talk 1424:talk 1389:talk 1376:talk 1361:talk 1348:talk 1334:talk 1320:talk 1302:Talk 1254:talk 1240:talk 1223:talk 1208:talk 1154:talk 1087:talk 1074:talk 978:back 926:talk 921:Cirt 876:talk 863:talk 850:talk 821:talk 778:Ched 771:most 701:talk 697:Gigs 679:talk 658:talk 645:talk 613:talk 600:talk 580:talk 542:Ryan 506:talk 450:Ched 437:talk 424:some 413:talk 408:Cirt 359:talk 330:talk 317:talk 286:talk 271:Talk 254:talk 241:talk 213:Ryan 152:talk 139:Talk 106:talk 26:The 3765:for 3723:) ( 3702:DGG 3618:CBM 3540:too 3522:DGG 3267:DGG 3257:DGG 3049:) ( 3007:-- 2434:) ( 1978:Ray 1963:) ( 1890:DGG 1851:CBM 1824:-- 1316:CBM 1256:) ( 1235:DGG 4115:) 4111:· 4107:· 4068:) 4051:) 3986:) 3871:) 3860:. 3842:) 3793:) 3787:)( 3727:) 3709:) 3693:) 3679:) 3666:) 3652:) 3620:· 3608:) 3550:) 3529:) 3502:) 3437:? 3434:: 3322:) 3309:) 3274:) 3249:) 3225:) 3203:) 3189:) 3175:) 3162:) 3149:) 3079:) 3075:· 3071:· 3059:-- 3053:) 3036:) 3023:) 2960:NW 2928:) 2913:) 2891:) 2878:) 2865:) 2830:NW 2766:) 2746:) 2724:) 2706:) 2634:) 2609:) 2559:) 2527:) 2492:) 2464:) 2451:) 2438:) 2420:) 2402:? 2399:: 2381:) 2365:) 2350:) 2225:) 2190:) 2175:) 2142:• 2126:) 2107:? 2104:: 2090:) 2049:) 2034:) 1997:) 1967:) 1950:) 1924:) 1897:) 1872:) 1853:· 1840:) 1664:) 1648:() 1632:) 1607:) 1588:) 1555:) 1532:) 1506:) 1493:) 1434:) 1430:· 1426:· 1391:) 1378:) 1363:) 1350:) 1336:) 1318:· 1305:• 1299:• 1288:— 1278:() 1260:) 1242:) 1225:) 1210:) 1156:) 1103:: 1095:-- 1089:) 1076:) 928:) 878:) 865:) 852:) 829:-- 823:) 784:? 781:: 756:: 740:| 703:) 681:) 660:) 647:) 615:) 602:) 588:) 508:) 485:-- 456:? 453:: 445:— 439:) 415:) 398:| 361:) 332:) 319:) 288:) 264:NW 256:) 243:) 154:) 141:) 108:) 68:. 4103:( 4064:( 4059:☺ 4047:( 3982:( 3916:T 3908:3 3904:z 3900:2 3896:y 3892:1 3888:x 3867:( 3862:☺ 3838:( 3790:T 3784:C 3781:( 3719:( 3705:( 3689:( 3675:( 3662:( 3648:( 3637:☼ 3624:) 3616:( 3604:( 3596:( 3546:( 3525:( 3498:( 3413:/ 3403:— 3388:/ 3373:⚔ 3360:* 3318:( 3305:( 3300:☺ 3289:τ 3270:( 3260:( 3245:( 3221:( 3209:— 3199:( 3185:( 3171:( 3158:( 3145:( 3135:⚔ 3067:( 3045:( 3032:( 3019:( 2970:) 2964:( 2924:( 2909:( 2897:— 2887:( 2874:( 2861:( 2851:⚔ 2840:) 2834:( 2786:) 2762:( 2742:( 2720:( 2702:( 2630:( 2625:☺ 2605:( 2555:( 2523:( 2488:( 2460:( 2447:( 2430:( 2416:( 2377:( 2361:( 2346:( 2327:/ 2299:/ 2221:( 2186:( 2171:( 2146:) 2138:( 2133:— 2122:( 2086:( 2065:/ 2045:( 2030:( 2011:/ 1993:( 1959:( 1946:( 1920:( 1893:( 1868:( 1857:) 1849:( 1836:( 1660:( 1628:( 1603:( 1584:( 1551:( 1528:( 1516:⚔ 1502:( 1489:( 1477:* 1422:( 1387:( 1374:( 1359:( 1346:( 1332:( 1322:) 1314:( 1293:E 1252:( 1238:( 1221:( 1206:( 1152:( 1085:( 1072:( 924:( 874:( 861:( 848:( 838:) 834:( 819:( 814:☺ 803:τ 732:– 717:/ 699:( 687:— 677:( 656:( 643:( 630:* 611:( 598:( 583:· 578:( 567:] 558:⚔ 504:( 494:) 490:( 475:τ 435:( 411:( 390:– 375:/ 357:( 328:( 315:( 303:* 284:( 274:) 268:( 252:( 239:( 229:⚔ 150:( 137:( 104:(

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

Knowledge (XXG)

:Requests for comment/Content dispute resolution - Knowledge (XXG)

Index