Knowledge (XXG):Requests for arbitration/Date delinking

2291:- I have participated in date-linking discussions previously, and while I don't hold a very strong opinion on the central issues, and my opinion has shifted over time (to the stage where I support most, but not all, date delinking), I'm involved enough and have discussed this with several of the editors concerned (at least four of the parties), to the extent that I don't feel I could impartially judge the behaviour issues here. I do agree with those who have stated that this case should most emphatically be about the behaviour here, and not the content. Incivility, unnecessarily strong criticism, tendentiousness, inability to compromise or see the other side's arguments, misreading of consensus (possibly in good faith, or being blinded by bias), edit warring, attacks against bot operators, impatient and unhelpful responses by bot operators, misguided application of the manual of style, and other issues, are among those that have taken place here (just a selection of the behaviour on both sides). I also echo the comments by those who point out that date delinking is not really the most urgent matter to be resolved here. 1764:

either full dates or bare years or the occasional more exotic combination. That's about 7000 articles delinked. If delinking were seriously disputed – by more than just Locke Cole and a few vocal others - you’d expect me to get a lot of complaints. How many have I had? Seven. In three cases I explained about the MoS and my argument was accepted. In two cases the editors wouldn’t accept that, so I just left them to it. And in two cases editors were so uncivil that no attempt at reasoned argument could have made any difference. This gives the lie to Locke Cole's suggestion that the changes are being steamrollered in. It's just that he doesn’t agree, plain and simple, and he won’t concede that the argument is lost. The community accepts the changes. The evidence is clear.

1756:, then even when he’d lost the RFCs – one of them specifically on the issue of using automated processes to implement the MoS - he’s still trying to say that there’s isn’t consensus to bring the encyclopaedia into line with its own Manual of Style, and also saying that MOSNUM is only a guideline and he doesn’t have to obey it anyway. This is someone who just can’t accepts that things aren’t going his way and is disrupting everyone else to make his point. The claim of incivility is just another spurious attempt to keep the dispute going – as Tony1 said "there have been instances of frayed tempers on both sides" - but none of it has resulted in anything that the ArbCom need be spending its time looking at. 943:

resolve them" (and related concerns by Arb. Vassyana) are laudable, but my experience in that forum suggests that MOSNUM talk will just have to wade through its difficulties as best it can, just as always: MOSNUM, indeed, deals with the most contentious issues of all style guides. I believe that any threat to the "stability to articles" (a concern for Arb. FloNight) has been overstated. Colonies Chris provides statistical and anecdotal evidence of a quite different situation. In summary, I think we're over the worst of it, and things go on despite the tension surrounding the issue (notably, in the past few weeks Locke Cole and Tennis expert have been very supportive of an unrelated initiative of mine).

1242:

the heated MOSNUM discussions, and most of the admins at MOSNUM were somehow involved in the debate and could not provide a neutral third opinion. I will note that those who have been complaining about the date delinking are largely a small minority group. In most cases, when users have asked questions about the delinking activities, they are given a polite, easy-to-understand answer, which is usually accepted without much complaint. The fact that there has not been a flurry of new complaints demonstrates that there is significant consensus for the date delinkings to occur. Therefore, I ask that the Arbitration Commitee decline this case and allow other forms of dispute resolution, such as

1760:

date links in articles, and you have about half a million articles still with some form of date linking, at a conservative estimate. What the objectors seem to forget when they object to automated delinking is that those links weren’t made by people carefully considering the merits of whether a particular date should be linked. They were made because that’s what the MoS recommended (in the case of autoformatting) or because the syntax of autoformatting is so unintuitive that the average editor tended to just link all bare years and other date fragments and time periods willy-nilly.

1898:, unless (in the words of FloNight) there is good evidence of a clear ongoing consensus building process that will end with a well-accepted solution. I think there are clear behavioral issues for ArbCom to examine here. The use of the consensus-building process and interpretation of its resolutions seems to be a fundamental issue here, along with related behavioral concerns. There is also a broad range of alleged behavioral issues surrounding these cirucmstances, including but not limited to (semi)automated tool abuse, incivility, OWNership, forum shopping and system gaming. 879:(2) If there are residual concerns about the claims of "incivility and poor behaviour on the part of the proponents of this change", I believe that a thorough examination of behaviour would conclude that there have been instances of frayed tempers on both sides, but that given the length of the discourse (some six months), this is not out of the ordinary and that other forums have been and could still be used to gain resolution. I do not see incivility as a major ongoing problem, and feel that in this context it has been overstated. 1449:, the process he believed was broken is only appears so because a handful of individuals, led by the plaintiff, have demonstrated utter disrespect for the consensus, using all means at their disposal to repeatedly "reinterpret" the declared will of the people. I have full confidence in ArbCom that this subversion not be allowed to pass, for it will surely be a day for the annals of WP as the beginning of the end - one of its fundamental pillars, the consensus model will be irreparably shattered, to be replaced by 816:

lost on the proponents of the change either: I get the general impression they feel empowered in these discussions to dismiss compromises and alternatives out of hand (yet another reason for the mass delinkings to stop). Hence my motion request. The community should be able to handle this, but not while editors are pushing their preferred version of things on the rest of us. Worth noting: there are 6,884,804 articles on Knowledge (XXG), I really doubt all of them have been delinked already. —

1777:

the MoS, where were the other tennis editors standing up to support this supposed local consensus? There were none - because it existed only in Tennis Expert's mind, as a justification for his insistence that everyone do things his way. Like it or not, hardly anyone has complained – see the facts in my statement above. And I have not imtimidated anyone, nor steam-rollered, edit warred, nor made aggressive posts and edit summaries. The evidence is open to anyone to examine.

1111:, respectively). Both are experienced and influential editors with a long track record on Knowledge (XXG). The only block on Tony’s record was quickly withdrawn as being done in error. These sort of track records just don’t happen by accident; they happen only by an editor exhibiting a consistent pattern of being logical and reasonable and by abiding by Knowledge (XXG)’s rules—even when under duress when acting in a leadership capacity, as Tony often finds himself in. 1297:, parry and recoil, but find myself no match for the plaintiff's aggressive and unrelenting onslaught. The plaintiff has consistently made it clear that he considers any form of delinking disruptive behaviour. This uncompromising stance makes for uneasy discussion. Things have gone so far and gone on for so long that I simply no longer believe that he takes no pleasure in seeing me blocked. 882:(3) I want to put on record that in the view of many users, the trialling, implementation and refinement of automated and semi-automated means for assisting editors to comply with the style guides WRT the removal of date-autoformatting, and the cleaning up the rather messy state of underlying date formats, have been characterised by politeness, cooperation and sensitivity to critical feedback. 763:") while objections and disputes remain unresolved or unanswered. Further than that, there remains the disparaging behavior of those who simply wish to ignore objections ("this is a waste of time", "don't you have something better to do", "this is only being continued by a 'gang of five'", etc). Remarks which are unhelpful at reaching a consensus, I might add. — 962:. Although using this as a test-case for establishing/confirming/changing the rules for bot usage might be possible, the technical complexities needed to underpin a judgement make me quiver. If this is to be part or all of the scope of a case, I submit that the scope be very tightly defined from the start (as suggested by Arb. Vandenberg). Please note that 2362:

the performance of administrative tasks. Editors making any or all of these types of contributions are welcome. The project and our progress toward our goals are diminished if we drive away or demoralize a good-faith editor who contributes or has the potential to contribute, while complying with Knowledge (XXG) policies, in any or all of these areas.

2422:

of the behavior of those they are in disputes with. Inappropriate behavior by other editors does not legitimize one's own misconduct, though it may be considered as a mitigating factor in some circumstances. Moreover, users who have been justifiably criticized or formally sanctioned for improper conduct are expected to avoid repeating that conduct.

6154: 1289:. There has been a micron-thin veneer of civility (usually in terse language wrapped in brown paper) but the underlying incivility is undeniable. You may not find extreme civility from me nor from Greg, but our wrapping is transparent film, so what you see is what you get. The plaintiff has had a strong influence on how this debate has taken on a 6729:(2) All remedies in the decision providing that a specified user is "prohibited from reversion of changes which are principally stylistic, except where all style elements are prescribed in the applicable style guideline" are modified by replacing these words with the words "prohibited from reverting the linking or unlinking of dates"; 6732:(3) All editors whose restrictions are being narrowed are reminded to abide by all applicable policies and guidelines in their editing, so that further controversies such as the one that led to the arbitration case will not arise, and any disagreements concerning style guidelines can be addressed in a civil and efficient fashion; 696:

been asked to stop because their changes are disputed and do not have consensus. We've held numerous discussions, conducted a month long RFC (which involved the community and was listed in the watchlist) and have no consensus for these mass automated changes as they're being enacted. In a prior ArbCom decision it was stated:

714:

attacks, and so forth) of those involved can be looked at. I understand the committee doesn't take up content disputes, but I fear this situation will not end without binding arbitration as those involved seem unwilling to consider compromises which don't involve automated date delinking. Thank you for your consideration. —

6735:(4) Any party who believes the Date delinking decision should be further amended may file a new request for amendment. To allow time to evaluate the effect of the amendments already made, editors are asked to wait at least 30 days after this motion is passed before submitting any further amendment requests. 839:

effectively present us with a situation that's already to their liking. And the thing to keep in mind is that Date delinker isn't the only one performing these operations. It wouldn't surprise me if there were already 50,000 edits of this type (combined amongst all automated and semi-automated accounts). —

6254:

3.1) If the Manual of style has not stabilised within three months after the close of the case, the committee will open a review of the conduct of the parties engaged in this battle and hand out permanent MOS bans to any parties who have actively prevented the manual of style stabilising on a version

6220:

While asking the enforcing administrator and seeking reviews at AN or AE are not mandatory prior to seeking a decision from the committee, once the committee has reviewed a request, further substantive review at any forum is barred. The sole exception is editors under an active sanction who may still

6187:

Administrators are free to modify sanctions placed by former administrators – that is, editors who do not have the administrator permission enabled (due to a temporary or permanent relinquishment or desysop) – without regard to the requirements of this section. If an administrator modifies a sanction

3188:

by several administrators and arbitrators for running fast automated date delinking processes. At the time he stopped editing, there was apparently a great degree of controversy at his talk page and the block lengths were a week to a month in length. Also, he submitted several rejected date-related

2697:

19) System administrators are responsible for the MediaWiki software configuration of the projects run by the Wikimedia Foundation, such as English Knowledge (XXG). They make changes to configuration based on a mix of Wikimedia Foundation, technical and project considerations. While their decisions

1776:

that there is a local consensus (on tennis-related articles) that overrides the MoS needs to be exposed for the self-serving nonsense that it is. When various dates in tennis-related articles were being unlinked, in line with the MoS, and Tennis Expert was reverting those changes, in contravention of

1763:

Here are some facts; most of what I do on WP is gnoming. Since the MoS was changed to deprecate autoformatting, I've been routinely unlinking dates in the course of my other edits. I estimate that I've edited about 10,000 articles, and roughly 70% of those edits involved some sort of date delinking –

1751:

First of all, this whole case is a blatant example of forum shopping. Locke Cole has opposed these changes tooth and nail from the very start – first he lost the argument on the changes to MOSNUM, then he tried to claim that delinking was disruptive even though it was line with MOSNUM; then he tried

1363:

which the plaintiff is attempting to put through in the latter. While there may be some limited discussion and agreement to merge the two, the timing of that action, together with the nature of amendments which have been made by the plaintiff (thus opening up another front in this dispute) while this

838:

The fait accompli is from the sheer magnitude of the edits being performed. As John Vandenberg notes, Date delinker has performed nearly 9,000 edits of this variety. Unless those of us on the other side choose to engage in identical behavior (using a bot or semi-automatic script to relink dates) they

2681:

are trusted members of the community and are expected to follow Knowledge (XXG) policies. They are expected to pursue their duties to the best of their abilities. Occasional mistakes are entirely compatible with this; members are not expected to be perfect. However, consistently or egregiously poor

2508:

8) When either of two styles are acceptable it is inappropriate for a Knowledge (XXG) editor to change from one style to another unless there is some substantial reason for the change. For example, with respect to British spelling as opposed to American spelling it would be acceptable to change from

2361:

2) Contributors to Knowledge (XXG) may benefit the project by participating in a variety of ways. Good-faith participation is welcome whether it comes in the form of editorial contributions, image contributions, wiki-gnoming, bot and script writing and operation, policy design and implementation, or

1759:

The claim that ‘the bot has unlinked everything already’ is utter nonsense. I’ve just picked a random date (September 12) and checked what links to it – there are about 7000 links, even disregarding links to calendar-related articles. Multiply that up by 365, divide by, say, 5, to allow for multiple

1679:

Please note that I am not asking the ArbCom to rule on the content issue of whether dates should be linked; I am perfectly aware that that is beyond their remit. Whatever the result is for that in the future, all parties should be expected to abide by it and discuss it in a fair and sanguine manner,

1085:

Clearly, with 6,884,804 articles on en.Knowledge (XXG), there are probably over a million date links to be fixed, the vast majority of which take readers to unrelated historical trivia that has little if any relevance to the topic of the article containing the links. This is far too many to manually

1032:

techniques to let readers know of the availability of these types of history-related articles. Furthermore, this method fully discloses the precise nature of the article a reader would be taken to if they clicked on the link. Since Tony, I, and others found ourselves often repeating the same message

954:

interpretation of the detailed RfCs at MOSNUM, which were not framed in a way that was ever going to produce clear results, is not something I'd wish on the arbitrators; in addition, those RfCs would need to be interpreted in the context of a huge amount of other information—they are only the tip of

942:

in this matter, which has not been out of the ordinary—indeed, the matter has been characterised by relative civility, even though the filer has concentrated on making a case that rudeness and chaos abound. Arb. Rlevse's concerns for "more input on behavioral issues related to MOSNUM and attempts to

700:

Editors who are collectively or individually making large numbers of similar edits, and are apprised that those edits are controversial or disputed, are expected to attempt to resolve the dispute through discussion. It is inappropriate to use repetition or volume in order to present opponents with a

695:

This has been an ongoing content dispute for the past six months that has repeatedly degenerated into incivility and poor behavior on the part of the proponents of this change. At the moment we have editors using a single script to mass delink dates (collectively over thousands of articles) who have

2909:

3.3.1) All three of the RfCs regarding date links have been plagued by disputes regarding wording, presentation, claims of bias, and related issues. These disputes continued through the drafting and comment phases, as well as persisting after RfC closures. Additionally, there are varied and sharply

2661:

16) Like administrators and other editors in positions of trust, bot operators have a heightened responsibility to the community. Bot operators are expected to respond reasonably to questions or concerns about the operation of their bot. An editor who (even in good faith) misuses automated editing

2421:

4) Perfection is not expected from editors, it being understood that everyone will occasionally make mistakes or misjudgments. However, an overall record of compliance with site policies and norms is expected, especially from regular contributors. Editors are expected to adhere to policy regardless

2311:

1.1) Until this case is decided or otherwise directed by the Arbitration Committee, all editors are instructed not to engage in any program of mass linking or delinking of dates in existing articles, including but not limited to through the use of bots, scripts, tools, or otherwise. This injunction

1929:

have been brewing for roughly two years and I keep seeing many of the same users involved in the disputes. The issue of whether to link or not link dates is clearly a content issue outside of arbcom's purview. I'd like to see more input on behavioral issues related to MOSNUM and attempts to resolve

1241:

of the debate have remained civil most of the time. Lastly, I do not believe that all other courses of dispute resolution have been used. Other than the Date Linking RFCs, there has been little interaction from editors, admin or not, to give their input. The ANI threads were usually importations of

1144:

the sort of tendentious editing that would account for such a block record. He cloaks uncivil, disruptive editing behind a veneer of civil words, much the same way a mugger might take care to not end his sentences with a preposition as he courteously relieves you of your wallet with a knife. I have

1002:

I really do want to avoid having my activities on one of my hobbies—Knowledge (XXG)—defined by the whims of others. So I expect (hope) to have a minimum of participation here. I just don’t want to be dragged down in the mud with unproductive bickering over something like how to format a date in an

815:

from the table. This situation right now makes it impossible (or really difficult) to discuss the issue when a sense of inevitability pervades all discussions ("we're doing this, so talk all you want, but while you were typing that up, I delinked another hundred articles"). This inevitability isn't

2645:

15) Editors who collectively or individually make large numbers of similar edits, and who are apprised that those edits are controversial or disputed, are expected to attempt to resolve the dispute through discussion. It is inappropriate to use repetition or volume to present opponents with a fait

2488:

7.1) Users confronted with inappropriate behavior should not respond in kind, or engage in sustained editorial conflict or unbridled criticism across different forums; inappropriate behavior by others does not legitimize one's own. Editors who have genuine grievances against others are expected to

1645:

that I shouldn't "be surprised if you see a rash of editors suppressing a discussion that has been brought up many times", and adding that "It is time to move on". In other words, if you raise the issue you'll be told to shut up, so go away. I do not believe that it is appropriate behavior for any

1308:

is "only a guideline" implying that compliance therewith is not mandatory. He has been all over town on his complains in attempts to stymie all efforts to clear the detritus, which a very significant number of users have expressed strongly wanting done away with within the project. I have stripped

713:

All of the editors involved in this dispute are aware of this decision (they were warned about it months ago), but they continue to operate under the assumption that their actions have consensus. I urge the committee to accept this case so the behavior (incivility, edit warring, stalking, personal

2761:

Policies, procedures and the manual of style may govern how and when the software may be used, however decisions to deprecate or disable software features are best left in the hands of the technical staff. Likewise, decisions which will involve large scale changes (e.g. hundreds of thousands of

2574:

is a set of guidelines governing appropriate editing on Knowledge (XXG). The Manual is prescriptive in areas that enjoy broad consensus; where there is no such consensus, the available options are described, but no prescriptive guidance is provided. Editors are expected to follow the Manual of

2377:

3) Knowledge (XXG) users are expected to behave reasonably, calmly, and courteously in their interactions with other users; to approach even difficult situations in a dignified fashion and with a constructive and collaborative outlook; and to avoid acting in a manner that brings the project into

1326:

To conclude, The way forward? I have already moved on, and am now concentrating my MOSNUM efforts to unifying date formats within articles. I am glad this ArbCom request is the last resort, because I would dearly like to see an end to this matter, which has been the most gigantesque distraction.

972:

might be an option. While focusing on small intervals of time or collating diffs over a long interval (as above) might give the impression that there are "no visible signs of abating" (Arb. Coren), the noise created by the few is likely to recede, given the strong support in the community for a

6228:

All actions designated as arbitration enforcement actions, including those alleged to be out of process or against existing policy, must first be appealed following arbitration enforcement procedures to establish if such enforcement is inappropriate before the action may be reversed or formally

6224:

These provisions apply only to contentious topics placed by administrators and to blocks placed by administrators to enforce arbitration case decisions. They do not apply to sanctions directly authorised by the committee, and enacted either by arbitrators or by arbitration clerks, or to special

2019:

Comment Because of the potential for a dispute on this topic to cause instability to a large amount of articles and the length of the dispute, I'm willing to take this case sooner rather than late, unless there if good evidence of clear ongoing consensus building process that will end with well

758:

I do not believe Mediation or a Third Opinion would help here. We've already solicited the entire community via a watchlist notice, and a slightly uninvolved administrator (Masem) has tried multiple times to try and mediate the issue. To no avail, it seems. The core behavioral issue here is the

7044:

Remedies 16 and 18 (as amended) are terminated, effective immediately. Ohconfucius is reminded that this subject remains within the jurisdiction of the Arbitration Committee, and that he is expected to abide by all applicable policies and guidelines, especially those concerning the editing and

2224:

Quick reply to two comments (by Locke Cole and Protonk), I certainly agree that making superficial editorial changes along with delinking dates is substantially the same as just delinking them; I was thinking really of manual routine page maintenance rather than automated mass changes. I would

1010:. As you can see, right at the beginning is a date, 7 April 1795, that is unlinked. Further, since the SI’s kilogram is not closely associated with the United States, I elected to consistently use the international-style date format throughout the article. Note also the two date-related links, 2757:

21) The MediaWiki software used on the Wikimedia projects, and configuration of that software, is the responsibility of the developers and system administrators. In the same way that system administrators are the decision makers to enable new functionality, deprecation or removal of MediaWiki

2625:

are also computer algorithms utilized to automate or semi-automate certain types of editing. These tools are extremely valuable for the purpose of facilitating the making of multiple edits that would be unduly time-consuming or tedious for a human editor to perform manually. Approval from the

872:

That the basis of the application is a content dispute is reinforced by this subsequent statement by the filing party: "I understand the committee doesn't take up content disputes, but I fear this situation will not end without binding arbitration as those involved seem unwilling to consider

2955:

Due to the English Knowledge (XXG) Date debate, and the complexity of the problem, the bug was conflated with many issues, suggestions and feature requests. A number of these suggestions were built by developer Bill Clark between September 2008 and November 2008. During the course of this

6726:(1) All remedies in the decision providing that a specified user is topic-banned from editing or discussing "style and editing guidelines" (or similar wording) are modified by replacing these words with the words "style and editing guidelines relating to the linking or unlinking of dates"; 2437:

5) Edit-warring is harmful. When disagreements arise, users are expected to discuss their differences rationally rather than reverting ad infinitum. Revert rules should not be construed as an entitlement or inalienable right to revert, nor do they endorse reverts as an editing technique.

1098:

Another important factor to consider is which camp of editors is best trying to adhere to the community consensus on this matter. How is it that we are all here at ArbCom after a month‑long series of RfCs that enjoyed wide input? I am not seeing any pattern of behavioral problems with the

1280:

and I have locked horns over the issue almost continually from September 2008 onwards. For the record, said editor is one of approximately five individuals totally opposed to removal of Date-autoformatting, and must be credited for having raised the issue most vocally in a manner akin to

5845:

Locke Cole is reminded to abide by all applicable policies and guidelines in his editing, so that further controversies such as the one that led to the arbitration case will not arise, and any disagreements concerning style guidelines can be addressed in a civil and efficient

2698:

may affect the English Knowledge (XXG), those decisions are binding on the projects and beyond the jurisdiction of the English Knowledge (XXG) community and its Arbitration Committee. The local community may, of course, challenge these decisions at meta forums, such as

2053:; I'm inclined to accept a case when the topic focus causes large, repeated threads on noticeboards with no visible signs of abating. This invariably means there is a behavioral problem, even if the problem is the repeated call to arms rather than the issue itself. — 182:

Please do not edit this page directly unless you are either 1) an Arbitrator, 2) an Arbitration Clerk, or 3) adding yourself to this case. Statements on this page are original comments provided when the Committee was initially requested to Arbitrate this page (at

889:

in the first RfC cited above provided strong consensus that the use of an automatic or semi-automatic process to bring article text into compliance with any particular guideline in the Manual of Style (dates and numbers) requires no separate or prior consensus.

3245:

The request was denied on October 22, 2008 by BAG member Mr.Z-man, with BAG members Bjweeks and Martinp23 also indicating that it was inappropriate for a bot to be undertaking delinking based on what they considered to be an insufficient level of consensus.

2036:. Not to make a content ruling but to assist in developing a process that will result in stability to articles and address any user conduct issues that may be causing local article discussion or global topic discussions to stall without forming consensus. 6121:

Appeals may be made only by the editor under sanction and only for a currently active sanction. Requests for modification of page restrictions may be made by any editor. The process has three possible stages (see "Important notes" below). The editor may:

6188:

placed by a former administrator, the administrator who made the modification becomes the "enforcing administrator". If a former administrator regains the tools, the provisions of this section again apply to their unmodified enforcement actions.

2826: 706: 2758:

functionality is a technical decision, and implementation of that decision may have technical implications that need to be considered. The project community should engage the technical team in decisions which relate to use of the software.

1313:

torrent of abuse. Of course Locke was well within his rights to demand clarification on the matter at RfC, but his adamant refusal to take 'no' for an answer, which ordinarily might do him credit for tenacity, can also be viewed as having a

1090:

be linked and which are accidentally swept up by bot activity can easily be hand-restored. Furthermore, as I have illustrated above, there are alternative, often superior ways to let readers know about relevant material, such as entries in

1086:

bring into compliance; human-guided bots are the only way I know of to address such an undertaking. The RfCs show that it should be a rare date indeed that is linked in the form of blued, in‑line body text. So the very few dates that

2020:

accepted solution. If the discussion is stalling due to problematic user conduct, then can address it if needed. If issues of unauthorized bot usage need to be addressed then make that clear. Please cite specifics of any problems.

1318:

dimension. Anyhow, there were few indications that Locke was ever committed to be bound by the outcome of the RfC, so this move hardly comes as a surprise. In fact. Lock has been strategically planning seizing this committee since

3692: 4423: 2737:

and may be improved by anyone, by way of bug reports, design documents, code patches, technical documentation, etc. Fair criticism of open source software is acceptable; however, it is incumbent on everyone to participate in

2205:

There are two caveats to my opinion. First, the issue of whether to link or delink dates is not, in my mind, entirely on a level with the merging and deleting seen in the Episodes and characters case, and does not create the

1680:

as for any other policy issue. No result has yet been found, and therefore it is inappropriate for any editor or group of editors to be acting as if it has. For that reason I have added myself as a co-sponsor of this RfAr. —

1410:

to achieve edit speeds of several pages a minute, which triggered WP's spam-guard mechanisms and alerted some admins to block the suspected bot. My arguments that I was not operating a bot was looked at and was accepted by

2662:

tools, such as bots and scripts, or fails to respond appropriately to concerns from the community about their use over a period of time, may lose the privilege of using such tools or may have such privilege restricted.

1629:

This was immediately after I had taken the time to go through the RfC in search. While there were undeniably a number of voices (roughly 40) agreeing with the proposal that "Year links should never be made", there were

2329: 2312:

is entered as an interim measure and does not reflect any prejudgment of any aspect of the case. The Clerk will notify the parties of this temporary injunction and post a note of it on the appropriate policy page(s).

199: 3764: 1212:

The diversity of the English Knowledge (XXG) means that disputes are inevitable, and it is unrealistic to believe that 100% support can be garnered for most things. The Date Linking RFCs clearly indicated that there

6183:

Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new sanction if fresh misconduct has taken place after the existing sanction was applied.

6111:

This procedure applies to appeals related to, and modifications of, actions taken by administrators to enforce the Committee's remedies. It does not apply to appeals related to the remedies directly enacted by the

4636:

1.3) All mass date delinking is restricted for six months. For six months, no mass date delinking should be done until the Arbitration Committee is notified of a Community approved process for the mass delinking.

5569:

is subject to an editing restriction for 12 months. John is prohibited from reversion of changes which are principally stylistic, except where all style elements are prescribed in the applicable style guideline.

2791: 6221:

request an easing or removal of the sanction on the grounds that said sanction is no longer needed, but such requests may only be made once every six months, or whatever longer period the committee may specify.

6078:

0) Should any user subject to a restriction in this case violate that restriction, that user may be blocked, initially for up to one month, and then with blocks increasing in duration to a maximum of one year.

2085:

Can anyone provide an estimate of: (i) the percentage of articles within the corpus that have so far been de-linked and (ii) the rough proportion of de-linked articles which have been subsequently reverted?

6053: 4575: 214: 2202:

an encyclopaedia. Removing links while doing other necessary changes on individual articles could not be disruptive, but systematically delinking for aesthetic reasons strikes me as a waste of server time.

1608: 1237:'s conduct, the survey of attitudes there indicated that not only was Tony1's conduct within policy, but his delinking of dates was not disruptive at all. I would like to impress upon the Arbitrators that 681: 1780:

How telling it is that the best Tennis Expert can come up with to support his allegation of edit warring is a complaint that he himself filed, and whose outcome was NOVIO. Strange he didn't mention that.

2818: 6772: 6762: 2069:; the issue pivots around large scale implementation of style changes, and the behavior surrounding the propriety of such changes. I don't think the name change is necessary, but it is acceptable. — 2830: 1665:

like reading mindless shit... turning yet more main body text into a giant blue turd". Reading through some of the archive links provided above by Locke Cole shows my experience was far from unique.

2555:

10.1) Users who disrupt the editing of articles by engaging in sustained aggressive point of view editing may be banned from the affected areas. In extreme cases, they may be banned from the site.

2399: 2106:

My estimation is very rough and is based on feeling rather than actual data: Perhaps 30 % of all articles with dates were forcibly delinked. Probably in less than 1 % the links were re-introduced.

6141: 4609: 4606: 4588: 4585: 4504: 4460: 4420: 4370: 4367: 4328: 4325: 4307: 4304: 4250: 4201: 4198: 4166: 4134: 4023: 3858: 3855: 3852: 3815: 3577: 3574: 3497: 3479: 3464: 3461: 3438: 3404: 3401: 3272: 3269: 3164: 3079: 3018: 2835: 1348: 1075: 195: 188: 6270:

Log any block, restriction, ban or extension under any remedy in this decision here. Minimum information includes name of administrator, date and time, what was done and the basis for doing it.

1814: 1668:

It is my concern, both as an editor with an opinion in this debate, and an administrator watching the situation, that the behavior of several individuals in this area equates to no less than an

1309:

dates off some 8,600 articles as at today's date, and have received only about ten complaints, most of which have nothing to do with the principle of removing dates. One notable complaint was

1074:. The end result, of course, is to reestablish links to articles that for the most part have nothing to do with sports. This is contrary to not only the general consensus of the RfCs, but also 973:"smarter" approach to linking and for the removal of date autoformatting. Waiting it out, I suspect, has been on our minds for some time, and is probably the natural and wiki-ish thing to do. 7024:

8) Lightmouse is limited to using only the account "Lightmouse" to edit. He may also use a separate bot account for any bot task or group of related tasks approved by the bot approvals group.

1149:

of the dispute to conform to expected conducted on Knowledge (XXG). I think this is germane to the dispute’s origins and believe any reasonable interpretation of the RfCs will bear this out.

868:

will not make editorial statements or decisions about how articles should read ("content decisions"). Please do not ask the committee to make these kinds of decisions, as they will not do so.

789:. Specifically those running automated or semi-automated tools to force their preferred version on the rest of us, but also the uncivil behavior of those participating in the discussions. — 2998:. In conjunction with blind reverts, bot and script bugs, and articles being delinked multiple times, the mass delinking contributed to the tension of the dispute and was self-defeating. 6834: 5853: 2127:

I agree that the issue for ArbCom here is behavioural: whether large-scale implementation was premature and whether consensus was sufficiently established for such a profound change. --

609: 3017:

occurred across the breadth of the project, usually consisting of one regular contributor to an article pitted against a well-coordinated team of MOS enforcers and their automations.

2952:" (a "sea of blue"). This bug is more relevant to wiki projects other than Knowledge (XXG), especially where the project has little need for "month day" pages, or even "year" pages. 3628:) on November 11, 2008 with the express purpose of using it for date delinking. It performed 9307 edits without BAG approval until January 30, 2009 when it was indefinitely blocked. 4110: 4055: 3998: 3957: 3893: 3796: 3580: 3520: 3476: 3435: 3432: 3085: 3687:

The March 2009 block evasion included reverting users involved in this date debate, and he subsequently initiated Arbitration Enforcement against the same users he had reverted.

1233:. Second, Locke's point of incivility does not seem well-supported. The one instance in which inciviliy was considered a major problem, when a situation culminated in an RFC on 1867:

Comment. Courtesy archive links for examples of WT:MOSNUM and noticeboard discussions would be appreciated, particularly for discussions leading up to and following the RfCs.

2273:

pending what the name will be. I support just keeping it to the date delinking conduct issues; if we widen the scope it could be dangerous, so I oppose a rename at this time.

1003:

article. I have a practice of my own that is fully in compliance with MOSNUM as well as with the current community consensus according the latest RfCs. Note the beginning

3169: 1837: 3268:

14) Lightbot has passed over articles multiple times. When errors in the first pass have been corrected by others, subsequent passes have repeated the original error.

5842:

Locke Cole remains subject to an editing restriction for 12 months (until June 14, 2010), under which he is prohibited from reverting the linking or unlinking of dates.

3190: 1276:, and would ask Arbcom to take this case because it is undoubtedly a behavioural issue stemming from a small group of individuals' inability to accept valid consensus. 1394:

There seems to be a misconception by a couple of arbitrators that the above account is a bot. I am the operator of this account. I believe it has been made clear that

6413:

for a period of two weeks for violation of the temporary injunction, and evading the above-noted 72-hour block with IP addresses to violate the temporary injunction.

3250: 3213: 2810: 2591: 1833: 7015:

7.1) Lightmouse is indefinitely prohibited from using any automation whatsoever on Knowledge (XXG) except for a bot task or group of related tasks authorized by the

4627:

Note: All remedies that refer to a period of time, for example to a ban of X months or a revert parole of Y months, are to run concurrently unless otherwise stated.

2193:

proposal. I don't think I have prejudged this case but if seriously asked to recuse on these grounds by a party to an accepted case then I would be bound to accede.

1304:, whereas the plaintiff is on record as not only opposing consensus on the issue (as borne out by the RfCs closed 25 December 2008), but also quoted as saying that 1053: 931:

I believe the Committee may face a difficult task in defining exactly what it should arbitrate on in relation to this application. These comments may be relevant.

736:

If accepted I would request that the committee pass a motion stopping all automated or semi-automated edits of this fashion until the conclusion of arbitration. —

701:

fait accompli or to exhaust their ability to contest the change. This applies to many editors making a few edits each, as well as a few editors making many edits.

6778: 2346:

1) The purpose of Knowledge (XXG) is to create a high-quality, free-content encyclopedia in an atmosphere of camaraderie and mutual respect among contributors.

1368:) is under consideration strikes me as being reckless and in contempt of process at worst; at best, I consider it unwise. I contend that this would put Locke's 6754: 6241: 6130: 6085: 1056:. It is a convenient portal as it contains links to the RfCs themselves. These RfCs also remind us of a central consideration to resolved here in arbitration: 5123:

23.2) Kotniski is topic banned for three months from style and editing guidelines relating to the linking or unlinking of dates, and any related discussions.

2742:. Deriding the developers, who are in short supply, is not acceptable; they are volunteers, and may have priorities other than fixing non-critical problems. 2646:

accompli or to exhaust their ability to contest the change. This applies to many editors making a few edits each, as well as a few editors making many edits.

1293:

over the most trivial issue of a pair of square brackets, using all the bureaucratic means at his disposal. I do confess to having given some best efforts to

2229:

a case strictly limited to the use of automated or semiautomated tools to delink dates on articles but nothing wider. The caveat about recusal still stands.

1230: 5647:

31.1) Pmanderson is topic banned for 12 month from style and editing guidelines relating to the linking or unlinking of dates, and any related discussions.

1044:

think I can be of assistance here by offering this observation: Towards resolving this dispute, arbitrators need a convenient and succinct way to establish

5280: 2210:" mentioned in the title of the principle. Second, if we were to accept the case, the committee cannot issue binding policy on the issues within the RFCs. 633: 5839:

Locke Cole remains indefinitely topic-banned from style and editing guidelines relating to the linking or unlinking of dates, and any related discussions.

5662:

32) Locke Cole is topic banned indefinitely from style and editing guidelines relating to the linking or unlinking of dates, and any related discussions.

3194: 2198:

That being said, I am concerned at the time spent by a small number of editors who have been mass delinking - which cannot truly, I think, be regarded as

1034: 5884: 4686:

6) Lightmouse is topic banned indefinitely from style and editing guidelines relating to the linking or unlinking of dates, and any related discussions.

3239: 2910:

conflicting interpretations of the discussion results. The contentious development and results of the December RfCs are reflective of this environment.

2509:

American spelling to British spelling if the article concerned a British subject. Revert warring over optional styles is unacceptable; if the article is

2300: 2283: 2265: 2219: 2101: 2057: 2027: 1949: 1876: 1823: 1623: 3597:

28) Ohconfucius has informed users that in an attempt to speed up the process of date delinking, he has operated multiple instances of AutoWikiBrowser.

6537: 6134: 5990:

37) Kendrick7 is topic banned 12 months from style and editing guidelines relating to the linking or unlinking of dates, and any related discussions.

5218: 4915:

Ohconfucius is topic banned indefinitely from style and editing guidelines relating to the linking or unlinking of dates, and any related discussions.

4836:

13) Greg L is topic banned indefinitely from style and editing guidelines relating to the linking or unlinking of dates, and any related discussions.

2786:

1) The longstanding dispute in this case is a disagreement between two groups of editors on the issue of linking dates. It encompasses the MediaWiki

1661:: "the puke you expect our articles should be linking to... just because you can prove you can stomach through reading that shit will only prove that 1479:

dates should be linked (opinions differ from only the most important, which bring huge additional value, to all dates), there is clear consensus that

6758: 2470: 5466: 5027: 1810: 483: 676: 5767: 5695: 531: 387: 243: 7068: 1563:

Delinking still continues and despite the effort of Dabomb87, Lightmouse and others, millions of articles cannot be delinked in few months time.

671: 6828:. The Committee thanks the participants for their efforts and encourages them to continue with their constructive work and consensus building. 1611:, as at the time I found the size of the discussion overwhelming, in addition to not having had any stake in the matter from prior experience. 5342: 3728: 2473:. Revert rules should not be construed as an entitlement or inalienable right to revert, nor do they endorse reverts as an editing technique. 1991:, largely per Vassyana and suggest renaming to MOSNUM due to larger issues. Date delinking is only the latest incarnation of MOSNUM problems. 1806: 187:), and serve as opening statements; as such, they should not be altered. Any evidence you wish to provide to the Arbitrators should go on the 6975:

is limited to using only the account "Ohconfucius" to edit. He may also use a separate bot account for any bot task or tasks approved by the

5156: 1095:

sections. Hand-restoring a relatively small number of links is a good opportunity for editors to avail themselves of these other techniques.

435: 2763: 920:

Much of what I was going to add about the substantive allegations in the statements by the filers and their associates has been clinched in

210: 184: 17: 6504: 6378: 5404: 5274: 3994: 3740: 627: 2843: 2595: 2533: 1352: 3325:

16) In an attempt to speed up the process of date delinking, Lightmouse has operated multiple instances of AutoWikiBrowser concurrently.

6312: 5878: 4869: 4416: 3758: 3746: 3674: 3625: 3075: 339: 6017: 5946: 5212: 4792: 4539: 3944: 3734: 1453:. The only other way I can see of ensuring no disputes on such matters in future would be to replace it with directives from the top. 291: 5247:

is subject to an editing restriction for three months. 2008Olympian is prohibited from reverting the linking or unlinking of dates.

6937: 6406: 6350: 6284: 5603: 5540: 5460: 5309:

is subject to an editing restriction for 12 months. Colonies Chris is prohibited from reverting the linking or unlinking of dates.

5021: 4162: 3752: 3688: 1145:

precious little admiration for this sort of behavior. There seems to be a pattern here regarding the willingness of notable editors

477: 5913:

is subject to an editing restriction for 12 months. Tennis expert is prohibited from reverting the linking or unlinking of dates.

4759:

9.3) Tony1 is indefinitely prohibited from editing any style and editing guidelines relating to the linking or unlinking of dates.

2678: 1752:

to get me, Lightmouse and others banned from using AWB to make these edits; then he lost two RFCs, and made spurious complaints at

2925:

5) Deprecation of autoformatting and date-delinking have been problematically conflated in this dispute. While both sides of the

6868: 6700: 6636: 6610: 6029: 5822: 5761: 5689: 5056:

is subject to an editing restriction for 12 months. Ohconfucius is prohibited from reverting the linking or unlinking of dates.

4551: 4300: 4234: 3146: 2929:

have conflated the issues, consensus for the deprecation of autoformatting has been abused as consensus for mass date delinking.

950:

for the changes would create a very difficult task for ArbCom. While I can see why Arb. Davies hints at this scope, producing an

848: 825: 798: 772: 745: 723: 525: 381: 237: 198:. That page may also be used for general comments on the evidence. Arbitrators will then vote on a final decision in the case at 5724:

is subject to an editing restriction for 12 months. Locke Cole is prohibited from reverting the linking or unlinking of dates.

2379: 6564: 6047: 6035: 5371:

is subject to an editing restriction for 12 months. SkyWalker is prohibited from reverting the linking or unlinking of dates.

5336: 4569: 4557: 4500: 4388: 4051: 3698: 3647: 3132: 3118: 1445:

With all due respect to the excellent technical efforts of Kotniski, his sage advice and his in my view correct reading of the

1347:

Not happy with the state of disruption he and his cohorts have sown in WP, a battle appears to have erupted over the merger of

6445: 5185:

is subject to an editing restriction for 12 months. Dabomb87 is prohibited from reverting the linking or unlinking of dates.

2490: 2458: 1817:

appears to be the most recent discussion, and problems with the automated edits were raised. Have those problems been fixed?

6882: 6437: 6023: 5150: 5101: 4545: 3886: 3848: 3231: 3160: 2465:, and for helping the debate move to better approaches by discussing their differences rationally. Edit-warring, whether by 2261: 429: 6703:) restriction re-widened to include the pages and talk pages of all MOS and style guidelines due to continuing disruption. 4898:

is subject to an editing restriction for 12 months. Greg L is prohibited from reverting the linking or unlinking of dates.

2540:. Over-rigid or over-zealous implementation can be more disruptive than the behaviour that they are intended to discourage. 2403: 2387: 1159:

by Colonies Chris. Notwithstanding that it is a hearty dose of plain-speak, I believe it all to be true and highly relevant.

955:

the iceberg. I note Arb. Blacketer's comment that "the committee cannot issue binding policy on the issues within the RFCs".

4821:

is subject to an editing restriction for 12 months. Tony1 is prohibited from reverting the linking or unlinking of dates.

3044: 3031: 3029: 3027: 3025: 3023: 3021: 2895:

3.2) Two RFCs held in December 2008 reaffirmed that the current date autoformatting functionality is undesirable, and that

2711: 6531: 6041: 5398: 4563: 4106: 1080:

relevant connections to the subject of another article that will help readers to understand the current article more fully

864:(1) The filing party begins by stating that "This has been an ongoing content dispute". Yet the lead clearly states that: 4419:) has edit-warred extensively to restore linking of dates, primarily on the tennis articles, but also on other articles. 3954:

On the 15th, 2008Olympian excessively edit-warred for a few days on tennis articles and other ongoing related edit-wars.

2968:) to add Cascading Stylesheet and Javascript control to all autoformatted dates, such as presenting them as normal text ( 2461:, rather than through disruptive editing. Editors are each responsible for noticing when a debate is escalating into an 6767: 6662: 6329: 5298: 4863: 3185:

12) Bobblewik was a very prolific editor from March 2004 to October 2006 (65,000+ edits), who was blocked over 17 times

651: 333: 5975:

is subject to an editing restriction for 12 months. He is prohibited from reverting the linking or unlinking of dates.

5495:

is subject to an editing restriction for 12 months. He is prohibited from reverting the linking or unlinking of dates.

5433:

is subject to an editing restriction for 12 months. He is prohibited from reverting the linking or unlinking of dates.

2991: 2707: 2571: 1959: 1676:

on style across articles on a vast scale in the absence of any policy requirement for it or even widespread consensus.

1634:(roughly 55) agreeing with the proposal that "Year links should be made in certain cases". This is not a consensus for 1033:

on WT:MOSNUM to ‘newcomer’ editors concerned about date de‑linking after seeing Lightbot activity affect them, I wrote

963: 886: 6467: 5940: 5902: 4786: 4456: 3358: 2973: 2969: 966:

produced convincing consensus that special consensus is unnecessary for bots to assist in compliance with styleguides.

885:(4) I submit that the filing party's construction of consensus in this context is not a balanced view. In particular, 785:

I'm not asking the committee to decide the content dispute, I'm asking the committee to look at the behavior of those

285: 3078:) almost exclusively pushing back repeatedly with 751 reverts. As a result, the battle become excessively personal. 1748:

I’ll divide my statement into two parts; my opinion, and some facts about the community reaction to date delinking.

6145: 5597: 5534: 5286: 5236: 4194: 3722: 639: 4426: 3082: 2839: 1221:

for a more detailed breakdown). Besides the RFCs, examples of this consensus against delinking dates exist in our

6205:(i) the clear and substantial consensus of (a) uninvolved administrators at AE or (b) uninvolved editors at AN or 5890: 5484: 5045: 3279: 1615: 573: 501: 2829:

on November 20, 2008, and has been protected from editing due to the unresolved dispute since November 18, 2008.

6710: 6685: 6647: 6621: 6593: 6586: 6569: 6527: 6522: 6498: 6489: 6452: 6422: 6391: 6372: 6363: 6335: 6315:) blocked indefinitely for violation of the temporary injunction. This is an alternate account of Ohconfucius. 6297: 6176:

prior affirmative agreement for the modification at (a) AE or (b) AN or (c) ARCA (see "Important notes" below).

5785: 5713: 5268: 5224: 3988: 2469:

or otherwise, is prohibited; this is so even when the disputed content is clearly problematic, with only a few

2238: 2165: 2142: 2113: 2073: 2043: 2010: 1981: 1907: 1890: 1860: 1846: 1735: 1701: 1594: 1570: 1546: 1462: 1432: 1381: 1336: 1259: 1199: 986: 903: 851: 828: 801: 775: 748: 726: 621: 549: 405: 261: 5836:, his full editing ban will be reinstated for the remainder of its original duration, until December 14, 2009. 3036: 2926: 2814: 2537: 1673: 1650: 6470:) blocked for violation of the temporary injunction until such time as he agrees to stop mass delinking, per 6513: 6306: 5872: 5472: 5360: 5033: 4410: 3668: 3619: 3069: 2739: 2234: 2215: 1048:

regarding the current community consensus on linking and related bot activity. Arbitrators should know that

585: 489: 4581: 2395: 6889:. "Automation" is to be interpreted broadly to refer to any automated or semi-automated tools whatsoever. 6011: 5773: 5701: 5206: 5174: 4533: 3938: 603: 591: 537: 453: 393: 249: 2599: 2466: 2454: 1925:

to double check that. While the issue of date delinking is roughly 6 months old, other issues related to

1446: 1243: 6931: 6400: 6344: 6278: 6180:

Administrators modifying sanctions out of process may at the discretion of the committee be desysopped.

5454: 5422: 5348: 5015: 4156: 3814:

32) The Rambling Man has edit-warred extensively to remove the linking of dates on the tennis articles.

3717: 1626:

to suspend the bot's blanket removal of year links until consensus for such an action was demonstrated.

1458: 1428: 1377: 1332: 579: 471: 2949: 2896: 2462: 2391: 2383: 1511: 194:

Arbitrators, the parties, and other editors may suggest proposed principles, findings, and remedies at

128: 5449: 4152: 6862: 6694: 6630: 6604: 6600: 5816: 5812: 5755: 5750: 5683: 5678: 5162: 4887: 4294: 4290: 4228: 3140: 2734: 2457:. This is done through the use of polite discussion—involving the wider community, if necessary—and 2296: 1406:

on the Userpage. Before AWB approval was gained, reliance was put on multi-windowed functionality of

1277: 844: 840: 821: 817: 794: 790: 768: 764: 741: 737: 719: 715: 689: 597: 519: 441: 375: 357: 231: 226: 2622: 1315: 6579: 6562: 6549: 6494: 6386: 6368: 6358: 6292: 6058:

is admonished for threatening to use his administrator tools to advance his position in a dispute.

5964: 5410: 5330: 5263: 5091: 4810: 4494: 4045: 3984: 3838: 3126: 3112: 2899:

of dates is not desirable; however, consensus has not been found on when dates should be delinked.

1742: 1507: 1439: 1356: 1152:

BTW, I want to specifically draw attention to and endorse the statements of the following editors:

616: 309: 3061: 2990:

7) Despite the ongoing dispute, mass date delinking has been conducted by many users via scripts,

2787: 1926: 1305: 1301: 1286: 707:

Knowledge (XXG):Requests_for_arbitration/Episodes_and_characters_2/Proposed_decision#Fait_accompli

6876: 6431: 6302: 5867: 5621: 5558: 5144: 5095: 4875: 4406: 3880: 3842: 3664: 3643: 3633: 3615: 3225: 3154: 3065: 2965: 2255: 2230: 2211: 2040: 2024: 1918: 1903: 1886: 1872: 1802: 1388: 1255: 1049: 423: 345: 1360: 1285:. This subject/guideline may have the dubious honour of having the record number of attempts to 1273: 3682:, and again in March 2009 when blocked for violating an injunction intended to stop the battle. 2961: 6707: 6006: 5952: 5392: 5201: 4798: 4703:

Lightmouse is indefinitely prohibited from using any automation whatsoever on Knowledge (XXG).

4528: 4100: 3934: 2250:

I am a good friend of Tony and my ability to be impartial may not be accepted by all. Cheers,

2151: 2128: 2087: 1553: 1535:. This is quite disrupting in continuation to work for the Knowledge (XXG) which I started in 1403: 1082:. Said another way, links should be germane and topical to the subject matter of the article. 1063: 297: 2945: 2621:

are processes that modify Knowledge (XXG) content in a fully or partially automated fashion.

2618: 1706:

Additional: I am becoming more and more concerned with the behavior of Greg L. Edits such as

1450: 1294: 1058:

is bot activity (or planned bot activity) in accordance with the current community consensus?

6972: 6927: 6656: 6418: 6396: 6340: 6323: 6274: 5609: 5546: 5010: 4857: 3948: 2536:

exist to facilitate the smooth running of the project. However, they should be applied with

2003: 1974: 1942: 1798: 1654: 1454: 1424: 1412: 1373: 1328: 1266: 1194: 466: 327: 7016: 6976: 6886: 6821: 5833: 4653: 3217: 2627: 1922: 1753: 1669: 1523: 1399: 1369: 1290: 1282: 6858: 6690: 6626: 6461: 6169:

No administrator may modify or remove a sanction placed by another administrator without:

5934: 4780: 4450: 4224: 3352: 3136: 2960:

resolved this bug by creating parser function "formatdate", and at the same time resolved

2292: 2182: 2109: 1590: 1566: 1542: 1469: 1015: 1011: 981: 898: 514: 370: 279: 6471: 5105: 5072: 4387:

47.5) Locke Cole has an extensive record of disruptive behavior spanning multiple years (

3014: 1247: 1226: 1222: 2630:

is generally required before an editor may use a bot for automatic or high-speed edits.

1672:

issue over the whole site, by using automated or semi-automated tools to forcibly apply

6676: 6553: 6480: 6449: 5591: 5528: 5325: 4490: 4188: 4041: 3122: 3108: 2851:. However, this resulted in further disputes on these pages, requiring page protection 2274: 1420: 1416: 1229:, where the delinking of dates was accepted without any form of resistance, as well as 1071: 209:

as needed, but this page should not be edited otherwise. Please raise any questions at

6816:

fulfills the requirement for "a Community approved process for the mass delinking" in

7062: 6872: 6644: 6618: 6427: 5139: 3876: 3221: 3150: 2699: 2251: 2037: 2021: 1899: 1882: 1868: 1829: 1720: 1686: 1642: 1619: 1557: 1530: 1251: 1206: 812: 760: 567: 418: 1618:

regarding the repeated removal of a single year link from the lede of an article by

6575: 5387: 4096: 3663:

30) Ohconfucius has unlinked dates while evading blocks in November 2008 using the

2575:

Style, although it is not policy and editors may deviate from it with good reason.

4944:

Ohconfucius is prohibited from using any automation in article space indefinitely.

4605:

52) Arthur Rubin has edit warred on the project pages related to the date debate.

3552:

25) Ohconfucius has edit warred on the project pages related to the date debate.

1079: 6652: 6414: 6317: 4852: 4324:

46) Locke Cole has edit warred on the project pages related to the date debate.

4267:

44) Pmanderson has edit warred on the project pages related to the date debate.

2957: 1994: 1965: 1933: 1856: 1842: 1819: 1658: 1300:

In addition to creating and expanding articles, I am interested in carrying out

1189: 996: 322: 5829:

Locke Cole is provisionally unbanned effective at the enactment of this motion.

4503:) has edit warred extensively on the project pages related to the date debate. 3769:

has made comments intended to encourage a contributor to return to retirement.(

3697:

In addition, Ohconfucius was blocked for evading the Arbitration injunction in

2948:

was raised in January 2006 to allow dates to be autoformatted without causing "

2762:

pages), should be thoroughly discussed with the technical team, at venues like

2715: 6457: 5929: 4775: 4446: 3348: 2822: 2517:, it would be wrong to switch simply to change styles as both are acceptable. 2070: 2054: 1809:

is a redlink. Has there been any communal approval of this bot? Very few of

1577: 1339:(reworked from edits 15:43, 10 January 2009 (UTC) and 01:12, 11 January 2009) 1234: 974: 891: 858: 274: 1272:

I would respectfully disagree with those who have said this has been largely

5586: 5523: 4184: 3519:

24) Ohconfucius has been incivil in their communication with other editors.

3496:

23) Greg L has edit warred on the project pages related to the date debate.

7045:

discussion of policies and guidelines, and the use of alternate accounts.

4580:

has threatened to use administrative tools in a dispute in which he was an

3947:) first became involved in the tennis articles by removing date links from 3400:

19) Tony1 has edit warred on the project pages related to the date debate.

3149:) which have a block log relevant to the community approval of bot account 6211:

is required. If consensus at AE or AN is unclear, the status quo prevails.

6820:

and the requirement for "ate delinking bots in a manner approved by the

6173:

the explicit prior affirmative consent of the enforcing administrator; or

4671:

5.1) Lightmouse is banned from Knowledge (XXG) for a period of one year.

3636:

unlinked years even when the year was a primary component of the subject.

2718:, each having their own processes and customs which should be respected. 1715: 1681: 1601: 1019: 1004: 562: 6940:) is permitted to use automation subject to normal community guidelines. 3064:

to delinking dates on tennis articles commenced in September 2008, with

1646:

editor to make another feel unwelcome in participating in this fashion.

6996: 4994: 4985: 4973:

Ohconfucius is limited to using only the account "Ohconfucius" to edit.

4927: 1407: 1217:

consensus against most, if not all, dates being linked (see my comment

116: 98: 6126:

ask the enforcing administrator to reconsider their original decision;

4744: 4715: 107: 5825:) from editing Knowledge (XXG) for six months is amended as follows: 4732:

Lightmouse is limited to using only the account "Lightmouse" to edit.

2510: 1499: 6511:

for a period of 48 hours for violation of the temporary injunction.

6385:

for a period of 24 hours for violation of the temporary injunction.

6357:

for a period of 72 hours for violation of the temporary injunction.

6291:

for a period of 48 hours for violation of the temporary injunction.

6144:. If the editor is blocked, the appeal may be made by email through 3962:

2008Olympian occasionally participated in the edit-wars afterwards.

3889:) has edit-warred extensively with respect to the linking of dates. 3460:

22) Greg L has been incivil in his communication with other editors.

682:

Knowledge (XXG):Manual of Style (dates and numbers)/Date Linking RFC

4956: 215:

Knowledge (XXG):Administrators' noticeboard/Arbitration enforcement

211:

Knowledge (XXG):Requests for arbitration#Requests for clarification

89: 6763:

Knowledge (XXG):Bots/Requests for approval/Full-date unlinking bot

5637:

Passed 7 to 0 (with 2 abstentions) at 10:53, 02 August 2009 (UTC).

4652:

2.1) Date delinking bots will perform in a manner approved by the

2733:

20.1) The software used by the English Knowledge (XXG) project is

2514: 1962:, it's using AWB on an alternate account, which is within policy. 1836:, but this "solitary year unlinking" functionality was covered by 1657:

and greeted with a torrent of aggressive language and swearing by

1103:

to this complaint. Tony and Lightmouse have exemplary block logs (

80: 62: 5729:

Passed 11 to 0 (with 2 abstentions) at 19:21, 14 June 2009 (UTC).

5190:

Passed 10 to 1 (with 2 abstentions) at 19:21, 14 June 2009 (UTC).

4691:

Passed 11 to 0 (with 2 abstentions) at 18:56, 14 June 2009 (UTC).

4616:

Passed 11 to 0 (with 2 abstentions) at 16:40, 14 June 2009 (UTC).

3445:

Passed 11 to 0 (with 2 abstentions) at 16:40, 14 June 2009 (UTC).

3414:

Passed 11 to 0 (with 2 abstentions) at 16:40, 14 June 2009 (UTC).

3390:

Passed 11 to 0 (with 2 abstentions) at 16:40, 14 June 2009 (UTC).

2825:

by the community. This page in the manual of style was taken to

6063:

Passed 11 to 1 (with 1 abstention) at 19:21, 14 June 2009 (UTC).

5667:

Passed 12 to 0 (with 1 abstention) at 19:21, 14 June 2009 (UTC).

5652:

Passed 8 to 1 (with 2 abstentions) at 19:21, 14 June 2009 (UTC).

5575:

Passed 9 to 1 (with 3 abstentions) at 19:21, 14 June 2009 (UTC).

5376:

Passed 9 to 1 (with 2 abstentions) at 19:21, 14 June 2009 (UTC).

5314:

Passed 10 to 1 (with 1 abstention) at 19:21, 14 June 2009 (UTC).

5252:

Passed 9 to 2 (with 2 abstentions) at 19:21, 14 June 2009 (UTC).

5113:

Passed 6 to 4 (with 3 abstentions) at 19:21, 14 June 2009 (UTC).

5080:

Passed 6 to 5 (with 2 abstentions) at 19:21, 14 June 2009 (UTC).

5071:

20) The Rambling Man is admonished for not pursuing appropriate

5061:

Passed 12 to 0 (with 1 abstention) at 18:56, 14 June 2009 (UTC).

4921:

Passed 12 to 0 (with 1 abstention) at 18:56, 14 June 2009 (UTC).

4903:

Passed 12 to 0 (with 1 abstention) at 18:56, 14 June 2009 (UTC).

4826:

Passed 9 to 2 (with 2 abstentions) at 18:56, 14 June 2009 (UTC).

4764:

Passed 9 to 2 (with 2 abstentions) at 18:56, 14 June 2009 (UTC).

4709:

Passed 12 to 0 (with 1 abstention) at 18:56, 14 June 2009 (UTC).

4595:

Passed 11 to 1 (with 1 abstention) at 16:40, 14 June 2009 (UTC).

4517: