Knowledge talk:Arbitration Committee/Noticeboard/Archive 14

6952:

do with whether rulings are being "violated", but everything to do with the unfortunate attitude and values that some admins who work in that area appear to have developed). ArbCom are given the same message from the Community that you as admins are given: do not impose punitive measures and do not do so to make a point. You are here to help the Community and the project in achieving its ultimate purpose; not to focus on your own purposes or priorities which can conflict with the ultimate purpose. Your work is meant to supplement, not unnecessarily disrupt, tarnish or choke. ArbCom is expected to treat each user on the basis of the evidence and the circumstances; users are not mere symbolic pawn pieces to be played or gambled or to be used to make points. Most cases, like this one, are distinct. It is only after informal and other attempts are not working that formal and increasingly blunt measures are required. Here it worked fine, because based on the evidence, circumstances and communications which were submitted, including those generally between Dreadstar and ArbCom, a reminder was the only formal thing left to do for this user. Of course, you may have some other evidence about this particular individual, or you may have decided to make an unpleasant assumption about him; that's in your court. But I don't think one is justified in saying that a dispute is resolved only after the most harshest warning to the individual is used. If you genuinely believe that you are only going to be reminded if you do something like what he did (or what 2 other admins thought was OK to ignore in the past), you have the ability to test that theory by gambling with your reconfirmation (though I would specifically not encourage it, least of all, after people have suggested it was a waste of time in your case

7017:

evidence will know that I believe Sandstein's action was not a good one, regardless of its validity as an AE block). As for Dreadstar, I was among the first uninvolved editors to advocate against a desysop, but I agree with Sandstein that some sort of sanction or at least "or you will lose your bit" should have been appended to "don't do that again". What people have to bear in mind is that admins do not block editors (aside from vandals, who are fair game) lightly, and do so even less lightly under AE rules precisely because of how difficult it is to overturn an AE block. All that aside, though, what gets me hot under the collar is that you (ArbCom collectively, not you personally) took two months to come out with this non-decision. You would have wasted a lot less of people's time if you'd just declined the case or resolved it by motion. There is no excuse for this case taking as long as it did when the result is just a lot of hot air. I'll briefly address the discretionary sanctions point by saying that ArbCom should spend a few weeks enforcing its own decisions, becuase I think those of you with AE experience have forgotten what it's like "in the field", so to speak and because you will quickly realise that it's impossible for 18 very busy people to keep up with the demand. I'll just add that discretionary sanctions most certainly have their uses, but they seem to have become a substitute for, rather than a supplement to, meaningful dispute resolution, and now I'll pipe down.

10870:

risks open editing already exposes living people to. So admins need to be free to look at the circumstances of a case, and make a call - baring in mind the overarching principle. You can't write a policy page to cover all eventualities - so admins need to have freedom of action in defence of BLPs. Call that "idiosyncratic" of you want - I just call it flexibility to respond to unforeseeable circumstances. Sure, the call be carefully reviewed later. Often it is possible to say "well, OK, but actually we can do this, if we just do it this way instead." But what we must to is err on the side of extreme caution, till we've done the risk assessment. That's why an unreferenced negative bio gets nuked on sight. It may be that later discussion will show the contents factual and fair, but we don't publish until we're sure no one will be damned. It is the same here. Unflagging BLPs may turn out to be harmless, or indeed a simply check by one admin may turn out to be sufficient. However, when a risk is pointed out, we stop, err on the side of extreme caution, assess the risk, and then if safe proceed. Unfortunately, that was missed, which resulted in regrettable measured being taken. In the cold light of day, we can see other ways of proceeding, and have now done so. But the principle is right.--

2010:, talking to HJ. However, the converse is that we've proven there are true limitations to the current rights set that makes simply doing what CU/OS's are appointed to do quite difficult. For example, a suppressed edit that is to a deleted page is invisible to someone with the OS flag that is not an admin. I wonder if the same would be true while in the Checkuser interface- would CU refuse to display an edit that the operator didn't have the permission to view? I tend to agree that anyone with sufficient confidence to gain a CU/OS bit or be elected to ArbCom should be able to pass an RFA, but should they be forced to? These changes in the rights set have proven necessary just to make the tools work as they should. The other option is a blanket prohibition against any non-admin gaining CU/OS flags, which is a very divisive move- RFA is not a gate by which editors become somehow "worthy" to hold advanced flags- there are tons of fully trustworthy editors around this place who have no need or desire for the admin tool set. The other option is to sysop by fiat anyone who gets a CU/OS flag by ArbCom decision. And well, that would cause a riot from some sectors. (ArbCom elections could always be treated as a 9585:, an article that hasn't been edited in 9 months), but no one has provided any evidence that I was not using sound judgment about articles. I was acting with a quite strong consensus. Scott objected, and brought the issue to ANI. When the response at ANI made it clear that others viewed my actions as being within consensus laid out, I continued, and Scott blocked me for implementing that consensus, despite it having been made quite clear to him that his position was without merit. When it continued to be clear that he had no support for his position, he brought it to Arbcom. Now Arbcom is acting as if I was acting uniliaterally and causing mass disruption, and the answer they are providing is to deprive all admins of exercising any judgment in making protection decisions when getting this trial to finally end. Normally in a case like this, Scott would have been desysopped summarily the moment he filed the Arbcom report: instead, Arbcom is acting as if he was reacting to a threat to Knowledge, and rewarding him by handing him what he wanted, and I'm being asked to go through all of my decisions and undo them as if I everything I had done was in error. I find it sad.— 10910:

my concerns, once investigated, prove unmerited then the mass action could continue. The important thing was to get the admin to halt so that there could be a proper examination. In hindsight, although I believe my blocking was justified, it would been wiser to get someone else to do it (as it would have caused less brouhaha. I was foolish not to have considered that.). There should be no big deal about a short pause when someone is doing something to BLPs on mass, and another admin in good faith expresses concerns. Kww's refusal to stop was quite unreasonable. Your second rant about floodgates and judgements is beside the point. Admins make mistakes. Having an admin take the unprecedented step of mass unprotecting BLPs runs the risk of serious mistakes. The point of the injunction is to slow that down, if people must mass unflag BLPs then temporarily they should protect them, so the ultimate protection for each can be considered at a slower pace, which has a lower chance of making mistakes. Anyway it is moot now, I just hope the lessons have been learned by all.--

6790:

try to appreciate why someone felt it was necessary. When an admin is finding ways to unnecessarily escalate issues as much as possible, it is not helpful to either the Community, AC, or the project. Supposing an admin did not heed these principles and applied AE sanctions anyway, then (5) Remember that longstanding principle on reversing sanctions still applies. Supposing an admin overturned something without the requisite permission or consensus, then whatever action taken is unlikely to excuse the out of process action. Reblocking and/or desysopping would not stop bickering in this case because punitive measures are not endorsed by the Community (Newyorkbrad has also explained why desysop was not taken). At the end of the day, AE sanctions (as intended by the Committee rather than as intended by any single admin) are to supplement the Community's processes and DR; they are not to be used just because your actions are unlikely to be reversed when taken under that scheme. All of that is clear from the principles, Fofs and remedies; that's not the problem.

10953:

to be placed against Kww in this situation. Reducing BLP risk through discussion is important, but certainly does not require the use of force. For instance, you could have reviewed some of the removals of PC protection yourself to determine whether semi or full protection was prudent, and asked other administrators to do the same. Kww stated that he reviewed the articles himself when unprotecting, and applied conventional protection where necessary, but let's assume that's not enough. There were only a couple hundred articles left under PC protection when you blocked Kww. If all the administrative energy that had been focused on your block and arbcom case in the next several hours had instead been redirected to examination of the articles that were PC protected, the situation could have been quickly resolved, simply by splitting the articles to be reviewed into small, easily manageable groups. In the absence of an emergency, administrators should resolve BLP issues through discussion and cooperation, not brute force power struggles.

10564:

was mounted in the face of considerable opposition, and it gained consensus on the promise that this would only be a temporary. The fact that we have only now voted to end the "2-month trial" without there being a real analysis of the results against the original goal supports my view of poor project management. Yes, post-trial, there are legitimate fears sudden dismantling would result in chaos, and the arbcom motion can be seen as an attempt at an orderly wind-down of PC. However, considering the vote to end, the motion is a knee-jerk which seeks to perpetuate the "trial" by locking in some default parameters requested by Scott but undiscussed by anyone else other than Arbcom. Having nudged Arbcom into passing the motion that it passed, Scott now seems to be seeking to apply the letter of the motion in a heavy-handed manner. Arbcom must agree that that was not the intent, and must amend the motion. Otherwise, Arbcom's own credibility will go down the tubes just as that of the project managers of PC.

11000:. I assume that, had Kww continued to unprotect articles, you would have reblocked him again and again until you were desysopped for wheel warring, involved blocking, and block warring. This behavior is brute force power struggling, not cooperation with other administrators, almost all of whom strongly disapproved of your actions in the AN/I discussion and in comments on the arbitration request. You certainly made your point, but whatever negligible gains were achieved by ensuring that a few articles weren't unprotected for even a couple of hours are outweighed by the community goodwill towards you, and towards PC protection, that was lost. Why should you care? Because of the most potentially valuable uses of pending changes is to place many BLPs that have previously had issues under level two protection. We're talking about a large number of articles, not the few you were fighting over. But that can't happen until the community approves a policy to authorize it. After this fiasco, and 10567:

Then, had we done a proper study of the results, we would also know which articles can have PC removed without much ado. We don't, so now it will have to be left to interested admins to sort the wheat from the chaff. I don't envy them. The Arbcom motion is unnecessarily formulaic, and treats our admins were a bunch of machines. I say we should perhaps just ask Rich Farmbrough to send Smackbot in to remove PC in the manner prescribed, because such formulaic rules lend themselves well to this being an automated task to achieve the very unnecessary two-step proccess mandated. Slim Virgin is one of those prepared to get the bit between her teeth, and attack the problem in a sensible manner; Kww should be thanked and have his back patted for applying a bit of nous. I would thoroughly commend her on her efforts to propose a pragmatic and reasonable implementation. If we continue to have intransigence and bullying like we have witnessed, the only solution would be to say "

3291:

particularly sensitive admin work, and there are a good many practical advantages (for example, it's nice for an oversighter to be able to delete pages). However I don't view this as a requirement for ArbCom or AUSC (hence my support for the technical change, also for a few other minor reasons). Regarding at-large AUSC members, I think they should be elected together with arbitrators in the annual arbcom elections. Regarding the regular CU/OS appointments, it's true to an extent that an election may not have been the best appointment process, but I think the way this is practiced now doesn't invite enough community participation, whether you want it or not, people will be more inclined to participate if they can make a 'vote' that can make the difference. This is why we could have a confirmation vote, with a majority needed to confirm the candidacy, but whose comparative results doesn't bind arbcom appointments.

3468:(that is, access to who CU'ed who when) without the ability to rerun checkuser actions to verify that the conclusions reached followed logically from the findings would be sufficient for a non-admin Arb or a non-admin audit subcommittee member. Fundamentally, if we take away the "admin" bits, an auditor-like role could oversee other functionary use of the tools, without actually having the ability to initiate e.g. CU's on their own. While some appear to have assumed that no non-administrator could be appointed to CU or OS, the committee has not seen that as a barrier--one of the top three most recent audit subcommittee community applicants, based on both community feedback and ArbCom validation of that feedback, was a non-admin. Now, he appears to be well on the way to having that level of confidence confirmed by his own RfA, but that's somewhat beside the point: it wasn't a showstopper. 9477:

those who want to go through and de-flag all articles to go ahead and do just that - but in a manner which does not lower the protection on any article. In many cases, the protection level can be removed or lowered. That can still happen, in the usual way, on a slower case-by-case basis. I'm the first to say that long-term full-protection is seldom if ever appropriate. With problematic underwatched BLPs a better response is to get them on several watchlists. That's what I've now done with the flagged articles I was tending, and I've removed the flagging now. This motion is a win/win, because it separates the desire to remove all flagging from the need to treat BLPs carefully on a case-by-case basis. If an article has been protected due to BLP violations, or (as in at least one case) because of an OTRS complaint, there's time to stop, think, consult, before lowering the protection.--

1967:

them and review those edits/actions for themselves. The community has been clear that it will seriously consider good candidates, whether administrator or non-administrator, for the Arbitration Committee; there is no requirement that arbitrators be administrators, never has been, and the community has discussed it in the past and chosen not to add that restriction. Being an arbitrator has little to do with blocking people or deleting pages. HJ Mitchell, many checkusers leave the blocking to independent reviewers, particularly when doing SPIs. I note that neither of you have bothered to address the point that permissions should stand alone and not be dependent on other permissions, which is pretty standard in most systems. And, having watched RFA for a long time, I'm not terribly persuaded that it has much to do with trust at all, but that's my personal opinion.

5079:

there has never been a requirement that Checkusers, Oversighters, AUSC members or Arbitrators be administrators, and there is no correlation between the activities of checkusers/oversighters and administrators. Now you're saying that there's a trust issue, but RFA has very little to do with trust; it has to do with whether or not the candidate knows what A7 is, and what percentage of their edits were made with automated tools, and whether or not they've written "sufficient" content. Lack of trust is rarely identified as a reason for opposing at RFA. This is process wonkery. Toolkits should include all the tools needed to do the job. The fact that both Checkuser and Oversight permissions were cobbled up many years ago very quickly because of an urgent need should not prevent them from being reconfigured properly so that they do what it says on the tin.

3590:

little bit different, but CU's are authorized to handle confidential about users, so I'd think they can also be trusted with deleted pages. But giving deleted page access to OS's while withholding it from CU's would in any case serve AUSC's purpose since AUSC members get both permissions. I also like the idea of letting auditors see the audit log of CU access without seeing the actual CU results, though the log itself is also privacy-sensitive. Finally, IMHO, re the appointments, arbcom made good choices. At least going by the candidate statements, Bahamut and Keegan seem like the best qualified (some others were pretty good too of course). And for "cabal"-phobes, Bahamut and Keegan's apparent prior relative non-involvement(?) in wiki-politics actually makes them more attractive as outside monitors.

9884:(ec) Indeed, the OTRS number is a pointer to a reason, not a reason itself. By listing an OTRS ticket in BLP protections I've done, I've intended to convey that 1) it is a good reason, 2) it's available to approved OTRS agents, and 3) people who need to know should refer to OTRS. I've always seen OTRS as a good place for this--if I get hit by a bus, no one knows why anything done "per Jclemens' conversation with the subject" really happened. Since the discussions are conducted through OTRS, any appropriate admin can pick up the conversation (including with the BLP subject) right where it left off. I'm still interested in hearing why anyone without OTRS access would think it's a good idea to unprotect such an article rather than referring to someone with OTRS access to read up on the history, first. 8859:

the trick. Article titles are an area that should be clamped down on hardest, granted, but that can easily be achieved by having a more severe penalty for article name related disruption. As far as I can see, Arbcom has not taken any action outside of article titles, yet on article titles it has gone far beyond that. Furthermore, it asks admins to proactively enforce it; a red rag to wolves who would take any opportunity to cry for help. In its current form, this will most likely shift the dispute from article titles to article text. Meanwhile, Wikiprojects that have reached clear consensus on dashes are mandated to leave inconsistency be until those entrenched in the issue resolve their differences. Editors who like to make use of page moving as a quick way of creating redirects can no longer do it.

11192:

might be good policy to check with the protecting admin. That is all fine, and always has been. The unique circumstances here was that admins were doing this not because "hey this article might be better with this particular protection" but because they were determined to remove all flagging by a strict deadline, and thus were removing it from multiple articles at once. That isn't normal, doesn't allow for the usual cautious pragmatism, and arbcom were really saying "if you are intent on doing that, to remove the protection by a strict deadline, just give the BLPs maximum protection, which can be reviewed later (as is normal) without any time pressure." It was a sensible measure for a unique (and time expiring) circumstance. It shouldn't stop any admin doing what any admin would usually do.--

6785:

to stop letting it arise (which I presume you term as 'the obvious'). That is, if it does arise, it reflects poorly on ALL involved; not just a single party. (1) When asking the Community for assistance on a given issue at a noticeboard, avoid inappropriate remarks. In the event this was not avoided sufficiently for whatever reason, then use clear communication and have the comments redacted, (which was incidentally, the step Dreadstar took immediately after the unblock - unfortunately, that happened too late in the piece, because discretionary sanctions were invoked). To avoid invoking discretionary sanctions unnecessarily, admins need to remember: (2) Discretionary sanctions must be used with caution where the Community is already dealing with the specific issue; seek input

6727:

mention of reducing discretionary sanctions, only a passing mention of the burden they place on admins and token support for the small group of admins who voluntarily devote hours of their time to cleaning up your mess? You should all be collectively ashamed of yourselves. Although my presence there will not be missed nearly as much as Sandstein's (whose loss is something AE will very quickly come to lament), I will also be parting company with arbitration enforcement and I would urge other over-worked admins to let ArbCom clean up the mess their pontificating creates. I have the utmost respect for the dozen individuals who heard this case, but they have collectively dropped the ball and I have no confidence in the ability of the current ArbCom to do what it was elected for.

6369:, without which no useful work at all can be done in an atmosphere characterized by, to quote the decision, "bitter long-term editing disputes and involving intractable and strongly opinionated editors". By not enforcing their own procedural rules, the Committee sends the message that they do not value or intend to support the volunteer work done by AE administrators on their behalf. Consequently, as I have already said during the case, I conclude that AE work under this Committee is a waste of time, and will no longer process AE requests. I may still use discretionary sanctions as a matter of convenience to deal with disruption I happen to come across, mainly because they allow for solutions other than blocks, but I am no longer under any illusions as to their authority. 10880:

neither acceptable, nor even useful, since the block may be quickly removed, as it was here. Instead, you should contact a steward on IRC, and request an emergency desysopping. Such requests are generally acted upon within minutes. The benefit of this approach is that it doesn't hold your own judgement of the matter as superior to other admins. Instead, a neutral, highly trusted third party will determine the correct course of action. If the situation actually constitutes an emergency, the offending administrator's activities will be halted in a way that can't be reversed until arbcom reviews the issue. Alternatively, if the steward declines your request and asks you to calm down, you can be assured that the matter wasn't as serious as you had thought.

6382:

the Roads and Iridescent – even took the liberty to simply ignore the case, even though they were otherwise active on Knowledge. The fact that Ludwigs2 is now both "cautioned" and "reminded" (both of which remedies are of course equally pointless) makes the remedies appear even more random and meaningless. Additionally, because the scope of the case was never made clear, the participants in the underlying pseudoscience-related feuds happily junked up the case pages with what must be megabytes of irrelevant petty insults aimed at one another, without little if any intervention from clerks or arbitrators. The Committee therefore kindly provided a forum for just the kind of disruption that the decision I attempted to enforce was intended to prevent.

9502:

been set explicitly due to BLP violations, and in at least one case with reference to an OTRS ticket. Any such should not have lesser protection without at least a careful inquiry as to the problem and an insuring that we don't open up a particularly vulnerable article to problems - particularly if it is underwatched. In such cases, notifying the admin who set the problem should be a minimum. Already we're seen two mistakes in what Kww was doing. Two problematic articles that were unprotected without seeing the problem (one OTRS related). I'm not blaming him, it is an easy mistake to make when you are coming at this from a mass-article approach. I suspect the number of articles that this will apply to is very limited, but we do need some care.--

7885:

combination of experiential acumen and popular approval (i.e. they've been around for a while, learned the practice and the philosophy primarily by digging in and participating rather than by studying, and earned respect from a broad range of others in the process); that fits better in my mind with a tribal modality than a more sophisticated bureaucracy. Plus -pragmatically - in a real mandarin-style bureaucracy the political tactics I consistently see used on project wouldn't work; there'd be an entirely different set of political games in play. Although, I suppose that given the nature of the project as an encyclopedia, there's a natural scholarship link; people with scholarly interests are more likely to participate and more likely to

4979:

effect on this issue. Requiring adminship for CU/OS rights is about providing enough feedback and scrutiny for candidates to a position which is highly sensitive. It's absolutely clear that the review made at RFA in addition to the review made during the AUSC appointment can provide much more feedback and scrutiny than just the review at the AUSC appointment. Also Jclemens, I don't see the 'silent majority' argument, why those who didn't have a problem didn't show up in Bahamut's appointment but they do show up here ? The explication stands rather in the lack of interest for the AUSC appointments due to the marginalization of the community participation in the process, it even more justifies use of RFA in addition.

6971:

those people that Dreadstar's unblock was just a normal administrative action (albeit still with some controversy). I can tell you that I personally tried to read as much as I could in regards to the Evidence, Workshop, etcetera. As for your proposals, I'm all ears on how to tone down the use of Discretionary Sanctions as a panacea or cure-all, while still giving administrators and the community a way to handle problematic topic areas and editors without requiring month-long (or longer) arbitration cases constantly. I think the idea of Discretionary Sanctions are a good way to provide administrators the flexibility they need in some areas, but if there are better ideas out there, I'm certainly willing to hear them.

11024:

did not share them, then a pause and discussion would have revealed that. There was no need for hurry here - except artificial deadlines. But we're going over old ground here. As for the removal of reviewer rights - the problem wasn't the removal - it was that there was no policy for granting them and they were being given out like cookies to people with no real clue (and who incidentally never asked for them). That's what made the whole trial so useless. If it isn't repeated, that's fine by me. If it is, you need to start be defining who gets rights, before you worry about how they are to be removed. Personally, I think the whole PC thing is a total waste of effort anyway wrt BLP, but that's another issue.--

8374:

take forever. To take a look at cases handled by the current ArbCom, we have three new sets of discretionary sanctions, which is really passing the buck to admins; we have AE sanction handling, which wasted lots of people's time to produce a result that is essentially meaningless; and now we have the Racepacket case, something that needs to be addressed quickly, in its third week and apparently due to take another two. It's not my place to tell the arbs how to spend their collective time, but if it was, I would suggest they focus more on resolving disputes (which is what they were elected for) and less time making meaningless rulings about procedures the majority of people really couldn't care less about.

10983:

should have checked every one of his 70 odd unprotections after the even is just silly. It was better to have a slower process. Kww should have stopped and discussed when reasonably asked (even if it turned out my fears were unjustified - there was no loss in a pause.) The block was justified as it was aimed at improving things for BLPs - it was perhaps unwise to do it myself, since it created a commotion (I'll not do that again). The notion that Kww should have been emergency desyopped is patently absurd - that would have caused 10000% brouhaha than a simple, quickly reversed, block. And, really, so is this discussion. Think what you want - I really don't care now. Unwatching.--

11225:

protection changes would be in its scope, but given the arbs don't seem interested in looking at your abuse of tools via wheel warring, handing out blocks against administrators enforcing consensus and despite being involved, removing permissions despite being involved and other examples of "sod the community" in a futile attempt at overriding community consensus, I am not seeing any real purpose for Arbcom to be involved in the slightest. In the end, my comment above is apt: ArbCom needs to show some common sense and learn that it should not exceed its mandate. They were not elected to govern Knowledge. That is the Foundation's job. Not theirs, and certainly not yours.

5317:(to Xeno) Okay, thanks for that information. I know for my own part that I don't comment in these places because the ArbCom is making the decision, so it's not clear what the value of input is. Also, I think it's unfair that candidates only see anonymized comments. They should be allowed to see who wrote it too, because that often makes a big difference. I've gone right off the idea of people corresponding privately with the ArbCom about other editors, where the latter are not allowed to see it. I used to support it (speaking as a writer and as a target), but it's been misused so much I really wish the ArbCom would put an end to it, except in the most extreme of scenarios. 9453:

expressed in their edit summaries. Since the process has now gone on past the target date, I can understand if some people rushed at the end, and the ArbCom announcement sounds like reasonable advice for people who don't have the time to figure out what the situation is with individual articles. With the notable exception that generally Pending Changes articles were protected for an infinite duration at the technical level, and for a two month test duration ending last year at the policy level, making the "equivalent duration" a hard thing to figure out. They should just have specified some fairly short fixed term and left it to be reviewed case by case after that.

10518:. This was part of the proposal, and the closer's discretion cannot go against that, the closer has no line veto; of course admins had to be watchful of BLP issues when evaluating the level of protection required (and if it's otrs), as always. Now because an admin made several such transitions in order to apply the consensus and among them two mistakes, he got blocked, this silliness got to arbcom, and arbcom made a swift rigorous injunction in order to appear tough on BLP. But unofficially arbs say that we can apply discretion subsequently. That's again an injunction for nothing but political interest. Keep going with such zeal, and PC will never be a reality on WP. 7175:(in the sense of independent judgment) AE administrators are supposed to exercise. Furthermore, it greatly complicates the resolution of disagreements about the block, since the question of whether the block was wrong is then automatically shifted to an arbitration case rather than to a simple appeal discussion. Finally, it introduces great uncertainty, because it makes the decision of whether or not to desysop the unblocker dependent on whether the original block is deemed correct or not, which is something that people can in good faith disagree about, rather than on the much more easily answered question of whether a block was undone without consensus. 2699:, it's outside of your jurisdiction). So please, respect the community, stay within your role, you just need to consult the community on this specific point, it's no big deal. Additionally, there's no pressing need to have the matter resolved since Bahamut0013 is about to gain adminship. Finally, as a general request, I'll ask that before you make decisions, especially outside formal arbitration cases, you make sure that (i) it is within your authority (ii) it is not made in order to achieve a political goal (by political, I mean the question of what should be the WP policies, which is a matter for the community to decide, with a few exceptions). 6404:

administrator based on comments by several editors who disagreed with your sanction, coupled with the other admin's own view of the situation. This, as we have reaffirmed, was not a sufficient basis for overturning an AE sanction, which we have emphasized requires a consensus of uninvolved administrators, not a few passing comments on a noticeboard. But I thought, and my colleagues agreed, that we had sufficiently emphasized the point that AE sanctions may not be overturned unilaterally by obtaining an assurance that the administrator in question would not repeat his action (which he has not), by admonishing him, and by reaffirming the principle.

6666:(responding to Skinwalker) To be clear, I wasn't saying that the incident that led to this case was isolated in the sense of being the only questionable administrator action that Dreadstar ever took; I meant simply that it was the only instance in which he had improperly reversed an AE sanction, and I don't think anyone has disputed that. With regard to your broader evidence, I didn't think we needed to get into it to resolve this case, in part because (as noted above) many of the incidents you refer to occurred some time ago. I do hope, and expect, that Dreadstar has considered all the points you made and will bear them in mind going forward. 10943:

nothing to do with "disruption" or with Kww. Risk should always minimised, and especially on BLPS that ought to be the aim of all of us. And we should always be willing to stop see if that can be done. I was of the view that the mass unflagging was a risk that could be reduced through discussion. Stopping the action was thus desirable in order to minimise the risk. No one is "suspending admins ability to exercise good judgement" - what is being said is that slightly slower actions, with a pause for review, is better judgement. You seem to be of the view admins can't improve what they are going, they should always be open to that possibility.--

6928:(responding to various comments above) I expected that ArbCom might show some indication that they listened to ahything that has been said in the last two months. It took me three hours to write up my comments on the evidence page and another two or three to come up with my proposed decisions in the workshop. I'm not naive enough to believe that ArbCom were going to be hanging on my every word begging to impliment my proposals, but I expected they might at least take them into consideration. If the result was going to be a bit of a bollocking for the two admins involved and no change to anything, then they should have done that two months ago. 7102:

interested onlooker was "There is fifteen Arbitrators, but everyone assumes you speak with one voice").. when the truth of the matter is, like any other group of editors, there's no groupthink (at risk of stirring up long dead memories, ArbCom is not a hivemind). We see problems differently, we think of different solutions for problems, we have different visions for the project (in the details, at least). Sometimes we disagree with each other as to handle a case, so then we have a case decided by the committee, which in general will not please everyone, and sometimes anyone, but it's the least worst thing that we can all collectively accept.

9644:. Articles which have not been edited in months, much less vandalized, are not generally left protected forever. You acted as if I was some kind of threat to Knowledge: I wasn't, am not, and will not be. This injunction is a case of Arbcom reacting to the wrong thing, and it saddens me that you are going to feel empowered by this decision as if you had some kind of justification for your actions. You didn't. You wheel-warred and blocked me invalidly, all because you didn't understand that PC was coming to an end. Your misreaction has now generated much worse problems, as we now have Arbcom dictating an invalid protection policy.— 3720:

big deal. Bad person A writes something, user B notices, Admin C revdel's and contacts oversight, Oversighter D removes it from admin view, and audit subcommittee member E reads it later. Actions of A, C and D are logged, but B is not (and B may be Google's indexing service). While B may have a time-limited window and E does not, what, precisely, is E going to do with something which was posted publicly then oversighted to cause harm to the project? I get that a lot of stuff is icky, nasty, defamatory, whatever... but not how access by one or more non-admin oversighters will make a significant difference in the risk profile.

6931:

and nor is allowing an admin who so clearly violated their own precious ruling to get off scot free (I'm not advocating a desysop, but something more than "oh, that wasn't great, don't do it again because if you do we'll be cross"). ArbCom have failed to take action against someone who vioalted their own ruling, they have failed miserably at resolving the dispute and they have wasted many hours of the valuable time of dozens of editors. So, given that, how can any AE admin expect their block to stand up now and how can editors have any confidence in the current ArbCom? Can I make a motion of no confidence in ArbCom?

9321:

days. Moreover, pending changes, like protections, are subject to reevaluation by and admin at any time, with possible outcomes including shortening the time a protection is applied and removing the protection all together, (especially if the admin that placed the protection no longer sees it as necessary). This injunction dosen't change this. It states that when PC goes down, protection of other means goes up, but says nothing about what is done to that protection afterwards. If someone really is worried here, a request for clarification should be filed, asking about the terms of these new protections.

6449:

send the message that the Committee takes AE seriously. But this message was not sent. Consequently, the bottom line for administrators working in AE is, your actions can now without consequence be undone on a whim and with no communication, and if you do not like this, you can spend a ridiculous two months litigating an arbitration case to arrive at the very same non-result. This is what every admin in AE now needs to be ready to repeat if they take any AE action. I'm not ready to waste another two months on this, so I'm leaving this area of admin activity. Good luck dealing with these people yourself.

5793:

edited) proves that ArbCom's selection and vetting process works. They were elected because the community trusts them to do things in thier name, most of which are highly sensitive. The AUSC committee was formed to help them do thier job of policing the CU/OS crowd, who were likewise vetted and elected (as well as the functionaries they are policing); it was a lack of interest in the most recent election that changed the method to appointment (further highlighted by complaints that the 2011 appointment process got limited community participation). The ArbCom has the trust of the community (albeit with a

6794:

come up with such a process on the spot; that would require work outside of the case. However, only arbitrators can respond to the anticipated questions which lead on from that: Are AC going to reduce reliance on DS, and if they are, why was no formal indication given in the case? If they aren't, why not? Does AC plan on doing work on an appeals process for DS (particularly short blocks like those found in this case, and shorter ones than that), if they are, why was no formal indication given in the case (or if they are, is such a process actually going to be worked on)? If they aren't, why not?

11099:" Your (Scott Mac's) statement seems to indicate you are on some sort of a high horse. I think Chester's assessment is spot on. You cite some BLP emergency, block a fellow admin who was by all accounts acting in good faith but who you disagreed with based on some notion that it was the other party and not you that needed to calm down. Kww demonstrated that he was prepared to discuss the matter, only not to a level satisfactory to you. I see it as a legitimate difference of opinion – Kww thought you were being overcautious, and you thought he was being cavalier with unprotection. You raised 7781:-style site (where each individual dons his/her helm of self-righteousness and sword of petulance and sallies forth to do meaningless battle with the forces of perspectival darkness and ignorance - essentially World of Warcraft without the graphics, and where no one thinks it's a game). But one hopes that's not the case, and if Knowledge is to avoid that fate it needs to set itself above and beyond that kind of behavior. I'm not making a judgement, mind you, I'm just noting (as a professional in this particular discipline) that the project is sooner or later going to have to 2535:

Again, there were no objections to a non-admin serving in this capacity. It looks like you didn't get the memo, so could you please cut to the chase and state plainly whether or not you think a non-admin, and in particular Bahamut0013, is suitable for the audit subcommittee. The technical change is merely implementing that appointment. If there is ever another non-admin candidate for these groups, it will be advertised just like any other candidacy; if the community doesn't want non-admins in these groups, they will have an opportunity to say so.

195:

always been a reasonable expectation of privacy throughout the appointment process, and it is incumbent upon the Arbitration Committee to uphold this commitment by keeping information about individuals who did not complete their application, applicants who did not move forward to community consultation, and candidates who were not appointed, in strict confidence. That being said: during any appointment round, applicants or candidates who do not move forward are welcome to request further information or constructive feedback from the committee. –

2961:

the move; but then it's not 'just a request', since according to you it reverses the burden of consensus. And no, the configuration of the CU/OS rights is certainly not under the purview of arbs, it's under the purview of the WMF and their devs; and they'd never give arbcom the 'purview' to configure such highly sensitive permissions. The community can decide to add some existing rights to the CU usergroup where it makes sense, but certainly not arbcom which has no authority to make bug requests on behalf of en.wp.

3349:

is this appearance of cabalism at the top; and it doesn't matter whether it's accurate or not—we know it often isn't accurate—but the perception of it increases every time there's one of these proposals aimed at a specific person or group. Please, let's just stick to the system we have. Almost everyone who really wants to succeed at RfA does so in the end, if they keep plugging away at it—so for one person simply to refuse, but to ask for the higher permissions anyway, that's not something we should encourage.

2732:

advanced privileges. The community has delegated to the committee the authority to oversee the use of advanced permissions (granting, removing, ensuring policy compliance, etc, a task which due to its constitution is not suitable for the community to do directly), it does not extend to changing the actual permissions. I am still puzzled as to why you do not want to consult the community. The list below proves my point, fr.wp requested the changes as a result of a community decision (linked below), it was not

9913:

for protection. Unless I've missed it, there has never been a consensus for indefinite semi-protection on BLPs that are not chronically vandalized. There were not any rejected anonymous edits during the course of the Pending changes trial, and no apparent history of heavily vandalism with the article at all. There's one oversighted edit in January 2010, and there was one anonymous editor that blanked it several times, but stopped quite a while ago. Given that history, what protection level is justified?—

7720:- but it should be the Arbiters' prerogative to say that it is not important and preclude it. Everyone will obviously be entitled to make necessary criticisms of other editors as they arise relevant to the case, but it should be the Arbiters' prerogative to determine what is and isn't relevant and where valid criticism should be blue-penciled out so it doesn't inflame tempers and start to reflect badly on the system as a whole. Remember, polisci 101: placing restrictions on what people can do is the 10825:

does not require freezing editing of the site. If an administrator is recklessly unprotecting articles in a manner which, evaluated against the community developed protection policy, portends an unacceptable level of future BLP violations, arbcom may intervene with emergency desysopping. But the committee should not use its power to rewrite the protection policy, force compliance with its rewrite, or countenance involved blocking due to simple disagreement with good faith administrative actions.

5297:

inclined to participate because their participation has no clear weight on the final decision. A possibility would be to have a confirmation vote, i.e. users need a majority of support to be confirmed as candidate, but the comparative results between confirmed candidates doesn't bind in any way the final appointments by arbcom. This incitement would provide for more participation, and therefore scrutiny, comments. Regarding AUSC, I think they should be elected during the arbcom elections.

35: 5766:"not a chance in hell" closes. The landslide approvals see many administrators giving weak reasoning. To me it appears like a "old boys club". Having someone on the "review" board that is not part of the club gives the community at large an opportunity to select someone they trust to review the CU/OS decisions should a objection be raised. I liken the community non-admin representative to the role of the muslim familes controlling the lock and key for the 2547:

advanced permissions? (I would be remiss if I didn't point out that the "reviewer" permission already exists today, so you could use that for this user rather than unilaterally changing permissions without discussion. I still don't think that would be a good idea, but it's an available technical means.) Unilaterally doing controversial things is one of the reasons that arbcom is thought of as being aloof and elitist, and is not particularly trusted. --

10448:

left and right, attempts made to community ban arbitrators, etc. While I have faith that stewards would exercise good judgement to eventually reign in a rogue committee, there's no need to escalate the conflict to that point. It's only a thousand articles, and half of the arbitrators will probably be voted out in December. That should be sufficient to send a message to those remaining on the committee that the will of the community must be respected.

9659:

by involved blocking to forcibly escalate the situation to arbcom, requesting action squarely in opposition to the community. Scott, how much cooperation in BLP-related efforts do you expect, after resorting to such high-handed measures? You will never be able to enforce the policy by yourself. Your best option would be to ask arbcom to reverse the motion, apologize to the community, and resign your administrative privileges as a gesture of penance.

3759:

I'm excluding meta/WMF assignments of rights.) This would include AUSC, because as of current practice AUSC members are appointed by arbcom, and while users can make comments, the selection is made by arbcom, not the community. (And it's unlikely to change in the short term, fully electing AUSC members would require a modification of the arbitration policy.) When the policy issue will have been clarified, we'll see more clearly the technical issue.

5747:

enforced by the software. So, I don't see it mattering much what the software does in a non-admin CU situation, if that situation can't happen due to policy. By now, editor are thinking hard enough about the policy question that I think there's not much chance of a non-admin CU appointment happening "under the radar" anytime soon. Therefore it doesn't much matter whether the code change is made or not made before the policy decision concludes.

6410:

clear that this case would end without a desysopping, and I don't see that our forebearance has had any negative effects at all). In that context, I thought that desysopping Dreadstar for a single, now acknowledged mistake would have been an overreaction that would have deprived the project of a competent, active administrator while yielding only a symbolic benefit that very few editors, other than yourself, seem to have believed was necessary.

1528:

or tell them to request help, or provide them with help if they are making slow work of it, or have someone shadowing them ready to take over if needed. I think you will also find, with the number of arbitrators, that some work slower or faster than others. The key is to really learn from drafting cases and hopefully see drafting arbitrators improving with subsequent cases (but please don't let all drafting be done by just a few arbitrators).

7573:

uncomfortable with being asked to do so. (There was then general agreement with the argument that the request in question would be outside of the scope of the clerks' role, and I think that the full implications of the request were perhaps not realised at the beginning of the discussion. That is to say, I don't think that there was some attempt at subverting the limitations on the role of the clerks.) The role of the clerks is precisely

1583:

the other hand, a case moving to a proposed decision and then we hear "wait a minute, please, my evidence isn't done." Thus, a fair deadline, at least a tentative one, is helpful to the parties. Note that it's a target date, not a rigid deadline; if some evidence comes in later, our position isn't "that evidence is late, so it will be deleted/ignored" so much as "we can't guarantee we'll all see it before we start drafting and voting."

4477:, that Bahamut wasn't an admin. The process is a bit mysterious to people I think, and I'm guessing editors feel a bit disenfranchised. I know the reason I don't comment there is that it feels pointless (wrongly, I accept that, because it's self-fulfilling), and it's not at all obvious why Bahamut would have been chosen (again, no disrespect to him intended). Also, the issue of private comments to ArbCom is quite problematic. 1587:

though of course they can slip sometimes. Interestingly, in three of the four cases I've wound up drafting this year, we've wound up extending the original target date not because of holdups on the arbitrators' end, but at least in part after a request for more time by one or more of the parties to the case. Such requests are evaluated on a case-by-case basis, but as one can imagine, are often honored when they are reasonable.

6975:

short of having your mop taken away from you, I think the hubbub that happened here would in itself be a deterrent.. I think that having to go through a Arbitration Committee hearing admitting from the first that your behavior was not optimal (apologizing), and that everyone would spend the next two months calling for your (theoretical) head anyway.. I almost think an instant "Take my mop away please" would be preferred.

2788:) using the abusefilter. This is a content ruling, absolutely outside of arbcom's remit, and the suggestion to use the abusefilter to control content is appalling, I don't understand why there hasn't been more consideration given to objections by fellow arbs (note that the community never followed the advise). Another case which worried me is when several arbs wanted to formally request that the toolserver management " 4380:. The community was asked to scrutinize and voice their opinions or objections to all the candidates and were given the opportunity to object to bahamut's candidacy for the Audit Subcommittee on the basis of non-adminship. The Arbitration Committee voted on the candidates after reviewing all the comments submitted publicly and privately and and all other relevant factors. bahamut0013, having met the 10672:

was simply set as a test and could be removed without any consequences, in a few cases it had been set because of extraordinary BLP issues, and it was important that consideration be given to what, other than PC, was needed to safeguard. As the person who sought (and welcomed) the injunction, I'll admit this one was probably overcautious in most cases, and has now probably outlived its usefulness.--

7918: 1766:@ Beeblebrox, you seem to have misunderstood my comment. I do not doubt that "these are the new procedures" but that they will be consistently enforced, given that similar policies have been stated but not been enforced in the past. What further assurance would I like? For a start, a simple statement that the clerks will be instructed to consistently enforce these policies would be reassuring. 10347:"Arbcom/foundation actions of which the community strongly disapproves are harmful to a community-based project."? ArbCom is part of the community. In any case, I'm not convinced that it causes any harm to ask that admins apply some form of protection if they're going to remove Pending Changes from BLPs. Quite the opposite. It seems like simple common sense in light of our current policies. 2780:

community trusts arbcom to a reasonable extent, provided that it stays within its role. Most of the big controversies around arbcom resulted of arbcom going outside of its role. I've long been concerned by this, over the years I've seen several decisions which were going way beyond the role of arbcom. I won't expose the well-known ones (e.g. the ACPD), I'll just give two examples. Arbcom in

4783:

be given to CU/OS recipients automatically--strikes me as so far off base as to be characterized as insanity. Ditto the complaint about someone's candidacy for functionary status not promoting the absence or presence of user-rights. No person engaged in this discussion is insane or asinine. Everyone here is acting in good faith and all that. I'm just talking about positions staked out.

3815:

specifically, active in areas where CU/OS are needed, such as dealing with sockpuppets, vandalism, BLP issues. But if it's going to be given to non-admins and non-Arbs, that may mean it'll be handed out for reasons other than need, and I think that's the worry—what exactly the criteria are, who's deciding them, and what are the risks, if any, of bypassing the RfA/Arbcom election processes.

5169:

argument against requiring RFA is convincing, so I'll cease from arguing in favor of requiring it. Instead, I will in the following months make proposals for increasing the community participation in the CU/OS appointment process, and propose that 'community representatives' be elected alongside arbitrators in arbcom elections (not any time soon to avoid fallout from this discussion).

10433:

was not mentioned in the injunction. So we should assume that we can immediately after apply discretion as usually (that is, after a review, with regard to the article and protection specifics, in accordance with the protection policy), and as pointed out above arbcom indeed would have no power to exempt those articles from the protection policy. This injunction is just a hype.

9741:

semi until either that admin is given a chance to review, or at least until another set of eyes looks at the article. If the BLP is underwatched, removing flagging for semi protection, at least has the potential for problems from confirmed accounts. It would also be good for the deflagger to watchlist any BLP articles, so that they see any problems their action might cause.--

3064:. If someone is trusted to be a CU, they're trusted to be an admin - although it does bring up "why do we allow resigned, retired or kicked-out-at-the-last-election'd arbitrators to keep associated userrights, userrights normally granted after a display of community trust, when the fact that they weren't re-elected or don't hold the associated role any more indicates they 2105:

see CU/OS removed if not used regularly. So if this were happening as part of a general reform I might feel differently about it, but even so there would have to be an election at some point: either an RfA, or a CU election, or an ArbCom election. It's not a good idea for ArbCom just to pluck editors out and give them higher permissions they've demonstrated no need for.

11009:

long-term policy for the use of PC protection will be very difficult, if not impossible. The result of delaying or never having a long-term plan for implementing pending changes protection will be more harm to living people, and the degradation of Knowledge's reputation. Given your obvious concern with BLP, this isn't a result you would like. So don't let it happen.

5500:. The applicants were vetted by the committee prior to the candidates being announced. One of the queries in the vetting process was whether policy requires a user to hold administrative rights before they may be granted advanced privileges. It does not. As there were no issues preventing bahamut0013 moving into the candidacy stage, we presented him as a candidate. – 5828:

concern—it's that decisions are made potentially affecting the community (as in this instance) for which no one is held accountable because decisions are made which are not transparent to the community—or if the decision is transparent (what it is, who made it), not all the criteria are transparent, again, making the decision ultimately still non-transparent.

718:

centrally tracked, logged actions to demonstrate response to community requests. If a functionary is only doing a few requests here-and-there for Wikifriends, however, the assurance that their use of advanced tools is serving the community and project as a whole is lacking. Note that I'm commenting for myself, not the committee as a whole in this assessment.

11131:

me nothing to do with larger consideration of PC, it was merely to do with a pragmatic approach to the articles before me. But way to assume bad faith. Anyway, I'm now repeating myself, and as you are evidently simply looking for stones hurl at me rather than a genuine attempt to understand my thinking, there's little point in continuing. You may have the

10239:, two things which are often sorely lacking with this project, and, in the case of BLPs, the lack of such can and have caused serious problems. If you admins took protection of BLPs seriously enough, then this wouldn't be necessary. To be fair, there aren't enough admins with enough time to police all BLPs, which is why pending changes is necessary. 7577:. Enforcing conduct standards is perhaps the most adventurous thing we do today. It may be that, as a clerk who joined the office some years ago and under a very different Committee, I am a little 'old-fashioned' in my views; but I would not accept any evidence-vetting by the clerks. A sounder model might be forming another sub-committee, or another 6352:

month of stress, nothing of any consequence happens thanks to A's facile apology at the very outset of the case, while all of B's own minor mistakes are leisurely scrutinized for two months. And then, of course, C comes along and undoes another AE action of B, who then has the option to do nothing or to start the two months cycle all over again.

11037:. If you believe that "the whole PC thing is a total waste of effort anyway wrt BLP", then there was no legitimate reason to create such a fuss over the removal of PC protection, since you claim pending changes was of no utility in preventing BLP problems, at least in its present formulation, as "the whole trial" was "useless". As many editors 1508:... Which is what I thought I was answering. Let me try again: By establishing a timeline, we're looking to prompt all participants (parties, uninvolved evidence providers, clerks, arbs, etc.) to collaboratively hit that target. Doesn't mean it will happen, but at least it establishes what we think a "normal" and uncomplicated case timeline 5094:

how marginalized the community has been by the selection process, I figure it needs RFA to counter-balance. RFA has to do with trust to an extent, because it provides scrutiny and you're trusted when you're scrutinized enough and no ground for making you untrustworthy are found. I've already said that I support the technical change.

3896:). The admin bit should be a strictly technical right. Whatever social privilege we have injected into it has only made RfA worse and relations between admins and editors worse. I'm absolutely stunned there is so much opposition to this change. Lets just start an RfC in order to allow the devs to make a change like this, please. 7491:, anyone?), and this would likely be amplified. I expect a narrative of ArbCom as a discerning elitist body which will hear only what it wants to hear would quickly come to the fore. Relevance of evidence aside, more stringent standards of "decorum" would in all likliehood be highly contentious, given the widespread contempt of the 10924:

protection. While contacting a steward would have risked having your judgement overturned, that's the point: that your assessment of a situation does not override everyone else's. Judging from the community response to your block, and how quickly it was removed, I doubt any other administrators would have been willing to place it.

2491:

appropriate is because it takes away nothing from the community's decision making process: a CU/OS without administrator privs will be able to see things that a CU/OS needs to see, but not block/unblock, delete/restore, protect/unprotect, grant/revoke permissions, and the rest of things that go along with the administrator role.

2394:

ArbCom appointing administrators without going through RfA, or changing the permissions such that a non-administrator CU or OS can still do the CU or OS job effectively, which gives the community a more appropriate say? From a controls and auditing perspective, it's best practice for each role to hold every necessary privilege.

1886:

cohort projects; several of them have non-administrators in these roles, and it is possible that a suitable non-administrator candidate may come forward on this project as well. Finally, there is the philosophy that a userright should be a complete package and should not be dependent on other userrights to function properly.

858:

is time to seriously consider their need for the tool at this time. Even if some checkuser or oversight permissions are withdrawn, that should not be taken as a sign that their work within the project (usually over many years) is devalued in any way; however, we need to be aware that sometimes people move on in their lives.

6238:

information you'll find from WHOIS etc, so I'd have no issues (on privacy grounds) with my IP being public knowledge, but if somebody edits from work or an educational institution, revealing their IP could very easily reveal where they work or are educated, which is a little more personal than knowing that my ISP is BT.

10261:. So grossly insulting statements comparing editors opposing the injunction to children who require "adult supervision" are counterproductive. Scott + arbcom + OTRS + foundation staff members cannot possibly police every biography. Effectively stopping Knowledge-based defamation and highly biased biographies requires 4822:

that; they have plenty of more important things on their plate. But when changes were made to the oversight permission a while back by the developers, it would have been the right time to quickly review both permissions and make them standalone, which is standard in just about every single system I've ever seen.

5702:

in his role. I'm not sure what more we could have done, and am confused by the objections at this late stage. If there are other unwritten considerations by which you feel the Arbitration Committee should be guided when granting advanced privileges, please seek to have them codified your earliest convenience. –

6291:

states that information can be released to protect projects. This does not mean that the IP address(es) of every disruptive user will be confirmed; in almost all cases, CheckUsers will have no reason to directly link the IP with the user, or the user's action will make it obvious that the two are connected.

5397:'s archives if you don't believe me. Now, given that RfA is avoided by many good editors who simply don't want to subject themselves to that particular style of adversarial review, and that the number of editors seeking adminship is declining, why would the community want to require candidates for jobs only 11004:, many editors will be genuinely concerned that any reauthorization of PC protection anywhere will serve as an excuse for harsh, authoritarian actions. To be honest, I don't know what I could tell them. Editors don't want to see reviewer rights used to suppress dissent by removing them from editors who make 10463:

the vast majority of voters look at what is said at the time of the election, and most specific incidents are long forgotten, especially when they happen 7-8 months earlier. Anyway, ask your questions at the election, and see what the responses are, but I doubt you will get the sweeping change you envisage.

3426:(ec) To your point about "accomodat one person", the fact is that Knowledge's existing permission structures are pretty antiquated and don't follow security best practices. That's true with or without a non-admin functionary at the moment. Granted, Giano faced a number of self-imposed barriers to actually 6224:

for concern). As for your first point, rereading the notice it is clearer that each sentence leads on to the next, and that it only suggests that CU discretion may be exerted within the bounds of the privacy policy; must have been half asleep when I first read it. Apologies for the hassle, kindest regards,

9162:

exclusively to deal with behavioral disputes, its scope has clearly broadened since then. I'm sorry you feel that exposing "the boring day-to-day operations" of the ArbCom seems like it would lead to "interference and misinterpretation". I think it would also lead to more transparency and understanding.

4052:

areas outside the purview of the admin bit. If we think that the CU/Os processes are insufficient to judge suitability to handle private information we ought to address that, but we shouldn't continue to load more social responsibility on the purely technical distinction of adminship than is necessary.

11305:

It's high time to have an RFC on Scott. While pending changes is gone, for now, he could certainly find some new pretense for wheel warring, involved blocking, threatening to block war, and generally disregarding consensus. An RFC would ensure that, if this happens again, an effective remedy could be

11144:

Either pending changes, as formulated during the trial, with reviewer rights as allocated for it, was a useful tool for prevent BLP problems, or it wasn't. In the latter case, "a pragmatic approach to the articles before" you would have been to do nothing, since PC protection wasn't going to stop any

11023:

The point of a "pause" was for multiple admins to see if more precautions were needed. It is better to have the maximum safeguards in place before protections are lowered, rather than scraping about checking articles later. In any case, if my fears were idiosyncratic, and other people involved in BLP

10854:

Also, the phrase "BLP trumps consensus" is greatly overused. While the policy page describes certain principles that the foundation is willing to protect, its exact text has been under the control of the community, and its application to particular factual circumstances determined by consensus, with

10824:

The correct level of protection for any article is a matter to be decided by the community, with due regard to BLP, but consideration also given to maintaining an editable wiki. While any level of page protection less than sysop only presents a non-negligible possibility of future BLP violations, BLP

10462:

Or you could stand on a platform yourself and see what support the community gives to that platform. That would be an alternative to judging 1-3 years work by some arbitrators on their stance on a single issue. In my experience, voters at such polls tend to see single-issue voting for what it is, and

10447:

The arbitrators seem to believe they can make whatever modifications to the protection or any other administrative policy they want, because they hold the power of desysopping. Widespread defiance of, well, whatever arbcom wants, would precipitate a constitutional crisis, with admins being desysopped

10005:

You haven't seen me take any steps to remove the protection once the OTRS ticket was pointed out to me, have you? I disagree with the concept that OTRS tickets last forever (and I would be interested in seeing a policy which says that they do), and, more importantly, we don't have any mechanism short

9912:

This particular case is the only one of the unprotections that I made that can validly be described as a "mistake" (I missed the OTRS ticket), and, even then, I don't think it's much of one. OTRS ticket or not, an article that hasn't been edited in three months is generally not considered a candidate

9639:

We've pointed it out multiple times, Scott: individual admins exercising sound judgment, with the normal checks and balances that are always in place, are able to handle all of these cases. Neither of the "errors" you point out as evidence of some kind of sloppiness or rushing on my part are clearcut

9320:

Now I'm not an admin, I've got no ability to add/remove changes, and have little to risk here, but my interpretation is that admins should be expected to use common sense here. The way I read this, if a page had PC with 37 days left on it before expiring on an article, the new protection should be 37

8779:

In the area I spend most of my time in (sports), proactive enforcement would most likely polarise people who previously only did this work in the interests of internal consistency. Not least in football, where large numbers of related articles in the XXXX–YY format are created annually. I'm sure even

8775:

Poor wording is forgiveable. I appreciate how difficult it must have been to draft a motion that is fair to both sides, whilst also achieving the primary objective of minimising disruption to the mainspace. But "proactive" enforcement of decision 1. will make endash usage controversial in areas where

7739:

I thought Knowledge is on the down side of the editing and editorship curve, so that if WP survived where it was 3 years ago it can survive indefinitely without doing much different? It seems like wikis are out of favor in general, and WP is no longer a very happening place. LOL :P What you say may

7699:

conditions... Knowledge can no longer afford to act like it's still a small group of computer geeks puttering away in some unseen corner of the internet; The project has to adapt to the fact that it has global scope, and that means growing up a bit and making respectable institutions that keep things

7348:

difference between talking and communication, and any practical, real-world venue for pubic hearings (from courtrooms to town-hall meetings to governmental hearings from the smallest town council to national congresses or parliaments) have strong and heavily enforced rules about the kinds of evidence

6838:

This is one of the things that gets me, the assumption that Dreadstar "got away" with his unblock only because he apologized. The decision is awfully clear: undoing an AE block is a Bad Idea. It continues to be a Bad Idea despite the fact that no one lost their bit over it this time around. I fail to

6474:

I can't speak for Cool Hand Luke and Elen of the Roads, but I explicitly didn't take part in this case. I was inactive at the time the case opened so didn't post a formal recusal at the time, but explained the decision to the other Arbs; I felt that I'd had enough acrimonious discussions with various

6053:

It is an unfortunate truth that we take more notice of the poorly-handled cases than the well-handled ones. But in my experience, almost all requests are actioned sensibly and with minimal weight given to wikilawyering respondents. I may be wrong, of course! I do however certainly think that the pool

5578:

SV: We did. It was advertised appropriately. No one objected at the time, and the decision was made on that basis. Are you suggesting that ArbCom should, in the face of raising a question and having it answered affirmatively, though perhaps anemically compared to a typical RfA, we should have kicked

5529:

It would have been good at that point if ArbCom had said: "No matter what policy says, let's ask the community whether it wants people with CU/OS access to be admins first." I think what people are looking for from ArbCom is interaction and transparency, as far as possible, and an ArbCom that divests

5168:

What I mean is that we need a process by which candidates are scrutinized more heavily than what would occur only with the ausc or cu/os appointments. Passing RFA isn't a guarantor, but it does provide scrutiny (it allowed to identify sockpuppetry, copyvios, etc). However, I recognize that the social

5108:

You're making adminship into something it's not. Adminship is the ability to protect, block, delete, and a few other tidbits. RfA is one process by which the community has decided who gets those bits. You're essentially arguing that a selection process designed to ascertain appropriateness for one

5093:

So you make me repeat myself again... When bugzillas are controversial, the community is asked to decide, it's because the vast majority of bugzillas are noncontroversial that the community isn't involved. I never said there was a requirement, never. I'm asking if there should be one, and considering

5035:

You become trusted when you have been scrutinized enough and nothing was found that made you untrustworthy. RFA can provide scrutiny, several RFAs have revealed evidence of sockpuppetry, copyright violations, and other inappropriate behavior. The way an admin use their tools can also indicate whether

4872:

In this case, the bugzilla was filed because the permissions are not standalone, as they properly should be in any secure system. That's not speaking ill of the developers; remember these toolkits were whipped up on the spot when specific issues needed to be addressed, and the community was in no way

4869:

Bugzillas are made by whoever makes them, with or without discussion with the community. Only a very small percentage of bugzillas filed involve discussion with the larger community, and often they are filed by someone who just happens to notice something and thinks the developers need to be aware. I

4746:

Xeno, I think that's what people are saying, that these things aren't read carefully. That page, for whatever reason, doesn't attract the input that RfA and other pages do. Some editors don't know it exists. Some don't understand the process. Some feel their input may be pointless. Others don't care.

4490:

If those objecting at this late stage did not notice that bahamut0013 was not an admin, then I wonder: to what extent did they scrutinize the candidate(s) at all? All the comments submitted by the community from any vector were read in full by every arbitrator who voted on the candidates - suggesting

4078:

The committee had a frank discussion about whether adminship was required for AUSC community representatives, and there were arbs who recommended that the tradition of adminship prior to appointment be maintained, but the majority didn't see it as an issue. I'm not sure that I would characterize the

3961:

No system is going to be perfect. But it makes sense that, the more eyes are on the account, the less likely it is to be an account that's going to cause serious problems for you. If you have a system where it's simply someone chosen by the Arbs, it increases the chance of an error. That's all anyone

3734:

I'm talking about bad stuff that is deleted but not oversighted (there are tons of it). Most admin tool misuse (delete main page, block Jimbo) is visible and can be undone easily. From what I understand, accessing deleted pages by admins isn't even detectable. I think you can figure out the rest.

3453:

The issue with Giano is that he didn't want to identify with the Foundation; his becoming an Arb without being an admin wasn't a concern that I'm aware of. The difficulty with making the technical change is the danger of Arbs alone deciding to give someone CU—without there having been an RfA, without

3134:

trustworthy. Sure, you can know the law perfectly - but nobody hires you as a lawyer without the exams to back it up. X or Y can be the most level-headed individuals to ever be considered for CU access - but without some sort of formal validation by the community, we have no reason to assume they are

2960:

Your position is contradictory. On one hand you say it's just a request, nothing like a decision. On the other hand, you say that instead of, as always, requiring consensus for making changes, the burden of consensus building should be reversed and it's up to the opposers to build a consensus against

2534:

The request for comment was well advertised. While there may only be three public comments in support, there are also no objections to a non-admin serving in this capacity. We requested members of the community to privately inform the committee of their thoughts about the candidates. And they did.

2490:

a non-admin CU/OS. Given that this has gone from theoretical (e.g., Giano's recent ArbCom candidacy) to the actual, it's up to ArbCom to implement some way for our newly elected community audit committee represenative to do his job (which, ironically, is checking up on us). The reason the change is

2393:

That's a red herring. The actual background has been that CU/OS have required permissions associated with the administrator role to do their jobs right. Let's look at it this way: ArbCom can appoint advanced permission holders, but doesn't currently appoint administrators. If the choice is between

2104:

Personally I'd like to see a situation where Arbs give up adminship, CU, OR, and any other positions they hold while on ArbCom—because it would mean people would stand only because they wanted to engage in dispute resolution, and wouldn't be able to wear multiple hats while doing it. I'd also like to

1800:

The evidence procedure is only one of several designed to improve case handling. The default timetable, for example, will also help reduce bloat by encouraging people to concentrate on essentials. Prohibiting evidence in user space is another way of keeping bloat down and increasing transparency. The

1567:

There are several more in the pipeline: they are mostly overhauls/reviews of existing procedures. They have been worked on over the past couple of months and are not taking resources away from cases. I don't see much point in publishing an agenda as hardly anyone took notice of it when we did; and it

669:

Could one of the arbitrators please explain to me the purpose of the "including at least one community-requested logged action" clause? If an Checkuser is watching a topic area and runs valid checks every so often on his or her own initiative, assuming everything is fine with those checks, why should

312:

One other issue that has been raised with non-sysops is that a successful request for adminship is a basic and necessary mark of community trust in a candidate. So long as a non-sysop appointee would not be unable to audit because of a technical inability to see deleted revisions, I think the lack of

11130:

I was not trying to make any point. I'm uninterested in the trial - and broadly I'm unenthusiastic about PC - for reasons I've given at length elsewhere. However, if you are going to have PC, then reviewing rights need to be meaningfully given to clued people. As for the original dispute, it was for

11096:

The important thing was to get the admin to halt so that there could be a proper examination. In hindsight, although I believe my blocking was justified, it would been wiser to get someone else to do it (as it would have caused less brouhaha. I was foolish not to have considered that.). There should

10996:

should have double-checked all of Kww's unprotections. You could have asked other administrators for help. This is the fundamental problem with many of your actions: the attitude that you're one of the few defenders of BLP on the wiki. If no other administrators cared about this issue, you'd have no

10952:

If there were really exigent circumstances, then Kww being reasonable, and stopping the unprotections after he was unblocked couldn't have been relied upon. But if there was no emergency, which you now concede, then there was no justification for an involved block, the only type which was ever going

10909:

An emergency desysop is quite ridiculous in these circumstances. The block was perfectly useful as it did have the desired effect of getting the admin to stop and the matter to be discussed. Indeed, with hindsight a shorter one would have sufficed. As for me calming down, that's beside the point. If

10566:

I agree with Harry that Arbcom appears to have exceeded its powers – the terms are well past what is reasonable or to encourage orderly unwinding. It's obvious that as a first and easy step, those bios with OTRS tickets can be taken off PC with immediate effect, and given a high level of protection.

10563:

Credibility is the biggest issue here, and those in charge of PC have lost it in a pretty big way, IMHO. Implementation and rollout were ill thought out. Its indefinite existence was a foregone conclusion, thus no proper planning was ever put into place for its dismantling. As I recall, the proposal

10432:

Arbcom cannot remove admin discretion with regard to protection; a few arbs acknowledged that admins could subsequently alter the protection level in accordance with the protection policy and though they emitted conditions such as 'after a review' or 'after a while', their opinions diverged and this

10285:

I would just like to commend ArbCom for the swift decision on this. NewYorkBrad's closing statement on the RFC correctly dictated that we should be cautious in implementing the consensus to end the Pending Changes trial. Since we seemed to be incapable of following a softer, more flexible request to

10171:

Just noticed that you are still mandating a two-step process. Might as well use a bot to do the robotic, judgment-free switch to semi-protection, and then have admins go over the result and do the real work. Or you can skip the bot, and just let admins do their jobs. Alternatively, I guess the first

10029:

Jclemens, we ('users') are not legally responsible for Knowledge. Legally we are users of a service, that's the WMF that is responsible for Knowledge. For Knowledge to have knowledge of defamation issue, it means that the WMF or its agents have knowledge of such issues. If mere users of the service,

9958:

this morning due to the immediate resumption of vandalizing IPs, for example. This is par for the course: a standard part of protecting and unprotecting articles is to monitor the article for the results of your actions. Evaluating the long-term history of an article is important as well: I'd oppose

9750:

How about just adding articles in general and BLPs in particular that you protect to your watchlist? I watch every article I've ever unprotected (except where I was reversing my own action) and I believe most RfPP/RfUP regulars do similarly. Notifying/discussing with the protecting admin, if they're

9658:

I think there's a very large difference here, between admins who believe that BLP is ultimately best served by working through community consensus, since it is largely dependent upon the community to do the legwork of enforcing the policy, and one administrator who seems to feel that BLP is advanced

9452:

I wish that they had added a qualifying word to that, such as "blindly". The PC test netted a range of articles, some of which had suffered vandalism, others not so much. The admins clearing out the list generally seemed to be taking time to figure out what level of protection was needed, as often

9192:

Will Beback, the overwhelming majority of resolutions approved by the Committee are posted onwiki. Those dealing with private or non-public personal information are not publicly posted, or posted in a manner that does not share the non-public information. Some that are of no significant consequence,

8913:

I am trying to figure out exactly what WFCforLife's questions are - yes I guess a broader 1RR on anything dash-related would (in hindsight) have been simpler. I was thinking in terms of the Request for Arbitration and hence the motions were a response to it, rather than broadening it. Ideally, if we

8710:

To answer "why can't this wait"? I certainly won't be moving an article like that until this whole issue has been resolved. I guess the real point of my question was that a lot of people to do not watch the MoS page or the ArbCom page and therefore won't know that moves involving dashes/hyphens have

8357:

I notice that there is no requirement in the procedure for the Committee or Subcommittee to inform the appellant of anything unless the appeal is summarily rejected for frivolity or groundlessness. Obviously it is common sense that the user be informed of other outcomes when they are decided, and so

7776:

with respect to the other point: Knowledge may be growing or shrinking (I don't know, and don't care much), but the point is that it is so far outside of the 'small, homogeneous, easy to navigate community' realm that acting as though that were still the case is borderline delusional. Now it may be

7703:

A large part of the respect and dignity of a deliberative body comes from the fact that limitations are placed on speech and behavior. When I look over the case and read the masses of irrelevant vituperative tripe that got passed of as meaningful discussion (some of which I passed off as meaningful

7627:

The one clerk active on the case did a fine job. ArbCom cases are primarily about conduct, so Iridescent's remarks are very relevant. If ArbCom had indicated earlier that there was no interest in discussing QuackGuru or any related issues, that would have considerably shortened the case (and some of

7509:

show this is possible, although I expect it would be more difficult in this case. A more muscular (and numerous) clerk presence, where parties are given notice to refactor irrelevant evidence as well as overly-long statements (as is the case now) could work. It's worth documenting expected standards

7486:

Effectively replacing inter-party sniping/conflict etc. with the clerk-party equivalent would come with its own friction. The largely pugnacious sort of Wikipedians who end up in arbitration don't react well to perceived busybodies telling them their input is unacceptable, as the free-flowing nature

7353:

to stay narrowly focused on the topic at hand and observe strict standards of decorum, because doing otherwise is viewed as contempt for the system itself and is potentially subject to hefty fines and jail time. Had the interaction that occurred on the case page been seen in a US courtroom, almost

7166:

The bottom line now seems to be that AE blocks may be be unilaterally undone in cases where enough arbitrators happen to agree afterwards that the block was wrong (because, as here, such unblocks are not sanctioned). This is inconsistent with the instant decision, which purports to recognize that AE

6970:

I hope no one minds me commenting here. HJ, one thing that I think is getting overlooked here, is that a significant part of the Committee disagrees with a fundamental part of your comment, that Sandstein's actions was a valid Arbitration Enforcement action. Coming from that direction, it follows to

6858:

consensus to unblock) that they can overrule an AE block. A third admin reversing the unblock is almost assured of a desysop for wheel warring, but the second admin merely has to offer an apology when it's all over. People seem to be factoring in a belief that Sandstein's warning, or block, or claim

6793:

It is my understanding that HJM's frustration is with a situation where no formal indication has been given by ArbCom to reduce the reliance on discretionary sanctions and to come up with a more effective appeal process (particularly for short blocks). I don't think it was possible for this case to

6784:

If they are stating the obvious, the fact that this series of missteps occurred anyway is a reflection that it is not obvious enough. All admins have therefore been put on notice; this case gives the warning/incentive to stop letting this sort of situation arise, and it also provides guidance on how

6765:

What principles are pretty clear? Is there any statement about what would happen if another Dreadstar situation arose (first admin makes what they claim is an AE block, and second admin unblocks and declines to reblock even after the meaning and implications of an AE block are explained, and with no

6381:

rules at their leisure. The period of two months from the request for arbitration to the final decision, in a case whose facts consisted of a mere handful of edits, adds to my general impression of a body dominated by sloth, factionalism, or both. Three "active" arbitrators – Cool Hand Luke, Elen of

6360:

made these decisions substantially more meaningless. Without support from the Committee, administrators cannot give meaning to these decisions. And by support I do not mean blind support of admin actions – these can be just as mistaken as anyone else's, which is why there is an appeals process – but

6351:

better than B's), B will not do anything about this, if they have any sense at all. Because doing so, if this case is any indication, will mean that B will have to waste two months of their time to pursue a full arbitration case (which few people have the stomach for in any case), and that after two

6237:

Surely CUs (if they don't already) should consider what information can be gained by looking up an IP. For example, if you CU'd me, you'd see I edit from an 86... IP. A knowledgable person can tell from the first two digits who my ISP is and in which country I reside, but that's the extent of useful

5765:

I had considered putting my name in for consideration of candidacy for AUSC to represent a community (non-admin) position. I observe that adminship, while claimed to be "no-big-deal", is a "big-deal". The recent RfAs have either been gigantic landslides, schadenfreude laced inquisitons, or snowball

5701:

was an open, nonsecret proposal to appoint a few members to a subcommittee, one of which happened to not be an admin. No one from the community at large objected to the candidate based on their nonadminship. After we appointed him, we requested the necessary technical change to allow him to function

5679:

You're right that it's impossible to know what people will object to. That's why it's important to find out by making proposals. Open projects are messy that way. But Knowledge was founded on transparent decision making. I hope that in the future the ArbCom will chose to hold discussions more openly

5597:

Past consensus doesn't bind current editors. If the community didn't notice that the intent was to appoint non-admins and so didn't object, that doesn't mean that the ability to object now has been lost. As for unwritten policy, do we need to write into policy that the community decides who is given

5211:

The bugzilla seemed uncontroversial because no one from the community at large had objected during the entire process where a non-admin was presented as a candidate who would need to see deleted and oversighted contributions. I think what some administrators are forgetting is that not everyone wants

4782:

I'm happy to tone it down but characterizing an argument isn't personalizing the discussion. I'm truly shocked that a beneficial (in my eyes) and nominally uncontroversial change has provoked such strong pushback. The response to this change--which basically means that the admin bit will no longer

3975:

While this may be a side issue, if I was faced with the history of attempted OUTING you have faced, I would use a proxy from here on out, and I would recommend that for any other user who's been similarly pursued. It's why I don't put myself on "do not call" lists: instead, I just never give out my

3689:

mostly for policy reasons (admins have much more authority in DR than they used to) rather than "security" (controlling access to the technical tools). (FWIW, I'm squicked out by the existence of "researcher" and I wonder what purposes that bit has been used for--I guess I should read the meta page

3482:

That's exactly what I'm finding odd about this entire discussion. The AUSC appointments were widely advertised and open for comment for quite some time. Its only now that these objections are being raised. I took the time to review the candidates and add my own comments at the time. I didn't comment

3348:

We want to become fairer as a community, less cabal-oriented, more professional. The Foundation has just made it a priority to recruit new editors and retain established ones, because the trend shows people are leaving and not arriving in the same numbers. The one thing that has plagued us for years

3264:

wants applicants not to have been through an RfA, that means no community input of any kind is backing that candidate. It would mean the ArbCom alone simply choosing who to give CU/OS to, and who to place on the functionaries list. And realistically that will mean maybe just one or two people on the

3192:

I would be concerned about this proposal. The idea of handing out these rights was always that there was a degree of progression, with adminship being the entry level, if you like. The reason that matters (whether you think RfA is broken or not) is that there are lots of eyes on the candidate during

3167:

I am relieved to hear that you don't consider the option to grant adminship by fiat as viable alternative, as the way Jclemens presented this as the only other option had me worried. That being said, it's really not helpful to make sarcasm of the position of others. I want to add that everyone wants

2754:

to consult the community - I simply feel that a good deal of the community probably trusts the Arbitration Committee to make good decision for the betterment of the project (i.e. the role for which the Arbitration Committee is elected), and doesn't need to be asked about every minor detail. However,

2713:

The community elects the Arbitration Committee to oversee advanced privileges. If the community wants us to consult them on every decision we make in regards to advanced privileges, there's probably not much point to having a committee in the first place. This change has nothing to do with political

2430:

There's two questions, really: 1) Is it consistent with information security best practices to convert the cumulative roles into standalone roles? That answer is obviously yes. 2) Is it the community's wish that non-administrators be excluded from election to the bureaucrat or appointed to CU and OS

2118:

What we did was RFC the appointment method, conduct an arbitrator vote on the appointment process, call for AUSC candidates, privately vet the applicants, publicly RFC the applicants allowing public and private comments, hold an arbitrator vote on each candidate and select the top three according to

1919:

I'm afraid I agree with B. I don't wish to slight the one non-admin, but if you're trustworthy enough to be a functionary, you're trustworthy enough to pass an RfA. Even with the ability to view deleted content, there are a a host of other things that a functionary without an admin bit can't do. For

1900:

That sounds, WADR, like a patently bad idea. If someone is a qualified checkuser candidate, they should submit themselves for adminship. If the community doesn't trust them with the admin tools, they certainly wouldn't trust them with checkuser/oversight. As for former arbiters who wish to resign

1815:

Equally, it's important that people have their say, especially in the early stages when the issues are unclear or in the process of being clarified but, obviously, brevity, relevance and focus plays an important part here too, which is a judgment call. An editor wishing to add evidence about several

1527:

This is a good step, but to really get cases moving (unless there are genuine reasons for delays, which should be communicated to all parties and posted on the case pages), then you should consider encouraging drafting arbitrators to drop all other responsibilities when they come to drafting a case,

857:

That's pretty well it, Cube lurker. If someone with CU or OS permissions is willing to participate but is experiencing challenges, we'd rather work with them to remove the obstacles to their participation. On the other hand, if someone has been essentially inactive, and remains unresponsive, then it

732:

Since the committee's list of community-requested actions includes "those made in response to threads...posted on a CheckUser's personal user talk page", I don't really see how this can address the problem of "a few requests here-and-there for Wikifriends" - as long as the Wikifriend posted a thread

180:

With regards to your second question, I'll quickly answer from my memory, which is a bit stale, and hope someone corrects me. The ability to see deleted content comes with a permission 'view archive' or 'browse archive'. The French Knowledge gives this permission as part of the OS/CU packages, and

152:

One of the candidates is not an administrator. What would happen in the event that he were appointed to the subcommittee? How would situations be handled in which he might need to view deleted content? Would the Oversight permission give him the ability to perform "normal" RevDels? Is there anything

10869:

BLP is by convention, necessity and practice more of a principle than a set of rules. It says "fairness of living people matters, and Knowledge's practices must always take this on board". This needs a lot of judgement, and at times creativity. We can't tolerate our inhouse rules adding to the high

10671:

The point of full-protection (which is usually undesirable) was to allow the immediate removal of PC, while also allowing a more cautious examination of articles to see what level of protection (often none or only semi) the merits of the particular article demanded. In most cases it appears that PC

10513:

This is all very dumb. The reason we don't have a consensual permanent PC implementation by now is because of the actions by some overzealous people who wanted PC immediately. We finally have the consensus to 'end' the 'trial', the plan was to allow admins to apply their discretion in transitioning

10358:

Please read the injunction more carefully. It doesn't just mandate "some form of protection". It states that semi-protection must be used to replace level 1 PC, and full-protection for level 2 PC. Simple common sense would be for the administrator removing the PC protection to review the history of

10290:

while we carry out removal of Pending Changes is the right thing to do obviously, and should allow admins act on the consensus of the RFC without further drama. Once that's done, the community can move on to creating a lasting policy about how and where to apply Pending Changes, if at all, and this

10033:

The OTRS system however is indeed a way to inform the WMF of defamation threats, and OTRS personnel can be considered agents of the WMF (not mere 'users'). Those 'agents', in their interaction with 'users', must follow the policies set by the WMF. From what I understand, generally admins may not of

10014:

article is a sign of my efforts to follow policies and guidelines. When I step through articles and remove PC, I do my best to follow policies and guidelines about what the protection state should become. In my judgment, on that article, it can reasonably fall either way: the only thing that nudges

9969:

just doesn't give any indication of that necessity. There's a short burst o problems in February, but that's about it. If I hadn't missed the OTRS ticket, I probably wouldn't of unprotected it just out of an abundance of caution, but there really isn't a strong case for continuing protection on the

9476:

I think there's an overreaction here. There are folk who want to go through all the articles which have FR set and remove it. that's causing problems with BLPs, because anyone doing mass removals may well not be fully aware of why a BLP was flagged in the first place. What this motion allows is for

9161:

I still can't find the consensus for this, or the lengthy hashing out which led to it, so I presume those discussions were held in private. A group that meets together to pass resolutions, some of which have the force of policy, certainly resembles a legislative body. While the committee was formed

8977:

I don't see anything in this procedure calling for discussions concerning resolutions to be held in public unless there's a specific reason for privacy. Does the ArbCom lack a forum in which they can discuss resolutions without other editors interrupting? If not, why hold deliberations in secret if

8858:

Given that, the purpose of this motion should be to prevent edit-warring on dashes/hyphens where the Manual of Style could be considered unclear. If part of the aim was to send out a message that escalation will not be tolerated, a broader 1RR rule on all dash-related edits would probably have done

8373:

No doubt this is an unfair comment that doesn't adequately take into account everything else ArbCom does, but somebody has to say it. ArbCom seems to be spending a lot of time and effort in adjusting its procedures and policies to its liking and yet when it's asked to resolve a dispute, it seems to

7608:

Rather than bothering with new subcommittees or internal teams, wouldn't it be much more expedient to simply ask the committee to guide the process a bit more than they've generally done in the past? This case didn't occur in a vacuum; once someone is listed as a party to an arbitration, the knives

7552:

to be offensive. Knowledge editors don't come from a single cultural background; what seems a polite formality to one editor can seem to be abusive passive-aggressiveness to another, what seems necessary bluntness to one editor can seem a personal attack to another, what seems a friendly attempt to

7222:

While it's nice to know I'm not the only one frustrated by this decision, the validity of the block as an AE block is not something that should be litigated on at all when it comes to deciding matters related to it's reversal. Whether or not it was a valid AE block, it was marked as being pursuant

7086:

Putting aside Ludwigs's comment, HJ, several of us made clear that only extenuating circumstances (the nature of the block and the fact that he did apologize) prevented a probable majority to remove the administrative tools, and again, many of us made clear in our statements in the workshop and the

7016:

SirFozzie, thank you for your response, but (you knew there was going to be abut, but what precedes it is sincere) the validity or otherwise of Sandstein's action is wholly irrelevant. It couldn't have been clearer marked as being made pursuant to an active arbitration remedy (and those who read my

6951:

The following response is specifically limited to the part of your comment which starts from "nor is allowing an admin....". I think that by pushing a view that an admin got off scot free, you are giving a very different reason for many admins to continue staying away from AE (and it has nothing to

6930:

Allowing the names of two excellent admins to be dragged through the mud for two months while they watch from upon high is not an acceptable way to handle things. Nor is a complete failure to give more than token recognition to the admins who spend many hours of their time cleaning up ArbCom's mess

6709:

Just for the record, I was I think the first Arb to support taking the case, and fully intended to take part. However an accident in the family required pretty much my full attention from 9-18 April (and was moved to inactive or should have been), and I was only at home 4 days out of seven for the

6488:

Additionally, looking at the workshop and proposed decision pages, it appears Cool Hand Luke was active for the case. It seems a party who was knocked off his pedestal is unhappy so he has started to make unjustified accusations about the people who dared to advise him to take a walk. (For example,

6372:

Even apart from the outcome, the case was not handled competently. Most of the Committee's activity, such as it was, was devoted to drafting elaborate rules for AE, which may even be useful, but would have been more easily developed as codified procedure outside the context of a case. It would have

6355:

A clearly communicated rule that is not enforced is not taken seriously, and neither are the people who make the rule. The decision purports to recognize that "the Arbitration Committee appreciates the work performed by administrators, without whom long-term remedies imposed in our decisions would

5664:

was through the community input process and the written codification of existing policy. Both the AUSC candidate feedback prior to appointment and VPP afterward are not finding a problem with the revised practice, and we are all agreed that at no point was the Administrator expectation codified in

4051:

But there is nothing about the admin bit that is at all connected w/ CU/OS. We don't ask questions about CU/OS issues in RfA, we don't expect admins be trusted w/ CU data (or oversighted revisions), and the RfA process is not designed to handle serving as a catch-all judgement about reliability in

4020:

Jclemens, I think you're underestimating how easy it is to make mistakes with proxies, even for technical people who know what they're doing. Forgetting to turn a proxy on or off isn't much different from making a logged-out edit by accident now and then, something that happens to lots of people.

3758:

Maybe we need a RFC on the policy issue. To avoid conflating issues, we should not consider there the assignment of CU/OS to arbitrators. The question would be: should adminship (obtained via RFA) be a prerequisite for being granted CU or OS rights (other than through arbcom elections) ? (Of course

3719:

You don't need to be sorry for sparking questions. As I see it, you have several members of ArbCom explaining politely to several dedicated community members what we were thinking and wny. As far as access to deleted pages goes, I suppose I could use a little bit more education on why it's such a

3700:

Before Bahamut's situation arose, I kind of doubt it occurred to anyone in this discussion that CU/OS didn't already have access to deleted pages, and I doubt anyone would have minded if they did. So I don't see much point to getting worked up about it on the technical side now. I thought we had

3678:

Re Jclemens "security best practices": I've long felt that access to deleted pages is the most powerful and dangerous ability that admins have. Just about everything else (blocking, deleting the main page, etc.) can only cause on-wiki disruption that's usually easily reversed. Deleted-page access

3610:

of checks that have been ran, you cannot see what was revealed in that check without actually rerunning the check yourself, and therefore making an entry in the log. (Though, to be fair, an intelligent person could figure some information out just be examining what was logged in a rapid sequence.)

2731:

If this were a regular decision in regards to advanced privileges, I doubt it would have been posted on this noticeboard. It's the first time that ArbCom files a bug request requesting a change in the permissions of a usergroup, Xeno, you know very well that this is not a regular decision regarding

2589:

Thank you for making up something that has nothing whatsoever to do with what I said. I think you are seeing what you want to see. I said that if they have the trust of the community, then they should be able to pass RFA. That does not mean that all persons who have not passed RFA are inherently

2509:

what you are talking about for the "community endorsed ... non-admin CU/OS"? An obscure page with three comments in support of this user is hardly a ringing endorsement of changing what has always been the de facto policy. And I think you well know that modifying user rights is somewhat different

1966:

That's possibly the most over-the-top analogy I've seen in a long time, B. "Nuclear football"? I'd suggest it's more akin to a cow-patty detection system. Checkuser results and suppressed/oversighted edits are involved in at least 30% of arbitration cases, and arbitrators need to be able to discuss

1582:

For me, the main benefit of target timetables is to set a date by which evidence should be submitted. This avoids the two unfair scenarios of an editor dropping everything else he or she is doing to compile evidence quickly, and it turns out he or she could have taken a more reasonable time, and on

1551:

This seems to be one of a number of internal process initiatives that are being published. I've commented on this one above, but wanted to ask in general whether there are there many more of these 'process' motions to come, and is the right balance being struck between this sort of work and work on

827:

Two responses: 1) It's a "may", not a "must", so we'll be handling issues on a case-by-case basis, and 2) since we've discussed formalizing the process with the functionaries email list, some have become more active, while others have remained inactive, so we already have a pretty good feel for who

783:

Specifically answering the part of the question about logged actions in response to particular types of requests, the largest number of concerns we receive from the community with relation to these permissions are "slow" responses to SPIs or ACC requests that are checkuser-dependent, or alternately

10923:

basically your justification for the involved block, wasn't it: that Kww's actions created a BLP emergency, and needed to be stopped immediately? Such desysopping would only have been "quite ridiculous" if there was no emergency, nothing justifying a forcible intervention to halt the removal of PC

10894:

And one reason the arbcom injunction is wrong is that administrators who can't be trusted not to take many injudicious actions on BLPs and open the floodgates of defamation shouldn't be admins. Human sysops whose judgement is sound do not require robot-like instructions - it's been observed that a

10399:

Precisely. We are being enjoined from using judgment. Sadly enough, people have been assuming that I am guilty of poor judgment: I note that Steven seems completely comfortable with stating that my actions were "injudicious". I would invite him to review the protection decisions I have made during

10302:

Creation of "a lasting policy about how and where to apply Pending Changes" could have already been achieved, if the foundation hadn't already messed up the "two month" trial. At its conclusion, the PC feature should have been disabled by developers as a technical measure. The community could then

9740:

Generally the "sound judgment" or semi-protection, is fine. However, since we know mistakes get made, and reviewing admins may not be in possession of the facts, then where OTRS or "BLP violation" has been given as the reason, the deflagger should also notify the protecting admin, and not lower to

9501:

Not by me (and the question seems to fail to assume good faith). Actually, I mostly agree with you. Looking at most of the PC set, they were set explicitly as part of the test or to avoid simple vandalism. In such cases, removing and substituting little or no protection is fine. However, some have

8639:

style Alternative Vote on all the various options; (d) the toss of a coin or (e) some other process. If you can come up with a process with which you can all agree will produce a fair result, then all's well and good and said process will run for all of June and half of July. If that doesn't work,

7856:

system: a loosely organized collectivity, where individual members are largely independent within kith and clan groups of various strength, and which has a weak decentralized authority structure administered by knowledgable, trusted elders (who operate largely independently, but adhere to a common

7612:

Of course, like I mentioned in the case pages, just as the Enforcement case wasn't going to "solve" AE, I doubt we're going to "solve" ArbCom here, either. Of course, it's amusing to think that anyone will fix it at all; if the committee changes its process by fiat, there'll be a riot, while if we

7572:

There was extensive discussion on the clerks' mailing list a couple of months ago about the limitations on the role of the clerks. We had been asked by an arbitrator to vet some evidence for suitability and relevance to the locus of the dispute, but I, and most of the other clerks, were distinctly

7378:

And what's worse, these kinds of behaviors breed: someone indulging a petty grudge or exposing some supposed scandal will cause someone else to register an indignant complaint, which will lead to self-righteous claims on both sides, which will mobilize outsiders who see the conflict as a threat to

6974:

As for the idea that not sanctioning Dreadstar further will weaken the ability of AE admins to make tough decisions, as Brad said, first off, we haven't seen anything like that, and de-sysopping Dreadstar has not been on the table for quite a while... and I would personally add that while it falls

6789:

applying a novel sanction or when a reasonable, uninvolved editor may question whether there is no pressing need for a given sanction. (3) Warnings and notices must be clearly communicated. (4) When actions are overturned, don't take it as a personal rebuke; learn from experience and feedback, and

6726:

What a total fucking joke. Did ArbCom actually listen to a single word that wasposted in the evidence or the workshop? Because it looks to me like you couldn't be arsed to come up with proper dispute resolution and so thought you'd go for a five-minute hatchet job. Two months to change nothing? No

6680:

Thank you for your response, Brad. I will drop the matter for now, but I may bring it up in the future if Dreadstar uses administrative privileges in a fringe dispute. To others, I don't think recall is a good idea at this point for a number of reasons. If you actually read my statements in the

6448:

Thank you, Newyorkbrad, for your explanation, which I understand, even though I do not agree with it. Although I proposed a desyop, which I think would have been appropriate, I did also say that some other sort of tangible sanction, such as a restriction on unblocks, would equally have sufficed to

6223:

I fully concur with your second paragraph, and I am confident that the checkusers on the English wikipedia, yourself included, are highly professional and very aware of privacy (I was somewhat aware of the circumstances of the report that this notice pertains to, and I personally did not see cause

5788:

If there was an issue with me getting the CU/OS bits as a non-admin, why didn't anybody raise any concerns until well after I had recieved them, and then submitted for RfA because of the technical issues we ran into on a case? The AUSC appointment page was sufficiently advertised, and there was an

5582:

Will, you can call it a policy change if you want, but the fact is that no one cared enough to document such an expectation, and no one objected at the time when a non-admin candidate was put forward. It appears that a few administrators assumed it was policy, didn't comment on the AUSC nomination

5422:

Is the ArbCom uncomfortable with discussing changes to policies and procedures like this on-Wiki or on a publicly viewable mailing list? I keep seeing references to discussions in which things were decided by the ArbCom with only an on-Wiki vote for the community to see. While "executive sessions"

5296:

I don't contest that you thought it was uncontroversial at first. I also recognize that there is a social argument for not requiring admin rights. Citing my reply to the similar comment you left at VPT: The problem with the appointment is that arbs would still make the final decision. Users aren't

4888:

I shouldn't have to repeat myself, why don't you look at what I said on this a little above before commenting ? Of course anyone can make bug requests, but when they are controversial, the wiki's community makes the decision. And this one was controversial, so even if there was an arbcom decision,

4821:

In what way? We're responsible for the use of the permissions on this project. Frankly, I don't understand why the permissions weren't designed this way in the first place, except because they were whipped up quickly and then never properly reviewed again. I'm not going to blame the developers for

3934:

No doubt you're right, but Protonk makes a very good point about the "social privilege" that has accrued around the admin bit, ossifying any hope of changes like this one. Even more radical reforms are needed to stall wikipedia's heat death from the admins' cold dead hands, but very little hope of

3674:

I don't have any problem with the bugzilla ticket on purely technical grounds, for reasons described just above (in my reply to SlimVirgin). The policy concerns of giving CU/OS to non-admins are separate (and valid), though Bahamut seems to be passing RFA nicely right now. More generally I'd say

3541:

The ability to read everyone else's CU results going back several months has the potential to cause real harm when IPs are exposed, but a search like that isn't logged anywhere, because it's just passive looking. So there has to be some kind of filter for CU candidates—no matter how imperfect—that

3515:

My concern is that we've had security failures—if that doesn't sound too dramatic—after RfAs (people turning out to be someone else, or a banned user, etc). And we've had a couple of similar problems after ArbCom elections. So those two processes are very imperfect. But the solution is not to have

3434:

a non-admin serve on ArbCom?" So, given the proximate issue, we're solving the wider technical issue. By next ArbCom election, we should have the technical means for a non-admin to fulfill the ArbCom roles, such that what the community gets to decide is whether or not any particular non-admin is

3041:

I think there's a fairly simple solution here. If a user is granted CU but is not an admin they still can't block anybody, so there's really no problem there. Persons using OS who have the ability solely for AUSC purposes should be required to limit their use of the tool to viewing only and should

2462:

Still, you should consult the community. You do not have power to grant rights over than CU and OS, and you do not have power to change permissions affected to a usergroup. If for some reason you think doing so would be good, then you need to consult the community. The recent appointment which you

1480:

us to actually throw darts at a board if we don't get an outcome drafted in time. I sincerely hope now that we're into Q2, that us newer members of the committee are going to be in a position to take over more drafting responsibilities. Unfortunately, I have no particular insight into Sandstein's

717:

The purpose of advanced permissions is to be responsible to the community, not just to a circle of editors with whom a particular functionary interacts. While privately emailing a functionary has not been deprecated at this point, formal tracking mechanisms (SPI, oversight-en-wp OTRS queue) allow

194:

In response to your first question: In order for editors to feel comfortable requesting or submitting an application to serve as a functionary, it is important that potential applicants for advanced privileges know that their participation in the vetting process will remain confidential. There has

11224:

Ok, how about this? Above, you had this comment: "We can keep fighting over this, or we can try to suggest to arbcom a better way." And my answer is to suggest that Arbcom butt out. Protection levels are, imnsho, a content decision that is outside of its mandate. Conduct issues surrounding the

11175:

I don't have the will to read the entirety of the text above, but it seems that at least some people are pushing for a motion that says "use common sense." Or in expanded form: when evaluating protection options, you can unprotect, semi-protect, or full protect at your discretion. How is that any

10982:

You are wikilawering now. Bottom line. There was a risk here. That risk could have been minimised. Kww unreasonably refused a request to stop and discuss. I blocked him for a very short time. Theoretically he could have resumed after the block was removed, but he wasn't that dumb. The idea that I

10942:

Rubbish. You are now taking this to extremis to make some silly point. It does not take an "emergency" to say "hey, stop, there's more sensitive ways of handling BLPs". Which ought to have resulted in administrators saying "Hm, OK. Let's talk about that. Maybe you are right - maybe not." This has

10798:

itself is a non-negotiable, foundation-approved policy. Should there ever develop a consensus to do something which arbcom believes violates the policy, the committee would be acting correctly in quashing it. However, the limited scope of BLP needs to be recognized. Primarily, the policy concerns

10136:

Add "if pending changes was set due to BLP violations, the admin who set the flag should be notified." I'd rather have them consulted prior to the protection being dropped, but I'll settle for notification. That means if semi isn't going to solve the problem (sleeper socks) and the admin removing

9628:

That would allow most of your removals to stand, and articles with BLP issues to have a number of eyes on them, and ones with complications identified, before we lower their protection. Seriously, I think the practical distance between us is very limited here. Sarah, if we could agree on a better

9437:

It's within arbcom's power in that the arbitrators hold the power to remove administrative privileges, and can use such to prescribe whatever rules of administration they like. The exercise of power may not be legitimate, but there's no doubt that in terms of sheer force, they have the ability to

8784:

removal of the endash from wikipedia would concede that year ranges are a black-and-white area, and that the final solution for year ranges should be universal. I would therefore request that this motion is amended to make a qualified exception for year ranges (what "qualifications" are necessary

8695:

I tend to agree with Dank's claim; but there is a minority which would settle the matter here by throwing out the endash altogether (as a non-keyboard character), which is only slightly smaller than the minority in favor of the present text of MOS. I don't belong to them, but why can't this wait?

7515:

I would also recommend making clear what the Committee wishes to investigate when it accepts a case, so as to discourage contributions on irrelevant topics. Granted, hints are given in the accepted list of parties and the name adopted, but I'd say there were more than a few editors surprised that

7446:

of a case of course, from ruling on the applicability of particular lines of evidence, and will increase the workload on clerks as they monitor discussions more heavily. But if the rules are defined clearly, the extra effort should be minimal, and the result will be greater peace of mind for the

7437:

into evidence because it was so thoroughly off the topics that the committee wanted to deal with; 80% of the material on the workshop and talk page would have been redacted by the clerks because it failed rules of evidence or decorum; tremendous amounts of bruised egos and bad feelings would have

7191:

Ultimately, the decision illustrates that "discretionary sanctions" are meaningless under this Committee, because arbitrators are unwilling, contrary to the text of the remedies, to let administrators actually exercise the discretion to determine which measures are best suited to stop disruption.

7183:

arbitrators. If you think that it matters whether my block was valid or not, you should have held an open vote on this issue, and then sanctioned either me (for making an invalid AE block) or Dreadstar (for overturning a valid one), depending on whether the block was deemed valid or not. What you

7162:

or otherwise wrong in some way, this argument should have been made in the context of an orderly appeal, as prescribed by the instant decision, and if there had been consensus that the block was an invalid AE action, it would have been undone by me, or overturned by someone else with no objection

7071:

With respect to your other point, as I said below that's really the fault of improper rules and procedures. Let one person dump a little raw sewage into the stream, and next thing you know everyone's dumping raw sewage in, and the stream gets choked. After that, getting what you need out of the

7045:

to make that block at his discretion, regardless of the value of it. Good admins screw things up from time to time, that's not a problem, but I think the point of this ruling is to say that admins should not to be careless with powerful tools like AEDS in the first place (particularly when their

6409:

I understand your belief that only a desysopping would have been a sufficient response, but I don't agree with you that the way we have responded devalues the work of administrators on AE, nor that it will encourage a raft of unilateral overturnings (it's been several weeks since it became pretty

5792:

If this really is an issue of trust and being vetted, I think the fact that I passed RfA rather overwhelmingly (in fact, all of the opposes and neutrals were based on the mistaken perception that I'm some kind of right-wing nutjob extremeist who will aggressively push a POV in articles I've never

5746:

and I thought it was uncontroversial. In retrospect, I guess someone should have called more attention to it during the candidate discussion. The question of CU/OS for non-sysops is certainly a social rather than technical one, just like "the same person must not have two admin accounts" is not

5150:" What. Assuming a succesful RfA the two are synonymous. Digging a bit deeper I would argue that our whole notion of RfA as a guarantor of trustworthiness in general is blatantly false. At best RfA is a decent heuristic for trust with the tools. Even if we establish the best case as the norm, 5078:

No, I think my arguments are pretty sound. The toolkit is a technical issue. You've started out with "it's invalid because you didn't ask me/us first", but that's a non-starter; bugzillas are filed all the time without community input. Then you've moved on to "but they didn't go through RFA", but

4978:

I agree with SV, I think this misses the point entirely. The issue here is not 'social', of course there's a social issue regarding the status of administrators, but this is not what matters here, and it would be wishful thinking to think that this technical change would have any kind of positive

3589:

change being proposed (to let CU and OS see deleted pages)? The policy issue (whether non-admins can have those permissions) is separate. OS can see suppressed edits, which are presumably even more sensitive than deleted pages, so letting them see deleted pages seems like a no-brainer. CU is a

3467:

I don't disagree with your summary of Giano's candidacy's failure, but the fact that he wasn't elected and thumbed his nose at the notion of identifying only postponed the need to intelligently deal with non-administrator functionaries. We have been actively debating whether a read-logs-only role

3305:

I partially agree with Cenarium. The mop itself is not the point, for me. Community approval is a prerequisite for adminship, so it concerns me that somebody (not wishing to make this personal, I've a lot of respect for Bahamut) can be appointed to a position thought of as "higher" than adminship

1719:

makes me deeply skeptical that the Committee will enforce or adhere to the provisions they have stated here. The Committee has a long history of announcing evidence limits, conduct standards and the like but then declining to enforce them. This not only lets cases get out of control but sends the

1586:

Since the Climate change case closed, I think many of the arbitrators (including myself) have rededicated ourselves to what was a declared goal at the time we were all elected, which is deciding cases more quickly. Target dates for moving the case to the proposed decision are helpful to this end,

11191:

Common sense is absolutely fine. If someone surveys an article and thinks the protection can be safely lowered, that's absolutely fine. They should obviously be very careful if the article has been the subject of BLP problems, and, if there's any doubt or possibility they've missed something, it

9725:

That's a good idea. Let's direct administrators to exercise sound judgement, as most have already been doing. We might want to create a special process with notification of the protecting admin and a 7 day delay for articles that were pending changes protected with an OTRS number referenced, but

9600:

The long-term viability of pending changes protection has been compromised by actions taken for the sake of short-term expediency. Not ending the "trial" after the prescribed two months, because of the belief that some articles would still benefit from the protection, has resulted in a situation

9519:

Well, no, it's not fine simply to remove it, because now there's a motion saying we have to add full protection in place of PC2. I'm the admin who set the Carl Hewitt protection, and I've carefully reviewed it and notified myself that, if we're removing PC, then semi is now fine. But now I'm not

9259:

And what happens, pray tell, when semi protection is not justified? One must first semi protect, then remove the semi protection? Such bureaucratic silliness arbcom, you disappoint me. A simple "Administrators shall review the possibility of applying page protection when removing pending changes

8125:

to ensure that all the pages relating to discretionary sanctions are tied up in one place. Things are a now lot less confusing and disparate with the current iteration of the page. Could you take a look and see if that's better, and indicate what else would be helpful? Note that I've asked Roger

7766:

lol - well, the 'everyone' was poetic license. I'm sure enough people read it to be, err... - annoyed, dismayed, repulsed; what is the correct word here? - by it, and hope that many people had enough common sense to ignore it completely. The point is that they should never have been put in the

7343:

Speaking clinically for a moment, the main difficulty in this case - which is a difficulty everywhere on project, but particularly in ArbCom cases where bad feelings are already running rampant - is that there are almost no controls on discussions. Anyone in my academic field will tell you that

7152:

SirFozzie, thanks for the explanation. It is very disconcerting to hear that the (non-)decision depended substantially on "part of the Committee" disagreeing that my block "was a valid Arbitration Enforcement action". This is of course an opinion that people may hold in good faith, even though I

6421:

I do agree that the case took longer than it should have to be resolved. We are making concerted efforts to move cases more quickly. One issue here was that the decision was literally written "by committee," with several different arbitrators contributing portions. I think recent experiences are

6290:

Hi Deskana, didn't recognise your new signature since it's just a bunch of boxes on my computer. The point that is being made here is that disruptive editors cannot log out to hide behind the privacy policy in order to perpetrate their disruption; there is a specific exclusion in the policy that

6257:

You are correct; I've seen many instances of CUs taking into account how much information can be determined by revealing the IP, and this being part of their decision making process. Several times the CU has issued a trout slap by telling the offender (either publicly or privately) what sort of

5560:

admins to CU/OS roles does not mean it wasn't the understanding of the community. I suppose there's also no policy which says that the Arbcom can't hand out the deletion and blocking tools to whoever it wishes, but if it decided to so that would be a policy change, not just a technical change.

5559:

I find it strange that some ArbCom members seem to be saying that policy is only what is written down. The written policies are simply descriptions of the practices the Knowledge finds acceptable. Just because no one ever felt it necessary to write down the long-standing practice of only appoint

3773:

You mean an RFC to enact a not-previously-existing restriction that users must be Administrators before ArbCom can appoint them to CU or OS roles? Unless I'm missing something somewhere, the restrictions listed (vetted by ArbCom, identified to the Foundation) don't mention administrator status,

3208:

As a matter of fact, yes there have been issues with inadequate numbers of both CU and OS candidates. However, unless I am mistaken this adjustment is just for purposes of the audit subcommittee. These users would not be involved in blocking anyone or actually suppressing anything, they would be

2424:

roles are essentially three: bureaucrat, checkuser, and oversight. Each of these relies upon privileges present in the administrator role. While that may have been a good idea for a small project, as things grow, enabling security access role granularity is just part of the growing up process:

10879:

I appreciate that you are genuinely and passionately concerned with BLP enforcement. But so are many other admins, and other editors. In the future, if you believe that another administrator's clearly good faith actions are so misguided as to constitute a BLP emergency, blocking him yourself is

10086:

When removing pending-changes protection from a biography of a living person, administrators should replace it with semi-protection for an appropriate length of time. Any administrator may review the protection level and switch to no protection or full protection. Where there is disagreement, a

10048:

Concern about legal liability misses the point. As a practical matter, if Knowledge becomes "the free scandal sheet anyone can vandalize", we're screwed. Implementing level-two PC protection on a wide range of BLPs is an important tool in preventing that outcome. But the pending changes feature

7785:

to manifest and institutionalize its own ideals, because if it doesn't do so its ideals won't be worth spit, and the choice will be made for it by people who could care less about ideals. I dislike Hobbes on principle, but one thing that Hobbes was quite correct about is that in the absence of

3237:

RfAs are often many years old, and many current sysops say they wouldn't pass another RfA now, so how useful is that as a prereq? My preference is that all OS/CU/AUSC appointments are done after an election, because at least that is fresh data, and focused on the candidates application for the

3115:

I don't know, that is certainly how I read it, and I know it's how a lot of non-admins read it too; perhaps you are correct, though, and what he means is that we should give adminship to anyone we appoint as checkusers. I can't, however, imagine that such an idea would get even a single support

2779:

I am concerned when arbcom goes beyond its authority, yes. But in no way I've been vociferous. This isn't really a question of procedure, but of staying within its role. This isn't a minor detail, this is a configuration change (requiring a bug request, etc), apparently politically charged. The

2624:. Your position is that only administrators should be eligible for advanced permissions and appointment to the Audit Subcommittee or election to the Arbitration Committee. I don't believe that this belief is widely held, but as above, I invite to initiate a community discussion to verify that. – 2546:

No, I really don't think you should be giving advanced permissions to non-admins. I don't know how I can be any clearer than that. If this person truly has the trust of the community, they should be able to pass RFA. If they don't have the trust of the community, then why are you giving them

2374:

While I personally support the move, I am compelled to point out that changing permissions affected to a usergroup should be a community decision. The ArbCom has been delegated the authority to oversee the use of CU and OS permissions, this does not extend to changing those permissions. I would

2307:

How many times have non-admins stood for those positions? In the last ArbCom elections, there were only two candidates that were not either admins or could have gotten their mop back by a simple request on BN. Perhaps the kind of people that would have an interest in being a functionary highly

1885:

In Arbitration Committee elections in recent years, there have been viable candidacies of non-administrators; current Arbcom members may also wish to resign as administrators but still have need of the CU/OS tools whilst continuing their role on the Committee. We can also learn from some of our

842:

Think I'm clear. A hypothetical checkuser who's been inactive for months, and who's shown so sign of becoming more active, you might begin this process at any time. Another hypothetical checkuser who's been inactive but has indicated they intend to be active and taken steps in that direction,

639:

From the 4 diffs the ArbCom present as evidence of my tendentious editing, one is not from me. Accusing me of "tendentious editing" is only possible if the content of the article is considered. In the first place does the ArbCom not judge about matters of content, and secondly has the ArbCom no

11008:

of which you disapprove, or any more wheel warring, involved blocking, disrespect for consensus, and useless arbcom injunctions. You could assuage these fears by apologizing and promising to work more cooperatively with the community in the future. But until and unless you do this, approving a

10328:

The past is repeating itself, in the form of a community-disrupting injunction, and foundation endorsement of the same. Removing PC protection from the remaining articles was supposed to limit the damage caused by the never-ending trial, so that I could, say, propose a policy that PC level two

9605:

efforts to create a long-term policy for implementing pending changes will be opposed by many editors who are angry with the trial situation. Exacerbating this problem, by blocking an administrator for attempting to actually end the trial as supported by community consensus, is ultimately very

9225:

The Internet never forgets. Since at least one ArbCom member seems to have been using GMail to conduct ArbCom business since its inception, you can rest assured that Google knows what Arbcom thinks and how we conduct business. Should the benefits outweigh the drawbacks, I expect they will do

9081:

as unnecessary and likely to cause trouble. I am not aware of any consensus or extensive public discussion about this topic. In fact I don't see any public discussion of this procedure on resolutions (which clearly has no privacy issues) prior to its adoption. If I missed it I'd be happy to be

8425:

HJ Mitchell: That's a very valid point. But, per Skomorokh, I don't think these general improvements to internal procedures are valueless (even if they do use up time that might be better spent doing other things). ArbCom is free to at any time update its internal procedures (and perhaps next,

7246:

so long as s/he can somehow establish some remote connection to some arbitration case, so that the editor is question is effectively screwed - unable to edit and forced to waste time and effort going through an extended process to get the sanction removed, even if the editor did nothing really

6808:

If an admin makes a good faith judgment that an AE block is needed, the community or ArbCom can deal with it. Except for obvious stuff like a possibly compromised admin account issuing an AE block to Jimbo, endorsing a decision to reverse an AE block is a one-way street to bedlam. The decision

5801:

So, let me ask this: nobody is unhappy that I got put into a functionary position? I think that seems to be the case, since people have been careful not to malign me (which is appreciated). If that's true, and nobody thinks I was "backdoored" in, then why would it be a problem to formalize it?

5346:

You seem to be holding somewhat contradictory positions - you want the candidates subject to intense scrutiny, yet you wish to discourage people bringing up relevant concerns privately? Someone may wish to submit their concerns privately because they may fear reprisals (e.g. from a politically

5131:

I'm not talking about adminship here, I'm talking about RFA. In either case you need general scrutiny of the candidate (sockpuppetry, copyvio, other difficultly identifiable behavior issues), the current appointment process doesn't provide for enough scrutiny, arbcom isn't omniscient, the more

3947:

Malleus, you may not care if people know where you're editing from, but please imagine that you did care—that you sometimes edit from work, that you sometimes edit contentious articles, that you've sometimes had editors you've opposed try to find out who you are. So the question is: who can be

3344:

I urge Bahamut to stand for RfA if he wants to obtain CU/OS, then take it from there. We can't have situations where the rules are changed to accommodate one person (I mean no disrespect to Bahamut; I know nothing about him, so I'm speaking generally). We had a situation during the last ArbCom

3086:

So you too are implying that anyone without an admin flag is untrustworthy. I actually find this more concerning than any of the other arguments on this page, and it bodes very poorly for the project that at least some administrators think the only trustworthy people on the project are...them.

1750:

I have started a discussion on the clerks' mailing list to establish precisely how these procedures will be enforced, but I expect that, now that the standard practice has been firmly codified, the clerks will be able to more consistently ensure these limits are followed by participants in the

576:

Which is why it somewhat surprised me. There's an active discussion in another case about reducing the use of discretionary sanctions and then out comes a brand new set. But alas, it's hardly something that can be addressed overnight. I'm glad to hear it's on the agenda—nice to know that I say

10483:

Kww: nowhere did I say your actions in particular were injudicious. I never even used the word. In fact, I said that your block was unfortunate, and I meant that. (I'd also like to remind everyone that this is my opinion as someone asked to help the tech staff talk to you all about this. It's

9682:

When removing pending-changes protection from a biography of a living person, administrators should replace it with semi-protection for the same length of time. Any other administrator may review the protection level and remove it, reduce the time period, or increase it to full protection, as

9387:

If you want to remove PC, replace it with the prescribed protection, and then remove that prescribed protection, all in the span of three seconds, with an edit summary expressing that no protection of any type is needed anymore, you've done your due diligence in assessing the threat posted by

7101:

Oh, and dealing with one of your other points.. I think that I'm not airing any Committee dirty laundry to state that the Committee was divided on how to view (and thus, how to handle) this request. Everyone has a vision of ArbCom being a vast monolithic entity (The way it got put to me by an

6853:

AE blocks are infrequent, and reversals of them are rare so we may never clearly see a connection between this decision and future events. Nevertheless, the precedent is now set that a second admin can decide on the weakest of grounds (a preliminary community discussion with some disquiet but

6415:

With regard to the scope of the case, it sometimes is quite difficult to determine precisely what the scope of a decision will be until the evidence is finished. You are probably right, however, that we could have done a better job of defining the parameters of what subjects were likely to be

6276:

I find it somewhat odd that we have now been told by the Audit Subcommittee that we are allowed to reveal IPs (where allowed by the privacy policy, of course), but we were previously told by the Audit Subcommittee that we should avoid even revealing a person's ISP (which is by definition less

5827:

There are two things going on, one regarding your status—which does not appear to be the problem. The other appears to boil down to (IMO) an uneasiness in the community over WP being increasingly run by a clique; were it merely for their own benefit that would be one issue, but that's not the

4854:

You're responsible for the good use of the permissions yes, but how could it possibly give you the authority to change the actual permissions ? Bugzilla requests are made, have always been made, by the community of users, developers will never recognize an arbcom-decided bug request regarding

3290:

It can be helpful in some cases, which is already a good thing. Just so that this is clear, I think adminship should be a requirement for regular CU/OS because this work requires to perform tasks often similar to adminship so this allows to see how good the user is at it, CU/OS is really just

2250:

Furthermore, we are only granting the ability to view deleted entries - administrators can do a lot more than that, so I don't see how this is a backdoor at all. Being an administrator is not a social requirement for appointment to checkuser, oversight, the Arbitration Committee, or the Audit

7040:

you are contradicting the evidence in this case. The block I got was useless, unnecessary, hasty, apparently punitive, and in all ways ill-considered. Not even Sandstein has argued that there was a functional purpose to it - he's focused his arguments on the technical point that it was his

5665:

any of the relevant policy pages. I am not a mind reader; I cannot tell what people will find objectionable, nor can I tell what people will object to if prodded enough, but I suspect that given enough invitations to object, we can find a Wikipedian or two to object to essentially anything.

3238:

specific role. However the committee has chosen to return to use a committee vote for the selection process, and it seems to be working ok as well. The "many eyes" of an RfA can also be brought to bear on the nomination pages, with the added benefit that ArbCom allows for private opinions.

2903:

for the decision on oversighters ('masqueurs'). It was decided unanimously that oversighters were chosen among admins, so there was no question regarding addition of view-deleted and co for them, and actually they don't have them. Checkusers however don't have to be sysops, a few aren't, and

10839:

I admit the hypothetical possibility of a future consensus to undermine the blocking and page protection policies which permit BLP violations to be forcibly stopped, or community actions reversing blocks and page protections to such an extent that the BLP content standards are substantially

9984:

Sure there is; it's called "due caution". That is, once an entity such as Knowledge has actual knowledge of defamation issues, it could be legally actionably irresponsible for that entity (us) to allow them to recur when we possessed the ability to prevent such recurrence. Beyond the mere

9708:

When removing pending-changes protection from a biography of a living person, administrators should exercise sound judgment. Generally, articles that have been on pending changes should be switched to semi-protection, but the admin may, at his discretion, switch to either full protection or

8897:

I understand that the arbitrators have limited time (and, for all I know, this may not be the correct venue), but I, for one, would really appreciate it if an arb (or indeed more than one arb) could answer WFCforLife's questions and my own questions. It would be greatly appreciated. Cheers,

8583:

It's nice to have something with teeth to put an end to this nonsesnse. It would have been nice to have something specific detailing what admins can do to enforce the motion, but I guess we'll have to sort that one out when someone appeals a sanction. Speaking of which, if I make a block in

7884:

Hmmm... If there's a transcript of that talk or paper associated with it could you post a link? I'd be interested in taking a look at it. It may just be my relative inexperience with procedures, but I have a hard time seeing the mandarinism. As best I can tell, admins are chosen through a

5742:

I thought it was clear from the initial announcement that non-admins could submit candidacies for AUSC. In the initial discussion about creating AUSC, I considered (don't think I posted) proposing that AUSC have some members from completely outside the en.wp community, e.g. checkusers from

5459:

What was discussed off-wiki was essentially "Is it a current policy requirement that CU/OS'es be admins, and if so should we reject Bahamut's application outright?" That's part of our job in vetting candidates before submitting them to the community. ArbCom consensus was that there was no

5378:

If RFA is a better venue for evaluating AUSC candidates and yet we want non-admins to be able to serve on AUSC, I don't see any problem with expanding the scope of RFA to also evaluate AUSC appointments. I could easily imagine being willing to support someone for auditor but not for admin.

2235:

attributing evil motives to every single action ArbCom takes. How do you reconcile "WADR" and "smells like wanting to be able to 'back door' somebody into adminship"? With all due respect, that seems kind of passive aggressive (see? I can do it too! You can't get mad, I said "with all due

5248:

is barely publicized, and ArbCom makes decisions independently of community input, so it's not clear why certain people are chosen and others not. Also, people are allowed to make private comments to ArbCom, which the candidate may never see. So it's problematic for all these reasons. More

3679:

is apparently unaudited and conceivably makes far-reaching disclosures (obnoxious BLP material, say) that can only be undone by erasing the person's mind. For that I'd consider CU/OS to be "cumulative" rather than "standalone" in terms of trust level, if they allow access to deleted pages.

2690:

You are giving me reasons why the change should be made, it's not the point of my objection, again I agree with the move. I am saying that this is not up to ArbCom to make the request. Any user (including an individual arb) can make requests on behalf of the English Knowledge when they are

153:

else that CU and OS might give him access to that he wouldn't otherwise have without the admin it? I'm certainly not saying that AUSC should be "admins only", but I think it's important for the community to know whether or not he would have access to things normally only granted via an RfA.

2976:

of ArbCom ? It was soundly rejected, and Mike Godwin even made clear that this was not going to happen for legal reasons. Of course this is of little relation to this case since CU/OS have higher requirements, but this shows that you should really not do things like that without community

9487:

The motion is irrational. A great deal of PC was added thoughtlessly, or with a view simply to testing it out to see how it fared. There is no way PC level 2 should be replaced in every case with full protection. Has there been lobbying behind the scenes about this by interested parties?

7851:

are liberal-democratic ideals. The first implies equal footing in decision making for all, the second reaches for balanced, multi-positional relativism, and the third largely revolves around mutual respect. It's not a monarchy of any sort because there's no sovereign. As I said, it's a

6403:

I'm sorry that you disagree so strongly with the Committee's decision in this matter, but you can have the consolation that your input throughout the case was carefully considered. What happened here was that you imposed an arbitration-enforcement sanction, and it was reversed by another

5656:(sigh) If there had been a policy change it would have indeed been brought for community discussion; ArbCom doesn't change policies by fiat. You'll see plenty of fairly minor things being brought forward for community discussion and ratification over the next month or two. The way this 3814:

A wiki-wide RfC wouldn't be a bad idea, asking how we want CU/OS to be distributed. It seems to have changed a lot over the years (sometimes election, sometimes appointment), but as I recall it was handed out in response to need, which usually meant the recipient was an active admin—and,

3454:

there having been a CU election, without there having been an election for promotion to ArbCom. That's where the cabalism unease will come from, not to mention that editors will be worried that someone who hasn't been through any of those processes will have access to their IP addresses.

784:

delays in response to an email to the OTRS oversight queue. (I'll note for the record here that the response in both areas is exponentially faster now than it was a few years ago, where weeks to months was the norm for SPIs, and oversight requests were lucky to get a response in a week.)

11270:" That is simply not true. You know that. I paused. I discussed at ANI. Your objections at the time had already been endlessly discussed, and you brought absolutely nothing new to the discussion. I explained that to you, and proceeded. Note that you were asking for people to go back and 9626:"Where flagged revisions has been set for reasons of "violations of BLP policy" or (OTRS or somesuch), the flagging should be substituted with the equivalent level of protection until the admin setting the protection is notified, and the article listed on a page for review for 7 days". 4006:

Just noting that I wasn't talking about myself in my post above. We have lots of editors not aware of these issues, not aware of how to use proxies. The Foundation has just made it a high priority to attract new people, and we can't expect everyone to be aware of these ins and outs.

6073:

I have deep doubts about topic bans generally, but if we choose to enact them they need to be broad and concrete. The value of making topic bans narrow lies more in congratulating ourselves for our judgement and beneficence than it does creating a useful and persistent restriction.

5401:

related to adminship be forced through that process? I don't have a problem believing that the community as a whole may indeed be fed up with RfA as a bottleneck and willing to tolerate candidates for advanced permissions who don't necessarily have track records as Knowledge admins.

3483:

on Bahamut0013 because I didn't have anything to say. I don't recall any significant interactions with him and there were no obvious red flags. There was an open process where user input was specifically requested. The fact that it wasn't in the snake pit at RFA doesn't change that.

144:

The format of the process means that only ArbCom knows who applied. I wouldn't ask them to disclose the identities of any applicants who weren't allowed to stand, but I think it would be good for the community to know how many (if any) of the people who filled in the questionnaire*

6859:

of an AE block, were faulty. However, there was no emergency, and if Sandstein was in error, a consensus would have arisen to unblock, and the precedent is now established that an AE block is no different from any other (except that reversing an AE block might lead to a reminder).

11041:

believe that the PC tool can be effectively used to stop the most serious BLP violations, such as material that could be defamatory with no or inadequate sources provided, there was no need to scuttle the future of pending changes by inflaming community opposition, simply because

9606:

harmful to BLP enforcement, because it is going to make the anti-PC editors even angrier, and sink any efforts to apply the protection to a large number of BLPs per a new policy. Scott's actions are anti-BLP, and support the use of Knowledge as a vehicle for anonymous defamation.

3168:

high standards for granting CU/OS, and that it is perfectly reasonable to consider that passing RFA is a legitimate test of the trust of a user and provides for scrutiny and feedback (and would certainly provide much more than the CU/OS or AUSC elections as currently practiced).

9580:

The motion is just a sign that Arbcom has misinterpreted the case set before it. I removed protection from some articles, I protected some articles. I made one mistake that has been pointed out (and one supposed error that isn't one: no one has pointed out any reason to protect

7500:

Having said that, I do think the basic contention that the culture of arbitration pages can and should be changed is valid. The move from more-or-less free-for-all aticle talkpages to ones where comments will routinely and without substantial opposition be removed on grounds of

220:(if any) applicants weren't allowed to progress. If ArbCom has decided it wouldn't be appropriate even to give that much information, then fair enough, I trust your collective judgement, or perhaps I should have been clearer that I was only seeking a number and not any names? 1816:

editors in a complicated case will be hard-pressed to do so within the limits. Equally, someone faced with many allegations from many editors will probably have difficulty keeping within the limits, especially if they also have new material about others they wish to submit.

7715:

Again, the purpose here would be for arbiters to preclude material that they (and common sense) determine is off-topic, inappropriate, unnecessary, and/or just plain pointlessly crapulent. Everyone will obviously have the opportunity to make a case for being heard - e.g.

5939:. Hopefully topic bans will become useful tool that actually cut all disruptive edits. Instead of, you know, causing the banned editor to switch from "disruptive POV-pushing in articles and talk pages" to "disruptive wikilawyering everywhere about the scope of his ban". -- 1818:

I suppose the underlying point here is that these are guidelines and there will be situations where they are inappropriate. However, 500 words and 50 diffs is a good starting point and permission to present a greater wordage/diffage can always be requested where needs be.

3635:~589, even though it was advertised at cent, etc (not in the watchlist notice though ?, but it wouldn't have changed much). So clearly RFA is adequate at providing greater scrutiny and feedback, which is essential for candidates to the highly sensitive CU/OS permissions. 10810:

a page protection when reasonably believed to be necessary to stop badly sourced contentious material from being inserted, the community can decide to remove it, either immediately or later, if the circumstances are judged to be otherwise, consistent with the protection

8844:

Sorry if the following paragraph is a little TL;DR. And before I sink my claws in further, I acknowledge that Arbcom was right to step in. Arbcom's raison d'être is to safeguard the project; prolonged, uncivil edit warring falls within that remit, however petty the root

10818:

affect substantive content about living people. Editors, even admins, can be blocked to stop potential defamation. But administrators must never place involved blocks against other admins to stop activities only indirectly affecting BLP content, such as unprotection of

8358:

not listing it here is not the end of the world. I would though have expected that in the event of the Subcommittee requiring an extended period of time to decide on a recommendation that both the user and the Committee be informed of this, rather than just the latter.

3571:

The issue for me isn't—this person isn't an admin. The issue is—this person has been selected by a very small number of people, and it's not clear that they've demonstrated a need for the tools, or a prior interest in doing the kinds of things the tools are needed for.

5893:

I think it would be helpful if the policy theorists here (SV, Cenarium, etc.) could look at the technical RFC. I see some issues arising from it that I don't really have a handle on. I made some comments (basically "go slow") but I'm probably out of my depth there.

2999:

making the changes, it was so that there was a request that the changes not be made to be considered alongside the ArbCom's request that the changes are made. I don't know how you managed to jump from me suggesting that to me implying that the request was a decision.

2308:

overlap with those who would enjoy being an administrator? Or perhaps the fact that it had never been done before was discouraging non-admins from even standing for such roles. There's a correlation here, but I'd be very hesitant about implying any causality here.

1264:

Could you clarify what is meant in the announcement by "votes cast"? Given that the last AUSC selections were made by ArbCom appointment rather than straight elections, does "votes cast" refer to internal committee voting, volume of pro-con email from the community,

10927:

If arbcom thought that BLPs were being unprotected too quickly or carelessly, they could have imposed specific rate limitation and due diligence requirements. There was no justification for simply suspending the ability of administrators to exercise good judgement.

9438:

make the injunction stick. Given this injunction, and the willful failure to deal with Scott's wheel warring and involved blocking, many of the current arbitrators may have difficulty in seeking reelection. Unfortunately, there is no process for arbitrator recall.

747:

It's probably more accurate to say that ensuring widespread responsiveness to all members of the community is the primary goal; as long as that's happening, there is no particular problem with specific responsiveness to well-established members of the community.

6750:

With all due respect, HJ, did you expect something else? The principles seem pretty clear on the best practices in this area, the committee promised to be clearer, etc. Anything else would've required a bit more agreement within the committee that wasn't there.

6427:

Thanks for your candid input and for your past participation in AE. As discussed on another page recently, your plan to take a break from this area may be for the best at this point, and I look forward to seeing your work on other areas of the project. Regards,

6039:. And I am not going to hunt for the requests for clarifications (there was more than one?), the discussions in AN/ANI, in user talk pages, etc. Maybe I'm only noticing the exceptional cases, and in reality most cases are dealt with swiftly and without drama? -- 10359:

the article, and determine what level of conventional protection, if any, should be used to replace it, OTRS situations excepted. Instead, administrators' hands are tied with useless bureaucracy. Please review some of the comments by community members here, on

2477:

The community's input isn't needed for #1: we don't hold RfC's on how to configure our networks or how much storage space to buy, do we? Why not? Because those are technical implementation details, just like this is. As far as #2 goes, the community's input

11176:

different from the current protection policy? Is it really necessary to re-declare that here? I don't like ArbCom as much as the next guy, but the answer isn't to try to prop them up with a corrected (silly) motion. Just ignore this one and move along. :-) --

9863:

The ticket most often contains the rationale, and often the information cannot (space reasons) and/or should not (privacy policy) be released. In cases where I cite an OTRS ticket, I almost always also use "Violations of the BLP policy" as the primary reason.

5342:

I would not be happy to learn that a significant number of people are withholding relevant comments on the candidates publicly or privately because they think their comments will be ignored or not have a meaningful impact on the result: this is simply not the

812:

Technical question. I may have missed it, but I don't see it specified in the motion. Does the clock start blank slate from the time of the motion, or does a checkuser who's been inactive fot 2 months have to make the 5 actions in the next month to meet this

7441:

If the committee works out these kinds of tightened procedures, they will find that AC cases progress far more smoothly, far more civilly, and far more quickly than they currently do, with far less negative fallout at the end. It requires more effort at the

5276:

as a prefix to their comment if it pleased them. All the comments submitted were read by every arbitrator voting on the candidates. Getting off-topic, but candidates are able to receive anonymized feedback about the privately submitted material upon request.

7132:

of a "monolitihic entity" rather than a group of human beings. Leaving aside everything else, surely you and ArbCom must acknowledge that taking two months to leave us basically back where we started is not a satisfactory outcome from anybody's perspective?

3193:

RfA, so the hope is that, if there's an obvious issue, it will be spotted. The fewer eyes, the less likely that is to happen, and the benefits of extending CU and oversight access aren't obvious anyway. Is there a problem of not having enough CU candidates?

8830:

I hope that the issue itself is not an all-consuming fever. But whether for simplicity, due to oversight, or simply down to twelve elected people having an off day simultaneously, this motion makes a pretty good attempt at giving what should be a non-issue

7409:

editors are required to formally request that a particular line of discussion be introduced into evidence before presenting anything on it, giving arbiters the opportunity to deny or limit what gets said before it gets poured all over the page and stirs up

6337:

As the administrator submitting the request for arbitration, and as one who has spent countless hours helping with arbitration enforcement, I am very disappointed with the decision. The bottom line, as far as I can tell, is that the Committee is simply not

6584:

With apologies for answering a question I was not asked, it seems reasonable to AGF here. One assumes that the evidence was not overlooked, but that ArbCom didn't agree with it, or didn't think it justified further sanctions. I notice that Dreadstar is on

1920:

example, a checkuser couldn't block based on their findings, they'd have to go to RfPP to request an article being targeted by socks be protected. What's the benefit of having a non-admin functionary other than proving that it's theoretically possible?

10400:

this time, and point out any that struck him as being "injudicious". So far, out of a couple hundred decisions I made, only one has been suggested to be counter to any policy or guideline, and no one has really made a conclusive statement on that one.—

6346:

Even though the decision tells us that AE actions may not be unilaterally overturned, its practical effect is the opposite. That's because if admin A were now to decide on a whim to undo admin B's AE action (because A is certain that their judgment is

5962:

feature. If you want to disincentivize scope-lawyering, address that directly; blocking for any mention of the topic by sanctioned parties by default in the absence of disruption is excessive, open to abuse, and would in all likelihood lead to serious

5743:

non-English wikis with no connections to enwp politics or personalities, i.e. actual non-editors and not just non-admins. I still don't know if that's a bad idea or not. Bahamut's non-admin appointment to AUSC was announced the WP Signpost 2011-04-04

5354:

And those are the most important things here - respect for privacy and a high degree of trust. And neither the requests for adminship process nor the administrative rights package conveys these qualities: they must be present in the editor themselves.

2435:

retain their administrator bit? That question is absolutely appropriate for community input, and the community has already failed to oppose a non-administrator being appointed to the audit subcommittee, an oversight role that requires both CU and OS.

8914:

get some broad input at a discussion page nutting out where/how we use each horizontal line, it'd be great if we got consensus broadly on a range of issues. I must say I was struck at how productive some of the discussion seemed to be a few days ago.

10967:

It is hypothetically possible that certain articles are associated with such severe BLP problems that they can't safely be unprotected for even an hour or two. But removal of protection would then constitute an emergency, which you say didn't exist.

7609:

come out, always. Perhaps it might work better to flip things around. Have an initial voting round where the committee decides what the scope of the case will be, with principles, and then ask the parties to show evidence related to those principles?

6956:). Again, making no comment on the questions about reliance on DS or appeals, which is probably the more important point which got lost in the noise again; responses to those questions might be able to sort some of this out (well, hopefully anyway). 4087:

the admin and functionary corps. A subtle semantic difference, perhaps, but one I consider important. I think this one decision was pretty minor, but indicative of the mood of the current committee towards the issues that have been raised recently.

239:

No; your question was clear- while the number of applicants may seem like an innocuous detail, disclosing such information does not complement the objective of instilling a high degree of confidence in the confidentiality of the appointment process.

2796:

of MZM's access, it was obviously outside of their role, arbcom just can't make requests on behalf of en.wp to other sites, hopefully this didn't pass. Yes, I think the community should be watchful of arbcom's excursions outside of its authority.

2043:

I can't imagine a situation in which an Arb would want to resign adminship but retain CU and stay on the Committee. Giving up adminship would serve no purpose in those circumstances; anyone wanting not to use the tools could simply stop doing so.

3046:

give the ability to see deleted contribs to non-admins. I can't imagine how there is any legal basis to that position, we don't know the real life identities of most admins and we do know them, or at least the Foundation does, for functionaries.

7196:

won't have to (because angering so many vested contributors would compromise our chances of re-election) – but should we ever happen to disagree with what you do, we won't support you in any way, and instead we will spend two months criticizing

3259:

John, the reason I mentioned RfA wasn't for the popularity aspect, but because many eyes were on that person's contribs, which would often (not always) throw up any very serious issue. If the Committee is also not requiring elections for CU/OS,

7046:

actions are at a questionable edge of a ruling), and if they screw something up somewhere they should be sensitive and open to the fact that they erred, and not stick to their guns on technicalities till the whole durned ship sinks around them.

3620:

The AUSC appointments didn't interest the community, the selection process is in the hands of arbcom, not of the community, so people won't be enticed to participate. During the 7 days of the AUSC appointment's 'community consultation' period,

6823:

If they could deal with it, we would neither have an unblock, a case, or a need to comment here. I think the decision says it was the totality of the circumstances which prompted this ruling; the apology was merely one of those circumstances.

2867: 6330: 6561:

I'm sure everyone (or most everyone) appreciates the Committee's clarification of best enforcement practices. Brad, I've noticed in several instances that you refer to Dreadstar's unblock as an isolated incident. Could you explain why the

5216:. This does not make them untrustworthy people. The fact that the administrative rights package is currently a technical requirement for the proper functioning of other privileges should be remedied, and that is why the bugzilla was filed. 9252: 5022:

I'm struggling a bit Cenarium to see the relevance of RfA to CU/OS rights. Can you explain why you see a connection between the two? I can't ever recall seeing an objection at RfA along the lines of "can't be trusted to have CU/OS rights".

10895:

bot account could have been used to more quickly and efficiently remove PC protection from BLPs in the way mandated. Being "free to look at the circumstances of a case, and make a call" is exactly what the injunction forbade admins to do.

3139:. You don't seem to have actually read what I wrote. I didn't say "give all checkusers admin status", I said "*don't* give checkuser status to those who aren't admins". There's a gap between "trustworthy" and "trustworthy enough to get ". 11274:

when the consensus had already been reached to remove pending changes from all BLPs. People sometimes react as if you were concerned that I was unprotecting BLPs, but, in fact, the articles you were objecting to were articles where I had

9417:

That's beyond ArbCom's power. Protection is added, removed or modifed in accordnace with the protection policy at the discretion of the admin or as a result of an RfPP request. That can't be changed without seeking site-wide consesnsus.

3223:"These users" is just one, at the moment, but yes: the entire point of decoupling permissions is to allow the isolated function of review of advanced permission use, without being able to function as or needing to be "an administrator". 1512:

be. Thus, when the actual timeline differs, we can say "where did it deviate?" and "can we learn any lessons from this to help avoid such problems in the future?". Call it a stepwise approach to professionalism and process improvement.

8242:

Actually, I don't think Beeblebrox was referring to me for two reasons - firstly, I am in the announcement which 'brox was responding to, secondly I may not have used the tool much (hence why I have requested the removal of the OS flag

6107:

Hi Cla, I think we're not going to get into hypotheticals, and instead ask the parties to use their best judgement and consider the discretionary sanctions carefully. We're not going to be looking to pound a square peg in a round hole.

7178:

Even if one were to agree that the validity of the block ought to be relevant for the purpose of the decision, the failure of the Committee to arrive at a clear decision is still a failure of leadership and organization on the part of

4762:

I did everything I could think of to ensure participation. If you have any suggestions on how to obtain additional meaningful feedback, I'm all ears. (serious question) Perhaps the 2012 candidate pages should be transcluded at WP:RFA?

2714:

goals, it's a simple technical change that should probably have been applied at a meta level long ago. As food for thought, adding viewdeleted privileges to other rights bundles is not a new concept, as seen by the list that follows. –

9383:

protections. The point here is not to leave articles hanging when they need protection; to prevent a less than thoughtful admin from performing an en-masse removal and in so doing leaving vulnerable articles where some protection is

6211:

The tradition is that CUs generally try to avoid linking IPs with named accounts publicly and explicitly even if the privacy policy would allow to do so, and instead often handle them through quiet blocks (by themselves or by proxy).

1801:

biggest difficulty though has not yet been addressed: encouraging people to submit concise actual evidence, that is factual material in the form of a brief statement for context, plus diffs (ie "X" has been uncivil, describing "A" as

1221:

I'd like to thank all candidates and arbs involved for volunteering to preserve this obscure but important institution, and to commend the committee for not being afraid to appoint a non-administrator. Best of luck in the term ahead,

8021: 6342:

in having its decisions enforced effectively, and is not interested in administrators doing their job, that is, preventing the disruption of a collegial and civil editing environment in particularly designated sensitive topic areas.

4668:

One thing I would ask is that the discussion not be personalized, and that people not be made to feel bad for disagreeing. Disagreement is good, it's healthy, and the concerns are valid, even if you disagree with them, not insane or

10840:

jeopardized, necessitating foundation intervention. But we are nowhere near that point yet. The community generally does take BLP pretty seriously, and allows administrators ample use of blocking and protection tools to enforce it.

5206: 6320: 7694:

to do it. Can you imagine what would happen at the US Supreme Court if they allowed random citizens to stand up and say whatever came to their mind at whatever length they desired? Let's see them tackle an abortion ruling under

6162: 1901:

as administrators, but still be checkusers and oversighters? That falls into the category of "doc it hurts when I do this" ("don't do that"). It would be analogous to the President wanting to resign as President, but retain the

9245: 11170: 8399:

Better procedures make for better case handling in the long run, and it is not clear that the two are mutually exclusive in the short. I for one am glad to see the Committee thinking critically about putting its house in order.

3915:

opposition to Bahamut's appointment as a community AUSC member, we wouldn't have ever proposed it. One of the problems with a consensus-based system is that those who don't see any problem with a proposal often don't show up to

561:

The committee is actively discussing ways in which discretionary sanctions can be improved throughout all cases in which they apply. Public comment will be invited in due course, but is obviously already ongoing at the AE case.

4152:

Correct, this is not a policy change, and there never was such a policy. There is no policy that forbids non-administrators from consideration as checkusers, oversighters, AUSC members or arbitrators, and there never has been.

3542:

involves many eyes, whether it's an RfA or an ArbCom election, or a rigorous CU election process. Hardly anyone seems even to know when or how these CU appointments are made. For example, how did Bahamut come to be chosen from

2973: 10137:

flagging misses this, there's an opportunity for the flagging admin to sort the issue (probably by getting the article on multiple watchlists). As I say, I'd want more - but I'll compromise. Informing an admin isn't onerous.--

132: 10676: 9633: 9481: 9378:

Read the comments by the voting arbs. A majority of the voters, Jclemens, John Vandenberg, Risker, Kirill, and Coren all mention in one way or another that this is a stopgap and does not impede the normal process of removing

9278:, in addition to indefinite semi-protection, with a view to stopping all but the most legitimate of edits. I had intended to remove PC and leave the semi in place. I certainly can't justify adding indefinite full protection. 7799:

take it as you will. I'm fascinated by the potential inherent in Knowledge for a really properly liberal-democratic system, but in the long run if it decays I'll shrug and see if I can get a few published papers out of it.

6054:

of administrators currently keeping AE ticked over are level-headed, sound folks who deal with topic ban complaints well—although there admittedly is quite a diverse, and interesting, range of approaches from sysop to sysop.

10006:

of full protection that prevents defamation from being inserted in articles: all we can reasonably pledge is to react promptly when it comes to our attention. Remember: my inclination and preference is to completely disable

9345: 9953:

Granted, and that's one of the problems with semi-protection: people can't try and fail, so you can't see if people are interested in trying. That's why watchlisting articles that you unprotect is important. I reprotected

9533:

Heee. Well, use IAR on that specific case, and for good cause. If you get arbcommed, I'll be happy to write you a testimonial! Meh, this is what happens when we put aside pragmatism and common sense for inflexible blanket

2940:

making the changes. I do happen to think that the configuration of the CU/OS userrights is the purview of the arbitrators, but that's not relevant to this discussion because, as I said, this is a request, not a directive.

1720:

implicit message that one can violate the rules with impunity, or indeed that if you follow the rules, you're a chump. Do we have any assurance that the Committee will back up these sensible provisions with their actions?

181:

they do have (or have had) OS/CU who are not admins. I expect we would similarly allow the non-sysop to view deleted content as required for their duties, and no other permissions would be granted to them without an RFA.

10774:

Semi has its uses. As does PC and, in extreme cases, FP. However, it is not within the remit of the Arbitration Committee (which, in name if nothing else, is a dispute resolution body) to dictate a new protection policy.

5878:

Woah, that discusses unbundling a whole lot of different bits (not just OS/CU), making the privilege graph a LOT more complicated. I wasn't expecting that and it makes things different. I'll try to comment over there.

2199:

I expect that even without the CU tool itself, auditors would still see a heck of a lot of private info by dint of their access to the CU mailing list. So it doesn't make much difference whether they also get the tool.

10329:

protection is to be used on all articles with a history of BLP problems, or all "high-risk" biographies, or whatever, without being shouted down. Now, any such discussion will be disrupted by complaints about the trial

6422:

leading me to the conclusion that a single strong lead drafter is needed for efficiency's sake in most cases, although of course that does not mean that any other arbitrator is not also free to add additional proposals.

6397: 531: 9821: 6092:

Does the recent "Race and Intelligence" ruling mean that if a regular editor at Israel-related topics accuses another editor of anti-Semitism, as happened to me once, they can be taken to the ArbCom enforcement board?

2129:

That the RfA is passing comfortably (touch wood) is evidence that the process we used didn't produce a result that the community objects to. The RfA also means that the configuration change will not be needed in this

1840: 1552:

cases (though some cases will always take longer than others) and the other ArbCom work? Have you considered resurrecting a published agenda, or is this being done on a more ad hoc basis or from an unpublished agenda?

9268: 8939:

with each possible segment of usage split to be voted on individually. Strictly speaking no-one need vote yet for another 12 or 13 days, but voicing opinion now is not a huge problem. Can folks ensure we have covered

8015: 6028: 2969: 8711:

become controversial. It would hardly seem fair for someone to cop an arbitration enforcement block for something they have been doing uncontroversially for years. While I'm here, I'll also ask should complying with

3394:

Then I'm confused on two points: (a) I thought this was a discussion about whether to make a technical change that would allow a non-admin to have CU; and (b) if he's standing for adminship anyway, what's the issue?

10609:

a waste of time for the sysops that have better things to do. It will also have an effect on editors. Protected page edit-requests are horribly ineffective. It takes lots of time, and it might not look good, but

8684:

FWIW, there's solid support in style guides of all flavors for en-dashes between numbers, indicating a range, and I haven't personally noticed any disagreement over this (but I haven't gone looking, either). - Dank

3891:

We are talking about a relatively minor, even superfluous change. We are also talking about a change which reduces the implicit social status of administrators (a platform which is laid out, but rarely followed at

1392: 8062: 7423:

giving the clerks the right and responsibility of redacting improperly presented evidence and behavior that doesn't conform to standards of decorum, and seeing to it that they do so diligently, fairly, and evenly.

5957:

I can understand its use in this instance given the incendiary nature of the topic in question, but employing what amounts to a gag order is an extreme measure and should be enacted very rarely, certainly not as a

1735:

Since you seem to be saying you don't have any confidence in their already given word that these are the new procedures, what kind of further assurance would you expect them to give that would make any difference?

11145:

BLP violations from developing in any case. Whether pending changes is useful at all is directly related to whether it's worth having this much of a fight over its removal. Did you really not consider this issue?

9594: 9116:

My personal opinion is that you're making two unwarranted presumptions: that ArbCom is in any meaningful way comparable to the legislative arm of a government (we are not), or that laws such as those you describe

7296:

Well, then we agree it's daft. I guess the only real difference in our positions, then, is that you want to rationalize the daftness, and I just want the daftness to go away. Different roads to the same end...

7192:

Even worse, the message seems to be: go ahead, do the dirty work for us, risk your reputation, become stressed out by arguing with rabidly argumentative Truth-bearers and generally make yourself unpopular so that

903: 479: 10548:

that a certain source is usable in a biography by removing his reviewer rights has a chilling effect on discourse within the project, and may lead to the community avoiding pending changes protection altogether.

7875:, administrators are mandarins selected on merit through an examination and higher functionaries taken from their ranks as experience and skill warrant). I actually had a talk on that subject in Gdańsk. :-) — 7001:

But that's presupposing that the admin whose action is reversed is feeling like initiating such a hearing in the first place and ready for "everyone the next two months calling for (theoretical) head" as well.

4116:

Where was this discussion held? All I see is the final decision. I strongly support the right of the ArbCom to discuss the details of cases in private, but discussions of policy changes should be held on-Wiki.

6155: 917: 6191: 6036: 5919: 5460:

requirement that an AUSC community member be an admin, so since no other issues were raised by the arbs, Bahamut was submitted for the appropriate community comment period just like the rest of the candidates.

2865:

usergroup has been mandated by the WMF, it's not 'under the jurisdiction' of the community, or Arbcom. The addition of the rights to the CU group by the french wikipedia was the result of a community decision,

9388:

removing protection. There should not be any problem with you doing that. Sure the extra step is a pain, but if it calms the worries of a large group of people, suck it up and make the extra two mouse clicks.

8641: 8537:

for announcement :). I felt as though the wording needed to be more crisp, and further was also, per Looie496, rather questionable. The motions will serve their purpose, though, so it's not worth dwelling on!

6284: 171: 118: 8661:

My reading of the first motion is that no editors are currently allowed (for lack of a better word) to make any moves involving a hyphen or dash. For example, am I no longer permitted to move an article from

8634:

Personally, I'm not particularly concerned whether this is settled by (a) a long rambling discussion in which you all thrash out something you can all live with; (b) an RFA style semi-headcount; (c) a formal

7357:

Put simply, Knowledge allows people to run on at the mouth, and it destroys the discussion process. People just aren't good at formal communication. Left to their own devices, most people in the world will:

7349:

that are considered acceptable, the kinds of statements that are proper, the kinds of behaviors that are allowable. In the US, for instance, everyone who speaks to Congress or a court is technically legally

4381: 1243: 8667: 7087:

decision that if it DID happen again, we wouldn't even need a case, the removing of the tools would be by motion. It may not say that in the actual findings, but I hope that it is sufficiently clear to all.

4392:. The oversight privilege's inability to view deleted revisions became immediately apparent in relation to an open case. Having had no objections to this point, we requested the necessary technical change. – 4377: 3976:

real phone number and pay the small fee to have it unlisted. People can't disclose what they don't know. But this is really a philosophical discussion better suited for over a beer than over the Internet.

2935:

from ArbCom that the developers institute these changes. If any members of the community disagree then, rather than criticising the request, they might instead try to get a community consensus in support of

2884:

Cenarium, that's just for CU. What about OS? I can understand (as said earlier) how CU is slightly trickier, but not letting OS see deleted pages just seems illogical. Can you tell how fr-wp handle that?

2230:

I'm as suspicious of authority as the next guy (well, as suspicious as an admin can be, I suppose), and some ArbCom members/decisions annoy me too sometimes, but I don't understand the apparent necessity in

2344:

This year is the first time a non-admin was presented as a candidate for the Audit Subcommittee, and there were almost no objections or concerns raised related to his not holding administrative privileges.

9811:

I don't understand why any admin without access to OTRS would modify a protection level with an OTRS ticket given as a reason. Can someone help me explain the reasoning behind someone wanting to do this?

8458: 8336: 8306:

I should have double-checked before posting that, the person I referred to didn't use it for several months after being granted access, but they have began using it recently. Sorry for th confusion, never

7120:

do this kind of thing lightly. I think the block that started this mess was an error in what is usally unimpeachable judgement by Sandstein. Certainly I don't make AE blocks lightly, and I've made my fair

6321: 1414: 11237:

Well, that's a valid opinion, the spelling out of which is worthwhile and may even persuade. Simply saying "you lack common sense" is simply abuse. Articulating opinions is useful, hurling abuse is not.--

10030:

even if they call themselves 'admins' or 'arbitrators', have knowledge of a defamation issue, it doesn't make it that 'Knowledge' as legal entity has knowledge of it (that's where your 'us' is incorrect).

7628:

the case pages). The Noleander case, in comparison, was expertly managed and quickly dispatched; there was surprisingly little ill-feeling between those presenting evidence from differing points of view.

11287:

me to stop. When I proceeded with doing what consensus had already been developed for, you unjustifiably blocked me. I really wish that you would understand that. It's unfortunate that Arbcom ducked the

8007: 126: 786:

As a side note, this process addresses only issues specific to inactivity. It does not preclude the Arbitration Committee removing a tool for other reasons, in accord with the authority outlined in the

556: 8971: 9353:

Any administrator who removes pending changes protection from any article flagged as a biography of a living person shall replace level 1 pending changes with semi-protection of an equivalent duration

9043:

as possible is necessary, taking most day-to-day business of the committee to the open would complicate matters a great deal for no obvious benefit to either the community or the committee. Everyone

8745:

The CSFD language should be removed. That suggestion is controversial; even if the present language of MOS were to become consensus, there would still be disagreement on whether it meant that example.

8350: 5988:

Enric, the attempted evasion of topic bans is quite vigorously enforced at the Arbitration Enforcement noticeboard—at least in my experience as somebody who has been active at AE for quite some time.

8663: 2789: 2506: 8153: 7724:

way to ensure people have real freedom. Free speech is worse than meaningless if people decide it means they have an inalienable right to continuously shout profanities at the top of their lungs. --

7438:

been avoided; and people would be much more satisfied with the ruling because they never would have been under the delusion that their emotional venting might be taken seriously by the committee.

7255:

to abuse the system; any admin who is trying to apply DS judiciously and thoughtfully would never get into a situation where there was any meaningful question about the validity of the sanction. --

4211:

But there's a community understanding, Risker, that people will be given CU/OS because they need it, and that they need it because they're active admins or Arbs working in areas where it's helpful.

1459:

encourage arbitrators drafting and voting? Is it an indication that patience has run out on the megacases, and that sprawling evidence and workshop pages will be shown less tolerance going forward?

1266: 8636: 6563: 3948:

trusted to have access to your IP addresses? Who can be trusted to have access to the functionaries list, where private issues are often discussed—not only locations but all kinds of private stuff?

10367:

to ascertain just how angry many editors are with the injunction, and the lack of sanction for Scott's wheel warring and involved blocking, which would ordinarily result in emergency desysopping.

7487:

of discussion in the rest of the project has created a cultural expectation of the right to speak one's mind. The existing regime has already seen significant conflict between clerks and parties (

5756: 1827: 931: 7269:

Not my position, mate, it's ArbCom's. I've always thought it daft that one admin is not allowed to reverse what another did just because the first called it an AE block. My understanding of the

1863: 1745: 1258: 8100:

Seriously, AC procedures are intricate and spread over enough pages as is, the least that can be done for the despairing searcher is to make it consistent and signposted. Appreciate your work,

7642:

Part of the problem is that it is generally not possible to determine a priori whether some avenues of inquiries will end up being relevant or not before the extent of the evidence is seen. —

5948: 5821: 5436: 3694:

I think the viewing of deleted pages by admins and others should be logged by the software with the logs visible to CU, for reasons given above. That gets off-topic for this discussion though.

2696: 661: 288:

Another thought: if I get appointed, I'm sure someone will come along and insist on nominating me for RfA anyway. I've already had a few emails along the lines of "get your butt over there!".

6148: 3833: 2904:

checkusers with admin rights usually don't block users that they have CU-ed. Regarding arbitrators, the vast majority of them don't have CU or OS rights, and several don't have admin rights.

1675:

What exactly is new besides "500 words and about 50 difference links" (The old limits were double the amount)? Everything else looks like standard practice. Is this just formalization of it?

10364: 7338: 9127:

covert but prone to interference and misinterpretation while any misbehavior putatively done in secret would still be done in secret. The only difference is that now people would have the

7201:. Even if adopted unconsciously, this is a deceptive and thoroughly disloyal attitude on the part of the Committee, and another reason why I decline to do the dirty work for them any more. 1789: 521: 8796: 8628: 6102: 5245: 4474: 3629: 3543: 1833: 1775: 640:

knowledge whatsoever of the matter involved. Implicitly has now been chosen in favour of an erroneous article content. As for my poor conduct, I very much would like to see the evidence.

9624:@Kww and SlimVirgin. We can keep fighting over this, or we can try to suggest to arbcom a better way. This isn't a matter of me winning or losing. I'd be content with a motion that said 5530:

itself of power, rather one that makes those decisions in private. An ArbCom that opens itself up more, and is more responsive, will be more popular, so it would be a win-win situation.

5238: 2792:", that is to say, they pushed to remove MZMcBride's toolserver access. And that based on flimsy grounds, while there were no indication that the community wanted this, disregarding the 8959: 8479: 8430:

that's been languishing for years!). I for one would rather it did so now, when there isn't a terribly large workload, than later in the year, when perhaps things might get far busier.

6596:

I don't have any relevant comments about Sandstein's essay, but for what little it's worth, I think the committee made the right choice to show a bit of leniency to all those involved.

6566:

I presented about Dreadstar's involvement in fringe topics and his prior misuse of tools in this area was apparently overlooked? In particular, I believed that Dreadstar's creation of

513: 11154: 11139: 11103:

when now you say there was no emergency. You still profess you've done nothing wrong in dropping the nuclear bomb. In doing so, you breached two important elements of WP:ADMIN, namely

11077: 11055: 11028: 11018: 10987: 10977: 10962: 10947: 10937: 10914: 10904: 10889: 10874: 9745: 9668: 9543:

Just ignore it, Slim. Not even a GovCom as mad with power as this one has become is going to desysop an admin as effective and prolific as you for doing the best thing for an article.

8991: 8907: 8876:

involved parties that the Manual of Style needs sorting out. But bear in mind that the interim measures are hitting hardest the very people who would implement any change to the MoS. —

2209: 1406: 10803:

enforce key portions of the content standards, such as involved blocking and page protection. However, BLP does not permit the following offensive behaviors, under any circumstances:

4959: 3774:

regardless of what folks have assumed in the past. Feel free to initiate one if you like, but I don't see correcting the permissions issue as contingent on a possible future change.

2598:. Indeed, RFA is a broken process that clearly has its faults. But what it does mean is that you shouldn't simply pretend that they have passed RFA and dispense with the process. -- 11291:

Whether they ducked the case or not, it's time for you to stop actively misrepresenting the facts of the case. Do not accuse me of unreasonable behaviour when it simply is not true.—

8167:

used the tool? OS is something to be used, not put on the trophy shelf. Such a user can still peep at suppressed sensitive information despite not contributing anything to the team.

7379:

their positions... We need structures to keep ourselves in line, because so very few of us have the capacity to keep ourselves in line by ourselves, and if we are just allowed to

7031: 5789:

option to submit questions and comments securely/anonymously. It's not as if I was secretly snuck through the back door under the cover of night and given permissions out of nowhere.

1156:(SOP) provisions, requiring that CU/OS can not be arbcom members and/or 'crats. For example, German Knowledge requires that each person can only perform one role above sysops. (see 1040:) are probably a practical necessity for the role, and we are still finalizing how to handle this. One option under consideration is adding the requisite userrights to the CheckUser 958: 11119: 10394: 10376: 10353: 10342: 10323: 10312: 9775: 9753:

On a more general note, Scott, BLP enforcement is, of course, of the utmost importnace and you do a great job under trying circumstances, but you would find it easier if you worked

9566: 9355:

sounds like I am obliged to semi-portect a BLP if I remove PC from it (which admins are obliged to do by the closure pof the RfC). That's re-writing the protection policy, which is

9051:

behind closed doors unless there are very serious privacy concerns, and that the committee should act with as much public explanation as possible—and this is where we are today. —

8367: 6719: 6268: 3970: 3599: 1729: 1644: 187: 10864: 10849: 10834: 10583: 10166: 10141: 10109: 9701: 9538: 9528: 9506: 9496: 9447: 9037:

The lack of response to your original comment is probably more due to the fact that that issue has been hashed to death several times in the past than because nobody is interested.

8607: 8291:

though, I find these to be rather misleading - in both cases, (especially with the Crat tools) I make rather a lot of responses that don't use any tool, for every one that does. --

8237: 8177: 7011: 6385:

I deeply regret that the many individually competent people on the Committee have, in this instance, not met by far the expectations I (and probably others) had in them as a body.

6262:

reveal: an unveiled threat that should the disruption continue, the CU wont be so circumspect next time as policy doesn't constrain them. At least then they have been forewarned.

3273: 3244: 3160: 2418:

roles contain everything needed to accomplish a task. Reviewer, Researcher, ipblock-exempt, rollback... all of these roles have everything needed to do that finite, specific task.

2194: 2113: 2079: 1704: 1635:

More seriously, that's kind of you to say, and I am sure that Roger and Kirill, who have spearheaded much of the procedure-writing work over the past few weeks, will appreciate it.

1608: 712: 11196: 11185: 10472: 9931:

edits to a page doesn't mean that there aren't folks waiting in the wings to make BLP edits. There are plenty of topics where IP editors will regularly make BLP-violating edits;

9432: 9412: 9373: 9202: 7690:

deliberative body that deals with significant public input, everywhere in the world, has rules of this sort. Some do it better, some do it worse, but they all do it because they

6647: 5045: 5030: 4942: 4097: 3942: 1085: 757: 742: 685: 11241: 11232: 11219: 10697: 9907: 8273: 5151: 3714: 3615: 3580: 3300: 2541: 1311: 1290: 1277: 10558: 10457: 10442: 10058: 9024: 8300: 6965: 6921: 6548: 5411: 4030: 2584: 1662: 1576: 1230: 727: 9879: 9557: 6690: 6570:

and his later use of delete and revdel on said article represented, at a minimum, poor administrative judgement and a clear statement of opinion in the area of fringe topics.

6502: 6481: 6373:

been much better if the Committee had rapidly resolved this incident by motion, desysopping or in some other way substantially sanctioning the administrator who had held their

6024: 5851: 5778: 5573: 4241: 3744: 3729: 3403: 3385: 2913: 2894: 2335: 2312: 1122: 822: 10536:

Indeed. Scott's wheel warring and involved blocking weren't his only recent imprudent actions in this area. The removal of reviewer status for wiki-political reasons, such as

10297: 9844:

But there's no harm in asking another admin with OTRS access to investigate before unprotecting and there might be a very good, but not so obvious, reason for the protection.

8654: 8408: 8388: 7237: 7213: 7147: 6984: 6945: 6741: 6579: 6461: 6437: 5975: 5857: 5598:

the deletion and blocking tools, or does the ArbCom acknowledge that the unwritten policy is that those tools are bestowed on users who have passed through the RFA process?

4228:

policy has been to only grant CU/OS to admins. Changing this well-established practice without any on-Wiki discussion or effort to gain community support seems precipitous.

1172: 804: 774: 10488:

an official Wikimedia Foundation "seal of approval" on anything or anyone. The word of the Foundation is not needed for a decision to be made about how the trial is closed.)

10278: 9751:

active, is courteous and to be strongly advised in borderline situations, but we don't need GovCom to essentially tell admins to do what the community made them admins to do.

9235: 8887: 8817: 8598: 8528: 7559: 7306: 7291: 7264: 7081: 6833: 6818: 6803: 6252: 5845: 5693: 5674: 5651: 5629: 5611: 5592: 5491: 5469: 4130: 3332: 1895: 1094: 852: 837: 591: 571: 11300: 11061: 11001: 10537: 9922: 9858: 9653: 9307: 8219: 8213: 7980: 7866: 7835: 7809: 7757: 7479: 6760: 6675: 5903: 5888: 5388: 5325: 4219: 4015: 3985: 3874: 3849: 3768: 3644: 3492: 3477: 3462: 3444: 3417: 3232: 1537: 1467: 1342: 1206: 1195: 1060: 1015: 983: 886: 11315: 11210: 10645: 10427: 10409: 9735: 9615: 9462: 9286: 9220: 8757: 8732: 8679: 8584:

accordance with this remedy, is it an AE block (and thus subject to appeal at AE, with no single admin allowed to overturn it) or can it be appealed like a "normal" block?

8322: 8191: 7651:

Hey, while you're here, I'm curious as to why QuackGuru wasn't addressed. Was it because the committee thinks he doesn't need addressing, or was there some other reason?

7535: 7111: 7096: 6661: 6627: 6605: 6020: 4849: 4792: 4755: 4591: 4162: 4061: 2870:. I would be surprised that this would not be the case for all others. The English Knowledge arbcom is comparatively the most powerful of arbcoms in wmf wikis, and by far. 1880: 1522: 1503: 1490: 1359: 867: 10718: 10665: 10527: 9175: 9135: 9095: 9055: 8514: 8494: 6520: 6228: 6218: 6083: 5909: 5347:

powerful and possibly soon-to-be advanced privilege-holder) or because the editor is their school/workmate, and the like. Forcing everyone to comment publicly is going to

5141: 5126: 3783: 2665: 2556: 2500: 2472: 2445: 2403: 2052: 2018: 1716: 10789: 10494: 9893: 9839: 8929: 7668: 7544:

I utterly disagree with "in AC cases it's better to err on the side of over-enforcing politeness, even if it constricts freedom of speech". AC cases are exactly where we

6868: 6848: 6779: 5714: 5512: 5454: 5178: 5163: 4302: 4283: 4262: 4147: 3929: 3148: 3096: 2357: 2298: 2263: 2245: 1959: 1444: 307: 283: 252: 234: 207: 8705: 8548: 7637: 6131: 6117: 6064: 6048: 6032: 6016: 5538: 5367: 5289: 5257: 5103: 5088: 5073: 5059: 5017: 5003: 4902: 4882: 4864: 4831: 4775: 4507: 4485: 4404: 4371: 4176: 3823: 3177: 3125: 3110: 1810: 1806: 1802: 323: 101: 93: 88: 76: 71: 63: 10248: 10214: 10181: 10131: 9720: 7931: 7879: 7591: 6312: 6300: 5050:

I do have to point out that the only people saying that CU/OS holders must be administrators are...administrators. Really, this is a social issue, not a technical one.

3685:

been treated as "root access"--that's why we used to say "adminship is no big deal", because admin tool operations were considered reversible. Adminship is a big deal

2781: 1947:

be a social requirement for appointment as a functionary - and you should feel free to initiate a community discussion to see if there is consensus for that position. –

1761: 1139: 10997:

alternative but to do exactly what you did: wheel war with Kww, block him, then, when he was unblocked, file a request for arbitration, and threaten to block him again

10769: 8805: 8440: 8136: 8108: 8082: 7646: 6766:

clear consensus for an unblock in a central discussion)? My reading of the decision is that people should try harder to be nice to everyone, however we need ArbCom to

6537: 5998: 5306: 2879: 2806: 2774: 2745: 2726: 2708: 2388: 1934: 1627: 1596: 1236: 10043: 10024: 10000: 9979: 9948: 8690: 8568: 7427:

of course this would mean that there would have to be an appeals process as well, where people could request that their comment (or a modified version) be reinstated.

3028: 3010: 2986: 1690: 1561: 10049:

cannot be properly deployed in an atmosphere so degraded by authoritarian actions that the community will never agree to it. Regaining our trust needs to start now.

7622: 6917: 1429: 1384: 1111: 2519: 11215:

That type of remark improves wikipedia how? Debate on issues is good, reasoned disagreement can clarify, inarticulate attacks do nothing constructive whatsoever.--

11068:

issue as well: removing the privilege without a good reason is not an acceptable means by which to draw attention to the purportedly negligent granting of rights.

634: 2607: 2572: 1976: 1914: 8452: 8122: 8033: 3408:

There are some weirdness with how the tools actually work. OS without Admin allows one to see deleted revisions... but not if the page itself has been deleted.

3042:

not be able to actually suppress material without going through the regular process. Although I had thought that, as has been mentioned, the Foundation said we

2014:

RFA). This isn't the ideal solution, but it is necessary unless consensus changes to demand adminship as a prerequisite to gaining a CU/OS flag for any purpose.

10385:

be recalled before the end of their terms, no matter how injudicious their decisions. If it were possible, we'd certainly be having recall elections right now.

7708:

Yes, people will get annoyed if you tell them that they cannot say something that they *want* to say (because everyone believes that what they *want* to say is

7128:

that that it's difficult to know what you really think. Obviously, it's necessary to an extent so you can all have confidence in each other, but it creates the

3886: 3345:

election where people were suggesting we change the rules mid-election about identifying to the Foundation. That kind of thing takes us in the wrong direction.

2650: 2636: 1148: 10317:

Arguing about the past does no one good, especially since I wasn't around or in charge for any Foundation decisions about extending the trial past two months.

8742:

AE should certainly warn (and revert) anybody who hasn't commented on the Arbitration Request - and most of those who have, who may not know the motion passed.

7733: 7456: 6686: 6575: 522: 5872: 9226:

something about that eventually. So, while there may be temporary obfuscation of the actual discussions, there is no chance they will be lost to antiquity.

4270:

May I ask again why the ArbCom's discussion of this change was held in private? Does the ArbCom lack an adequate forum or page to hold discussion on-Wiki?

10919:

Emergency desysopping is a perfectly reasonable response when an administrator's use of the tools is so disruptive as to create exigent circumstances. That

10418:, many of the current arbitrators responsible for creating this mess will be up for reelection in December. I encourage editors to vote the incumbents out. 8247:

the OP by 'brox, because work and family commitments have reduced my usage of Knowledge in general, and OS in particular) but I *have* used it a few times.

7242:

The problem with that (as I have pointed out numerous times) is that you're basically asserting that an admin should be able to use AEDS to block an editor

5583:

process, and are now dissatisfied with the results. That's OK, but that's not somehow ArbCom's fault for not complying with such an undocumented "policy".

1383: 9831:

are not a valid protection reason. It may be that the ticket contains such a reason, but then you should be supplying that as a protection reason instead.

9073:

Thanks for your reply. Every legislative committee or group finds it more convenient to conduct their business in private. Legislators routinely object to

8048: 8000: 4855:

wikipedia (of course in case it isn't obvious, I'm not talking about bugs concerning your mailing lists, arbwiki, or made by arbs in a personal capacity).

10544:

discuss sources that may or may not be appropriate on article talk pages, rather than unilaterally adding them to BLPs. To punish an editor for daring to

8287:

Might have been me - I am quite sheepish about the fact that for various reasons I was inactive with the tool until early March of this year. As with the

10015:

it towards semi-protection is the OTRS ticket, and I'm not aware of a policy that makes those tickets last beyond the apparent cessation of the problem.—

8964: 5784:

You know, I had no idea this was as big a controversy as it seemed until today. I never meant to sow this kind of discord. But I'm struck by two things:

3905: 1157: 649: 3697:

I don't see a problem with the idea of arbcom endorsing a bug report/RFE. They've certainly informally encouraged various software changes in the past.

2695:

community decision. This is how bugzilla works, always worked; arbcom has no special authority to make bug requests for the English Knowledge (as you'd

2133:

This configuration change isn't 'reform', but it does remove the technical restriction that currently ensures Arbs, CU and OS can't give up sysop tools.

1632:

Well, I guess Marek has said all there is to say and pretty much summarized the entire community's sentiments here.... Shall we close the thread now? :)

1254:

a factor in the appointments last month; that is, none of the candidates had any concerns regarding privacy or breaches of trust raised regarding them.

893: 615: 8343: 10303:

have discussed a long-term pending changes policy, without having the debate continually derailed by complaints that the trial was unfairly extended.

6682: 6571: 629: 10855:

a few interjections by arbcom. BLP is certainly not a license to elevate one's own idiosyncratic view of the policy to the force of divine mandate.

10265:

by Knowledge's 500+ active administrators, and tens of thousands of regular editors. Such a goal necessitates that the community to be treated with

6177:

by the privacy policy. It is therefore perhaps incorrect to state that the "practice of declining to publicly link such activities to an account is

5579:

out a perfectly good candidate and/or stopped the entire process pending an RfC on the topic? It sounds like a recipe for analysis paralysis to me.

910: 10360: 8146: 4290:

Again, there has been no change. Bahamut's lack of administative privileges was discussed during vetting prior to the candidates being announced. –

3735:

This doesn't pertain to AUSC (which is why I called it off-topic); it's just pointing out a flaw in the theory that admin tool use is reversible.

1377: 894: 601: 21: 10799:

itself with substantive standards for content about living people. To a lesser extent, it prescribes certain extreme remedies that can be used to

8804:

BTW, I suggest for people that this is an all-consuming fever, I'd look at the reaction from neutral people in the ArbCom Report at the Signpost:

8094:

2) Needs to be clear from the other end too; the "Discretionary sanctions" page should have or at least link to all the relevant info on its topic

2073:

I think all ArbCom members should drop their sysop buttons. Simply not using them doesn't remove the ability to implicitly threaten to use them.

8670:? As I understand it, and perhaps PMAnderson will be able to correct me if I'm wrong, moves like this have never been in dispute. Please advise, 7712:

important, always), but in general people cope with strong-but-fair restrictions far better than they cope with open mic night at the crap-fest.

5620:

on it, and the initial community response seems to be endorsing ArbCom's interpretation of policy, I think either proffered option is premature.

4988: 3357: 3218: 3201: 3056: 698:

to ask that functionaries make one action through SPI or the oversight OTRS queue in three months. That is, after all, the point of having them.

10704: 5423:

are obviously necessary when discussing editors, there doesn't seem to be any cause for secrecy in regard the policy on granting permissions.

3209:

auditing the work of the users who were appointed through the more traditional processes. I mentioned this earlier but nobody seemed to notice.

3077: 2848:

pt.wp 'eliminator' includes 'browsearchive', 'delete', 'nuke', 'undelete', 'deletedhistory', 'deletedtext', 'autopatrol', and 'suppressredirect'

112: 7871:

Very astute, though you're missing (IMO) the very strong flavor of Chinese scholar-official bureaucracy that permeates much of our process (in

924: 10091:

for review. Where pending changes was added as a result of an OTRS ticket, or BLP violations, the protecting administrator should be notified.

8533:

I do not intend to insult Cas, but it took all of my willpower to not re-write the text of the actual motions when I was copying them over to

6888: 6174: 5856:

Since several users above and the responding developer feel the requested change would benefit from a formal consensus discussion, please see

4973: 1144:

There are no wikis which prohibit CU/OS from being administrators. However, it is not mandatory for checkusers to be an administrator n Dutch

6187:

as part of an SPI), however, there are plenty of other cases where doing so would be a violation of privacy, not just a breach of tradition.

5910: 5272:, and requested a watchlist message (which was declined). Any form of comment at the consensus discussion was acceptable, one could even use 3265:

ArbCom, because when someone is suggested, the others won't want to object unless the objection is very serious. This can't be a good thing.

2900: 4582:

I'm with Xeno, if the objections are that Bahamut didn't put "not an admin" with the blink tag on the top of his candidacy, that's asinine.

2762:(apparently because you see this as some kind of "power grab"), I would wager the developers will ask us to consult the community (again). – 1327: 10998: 8936: 8619:

and the subsequent discussion over many sections what ArbCom has in mind? If not, what would be, and would ArbCom mind indicating a model?

8616: 3806: 3368: 3153:

Risker is quite right. The idea that all administrators are trusted to even find their own arses using both hands is quite simply risible.

1161: 11279:

Your concerns had already been refuted innumerable times. There was no need for further discussion. There was no obligation on my part to

8499:

I wrote it - yes, looking back, several other verbs might have been better - e.g. "urged", "exhorted", "requested", "beseeched/besought".

6209:

refers to the sentences before, which qualifies them as certain disruptive behaviors that are considered valid reasons per privacy policy.

3791:← As an FYI, a developer has interpreted the four or five objections above as indicative of a lack of community consensus for this change 2951: 2925: 10684: 10286:

act judiciously (which resulted in an unfortunate block) an injunction more clearly spells out what Brad meant. Abiding by the spirit of

9011:

OK, I acknowledge that no one else is interested in having the ArbCom conduct routine business in the open. I won't bring it up again.

654: 8872:

As a final point, I disagree with Looie. I'm normally against Arbcom flexing its muscle, but applaud you guys for having the cohones to

8329: 11097:

be no big deal about a short pause when someone is doing something to BLPs on mass, and another admin in good faith expresses concerns.

8644:

gets dusted off and we get a rerun of Date Delinking which will last until September. Come September the two-year moratorium on moving

7433:

Had this kind of tightened procedure been in place prior to this particular case, more than half of the evidence would never have been

4250:, wherein we presented a non-admin candidate - and received no objections from the community at large as regards bahamut's candidacy? – 1145: 9939:

are two that come to mind. They need to remain indefinitely semi-protected regardless of how infrequently viewed or edited they are.

3633: 1165: 11203:

There would be some irony in a body that so thoroughly fails to use common sense itself passing a motion telling others to do same.

7998: 7223:

to a active arbitration remedy. My understanding was that that means it's treated as an AE block until consensus says it's invalid.

7188:

have done was passing a substantially meaningless "lowest common denominator" decision merely for the sake of superficial unanimity.

5638:. While discussions of editors should be private, discussions of issues like this should be transparent. Would that be a problem? 1367:

At first I thought that this was useless waffle, but it's actually a neat idea. Smaller groups have more focus and less stagnation.

10415: 10034:

their own discretion change OTRS protections, but consensus can unless otherwise directed by WMF officials (not mere OTRS agents).

8163:

I don't really want a make too big of a deal about this, but isn't there another OS user who got in at the same time I did who has

6490: 9207:

Thanks for that reply, but I was addressing the issue of the discussions which lead to resolutions, not just their final texts.

3962:

is arguing. The issue isn't pro–admin; that's a red herring. It's pro–more eyes, and RfA and ArbCom elections give us those eyes.

1043: 762:

Fulfilling an onwiki request allows at least some scrutiny of a CheckUser's activity by those who are unable to access the logs. –

8126:

Davies to check my work to ensure that it's agreeable and I'm waiting on him getting back to me, so things aren't finalised yet.

2563:

You come across as implying that if editors do not have the admin tools, they are not trustworthy. I find that very disturbing.

1785: 1771: 1725: 10605:. Also, full protection?! If there is not any more vandalism, no protection. If you put protection of pages like that, it is 10333:

the injunction. Arbcom/foundation actions of which the community strongly disapproves are harmful to a community-based project.

4386:

Knowledge talk:Arbitration Committee/Noticeboard/Archive 14#Audit Subcommittee appointments: Invitation to comment on candidates

1871:

What is the purpose of giving CU/OS to non-admins? Is it just for AUSC, or is there some other situation where you'd want it?

1071:

Well these are four very sensible appointments. I'm happy to concede it to these guys and I'm sure they'll do an excellent job.

5117:

trust evaluation criteria which have been set up by those tasked with giving and taking away those tools, who would be ArbCom.

1751:

arbitration process. So your worries may not be as well-founded as you think, although we will of course have to wait and see.

1451:

I wonder what the purpose of shifting from a "cases will go on as long as they need to" regime to a "cases will typically last

11046:

don't regard it as useful. This is a problem with many of your BLP related actions: the belief that your way is the only way.

10010:

anonymous editing, effectively semi-protecting all articles. I don't get my way on that, and I know it. That I ever unprotect

8485:(To clarify the point, ArbCom has a number of powers, but instructing editors on how to spend their time is not one of them.) 3669:

Well I'm sorry (and surprised) to have kicked off so much drama with what I thought was a non-provocative query. My thoughts:

3101:

No he does not imply this. Please take more care at reading what users say before jumping to make such unfounded allegations.

8720: 6122:

No problem. Hopefully, something like that won't happen again so no one will have to try to figure out what to do about it.

3130:

Not at all; I'm suggesting that anyone without the admin flag has not got the required stamp of approval to be classified as

9293:

Since when did GovCom have the power to re-write the protection policy? I for one won't take a blind bit of notice of this.

8042: 7613:

wait for an RfC to finish that describes a new process, well, by then, I might have enough edits to run for ArbCom myself.

5895: 5880: 5748: 5380: 4022: 2201: 51: 17: 4363:

Where was it discussed, Xeno? The problem may be that people aren't aware of these discussions, not that they don't care.

1495:

Sorry, what I meant to inquire about was the intent behind the decision to adopt a target timetable for cases in general.

6913: 6169:

It would seem to me that the IP address of a user would qualify as personally identifiable information (privacy policy: "

4079:

situation as nearly as dire as you just did, Malleus, but I personally am committed to making sure that Knowledge is run

3736: 3706: 3591: 2886: 1872: 9260:

protection from any article." would have done nicely. Instead we have this overreaching mandate that should be ignored.

6710:

following weeks. I knew I couldn't devote the time necessary to fully evaluate all the discussion, so remained inactive.

9782: 8267: 4376:

All the applications were discussed and scrutinized Mar 7-14 internally by the committee during the vetting phase; see

3911:

Thanks, Protonk. If we didn't think that this sort of sentiment was the "silent majority" that was represented by the

2931:

The Arbitration Committee does not control how userrights are configured, and is not trying to. This announcement is a

1781: 1767: 1721: 1399: 8648:

expires, so I personally would really hope the Great Endash Debate will be resolved one way or another before then. –

7247:

sanctionable. 3rd world police tactics extended to Knowledge - wunnerful. The only people who would benefit by this

5767: 5744: 7510:

of behaviour and trying out their enforcement in some of the more minor cases to come before the Committee in future.

7125: 5814: 971:

privileges for the duration of his term. He is, of course, free to seek administrator privileges of his own accord. –

300: 5797:

vocal dissenting minority); and they proved with me that they still have thier finger on the pulse of the community.

2486:

approved by Arbcom after community input. The entire reason this change is being required is because the community

8883: 8792: 8318: 2837:

hi.wp 'eliminator' includes 'delete', 'undelete', 'rollback', 'browsearchive', 'deletedhistory', and 'deletedtext'

2280:

requirement (at least for the community, but not for appointments by ArbCom), then why has no non-admin ever been

9901: 7401:

basically limit people to strict relevance, narrowly defined, and prevent fishing expeditions int unrelated areas

7398:

creating clear rules of evidence, so that people aren't allowed to say any old thing that comes into their head.

6015:

I was thinking of Captain Occam, where the vagueness of the R&I topic ban caused a total of six AE requests:

5937:

that-means-all-edits-that-deal-with-the-topic-even-those-made-in-articles-that-weren't-originally-about-the-topic

1905:. This is a truly terrible idea and it smells like wanting to be able to "back door" somebody into adminship. -- 177:

I've taken your first question to the committee to check how we want to answer that. Should have an answer soon.

7418:

in AC cases it's better to err on the side of over-enforcing politeness, even if it constricts freedom of speech

6809:

appears to say that a second admin can overrule an AE block providing they issue an apology when it's all over.

6589:

if you feel that strongly about it. But it might be perceived as unseemly, if not completely out-of-process and

3866:

Cenarium, I would put the RfC on its own page, so the discussion can be wide-ranging. Do you mind if I move it?

8955: 8925: 8564: 8510: 6954:, and generally, I have a lot of respect for what you say/do so I don't want to see you go down the wrong route 1601: 1164:) And on Dutch Knowledge they have an 'arbcom' group, and many of their arbcom members are not administrators. 9985:

legalities, which are imprecise and vary from jurisdiction to jurisdiction, there's always the fact that it's

9121:

in fact have tangible benefit even on actual legislatures (I am not convinced there is evidence that they do).

8603:

If you're blocking someone pursuant to the terms of the motion, then yes, it would be considered an AE block.

5497: 1417:

was opened a month ago. Could you tell us when we can expect the proposed decision to be published? Regards,

10731: 7273:

ruling and subsequent discussions, clarifications, etc is that you have to get consensus that the block was

6181:" (emphasis added). Under some circumstances it is acceptable to link a user account to an IP (e.g. if it's 6141: 5226:

detract from the community's ability to scrutinize the suitability of a candidate for advanced privileges? –

2995:

Late reply, but here you go. No, you misunderstand me. When I suggested that the dissenters get a consensus

2590:

untrustworthy, by any remote stretch of the imagination. Nor does it even mean that all trustworthy people

792: 788: 10641: 9965: 7963:

Why doesn't Jimbo count as a monarch? He can ban anyone unilaterally. What about the board of directors?

4836:

Again, where was this discussion held? If it was not on-Wiki, was there some reason it had to be secret?

2409: 1568:

would be subject to much change because of, as the Royal Navy used to say, the exigencies of the service.

7740:

be true if WP is growing or somehow changing in a way which would make it more necessary to have rules...

6511:? If so, shouldn't you try to maintain some publicly reserved distance from giving opinions about cases? 10206:

I agree we should just let people do their jobs, but I'm thinking this would be a reasonable compromise.

9562:

Actually, I agree. An action in the obvious best interests of a particular article is always justified.--

9274:

This is not a realistic proposal. For example—after protracted problems—I added indefinite level 2 PC to

6715: 8068:

The last page is not in use. The top page is cross-referenced from the actual procedure. The middle one

7706:"What's wrong with these arbs that they would allow this kind of bull to go on under their very noses?" 10762: 7007: 5027: 4939: 4491:

that the community has not been invited to participate in this process is ingenuine at best. See also:

3939: 3157: 2581: 738: 42: 10540:

tends to confirm editors' worst fears that the PC tool will be used in an authoritarian manner. Users

10381:

Also, "ArbCom is part of the community" only in the sense that they are elected by the community, but

5132:

scrutiny the better. Even if we improved the appointment process, that plus RFA would be even better.

2375:

especially not want this to set a precedent. There is no harm in asking the community for feedback at

606:

Thank you Arbcom for your kind attention to this dispute. Is there any point in saying anything else?

11238: 11216: 11193: 11136: 11025: 10984: 10944: 10911: 10871: 10673: 10138: 9904: 9742: 9630: 9563: 9535: 9503: 9478: 9193:

such as who will be mailing list administrators or the like, aren't posted here. I hope that helps.

7914:

Eh, dunno if we want to get sucked into this kind of political maundering here, much as I enjoy it.

7374:

expose scandals, personal details, and engage in other forms of tabloid reasoning with salacious glee

1623: 7818:, WP is already a monarchy with elements of representative democracy, bureaucracy, and gangs/mobs. 6839:

see how ArbCom is "endorsing a decision to reverse an AE block," but perhaps I'm missing something.

5634:

A community discussion is what should have happened first, not an announcement that the change is a

11311: 11150: 11073: 11051: 11014: 10973: 10958: 10933: 10900: 10885: 10860: 10845: 10830: 10554: 10453: 10423: 10390: 10372: 10338: 10308: 10274: 10054: 9955: 9872: 9793: 9731: 9664: 9640:

errors: both articles would stand a very good chance of being unprotected if a request was made at

9611: 9443: 8230: 8038: 6640: 6475:

parties in the case, that I could reasonably be considered non-neutral by an impartial observer. –

5899: 5884: 5752: 5384: 4947:

FWIW I'm quite encouraged that Malleus is quite encourged by the committee's stand on this issue.

4026: 2205: 1683: 1008: 951: 678: 6277:

personally identifying than their IP). So which is it? Are we to ignore the previous directive? --

3626: 2379:

or another appropriate venue. If you expose it well, I'm sure it'll gain consensus pretty easily.

2321:

There have been many viable non-admin candidates over the years, but none have ever been elected.

9403: 9336: 9039:

That said, the general consensus is that while openness is desirable in theory, and that as much

7553:

lighten the mood to one editor can seem a vicious belittling of beliefs or culture to another. –

3740: 3710: 3595: 2890: 2656: 2621: 1876: 611: 268: 8748:

The RM has been been notified (and I hold that a colon is preferable to either dash or hyphen).

4021:

Proxies themselves are also less effective than they might sound, in an environment like this.

2119:

the appointment process. It's not an election, but it is a long way from a plucking process ;-)

8261: 7516:

this particular case focused almost entirely on Sandstein/Dreadstar and not Ludwigs2/QuackGuru.

6711: 4955: 4764: 4291: 4251: 2784:'strongly advised' the community to effectively ban the replacement of "Macedonia" by "FYROM" ( 1848: 1352: 1131:

Knowledge, but it's SOP on some other wikis. In fact, I think there's even a couple where you

334: 7447:

participants, quicker and cleaner discussions, and greater respectability for the process. --

1269:, or does this signal an intent to return to straight elections for future selections? Grazi, 11117: 10784: 10602: 10581: 10572: 9853: 9770: 9552: 9427: 9368: 9302: 9214: 9169: 9089: 9018: 8985: 8593: 8524: 8383: 8209: 7286: 7232: 7142: 7026: 7003: 6961: 6940: 6829: 6799: 6736: 6671: 6498: 6433: 6247: 6044: 5964: 5944: 5812: 5687: 5645: 5605: 5567: 5485: 5430: 5024: 4936: 4843: 4277: 4235: 4167:

Even so, configuration changes, like policy changes, are outside of the authority of arbcom.

4124: 3936: 3380: 3327: 3154: 2578: 2330: 2293: 2241: 1929: 1700: 1656: 1640: 1592: 1080: 992:

enough by itself to review the actions of oversighters? Are there any special permissions in

939:

Just curious: what new user groups will Bahamut0013 be added to for his time on the AUSC? If

848: 818: 734: 707: 586: 551: 298: 229: 166: 8029:

The following pages should perhaps be updated with or cross-referenced to the new measures:

7124:@Fozzie, I can see that the Committee was divided, but you all seem to so rigidly adhere to 3318:

as a functionary/auditor/arb, because that shows that the person has the community's trust.

338: 11104: 10468: 8880: 8789: 8753: 8701: 8624: 8314: 8173: 7976: 7831: 7753: 7686:

Hmmm.... well, I want to make it clear that I'm not indulging in whimsical thinking here:

7664: 7475: 6623: 6544: 6264: 4994:

I disagree entirely. The only arguments against it are social, not technical or practical.

3488: 3240: 3214: 3052: 2862: 2855: 2661: 2537: 2190: 2075: 1741: 1619: 1557: 1533: 1202: 1168: 1153: 625: 509: 475: 183: 10365:

Knowledge:Administrators'_noticeboard/Incidents#Mass_removal_of_Flagged_revision_from_BLPs

7578: 6586: 8: 11307: 11181: 11146: 11069: 11047: 11010: 10969: 10954: 10929: 10896: 10881: 10856: 10841: 10826: 10594: 10568: 10550: 10449: 10419: 10386: 10368: 10334: 10304: 10270: 10050: 9865: 9786: 9727: 9660: 9607: 9439: 8813: 8645: 8604: 8401: 8363: 8288: 8223: 8101: 8055: 7840: 7704:

myself, sad to say), the first thought that comes into my head is (no offense to anyone)

7528: 7107: 7092: 6980: 6633: 6113: 5968: 5698: 5036:

that admin would make a good CU/OS or not, since it's similar work, just more sensitive.

4385: 4247: 3144: 3073: 1676: 1496: 1460: 1304: 1287: 1270: 1255: 1223: 1001: 944: 671: 4378:

Knowledge:Arbitration Committee/Audit Subcommittee/2011 appointments#Appointment process

3019:

This still appears like reversing the burden of consensus to me. Anyway, it's moot now.

1943:

to be an administrator. It sounds to me like you both think that being an administrator

963:

Pending his identification to the Wikimedia Foundation, Bahamut0013 will be granted the

843:

you're likely not to be too focused on the past as long as they're fine going forward.--

11229: 11207: 10714: 10693: 10661: 10523: 10438: 10039: 9996: 9944: 9889: 9817: 9389: 9322: 9315: 9231: 8949: 8919: 8785:

would be entirely down to the committee, I don't know the ins and outs of this case). —

8558: 8504: 8490: 8475: 7923: 7858: 7801: 7725: 7448: 7298: 7256: 7073: 6864: 6814: 6775: 6213: 5841: 5670: 5625: 5588: 5465: 5407: 5394: 5302: 5174: 5137: 5122: 5099: 5069: 5041: 5013: 4984: 4898: 4860: 4172: 4093: 3981: 3925: 3845: 3779: 3764: 3725: 3640: 3573: 3473: 3440: 3413: 3296: 3228: 3173: 3106: 3024: 2982: 2909: 2875: 2802: 2741: 2704: 2496: 2468: 2441: 2399: 2384: 2005: 1518: 1486: 833: 753: 723: 607: 567: 333:

If we have a non-admin checkuser or oversighter, we will need to file a bug similar to

11111:. now you are accusing Chester of wikilawyering. I find this extremely distasteful. -- 10172:

admin could semi-protect any article that didn't need protection for 5 minutes or so.—

2126:

member, and now has need for these three permissions in order to fulfill their duties.

1455:

weeks" one is? Targets as self-discipline, internal motivation? A stick with which to

10617: 10490: 10349: 10319: 10293: 8903: 8728: 8675: 8296: 8250: 8187: 7633: 7618: 6844: 6756: 6657: 6601: 6533: 6306: 6278: 6079: 5774: 5393:

RfA is widely perceived to be broken, but opinions differ on how to fix it. Go read

5159: 4948: 4788: 4587: 4384:, was appointed. The issue of viewdeleted was discussed at various points, including 4057: 3901: 2868:

fr:Wikipédia:Prise de décision/Droits supplémentaires aux vérificateurs d'adresses IP

1820: 1569: 263:

From a strictly technical perspective, the Oversight userright grants the ability to

5212:

to be an administrator; and further, that not everyone wants to be an administrator

3675:

future AUSC appointments should get more attention from users if they have concerns.

11112: 10776: 10576: 10514:

to no protection, SP or FP, with all due regard to article specifics and following

9845: 9762: 9544: 9419: 9360: 9294: 9209: 9198: 9164: 9084: 9013: 8980: 8585: 8520: 8375: 8205: 8069: 7278: 7224: 7134: 7018: 6957: 6932: 6825: 6795: 6728: 6667: 6525: 6494: 6429: 6296: 6239: 6040: 5940: 5804: 5682: 5640: 5600: 5562: 5480: 5425: 5084: 5055: 4999: 4878: 4838: 4827: 4272: 4230: 4158: 4119: 3372: 3319: 3121: 3092: 2970:

Knowledge:Village pump (proposals)/Persistent proposals/Straw poll for view-deleted

2568: 2322: 2285: 2237: 1972: 1921: 1902: 1891: 1696: 1651: 1636: 1588: 1440: 1091: 1072: 863: 844: 814: 800: 699: 645: 578: 543: 290: 221: 158: 9582: 9246:

Preliminary injunction regarding pending changes and biographies of living persons

7038:"admins do not block editors lightly, and do so even less lightly under AE rules" 3516:

almost no transparent process at all, because that's likely to mean more mistakes.

2786:

any instances of changing the word "Macedonia" to "FYROM" (...) shall be prevented

11108: 11065: 11034: 10628: 10590: 10464: 10244: 10207: 10159: 10102: 9932: 9694: 9521: 9489: 9279: 8877: 8786: 8749: 8697: 8649: 8620: 8466:

Motion 2 is quite possibly the worst-worded motion I have yet seen from ArbCom.

8427: 8310: 8169: 8091:

1) Then it and its associates should probably be dispensed with or tagged as such

7554: 7502: 6590: 6516: 6476: 6127: 6098: 5531: 5318: 5250: 4748: 4478: 4364: 4212: 4008: 3963: 3867: 3816: 3612: 3484: 3455: 3396: 3350: 3266: 3210: 3194: 3048: 2309: 2106: 2045: 2015: 1737: 1713: 1553: 1529: 621: 140:

I have a couple of questions that I hope someone (probably an arb) might answer:

7172: 2655:

That was an option we looked at briefly, however "researcher" is managed by the

2577:

I find it very typical of a deep-rooted problem within the administrator caste.

50:

If you wish to start a new discussion or revive an old one, please do so on the

11177: 11132: 10756: 10088: 9684: 9641: 8809: 8716: 8686: 8534: 8359: 7844: 7204: 7103: 7088: 6976: 6452: 6388: 6109: 5868: 5710: 5508: 5450: 5363: 5285: 5234: 4771: 4503: 4400: 4298: 4258: 4143: 3802: 3140: 3069: 2840:

nl.wp 'checkuser' includes 'deletedhistory', 'deletedtext', and 'browsearchive'

2770: 2722: 2632: 2353: 2259: 2123: 1955: 1859: 1420: 1338: 1107: 1056: 979: 770: 279: 248: 203: 11283:, for the simple reason that you never, at any point, provided a valid reason 2834:

fr.wp 'checkuser' includes 'browsearchive', 'deletedhistory' and 'deletedtext'

1649:

Thanks to those who've brought it to completion. It was a long-time coming.

1118:

Is it just me, or is Bahamut0013 the first non-admin with CU and OS access? --

313:

objection to his candidacy is just a valid a community endorsement as is RFA.

11296: 11226: 11204: 10806:

Wheel warring over page protection. While even an involved administrator can

10795: 10710: 10689: 10657: 10519: 10434: 10405: 10287: 10258: 10177: 10127: 10035: 10020: 9992: 9975: 9940: 9918: 9885: 9813: 9716: 9649: 9590: 9458: 9227: 8945: 8915: 8554: 8539: 8500: 8486: 8471: 8431: 8127: 8073: 7848: 7582: 7506: 7492: 6860: 6810: 6771: 6322:

Knowledge:Arbitration/Requests/Case/Arbitration Enforcement sanction handling

6225: 6188: 6055: 5989: 5829: 5666: 5621: 5617: 5584: 5461: 5403: 5298: 5266: 5222:

How does holding the consensus discussion at a page with a prefix other than

5170: 5133: 5118: 5095: 5065: 5037: 5009: 4980: 4894: 4870:

don't understand where you get the idea that bugzillas are community-driven.

4856: 4168: 4089: 3977: 3921: 3893: 3841: 3837: 3775: 3760: 3721: 3636: 3622: 3469: 3436: 3430:

election to ArbCom, but there was a sizeable minority of folks who said "Why

3409: 3292: 3224: 3169: 3102: 3020: 3001: 2978: 2942: 2905: 2871: 2798: 2793: 2737: 2700: 2492: 2464: 2437: 2395: 2380: 2376: 2176:). Then members can see what needs to be seen, and they can shed any of the 1752: 1514: 1482: 1473: 1415:

Knowledge:Arbitration/Requests/Case/Arbitration Enforcement sanction handling

1368: 1186: 1119: 829: 749: 719: 563: 314: 4747:

So yes, the scrutiny or participation on the community side is not optimal.

3310:

community approvals process. I would have no problem with a non-admin being

2843:

nl.wp 'arbcom' includes 'deletedhistory', 'deletedtext', and 'browsearchive'

10624: 10621: 10593:. The arbitrators have the power to there heads; it is just contradicting 10515: 9832: 9261: 9074: 8899: 8724: 8671: 8292: 8197: 8183: 8016:

Committee procedures relating to Ban appeals and to Discretionary sanctions

7629: 7614: 6840: 6752: 6653: 6597: 6529: 6309: 6281: 6075: 5770: 5155: 4784: 4583: 4053: 3897: 3792: 2790:

reevaluate the propriety of MZMcBride's continued access to the toolservers

1435:

Is there any point setting such a target which is unlikely to be achieved?

10122:"Same length of time" results in indefinite semiprotection in most cases.— 10634: 9987: 9275: 9194: 7777:

that Knowledge is headed down the path where it will become just another

7158: 6681:

case, I never asked for or advocated a specific sanction for Dreadstar.

6292: 5080: 5051: 4995: 4874: 4823: 4492: 4154: 3546:? (Again, no disrespect intended; I just don't know what the process is.) 3117: 3088: 2646: 2603: 2564: 2552: 2515: 1968: 1910: 1887: 1436: 859: 796: 641: 9683:

appropriate. Where there is disagreement, a request should be posted to

9123:

What rules like this do is expose the boring day-to-day operations that

6652:(edit conflict) Just to be clear, I'm not advocating for a recall here. 6156:

Checkuser practice regarding the association of IP addresses to accounts

879: 10682:

I am still wondering what the answer is to the question that was asked

10240: 9351:

Well perhaps we're reading it and seeing different things, but, to me,

9132: 9052: 7876: 7643: 6512: 6493:

against an editor who presented evidence against him during the case).

6123: 6094: 2831:

fi.wp 'arbcom' includes 'deletedhistory', 'deletedtext', and 'undelete'

1136: 3840:

should be a prerequisite for being granted CU or OS rights by arbcom.

3794:, so it will not be processed until after an RFC or similar process. – 2188:

groups which they dont use regularly, or don't want to use regularly.

10750: 10589:

I think now that the arbitration committee. Is just giving power to

9960: 9936: 9078: 6489:

shortly after writing the essay above, Sandstein proceeded to file a

5861: 5703: 5501: 5443: 5356: 5278: 5227: 4496: 4393: 4136: 3795: 2763: 2760:

procedural opposition to a technical change that you actually support

2715: 2625: 2346: 2252: 1948: 1852: 1331: 1100: 1090:

Congratulations to the appointees, who I'm sure will do a great job.

1049: 972: 763: 272: 241: 196: 8201: 3630:

Knowledge:Arbitration Committee/Audit Subcommittee/2011 appointments

3544:

Knowledge:Arbitration Committee/Audit Subcommittee/2011 appointments

127:

Audit Subcommittee appointments: Invitation to comment on candidates

11292: 11100: 10401: 10173: 10123: 10016: 9971: 9914: 9712: 9645: 9629:

motion, more to your liking, I think we could pitch it to arbcom.--

9586: 9454: 8712: 6356:

be meaningless", but does not acknowledge that this (non-)decision

6173:"), and should only be released under the circumstances underlined 5680:

when they don't require secrecy, even if that's less efficient.

4135:

What policy change? We were discussing the technical requirement. –

2659:, and audit subcommittee members dont meet their pre-requisites. -- 4935:

FWIW I'm quite encouraged by the committee's stand on this issue.

2463:

mentions doesn't justify that you step outside of your authority.

10794:

I believe the problem here arises from the conflation of issues.

8196:

I presume he was talking about Phantomsteve, who has since then,

7548:

be giving people the benefit of the doubt unless they're clearly

7116:@Ludwigs, I suppose what I should have said is that admins don't 5351:

people from bringing forth concerns related to privacy and trust.

2828:

en.wp 'researcher' includes 'browsearchive', and 'deletedhistory'

1472:

I think "consensus intention" is a good way of putting it. It's

1200:

Aye. However 'separation of powers' would have made more sense.

11033:

Thanks for confirming that your recent actions were nothing but

5927:

Oh, hey, Arbcom has finally learnt to issue topic bans that are

5478:

Why was it necessary to have that policy discussion off-Wiki?

943:

is one of those, will it too be removed after his term expires?

10992:

You're mischaracterizing my position. I never claimed that you

7853: 7778: 7383:

our own emotional incontinence will never allow us to actually

7153:

disagree with it, but it should not have affected the outcome:

6610:

Skinwalker's evidence was archaic and unconvincing in context.

5008:

Providing greater scrutiny and feedback is a social argument ?

2691:

non-controversial, but if they are, they should be based on an

2642: 2599: 2548: 2511: 2425:

we're a long way from every administrator having 'root' access.

1906: 5858:

Knowledge:Requests for comment/Make userrights self-sufficient

3701:

gotten past the idea of turf battles between users and arbcom.

11062:

User:Scott MacDonald/Removal of reviewer rights from User:Wnt

11002:

User:Scott MacDonald/Removal of reviewer rights from User:Wnt

10361:

Knowledge:Arbitration/Requests/Case#BLP_and_flagged_revisions

6893:

I therefore respectfully ask the Committee to take the steps

5262:

I advertised it at every relevant venue including WT:RFA and

4267:

I don't see any mention of that candidate not being an admin.

2251:

Subcommittee, so why should it be a technical requirement? –

5148:

I'm not talking about adminship here, I'm talking about RFA.

1834:

Changes requested to the checkuser and oversight permissions

271:) which I believe is what you refer to as "normal" RevDel. – 7462:

This is good, especially the "evidence introduction" part.

6377:

rules in open contempt, and then they could have worked on

4389: 10291:

injunction will have served its purpose. Thank you again,

9963:, for example, due to the long-term history of vandalism. 8806:

Knowledge:Wikipedia_Signpost/2011-05-16/Arbitration_report

8617:

WT:MOS#RfC: simple resolution to disagreements over dashes

7790:

than animals, because animals have natural self-restraint.

7354:

everyone involved would have spent a month or so in jail.

6567: 2620:

permission has nothing to do with deleted revisions - see

7394:

tighten procedures. That would mean (at least in part):

7171:

be unilaterally undone. It is also inconsistent with the

6171:

contributor's IP address, and other personal information

1780:@ AGK, That would be a good thing. I hope you are right. 1385:

Knowledge:Arbitration/Requests/Case/Race and intelligence

10231:

Colleagues, this injunction by ArbCom is what is called

3435:

suited for the role. That's as anti-cabal as it comes.

1020:

While I don't think that it is absolutely necessary (as

11268:

Kww unreasonably refused a request to stop and discuss.

8123:

Knowledge:Arbitration Committee/Discretionary sanctions

8034:

Knowledge:Arbitration Committee/Discretionary sanctions

6593:, to start that process so soon after this case closed. 3606:

Point of order, although the CU bit lets you examine a

1026:

Review and restore revisions hidden from administrators

337:. i.e. the following configuration change is needed to 6887:

Sandstein should change the following sentence in his

523:

Knowledge:Arbitration/Requests/Case/Monty Hall problem

9900:@Jclemens. The stated reason was "Trial is complete" 9711:" There's no reason to prescribe a two-step process.— 4493:#Non-administrators are not prima facie untrustworthy 2144:

group which gives members the read-only permissions (

1099:

Thank you, both, for stepping forward to volunteer! –

911:

Updated procedures for arbitrator activity and voting

10814:

Involved blocking to stop any action which does not

10633:". Not everyone can edit pages with protection. ~~ 8049:

Knowledge:Arbitration Committee/Directory/Ban appeal

5207:

Non-administrators are not prima facie untrustworthy

7767:

position of having to ignore it in the first place.

6507:Ncmvocalist, don't you cover ArbCom issues for the 113:

Knowledge:Arbitration/Requests/Case/Kehrli 2 closed

7718:"I think it's important I talk about X because..." 7415:establishing clear and stringent rules of decorum 6526:The Arbitration Committee is Decadent and Depraved 2510:than deciding how much hard drive space to buy. -- 1286:It refers to an internal vote by the arbitrators. 1237:Criteria for appointment to the Audit Subcommittee 9757:the community and your fellow admins rather than 9726:that's a vanishingly small fraction of all BLPs. 8739:I type subject to correction, but in my opinion: 8200:for his OS bit to be removed. He is no longer an 7072:stream is an unpleasant, time-consuming task. -- 6770:community bickering, not to tell us the obvious. 5064:Here's the point where you run out of arguments. 1250:For the avoidance of any doubt, criterion #1 was 828:is still interested in serving in this capacity. 10620:also may discourage editors. Our motto is "The 7365:get indignant over about minor perceived insults 7036:Pardon me for disagreeing, HJ, but when you say 4083:the content creators and improvers, rather than 2972:. Remember that this discussion was done at the 2968:been a community decision on a related subject, 1476:, rather than compulsory, unless everyone would 895:Knowledge:Arbitration/Requests/Case/Henri Coanda 10538:disagreement with an editor's talk page comment 8453:Arbitration motion regarding hyphens and dashes 8330:New procedure for quorum for urgent resolutions 5496:Please familiarize yourself with the published 10656:PC has been removed from all mainspace pages. 8043:Bans by administrators under Arbcom delegation 212:With the greatest respect, my question wasn't 10075:Another suggestion, then, based on the above: 6416:considered, at some stage of the proceedings. 5911:Knowledge:Arbitration/Requests/Case/Noleander 5109:set of tools be used as a prerequitite for a 11264:Kww's refusal to stop was quite unreasonable 8937:Knowledge talk:Manual of Style/dash drafting 7406:creating an 'evidence introduction' process 5862: 5704: 5502: 5444: 5357: 5279: 5228: 4765: 4497: 4394: 4292: 4252: 4137: 3796: 2764: 2716: 2626: 2431:roles and that holders of these three roles 2347: 2253: 1949: 1853: 1332: 1101: 1050: 973: 764: 273: 242: 197: 8965:Updated procedure for Committee resolutions 8935:PMAnderson as kindly set up the subpage at 8637:Ireland/Republic of Ireland/Ireland (state) 8218:Rolling six month statistics are available 3836:, I kept it on the narrow issue of whether 1000:, I think it's called) that are necessary? 8344:Updated procedure for handling ban appeals 7814:True that. I'm not sure what you mean by 4473:Perhaps people didn't realize, during the 2482:sought, and a non-administrator candidate 10729:This is ridiculous. For no reason should 5933:broadly-interpreted across all namespaces 11171:What did a section break ever do to you? 10416:Template:ArbitrationCommitteeChartRecent 8668:2010–11 random sports team/league season 8664:2010-11 random sports team/league season 8147:Changes in Checkuser/Oversight Personnel 2901:fr:Wikipédia:Prise de décision/Oversight 2136:The "real" reform would be to create an 2122:The result is that Bahamut0013 is now a 1939:Keep in mind that not everyone actually 733:at the CU's user talk every 3 months... 7390:If you want my advice, ArbCom needs to 4873:involved in the discussion about them. 4390:#Audit Subcommittee appointments (2011) 4246:Perhaps you missed the well-advertized 2412:shows that we have two types of roles: 14: 10739:, even because of Arbcom's ruling. PC 9781:I'm curious; what would you have done 9709:unprotection if circumstances warrant. 8468:"Interested parties are instructed..." 6305:Okay, thanks for the clarification. -- 6203:to an account is merely a tradition, … 1127:I'm pretty sure he's the first on the 925:Audit Subcommittee appointments (2011) 48:Do not edit the contents of this page. 11272:reinstall pending changes on all BLPs 9761:them (emergencies aside, of course). 9047:agrees that the committee should not 3585:Slim, do you have a problem with the 1330:at the announcement, for posterity. – 10257:involvement is necessary to enforce 9675:I would suggest something like this: 7915: 7527:Not my perceptions, you understand. 29: 18:Knowledge talk:Arbitration Committee 9520:allowed to do that. This is silly. 9131:that everything is in the open. — 655:Advanced permissions and inactivity 27: 7521: 7371:militantly oppose imagined threats 4889:the devs discarded it because the 3116:within the Arbitration Committee. 1782:The Spirit of Neutrality and Truth 1768:The Spirit of Neutrality and Truth 1722:The Spirit of Neutrality and Truth 1712:While I applaud this development, 1152:There are wikis that have enacted 28: 11337: 10591:disrupt wikipedia to make a point 10414:On the bright side, according to 10253:You've hit the nail on the head: 9833: 9262: 8978:there are no privacy concerns? 8097:3) And that's why we have clerks! 7126:cabinet collective responsibility 6587:the list of admins open to recall 6142:Happy-melon Oversight resignation 5246:audit committee appointments page 5224:Knowledge/Requests for adminship/ 2641:Clearly, I meant "researcher". -- 11035:disruption to illustrate a point 10732:an article ever be indefinitely 10597:. Sysops should just use there 8719:, and what should be done about 7916: 7251:license would be admins who are 670:they be removed for inactivity? 33: 11277:increased the protection level. 8650: 8403: 8268: 8262: 8254: 8251: 8103: 8057: 7555: 7530: 7387:effectively or meaningfully. 7368:declaim self-righteous opinions 6477: 5970: 5249:transparency would help a lot. 1498: 1462: 1306: 1272: 1225: 1135:hold both at the same time. — 1044:such as at the French Knowledge 577:something useful now and then! 9966:Peaches (pornographic actress) 9927:Just because no one is making 9405: 9390: 9338: 9323: 7786:defined structures people are 7522: 5616:Well, since there's an RfC at 2408:Another way of looking at it: 13: 1: 11060:Based on your comment above, 8553:Meh, we have our bad days :/ 7999:Arbitration motion regarding 6632:Let's let this go, shall we? 6199:… declining to publicly link 5869: 5711: 5509: 5451: 5364: 5286: 5235: 5113:set of tools, instead of the 4772: 4504: 4401: 4299: 4259: 4144: 3803: 2771: 2723: 2633: 2354: 2260: 1956: 1860: 1339: 1108: 1057: 980: 771: 280: 249: 204: 10087:request should be posted to 8715:be removed as a criteria at 8519:Was that correct hyphenage? 8222:, if it isn't Phantomsteve. 8070:also should be updated, yeah 7277:before you can overturn it. 5768:Church of the Holy Sepulchre 2410:Knowledge:User access levels 2284:as a functionary or an arb? 7: 10601:sense of judgement and use 2736:requested by their arbcom. 1183:standard operating practice 341:(warning: very large file) 10: 11342: 7857:passed-down ideology). -- 6365:enforcement of an orderly 6132:00:43, 21 April 2011 (UTC) 6118:23:11, 20 April 2011 (UTC) 6103:23:09, 20 April 2011 (UTC) 6084:19:55, 19 April 2011 (UTC) 6065:22:37, 18 April 2011 (UTC) 6049:22:18, 18 April 2011 (UTC) 5999:21:06, 18 April 2011 (UTC) 5976:17:26, 18 April 2011 (UTC) 5949:16:53, 18 April 2011 (UTC) 5904:04:58, 13 April 2011 (UTC) 5889:22:34, 12 April 2011 (UTC) 5873:15:22, 12 April 2011 (UTC) 5846:14:20, 19 April 2011 (UTC) 5822:12:21, 19 April 2011 (UTC) 5779:13:07, 15 April 2011 (UTC) 5757:22:23, 12 April 2011 (UTC) 5715:10:43, 12 April 2011 (UTC) 5694:07:12, 12 April 2011 (UTC) 5675:06:53, 12 April 2011 (UTC) 5652:06:35, 12 April 2011 (UTC) 5630:06:24, 12 April 2011 (UTC) 5612:06:11, 12 April 2011 (UTC) 5593:05:23, 12 April 2011 (UTC) 5574:03:54, 12 April 2011 (UTC) 5539:03:23, 12 April 2011 (UTC) 5513:02:43, 12 April 2011 (UTC) 5492:02:38, 12 April 2011 (UTC) 5470:02:28, 12 April 2011 (UTC) 5455:02:10, 12 April 2011 (UTC) 5437:02:03, 12 April 2011 (UTC) 5412:06:58, 13 April 2011 (UTC) 5389:05:09, 13 April 2011 (UTC) 5368:02:31, 12 April 2011 (UTC) 5326:02:22, 12 April 2011 (UTC) 5307:02:04, 12 April 2011 (UTC) 5290:02:10, 12 April 2011 (UTC) 5258:02:03, 12 April 2011 (UTC) 5239:01:53, 12 April 2011 (UTC) 5179:12:32, 12 April 2011 (UTC) 5164:03:12, 12 April 2011 (UTC) 5142:02:15, 12 April 2011 (UTC) 5127:01:52, 12 April 2011 (UTC) 5104:01:42, 12 April 2011 (UTC) 5089:01:28, 12 April 2011 (UTC) 5074:00:31, 12 April 2011 (UTC) 5060:00:09, 12 April 2011 (UTC) 5046:00:07, 12 April 2011 (UTC) 5031:23:55, 11 April 2011 (UTC) 5018:23:54, 11 April 2011 (UTC) 5004:23:47, 11 April 2011 (UTC) 4989:23:43, 11 April 2011 (UTC) 4960:23:52, 11 April 2011 (UTC) 4943:23:49, 11 April 2011 (UTC) 4903:00:31, 12 April 2011 (UTC) 4893:should make the decision. 4883:00:08, 12 April 2011 (UTC) 4865:23:54, 11 April 2011 (UTC) 4850:23:52, 11 April 2011 (UTC) 4832:23:46, 11 April 2011 (UTC) 4793:03:23, 12 April 2011 (UTC) 4776:03:29, 12 April 2011 (UTC) 4756:03:15, 12 April 2011 (UTC) 4592:03:07, 12 April 2011 (UTC) 4508:02:04, 12 April 2011 (UTC) 4486:01:44, 12 April 2011 (UTC) 4405:01:25, 12 April 2011 (UTC) 4372:00:43, 12 April 2011 (UTC) 4303:00:38, 12 April 2011 (UTC) 4284:00:30, 12 April 2011 (UTC) 4263:00:15, 12 April 2011 (UTC) 4242:00:03, 12 April 2011 (UTC) 4220:23:55, 11 April 2011 (UTC) 4177:23:39, 11 April 2011 (UTC) 4163:23:36, 11 April 2011 (UTC) 4148:23:30, 11 April 2011 (UTC) 4131:23:21, 11 April 2011 (UTC) 4098:23:16, 11 April 2011 (UTC) 4062:23:41, 11 April 2011 (UTC) 4031:20:10, 12 April 2011 (UTC) 4016:23:53, 11 April 2011 (UTC) 3986:23:30, 11 April 2011 (UTC) 3971:23:09, 11 April 2011 (UTC) 3943:22:57, 11 April 2011 (UTC) 3930:22:45, 11 April 2011 (UTC) 3906:22:20, 11 April 2011 (UTC) 3875:00:00, 12 April 2011 (UTC) 3850:23:46, 11 April 2011 (UTC) 3824:22:57, 11 April 2011 (UTC) 3807:12:44, 11 April 2011 (UTC) 3784:06:50, 11 April 2011 (UTC) 3769:23:59, 10 April 2011 (UTC) 3745:16:37, 10 April 2011 (UTC) 3730:07:44, 10 April 2011 (UTC) 3715:07:26, 10 April 2011 (UTC) 3645:00:18, 11 April 2011 (UTC) 3616:08:15, 10 April 2011 (UTC) 3600:06:46, 10 April 2011 (UTC) 3581:04:08, 10 April 2011 (UTC) 3493:03:11, 10 April 2011 (UTC) 3478:02:06, 10 April 2011 (UTC) 3418:02:08, 10 April 2011 (UTC) 3029:12:53, 20 April 2011 (UTC) 3011:22:11, 17 April 2011 (UTC) 2914:14:37, 11 April 2011 (UTC) 2895:08:57, 11 April 2011 (UTC) 2594:pass RFA - just that they 2210:19:39, 12 April 2011 (UTC) 2195:04:01, 10 April 2011 (UTC) 1828:13:04, 18 April 2011 (UTC) 1790:13:29, 18 April 2011 (UTC) 1776:13:29, 18 April 2011 (UTC) 1762:11:53, 18 April 2011 (UTC) 1746:06:53, 18 April 2011 (UTC) 1730:04:46, 18 April 2011 (UTC) 1705:02:43, 18 April 2011 (UTC) 1691:02:17, 18 April 2011 (UTC) 1663:01:21, 18 April 2011 (UTC) 1645:00:02, 18 April 2011 (UTC) 1628:23:30, 17 April 2011 (UTC) 1597:23:59, 17 April 2011 (UTC) 1577:07:20, 13 April 2011 (UTC) 1562:04:18, 13 April 2011 (UTC) 1538:04:14, 13 April 2011 (UTC) 1523:00:56, 13 April 2011 (UTC) 1504:14:59, 12 April 2011 (UTC) 1491:14:31, 12 April 2011 (UTC) 1468:11:48, 12 April 2011 (UTC) 1445:11:40, 12 April 2011 (UTC) 1430:08:18, 12 April 2011 (UTC) 1400:Target timetable for cases 1112:17:31, 31 March 2011 (UTC) 1095:17:16, 31 March 2011 (UTC) 1086:16:59, 31 March 2011 (UTC) 1061:16:23, 31 March 2011 (UTC) 1048:or Oversight privileges. – 1016:16:15, 31 March 2011 (UTC) 984:16:10, 31 March 2011 (UTC) 959:16:06, 31 March 2011 (UTC) 868:19:50, 30 March 2011 (UTC) 853:19:34, 30 March 2011 (UTC) 838:19:20, 30 March 2011 (UTC) 823:18:58, 30 March 2011 (UTC) 805:18:36, 30 March 2011 (UTC) 775:18:33, 30 March 2011 (UTC) 758:18:32, 30 March 2011 (UTC) 743:18:29, 30 March 2011 (UTC) 728:18:22, 30 March 2011 (UTC) 713:18:16, 30 March 2011 (UTC) 686:18:04, 30 March 2011 (UTC) 650:17:37, 25 March 2011 (UTC) 630:18:05, 25 March 2011 (UTC) 620:Thank you. Let's move on. 616:09:54, 25 March 2011 (UTC) 592:08:54, 25 March 2011 (UTC) 572:08:47, 25 March 2011 (UTC) 557:08:43, 25 March 2011 (UTC) 514:00:54, 19 March 2011 (UTC) 480:00:49, 19 March 2011 (UTC) 324:20:16, 14 March 2011 (UTC) 308:14:25, 14 March 2011 (UTC) 284:13:52, 14 March 2011 (UTC) 253:04:12, 15 March 2011 (UTC) 235:03:42, 15 March 2011 (UTC) 208:02:57, 15 March 2011 (UTC) 188:06:44, 14 March 2011 (UTC) 172:04:36, 14 March 2011 (UTC) 10786:Penny for your thoughts? 10747:—it's as simple as that. 9855:Penny for your thoughts? 9772:Penny for your thoughts? 9554:Penny for your thoughts? 9429:Penny for your thoughts? 9370:Penny for your thoughts? 9304:Penny for your thoughts? 8595:Penny for your thoughts? 8470:?? Seriously, people... 8385:Penny for your thoughts? 8160:my bad, see comment below 7288:Penny for your thoughts? 7244:for any reason whatsoever 7234:Penny for your thoughts? 7144:Penny for your thoughts? 7028:Penny for your thoughts? 6942:Penny for your thoughts? 6738:Penny for your thoughts? 6249:Penny for your thoughts? 5660:was distinguished from a 3463:21:54, 9 April 2011 (UTC) 3445:18:49, 9 April 2011 (UTC) 3404:21:54, 9 April 2011 (UTC) 3386:18:48, 9 April 2011 (UTC) 3382:Penny for your thoughts? 3358:18:34, 9 April 2011 (UTC) 3333:18:14, 9 April 2011 (UTC) 3329:Penny for your thoughts? 3301:16:28, 9 April 2011 (UTC) 3274:18:24, 9 April 2011 (UTC) 3245:07:55, 9 April 2011 (UTC) 3233:02:47, 9 April 2011 (UTC) 3219:02:35, 9 April 2011 (UTC) 3202:01:16, 9 April 2011 (UTC) 3178:01:58, 9 April 2011 (UTC) 3161:02:35, 9 April 2011 (UTC) 3149:01:38, 9 April 2011 (UTC) 3126:01:34, 9 April 2011 (UTC) 3111:01:30, 9 April 2011 (UTC) 3097:01:23, 9 April 2011 (UTC) 3078:01:04, 9 April 2011 (UTC) 3057:19:54, 8 April 2011 (UTC) 2987:16:38, 8 April 2011 (UTC) 2952:13:59, 8 April 2011 (UTC) 2880:16:38, 8 April 2011 (UTC) 2807:01:20, 9 April 2011 (UTC) 2775:17:44, 8 April 2011 (UTC) 2746:17:37, 8 April 2011 (UTC) 2727:14:31, 8 April 2011 (UTC) 2709:13:27, 8 April 2011 (UTC) 2666:07:37, 9 April 2011 (UTC) 2651:20:00, 8 April 2011 (UTC) 2637:13:38, 8 April 2011 (UTC) 2608:19:59, 8 April 2011 (UTC) 2585:13:21, 8 April 2011 (UTC) 2573:13:14, 8 April 2011 (UTC) 2557:12:56, 8 April 2011 (UTC) 2542:06:46, 8 April 2011 (UTC) 2520:04:53, 8 April 2011 (UTC) 2501:17:49, 7 April 2011 (UTC) 2473:17:21, 7 April 2011 (UTC) 2446:17:01, 7 April 2011 (UTC) 2404:16:50, 7 April 2011 (UTC) 2389:16:43, 7 April 2011 (UTC) 2358:14:19, 7 April 2011 (UTC) 2336:13:57, 7 April 2011 (UTC) 2332:Penny for your thoughts? 2313:13:47, 7 April 2011 (UTC) 2299:13:38, 7 April 2011 (UTC) 2295:Penny for your thoughts? 2264:13:20, 7 April 2011 (UTC) 2246:13:12, 7 April 2011 (UTC) 2114:22:35, 9 April 2011 (UTC) 2080:07:32, 9 April 2011 (UTC) 2053:01:26, 9 April 2011 (UTC) 2019:13:09, 7 April 2011 (UTC) 1977:13:06, 7 April 2011 (UTC) 1960:13:32, 7 April 2011 (UTC) 1935:12:54, 7 April 2011 (UTC) 1931:Penny for your thoughts? 1915:12:10, 7 April 2011 (UTC) 1896:22:52, 6 April 2011 (UTC) 1881:22:42, 6 April 2011 (UTC) 1864:14:24, 6 April 2011 (UTC) 1378:14:12, 8 April 2011 (UTC) 1343:13:09, 6 April 2011 (UTC) 1312:11:42, 6 April 2011 (UTC) 1291:11:39, 6 April 2011 (UTC) 1278:11:38, 6 April 2011 (UTC) 1259:00:17, 6 April 2011 (UTC) 1231:11:34, 6 April 2011 (UTC) 1207:07:10, 3 April 2011 (UTC) 1196:14:09, 2 April 2011 (UTC) 1173:03:19, 2 April 2011 (UTC) 1140:02:18, 2 April 2011 (UTC) 1123:00:24, 2 April 2011 (UTC) 1082:Penny for your thoughts? 709:Penny for your thoughts? 588:Penny for your thoughts? 553:Penny for your thoughts? 542:discretionary sanctions? 231:Penny for your thoughts? 168:Penny for your thoughts? 11316:20:13, 30 May 2011 (UTC) 11301:20:03, 30 May 2011 (UTC) 11242:19:30, 30 May 2011 (UTC) 11233:18:40, 30 May 2011 (UTC) 11220:17:40, 30 May 2011 (UTC) 11211:16:41, 30 May 2011 (UTC) 11197:16:29, 30 May 2011 (UTC) 11186:01:55, 30 May 2011 (UTC) 11155:19:49, 30 May 2011 (UTC) 11140:19:36, 30 May 2011 (UTC) 11120:02:14, 2 June 2011 (UTC) 11078:19:29, 30 May 2011 (UTC) 11056:19:17, 30 May 2011 (UTC) 11029:16:36, 30 May 2011 (UTC) 11019:04:42, 30 May 2011 (UTC) 10988:21:57, 29 May 2011 (UTC) 10978:21:36, 29 May 2011 (UTC) 10963:20:47, 29 May 2011 (UTC) 10948:20:21, 29 May 2011 (UTC) 10938:19:52, 29 May 2011 (UTC) 10915:19:29, 29 May 2011 (UTC) 10905:04:20, 29 May 2011 (UTC) 10890:04:07, 29 May 2011 (UTC) 10875:23:31, 28 May 2011 (UTC) 10865:08:11, 26 May 2011 (UTC) 10850:07:34, 26 May 2011 (UTC) 10835:07:18, 26 May 2011 (UTC) 10790:23:30, 24 May 2011 (UTC) 10770:23:07, 24 May 2011 (UTC) 10719:11:11, 25 May 2011 (UTC) 10698:21:30, 24 May 2011 (UTC) 10677:20:11, 24 May 2011 (UTC) 10666:14:11, 24 May 2011 (UTC) 10646:19:47, 24 May 2011 (UTC) 10584:04:59, 24 May 2011 (UTC) 10559:02:02, 23 May 2011 (UTC) 10528:01:48, 23 May 2011 (UTC) 10495:03:29, 23 May 2011 (UTC) 10473:01:05, 24 May 2011 (UTC) 10458:03:05, 23 May 2011 (UTC) 10443:02:51, 23 May 2011 (UTC) 10428:02:43, 23 May 2011 (UTC) 10410:02:31, 23 May 2011 (UTC) 10395:02:27, 23 May 2011 (UTC) 10377:02:23, 23 May 2011 (UTC) 10354:02:11, 23 May 2011 (UTC) 10343:01:52, 23 May 2011 (UTC) 10324:01:38, 23 May 2011 (UTC) 10313:00:45, 23 May 2011 (UTC) 10298:00:28, 23 May 2011 (UTC) 10279:00:40, 23 May 2011 (UTC) 10249:22:42, 22 May 2011 (UTC) 10215:22:54, 22 May 2011 (UTC) 10182:22:41, 22 May 2011 (UTC) 10167:22:35, 22 May 2011 (UTC) 10142:22:30, 22 May 2011 (UTC) 10132:22:28, 22 May 2011 (UTC) 10110:22:21, 22 May 2011 (UTC) 10059:01:19, 23 May 2011 (UTC) 10044:00:56, 23 May 2011 (UTC) 10025:00:37, 23 May 2011 (UTC) 10001:00:09, 23 May 2011 (UTC) 9980:00:03, 23 May 2011 (UTC) 9959:any effort to unprotect 9956:Indo-Pakistani relations 9949:23:35, 22 May 2011 (UTC) 9923:22:28, 22 May 2011 (UTC) 9908:22:12, 22 May 2011 (UTC) 9894:22:17, 22 May 2011 (UTC) 9880:22:16, 22 May 2011 (UTC) 9859:22:11, 22 May 2011 (UTC) 9840:22:09, 22 May 2011 (UTC) 9822:22:02, 22 May 2011 (UTC) 9776:22:11, 22 May 2011 (UTC) 9746:22:00, 22 May 2011 (UTC) 9736:21:50, 22 May 2011 (UTC) 9721:21:44, 22 May 2011 (UTC) 9702:21:38, 22 May 2011 (UTC) 9669:21:36, 22 May 2011 (UTC) 9654:21:30, 22 May 2011 (UTC) 9634:21:20, 22 May 2011 (UTC) 9616:21:16, 22 May 2011 (UTC) 9595:21:08, 22 May 2011 (UTC) 9567:21:22, 22 May 2011 (UTC) 9558:21:07, 22 May 2011 (UTC) 9539:21:02, 22 May 2011 (UTC) 9529:20:59, 22 May 2011 (UTC) 9507:20:51, 22 May 2011 (UTC) 9497:20:43, 22 May 2011 (UTC) 9482:20:39, 22 May 2011 (UTC) 9463:20:30, 22 May 2011 (UTC) 9448:20:08, 22 May 2011 (UTC) 9433:18:06, 22 May 2011 (UTC) 9413:17:51, 22 May 2011 (UTC) 9374:17:41, 22 May 2011 (UTC) 9346:17:18, 22 May 2011 (UTC) 9308:17:17, 22 May 2011 (UTC) 9287:17:02, 22 May 2011 (UTC) 9269:16:38, 22 May 2011 (UTC) 9236:03:59, 21 May 2011 (UTC) 9221:19:58, 17 May 2011 (UTC) 9203:04:55, 17 May 2011 (UTC) 9176:19:58, 17 May 2011 (UTC) 9136:04:27, 17 May 2011 (UTC) 9096:23:02, 16 May 2011 (UTC) 9056:13:08, 16 May 2011 (UTC) 9025:12:29, 16 May 2011 (UTC) 8992:12:20, 15 May 2011 (UTC) 8960:11:01, 19 May 2011 (UTC) 8930:03:04, 19 May 2011 (UTC) 8908:00:00, 19 May 2011 (UTC) 8888:01:22, 18 May 2011 (UTC) 8818:23:47, 17 May 2011 (UTC) 8797:23:18, 17 May 2011 (UTC) 8776:it previously was not. 8758:21:50, 17 May 2011 (UTC) 8733:21:38, 17 May 2011 (UTC) 8706:21:23, 17 May 2011 (UTC) 8691:21:19, 17 May 2011 (UTC) 8680:21:03, 17 May 2011 (UTC) 8655:20:56, 17 May 2011 (UTC) 8629:20:37, 17 May 2011 (UTC) 8608:10:33, 17 May 2011 (UTC) 8599:10:16, 17 May 2011 (UTC) 8569:03:04, 19 May 2011 (UTC) 8549:20:26, 17 May 2011 (UTC) 8529:05:21, 17 May 2011 (UTC) 8515:02:59, 17 May 2011 (UTC) 8495:22:03, 16 May 2011 (UTC) 8480:21:47, 16 May 2011 (UTC) 8441:20:30, 17 May 2011 (UTC) 8409:10:40, 17 May 2011 (UTC) 8389:10:36, 17 May 2011 (UTC) 8368:22:21, 16 May 2011 (UTC) 8323:20:21, 12 May 2011 (UTC) 8301:16:49, 12 May 2011 (UTC) 8274:16:42, 12 May 2011 (UTC) 8238:10:44, 11 May 2011 (UTC) 8214:08:46, 11 May 2011 (UTC) 8192:08:19, 11 May 2011 (UTC) 8178:05:07, 11 May 2011 (UTC) 8039:Knowledge:Banning policy 5852:RFC on technical aspects 4382:criteria for appointment 1618:I like it. Long overdue. 343: 8137:18:45, 7 May 2011 (UTC) 8109:13:33, 7 May 2011 (UTC) 8083:13:23, 7 May 2011 (UTC) 8063:13:16, 7 May 2011 (UTC) 7981:00:33, 8 May 2011 (UTC) 7932:23:31, 7 May 2011 (UTC) 7880:21:58, 7 May 2011 (UTC) 7867:21:39, 7 May 2011 (UTC) 7836:18:52, 7 May 2011 (UTC) 7810:05:00, 7 May 2011 (UTC) 7758:03:06, 7 May 2011 (UTC) 7734:02:24, 7 May 2011 (UTC) 7669:00:32, 7 May 2011 (UTC) 7647:22:59, 6 May 2011 (UTC) 7638:21:51, 6 May 2011 (UTC) 7623:20:59, 6 May 2011 (UTC) 7592:20:04, 6 May 2011 (UTC) 7560:18:35, 6 May 2011 (UTC) 7536:18:28, 6 May 2011 (UTC) 7480:18:02, 6 May 2011 (UTC) 7457:14:54, 6 May 2011 (UTC) 7307:03:54, 8 May 2011 (UTC) 7292:00:29, 8 May 2011 (UTC) 7265:00:20, 8 May 2011 (UTC) 7238:23:22, 7 May 2011 (UTC) 7214:23:05, 7 May 2011 (UTC) 7148:22:20, 7 May 2011 (UTC) 7112:21:44, 7 May 2011 (UTC) 7097:21:37, 7 May 2011 (UTC) 7082:21:21, 7 May 2011 (UTC) 7032:20:32, 7 May 2011 (UTC) 7012:18:59, 7 May 2011 (UTC) 6985:18:25, 7 May 2011 (UTC) 6966:17:44, 7 May 2011 (UTC) 6946:13:21, 7 May 2011 (UTC) 6922:08:18, 7 May 2011 (UTC) 6869:08:12, 7 May 2011 (UTC) 6849:07:42, 7 May 2011 (UTC) 6834:06:04, 7 May 2011 (UTC) 6819:05:23, 7 May 2011 (UTC) 6804:05:02, 7 May 2011 (UTC) 6780:02:45, 7 May 2011 (UTC) 6761:02:23, 7 May 2011 (UTC) 6742:00:12, 7 May 2011 (UTC) 6720:09:51, 6 May 2011 (UTC) 6691:16:37, 6 May 2011 (UTC) 6676:14:28, 6 May 2011 (UTC) 6662:07:39, 6 May 2011 (UTC) 6648:07:24, 6 May 2011 (UTC) 6628:07:10, 6 May 2011 (UTC) 6606:04:40, 6 May 2011 (UTC) 6580:01:51, 6 May 2011 (UTC) 6549:08:31, 6 May 2011 (UTC) 6538:07:42, 6 May 2011 (UTC) 6521:07:14, 6 May 2011 (UTC) 6503:07:02, 6 May 2011 (UTC) 6482:01:36, 6 May 2011 (UTC) 6462:05:50, 7 May 2011 (UTC) 6438:01:18, 6 May 2011 (UTC) 6398:22:50, 5 May 2011 (UTC) 6313:07:45, 6 May 2011 (UTC) 6301:23:36, 5 May 2011 (UTC) 6285:13:45, 4 May 2011 (UTC) 6269:08:25, 6 May 2011 (UTC) 6253:13:00, 4 May 2011 (UTC) 6229:19:29, 3 May 2011 (UTC) 6219:14:17, 3 May 2011 (UTC) 6192:13:53, 3 May 2011 (UTC) 5442:What change was made? – 5152:trust is not transitive 2657:meta:Research Committee 2622:Special:ListGroupRights 793:global Oversight policy 789:global CheckUser policy 487:nl.wiki also has given 269:Special:ListGroupRights 10491:Steven Walling at work 10350:Steven Walling at work 10320:Steven Walling at work 10294:Steven Walling at work 10093: 9689: 8426:passing that bloomin' 6889:case request statement 5902:) (was 75.57.242.120) 2750:I never said I didn't 2166:abusefilter-log-detail 1602:Arbitration procedures 339:InitialiseSettings.php 10084: 9988:the right thing to do 9680: 9253:Original announcement 8972:Original announcement 8460:Original announcement 8351:Original announcement 8337:Original announcement 8154:Original announcement 8121:Okay, I've rewritten 8023:Original announcement 8009:Original announcement 7362:indulge petty grudges 7339:Comment on procedures 6897:considers appropriate 6331:Original announcement 6163:Original announcement 6149:Original announcement 5920:Original announcement 3920:their lack of issue. 3832:I've started the RFC 1841:Original announcement 1609:Original announcement 1407:Original announcement 1393:Original announcement 1360:Original announcement 1244:Original announcement 932:Original announcement 918:Original announcement 904:Original announcement 887:Original announcement 690:I don't know if it's 662:Original announcement 532:Original announcement 134:Original announcement 120:Original announcement 46:of past discussions. 10158:Okay, changes made. 8944:bone of contention? 8428:updated policy draft 7156:If the AE block was 6910:consider appropriate 6491:frivolous AE request 6367:procedural framework 6205:" (emphasis mine) – 2856:User:John Vandenberg 2170:abusefilter-hide-log 1185:, but I'm not sure. 1154:separation of powers 8646:Republic of Ireland 7581:, to vet evidence. 6258:information the CU 5498:appointment process 3628:~1953 times, while 2964:In addition, there 1803:"snivelling weasel" 1481:original question. 1181:, I think he meant 11006:talk page comments 10743:; semi-protection 10575:going forwards. -- 7816:liberal-democratic 6179:merely a tradition 2854:(list prepared by 1458: 1267:community comments 11064:now seems like a 10233:adult supervision 10213: 10165: 10108: 9700: 9527: 9495: 9410: 9343: 9319: 9285: 8756: 8704: 8627: 8547: 8439: 8182:Who do you mean? 8161: 8135: 8081: 7710:oh-so-desperately 7700:on an even keel. 7590: 7212: 6955: 6712:Elen of the Roads 6460: 6396: 6063: 5997: 5844: 5833: 5819: 5537: 5324: 5256: 4754: 4484: 4475:public discussion 4370: 4218: 4014: 3969: 3873: 3822: 3579: 3461: 3402: 3367:CU and OS and he 3356: 3272: 3200: 3009: 2950: 2849: 2845: 2824: 2821: 2112: 2051: 2009: 1760: 1695:Mostly, I think. 1456: 1428: 1376: 1194: 635:Comment by Nijdam 322: 305: 149:allowed to stand. 107: 106: 58: 57: 52:current talk page 11333: 11115: 10787: 10781: 10768: 10765: 10759: 10753: 10738: 10637: 10579: 10569:fuck bureaucracy 10493: 10352: 10322: 10296: 10212: 10210: 10164: 10162: 10107: 10105: 9968: 9875: 9856: 9850: 9837: 9796: 9773: 9767: 9699: 9697: 9555: 9549: 9526: 9524: 9494: 9492: 9430: 9424: 9409: 9404: 9401: 9371: 9365: 9342: 9337: 9334: 9313: 9305: 9299: 9284: 9282: 9266: 9217: 9212: 9172: 9167: 9092: 9087: 9021: 9016: 8988: 8983: 8752: 8700: 8652: 8623: 8596: 8590: 8546: 8544: 8438: 8436: 8406: 8405: 8386: 8380: 8325: 8270: 8264: 8256: 8253: 8233: 8159: 8134: 8132: 8106: 8105: 8080: 8078: 8060: 8059: 8001:Russavia-Biophys 7973: 7929: 7926: 7921: 7920: 7919: 7864: 7861: 7828: 7807: 7804: 7750: 7731: 7728: 7661: 7589: 7587: 7557: 7533: 7532: 7526: 7472: 7454: 7451: 7304: 7301: 7289: 7283: 7262: 7259: 7235: 7229: 7211: 7209: 7202: 7145: 7139: 7079: 7076: 7029: 7023: 6953: 6943: 6937: 6739: 6733: 6643: 6620: 6547: 6479: 6459: 6457: 6450: 6395: 6393: 6386: 6267: 6250: 6244: 6216: 6204: 6062: 6060: 5996: 5994: 5973: 5972: 5965:chilling effects 5870: 5866: 5839: 5831: 5820: 5811: 5807: 5712: 5708: 5690: 5685: 5648: 5643: 5608: 5603: 5570: 5565: 5536: 5534: 5510: 5506: 5488: 5483: 5452: 5448: 5433: 5428: 5365: 5361: 5323: 5321: 5287: 5283: 5271: 5265: 5255: 5253: 5236: 5232: 4952: 4846: 4841: 4773: 4769: 4753: 4751: 4505: 4501: 4483: 4481: 4402: 4398: 4369: 4367: 4300: 4296: 4280: 4275: 4260: 4256: 4238: 4233: 4217: 4215: 4145: 4141: 4127: 4122: 4013: 4011: 3968: 3966: 3887:This is insanity 3872: 3870: 3821: 3819: 3804: 3800: 3578: 3576: 3460: 3458: 3401: 3399: 3383: 3377: 3355: 3353: 3330: 3324: 3314:or installed by 3271: 3269: 3243: 3199: 3197: 3008: 3006: 2949: 2947: 2847: 2826: 2823: 2820: 2772: 2768: 2724: 2720: 2664: 2634: 2630: 2540: 2355: 2351: 2333: 2327: 2296: 2290: 2261: 2257: 2193: 2187: 2183: 2179: 2175: 2171: 2167: 2163: 2159: 2155: 2151: 2147: 2143: 2139: 2111: 2109: 2078: 2050: 2048: 2003: 1957: 1953: 1932: 1926: 1903:nuclear football 1861: 1857: 1825: 1807:"spineless worm" 1759: 1757: 1686: 1659: 1654: 1574: 1501: 1500: 1465: 1464: 1427: 1425: 1418: 1375: 1373: 1340: 1336: 1309: 1308: 1275: 1274: 1228: 1227: 1205: 1193: 1191: 1177:When Coren said 1171: 1109: 1105: 1083: 1077: 1058: 1054: 1022:suppressrevision 1011: 999: 995: 991: 981: 977: 954: 942: 772: 768: 710: 704: 681: 589: 583: 554: 548: 512: 506: 502: 498: 494: 490: 478: 470: 467: 464: 461: 458: 455: 452: 449: 446: 445:'deletedhistory' 443: 440: 437: 434: 431: 428: 425: 422: 419: 416: 413: 410: 407: 404: 401: 398: 397:'deletedhistory' 395: 392: 389: 386: 383: 380: 377: 374: 371: 368: 365: 362: 359: 356: 353: 350: 347: 346:'groupOverrides' 321: 319: 306: 297: 293: 281: 277: 265:'deleterevision' 250: 246: 232: 226: 205: 201: 186: 169: 163: 85: 60: 59: 37: 36: 30: 11341: 11340: 11336: 11335: 11334: 11332: 11331: 11330: 11173: 11113: 10785: 10777: 10763: 10757: 10751: 10748: 10730: 10644: 10635: 10630:anyone can edit 10618:Full protection 10577: 10489: 10348: 10318: 10292: 10208: 10160: 10103: 9964: 9933:Stargate fandom 9873: 9854: 9846: 9794: 9771: 9763: 9695: 9553: 9545: 9522: 9490: 9428: 9420: 9398: 9394: 9369: 9361: 9331: 9327: 9303: 9295: 9280: 9248: 9215: 9210: 9170: 9165: 9090: 9085: 9019: 9014: 8986: 8981: 8967: 8750:Septentrionalis 8698:Septentrionalis 8621:Septentrionalis 8594: 8586: 8540: 8455: 8432: 8402: 8384: 8376: 8346: 8332: 8308: 8231: 8149: 8128: 8102: 8074: 8056: 8018: 8004: 7979: 7968: 7927: 7924: 7917: 7889:to be admins... 7862: 7859: 7834: 7823: 7805: 7802: 7756: 7745: 7729: 7726: 7667: 7656: 7583: 7529: 7478: 7467: 7452: 7449: 7341: 7302: 7299: 7287: 7279: 7260: 7257: 7233: 7225: 7205: 7203: 7143: 7135: 7077: 7074: 7027: 7019: 6941: 6933: 6737: 6729: 6641: 6626: 6615: 6545:John Vandenberg 6543: 6453: 6451: 6389: 6387: 6326: 6265:John Vandenberg 6263: 6248: 6240: 6214: 6207:such activities 6201:such activities 6198: 6158: 6144: 6056: 5990: 5969: 5915: 5854: 5817: 5810: 5805: 5688: 5683: 5646: 5641: 5606: 5601: 5568: 5563: 5532: 5486: 5481: 5431: 5426: 5319: 5269: 5263: 5251: 5209: 4976: 4950: 4844: 4839: 4749: 4479: 4365: 4278: 4273: 4236: 4231: 4213: 4125: 4120: 4009: 3964: 3889: 3868: 3817: 3690:about it...) U 3574: 3456: 3397: 3381: 3373: 3351: 3328: 3320: 3267: 3241:John Vandenberg 3239: 3195: 3002: 2943: 2928: 2662:John Vandenberg 2660: 2538:John Vandenberg 2536: 2331: 2323: 2294: 2286: 2191:John Vandenberg 2189: 2185: 2181: 2177: 2173: 2169: 2165: 2161: 2157: 2153: 2149: 2145: 2141: 2137: 2107: 2076:John Vandenberg 2074: 2046: 1930: 1922: 1836: 1821: 1811:"two-faced rat" 1753: 1684: 1657: 1652: 1620:Volunteer Marek 1604: 1570: 1497: 1461: 1421: 1419: 1402: 1388: 1369: 1355: 1328:made this clear 1305: 1271: 1239: 1224: 1203:John Vandenberg 1201: 1187: 1169:John Vandenberg 1167: 1081: 1073: 1009: 997: 993: 989: 952: 940: 927: 913: 899: 882: 880:BASC Statistics 708: 700: 694:, but it's not 679: 657: 637: 604: 587: 579: 552: 544: 527: 510:John Vandenberg 508: 504: 500: 496: 492: 488: 476:John Vandenberg 474: 472: 471: 468: 465: 462: 459: 456: 453: 450: 447: 444: 441: 438: 435: 433:'browsearchive' 432: 429: 426: 423: 420: 417: 414: 411: 408: 405: 402: 399: 396: 393: 390: 387: 385:'browsearchive' 384: 381: 378: 375: 372: 369: 366: 363: 360: 357: 354: 351: 348: 345: 315: 303: 296: 291: 230: 222: 184:John Vandenberg 182: 167: 159: 129: 115: 81: 34: 26: 25: 24: 12: 11: 5: 11339: 11329: 11328: 11327: 11326: 11325: 11324: 11323: 11322: 11321: 11320: 11319: 11318: 11308:Chester Markel 11289: 11251: 11250: 11249: 11248: 11247: 11246: 11245: 11244: 11200: 11199: 11172: 11169: 11168: 11167: 11166: 11165: 11164: 11163: 11162: 11161: 11160: 11159: 11158: 11157: 11147:Chester Markel 11128: 11127: 11126: 11125: 11124: 11123: 11122: 11092: 11091: 11090: 11089: 11088: 11087: 11086: 11085: 11084: 11083: 11082: 11081: 11080: 11070:Chester Markel 11058: 11048:Chester Markel 11011:Chester Markel 10970:Chester Markel 10965: 10955:Chester Markel 10930:Chester Markel 10925: 10897:Chester Markel 10892: 10882:Chester Markel 10857:Chester Markel 10852: 10842:Chester Markel 10837: 10827:Chester Markel 10822: 10821: 10820: 10812: 10724: 10723: 10722: 10721: 10669: 10668: 10654: 10653: 10652: 10651: 10650: 10649: 10648: 10640: 10573:WP:COMMONSENSE 10551:Chester Markel 10531: 10530: 10511: 10510: 10509: 10508: 10507: 10506: 10505: 10504: 10503: 10502: 10501: 10500: 10499: 10498: 10497: 10481: 10480: 10479: 10478: 10477: 10476: 10475: 10450:Chester Markel 10420:Chester Markel 10387:Chester Markel 10379: 10369:Chester Markel 10335:Chester Markel 10305:Chester Markel 10283: 10282: 10281: 10271:Chester Markel 10228: 10227: 10226: 10225: 10224: 10223: 10222: 10221: 10220: 10219: 10218: 10217: 10193: 10192: 10191: 10190: 10189: 10188: 10187: 10186: 10185: 10184: 10149: 10148: 10147: 10146: 10145: 10144: 10134: 10115: 10114: 10113: 10112: 10097: 10096: 10095: 10094: 10079: 10078: 10077: 10076: 10073: 10072: 10071: 10070: 10069: 10068: 10067: 10066: 10065: 10064: 10063: 10062: 10061: 10051:Chester Markel 10031: 9898: 9897: 9896: 9882: 9861: 9809: 9808: 9807: 9806: 9805: 9804: 9803: 9802: 9801: 9800: 9779: 9728:Chester Markel 9691: 9690: 9677: 9676: 9672: 9671: 9661:Chester Markel 9656: 9621: 9619: 9618: 9608:Chester Markel 9578: 9577: 9576: 9575: 9574: 9573: 9572: 9571: 9570: 9569: 9541: 9512: 9511: 9510: 9509: 9474: 9473: 9472: 9471: 9470: 9469: 9468: 9467: 9466: 9465: 9440:Chester Markel 9396: 9392: 9385: 9329: 9325: 9311: 9310: 9290: 9289: 9257: 9256: 9247: 9244: 9243: 9242: 9241: 9240: 9239: 9238: 9189: 9188: 9187: 9186: 9185: 9184: 9183: 9182: 9181: 9180: 9179: 9178: 9148: 9147: 9146: 9145: 9144: 9143: 9142: 9141: 9140: 9139: 9105: 9104: 9103: 9102: 9101: 9100: 9099: 9098: 9064: 9063: 9062: 9061: 9060: 9059: 9030: 9029: 9028: 9027: 9006: 9005: 9004: 9003: 8995: 8994: 8975: 8966: 8963: 8933: 8932: 8895: 8894: 8893: 8892: 8891: 8890: 8865: 8864: 8863: 8862: 8861: 8860: 8851: 8850: 8849: 8848: 8847: 8846: 8837: 8836: 8835: 8834: 8833: 8832: 8823: 8822: 8821: 8820: 8773: 8772: 8771: 8770: 8769: 8768: 8767: 8766: 8765: 8764: 8763: 8762: 8761: 8760: 8746: 8743: 8658: 8657: 8613: 8612: 8611: 8610: 8580: 8579: 8578: 8577: 8576: 8575: 8574: 8573: 8572: 8571: 8464: 8463: 8454: 8451: 8450: 8449: 8448: 8447: 8446: 8445: 8444: 8443: 8416: 8415: 8414: 8413: 8412: 8411: 8392: 8391: 8355: 8354: 8345: 8342: 8341: 8340: 8331: 8328: 8327: 8326: 8285: 8284: 8283: 8282: 8281: 8280: 8279: 8278: 8277: 8276: 8240: 8148: 8145: 8144: 8143: 8142: 8141: 8140: 8139: 8114: 8113: 8112: 8111: 8098: 8095: 8092: 8086: 8085: 8052: 8051: 8046: 8041:(specifically 8036: 8027: 8026: 8017: 8014: 8013: 8012: 8003: 7997: 7996: 7995: 7994: 7993: 7992: 7991: 7990: 7989: 7988: 7987: 7986: 7985: 7984: 7983: 7974: 7947: 7945: 7944: 7943: 7942: 7941: 7940: 7939: 7938: 7937: 7936: 7935: 7934: 7901: 7900: 7899: 7898: 7897: 7896: 7895: 7894: 7893: 7892: 7891: 7890: 7829: 7794: 7793: 7792: 7791: 7771: 7770: 7769: 7768: 7761: 7760: 7751: 7684: 7683: 7682: 7681: 7680: 7679: 7678: 7677: 7676: 7675: 7674: 7673: 7672: 7671: 7662: 7610: 7599: 7598: 7597: 7596: 7595: 7594: 7565: 7564: 7563: 7562: 7539: 7538: 7518: 7517: 7512: 7511: 7497: 7496: 7493:civlity policy 7489:Climate change 7483: 7482: 7473: 7431: 7430: 7429: 7428: 7421: 7420: 7419: 7413: 7412: 7411: 7404: 7403: 7402: 7376: 7375: 7372: 7369: 7366: 7363: 7340: 7337: 7336: 7335: 7334: 7333: 7332: 7331: 7330: 7329: 7328: 7327: 7326: 7325: 7324: 7323: 7322: 7321: 7320: 7319: 7318: 7317: 7316: 7315: 7314: 7313: 7312: 7311: 7310: 7309: 7217: 7216: 7189: 7176: 7164: 7122: 7099: 7058: 7057: 7056: 7055: 7054: 7053: 7052: 7051: 7050: 7049: 7048: 7047: 6992: 6991: 6990: 6989: 6988: 6987: 6972: 6925: 6924: 6901: 6900: 6884: 6883: 6882: 6881: 6880: 6879: 6878: 6877: 6876: 6875: 6874: 6873: 6872: 6871: 6836: 6791: 6745: 6744: 6723: 6722: 6707: 6706: 6705: 6704: 6703: 6702: 6701: 6700: 6699: 6698: 6697: 6696: 6695: 6694: 6693: 6650: 6621: 6594: 6559: 6558: 6557: 6556: 6555: 6554: 6553: 6552: 6551: 6469: 6468: 6467: 6466: 6465: 6464: 6441: 6440: 6424: 6423: 6418: 6417: 6412: 6411: 6406: 6405: 6361:the clear and 6335: 6334: 6325: 6319: 6318: 6317: 6316: 6315: 6274: 6273: 6272: 6271: 6234: 6233: 6232: 6231: 6210: 6167: 6166: 6157: 6154: 6153: 6152: 6143: 6140: 6139: 6138: 6137: 6136: 6135: 6134: 6090: 6089: 6088: 6087: 6086: 6071: 6070: 6069: 6068: 6067: 6006: 6005: 6004: 6003: 6002: 6001: 5981: 5980: 5979: 5978: 5952: 5951: 5924: 5923: 5914: 5908: 5907: 5906: 5896:69.111.194.167 5891: 5881:69.111.194.167 5853: 5850: 5849: 5848: 5815: 5799: 5798: 5790: 5782: 5781: 5749:69.111.194.167 5740: 5739: 5738: 5737: 5736: 5735: 5734: 5733: 5732: 5731: 5730: 5729: 5728: 5727: 5726: 5725: 5724: 5723: 5722: 5721: 5720: 5719: 5718: 5717: 5580: 5548: 5547: 5546: 5545: 5544: 5543: 5542: 5541: 5520: 5519: 5518: 5517: 5516: 5515: 5473: 5472: 5457: 5417: 5416: 5415: 5414: 5381:69.111.194.167 5376: 5375: 5374: 5373: 5372: 5371: 5370: 5352: 5344: 5333: 5332: 5331: 5330: 5329: 5328: 5310: 5309: 5294: 5293: 5292: 5208: 5205: 5204: 5203: 5202: 5201: 5200: 5199: 5198: 5197: 5196: 5195: 5194: 5193: 5192: 5191: 5190: 5189: 5188: 5187: 5186: 5185: 5184: 5183: 5182: 5181: 4975: 4972: 4971: 4970: 4969: 4968: 4967: 4966: 4965: 4964: 4963: 4962: 4926: 4925: 4924: 4923: 4922: 4921: 4920: 4919: 4918: 4917: 4916: 4915: 4914: 4913: 4912: 4911: 4910: 4909: 4908: 4907: 4906: 4905: 4852: 4819: 4818: 4817: 4816: 4815: 4814: 4813: 4812: 4811: 4810: 4809: 4808: 4807: 4806: 4805: 4804: 4803: 4802: 4801: 4800: 4799: 4798: 4797: 4796: 4795: 4780: 4779: 4778: 4707: 4706: 4705: 4704: 4703: 4702: 4701: 4700: 4699: 4698: 4697: 4696: 4695: 4694: 4693: 4692: 4691: 4690: 4689: 4688: 4687: 4686: 4685: 4684: 4683: 4682: 4681: 4680: 4679: 4678: 4677: 4676: 4675: 4674: 4673: 4672: 4671: 4670: 4629: 4628: 4627: 4626: 4625: 4624: 4623: 4622: 4621: 4620: 4619: 4618: 4617: 4616: 4615: 4614: 4613: 4612: 4611: 4610: 4609: 4608: 4607: 4606: 4605: 4604: 4603: 4602: 4601: 4600: 4599: 4598: 4597: 4596: 4595: 4594: 4545: 4544: 4543: 4542: 4541: 4540: 4539: 4538: 4537: 4536: 4535: 4534: 4533: 4532: 4531: 4530: 4529: 4528: 4527: 4526: 4525: 4524: 4523: 4522: 4521: 4520: 4519: 4518: 4517: 4516: 4515: 4514: 4513: 4512: 4511: 4510: 4438: 4437: 4436: 4435: 4434: 4433: 4432: 4431: 4430: 4429: 4428: 4427: 4426: 4425: 4424: 4423: 4422: 4421: 4420: 4419: 4418: 4417: 4416: 4415: 4414: 4413: 4412: 4411: 4410: 4409: 4408: 4407: 4332: 4331: 4330: 4329: 4328: 4327: 4326: 4325: 4324: 4323: 4322: 4321: 4320: 4319: 4318: 4317: 4316: 4315: 4314: 4313: 4312: 4311: 4310: 4309: 4308: 4307: 4306: 4305: 4268: 4192: 4191: 4190: 4189: 4188: 4187: 4186: 4185: 4184: 4183: 4182: 4181: 4180: 4179: 4150: 4105: 4104: 4103: 4102: 4101: 4100: 4071: 4070: 4069: 4068: 4067: 4066: 4065: 4064: 4042: 4041: 4040: 4039: 4038: 4037: 4036: 4035: 4034: 4033: 4023:69.111.194.167 4018: 3995: 3994: 3993: 3992: 3991: 3990: 3989: 3988: 3954: 3953: 3952: 3951: 3950: 3949: 3888: 3885: 3884: 3883: 3882: 3881: 3880: 3879: 3878: 3877: 3857: 3856: 3855: 3854: 3853: 3852: 3827: 3826: 3789: 3788: 3787: 3786: 3754: 3752: 3751: 3750: 3749: 3748: 3747: 3703: 3702: 3698: 3695: 3692: 3676: 3671: 3670: 3666: 3665: 3664: 3663: 3662: 3661: 3660: 3659: 3658: 3657: 3656: 3655: 3654: 3653: 3652: 3651: 3650: 3649: 3648: 3647: 3632:has been seen 3625:has been seen 3558: 3557: 3556: 3555: 3554: 3553: 3552: 3551: 3550: 3549: 3548: 3547: 3528: 3527: 3526: 3525: 3524: 3523: 3522: 3521: 3520: 3519: 3518: 3517: 3502: 3501: 3500: 3499: 3498: 3497: 3496: 3495: 3448: 3447: 3424: 3423: 3422: 3421: 3420: 3389: 3388: 3342: 3341: 3340: 3339: 3338: 3337: 3336: 3335: 3283: 3282: 3281: 3280: 3279: 3278: 3277: 3276: 3250: 3249: 3248: 3247: 3235: 3205: 3204: 3189: 3188: 3187: 3186: 3185: 3184: 3183: 3182: 3181: 3180: 3165: 3164: 3163: 3137:to that degree 3081: 3080: 3059: 3038: 3037: 3036: 3035: 3034: 3033: 3032: 3031: 3014: 3013: 2990: 2989: 2977:consultation. 2962: 2955: 2954: 2927: 2924: 2923: 2922: 2921: 2920: 2919: 2918: 2917: 2916: 2851: 2850: 2844: 2841: 2838: 2835: 2832: 2829: 2818: 2817: 2816: 2815: 2814: 2813: 2812: 2811: 2810: 2809: 2687: 2686: 2685: 2684: 2683: 2682: 2681: 2680: 2679: 2678: 2677: 2676: 2675: 2674: 2673: 2672: 2671: 2670: 2669: 2668: 2619: 2614: 2613: 2612: 2611: 2610: 2587: 2527: 2526: 2525: 2524: 2523: 2522: 2453: 2452: 2451: 2450: 2449: 2448: 2427: 2426: 2419: 2406: 2371: 2370: 2369: 2368: 2367: 2366: 2365: 2364: 2363: 2362: 2361: 2360: 2339: 2338: 2316: 2315: 2302: 2301: 2276:If it's not a 2269: 2268: 2267: 2266: 2227: 2226: 2225: 2224: 2223: 2222: 2221: 2220: 2219: 2218: 2217: 2216: 2215: 2214: 2213: 2212: 2202:69.111.194.167 2162:suppressionlog 2150:deletedhistory 2134: 2131: 2127: 2120: 2091: 2090: 2089: 2088: 2087: 2086: 2085: 2084: 2083: 2082: 2062: 2061: 2060: 2059: 2058: 2057: 2056: 2055: 2034: 2033: 2032: 2031: 2030: 2029: 2028: 2027: 2026: 2025: 2024: 2023: 2022: 2021: 1988: 1987: 1986: 1985: 1984: 1983: 1982: 1981: 1980: 1979: 1964: 1963: 1962: 1849:bugzilla:28440 1845: 1844: 1835: 1832: 1831: 1830: 1817: 1814: 1797: 1796: 1795: 1794: 1793: 1792: 1778: 1710: 1709: 1708: 1707: 1672: 1671: 1670: 1669: 1668: 1667: 1666: 1665: 1633: 1613: 1612: 1603: 1600: 1580: 1579: 1549: 1548: 1547: 1546: 1545: 1544: 1543: 1542: 1541: 1540: 1448: 1447: 1411: 1410: 1401: 1398: 1397: 1396: 1387: 1382: 1381: 1380: 1364: 1363: 1354: 1353:Internal teams 1351: 1350: 1349: 1348: 1347: 1346: 1345: 1319: 1318: 1317: 1316: 1315: 1314: 1296: 1295: 1294: 1293: 1281: 1280: 1248: 1247: 1238: 1235: 1234: 1233: 1218: 1217: 1216: 1215: 1214: 1213: 1212: 1211: 1210: 1209: 1151: 1116: 1115: 1114: 1088: 1069: 1068: 1067: 1066: 1065: 1064: 1063: 1039: 1035: 1031: 1030:deletedhistory 1024:allows one to 1023: 970: 966: 936: 935: 926: 923: 922: 921: 912: 909: 908: 907: 898: 892: 891: 890: 881: 878: 877: 876: 875: 874: 873: 872: 871: 870: 813:requirement?-- 810: 809: 808: 781: 780: 779: 778: 777: 760: 715: 666: 665: 656: 653: 636: 633: 603: 600: 599: 598: 597: 596: 595: 594: 536: 535: 526: 520: 519: 518: 517: 516: 499:to the groups 489:deletedhistory 344: 335:bugzilla:21044 331: 330: 329: 328: 327: 326: 301: 266: 260: 259: 258: 257: 256: 255: 191: 190: 178: 155: 154: 150: 138: 137: 128: 125: 124: 123: 114: 111: 109: 105: 104: 99: 96: 91: 86: 79: 74: 69: 66: 56: 55: 38: 15: 9: 6: 4: 3: 2: 11338: 11317: 11313: 11309: 11304: 11303: 11302: 11298: 11294: 11290: 11286: 11282: 11278: 11273: 11269: 11265: 11261: 11260: 11259: 11258: 11257: 11256: 11255: 11254: 11253: 11252: 11243: 11240: 11236: 11235: 11234: 11231: 11228: 11223: 11222: 11221: 11218: 11214: 11213: 11212: 11209: 11206: 11202: 11201: 11198: 11195: 11190: 11189: 11188: 11187: 11183: 11179: 11156: 11152: 11148: 11143: 11142: 11141: 11138: 11134: 11129: 11121: 11118: 11116: 11110: 11106: 11105:WP:UNINVOLVED 11102: 11098: 11093: 11079: 11075: 11071: 11067: 11063: 11059: 11057: 11053: 11049: 11045: 11040: 11036: 11032: 11031: 11030: 11027: 11022: 11021: 11020: 11016: 11012: 11007: 11003: 10999: 10995: 10991: 10990: 10989: 10986: 10981: 10980: 10979: 10975: 10971: 10966: 10964: 10960: 10956: 10951: 10950: 10949: 10946: 10941: 10940: 10939: 10935: 10931: 10926: 10922: 10918: 10917: 10916: 10913: 10908: 10907: 10906: 10902: 10898: 10893: 10891: 10887: 10883: 10878: 10877: 10876: 10873: 10868: 10867: 10866: 10862: 10858: 10853: 10851: 10847: 10843: 10838: 10836: 10832: 10828: 10823: 10817: 10813: 10809: 10805: 10804: 10802: 10797: 10793: 10792: 10791: 10788: 10782: 10780: 10773: 10772: 10771: 10766: 10760: 10754: 10746: 10742: 10737: 10735: 10728: 10727: 10726: 10725: 10720: 10716: 10712: 10708: 10706: 10701: 10700: 10699: 10695: 10691: 10687: 10686: 10681: 10680: 10679: 10678: 10675: 10667: 10663: 10659: 10655: 10647: 10643: 10638: 10632: 10631: 10626: 10623: 10619: 10615: 10614: 10608: 10604: 10600: 10596: 10592: 10588: 10587: 10586: 10585: 10582: 10580: 10574: 10570: 10562: 10561: 10560: 10556: 10552: 10547: 10543: 10539: 10535: 10534: 10533: 10532: 10529: 10525: 10521: 10517: 10512: 10496: 10492: 10487: 10482: 10474: 10470: 10466: 10461: 10460: 10459: 10455: 10451: 10446: 10445: 10444: 10440: 10436: 10431: 10430: 10429: 10425: 10421: 10417: 10413: 10412: 10411: 10407: 10403: 10398: 10397: 10396: 10392: 10388: 10384: 10380: 10378: 10374: 10370: 10366: 10362: 10357: 10356: 10355: 10351: 10346: 10345: 10344: 10340: 10336: 10332: 10327: 10326: 10325: 10321: 10316: 10315: 10314: 10310: 10306: 10301: 10300: 10299: 10295: 10289: 10284: 10280: 10276: 10272: 10268: 10264: 10260: 10256: 10252: 10251: 10250: 10246: 10242: 10238: 10234: 10230: 10229: 10216: 10211: 10205: 10204: 10203: 10202: 10201: 10200: 10199: 10198: 10197: 10196: 10195: 10194: 10183: 10179: 10175: 10170: 10169: 10168: 10163: 10157: 10156: 10155: 10154: 10153: 10152: 10151: 10150: 10143: 10140: 10135: 10133: 10129: 10125: 10121: 10120: 10119: 10118: 10117: 10116: 10111: 10106: 10101: 10100: 10099: 10098: 10092: 10090: 10083: 10082: 10081: 10080: 10074: 10060: 10056: 10052: 10047: 10046: 10045: 10041: 10037: 10032: 10028: 10027: 10026: 10022: 10018: 10013: 10009: 10004: 10003: 10002: 9998: 9994: 9990: 9989: 9983: 9982: 9981: 9977: 9973: 9967: 9962: 9957: 9952: 9951: 9950: 9946: 9942: 9938: 9934: 9930: 9926: 9925: 9924: 9920: 9916: 9911: 9910: 9909: 9906: 9902: 9899: 9895: 9891: 9887: 9883: 9881: 9878: 9876: 9869: 9868: 9862: 9860: 9857: 9851: 9849: 9843: 9842: 9841: 9838: 9836: 9830: 9826: 9825: 9824: 9823: 9819: 9815: 9799: 9797: 9790: 9789: 9784: 9780: 9778: 9777: 9774: 9768: 9766: 9760: 9756: 9749: 9748: 9747: 9744: 9739: 9738: 9737: 9733: 9729: 9724: 9723: 9722: 9718: 9714: 9710: 9705: 9704: 9703: 9698: 9693: 9692: 9688: 9686: 9679: 9678: 9674: 9673: 9670: 9666: 9662: 9657: 9655: 9651: 9647: 9643: 9638: 9637: 9636: 9635: 9632: 9627: 9622: 9617: 9613: 9609: 9604: 9599: 9598: 9597: 9596: 9592: 9588: 9584: 9583:Tony Meléndez 9568: 9565: 9561: 9560: 9559: 9556: 9550: 9548: 9542: 9540: 9537: 9532: 9531: 9530: 9525: 9518: 9517: 9516: 9515: 9514: 9513: 9508: 9505: 9500: 9499: 9498: 9493: 9486: 9485: 9484: 9483: 9480: 9464: 9460: 9456: 9451: 9450: 9449: 9445: 9441: 9436: 9435: 9434: 9431: 9425: 9423: 9416: 9415: 9414: 9411: 9408: 9402: 9400: 9386: 9382: 9377: 9376: 9375: 9372: 9366: 9364: 9358: 9354: 9350: 9349: 9348: 9347: 9344: 9341: 9335: 9333: 9317: 9316:edit conflict 9309: 9306: 9300: 9298: 9292: 9291: 9288: 9283: 9277: 9273: 9272: 9271: 9270: 9267: 9265: 9255: 9254: 9250: 9249: 9237: 9233: 9229: 9224: 9223: 9222: 9219: 9218: 9213: 9206: 9205: 9204: 9200: 9196: 9191: 9190: 9177: 9174: 9173: 9168: 9160: 9159: 9158: 9157: 9156: 9155: 9154: 9153: 9152: 9151: 9150: 9149: 9138: 9137: 9134: 9130: 9126: 9120: 9115: 9114: 9113: 9112: 9111: 9110: 9109: 9108: 9107: 9106: 9097: 9094: 9093: 9088: 9082:corrected. 9080: 9076: 9075:sunshine laws 9072: 9071: 9070: 9069: 9068: 9067: 9066: 9065: 9058: 9057: 9054: 9050: 9046: 9042: 9036: 9035: 9034: 9033: 9032: 9031: 9026: 9023: 9022: 9017: 9010: 9009: 9008: 9007: 9002: 8999: 8998: 8997: 8996: 8993: 8990: 8989: 8984: 8976: 8974: 8973: 8969: 8968: 8962: 8961: 8957: 8954: 8951: 8947: 8943: 8938: 8931: 8927: 8924: 8921: 8917: 8912: 8911: 8910: 8909: 8905: 8901: 8889: 8885: 8882: 8879: 8875: 8871: 8870: 8869: 8868: 8867: 8866: 8857: 8856: 8855: 8854: 8853: 8852: 8843: 8842: 8841: 8840: 8839: 8838: 8829: 8828: 8827: 8826: 8825: 8824: 8819: 8815: 8811: 8807: 8803: 8802: 8801: 8800: 8799: 8798: 8794: 8791: 8788: 8783: 8780:advocates of 8777: 8759: 8755: 8751: 8747: 8744: 8741: 8740: 8738: 8737: 8736: 8735: 8734: 8730: 8726: 8722: 8718: 8714: 8709: 8708: 8707: 8703: 8699: 8694: 8693: 8692: 8688: 8683: 8682: 8681: 8677: 8673: 8669: 8665: 8660: 8659: 8656: 8653: 8647: 8643: 8638: 8633: 8632: 8631: 8630: 8626: 8622: 8618: 8609: 8606: 8602: 8601: 8600: 8597: 8591: 8589: 8582: 8581: 8570: 8566: 8563: 8560: 8556: 8552: 8551: 8550: 8545: 8543: 8536: 8532: 8531: 8530: 8526: 8522: 8518: 8517: 8516: 8512: 8509: 8506: 8502: 8498: 8497: 8496: 8492: 8488: 8484: 8483: 8482: 8481: 8477: 8473: 8469: 8462: 8461: 8457: 8456: 8442: 8437: 8435: 8429: 8424: 8423: 8422: 8421: 8420: 8419: 8418: 8417: 8410: 8407: 8398: 8397: 8396: 8395: 8394: 8393: 8390: 8387: 8381: 8379: 8372: 8371: 8370: 8369: 8365: 8361: 8353: 8352: 8348: 8347: 8339: 8338: 8334: 8333: 8324: 8320: 8316: 8312: 8305: 8304: 8303: 8302: 8298: 8294: 8290: 8275: 8271: 8265: 8259: 8258: 8257: 8246: 8241: 8239: 8236: 8234: 8227: 8226: 8221: 8217: 8216: 8215: 8211: 8207: 8203: 8199: 8195: 8194: 8193: 8189: 8185: 8181: 8180: 8179: 8175: 8171: 8168: 8166: 8158: 8157: 8156: 8155: 8151: 8150: 8138: 8133: 8131: 8124: 8120: 8119: 8118: 8117: 8116: 8115: 8110: 8107: 8099: 8096: 8093: 8090: 8089: 8088: 8087: 8084: 8079: 8077: 8071: 8067: 8066: 8065: 8064: 8061: 8050: 8047: 8044: 8040: 8037: 8035: 8032: 8031: 8030: 8025: 8024: 8020: 8019: 8011: 8010: 8006: 8005: 8002: 7982: 7978: 7972: 7966: 7962: 7961: 7960: 7959: 7958: 7957: 7956: 7955: 7954: 7953: 7952: 7951: 7950: 7949: 7948: 7933: 7930: 7913: 7912: 7911: 7910: 7909: 7908: 7907: 7906: 7905: 7904: 7903: 7902: 7888: 7883: 7882: 7881: 7878: 7874: 7870: 7869: 7868: 7865: 7855: 7850: 7846: 7842: 7839: 7838: 7837: 7833: 7827: 7821: 7817: 7813: 7812: 7811: 7808: 7798: 7797: 7796: 7795: 7789: 7784: 7780: 7775: 7774: 7773: 7772: 7765: 7764: 7763: 7762: 7759: 7755: 7749: 7743: 7738: 7737: 7736: 7735: 7732: 7723: 7719: 7713: 7711: 7707: 7701: 7698: 7693: 7689: 7670: 7666: 7660: 7654: 7650: 7649: 7648: 7645: 7641: 7640: 7639: 7635: 7631: 7626: 7625: 7624: 7620: 7616: 7611: 7607: 7606: 7605: 7604: 7603: 7602: 7601: 7600: 7593: 7588: 7586: 7580: 7579:internal team 7576: 7571: 7570: 7569: 7568: 7567: 7566: 7561: 7558: 7551: 7547: 7543: 7542: 7541: 7540: 7537: 7534: 7525: 7524: 7520: 7519: 7514: 7513: 7508: 7504: 7499: 7498: 7495:as it stands. 7494: 7490: 7485: 7484: 7481: 7477: 7471: 7465: 7461: 7460: 7459: 7458: 7455: 7445: 7439: 7436: 7426: 7425: 7422: 7417: 7416: 7414: 7408: 7407: 7405: 7400: 7399: 7397: 7396: 7395: 7393: 7388: 7386: 7382: 7373: 7370: 7367: 7364: 7361: 7360: 7359: 7355: 7352: 7347: 7308: 7305: 7295: 7294: 7293: 7290: 7284: 7282: 7276: 7272: 7268: 7267: 7266: 7263: 7254: 7250: 7245: 7241: 7240: 7239: 7236: 7230: 7228: 7221: 7220: 7219: 7218: 7215: 7210: 7208: 7200: 7195: 7190: 7187: 7182: 7177: 7174: 7170: 7165: 7161: 7160: 7155: 7154: 7151: 7150: 7149: 7146: 7140: 7138: 7131: 7127: 7123: 7119: 7115: 7114: 7113: 7109: 7105: 7100: 7098: 7094: 7090: 7085: 7084: 7083: 7080: 7070: 7069: 7068: 7067: 7066: 7065: 7064: 7063: 7062: 7061: 7060: 7059: 7044: 7039: 7035: 7034: 7033: 7030: 7024: 7022: 7015: 7014: 7013: 7009: 7005: 7000: 6999: 6998: 6997: 6996: 6995: 6994: 6993: 6986: 6982: 6978: 6973: 6969: 6968: 6967: 6963: 6959: 6950: 6949: 6948: 6947: 6944: 6938: 6936: 6927: 6926: 6923: 6919: 6915: 6914:31.166.57.231 6911: 6909: 6903: 6902: 6898: 6896: 6890: 6886: 6885: 6870: 6866: 6862: 6857: 6852: 6851: 6850: 6846: 6842: 6837: 6835: 6831: 6827: 6822: 6821: 6820: 6816: 6812: 6807: 6806: 6805: 6801: 6797: 6792: 6788: 6783: 6782: 6781: 6777: 6773: 6769: 6764: 6763: 6762: 6758: 6754: 6749: 6748: 6747: 6746: 6743: 6740: 6734: 6732: 6725: 6724: 6721: 6717: 6713: 6708: 6692: 6688: 6684: 6679: 6678: 6677: 6673: 6669: 6665: 6664: 6663: 6659: 6655: 6651: 6649: 6646: 6644: 6637: 6636: 6631: 6630: 6629: 6625: 6619: 6613: 6609: 6608: 6607: 6603: 6599: 6595: 6592: 6588: 6583: 6582: 6581: 6577: 6573: 6569: 6565: 6560: 6550: 6546: 6541: 6540: 6539: 6535: 6531: 6527: 6524: 6523: 6522: 6518: 6514: 6510: 6506: 6505: 6504: 6500: 6496: 6492: 6487: 6486: 6485: 6484: 6483: 6480: 6473: 6472: 6471: 6470: 6463: 6458: 6456: 6447: 6446: 6445: 6444: 6443: 6442: 6439: 6435: 6431: 6426: 6425: 6420: 6419: 6414: 6413: 6408: 6407: 6402: 6401: 6400: 6399: 6394: 6392: 6383: 6380: 6376: 6370: 6368: 6364: 6359: 6353: 6350: 6344: 6341: 6333: 6332: 6328: 6327: 6323: 6314: 6311: 6308: 6304: 6303: 6302: 6298: 6294: 6289: 6288: 6287: 6286: 6283: 6280: 6270: 6266: 6261: 6256: 6255: 6254: 6251: 6245: 6243: 6236: 6235: 6230: 6227: 6222: 6221: 6220: 6217: 6208: 6202: 6196: 6195: 6194: 6193: 6190: 6186: 6185: 6180: 6176: 6172: 6165: 6164: 6160: 6159: 6151: 6150: 6146: 6145: 6133: 6129: 6125: 6121: 6120: 6119: 6115: 6111: 6106: 6105: 6104: 6100: 6096: 6091: 6085: 6081: 6077: 6072: 6066: 6061: 6059: 6052: 6051: 6050: 6046: 6042: 6038: 6034: 6030: 6026: 6022: 6018: 6014: 6013: 6012: 6011: 6010: 6009: 6008: 6007: 6000: 5995: 5993: 5987: 5986: 5985: 5984: 5983: 5982: 5977: 5974: 5966: 5961: 5956: 5955: 5954: 5953: 5950: 5946: 5942: 5938: 5934: 5930: 5926: 5925: 5922: 5921: 5917: 5916: 5912: 5905: 5901: 5897: 5892: 5890: 5886: 5882: 5877: 5876: 5875: 5874: 5871: 5867: 5865: 5859: 5847: 5843: 5838: 5836: 5826: 5825: 5824: 5823: 5818: 5813: 5809: 5808: 5796: 5791: 5787: 5786: 5785: 5780: 5776: 5772: 5769: 5764: 5761: 5760: 5759: 5758: 5754: 5750: 5745: 5716: 5713: 5709: 5707: 5700: 5697: 5696: 5695: 5692: 5691: 5686: 5678: 5677: 5676: 5672: 5668: 5663: 5659: 5655: 5654: 5653: 5650: 5649: 5644: 5637: 5636:fait accompli 5633: 5632: 5631: 5627: 5623: 5619: 5615: 5614: 5613: 5610: 5609: 5604: 5596: 5595: 5594: 5590: 5586: 5581: 5577: 5576: 5575: 5572: 5571: 5566: 5558: 5557: 5556: 5555: 5554: 5553: 5552: 5551: 5550: 5549: 5540: 5535: 5528: 5527: 5526: 5525: 5524: 5523: 5522: 5521: 5514: 5511: 5507: 5505: 5499: 5495: 5494: 5493: 5490: 5489: 5484: 5477: 5476: 5475: 5474: 5471: 5467: 5463: 5458: 5456: 5453: 5449: 5447: 5441: 5440: 5439: 5438: 5435: 5434: 5429: 5421: 5413: 5409: 5405: 5400: 5396: 5392: 5391: 5390: 5386: 5382: 5377: 5369: 5366: 5362: 5360: 5353: 5350: 5345: 5341: 5340: 5339: 5338: 5337: 5336: 5335: 5334: 5327: 5322: 5316: 5315: 5314: 5313: 5312: 5311: 5308: 5304: 5300: 5295: 5291: 5288: 5284: 5282: 5275: 5268: 5261: 5260: 5259: 5254: 5247: 5243: 5242: 5241: 5240: 5237: 5233: 5231: 5225: 5221: 5217: 5215: 5180: 5176: 5172: 5167: 5166: 5165: 5161: 5157: 5153: 5149: 5145: 5144: 5143: 5139: 5135: 5130: 5129: 5128: 5124: 5120: 5116: 5112: 5107: 5106: 5105: 5101: 5097: 5092: 5091: 5090: 5086: 5082: 5077: 5076: 5075: 5071: 5067: 5063: 5062: 5061: 5057: 5053: 5049: 5048: 5047: 5043: 5039: 5034: 5033: 5032: 5029: 5026: 5021: 5020: 5019: 5015: 5011: 5007: 5006: 5005: 5001: 4997: 4993: 4992: 4991: 4990: 4986: 4982: 4961: 4957: 4953: 4946: 4945: 4944: 4941: 4938: 4934: 4933: 4932: 4931: 4930: 4929: 4928: 4927: 4904: 4900: 4896: 4892: 4887: 4886: 4885: 4884: 4880: 4876: 4868: 4867: 4866: 4862: 4858: 4853: 4851: 4848: 4847: 4842: 4835: 4834: 4833: 4829: 4825: 4820: 4794: 4790: 4786: 4781: 4777: 4774: 4770: 4768: 4761: 4760: 4759: 4758: 4757: 4752: 4745: 4744: 4743: 4742: 4741: 4740: 4739: 4738: 4737: 4736: 4735: 4734: 4733: 4732: 4731: 4730: 4729: 4728: 4727: 4726: 4725: 4724: 4723: 4722: 4721: 4720: 4719: 4718: 4717: 4716: 4715: 4714: 4713: 4712: 4711: 4710: 4709: 4708: 4667: 4666: 4665: 4664: 4663: 4662: 4661: 4660: 4659: 4658: 4657: 4656: 4655: 4654: 4653: 4652: 4651: 4650: 4649: 4648: 4647: 4646: 4645: 4644: 4643: 4642: 4641: 4640: 4639: 4638: 4637: 4636: 4635: 4634: 4633: 4632: 4631: 4630: 4593: 4589: 4585: 4581: 4580: 4579: 4578: 4577: 4576: 4575: 4574: 4573: 4572: 4571: 4570: 4569: 4568: 4567: 4566: 4565: 4564: 4563: 4562: 4561: 4560: 4559: 4558: 4557: 4556: 4555: 4554: 4553: 4552: 4551: 4550: 4549: 4548: 4547: 4546: 4509: 4506: 4502: 4500: 4494: 4489: 4488: 4487: 4482: 4476: 4472: 4471: 4470: 4469: 4468: 4467: 4466: 4465: 4464: 4463: 4462: 4461: 4460: 4459: 4458: 4457: 4456: 4455: 4454: 4453: 4452: 4451: 4450: 4449: 4448: 4447: 4446: 4445: 4444: 4443: 4442: 4441: 4440: 4439: 4406: 4403: 4399: 4397: 4391: 4387: 4383: 4379: 4375: 4374: 4373: 4368: 4362: 4361: 4360: 4359: 4358: 4357: 4356: 4355: 4354: 4353: 4352: 4351: 4350: 4349: 4348: 4347: 4346: 4345: 4344: 4343: 4342: 4341: 4340: 4339: 4338: 4337: 4336: 4335: 4334: 4333: 4304: 4301: 4297: 4295: 4289: 4288: 4287: 4286: 4285: 4282: 4281: 4276: 4269: 4266: 4265: 4264: 4261: 4257: 4255: 4249: 4245: 4244: 4243: 4240: 4239: 4234: 4227: 4223: 4222: 4221: 4216: 4210: 4209: 4208: 4207: 4206: 4205: 4204: 4203: 4202: 4201: 4200: 4199: 4198: 4197: 4196: 4195: 4194: 4193: 4178: 4174: 4170: 4166: 4165: 4164: 4160: 4156: 4151: 4149: 4146: 4142: 4140: 4134: 4133: 4132: 4129: 4128: 4123: 4115: 4114: 4113: 4112: 4111: 4110: 4109: 4108: 4107: 4106: 4099: 4095: 4091: 4086: 4082: 4077: 4076: 4075: 4074: 4073: 4072: 4063: 4059: 4055: 4050: 4049: 4048: 4047: 4046: 4045: 4044: 4043: 4032: 4028: 4024: 4019: 4017: 4012: 4005: 4004: 4003: 4002: 4001: 4000: 3999: 3998: 3997: 3996: 3987: 3983: 3979: 3974: 3973: 3972: 3967: 3960: 3959: 3958: 3957: 3956: 3955: 3946: 3945: 3944: 3941: 3938: 3933: 3932: 3931: 3927: 3923: 3919: 3914: 3910: 3909: 3908: 3907: 3903: 3899: 3895: 3876: 3871: 3865: 3864: 3863: 3862: 3861: 3860: 3859: 3858: 3851: 3847: 3843: 3839: 3835: 3831: 3830: 3829: 3828: 3825: 3820: 3813: 3812: 3811: 3810: 3809: 3808: 3805: 3801: 3799: 3793: 3785: 3781: 3777: 3772: 3771: 3770: 3766: 3762: 3757: 3756: 3755: 3746: 3742: 3738: 3737:75.57.242.120 3733: 3732: 3731: 3727: 3723: 3718: 3717: 3716: 3712: 3708: 3707:75.57.242.120 3705: 3704: 3699: 3696: 3693: 3691: 3688: 3684: 3677: 3673: 3672: 3668: 3667: 3646: 3642: 3638: 3634: 3631: 3627: 3624: 3619: 3618: 3617: 3614: 3609: 3605: 3604: 3603: 3602: 3601: 3597: 3593: 3592:75.57.242.120 3588: 3584: 3583: 3582: 3577: 3570: 3569: 3568: 3567: 3566: 3565: 3564: 3563: 3562: 3561: 3560: 3559: 3545: 3540: 3539: 3538: 3537: 3536: 3535: 3534: 3533: 3532: 3531: 3530: 3529: 3514: 3513: 3512: 3511: 3510: 3509: 3508: 3507: 3506: 3505: 3504: 3503: 3494: 3490: 3486: 3481: 3480: 3479: 3475: 3471: 3466: 3465: 3464: 3459: 3452: 3451: 3450: 3449: 3446: 3442: 3438: 3433: 3429: 3425: 3419: 3415: 3411: 3407: 3406: 3405: 3400: 3393: 3392: 3391: 3390: 3387: 3384: 3378: 3376: 3370: 3366: 3362: 3361: 3360: 3359: 3354: 3346: 3334: 3331: 3325: 3323: 3317: 3313: 3309: 3304: 3303: 3302: 3298: 3294: 3289: 3288: 3287: 3286: 3285: 3284: 3275: 3270: 3263: 3258: 3257: 3256: 3255: 3254: 3253: 3252: 3251: 3246: 3242: 3236: 3234: 3230: 3226: 3222: 3221: 3220: 3216: 3212: 3207: 3206: 3203: 3198: 3191: 3190: 3179: 3175: 3171: 3166: 3162: 3159: 3156: 3152: 3151: 3150: 3146: 3142: 3138: 3133: 3129: 3128: 3127: 3123: 3119: 3114: 3113: 3112: 3108: 3104: 3100: 3099: 3098: 3094: 3090: 3085: 3084: 3083: 3082: 3079: 3075: 3071: 3067: 3063: 3060: 3058: 3054: 3050: 3045: 3040: 3039: 3030: 3026: 3022: 3018: 3017: 3016: 3015: 3012: 3007: 3005: 2998: 2994: 2993: 2992: 2991: 2988: 2984: 2980: 2975: 2971: 2967: 2963: 2959: 2958: 2957: 2956: 2953: 2948: 2946: 2939: 2934: 2930: 2929: 2915: 2911: 2907: 2902: 2898: 2897: 2896: 2892: 2888: 2887:75.57.242.120 2883: 2882: 2881: 2877: 2873: 2869: 2864: 2860: 2859: 2857: 2853: 2852: 2846: 2842: 2839: 2836: 2833: 2830: 2827: 2825: 2822: 2808: 2804: 2800: 2795: 2791: 2787: 2783: 2778: 2777: 2776: 2773: 2769: 2767: 2761: 2758: 2753: 2749: 2748: 2747: 2743: 2739: 2735: 2730: 2729: 2728: 2725: 2721: 2719: 2712: 2711: 2710: 2706: 2702: 2698: 2694: 2689: 2688: 2667: 2663: 2658: 2654: 2653: 2652: 2648: 2644: 2640: 2639: 2638: 2635: 2631: 2629: 2623: 2617: 2615: 2609: 2605: 2601: 2597: 2593: 2588: 2586: 2583: 2580: 2576: 2575: 2574: 2570: 2566: 2562: 2561: 2560: 2559: 2558: 2554: 2550: 2545: 2544: 2543: 2539: 2533: 2532: 2531: 2530: 2529: 2528: 2521: 2517: 2513: 2508: 2504: 2503: 2502: 2498: 2494: 2489: 2485: 2481: 2476: 2475: 2474: 2470: 2466: 2461: 2460: 2459: 2458: 2457: 2456: 2455: 2454: 2447: 2443: 2439: 2434: 2429: 2428: 2423: 2420: 2417: 2414: 2413: 2411: 2407: 2405: 2401: 2397: 2392: 2391: 2390: 2386: 2382: 2378: 2373: 2372: 2359: 2356: 2352: 2350: 2343: 2342: 2341: 2340: 2337: 2334: 2328: 2326: 2320: 2319: 2318: 2317: 2314: 2311: 2306: 2305: 2304: 2303: 2300: 2297: 2291: 2289: 2283: 2279: 2275: 2274: 2273: 2272: 2271: 2270: 2265: 2262: 2258: 2256: 2249: 2248: 2247: 2243: 2239: 2236:respect"!) -- 2234: 2229: 2228: 2211: 2207: 2203: 2198: 2197: 2196: 2192: 2158:checkuser-log 2146:browsearchive 2135: 2132: 2128: 2125: 2121: 2117: 2116: 2115: 2110: 2103: 2102: 2101: 2100: 2099: 2098: 2097: 2096: 2095: 2094: 2093: 2092: 2081: 2077: 2072: 2071: 2070: 2069: 2068: 2067: 2066: 2065: 2064: 2063: 2054: 2049: 2042: 2041: 2040: 2039: 2038: 2037: 2036: 2035: 2020: 2017: 2013: 2007: 2006:edit conflict 2002: 2001: 2000: 1999: 1998: 1997: 1996: 1995: 1994: 1993: 1992: 1991: 1990: 1989: 1978: 1974: 1970: 1965: 1961: 1958: 1954: 1952: 1946: 1942: 1938: 1937: 1936: 1933: 1927: 1925: 1918: 1917: 1916: 1912: 1908: 1904: 1899: 1898: 1897: 1893: 1889: 1884: 1883: 1882: 1878: 1874: 1873:75.57.242.120 1870: 1869: 1868: 1867: 1866: 1865: 1862: 1858: 1856: 1850: 1843: 1842: 1838: 1837: 1829: 1826: 1824: 1812: 1809:and "C" as a 1808: 1804: 1799: 1798: 1791: 1787: 1783: 1779: 1777: 1773: 1769: 1765: 1764: 1763: 1758: 1756: 1749: 1748: 1747: 1743: 1739: 1734: 1733: 1732: 1731: 1727: 1723: 1718: 1715: 1706: 1702: 1698: 1694: 1693: 1692: 1689: 1687: 1680: 1679: 1674: 1673: 1664: 1661: 1660: 1655: 1648: 1647: 1646: 1642: 1638: 1634: 1631: 1630: 1629: 1625: 1621: 1617: 1616: 1615: 1614: 1611: 1610: 1606: 1605: 1599: 1598: 1594: 1590: 1584: 1578: 1575: 1573: 1566: 1565: 1564: 1563: 1559: 1555: 1539: 1535: 1531: 1526: 1525: 1524: 1520: 1516: 1511: 1507: 1506: 1505: 1502: 1494: 1493: 1492: 1488: 1484: 1479: 1475: 1471: 1470: 1469: 1466: 1454: 1450: 1449: 1446: 1442: 1438: 1434: 1433: 1432: 1431: 1426: 1424: 1416: 1409: 1408: 1404: 1403: 1395: 1394: 1390: 1389: 1386: 1379: 1374: 1372: 1366: 1365: 1362: 1361: 1357: 1356: 1344: 1341: 1337: 1335: 1329: 1325: 1324: 1323: 1322: 1321: 1320: 1313: 1310: 1302: 1301: 1300: 1299: 1298: 1297: 1292: 1289: 1285: 1284: 1283: 1282: 1279: 1276: 1268: 1263: 1262: 1261: 1260: 1257: 1253: 1246: 1245: 1241: 1240: 1232: 1229: 1220: 1219: 1208: 1204: 1199: 1198: 1197: 1192: 1190: 1184: 1180: 1176: 1175: 1174: 1170: 1166: 1163: 1162:this decision 1159: 1155: 1149: 1146: 1143: 1142: 1141: 1138: 1134: 1130: 1126: 1125: 1124: 1121: 1117: 1113: 1110: 1106: 1104: 1098: 1097: 1096: 1093: 1089: 1087: 1084: 1078: 1076: 1070: 1062: 1059: 1055: 1053: 1047: 1045: 1038:browsearchive 1037: 1036:(and perhaps 1033: 1029: 1027: 1021: 1019: 1018: 1017: 1014: 1012: 1005: 1004: 994:administrator 987: 986: 985: 982: 978: 976: 968: 964: 962: 961: 960: 957: 955: 948: 947: 941:administrator 938: 937: 934: 933: 929: 928: 920: 919: 915: 914: 906: 905: 901: 900: 896: 889: 888: 884: 883: 869: 865: 861: 856: 855: 854: 850: 846: 841: 840: 839: 835: 831: 826: 825: 824: 820: 816: 811: 807: 806: 802: 798: 794: 790: 782: 776: 773: 769: 767: 761: 759: 755: 751: 746: 745: 744: 740: 736: 731: 730: 729: 725: 721: 716: 714: 711: 705: 703: 697: 693: 689: 688: 687: 684: 682: 675: 674: 668: 667: 664: 663: 659: 658: 652: 651: 647: 643: 632: 631: 627: 623: 618: 617: 613: 609: 608:Martin Hogbin 593: 590: 584: 582: 575: 574: 573: 569: 565: 560: 559: 558: 555: 549: 547: 541: 538: 537: 534: 533: 529: 528: 524: 515: 511: 497:browsearchive 486: 485: 484: 483: 482: 481: 477: 457:'deletedtext' 409:'deletedtext' 342: 340: 336: 325: 320: 318: 311: 310: 309: 304: 299: 295: 294: 287: 286: 285: 282: 278: 276: 270: 264: 262: 261: 254: 251: 247: 245: 238: 237: 236: 233: 227: 225: 219: 216:applied, but 215: 211: 210: 209: 206: 202: 200: 193: 192: 189: 185: 179: 176: 175: 174: 173: 170: 164: 162: 151: 148: 143: 142: 141: 136: 135: 131: 130: 122: 121: 117: 116: 110: 103: 100: 97: 95: 92: 90: 87: 84: 80: 78: 75: 73: 70: 67: 65: 62: 61: 53: 49: 45: 44: 39: 32: 31: 23: 19: 11284: 11280: 11276: 11271: 11267: 11263: 11174: 11095: 11043: 11038: 11005: 10993: 10920: 10815: 10807: 10800: 10778: 10744: 10740: 10733: 10703: 10683: 10670: 10629: 10625:encyclopedia 10612: 10611: 10606: 10603:common sense 10598: 10571:" and apply 10565: 10545: 10541: 10485: 10382: 10330: 10266: 10262: 10254: 10236: 10232: 10085: 10011: 10007: 9986: 9928: 9870: 9866: 9847: 9834: 9828: 9810: 9791: 9787: 9764: 9758: 9754: 9752: 9707: 9681: 9625: 9623: 9620: 9602: 9579: 9546: 9475: 9421: 9406: 9391: 9380: 9362: 9356: 9352: 9339: 9324: 9312: 9296: 9263: 9258: 9251: 9208: 9163: 9128: 9124: 9122: 9118: 9083: 9077:such as the 9048: 9044: 9041:transparency 9040: 9038: 9012: 9000: 8979: 8970: 8952: 8941: 8934: 8922: 8896: 8873: 8781: 8778: 8774: 8687:push to talk 8614: 8587: 8561: 8541: 8507: 8467: 8465: 8459: 8433: 8377: 8356: 8349: 8335: 8286: 8249: 8248: 8244: 8228: 8224: 8164: 8162: 8152: 8129: 8075: 8053: 8028: 8022: 8008: 7970: 7964: 7946: 7886: 7872: 7841:wp:CONSENSUS 7825: 7819: 7815: 7787: 7782: 7747: 7741: 7721: 7717: 7714: 7709: 7705: 7702: 7696: 7691: 7687: 7685: 7658: 7652: 7584: 7574: 7549: 7545: 7523: 7488: 7469: 7463: 7443: 7440: 7434: 7432: 7391: 7389: 7384: 7380: 7377: 7356: 7350: 7345: 7342: 7280: 7274: 7270: 7252: 7248: 7243: 7226: 7206: 7198: 7193: 7185: 7180: 7168: 7157: 7136: 7129: 7117: 7042: 7037: 7020: 6934: 6929: 6907: 6905: 6894: 6892: 6855: 6786: 6767: 6730: 6638: 6634: 6617: 6611: 6568:this article 6542:If only... 6508: 6454: 6390: 6384: 6378: 6374: 6371: 6366: 6362: 6357: 6354: 6348: 6345: 6339: 6336: 6329: 6275: 6259: 6241: 6206: 6200: 6183: 6182: 6178: 6170: 6168: 6161: 6147: 6057: 5991: 5959: 5936: 5932: 5928: 5918: 5863: 5855: 5834: 5803: 5800: 5794: 5783: 5762: 5741: 5705: 5699:WP:AUSC/2011 5681: 5661: 5657: 5639: 5635: 5599: 5561: 5503: 5479: 5445: 5424: 5419: 5418: 5398: 5358: 5348: 5280: 5273: 5229: 5223: 5219: 5218: 5213: 5210: 5147: 5114: 5110: 4977: 4890: 4871: 4837: 4766: 4498: 4395: 4293: 4271: 4253: 4248:WP:AUSC/2011 4229: 4225: 4138: 4118: 4084: 4080: 3917: 3912: 3890: 3797: 3790: 3753: 3686: 3682: 3680: 3607: 3586: 3431: 3427: 3374: 3364: 3347: 3343: 3321: 3315: 3311: 3307: 3261: 3136: 3131: 3065: 3061: 3043: 3003: 2996: 2965: 2944: 2937: 2932: 2819: 2785: 2765: 2759: 2756: 2751: 2733: 2717: 2692: 2627: 2595: 2591: 2487: 2483: 2479: 2432: 2421: 2415: 2348: 2324: 2287: 2281: 2277: 2254: 2232: 2011: 1950: 1944: 1940: 1923: 1854: 1846: 1839: 1823:Roger Davies 1822: 1754: 1711: 1681: 1677: 1650: 1607: 1585: 1581: 1572:Roger Davies 1571: 1550: 1509: 1477: 1452: 1422: 1412: 1405: 1391: 1370: 1358: 1333: 1251: 1249: 1242: 1188: 1182: 1178: 1132: 1128: 1102: 1074: 1051: 1041: 1025: 1006: 1002: 998:view-deleted 974: 949: 945: 930: 916: 902: 885: 785: 765: 701: 696:unreasonable 695: 691: 676: 672: 660: 638: 622:Richard Gill 619: 605: 580: 545: 539: 530: 473: 332: 316: 289: 274: 243: 223: 217: 213: 198: 160: 156: 146: 139: 133: 119: 108: 82: 47: 41: 11114:Ohconfucius 10779:HJ Mitchell 10578:Ohconfucius 9848:HJ Mitchell 9765:HJ Mitchell 9706:How about " 9687:for review. 9547:HJ Mitchell 9422:HJ Mitchell 9363:HJ Mitchell 9357:ultra vires 9297:HJ Mitchell 9276:Carl Hewitt 9211:Will Beback 9166:Will Beback 9086:Will Beback 9015:Will Beback 8982:Will Beback 8642:this clause 8588:HJ Mitchell 8521:Killiondude 8378:HJ Mitchell 8206:Ncmvocalist 8202:oversighter 7385:communicate 7344:there is a 7281:HJ Mitchell 7275:ultra vires 7227:HJ Mitchell 7159:ultra vires 7137:HJ Mitchell 7021:HJ Mitchell 6958:Ncmvocalist 6935:HJ Mitchell 6826:Ncmvocalist 6796:Ncmvocalist 6731:HJ Mitchell 6668:Newyorkbrad 6495:Ncmvocalist 6430:Newyorkbrad 6363:predictable 6242:HJ Mitchell 6041:Enric Naval 5941:Enric Naval 5806:bahamut0013 5684:Will Beback 5642:Will Beback 5602:Will Beback 5564:Will Beback 5482:Will Beback 5427:Will Beback 4840:Will Beback 4274:Will Beback 4232:Will Beback 4121:Will Beback 3375:HJ Mitchell 3369:is standing 3322:HJ Mitchell 2782:Macedonia 2 2755:given your 2325:HJ Mitchell 2288:HJ Mitchell 2238:Floquenbeam 2154:deletedtext 1924:HJ Mitchell 1805:, "B" as a 1697:Newyorkbrad 1653:Will Beback 1637:Newyorkbrad 1589:Newyorkbrad 1303:Thank you. 1075:HJ Mitchell 1034:deletedtext 845:Cube lurker 815:Cube lurker 702:HJ Mitchell 581:HJ Mitchell 546:HJ Mitchell 493:deletedtext 421:'checkuser' 373:'oversight' 292:bahamut0013 224:HJ Mitchell 161:HJ Mitchell 40:This is an 22:Noticeboard 10994:personally 10465:Carcharoth 10237:leadership 10209:SlimVirgin 10161:SlimVirgin 10104:SlimVirgin 9696:SlimVirgin 9523:SlimVirgin 9491:SlimVirgin 9281:SlimVirgin 8754:PMAnderson 8723:? Cheers, 8702:PMAnderson 8651:iridescent 8625:PMAnderson 8311:Beeblebrox 8170:Beeblebrox 7556:iridescent 7207:Sandstein 7173:discretion 7130:impression 6683:Skinwalker 6572:Skinwalker 6478:iridescent 6455:Sandstein 6391:Sandstein 6340:interested 5929:indefinite 5533:SlimVirgin 5349:discourage 5320:SlimVirgin 5252:SlimVirgin 4750:SlimVirgin 4480:SlimVirgin 4366:SlimVirgin 4214:SlimVirgin 4010:SlimVirgin 3965:SlimVirgin 3869:SlimVirgin 3818:SlimVirgin 3681:Admin has 3613:Courcelles 3575:SlimVirgin 3485:Beeblebrox 3457:SlimVirgin 3398:SlimVirgin 3352:SlimVirgin 3268:SlimVirgin 3211:Beeblebrox 3196:SlimVirgin 3068:trusted?" 3049:Beeblebrox 2863:researcher 2757:vociferous 2422:Cumulative 2416:Standalone 2310:Courcelles 2108:SlimVirgin 2047:SlimVirgin 2016:Courcelles 1738:Beeblebrox 1717:experience 1554:Carcharoth 1530:Carcharoth 1423:Sandstein 1158:this image 1150:Knowledge. 1147:and French 102:Archive 20 94:Archive 16 89:Archive 15 83:Archive 14 77:Archive 13 72:Archive 12 64:Archive 10 11306:imposed. 11239:Scott Mac 11217:Scott Mac 11194:Scott Mac 11178:MZMcBride 11137:Scott Mac 11133:last word 11026:Scott Mac 10985:Scott Mac 10945:Scott Mac 10912:Scott Mac 10872:Scott Mac 10819:articles. 10736:protected 10711:Guy Macon 10690:Guy Macon 10674:Scott Mac 10363:, and at 10255:community 10139:Scott Mac 9970:article.— 9961:Sacagawea 9937:GMT Games 9905:Scott Mac 9783:this case 9743:Scott Mac 9631:Scott Mac 9564:Scott Mac 9536:Scott Mac 9504:Scott Mac 9479:Scott Mac 9079:Brown Act 8831:traction. 8810:SirFozzie 8404:Skomorokh 8360:Thryduulf 8289:cratstats 8198:requested 8104:Skomorokh 8058:Skomorokh 7873:principle 7550:intending 7531:Skomorokh 7392:seriously 7271:Trusilver 7253:intending 7118:generally 7104:SirFozzie 7089:SirFozzie 7004:T. Canens 6977:SirFozzie 6349:obviously 6184:necessary 6110:SirFozzie 5971:Skomorokh 5960:de rigeur 5220:Question: 5115:different 5111:different 4891:community 3587:technical 3316:consensus 3141:Ironholds 3070:Ironholds 2186:checkuser 2182:oversight 2174:oversight 2130:instance. 1499:Skomorokh 1463:Skomorokh 1413:The case 1307:Skomorokh 1273:Skomorokh 1226:Skomorokh 996:(such as 990:oversight 969:oversight 965:checkuser 735:T. Canens 692:necessary 602:Thank you 501:checkuser 11109:WP:WHEEL 11101:DEFCON 5 11066:WP:POINT 10816:directly 10801:directly 10658:Dabomb87 10642:Contribs 10520:Cenarium 10435:Cenarium 10036:Cenarium 9993:Jclemens 9941:Jclemens 9886:Jclemens 9814:Jclemens 9534:rules.-- 9381:unneeded 9228:Jclemens 9129:illusion 9001:crickets 8956:contribs 8946:Casliber 8926:contribs 8916:Casliber 8713:MOS:DASH 8565:contribs 8555:Casliber 8511:contribs 8501:Casliber 8487:Looie496 8472:Looie496 8319:contribs 8269:contribs 8054:Cheers, 7971:Critical 7826:Critical 7748:Critical 7659:Critical 7575:clerical 7503:WP:FORUM 7470:Critical 7351:required 7346:profound 7163:from me. 6861:Johnuniq 6811:Johnuniq 6787:prior to 6772:Johnuniq 6618:Critical 6564:evidence 6509:Signpost 6226:Spitfire 6215:Amalthea 6189:Spitfire 5763:Seconded 5667:Jclemens 5658:practice 5622:Jclemens 5585:Jclemens 5462:Jclemens 5420:Question 5404:Jclemens 5399:somewhat 5299:Cenarium 5171:Cenarium 5134:Cenarium 5119:Jclemens 5096:Cenarium 5066:Cenarium 5038:Cenarium 5028:Fatuorum 5010:Cenarium 4981:Cenarium 4940:Fatuorum 4895:Cenarium 4857:Cenarium 4669:asinine. 4226:de facto 4169:Cenarium 4090:Jclemens 3978:Jclemens 3940:Fatuorum 3922:Jclemens 3918:register 3842:Cenarium 3776:Jclemens 3761:Cenarium 3722:Jclemens 3637:Cenarium 3470:Jclemens 3437:Jclemens 3410:Jclemens 3371:at RfA. 3306:without 3293:Cenarium 3225:Jclemens 3170:Cenarium 3158:Fatuorum 3135:trusted 3103:Cenarium 3021:Cenarium 2979:Cenarium 2906:Cenarium 2872:Cenarium 2799:Cenarium 2794:benefits 2738:Cenarium 2701:Cenarium 2693:explicit 2618:reviewer 2582:Fatuorum 2493:Jclemens 2488:endorsed 2484:has been 2465:Cenarium 2438:Jclemens 2396:Jclemens 2381:Cenarium 2278:de facto 2012:de facto 1515:Jclemens 1483:Jclemens 1474:optative 1120:Dylan620 830:Jclemens 750:Jclemens 720:Jclemens 564:Jclemens 358:'enwiki' 218:how many 20:‎ | 11266:" and " 10811:policy. 10745:doesn't 10546:suggest 10267:respect 10089:WP:RfPP 9835:Prodego 9829:tickets 9759:against 9685:WP:RfPP 9642:WP:RFPP 9399:anguard 9384:needed. 9332:anguard 9264:Prodego 8900:Jenks24 8725:Jenks24 8721:this RM 8717:WP:CFDS 8672:Jenks24 8535:WP:AC/N 8293:Dweller 8252:Phantom 8184:Jafeluv 7925:Ludwigs 7860:Ludwigs 7845:wp:NPOV 7803:Ludwigs 7727:Ludwigs 7630:Mathsci 7615:Archaeo 7450:Ludwigs 7435:entered 7410:trouble 7300:Ludwigs 7258:Ludwigs 7249:extreme 7184:should 7169:may not 7167:blocks 7075:Ludwigs 6841:Archaeo 6753:Archaeo 6654:Archaeo 6598:Archaeo 6530:Archaeo 6375:current 6310:ɐuɐʞsǝp 6282:ɐuɐʞsǝp 6076:Protonk 5771:Hasteur 5274:Oppose: 5214:forever 5156:Protonk 5025:Malleus 4974:break 2 4951:Georgia 4937:Malleus 4785:Protonk 4584:Protonk 4054:Protonk 3937:Malleus 3913:lack of 3898:Protonk 3428:winning 3312:elected 3155:Malleus 2997:against 2974:request 2933:request 2734:decreed 2579:Malleus 2282:elected 2140:and/or 2124:WP:AUSC 1129:English 147:weren't 43:archive 10796:WP:BLP 10636:EBE123 10595:WP:NOT 10542:should 10383:cannot 10288:WP:BLP 10263:buy-in 10259:WP:BLP 9601:where 9195:Risker 9125:aren't 8845:cause. 8605:Kirill 8245:before 7854:tribal 7849:wp:CIV 7847:, and 7783:choose 7779:usenet 7546:should 7507:WP:BLP 7121:share. 6906:steps 6891:from " 6591:pointy 6324:closed 6307:(ʞɿɐʇ) 6293:Risker 6279:(ʞɿɐʇ) 5913:closed 5662:policy 5618:WP:VPP 5395:WT:RFA 5081:Risker 5052:Risker 4996:Risker 4875:Risker 4824:Risker 4155:Risker 3935:that. 3894:WP:NBD 3838:WP:RFA 3623:WP:RFA 3118:Risker 3089:Risker 3066:aren't 3062:oppose 2596:should 2565:Risker 2377:WP:VPR 2233:always 2172:, and 2142:arbcom 1969:Risker 1945:should 1888:Risker 1847:Filed 1510:should 1437:Stifle 1288:Kirill 1256:Kirill 1092:Ucucha 897:closed 860:Risker 797:Risker 642:Nijdam 525:closed 505:arbcom 460:=: --> 448:=: --> 436:=: --> 424:=: --> 412:=: --> 400:=: --> 388:=: --> 376:=: --> 361:=: --> 349:=: --> 11288:case. 11262:Re: " 10808:place 10741:works 10734:fully 10627:that 10613:it is 10516:WP:PP 10241:Cla68 9929:valid 9827:OTRS 9133:Coren 9053:Coren 8942:every 8782:total 8640:then 8307:mind. 8255:Steve 8165:never 8072:… ;) 7877:Coren 7788:worse 7697:those 7688:every 7644:Coren 7444:front 7043:right 6513:Cla68 6260:could 6124:Cla68 6095:Cla68 6025:three 5832:ЄTЄRS 5816:deeds 5343:case. 4949:Sandy 3683:never 3432:can't 3044:can't 2926:break 2178:sysop 2138:audit 1941:wants 1714:prior 1326:I've 1137:Coren 1133:can't 427:array 379:array 364:array 352:array 302:deeds 267:(see 16:< 11312:talk 11297:talk 11281:stop 11230:lute 11227:Reso 11208:lute 11205:Reso 11182:talk 11151:talk 11135:. -- 11107:and 11074:talk 11052:talk 11015:talk 10974:talk 10959:talk 10934:talk 10901:talk 10886:talk 10861:talk 10846:talk 10831:talk 10752:mc10 10715:talk 10705:here 10694:talk 10685:here 10662:talk 10622:free 10607:just 10555:talk 10524:talk 10469:talk 10454:talk 10439:talk 10424:talk 10406:talk 10391:talk 10373:talk 10339:talk 10309:talk 10275:talk 10245:talk 10235:and 10178:talk 10128:talk 10055:talk 10040:talk 10021:talk 9997:talk 9976:talk 9945:talk 9935:and 9919:talk 9890:talk 9874:Talk 9818:talk 9795:Talk 9755:with 9732:talk 9717:talk 9665:talk 9650:talk 9612:talk 9591:talk 9459:talk 9444:talk 9407:Wha? 9395:ven 9340:Wha? 9328:ven 9232:talk 9216:talk 9199:talk 9171:talk 9091:talk 9045:does 9020:talk 8987:talk 8950:talk 8920:talk 8904:talk 8874:tell 8814:talk 8729:talk 8676:talk 8559:talk 8525:talk 8505:talk 8491:talk 8476:talk 8364:talk 8315:talk 8297:talk 8263:talk 8232:Talk 8220:here 8210:talk 8188:talk 8174:talk 7977:Talk 7887:want 7832:Talk 7754:Talk 7722:only 7692:have 7665:Talk 7634:talk 7619:talk 7505:and 7476:Talk 7381:talk 7108:talk 7093:talk 7008:talk 6981:talk 6962:talk 6918:talk 6904:to " 6865:talk 6845:talk 6830:talk 6815:talk 6800:talk 6776:talk 6768:stop 6757:talk 6716:talk 6687:talk 6672:talk 6658:talk 6642:Talk 6624:Talk 6602:talk 6576:talk 6534:talk 6517:talk 6499:talk 6434:talk 6297:talk 6175:here 6128:talk 6114:talk 6099:talk 6080:talk 6045:talk 6033:five 6029:four 5945:talk 5935:and 5931:and 5900:talk 5885:talk 5864:xeno 5842:TALK 5795:very 5775:talk 5753:talk 5706:xeno 5689:talk 5671:talk 5647:talk 5626:talk 5607:talk 5589:talk 5569:talk 5504:xeno 5487:talk 5466:talk 5446:xeno 5432:talk 5408:talk 5385:talk 5359:xeno 5303:talk 5281:xeno 5267:CENT 5244:The 5230:xeno 5175:talk 5160:talk 5138:talk 5123:talk 5100:talk 5085:talk 5070:talk 5056:talk 5042:talk 5014:talk 5000:talk 4985:talk 4956:Talk 4899:talk 4879:talk 4861:talk 4845:talk 4828:talk 4789:talk 4767:xeno 4588:talk 4499:xeno 4495:. – 4396:xeno 4388:and 4294:xeno 4279:talk 4254:xeno 4237:talk 4224:The 4173:talk 4159:talk 4139:xeno 4126:talk 4094:talk 4058:talk 4027:talk 3982:talk 3926:talk 3902:talk 3846:talk 3834:here 3798:xeno 3780:talk 3765:talk 3741:talk 3726:talk 3711:talk 3641:talk 3596:talk 3489:talk 3474:talk 3441:talk 3414:talk 3297:talk 3229:talk 3215:talk 3174:talk 3145:talk 3132:that 3122:talk 3107:talk 3093:talk 3074:talk 3053:talk 3025:talk 2983:talk 2910:talk 2899:See 2891:talk 2876:talk 2861:The 2803:talk 2766:xeno 2752:want 2742:talk 2718:xeno 2705:talk 2647:talk 2628:xeno 2616:The 2604:talk 2592:WILL 2569:talk 2553:talk 2516:talk 2507:this 2497:talk 2469:talk 2442:talk 2433:must 2400:talk 2385:talk 2349:xeno 2255:xeno 2242:talk 2206:talk 2184:and 1973:talk 1951:xeno 1911:talk 1892:talk 1877:talk 1855:xeno 1786:talk 1772:talk 1742:talk 1726:talk 1701:talk 1685:Talk 1658:talk 1641:talk 1624:talk 1593:talk 1558:talk 1534:talk 1519:talk 1487:talk 1478:like 1457:beat 1441:talk 1334:xeno 1160:and 1103:xeno 1052:xeno 1032:and 1010:Talk 975:xeno 967:and 953:Talk 864:talk 849:talk 834:talk 819:talk 801:talk 791:and 766:xeno 754:talk 739:talk 724:talk 680:Talk 646:talk 626:talk 612:talk 568:talk 540:More 503:and 495:and 463:true 451:true 439:true 415:true 403:true 391:true 275:xeno 244:xeno 199:xeno 11293:Kww 11285:for 11044:you 10921:was 10702:Or 10639:~~ 10616:. 10599:own 10486:not 10402:Kww 10331:and 10174:Kww 10124:Kww 10017:Kww 10012:any 10008:all 9972:Kww 9915:Kww 9903:.-- 9713:Kww 9646:Kww 9603:any 9587:Kww 9455:Wnt 9049:act 8666:to 8615:Is 8542:AGK 8434:AGK 8130:AGK 8076:AGK 7585:AGK 7199:you 7186:not 7181:all 6379:new 6358:has 6058:AGK 6037:six 6021:two 6017:one 5992:AGK 5860:. – 4081:for 3687:now 3608:log 3365:has 3363:He 3308:any 3262:and 3004:AGK 2966:has 2945:AGK 2938:not 2697:say 2505:Is 2480:was 2156:, 2148:, 1851:. – 1755:AGK 1371:AGK 1252:not 1189:AGK 1179:SOP 1028:), 988:Is 317:AGK 214:who 11314:) 11299:) 11184:) 11153:) 11076:) 11054:) 11039:do 11017:) 10976:) 10961:) 10936:) 10903:) 10888:) 10863:) 10848:) 10833:) 10783:| 10717:) 10709:. 10696:) 10688:. 10664:) 10557:) 10526:) 10471:) 10456:) 10441:) 10426:) 10408:) 10393:) 10375:) 10341:) 10311:) 10277:) 10269:. 10247:) 10180:) 10130:) 10057:) 10042:) 10023:) 9999:) 9991:. 9978:) 9947:) 9921:) 9892:) 9867:NW 9852:| 9820:) 9788:NW 9785:? 9769:| 9734:) 9719:) 9667:) 9652:) 9614:) 9593:) 9551:| 9461:) 9446:) 9426:| 9367:| 9359:. 9301:| 9234:) 9201:) 9119:do 8958:) 8928:) 8906:) 8886:— 8816:) 8808:. 8795:— 8731:) 8689:) 8678:) 8592:| 8567:) 8527:) 8513:) 8493:) 8478:) 8382:| 8366:) 8321:) 8317:• 8309:-- 8299:) 8272:\ 8225:NW 8212:) 8204:. 8190:) 8176:) 7975:__ 7965:BE 7922:-- 7843:, 7830:__ 7820:BE 7800:-- 7752:__ 7742:BE 7663:__ 7653:BE 7636:) 7621:) 7474:__ 7464:BE 7297:-- 7285:| 7231:| 7194:we 7141:| 7110:) 7095:) 7025:| 7010:) 6983:) 6964:) 6939:| 6920:) 6912:" 6895:it 6867:) 6856:no 6847:) 6832:) 6817:) 6802:) 6778:) 6759:) 6735:| 6718:) 6689:) 6674:) 6660:) 6635:NW 6622:__ 6612:BE 6604:) 6578:) 6536:) 6528:? 6519:) 6501:) 6436:) 6299:) 6246:| 6130:) 6116:) 6101:) 6082:) 6047:) 6035:, 6031:, 6027:, 6023:, 6019:, 5967:. 5947:) 5887:) 5777:) 5755:) 5673:) 5628:) 5591:) 5468:) 5410:) 5387:) 5305:) 5270:}} 5264:{{ 5177:) 5162:) 5154:. 5140:) 5125:) 5102:) 5087:) 5072:) 5058:) 5044:) 5016:) 5002:) 4987:) 4958:) 4901:) 4881:) 4863:) 4830:) 4791:) 4590:) 4175:) 4161:) 4096:) 4085:by 4060:) 4029:) 3984:) 3928:) 3904:) 3848:) 3782:) 3767:) 3743:) 3728:) 3713:) 3643:) 3598:) 3491:) 3476:) 3443:) 3416:) 3379:| 3326:| 3299:) 3231:) 3217:) 3176:) 3147:) 3124:) 3109:) 3095:) 3076:) 3055:) 3027:) 2985:) 2912:) 2893:) 2878:) 2858:) 2805:) 2744:) 2707:) 2649:) 2606:) 2571:) 2555:) 2518:) 2499:) 2471:) 2444:) 2402:) 2387:) 2329:| 2292:| 2244:) 2208:) 2180:, 2168:, 2164:, 2160:, 2152:, 1975:) 1928:| 1913:) 1894:) 1879:) 1813:). 1788:) 1774:) 1744:) 1728:) 1703:) 1678:NW 1643:) 1626:) 1595:) 1560:) 1536:) 1521:) 1489:) 1443:) 1079:| 1003:NW 946:NW 866:) 851:) 836:) 821:) 803:) 795:. 756:) 741:) 726:) 706:| 673:NW 648:) 628:) 614:) 585:| 570:) 550:| 507:. 491:, 469:), 466:), 418:), 370:.. 228:| 165:| 98:→ 68:← 11310:( 11295:( 11180:( 11149:( 11094:" 11072:( 11050:( 11013:( 10972:( 10957:( 10932:( 10899:( 10884:( 10859:( 10844:( 10829:( 10767:) 10764:c 10761:/ 10758:t 10755:( 10749:— 10713:( 10707:. 10692:( 10660:( 10553:( 10522:( 10467:( 10452:( 10437:( 10422:( 10404:( 10389:( 10371:( 10337:( 10307:( 10273:( 10243:( 10176:( 10126:( 10053:( 10038:( 10019:( 9995:( 9974:( 9943:( 9917:( 9888:( 9877:) 9871:( 9816:( 9798:) 9792:( 9730:( 9715:( 9663:( 9648:( 9610:( 9589:( 9457:( 9442:( 9397:M 9393:S 9330:M 9326:S 9318:) 9314:( 9230:( 9197:( 8953:· 8948:( 8923:· 8918:( 8902:( 8884:C 8881:F 8878:W 8812:( 8793:C 8790:F 8787:W 8727:( 8685:( 8674:( 8562:· 8557:( 8523:( 8508:· 8503:( 8489:( 8474:( 8362:( 8313:( 8295:( 8266:| 8260:/ 8235:) 8229:( 8208:( 8186:( 8172:( 8045:) 7969:— 7967:— 7928:2 7863:2 7824:— 7822:— 7806:2 7746:— 7744:— 7730:2 7657:— 7655:— 7632:( 7617:( 7468:— 7466:— 7453:2 7303:2 7261:2 7106:( 7091:( 7078:2 7006:( 6979:( 6960:( 6916:( 6908:I 6899:" 6863:( 6843:( 6828:( 6813:( 6798:( 6774:( 6755:( 6714:( 6685:( 6670:( 6656:( 6645:) 6639:( 6616:— 6614:— 6600:( 6574:( 6532:( 6515:( 6497:( 6432:( 6295:( 6197:" 6126:( 6112:( 6097:( 6078:( 6043:( 5943:( 5898:( 5883:( 5840:► 5837:V 5835:J 5830:P 5773:( 5751:( 5669:( 5624:( 5587:( 5464:( 5406:( 5383:( 5355:– 5301:( 5277:– 5173:( 5158:( 5146:" 5136:( 5121:( 5098:( 5083:( 5068:( 5054:( 5040:( 5012:( 4998:( 4983:( 4954:( 4897:( 4877:( 4859:( 4826:( 4787:( 4763:– 4586:( 4171:( 4157:( 4092:( 4056:( 4025:( 3980:( 3924:( 3900:( 3844:( 3778:( 3763:( 3739:( 3724:( 3709:( 3639:( 3594:( 3487:( 3472:( 3439:( 3412:( 3295:( 3227:( 3213:( 3172:( 3143:( 3120:( 3105:( 3091:( 3072:( 3051:( 3023:( 2981:( 2908:( 2889:( 2874:( 2801:( 2740:( 2703:( 2645:( 2643:B 2602:( 2600:B 2567:( 2551:( 2549:B 2514:( 2512:B 2495:( 2467:( 2440:( 2398:( 2383:( 2345:– 2240:( 2204:( 2008:) 2004:( 1971:( 1909:( 1907:B 1890:( 1875:( 1784:( 1770:( 1740:( 1724:( 1699:( 1688:) 1682:( 1639:( 1622:( 1591:( 1556:( 1532:( 1517:( 1485:( 1453:x 1439:( 1046:) 1042:( 1013:) 1007:( 956:) 950:( 862:( 847:( 832:( 817:( 799:( 752:( 737:( 722:( 683:) 677:( 644:( 624:( 610:( 566:( 454:, 442:, 430:( 406:, 394:, 382:( 367:( 355:( 240:– 157:— 54:.

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

Knowledge

talk:Arbitration Committee/Noticeboard/Archive 14 - Knowledge

Index