Misplaced Pages

talk:Requests for arbitration/Date delinking/Proposed decision: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages talk:Requests for arbitration | Date delinking Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 11:28, 30 April 2009 editKotniski (talk | contribs)Autopatrolled, Pending changes reviewers, Rollbackers40,317 edits Major omission: serious error, if these are the facts being accepted by ArbCom← Previous edit Latest revision as of 13:33, 18 February 2023 edit undoMalnadachBot (talk | contribs)11,637,095 editsm Fixed Lint errors. (Task 12)Tag: AWB 
(938 intermediate revisions by 78 users not shown)
Line 1: Line 1:
{{archivebox|auto=long}}
{{ACA|Date delinking=yes}}


== Arbitrators active on this case ==
== Protected ==


{{#ifeq:|yes|
I note that ] has been protected since . I would hope any remedies would include some sort of path to unprotection. ''']''' <sup>]</sup> 05:34, 25 January 2009 (UTC)
'''Active:'''
:I suppose it is rather meanginless to note that ] does not sit on its own, as since its protection the edit warring has continued by the involved parties at ] as of Feb 2nd: , . So my above comment should probably be phrased as "I would hope any remedies would include some sort of path to '''long term''' unprotection '''of all date-related ] pages'''. ''']''' <sup>]</sup> 03:16, 2 February 2009 (UTC)
#Cool Hand Luke
#Coren
#FayssalF
#FloNight
#Jayvdb
#Newyorkbrad
#Rlevse
#Roger Davies
#Stephen Bain
#Vassyana
#Wizardman


'''Inactive:'''
== "Temporary" injunction ==


'''Recused:'''
The injunction in this case has been in place for nearly three months. This might be acceptable if it was limited in application and affected only the parties to the case. However, it is incredibly broad, applying to "all editors" and affecting edits that are extremely common. Despite that, I doubt it's well known to everyone it might affect, or that it's been adequately publicized. Although the stated dispute is about the use of bots and scripts, the injunction has now against someone who is not using any such tools, is not a party to the case, but is simply going about normal systematic editing that isn't particularly about date links, even though they happen to come up (kind of hard to avoid, actually). So I'd like to ask, why is this injunction staying in place so long with no apparent progress on the case? --] (]) 16:27, 8 April 2009 (UTC)
#Carcharoth
:I'd make it clearer what is meant by "mass" to avoid hitting people acting in good faith, for example: "Until the case is closed, any editor adding or removing links to year articles and/or day-of-the-year articles from more than <var>n</var> distinct articles within an <var>x</var>-hour period may be blocked." I'd go with <var>n</var>&nbsp;=&nbsp;24 and <var>x</var>&nbsp;=&nbsp;168, but any reasonable values would do. --<span style="font-family: monospace; font-weight: 600; color: #00F; background-color: #FFF;">]</span> (formerly Army1987)<small>&nbsp;—&nbsp;''],&nbsp;not&nbsp;]''.</small> 18:52, 8 April 2009 (UTC)
#Casliber
::I agree that this type of clarification is necessary for editors not using bots, especially considering the way that ] is going. ] (]) 20:15, 8 April 2009 (UTC)
#Kirill Lokshin
::*As Michael eloquently points out, the block in the case he noted above is entirely unfair &ndash; this is clearly collateral damage which should not occur. The injunction should only have been applied to automated linking and delinking by the parties only, plus ] in view of the evidence ]. Its application/enforcement (or not, as the case may be) has resulted in more drama and harm than it was ever meant to prevent, and should be lifted. ] (]) 01:57, 9 April 2009 (UTC)
#Risker
::: While I can understand your frustration, I just don't see what is so '''urgent''' about delinking dates. I absolutely cannot understand why, when someone has been informed that a temporary injunction exists, why it is so absolutely necessary to continue to delink all dates in the articles which he visits. It beggars belief that he feels that it is so crucial for the survival of wikipedia as a whole, that it is worth violating an arbcom injunction. Additionally, if the outcome of this arbcom is as you hope, then his edits will be performed in about ten seconds by lightbot. So the edits have saved about ten seconds of server time and wasted the time of everyone involved, including the person who delinked the dates. This is why my sympathy is extremely limited. ] (]) 07:10, 9 April 2009 (UTC)
::::There is nothing particularly "urgent" about cleaning up the date autoformatting mess or inconsistencies and illogical choices of format in any ''particular'' article. But it ''is'' urgent that our transition from amateur to professional standards continue apace, and the broader programs of such cleaning up are significant to the transition. This is why the ] efforts of editors such as ] and the skilled and sensitive development of bots and scripts by editors such as ] are so important to WP. The temporary injunction needs to be lifted for a host of reasons, among them that we can get on with the job. The community has discarded the creaking old date autoformatting system that was hastily introduced without consensus in 2003, and there is something of a landslide at the RFC for the relevance-related linking of date-fragments.
::::I believe we should take notice of by researcher Dr Bill Wedemeyer, Faculty of Biochemistry and Molecular Biology, Michigan State University, who conducted an extensive study of the quality of (mainly) scientific articles on WP. One of his conclusions is the significance of bots etc. to improving our article quality and MoS compliance (I think it's around 30 minutes in). ] ] 07:48, 9 April 2009 (UTC)
:::::Apparently ] does not really need the injunction to be lifted or modified as he never quit delinking dates anyway. See, e.g., , , , , , all of which were after March 28, 2009. ] (]) 09:44, 9 April 2009 (UTC)
:::::It's a volunteer project and thus there is no ]. The only two places that we need to act fast are with respect to copyvios and with respect to BLP. The entire reason this case exists is that people felt MOS compliance was a high urgency task - it is not. --] (]) 12:36, 9 April 2009 (UTC)


}}<!---
(od) This injunction has served its stated purpose, but in light of the recent ], is now simply an impediment to what should be normal editing. I understand that there is no deadline, but have to ask what the conditions for lifting this injunction are? The arguments above simply seem to suggest that the passage of time is required. If so, then how much time? Does it improve the encyclopedia to stop the wishes of the community being carried out? If removing deprecated date links improves the encyclopedia, then ] would surely trump this injunction right now. Any contributor can point to the poll results as consensus for their removal of an irrelevant date link. I understand that ArbCom may take an arbitrarily long period of time to consider other issues in this case, but the injunction does not depend, per se, on the outcome of those other issues. Can anyone explain how to propose a motion that the injunction be lifted? --] (]) 13:49, 19 April 2009 (UTC)
-->{{#ifeq:|yes|
:While I would agree that the consensus is clear on how we should link dates, we certainly have not resolved how this should be carried out. After all, one of the issues here is specifically about how the consensus position on linked dates should be carried out. Many people were (and are likely still) opposed to using a bot to delink all dates indiscriminately, as Lightbot does, when the consensus specifically allows for certain relevant dates to remain linked. -] (]) 14:24, 19 April 2009 (UTC)
'''Active:'''
::Consensus has shown that few date links need to remain, and can be easily relinked. See ] for more discussion on the matter. ] (]) 14:32, 19 April 2009 (UTC)
#Casliber
:::Consensus actually appears to have shown that ''relevant'' date links need to remain — how few or many that is remains to be seen. Regardless, if bots and scripts are ultimately going to be let loose on the article base to remove the dates that were purely for autoformatting and are not relevant — which would seem to be the most efficient solution — dates that should not be removed need to be protected in some manner before that happens. That same mechanism for protection would also keep them from getting removed in subsequent sweeps of the bot. In my mind, this is the most important item to be addressed through this arbitration. ] (]) 15:06, 19 April 2009 (UTC)
#Cool Hand Luke
::::I already "protected" the relevant link from the dab page ] to the article ] (however clumsily). Assuming that bots won't touch chronological articles, I think that job's finished, unless you can give any other instances of a link to a year or day-month article that's actually relevant? --] (]) 15:21, 19 April 2009 (UTC)
#Coren
:::::All that has to be done is to create a template what should be used to wrap and protect dates that should be linked, giving editors say 2 weeks to apply it (those that are concerned about date linking will be well aware of it), and then let Lightbot loose on any unprotected date in other articles. This may require that the date be a bit more formalized in the template arguments to make it look like anything but a date so that Lightbot can run without modification (and probably the easiest solution). Yes, there may be some dates that should be kept in articles that are not watched or maintained by those with date linking interests, but it can also be corrected in the same manner with the template. --] (]) 17:26, 19 April 2009 (UTC)
#FloNight
*There's a basic misunderstanding here: the proposal is that Lightbot should unlink '''only tripartite dates (that is, date autoformatting alone)''', not date fragments for which the consensus did indeed settle on a relevance test, albeit a strict one. The Lightbot task is framed as narrow in scope, to keep it technically simple and uncontroversial, to be applied broadly. This is a much stricter application of Lightbot than previously performed. ] ] 17:02, 19 April 2009 (UTC)
#Jayvdb
:* Moreover, the screening criteria his bot uses seems rather sophisticated. In a test of 40, randomly selected articles, his bot had 0% error in leaving alone articles like ], which are allowed to have linked dates, and it had 100% success in catching dates like the date in the second paragraph here in ]. We have also proposed that Lightmouse can have his bot go through—say—a hundred articles and wait for feedback. If an editor responds with “why is my precious link now black instead of link-blue”, we can direct them to MOSNUM. But we might also find that Lightbot fouls up with captions or some unforeseen issue (this is just an example). Lightmouse can tweak and then process, say, a thousand articles. This ramped approach is quite conservative and should be uncontroversial. It’s easy enough to hit and write to Lightmouse. Lightmouse can provide a “contact me” link in the edit summaries. <span style="white-space:nowrap;">''']''' (])</span> 17:17, 19 April 2009 (UTC)
#Kirill Lokshin
:*Thank you for clarifying, Tony. I agree that removing the linking for such dates is uncontroversial. I'm only concerned that a lifting of the injunction prior to the resolution of this case also opens the door to delinking of all kinds which is just a recipe for more drama. -] (]) 17:54, 19 April 2009 (UTC)
#Newyorkbrad
::I agree that the injunction should be lifted. I've been afraid to touch any dates because of the way I was informed and warned about the injunction. (In short, I knew nothing about it and was immediately warned with the threat of blocking. I hear that someone else who had no idea about the injunction was already blocked as well.) I also don't know what the big deal is about using Lightmouse's script. The script shows you the proposed changes before it saves the page. I have a brain and I can simply correct any edits to dates that should not be delinked myself, before saving. Anyone using the script could do the same. I also wholeheartedly agree with Greg L's above proposal of how to test Lightbot. ] ] 18:35, 19 April 2009 (UTC)
#Rlevse
#Roger Davies
#Stephen Bain
#Vassyana
#Wizardman
#FayssalF


'''Inactive:'''
:*Agreed, the fat lady has sung. ] (]) 04:20, 20 April 2009 (UTC)
#Carcharoth
#Risker


'''Recused:'''
:No misunderstanding on my part, Tony — just an absence of relevant information. I hadn't seen any discussion about a narrower scope for Lightbot, and so my comments were strictly a response to RexxS' suggestion that the injunction should be lifted. Assuming that the new scope would be removing linking in situations like <nowiki>] or ], ] — where the purpose of the links is clearly for autoformatting — I'd be supportive of a limited suspension of the injunction for Lightbot only, in order to begin some live test runs as described by Greg L. I'm assuming, however, that in this stricter application, if it were to encounter a pair such as ], ]</nowiki>, it would remove only the first link and not the second. If that assumption is incorrect, then my original concerns still remain. While the piped link clearly looks like broken autoformatting, determining intent is a lot trickier. As it links to what may be relevant information (depending on the context), I still don't believe it should be removed by automated process. ] (]) 05:13, 20 April 2009 (UTC)


}}<!---
:*There has been discussion about the action plan at ]. There seems now to be a general agreement for bot action to remove the square brackets around full dates only (any date that contains the three elements, day, month, year, in whatever sequence or format) in instances of misformatted dates. At the same time, the bot would insert a space where it is missing from the raw text, and insert a comma where it is missing from the raw text in mdy format. Date fragments (linked years and linked day-months) would be left untouched. In this connection, work is being done to prepare a ] where there are misformatted dates. ] (]) 05:51, 20 April 2009 (UTC)
-->{{#ifeq:|yes|
'''Active:'''
#Carcharoth
#Cool Hand Luke
#Jayvdb
#Kirill Lokshin
#Newyorkbrad
#Rlevse
#Roger Davies
#Stephen Bain
#Vassyana
#Wizardman


'''Inactive:'''
::*Oh sure; of all the pages '''not''' to have watch-listed, I pick that one. Thanks for the link, Ohconfucius. I've paged through the discussion, and it looks good to me. I think I saw a suggestion about halfway through the page that piped date links be left alone — I can't tell for sure from your comments directly above whether that's been included in the planning or not. If not, I still have concerns. However, if piped links will be unmolested in this phase, then count me as a voice from the "other" side of this issue in support of the proposed go-forward plan. ] (]) 15:14, 20 April 2009 (UTC)


'''Recused:'''
:::*The list of instances is a new page, so you can go easy on yourself. We have been discussing a more general approach on WT:DATEPOLL, but the specific recommendation came from . He will be joining the DATEPOLL discussion. ] (]) 15:27, 20 April 2009 (UTC)
#Casliber
:::::OhConfucius's link seems to lead to a version of the discussion from a few days ago - ] the current version. ] (]) 17:42, 20 April 2009 (UTC)
#Coren
::::*Mlaffs: "limited suspension" of the injunction? Why? It was a temporary injunction and is no longer appropriate given the results of the RFC. Wikignoming to clean up dates and many other aspects of articles needs to resume as before the injunction, nearly four months ago. I can't imagine why you think the injunction should be merely "suspended". Lighbot will not touch piped links.
#FayssalF
::::*Chunky Rice: Have you read the results of the RFC? ] ]
#FloNight
:::::*I just skimmed it. Why? Did I miss something about how the community wishes to proceed with delinking? -] (]) 16:52, 20 April 2009 (UTC)
#Risker


}}<!--
* (outdent) With regard to “limited suspension”, I think Mlaffs is using phraseology that actually refers to going forward precisely as we are proposing. He wrote …{{xt|I'd be supportive of a limited suspension of the injunction for Lightbot only, in order to begin some live test runs as described by Greg L }}. Then he wrote …{{xt|then count me as a voice from the "other" side of this issue in support of the proposed go-forward plan}}. In this case, “limited” merely means that he supports the idea of lifting the injunction so Lightmouse can commence his conservative, stepped approach to getting Lightbot up and going as he tweaks his bot between successively larger runs.<p>Lightmouse wants controversy about as much as hole in his head. He can deal with technical issues pertaining to his bot all by himself. But the poor bastard will need help if an editor like you{{nbhyph}}know{{nbhyph}}who pops up who vehemently disagrees with the MOSNUM guidelines being implemented by Lightbot. Accordingly, the need for intervention by anyone from ArbCom might only be necessary if another editor were to set himself ablaze over how “delinking dates is evil and the last RfC was invalid” and files WQAs and ANIs against Lightmouse. If it comes to that, I’m sure someone on the ArbCom can figure out an expedient and efficient procedure to deal with that sort of thing—perhaps refer them to ].<p>Besides, Tony, Mlaffs uses an iMac, just like you and I, so we know we think alike in many ways.;-) <span style="white-space:nowrap;">''']''' (])</span> 18:02, 20 April 2009 (UTC)
-->{{#ifeq:|yes|
'''Active:'''
#Casliber
#Cool Hand Luke
#Coren
#FayssalF
#FloNight
#Jayvdb
#Kirill Lokshin
#Newyorkbrad
#Rlevse
#Roger Davies
#Stephen Bain
#Vassyana
#Wizardman


'''Inactive:'''
:*Nicely put, Greg. Tony, I just figure that if there's a plan being developed for Lightbot to do the work in an orderly manner, with pre-defined logic, then we should let Lightbot do it. If the edits all come from one source, with a consistent edit summary and a pointer to where to deliver reasonable, policy-based expressions of concern, then I'd hope to see a material decrease in the associated drah-ma. There will be hundreds of eyes — well, dozens at the very least — on these edits, and it'll be a lot easier if they all need to focus in only one direction.<p>On the other hand, if we lift the injunction completely right now, then the chance for consistency goes way down with everybody running every which way to link and delink based on their own interpretations, and the gnashing of teeth and wailing will almost assuredly begin anew. In the meantime, hopefully Arbcom will finish up with the case and deliver whatever statements about policy, the application thereof, and user conduct that it feels are appropriate, and then the injunction can be lifted completely.<p>Besides, the injunction was only with regard to date linking/de-linking. I'd be distressed if wikignoming to clean up "other aspects of articles" had been slowed down in any way. Heck, my iMac and I have been wikignoming our posteriors off. ] (]) 18:39, 20 April 2009 (UTC)
#Carcharoth
#Risker


::*I know of one such case where gnoming has come to a halt: Colonies Chris has been knobbled several times in his cleanup efforts because of the interpretation of the injunction. As an occasional gnome, I know it is extremely inefficient to run an AWB pass only knowing you need to do it again after the injunction; it's difficult to reformat 256 unlinked dates in an article and have to leave a small handful of dates linked. ] (]) 01:52, 21 April 2009 (UTC)


}}<!--
===The injunction and auto formatting===
-->{{#ifeq:|yes|
As regards the latest RFC results, while it's true that the community seems interested in reducing the number of date links, they have not reached consensus on the issue of auto formatting. As auto formatting relies upon linking, I think it would be premature to remove the injunction and engage in mass removal of date links (and hence date auto formatting). —] • ] • ] 21:01, 20 April 2009 (UTC)
:It's pretty apparent that the community doesn't want most dates to be linked. A majority of RfC responses also said no to any form of autoformatting; there was not consensus from the minority on what technical way autoformatting should be implemented. See ] and ]. ] (]) 21:20, 20 April 2009 (UTC)
::I already said the community doesn't want most dates to be linked, but that's irrelevant if the community isn't prepared to abandon date auto formatting. I also disagree with Ryan's interpretation of the way forward: I don't think it's appropriate to begin mass delinking (which would also effectively remove all the markup for auto formatting) when auto formatting hasn't been rejected. —] • ] • ] 21:45, 20 April 2009 (UTC)
:::However, any autoformatting ''using links'' has been rejected. You asked the question; this was the answer: ] : 247 Support / 48 Oppose / 7 Neutral --] (]) 00:47, 21 April 2009 (UTC)
::::I think we should leave Locke alone with his rather "unique" interpretation of the consensus. He didn't get it on 25 December 2008, it doesn't look like he's getting it any better on 13 April 2009. ] (]) 01:56, 21 April 2009 (UTC)
:::::Wow, where have I seen this comment before.. oh right, it's the way you discourage people from working with me to try and win support for your "one true way". Go away. —] • ] • ] 11:38, 21 April 2009 (UTC)
::::I didn't ask that question, but thanks for continuing to attribute multiple editors work to me. It's flattering. No, those results are, according to {{user|Tony1}}, invalid because of the way they were phrased, remember? Besides, if we can fix the current system (which UC Bill showed we can in large part), I don't see the point in killing it. Further, if we remove date links of the coming year, and then a future auto formatting system is implemented that goes back to using the linking syntax, do we really want to have more bots going around relinking (and re-autoformatting) dates? The community supported "some form", which I take to mean a "working form". So let's fix this system and avoid all the unnecessary bot/script edits. —] • ] • ] 11:38, 21 April 2009 (UTC)
::::*Exactly, where have I seen this comment before...? Finally, I've found the right term this time &ndash; ']'. I think it's you who needs to "Go away". ] (]) 12:53, 21 April 2009 (UTC)
:::::40% of the community supported "some form" of autoformatting. That is a minority view by any stretch of the imagination. ] (]) 13:51, 21 April 2009 (UTC)
:::::: My apologies, Locke, I thought you were part of the team that devised the second RfC in November last. Anyway, you and Tony are entitled to your opinions about the validity or otherwise of the RfCs, but I'm more interested in looking for things we can all agree on. Looking at the comments from those RfCs and from the recent poll, I am convinced that using links to format dates was the one autoformatting markup that was near-universally rejected. I really hoped you would be able to agree (once more) with that conclusion. The point in killing the current system is that folks don't want it. I understand that you feel if we delink dates now, it will make it harder to re-introduce some other form of date autoformatting in the future, but that probably is not so. Well-formatted, plain text dates (which is what we will have) are not at all difficult for a bot to recognise. Believe it or not, if the community at some point wants a new system of DA that doesn't use link markup, I'm sure Lightbot would set about that task, if required. Heck, I'd write one for you myself if you wanted. More importantly, I'd urge you to consider this: at some point, the community will be asking "After we made our views clear on linked dates, why are they still there in huge numbers?" It is commendable to argue your case; but at some point, the lack of support for that argument will put you in the position of a "blocking minority". My advice, for what it's worth: Accept that some battles will not be won and look for ways where you can move forward on common ground with all the other editors. Building this encyclopedia needs that approach. Sincerely --] (]) 00:01, 22 April 2009 (UTC)
:::::::Please read ], consensus is not a majority, nor is it determined through polling. We've concluded that the community rejects date links but is indecisive about date auto formatting, the path forward is to disable the links but keep the auto formatting, not throw away both. —] • ] • ] 02:07, 22 April 2009 (UTC)
:::::::* ]The “there is no consensus” argument. ''(*sigh*)'' You seem to be deluding yourself here (and everywhere else), Locke, that you can influence the ArbCom decision. What’s going to happen is going to happen. What are you going to do when the rulings come down(?), appeal to Jimbo? Everyone else but you understands that the community has spoken and this last RfC is just that: the <u>''last''</u> one on this issue. Please. Give it up; it’s over. <span style="white-space:nowrap;">''']''' (])</span> 03:15, 22 April 2009 (UTC)


'''Active''':
== draft status ==
#Casliber
#Cool Hand Luke
#Coren
#FayssalF
#FloNight
#Jayvdb
#Kirill Lokshin
#Newyorkbrad
#Rlevse
#Roger Davies
#Stephen Bain
#Vassyana
#Wizardman


'''Inactive:'''
The draft that has been posted is not ready for voting. There are a number of aspects that need to be discussed. Specifically comments on the "Manual of Style" options will likely help arbitrators gain an appreciation of which option is more appropriate. Also, I will be notifying wikitech-l of the principles "MediaWiki developers", "System administrators", "Open source" and "Deprecation of MediaWiki functionality" - if they see issues with those principles, we can take them over to the Workshop and collaborate on them. <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 04:32, 30 April 2009 (UTC)
#Carcharoth
#Risker


'''Recused''':
== Two concerns ==


}}<!--
Of concern is that the arbitrators cannot vote that the December RFC reaffirmed that DA is undesirable AND that there is consensus that dates should be delinked (contrary to ]). This problem arises from the conflation of the two points in 3.2.
-->{{#ifeq:yes|yes|
'''Active''':
#Cool Hand Luke
#Coren
#FayssalF
#FloNight
#Jayvdb
#Kirill Lokshin
#Newyorkbrad
#Risker
#Rlevse
#Roger Davies
#Stephen Bain
#Vassyana
#Wizardman


'''Recused''':
<blockquote>3.2) Two RFCs held in December 2008 reaffirmed that date autoformatting is undesirable, and that WP:OVERLINKing of dates is not desirable, however consensus has not been found on when dates should be delinked.</blockquote>
#Carcharoth
#Casliber


'''Away or inactive''':
It is noted that the continual incivility of Locke Cole, instances of which were reported on the Evidence page, has been passed over. Perhaps this was inadvertent. ] ] 07:24, 30 April 2009 (UTC)
}}<!--
-->{{#ifeq:|yes|
'''Active''':
#Casliber
#Cool Hand Luke
#Coren
#FayssalF
#FloNight
#Jayvdb
#Kirill Lokshin
#Newyorkbrad
#Rlevse
#Roger Davies
#Stephen Bain
#Vassyana
#Wizardman


'''Recused''':
:Tony, you appear to have not seen the word "when" in proposal 3.2. There are a few sets of working notes that I am pulling together, so there are a number of omissions. <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 07:38, 30 April 2009 (UTC)
#Risker
::John, thanks for your response, and for drawing my attention to the word "when". May I politely request that "when" be more specific, since I took it to mean "in what circumstances"; now I see it could mean "the time onwards from which" or "what ''type'' of date or ''context'' in which a date occurs". May I also ask that there be no confusion among readers concerning whether (tripartite) "full dates" are the referent, or "date fragments" (such as month-day and solitary year items). ] ] 07:50, 30 April 2009 (UTC)


'''Away or inactive''':
:::I will not attempt to clarify it, because the ambiguity in that proposed finding underscores the point being made. I wont mind if another arb rewrites 3.2 or adds an option, but the problem is that if the proposed finding does not appear to be an accurate description of the events, not all arbtritrators will be able to support it.
#Carcharoth
:::I do not believe we are able to find very much conclusive about any of the RFC, especially given the behaviour of the key players. You believe the RFCs laid clear the path for delinking. I do not believe that is true. Your belief that these polls gave you license to behave as you have is what got you into this mess. For starters, I do not hold your poll in high regard from a user conduct point of view, but there is limited value in detailing every user conduct issue in the proposed decision. Despite the underlying problems in the hows and whys of your poll, it only tried to demonstrate disapproval for "Years, months, days/months, and full dates should normally be linked" and the poll results dont even clearly demonstrate that!, much less demonstrate actual approval for any concrete scenarios where a link should exist, and where it should be removed. Unless you can show me something vaguely like an actual ] being put to the community as an RFC, there is no clear definition of the desired changes or intended outcome. You continue to believe that there is. The more recent poll does a far better job of describing where the MOS would say MUST rather than SHOULD or MAY, but that poll wasnt conducted in December. <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 08:37, 30 April 2009 (UTC)
}}
::::Jayvdb, do you have an undisclosed interest in the outcome of this arbitration? Should you have recused yourself from any involvement? Before you answer, take a good look at the recusal statements from Carcharoth and Casliber and then tell me whether you have applied the same scrupulous standard to yourself.--] (]) 10:15, 30 April 2009 (UTC)
:<small>''To update this listing, and scroll down until you find the right list of arbitrators.''</small>
:Yes, I'm also troubled by the omission of anything covering the ] by Tony1 and Lightmouse in the most recent date linking RFC (also on the evidence page). There's also nothing about the off-wiki coordination that's obviously been going on amongst Tony1/HWV258/Dabomb87/Lightmouse/Ohconfucius/Greg L (and perhaps others) to effectively steamroll discussions with their point of view as soon as they're started (I'm not certain, but as I recall a recent ArbCom decision frowned on this kind of behavior) or coordinate edit warring to try and induce editors not on their "side" to violate 3RR. I believe the canvassing shows a complete lack of good faith in the process, and taken in the context of the ongoing behavior shows an unwillingness to abide by community norms. —] • ] • ] 07:57, 30 April 2009 (UTC)
::Not only Locke Cole is being let off easy. The three ultra-hardcore warriors fighting against community consensus over dates, besides LC, are Tennis expert and Septentrionalis PMAnderson; the latter is continuing to attack editors opposed to him using the most vicious and hate-filled language but no mention of him in the Proposed Decision. It is just as I said on the Workshop page: the refusal by Tony1 and others to stoop to their accusers' level and go dumpster diving for examples with which to hang their opponents is being used against them. I lost my faith in Arbcom a long time, this just confirms me. I did not vote in WP:DATEPOLL because I knew what was going to happen.--] (]) 10:32, 30 April 2009 (UTC)


== Mass date delinking, Remedy 1.3 ==
==Major omission==
As far as I can see, there is nothing in the proposed judgment so far to deal with the matter which is at the very heart of the dispute and will repeatedly cause other disputes in the future if something is not done to deal with it - how do we know (in a situation without unanimity) when we have consensus or not? Who decides, and on what basis, and by what process? And what is the point of saying that we must abide by consensus if edits made to enforce (and explicitly justified by) consensus decisions are treated as edit warring just the same as those which knowingly go against consensus? That is surely an untenable position. If you can't address these fundamental issues, then we won't have learnt anything from all this.--] (]) 09:36, 30 April 2009 (UTC)


I added to balance the concerns that the dispute will resume after the case closes, with the idea that the Community can find a way forward now that the other remedies are in place. ]] 16:06, 6 June 2009 (UTC)
:If a user ever finds that they are reverting or being incivil, and thinking to themselves "this is like the date delinking case; I wish the arbs had given us better guidance", that person has already gone to far, and should step away from the keyboard, go for a long walk (or otherwise occupy themselves), and either decide to a) walk away from the silly mess and do something better with their time, or b) stop reverting and/or being incivil and find a better approach to resolve the dispute, or go to dispute resolution.
:It seems a bit contradictory though; you restrict date linking for a defined period of 6 months (no matter what), and then you say that it shouldn't be done until a Community-approved process has developed. ] (]) 19:02, 6 June 2009 (UTC)
:The revert button is not a form of dispute resolution. The revert button is not an means of keeping consensus in the face of opposition by good faith contributors; the ] sequence only includes one revert.
::If it can be misunderstood, it could stand rephrasing; but it is seems clear enough to me: the restriction ''consists'' of the requirement that community approval of any such process be demonstrated to ArbCom before implementation. In other words, either six months or community approval is necessary. ] <small>]</small> 19:14, 6 June 2009 (UTC)
:The vagueness of "consensus" didnt cause this mess. One side became fed up of waiting for the developers to do something about this extremely important issue, and they took out all stops to force consensus, by any means possible. Sadly, the escalation has meant that a few people who were trying to simply keep order ended up engaged in this battle (if only briefly), and have been included in the FoFs and the remedies. I appreciate that this "All editors involved" approach is hard on them, and that is why there is a template for individual user remedies: if the arbitrators decide that the "All editors involved" approach is too hard on those who were not major players, we will replace the "All editors involved" remedy with per-user remedies, which will allow the remedy for each person to be fine tuned based on the level of their involvement.
:I think this is a terrible encroachment on the community. For user conduct, all applicable remedies have been dealt with. But for formatting concerns, if the community comes to consensus and has a plan for moving forward, why should the community have to come to ArbCom first to have it "approved"? Arbcom isn't there to approve content decisions by the community, is it? &ndash; ] <sup>(])</sup> 19:09, 6 June 2009 (UTC)
:My preference is to go with the "All editors involved" remedy and hand out a lighter option to them all (to clear the air), and have stronger user-user remedies for the people who engaged in the incivil behaviour that made this such a minefield. <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 10:37, 30 April 2009 (UTC)
::All ArbCom approves here is the claim that there ''is'' consensus. Since that has been one of the major issues throughout this case, it seems only sensible to have a witness that consensus actually exists. ] <small>]</small> 19:14, 6 June 2009 (UTC)
::What does this have to do with the developers? I'm sorry, but the facts here are just wrong. One side wanted to change something to make Misplaced Pages better, in a way which didn't require any developer assistance. They launched discussion, argued their points, got consensus (or thought they did), and went about implementing it. Others objected that there wasn't consensus, so: more discussion, consensus was again confirmed, implementation of the improvements continued. Other side ''still'' disputes the consensus, so they come complaining to ArbCom. How is this whole problem not caused by the vagueness of consensus? If the Arbs seriously think that this needed to have anything to do with the developers, then this is simply incorrect - it is the other opposing side who were urging the developers to do something new, in the (now confirmed) absence of consensus to do it.--] (]) 11:28, 30 April 2009 (UTC)
:::Septentrionalis said what I was going to say, except that there's a possible ambiguity whether it's "and" or "or". As Arbcom remedies are explicitly "indefinite" if longer than a year, I'd have to say that Septentrionalis's interpretation is more accurate than mine. — ] ] 19:19, 6 June 2009 (UTC)
::::Clearly this could use rephrasing: ''For the next six months, any mass delinking of dates must demonstrate, before implementation, to ArbCom that there is community support amounting to ] for the delinking process.''? ] <small>]</small> 19:27, 6 June 2009 (UTC)
::Ah, it appears my statement was based on a misreading. On (much later) re-reading, I retract my objection and apologize for the confusion. &ndash; ] <sup>(])</sup> 00:15, 12 June 2009 (UTC)
: This looks fine to me. Mass date delinking doesn't require ArbComs approval, just community consensus and that ArbCom is notified. --] (]) 19:47, 6 June 2009 (UTC)

"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."

Sorry, I stared at it and wondered whether it means:
<blockquote>1.3) No mass date delinking should be performed for six months or until the Committee is notified of a community-approved process for mass date linking—whichever is earlier."</blockquote>

Does it? ] ] 07:54, 7 June 2009 (UTC)
:That is a good paraphrase. The committee will be looking to endorse any community approved process before the community implements it. The more obvious the community approval, the less of a role the committee will play in determining whether the implementation can proceed. <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 10:17, 7 June 2009 (UTC)
::Thanks for clarifying that this is the intended meaning. WRT your additional comment, I wonder whether you might discuss this with Arbitrator Vassyana, who commented after his vote: "This is a good proposal. It creates a preventative restriction that automatically lifts upon notice of a community approved process." <small><span class="autosigned">— Preceding ] comment added by ] (] • ]) 11:57, 7 June 2009 (UTC)</span></small><!-- Template:Unsigned -->
:::As I said above, if community approval is not questionable, this proposal would mean that the committee is bound to lift the restriction as soon as it is notified. I doubt we would automatically lift it if the community approval is contrived and/or the notice is deceptive.
:::Do you agree that ''if'' we are notified of a "community approved process", Vassyana and I have said the same thing? <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 13:34, 7 June 2009 (UTC)
::::Not really: Arb. Vassyana says "automatically lifts upon notice of a community approved process"; you have interpolated greater detail, which may or may not represent what other arbitrators think: "The more obvious the community approval, the less of a role the committee will play in determining whether the implementation can proceed." I'm unsure what to make of it. But at the moment, the more important issue is how ArbCom defines "mass delinking" ... see below. ] ] 16:54, 10 June 2009 (UTC)
Question to arbs: Would this also apply to ''re''-linking? That wouldn't be any more helpful than delinking. ] (]) 21:42, 7 June 2009 (UTC)
: Well the difference is that '''no one''' is arguing that we should link everything or even most things. So anyone who wanted to do "mass" linking would be going against pretty much everyone's consensus and could be addressed quickly. As for the community notifying Arbcom of a consensus, I'd like to suggest that whoever pulls that together is '''not''' one of the named parties here. Its time for fresh voices and better discussion. ] (]) 21:58, 7 June 2009 (UTC)

Another question: what is the definition of 'mass delinking'? Back in February Arb Jayvdb
<blockquote>
If you are consciously removing each bracket, and edit articles at a rate which is consistent with that, the injunction doesnt restrict you. The injunction doesnt completely prohibit the use of scripts, however editors should not be primarily focused on delinking.
</blockquote>

But at different times I've ended up blocked by one admin for exactly that sort of editing - delinking in the course of my normal gnoming activities - and also not blocked by another admin for exactly the same sort of editing. And Arb Wizardman has perfomed this sort of editing but escaped censure. So we need clarification of what's allowed and what's not. ] (]) 22:27, 7 June 2009 (UTC)

====Three questions for the arbitrators and the community====
In relation to the matter above, dm claimed:
<blockquote>... the difference is that '''no one''' is arguing that we should link everything or even most things. So anyone who wanted to do "mass" linking would be going against pretty much everyone's consensus and could be addressed quickly.</blockquote>

Forgive my cynicism, but User:Kendrick7 went on a brazen campaign of relinking dates during and after the blocking of Colonies Chris for performing his standard gnoming duties. Kendrick7 was reported at the ArbCom enforcement page. Nothing was done about it (admin. said: oh, I didn't catch him in time).
: Tony, in this war, bad things were done by both sides, let's move past specific incidents and look at the bigger picture. I have no problem with the proposal being worded so that both linking and delinking are prohibited, but if there's *one* thing that we can all agree that came out of Ryan's RFC is that there is consensus that some dates may be linked if appropriate, but not all dates, nor even most dates. Can you point to anyone who's been arguing for more linking than that since Ryan's RFC? ] (]) 08:55, 8 June 2009 (UTC)
::This has little to do with the matter I have raised. "Relinking" has been removed from the wording. Why? ] ] 16:54, 10 June 2009 (UTC)
:*Tony's comments and concerns above are, I would say, a natural reaction to the rather poisoned atmosphere which surrounds the case. Your reaction is understandable, but the fears are symptomatic not only of the absence of trust in the linkers, but questions over the justice of the meandering process itself. ] (]) 09:08, 8 June 2009 (UTC)
::*And yes, there is at least one editor who continues to talk about retaining all square brackets around dates. ] (]) 09:11, 8 June 2009 (UTC)
:::*However, no editor has advocated linking all dates. Please do not try to deceive the community by asking if they do or don't want date links if you really wanting something else removed (the square brackets; the markup). There is a simpler software solution to removing date links that doesn't involve the use of scripts/bots to perform the operation. It also leaves open the possibility of forcing date links where such links are intentional. All the while this leaves open the door for fixing auto formatting (something community desires in some form, and has not rejected outright except in its current incarnation). —] • ] • ] 10:51, 8 June 2009 (UTC)
I'd like to know:
#why the reference to ''re''linking in the "temporary" injunction has been removed from the current proposal,
#why, despite persistant problems for admins and editors alike in defining "mass delinking"—and apparent injustices—the term remains vague in the proposal; and
#how the ArbCom policy, which is very clear under "Injunctions" that such measures have effect only during a case, mandates what appears to be a huge expansion of ArbCom's power.] ] 07:42, 8 June 2009 (UTC)

:*You know that one of the big problems all throughout this case has been scope creep... ] (]) 08:34, 8 June 2009 (UTC)

::*Frankly I wish the scope had been expanded to cover all of MOS at the outset (and at least one arbitrator agreed when he accepted this case); the behavioral patterns (off-wiki ] and cabal-like behavior) become more obvious if you look at ''other'' disputes at MOS. —] • ] • ] 10:51, 8 June 2009 (UTC)

===to be clear...===
To be clear, ArbCom is taking the position of judging whether or not a consensus exists for implementation in the desire of promoting peace? <span style="background-color: maroon; color: white">]</span>&nbsp;<sup>]</sup> 23:06, 7 June 2009 (UTC)
:I think so, and the consensus would be formed at another ]. ] (]) 23:13, 7 June 2009 (UTC)
::Dabomb, I should have been more specific (nothing against you personally): I'd like to hear an Arbitrator's opinion on the matter just to make sure I'm understanding this correctly. <span style="background-color: maroon; color: white">]</span>&nbsp;<sup>]</sup> 08:16, 12 June 2009 (UTC)

== Motion 1.3: the meaning of "mass delinking" is still unclear ==

I do believe that if ArbCom is to take the extraordinary step of imposing restrictions on the entire WPian community, including anyone in the world who visits and makes an edit, that the meaning of the term "mass delinking" needs to be clarified, either in the wording of the motion or here. Admins and other editors deserve to know where the boundaries lie. By contrast, the operation of the temporary injunction was marred by inconsistency in the application of blocking for alleged breaches. That is good for no one.

I believe it is reasonable for the community to assume that , as Colonies Chris cites above, will pertain:
<blockquote>
"If you are consciously removing each bracket, and edit articles at a rate which is consistent with that, the injunction doesn't restrict you. The injunction doesn't completely prohibit the use of scripts, however editors should not be primarily focused on delinking."
</blockquote>

I'm sorry to nit-pick, but the devil is in the detail, and feedback on a few solid examples would help admins and other editors to get it right.

Are the following examples acceptable? In each scenario, no note is left on the article talk page by the unlinking editor, before or after his/her edit. The unlinking editor politely discusses any related issue if ever raised on her/his talk page concerning such edits. If the date links are reinstated by another editor, the unlinking editor is polite and does not challenge the reverter.
#The editor performs a copy-edit to improve the language/style of a medium- to large-size article by treating about 10 words or phrases (let's say from eight to 12 on average), and as well, unlinks the full (month-day-year) dates in the article. The process takes 5–10 minutes. The editor does this on average '''three''' times a day.
#Same as (1.), except that no full dates are linked; instead, the editor copy-edits and unlinks isolated month-day and year items that s/he considers do not pass the relevance test that the community endorsed (now in MOSNUM and MOSLINK). Average '''three''' times a day.
#Same as (1. or 2.), but an average of '''ten''' articles a day.
#The editor unlinks only full and apparently irrelevant dm or year items ''without associated article improvement'' in an average of '''one''' article a day, but treats an average of, say, three other articles each day in which date unlinking is ''not'' involved.
#Same as (5.), but an average of '''three''' articles and three other articles a day, respectively.
#A more prolific wikignome treats '''16''' articles a day, four minutes on each, in which about half ('''eight''') might involve at least one unlinking of a chronological item.
These examples seem to me not to represent the campaign of "mass unlinking" that ArbCom might be concerned would run the risk of causing disruption. Can ArbCom please comment so the community knows where it stands? ] ] 16:54, 10 June 2009 (UTC)

:All six seem acceptable to me, although I would not encourage 4 & 5; generally speaking, edits whose ''only'' purpose is to unlink dates would best be made after the relevant guidelines had been adopted and stabilized. ]&nbsp;<sup>]]&nbsp;]]</sup> 13:56, 11 June 2009 (UTC)

:Agree with Kirill assessment of the situation. ]] 15:09, 11 June 2009 (UTC)
:I'll third that. None of the examples are "mass unlinking" by any reasonable interpretation of the phrase, although edits that ''only'' unlink dates might be unwise at this time for different reasons. &mdash;&nbsp;]&nbsp;<sup>]</sup> 17:59, 11 June 2009 (UTC)
:Per Kirill. -- ] - <small><sup>]</sup></small> 18:27, 11 June 2009 (UTC)

:An editor who does "6" on a regular basis could be crossing the line if they delink every date/year/century from those eight pages. If they are leaving the most important links, or adding links to "xxxx in science", they should be fine provided they don't edit war. <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 00:06, 12 June 2009 (UTC)

Two more examples of clarification needed:
#A user who is about to submit an article or list to FAC (]) or FLC (]) delinks the dates in the article to comply with the criteria for those processes. The user does not make any other changes in that edit, but does not proceed to delink dates in any other article. I think an exception can be made for that instance also.
#A reviewer of an FAC or FLC delinks the dates in the article/list that they are reviewing. They do not make any more changes in terms of edits to that article, but their delinking is made in conjuntion with a full list of suggestions on how to improve the article/list at the FAC/FLC page. The reviewer does not delink dates in any other article. ] (]) 17:24, 10 June 2009 (UTC)

:Both of those look fine as well, although they can obviously be gamed by someone sufficiently motivated; if someone submits a hundred lists to FLC per day, delinking them as they go, that would be problematic. It may be better to frame the first one as "a significant editor of an article or list who is about to submit it...". ]&nbsp;<sup>]]&nbsp;]]</sup> 13:56, 11 June 2009 (UTC)
::I would report such a person myself, in view of the need to regain trust among editors on the issue. A hundred nominations to FLC by one editor in a month would be laughed out of the house on the basis of compliance with the criteria, in any case. I think we are safe from such abuse. ] ] 14:49, 11 June 2009 (UTC)
:::Agree with Kirill's comments. ]] 15:09, 11 June 2009 (UTC)
:::Per Kirill and also agree with Tony. -- ] - <small><sup>]</sup></small> 18:27, 11 June 2009 (UTC)
::::Thanks to the arbitrators for their timely and reasonable replies. I'll second Tony in saying (as a very active editor at FLC and fairly active at FAC) that no editor with any bit of ] would do that (what Kirill described) and expect to get away with it. ] (]) 20:17, 11 June 2009 (UTC)
:I agree with Kirill - featured review forums are heavily trafficked, so these delinking scenarios have plenty of careful eyes on them, lots of discussion, and the process itself limits the number of articles affected. <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 00:11, 12 June 2009 (UTC)
===More clarification requested on the injunction===
In the light of the answers above, here is a very specific question. Suppose a wikignome performs the following eleven article edits in a single session:

*Around 10 changes, of which one was a delinking of a bare year
*Around 20 changes, of which two were unlinking of decades (the second of which was a duplicate link)
*Over 30 changes, of which 1 was a delinking of an autoformatted date
*7 changes, of which 3 were delinking autoformatted dates
*A large number of changes, including quite a few date fragment unlinkings, almost all of which were bare day-month links
*Around 15 changes, of which 3 were delinking bare years
*6 changes, of which 1 was delinking an autoformatted date
*7 changes, of which 1 was delinking an autoformatted date
*9 changes, of which 2 were delinking autoformatted dates
*13 changes, of which one was delinking a bare year, 2 were delinking autoformatted dates, and one was delinking a date incorrectly autoformatted inside an <nowiki>{{as of}}</nowiki> template
*4 changes, of which 3 were delinking autoformatted dates (the other was a spelling correction).

Is he in operating within the terms of the injunction or is he so grossly violating it that, in the words of Arb Jayvdb, ?

I would appreciate a clear answer to this question as my activities as a wikignome are entirely dependent on it. Arbs may also like to be aware of the consequences of travesty of justice this case has become - one of our best and most prolific gnoming editors, ] has retired in disgust at his mistreatment here. ] (]) 10:06, 14 June 2009 (UTC)

Another valuable editor, ] has also announced his intention to take a long wikibreak as a result of his treatment in this case. But Arbcom seem not to care that they have driven away decent and hardworking editors who won't accept being made victims of this witchhunt. ] (]) 16:42, 14 June 2009 (UTC)

:I agree that ] announcement of a long wikibreak is a terrible loss. He and I worked congenially on his FA article ], the subject of much vandalizm, and never have I seen him react in any but an appropriate manner that was never aggressive. His editing behavior is always of the utmost in civility. It is extremely unfortunate that a few of his edits are seen as been part of this controversial situation regarding delinking. Regards, &mdash;] (]) 16:54, 14 June 2009 (UTC)
::John has left as well. Another one gone. Grown-ups treated like children and sent to the corner, especially when they can see no justice in the punishment, tend to spurn and resent. Is that what ArbCom wants? It's not as though there's an inexhaustible supply of top-notch editors. ] ] 18:34, 14 June 2009 (UTC)

===Colonies Chris is seeking to clarify his wikignoming compliance===
Above, Colonies Chris, one of our leading wikignomes who has applied much skill and experience to the maintenance of WP articles (with admirable politeness) asks what might at first seem like a re-run of the questions asked by dabomb87 and me, and kindly clarified by several arbitrators.

I suspect that now the dust has settled, he may not have been blocked as occurred in March, when uncertainty abounded about the application of the temporary injunction. But either way, he is concerned to know how to comply with the new restriction on "mass date delinking"; such delinking forms only a small part of his gnoming, as you can see in the list above. I know arbitrators have a full agenda, but if Chris could be re-assured that he may undertake his careful work (which he does at a slow, considered pace), that might resolve the matter, which would be of great benefit to the project. ] ] 09:19, 15 June 2009 (UTC)

== Proposed topic ban and restrictions on Tony1 ==

I have not been involved in this dispute. I do occasional work on MOS pages (I have some relevant real life experience), but I am not one of the "regulars" there.

I apologize for commenting at this late stage in these proceedings. It was only yesterday, however, that I looked at the proposed decision for the first time. There is an important consideration that the proposed topic ban and edit restrictions being considered for ] overlook: Tony1 is one of the very, very best stylists and wordsmiths on Misplaced Pages. His user space essays and exercises on writing are of publishable quality, and superior to much of what is professionally publshed. Therefore, banning him ''indefinitely'' from editing ''any'' policy or guideline page on style deprives the Misplaced Pages project of a valuable resource specifically where his expertise is most useful.

Because of the nature of wiki editing, the MOS pages require periodic maintenance: copy editing, organizing, assuring consistency of guidelines throughout all the MOS pages, and wikifying the MOS pages themselves so they serve as models of MOS compliance. Tony1 excels at that work. He also excels at both formulating specific style guidelines and in wording guidelines clearly. It would be self-defeating for Misplaced Pages to deny itself all future contributions by Tony1 to style policies and guidelines.

Evidently, the issues of date linking and auto-formatting arouse extraordinary passions on both sides. I don't condone edit warring on that, or any, issue. However, prohibiting Tony1 from doing constructive work on ''any'' style policy or guideline is overly broad, especially because of the value to Misplaced Pages of Tony1's very many useful contributions in that area. Since the issues of date linking and auto-formatting are so extraordinarily contentious, it should not be necessary to bar Tony1 from ''all'' editing of style policies or guidelines, especially ''indefinitely''. (If ''indefinitely'' is interpreted as ''until there is a change in circumstances'', and Tony1 is broadly barred from the field, what circumstances could change that that would end the restrictions?)

One way to narrow these restrictions, and still retain Tony1's constructive contributions to Misplaced Pages style, would be to make the restrictions specific to date linking and date formatting. Another would be to restrict Tony1, for some reasonable but definite period, from making substantive changes to style guidelines without first obtaining consensus for the change on a talk page. A third would be to prohibit specific conduct that constitutes edit warring.

Please consider the restrictions to be imposed on Tony1 with a view to retaining the benefit that Misplaced Pages derives from his constructive contributions to Misplaced Pages's style guidelines and policies. Thank you. ] ] 18:45, 11 June 2009 (UTC)

:''"what circumstances could change that that would end the restrictions?"'' - Tony could demonstrate conclusively that he is able to play nicely with others. — ] ] 19:44, 11 June 2009 (UTC)

::As I understand remedy 9.3, Tony will be free to contribute anywhere in the MOS talk pages as well as in user space, and I expect that he will continue to do so with his usual skill and expertise. Now that the heat has gone out of the dispute (and I am disappointed that ArbCom has not acknowledged Ryan's ] in achieving much of that), Tony and the other affected parties will have the opportunity by their contributions and behaviour to demonstrate that these restrictions are unnecessary. Because of the nature of "indefinite" restrictions, I sincerely hope that ArbCom will review the situation in a few months time, and be open to hearing an argument that these sanctions could then be profitably lifted. --] (]) 20:27, 11 June 2009 (UTC)
:::I petition for the ability to discuss (although I do not expect to; I've said my piece on what I hope MOS will be, and ]; I'm willing to see what happens). The only evidence for my edit-warring, after all, is , in which the edit-war was with Tony. If that is unacceptable, give me the three months I expect to stay away from the MOS disasters anyway. ] <small>]</small> 21:09, 12 June 2009 (UTC)

== view on automatic editing and other issues ==

I support AKAF's remarks about bots that are now in Archive 2. There are too many bots on Misplaced Pages, and BAG (being composed of bot enthusiasts) aren't really representing the editing community in that it's too willing to delegate functions to bots that really should be done by humans, through policy adjustments or server side code when necessary. The amount of bot drama on WP and in arb cases is increasing steadily and will keep doing so unless something is done. One suggestion for these cases is editing restrictions of the form "so-and-so is prohibited from editing more than 25 mainspace pages in any 24-hour period". This is adapted from a restriction developed for Betacommand through pretty good consensus at an ANI sub-page. It had the advantage of being simple to understand and enforce, and resists typical gaming ploys ("that wasn't a bot, I had 50 browser tabs open" etc.) while leaving enough space for normal human editing.

As a meta-comment, Brad asked why this case is such a clusterfuck. I believe it comes from the culture of ] that Misplaced Pages cultivates, and its acceptance of gaming and wikilawyering. The parties in this case are unusually bad products of that culture. They aren't stupid or clueless, so arbcom should respond sharply. (The genuinely clueless, like BC, are usually met with more forbearance). There is a meme in WP dispute resolution that we ''must'' put up with endless crap from tendentious dicks because otherwise, newbie editors might be dissuaded from editing. To state the obvious, plenty of oldbie editors quit (or retire to the more placid corners of the encyclopedia) because of the crap. Really, among WP's endless rules and policies, "use common sense" doesn't hold nearly enough sway. Constant codification of boundaries is actually counterproductive, not just because editors exist who want to push right up to the boundaries, but because they foster a culture that actually grows such editors. Stop treating WP DR like a court of law with endless "due process"; it isn't one, it has no real investigative or sanctioning powers (the most it can do is throw someone off of a web site, not put them in jail), and nobody really has a right to edit here. Most editors with any sense can work productively even in controversial areas without getting into trouble, so is it really asking too much to tell those unwilling to act sensibly to take their antics elsewhere?

Regarding rude developers, sanctioning off-wiki actions isn't in arbcom's jurisdiction, but as arbcom reports to the WMF I'd presume it's allowed to refer issues to other WMF projects (including mediawiki development) through the Foundation in situations that warrant it. I hadn't felt this was one of those situations but some other posts to the talk archives indicate that it might be. Anyway, it could always simply note this possibility in "principles" and then pass a remedy encouraging everyone to stay civil in all venues. ] (]) 07:47, 12 June 2009 (UTC)
==Note to clerks==
Should the auto-archiving here be turned off, now that this page is likely to go out of use? ] <small>]</small> 14:43, 15 June 2009 (UTC)
:I second the question. ] (]) 21:23, 15 June 2009 (UTC)
::Yes. Done. &mdash;&nbsp;]&nbsp;<sup>]</sup> 12:54, 16 June 2009 (UTC)

Latest revision as of 13:33, 18 February 2023


Archives
Archive 1Archive 2Archive 3

Arbitrators active on this case

Active:

  1. Cool Hand Luke
  2. Coren
  3. FayssalF
  4. FloNight
  5. Jayvdb
  6. Kirill Lokshin
  7. Newyorkbrad
  8. Risker
  9. Rlevse
  10. Roger Davies
  11. Stephen Bain
  12. Vassyana
  13. Wizardman

Recused:

  1. Carcharoth
  2. Casliber

Away or inactive:

To update this listing, edit this template and scroll down until you find the right list of arbitrators.

Mass date delinking, Remedy 1.3

I added Remedy 1.3 to balance the concerns that the dispute will resume after the case closes, with the idea that the Community can find a way forward now that the other remedies are in place. FloNight♥♥♥ 16:06, 6 June 2009 (UTC)

It seems a bit contradictory though; you restrict date linking for a defined period of 6 months (no matter what), and then you say that it shouldn't be done until a Community-approved process has developed. Dabomb87 (talk) 19:02, 6 June 2009 (UTC)
If it can be misunderstood, it could stand rephrasing; but it is seems clear enough to me: the restriction consists of the requirement that community approval of any such process be demonstrated to ArbCom before implementation. In other words, either six months or community approval is necessary. Septentrionalis PMAnderson 19:14, 6 June 2009 (UTC)
I think this is a terrible encroachment on the community. For user conduct, all applicable remedies have been dealt with. But for formatting concerns, if the community comes to consensus and has a plan for moving forward, why should the community have to come to ArbCom first to have it "approved"? Arbcom isn't there to approve content decisions by the community, is it? – Quadell 19:09, 6 June 2009 (UTC)
All ArbCom approves here is the claim that there is consensus. Since that has been one of the major issues throughout this case, it seems only sensible to have a witness that consensus actually exists. Septentrionalis PMAnderson 19:14, 6 June 2009 (UTC)
Septentrionalis said what I was going to say, except that there's a possible ambiguity whether it's "and" or "or". As Arbcom remedies are explicitly "indefinite" if longer than a year, I'd have to say that Septentrionalis's interpretation is more accurate than mine. — Arthur Rubin (talk) 19:19, 6 June 2009 (UTC)
Clearly this could use rephrasing: For the next six months, any mass delinking of dates must demonstrate, before implementation, to ArbCom that there is community support amounting to WP:Consensus for the delinking process.? Septentrionalis PMAnderson 19:27, 6 June 2009 (UTC)
Ah, it appears my statement was based on a misreading. On (much later) re-reading, I retract my objection and apologize for the confusion. – Quadell 00:15, 12 June 2009 (UTC)
This looks fine to me. Mass date delinking doesn't require ArbComs approval, just community consensus and that ArbCom is notified. --Apoc2400 (talk) 19:47, 6 June 2009 (UTC)

"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."

Sorry, I stared at it and wondered whether it means:

1.3) No mass date delinking should be performed for six months or until the Committee is notified of a community-approved process for mass date linking—whichever is earlier."

Does it? Tony (talk) 07:54, 7 June 2009 (UTC)

That is a good paraphrase. The committee will be looking to endorse any community approved process before the community implements it. The more obvious the community approval, the less of a role the committee will play in determining whether the implementation can proceed. John Vandenberg 10:17, 7 June 2009 (UTC)
Thanks for clarifying that this is the intended meaning. WRT your additional comment, I wonder whether you might discuss this with Arbitrator Vassyana, who commented after his vote: "This is a good proposal. It creates a preventative restriction that automatically lifts upon notice of a community approved process." — Preceding unsigned comment added by Tony1 (talkcontribs) 11:57, 7 June 2009 (UTC)
As I said above, if community approval is not questionable, this proposal would mean that the committee is bound to lift the restriction as soon as it is notified. I doubt we would automatically lift it if the community approval is contrived and/or the notice is deceptive.
Do you agree that if we are notified of a "community approved process", Vassyana and I have said the same thing? John Vandenberg 13:34, 7 June 2009 (UTC)
Not really: Arb. Vassyana says "automatically lifts upon notice of a community approved process"; you have interpolated greater detail, which may or may not represent what other arbitrators think: "The more obvious the community approval, the less of a role the committee will play in determining whether the implementation can proceed." I'm unsure what to make of it. But at the moment, the more important issue is how ArbCom defines "mass delinking" ... see below. Tony (talk) 16:54, 10 June 2009 (UTC)

Question to arbs: Would this also apply to re-linking? That wouldn't be any more helpful than delinking. Dabomb87 (talk) 21:42, 7 June 2009 (UTC)

Well the difference is that no one is arguing that we should link everything or even most things. So anyone who wanted to do "mass" linking would be going against pretty much everyone's consensus and could be addressed quickly. As for the community notifying Arbcom of a consensus, I'd like to suggest that whoever pulls that together is not one of the named parties here. Its time for fresh voices and better discussion. dm (talk) 21:58, 7 June 2009 (UTC)

Another question: what is the definition of 'mass delinking'? Back in February Arb Jayvdb stated

If you are consciously removing each bracket, and edit articles at a rate which is consistent with that, the injunction doesnt restrict you. The injunction doesnt completely prohibit the use of scripts, however editors should not be primarily focused on delinking.

But at different times I've ended up blocked by one admin for exactly that sort of editing - delinking in the course of my normal gnoming activities - and also not blocked by another admin for exactly the same sort of editing. And Arb Wizardman has perfomed this sort of editing but escaped censure. So we need clarification of what's allowed and what's not. Colonies Chris (talk) 22:27, 7 June 2009 (UTC)

Three questions for the arbitrators and the community

In relation to the matter above, dm claimed:

... the difference is that no one is arguing that we should link everything or even most things. So anyone who wanted to do "mass" linking would be going against pretty much everyone's consensus and could be addressed quickly.

Forgive my cynicism, but User:Kendrick7 went on a brazen campaign of relinking dates during and after the blocking of Colonies Chris for performing his standard gnoming duties. Kendrick7 was reported at the ArbCom enforcement page. Nothing was done about it (admin. said: oh, I didn't catch him in time).

Tony, in this war, bad things were done by both sides, let's move past specific incidents and look at the bigger picture. I have no problem with the proposal being worded so that both linking and delinking are prohibited, but if there's *one* thing that we can all agree that came out of Ryan's RFC is that there is consensus that some dates may be linked if appropriate, but not all dates, nor even most dates. Can you point to anyone who's been arguing for more linking than that since Ryan's RFC? dm (talk) 08:55, 8 June 2009 (UTC)
This has little to do with the matter I have raised. "Relinking" has been removed from the wording. Why? Tony (talk) 16:54, 10 June 2009 (UTC)
  • Tony's comments and concerns above are, I would say, a natural reaction to the rather poisoned atmosphere which surrounds the case. Your reaction is understandable, but the fears are symptomatic not only of the absence of trust in the linkers, but questions over the justice of the meandering process itself. Ohconfucius (talk) 09:08, 8 June 2009 (UTC)
  • However, no editor has advocated linking all dates. Please do not try to deceive the community by asking if they do or don't want date links if you really wanting something else removed (the square brackets; the markup). There is a simpler software solution to removing date links that doesn't involve the use of scripts/bots to perform the operation. It also leaves open the possibility of forcing date links where such links are intentional. All the while this leaves open the door for fixing auto formatting (something community desires in some form, and has not rejected outright except in its current incarnation). —Locke Coletc 10:51, 8 June 2009 (UTC)

I'd like to know:

  1. why the reference to relinking in the "temporary" injunction has been removed from the current proposal,
  2. why, despite persistant problems for admins and editors alike in defining "mass delinking"—and apparent injustices—the term remains vague in the proposal; and
  3. how the ArbCom policy, which is very clear under "Injunctions" that such measures have effect only during a case, mandates what appears to be a huge expansion of ArbCom's power.Tony (talk) 07:42, 8 June 2009 (UTC)
  • Frankly I wish the scope had been expanded to cover all of MOS at the outset (and at least one arbitrator agreed when he accepted this case); the behavioral patterns (off-wiki collusion and cabal-like behavior) become more obvious if you look at other disputes at MOS. —Locke Coletc 10:51, 8 June 2009 (UTC)

to be clear...

To be clear, ArbCom is taking the position of judging whether or not a consensus exists for implementation in the desire of promoting peace? — BQZip01 —  23:06, 7 June 2009 (UTC)

I think so, and the consensus would be formed at another RfC that is in the works. Dabomb87 (talk) 23:13, 7 June 2009 (UTC)
Dabomb, I should have been more specific (nothing against you personally): I'd like to hear an Arbitrator's opinion on the matter just to make sure I'm understanding this correctly. — BQZip01 —  08:16, 12 June 2009 (UTC)

Motion 1.3: the meaning of "mass delinking" is still unclear

I do believe that if ArbCom is to take the extraordinary step of imposing restrictions on the entire WPian community, including anyone in the world who visits and makes an edit, that the meaning of the term "mass delinking" needs to be clarified, either in the wording of the motion or here. Admins and other editors deserve to know where the boundaries lie. By contrast, the operation of the temporary injunction was marred by inconsistency in the application of blocking for alleged breaches. That is good for no one.

I believe it is reasonable for the community to assume that John Vandenberg's explanation, as Colonies Chris cites above, will pertain:

"If you are consciously removing each bracket, and edit articles at a rate which is consistent with that, the injunction doesn't restrict you. The injunction doesn't completely prohibit the use of scripts, however editors should not be primarily focused on delinking."

I'm sorry to nit-pick, but the devil is in the detail, and feedback on a few solid examples would help admins and other editors to get it right.

Are the following examples acceptable? In each scenario, no note is left on the article talk page by the unlinking editor, before or after his/her edit. The unlinking editor politely discusses any related issue if ever raised on her/his talk page concerning such edits. If the date links are reinstated by another editor, the unlinking editor is polite and does not challenge the reverter.

  1. The editor performs a copy-edit to improve the language/style of a medium- to large-size article by treating about 10 words or phrases (let's say from eight to 12 on average), and as well, unlinks the full (month-day-year) dates in the article. The process takes 5–10 minutes. The editor does this on average three times a day.
  2. Same as (1.), except that no full dates are linked; instead, the editor copy-edits and unlinks isolated month-day and year items that s/he considers do not pass the relevance test that the community endorsed (now in MOSNUM and MOSLINK). Average three times a day.
  3. Same as (1. or 2.), but an average of ten articles a day.
  4. The editor unlinks only full and apparently irrelevant dm or year items without associated article improvement in an average of one article a day, but treats an average of, say, three other articles each day in which date unlinking is not involved.
  5. Same as (5.), but an average of three articles and three other articles a day, respectively.
  6. A more prolific wikignome treats 16 articles a day, four minutes on each, in which about half (eight) might involve at least one unlinking of a chronological item.

These examples seem to me not to represent the campaign of "mass unlinking" that ArbCom might be concerned would run the risk of causing disruption. Can ArbCom please comment so the community knows where it stands? Tony (talk) 16:54, 10 June 2009 (UTC)

All six seem acceptable to me, although I would not encourage 4 & 5; generally speaking, edits whose only purpose is to unlink dates would best be made after the relevant guidelines had been adopted and stabilized. Kirill  13:56, 11 June 2009 (UTC)
Agree with Kirill assessment of the situation. FloNight♥♥♥ 15:09, 11 June 2009 (UTC)
I'll third that. None of the examples are "mass unlinking" by any reasonable interpretation of the phrase, although edits that only unlink dates might be unwise at this time for different reasons. — Coren  17:59, 11 June 2009 (UTC)
Per Kirill. -- FayssalF - 18:27, 11 June 2009 (UTC)
An editor who does "6" on a regular basis could be crossing the line if they delink every date/year/century from those eight pages. If they are leaving the most important links, or adding links to "xxxx in science", they should be fine provided they don't edit war. John Vandenberg 00:06, 12 June 2009 (UTC)

Two more examples of clarification needed:

  1. A user who is about to submit an article or list to FAC (featured article candidate) or FLC (featured list candidate) delinks the dates in the article to comply with the criteria for those processes. The user does not make any other changes in that edit, but does not proceed to delink dates in any other article. I think an exception can be made for that instance also.
  2. A reviewer of an FAC or FLC delinks the dates in the article/list that they are reviewing. They do not make any more changes in terms of edits to that article, but their delinking is made in conjuntion with a full list of suggestions on how to improve the article/list at the FAC/FLC page. The reviewer does not delink dates in any other article. Dabomb87 (talk) 17:24, 10 June 2009 (UTC)
Both of those look fine as well, although they can obviously be gamed by someone sufficiently motivated; if someone submits a hundred lists to FLC per day, delinking them as they go, that would be problematic. It may be better to frame the first one as "a significant editor of an article or list who is about to submit it...". Kirill  13:56, 11 June 2009 (UTC)
I would report such a person myself, in view of the need to regain trust among editors on the issue. A hundred nominations to FLC by one editor in a month would be laughed out of the house on the basis of compliance with the criteria, in any case. I think we are safe from such abuse. Tony (talk) 14:49, 11 June 2009 (UTC)
Agree with Kirill's comments. FloNight♥♥♥ 15:09, 11 June 2009 (UTC)
Per Kirill and also agree with Tony. -- FayssalF - 18:27, 11 June 2009 (UTC)
Thanks to the arbitrators for their timely and reasonable replies. I'll second Tony in saying (as a very active editor at FLC and fairly active at FAC) that no editor with any bit of common sense would do that (what Kirill described) and expect to get away with it. Dabomb87 (talk) 20:17, 11 June 2009 (UTC)
I agree with Kirill - featured review forums are heavily trafficked, so these delinking scenarios have plenty of careful eyes on them, lots of discussion, and the process itself limits the number of articles affected. John Vandenberg 00:11, 12 June 2009 (UTC)

More clarification requested on the injunction

In the light of the answers above, here is a very specific question. Suppose a wikignome performs the following eleven article edits in a single session:

  • Around 10 changes, of which one was a delinking of a bare year
  • Around 20 changes, of which two were unlinking of decades (the second of which was a duplicate link)
  • Over 30 changes, of which 1 was a delinking of an autoformatted date
  • 7 changes, of which 3 were delinking autoformatted dates
  • A large number of changes, including quite a few date fragment unlinkings, almost all of which were bare day-month links
  • Around 15 changes, of which 3 were delinking bare years
  • 6 changes, of which 1 was delinking an autoformatted date
  • 7 changes, of which 1 was delinking an autoformatted date
  • 9 changes, of which 2 were delinking autoformatted dates
  • 13 changes, of which one was delinking a bare year, 2 were delinking autoformatted dates, and one was delinking a date incorrectly autoformatted inside an {{as of}} template
  • 4 changes, of which 3 were delinking autoformatted dates (the other was a spelling correction).

Is he in operating within the terms of the injunction or is he so grossly violating it that, in the words of Arb Jayvdb, "the block for 24 hrs is extremely light, and he should have been blocked for much longer for flagrantly ignoring the injunction."?

I would appreciate a clear answer to this question as my activities as a wikignome are entirely dependent on it. Arbs may also like to be aware of the consequences of travesty of justice this case has become - one of our best and most prolific gnoming editors, User:John has retired in disgust at his mistreatment here. Colonies Chris (talk) 10:06, 14 June 2009 (UTC)

Another valuable editor, User:HJensen has also announced his intention to take a long wikibreak as a result of his treatment in this case. But Arbcom seem not to care that they have driven away decent and hardworking editors who won't accept being made victims of this witchhunt. Colonies Chris (talk) 16:42, 14 June 2009 (UTC)

I agree that User:HJensen announcement of a long wikibreak is a terrible loss. He and I worked congenially on his FA article Frank Zappa, the subject of much vandalizm, and never have I seen him react in any but an appropriate manner that was never aggressive. His editing behavior is always of the utmost in civility. It is extremely unfortunate that a few of his edits are seen as been part of this controversial situation regarding delinking. Regards, —Mattisse (Talk) 16:54, 14 June 2009 (UTC)
John has left as well. Another one gone. Grown-ups treated like children and sent to the corner, especially when they can see no justice in the punishment, tend to spurn and resent. Is that what ArbCom wants? It's not as though there's an inexhaustible supply of top-notch editors. Tony (talk) 18:34, 14 June 2009 (UTC)

Colonies Chris is seeking to clarify his wikignoming compliance

Above, Colonies Chris, one of our leading wikignomes who has applied much skill and experience to the maintenance of WP articles (with admirable politeness) asks what might at first seem like a re-run of the questions asked by dabomb87 and me, and kindly clarified by several arbitrators.

I suspect that now the dust has settled, he may not have been blocked as occurred in March, when uncertainty abounded about the application of the temporary injunction. But either way, he is concerned to know how to comply with the new restriction on "mass date delinking"; such delinking forms only a small part of his gnoming, as you can see in the list above. I know arbitrators have a full agenda, but if Chris could be re-assured that he may undertake his careful work (which he does at a slow, considered pace), that might resolve the matter, which would be of great benefit to the project. Tony (talk) 09:19, 15 June 2009 (UTC)

Proposed topic ban and restrictions on Tony1

I have not been involved in this dispute. I do occasional work on MOS pages (I have some relevant real life experience), but I am not one of the "regulars" there.

I apologize for commenting at this late stage in these proceedings. It was only yesterday, however, that I looked at the proposed decision for the first time. There is an important consideration that the proposed topic ban and edit restrictions being considered for Tony1 overlook: Tony1 is one of the very, very best stylists and wordsmiths on Misplaced Pages. His user space essays and exercises on writing are of publishable quality, and superior to much of what is professionally publshed. Therefore, banning him indefinitely from editing any policy or guideline page on style deprives the Misplaced Pages project of a valuable resource specifically where his expertise is most useful.

Because of the nature of wiki editing, the MOS pages require periodic maintenance: copy editing, organizing, assuring consistency of guidelines throughout all the MOS pages, and wikifying the MOS pages themselves so they serve as models of MOS compliance. Tony1 excels at that work. He also excels at both formulating specific style guidelines and in wording guidelines clearly. It would be self-defeating for Misplaced Pages to deny itself all future contributions by Tony1 to style policies and guidelines.

Evidently, the issues of date linking and auto-formatting arouse extraordinary passions on both sides. I don't condone edit warring on that, or any, issue. However, prohibiting Tony1 from doing constructive work on any style policy or guideline is overly broad, especially because of the value to Misplaced Pages of Tony1's very many useful contributions in that area. Since the issues of date linking and auto-formatting are so extraordinarily contentious, it should not be necessary to bar Tony1 from all editing of style policies or guidelines, especially indefinitely. (If indefinitely is interpreted as until there is a change in circumstances, and Tony1 is broadly barred from the field, what circumstances could change that that would end the restrictions?)

One way to narrow these restrictions, and still retain Tony1's constructive contributions to Misplaced Pages style, would be to make the restrictions specific to date linking and date formatting. Another would be to restrict Tony1, for some reasonable but definite period, from making substantive changes to style guidelines without first obtaining consensus for the change on a talk page. A third would be to prohibit specific conduct that constitutes edit warring.

Please consider the restrictions to be imposed on Tony1 with a view to retaining the benefit that Misplaced Pages derives from his constructive contributions to Misplaced Pages's style guidelines and policies. Thank you. Finell (Talk) 18:45, 11 June 2009 (UTC)

"what circumstances could change that that would end the restrictions?" - Tony could demonstrate conclusively that he is able to play nicely with others. — Hex (❝?!❞) 19:44, 11 June 2009 (UTC)
As I understand remedy 9.3, Tony will be free to contribute anywhere in the MOS talk pages as well as in user space, and I expect that he will continue to do so with his usual skill and expertise. Now that the heat has gone out of the dispute (and I am disappointed that ArbCom has not acknowledged Ryan's WP:DATEPOLL in achieving much of that), Tony and the other affected parties will have the opportunity by their contributions and behaviour to demonstrate that these restrictions are unnecessary. Because of the nature of "indefinite" restrictions, I sincerely hope that ArbCom will review the situation in a few months time, and be open to hearing an argument that these sanctions could then be profitably lifted. --RexxS (talk) 20:27, 11 June 2009 (UTC)
I petition for the ability to discuss (although I do not expect to; I've said my piece on what I hope MOS will be, and some agreed; I'm willing to see what happens). The only evidence for my edit-warring, after all, is this ill-advised sequence, in which the edit-war was with Tony. If that is unacceptable, give me the three months I expect to stay away from the MOS disasters anyway. Septentrionalis PMAnderson 21:09, 12 June 2009 (UTC)

view on automatic editing and other issues

I support AKAF's remarks about bots that are now in Archive 2. There are too many bots on Misplaced Pages, and BAG (being composed of bot enthusiasts) aren't really representing the editing community in that it's too willing to delegate functions to bots that really should be done by humans, through policy adjustments or server side code when necessary. The amount of bot drama on WP and in arb cases is increasing steadily and will keep doing so unless something is done. One suggestion for these cases is editing restrictions of the form "so-and-so is prohibited from editing more than 25 mainspace pages in any 24-hour period". This is adapted from a restriction developed for Betacommand through pretty good consensus at an ANI sub-page. It had the advantage of being simple to understand and enforce, and resists typical gaming ploys ("that wasn't a bot, I had 50 browser tabs open" etc.) while leaving enough space for normal human editing.

As a meta-comment, Brad asked why this case is such a clusterfuck. I believe it comes from the culture of ambiguity intolerance that Misplaced Pages cultivates, and its acceptance of gaming and wikilawyering. The parties in this case are unusually bad products of that culture. They aren't stupid or clueless, so arbcom should respond sharply. (The genuinely clueless, like BC, are usually met with more forbearance). There is a meme in WP dispute resolution that we must put up with endless crap from tendentious dicks because otherwise, newbie editors might be dissuaded from editing. To state the obvious, plenty of oldbie editors quit (or retire to the more placid corners of the encyclopedia) because of the crap. Really, among WP's endless rules and policies, "use common sense" doesn't hold nearly enough sway. Constant codification of boundaries is actually counterproductive, not just because editors exist who want to push right up to the boundaries, but because they foster a culture that actually grows such editors. Stop treating WP DR like a court of law with endless "due process"; it isn't one, it has no real investigative or sanctioning powers (the most it can do is throw someone off of a web site, not put them in jail), and nobody really has a right to edit here. Most editors with any sense can work productively even in controversial areas without getting into trouble, so is it really asking too much to tell those unwilling to act sensibly to take their antics elsewhere?

Regarding rude developers, sanctioning off-wiki actions isn't in arbcom's jurisdiction, but as arbcom reports to the WMF I'd presume it's allowed to refer issues to other WMF projects (including mediawiki development) through the Foundation in situations that warrant it. I hadn't felt this was one of those situations but some other posts to the talk archives indicate that it might be. Anyway, it could always simply note this possibility in "principles" and then pass a remedy encouraging everyone to stay civil in all venues. 67.122.209.126 (talk) 07:47, 12 June 2009 (UTC)

Note to clerks

Should the auto-archiving here be turned off, now that this page is likely to go out of use? Septentrionalis PMAnderson 14:43, 15 June 2009 (UTC)

I second the question. Newyorkbrad (talk) 21:23, 15 June 2009 (UTC)
Yes. Done. — Coren  12:54, 16 June 2009 (UTC)