Misplaced Pages

Revision as of 14:59, 20 April 2009

All editors are invited to examine the text and to provide any comments or suggestions they may have:

• General comments, or comments which quote passages from the text, may be made on this page.
• Comments on specific points in the text and changes to wording may be made here.

Last resort

Summary: Question on if it should it be stated the committee is not the final arbiter of content. Status quo is that the committee traditionally avoids content issues, but is not forbidden from taking them.

"To act as a decision-maker of last resort for Misplaced Pages disputes," - this needs to make clear that it is disputes about user behaviour and NOT content. The committee is not the final arbiter of content.--Scott Mac (Doc) 01:06, 9 April 2009 (UTC)

We do assist with disputes about policy and content by assisting the Community in finding ways to settle the dispute and on some occasions we say that the community decision needs to stick. So, we need to be careful with our wording so to not mislead about what falls in our scope. FloNight♥♥♥ 12:53, 10 April 2009 (UTC)

Actually it's only by custom that ArbCom don't resolve content issues, since it is technically within their formal remit:

• "The Committee reserve the right to hear or not hear any dispute, at their discretion" - policy
• "will primarily investigate interpersonal disputes" - policy

(Also note that until very recent years, most Requests for Arbitration were resolvable in principle, by addressing the conduct issue alone. A lot of the 2004-07 cases for example were "please help with this disruptive user" problems.)

FT2  12:00, 11 April 2009 (UTC)

Normal appointments

Summary: Suggestion of move from election results being advisory, to appointments according to election.

I propose changing "The members of the Committee shall be appointed by Jimbo Wales, in his role as project leader, following advisory elections whose format shall be decided by the community" to read "The members of the committee shall be appointed by Jimbo Wales, in his rôle as project leader, in accordance with the results of elections whose format shall be decided by the community". (changes boldes for clarity) DuncanHill (talk) 05:17, 9 April 2009 (UTC)

Up to now, Jimbo has used the results of the election to advice him about who to choose for the Committee. Since he has decided to expand the Committee, we've not had elections where people were running for specific seats. I think the original wording reflects what has happened in the past. FloNight♥♥♥ 13:01, 10 April 2009 (UTC)

It does reflect what has happened in the past, but it should reflect what should happen in the future. I see his rôle as developing into a more constitutional one, rather than an arbitrary one as it is now. DuncanHill (talk) 12:27, 20 April 2009 (UTC)

General Comments

I think this draft looks pretty good: it seems to follow the current practices very well. However, I am unclear exactly what changes are to be made... or is this just a clarification of existing policy? If that is not the case, perhaps a summary of significant changes would be useful to readers who aren't extremely intimate with Arbcom. bahamut0013_deeds 05:49, 9 April 2009 (UTC)

As you say, the draft follows current practices and tries to cover all current issues following the norms in place. The Arbitration Committee is in fact undergoing some structural adaptations which are set to be leveled with the the needs of a rapidly evolving encyclopedia that anyone can edit. This draft comes to lay down the general foundation of the adapted Arbitration system.

The adaptation process follows an agenda. In January 2009, the Committee has set up a noticeboard to keep the community informed of all its activities. The noticeboard serves for announcements of and statements made by the Arbitration Committee. Some of the newly implemented procedures have already been put in place. Starting April 2009, The Committee established a new new ban appeals subcommittee and procedure. Also, the Committee is actually implementing a new Arbitration case management system. From now on, the drafting of new opened cases will be assinged to in individual arbitrators while teamed with one or two more arbitrators to work proactively in cases. In the same area, the organization of Arbitration case pages will be shifted to a more flexible system of organization based on a new process and a newly formatted layout of the Workshop pages where importance is given to the proactivity of the Arbitrator(s), the active involvment of the participants through questions and answers and the empowerement of the Clercks to protect against disruption of the process. A deadline will also be fixed in agreement with the parties at the start of the process; though may be changed depending on the flow of the case. Note that this change is only in its experimental stage and a flexible guideline will be produced after the closure of a few cases. Also note that, individual or subgroup Arbitrators Arbitrators may still opt for they own preferred guidelines. So keep reviewing the ArbCom noticeboard to keep you informed. Thanks. -- FayssalF - 01:45, 10 April 2009 (UTC)

Ok, that summary helped a great deal. It makes me feel warm and fuzzy to see the Committee willing to be transparent. bahamut0013_deeds 13:43, 10 April 2009 (UTC)

Soooo many headings

Summary: Request to reduce number of headings.

The number of headings in this document is utterly excessive. Unlike legal documents, which this is somewhat simulating, we don't need to be able to reference each and every individual clause separately. Many of the headings can be combined and reduced; I'll do a diff. Happy‑melon 09:56, 9 April 2009 (UTC)

This would be a good start. Happy‑melon 10:06, 9 April 2009 (UTC)

We're aware of that, and many of the headings will likely be removed in a subsequent draft. At the moment, they're in place more for ease of commenting than anything else. Kirill  12:39, 9 April 2009 (UTC)

re; Expedited decisions and motions

Summary: Objection to allowing a simple majority to substitute expedited decision for a full hearing. Discussion of ways to ensure that a suitable decision making process is followed to decide when a case is expedited.

I suggest that simple majority is not the benchmark for the "substitution" for a full hearing (although it may suffice where the alternative to motion is a denied request), that a 51/49% split between Arbs is insufficient to satisfy the community that there isn't evidence that needs placing and reviewing in a full case. Perhaps a wording similar to "majority + 2" or "Nett 3 support" gives sufficient split without likelihood of opposes hamstringing this option? LessHeard vanU (talk) 13:11, 9 April 2009 (UTC)

How about "majority plus two or consent of those named in the request."? --Barberio (talk) 13:20, 9 April 2009 (UTC)

Named in the request or affected by the motion(s) in question? Since people are free to add themselves as parties, do we want to give everyone doing so the ability to affect this? Kirill  13:26, 9 April 2009 (UTC)

Since RfAR's are not brought with the intent of being superceded by motion (at least, I hope not) then the decision is best regarded as an internal one, but not one that should balance on one or two votes - I am looking for something between "overwhelming" and "simple" majority to make clear that a sizable percentage of the ArbCom believes motion/expedited is the best solution. LessHeard vanU (talk) 15:31, 9 April 2009 (UTC)

Things Missing

Summary: A request for and discussion of more explicit language on some functions related to appointments, and communication standards; changing 'Jimbo Wales' in the document to 'Misplaced Pages Project Leader'; and automatic acceptance of cases referred from the foundation. Foundation does not current refer cases, so last point is currently moot. Discussion that there might be a case for clarifying the relationship between Jimbgo Wales and the committee.

Here are a few things from the past discussions that I think had consensus which are missing from this draft,

1. Identifying the Arbcom's ability to make and vet appointments to various functions of en.wikipedia
2. Requirement to communicate clearly with the community.
3. Switching phrasing 'Jimbo Wales' to 'Misplaced Pages Project Leader'.
4. 'Recommend changes to policy' functions.
5. Automatic acceptance of cases referred from the foundation.

There may be other functional differences with the version at Misplaced Pages:Arbitration_policy_proposed_updating that should be reconciled. --Barberio (talk) 13:16, 9 April 2009 (UTC)

I think some of those are present, albeit not necessarily in the same form as in earlier drafts:

1. Present as point 4 under "Duties and responsibilities"; or are you looking to put more detail on the appointment process itself into the policy?
2. "Arbitrator conduct" and "Language of decisions" might be relevant here; or does that not cover it explicitly enough?
3. This is a constitutional issue somewhat beyond the arbitration policy; it's not really appropriate to do that unless some provision exists to have a leader other than Jimbo, which I don't believe is the case at the moment.
4. The second clause under "Scope of arbitration" addresses that to an extent. I'm not sure that mere recommendations outside of dispute scenarios need to be covered here; we can recommend policy, sure, but so can any other editor. Or did you mean something other than the normal proposal process?
5. That's probably a pretty moot point, since the WMF has never referred a case to us, and almost certainly wouldn't do so for legal reasons in any case.

Kirill  13:24, 9 April 2009 (UTC)

Generally, more detail on the appointment process would be good. For instance, can the community over-rule/veto an arbcom appointment?

Yes, there needs to be more explicit coverage of what behavior is expected, even if that's not strictly enforceable, it establishes a 'spirit of the law' for the rest of the policy.

The "recommended policy changes" text from the previous proposal is less a 'power' than it is an explicit restriction of how Arbcom or Arbcom Clerks should behave when editing policies, to prevent even the perception of policy by fiat. --Barberio (talk) 19:58, 9 April 2009 (UTC)

edit conflict with Kirill -- some points are duplicated

For #1, I think this is found in point #4 here.

For #2, is this what is needed? Or do you mean a more general need to communicate clearly with the community? It would be good, I think, to have such a commitment from the Committee.

For #3, I personally think that would be misleading. It is far from clear that, in Jimmy's absence, anyone would fill that role. There are several references to "in his capacity as project leader"; perhaps this could be cleared up with a section that explicitly defined the relationship between the Committee and Jimmy.

I don't think I've seen references to #4 or #5 before. To be honest, I can't imagine a circumstance where the Foundation would refer a case to the Committee (beyond their saying "no, we can't sort this for you; try these guys"). Having the Committee draft and corporately endorse changes to policy would, I think be an excellent idea (I have advocated it privately in the past).

] 13:38, 9 April 2009 (UTC)

I am also unsatisfied with the detail in discussing arbitrator conduct (I'd like some more adjectives: diplomatic, serious, diligent, mature maybe) and overall responsibilities (Block/ban reviews, OS/CU, Administrator conduct)--Tznkai (talk) 13:57, 9 April 2009 (UTC)

Jimbo

Summary: Should the policy no longer refer to Jimbo?

Has the comittee considered removing the Jimbo function from its charter? Hipocrite (talk) 13:35, 9 April 2009 (UTC)

While I'm somewhat sympathetic to this idea (build for a future without Jimbo, it will come eventually, if only due to natural causes) I think this would have the effect of provoking a constitutional crisis.--Tznkai (talk) 13:44, 9 April 2009 (UTC)

Only if the Jimbo figure opposed removing the Jimbo figure from the policy. Is that the case? Hipocrite (talk) 13:46, 9 April 2009 (UTC)

Considering he fights to keep titles on smaller projects he never edits, I think it can be assumed that he's not relinquishing the GodKing title without a fight. لennavecia 15:19, 9 April 2009 (UTC)

Hey, Jimbo's the guy who got this thing up and running, and stopped it going down really bad pathways. He has not allowed advertising. He's a good PR person. These are good reasons for not changing this aspect—not yet, anyway. There are far more urgent aspects to get right before his relationship with ArbCom and the project were ever challenged. Tony (talk) 15:39, 9 April 2009 (UTC)

I don't mind the policy referring to Jimbo, or to him having certain functions within the policy, but I do think that this should only be as formally given to him by the community. He will not be with us forever, and I think it is time that we learnt to stand on our own several million feet. DuncanHill (talk) 12:24, 20 April 2009 (UTC)

Duties and responsibilities

I would like to offer my thanks to whoever wrote this for their efforts. I do have one question. Duties and responsibilities #1 says "To act as a decision-maker of last resort for Misplaced Pages disputes, to determine which of these disputes are suitable for arbitration, and to carefully review and render binding decisions in those disputes;..." I hope I'm not starting anything here, but it seems to me as if by the phrasing it is being indicated that the ArbCom becomes the final authority short of Jimbo and the Foundation for all matters related to wikipedia. Personally, I would welcome having someone identified as the final authority, and there have been several discussions that basically didn't result in anything regarding the matter of "final authority" being vested somewhere, so I don't mind seeing that, but would like some clarification as to whether that is what it is intended to say. John Carter (talk) 13:38, 9 April 2009 (UTC)

Indeed, this is a major undertaking, and arbitrators and clerks who have contributed deserve thanks. Tony (talk) 15:59, 9 April 2009 (UTC)

Clerks

Summary: Explicitly identify Clerks as a group with delegated powers of maintenance in Arbitration project pages. Discussion on how the committee should relate with bureaucrats.

A narcissistic moment here: but the the clerks are referred to 4 different times, without an explanation once of what it is we do. It might be useful to put clerks within the overall category of "Delegation" which would also cover subcommittees and any other panels or groups ArbCom wants to put together - and mention those things in some detail. Much of this policy is vague and broad, and there are some odd pieces of specification.--Tznkai (talk) 14:03, 9 April 2009 (UTC)

The clerks' role does need to be spelled out in this policy, I believe. It's easier to comprehend, and the right thing to do for all parties. Tony (talk) 15:42, 9 April 2009 (UTC)

I just found it odd we were mentioned at all in the main policy.--Tznkai (talk) 20:21, 9 April 2009 (UTC)

We could, I suppose, avoid mentioning the clerks specifically and leave them as an unnamed group to which authority has been delegated; but, given the central role you guys play in the case procedures and the firmly established nature of the role, it seems appropriate to mention you explicitly at certain points. Kirill  00:14, 10 April 2009 (UTC)

It might be useful to put clerks within the overall category of "Delegation" which would also cover subcommittees and any other panels or groups ArbCom wants to put together... I agree. -- FayssalF - 04:20, 10 April 2009 (UTC)

The Clerks' role needs to be explicated in a very public place. At least, certain things about their role. The ArbCom policy can't properly be revised without revising the policy that governs the roles and responsibilities of the clerks. Probably one separate section is require; it doesn't have to be long. Tony (talk) 16:20, 11 April 2009 (UTC)

I agree that a section detailing the role of the clerks would help. But there are other groups that ArbCom (or at least this current ArbCom) co-ordinate with. Off the top of my head, we have the functionaries (former arbs, checkusers and oversighters), various foundation people (mainly Jimmy and Cary Bass), and sometimes checkuser and oversight people on other WMF wikis (though not that often). If the role of the clerks is being explicitly laid out, maybe some of these other relationships could also be made more explicit? Oh, sometimes stewards as well (when emergency desysops take place) and sometimes bureaucrats. That last one is interesting: the relationship between ArbCom and bureaucrats has never really been clearly laid out in my view - maybe because the roles shouldn't really ever interact that much - but it has come up in relation to bureaucrats declining requests for resysopping. The relationship between ArbCom and community processes like RFA also came up recently, and is often discussed in relation to desysopped admins and where resysop applications should be made: ArbCom, bureaucrats or RFA? Carcharoth (talk) 16:48, 12 April 2009 (UTC)

Doubts

I don't suppose I'll have much effect by writing this, but I'll take the opportunity to point out what I think is fundamentally wrong with the arbitration setup.

1. If you're primarily dealing with conduct (not content) disputes, then (to use a legal metaphor) you're a criminal court, not a civil court. In fact, since bad conduct is dealt with in the first instance by admins, you're a criminal appeal court. The parties in your cases should be appellant and appellee - the editor who feels he's been wrongly treated, and the admin who so treated him. No need for any more drama or legal posturing than just talking to those parties, deciding whether the admin's action was right, and taking appropriate corrective action. You certainly shouldn't be encouraging editors to debate at length about each others' conduct - this is just the sort of discussion that (deliberately or otherwise) derails the important process of reaching consensus on content matters. Of course, editors should be very concerned about incivility and other bad behaviour, as this will destroy our community if unchecked, but that doesn't mean we should all be encouraged to take on the role of prosecutor.
2. You would have much more value as an institution, however, if you did take on content disputes in some meaningful way. These are the ones that matter - we're writing an encyclopedia, remember, and it's the content of that encyclopedia (and, secondarily, of the guidance given to those writing it) that ultimately matters to all of us. Of course, if we had an effective means of resolving such disputes, then we would need no help from ArbCom. But of course we don't - OK, most disputes go away, usually with the right result, but not always - and the serious conduct disputes arise precisely because we don't have a means of settling content disputes properly. Bad conduct would happen much less if it weren't rewarded in terms of getting what you're arguing for. But under the current system, it very often is rewarded, because in practice, it's the most effective edit-warriors and bullies who get their way if they're determined enough. ArbCom should be part of, or at least encourage the institution of, a system for determining, based on rational and civilized discussion, what the community's view is on a given content matter and for enforcing that view on those occasions when there are still people who disagree strongly with it.
3. All right, I could go on, but I'll stop. Please think about it.--Kotniski (talk) 14:12, 9 April 2009 (UTC)

Erm, Criminal courts deal with crimes against the People (or the Crown, or the State) and civil courts deal with controversies between individuals, with enforced resolution by an outside entity. Arbcom covers both. It has universal original and appellate jurisdictions - and there is very often more than two groups of adversaries. I agree that our current "evidence" proceedings can, and do descend into a free-for-all attack though. As for this thing on conduct versus content, thats part of a larger argument best served elsewhere, but I will make the claim that a normalized, civil editing environment is the most efficient context for good article writing.--Tznkai (talk) 14:17, 9 April 2009 (UTC)

I agree strongly with your last statement, and for that reason, bad conduct is a crime against the People (possibly with a specific victim as well). But with real crimes, that victim (or other bystander) doesn't generally arrest or prosecute the perpetrator. On WP, if editors see bad behaviour, and gentle warnings don't help, they should be encouraged to report it to the admins and expect action to be taken. It's only if an administrator's action is questioned that we need ArbCom - the fact that you get cases that are more complicated is probably due to failure to require that complaints about conduct be specific and be addressed to administrators in the first instance. And I don't understand why the "larger" argument should take place elsewhere - where did you have in mind? --Kotniski (talk) 15:07, 9 April 2009 (UTC)

On this language issue, I want us to be very very very clear... ArbCom is not in any way a 'civil court' or a 'criminal court', Misplaced Pages is in no position to impose bailiff enforced fines or custodial sentencing. It is Misplaced Pages's internal Tribunal, who's powers against a person are limited at most to removing them from the project.

I'd probably suggest that we should consider renaming at some point from 'Arbitration' to 'Tribunal', to try and correct the terminology issue. --Barberio (talk) 20:19, 9 April 2009 (UTC)

I believe that Kotniski is raising issues that need to be talked through.

Adding content disputes would be a major change. I have specific questions on this. Can arbs/clerks explain here the original/continuing reasons for the restricting of the scope to behavioural issues alone? Is it a perception that the community should sort content out, always? Is it a fear that ArbCom might be swamped with work, or with cases that are highly political and difficult to rule on?

One major problem in the current scope is that it's often difficult to separate behavioural from content issues. The latter can keep festering as the source of the tension between editors. Tony (talk) 15:56, 9 April 2009 (UTC)

I will give my best apologia for the standing restriction of scope:

A fundamental part of the wiki process, is that in content matters all editors are equal. As rational creatures, we should be able to come to an agreement (that is, consensus) through reasoned argument between editors. The best argument, the best content, wins on its own.Not only is this a philosophy we abide by, but it is as a practical matter, one of the few ways we have to quickly generate neutral writing on a wide variety of topics - with the input of as many voices as possible. When this process fails, it is because of behavioral issues. Civility issues clouding editorial judgment, users unwilling to participate in reasoned debate, bad faith users, trolls, vandals, and others who do not wish to act like rational creatures benefiting the project. That is, those who disrupt the editing environment. By eliminating those users from the editing environment, the editing environment should return to normal.

In addition there is no group of editors, certainly not the Arbitration Committee which is qualified to make judgements on all content matters - perhaps not any content matters. Human knowledge, which Misplaced Pages tries to capture, is far larger than any one, or any small group of humans could hope to manage. It is in fact, such a large topic, that it takes a project like Misplaced Pages to generate that much data that quickly. Our own success limits the ability of any one body to successfully control it. For example, there is no way, however laudable it would be, to create a unified "voice" for Misplaced Pages, a distinctive writing style, because there is far to much writing for any group to unify. Creating multiple content bodies would create either a useless and overwhelmed bureaucracy, or a high functioning but extremely slow bureaucracy.

Behavior problems, by comparison, are pretty simple. Most of us, most of the time, recognize when someone is being a jerk, especially when we're not involved. The Arbitration Committee then, is a collection of people who are responsible, mature, sensible and most importantly distant from the problems at hand. They are able to view it as an outsider, and sort it out.

Thus, the wiki process is best served, and perhaps can only be served, by a group focused on behavioral problems. While we have seen complexity rise that puts the model I've described in question (the fuzzy line between bad behavior and advocating for "wrong" content) certain fundamental truths have not changed. The amount of legitimate disagreement has not gone down, (perhaps our patience to admit the legitimacy of the opposition has though), the sheer breadth of content has not decreased, and the value of a normalized editing environment is still paramount. What has arisen then, are not examples that invalidate the Committee's underlying theory, but exceptions that need to be adjusted for.--Tznkai (talk) 20:20, 9 April 2009 (UTC)

I think we agree in principle with all that, but sometimes the facts on the ground fail to live up to the ideal. For me, it breaks down when you say "the best argument, the best content wins on its own". Yes, in 99.9% of cases, Just as in 99.9% of cases of behavioural problems the right result is achieved through the normal processes of peer pressure and admin action. It's only because of the exceptional cases that we need ArbCom at all. And in practice, the way we do things at the moment, the exceptional cases tend to be mixtures of content and conduct disputes all rolled in together, feeding off each other and disenfranchising the reasonable editors who aren't interested in fighting.

Rather than go on complaining, I'll just set down my proposed model in a new thread (below).--Kotniski (talk) 07:20, 10 April 2009 (UTC)

Tznkai: thanks for your detailed explanation, which does present a reasonable case for the behavioural-only practice. However, a few things remain: if all behavioural cases were "easy to recognise", why is ArbCom necessary? And what of behavioural issues that arise from unresolved content issues that are seemingly intractable without authoritative decision-making? And ArbCom can, as pointed out above, deal with content issues at its discretion (but this needs to be defined a little more closely). Tony (talk) 16:30, 11 April 2009 (UTC)

To butcher a U.S Supreme court Justice's statement: "ArbCom is not final because they are necessary , they are necessary because they are final." What it really comes down to is that sometimes you need a body at the end of the road to take the responsibility to make a bold and definitive decision, because people get unreasonable and stubborn. As for content-originated and other intractable disputes? They're a serious problem (as I have commented elsewhere) and tend to be genuinely difficult to solve. I'm not convinced however, that unshackling ArbCom to make content decisions is a good solution. The current structure of Arbitration cases invite more bickering in these disputes, not less, and in no meaningful way illuminate on the underlying content issue, and we still have the problems I pointed out above, namely that I'm not sure I trust any group of users to dictate a content decision, let alone a body that was elected to do something else. Of note, the body that does deal with content decisions, WP:MEDCOM, is often avoided or actively sabotaged by participants. I agree there is a serious problem, but I don't think the solution is within arbcom expanding its scope. I have made some fairly radical suggestions elsewhere, but I think there are also some very simple ones. All of these however, involve encouraging arbcom to be more aggressive, and that is usually met with significant resistance.--Tznkai (talk) 18:34, 19 April 2009 (UTC)

A model for dispute resolution

This is my basic model, which I suspect is far too simple and rational ever to be accepted at WP, but one never knows... The principles would be something like this ("admins" may be extended to include other neutral and respected editors):

1. Disagreements over content are decided by good-natured reasoned discussion.
2. Disagreements over what has been decided in reasoned discussion are resolved by neutral admins. (This isn't a fundamentally new concept - it just extends what already happens at AfD etc.; and doesn't require the admins to have specialist knowledge, just to recognize a cogent argument.)
3. Complaints about conduct (if a polite peer-to-peer remark isn't sufficient) are made to the admins, who take appropriate action. Unacceptable conduct includes disrupting the process of good-natured reasoned discussion (per 1) and editing contrary to what has been decided in reasoned discussion (per 2).
4. Complaints about admins' acts or omissions are made to the wider body of admins, and if still unresolved, to ArbCom.
5. Administrators' and arbitrators' rulings (where not obvious) should be preceded by focused and mutually respectful discussion with those involved, to ensure that all arguments have been noted and understood.

Details to be filled in of course, but honestly, wouldn't this be a far better and clearer basis to start from?--Kotniski (talk) 07:17, 10 April 2009 (UTC)

• I'm not sure where to reply, because I have issues with what you say in the section above this one, but you've sort of closed that down to move here. My first issue is that arb-com isn't a court, it is an arbitration committee. It's meant to arbitrate. Where I think arbitration has failed is that it doesn't tend to arbitrate anymore. If it worked along the lines of an actual arbitration body, limiting itself to issues of behaviour, and provided a final, binding decision, then maybe things would move a little better on Misplaced Pages. For starters, if arb-com better enforced our policies and guidance on civility, we wouldn't be in half the mess we are, because everyone would have to speak on a level playing field. Similarly, if it upheld the idea of consensus, half the issues we have would quickly be resolved. How do I mean? Well for me, if I have a dispute with someone, I'll try and settle it by building consensus or discussion. And when that fails, I try and get a wider input, to get a decision made, one way or the other. Just so we can have it done and dusted for the time being and all go do something less boring instead. That's how Misplaced Pages is supposed to work. It doesn't always work like that though. Sometimes things get a little awry, and I'm as guilty of that as the next person. But that's where WP:DR and arbitration come in. If you've got a behavioural dispute, where two sides are breaching 3RR or edit warring, or whatever the behaviour may be, that's where arbitration has got to step in. And we've limited arbitration to behaviour, so for me, it's quite simple. Arbitration should just call out bad behaviour, and deal with those committing it. And if it is at arbitration, then that call out is the final call out. So "kick them out of the game". If they can't build consensus period, bye bye. If they can't build consensus on a specific issue, then they don't get a say on that issue. For me, it's that simple. Our consensus making policy should actually resolve most of the disputes we ever have here, because it ultimately means that the side with the most people dedicated to seeing the issue to a finish will get the "final say". The trouble starts when the side in the minority refuses to recognise that. And that's when arbitration kicks in, because part of consensus policy is that you have to compromise. Someone not compromising is not building a consensus. So you can see people who refuse to compromise will end up on the smaller side at the end of a dispute, because people will have eventually compromised by dropping out of the dispute. That's how it should work. That's the framework of decision-making on Misplaced Pages. There's a handy flow-chart at File:Consensus_Flowchart.svg that delineates it. That's my take on it, anyway. Hiding T 12:05, 10 April 2009 (UTC)

• The one question that comes to mind for me is when we have intractable, entrenched, partisan arguments, when basically the only people consistently involved are those who are least rational and reasonable. I too think that in such cases policies or guidelines could be written to deal with them, but then what will probably happen is that the same intractable partisans who were arguing before will continue to argue, saying the other side is at fault. I agree that ArbCom should be primarily an arbitrating body. However, there are, admittedly rare, situations in which more is needed. Individual admins could conceivably step in and act according to rules in such cases, but in the more contentious fights there will already be admins probably on both sides, making it harder to know what to do. For situations such as these, when the community makes it clear that for whatever reason it cannot or will not act to resolve a matter which seemingly needs to be resolved somehow, I can see ArbCom perhaps not dealing with it directly, but maybe helping create a body of experienced, reputable editors who can review it and arrive at a fair solution. Like I said, these situations aren't that common. However, the longer we continue to not have an effective way to deal with them, the more common they will become, and the more difficulty there will be in resolving them. John Carter (talk) 13:17, 10 April 2009 (UTC)

• When we have intractable, entrenched, partisan arguments, we have people in breach of WP:NPOV. What more do we need to know? It really is that simple. Hiding T 13:49, 10 April 2009 (UTC)

Agreed. So, in those cases, everybody involved is in violation of POV. What do we do, block or ban the lot of them from given content? What does that do the content? Particularly, what if they're the ones developing the content in the first place? This happens, particularly with things like the 9/11 conspiracy theories and the like, or when they're the ones most familiar with the content so that they would have the best of idea of WP:DUE and the like. Yes, in an ideal world, we would have enough community-minded individuals willing to undergo virtual torture to deal with raving loons on both sides. That don't happen that often though. And, of course, if an outsider were to consistently oppose one side or the other, possibly because they're, well, wrong, that side will now consider the outsider a partisan for the other side and begin to ignore any input from them. We could virtually permanently lock the content in dispute, but that's generally something we try to avoid. And, in some cases, even if we did, the only thing that would happen would be that, as soon as the block is lifted, the edit wars start over again, from the same people doing the same things.

I myself don't see it as an ideal solution, but I'd rather have a way to bring these arguments to a clear conclusion or cessation pending definitive outside input than have edit wars going on for a number of years, potentially costing us some of our best editors when they find themselves in a minority position or such. And, yes, if we don't like the "interim measures", that gives us all the more reason to try to resolve them some other way more quickly. John Carter (talk) 14:07, 10 April 2009 (UTC)

You've lost me. At what point are partisan people the right people to adjudge WP:UNDUE? Only people who do not take a partisan approach cen determine what is due weight. Yes, people should be blocked and topic banned, that's the only way you'll get a consensus on the issue, that's how consensus is supposed to work, how Misplaced Pages is supposed to work. That's the well from which everything springs. Hiding T 14:26, 10 April 2009 (UTC)

I was actually thinking of undue weight within a given article, like say how much of a central article to devote to a given conspiracy theory, for instance. But, if we did the blocks or topic bans like things should work, particularly on the more contentious subjects, we run the risk of basically losing that content, either through vandalism which takes place after all the regulars have been "kicked off" the page or simple lack of updating. I agree it's the way wikipedia is supposed to work. But with almost 3 million articles now, most of us, including maybe you, are really just barely able to keep up with the things we are most interested in, and unfortunately sometimes willing to leave the other stuff to the hypothetical others who care about that. But if those others have all been blocked or banned from that content, there's nothing they can do either. And we can't force people to take an interest in and be willing to work on stuff they're not really interested in. I wish, but we can't. How often does it happen that important content becomes damaged through lack of interest? I honestly don't know. But I can see how it easily could happen fairly frequently. And maybe to prevent that, in those rare cases when it's the only way to do so, allowing ArbCom to maybe step over the line of arbritration for a while and make "interim declarations" or whatever you want to call it to preserve the work that's already been done on some subject might be acceptable. But, yes, we would want it as rarely and for as short a time as possible in each instance. John Carter (talk) 14:46, 10 April 2009 (UTC)

I'm not following you at all. I reject your model, but if I do follow it, then I'd opt for the lesser evil, which is a poor article, than having a poor article people argue over. But where I reject your model is at the start. Someone who can adjudge how much of an article to give to a given conspiracy theory is not someone likely to get blocked or content banned, are they? Basically, if everyone followed the policies, we'd have no problem. And if everyone who wanted what was best for Misplaced Pages followed the processes, we'd have no problem either, because at that point anyone not following the processes is easily identified as not wanting what is best for Misplaced Pages. So if we start acting like that, we actually start supporting those editors you think would get topic banned. Hiding T 15:00, 10 April 2009 (UTC)

I understand your position. But there will be cases when an article has been good, maybe even recognized, and then the circumstances of the world or whatever change and new content has to be added. I'm thinking of the Ireland naming mentioned earlier, very inflammatory new published allegations regarding a person or subject, or any case where there is a hotly contested new issue regarding a given subject. That issue may not be all-important to the article, but it might be all-important to those editors at that time, for however long the issue hangs around. The rest of the article might be in good, maybe very good, shape. And the new controversy might only affect a piece of it, but be almost constant. If there are "sides" to those controversies, and there often are, they might be comparatively unbending. I'm told some of the Israel-Palestine articles, and other material on contentious issues, is like this, where there are editors who want to make the content fair and balanced on both sides, but both sides reject the sources of the other as unreliable. And, to an extent, in some cases, they're both somewhat right about that, but they might be the only sources we've got. And in these issues in particular, when personal issues also often figure in, it can be very hard to be really objective about the material submitted from the "other side". Yes, we've got a noticeboard for issues like this, but I know of a few very good editors who have been blocked or banned from helping the content anyway. Personally, I'd rather have some less than perfect interim rules with a few more very good, but less than perfect, editors still able to edit, than better rules and fewer good editors. But I can see how others might think differently. John Carter (talk) 15:14, 10 April 2009 (UTC)

I can't see how this problem would not be solved through correct application of WP:BRD and WP:DR. Hiding T 15:35, 10 April 2009 (UTC)

I maybe have less experience of these major conflicts than most people here, but I really don't see how it's better to let something go on and on spiralling out of control, and have a committee attempt to "rule" on it some long way down the line, than have admins take control of the situation early on, as soon as it becomes clear that there are enough belligerents around to thwart civil discussion, or where it's clear that those involved in the discussion are not going to be able to agree for themselves what conclusions that discussion has led to (this is perhaps the key point that people usually don't get - I've been saying it all through the date linking thing - if we're going to say that consensus rules, then we must have a convergent process for deciding what consensus is - just like we already do reasonably successfully at AfD). If we laid down clear principles that would be applied on an ongoing basis, like the ones I've tried to formulate above, and the existing (theoretically) ones others have referred to, then ArbCom's role would be much clearer and the cases it hears much more focused - basically they would be reviewing specific administrative actions (or possibly inactions). The first place anyone (particularly bystanders) should take any complaint about behaviour should be the appropriate admin noticeboard, and admins must act decisively (I don't mean block without warning, but talk tough) to rein it in straight away. I may be missing something, but I see no other role for ArbCom than the important one of a final reviewer of admins' and other officials' actions. It doesn't need to create ("interpret") new policy - that could be done the community without any help if we could be sure that a consensus-forming and -enforcement process existed and would not be allowed to be derailed. Happy Easter everyone, --Kotniski (talk) 17:08, 10 April 2009 (UTC)

It's not better to let something spiral out of control, and that's been my point to John Carter all along. I've always maintained if everyone stayed within the bounds of behavioural policies, it would be easier to work out who is causing problems, because they'd break cover immediately. Hiding T 18:57, 10 April 2009 (UTC)

And, for the most part, I agree with you. My points of disagreement are (1) while I agree with you regarding future problems, your solution goes no way toward addressing current ones that somehow have come into existence despite the best efforts of many people, (2) even when many people are behaving well and some are not, there can be a situation where the person(s) misbehaving may in some way be immune from any sort of sanction or those who could impose one, for whatever reason, choose not to do so, and (3) unfortunately, in several cases, once it gets to outsider intervention, the outsider might face the problem of sanctioning most or all the parties involved, for the occasional "slips" they may have made since the disagreement began. In such cases, the only people who might be able to intervene fairly are the ArbCom, but, as we know, sometimes it can take a while for a decision to come down, which can exacerbate the situation itself.

In short, while I agree that I would prefer seeing what Hiding proposes, I think that realistically if we chose that option as the sole tactic we would, regretably, still see many of the same problems we see today. And those sorts of problems, which develop over time and involve several editors, are generally the most difficult to resolve. Maybe, in those cases, it might be better to have a bandage placed on the problem quickly, and actively seek to create a more permanent solution immediately. Of course, even then, when new policies and guidelines are proposed to deal with specific problems that have arisen, it often happens that they are not approved because people either aren't interested or think that even a limited new guideline would be misused. Then we're right back where we started again. John Carter (talk) 19:32, 10 April 2009 (UTC)

I'm not really sure what you're saying. We don;t really need any new behavioural policy, we have all we need. What we need is to actually apply it. Too many times we kind of let people off the hook because, well, we just do. If we stuck to our guns and simply held to the fact that you don;t disrupt Misplaced Pages to prove a point, and recognised that consensus means that ultimately, the majority view does decide, there are no issues. Any dispute, active right now, can be settled with recourse to appropriate policy right now. There's just very little will to do so, and there's very little authority left on Misplaced Pages to be able to do so. It's very hard to make a block against an established user stick now, and it's very hard to get a consensus established now. There's just no will to recognise anti-consensus actions for what they are any more. Even this discussion proves that. Hiding T 16:14, 13 April 2009 (UTC)

Executive summary of the major changes?

That would make community input so much easier and more effective. Did anyone think of doing this, or are the changes so great as to make that not useful? Tony (talk) 15:58, 9 April 2009 (UTC)

I second the motion. Looie496 (talk) 19:14, 9 April 2009 (UTC)

I can try to put a list of the most salient changes; but, overall, the changes from the current policy are so substantial as to make a comprehensive list infeasible. (A list of changes from the earlier drafts would be much easier to construct; but I don't think that's what you're asking for, is it?) Kirill  00:17, 10 April 2009 (UTC)

For my part, a list of the most salient changes would help, so I don't have to do a point-by-point comparison to figure out what the important changes are. Looie496 (talk) 00:21, 10 April 2009 (UTC)

Okay, I'll work on that once I finish some of the other paperwork I have this evening. :-) Kirill  00:24, 10 April 2009 (UTC)

Here's a list of some of the major items in the draft that aren't present in the current policy:

• Arbitrator appointment and removal
• Establishing interim measures until consensus forms
• Not ruling on content disputes
• Expedited hearings
• Private hearings
• Right to respond to cases
• Departure and resignation during cases
• Evidence from outside sources
• Private submission of evidence
• Amendments to the policy

This certainly isn't an exhaustive list, and I'll probably add more detail if/when I have the time to go through and do a clause-by-clause comparison; but it should be enough for people to comment on. Kirill  03:15, 10 April 2009 (UTC)

Most of those appear to be what ArbCom is presently doing. Are there any changes from present practice? Septentrionalis PMAnderson 18:42, 10 April 2009 (UTC)

The only significant changes from nominal current practice that I can think of are the restrictions on the purposes for which evidence from outside sources can be used, and the explicit recognition of a right to respond. The other stuff is mostly either formalization of existing practice (e.g. departure and resignation rules) or contingency cases that haven't actually occurred (e.g. arbitrator suspension and removal). Kirill  02:11, 11 April 2009 (UTC)

Timeliness

The previous discussions also had support for 'timeliness' requirements. As I've stated elsewhere tho, I think it might be unwise to put those in at the same time as making substantial other changes, since we don't and can't know how the work flow will settle out till after the new system has been running long enough to be 'normal'.

So I'm going to recommended again that we hold off on 'timeliness' and 'fast track' alterations till at least the end of the year. --Barberio (talk) 20:11, 9 April 2009 (UTC)

I'm not convinced that the precise details of case scheduling need to be spelled out at the policy level in any case (beyond the nominal minimum period for responses); and, given some of the other reforms to case handling that we're moving on, this may become somewhat of a moot point. Kirill  00:19, 10 April 2009 (UTC)

Confidentiality

Summary: Request that accepted conduct in handling confidential evidence should be outlined in the conduct section.

I may be missing this somewhere else, but I think the arbitrator conduct section should outline how arbs are expected to treat confidential information. And maybe elsewhere outline what kind of correspondence with ArbCom or arbtrators should or should not be assumed confidential.--BirgitteSB 20:35, 9 April 2009 (UTC)

Agreed. Some common sense is needed, but I would support moving to a system where material sent to arb-l is not considered automatically confidential, but that people sending in confidential information should mark it as such. The current system, where people send in stuff and we have to say "sorry, that's not confidential, please post it on the case evidence pages" does work to an extent, but I would prefer it if people e-mailing arb-l said explicitly "this is confidential". One obvious case is people e-mailing us under their real names. People do rightly assume that this is confidential, but in some cases we have to pass e-mails to others to help us resolve particular cases, and things get held up as we ask for permission to do this. Sometimes, people say "no, please don't pass this e-mail to XYZ", which is fair enough. But if XYZ has had allegations made against them, then we have to summarise what has been said. Those are just two examples. Checkuser cases are even more complex in terms if privacy and confidentiality. Carcharoth (talk) 16:40, 12 April 2009 (UTC)

Exclusivity

It might be worth noting that ArbCom (currently) has nearly exclusive jurisdiction over certain things: CU/OS, non-emergency, admin desysop, I'm certain I am forgetting many things.--Tznkai (talk) 20:50, 9 April 2009 (UTC)

Scope of arbitration

In exceptional cases of communal division or exceptional risk of harm to the project, the Committee may determine a interim means to achieve the aims of communal policies or to curtail dispute in the area, until the community has developed a better consensus.

I'm having a dense moment, but for the life of me I have no idea what this means. I can grope towards something like if the crap hits the fan, we have the right to try and pull a rabbit out of a hat, but that's no basis for scope, and that's not really within arb scope anyway. Or is it? Hiding T 11:31, 10 April 2009 (UTC)

Doesn't it mean things like temporary injuctions, like I understand has been imposed in the date linking saga?--Kotniski (talk) 11:44, 10 April 2009 (UTC)

I don't know, that's why I am asking. I haven't really followed the date linking saga. It's one of those tiresome issues where a decision is needed but is being filibustered. The way I look at it, if you allowed everyone to act within policy over the issue, auto-formatting would be deprecated, because if no-one breaches WP:3RR then they'd be removed from articles based on weight of numbers. Sometimes it is that simple, once you reduce policy down to their actual intent. That's why policy cruft has been the biggest barrier to getting things done on Misplaced Pages. And my god, am I sorry for the part I've played in crufting them up. Hiding T 12:11, 10 April 2009 (UTC)

This is actually more spurred by things like the Ireland naming dispute and so forth, but date delinking is another example. Basically, if the community can't agree on a policy, we're not going to impose one by fiat; but we will, essentially, pick an approach to be used in the interim until a policy emerges, to try and limit the spread of the conflict.

For example, if there's a fight over the meaning of a deletion criterion, and the community is having trouble coming to a consensus, we'd say something like "until the community decides otherwise, administrators should interpret the criterion as meaning 'X'".

Currently, we try to do this by using temporary injunctions, but those only last for the duration of the case—meaning that we have to keep the case open for them to have any effect—and are really supposed to apply only to the parties to the case itself. The idea here is to make it explicitly permissible for us to issue a temporary ruling in an active dispute without having to leave a case sitting open in the meantime. Kirill  12:40, 10 April 2009 (UTC)

I'm not sure I agree with this then. I'd hate for arb-com to start deciding how policy should be interpreted. I'm not sure I see why this is necessary either. There are plenty of other tools within the arbitration box to take this forwards. Surely there would be a distinction between good faith efforts to resolve the issue and bad faith efforts, that would be evinced through evidence. I've looked at Misplaced Pages:Requests for arbitration/Ireland article names but no temporary injunction is listed. What have I missed? Hiding T 13:11, 10 April 2009 (UTC)

The "No moves pending discussion" remedy is the most obvious; but the "Back-up procedure" and "Binding resolution" remedies are also applicable here. Basically, the entire outcome of the case was a temporary ruling pending the community coming up with a permanent one. Kirill  13:17, 10 April 2009 (UTC)

<edit conflict> "No moves pending discussion" would already lead back to WP:CONSENSUS, WP:BRD and move policy, wouldn't it? "Back-up procedure" is simply implementing WP:DR. I'm staggered at "Binding resolution". I need time to build a suitable response to that. My initial reaction is one of horror. Hiding T 13:38, 10 April 2009 (UTC)

• I can't work out a way in which I could support a solution such as "Binding resolution". My apologies. That's crossed the line for me. Hiding T 13:54, 10 April 2009 (UTC)

• It certainly is something that we would not use except as an absolute last resort. This ruling is an example of why that we need to have the ability to do when there is no other way to end a dispute that the Committee and the Community agree needs to end. FloNight♥♥♥ 14:14, 10 April 2009 (UTC)

• Then I guess I oppose it as vehemently as I can, for whatever that is worth. My sincere apologies. I can't support something that allows arb-com the right to make such decisions. I appreciate what you are trying to do, but I don't think Arb-com has or should be able to have the right to limit the actions of the entire community. I think you agree with me, judging by your comments when the decision was proposed. Hiding T 14:33, 10 April 2009 (UTC)

Hiding, in some ways what the Committee does is similar to an admin protecting an article. An admin looks at the article closely enough to make sure that we are not protecting it with a major policy violation like a blatant copyright violation, vandalism, or obvious defamation. But other than that, an admin does not choose which wording of the article to use, instead, they protect in the form that they see without making a decision about the content dispute. When the Committee acts in policy or content dispute we are interested in halting the active reverting or other conduct that is making the situation absolutely unacceptable, and assist in the ways that be can to help the Community find a solution to the dispute, and if necessary use our ruling to make it stick. So, we dig into the dispute slightly so we understand the nature of the conflict and what needs to happen to get a stable result. But we are not interested in making a decision on the actual dispute. We are interested in finding a process that will bring an end to the conflict. For small issue we will not get involved at all. But if the conflict covers a large number of articles, then something needs to happen to assist in bringing stability to the articles. FloNight♥♥♥ 13:34, 10 April 2009 (UTC)

I'm not sure what you are responding to here. Hiding T 13:47, 10 April 2009 (UTC)

A general response to all your comments in this thread. You didn't seem to understand the reasoning behind our decision to get involved, our method of intervening to solve the dispute. FloNight♥♥♥ 14:11, 10 April 2009 (UTC)

I think we are talking at cross purposes. I don't understand the language in this injunction, nor what it means. But I don't disagree with what you have written, so maybe I should try another tack. Why is this addition necessary? What will it allow that isn't currently allowed? Hiding T 14:16, 10 April 2009 (UTC)

Your questions and concerns are understandable. I don't have time at the moment to give as complete a reply as this needs, so I'll get back to it later. I do want to explain as best I can, but need to do a few other things related to case work first. FloNight♥♥♥ 17:39, 10 April 2009 (UTC)

No problem. Hiding T 18:59, 10 April 2009 (UTC)

Possible "full disclosure" clause

Part of the problem with arbitrations is that editors tend to give very partisan evidence, and actively conceal important evidence that may hurt their case. It would be helpful if they were required to provide full facts, even stuff fatal to their case, as a way of moving things along.  Roger Davies 14:04, 10 April 2009 (UTC)

Exactly how are we going to enforce this? In the U.S the analogous structure is that the prosecution must reveal all pertinent facts to the defendant (in the interests of justice) and both sides have certain obligations to announce and prepare each opposing side with certain information. We don't have prosecutors and lawyers, we don't have the power to hold people in contempt of court, and we can't disbar people for misconduct. I mean, it'd be awesome if people were expected to treat arbitration with the same attitude they are supposed to approach articles ( and even better if they did so), but specific behavioral injunctions/requirements such as this beg to be enforced - and I don't see a good way to do it. --Tznkai (talk) 15:38, 10 April 2009 (UTC)

This is a difficult question. The Committee has often found itself having to dig up a significant amount of the relevant evidence on its own in order to make a fair decision that reflects the needs of the encyclopedia and the community. Ideally, that evidence would best be developed by neutral third parties; when this happens, I believe the decision is often better balanced and can be more timely as well. Risker (talk) 16:14, 10 April 2009 (UTC)

That would be delightful - but how to incentivize these 3rd parties to actually show up?--Tznkai (talk) 16:30, 10 April 2009 (UTC)

Incentivize? I presume you mean "what incentive can be provided to neutral third parties to develop evidence?" I don't have a good answer to this question. I know that several current members of the committee have done this before their tenure; from what I recall, their motivation was genuine curiosity at what the results would be. Evidence is a lot more useful in crafting good decisions than, say, extensive discussion of a fairly subjective evidence submission, or proposing findings based on such limited evidence. Risker (talk) 16:41, 10 April 2009 (UTC)

For whatever reason, there are usually more statements than people providing evidence, so interest in commenting on the case doesn't correlate well with providing evidence. Who knows? Maybe simply establishing that neutral evidence is welcomed will help.--Tznkai (talk) 17:13, 10 April 2009 (UTC)

It would suffice if editors approached articles with the attitude that they are supposed to use in approaching articles. But they don't. Septentrionalis PMAnderson 18:45, 10 April 2009 (UTC)

Given that we are often dealing with angry people that dislike each other and hold strong points of view, I think that the involved parties think that they are giving a fair telling of the facts. At least that has always been my impression. FloNight♥♥♥ 16:45, 10 April 2009 (UTC)

Anyone has the right to say 'I forgot that', 'I am sorry, I missed those evidences' or 'I didn't believe that would be considered as an evidence of something', etc... That'd be moot. -- FayssalF - 17:02, 10 April 2009 (UTC)

I think that the previous attempts at dispute resolution will be the only venues where there is a hope of third parties having looked neutrally at all the evidence (RfC, Third Opinion and the Noticeboards) - by the time it has got to RfAR the positions are entrenched. I think this is adequately covered by the requirement for there to have been previous attempts, since these histories can be reviewed. Further, by the time a dispute gets to ArbCom it has usually been distilled into the pertinent policy violations and there is no need to see what collateral disruption existed and had been previously commented upon. Where there is an arguable dispute both sides will present their cases along with evidence, for which it is the ArbCom's duty to sift and test along with the community at the workshop and other pages, and where one side is lacking in reasonable points it is indicative of them being in error. Why have the necessity of trying to find "missed" problems? LessHeard vanU (talk) 19:31, 10 April 2009 (UTC)

Why have the necessity of trying to find "missed" problems? Because our mission is to restore a collaborative editing environment for the Community so that stable NPOV articles can be written. If one or both sides in a dispute do a lousy job of presenting the evidence of how contributors are really violating policy, we still need to know it so we can find the appropriate remedies to end the dispute. FloNight♥♥♥ 16:35, 11 April 2009 (UTC)

FT2 comments

Comments are split into two sections - those where the effect is substantively unchanged but needing loopholes fixed or other copyediting, and those where important omissions or issues require some checking by the Committee and community.

Copyediting

There are several places where wording could be simplified or is too formalized, as well as some other points where some clarification may help:

• With suggested copyedits annotated (link)
• The same but without annotation (link).

Summary of main suggested edits (kept to a minimum):

1. Subsection fever - Too many subsections tends to encourage a legalistic view, or be tiring to readers. A plethora of one sentence sections isn't needed - kill most of the third level headers, merge and cleanup.
2. Arbitration proceedings section header - Needs to have a "one sentence version" of the actual goal of arbitration cases (as opposed to the duties of the arbitration committee). Added "Arbitration exists to determine an appropriate and binding way forward for intractable disputes (etc)"
3. Normal hearings and dismissal of cases - both better merged elsewhere.
4. Explanation of conduct vs. content disputes - Repeated contentious issue at RFAR, well worth clarification. Possible reword and footnote added.
5. Conduct - Clerks manage conduct on most arbitration pages, not just the "case pages". Conduct that the clerks have to manage can routinely spill over onto WT:AC and the like, which aren't "case pages" as such. Fix.
6. Private hearing participation - 1/ the right to participate is moved from "private hearings" to "participation", and 2/ sentence added per Kirill's point below to clarify that in case of genuine emergency or temporary action there will be opportunity to participate and respond after that action and before the case is finally decided or affirmed.
7. Evidence - Considerable scope for improvement here. Many issues, some unnnecessarily complicated wording. Changes:

   1. Easy to simplify the wording of "acceptable evidence"
   2. Mediation policy, itself an exception to a general evidence rule, itself makes clear exceptions; important to note this and clarify better than it does at present.
   3. A common case where external evidence routinely may be salient, is prima facie omitted; make it explicit.
   4. Simplify the paragraph about posting such evidence on the wiki. Much easier to say "if you wish to post evidence like this, submit to ArbCom who will say whether its relevant and if so, whether it should be private or public".

8. Follow up cases and clarifications - drafted a better explanation.

Hopefully the copyedits shown improve the draft.

FT2  19:28, 10 April 2009 (UTC)

Brief comments on some of the points:

1. Yes, this has already been noted above; the section fracturing will be reduced in the next draft.

2. Isn't this redundant to the first section of the policy? I'm not in favor of repeating things merely because some people don't want to read the entire document.

5. We are dealing specifically with proceedings here. General talk pages are adequately governed by the normal policies; we can simply add an overall "ArbCom can set conduct standards on its own pages" clause if it's really necessary.

6.2. We're not forced to follow the minutae of the mediation policy; if there's a legitimate exception, MedCom will approve the use, and we'd rather not bother with arguments over gray areas.

6.3. Merely because something is commonly used doesn't mean we must permit it. We don't need or want to rule on intent, in any case.

Kirill  02:25, 11 April 2009 (UTC)

2. The first section states AC is "resolver of last resort" (as one of its roles), but nothing in the policy says what "resolving" means in a Misplaced Pages context. Not a trivial exclusion - we get a lot of people confused innocently or deliberately over that point, so it's worth adding explicitly, the purpose of dispute arbitration, which isn't the same as the role of the arbitration committee. Resolving doesn't mean "court-like figuring out who did what", it means "determining the best way forward for the community", and that's sufficiently different from the everyday meaning that somewhere, it should say so.

5. An "ArbCom can set and enforce conduct standards on its own pages" clause would do the job just fine. Point here is that arbitration pages may have (or need) tighter behavioral controls and the right to set and enforce standards that are felt appropriate, more than the normal wiki page, since any kind of gaming, disputing, dirty-washing-hanging-out, grudges, accusations (true or untrue), untramelled multi-party arguments, etc may take place on these pages far more than on an average page elsewhere on the wiki.

6.2. People taking a bad actor to arbitration will read AC policy where they may well not have read mediation policy (or forgotten the detail). Saying point blank with no exclusions "may not be quoted" misrepresents mediation policy and may encourage misconceptions (and worse, can encourage misleading quotation or 'lawyering).

6.3 Then the case of "conspiracy to ...." needs wider scope. One person cannot be a "conspiracy", and in cases of serious disruption, POV pushing etc we might not name the real world connections, but editors need to be able to allude to the "bad actor"s real life affiliation with some business, group, or whatever. Since solo dedicated hardened POV pushers are a routine matter at arbitration, it seems odd to say that evidence from the outside is permissible when there are 2 or more individual people in a "conspiracy" to violate policy, but not when it is one person alone. Since external evidence should never be used unless directly salient, a wording to the effect "direct evidence" of a "seriously disruptive" whatever... makes sense. You don't want such evidence unless it's both serious, and very salient indeed, but to strike it out in all cases unless 2 or more users can be identified in a "conspiracy" seems to provide good odds of an issue best avoided. A user is entitled to say "this seems to me good evidence of a serious disruptive intention" (in private if required), even if in fact ArbCom reviewing the case ultimately form their own view of the case.

Thoughts. FT2  10:59, 11 April 2009 (UTC)

Issues oustanding in the draft

There are also about 5 important points where community or ArbCom review is important, and more input may be needed:

Item	Possible rewording	Original	Concern
Arb conduct	"Arbitrators are users endorsed and trusted by the community to undertake some of the most sensitive and wide ranging issues within the community. The trust of the community, the integrity and good faith of arbitrators, and the high standards expected, are to be respected in private wiki-related discussions, as in public." "Good communication and high standards are expected of arbitrators. More so than administrators, they are expected to enact high standards even under reasonable pressure. Arbitrators will explain their Wiki conduct and matters relevant to their trusted roles, to their colleagues, if their actions cause concern, and (privacy permitting) to the community."	Arbitrators shall, at all times, act with integrity and good faith to uphold the trust of the community and the high standards expected of them. Should their actions cause concern, arbitrators shall explain their conduct in matters relevant to their trusted roles to their colleagues and to the community.	Not nearly strongly enough worded. Commented same on the previous draft of the policy. Needs to be explicit about the standard expected.
Recusal	"Arbitrators are not expected to be free of "history" of interaction with each user and topic, but their ability to reach a decision neutrally and fairly is paramount. Arbitrators are expected to assess their neutrality for each case and to take note of the concerns of others. An Arbitrator who may be perceived to have significant past interactions should either recuse, or else should disclose any prior issues (privately or on-wiki as appropriate), and explain the basis of their belief they are able to assess the case neutrally, if necessary."	An arbitrator shall recuse himself or herself in any case in which he or she has a conflict of interest, such as prior involvement in the substance of the dispute or a history of disagreements with one of the parties, such that his or her impartiality in the case could reasonably be questioned.	As above.
Private hearings	"Regardless of whether an editor's conduct is considered by the Committee in private or public, the editor concerned will usually be given due notice and opportunity to respond before any decision. In very serious cases, or those where for privacy or other reasons this is not practical, a provisional decision and actions will be announced to prevent or reduce harm, and the editor concerned will have a right of appeal and discussion (in private or public as the Committee may decide) before any final decision is made or affirmed."	"... will be given due notice and an opportunity to respond, as provided below."	Recheck by Arbitrators whether this is tenable as drafted. Issues: Although prior warning and discussion is often desirable and very common, a number of actions (including many admin actions every day) in fact get enacted first, with the right of appeal instead. The important feature is the user has the right to respond and to address the case, either before or afterwards. Is every case involving the Committee guaranteed to bear "due notice", prior warning, opportunities to discuss the case etc, before any decision or action? That needs considering before writing into a policy. As examples, a number of cases involving very serious issues have not involved prior posts to the user, lengthy discussion etc; rather, a summary decision is made by the Committee with any discussion following. Runcorn, ArchTransit, certain serious harassers, are examples. So a commitment of this kind would be a change, and it needs considering whether it will always be viable, or sometimes not. The wikilinked text "as below" does not in fact link to anything that answers the issues. Private cases are a difficult area. Suggested rewrite fits current practice, and may help.
Community kept "in the loop"	"If any stage of a case extends (or seems likely to extend) beyond a usual or reasonable time, then any Arbitrator shall advise the community of the progress of the case and the matters causing the delay, no less than once every seven days."	Although lengthy cases are the norm, there should be a positive requirement for communication by the Committee, when there's a long delay, why it's so and what's actually going on. Experience suggests if this duty is laid on the committee as a whole it may never be done (or very watered down) hence given to any individual arbitrator to ensure it's explained, so that there isn't a hold-up in order to get a formal statement by the whole committee first. The time period ensures time is kept firmly in focus.	No provision for informing community.
Public explanation for decision	"The arbitrators may discuss and deliberate on cases between themselves, particularly where warranted by privacy or similar factors, but the substantive basis for the final decision should be apparent from the decision itself or from arbitrators' comments on it."	The substantive reason for a decision should be given to the community, even if no details can be disclosed. This isn't said clearly. It should be.	Clear public accountability and awareness.

FT2  19:28, 10 April 2009 (UTC)

A few (brief) comments on the five points:

1. I don't see any functional improvement here; the proposed version is longer, but doesn't add any concrete rules for conduct. The substance of the clause is the requirement to explain one's conduct; everything else is just background, really.
2. The only functional difference I see here is a requirement to disclose potential conflicts of interest, yes?
3. We're not going to conduct private hearings without giving everyone involved the opportunity to respond; and genuine emergency actions aren't covered by that portion of the policy.
4. This seems more like a question of internal procedure. I don't think it ought to be in the policy to begin with; and its relevance is questionable, given the other procedural reforms we're working on.
5. This could probably be handled by some minor additions to the description of the decision components; really, the basis for the remedies should be apparent from the findings of fact.

Kirill  02:18, 11 April 2009 (UTC)

1+2: You're missing the point I think. The point here is not procedural or functional in the sense that it doesn't lay down a proposed change of process. The aim of 1+2 are to emphasize the overriding need in these areas and emphasize the standard expected. The key expressions are not the disclosure and such, they are these two points:

• "Arbitrators are users endorsed and trusted by the community to undertake some of the most sensitive and wide ranging issues within the community... More so than administrators, they are expected to enact high standards even under reasonable pressure"
• "Their ability to reach a decision neutrally and fairly is paramount."

Those strongly worded points are what is missing. Recusal and conduct should not be a generic "high standard expected"; the wording should be rather more forceful and forthright than that. Saying that these are "not making a functional change" suggests the focus of these has not been appreciated.

3. That's fine, then it needs to add that "This does not cover genuine emergency and temporary actions, which will be followed up by opportunity to respond." Updated: I have amended the suggested draft to cover this.

4. No. Explaining to the community and participants what's holding up a case for an (apparently) unreasonable period is not merely "a question of internal procedure", nor in light of track record is reliance upon "other procedural reforms we're working on" sufficient. If a case is stressing users by taking forever, there should be a positive requirement that an arbitrator is to directly post to the talk pages, "what's going on to cause the delay, and where it's at", and to keep that updated by regular follow-up posts if the delay persists.

5. It should be made clear. This adds a specific requirement that however the matter is addressed and presented, whatever the case or issue, the end result should be the community has some understanding of its substantive basis. Usually of course that will be via the FoF or other statement, but this guarantees the end result for all cases regardless of presentation, whereas "an FoF will be published" does not.

FT2  11:18, 11 April 2009 (UTC)

FT2, I strongly disagree with your rationale about recusing. Many arbitrators have deeply personal reasons for recusing from certain cases, and publicly identifying some of those reasons can lead to revelation of private information about the arbitrator. The reason that an arbitrator recuses is not usually all that important; the fact that an arbitrator is willing to recuse if they perceive a conflict of interest is what is key. In my own case, there are very few on-wiki reasons for me to recuse (I don't anticipate many arbitration cases involving the James Blunt article, for example), but several personal reasons that I may recuse that will not be obvious from anything I have ever done on this site. In many cases, if my reason is linked to something that can be personally identifying, I am probably not going to provide details even to my fellow arbitrators. That is as much for their protection as mine; I do not wish to put them in the position of unintentionally revealing personal information about me, something that is very easy to do, especially when the primary means of interpersonal communication is via mailing list. Risker (talk) 03:59, 11 April 2009 (UTC)

The question then is, "Should an arbitrator who feels unable to give an explaination why they consider themselves neutral in the dispute, expect to (or feel obligated to) recuse"? It's not that common a problem, really. If an arbitrator wants to recuse (without explaining) they can, but if they are challenged on it, and feel themselves neutral, but do not wish to say why... that's a problem. The rest, see comment to Kirill above. FT2  11:18, 11 April 2009 (UTC)

If an arbitrator recuses without giving a reason, no harm comes. There is no conflict of interest, and no personal agenda affecting the outcome. This is *not* a problem. Problems come when people *fail* to recuse, not when they do so without explanation. Risker (talk) 12:54, 11 April 2009 (UTC)

Then we're on the same page. The suggestion I've made is that "An Arbitrator who may be perceived to have significant past interactions should either recuse, or else should disclose any prior issues (privately or on-wiki as appropriate) and explain the basis of their belief they are able to assess the case neutrally if necessary". Presumably an arbitrator with no neutrality issues doesn't have a problem; nor does an arbitrator who will recuse. But an arbitrator with a possible or perceived neutrality issue should disclose it and their reason for believing they can be neutral if (and only if) they do not plan to recuse. Does that clarify? FT2  13:49, 11 April 2009 (UTC)

right to not participate

A matter seems to have come up on an outstanding case , discussed at WP:ANB which bears on the proposed section 2.7.3 "Editors named as parties to an arbitration case and given due notice of the case are expected to participate in the proceeding" which in an apparently contradictory way continues to say, in 2.7.4, "Should a party to a case fail to respond ... or explictly refuse to participate in the case, the Committee may nonetheless rule on that party's conduct in his or her absence."--which second part seems to be the current rule. DGG (talk) 04:29, 12 April 2009 (UTC)

I don't see the contradiction here. A party has the right to respond, and they're expected to do so; if they fail to do so, we'll go on without them. Kirill  05:14, 12 April 2009 (UTC)

...and it'll affect poorly on the party who doesn't. If you're "expected" to do something, and you don't, you can have no complaints when your failure to do that thing results in further sanction. For me, 2.7.3 and 2.7.4 make sense. Daniel (talk) 07:44, 12 April 2009 (UTC)

I think it's OK - parties are expected to respond, but failure to respond should not prevent a case proceeding. DuncanHill (talk) 12:28, 20 April 2009 (UTC)

Jimbo Wales's powers in relation to ArbCom: clash of texts?

The current text says: "In April 2007, Wales confirmed that the Committee could overturn any decision he makes in his traditional capacity within Misplaced Pages."

At that link, Wales said:

Does this "traditional capacity within Misplaced Pages" include his relationship with the Committee itself? It appears to. This is confusing. Will it be retained in the updated text? If not, are we to understand that the current draft is a "climb down" from Jimbo's statement, in that he will now be given several explicit powers that are, ultimately, in conflict with his "decree" in 2007. If Jimbo sacks an arb. tomorrow, he has explicitly said that the Committee can say "get f...., we're overruling you". Will that be the case under the rewritten text? Tony (talk) 15:42, 12 April 2009 (UTC)

I don't believe that the new wording represents a change in procedure, although I think both the old and new wordings are fairly unclear and would prompt something of a constitutional crisis if they were ever to be tested. I would view the "traditional capacity"/"role as project leader" clauses to effectively cover every action not taken in the role of a Foundation Board member; that is, office actions remain outside jurisdiction, everything else remains within, including actions related to the Arbitration Committee. That is, I would expect that in the event that Jimbo sacks an arb, and the arb takes Jimbo to ArbCom, ArbCom would have jurisdiction to hear the case and potentially reverse Jimbo's decision. The question of whether the arb should sit on the committee is mute because they would have to recuse anyway. Ditto for a contested term alteration or controversial appointment. There is no case I can think of where it would be impossible to find a neutral ArbCom to hear a case against Jimbo unless he tried to sack the entire ArbCom, which would be such a messy situation as to render any policy wording we can make here mute (since he would be effectively tearing up the entire ArbPol anyway). I don't think it's a particular issue. Happy‑melon 16:00, 12 April 2009 (UTC)

It's debatable whether this is a useful question. A lot of time has passed and ArbCom is no longer new, Jimbo is no longer in the same day to day "hands-on" role he was in 2003 when the idea of an Arbitration Committee was suggested. But if one is referring back historically, then this seems to be the rough position:

• Originally, a user who was seriously disruptive, could only be banned by Jimbo, effectively as being the project leader. Disputes were handled so far as possible within the community and the community used consensus as its decision process. When the community gave up, the case was referred outside the community to Jimbo, for an executive decision as he saw fit.
• The Arbitration Committee was very clearly created as a delegated vehicle to Jimbo. That is, instead of poring through the evidence himself, he could ask the committee to hear a case, and broadly he'd be happy to trust their decision. (It was only later that it was proposed cases could be submitted to Arbcom itself directly by the community.) The position was still, in effect, that all disputes were to be resolved by the community, collaboratively, using consensus seeking, and if a serious dispute could not be resolved this way it was submitted to a body outside the community, for a decision (ie Arbcom acting as Jimbo's stand-in).
• This places Arbcom in an unusual position in which it is partly in and of the community, as a panel of trusted users, but also partly outside the community as a vehicle for Jimbo's day-to-day powers as project leader (ie to hear and decide certain cases) to be managed by a committee rather than by him personally.
• So my interpretation of the relationship is roughly, that when it comes to actions within the community, such as blocks, bans, changes or access, editing decisions etc made by Jimbo as a normal contributor, Jimbo has said "if there is doubt, I will accept Arbcom's view on it". But when it comes to the Jimbo-Arbcom relationship generally, Arbcom is still in part constituted as a vehicle outside the community to handle Jimbo's executive powers on a day-to-day basis, and Jimbo still "owns" that relationship (even if by inclination he doesn't wield it dictatorially but as a benign partner and participant). And if Jimbo says "this is my decision as project leader", then that's probably basically it. Right to leave and right to fork.

If one is after any meaning of "traditional role", that's my own understanding on the point.

However the reality as of 2009 is, Jimbo consults and discusses, but almost never these days directs; I cant remember any occasion in 2008 when Jimbo "ordered" ArbCom to do anything as such or even came close to it. His preference has been to gradually allow ArbCom to take over the role it now has, and that is roughly what the policy draft reflects. FT2  20:52, 12 April 2009 (UTC)

re : arbcom being partly outside the community as a vehicle for Jimbo's day-to-day powers as project leader - I'm not sure either that this is the case, or that it should be. Presumably other arbcoms (for example the german) are entirely 'of' their communities? I think our dear arbcom probably should be / is too :-) Privatemusings (talk) 05:11, 13 April 2009 (UTC)

Delegation

"The Committee may, at its discretion, delegate any authority granted to it by this policy to another group of its choosing."

I've never liked clauses like this. Arbitrators are subject to a long process of community evaluations and approval. It stands to reason therefore that the community expects to be involved in deciding who is trusted with your authority. While handing off some functions to persons who were not so publicly vetted is likely to be fine, other functions may be controversial. You weren't elected to "pass the buck" as they say.

I'd like to see this expanded to either be more explicit in its scope (e.g. targeted to which powers and under what circumstances), or include explicit community consultation on hand-offs of power, or both. I'm assuming that the existing Committee has ideas for how they might use delegation, and perhaps it would be better to elaborate on those. Personally, I consider this unrestrained clause unreasonably broad. Dragons flight (talk) 23:12, 12 April 2009 (UTC)

Might be an idea to start by listing the possibilities for delegation. Currently, the committee has subdelegated within itself the ban appeals process, in an attempt to have most appeals (where the full committee is not needed) delegated to a subcommittee of three (in theory freeing up the time of the other arbitrators to concentrate on other things, such as cases). It has been mooted that this could be delegated even further at some point - but how far should this be delegated? The other delegation going on at the moment is the CU/OS audit function, where ArbCom are expected to review allegations of misuse of the CU (checkuser) or OS (oversight) tools. It was recently announced that there will be a subcommittee of three arbs and three editors to carry out this CU/OS audit function (three initially appointed to get things set-up, and then three elected once it is clear how many elections people will put up with and what timings would be best) - see here. I think those two functions are all that is or was on the agenda to delegate. It should be noted that in both cases ArbCom retain the authority to some degree, because they still receive a final report and can do a full review if needed. As for other delegations, when the update to arbitration enforcement procedures comes along (the recent RfC on that is being analysed at the moment), some delegation might possibly happen there, or, depending on what people want, arbs may get more closely involved with arbitration enforcement. The other thing being delegated, in this case to to the community, though still with some ArbCom input, is the selection of new OS and CU people (previously done by ArbCom following a period of consultation). There were elections on that recently, and depending on the review of how successful that was, similar elections will probably be held when more CU/OS people are needed. There is even some subdelegation going on with caseload, as we are now designating an arbitrator to be a point-of-contact on each case, along with the clerk(s) for the case (see Template:ArbComOpenTasks). There is only one other thing I can think of that might be covered by the wording you have mentioned, and that is passing on enquiries, and other matters that come to us, to other people to deal with. That is not so much delegating our authority, but saying "this isn't something we can or should deal with - go and see these people instead" (e.g. go and ask checkusers, oversighters, the admin who blocked you, etc.). There are also times when issues that date back many years come up again and we ask former arbs for advice (they may have been the ones around for the original case). I think we normally ask them to advise us, but there are cases where it can be easier to say "can you deal with this?". Is that an acceptable "delegation of authority", or is that just simple delegation of a task? In general, most of the time, delegation happens either because we don't have time to deal with something, or because we aren't the best people to deal with something. I guess the question is: do people want a consultation period before any major formal role is delegated, asking whether ArbCom should retain the role instead of delegating it? Carcharoth (talk) 01:18, 13 April 2009 (UTC)

.

I think almost no one would complain about internal delegation. In fact, until your reply, it hadn't crossed my mind that the delegation clause was even meant to encompass internal matters. As long as the Committee of the whole can be called upon to appeal subcommittee actions when appropriate, I don't think anyone would be bothered by the Committee finding ways to better organize the workload internally. It should probably be mentioned in the new policy, but I see no problems there.

The other extreme is delegating power to agents outside of the committee. AE is sort of an example of this, though not a very strong one since ArbCom hasn't historically ever done much enforcing. One might imagine more blatant examples, such as giving people who aren't current Arbs final authority over ban appeals etc. I would say that if one intends to delegate power to people outside of the committee (which is how I initially read the clause), then a process of community consultation ought to be expected and necessary. Dragons flight (talk) 03:52, 13 April 2009 (UTC)

A long while ago, certain matters were delegated to the clerks. We were controversial then, but not so much now. I think the solution to the democracy/vetting problem is to elect arbs who are good judges of character. --Tznkai (talk) 04:20, 13 April 2009 (UTC)

May I suggest,

"The Committee may, at its discretion and with general consent of the community, delegate any authority granted to it by this policy to another group of its choosing."

as an alternative. --Barberio (talk) 23:31, 14 April 2009 (UTC)

• How would that "general consent" be obtained? It is a fact of life that constitutions, rubrics, laws, cannot be infinitely fine-grained. It is a matter of practicality and workability that ArbCom be able to delegate powers to others it trusts. ArbCom itself is ultimately responsible if such delegates mess up; this is what happens in real life. However, in the case of the clerks, I believe their role is central to hearings and that it needs to be more closely defined. Tony (talk) 15:29, 17 April 2009 (UTC)

How about

"The Committee may, at its discretion and with assumed consent of the community, delegate any authority granted to it by this policy to another group of its choosing."

ie, unless it's demonstrated that the community doesn't consent to delegation of an authority.

I'd also recommend the following also be added after it.

"The Committee will supervise the activities of these groups, and have final power to overrule or alter any delegated decision or action."

--Barberio (talk) 13:25, 19 April 2009 (UTC)

That may be usable, although it doesn't define what would demonstrate a lack of consent. We probably need to add some more material on ratification processes and so forth in the next draft. Kirill  16:09, 19 April 2009 (UTC)

Expedited decisions and motions

Starting this section to fulfil a promise (from January 2009) to make sure this issue got discussed. Am contacting the three editors involved at the time, to invite them here to discuss the section of this draft policy describing expedited motions and decisions. Please could others also comment, so that there is an indication of what the feelings are about whether expedited motions and decisions are good or not. Some links to help get up to speed:

• Relevant section in draft policy
• Previous discussion (1)
• Previous discussion (2)
• Previous discussion (3)

It is that last discussion where I promised to bring this up again when it was being discussed. There are several examples of previous instances of expedited motions instead of a full case. Does anyone want a list? Carcharoth (talk) 02:00, 13 April 2009 (UTC)

It seems to me that the third paragraph of the relevant section in the draft policy is all that is needed here. Whether a case would benefit from a speedy resolution is something that the members of the committee can make an informed judgment on, whereas whether they have all the pertinent facts is veering into Donald Rumsfeld's "unknown unknowns" territory. When the facts of a situation are genuinely "substantially undisputed" the case shouldn't be at Arbcom in the first place, so the request should be rejected. In cases where user conduct is called into question there certainly shouldn't be a facility to circumvent the editors' ability to put their case. Yomangani 08:57, 14 April 2009 (UTC)

Penalties for arbitrator violations

There are no penalties listed for violations. Arbitrators already don't follow the rules without penalty, so why bother tinkering with the rules? -- SEWilco (talk) 03:00, 13 April 2009 (UTC)

The penalty is found in the ballot box.--Tznkai (talk) 04:20, 13 April 2009 (UTC)

This made me chuckle. In all of history I think there has only been one Arb with more than 6 months active service to be re-elected. Should we conclude therefore that nearly all Arbs do a terrible job? One would have to better manage the burn-out and/or shorten the terms before the ballot box would be much of a deterrent to anything. Dragons flight (talk) 17:35, 13 April 2009 (UTC)

I guess the job is the penalty then.--Tznkai (talk) 04:06, 14 April 2009 (UTC)

FWIW, arbitrator recall is on our agenda at the moment. Kirill  05:32, 14 April 2009 (UTC)

Private submissions of evidence, and the role of the Community

Surely all evidence should be made public unless there is good reason not to. That doesn't seem to be the internal logic of this section, which notes evidence that could be made public won't automatically be made public. Also, why isn't discussion of evidence done in public? There is still no attempt to link decisions to evidence, making decisions sometimes hard to fathom. Also, the arbitration committee does recognise it is answerable to the community, doesn't it? I can't really see that principle enshrined. For example, the committee is free to modify its internal procedures, and free to delegate any authority granted to it by this policy, but it appears the community does not have that right. Surely the Committee serves the community, and serves at the community's request and tolerance? I would have thought that was a part of the unwritten constitution, muchg as Jimbo's power is limited by what the community will tolerate, as has been evinced on other Wikipedias. I think if a new draft is being settled upon, there really should be some thought to how the power is structured. Currently arb-policy apparently needs "consensus among Committee members". Will we be reflecting that truly, it requires consensus in both houses as it were, the Committee and the community? Hiding T 14:28, 13 April 2009 (UTC)

I think more accurately, the committee is answerable to the project - that is, to the aim of creating a neutral 💕. "Misplaced Pages" per se is a project whereby a community writes a neutral encyclopedia of free knowledge, and the community is one part of the equation. If the community were to drift away from those goals (and many well-meaning communities do over decades drift away from their founding ideals) then the committee's obligation is to the goals of the project, rather than to "whatever whims might sweep the community". Thus in RFAR cases you'll always see the committee referring to principles of the project, but rarely or never to "this years" current moods and trends of the community, in guiding its decisions, unless those are seen to also serve the project's goals.

In that sense, the committee is not just there to serve the community without limit. It's there very definitely to serve the community in the community's goal of furthering the project -- and part of that service is to say when the community (in its view) needs reminding of those goals and principles, or they need enforcing beyond what the community is currently doing, or it's (in the committee's view) off track. And it's also there to serve Jimbo Wales as project leader, in its role of delegatee of some of his traditional role and powers. FT2  16:13, 13 April 2009 (UTC)

<edit conflict, above text may have altered since this reply was initially composed>I'm not sure we're talking about the same things. I'm a bit baffled by the statement that the Committee can remind the community of its goals and principles. You seem to have taken things to a confrontational extreme, and it does beggar the question; what would be the outcome if the community told the Committee to get stuffed? Within the unwritten constitution, not a lot, unless the Committee has powers I am currently unaware of. I think you've conflated the Committee with the Board. The Committee's pronouncements and remedies are only effective as long as there is a consensus amongst the community to respect and implement them. That needs to be recognised in policy in some sense, surely? Also, the Committee is not there to serve Jimbo Wales as project leader. It's there to arbitrate on disputes. That's what Jimmy delegated to it. Jimmy delegated the responsibility for Wikipedias aims to the board, and responsibility for content was delegated way back when to the community. Hiding T 16:38, 13 April 2009 (UTC)

What would happen if the community tried to defy ArbCom? The community would lose. Any editor who defies ArbCom can be blocked: all arbs are admins. Any admin who wheel wars with ArbCom can be desysopped: ArbCom can command the stewards. It is not possible for a community to exist in defiance of ArbCom, because ArbCom is, as FT2 says, ultimately answerable to the project above the community. If ArbCom decides that an element of the community is acting counter to the goals of the project (and can convince the members of a suitably high-level group that they are right) then any necessary action can be taken.

Of course, that is not the point. The community might 'lose' such a war, but there is no way ArbCom or the Foundation could be said to have 'won'. A project without a community is not going anywhere, and the need to retain an active and happy community must be weighed as one of the goals of the project which ArbCom is defending. If the situation deteriorates to the point where ArbCom and the community have such radically different views that there is active fighting, something has gone very badly wrong. Part of ArbCom's purpose is to nip such digressions in the bud, and keep the community aligned with the goals of the project. As long as those interests remain aligned, any discussion of such "confrontational extremes" is entirely academic. Happy‑melon 16:52, 13 April 2009 (UTC)

Not sure I'm comfortable with either of these completely.

• Hiding - the WMF board operates the project but not the content of Misplaced Pages; its role is the provision of an operational charitable framework, server and software, on which the community can exist, and set a handful of the very top level policies (privacy, NPOV, etc), etc. Most large systems have checks and balances; ArbCom is a check and balance as well as an operational part of the whole. As a check and balance, it can't simply reflect "whatever happens to be the trend"; sometimes it may have to act in opposition to a trend.
• Happy-Melon - Arbcom isn't some kind of top level executive board in the sense that post might suggest. Its role is broadly to resolve problems that impact the project's editors, not to go round wholesale blocking and banning. But your general point is correct that extreme divergences are highly undesirable; what is a desirable or undesirable trend is very much case by case though.

Mostly though, the idea is to aim for the happy middle road, where we're all solidly behind the aims of the project and attempt to develop these in the best way we can, and with good collaboration skills. If that fails, ArbCom's "dispute resolution" role is basically, to fix it if the wider community can't. FT2  17:03, 13 April 2009 (UTC)

Concentrating, for the moment, on the relationship between the Committee and the community: there's a distinction that should be drawn between the constitutional basis of the Committee's authority and the practical aspects of the Committee's work. It's one thing to say that, in principle, the Committee is subject to the community; it's another to try and have the community as a whole micro-manage what the arbitrators do on a day-to-day basis. The driving force behind §1.3 and §1.4 is the need for us to be able to make routine changes to our internal roles and procedures so that we can actually get things done; if we must to conduct a community ratification vote every time we adopt a mail sorting process, or if the community starts making changes to our workflow on a whim, things will simply grind to a halt. Kirill  04:38, 14 April 2009 (UTC)

I've got no argument with that. But surely there's got to be a better way of framing that. Perhaps something like "To make routine changes to our internal roles and procedures as necessary to ensure the smooth running of arbitration." That wouldn't suffer from degradation. But I agree with the comment at the bottom of the page, this is far to legalised and technical. We've always tried to avoid that approach on Misplaced Pages if possible, because it makes things too complicated. But I also wanted to focus on the issue of evidence here too. Is there any reason evidence submitted privately should be kept private without good reason? Surely cases are held as publicly as possible, rather than as privately as possible. Which one would be the arbitration committee's preference? Hiding T 09:18, 14 April 2009 (UTC)

Maybe we could combine 1.3 and 1.4 into something like "The Committee may, at its discretion, modify its internal procedures, form subcommittees, or designate individual arbitrators for particular tasks or roles, as necessary to ensure effective operation. Where appropriate, the Committee shall allow a period of community consultation for proposed changes before adopting them."?

As far as the evidence is concerned, we do prefer things public unless there's a need to have them private, hence the "The Committee may request that privately submitted evidence be posted publicly if there is no reasonable cause for it to be private" clause in 2.10.4. Perhaps simply stronger wording there would be sufficient? Kirill  12:29, 14 April 2009 (UTC)

necessary jimbofication?

The jimbo count on the proposed draft is in double figures, with ten mentions! - I'd very much like to encourage a sensible process for measuring wide community input into the merits and wisdoms of this level of jimbofication. Personally, I'd like to see Jimbo as a constitutional monarch - the role he's also identified himself as the best fit. This draft as written doesn't really match - with the appearance of rather wide-ranging discretionary powers. I feel sure the english wiki arbcom can function along similar lines to the german arbcom, without a single person holding any special power. I would edit the draft to reflect this, but can't (that's another discussion for another day ;-) Privatemusings (talk) 22:47, 13 April 2009 (UTC)

You could add a footnote here. How many mentions of Jimbo are in the current policy? Carcharoth (talk) 23:41, 13 April 2009 (UTC)

Cut it up

This is creepy. It's far too long, it's couched in language that's too legalistic, and it's at once obsessively focused on procedural minutiae, yet way too broad in scope. A policy document should be just that: a statement of the irreducible policies that govern ArbCom, unencumbered by anything else.

Chop it up. I think you need several short documents, not one long one — with each document serving a clearly-defined function and addressed at a clearly-defined group of users.

For example:

1) Overview of ArbCom (introductory and historical material that gives background, intended audience: someone who doesn't know what ArbCom is)

2) Policies (the things ArbCom couldn't change, or would never change, intended audience: participants at ArbCom)

3) Custom & Practice (the way ArbCom does things at the moment, but could change if it saw fit, intended audience: participants at ArbCom)

4) Procedure (step-by-step breakdown of a typical case, with timescales, intended audience: participants at ArbCom)

5) Scope (i.e. What ArbCom Is Not, intended audience: someone who's thinking of bringing a case)

—S Marshall /_Cont 00:54, 14 April 2009 (UTC)

Well, I think that it's a fairly safe assumption that anything which ends up in the final "arbitration policy" document will essentially be set in stone for the foreseeable future, while anything that's considered merely a Committee procedure will remain significantly more open to change. This has, to some degree, guided the choice of contents here; we've tried to put in those items which we thought should be fixed.

There's certainly a reasonable argument to be made for omitting some of the more technical and procedural items in the text (e.g. the acceptance criteria in "Voting on acceptance", the activation procedures in "Active arbitrators", and so forth) from the formal policy and handling them as procedures, and concentrating the core policy on the duties and authority of the Committee, and the rights and responsibilities of editors in arbitration; but I'm not sure whether the community would prefer that approach.

What do people think? Should we reduce the amount of procedural detail in the policy, putting things in terms of rights and responsibilities instead? Or stick with the current approach? Kirill  05:16, 14 April 2009 (UTC)

I'm no fan of the current approach, I think it's fair to say. Hiding T 09:19, 14 April 2009 (UTC)

Nor me, though splitting it up isn't necessarily the answer either. I certainly think we need to discuss carefully the fundamental principles behind all this and decide what we want to achieve. Above all, people should know what sort of complaint is appropriate to take to ArbCom. My suggestion above - which AFAICS no-one addressed either positively or negatively - was that it should be only complaints about specific actions (or failures to act) of admins and other "officials". Ordinarily, if you've got a complaint about someone's behaviour, then your first port of call (preceding ArbCom, anyway) should be the admins' noticeboard. Others probably disagree with that would-be principle, but surely we can make some effort to answer this question. This seems a far more essential sort of thing to get right than the minutiae of procedure which we seem to be concentrating on at the moment.--Kotniski (talk) 11:28, 14 April 2009 (UTC)

Well, that's the point of having a "What ArbCom is not" document.—S Marshall /_Cont 12:56, 14 April 2009 (UTC)

OK, one thing we have to decide is what ArbCom is not; another (less important) thing is whether that information is best presented on a separate page from other information. I agree with your proposed list of topics that need to be addressed, though I think the presentational question of how many separate pages are needed is not one we need worry about yet (we need to know what the information is before deciding on how to present it). I would like to make a formal proposal about Scope and about the dispute resolution process in general, along the lines set out above at #A model for dispute resolution, but since I have relatively little experience in this area, I'd like to get some concrete feedback about these ideas from those who do.--Kotniski (talk) 13:12, 14 April 2009 (UTC)

• Sorry, I do not at all agree with the idea of "cutting this up", nor that its tone or register are over-legalistic. The community and ArbCom itself needs to know where it stands, and a whole-of-picture document that sets things out clearly, simply, and precisely, will serve this purpose best. The term "legalistic" is a pejorative term for these qualities. The argument has not been made as to why the document should not embrace them. Tony (talk) 15:12, 17 April 2009 (UTC)
  • It should not embrace confusing terminology because it then becomes unclear to readers what is being said. Try and parse "In exceptional cases of communal division or exceptional risk of harm to the project, the Committee may determine a interim means to achieve the aims of communal policies or to curtail dispute in the area, until the community has developed a better consensus." I'm pretty sure words four to fourteen are irrelevant. From word fifteen on, the intent become muddy. If they really want to say "In exceptional cases, exceptional action may be required", fine, but don't dress it up in jargon. I'm not going to attack the odd typo, but you've got aspirational grammar with no definitive point to it. "may determine"? "achieve the aims"? You are absolutley right, we need a whole-of-picture document that sets things out clearly, simply, and precisely. We deserve so much better than, and I apologise here, corporate management speak. Could we get much closer to "the arbitration committee will provide blue sky thinking and forward thinking methods for thinking out of the box while ensuring longstanding goals are delivered within a reasonable time frame, allowing for input from the wider community where their opinions impact in the day to day implentation of consensus." Hiding T 17:10, 17 April 2009 (UTC)
    • Agreed: the whole text needs a plain-English copy-edit. See the footnotes appended by several users to the draft. Tony (talk) 16:01, 19 April 2009 (UTC)

"Jurisdiction over actions of Jimbo Wales"

Why is this limited to just his admin/steward actions? I strongly recommend this extend to any of his actions involving the Arbcom itself, so that the seated Arbcom firmly state that they can override his actions in regards to them--which they already have the power to do, as Jimbo cannot supercede any Arbcom decision anymore. For example, in the current wording of this document, Jimbo could remove an Arbcom member for "reasonable" cause, but without the approval of the Arbcom. Or, he could place someone on the Arbcom without the approval of the community or Arbcom itself. Jimbo is one person, and a person is never an institution. The Arbcom and Misplaced Pages are separate institutions; Jimbo is neither Misplaced Pages nor the Arbcom. This subtle wording change is the perfect opportunity to start defining boundaries for long-term success. What do you say, Arbcom? rootology (C)(T) 21:56, 14 April 2009 (UTC)

Jimbo can get up one morning and abolish ArbCom in its entirety, right? As I understand it, ArbCom only exists because Jimbo delegated certain powers to it, and he retains the right to reverse that. In any case, if we're going to discuss what ArbCom might or might not do in respect of Jimbo, we ought to ensure the participation of the great man himself.--Kotniski (talk) 13:54, 15 April 2009 (UTC)

I addressed a similar question a while ago, but I'll bottom line it. We don't know who has the ultimate wiki-legal power. We don't want to know. Misplaced Pages is not a bureaucracy, nor a government. We gave up no natural rights on Misplaced Pages, and we took no civil rights in return. If the "Jimbo question" is ever provoked and subsequently contested, it will be moment of complete and total failure of Misplaced Pages governance.--Tznkai (talk) 14:21, 15 April 2009 (UTC)

Consistency

Will the Committee be updating the other pages related to the policy when it puts forward the final policy version to ensure consistency? Pages such as:

• Misplaced Pages:Arbitration rationale
• Misplaced Pages:Arbitration Committee
• Misplaced Pages:Arbitration policy/Case handling
• Misplaced Pages:Requests for arbitration/How to present a case
• Misplaced Pages:Arbitration guide
• Misplaced Pages:Arbitration Committee/Procedures
• Misplaced Pages:Arbitration policy/Procedure for changing this policy

Put otherwise, is someone making sure we don't have contradictory guidance floating around at the end of this process? Thanks. MBisanz 06:44, 18 April 2009 (UTC)

Noted, thanks. Before any final version goes live (and the next iteration will probably be put out for comment again - though I'm not certain about what comes next here), those pages should indeed be updated, and hopefully this will not be neglected or forgotten. Carcharoth (talk) 10:14, 18 April 2009 (UTC)

1. Why is this list not centrally located so that everyone can easily gain access to all text related to ArbCom?
2. The Clerks policy page is missing from this list.
3. Looks like a case of bloat to me. Can't some of them be rationalised?
4. Yes, they all need to be updated, rewritten, copy-edited, and put here for community comment. The language is pretty bad throughout. Tony (talk) 16:48, 19 April 2009 (UTC)

We're working on it; see WP:AC/N#Relocation of arbitration pages. ;-) Kirill  17:38, 19 April 2009 (UTC)

Continuation of the expansive model for hearings is untenable

Summary: Evidence from third parties accepted only with the agreement of the Clerk; no workshop page; evidence limited to 500 words per party; scope and deadline for evidentiary submissions stated at the start; ArbCom can alter the scope during the case by announcement on the Evidence page.

The model for ArbCom hearings was established as expansive and all-inclusive. It appears to be implicitly premised on two notions:

• (i) that the body of evidence and opinion on which arbitrators form their judgements should be subject to minimal restrictions in scope and size; and
• (ii) that participation in the process should be open not only to the named parties, but to the whole town square.

While I have no doubt these notions were advanced in good faith, in practice, bloat and irrelevant material have become major barriers to the good management of cases and to the delivery of fair and prompt judgements. Any case beyond the very simple can easily get out of control—witness the dates case and its humungous volume of hogwash, and worse, of its encouragement of parties to poke their tongues out at each other, to bicker, to accuse, to carry on their dispute with renewed vigour on ArbCom’s pages themselves. This damages the reputation of the hearings process and of WP itself, and makes the task of the arbitrators unreasonably difficult. It leads to lengthy cases and a backlog for ArbCom that could easily affect the morale of the Committee.

The expansive, inclusive model is consistent with some of the statements in “important features”; not only this, the all-important section shows an uncertain, internally contradictory understanding, and a vagueness that is embarrassing if the hearings process is to be taken as the peak instrument for resolving disputes at the world’s most important information site. This garbled advice apparently underpins the structure and management of ArbCom hearings:

• “Arbitrators focus on the risk and benefits for future, not on past historic issues.”
• But then we learn that the past is important: a few lines later, “old incidents may not be actionable but can sometimes show a persistent history of problems.”
• Then, “A person's general manner is probably evidence of their likely behavior”, and “insightful impressions by reasonable people may be valuable, even if just "impressions"”.
• “Arbitration is more likely to ask if a user can change or what restrictions would have an effect, than "who said exactly what"” .

The oversized structure and laissez faire approach to management are an invitation for cases to spiral out of control, or at least to be far bigger deals than they should be. Arbitrators seem to be swamped by text. It is unruly, undisciplined, often chaotic. This is the opposite of what is required for an efficient, fair process.

Below, the four elephants in the living room are outlined. They need to be addressed in this re-write of the policy.

It's time to dispense with the Workshop page

The Workshop idea appears to have been the idea of Fred Bauder; I don't know the details, but its inclusion was possibly a decision made in haste. The page is nothing more than an invitation to admit bloat and irrelevance, and to attack. A senior admin recently informed me in writing that:

"several arbs not to waste time on workshops, nobody's gonna read them anyway ... not once they're long and messy".

Having four separate pages—Request, Evidence, Workshop, and Judgement—is excessive and needs to be reduced. Why is the Evidence page insufficient to provide the evidence required to make a sound judgement? Just why anyone but the arbitrators should be proposing "general principles", "remedies", and "enforcement provisions" is unfathomable. There should be an application, evidence, and a judgement—not brouhaha in the village square. Take a look at the Workshop page for the "dates" case.

Well, I've always found the workshop to be invaluable on cases I draft; where else would I do the actual drafting? It's a fair point that participation there should be more carefully managed—you might want to take a look at what Fayssal is doing on the Ryulong case for one approach we're considering—but getting rid of the page entirely would inconvenience the arbitrators more than it would help the parties. Kirill  16:02, 19 April 2009 (UTC)

Why do arbitrators need to be told by the parties and whoever wants to fly by what principles are stake, and what enforcements and remedies are appropriate? Don't we elect them to do that? Don't we put our trust in them? What kind of convenience is the Workshop page for the Dates case? Tony (talk) 16:42, 19 April 2009 (UTC)

You're talking about who does drafting; I'm talking about where drafting gets done. Even if non-arbitrators were barred from commenting entirely, the arbitrators themselves would still need the workshop (or some equivalent page with a different name) as a place to draft decisions before proposing them for voting. Kirill  17:40, 19 April 2009 (UTC)

That would be fine—parties present the evidence; arbitrators draft the decisions. Arbitrators might ask for clarification on the evidence page, but not the other way around. These parts of the process really need to be kept separate. At the moment, much of the drafting is done privately by the arbitrators, anyway. That is not a problem to me. Tony (talk) 18:02, 19 April 2009 (UTC)

Alternatively, if the current Workshop system is maintained, I think clerks/Arbs should do a better job of explaining and regulating what and what not would be appropriate for Proposed principles, FoFs, and proposed remedies. For example (taking it from the dates case), Misplaced Pages:Requests for arbitration/Date delinking/Workshop#Trout is just plain silly. A better and more unclear example is Misplaced Pages:Requests for arbitration/Date delinking/Workshop#Removing hyperlinks to years damages the bidirectional hyperlink structure of Misplaced Pages and impedes editing—this seems like a content ruling, and is it something that Arbcom could rule on regardless? Dabomb87 (talk) 03:41, 20 April 2009 (UTC)

The dates case has clearly shown that the workshop page is a useless duplication at best (where parties are unsure about where to post something, they do it in both places) and at worst, it is an open forum for a disruptive slanging match between parties where they can and do throw the kitchen sink at each other. How parties' submissions here can help Arbcom arrive at a resolution when one or both sides baying for blood of the other side (ie exacting revenge) by proposing tit-for-tat sanction motions is yet to be demonstrated. Sure, having been through one case doesn't make me an expert, but this case has been particularly acrimonious, and has brought out the worst in everybody that nobody (including Arbcom and its clerks) comes out looking good, so I think we could use this as a benchmark for a "doomsday scenario". I take note of Kirill's point, and would simply state that this can be the working page of Arbcom should it wish. I would encourage/welcome that additional transparency in the proceedings. However, if it is Arbcom's continued wish to work on various elements of judgement off-line, WORKSHOP's only rightful place is the waste receptacle. Ohconfucius (talk) 14:37, 20 April 2009 (UTC)

It's time to drop the peanut gallery

It is eccentric that a quasi-judicial process should allow anyone who wishes to throw paper planes into the room. It has the capacity to make the proceedings undignified and threatens any focus that might have been achieved if participation had been restricted to the parties, the clerks and the arbitrators. The current dates case is full of irrelevant comments from users who want to have their two cents' worth, with apparently little or no control over relevance, standard of proof, hidden and not-so-hidden agendas, or potential libel. This is not only a matter of retaining focus, but of procedural fairness and dignity, and making arbitrators’ lives liveable, without outsiders' licence to fling in drive-by comments without constraint.

Possible exception. Occasionally, a user who has not been named as a party in the application may have cause to make a useful contribution. I believe this should be allowed only by open application to the clerk, who should be convinced that that the user will make a bona fide and relevant contribution before allowing outsider comments or questions.

See my comment above about managing participation. Kirill  16:02, 19 April 2009 (UTC)

Which comment in particular? Can you lay out specifically what you mean in relation to the peanut gallery? Tony (talk) 03:09, 20 April 2009 (UTC)

The one about Fayssal; see Misplaced Pages:Requests for arbitration/Ryulong/Workshop (and related pages) for what he's working on. Personally, I don't believe that we'll be making any major changes to how cases are conducted without trialling them first; this happens to be our first attempt in that regard. Kirill  03:19, 20 April 2009 (UTC)

• Comment - I've found in more than a few cases that the most impartial, factual and/or complete evidence has been presented by people who are not directly involved in the dispute. Timelines, documentation of edit/action patterns, identification of impacts into other areas of the project that may not be immediately apparent to the involved parties, are all things that have been brought to the table by non-involved parties, and all have been useful to the present and previous iterations of the Committee in coming up with the best solution for the encyclopedia. One must keep in mind that, when a dispute gets as far as an Arbitration Committee case, it's almost never just an issue between a few editors, it is something that impacts the project itself. Risker (talk) 13:25, 20 April 2009 (UTC)

This is useful, and right at the opening? Not that I want to single out one third party, or to imply that the parties themselves didn't write a huge amount of tripe.

I'd like you to consider the following points in response to your post:

1. The Arbitrators are elected to be impartial judges, and a great number of them typically contribute to the collective wisdom of the Committee.
2. I have proposed (below) that third-party contributions be allowed if accepted after open application to the Clerk, on the basis that the third party has a relevant and useful contribution to make. I believe this is an efficient method for admitting (indeed, even encouraging) the valuable, impartial, factual evidence you refer to from non-involved parties. Of course, my assumption is that the scope has already been stated (and explicitly modified if necessary); without that, all is lost. Tony (talk) 13:45, 20 April 2009 (UTC)

• Whilst those with demonstrably valuable input may be welcome (per Tony), admitting tricoteuses is an invitation to irrelevance and bloat. In the dates case, there were enough parties alone shouting "off with his head", tricoteuses should thus be banished. Ohconfucius (talk) 14:46, 20 April 2009 (UTC)

Need for explicit scope and the active control of relevance

A key part of the expansive, inclusive model of ArbCom hearings is the avoidance of stating the scope at the start. It is unacceptable that neither parties, clerks nor arbitrators know the boundaries of the scope until the arbitrators finally sort out a judgement. This precludes proper action by the clerks to enforce relevance on the Evidence page (probably by liaising with a presiding arbitrator for each case). Why is there no requirement for the original filer to state their preferred scope, and the explicit expectation that this might then need to be negotiated with the clerk / presiding arbitrator. Better it be done at the start than after chaos ensues. The fact that ArbCom can, at its discretion, decide on matters beyond the behavioural makes it yet more urgent to be transparent from the time of accepting a Request. It would be much less work for the arbitrators to decide on a statement of the scope at the start than deal with tons of sludge later. I believe ArbCom routinely deals with four or more cases at once: that is crazy.

I'm not sure how feasible fixing the scope at the start of the case would be; in many cases, new issues emerge during the investigation. Possibly something like a regularly updated list of matters being investigated would be more useful? Kirill  16:05, 19 April 2009 (UTC)

The "new issues emerge" during the investigation precisely because the scope is not fixed at the start, surely? Frankly (though these comments are based only on the one ArbCom case I've had any significant contact with), the whole thing is really the most appalling mess, where no-one has any idea what's going on or whether it's worth spending their time on trying to influence anything. Unless you actually like extreme drama (which I suppose to some extent you must do if you agree to sit on ArbCom as it currently works), you must surely see that significant changes are necessary, not just tinkering with the wording of the policy. If someone "brings a case" (makes a complaint, in more normal language) to ArbCom, they should say against whom they are making it and what the complaint is, and why they feel the need to bring it to ArbCom and not (say) to the admins' noticeboard. As I've already said several times, I can't see any reason why complaints against ordinary editors should be brought to ArbCom rather than to the admins - but even if you think there are such situations, the complaint should still be specific in terms of who and what is being complained about. If "other issues emerge" - i.e. people start complaining about other things - then they should be told to make separate complaints through the appropriate channels. --Kotniski (talk) 16:30, 19 April 2009 (UTC)

In response, I don't think that new issues emerge solely because the scope isn't set. It can be and several times is the case that there have been other actions meriting ArbCom comment which are not included in the original matter, but which are related. These could include misconduct by the filers which are not included in the original comments, evidence of involvement by parties not mentioned in the original filing, etc. While I can see how it might be useful to limit the scope up front, and how it would certainly make things easier, it might also obstruct justice regarding other matters. The members of ArbCom aren't really in a position to open requests themselves, so with a strictly limited scope they would be basically unable to do anything about misconduct which becomes visible during the examination of a case but which is not directly included in that case. As the bereaved parties may in some cases have left wikipedia since the incidents, there is potentially also a lack of parties to file such a complaint. Having a undetermined scope allows such actions to be addressed, while a tighter scope might not. John Carter (talk) 19:16, 19 April 2009 (UTC)

"The behaviour of X and Y in relation to since ."? "Since" keeps going until the judgement. This is a red herring, John. All serious judicial/judging processes have a scope. This idea that "things might pop up during the case" that need to be covered by the scope is sheer nonsense as an argument for not stating the scope at the start. Tony (talk) 03:08, 20 April 2009 (UTC)

Well, it's not quite that simple. Suppose that we have a case brought concerning the conduct of user A, and so we open it with a scope like "behavior of A since ". It's quite common for A, when presented with findings against them, to plead extenuating circumstances—for example, that user B, whom they were attacking, was harassing them elsewhere. We would be negligent if we did not investigate this claim; but B's conduct is not covered by the scope, so we would be left with, as John proposes, modifying the scope during the case based on what comes up.

I'm not certain that there's really a good solution here; fundamentally, if we don't have a flexible scope, we'll be forced to turn a blind eye to misbehavior on the technicality that it was not mentioned in the original complaint. Personally, I don't think a fixed scope is worth it in this scenario; obviously, your opinion may differ. Kirill  03:27, 20 April 2009 (UTC)

The solution is to require A (the filer) to state a preferred scope upon application to hear the case. That is what happens in the real world. In the unusual case where significant other aspects need to be judged, the scope can always be changed, but it should be done explicitly and in writing, so all parties and the community can be in no doubt. That is the whole point: swimming in porridge, where no one, not least the arbitrators, has a clear idea of the scope, is nonsense. If the scope changes, we all deserve to know. One would hope that usually the scope doesn't change, but I understand why it might. Unfortunately, it's hard to know what proportion of cases have and have not involved a change of scope, to guide us in this respect, because ... um ... no one knows what the original scope was. The hearings need to be open, transparent and clear. Tony (talk) 03:37, 20 April 2009 (UTC)

• I think Tony is spot on: without a tightly defined scope, we will get into situations where we might ask questions like "how bad is bad", or "how long is a piece of string". It's those typically open-ended situations which inspire the filibusters and malingerers (and guarantee proliferation of drama). The dates case, now in its third month, has not yet set a record. However, it probably would have been over by now had the three elephants above not been inhabiting our living room during this time. The obvious advantage of banishing these pachyderms is that it would cut the case time and hence workload of Arbcom members. Ohconfucius (talk) 04:46, 20 April 2009 (UTC)

I don't see how pleading extenuating circumstances would cause a breach of the defined scope. If, following a complaint about A's behaviour, A seeks to justify it with reference to B or C's behaviour, then that's perfectly within the scope of the complaint. But if the "case" becomes a focal point for any D, E and F to start complaining about any X, Y and Z's behaviour in vague relation to a particular topic, then something's clearly broken down. (And once again, admins are perfectly capable of dealing with these complaints between editors. I'm still waiting for someone to tell me why ArbCom needs to accept complaints about other editors' behaviour, as opposed to complaints about admins' handling of such complaints.)--Kotniski (talk) 06:03, 20 April 2009 (UTC)

Better organisation

The Clerks need to be more active, which is a good reason for them to be highly sensitive to issues of conflict of interest, and for each case to be allocated a presiding arbitrator, who can liaise between the Committee and the Clerk, if necessary. There needs to be a time limit for the submission of evidence, regardless of the perceived complexity of the case, and lower word and diff limits for each party's submission. Being able to predict when the Evidence page is complete would allow basic organisation of ArbCom's workflow. Arbitrators are busy people, and should be given the courtesy of being able to plan a few weeks ahead.

This is already being done as a procedural matter. I don't think how the Committee allocates cases among arbitrators internally should be covered in the policy, beyond the mention in §1.3. Kirill  16:03, 19 April 2009 (UTC)

If it's already a procedural norm, can it be written on the application page and elsewhere? Tony (talk) 16:50, 19 April 2009 (UTC)

Summary of recommendations

1. The filing template to include the requirement for a filer to state their preferred scope.
2. ArbCom's acceptance of a case to include:
   • (a) a brief statement of the scope, including, if appropriate, temporal and article limitations;
   • (b) a deadline for submissions to the Evidence page—probably two weeks; and
   • (c) the naming of an arbitrator to preside over the case (mainly to liaise with the Clerk where necessary).
3. ArbCom to have the ability to modify the scope and the list of parties at its discretion during the case, by notification on the Evidence page.
4. The number of words and diffs allowed to each party on the Evidence page to be reduced from 1000 words and 100 diffs down to 500 words (in display mode) including diffs, and enforced by the Clerk, with limits exceeded only by acceptance of an open application to the Clerk.
5. No third-party input to be allowed on the Evidence page, except by acceptance of an open application to the Clerk.
6. The Workshop page to be binned.

Tony (talk) 15:46, 19 April 2009 (UTC)

I've commented in the individual subsections above. Kirill  16:05, 19 April 2009 (UTC)

I completely agree with Tony's suggestions, at least as a minimum as regards what needs to be done.--Kotniski (talk) 16:35, 19 April 2009 (UTC)

Tony, I would encourage you (and other interested parties) to read Wikitruth through Wikiorder which is an academic paper reviewing the history of ArbCom through 250 decisions. You appear to be trying to make ArbCom "better" by making it more closed, rigid, and closer to real world judicial proceedings. I would argue, in line with the central thesis of the cited paper, that much of ArbCom's success stems from the fact it is fundamentally not a process of law. Given the nature of the wiki-environment, I believe the community is better served by the open and flexible process than it would be by one that was more rigid and closed. Some cases do get a bit out of hand, but I think the answer to that is better management to address specific problem cases and not broad global restrictions. Dragons flight (talk) 03:46, 20 April 2009 (UTC)

So how do you propose ensuring this better management? If ArbCom itself has failed to provide it, then the community has to guide it in some way.--Kotniski (talk) 06:17, 20 April 2009 (UTC)

"A bit out of hand", Dragons flight? The dates case is a farcical explosion of chaos, confusion, un-wiki angst, and time-consumptive crap. Several others I've seen also approach this level of festering uselessness, e.g., the repeated one - I think it's been here three times now - about TV show episode/character articles and related WikiProject controlfreakism and "microconsensus" that tries to carve out special niches immune to WP-wide consensus. I have to agree with Tony1 on virtually all points raised here. The only one I recall feeling a need to concede on is that ArbCom itself would still benefit from a workshop page, provided that outsiders were not allowed to edit it; the workshop as currently operating certainly should be "binned". And especially, without scope being explicitly limited from the start (with the proviso that the ArbCom can expand it as genuinely necessary) ArbCom cases are simply an exercise in forum shopping for new venues to tumidly re-air the same dirty laundry, practically endlessly. — SMcCandlish ‹(-¿-)› 10:34, 20 April 2009 (UTC)

Dragons, I believe your post is in good faith; however, here are my responses.

Chaos and time sink. Is "a bit out of hand" code for "chaotic"? The article you cite (Hoffman & Mehra 2009) points out in its first paragraph that the Darwin's/Lincoln's birthday case "generated over 30,000 words in evidentiary submissions and thousands of volunteer man-hours". They seem to be making the point that there's an awful lot of huff and puff for a trivial matter. (And sorry to be a logic-snob, but how does an ArbCom case "generate" man-hours?) But wait, we can beat that hands-down with the Dates case:

Application page: 7.8 thousand words

Evidence page: 23.3 thousands words

Workshop page: 121.3 thousand words

Grand total: 152.4 thousand words, not including significant overhead text, the associated RFC text, and the judgement text (pending).

A legal process or not? Now, you say "much of ArbCom's success stems from the fact it is fundamentally not a process of law". That's odd; the opening page of the article you cite states that the "Arbitration Committee ... hears evidence presented by the parties before issuing findings of fact and conclusions of policy and law". (My italics in both quotations.) Within seconds, the authors state: " decisions, organized by volunteer arbitration clerks and disseminated by volunteer reporters, have created a virtual Wiki-common law." Oops. Sounds pretty much like a process of law to me.

Flawed article. Problems leap out at the reader all over the place in that article. For example, Footnote 6 says "And sometimes the parties’ advocates". Tell me, to what extent were PMAnderson, MBisanz and many other self-appointed commenters "advocates" of the parties in the Dates case? But more fundamentally, ArbCom hearings are clearly described in the article (three times by the end of the second para) as a "dispute resolution" process, yet—oh dear—in the abstract, we are told "In effect, the system functions not so much to resolve disputes and make peace between conflicting users, but to weed out problematic users while weeding potentially productive users back in to participate." My head is spinning; and ... weed back in? Pardon me.

False binary: masses of flab or the truth cannot be arrived at. What bothers me about your post is the assumption that big and baggy and loose and unfocused is inherently good for the pursuit of ArbCom's goals—that any restriction on evidentiary freedom amounts to a curtailment of "tha truthe", a cloudy concept at the best of times. The limitation of this line of argument is that clarity, sound judgement, justice, and—let's be honest—the reasonable efficiency of the process, are egregiously damaged by acres of fluff, anger, irrelevance and the time sink. Your binary suppositions that these are a necessary part of an "open and flexible" process, and that any attempt to bring the system under proper, professional management would render it "closed, rigid", have no basis in evidence. This article you refer to is certainly not reliable evidence; it is seriously flawed from the outset. Tony (talk) 11:25, 20 April 2009 (UTC)

• To use a Parkinson's Law parallel, if you plan to accept chaos and bloat, that's what you will get. To ensure efficiency, we need to redesign the structured so as to deliver the desired result, and not close our eyes and hope for the best. Ohconfucius (talk) 14:59, 20 April 2009 (UTC)

Suggested changes summaries

I'm going to try and go through the above, and highlight out significant suggested changes, to make it easier for drafting purposes. --Barberio (talk) 12:04, 20 April 2009 (UTC)

This turns out to be a bit more difficult and time consuming on freeform discussion than I thought, so if anyone else would like to chip in to put up summaries of the above discussions? --Barberio (talk) 12:53, 20 April 2009 (UTC)