This user has autopatrolled rights on the English Wikipedia.
This user has file mover rights on the English Wikipedia
This user has pending changes reviewer rights on the English Wikipedia.
This user has rollback rights on the English Wikipedia.
From Wikipedia, the free encyclopedia
John Cline
Originally known as user:My76Strat


Userpage


Talkpage


Aboutme


Mypages


Myawards


Subpages


Openone


Mytools

Open discussions Information

Closed discussions Information

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


RfC for reviewer permission criteria

At Wikipedia:WikiProject Articles for creation/RfC Reviewer permission a consensus was reached to introduce a permission system for reviewers. The topics on what the permission threshold should be, and how it would be implemented, were deliberately left open.

  1. This RfC discusses suggestions for the threshold of experience for users to demonstrate that they are adequately versed in the policies and guidelines involved for an article that can exist uncontentiously in mainspace.
  2. This RfC does not discuss how this threshold will be granted and/or implemented. That will be the topic of a further discussion, when the threshold itself has been established.
  3. This RfC is not a vote. Participants are invited to discuss what would be a reasonable threshold. The closer will assess the outcome based on the discussion.
  4. Consensus has been reached for this permission, this RfC is not for rediscussing whether a permission is needed.

Background examples

  • Reviewer (Pending Changes Reviewer): Quick check to ensure edits don't contain vandalism, violations of the policy on living people, copyright violations, or other obviously inappropriate content. The threshold is deliberately low but Reviewers are not expected to be subject experts and their review is not a guarantee in any way of an error-free article. They are expected to have a reasonable editing history, distinguish what is and what is not vandalism, and be familiar with basic content policies.

Reviewer permission are specified as follows:

  1. You have an account, and routinely edit.
  2. You have a reasonable editing history – as a guide, enough edits that a track record can be established.
  3. You have read our policy on vandalism and understand what is and what is not vandalism.
  4. You are familiar with the basic content policies: Biographies of living persons, Neutral point of view, No original research, Verifiability and What Wikipedia is not.
  5. You are familiar with the basic legal policy: Wikipedia:Copyrights.
  6. You have read the guideline on reviewing.
Permission is granted by an admin.
  • Rollbacker: While there is no fixed requirement, a request is unlikely to be successful without a contribution history that demonstrates an ability to distinguish well intentioned edits with minor issues from unconstructive vandalism. Users with 200 edits (generally discounting those to their own user space) can apply for training to the WP:CVUA. Admins rarely grant the tool for less than a clear run of at least 100 reverts of clearly identifiable vandalism without errors. Significant experience is needed to identify the kind of edits that may not appear to vandalism at first sight e.g. inappropriate edits missed by the bots and abuse filters.
Permission is granted by an admin.
  • Stiki: The account must have either: (1) the rollback permission/right, (2) at least 1000 article edits (in the article namespace, not talk/user pages), or be approved after discussion with the developer.
  • Huggle: Requires rollback permission in order to function but does not otherwise have an approvals system.
  • AWB: Users must be added to a whitelist in order to use AWB. Only admins can edit the whitelist, and admins automatically have access. As a general rule, only users with more than 500 mainspace edits will be registered, and admins tend to only give access if a user has specified a task they want to use AWB for.

Discussion

Suggestion by Kudpung

  • I'll start the ball rolling here with a fairly low threshold. Having seen plenty of the kind of errors that are made by editors who review AfC, I suggest that the minimum should be based on candidates having the choice of satisfying either of these two criteria (but not a lower mix of each).
1. Must have both Reviewer and Rollbacker rights, and have demonstrated that they have used these correctly within a minimum of 500 mainspace edits, and a minimum of one month tenure.
or
2. Must have patrolled at least 200 pages at WP:New pages patrol without recent error and demonstrated that they are a) familiar with the tags and deletion criteria offered by the Page Curation Toolbar without error. b) made significant use of the 'message to the creator' tool.
3. Above all, candidates must have demonstrated that they understand WP:PROD, WP:AfD, and WP:Notability, and are able to interact with other users in a polite, friendly, and helpful manner.
Kudpung กุดผึ้ง ( talk) 02:25, 18 October 2013 (UTC)
Does Page Curation need to be singled out? Don't a lot of users do NPP with other tools, like Twinkle? I think you should refer to NPP-related tags and criteria in general. Also, I think reviewer/rollbacker would be fine with one-or-the-other, rather than needing both. Jackmcbarn ( talk) 03:21, 18 October 2013 (UTC)
NPP should only be done nowadays with the Special:NewPagesFeed which does not use Twinkle. There may be a few editors still using the old page feed, but that system has been redundant now for a long time. Kudpung กุดผึ้ง ( talk) 04:39, 18 October 2013 (UTC)
I happened to just ask Dragonfly67 on IRC the other day, and he doesn't use the curation tool... Not implying one way or the other whether or not he would want AfC reviewer (yes, I obviously realize as an admin it doesn't really make much difference), just wondering if someone like him that doesn't use page curation but has patrolled thousands of pages should really be excluded. TL;DR, I think that saying that curation tool use is a requirement of proper page patrolling is inaccurate. Technical 13 ( talk) 04:49, 18 October 2013 (UTC)
Ditto... I patrol off WP:SCV and #wikipedia-en-spam. What we are looking for are speedy deletion accuracy and PROD/AFD nominations getting deleted. MER-C 05:19, 18 October 2013 (UTC)
MER-C, That's probably what you do, and naturally you are perfectly free to pick and choose how, what, and when you do, but patrollers should be aware of the recommendations at WP:NPP otherwise they are not really helping the project. I, for example, generally only look for blatant candidates for ultra speedy - and some of them I then summarily delete already - leaving the rest for other patrollers to figure out and learn from; I certainly don't plod systematically through the list, well, not these days - three years ago I cleared about 20,000 from the backlog in as many days, but I guess I was still full of Wikithusiasm. IMHO the new page feed and its curation tool is a brilliant piece of software; the only problem is that it's only any good in the hands of users who know what they are doing. Kudpung กุดผึ้ง ( talk) 07:02, 18 October 2013 (UTC)
  • I would like to see a certain number of articles created, perhaps 20, as a criterion for this user right. This would allow a fair assessment of the user's understanding with regard to article creation in my opinion. Additionally, I think the right could be bundled with autopatrolled just as well as sysop.— John Cline ( talk) 03:23, 18 October 2013 (UTC)
While I like the idea of requiring some article creation experience I'm afraid 20 is far too high a threshold. I had been active here for 5 years and logged about 20,000 edits by the time I created my 20th article. Many of the most suitable candidates for AfC reviewer are those editors who have a lot of "wikignome"-editing experience - they generally don't create many articles. In any case "articles" is not a very useful unit of measurement - because both a 50-word stub about a village in Uzbekistan and a comprehensive GA-rated article about an obscure disease count as "1". I would give the right to the creator of one comprehensive article before I give it to a stub-mill with hundreds of three-sentence stubs, that just barely scrape past the minimum standards, on their scorecard. Roger (Dodger67) ( talk) 06:47, 18 October 2013 (UTC)
Dodger67, for 'Autopatrolled' the default criterion is 50 articles. However, admins review these carefully, discount redirects and dab pages, and and don't generally accord the right to '100 stub wonders'. 1-line stubs about one specific topic area do not demonstrate a sufficiently broad knowledge of policies and guidelines, especially the mass creators who use AWB or their first stub as a template. Kudpung กุดผึ้ง ( talk) 09:26, 18 October 2013 (UTC)
When I saw the topic, I was going to suggest article creation as a possible prerequisite. If as high as 20, I'd recommend that it replace one or more other requirements. If standalone, I would recommend a lower threshold, perhaps 5, but those articles must demonstrate knowledge of notability, reliability, independence, etc. If more than 5 articles are created, not all need to pass this criteria (some should could be stubs), but there must be 5 that do, and there must not be recent creations that demonstrate lack of knowledge in the critical areas. 78.26 ( I'm no IP, talk to me!) 12:09, 18 October 2013 (UTC)
That largely echos my thinking. Article creation is good, but expansion of a stub to a full-blown article may be worth as much or more.-- SPhilbrick (Talk) 13:40, 18 October 2013 (UTC)
While creating content within an existing article is an important measure, it presumes the existence of a notable article, rife for improvement. Article creation better demonstrates the all important ability of identifying notable subjects. AfD participation is perhaps another good way to gage clue in this regard.— John Cline ( talk) 14:03, 18 October 2013 (UTC)
  • Question as I'm seeing a lot of numbers or other rights being required here, which would be a major hurdle for many existing reviewers without of "grandfathering" of some kind. I'm not saying that these requirements are necessarily bad, just that they may be overzealous. Along the same lines as WP:CVUA for Rollbacker, I would like to think that a user without any of Reviewer or Rollbacker or 500 mainspace edits or 200 WP:New pages patrol or 20 created articles but who has demonstrated that they understand all of the proper policies (especially WP:Notability) via an AfC specific training program would be eligible. Technical 13 ( talk) 03:35, 18 October 2013 (UTC)
  • Kudpung said:

    Above all, candidates must have demonstrated that they understand WP:PROD, WP:AfD, and WP:Notability, and are able to interact with other users in a polite, friendly, and helpful manner.

You nailed it right there.
Any counts or other criteria we come up with are just ways to tell those who have done this from those who haven't, without having to spend hours wading through prospective reviewer's wiki-histories. davidwr/( talk)/( contribs) 00:47, 19 October 2013 (UTC)
@ Kudpung: I hope you don't mind, I turned it into the {{ tmbox}} at the top. davidwr/( talk)/( contribs) 01:08, 19 October 2013 (UTC)
I mind. Promoting one person's comment above all others with a big flashy spotlight is not conducive to consensus-building. -- ShinmaWa( talk) 01:19, 19 October 2013 (UTC)

Suggestion by Anne Delong

  • There was a lot of concern during the previous discussion that this would be a privilege which would be bestowed on some editors by others. This is how I envision the process working:
  • The Afc helper script be changed to only function for those on the Wikiproject AfC reviewer list.
  • The list could be on a protected page so that someone with regular reviewer rights would be needed to add names.
  • On request, an editor would automatically be added if they had reached a certain level of editing (for example, 2000 edits and one year of experience).
  • Editors wanting to review sooner or with less experience would have to meet the lower numbers of edits and time served mentioned above, and also convince a reviewer to add them to the list by demonstrating such items as Kudpung has mentioned above.
  • Names could be removed if problems cropped up (such as frivolous or frequently incorrect reviews).
The reason I suggest the addition of an automatic pass level is that I believe that many of the people who supported the previous Rfc only did so because they believed that it would be an automatic rather than requested permission. — Anne Delong ( talk) 03:50, 18 October 2013 (UTC)
Consensus not to implement, due to concerns about threshold being too high. -- Mdann 52 talk to me! 13:32, 13 January 2014 (UTC) ( non-admin closure)
The following discussion has been closed. Please do not modify it.
  • There were absolutely no mentions in the proposal on the previous RfC that the right would be automatically conferred. Criteria for the right, and how it would be granted were deliberately left open for further discussions. This discussion is to determine those criteria. What was clear on that RfC was the typical phenomenon on Wkipedia discussions that many people, especially those commenting later, do not fully read the preamble and proposition correctly and the following discussion and go off at half-tack - even introducing items that were expressly not required in the discussion.
I didn't mention it above, but but I would assume that current active reviewers who have not demonstrated any controversial issues with their reviewing would be grandfathered in.
I think requiring 20 article creations would be setting the bar too high. This is not required for NPP which has a similar need for knowledge of policies and practice but which does not require a permission (yet) and still suffers from the same problems: not enough patrollers, and often too little experience. I know I keep drawing these comparisons with NPP but I do feel it's relevant. Kudpung กุดผึ้ง ( talk) 04:31, 18 October 2013 (UTC)
  • Oppose criteria 2 New pages patrol is quite tedious and many users that could do it choose not to. I have to believe that asking people to do 300 NPPs will deter a ton of people from asking for AfC reviewer permission because there are plenty of other things most people would rather do than spend 20 hours doing NPP. Sven Manguard Wha? 06:15, 18 October 2013 (UTC)
I agree it is tedious. I did some quite some time ago and hated it. That said, it is eye-opening, and I wouldn't mind inclusion at a much lower level. -- SPhilbrick (Talk) 13:44, 18 October 2013 (UTC)
  • Given the exceedingly limited use of pending changes, what does reviewer actually signify? I agree with Sven's comments regarding NPP, as a long-standing patroller: 300 reviews is exceedingly high, both as something for the candidate to achieve and as something for anyone reviewing the candidacy to actually triage and check. Ironholds ( talk) 06:37, 18 October 2013 (UTC)
Ironholds, I don't see anywhere that anyone has suggested 300 new page patrols. Perhaps if people would read discussions before they participate. I disagree most strongly that at NPP it is so difficult to attain a number of patrolls, I have done thousands and so have you. At the rate at which some patrollers review new articles, 200 patrols can be done in 200 minutes - alebeit probably as slipshod as some of the reviewing at AfC. Kudpung กุดผึ้ง ( talk) 06:47, 18 October 2013 (UTC)
As usual, I'm going to ignore the pointless (and pointed) elements of your comment. To the remainder: the argument seems to boil down to "hey, you did it", which would be great if I wasn't the most active patroller for a solid two years by an order of magnitude I was even in a research study, how about that - "you can do it and I can do it" simply proves we can do it, not that it's achievable by anyone else. You know full well that our work on NPP is non-standard even for patrollers.
Sure, it's possible in a few hours, or days, or weeks if you actually want to put some effort in: that's not the point. It's a lot of work to put in to an activity you may actually have zero interest in - your interest is in AfC, not in NPP. It'd be like saying that for someone to be autopatrolled, they need to have extensive experience patrolling articles: sure, it's indicative of knowing what makes a good or bad article. It's also something that may bore them silly. I'm not entirely sure how excluding the people who don't enjoy NPP is going to help improve the quality or frequency of AfC work. I'd appreciate if you could address the reviewer comment as well. Ironholds ( talk) 06:53, 18 October 2013 (UTC)
There are dozens of patrollers who have made 200 or more patrols - if you only do one a day that's about half a year, so please let's keep this in perspective. If the task is as thankless and boring as some have pointed out (which IMO it is), armed with that qualification they may find AfC more rewarding. No one is excluding those who have not done NPP - but you probably missed the alternative qualifications that were suggested. Whilst I see many parallels in the work of AfC and NPP, I see little or no correlation with PC reviewing. Kudpung กุดผึ้ง ( talk) 07:18, 18 October 2013 (UTC)
Then I'm rather confused as to why you've recommended 'reviewer' as part of a qualification to get this right, since it's a PC-centric userright (unless someone can explain other uses it has, other than AFT5). Ironholds ( talk) 07:24, 18 October 2013 (UTC)
Ironholds, it should be quite obvious that these are listed as examples of criteria for permissions that are accorded based on prior general experience and as incremental stages of user experience that demonstrate some metrics of knowledge of guidelines, policies, and practice for the purpose of access to different levels of meta tasks. We naturally have to start somewhere. You appear to be confused that we are discussing a MedWiki 'user right' according to the semantics of the Foundation, rather than a 'permission' as applied to this exercise. Kudpung กุดผึ้ง ( talk) 08:46, 18 October 2013 (UTC)
Actually, it wasn't that obvious. I had to read it twice, after being initially puzzled that these were being designated as prerequisites. Then I realized they were examples of other rights, along with the criteria, so people could see example of criteria which could be used to think through the criteria for this right.-- SPhilbrick (Talk) 13:49, 18 October 2013 (UTC)
Thanks, Sphilbrick. The text is indeed pretty confusing. Ironholds ( talk) 16:40, 18 October 2013 (UTC)
  • Support except for criterion 2 - but only because I have never done NPP at all. I've just thought of a way to imlplement "Criterion 3". Basically it ammounts to putting new reviewers "on probation". We use a mechanism similar to the "re-review" that is currently used as a "quality control" check during backlog elimination drives. Thus someone who meets the (deliberately low) technical threshold has their first reviews logged at a special page from where they are rechecked by experienced reviewers. The "probation" is lifted once the new reviewer has demonstrated comptence to the satisfation of the other reviewers.. Roger (Dodger67) ( talk) 07:32, 18 October 2013 (UTC)
Dodger67, that's why aspiring candidates can choose between the two sets of criteria that fits their situation best. They don't need to satisfy them both. Essentially however, exactly what we are trying to do here is to avoid having to monitor the work of new reviewers as much as possible. This is currently being done on an ad hoc basis, but only when issues come to light. It would be impossible to do a double-control on all new reviewers - AfC resources are stretched too far already. Kudpung กุดผึ้ง ( talk) 09:05, 18 October 2013 (UTC)
I think RogerDodger67 has the right mindset ... but I agree with Kudpung that manually reviewing past work, by having existing AfC folks manually monitor some please-check-me-for-accuracy queue, is not the way to go. Methinks the only approach that can put new reviewers on probation, and also automatically check their competence *without* requiring any additional effort from existing AfC folks, is to use an auto-test setup ... where the candidate AfC reviewer attempts to pass judgement on a stream of submissions, which some existing AfC folks have already judged. If the candidate gives the same answers as the existing folks, then the candidate has proven their worth. See my detailed suggestion-section, below. 74.192.84.101 ( talk) 07:27, 19 October 2013 (UTC)
  • Oppose rollback requirement. There are other ways to revert vandalism, for example by using Twinkle's rollback function. I find Twinkle's rollback feature superior to the standard rollback feature as it allows specifying an edit summary, and for that reason, I haven't even seen any need to apply for rollback permission on this project, although I occasionally use the rollback function on Commons. A user's choice to use alternative tools shouldn't affect the chances of becoming an AfC reviewer. -- Stefan2 ( talk) 13:11, 18 October 2013 (UTC)
  • Oppose setting the bar wildly higher for WP:AFC than for WP:NPP as both largely compete for attention of the same volunteers. The requirements for both, while not identical, should be close. It's reasonable to ask that a reviewer be someone who has written an article or two which didn't get deleted, and understands the basic policies (particularly notability and sources), but set the bar arbitrarily high and the only result is to make an already-bad AFC backlog worse. That does no one any favours. K7L ( talk) 13:43, 18 October 2013 (UTC)
Ironically there is no bar for NPP. That's why they have problems there too. I campaigned for years for a solution for the control of new articles which accumulated in the ill fated WP:ACTRIAL, and for improvement of NPP, and that was why we ultimately got the Page Curation system, but it still did not address the two issues: too few patrollers, and too little experience - and there is still an unacceptable backlog with some less easy articles not getting patrolled for months. Kudpung กุดผึ้ง ( talk) 17:26, 18 October 2013 (UTC)

Suggestion by Sven Manguard

Despite "Consensus has been reached for this permission, this RfC is not for rediscussing whether a permission is needed." I still think that this is an incredibly bad idea and will ultimately complicate a process that is already so heavily bureaucratized and understaffed that it has had to come and beg people to help multiple times.

That being said, my suggestion is that rather than make the criterion based on vandalism fighting, we make it based on content creation. The permission would be given to:

  • Autopatrolled (automatically, by making adding it to the autopatrolled package)
  • Anyone with at least one GA or at least two DYKs
  • Anyone that has a track record of positive work doing AfC reviews (before the RfC)

Admins should feel free to assign the permission to anyone that qualifies. Rather than set up a request board, the AfC instructions should instruct people looking for reviewer permission to ask an admin already involved in AfC.

Finally, and I can't stress this enough, the AfC reviewer userright group should never be used to determine recipients for mass messages. AfC has, in my opinion, a shockingly bad track record when it comes to soliciting participation from people that don't want to hear from AfC, and no matter what the ultimate decision about what the AfC reviewer criteria is, plenty of people are going to be given the userright despite having no interest in AfC reviewing (not least because admins will get the right automatically, as they do with almost every other right).

Cheers, Sven Manguard Wha? 06:32, 18 October 2013 (UTC)

  • I'm still confused as to why we're talking about a userright. What technical privilege would it confer, and has anyone taken the time to ask the developers if this would actually be possible or even desirable as MediaWiki functionality? Ironholds ( talk) 06:38, 18 October 2013 (UTC)
We can restrict use of the AfC tool. I'm not sure if that conforms to the definition of a userright. Re: "Has anyone taken the time..." Would you mind being a bit less combative? In the previous RfC, linked above, someone with (WMF) in their sig, who seemed to know technical stuff chimed in. -- Anthonyhcole ( talk · contribs · email) 07:03, 18 October 2013 (UTC)
Ahh. Me or Sven? Sorry if I'm coming off as combative; that's not the intent. Userrights are software-recognised things that permit or restrict MediaWiki actions; admin is a userright that allows access to things like Special:Block, autopatrolled lets MediaWiki automatically mark a page as reviewed, so on and so forth. From a MediaWiki point of view, AfC does not exist; it's not special functionality, just a set of pages. So I'm trying to ascertain if people have actually spoken to the developers and asked if this makes sense as a technically-implemented userright. If not, some of the comments above (rolling it in with autopatrolled, for example) seem unnecessary, and people might want to use less confusing terminology. Userright == MW-recognised status that grants access to special functionality. AfC is not software-recognised functionality.
The WMF-person I can see is Steven Walling; his statement was "I have no idea whether it will be even possible to fulfill the request from a technical perspective". So, this probably needs further investigation before rather than after criteria are established. Ironholds ( talk) 07:08, 18 October 2013 (UTC)
Thanks for clarifying userright. We should probably determine what level of competence a person needs to have demonstrated before being permitted to review AfCs, before discussing whether we need to enforce it with a technical fix. I proposed earlier in this discussion that we use Wikipedia:Reviewer as a marker for adequate competence, and use social control to enforce it along with changing the AFC tool script to prevent anyone not on Special:ListUsers/reviewer from using the tool. But I pulled it, wondering whether that's setting the bar too low. Regardless, we can probably do what we want here without involving MediaWiki development. -- Anthonyhcole ( talk · contribs · email) 07:32, 18 October 2013 (UTC)
I don't know the plans for how to implement this, but a user right does not necessarily need to give access to extra special pages. For example, Commons has the OTRS-member, and the only difference between "OTRS-member" and "autopatrolled" is that an "OTRS-member" can add certain templates to a page without triggering Commons:Special:AbuseFilter/69. This user right could potentially be used in a similar abuse filter to prevent addition of certain AfC templates. -- Stefan2 ( talk) 13:17, 18 October 2013 (UTC)

( edit conflict)Once again, as there is little likelihood that a MedWiki solution will be granted - or even asked for, the question is moot. Some non MedWki methods have already been suggested and even by Brandon himself with whom I had a lengthy (and exceptionally friendly) discussion in Hong Kong. It's been mentioned dozens of times that permissions are needed for several MedWiki-independent actions. They are however listed at WP:PERM as the portal for permissions that are granted by admins. So again, we are discussing something that is not on the agenda of this RfC. Implementation/deployment comes later. Kudpung กุดผึ้ง ( talk) 07:35, 18 October 2013 (UTC)

I am befuddled by this counsel! Considering notes 1 thru 3 of the original RfC, how can one say another's suggestion is moot upon its rendering? Otherwise, this is not a request for comment, but instead, a request for support; of ideas apparently already decided.— John Cline ( talk) 09:35, 18 October 2013 (UTC)
Absolutely not, John. This is a think tank with an objective to define some criteria of experience for reviewing articles submitted to AfC. As stated in the previous RfC, what these criteria would be are for discussion (now here), and how it would be implemented will be discussed when the criteria have been established. One of the reasons that Wikipedia RfC fail or become overly convoluted is that there is often a tendency to discuss tangential issues at the same time, or ones that are not yet up for debate. Ironholds has made it perfectly clear that he will resist any suggestions to make this a MedWiki based 'user right', but has mistakenly assumed that that was the intention (on both this and the previous RfC). That said, if indeed any of the senior staff at the WMF decide that this 'permission' is of significant interest to entertain a MedWiki solution, we would be most pleased to hear about it, but we are not aware of any such offers as yet - in fact a closer look at my comments will reveal that I concur entirely with Ironholds that this is not a MedWiki operation, hence such suggestions are off topic as being evidently unworkable. Kudpung กุดผึ้ง ( talk) 10:27, 18 October 2013 (UTC)
In my opinion it would greatly serve this discussion if there was a definitive answer regarding MediaWiki support. If the entire modification is to be implemented at the WikiProject level, then yes, we are straying off topic by suggesting a new userright, whether automatic or granted; and should therefore focus the eye of our brain storm locally. That said, the best solution to my eyes involves MediaWiki support, and I for one wish we had garnered that support already. Otherwise I think Graeme Bartlett is correct that a blacklist is the way to segregate bad apples and I suppose we could use discretionary sanctions to ban individual involvement where cause has been shown. Notwithstanding, I am optimistic that better ideas are forthcoming, provided we don't stifle the creative flow of ideas by the heavy hand of pessimism.— John Cline ( talk) 13:24, 18 October 2013 (UTC)
Sorry to keep coming back to this John, but I think Ironholds (whichever hat he is wearing) has made it already abundantly clear. We're essentially discussing a set of criteria for a 'permission' rather than a 'User Right' per per Foundation semantics. I had an interesting in-depth discussion on this very topic with Brandon Harris, Erik Möller, and Steven Walling in Hong Kong and although they made some very interesting suggestions how we could approach an improvement to the AfC process, I do not believe there would be a spark of optimism for a MedWiki solution unless this were to have a cross-Wiki rollout. Personally I think it's best for us to find our own solutions locally. There is a faint chance that if they see we're making a superb effort in the right direction ourselves (as they did with NPP) they may step in towards the end bearing gifts, but I wouldn't bank on it. That said, although we want to avoid hat-collecting, I'm very suspicious that one of the reasons why NPP performs badly is that it ironically doesn't have a hat to collect although it demands far more knowledge than PC Reviewer or Rollbacker. Only today I came across a blatant long copyvio synthesis of multiple academic papers completely wrongly tagged by a 14-year-old patroller, who even apologised to the creator and removed the tag again! How many 100s of users would we need to blacklist before we have a few dozen reliable AfC reviewers left? A blacklist only shuts the barn door after the horse has bolted. Kudpung กุดผึ้ง ( talk) 14:54, 18 October 2013 (UTC)
What were their suggestions? And this isn't a Foundation POV, this is a software POV - the two are very much distinct. Ironholds ( talk) 16:39, 18 October 2013 (UTC)
Their suggestions are for a different discussion. As to WMF vs Software, you are best placed to know these things, but as far as the community is probably concerned, the Foundation holds the keys to development priorities, the human resources, the servers, and the funds. Please note that I support your theory that this is most unlikely to be accepted as a MedWiki request and I'm doing my best to stifle any sidetracking on the assumptions that it will. That said, from what I have heard from the Foundation staff and from competent programmers among the volunteer community, it won't be too difficult to find a local en.Wiki solution, whether a social one or one governed by some kind of script(s). Kudpung กุดผึ้ง ( talk) 17:53, 18 October 2013 (UTC)
If all that we want from this is to limit who uses the Afc Helper script, I don't see why any WMF changes are needed. The script is developed by our volunteer coders here. As I mentioned in my suggestions above, to enforce this all that would be needed is (1) The list of reviewers on the "Participants" page would be protected so that someone with Reviewer status would be needed to add a username, and (2) The script would check the list and only work for a username on the list. Whatever criteria we decide to use, this combination should prevent random new users from coming along and adding themselves to the list. — Anne Delong ( talk) 22:42, 18 October 2013 (UTC)
And what does that solve? The AfC Helper script is just a helper. There's no requirement to use it. It provides no functionality that a user can't do without it. AfC went a long time without having it, so I'm not sure what restricting it from some users accomplishes. If this whole RfC is about limiting a helper script, we really don't need an RfC at all. Just code it. However, the initial RfC made it very clear that this isn't just about the script. So, if it isn't a bit and it isn't just the script -- what is it? -- ShinmaWa( talk) 23:42, 18 October 2013 (UTC)
I was just about to redirect this deep thread to ShinmaWa's question-section at the bottom. Agreed that there is no software-enforced requirement that only threshold-approved official AfC folks are permitted to perform AfC actions... but we can make that the *default* way that AfC is handled, and folks doing it *outside* the default way (with exceptions made to grandfather-in people with 10k edits that are using old-school tools or their own custom workflow or whatever) will therefore stick out. This makes it easier to see who is 'officially' doing AfC within the threshold-limits, of course... and if needed, we can tell people doing it *badly* outside the threshold helper-script world to please stop, right? I think enforcement without no cracks in the security is *not* the goal here, because WP:AGF. 74.192.84.101 ( talk) 23:58, 18 October 2013 (UTC)

Suggestion by Lukeno94

  • In my eyes, an AfC reviewer should experienced enough that they would easily qualify for the rollback tool. Putting that aside, I would agree that having at least 1000 mainspace edits is a good idea for an AfC reviewer. I would not say that the conventional reviewer right was enough; it's one thing reviewing and rejecting vandalism, and a whole other one reviewing a whole article. I don't see how GA/DYK/FA count should be relevant. The "autopatrolled" bar is too high for the AfC reviewer right; and as I've said before, you can be a great article writer but very poor at reviewing other's works. Having to patrol 200 things at NPP is excessive, although I agree that some experience is required (maybe 25-50?), due to that being one of the more relevant comparisons. I'll come up with my own proposal later, if I have time. Lukeno94 (tell Luke off here) 07:26, 18 October 2013 (UTC)
"Rollback" is a vandalism tool; it allows multiple edits to be undone quickly where a vandal has randomly hit multiple articles. "Autopatrolled" is intended to keep extremely prolific but otherwise harmless new page authors from flooding WP:NPP. Neither necessarily infer a better AFC reviewer, although they normally are given to someone who is doing no harm. A good or featured article usually has multiple contributors instead of being WP:OWNed by one primary author; someone who'd submitted a pile of stubs in 2002 on valid topics, left the project for a decade and then returned to find some were expanded to GA/FA level would be given more credit than due. An editor which pulls a topic off the WP:AFD pile and rewrites it to WP:FA status, conversely, is not credited with creating an article. All of these metrics have their limitations - preview nothing before you save it and you can run up edit count more quickly, for instance. Experience writing valid articles or bringing existing articles up to some standard (off AfD to viable, off stub/start to B/A/GA, ordinary article to FA) is valuable but collecting privilege flags or edit count just for the sake of doing so does not always guarantee a better reviewer. K7L ( talk) 14:18, 18 October 2013 (UTC)

Ideas by Graeme Bartlett

We should consider what we are trying to achieve here:

  • Firstly we want to build the encyclopedia. So such a person should show that they can recognise the useful content for Wikipedia. The person should be able to understand what is and is not a suitable topic. They should be able to find a duplicte topic.
  • Secondly we want to encourage the contributors, so we want the candidate to be able to talk to the contributors to explain what is needed to improve or to make an acceptable article. The person should be civil in their communication.
  • Thirdly we want to keep it legal, so the candidate should be able to recognise a copyright infringement, or an attack page.
  • Fourthly some nice to have features: The person can add categories and stub tags. The script seems entirely cabable of adding the almost useless orphan tag, so I hope our person can also show that they can edit articles to link to pages, including use of piped links.

Graeme Bartlett ( talk) 07:59, 18 October 2013 (UTC)

Pretty accurately sums up what I said in my suggestion, Graeme. What we're looking for now are some metrics that define those qualities for the purpose of according the permission. Kudpung กุดผึ้ง ( talk) 08:56, 18 October 2013 (UTC)
So I am not so demanding in predefined standards, but the candidate should be able to show these capabilities. If a person is asking for it they can show diffs that illustrate these capabilities. I do agree that NPP is quite a useful precursor experience for AfC reviewer. The other flags such as rollback and reviewer are not directly relevant, but certainly would show that the editor is constructive. If the person does not want to do 400 NPP items, perhaps they could do some apprenticeship work, perhaps checking AFC contributions and giving feedback to a mentor that would prove that they are on the right track. Graeme Bartlett ( talk) 10:11, 18 October 2013 (UTC)
I see that 200 has grown to 300 and now to 400. Sounds a bit Falstaffian ;) Mine were but the first suggestions to get the ball rolling and I knew it would entrain some discontent; let's lurk awhile and see what others may suggest. Kudpung กุดผึ้ง ( talk) 10:38, 18 October 2013 (UTC)
I like Graeme's ideas, and as a submitter I would love to work with an AfC person who met all these criteria... but I am very hesitant that some of them can be decided without fawning, interviewing, role-playing sessions, and other expensive overhead. (Yes, we are all volunteers for the most part, I'm talking about opportunity cost here... every minute an existing AfC person spends interviewing an AfC candidate, is *two* minutes that those people could have been actually whittling down the AfC queue backlog.)
   In particular, Graeme's point#2 about being an encouraging person, explaining things well, invariably civil, good looking, well dressed... okay, not those last two. But I hope the point is clear: there is no way to automatically test and verify those things. Just because somebody is good with those things in a one-hour interview is also no guarantee they will be that way *every* day, to more or less *every* contributor they happen to work with. Some people have a naturally sunny, cheerful, helpful disposition: I've met a few librarians like that, and many teachers. But for every one of those, I've interacted with hundreds if not thousands of fast-food clerks, waiters in restaurants, checkout clerks at the grocery store, floor assistants in retail stores, tech support folks via telephone or IM, and so on and so forth. It is *hard* to be consistently nice, consistently helpful, explain intricate details fully, and all that. Such people are diamonds in the rough, not grains of sand lying on the beach. If we *do* get a gemstone in AfC, I'd recommend we use them as a second-tier, for when contributors have trouble with their first tier person for whatever reason, they can be passed to the sunny cheery natural teacher sitting in the tier-two chair.
   Since point#2 took so much verbosity, I'll hit point#3 super-lightly: don't we have copyvio bots? And aren't BLP articles a specialist niche, given their legal-kryptonite-status, which ought be directed to *only* the AfC folks most experienced with such things? Point#1 methinks we *can* auto-test, see my 74-whatever comment below, and some of point#4 is also either auto-testable, or demonstrable in a three-minute (as opposed to three-hour) interview process. 74.192.84.101 ( talk) 06:58, 19 October 2013 (UTC)
74 it sounds like you are raising the quality bar on the point 2, I was not expecting the behaviour always, but enough to do the job and encourage the contributors. The idea was not to have just gamers that can only push buttons. BLPs are most of what we have (may be companies too) so we need people to handle them too. But perhaps also we need people who can recognise their own limitations and not attempt something the mess up. So even someone that can decline a joke or vandalism can be useful if they just stick to that. Graeme Bartlett ( talk) 21:33, 19 October 2013 (UTC)
Well... I'm not really trying to raise the bar, so much as point out that cheerfulness is a spectrum, but with some pretty well-defined focus-areas. I'm actually trying to lower the bar, if anything. I think we want the tier-one AfC candidates to be the equivalent of the sales-associates at the designer clothing store: efficient-n-quick with straightforward purchases, at least minimally friendly, but do not really have time (and thus do not really need to have the skillset) for solving difficult sticky-wicket cases. If you are trying to create an article about a BLP, who was formerly a relatively unknown business owner, but just announced their candidacy for the mayorship of a large city, and leapt to frontrunner status in the polls, then the sales-associate can send your article on through. If your little brother has a garage band, and the school newspaper mentioned their name once, and that is it so far, then the sales-associate can politely tell you WP:NOTNOW.
   The grey areas are more tricky, where something is borderline-Notable, but requires more depth in the sources, or whatever. I want those types of grey-area cases to be quickly glanced over by the first-tier sales-associate, and then passed back to the second-tier cheerful-librarian-associate. If the second-tier folks cannot solve the issues in a timely fashion, I want the third-tier to be, that the submitter is redirected to the WP:TEAHOUSE to find help doing the rewrite, and their AfC submission goes to the back of the queue. TLDR, rather than insist that our sales-associates aka AfC reviewers *must* be "interviewed for cheerfulness and tested on how sunny their disposition is", methinks we just need to remind everybody to be WP:NICE, which is required of *all* wikipedians anyways. If we happen to run across somebody that is *naturally* cheery and sunny, then we should then 'promote' them to tier-two work, where their special skill is extra-applicable: handling grey-areas. HTH. 74.192.84.101 ( talk) 20:57, 4 November 2013 (UTC)
  • We have copyvio bots, but they probably can't be used until AfC submissions are made on a namepage e.g; 'Draft', instead of a talk page or sub page. Kudpung กุดผึ้ง ( talk) 02:59, 20 October 2013 (UTC)
  • User:MadmanBot already scans AFCs (it misses at least some copyvios) when it's working. Patroller recognition of copyvios is still a must. MER-C 04:34, 21 October 2013 (UTC)
Okay... and how do we test whether an AfC reviewer-candidate possesses that special skill, ability to sniff WP:COPYVIO? There is a tool for analyzing whether URL#1 and URL#2 have copyvio problems. And there are bots that detect plagiarism, kinda-sorta. But short of glancing over the output of such tools, can humans really detect COPYVIO? I guess some things will be obvious, like a submission that says "copyright New York Times" at the top or the bottom of the text, or more subtly, text that has a bunch of internal links that are not wikilinks, but look like they came from a view-source-cut-n-paste job. But baretext submission, that was cut-n-pasted from the middle of some obscure website? Seems unlikely an AfC reviewer will detect the plagiarism with their spidey-senses. Maybe it's not that hard, because the plagiarized portion sticks out as a different 'voice' from the other portions of the AfC submission? (If there is a knack to copyvio-sniffing, methinks the parallel-primary-criteria scheme is useful training.) 74.192.84.101 ( talk) 21:06, 4 November 2013 (UTC)

Suggestion by Andy Dingley

Oppose any creation of a new right that resembles a "collectable hat" in any way, or that makes editors of this, "the encyclopedia that anyone can edit" more dependent upon bureaucracy.

We have a vandalism problem that ab initio editors can pop up, trash an article, post spam links and wander off. We have no checks on this. We allow unregistered editing and we allow unregistered editors to wreak all manner of havoc on established articles. I thus fail to see why we should start narrowing down AfC in particular to a subset of editors willing to jump through hoops.

In particular, making AfC review dependent upon a discretionary permission like rollback. I don't have rollback. I did have, and it was removed for a disagreement over regarding this edit / User_talk:Andy_Dingley/Archive_2009_September#Reversion as vandalism or not. Ever since then I've made a point of never asking for such a discretionary permission, lest it be pulled by some teenage admin with an axe to grind.

I can see some virtue to restricting AfC review (and think a lot more things, up to basic editing) should be restricted. But can we please keep this to a very lightweight, automatically-granted permission, not one dependent on cliques and fawning. Andy Dingley ( talk) 09:39, 18 October 2013 (UTC)

This idea of a automatic permission, or one that is very easy to get, appears to have overall support. -- Mdann 52 talk to me! 13:38, 13 January 2014 (UTC)
The following discussion has been closed. Please do not modify it.
To clarify a point raised off-line, there is a genuine concern that "editors who can't accurately review" shouldn't have this permission (that being it's point). We can attempt to judge this before granting it (which seems difficult to judge) but we can just as readily judge it after it has been awarded. If awarding the permission is a simple edit-count as a first filter, then it's easier to judge real skill by seeing some AfC reviews (and most editors just won't get involved anyway). Andy Dingley ( talk) 11:20, 18 October 2013 (UTC)
On the matter of (pre-)judging-ability-to-accurately-review, see this section -- Wikipedia:WikiProject_Articles_for_creation/RfC_for_AfC_reviewer_permission_criteria#An_idea_from_Ross_Hill 74.192.84.101 ( talk) 06:38, 19 October 2013 (UTC)
  • I support these sentiments.— John Cline ( talk) 09:43, 18 October 2013 (UTC)
  • Support. AfC is desperately understaffed as it is, and unless the permission is automatic this already understaffed project will become a huge bottleneck for the encylopedia. At the very least, everyone who has previously done favourable work at AfC (10 or more good reviews) should have this permission from the outset. -- LukeSurl t c 10:32, 18 October 2013 (UTC)
  • Support this view. Any limitation on Articles for Creation will end up shutting out more good contributors than bad, and AfC is horrible backlogged already. Howicus (Did I mess up?) 14:16, 18 October 2013 (UTC)
Where are the hoards of volunteers 'without' a criteria who are already prepared to step in and review AfC submissions competently? AfC is indeed desperately understaffed as it is, and does not have the person-power to review every reviewer's work. That would only make the bottleneck worse. Some are obviously getting it wrong and yet others blatantly abuse the system for their own ends. We either want reviewers or we don't, but appointing them through some arbitrary automated selection method without any real control would probably lead to greater disaster. The permission has been created by consensus. This is an RfC to determine the criteria for that permission and not to re-debate the need for it. Once the criteria have been established, it will be further discussed how to implement them specifically in a way that it does not become a trophy for the hat-collectors, with as little 'cliques and fawning' as possible, and avoid being pulled by the (fortunately) ever dwindling corps of teenage admins with an axe to grind. Kudpung กุดผึ้ง ( talk) 11:03, 18 October 2013 (UTC)
I think getting more AfC candidates is a job for WP:RETENTION, and similar anti- WP:BITE organizations like the teahouse. Bluntly, it is very difficult to *increase* the percentage of editors that will want to get involved with AfC work, by demanding they first meet some threshold-criteria. (That is not strictly the case, which is why I said 'very difficult' and not flat impossible... one could imagine threshold-criteria like 'willing to accept USD$100/hour from wikimedia foundation for their AfC work' that would *dramatically* increase the pool of editors willing to fight for an AfC slot, but as a class those tend to be unrealistic).
   I think what Andy and LukeSurl are trying to say is that the point of the threshold-criteria is to keep from accidentally reducing the number of AfC candidates *too* much, while still satisfying the basic goal that the threshold-criteria gives us a usable metric from separating the wheat from the chaff. We want the threshold to prevent COUNTERPRODUCTIVE folks from becoming AfC workers, where their net contribution is negative, because they make so many mistakes which other folks end up needing to clean up later on. But if we require fawning, or non-automatic AfC-permbit acquisition, or tons of paperwork, or running the gauntlet ("in order to get the AfC-permbit you must undergo RfA -- even if you already have the admin-bit"), or significant friction-slash-overhead, we shoot ourselves in the foot. Too much friction, and the overall benefit of having a threshold (eliminating N counterproductive candidates) will not outstrip the overall disadvantage of having a threshold (eliminating M productive candidates!). Agreed that we don't want an "arbitrary automated selection method without any real control" ... but we do need it automated, preferably non-arbitrary, and with as little bureaucratic friction as possible, both to keep from tying up existing AfC folks in resume-review-and-interview stuff, plus also to keep from tying up AfC candidates in fawning-and-paperwork. 74.192.84.101 ( talk) 06:35, 19 October 2013 (UTC)
I think we do need a human assessment rather than an automated one. Perhaps it can be easy to get but then easy to remove if there are stuff ups. Perhaps a list such as for AWB can be useful, and alternative could be that we just have a black list. The kind of hat that people would not want to collect is a possible. The hat could be "restricted from AFC review" and only stop people from doing it. We could have other bits for vandals or clueless or copyright infringers. Then these are the people that don't get to operate it. for the axegrinders, we need an axeginder bit too! Though I think I am stretching this to non-seriousness here. Graeme Bartlett ( talk) 11:21, 18 October 2013 (UTC)
The Eric Corbett CIVILity-inapplicable bit. Andy Dingley ( talk) 11:25, 18 October 2013 (UTC)
For the axegrinders we need an angle-grinder. Kudpung กุดผึ้ง ( talk) 11:40, 18 October 2013 (UTC)
  • support as best idea I've seen thus far. Hobit ( talk) 12:23, 6 December 2013 (UTC)

An idea from Ross Hill

I agree with all the goals put forward by Graeme Bartlett.

So far the suggestions have mentioned edit count, rollback, AWC, etc. as prerequisites. However none of those things truly show that one can review articles well. What is a better way to prove your worth at reviewing articles, than reviewing articles? I propose that every candidate find 5 pending articles they would decline, and 5 they would accept and they would have to explain their reasoning, citing policy. They should also be able to explain WP:BLP, WP:NOTABILITY, WP:VERIFIABILITY, etc. An admin would then review their responses and choose whether to accept them as a reviewer. Thoughts? Ross Hill ( talk) 16:30, 18 Oct 2013 ( UTC) 16:30, 18 October 2013 (UTC)

It's a bit hard to find acceptable articles...how about 5-8 articles total, whether acceptable or not? Howicus (Did I mess up?) 23:46, 18 October 2013 (UTC)
Oppose "admin would then review". I don't see any reason why administrators are required for this process, unless there's a technical implementation requirement for them to be. -- ShinmaWa( talk) 23:48, 18 October 2013 (UTC)
I wasn't really focussing on any specifics. I don't care if it's an admin, or an experienced reviewer. 5 articles, or 3. I just want feedback on the idea. Ross Hill ( talk) 23:52, 18 Oct 2013 ( UTC) 23:52, 18 October 2013 (UTC)
Fair enough. Of course, how feasible this suggestion is depends upon the implementation (which is why it is folly to attempt to separate criteria from implementation). However, given all the social-based implementation ideas presented so far, including AfC mentoring, elaborate testing, and the like, this one is the best so far, I think. However, it would need to be fleshed out quite a bit on the specifics of who gets to review, based on what objective criteria, and -- to beat the dead horse -- how approving an applicant would be implemented. -- ShinmaWa( talk) 00:03, 19 October 2013 (UTC)
I have fleshed out an implementation plan for Ross Hill's idea, which I believe is the only truly fair (and predictive) basis for 'testing'. (My answers to ShinmaWa's questions are nobody, based on the objective performance of existing trusted AfC folks, and automatically based on the specified X-and-Y values at the time -- or perhaps retroactively.) The other criteria being discussed (editcount/etc) are all secondary criteria, which might be useful as a way to pass-the-test-without-testing, but cannot replace the trial by fire of AfC work itself. Rather than choosing articles at random, and let possibly-biased editors make the call on whether the candidate judged correctly, I suggest using real articles that are really going through AfC. If the candidate gets right answers (where 'right' is defined by the answers the actual AfC person gave) on enough of the articles, they too become an official AfC person. See here -- Wikipedia:WikiProject_Articles_for_creation/RfC_for_AfC_reviewer_permission_criteria#Suggestion_by_74-whatever
support this. If we must have a 'crat allocated privilege, then at least let's bind it to the real task in hand. Candidates review some (clarification needed) unreviewed AfC candidates, of which at least a couple must be judged pass/fail as a result. Andy Dingley ( talk) 19:26, 19 October 2013 (UTC)

Suggestion from Sj

It's distracting to separate criteria from implementation here, since they are closely tied together. (The criteria you use affect how you can implement it, and v-v.) So here's a joint suggestion:

Simple option
Maintain a list of reviewers on a wikipage. Let anyone add themselves; remove those who aren't working out yet. Add a feature to one of the popular review-tools that checks to see if new articles on an AfC topic are created by users who aren't on the list -- a flag that someone else should doublecheck the work.
Tying this right to 'edit count' or 'rollback' seems like a terrible idea to me. The number of people willing and able to do this work is tiny; you can interact with them all personally. Instead, tie it to a single back-and-forth welcoming interest and asking people if they feel comfortable they know what a good article looks like [with pointers].
Future technical option
Combine this with the Reviewer flag. Make this the Flagged-Revs workflow for the very first rev of an article. Make it something that is given automatically to people meeting certain threshholds, and to anyone else who asks. Allow it to be removed for misuse; but most granting of the right should be automatic, other than time spent welcoming new collaborators.
The flag should allow access to tools that make AfC work streamlined and easy, and that update any special pages that track requested articles. (In comparison: anyone, with or without this right, can browse the AfC requests and create articles based on them. But it won't be checked off of the queue until a reviewer checks that work.)

Aside: it seems to me that the impact of the Reviewer flag has been weakened by the requirement that admins apply the right, with no automatic way to get the flag. This is unlike basically every other reputation-ladder I know of. Our lack of automatic activity-based rights (other than autoconfirmation) is a waste of energy, and seems self-perpetuating. –  SJ  + 17:14, 18 October 2013 (UTC)

I totally agree. I am still against a user right for this, and reading over what is written here, it looks like what we need is a "reviewer block" for bad reviewers, not an extra reviewer right. All of the criteria I have read above just reinforces my scepticism, because whenever someone talks about "grandfathering in" they really mean "let's keep this cabal small, trusted and among ourselves". We really need to start trusting newbies again like we did back in 2006, or the editor retention rate is going to drop more and more rapidly as the "grandfathers" start to drop off, for whatever reason. Jane ( talk) 10:16, 28 October 2013 (UTC)

Suggestion for Buffbills7701

Alright, I'm going to cut right to the chase. I think that in order to get the reviewer right, you need to get past this. The mentoring program is currently a work in progress, but when it's done, it would be the perfect solution for the new AFC reviewer right. buff bills 7701 20:29, 18 October 2013 (UTC)

This should be one way to get the access to the AFC Helper Script. It should not be the only way (e.g. most very experienced editors with good reputations shouldn't have to "go to school" to get access to the tool). davidwr/( talk)/( contribs) 23:49, 18 October 2013 (UTC)
Seems like a great way to open a hatshop for the currently inexperienced. No, or at least very few, long term editors would go near it. Andy Dingley ( talk) 00:40, 19 October 2013 (UTC)
Andy, I'm sure Buffbills meant 'one way' as David expanded. Every single user right from Confirmed through to Bureaucrat is a millinery in our information mall, but generally only on the lower floors - anyone who has worked extensively at WP:PERM and WP:RfA knows this. However, the systems of scrutiny that accord those rights generally function well but there will always be a tiny few who loose their flags - especially admins who have an axe to grind. At the lower levels, it is even more rare for PC reviwers, Rollbackers, File Movers, Autopatrolled, etc. to be demoted, but it does happen. I've never been subject to sanctions, but as one who was bullied by two teenage admins early in my Wiki career, and completely bullied away by an admin (now desyoped) from one topic area, never to return, where I had most to offer the encyclopedia, I do follow the ANI/AN, RfC/U, and Arbcom rituals very closely even if I don't participate much there. As an admin however, I don't have any axes to grind.
Let's not get too uptight or paranoid about the occasional hat-collector slipping through the net, a system of control over who can process AfC submissions is far better than none at all or one that is accorded automatically based simply on editcount/tenure, etc. Possibly those who work regularly at AfC and its maintenance are more aware of the issues than those who don't, but what we are here to do is ask the broader community for their opinion on, and to suggest, a set of criteria that would largely contribute to improving the quality of AfC reviewing, ensure that all reviewers are singing from the same page, and are friendly to the the submitters. The permission does not grant any further rights or hamper the work of article creators who know what is expected from an article that will survive legitimately in the encyclopedia. Kudpung กุดผึ้ง ( talk) 04:47, 19 October 2013 (UTC)
I would agree with David here. We have a need to solve the current problem of poor quality reviewing. I believe we need this right, but it should be very low, based on a simple mileage count – then if needs be, withdrawn from poor reviewers, based on the quality of their reviews. Secondly we can achieve this by encouraging experienced editors to take more part (AfC review is not rocket science) and anything that could be seen as "patronising" is hardly likely to achieve that. How many 5+ year / 10s of kedits editors want to be "mentored" by someone who has maybe 6 months of springy-tailed editing inbetween school? I spent a chunk of last week being lectured on 1950s motor racing history by someone who's barely old enough to have a driving licence, but here they have the free time to do a lot of typing, so they get to shout loudly and often. Andy Dingley ( talk) 10:15, 19 October 2013 (UTC)
Buffbills7701, editors with only double digit edits regularly add their names to WP:WPAFC/P list and due to the immense workload we're not always quick enough to do something about it. Last week one registered with the sole purpose of passing their own articles. One of our concerns therefore is for the grey area of editors who review, but whom we are not aware of. I support the idea of a school for aspiring reviewers and I'm currently working with other editors to set one up. I don't believe genuine hat-collectors are very interested in going through the rigours of our various training systems (I completely redesigned the WP:CVUA from the ground up and also set up an NPP school) . One of our standard answers at WP:PERM (Rollbacker) is "Hi, I appreciate your enthusiasm but with only 46 edits to mainspace I don't think you have sufficient experience yet. When you have made at least 200 edits, you may wish to enroll at the Wikipedia:Counter-Vandalism Unit/Academy to learn more about it." Kudpung กุดผึ้ง ( talk) 04:47, 19 October 2013 (UTC)
Here's what I don't understand about all this. You've brought up this editor who registered an account to "pass his own articles" on a number of occasions. So. What. You act as if this is some kind of real crime against the project. In reality is that once he's a registered user, he has every right to create his own articles in mainspace as much as every other user does. If he wants to clear the duplicate article out of AFC in the process, there might have been better ways to do it, but overall, he didn't hurt the project at all and he certainly didn't hurt AFC one bit in doing so. That argument is completely a red herring and I do wish you'd stop using it. -- ShinmaWa( talk) 19:06, 3 November 2013 (UTC)

Suggestion by 74-whatever

temporarily delayed as my suggestion is for auto-testing and auto-confirming *technical* competence at AfC specifically, and kudpung is after *moral* competence and ethical commitment to wikipedia generally

Kudpung and Anne and others have suggested various secondary criteria for the threshold: edit-count, NPP, and so on. Lukeno pointed out that some secondary criteria (like participation bringing something to GA status) have little relevance, because most of the AfC stuff is nowhere *near* that status. Several people have pointed out an automatic-grant-the-bit solution is the best way to minimize bureaucracy, but other people have countered that the human element is crucial, for most secondary characteristics do not really tell us if the candidate will be any good at judging AfC submissions. It is important that they be good at this task, because too many false-negatives will cause a dramatic amount of work downstream, and of course a lot of drama if an 'accepted' article is then speedy-AfD'd the following week. I believe there is a way AfC folks can have their cake and eat it too. We should judge the worth of potential AfC folks, based on how they would do on real-world AfC submissions, compared to current AfC folks on those same submissions.

  • Candidates wishing to get the authorized-for-AfC bit test their skills against real-world AfC submissions
  • Threshold should be an X% success rate on a minimum of Y real-world AfC decisions
  • In parallel, and blind to such candidates, the already-authorized AfC folks do their normal work
  • Example test: on Wednesday evening, Anne Delong judges ten AfC submissions from the queue; I do the same, without seeing any of her decisions
  • Example math: Anne's answers were yyNNyyNNyy to those ten, and my answers were yyNNyyNNNN , which means I made two mistakes (Anne is perfect -- good work Anne :-)
  • Example fail: if the threshold chosen is X>=90% and Y>=10_decisions, I satisfied my_Y>=10 but I failed to satisfy my_X>=90.
  • Example learn: determined to get there, I study Anne's answers (now visible to me after my test-session), and keep trying.
  • Example win: in my next test-session, I judge ten more of Anne's cases in parallel, and make no mistakes. Now my_Y=20 and my_X=18/20, which means I just auto-passed with my_Y>=10 and my_X>=90%.

Disadvantages:

  • the test-session itself is duplication of 'real' work (Anne is working -- I'm only *simulating* work she already did)
  • somewhat difficult to explain the concept of auto-testing in parallel (cf verbosity of this proposal)
  • may be *quite* difficult to implement the concept of auto-testing in parallel, since Q&A with the submitter is not something we can simulate
  • likely impossible slash infeasible to really make the 'blindness' of the auto-test secure (if Anne emails me the answers I *will* pass)
  • even if we posit that security is not a big deal, and Q&A can be elided, still need a dev to write some code for auto-testing (not true of e.g. simplistic editCount>=1000 threshold or similar)
  • hard to pick the initial Y ... make it too high, and nobody will try, make it too low, nobody will fail
  • hard to pick the initial X ... make it too high, and *existing* AfC folks will be eliminated, unless grandfathered in
  • just because you crammed, and memorized the policies long enough to pass a test-session, does not mean you really are good at AfC later on
    • "Kudpung: Last week one registered with the sole purpose of passing their own articles." Somebody could cram for the test-session with that purpose in mind, too. Only an admin can catch that.
  • scoring well on the auto-test does *not* necessarily make you a good AfC judge... it depends on whose answers you correctly mimic'd!

Advantages:

  • threshold is real-world *primary* criteria, not secondary
  • although no humans are involved with granting the bit once I pass, a real human is doing the testing (Anne is testing me)
  • as with anything in wikipedia, WP:IAR means that even if I auto-pass, some admin can always *manually* remove my authorized-bit later on
  • fair nature of the automated testing means no complaints about bias/fawning/etc
  • easy to auto-grant the permbit when the threshold is met , with a database table of people-who-passed-the-automated-testing
  • easy to auto-warn an 'official' AfC person when their ongoing work falls below the testing-threshold at any point
  • easy to retroactively adjust the threshold-values of X and Y upwards to improve quality, or downwards to improve reserve-troop-strength
  • difficult to explain 'on paper' but in practice easy to explain... watch what Anne does today, tomorrow do what Anne does, if you do well you pass, if you don't you can try again.

Hope this helps. 74.192.84.101 ( talk) 23:00, 18 October 2013 (UTC)

p.s. Forgot to mention that I agree that *some* sorts of work should automatically be given the AfC-permbit. Have three years and 10k edits with no blocks in the past year? You get the AfC-permbit without needing to pass the X-out-of-Y-auto-testing-threshold. 42 edits on enWiki, but 10k edits on deWiki? Prolly you have to take the auto-test, as a real-world check on your ESL skill. Have 333 NPP credits? Ditto. Have 10 new articles in existence, each older than a month without being deleted? Ditto. Member of arbcom, passed an RfA (regardless of whether you still hold the admin-bit), surname Wales? Ditto ditto ditto. But these secondary criteria should be, well, secondary. What matters is not your edit-count, but how your judgement matches up against Anne Delong's judgement. Our existing AfC personnel should be the gold standard, both now, and five years from now. Auto-testing is a self-reinforcing metric of 'goodness' methinks. 74.192.84.101 ( talk) 23:17, 18 October 2013 (UTC)

And in particular, one group that should automatically get the AfC-permbit was mentioned by Anthonyhcole (besides the 1500 admins), namely, the 6000 people with the Reviewer-permbit. Much like I'm suggesting here, there is a trial period. However, the threshold-criteria for Reviewer-permbits are not numerical and automatic, but require an interview process: knowledge of the reviewing-guide & vandalism-policy, familiarity with WP:COPYVIO / WP:BLP / WP:NPOV / WP:OR / WP:V / WP:NOT, and finally "have an account with track-record of routine editing". 74.192.84.101 ( talk) 07:14, 19 October 2013 (UTC)

The above suggestion that at first the new reviewer would review "in parallel" seems overly complicated, but there would be a simple way to implement this. A new reviewer could pick out a submission to review, and instead of actually reviewing it, leave a message on the Afc talk page saying something like "I think that XXX is ready to be accepted" or "I think that XXX should be declined with this decline reason ___ and I would leave this message:___". Then any of the regular reviewers could say "Looks good to me, go ahead". That way we'd all be "mentors" and the new reviewer would safely get practice. — Anne Delong ( talk) 23:24, 19 October 2013 (UTC)
Anne, similar ideas have been posited above in other sections. I personally do not support any solutions that will: eiher increase the workload of other reviewers or project editors working at AfC, and/or slow down the reviewing procerss; What this RfC asks for is not alternative solutions, but for a set of criteria of experience. Although the rights Rollbacker, reviewer, template editor, File mover, etc., may in some instances not be a good parallel, thier granting system is not dependent on any form of probation or monitoring of their progress. I think we need to look for a similar, simple 'granting' process here based on experience than can be quickly investigated (edit count, type of edits, talk page comments, block logs, etc.,) rather than look towards implementing a more complex and time consuming process. An AfC Academy has now been developd and any aspiring reviewers who fall short of the criteria that we will set here can be referred to that for training if they are serious about becoming reviewers in much the same way as we have a CVU school and an NPP school - bearing in mind that this latter is generally only used when NPPers (who don't need any quals at all) persistently get their patrolling wrong and are asked by an admin to stop. Kudpung กุดผึ้ง ( talk) 03:18, 20 October 2013 (UTC)
I've already given my opinion about the qualifications above, but you didn't like that either, so I will go back to reviewing now. — Anne Delong ( talk) 03:24, 20 October 2013 (UTC)
Hello again Anne, thanks for the comments. Yes, my suggestion is obviously quite complex, to understand and to implement, whereas your mentor-by-humans approach is straightforward and easy to implement. But the worry for Kudpung is that you and the other AfC regulars are *already* overloaded, so mentor-by-humans is going to pull expert AfC reviewers into mentoring (and thus necessarily out of AfC work), and I share that worry. My complex review-in-parallel scheme is designed to let the computer be the mentor, so that a beginning AfC candidate can test their mettle against your known skill, *without* you needing to directly mentor them. Once the top candidates were known, then mentoring would be the next phase. Anyways, as Kudpung points out, my solution is not what this RfC is for... this RfC is for coming up with a bunch of secondary criteria, that can be used for autogranting the AfC kinda-sorta-like-a-permbit-yet-not-really. (My scheme attempts to dispense with secondary criteria, and directly measure How Good The Candidate Is At AfC Work Itself.) Appreciate the criticism, danke. 74.192.84.101 ( talk) 20:38, 4 November 2013 (UTC)

Question from ShinmaWa

While this RfC is primarily about the criteria, which I fully recognise, some thought into implementation needs to take place lest we paint ourselves into a corner that can't be implemented. A lot of discussion is about a UserRight bit, which has technical issues which Ironholds discussed above. There's also been a lot about restricting scripts and tools. However, while there are a number of scripts and tools available to assist with AfC, they are 100% optional. Everything done at AfC can be done without a single tool in place and was for a very, very long time.

When boiled down to its essence, AfC requires that users be able to 1) Move pages from the "Wikipedia talk" namespace into article space and/or create new pages in article space and 2) Edit existing pages in the Wikipedia namespace. That's it. Every autoconfirmed user on the planet has the capability to do this. Restricting the tooling will just restrict the tooling. It won't actually keep a single user from participating in AfC.

So, the question is this: For this criteria/permission/etc to be meaningful, failure to meet this criteria somehow has to prevent users from creating articles nominated in AfC (which has all kinds of bad second-order impacts) and prevent users from editing articles in the "Wikipedia talk" namespace that "belong" to AfC (ditto). Just how are we going to go about this? -- ShinmaWa( talk) 23:15, 18 October 2013 (UTC)

"if it isn't a bit and it isn't just the script what is it?" From what I understand, it is a community standard, used by enWiki, to see who is 'qualified' to be an AfC person. It is like the ISO standard for papersizes, where there are tolerances plus-and-minus a few micrometers, but if you are within the tolerances you can say you are ISO-standard-sized A4 paper, or whatever. That does not mean that *every* piece of paper is ISO-standard, nor even that ISO-standardized paper is the best (arguably vellum is the best). It just means that, if you have satisfied whatever threshold this discussion ends up recommending, that you become a Recognized Official AfC Member In Good Standing, subject of course to other admin-actions that might keep you from acting on your over-the-threshold qualifications. Maybe someday it will be a 'real' permbit like the admin bit, where security matters... for at present, methinks it is just metaphorically an AfC-permbit, loosely enforced by community standards rather than strictly enforced by software. 74.192.84.101 ( talk) 00:03, 19 October 2013 (UTC)
"For this criteria/permission/etc to be meaningful, failure to meet this criteria somehow has to prevent users from creating articles nominated in AfC" (emphasis added). I think the 'somehow' is going to be, by manual admin intervention. If you have not satisfied the threshold, and you keep submitting perfect articles as AfC, which always pass with flying colors, who cares? If you have not satisfied the threshold, and you 'manually' create articles without the AfC helper-script, sooner or later an admin will make it their business to care, and call you out for disruption. 74.192.84.101 ( talk) 00:06, 19 October 2013 (UTC)
So, a completely social-based implementation. How does criteria play into this then? This approach winds up being a no-op and bringing us right back to where we started. Specifically, "If you don't meet our criteria, you can't play in our sandbox" just becomes "If you are being disruptive, an admin will intervene". However, that's already the case. We don't need an RfC or a bit or criteria or any of that to have admins deal with disruptive users. So, I'm quite confused as to what that accomplishes realistically. -- ShinmaWa( talk) 00:16, 19 October 2013 (UTC)
Those who do not meet the criteria will be slowed down significantly, and those who make mistakes and are warned and continue to make mistakes can rightfully be called disruptive. Likewise, those who have been given access to the tool and had it later revoked and who come back and "do it by hand" in a substandard way can also rightfully be called disruptive. Wikipedia already had mechanisms for dealing with disruptive editors. Revoking access to the tools for editors who are merely incompetent can slow them down enough to encourage them to think about what they are doing, which will hopefully mean they will have a higher rate of competent reviews. Let's suppose Joe Novice Wikipedian is trying to help out and somehow gets access to the tools and makes 30 reviews in 2 days, but botches half of them. He gets access to the tools revoked but he is determined to help out. Over the next 2 days he does only 10 reviews because he's been slowed down for lack of access to the tools. At worst, we have 10 reviews to re-review and 5 to clean up. But hopefully he'll be more accurate becuase he's working slower (and gaining experience as he goes) and only flub 2 or 3. davidwr/( talk)/( contribs) 00:42, 19 October 2013 (UTC)
I can certainly respect that. In fact, I even support this approach. It doesn't take the gun away, but it removes the fully automatic selector switch. There's certainly precedence for this with Twinkle and the like. However, this begs the question if this actually meets the consensus formed in the original RfC. While I opposed that RfC, many people didn't, and I suspect some supporters might see restricting just the script as being a half-measure. *shrug* Thanks for responding, davidwr. -- ShinmaWa( talk) 01:10, 19 October 2013 (UTC)
There are some very relevant comments in this thread, and I'll just reiterate that the consensus in the previous RfC was There is community consensus for the introduction of a requestable permission which will be required to review articles at Articles for Creation. - nothing more, nothing less, and that is what was asked for. Firstly, I believe even a half-measure is better than none at all, to the exclusion of any arbitrary automated granting of the access. Having a list of users who are 'authorised' to use the script is also a kind of 'half way' that we already have, but as I mentioned somewhere above, we need to get all reviewers on a list. Naturally if they get their flag removed, under the current technological aspect of the process, there is nothing to stop them continuing to do manual reviews; it would certainly slow them down, but we would know who they are. Secondly however, with a couple of thousand submissions in the queue, we don't know who is actually doing the reviews at all - we just don't have the person-power to do a double check on every submission that gets declined, moved to mainspace, or CSDd under an appropriate criterion. But we are diverging here - we need to set the criteria for permission first - and that shouldn't really be too difficult (we have enough examples cited above for the granting of various user 'rights' that do need official WMF approval) , then see how they can be technically or socially implemented. 06:06, 19 October 2013 (UTC) Kudpung กุดผึ้ง ( talk)
As mentioned by me and several other people, it is folly to attempt to separate the criteria from the implementation and it is awkward to attempt discuss one without the other. One impacts the other at a fundamental level. Further, many of the suggestions demand a certain implementation and/or precludes others. So, if we can't talk about implementation, then our criteria options become severely limited to stuff like edit counts and other similar statistics. In essence, the "no implementation" restriction steers down a very narrow set of options -- namely the options that you suggested at the top at the RfC. I think we need to look beyond that scope. -- ShinmaWa( talk) 02:55, 20 October 2013 (UTC)

What Shinmawa raises is a fundamental flaw, this RfC is invalid

A userright represents the ability to use a technical feature. Since this userright won't place any technical restrictions on anyone, there is no point at all in creating it. Access to the common scripts could be toggled with or without a userright. But they could still load the same exact script via their custom JS interface, and we can't stop them from doing that. So in my mind, the prior consensus is irrelevant because it is not possible to implement.

If there is a desire to create a socially enforced white or blacklist, then we should be talking about creating a process for that, and this RfC should be closed and reframed properly, with first a discussion about whether it should be a whitelist or a blacklist, before any criteria are proposed.

A blacklist makes the most sense to me, because there is nothing at all stopping someone who isn't whitelisted from processing AfCs, and if they do it correctly, are we going to really block them for failing to participate in the bureaucracy? Gigs ( talk) 18:31, 28 October 2013 (UTC)

Suggestion by Davidwr - Leave access to "AFC Comment" unrestricted

Leave the "Comment" button on for everyone by default.

If an editor abuses it, they can be blacklisted.

The kinds of comments editors leave are probably the best judge of whether they should get access to the rest of the buttons. davidwr/( talk)/( contribs) 00:31, 19 October 2013 (UTC)

I do not think that new people will bother activating the tool jsut to get the comment button. However I don't think that being able to comment is harmful. After all it is not that hard to edit the article and add a comment, even using the correct afc comment template is not that hard to do. Blacklisting against adding comments I suspect would be about equivalent to a topic ban. Since it is so easy to bypass I would not suggest implementing a comment blacklist. Graeme Bartlett ( talk) 21:01, 19 October 2013 (UTC)

Suggestion by Davidwr - Make it a "throttle" like AccountCreator

Tweak the AFC Helper Script so everyone can use the full set of tools on no more than a handful of different submissions in a rolling 2-3 day period.

Those who abuse the tools can be blacklisted. davidwr/( talk)/( contribs) 00:31, 19 October 2013 (UTC)

I assume that you do not want to rate limit it for every one, so the users with the permission can review faster. Although I suspect our bulk and speedy reviewers do make some errors too, such as we can see by the number of AFDs and prods that pop up. Also the stuff declined for a weak reason will not show as a problem that way, but just drive away contributors and content. However I do like the idea to do a rate limit for the people with no permission, but then also add their work to a special list for extra review by others. Graeme Bartlett ( talk) 20:54, 19 October 2013 (UTC)

Suggestion by Davidwr - many routes to full access to the tools

There shouldn't just be one route to get access to the full AFC Helper Script.

I'd give access to these buttons to anyone requesting them who:

  • is a long-time Wikipedia editor with no recent relevant problems
  • is grandfathered in because of significant recent AFC participation and no recent relevant problems
  • demonstrated competence through intelligent, accurate AFC comments or direct feedback to editors over an extended period of time and a significant number of articles
  • demonstrates competence through intelligent collaborative content-improvement in other areas of Wikipedia over an extended period of time and over a significant number of articles
  • is under the training or sponsorship of another experienced AFC editor, editors, "acadamy," or similar, or has been declared to be competent to have the tools by their sponsor
  • while not clearly making the cut on any one of the above, goes through a short (1-3 days?) discussion period and get the rights if there is a consensus to give it to them.

Revocation should be relatively easy, with the typical "appeal" taking the form of the 1-3 day discussion period outlined above.

Even after adoption, this list should not be cast in stone. davidwr/( talk)/( contribs) 00:31, 19 October 2013 (UTC)

This idea has overwhelming support. -- Mdann 52 talk to me! 13:42, 13 January 2014 (UTC)
The following discussion has been closed. Please do not modify it.
This sounds like a reasonable idea. It is better than a hard list of requirements that may seriously limit the numbers of new reviewers. Graeme Bartlett ( talk) 20:49, 19 October 2013 (UTC)
I particularly like davidwr's mentorship idea. When I started reviewing I hardly knew how to do anything, so I just started out asking questions and reporting problems on the Afc talk page and at the Teahouse, and other more experienced editors (usually Huon), would take action and I would see what was done and know what to do next time in that situation. — Anne Delong ( talk) 23:14, 19 October 2013 (UTC)
The mentorship idea is just a special "private tutoring" case of Buffbills7701's school idea (see "his" section above). I'm not sure if the original idea of a training program is Buffbill7701's or someone else's, it's been floating around for weeks if not months. davidwr/( talk)/( contribs) 01:59, 20 October 2013 (UTC)
This is entirely reasonable. MER-C 04:35, 21 October 2013 (UTC)
I like it. 78.26 ( I'm no IP, talk to me!) 11:54, 24 October 2013 (UTC)
Support This "many routes" idea sounds like the best suggestion yet. (I assume that, aside from the sixth or "discussion" option, the right could be awarded by any administrator.) -- MelanieN ( talk) 14:43, 24 October 2013 (UTC)
Complete and total support - This is the greatest idea I've seen. While there should be some kind of sieve to limit inexperienced or even malevolent editors from reviewing articles and destroying things, you cannot ignore the major backlog of AfC articles. Writing up a rigid list of requirements that admins must dig through edits to find is laborious for all parties involved and will make the backlog worse. The new "right" should be more to keep bad reviewers out than let good reviewers in. ö Brambleberry of RiverClan 15:11, 31 October 2013 (UTC)
Support, per Brambleberry; this is a really good idea. APerson ( talk!) 02:49, 11 November 2013 (UTC)
Support. At this point, it does not seem likely that any one of the proposals at the foot of the page will gain sufficient support for a consensus to emerge; instead, I'll endorse this "open access" or "flexibility" principle as the way forward. If a software-based AfC Reviewer permission is not going to be technically feasible, perhaps restrict access to the reviewing script dependent on being added to an official whitelist, in a manner similar to how access to AWB is currently regulated. Super Mario Man 02:43, 21 November 2013 (UTC)

Implementation detail suggestion by Davidwr - preventing moves

Withdrawn per "law of unintended consequences" as pointed out below by stefan2 at 13:23, 19 October 2013 (UTC). How did I miss that possibility? davidwr/( talk)/( contribs) 15:44, 19 October 2013 (UTC)
The following discussion has been closed. Please do not modify it.


Should there be a consensus to prevent non-approved editors from accepting articles, one way to do this is to bot-move-protect the WT:AFC page shortly after creation, then allow the AFC Helper Script to trigger a bot to do any required moves. This would not require any changes to MediaWiki software. davidwr/( talk)/( contribs) 01:21, 19 October 2013 (UTC)

I'm not sure I understand this suggestion. Isn't there more than one way to skin a cat, as ShinmaWa's question-section above points out? Use of the helper-script is optional, and I guess I don't understand why bot-move-protecting the WT:AFC page will add security. Is there really no other way to get an article created (or take an existing stub and get it renamed) without going through WT:AFC at all? 74.192.84.101 ( talk) 06:15, 19 October 2013 (UTC)
  • Oy vey... All of these unproductive subheadings and then multitudes of comments about stuff in other subheadings... I can't follow the thread of any of these discussions and this page has gotten way TL;DR overnight. Unless someone who has been following can create a convenience break with an overview summary of all the ideas in one section or get rid of all of the subsections above or re-arrange comments so that comments are in the proper section headings (very bad wiki-etiquette, please don't), I'm afraid I can't contribute to this discussion at this time. I just don't have two days to try and piece mail all of the badly fragmented discussions back together. Technical 13 ( talk) 12:25, 19 October 2013 (UTC)
  • Oppose If moves are made more difficult, then we are likely to get more copy & paste moves which violate the attribution requirement. -- Stefan2 ( talk) 13:23, 19 October 2013 (UTC)
I disagree with encumbrances necessitated by the weakest link or worst-case scenario. We ought instead to fortify an imaginable breech with effective countermeasures; which do exist.— John Cline ( talk) 03:20, 20 October 2013 (UTC)

Comment by James500

I was not aware of the existence of the previous RfC and I suspect that many others were not aware either. Consensus can change, so there is no reason why we cannot now discuss whether any new permissions are needed at all. James500 ( talk) 20:03, 19 October 2013 (UTC)

Well alternatives could be a whitelist or a blacklist of those who can or those who can't. Other ideas were a series of awards to indicate progress or achievement. And there should be hat for the hat collectors. We already have barnstars and a listing of project participants. Perhaps someone can vet the newly added names to see how they are going. Graeme Bartlett ( talk) 20:44, 19 October 2013 (UTC)
That's been dicussed further up. The problem is that currently, no reviewers are obliged to enter their names on that lit, hence we do nots always even know who is reviewing until problems come to light and are brought to the AfC talk page. Most issues are handled locally on the reviewer's talk page: 'Why did you decline my submission?' which begs the question: Why was the creator not provided with more detailed information?.
Hat collecting is an unavoidable but necessary evil. We get plenty of them at WP:PERM but we are fairly good at filtering them out. Kudpung กุดผึ้ง ( talk) 03:23, 20 October 2013 (UTC)
The 'why did you decline my submission' enquiries occur even if you do explain the reasons when declining. Particularly troublesome are autobiography and WP:COI as a decline (even on material previously declined by another reviewer) often gets a flood of WP:OTHERSTUFFEXISTS and "but I worked so hard" pleas as to why the author really deserves to have their own article. This will continue even if you create roadblocks to entry for new reviewers. K7L ( talk) 21:56, 20 October 2013 (UTC)

I don't like any of the proposals that have been made, but I think that a blacklist of those who have demonstrated that they are incompetent, compiled by human beings, would be the least worst option. James500 ( talk) 07:06, 24 October 2013 (UTC)

Suggestion by TheOriginalSoni

Of all the solutions, I found Ross Hill's solution to be the most practical and useful, and hence I propose the following steps for selecting the AFC reviewers, based on a few adjustments I think should be made on it

  • A selected few active and/or trusted reviewers will be grandfathered in. The exact details of how it will be done will be decided later.
  • Anyone who wishes to become an AFC reviewer would be submitting their reviews of at least 10 articles currently at AFC. This would be done at a special requests page for
    • The review must be clear on why it is rejected, and any other such comments.
    • There must be at least 3 declines and 3 approvals among those submitted reviews
    • The reviews should be among pending submissions at the time of submission
    • Once any particular review is submitted, there should be no changes to it.
  • These reviews are all open for comment from any current AFC Reviewers, who may choose to "Endorse" or "Disagree" with a particular review.
  • Any article among the list which gets rejected or accepted externally would auto-count as an endorse or disagree by itself.
  • After a period of time/ after all the reviews have been looked into, a designated person (the qualifications of which will be decided in future discussions) would close the request as pass or fail. In general, 8 or more correct reviews would count as pass, and 6 or less correct ones would be a fail.
  • [Additional proposal under discussion] Any sufficiently trust candidates who have demonstated enough competence might not be required to go through this process, but handed over the tools directly on request.

This is the general schematic of how I think it should proceed. Every specific point in this suggestion is open for discussion, and would be altered as per consensus and common sense. TheOriginalSoni ( talk) 00:42, 21 October 2013 (UTC)

Support Because reviewing skill is what matters, so that should be what we test. Ross Hill ( talk) 00:59, 21 Oct 2013 ( UTC) 00:59, 21 October 2013 (UTC)
Support as ONE way Oppose as THE ONLY way. Anyone who comes in having already demonstrated competence regarding content guidelines/policies and who doesn't have anything negative should be given a pass on this. Basically, any editor who has an edit history that would make them a credible candidate at RfA (I didn't say he would pass, just that he wouldn't be WP:SNOW-closed or otherwise fail miserably) and who doesn't have any thing negative in their recent history should not be required to do more than ask for access to the tools. The same goes for editors who might fail miserably at RfA only for reasons not relevant to AFC work. davidwr/( talk)/( contribs) 01:57, 21 October 2013 (UTC)
  • I failed to notice this point. I agree that WP:IAR should apply to obviously trusted candidates and they shouldn't have to go through the entire process. But at the same time, I wonder if there is any harm in having them go through this simple enough process. If others also agree to the additional proposal, I'd be willing to add it. TheOriginalSoni ( talk) 09:33, 21 October 2013 (UTC)
Neutral Overall those points look good, however the no more than "7/10 one direction" rule is going to jump up and bite a lot of hopefuls. Hasteur ( talk) 13:55, 21 October 2013 (UTC)
I'm assuming that the intent is for the candidate to have at least 3 approves and at least 3 declines among the 10 reviews, so that his competency on both approvals and declines can be evaluated. A person may be fine when evaluating an article that should be declined but he may routinely over-decline and mis-evaluate things that should be approved, or vice-versa. Too many errors in either direction is counter-productive. davidwr/( talk)/( contribs) 16:14, 21 October 2013 (UTC)
The problem I was trying to indicate is ast least in my experience, I do about 80 to 90% decline simply because it takes a lot of effort to get a submission up to the level that I would pledge my reputation to the submission by accepting it. Hasteur ( talk) 23:43, 21 October 2013 (UTC)
  • Even then, I am of the opinion that there should be some limit of this sort to check for both sides of whether the reviewer knows the policies. If your concern is indeed correct, maybe we could lower it to at least 2, but I wouldn't want to remove it. TheOriginalSoni ( talk) 13:07, 22 October 2013 (UTC)
Sure, we need proof that the person can approve at least 3, and decline at least 3, and we want to have at least 10 example-decisions to look over. Rather than saying that they must have ten cases, and they must approve 3 of *those* ten, and decline at least three of *those* ten, instead make this the rule: There must be no more than 7 declines or approvals among those 10 reviews The ten selected example-reviews *must* include at least 3 approves, and at least 3 denials; note that the reviewer-candidate often may actually need to review more than ten actual cases, to achieve 3 of each type... but only ten selected cases (including at least 3 approves and at least 3 denials) will really "count" when determining whether the reviewer-candidate passes the examination. HTH. 74.192.84.101 ( talk) 21:21, 4 November 2013 (UTC)
  • @74 Does the current wording of the proposal make more sense, or should there be further rewording on it? TheOriginalSoni ( talk) 07:45, 6 November 2013 (UTC)
Looks fixed to me. I noticed a spelling error and fixed it, while I was here. That said... I think your idea, like my own suggestion elsewhere on this same page, is testing the "wrong" thing for what Kudpung is really trying to accomplish. See my TLDR explanation below. At this time, I've collapsed mine, for resubmission as part of a future RfC discussion.
  The motivating problem (unstated in the RfC-intro-text which was a mistake) seems to be that Kudpung only want editors that are Ethically Committed To Wikipedia's Values to be able to perform AfC-review-approvals. There are incidents where a spammer will create an account, 'review' a small set of AfC submissions -- often given *randomized* answers which is awful for both the submitters and for the NPP folks that have to clean up the mess later -- and then approve ten of their own blatantly promotional submissions. This is particular bad when socking is involved, because without checkuser (which everybody is rightly *very* hesitant to go handing out all over the place), you end up with what looks like one username submitting to AfC, another seemingly-unrelated username adding some cites, a third username reviewing-and-approving using the AfC-helper-script, and then several 'other' usernames which make more changes to the article once it is in mainspace. But it is all the same person, or same spambot!
  Very tough to fight, right now. Even worse, the sockpuppet could pass *your* quiz, though, right? Because it only takes 8 out of 10... and then they are free to approve several hundred spamvertisments, before they finally get caught. The same problem applies to my suggestion: a motivated spammer can pass my ten-or-more quiz, just like yours. Anyways, long story short, it turns out this RfC is not about passing the 80%-correct-mark... though that skill is still crucially important, it is orthogonal. This specific RfC is about moral-n-ethical *secondary* criteria (e.g. min-edit-count to prove you love wikipedia), whereas what you and I are testing is technical-n-policy *primary* criteria (e.g. ability to get 8 out of 10 reviews correct). Suggest we submit our ideas to another, future RfC. Hope this helps. 74.192.84.101 ( talk) 22:31, 18 November 2013 (UTC)

Suggestion by Pol430

I worry that asking potential reviewers to conduct trial reviews leaves too much room for 'instructor creep' and who will assess their performance? One person or more than one? The idea strikes me as fertile ground for creating a 'priesthood of gatekeepers' or turning the process into pseudo-RfA. I think we need to keep the process as simple as possible with a fairly black and white set of metrics to work to. Also, whatever form this permission takes, it should be transparently requestable via a noticeboard in the same way as other permissions. In my involvement at AfC, I have found that reviewers need to be able to demonstrate the following essential qualities:

  1. Must be able to judge what constitutes vandalism, attack pages, and wholly negative unsourced BLPs
  2. Must be able to identify copyright violations
  3. Must be able to recognise WP:ARTSPAM and blatant hoaxes
  4. Must demonstrate a sound understanding of notability, verifiability/reliable sourcing, and the BLP policy
  5. Must be able to communicate with patience and clarity with new editors

I believe that these qualities would be best evidenced against the following criteria:

  1. Must have carried out at least 50 good vandalism reverts -- a common threshold for granting of rollback (includes the speedy deletion of pages as blatant vandalism).
  2. Must have correctly identified more than 5 attack pages or wholly negative BLPs, by whatever means.
  3. Must have correctly cleaned up 20 articles with copyright concerns or correctly nominated 15 pages for speedy deletion as blatant copyright violations.
  4. Must have copy edited/cleaned up at least 20 articles to make them NPOV compliant or correctly nominated 15 pages for speedy deletion as blatant spam/advertising.
  5. Must have participated in at least 20 AfD discussions and !voted/commented with correct policy-based observations that demonstrate knowledge of notability, verifiability and reliable sourcing.
  6. Must have demonstrated a sound knowledge of BLP Policy issues, by whatever means. For example, working at the BLP noticeboard.
  7. Must have demonstrated an ability to help and work patiently with newer editors. For example, tea house host, adoption, help boards, user talk page assistance.

These minimum criteria could be assessed by any administrator patrolling the noticeboard, but should be rigidly applied. In the case of the right/permission being abused, any administrator may remove the right as a discretionary sanction in the same manner as other rights. Pol430 talk to me 18:00, 21 October 2013 (UTC)

I've been an editor and AFC-participant for many years and I don't think I meet all seven of the items on the bottom list, and I know that I have weaknesses in notability in certain subject areas and an inability to communicate with patience and clarity with certain editors. I'm also not as good at detecting advertisements disguised as articles as I would like, but I am getting better at that with experience. davidwr/( talk)/( contribs) 19:51, 21 October 2013 (UTC)
I'm pretty sure that you have made 50 good reverts in your Wiki career and most of the CSD criteria would be easily evidenced by someone who spent a few months patrolling new pages. Equally, participation in 20 AfD discussions is not hard for most long-serving Wikipedians to evidence. Knowledge of BLP policy can be demonstrated by various means and I think your interaction with users on your talk page demonstrates point 7 just fine. I think notability is an area that AfC can sometimes get a little hung up on. In terms of notability, AfC's job is to keep out articles about obviously non-notable subjects; this includes cases where a very solid policy-based argument for not including a subject can be made. Where notability is borderline, then articles need to have the opportunity to receive community discussion about their inclusion in Wikipedia, this means accepting a submission without prejudice to it being nominated at AfD. In cases where notability is difficult to establish because of the specialised nature of the subject area then help may be forthcoming from a relevant Wikiproject. If not, we still have an obligation to AGF and accept a submission without prejudice to an AfD nomination -- that is where the responsibility for ruling definitively on a subject's notability lays. Pol430 talk to me 16:40, 22 October 2013 (UTC)
Huh? First you said "keep it simple" and then you came up with the most complicated possible process. You laid out seven specific numerical criteria which you think should be "rigidly applied". Who in the world (either applicant or administrator) is going to go through histories counting how often someone has cleaned up copyvio or identified attack pages? This process would be unworkable, and furthermore it is not based on any evidence that these things would matter. I agree with "keep it simple", namely, let administrators review the person's contributions and decide if they seem competent enough for the task. Period. -- MelanieN ( talk) 21:39, 23 October 2013 (UTC)
Good luck with trying to search my 30,000+ contributions to check that I pass all seven "must have" criteria. Roger (Dodger67) ( talk) 09:58, 29 October 2013 (UTC)
I recognise that cross-checking those seven criteria would be laborious, but I thought the purpose of the exercise was to ensure high standards rather than dish out a new hat as quickly and widely as possible. I have struck out the criteria that were so evidently wide of the mark. Thanks for your feedback. Bellerophon talk to me 00:10, 31 October 2013 (UTC) (formerly Pol430)

Comment by Brambleberry of RiverClan

The list of articles waiting to be reviewed is backlogged enough, so while I agree that we do need something to make sure reviewers are qualified, those standards should not be so high that only a select few can access them. I think that the criteria should be rather vague, leaving it up to a case-by-case basis. There can be a few strict ones, like a certain amount of article space edits, but things such as "must have rollback and/or reviewer rights" seem a bit too constricting and would be thoroughly unconstructive to the main purpose: reviewing articles to add to Wikipedia. ö Brambleberry of RiverClan 23:48, 21 October 2013 (UTC)

I agree with this. The process should be simple, not stringent; we are simply trying to stop the current situation where unsuitable and/or inexperienced editors are trying (mostly in good faith) to review at AfC without sufficient knowledge of Wikipedia policies. IMO the AfC Reviewer right should be awardable by any administrator who believes the user has sufficient relevant experience to know an acceptable Wikipedia article when they see one. We trust administrators to make far more difficult/controversial decisions than this, and I don't really think Wikipedia will suffer any harm from letting them use their judgment in awarding this right. The qualifications for Reviewer, as listed at the top of this discussion by Kudpung, would serve equally well as qualifications for AfC Reviewer, but the one should not be a prerequisite for the other. As for Rollbacker, that right is both trivial and annoying; personally after having it (and cussing at it) for six months I asked that it be removed. Presence or absence of a Rollbacker right does not in any way reflect the user's ability to review submitted articles. -- MelanieN ( talk) 21:31, 23 October 2013 (UTC)
Part of the reason for the backlog is that many experienced users will not participate. One reason is the many useless, complicated ,and counterproductive procedures in the AfC process, for which see my user talk special archive. But the main reason is that unless most reviewers are moderately competent, what a good reviewer can contribute will be wasted. there's no point in contributing to processes which work poorly and on which one can not make an impact. Otherwise there is a much higher priority for anyone who knows what to do--which is checking their work, and trying to teach those who most need it. Ten good people without interference from the unqualified can do the process better than ten good ones trying also to cope with fifty unqualified.
If we cannot get high standards, we will need to see this only as a first screen, and the accepted articles are going to have to go into NPP so they will be checked a second time. As for the wrongly rejected, they will mostly continue to be lost to us. DGG ( talk ) 04:58, 25 October 2013 (UTC)
If the commonly used tools do not maintain a log page, they could be modified to do so. Gigs ( talk) 18:43, 28 October 2013 (UTC)
DGG, a very accurate summary, and so much of it applies equally to NPP. Allowing them through to NPP would be counter productive, the NPP system has the same kind of flaws as AfC and there is no guarantee that the patrollers, who need no qualifications at all, will pass or tag such an article correctly. Most worrying of course, are the 'lost' incorrectly rejected articles, while a significant concern is whether articles are correctly checked for spam or copyvio etc. (BTW: I have taken the liberty of correcting the link to your talk page archive - that thread is very important and although long, I would recommend the participants here to read it). Kudpung กุดผึ้ง ( talk) 07:09, 29 October 2013 (UTC)
A quick note regarding wrongfully rejected articles – that is also an editor retention issue ... if newcomers are being encouraged to send articles to AfC under the guise that "an experienced reviewer will double-check everything before sending it to mainspace" (which is usually what they are told at places like the Teahouse, and I at times am the one telling them that), then that is a problem. I think DGG's comment regarding sending pages to NPP may have a valid point, however agreeing with Kudpung, NPP draws inexperienced reviewers as well, but at least if you have two chances to catch a problem, that is better than only one. Nevertheless, the more I read about this and think about this, the more I am convinced that the new AFC academy is a good idea if people actually use it and have a desire to do things correctly, and frankly, perhaps a user right is in order. I would think anyone trusted with reviewer or autopatrolled would have necessary qualifications to review new articles, but I don't know for sure. I know user rights mean more bureaucracy, and a manufactured debate over the haves and have nots, but at the end of the day, bad reviewing of AfC and NPP has ramifications on copyright, editor retention, and, perhaps most importantly, missing content that can fit into the breadth of the world's knowledge; that is what we need to protect in these discussions. We can discuss whether someone should have 500 edits or 750 all day long, but that is not what is important. We need people who simply know what they are doing, and if they are doing things wrong, we can firmly, yet gently suggest they utilize training of some kind, and if they refuse that, they simply must be told to stop, as they hinder progress. I think the best way to maintain our NPP and AFC processes would be if experienced editors – article writers, content gnomes, admin, etc. – would all simply commit to reviewing x articles per week, and keep up with it. That would prevent massive backlogs, improve the quality of the reviews, and reduce potential ensuing burnout from one person trying to simply bust the backlog on their own. Go Phightins ! 10:46, 29 October 2013 (UTC)
Another very appropriate comment. However, have you tried herding cats? It works, but you have to give them something. Kudpung กุดผึ้ง ( talk) 11:04, 29 October 2013 (UTC)
@ Go Phightins!: totally agreed. -- phoebe / ( talk to me) 19:29, 30 October 2013 (UTC)

Comment from Phoebe

I don't have an opinion on the technical details of a right, how it is implemented, what the threshold is, etc. But I am worried, in general, about the impact of AfC on new users. The difference between a constructive, welcoming review -- even if the article isn't really up to par, a constructive review can still be made -- and a snarky or brusque one (made for whatever reason, including working fast because of the backlog) is huge for a new contributor. If a right can help with standards-setting among AfC reviewers on interacting with new users -- and maybe even make AfC a more attractive place to participate for experienced editors -- then I'm all for it.

I am well aware of our backlogs and the huge amounts of spam etc. But AfC is also a touchpoint for hundreds of new contributors who if they make it to AfC in the first place are generally also well-meaning and interested enough to perhaps be converted into active editors. Currently, AfC is sort of a Wikipedia backwater, and I feel like it should be front-and-center as a place for us to triage and work. I think a right if done well *might* help with this -- so to the extent it does, I'd support it. (If, however, it turns into simply 'one more collectible thing' as someone else pointed out, or somehow limits participation in AfC by existing helpful reviewers, then I wouldn't). -- phoebe / ( talk to me) 19:27, 30 October 2013 (UTC)

I certainly agree that it should be a 'front-and-center' operation and akin to the importance of NPP which was granted a complex set of tools by the Foundation. However, alone the 60,000 abandoned G13 drafts, of which I have physically deleted several hundred, demonstrate that what comes through AfC includes a vast amount of totally unacceptable junk, often far worse that what comes through NPP, and the fact that the creators have gone through the Article Wizard or AfC does not prove at all, unfortunately, that they are all good faith submissions. At AfC there is a cohesive and supportive dedicated team driving things forward; NPP has nothing of the kind bar its instruction page, has a talk page that sees a message once in a blue moon, needs no qualifications, and suffers from the same ailments as AfC. Kudpung กุดผึ้ง ( talk) 04:42, 31 October 2013 (UTC)
NPP has one advantage over AFC: By definition, every page they looked at was created by an autoconfirmed or confirmed editor. davidwr/( talk)/( contribs) 15:21, 31 October 2013 (UTC)
by G13 drafts you mean random userpage drafts, right? 1) If so, I don't know why you or anyone else would delete these; userpages are meant for drafts, and perhaps except in extreme libel situations or similar are doing no one any harm even if they're not destined to be good articles. 2) Not sure how this relates to the good-faith-edness of AfC. When I teach people how to edit, I tell them to start in their sandboxes. By your measure, if their userpage drafts aren't up to speed they're not contributing in good faith? That makes no sense; these are two different measures. Good faith is largely unrelated to whether the article is complete, referenced, notable, etc. And I've looked at enough AfC submissions myself to be pretty sure they're not all "Johnny sucks" or similar. -- phoebe / ( talk to me) 15:43, 31 October 2013 (UTC)
See WP:CSD#G13, a relatively recent speedy deletion criterion which specifies that AfC submissions which have not been edited at all (not even a keystroke) in more than 6 months may be deleted. DES (talk) 16:00, 31 October 2013 (UTC)
Yes, there are many good (or eventually good) submissions to Afc. As well as beginning editors, it's also widely used by COI editors who want to make sure that their articles won't be deleted as advertising. Afc reviewers help tone these down. To date there have been over 34,000 successful accepted submissions, and most of them left Afc in far better condition than when they arrived. Here are the ones accepted this month: CatScan report Also, articles eligible for deletion under the G13 criteria aren't always deleted; there are a number of editors who are checking through them and picking out ones to improve. — Anne Delong ( talk) 08:20, 1 November 2013 (UTC)
Thanks for the pointer to the CatScan tool Anne. That's very useful. Steven Walling (WMF) •  talk 05:52, 7 November 2013 (UTC)

Research needed?

Hey all. I don't have an opinion about the RFC in question, at least in an official WMF capacity. However, my team is just barely beginning to explore potential improvements to article creation. As a part of this, myself and our research scientist are working on measuring the current state of article creations and creators each month. That includes the volume at AfC, which though unique to English Wikipedia, is obviously an important route for new authors here. If you can help us think of strategies for accurately measuring the number of submissions, as well as decline/accept rates, that would be most welcome. Our notes are at Research:Wikipedia article creation. Many thanks, Steven Walling (WMF) •  talk 05:57, 7 November 2013 (UTC)

As one Foundation staff member has emphatically suggested that AfC is niether in the interest of nor within the remit of the WMF, I'm rather surprised to see this. AFAICS, the community has therefore accepted to investigatigate the possibilities of its own local solutions for improvement to AfC. However, any research that can save volunteers' time would be most welcome. That said, the project you linked to may appear to be a duplication in part of the buried(?) project here and here which, along with Page Curation, was offered as an olive branch to WP:ACTRIAL; it saw no further development. Kudpung กุดผึ้ง ( talk) 18:09, 7 November 2013 (UTC)
Yeah I don't mean to suggest that we're interested in making software updates to AfC as it exists now. Rather, that any new article creation software support we build needs to take in to account lessons from AfC, and the beginning of that is understanding the volume of submissions, the success rate, and so on. Steven Walling (WMF) •  talk 20:34, 7 November 2013 (UTC)
@ Steven (WMF): The feedback from en's AFC team to you would probably be best done in a central location. Where would you like us to do it? davidwr/( talk)/( contribs) 20:45, 7 November 2013 (UTC)
@ Davidwr: A good question to which I don't have the perfect answer. Most helpful for us is going to Research talk:Wikipedia article creation. But if people have comments and want to stick to WT:AFC for now, I'd be okay with that. Steven Walling (WMF) •  talk 00:28, 8 November 2013 (UTC)
@ Steven (WMF): - then perhaps you should take a look in your talk page archives at the thread you allowed to die out. Kudpung กุดผึ้ง ( talk) 04:52, 9 November 2013 (UTC)
Stevan, we do not want or expect the WMF to know how to improve page creation, except by implementing whatever requests for technical features the community here decides on. But it is always helpful if people new to a problem take a look at it, because they may well see things those of us who have been specializing in it may miss. DGG ( talk ) 05:59, 10 November 2013 (UTC)
Given that A) many people at the WMF are community members B) we spend countless hours doing research in to the quantitative and qualitative characteristics of activities like article I think you probably would be surprised how much we know about activities like page creation. ;) We're not just janitors sweeping things up and taking requests these days. Steven Walling (WMF) •  talk 01:23, 20 November 2013 (UTC)

Yet another suggestion

What if, were this change to be implemented, we only allowed people with the AFC reviewing userright to view the AFC submissions, not just review them? Because they can be potential copyright violations, and, given that anyone can create one, may also contain defamatory material. Jinkinson talk to me What did he do now? 23:10, 14 December 2013 (UTC)

This would "break the wiki" - even if those who had edited the page before were allowed to see it, if I submit an article with a dynamic IP address then come back the next day with a different IP address, I would be unable to improve the submission, defeating the whole point of AFC. davidwr/( talk)/( contribs) 02:10, 15 December 2013 (UTC)

Technicalities

Back on track, or partly - because there are mixed opinions whether an MedWiki-independent solution could be achieved, there is something for our resident programmers to look at: here. Other ideas may be coming soon, but I still feel that a set of criteria comes first, then to see how they can best bee implemented. Kudpung กุดผึ้ง ( talk) 03:05, 5 November 2013 (UTC)

In looking at your question to this user, you specifically asked We are having a discussion on how to implent[sic] a local user permission system for a script that is used at WP:AfC. (Emphasis mine.) I'm sorry, but when did this discussion get reframed to be just the script? That is a broad departure and narrowing of the stated purpose of both this RfC and its predecessor. Additionally, you keep saying that we should not be talking about implementation (even though 3 of the 5 of your own examples at the top speak directly to implementation), but then you frame this RfC as an implementation discussion (and specifically, your preferred implementation) to people like West.andrew.g. Frankly, this RfC is fundamentally flawed and really needs to be blown up and redone. -- ShinmaWa( talk) 23:02, 8 November 2013 (UTC)
I can't agree. This RfC is about setting a suitable criterion or criteria for permission to review article submissions at AfC. You have incorrectly interpreted the examples of permissions cited in the preamble as being suggestions for the creation of a MedWiki solution, which the Foundation has clearly stated will not be entertained anyway. I have repeated many times that when those criteria have been agreed on, then we should look at how they could be technically or socially implemented. Any preemptive research into possible local or non MedWiki technical solutions has nothing to do with setting the criteria. And BTW, there is more research going on than only the message to Andrew. Kudpung กุดผึ้ง ( talk) 04:49, 9 November 2013 (UTC)
"You have incorrectly interpreted the examples of permissions cited in the preamble as being suggestions for the creation of a MedWiki solution". No, I didn't. Not once. Not in thought, not in words. That's a complete fabrication on your part. I was actually referring to the fact that your background examples include implementation details such as admin interaction, script developer interactions, and whitelists, which conveniently enough seem to overlap with the implementation solution that you are "preemptively researching". Funny that. However, in addition to completely fabricating my words and intent, you have also failed to address my main point that you have framed this discussion externally as how to "implement a local user permission system for a script" while at the same time insisting that no one else discuss any competing implementation ideas, which seems to me that you are using this RfC as nothing more than a thin facade of consensus building to force the implementation of your preferred solution. -- ShinmaWa( talk) 05:57, 9 November 2013 (UTC)
I don't have a preferred solution other than hoping that the community will come up with some criteria for sufficient experience for reviewers. All I have done is cited some examples as possible leads, but they are absolutely neither my recommendations nor preferences, I simply made the first suggestion to get the ball rolling, and I am as entitled to make a suggestion there are you are. Having reviewed every further comment I have made, I don't see me insisting on them; more to the point, I have simply attempted to keep this discussion on track. I stress again that any possible implementation of such criteria should/would come later. There is no harm whatsoever in looking into how permissions for Stiki, Huggle, or AWB are locally implemented - it's called 'gathering knowledge'. I don't see how you or anyone can suggest I have claimed otherwise. I am tempted to view your accusations as lacking in good faith. If you have some suggestions for criteria, please make them, but this RfC is not for redebating whether AfC needs competent reviewers or not. Kudpung กุดผึ้ง ( talk) 06:49, 9 November 2013 (UTC)
Where have I redebated whether AfC needs competent reviewers? Again, you are putting words in my mouth. While I came to this discussion assuming good faith, you have shaken that assumption. I am moving on to other things and will no longer participate here as this RfC is not a request for comments but a request for confirmation. -- ShinmaWa( talk) 18:34, 9 November 2013 (UTC)
ShinmaWa, methinks I can understand the ongoing back-and-forth here. I was personally confused about what Kudpung was trying to accomplish, myself, also, but believe I'm on the same page with them now. (Due to my confusion, earlier, my suggestion-by-74 above absolutely positively demands a very specific implementation -- very different from what Kudpung envisions I will not -- but more importantly solves a completely different problem!) See deeper explanation below. Hope this helps. 74.192.84.101 ( talk) 21:23, 18 November 2013 (UTC)
As I understand it, *this* discussion, on *this* page, is about trying to find consensus for a reasonably *specific* set of secondary criteria (like edit-counts) that are specific to helping guarantee that editors that sign up to be AfC reviewers are morally competent for that role. 74.192.84.101 ( talk) 21:23, 18 November 2013 (UTC)

What is the motivation for this RfC?

The motivation is, reading between the lines, there are plenty of examples -- of increasing frequency if I correctly read between the lines -- of new editors with WP:COI difficulties signing up as AfC-reviewers, and then approving the blatantly-policy-violating-articles of their buddies, or in some cases of themselves. To stop such shenanigans, we need to agree on a set of secondary criteria (minimum edit-count being the most obvious). Then, once we have got consensus on the thing we will be using to secure the AfC process against abuse, there would be a discussion about how to best implement -- in software or in human-administered-policy or whatever -- some sort of security mechanism that *enforces* those secondary criteria.

  The mechanism itself, Kudpung does not wish to get bogged down in, as yet... but that topic is supposed to be the very next RfC, right after this one! Also, since Kudpung is not a programmer, that makes it hard for them to be the host a mechanism-oriented discussion (as opposed to this current policy-oriented RfC). But the point is, that the nuts-n-bolts implementation mechanism... although it will clearly have *something* to do with software that *some* sort of programmer will have to mess with at least some of it... would ideally be out of scope (aka "off track" or perhaps rather "cart ahead of the horse" or somesuch homely metaphor), at least until we decide upon what specific secondary-criteria we are actually trying to secure! Note well the careful use of ideally. Furthermore, we do have a few relevant facts, that are "implementation" facts, but which may influence our discussions here about "criteria-slash-policy" decisions.

  1. First, the WMF will not be footing the bill. That means, the implementation has to be simple enough that volunteer hackers, here on enWiki (like perhaps User:mabdul) to implement on a spare-time no-pay basis. That is why suggestions to modify mediawiki are out of line: we do not want to fork mediawiki just for enWiki's use!
  2. Second, *most* of the folks already working in AfC today, are already using the existing javascript-based AfC-helper-script-gadget (which is maintained by User:mabdul and others), and it makes sense that whatever secondary-criteria-security-solution we come up with, should interface with our existing wiki-tools. That is the 'script' that Kudpung speaks of, nothing more, nothing sneaky going on here.
  3. Third, and finally, it is a plain-and-indisputable-fact that we would like whatever 'implementation' mechanism is chosen to be low-bureaucracy-required, because there are literally thousands of AfC-submissions pending in the queue, and anything that takes our AfC reviewers away from that queue, is a Bad Thing. That is why any solution involving laborious additional tasks for the existing AfC reviewers is seen as strongly counterproductive; they are already under too much pressure now, and adding these criteria cannot help, and might easily hurt.

Finally, in terms of out-of-scope discussions, we have my own suggestion, which I now understand is "off topic". The separate issue, which I concentrated on in my suggestions, is whether it is possible to assess *primary* criteria, namely, whether a given AfC-reviewer-job-candidate is actually any good aka technically-competent at performing reviews (without later getting reverted for mistakes). This is my main concern... but this question is utterly orthogonal to the question of whether an AfC-reviewer-job-candidate is any Good aka morally-competent at performing reviews (without later getting banned for abuse). Both types of competence are important, sure... but only the morally-competent secondary-criteria are under discussion here. Well, that is to say, those are what ought to be under discussion here.

  Kudpung tried valiantly to explain what was going on, but most people misinterpreted the actual intro of the RfC, which used examples in a way that looked like preferred-outcome, and which failed to inform newcomers like myself that the motivation for the whole shebang is prevention of WP:PUPPET folks abusing the AfC queue. Stopping that sort of behavior requires moral-competence, and technical-competence is a distinct issue. Most discussions above are trying to solve all three problems simultaneously: implementation details, technical prowess at AfC duties via primary/secondary criteria (in the relevant decision-areas), and moral competence at AfC duties via secondary-criteria (in terms of ethical-commitment-to-wikipedia-metrics).

  Anyways, while I disagree that Kudpung has tried to ramrod some particular implementation down our throats, I cannot disagree that the current RfC is in trouble. Either we need to have an arbitrary-section-break, with a rewritten-motivation-and-examples section, so we can then copy the proposals down there that *specifically* address the moral-competence and the ethical-commitment-to-wikipedia angles (only!), or alternatively, maybe even take ShinmaWa's suggestion to deploy the WP:TNT, and reopen round-two of this RfC with the rewritten-motivation-and-examples. I will ping ShinmaWa about this long-winded explanation, and hope that they return to assist us. 74.192.84.101 ( talk) 21:23, 18 November 2013 (UTC)

Better alternative - Close AfC

It's outlived its usefulness and is run by a clique of editors who treat it like a personal fiefdom operating under its own rules, ignoring rules that govern the project as a whole, and beat away those contributors who think differently (despite being well-supported by those ignored policies and guidelines). If anyone wants to create an article, let them open an account and create the article already--let speedy deletion or AfD deal with it if it should be deleted. Clear out the backlog, get rid of the endless drama and fiefdom-ownership politics, and let this dinosaur finally die. -- ColonelHenry ( talk) 21:09, 30 December 2013 (UTC)

Round 2: Straw poll

We've had the discussion, now it's time to gather consensus. To reiterate, the above discussion was about setting criteria for allowing users to review pages submitted to AfC. There was no mention in the proposal that the methods of implementation or other methods of reviewer control were up for discussion. It was stated that the criteria should come first, then the community can discuss how best to implement them. This straw poll is not for discussing the implementation either. The criteria mentioned in the preamble were cited strictly as examples only and were not suggestions either for what we should do, nor for a traditional 'user right' implementauion.

There are two major issues concerning reviewing at AfC:

  • Poor quality of reviewing.
  • Abuse of the system.

Proposal 1

To review pages at Articles for Creation, users should have made a minimum of 500 non-automated edits to en.Wikipedia mainspace, with an account registered for at least 90 days.

  • Support, as proposer. Kudpung กุดผึ้ง ( talk) 23:49, 18 November 2013 (UTC)
  • Support - a sensible amalgamation of the aforementioned ideas. Not too stringent, not too lenient. Ultimately, I think this is the best way to go. Go Phightins ! 01:22, 19 November 2013 (UTC)
  • Support Let's take into account that before this, there was basically no requirement. This proposal screens out obvious new users and does not create an opportunity for a backlog to occur of those seeking the AfC reviewer permission and is objective, not subjective. Ramaksoud2000 ( Talk to me) 03:22, 19 November 2013 (UTC)
  • Oppose any requirement on second thought. If someone wants policy-violating material in the mainspace, they can simply create it themselves. autoconfirmed to move the page is enough and is more than the requirement to create articles the normal way. Ramaksoud2000 ( Talk to me) 18:37, 30 December 2013 (UTC)
  • Support - It's simple, unambiguous and straightforward, and anyone who doesn't meet the criteria can do so with time and experience. Ritchie333 (talk) (cont) 14:50, 19 November 2013 (UTC)
  • Support - I like it because it assumes good faith and allows everyone with a little experience to take part. There needs to be a way to prevent misuse, but there is already the "topic ban", which could be used in case of problems with specific editors. I assume that these would be 500 undeleted edits, so that spam and copyvios wouldn't count. — Anne Delong ( talk) 15:26, 19 November 2013 (UTC)
  • Oppose as I feel this is too lenient. See proposal 3 below (as much as I hate to make another proposal splitting up the votes...) Technical 13 ( talk) 15:56, 19 November 2013 (UTC)
  • Support. It's a low bar, but at least it's a bar. The documentation should indicate somehow that this is not an entitlement to review. -- Anthonyhcole ( talk · contribs · email) 03:03, 21 November 2013 (UTC)
  • Support - A nice bar that will allow anyone with good faith and a decent handle on Wikipedia to work. Will prevent an insane backlog from forming. Nice and simple. ö Brambleberry of RiverClan 16:09, 27 November 2013 (UTC)
  • Support, as the lowest proposed bar. Ironholds ( talk) 07:41, 2 December 2013 (UTC)
  • Support low bar with minimal "overhead". All it requires is a "filter" to be added to the AFCH script that simply checks the user's mainspace edit count and registration date. It doesn't add to the workload of the existing reviewers. This criterion will also be easy to carry over to whatever review mechanisms will be implemented for the upcoming Drafts namespace. Roger (Dodger67) ( talk) 09:40, 2 December 2013 (UTC)
  • Support- minimal standard. Rankersbo ( talk) 10:51, 9 December 2013 (UTC)
  • Support with one addition, namely this: any two approved-at-the-time AfC reviewers X and Y, can by mutual agreement, appoint a third person Z, thereby making Z an AfC reviewer, despite Z not meeting the criteria. 74.192.84.101 ( talk) 16:15, 9 December 2013 (UTC)
  • Support. This is certainly not burdensome, and if anything is too lenient. I think the second proposal, just below, would create additional workload for whoever does the reviewing, and the third proposal really isn't a significant improvement on this one, so I support this one as a step in the right direction. -- Tryptofish ( talk) 21:02, 12 December 2013 (UTC)
  • Monumental oppose for the reasons I have given in proposal 5. James500 ( talk) 13:57, 31 December 2013 (UTC)
  • Support, This is the only practical workable proposal I see. Alanl ( talk) 08:15, 12 January 2014 (UTC)
  • Support - Quite simple, users with these requirements show knowledge in the policies and guidelines. ///EuroCar GT 00:32, 13 January 2014 (UTC)

Proposal 2

Reviewers at Articles for Creation will be selected after evaluation of 10 sample reviews performed (as detailed out at the relevant suggestion section from TheOriginalSoni above)

  • Kudpung There is no overload on the existing pool of reviewers, if you look at the proposal carefully. TheOriginalSoni ( talk) 02:31, 19 November 2013 (UTC)
Too complex and someone still needs to control it. Kudpung กุดผึ้ง ( talk) 05:53, 19 November 2013 (UTC)
My now-collapsed proposal is very similar to what OriginalSoni proposes, except fully automated (no burden on existing AfC folks at all)... but therefore dramatically more complex (adds burden to mabdul/Technical_13/Theopolisme/etc who are the AfC devs right now. See below, suggest we finish implementing the Kudpung approach, and then later open another RfC about the OriginalSoni approach, as complementary (not conflicting). This is not a zero-sum-game, we can actually have our cake an eat it too, in this rare case.  :-)   — 74.192.84.101 ( talk) 16:08, 9 December 2013 (UTC)
  • Oppose Too stringent and long and creates the opportunity for a backlog to form. It is also subjective, and not objective. Ramaksoud2000 ( Talk to me) 03:25, 19 November 2013 (UTC)
  • Oppose as I feel this is too stringent. I agree that it requires too much reviewer time UNLESS there is someone (like me) that doesn't spend a lot of time on reviews and focuses on AfC project management (like helper script development) that has the time to go through and review these users. See proposal 3 below (as much as I hate to make another proposal splitting up the votes...) Technical 13 ( talk) 15:56, 19 November 2013 (UTC)
  • Are you suggesting that we start a new proposal for a "reviewer reviewer" hat? Noooo..... — Anne Delong ( talk) 16:40, 19 November 2013 (UTC)
  • Defer proposal#2, for consideration as a future RfC. The point of OriginalSoni's proposal is to grade potential reviewers on the *merits* of their technical proficiency at reviewing. If they are good at it, they will get 9 out of 10 correct, on the quiz. This is not only different from, but orthogonal to Kudpung's proposal, which is primarily intended to prevent *abuse* of the AfC reviewer infrastructure, by folks that are not committed to the long-term goals of wikipedia. 500 edits and 90 days is a security-system, in other words. Getting 9 out of 10 correct is a competence-check. As Technical_13 points out below, it is theoretically possible to perform 6 spelling-corrections each day for three months, and thus "pass" the security-system, yet still be Not Very Good at correctly reviewing submissions.
  But my suggestion is that we should be careful to neither confuse nor conflate the two goals. Testing competence at correctly reviewing submissions should be *ongoing* and not just an "interview" which means there is a need for what OriginalSoni is proposing, that directly test competence in actual reviewing-work. At the same time, plenty of COI sockpuppets will be able to pass the 10-question-quiz with flying colors, so we also need some sort of morality-quiz that proves a minimal dedication to the five pillars. This necessarily will have to be a secondary criterion: 90+ days editing, and 500+ edits, seems like a reasonable proxy-for-commitment. HTH. 74.192.84.101 ( talk) 16:08, 9 December 2013 (UTC)
  • Monumental oppose for the reasons I have given in proposal 5. James500 ( talk) 13:57, 31 December 2013 (UTC)
  • Oppose . A good idea, but alas we don't have enough experienced reviewers doing AfC to devote to do the auditing. Alanl ( talk) 08:18, 12 January 2014 (UTC)

Proposal 3

To review pages at Articles for Creation, users should have made a minimum of 500 non-automated, non-minor edits to the English Wikipedia mainspace, with an account registered for at least 90 days with regular activity.

  • Support as proposer. Technical 13 ( talk) 15:56, 19 November 2013 (UTC)
  • Oppose - I think this is too restrictive. Spelling fixes may be marked as minor edits, but they're most definitely helping the project. What's "regular activity"? I took a Wikibreak in April this year - would that count against me? Ritchie333 (talk) (cont) 16:17, 19 November 2013 (UTC)
  • What's the point of a 90 day requirement if the user creates an account, makes a couple hundred punctuation fixes, goes away for 85 days, comes back and gets their edit count to 500 fixing spelling and what not. There are no significant edits and they have maybe 10-15 days of editing. I think we gain nothing by this, and this minor adjustment to P1 rectifies this. Technical 13 ( talk) 16:32, 19 November 2013 (UTC)
Do you think that's a likely scenario? Anyone can game the system if they want. You can run for RfA the minute you score 500 on Scottywong's tool - it doesn't mean you'll succeed! For those people, we can simply nudge them in the right direction, and topic ban them if necessary. Ritchie333 (talk) (cont) 16:43, 19 November 2013 (UTC)
When I first had 500 mainspace edits on the English Wikipedia, I would've had no place reviewing AfC submissions. I think it is a very likely scenario. If there are going to be count and time restrictions, let's make sure they actually do something other than look pretty. Technical 13 ( talk) 18:16, 19 November 2013 (UTC)
  • Comment (edit conflict) - I don't think that this proposal is significantly less lenient than Proposal 1, since the user chooses whether or not to mark edits as "minor". Please explain why you think that evenly spaced edits are better than bunched-up ones. I suppose that you are hoping to ensure that they are five hundred substantive edits (rather than, say, adding a piece of spam to 500 articles...) — Anne Delong ( talk) 16:26, 19 November 2013 (UTC)
  • Anne, I do believe you misunderstood what I wrote about minor edits. I did not mean necessarily edits marked as minor, I meant edits that qualify as minor in that only superficial differences exist between the current and previous versions. Examples include typographical corrections, formatting and presentational changes, and rearrangements of text without modification of its content. Whether or not the editor knows how to properly mark such edits may be out of scope (other than I would question a user with the first 500 sequential edits and having none marked as minor as really having any CLUE about policies and how to review articles). Technical 13 ( talk) 18:29, 19 November 2013 (UTC)
  • Oppose, after the above explanation. Not because I disagree with with anything you've said above, but I wouldn't be willing to do the work of measuring the value and complexity of hundreds of edits, so I can't !vote to put that work on someone else. — Anne Delong ( talk) 18:55, 19 November 2013 (UTC)
    • Administrators already do this at WP:RFPERM to hand out rights like reviewer and rollback. (Personally I don't think any rights should be necessary to review AfC nominations. If you wish to clamber through Wikipedia's crap pile to find the odd gem, have at it. Rather them than me.) — Tom Morris ( talk) 13:56, 27 December 2013 (UTC)
  • Oppose Anybody at all can create articles. Anybody. So why would you think someone would try to game the system as you said above and accept or deny a review if they can go ahead and create an article. Ramaksoud2000 ( Talk to me) 18:15, 30 December 2013 (UTC)
  • Monumental oppose for the reasons I have given in proposal 5. James500 ( talk) 13:57, 31 December 2013 (UTC)

Proposal 4: Piggy-back on rollback or PC reviewer

We already have two user rights we give out to people who have reached minimal competence with Wikipedia: pending changes reviewer and rollback. Because of the potential for hat collecting, it seems generally preferable to not duplicate entities beyond mere necessity. At a time when we have few enough people willing to delve through the ever-regrowing crap pile not only at WP:AFC but at a wide number of backlogs across the 'pedia. The main problem with AFC isn't bad reviewers, it's no reviewers. Adding another layer of gate-keeping on the front of an already backlogged process seems rather pointless. Instead, use the existing permissions structure: rollback, or pending changes reviewer. This isn't unheard of: when Article Feedback Tool v5 was still in operation on English Wikipedia, we reused the "reviewer" permission for reviewing AFT5 comments.

The advantage of this: administrators don't have to start handing out new permissions. The number of hats on offer is kept to an absolute minimum. We neatly sidestep the addition of more bureaucracy. — Tom Morris ( talk) 14:41, 27 December 2013 (UTC)

  • Support As proposer. — Tom Morris ( talk) 14:41, 27 December 2013 (UTC)
  • Oppose: This RfC does not discuss how this threshold will be granted and/or implemented. That will be the topic of a further discussion, when the threshold itself has been established. Kudpung กุดผึ้ง ( talk) 21:36, 27 December 2013 (UTC)
  • Kudpung, I do not think Tom made any statement towards that context. All he stated was to use a simple Reviewer or Rollbacker as the required permission threshold. (Correct me if I'm wrong on the reviewer-rollbacker part.) TheOriginalSoni ( talk) 22:21, 27 December 2013 (UTC)
  • Support This proposal neatly sidesteps any possible hat-collection issues we had, while still solving our basic competence requirements, like Proposal 1. It also makes it technically simple to implement any such requirements. TheOriginalSoni ( talk) 22:21, 27 December 2013 (UTC)
  • Question. What is being suggested here, exactly? That we dramatically reduce the count of viable candidates for AfC duty? Or that we dramatically increase the count of people with the R&R userRight?
explanation of my question
  Proposal#1 sets the low-but-not-too-low bar of 500+edits and 90+days, not to increase hat-count, but to keep out spammers that approve their sockpuppet's spam, and buddies who approved their friend's non-Notable garage-band. It is basically a minimum-morals qualification-criteria, indicating some level of commitment to wikipedia's goals. It is one step up from autoconfirmed. Now clearly, the current user-rights of reviewer && rollbacker *are* morally qualified. But currently, it is a *lot* more effort than 500 edits, and a lot more time invested than 90 days, before an editor is "whitelisted" by being given the R&R bits. Are we setting the bar too high, for being an AfC reviewer, if we demand only R&R-quality folks and above?
  How many of our existing hard-working AfC reviewers have the R&R bits, right now today? More pragmatically, I will point out that we already have plenty of folks with R&R bits... and any of them, or all of them, would be welcomed with open arms, if they showed up to help with the AfC queue tomorrow morning. And yet, there are still well over 1k articles in the main queue, and well over 10k in the G13 backlog. If we want those backlog-numbers to decrease, we would need to vastly expand the number of people who are given R&R bits. I think there are two possibilities for what proposal#4 means.
  Possibility#1, Tom_Morris is putting forth Proposal#4, and saying that only existing R&R bit-holders ought be allowed to become AfC reviewers... in which case, I oppose proposal four, on the grounds that there are simply not enough existing R&R bit-holders to solve the AfC backlog. 5992 reviewers and/or 4981 rollbackers, with significant overlap, plus 1423 admins that have those powers and more. Only 45% of admins are "active" aka ~15+edits/mo... conservative assumptions about overlap & activeness, means we might have 2700-to-3700 active R&R folks today, plus 600 active admins... aka roughly one R&R-or-admin for every 7 active editors. We also have 3000 very-active-editors making 100+edits/mo, [1] and an educated guess is that these 1-to-9-folks are the basically the *same* editors as the 1-to-7-folks that already have the R&R user-right.
  Possibility#2, Tom_Morris is suggesting that we dramatically increase the number of people who are given R&R bits... and in fact, might even be saying that every person with 500+edits and 90+days should automagically be given the pending-changes-reviewer bit, which could then also double as the AfC-submission-reviewer bit. Possibility#2 is something I could support... but as Kudpung says, that is an implementation question (we could also implement the 500-n-90 restriction purely as a jscript hack inside AFCH or as a custom server-side PHP kludge or as a pure social system using moral suasion or in various other ways). It's not clear that it will be easy to gain consensus for dramatically lowering the traditionally-pretty-dern-high level of experience that R&R bits have demanded in the past, to just 500-n-90. Therefore, if possibility#2 is the aim, in that case I would suggest deferring proposal#4 as an implementation-question, to the next phase of this RfC-sequence. 74.192.84.101 ( talk) 00:52, 30 December 2013 (UTC)
My point is that "500 edits + 90 days" (plus a quick manual check to make sure they aren't mad as a hatter) is about the rough guideline that admins use to hand out rollback or reviewer. I'm simply saying that we already have a process to determine whether or not new users are sensible enough to start reviewing (and indeed rolling back) other people's edits. — Tom Morris ( talk) 11:02, 30 December 2013 (UTC)
Remember that anybody can create articles with an account. Suggesting that you need rollback and reviewer is kind of too much. Ramaksoud2000 ( Talk to me) 18:10, 30 December 2013 (UTC)
  • Ramaksoud2000, this discussion is for who can review AFC submissions. I think a large number of our current AFC reviewers will have either of these priviledges, and almost all of the rest would be given the permission should they request it. TheOriginalSoni ( talk) 21:58, 30 December 2013 (UTC)
  • I'm saying what's the point of making the requirement so high when they can just create the article another way. Ramaksoud2000 ( Talk to me) 05:56, 31 December 2013 (UTC)
  • Ramaksoud2000, AFC Reviewers do not write the articles. The articles are written by newcomers, and reviewers "review" them, thus approving or declining the article. As I said, most current AFC reviewers alaready have this right. TheOriginalSoni ( talk) 10:54, 31 December 2013 (UTC)
  • In all fairness, there is no difference in principle between accepting an AFC submission and creating a new page from scratch. James500 ( talk) 12:29, 31 December 2013 (UTC)
  • Monumental oppose for the reasons I have given in proposal 5. James500 ( talk) 13:57, 31 December 2013 (UTC)

Proposal 5: Maintain consistency with rights to create articles from scratch

Any registered user can accept an AFC submission. Only users with either the reviewer or rollbacker user right can decline an AFC submission.

  • Support as proposer. It would be absurd to prohibit users who can create new pages in the mainspace from accepting an AFC submission. It would not be consistent with existing user rights at all. James500 ( talk) 11:37, 31 December 2013 (UTC) In fact you could argue that, in order to be completely consistent, only admins should have the right to reject an AFC submission, because they are the only ones who, at present, have the authority to remove an article from the mainspace by deletion or otherwise. James500 ( talk) 12:10, 31 December 2013 (UTC)
  • Oppose as that is entirely inaccurate. Any autoconfirmed user can move a page from mainspace to a subpage of a user's space or to Draft: effectively removing from mainspace. Allowing any user to accept, is also counter productive as AfC is intended to help new users create an article with out it getting speedily deleted half a dozen times for simple issues like promotional tone or lack of indication of importance, allowing all users unable to see these things or whom are unfamiliar with the policies/essays/guidelines that can give constructive feedback is a bad idea. Technical 13 ( talk) 12:48, 31 December 2013 (UTC)
I disagee. What WP:USERFY actually says is "Except for self-userfying and obvious non articles such as accidentally-created user pages in the main namespace, it is generally inappropriate to userfy an article without a deletion process". The recommended process is AfD. So, assuming the essay you have linked to is accurate, a non-admin cannot userfy an attempt at a proper article that someone else has created. James500 ( talk) 13:08, 31 December 2013 (UTC) And the other limb of your argument is absurd. James500 ( talk) 13:17, 31 December 2013 (UTC) And "promotional tone" is not a criteria for speedy deletion. What is required is blatant advertising. James500 ( talk) 13:27, 31 December 2013 (UTC)
  • Oppose - Any confirmed user can move an article out of Afc and into mainspace to create an article (at risk of being reverted, or course). The above proposals 1-4 won't prevent that. They are only about limiting the use of the Afc reviewing tools and Afc review templates which give the appearance that the person placing them is an experienced and knowledgeable editor, and not someone who joined Wikipedia last week. There are exceptions, of course; a use with a new account could have been editing under another name, or as an IP, for years, but as usual the application of the criteria will be tempered by common sense. — Anne Delong ( talk) 14:32, 31 December 2013 (UTC)
As far as I am aware, a page move from AFC to the mainspace cannot be reverted without a deletion process (such as AfD), except in very limited circumstances. James500 ( talk) 15:11, 31 December 2013 (UTC) If the proposals above are only about access to scripts and templates, their wording needs to be made much clearer. I can't actually find a project page that defines the meaning of "review" and "reviewer" in this context. It sounds like "move into the mainspace". It is clear to me from the foregoing discussion that I am not the only one who thinks this. James500 ( talk) 15:59, 31 December 2013 (UTC)
I hope some others will weigh in about the meaning or "reviewer". And yes, you are right; I shouldn't have said "revert". The more likely (and more serious) results of an inexperienced editor moving a draft prematurely to mainspace would be: (1) speedy deletion under a number of categories from which the draft submissions are protected so that the problems can be fixed, and (2) being dragged to Afd. In either case the poor draft creator, usually a beginning user, could be very bewildered and have an unnecessarily negative experience, all so that some other new user can have the freedom of creating an article out of someone else's draft without having to take the time to learn any of Wikipedia's policies. — Anne Delong ( talk) 19:16, 31 December 2013 (UTC)
Prohibiting "inexperienced" users from moving drafts into the mainspace might help deletionists in their mission to prevent the creation of perfectly valid stubs. James500 ( talk) 20:35, 31 December 2013 (UTC)
  • Oppose as already detailed by Anne and Technical13. The need for this RFC is to make sure AFC performs better in making sure it's articles survive Mainspace, not the other way round. The current proposal is detrimental to the AFC process, and will work against getting better articles out of here. TheOriginalSoni ( talk) 21:26, 31 December 2013 (UTC)
I disagree. It is clear to me that AFC reviewers are rejecting submissions that would survive (and have survived) an AfD. In any event, if you are worried about articles on valid topics surviving in the mainspace, what you need to look at are the deletion processes, because that is where the problem will be. James500 ( talk) 07:34, 1 January 2014 (UTC)
  • Oppose. I seriously doubt any AfD proposal will survive, and there been many attempts over the years. There are enough orphaned stubs out there in mainspace, and as a mature project, the whole point of AfC is to improve the quality of new articles. If you allow this, then you might as well disband AfC altogether. Alanl ( talk) 08:26, 12 January 2014 (UTC)

Proposal 6: Complete consistency with other deletion processes

Any registered user can move an AFC submission into the mainspace, whereupon it will be treated like any other article. Only users with either the reviewer or rollbacker user right can use AFC scripts and templates. Subject to the following exception, only users with the admin user right can decline an AFC submission. The exception is AFC submissions that are clearly not intended to be articles (ie those that , if created in the mainspace, could be legitimately userfied by a non-admin). Non-admins can nominate an AFC submission for rejection, using a template created for this purpose.

  • Support as proposer. This is probably my first choice on grounds that rejecting an AFC submission is equivalent to deleting an article from the mainspace. James500 ( talk) 07:34, 1 January 2014 (UTC)
  • Strong Oppose This isn't even consistent with deletion processes as your title claims. Ramaksoud2000 ( Talk to me) 05:20, 7 January 2014 (UTC)
This is proposal is exactly consistent with deletion processes. In what way is it not consistent? James500 ( talk) 08:47, 12 January 2014 (UTC)
  • Absolutely Oppose the proposers completely erroneous claim that "rejecting an AFC submission is equivalent to deleting an article from the mainspace" only shows that the proposer has no clue at all about how AFC actually works. An AFC rejection is simply: "this draft isn't ready yet because of this problem, here is a guideline on how to fix it. When you've fixed it please resubmit it. If you need further assistance you can get it here". Roger (Dodger67) ( talk) 08:29, 12 January 2014 (UTC)
My claim that "rejecting an AFC submission is equivalent to deleting an article from the mainspace" is based on similar reasoning in WP:USERFY, and I don't believe that there is any difference in principle. Bear in mind that rejection also facilitates CSD G13, so we don't want it done in error. G13 does not, in express words, require the admin to vouch for the correctness of the rejection. It seems to me that he could just rubber stamp it. So, if you allow reviewers and rollbackers to reject submissions you are potentially giving a user with 500 edits the power in effect to speedy delete large numbers of articles at his discretion with no questions asked. James500 ( talk) 08:38, 12 January 2014 (UTC)

Proposal 7

Amend CSD G13 so that it authorizes the speedy deletion of a rejected AFC submission only if that submission was correctly rejected.

  • Support as proposer. This would remove what is, in my view, a potentially serious problem with allowing non-admins to reject AFC submissions. See my comments under proposal 6. James500 ( talk) 04:03, 13 January 2014 (UTC)


Pages recently put under extended-confirmed protection

Report
Pages recently put under extended confirmed protection (24 out of 8013 total) ( Purge)
Page Protected Expiry Type Summary Admin
Template:Dune franchise 2024-07-15 01:57 2024-10-15 01:57 edit Persistent sock puppetry NinjaRobotPirate
That's Entertainment (Hazbin Hotel) 2024-07-15 01:43 2024-10-15 01:43 edit Persistent sock puppetry NinjaRobotPirate
July 2024 al-Shati refugee camp attack 2024-07-15 00:00 indefinite edit,move Arbitration enforcement, see Wikipedia:Contentious topics/Arab–Israeli conflict Bradv
Ruth Westheimer 2024-07-14 21:35 2024-08-14 21:35 edit,move Contentious topic restriction: WP:A/I/PIA ToBeFree
Template:Fa top 2024-07-14 18:00 indefinite edit,move High-risk template or module: 2501 transclusions ( more info) MusikBot II
Zionism 2024-07-14 16:31 indefinite edit,move Arbitration enforcement: Removing full protection per progress on talk page Bradv
Thomas Matthew Crooks 2024-07-14 16:00 indefinite edit Disruption magnet; requested at WP:RFPP; WP:ARBAP2 Abecedare
Template:Current event 2024-07-14 07:39 indefinite edit,move High risk template Zzuuzz
File:Shooting of Donald Trump.webp 2024-07-14 02:07 indefinite edit,move,upload Irrespective of whether this gets kept or deleted at Wikipedia:Files for discussion/2024 July 14, it is a risk to have it unprotected on such a high visibility article. Protecting in line with the main article. Daniel
2024 shooting at a Donald Trump rally 2024-07-14 00:01 2025-01-13 23:20 edit Immediate risk of move warring Fences and windows
2024 assassination attempt of Donald Trump 2024-07-13 22:56 2025-01-13 23:20 edit Persistent vandalism ScottishFinnishRadish
Death Shelters 2024-07-13 22:55 indefinite edit,move Contentious topics enforcement for WP:CT/A-I; requested at WP:RfPP Daniel Quinlan
2024 targeted assassination of Muhammad Deif 2024-07-13 19:54 indefinite edit,move Contentious topics enforcement for WP:CT/A-I; requested at WP:RfPP Daniel Quinlan
13 July 2024 Al-Mawasi airstrikes 2024-07-13 19:47 indefinite edit,move Contentious topics enforcement for WP:CT/A-I; requested at WP:RfPP Daniel Quinlan
Aaron Maté 2024-07-13 18:09 2025-07-13 18:09 edit,move Contentious topics enforcement for WP:CT/BLP; requested at WP:RfPP Daniel Quinlan
Hruso people 2024-07-12 21:05 indefinite edit,move Persistent disruptive editing: per RFPP; will log at WP:GS/CASTE Daniel Case
Koli Samaj 2024-07-12 14:06 indefinite edit Persistent sock puppetry by warring sock-farms including Wikipedia:Sockpuppet investigations/Thakor Sumant Sinhji Jhala Abecedare
Levantine Arabic 2024-07-12 12:30 indefinite edit,move Contentious topic restriction: Arab–Israeli conflict K6ka
Antioch International Movement of Churches 2024-07-12 02:37 2025-01-12 02:37 edit Persistent sock puppetry The Wordsmith
Mohsin Hossain Bablu 2024-07-12 00:47 indefinite create Repeatedly recreated BusterD
Adult Swim (Latin American TV channel) 2024-07-11 20:54 2024-08-11 12:00 edit,move persistent disruptive editing & block-evasion JBW
Draft:Suck my dick 2024-07-11 16:31 indefinite create Offensive name BusterD
Draft:Ari 2024-07-11 16:24 indefinite create Repeatedly recreated BusterD
Draft:Saeed Khan Bozdar 2024-07-11 12:19 indefinite create Repeatedly recreated Amortias

ARBPIA gaming?

The user Amayorov, despite having an eight-year-old account, made their first edit on 3 July 2024 before proceeding to pass 500 edits and receive extended confirmed permissions on 6 July 2024. All of the edits made, 100s a day, were on European politics and history. Shortly after achieving EC permissions, suddenly it's all 1948 Palestine war, specifically inserting Benny Morris as a source all over the place and doing some work on the Benny Morris biography. Apparently European content has lost its appeal. Make of this what you will. I also have to wonder if, despite having an extant account for 8 years, achieving 500 edits in three days (rather than the 30 days as envisaged in the ECR rule set) is somewhat of a violation of the spirit of the restrictions, even if not the technical function. Iskandar323 ( talk) 19:08, 7 July 2024 (UTC)

Were there any issues with the edits?
Discussions recently have come to the conclusion that absent obvious abuse - unproductive or disruptive edits, or repeatedly making a dozen edits to do what could be done in one or two - it’s acceptable for editors to work towards ECP.
To an extent, this makes sense - if we tell people "this is what you need to edit this topic area" we can’t reasonably expect editors interested in the topic area to not work towards it. BilledMammal ( talk) 19:16, 7 July 2024 (UTC)
see my reply Amayorov ( talk) 19:19, 7 July 2024 (UTC)
Issues other than that pushing Benny Morris here there any everywhere with little regard for any other sources is a terrible form of disregard for NPOV? That alone, in a contentious topic area, is pretty disruptive. The 500/30 rule is aimed at ensuring a minimum level of understanding and competency. Yes, some are encouraged to rush the requirements, but we shouldn't encourage editors to rush the requirements. Iskandar323 ( talk) 19:20, 7 July 2024 (UTC)
I did not "push Benny Morris" but rather expanded on the already existing citations to his work. Recall that Benny Morris' 2008 book had already been the most quoted reference on that page. When necessary, I've added phrases such as "some scholars allege that" etc.
When you and other users disagreed with my edits, I didn't proceed, but rather created sections on the Talk page. Unlike other users, you didn't engage.
I think the extensive sourcing I use in any of my edits illustrate that I at least possess "a minimum level of competency". Amayorov ( talk) 19:26, 7 July 2024 (UTC)
I have engaged. As of the time of me writing this, there are at least two comments from me to you that you have not responded to. Again, this can be checked. I suggest you desist from misrepresenting very verifiable information in this forum. Iskandar323 ( talk) 19:39, 7 July 2024 (UTC)
You wrote those comments less than an hour before reporting me on the Admin board. Yes –– all of this can be checked.
I suggest you desist from misrepresenting very verifiable information in this forum. Amayorov ( talk) 19:51, 7 July 2024 (UTC)
I meant in regardless to the substance of this complaint - with the edits to reach 500.
If we don’t tell editors that they can’t work towards 500/30, then how should they know we don’t want them to work towards them? If the goal is to ensure a minimum level of understanding and competency, and 500 edits isn’t sufficient for that, then let’s modify the requirements - for example, require edits to be a minimum byte size to count, as I have proposed in the past. BilledMammal ( talk) 19:28, 7 July 2024 (UTC)
I think that would be a good idea. However, I have clearly written plenty of bytes in my 500 edits, in some cases going as far as copy-editing entire pages that had been poorly translated or unsourced. You can see all that in my edit history. Amayorov ( talk) 19:30, 7 July 2024 (UTC)
This is patently false. I have made extensive edits to various topics, including military history and Central Asian history, paganism, and engineering. All my corrections were extensively referenced. I have also rewritten several large articles, requiring copy-edit and verification.
It is true that I have re-activated my account in the week. This is simply a reflection of the fact that I have free time, and have grown fond of Wikipedia.
Benny Morris' 1948 book has always been the most referenced book on the topic. I have used not only that book but also others by different authors, as well as sourcing UN archives.
I have added corrections and more references on the subject, including 1948 Palestinian expulsion and flight and Palestinian nationalism. None of the other users had an issue with my work.
By contrast, @ Iskandar323 has reverted my edits without giving a justification. They also ignored my attempts at a discussion in the Talk pages. Amayorov ( talk) 19:19, 7 July 2024 (UTC)
I had a justification, and I have responded on talk. I suggest that you avoid misrepresenting things that can be checked up on (on an administrative noticeboard). And yes, other users have taken up issue with your edits. I'm not sure why you would misrepresent this. Iskandar323 ( talk) 19:24, 7 July 2024 (UTC)
Your justification was RV gf edits - unfortunately, adding random titbits of background information from Morris, removing dates and badly rephrasing other parts is not an improvement.
This is not specific or constructive. In order to clarify your objections, I created discussion topics on the Talk page – which you have ignored. Amayorov ( talk) 19:27, 7 July 2024 (UTC)
I have responded to some, not all of your posts. However, I would prefer to see what administrators think of this situation before potentially unduly spending more time on explaining why expanding claims from a single source that is, in your own words, already the most [(over-)]quoted reference on the page, is not particularly in the service of NPOV. Iskandar323 ( talk) 19:35, 7 July 2024 (UTC)
You have responded to them half an hour ago, almost immediately posting on the Admin board.
Yes, Benny Morris is the most quoted historian on the 1948 war. I barely added new references to him, usually simply extending the existing ones. Amayorov ( talk) 19:37, 7 July 2024 (UTC)
I suppose I should be grateful that you've helped illustrate quite how over-represented Benny Morris is (more than 50 citations and mentions), but again, that begs the question of why you think this clear imbalance problem should be worsened. If you can't see that there might be an imbalance problem there, that somewhat illustrates why the 500/30 rule exists and why a month of actual editing is, in spirit, what is expected of it. Iskandar323 ( talk) 19:47, 7 July 2024 (UTC)
Because Morris has written multiple, highly regarded books on the 1948 war. He's cited by plenty of other authors, such as Shlaim, Khalidi, Ben-Ami, and others.
Besides, and as I've previously explained, I didn't add much new material. I've clarified previous references and added qualifications to partisan statements. Amayorov ( talk) 19:53, 7 July 2024 (UTC)
This seems like a content dispute, Iskandar323, moreso than any actual gaming. It seems like it might be better to have discussed this with the editor on a talk page, not hauled them to AN. The editor's contributions appear to be in good faith, and while I haven't gone into a full deep-dive or anything of the sort, they don't seem to be unconstructive at first glance. Favoring a specific historian isn't necessarily a behavioral issue, so long as they are willing to discuss inclusion and abide by the results of consensus. Building a culture of continually questioning those who take the time to build a constructive editing history in order to prove they can be trusted with access to contentious topics is a terrifying idea. If I was to accuse someone of gaming for rollback, for example, because they spent a lot of time reverting vandals, it would likely be considered at the very least rude, and at worst a personal attack. EggRoll97 ( talk) 21:18, 7 July 2024 (UTC)
There is a content dispute for sure, which I will continue in good faith. At the same time, there is only one type of account that I have ever seen that goes from 0 to 100 edits a day on some random topic before switching (after 3 frenetic days) to almost pure ARBPIA edits, and it isn't the constructive variety. There are plenty of dubious accounts that have just passed this threshold currently operating in the contentious topic area. This account, however, caught my eye due to the rapid edit aggregation and glaring topic switch. I have raised the issue of quite a few gaming accounts on this noticeboard, and to date, most of them have raised eyebrows for admins too. Iskandar323 ( talk) 21:39, 7 July 2024 (UTC)

FWIW, from my perspective there appears to be some unnecessary edit farming in this user's background. For instance, Sukhoi Shkval did not require 40 edits in a row to achieve this relatively minimal difference, while not managing to add a single in-line citation or new source. On 9К512 Uragan-1M we got some extremely minor, non-substantive copyediting that frankly didn't change the readability of the article much. An improvement? Perhaps trivially, but reasonable editors could disagree there. Worth sanctioning over? IMO probably not, but I don't think Iskandar323's concerns are without merit. SWATJester Shoot Blues, Tell VileRat! 22:44, 7 July 2024 (UTC)

Regarding 9K512 Uragan-1M, the article had been marked as “roughly translated.” I did my best to correct residual grammatical errors, before marking the issue as resolved.

Regarding Sukhoi-Shkval, I agree that 40 edits were excessive. One reason for this was that I was still learning about the editing tools, discovering new templates and features. Another justification is that I had to decipher some unclear text, such as “Each wing has a rudder that functions as a rudder and aileron.” Here, the first “rudder” is in fact not a rudder at all, but a flap. I had only figured that out once I read through the sources. Amayorov ( talk) 18:03, 8 July 2024 (UTC)
It wouldn't require 40 edits from an experienced editor who knew everything about how wikitext worked, but for somebody figuring it out for the first time I am inclined to assume good faith. jp× g 🗯️ 20:36, 9 July 2024 (UTC)
There may be something going on with ARBPIA, perhaps unrelated to this, but worth thinking about. We had a recently compromised account jump into ARBPIA in the past week, threatening to report other editors if reverted, then reporting a prominent ‘opponent’ to WP:AE, volunteering to be topic banned if the ‘opponent’ is also topic banned, before being Checkuser blocked by an Arb. starship .paint ( RUN) 23:24, 7 July 2024 (UTC)

I was going to report this user as well. Account created in 2016 but first edit made a few days ago and quickly put in 500 edits, immediately jumps into Israeli-Palestinian conflict topic area, seemingly POV-pushing. Seems to be an experienced user as well. I agree with @ Starship.paint that there seems to be something going on with ARBPIA, specifically a surge in sock accounts. IOHANNVSVERVS ( talk) 05:25, 8 July 2024 (UTC)

I don't know whether these plots can provide any illumination. The dramatic change in slope and shape of the bytes added and page byte size change curves after extendedconfirmed has been granted at 500 edits is consistent with the notion of gaming to obtain the privilege in order to enter the contentious PIA topic area. These kind of signal shapes for users that enter the PIA topic area can often be seen for sockpuppets of AndresHerutJaim/יניב הורון, not that that suggests this is an AHJ sock. Wikipedia provides tools to help new users rapidly gain EC. Sometimes this kind of impressive efficiency is thanks to the Wikimedia Foundation Growth team's "Newcomer tasks" project. Also, their first edit being an WP:ARBECR violation is not great. Sean.hoyland ( talk) 09:42, 8 July 2024 (UTC)

When I was doing my edits, I was using almost exclusively Wiki’s backlog. I chose the issues that I could conceivably help with, such as Rough Translation from Russian and French (the languages I speak), and lead rewrite requests. I intend to continue on with this work in the future.
And, yes, I’m interested in the IP history, about which I’ve read a lot. Since gaining extended privileges, I’ve made improvements to those articles. Those edits have arguably been better-sources than any of my other work, due to my having more knowledge to my having more knowledge on the topic. I do not deny that I wanted to contribute to these topics from the start. Amayorov ( talk) 10:47, 8 July 2024 (UTC)
Thanks for the info Amayorov but you don't need to defend yourself to me. I'm nobody. I'm just providing information. Either way, the notion of gaming in Wikipedia and its relationship to the WP:ARBECR barrier is currently rather vague. Sean.hoyland ( talk) 11:12, 8 July 2024 (UTC)
Where did you learn to add a colon prefix to the category name in your busy schedule by the way e.g. :Category:Wikipedia backlog|Wiki’s backlog? Sean.hoyland ( talk) 05:02, 9 July 2024 (UTC)
The visual editor adds it automatically, when I link to the url /info/en/?search=Category:Wikipedia_backlog Amayorov ( talk) 13:45, 9 July 2024 (UTC)

Either way, regardless of the specifics of this editor, it's important for the community to acknowledge that a) WP:ARBECR was introduced as an entry barrier for good reasons and b) highly motivated people have already discovered ways to essentially tunnel through that barrier. Sean.hoyland ( talk) 10:17, 8 July 2024 (UTC)

Not being a tech wizard, I can only judge by what I see over time. I am in the habit of adding awareness notices if I notice new editors (non EC or EC) making edits in the topic area and off the top of my head, I would say that occurs 3 or 4 times a month at least, there appears to be an increase in the number of such editors in recent times, as to what proportion of them are WP:NOTHERE I couldn't say but experience tells me that some at least are in that category. Selfstudier ( talk) 10:57, 8 July 2024 (UTC)
I think you are underestimating your contribution. This year I think you have provided the awareness notices to 202 users, or thereabouts. That is based on your revisions to user talk pages where the byte size change is in a range consistent with the awareness template size. Sean.hoyland ( talk) 16:08, 8 July 2024 (UTC)
The top of my head is very unreliable then, lol. Selfstudier ( talk) 16:13, 8 July 2024 (UTC)
@ Sean.hoyland: There is an easier way to check; see this log search. Selfstudier has posted 210 this year. BilledMammal ( talk) 21:41, 9 July 2024 (UTC)
Ah, that's useful to know. Thanks. I've not really spent any time looking at the filters, despite them being a likely information goldmine. On the other hand, the pointlessly harder path is often more fun. Sean.hoyland ( talk) 04:08, 10 July 2024 (UTC)

No comment about the gaming accusation, but the ARBPIA edits themselves seem fine. Morris is arguably the most prominent historian in this area, and one of the more neutral ones, with critics from both sides. It's debatable whether some of the added content is important enough to include, but it's reasonable enough, and Amayorov seems open to feedback and compromise. POV pushing involves aggression, which I don't see here. If we were to expect some kind of strict symmetry in editing behavior, the vast majority of us ARBPIA editors would fail that standard. — xDanielx T/ C\ R 18:19, 8 July 2024 (UTC)

I think it's quite natural that hot topics attract new editors trying to fix (perceived) gaps or biases. I myself got to 500 edits within two months after getting involved in another contentious area. At the end of the day the question should be whether an editor understands and follows the rules. Alaexis ¿question? 21:28, 11 July 2024 (UTC)
I would say, at the start of the day the test should be - is an editor violating the rules merely by being here evading a block or ban. Unfortunately, it's not possible to tell whether an editor understands and follows the rules, all of the rules, not just a subset, by looking at the content they generate and the image they present. If an editor violates the rule against sockpuppetry by employing deception, a very common occurrence in the PIA topic area, it's reasonable to assume they will likely violate other rules while generating content or interacting with editors at some point. Sean.hoyland ( talk) 02:50, 12 July 2024 (UTC)
  • Amayorov can you explain why your account was created on July 8, 2016, but your very first edit [13] is on July 3, 2024? To me that's a red flag. A proposed remedy is that Amayorov's 30 days start from July 3, 2024. VR (Please ping on reply) 19:59, 12 July 2024 (UTC)
    I explained it here. In 2016, I created an account for a university practical that required me to create a web page about a chemical compound on Wikidata. In my case, it was a terpenoid, Q44009079‬. I don't know why the page doesn't exist anymore, but I found emails from 2018, notifying that other pages have been linked to it (see screenshots).
    A couple weeks ago, I started to be interested in trying out Wikipedia editing. I'm currently waiting to start a new job, and have plenty of time. Amayorov ( talk) 20:23, 12 July 2024 (UTC)
    Actually, I've been able to retrace this a bit more, and what I said wasn't entirely accurate. In 2017, I created a new account, @ Alexmayorov, specifically for that practical. I used it to create Q44009079. Both Amayorov and Alexmayorov are registered on the same email address. Regarding @ Amayorov, created in 2016, I can't recall why I made it.
    In April 2023, I decided to restore access to my account. I couldn't recall my username, and requested a password reset using my email. That reset came back with Amayorov as the user. Amayorov ( talk) 20:41, 12 July 2024 (UTC)
    Hello, this is my second account, which I've only just realised I had! Alexmayorov ( talk) 20:43, 12 July 2024 (UTC)
    I'm confused. It says "20:42, July 12, 2024 User account Alexmayorov talk contribs was created automatically", as opposed to 2017. VR (Please ping on reply) 23:18, 12 July 2024 (UTC)
    https://m.wikidata.org/wiki/Special:Contributions/Alexmayorov IOHANNVSVERVS ( talk) 23:25, 12 July 2024 (UTC)
    Because it was a wikidata only account. So the en.wiki one poofed into existence when they logged in here. Iskandar323 ( talk) 05:31, 13 July 2024 (UTC)
    @ Vice regent 🏓 Amayorov ( talk) 11:57, 13 July 2024 (UTC)
    Got it, thanks! VR (Please ping on reply) 18:04, 13 July 2024 (UTC)
    @ Vice regent Ping as requested Amayorov ( talk) 22:05, 12 July 2024 (UTC)

Conflict of interest VRT consultations, July 2024

The Arbitration Committee has received applications for conflict of interest VRT queue access and has reviewed them in consultation with the functionaries team. The Community is invited to evaluate the candidacies and comment here until the end of 17 July 2024 (UTC).

On behalf of the Committee, Sdrqaz ( talk) 00:01, 8 July 2024 (UTC)

Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard § Conflict of interest VRT consultations, July 2024

Multiple reverts

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


A user has reverted my edits two times each in First Dutch Military Aggression and Second Dutch Military Aggression. Can someone please prevent him from reverting it. I'm trying to avoid violating WP:3RR. Desertasad ( talk) 01:25, 8 July 2024 (UTC)

I've blocked the OP for 72 hours for their homophobic comments they posted at NFSreloaded's Talk page, whom they failed to notify of this complaint. Any administrator is free to block Desertasad for longer.-- Bbb23 ( talk) 01:42, 8 July 2024 (UTC)
I can tell you that if I were an admin, I'd indef. Saying that the legalisation of LGBTQIA+ is a bad thing is extremely disruptive. I've seen users indeffed for less. LilianaUwU ( talk / contributions) 01:47, 8 July 2024 (UTC)
I agree and have made it an indef. –  Joe ( talk) 10:29, 9 July 2024 (UTC)

Appreciate the tag. In response to this complaint: the manual reverts in question are here and there on Operation Product, and here and there on Operation Kraai. On the former article OP duplicated information already present in the lead section, on the latter article they moved the informal non-English terms for the military operation up to the first sentence. I considered both contributions redundant and undid them, ultimately resulting in the exchange on my talk page. That said, I don't feel I was pushing any kind of nationalist narrative in this situation or elsewhere. -- NFSreloaded ( talk) 02:24, 8 July 2024 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

https://zh.wikipedia.org/zh-hant/蔡瑞月

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Hi Administrators,

Someone upload a wrong portrait of Madam Tsai Jui-yueh on the Traditional Chinese Wikipedia page. https://zh.wikipedia.org/zh-hant/蔡瑞月

Someone uploaded using the reference below, Madam was tagged in that News article photo album, but photo is someone else in a group photo https://ahonline.drnh.gov.tw/index.php?act=Display/image/4359360wg9foOB#d6C


The same news article and album you can see Madam Tsai Jui-yueh is in this photo https://ahonline.drnh.gov.tw/index.php?act=Display/image/4359360wg9foOB#0Osa

Can someone please check the reference and correct this page.

該封禁的查封ID是#560409。--Tjyfoundation(留言) 2024年7月8日 (一) 11:27 (UTC) Tjyfoundation ( talk) 12:05, 8 July 2024 (UTC)

zh.wikipedia.org is a different project. There's nothing that en.wikipedia.org can do for you, you need to raise your concern on that project. -- Yamla ( talk) 12:07, 8 July 2024 (UTC)
How to raise my concern on that project? Tjyfoundation ( talk) 12:24, 8 July 2024 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


RfC closure review request at Wikipedia:Reliable sources/Noticeboard#RFC: The Telegraph on trans issues

WP:RSN ( talk| | history| logs| links| cache| watch) ( RfC closure in question) ( Discussion with closer)
Page now archived at /info/en/?search=Wikipedia:Reliable_sources/Noticeboard/Archive_444#RFC%3A_The_Telegraph_on_trans_issues

Closer: S Marshall ( talk · contribs · deleted contribs · logs · filter log · block user · block log)

Notified: User talk:S Marshall#Closure review

Background: There are two separate objections. One to the close as a whole, and the other to the third paragraph. We present both here, and ask editors to say whether they support overturning the whole close, only the third paragraph, or none.

Reasoning - Third paragraph: Overall, I am satisfied with this closure. However, the closer claims that the Telgraph has an unashamed embrace of the widely-debunked Litter boxes in schools hoax, which is really misleading. That part of the debate centered over the Telegraph's unretracted claim that a student identified as a cat at a certain school (evinced by a viral argument in which a student brings up the "cat student" part as a rhetorical device), which is to be way less than what "embracing the litter boxes in schools hoax" implies; the Telegraph didn't even give that fact much weight anyways.
Now, someone has quoted this part of the closing summary on the Telegraph's WP:RSP entry, thus enabling this misleading part to inflict a lot more damage on those wishing to use RSP for a quick summary of existing consensus. If nothing else, I'd like at least this part to be amended.

As seen on the closer's talk page, at least 3 others are a lot more unsatisfied, believing that the closer falsely made claims of other misrepresentations being brought up and evinced. See BilledMammal's comment for details of this argument. Meanwhile, commenters here may want to consider the magnitude of !voters for deprecation who weren't convinced by the lack of factual misrepresentation. In the end, however, I personally am only concerned with removing or amending the misleading language I mention in the first paragraph. Aaron Liu ( talk) 04:19, 9 July 2024 (UTC)

Note that by "first paragraph", I meant the problematic language that I bring up in the first paragraph of my statement, not the first paragraph of the actual close. Aaron Liu ( talk) 12:43, 9 July 2024 (UTC)

Reasoning - Close as a whole: There are two issues with this closure; the closer has substantially misread the discussion, and the closer is WP:INVOLVED.

The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax is discussed at great length. The disputed article, here, is exhaustively dissected by the community, and, on the basis of scholarly sources and an Ofsted report, various misrepresentations contained in that article are noted. It's questioned whether these are really "misrepresentations" or confusions between fact and opinion. Towards the end of this, the "generally reliable" camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes, which I receive as a concession that the article is misleading. And if the Telegraph has published a correction, then the "generally reliable" camp hasn't unearthed it.

This quoted paragraph, which is the only part of the close which focuses on the arguments made, is rife with inaccuracies. They say that various misrepresentations contained in that article are noted, but as far as I can tell only two misrepresentations were alleged; that the Telegraph endorsed the litter boxes in schools hoax, and that the Telegraph falsely claimed that a student identified as a cat.

The closer says that these allegations are proven on the basis of scholarly sources and an Ofsted report, but this in incorrect. As far as I can tell no scholarly papers were presented in relation to these allegations, and while the Ofsted report was presented, it was presented by those arguing "generally reliable", who pointed out that it took no position on whether a student actually identified as a cat.

They also interpret the consensus of the discussion on this as that the Telegraph has unashamed[ly] embrace[d] the widely-debunked Litter boxes in schools hoax. This is not a reasonable reading of discussion; editors rejected that claim on the basis that the Telegraph explicitly called claims of litter boxes in schools a hoax, and this counter-argument was endorsed by the majority of editors who commented on the claim.

Finally, they say towards the end of this, the "generally reliable" camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes. While a few editors on both the "generally reliable" and "generally unreliable" side said that reliable sources are allowed to make occasional mistakes, it doesn't appear that this statement was especially common among the "generally reliable" camp, and to interpret this statement as meaning that those editors are recognizing that this specific example is a mistake is to read something into these !votes that is not there.

Given the number of factual errors made in the closer's summary of the discussion it is clear that it needs to be overturned and reclosed. This is particularly true because the closer is WP:INVOLVED, having argued in a previous discussion at RSN about the Telegraph in relation to politics that, while they considered it reliable for that sub-topic, it employs people with ghastly and abhorrent opinions. BilledMammal ( talk) 05:55, 9 July 2024 (UTC)

Closer

This is a no-consensus close, and there are two possible approaches to no-consensus. The first is the one usual at WP:AFD, where no consensus means no change. AFD puts the burden to achieve consensus on the pro-change side. User:Seraphimblade, below, clearly sees the discussion as being in this category.

The second is the one usual with content decisions, at WP:ONUS. ONUS puts the burden to achieve consensus on the anti-change side, and authorizes the removal of disputed material.

In closing this, I decided that the community doesn't have widespread confidence in the Daily Telegraph's coverage of trans issues, and therefore it shouldn't be listed as generally reliable. In other words, I decided to treat this as more like a content decision governed by WP:ONUS than a procedural one governed by AFD consensus. In doing this, I removed the first mover advantage that the "generally reliable" side expected and I think relied on. At issue here is the question: was I right to do that? If you think I was, you belong in the "endorse" column, and if you think I wasn't, then you belong at "overturn".

It's very arguable, and I won't object if the community overturns me here on that point. But I do think I'm right. My position is that we shouldn't be listing sources as generally reliable when the community has real doubts.

The claim that I was INVOLVED is much less arguable. INVOLVED means you can't close a discussion you've voted in, and it means you can't close a discussion about an article you've made non-trivial edits to. And that's all it says. If you stretch INVOLVED to allow claims that you're INVOLVED because you participated in a tangentially-related RFC on RSN the thick end of a year ago on the other side of the debate from your closure, then you've pulled it a long way out of its original shape, haven't you?

We as a community need to clarify what's INVOLVED and what isn't, because I've noticed that pretty much every time you make a disputed closure someone mentions it.— S Marshall  T/ C 07:25, 9 July 2024 (UTC)

I think you misread INVOLVED. It’s not about single discussions, but disputes as a whole - and you’ve been involved in disputes in relation to the reliability of The Telegraph, and given the part of your comment I quoted you clearly also have strong feelings on the subject. BilledMammal ( talk) 07:35, 9 July 2024 (UTC)
No, I don't have strong feelings about the Daily Telegraph. It employs people with ghastly and abhorrent opinions, and I certainly do have my views and opinions about some of those people, but that's not what's at issue here and the Daily Telegraph as a whole isn't a subject I care about.— S Marshall  T/ C 07:41, 9 July 2024 (UTC)
That's not what ONUS says - it doesn't put the burden on "the anti-change side". It puts the burden on "those seeking to include disputed content". "Seeking to include" means the ones adding it. It doesn't say "seeking to include or retain". DeCausa ( talk) 13:23, 9 July 2024 (UTC)
The policy issue is where I said this: My position is that we shouldn't be listing sources as generally reliable when the community has real doubts.S Marshall  T/ C 13:46, 9 July 2024 (UTC)
I don't have a view on that. I was just pointing out you've misread ONUS. DeCausa ( talk) 15:51, 9 July 2024 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


S Marshall, I had not seen the indications of your involvement in this close, but you have even shown those here. WP:BADNAC states as the first reversal reason for a bad non-admin closure: The non-admin has demonstrated a potential conflict of interest, or lack of impartiality, by having expressed an opinion in the discussion or being otherwise involved, with the exception of closing their own withdrawn nomination as a speedy keep[a] when all other viewpoints expressed were for keeping as well. You have indicated an opinion even here, and did so beforehand as well. So I will give you the option of reversing your closure, or I will, but it's going to be reversed. A discussion like this should be closed by an impartial closer, or perhaps a panel of them, but you have shown yourself not to be that. If you do not reverse your closure, I will do so. Seraphimblade Talk to me 09:41, 9 July 2024 (UTC)
That would be an unwise and deeply controversial thing to do. I am not involved in this matter. At issue is whether the Daily Telegraph is reliable for statements about trans issues. I have never expressed a view on that. Historically I did express a view on the Daily Telegraph's reliability on politics. I said it was reliable for that, and it remains my view that the Daily Telegraph is reliable for politics. This doesn't make me involved in its reliability on other things and you do not get to unilaterally reverse a RFC close on your own judgment. That is not one of the powers the community has granted sysops.— S Marshall  T/ C 09:50, 9 July 2024 (UTC)
Either reverse or don't, coercing the closure to do so with an ultimatum is not ok. CNC ( talk) 10:20, 9 July 2024 (UTC)
That is, in fact, one of the powers the community has granted sysops. WP:NAC specifically states that NACs are not appropriate in either of the following two situations: The non-admin has demonstrated a potential conflict of interest, or lack of impartiality, by having expressed an opinion in the discussion or being otherwise involved, with the exception of closing their own withdrawn nomination as a speedy keep[a] when all other viewpoints expressed were for keeping as well., and The outcome is a close call (especially where there are several valid outcomes) or likely to be controversial. This closure at least arguably fails the two, but it dead clearly fails the second. It further states: Per Wikipedia:Deletion process § Non-administrators closing discussions,[b] inappropriate early closures of deletion debates may either be reopened by an uninvolved administrator. So, I intend to reopen it. For clarity, I don't intend to close it; I will leave that to others. I don't have a preferred outcome here, but this close was not appropriate. Seraphimblade Talk to me 10:53, 9 July 2024 (UTC)
You won't do that without pushback. This wasn't a deletion decision so you don't get to rely on rules about deletion decisions, and I'm rather self-evidently not involved. Politics is not gender.— S Marshall  T/ C 10:56, 9 July 2024 (UTC)
I don't imagine I'll do it without pushback or without having people shouting at me. I've got a pretty thick skin by now. But I still think it needs to be done. Seraphimblade Talk to me 11:01, 9 July 2024 (UTC)
I've reopened the discussion. As above, I do not intend to close it or in any way be involved with deciding on the outcome, but that outcome does need to be decided properly. Seraphimblade Talk to me 11:09, 9 July 2024 (UTC)
Overturning the close might be premature. Is it normal to short circuit an AN RFC review in such a manner? Doesn't seem very efficient to have a big discussion here if the outcome is already ordained. – Novem Linguae ( talk) 11:20, 9 July 2024 (UTC)
( edit conflict)Do you also believe, per WP:NAC, that all of S Marshall's RfC closes on controversial topics should be reverted? Do you really want to set the precedent that all controversial closes must be handled by administrators? Do you think we have that capacity? I think this is a spectacularly bad exercise of judgement. ~~ AirshipJungleman29 ( talk) 11:23, 9 July 2024 (UTC)
So you've overturned and relisted as an involved admin in this request, because you deem the closure was involved? I can't be the only one who sees the irony in this. CNC ( talk) 11:25, 9 July 2024 (UTC)
I saw a supervote/BADNAC here, and overturned it. I think that's what should be done. I wasn't involved in the discussion; I was upset by it because of how clearly unacceptable it was. That close didn't summarize the opinions in the discussions, it expressed the opinions of the closer. If that's not a bad close, I don't know what is. Seraphimblade Talk to me 11:30, 9 July 2024 (UTC)
And why do you think your 'upset' trumps the opinions of other editors who have expressed support for this close, or indeed those that agree that it should be overturned, but have decided to express that through discussion? This was very poor judgement. –  Joe ( talk) 11:33, 9 July 2024 (UTC)
BADNAC or not, your decision makes a mockery of this RfC review process. You expressed your opinion below to overturn and are clearly involved in the dispute here, then went ahead and supervoted the outcome. Being upset is no excuse for this, it's shocking. CNC ( talk) 11:39, 9 July 2024 (UTC)
@ Seraphimblade: Please restore the close and follow process here. voorts ( talk/ contributions) 12:11, 9 July 2024 (UTC)
Jesus Christ, what arrogance. Okay someone close this close review, although the AN certainly hasn't seen the last of this.— S Marshall  T/ C 11:35, 9 July 2024 (UTC)
I'm stunned, Seraphimblade. Not only did you choose to ignore all the editors telling you that this was a bad idea and do it anyway, but you're now edit warring over it. Do you think this is how contentious decisions should be carried out? –  Joe ( talk) 11:44, 9 July 2024 (UTC)
The close review shouldn't be closed. Seraphimblade should either do the right thing or a new discussion should he started here about the unilaterak overturn. voorts ( talk/ contributions) 12:14, 9 July 2024 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Non-participants

  • Overturn. Firstly, the close strikes me as making an argument rather than summarizing them, which raises at least substantial concerns of a supervote. But, that aside, the close seems to be a "no consensus", which means no change to the status quo, yet it then calls for a change in the status quo. Given these concerns and the incoherent nature in general, I think the discussion needs to be reclosed in terms of first, determining if there is any consensus whatsoever (if "no", no changes are made), and, if so, what it is and why. While I have not exhaustively reviewed the discussion, I did take a look over it, and I don't think a clear consensus could be discerned from it, so I think a "no consensus, therefore no change" closure would be the most appropriate result. But certainly "No consensus, but make a change anyway" is an incoherent one, so that can't stand. Seraphimblade Talk to me 06:03, 9 July 2024 (UTC)
  • Comment. Responding to I decided to treat this as more like a content decision governed by WP:ONUS than a procedural one governed by AFD consensus. In doing this, I removed the first mover advantage that the "generally reliable" side expected and I think relied on. At issue here is the question: was I right to do that? It is my opinion that "no consensus" often means "no change", even outside of AFD. But RSP is a clear exception to this, as stated in WP:MREL. No consensus, unclear, or additional considerations apply. The words "no consensus" are literally in the title/definition of what is frequently "option 2" in RSN RFCs. Unfortunately, my opinion on this does not add clarity here, but instead suggests that an RFC like this one, which had a lot of option 1 and option 3 !votes, could reasonably be closed as "no consensus" and become a consensus for option 2. Because of the murkiness of all of this, I leave this as a comment rather than a bolded endorse/overturn, and I simply leave this as food for thought. – Novem Linguae ( talk) 08:57, 9 July 2024 (UTC)
    Agree. RSP is simply a place where summaries of discussions are documented, not much else. We can't omit NC discussions because there was previously consensus for X, Y and Z. Whether previous consensus should remain, or be prioritised over a NC discussion, is another topic that effects more RSP entries than just The Telegraph. CNC ( talk) 09:47, 9 July 2024 (UTC)
    As to where the boundary of WP:INVOLVED is, it is my opinion that one is involved if reasonable editors perceive the closer as having an obvious bias. Even if the closer is not actually biased, the perception of such is important, imo. Is S Marshall involved here? I don't know. It will depend on if more than a couple editors feel that he has an obvious bias. A couple clearly think he does, but I think more input is needed before deciding that. – Novem Linguae ( talk) 11:28, 9 July 2024 (UTC)
    While your obviously entitled to your opinion, INVOLVED is not based on having a perceived bias. You have to prove that bias makes the closure impartial based on disputes or conflicts with other editors within that topic area. CNC ( talk) 11:42, 9 July 2024 (UTC)
  • Endorse close, but can understand re-listing in order to be re-closed by a group of editors to satisfy all these "extra" issues, specifically regarding the closing summary. From a look at the discussion, I don't think any other close could have reasonably ascertained that there was consensus for GR or GU while remaining impartial, and thus no consensus was the correct assessment by default. I found the closing rationale very reasonable, even if I do understand concerns regarding some of the wording. In my opinion the weight given to the dispute of reliability in the closing summary otherwise makes sense. If the RfC failed to gain consensus, it makes sense to use more words explaining why there wasn't consensus from those who disputed reliability, as opposed to elaborating on why editors believed it was reliable, similar to the closure summaries of other contentious RfCs. Concerns over the closure's involvement otherwise need to be supported with diffs, specifically of the closure's involvement in disputes regarding The Telegraph or trans issues, otherwise this "fall back" argument is meaningless. CNC ( talk) 10:06, 9 July 2024 (UTC)
    @ CommunityNotesContributor: I think you overlooked this diff I provided - sorry, I should have made its presence clearer rather than including it as a WP:EASTEREGG. BilledMammal ( talk) 10:10, 9 July 2024 (UTC)
    So no dispute then? Having an opinion is not being involved. Anything else? CNC ( talk) 10:13, 9 July 2024 (UTC)
    The dispute was regarding the reliability of the Telegraph. Having an opinion made them a party to that dispute. Editors who are parties to a dispute are forbidden from closing discussions broadly related to that dispute, and whether the Telegraph is reliable for politics is a dispute very closely related to whether it is reliable for trans issues. BilledMammal ( talk) 10:20, 9 July 2024 (UTC)
    "Having an opinion made them a party to that dispute." That's a huge stretch. CNC ( talk) 10:24, 9 July 2024 (UTC)
    To clarify; they expressed their opinion while participating in the dispute. That makes them a party to the dispute. BilledMammal ( talk) 10:27, 9 July 2024 (UTC)
    The discussion was "What do we think of the reliability of this story", the editor provided an opinion on that. They didn't engage in any dispute with other editors, ie argue with other editors, it was an isolated comment. To clarify, this discussion is a dispute, because we are arguing. See the difference? CNC ( talk) 10:33, 9 July 2024 (UTC)
    The discussion was Reliability of the Daily Telegraph for politics?, and the notion that it is only a dispute if there is arguing is... novel. Interpreting it that way would mean that editors would even be able to close RfC's they participate in, so long as they don't engage in any back-and-forth discussion.
    This discussion is getting a little deep, so I'll step out now. BilledMammal ( talk) 10:40, 9 July 2024 (UTC)
    WP:INVOLVED does have novel wording: " Involvement is construed broadly by the community to include current or past conflicts with an editor (or editors), and disputes on topics,...". This is not a " conflict" with other editors, nor based on trans topics. The wording at WP:CLOSE arguably has a higher bar for contesting: "if the closing editor may have become inextricably involved through previous experience in the conflict area", so a throwaway opinion isn't going to cut it here. CNC ( talk) 11:19, 9 July 2024 (UTC)
  • Endorse. I found the close very reasoned. I can understand that some may take issue with the description "unashamed embrace", however the crux of the issue is that the paper published a hoax in the area of gender identity and when it was demonstrated that it was hoax they didn't publish a correction. To me that seems perfectly relevant to the question of whether The Telegraph is reliable on trans issues regardless of the specific wording. TarnishedPath talk 11:35, 9 July 2024 (UTC)
    What hoax are you referring to with the paper published a hoax? BilledMammal ( talk) 11:38, 9 July 2024 (UTC)
    The kitty litter hoax, the claim that accommodations were being made to children who identified as animals. Is there something else that the close referred to as an "unashamed embrace" of? TarnishedPath talk 03:36, 10 July 2024 (UTC)
    The paper did not make that claim, it reported on others making that claim, cited to them. It did not report that as fact. We don't expect reliable sources to avoid reporting on others spouting falsehoods - otherwise every US news source that has reported on all of Trump's falsehoods would have to be unreliable, since they reported them! -bɜ:ʳkənhɪmez ( User/ say hi!) 04:12, 10 July 2024 (UTC)
    (however many do expect newspapers to issue updates when falsehoods come to light, but we're going off-topic here. point is, that part of the close unduly exaggerates the consensus on the nature of the issue discussed.) Aaron Liu ( talk) 04:16, 10 July 2024 (UTC)
    There was a recent discussion about Al Jazeera that many of the editors commenting here had to have seen (and quite a few participated in) where the conclusion I observed is that is not expected for "news" that was accurate at the time and cited/attributed to another source that later updates itself - so long as their future news stories are in compliance with the updated information. I agree with you that it unduly exaggerates the amount of consensus for "unreliable" to make it a "no consensus". -bɜ:ʳkənhɪmez ( User/ say hi!) 05:34, 10 July 2024 (UTC)
    That the newspaper published a hoax is not a summary of the discussion. It is one contention that was strongly disputed within the discussion. The term "unashamed embrace" shouldn't be an issue for some, it should be an issue for all, as it wasn't even argued during the discussion. Editors who claimed the Telegraph was knowingly printing false material also often argued that they snuck it in through quotes by dubious actors rather than putting it in their own voice. Samuelshraga ( talk) 14:35, 9 July 2024 (UTC)
  • Overturn. Closer says that WP:ONUS applies to editors who object to adding a rule so "those who want the status quo need to achieve positive consensus for it", it will be good if admins comment that's not how it works. It's fine to agree with the minority that the cat affair justifies action but that's a vote not an evaluation of consensus. However, adding twaddle to the essay-class WP:RSP page needn't concern admins. Peter Gulutzan ( talk) 13:59, 9 July 2024 (UTC)
  • Overturn. Given that the closer assessed this as "no consensus", the correct and only outcome is to retain the status quo, which is that the Telegraph is "generally reliable". The spiel above about WP:ONUS mandating some other outcome is not supported by WP guidelines and effectively takes the close into WP:SUPERVOTE territory. This should be reclosed properly, with no consensus meaning no change to the status. That's not to say we would always have to follow the Telegraph on trans issues, of course, ONUS does apply at individual article level across the project, and where claims in the Telegraph represent WP:FRINGE viewpoints when compared with other sources, it's correct to ignore them. That's a far cry from there being a consensus to label it as "reliability disputed" though.  —  Amakuru ( talk) 14:52, 9 July 2024 (UTC)
    Note that "no consensus" for a source evaluation brings it into WP:MREL, its own status for "no consensus". Aaron Liu ( talk) 15:41, 9 July 2024 (UTC)
    That would apply if the matter had never been discussed before, with no status quo, and this were to establish a new position. But that's not the case. There was an RFC in 2022 which concluded that the Telegraph is generally reliable. This RFC here sought to amend that prior consensus and add a new caveat for trans issues specifically. Altering previous consensus requires consensus, not a lack thereof. Lack of consensus means retain status quo.  —  Amakuru ( talk) 16:10, 9 July 2024 (UTC)
    Lack of consensus that a source is generally reliable means that it isn't generally reliable. Thryduulf ( talk) 16:13, 9 July 2024 (UTC)
    It means nothing of the sort. It means nobody could agree if it is or not. You don't get to "win" the argument by default just because some people agreed with you and some people didn't. This principle would also apply if it had previously been declared unreliable. The status quo remains.  —  Amakuru ( talk) 16:15, 9 July 2024 (UTC)
    If nobody can agree if it is or is not reliable, then it can't, by definition, be generally reliable. WP:RSP#Legend defines "Generally reliable" as Editors show consensus that the source is reliable in most cases Thryduulf ( talk) 16:18, 9 July 2024 (UTC)
    The status quo of RSP is categorising discussions based on consensus or lack of. CNC ( talk) 16:19, 9 July 2024 (UTC)
    It's been referenced before but RSP is a summary of discussions. If there is no consensus over the reliability of a source, or over a particular topic from a source, then it will be documented as such. The reliability of The Telegraph was otherwise previously discussed prior to the RfC. What your implying has broader implications on RSP categorisation. CNC ( talk) 16:17, 9 July 2024 (UTC)
  • Overturn. Potential involvement aside, the bit about WP:ONUS on the closer's talk page takes this into supervote territory. I will leave it to the new closer or closers to decide the outcome. ~~ Jessintime ( talk) 15:28, 9 July 2024 (UTC)
  • Endorse. This was a good close. Firstly I don't see how a single past opinion about a separate topic that The Daily Telegraph covers would then indicate the closer is therefore WP:INVOLVED in this topical circumstance (i.e., this single opinion doesn't make the closer " inextricably involved... in the conflict area"). This is especially true in this case, where the closer's broader comment was essentially about the apparent ability of the newspaper to still remain factual despite the individual biases of of a subset of employees. Secondly, about the close itself, the legend for Perennial Sources list entries labeled "No consensus, unclear, or additional considerations apply" (i.e. Option 2 of RSN RfCs) provides the relevant detail for evaluation here: "Editors may not have been able to agree on whether the source is appropriate, or may have agreed that it is only reliable in certain circumstances." The discussion in this RfC clearly fits the description of "may not have been able to agree on whether the source is appropriate". If discussions are split between Options 1 and 3 (or 4) and no consensus emerges, as was the case here, the discussion then pretty clearly renders into Option 2 territory when it's time to close. It's clear to me the Option 2 of active RfC discussions is for considering the "unclear" and "additional considerations apply" aspects of the label during such discussions, but needn't be explicitly invoked at a level that cements 'consensus for a lack of consensus', so to speak, for it to be the correct outcome. This case shakes out as no consensus about the reliability of The Daily Telegraph for the subject of trans issues, exactly as the closer found it. -- Pinchme123 ( talk) 20:56, 9 July 2024 (UTC)
  • Endorse as far as I am concerned, closes deserve some minor presumption of regularity, and there should be a showing of some meaningful issue or bias before we go about overturning one. I see nothing of the sort here, and the close strikes me as well within the range of possibilities that a reasonable closer might choose. Cheers, all. Dumuzid ( talk) 21:18, 9 July 2024 (UTC)
  • Overturn. The closer's summary is rife with misleading claims and analysis, along with real concerns of a supervote, as many others have pointed out at length. I'd like to put specific emphasis on what the closer should have, but did not mention in the summary:
    • 1. The sheer amount of sensationalist claims the original poster had listed that went on to be directly and irrefutibly shown to be either false or misleading. See discussion there at length
    • 2. Directly following that, a re-evaluation of the merits of the one remaining possible 'single mistake' (the child's identity as a cat) to even possibly warrant this RfD to result in a characterization of 'reliability disputed'
    • 3. An accurate presentation of the terms of that misrepresented 'one mistake', which was revealed in discussion to be a mistaken assumption based on information the paper was provided with
    • 4. The major amount of support in the 'unreliable' camp that were either based on non-arguments or used language suggesting they had taken all of the original poster's assertions at face value. A sampling: "it was extensively proven that the Telegraph propagates blatant lies"; another user says "we should never use a newspaper for almost anything"; yet another states "the Telegraph is not a source of expert opinion on this topic... there's no reason Wikipedia needs to publish anything they say about it". There are many more !votes that are non-starters when you read the reasoning.
The closer did not recognize the importance of depreciating the value of any editors' votes that were not based on any evidence discussed in the RfC, besides the other issues raised above and by other editors. I hope the next close will be fairer. JoeJShmo 💌 06:26, 10 July 2024 (UTC)
  • Overturn While I think I agree with the closer, the way it was phrased makes it fairly clear this was a supervote at best. Lulfas ( talk) 17:57, 10 July 2024 (UTC)
  • Overturn First, I don't find the WP:INVOLVED argument compelling. Commenting on a previous RFC about the Telegraph's reliability as a whole is approaching the line, but I think it is firmly on the "acceptable" side of it. Reading the close itself, I see substantial defects on the merits to the point that it looks like a WP:SUPERVOTE. The close seems to take assertions made by the 3/4 camp at face value (especially the litter box thing, which was a clear point of disagreement as to what facts they were stating), while minimizing or totally glossing over arguments made by the 1 !voters, especially the comprehensive refutations of the RFC basis by Chess. The weighting applied to these arguments is also strange. Editors on both sides made some poor arguments, but a lot of the 3 and most of the 4 !voters made arguments that were weak or totally irrelevant. Those addressing the opinion pieces or "platforming" certain views mean nothing for reliability, since those are already unusable for statements of fact. Some accepted the litter box claims at face value, totally ignoring the refutations to them much like the close itself did. Other !votes were bare statements of opinion, such as I'd barely trust the Telegraph with the weather, let alone any politics, and least of all any kind of gender politics. When these non-arguments are down-weighted or discarded, I believe the consensus becomes very clear. I would have closed it as WP:GREL, but with an additional note that while factually reliable, there was consensus that their coverage of trans issues is biased and special attention should be given to WP:DUE. The Wordsmith Talk to me 18:29, 10 July 2024 (UTC)
    But that clearly would have been a WP:SUPERVOTE, since there obviously wasn't a consensus in the discussion. The idea that a "refutation" must be accepted by everyone else who !votes subsequent to it is obviously silly. The "refutation" just wasn't convincing to many editors. Loki ( talk) 18:38, 10 July 2024 (UTC)
    It was not convincing or not - many editors chose to ignore it completely, rather than explain why they were not convinced. As I stated elsewhere, if an editor wishes to express their view that a refutation is not convincing, that is fine and could be given weight as appropriate, as the person you replied to did. But if all they do is ignore it, their vote must be seen in light of the fact they are ignoring the discussion on it, and only commenting with their opinion. -bɜ:ʳkənhɪmez ( User/ say hi!) 19:02, 10 July 2024 (UTC)
    In which case we must also regard every comment that does not explicitly mention every piece of evidence or (claimed) refutations of that evidence as ignoring that evidence and/or refutation. i.e. the same standards must be applied to everyone. Thryduulf ( talk) 19:06, 10 July 2024 (UTC)
    I don't think it is especially controversial to say that a !vote that considers the counter arguments and rejects them is stronger than one that simply repeats the claims with nothing showing they've done any actual analysis of it. I didn't say those should be totally ignored, just weighted accordingly. The Wordsmith Talk to me 19:11, 10 July 2024 (UTC)
    I think it's more controversial than you think it is. Imagine the following two !votes:
    • Support I think we should only include a mention of Darwin's Origin of Species, because of the many reliable sources that support it, and the zero that support the "aliens did it" hypothesis advanced by the OP. - Alice
    • Oppose Alice claims that no reliable sources support the "aliens did it" hypothesis, but what about "Aliens Did It" by Quacky McQuackerson? - Bob
    Which of these !votes is stronger? Which should be weighted more highly? Loki ( talk) 19:56, 10 July 2024 (UTC)
    Considering that in this hypothetical you're "Bob" (Alice claims that the Telegraph doesn't endorse the Litter boxes in schools hoax, but what about this article where they call it a hoax?), that isn't exactly a counter-argument. BilledMammal ( talk) 20:00, 10 July 2024 (UTC)
    You are indeed Bob in this case. You are saying that the source says something that everyone with eyes can read for themselves is not what the source is saying. You’ve claimed that the source “states that the litter boxes in schools happened” - but that was clearly refuted as they merely reported on the hoax that was stated by others, with attribution. Ditto for the other things you’ve claimed. To be quite blunt, when an editor is as misleading as your initial claims in the RfC are, and they are so clearly refuted that there is virtually nobody arguing after the fact that isn’t equally misrepresenting the sources, all of the !votes based on the misrepresentation need to be weighted heavily down, or given no weight if they provide zero other justification than the misinformation.
    In other words, we should not be in the habit of rewarding people who promote quackery (such as Bob), or who promote misinformation/misleading reading of a source to try and “win” the argument (like you did). -bɜ:ʳkənhɪmez ( User/ say hi!) 20:09, 10 July 2024 (UTC)
    You say "everyone with eyes" agrees with you, ignoring the many people with eyes who disagree with you. Loki ( talk) 20:15, 10 July 2024 (UTC)
    ...which is what many option 3 !voters did. The difference between these sides which both didn't mention refutations is that more option 3 !voters often did not provide refutations. Aaron Liu ( talk) 20:16, 10 July 2024 (UTC)
    And what I'm saying here is that a weak refutation should not be more heavily weighted than no refutation. If anything it should be weighted less, because it reveals a fundamentally weak argument. Loki ( talk) 20:20, 10 July 2024 (UTC)
    That’s absolutely absurd. Someone who is expressing their opinion with reasoning/rationale will always be weighted higher than someone who drives by and “throws a !vote at the house”. You claim it’s weak, then care to explain why a majority of “non drive by” editors after the refutation agreed with it? And of those who didn’t, very few bothered to actually explain what they found wrong with it? Those two things are, in fact, the sign of a strong refutation. -bɜ:ʳkənhɪmez ( User/ say hi!) 20:25, 10 July 2024 (UTC)
    I disagree wholeheartedly. This contention seems entirely misconceived to me, and also somewhat oppressive. Giving full reasons can't be mandatory. If I'm at AfD, I shouldn't have to type out, "I concur with the nominator. I too have carried out an exhausive search for sources and I too have not been able to locate an acceptable one. Like the nominator, I don't agree that this person's blog is a useful source for their biography." I should be allowed to type "Delete per nom" in the happy expectation that my contribution will get full weight. People must not be made to feel they have to type out arguments that have already been well made, in full, before their view is counted.— S Marshall  T/ C 22:23, 10 July 2024 (UTC)
    It depends on the context. If at the AfD the nom says "Fails GNG", and an editor subsequently posts a list of sources, saying "per nom" is a very weak argument - you need to address the rebuttal.
    It's similar here. If you say "Per Loki", you need to address the rebuttal that argued Loki not only failed to provide sources for the claim that the Telegraph endorsed the Litter boxes in schools hoax, but that one of the sources they did provide explicitly called it a hoax. BilledMammal ( talk) 22:27, 10 July 2024 (UTC)
    It's long been understood that WP:PERX is a weak argument. While WP:ATA is an essay, it has broad community support. As mentioned on that page, Where reasonable counter-arguments to the nomination have been raised in the discussion, you may wish to explain how you justify your support in your own words and, where possible, marshalling your own evidence. At least giving some evidence that you've read the opposing arguments and disagree with them shows that you've done some kind of analysis. If we don't weigh arguments according to how comprehensive, informed, and well-grounded they are then all we have left is a headcount. To also quote from WP:CRFC, The degree to which arguments have been rebutted by other editors may be relevant, as long as the rebuttals themselves carry sufficient weight. If one group is responding directly to the other’s arguments but the other isn’t, that may be relevant to determining which group has better reasoning. The Wordsmith Talk to me 23:38, 10 July 2024 (UTC)
    When the arguments they are citing have been solidly refuted with significant agreement with that refutation, then yes, the editor should be expected to justify their agreement or have their argument down weighted accordingly. -bɜ:ʳkənhɪmez ( User/ say hi!) 23:50, 10 July 2024 (UTC)
    Considering almost all of nom's original arguments were at best misrepresentations, votes along the lines of "delete per nom" should've been- and should be- majority depreciated. The litter box hoax was a non starter, and nom was reduced to "claims along the lines of a litter box hoax". Further claims were shown to be non-starters as well. Any vote relying on nom's presentation of the issues stated quite possibly could've been completely disqualified, and at the least depreciated. JoeJShmo 💌 01:21, 11 July 2024 (UTC)
    @ S Marshall, is your reading of the discussion that Loki's opening stood more or less unrebutted? Nominator brought 14 links to the Telegraph in their nomination. 9 were described by nominator as directly saying false things. All 9 by my count conclusively refuted farther in the discussion as nothing more than biased presentation at most.
    The 5 others were to do with the cat-gate at Rye College. Nominator brought two articles from the Guardian and Pink News to show Telegraph coverage was proven false. In fact, while the Pink News at least states that the Telegraph's reporting is false, it certainly doesn't prove it. The Guardian simply carries the school's denial that a student identifies as a cat.
    And then the rub. No one has actually proven that a student did or didn't identify as a cat. But editors continue to dispute whether demonstrating factual inaccuracy is an important part of a finding of unreliability, so there's that.
    Nominator also brought up some academic sources which I haven't had time to look into as deeply but which were strongly contested in discussion (and which you didn't mention in your close anyway).
    So out of 14 Telegraph articles, and 2 articles in the Guardian and Pink News, nominator managed to directly misrepresent the content of 11, and there is, at the very least, a significant case that nominator directly misrepresented the content of the other 5. This was spelled out clearly early in the discussion. But you think "Per Loki" and "Per Chess" should be given equal weight, because Loki actually made the misrepresentations, while Chess only pointed them out? Samuelshraga ( talk) 06:02, 11 July 2024 (UTC)
Loki's nomination statement was exhaustively analyzed by the community in that RFC. It enjoyed significant support and received significant opposition, and overall there was no consensus about its accuracy. The question at issue in that RFC was: Where does bias become unreliability? The community doesn't agree on the answer, but there certainly is not a consensus that the Telegraph is general reliable about trans people.
I did not say and do not think that all Loki's arguments were unrefuted. I do think it's proven that the Telegraph's reporting on the litter boxes in schools hoax was inflammatory in the extreme, that it published the report using reported speech but otherwise uncritically, and that it failed to publish a correction.— S Marshall  T/ C 07:06, 11 July 2024 (UTC)
This is just not a reasonable, policy-informed reading of the RfC. The question at issue was not Where does bias become unreliability. Bias does not become unreliability. One can be biased without being unreliable and vice versa. The question was "What is the reliability of the Telegraph on trans issues?". Being inflammatory is not evidence of unreliability. Failing to publish a correction is not evidence of unreliability if it can't be demonstrated that the paper published a falsehood.
The nomination statement enjoyed significant support and received significant opposition, and overall there was no consensus about its accuracy. Is this more vote counting? Where have you weighed arguments? Samuelshraga ( talk) 07:41, 11 July 2024 (UTC)
...and now we're getting somewhere. You don't have to be caught in a lie to be deceptive. Those appalling fundraising banners that the Wikimedia Foundation displays on our site are a really good example of this: being deceptive without actually lying. This practice of misleading people by telling the absolute truth, in an incredibly selective way, is called paltering and it's widely used by marketers, politicians, lawyers, pressure groups, and at least here in the UK, in newspapers. And if you could read what the "unreliable" camp said without understanding this, then I would gently suggest that you have an opportunity to re-read the debate more carefully.
The "unreliable" camp did not have to catch the Daily Telegraph in a falsehood. They just had to catch them telling the truth so selectively that bias becomes actual deception.
They didn't have to prove the Daily Telegraph intends to deceive. Deception can be inadvertent, particularly when it's by editors who're checking facts rather than checking for balance. We know all about this from Wikipedian content disputes: it's possible to deceive in good faith.
All the "unreliable" camp had to do was convince Wikipedians (1) that it's possible to be mislead by the Telegraph's coverage and (2) this happens often enough to affect the Daily Telegraph's reliability about trans people.
In my judgment, they failed. They did not achieve a consensus that the Daily Telegraph is unreliable.
I then had to decide what to do in the absence of a consensus.— S Marshall  T/ C 08:57, 11 July 2024 (UTC)
It's fascinating if this was the basis for your ruling, given that you don't seem to have mentioned this in either your original or expanded close.
Had you mentioned it, doubtless you would have given an excellent explanation of how when editors rebutted charges of "misleading" with a defence of factual accuracy (e.g. here), they were missing the point. And pointed to discussants who actually said that being accurate but misleading was the basis of their case for GUNREL.
And when it was argued that the bar for reliability should be rooted in what false/misleading claims could be cited in articles rather than uncitable misleading implications (first sentence here and last 2 paragraphs here), you would have explained which counter-arguments you found to this point and how you weighted them, to reach a No Consensus finding.
I also note that this is the 3rd separate explanation I've seen you give for your close. It still doesn't contain a weighing of arguments, but I'll grant you that it's less egregious than the previous two. I look forward to the next one. Samuelshraga ( talk) 10:46, 11 July 2024 (UTC)
I'm clearly never going to convince you, but I have a chance at convincing your audience, so I'll deal with that too.
I'm allowed to explain my close in different ways, because you're allowed to spend thousands of words attacking it in different ways.
It's not for me to decide which counterarguments are persuasive. That's not the closer's role.
The RFC isn't a closer's suggestion box. It's an exhaustive dive into what the community thinks.
I don't decide who was right. I decide what the community as a whole thinks about the subject.
I believe that the community as a whole is at "no consensus" on the Daily Telegraph's reliability on trans issues.
And I believe that RSP should say so.
And if I'd weighted the arguments the way you want, I really would have been supervoting.— S Marshall  T/ C 11:42, 11 July 2024 (UTC)
If I thought you'd weighed arguments in a way that I don't like - if I thought you'd weighed arguments at all - then I would have just grumbled about Wikipedia in my head, and not come to a big central forum like this.
People on this noticeboard seem to have plenty of respect for your track record as a closer, even if they think you missed the mark here. As someone who is new to these discussions, I don't see much to respect about this close. In fact I don't see much evidence that you even gave the RfC more than a cursory skim. I wasn't one of the people who invested a lot of time in the arguments at the RfC, but if I were I would be pretty livid that someone would come on and clearly count votes without reference to arguments or policy. If I encounter your future closes I will endeavour to keep an open mind, in deference to the people who seem to value your contributions in general, though not in this case. Samuelshraga ( talk) 13:06, 11 July 2024 (UTC)
  • The idea that a "refutation" must be accepted by everyone else who !votes subsequent to it is not what's being proposed here. I also don't expect S Marshall to take every unrefuted point as fact,
    The ask is that a closing statement explain why an evaluation of consensus was made.
    S Marshall accepted your view that The Telegraph promoted the litter boxes in schools hoax, but did not provide an explanation for why your claim was the consensus and why refutations of it were not. Because your claim was accepted at face value, the consensus was for Option 2.
    I expect closes to explain why opposing views were rejected in addition to summarizing consensus. Otherwise, there is no indication that a closer considered viewpoints other than the one they ultimately endorsed. Chess ( talk) (please mention me on reply) 21:02, 10 July 2024 (UTC)
    Very, very well put. -bɜ:ʳkənhɪmez ( User/ say hi!) 21:09, 10 July 2024 (UTC)
    Note that this was originally a reply to Loki's comment above, starting with But that clearly would have been a WP:SUPERVOTE. Aaron Liu ( talk) 03:14, 12 July 2024 (UTC)
  • Endorse. As Novem Linguae notes in their comment above, no consensus on source reliability is not the same thing as no change or keeping the status quo. We have here a source which where reliability is a matter of contention among editors, with dozens of well explained and policy-grounded arguments for both declaring the source as unreliable and reliable. Even discounting arguments focused on bias instead of reliability, I can see no weighing of the arguments that comes to any conclusion besides that editors do not agree on the reliability of The Telegraph on transgender topics. WP:MREL exists for a reason. RSP provides guidance on whether there is broad consensus on the reliability of common sources. Source evaluation within articles is always a matter of judging the specific claims and context. Dylnuge ( TalkEdits) 02:12, 11 July 2024 (UTC)
  • Overturn and reclose to same result. People have already pointed out the problems with the close statement itself, but I think "no consensus" is the correct conclusion to be drawn from that discussion. WP:MREL says Editors may not have been able to agree on whether the source is appropriate which I think is certainly the case here. It would be very hard to close the discussion for one side or the other without that close being a supervote itself. Pinguinn  🐧 11:38, 11 July 2024 (UTC)
  • Endorse outside of paragraph 3 The INVOLVED concerns do not move me per CNC, and I think S Marshall's interpretation of RSP (that a lack of consensus for reliability should be explicitly noted, not keep the status quo) is correct. With that being said, no consensus was found that the Telegraph articles about the Rye College debacle constituted promotion of a "hoax"; the closer writes about it as if the proposition there was hoax-promotion was agreed upon, and editors disagreed whether that alone was enough to make the Telegraph unreliable. Still, there was definitely not consensus the Telegraph is reliable for these issues; Aquillion's presentation of academic sources that criticize the Telegraph's reporting on this subject was never adequately rebutted, for one.
Even if S Marshall's close was flawed, I really do not want to go through the whole song and dance of reclosing with what will almost certainly be the same result, stated more verbosely. Sometimes I feel as if the consensus model tends toward rule by CAVE people. Mach61 13:05, 11 July 2024 (UTC)
  • Overturn Agree with the those who have argued that this should be reclosed properly. Even some of the editors who endorse the close recognize there's problems with wording of the close. The best way forward is to overturn the close and close it correctly. I realize this might seem like a waste of time, but when editors invest this much time into a review we might as well get it right. Thanks! Nemov ( talk) 14:39, 11 July 2024 (UTC)
  • Endorse Its pretty clear from above that many agree with the close substance, like I do as well. It seems that the closer made a comment in the close that led to this discussion, but that doesnt lead me to question the substance of the close. I do not find the supervote nor involved arguments to be convincing either. If the source isnt generally reliable, which clearly it isnt from this and other discussions, then it starts to look more like a drop the stick or SOAP issue to me. Jtbobwaysf ( talk) 20:03, 11 July 2024 (UTC)
    • @ Jtbobwaysf: - regardless of the substance of the close, the controversial comment I suppose you are referring to was explictly referred to in the added RSN entry: ("In the 2024 RfC, The Telegraph's "unashamed embrace of the widely-debunked litter boxes in schools hoax" was discussed, and it was noted that the misrepresentations about this remain unretracted.) How do we solve this issue if the close is endorsed? starship .paint ( RUN) 00:05, 12 July 2024 (UTC)
      The obvious place would be discussing it at RSP, to discuss how a summary should read. I don't think you'll find any support for including that quote in future, based on this discussion alone. Common sense can simply prevail here. CNC ( talk) 01:28, 12 July 2024 (UTC)
      I don't question the substance either, but it is extremely bad for what's supposed to be a neutral summary that saves peoples' time to mislead its readers on such an important point. Aaron Liu ( talk) 03:15, 12 July 2024 (UTC)
      I agree with CNC that this additional and unnecessary summary of the close should be trimmed over at RSP. The fact that we are discussing such far off theories (even if untrue) associated with this source should point to the validity of the close. Again I endorse, I am confident the additional comment can be struck without needing to re-run the discussion. Just do what is simple rather than making it complicated. I believe whoever closes this discussion can just find that the close comment as a matter of fact is incorrect (while the overall close is non-controversial), strike it, and thus subsequently remove the summary over at at RSP. Seems simple enough to me Jtbobwaysf ( talk) 09:57, 12 July 2024 (UTC)
      So now we've got the nominator at this close review who wants to overturn, and an uninvolved contributor who endorses, both giving exactly the same reasoning for their position.— S Marshall  T/ C 10:36, 12 July 2024 (UTC)
      Important to note that I dont agree that the closer was involved, so we disagree on a key policy issue. We can be clear from this review discussion as well as the original discussion that there is clearly no-consensus that the source is reliable, or anywhere close to reliable for that matter. This isnt a matter where this discussion is going to be overturned and then spontaneously the source will be viewed in the next discussion as reliable. So common sense means we would not need to overturn this to put it back to another discussion, as if the matter was undecided. We are only dealing with a close summary that was a bit off, but the close itself is correct. Thanks! Jtbobwaysf ( talk) 11:28, 12 July 2024 (UTC)
      I think that overturning that paragraph counts as overturning the close. It seems Jtbob feels like the biggest damages can be resolved without amending the close statement and that the summary isn't damaging enough to amend, the latter of which I definitely disagree with. Aaron Liu ( talk) 15:33, 12 July 2024 (UTC)
      You're right that directly amending the close would be overturning. Hence for example I endorse the close as the correct outcome, but can understand overturning based on the summary. The reality is this RfC could be closed specifying that parts of the closing summary X, Y and Z, were inappropriate and/or inaccurate, while not directly overturning that RfC, only adding an additional summary to it, based on the discussion that has occurred here. Ie as a note to the top of that RfC, but not within it, thus not actually overturning the close itself. Sometimes it'd be nice to simply think outside the box to avoid a lot of legwork of re-closing such a long RfC. CNC ( talk) 16:17, 12 July 2024 (UTC)
      I don't see how the additional summary would work. If it doesn't mention that the close's language on Rye College is inaccurate, then it won't really be effective. If it does, I feel like we'd need consensus that it's inaccurate. Aaron Liu ( talk) 18:21, 12 July 2024 (UTC)
      Consensus based on the close of this RfC, attached above the previous. It would be the same concept as re-closing with the same result, without the extra hassle. A new concept you might say. CNC ( talk) 19:54, 12 July 2024 (UTC)
      I feel like that would require the same level of consensus as a closure review. Aaron Liu ( talk) 22:09, 12 July 2024 (UTC)
      It wouldn't no. It would be another RfC closure, as this is an RfC. CNC ( talk) 22:22, 12 July 2024 (UTC)
    This isn't an RfC, and if it requires consensus here anyway I'd rather we just amend the original language than invent something untested and potentially confusing. Aaron Liu ( talk) 22:31, 12 July 2024 (UTC)
  • Endorse except paragraph 3. S Marshall's interpretation of RSP is right. However, 'unashamed embrace' of the litter boxes hoax is an inaccurate summary of consensus. That incorrect phrasing was immediately being used in RSP for anyone looking-up the source. Rewriting that part might be the simplest way of resolving this, some editors have helpfully suggested alternative wording. I can believe the closer is usually good, I agree with much of what they say and know closing detail is tricky, but the summary currently doesn't do justice to the editors who spent time analysing the sources. It makes sense to bring up the further explanation added by the closer afterward, up into the main summary, so it's all easily accessible without further clicks, Tom B ( talk) 22:42, 12 July 2024 (UTC)
  • Overturn The close was no doubt in good faith, however it is not well argued, and indeed it should not really be argued at all. It also isn't really a close.
    • It gives platform to the most flagrantly gender-critical tracts by anti-woke activists. This is irrelevant. Tracts by activists are opinion pieces, and whether they are the "most flagrant" or the "most Satanic" or the "most wonderful" they should not be cited for anything other than the opinion of their authors.
    • widely-debunked Litter boxes in schools hoax - as remarked elsewhere the Telegraph pointed out that it was a hoax. The only factual error seems to have revolved around whether there was a cat identifying pupil, which to me seems irrelevant. The crux of the story is the, undisputed, unkind criticism of the child who thought such a thing would be silly.
    • We label a source as "generally reliable" when there's widespread consensus that the source can be trusted to publish fact and retract error. I think this is overegging the pudding. In general there is consensus among relatively few editors, which we believe would be widely shared.
    • We must say […] that the Daily Telegraph is generally reliable, except as regards trans issues and gender-critical views, where the Daily Telegraph's reliability is disputed. This is really not a close. It's a continuation of the RfC by other means.
All the best: Rich Farmbrough 00:43, 13 July 2024 (UTC).
  • Overturn - too much of the closer's own opinion on the issue in dispute was in the closing statement; not enough of the statement was spent summarizing the discussion and explaining how votes were weighed. Let someone else close it; no comment on how it should be closed. But a "no consensus" result at RSN (for a perennial source) should mean a 2 (yellow) listing at RSP. That's what "2" means: no consensus on reliability. "1" if there is consensus it's reliabile, "3" if there is consensus it's not, and otherwise, 2. Levivich ( talk) 18:13, 13 July 2024 (UTC)
  • Overturn. I did not participate in the discussion and have no interest in this dispute other than an interest in broadsheet newspapers generally. The close misrepresents consensus. For example, the close says that the Telegraph embraced the hoax. In reality, there is at least no consensus that the Telegraph embraced the hoax, and a lengthy argument about whether it did. Similarly, the close misrepresents and displays a failure to understand policy. For example, the close claims that a source is not "generally reliable" unless there is widespread consensus that it is. In reality, the policy WP:NEWSORG says that news reporting from well-established news outlets is "generally" reliable for statements of fact. If it is possible under that policy to dispute the "general" reliabilty of the Telegraph at all (and it is not obvious that it is possible to dispute it under the policy, if you accept that the Telegraph is "well-established" as a national daily quality broadsheet newspaper of record established in 1855, and one of at most five such newspapers still published in England), the policy must create a presumption that it is generally reliable and place the burden of proof on those who seek to rebut that presumption. Likewise the closer claims that WP:ONUS applies to disputes over the reliability of sources. In fact, WP:ONUS applies to the disputes about the inclusion of content in articles, which is a completely different matter concerned with the exclusion of verifiable content on grounds of "due weight" and similar issues. Likewise the closer claims that the question in the RfC was where does bias become unreliability? In reality, policy WP:BIASED says that reliable sources are not required to be unbiased. Finally, the closer misrepresents the effect of no consensus in a discussion where there are already policies, namely WP:NEWSORG and WP:BIASED. If there are policies, there is an existing site consensus. WP:DETCON says "consensus is ascertained by the quality of the arguments given on the various sides of an issue, as viewed through the lens of Wikipedia policy" (my emphasis). That appears to mean viewed through the lens of the policy WP:NEWSORG. I think I should also point out that WP:RSP is not a policy or guideline, does not override the policy WP:NEWSORG, and should have been weighted accordingly. I think it could also be reasonably argued that no consensus is capable of meaning "no consensus to change the text of RSP", but I express no opinion about whether it does mean that. James500 ( talk) 07:52, 14 July 2024 (UTC)
    WP:NEWSORG isn't policy, and it doesn't say all newspapers are reliable unless there's consensus otherwise. We've rightly found parts of the British mainstream press, notably but not only the Daily Mail, properly unreliable in the past. The burden of proof doesn't lie where you say it does.— S Marshall  T/ C 09:27, 14 July 2024 (UTC)
    Okay, upon closer inspection, I find that WP:NEWSORG is in fact a guideline, and not a policy. However, if WP:DETCON does not apply to guidelines, the effect would be to throw all guidelines out of the window. I am not aware that we have ever found a quality broadsheet print newspaper to be unreliable. The Daily Mail is a tabloid, and it is not, and as far as I am aware, never has been, quality press. It is not apparent that the Daily Mail is "well established" within the meaning of WP:NEWSORG. I think I should point out that NEWSORG makes a distiction between news sources being reliable and their being generally reliable. I am not saying that the Telegraph cannot be unreliable for a particular fact or statement, or even for a particular topic. I am saying that "generally reliable" means something different to that in NEWSORG. James500 ( talk) 09:43, 14 July 2024 (UTC)
    Well, exactly so. The discussion we're analysing is about whether the Telegraph is unreliable for a particular topic, to whit, trans people. My position is that there's no consensus about whether it's reliable for that topic, and that WP:RSP should say so. Do you think there's a consensus it's reliable?— S Marshall  T/ C 11:08, 14 July 2024 (UTC)
    Even if all well-established broadsheet newspapers are presumed to be generally reliable until found otherwise, this requires that there be some mechanism by which such newspapers can be found otherwise (otherwise we would be saying they are always generally reliable regardless of any evidence to the contrary). That mechanism is a discussion at RSN, and this RFC was an example of such a discussion. It follows that it must be possible for that discussion to find that a well-established broadsheet newspaper is something other than generally reliable, either for all topics or for some subset of topics. Whether this discussion did establish that is the point of this discussion. Additionally, the reliability of a source can change over time - just because the Telegraph has a long history of being regarded as reliable does not imply anything about whether it is or is not reliable today. Thryduulf ( talk) 11:34, 14 July 2024 (UTC)
    I am going to strike my !vote, since it appears that it might actually be unitelligible. I was not asserting that the newspaper was reliable on this topic, a matter on which I have no personal opinion. All that I objected to was to was certain reasoning and wording used in the closing statement and by the closer to produce a particular outcome. I did not mean to express any opinion on the outcome itself. James500 ( talk) 11:55, 14 July 2024 (UTC)
    I don't think it was unintelligible. The close mispresents consensus. For example, the close says that the Telegraph embraced the hoax. In reality, there is at least no consensus that the Telegraph embraced the hoax, and a lengthy argument about whether it did. This on its own is a perfectly reasonable and widely shared opinion that argues for overturn, before any weighing of the second part of your comment.
    Your opinion about the relative weight of the status quo in the presumption of reliability in established news organisations should not have been read by anyone as an argument that the Telegraph was reliable. I think it was an important response, especially that you pointed out that no consensus is capable of meaning "no consensus to change the text of the RSP". It was certainly my understanding of the RfC, and the way that I framed my contribution to it, that the question was whether the evidence presented merited downgrading the Telegraph, and that positive arguments for its reliability were assumed. I'm sure some editors would have put those arguments had the discussion been framed in the way that some people in this review now interpret it. Samuelshraga ( talk) 14:27, 14 July 2024 (UTC)
    The question was "What is the reliability of the Telegraph on trans issues?". If the outcome of that discussion is "no consensus", how can an RSP entry saying "Editors show consensus that the source is reliable in most cases" on trans issues be accurate or appropriate? This is a genuine question - I am trying to understand the arguments for that position because I currently do not. Thryduulf ( talk) 16:51, 14 July 2024 (UTC)
    The RSN RFC question was exceedingly clear, and is the standard question for RSN RFCs: What is the reliability of the Telegraph on trans issues? The questions was not "should it be downgraded," or "should the RSP entry be changed", in which case, one could argue that no-consensus means no change. But since the question was "What is the reliability?" with the standard 4 options, no consensus on the reliability means Option 2, at least in my view. And that's true for all RSN "What is the reliability?" 4-question RFCs. Levivich ( talk) 19:16, 14 July 2024 (UTC)
    I didn't think it was unintelligible either; seemed well-reasoned to me. Levivich ( talk) 19:13, 14 July 2024 (UTC)

Participants

  • Support close. So, technically speaking, the Telegraph may have "only" supported a clearly false assertion that is very similar to the litter boxes in schools hoax, depending on how narrowly you read that page. However, IMO this is a nitpick. In practice what they said has all the important elements of the litter boxes in schools hoax: the important bit is that they claim a school officially supported students identifying as animals, and not the literal litter box part. If you object to the wording at WP:RSP, then edit that. Loki ( talk) 05:05, 9 July 2024 (UTC)
    I object to the wording of the part of the close quoted at RSP. As long as the quoted content remains part of the close, I'm pretty sure arguments for removing it are unlikely the gain ground.
    Regardless of whether the hoax includes the situation in the articles mentioned, casual readers are likely to misinterpret what the misrepresentation is at first glance, which is something a summary should avoid. This "nitpick" has been raised at the closer's talk page and he has refused to change this wording. Aaron Liu ( talk) 05:10, 9 July 2024 (UTC)
    As was clearly and prominently refuted during the discussion, the Telegraph did not claim a school officially supported students identifying as animals. They reported, as a reliable source is allowed to, that the parents of a suspended student claimed that the school was doing that, and citing that belief to the parents themselves. -bɜ:ʳkənhɪmez ( User/ say hi!) 05:30, 9 July 2024 (UTC)
    If you think that was refuted at all, much less clearly, you're wrong. In fact I personally think you're lying, since it very clearly wasn't. Loki ( talk) 14:06, 9 July 2024 (UTC)
    It very clearly was, based on the relative amount of “legitimate” !votes for 1/3/4 after it was (legitimate meaning not based on “it’s biased” or “I don’t like it”), and for you to accuse me of lying shows a massive lack of AGF. -bɜ:ʳkənhɪmez ( User/ say hi!) 14:19, 9 July 2024 (UTC)
    It should be pretty clear that you can't just count votes to decide on a factual claim. Many people weren't convinced by my argument as a whole, but also many were, including several who were specifically convinced by the Rye College thing. Conversely many Option 1 voters, like the closer noted, waved off the Rye College articles as a single mistake without denying they were false. Loki ( talk) 14:23, 9 July 2024 (UTC)
    Yet significantly more people were either not convinced by your claims in the first place, or - and this is the important part - were convinced by the refutations. The mere fact that a relatively small proportion of editors claimed to still be convinced by your evidence does not change the fact that there can be consensus on reliability. If 10% of editors think it’s unreliable, but 90% were happy with the refutation, then it’s laughable to suggest it should be listed as “unclear” - that would be one of the clearest consensuses possible. Yet the closer didn’t even attempt to evaluate how the discussion evolved or the relative strength of the arguments. -bɜ:ʳkənhɪmez ( User/ say hi!) 14:29, 9 July 2024 (UTC)
    I've just re-read every bolded "Option 1" !vote, and and while I may have missed something I can't see any who waved off the Rye College articles as a single mistake without denying they were false. If I did miss something, can you link the !votes? BilledMammal ( talk) 14:35, 9 July 2024 (UTC)
    For the record, I also do not think that S Marshall is INVOLVED based off personal experience closing an RFC while having previously participated in an RFC in the topic area, and having that firmly upheld on close review. Loki ( talk) 14:08, 9 July 2024 (UTC)
  • Overturn, and reclose. The closer did not take into account, or at a minimum failed to explain how they took into account, the number of !votes (primarily on the "unreliable/deprecate" side, but also a few on the reliable side) that were based solely on "I don't like it" or "it's biased thus by default unreliable" standpoints. That fact alone should merit overturning the close, since the closer did not take the strength of those arguments into account and down-weight them accordingly. However, the closer also admits on their talk page that they basically supervoted. They didn't assess the community's belief, and especially Chess's refutation, of the claims regarding the "cat" hoax/"litterbox" hoax. They assessed, without explaining how they felt the community came to that consensus, that it was blatant misinformation, and they based their close in large part on the fact that, since the source published information about that, all arguments for unreliability must be accurate. In fact, Chess and other users (including myself), refuted the fact that it was a "hoax" published by the Telegraph - the Telegraph published what others were saying about it, and cited their sources accordingly when they did report the views/opinions of others. However, the closer did not take into account any of these arguments made. Lastly, there was a clear turn of the discussion after Chess and others discussed and refuted the claims at length during the discussion. Before Chess's comments and the ensuing discussions, there were people claiming that the evidence presented at the start was grounds for unreliability on its own. Many of these people admitted that Chess's refutation was valid, and that their arguments were much less strong. But even more damning for this close, after Chess's refutations and the ensuing discussions had been discussed, there were virtually no !votes for unreliable/deprecate that were actually based on the evidence presented at the beginning. The vast majority, if not all, of the !votes after the discussions were based on the improper arguments such as "I don't like it" or "It's biased thus unreliable", which were not properly weighted by the closer. Ultimately, I thank the closer for making an attempt, but it is clear that the close failed in three primary ways: It did not evaluate the strength of the arguments, it did not evaluate the "turn of the tide" after the opening arguments were largely refuted, and the closer injected their personal opinion as to the "cat/litterbox" hoax into their evaluation. For these reasons, the close should be overturned. -bɜ:ʳkənhɪmez ( User/ say hi!) 05:27, 9 July 2024 (UTC)
  • Overturn. The close is not close to a faithful conclusion of the discussion. The issues with this close are in the third and fourth paragraphs. In the third, the close takes as a fact The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax. Any reading whatsoever of the discussion will show that the idea that the Telegraph promoted some version of the litterbox hoax is contested, with many editors subscribing to refutations of this point.
    The next paragraph goes on to assert that On trans issues, Wikipedians simply do not have this level of confidence in the Daily Telegraph. The only argument referenced to this point has been the litterbox one. Editors who took issue with the third paragraph therefore found the fourth, which finds that reliability is disputed, to be invalid. However, the closer clarifies on talk that Fourth paragraph is independent of the third.
    The assessment that reliability is disputed was therefore not given any justification in the close itself, so closer expanded the close. The expansion provides but one reason why to give weight to the argument that the Telegraph is not generally reliable on trans issues: Although some members of the community have confidence that the Daily Telegraph is reliable on trans issues, this view is strongly disputed by significant numbers. In other words, closer is counting votes. Except closer tells me on talk that the point is not to count votes, and I didn't, but to weigh arguments, which I did.
    Closer has shown no evidence of weighing arguments (except in the case of the litterbox hoax claim, in which closer showed no evidence of weighing arguments fairly). Closer claims both not to have counted votes, but also bases their close of "Reliability disputed" on the claim that the view that the Telegraph is reliable "is strongly disputed by significant numbers". If closer is not willing to revert, close should be overturned as closer won't give a consistent account of what the reason is for the close. Samuelshraga ( talk) 06:51, 9 July 2024 (UTC)
  • Support close because I think it's a perfectly reasonable close despite me thinking very negatively of The Telegraph. My emotions want it deprecated, but I know that this is the best we can get. LilianaUwU ( talk / contributions) 07:36, 9 July 2024 (UTC)
    Seraphimblade, you can't reopen the discussion when it's still at AN... I would say the same if I wanted it overturned. LilianaUwU ( talk / contributions) 11:48, 9 July 2024 (UTC)
    Oh, and that's misuse of rollback. LilianaUwU ( talk / contributions) 12:21, 9 July 2024 (UTC)
  • Support close, but what the hell is (The Telegraph) is a willing warrior in the war on wokery. It gives platform to the most flagrantly gender-critical tracts by anti-woke activists. I'm not sure what "woke" is being used as a synonym for here, but there are better words for the Telegraphs "anti-woke activists". They are called transphobes. Most of them even call themselves "gender-critical", which is the same thing. Also, radical feminists like Julie Bindel are not "anti-woke". Black Kite (talk) 10:18, 9 July 2024 (UTC)
    I don't see gender-critical and transphobic as 100% synonymous although Julie Bindel certainly qualifies as both. I specifically wanted to say that the Telegraph is activist on this issue.— S Marshall  T/ C 10:23, 9 July 2024 (UTC)
  • Overturn - first I would like to thank S Marshall for their effort in closing such a large RfC, as they have done so many times before. Unfortunately despite that, I share the concerns of Berchanhimez and Samuelshraga particularly regarding the litterbox issue, it was far more disputed by editors than what the original and extended closures portrayed. Since this was a significant and prominent part of the close, that causes the entire closure to fall into doubt. starship .paint ( RUN) 12:12, 9 July 2024 (UTC)
  • Kind of overturn I agree with the closing in that when we have such a clear 1 or 3 split we can't just say no consensus so no change. Certainly such a gap means on this topic we need to use caution. I also agree that the closing was not a summary of the arguments and for that reason the closing statement either needs to be changed to align with a true summary of the discussion or another editor should close the discussion. That the source was biased seemed to have consensus but how much did not have a consensus. The closing suggests there was agreement on how biased the source was. I also agree that some of the language used in that part of the closing appeared to be expressing an opinion rather than summarizing the discussion. Since much of the discussion centered on the litter box hoax it is important to get that part of the close correct. I think all would agree that there was a clear dispute regarding if the source was just reporting or if they were embracing. As such the claim that the statement, "The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax" is clearly inaccurate. I don't have a strong view on the involved claim but I'm not sure I view that as disqualifying in this case. Springee ( talk) 12:19, 9 July 2024 (UTC)
  • Overturn
    The close expansion includes: Towards the end of this, the "generally reliable" camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes, which I receive as a concession that the article is misleading. I don’t see this in the discussion.
    Also, there is no mention of the general disparity between those who supported Option 1, who generally discussed the question of whether the Telegraph is reliable on transgender matters - which is what the RfC was supposed to be about - and those who supported Option 3, who mostly said we should not use the Telegraph on transgender matters because it is biased – which is not what the RfC was supposed to be about.
    On the contrary, the closing comment summarises the attitude of those who preferred Option 3, It is a willing warrior in the war on wokery. It gives platform to the most flagrantly gender-critical tracts by anti-woke activists.without making the obvious conclusion that such views are irrelevant to an RfC on reliability. Sweet6970 ( talk) 12:39, 9 July 2024 (UTC)
  • Overturn, the weighting and evaluation of the arguments was done poorly, and the tone of the original close leaves much to be desired. Unfortunately, some of the summaries of the arguments (like the cat story) was either done poorly, or added onto through the closers own arguments trending towards a supervote. Lastly, whether or not the closer is clearly involved, there is definitely a strong appearance of involvement, which is enough IMO. FortunateSons ( talk) 12:56, 9 July 2024 (UTC)
  • Support closer, oppose close. It's a real stretch to accuse S Marshall of being involved for having an opinion on a related matter (or even on this matter). We're not robots nor should we pretend to be - and I have previously seen S Marshall demonstrate high competence in separating personal views from the principles at hand in a discussion. However, I do agree that the close rationale erred in endorsing a point that had been thoroughly rebutted in the discussion, and in taking a bold interpretation of WP:ONUS. It is not clear to me that the policy on onus with respect to article content should automatically apply to discussions of general reliability. This is a point that could potentially be argued in the abstract, but in this specific case, when our starting point is a previous RfC finding general reliability, then the onus should very much be on bringing new evidence, and the focus of the close should be on whether or not that evidence has been successfully rebutted - not on whether there was a dispute. If there's no consensus that the new charges are valid, then they should be considered unproven, and the status quo should remain. Proving unreliability should be hard, as a countermeasure to the chilling effect of a downgrade. Barnards.tar.gz ( talk) 12:58, 9 July 2024 (UTC)
  • Overturn. The closer was WP:INVOLVED with respect to The Telegraph's reliability in the context of political topics, as their comment from April 2024 shows. And the sort of involvement does somewhat show in the close; the close does not faithfully represent the consensus attained on key points, and it doesn't appear to attempt to summarize what the arguments on each side were. Instead, the close reads much more as if it were a !vote in the RfC, where the closer inserts his own analysis of the source (It is a willing warrior in the war on wokery) and appears to give definitive weight to one questionable interpretation of The Telegraph's reporting (unashamed embrace of the widely-debunked Litter boxes in schools hoax) as if it were to have reflected the broad consensus of the discussion.
    Because the closure should represent the discussion faithfully, and this closing summary is more of an argument than an attempt to do so, it should be overturned. — Red-tailed hawk  (nest) 13:56, 9 July 2024 (UTC)
  • SMarshall was not INVOLVED. I'm not going to express an opinion about the close as a whole as I fear I would fail to avoid the relitigation that multiple editors here are doing) but I see absolutely no evidence that SMarshall was INVOLVED within the meaning of that policy and so that allegation should not be factored into the assessment of the close. Thryduulf ( talk) 14:38, 9 July 2024 (UTC)
  • Overturn - the finding that there was no consensus the Telegraph is not reliable, but the source should still be considered "not generally reliable" (in some unspecified way) is unreasonable. It is probably better to vacate it entirely rather than modify it to a pure "no consensus" close. Walsh90210 ( talk) 15:47, 9 July 2024 (UTC)
    No consensus (MREL) also means "not generally reliable" (GREL). It does not mean "generally unreliable" (GUNREL). Everything that isn't GREL is not generally reliable to put it simply, such as a "pure no consensus close". CNC ( talk) 15:53, 9 July 2024 (UTC)
    That's just how WP:RSP works. The normal rule of no consensus = no change doesn't apply. Instead "no consensus" is a status, and it's WP:MREL. Loki ( talk) 16:33, 9 July 2024 (UTC)
    This is ridiculous. If there is "consensus for no consensus" that is one thing, but a "no consensus at all so a specific change must happen" is a supervote. Walsh90210 ( talk) 18:26, 9 July 2024 (UTC)
    You might think it's ridiculous but that's how RSP works. "Generally reliable" is defined to mean "there is a consensus that this source is generally reliable". There is a specific category for sources about which there is no consensus. Thryduulf ( talk) 18:32, 9 July 2024 (UTC)
    I think we're at the point of " beating a dead horse". I've asked below in the clarity section on whether this RfC should be an exception to the status quo, or whether RSP should be changed, and if so whether it should be retrospectively; but so far there are no proposals. Any closer of this discussion is surely aware of how RSP operates by now. CNC ( talk) 18:39, 9 July 2024 (UTC)
  • Support close to prevent time-wasting: I supported option 3 but find the close a clear reading of the discussion. While it's not a vote count, we should be on the same page about the trend of the discussion. By a quick count: ~55 editors said option 1 (with many arguing it was biased but not enough to effect reliability), ~8 supported option 2, ~50 said option 3/4, ~8 said 1/2, and ~4 said 2/3. That leaves us with a clear majority in favor of "there are issues with calling this straight up reliable" (~8070(fixed per starship) v ~55, with, as I noted, many in the latter camp acknowledging it does have a GC slant). Editors presented RS that supported the claims of bias as well. When such a large outpouring of editors have significant concerns regarding a source's reliability, that must be reflected in the close - there was no earthly way this could have been closed with "the community agrees this is reliable on trans topics". WRT claims that those questioning it's reliability did so on WP:IDLI grounds - editors considered platforming anti-trans activists and talking points in every article a clear sign of unreliability/bias just as if their editorial line was obviously pro-flat earth or pro-race realism (please note that regardless of your opinions on whether the GC movement is correct or not, RS do overwhelmingly say it's a hate-based movement supportive of disinformation). Your Friendly Neighborhood Sociologist ⚧ Ⓐ ( talk) 15:59, 9 July 2024 (UTC)
    • Addition error. 70 per your numbers. Not 80. starship .paint ( RUN) 16:26, 9 July 2024 (UTC)
    • P.S. Everyone should disclose how they voted Your Friendly Neighborhood Sociologist ⚧ Ⓐ ( talk) 15:59, 9 July 2024 (UTC)
      I simply don't see how you think counting votes is an argument in support of a close, especially when the closer's only justification is that they counted votes. (Leaving aside the fact that counting 1/2 !votes as against calling it WP:GREL is a stretch. Those votes explicitly support calling it generally reliable, and are broadly saying they would accept/support adding a note in RSP, not downgrading the source. I conclude this by actually reading those comments, rather than counting them.) Samuelshraga ( talk) 18:02, 9 July 2024 (UTC)
    • Could you address the reasons we, or at least I, brought up the close review? Aaron Liu ( talk) 18:18, 9 July 2024 (UTC)
      Gladly: to start, please take my comment in the context that the close review grew beyond your point.
      • Regarding the "overturn whole close": I do not believe the closer was involved (which would, in my view, entail either participating in the discussion or being generally active in GENSEX). I do not believe he misread the discussion in finding MREL.
      • Regarding your specific note on the litter box hoax: I actually agree with you it could have been better (though on procedural grounds I think it was fine and this 2 pronged close review is wasteful of editor labor). Being more specific:
        • The litterboxes were extensively discussed and would inevitably have been mentioned in the close. An uninvolved editor weighed up the arguments on both sides, and believed that the "hoax promotion" had better ones - but it could have been the other way or more equivocal and still be a valid close imo. To be clear, I think The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax is discussed could have been better phrased as Whether the Telegraph embraced the widely-debunked ...
        • That being said, I think it should have been a more general statement on misinformation: misrepresenting the Cass Review, incorrect statements on "desistance", use of meaningless scarewords like "gender ideology" or "trans agenda" in its voice, and etc. Particularly, as many noted, platforming FRINGE groups to make false statements on issues while portraying them as experts and disregarding more mainstream ones.
          • Sidenote to that, I disagreed with the extended close's statement about its historic homophobia and advocacy for conversion therapy (neither of which is the paper's current editorial position). - They no longer support LGB conversion therapy, but its blatant in practically every article that they support it for trans people, and I would further argue that their repeated framing of issues as LGB v T, as if they're mutually exclusive, is homophobic in itself.
      Your Friendly Neighborhood Sociologist ⚧ Ⓐ ( talk) 20:53, 9 July 2024 (UTC)
      To your point on the "litterbox hoax" and their reporting on it, your recommended alternative sentence starting with "whether" changes the meaning completely. SM's close referred explicitly to the fact that many people "believed" they "embraced" the hoax, and did not address the fact that, aside from those whose !votes were based on their opinions on the underlying subject as a whole, the majority of editors did not see it as being reported as truthful in the reporting - and in fact a reading of the articles in question confirms that they are right to not see it that way. If editors base their !votes on "facts" that are disproven, whether before or after their !vote, then their !vote needs to be weighted down accordingly - not given full/extra weight as SM did. -bɜ:ʳkənhɪmez ( User/ say hi!) 21:08, 9 July 2024 (UTC)
      This seems to be a bit of a point of dispute in these discussions. I think some of the endorse editors look at the yellow rating and reasonably say, "with arguments on both sides and a clear 1 vs 3 division yellow is the only reasonable outcome." I can get behind that. However, I also agree with editors who note that there were clear errors in the summary of the arguments. I don't see how a reasonable close could state as fact that the source embraced the litter box hoax. That was a clear point of contention and if neither side convinced the other then we shouldn't treat it as some sort of consensus outcome. When doing a closing it's not just that the color needs to be right, the summaries need to be accurate as well. We don't have that here. At minimum editing the summary to reflect the actual state of the discussion is warranted. Personally, I think having a new closing is better. Springee ( talk) 21:16, 9 July 2024 (UTC)
  • Overturn. Two distinct issues here:
    1. Imbalance and inaccuracy in the summary. Rather than fairly sum up both sides of the discussion, the close is weighted towards the unreliability perspective to an extent that does not reflect the genuine course of discussion. Vigorously contested assertions (e.g. the notion of The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax) are treated as fact. At times S Marshall appears to be carrying on the argument in his own close (e.g. Towards the end of this, the "generally reliable" camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes, which I receive as a concession that the article is misleading. And if the Telegraph has published a correction, then the "generally reliable" camp hasn't unearthed it.)
    2. The, um, let's call it "novel" interpretation of ONUS such that a supposedly "no consensus" close somehow ends up in effect a consensus to downgrade? I don't have much to add to what Barnards has already said: (1) ONUS is geared towards discussions about whether to include specific things like an image or a certain paragraph in an article, not broad discussions about the reliability of a source; and (2) there's an existing RfC finding consensus for general reliability, so that should be the assumed baseline we're working from.
  • S Marshall made an odd comment about the decision to adopt this interpretation: In doing this, I removed the first mover advantage that the "generally reliable" side expected and I think relied on. The part about editors advocating for reliability "relying on" a supposed first-mover advantage comes across to me as if he is taking the view these editors are abusing or at least leaning on procedure to get a preferred result. This does not seem to be a fair characterisation to me.
  • I don't see how S Marshall is INVOLVED, though. – Tera tix 16:26, 9 July 2024 (UTC)
  • Support close. It was a very reasoned, balanced close. I would have preferred a "generally unreliable" close, but I accept that S Marshall made a good faith effort to close this RfC in a balanced and impartial manner. -- Amanda A. Brant ( talk) 17:39, 9 July 2024 (UTC)
  • Overturn, and reclose per Berchanhimez. S. Marshall deserves some credit for stepping in where angels fear to tread, but a no-consensus outcome doesn't justify changes to the status quo. *Dan T.* ( talk) 17:56, 9 July 2024 (UTC)
    It explicitly does at WP:RSP, and in fact "no consensus" is part of the definition of WP:MREL. Loki ( talk) 19:48, 9 July 2024 (UTC)
    Let's leave it for Part 2 to deal with. CNC ( talk) 20:04, 9 July 2024 (UTC)
  • Endorse close and this relentless badgering of closers when a consensus doesn't go someone's way needs to stop. I've seen it a lot in the last year and if it's not stamped down on it's going to be next to impossible to find anyone to volunteer to close anything but the most obvious community discussion. Daveosaurus ( talk) 18:21, 9 July 2024 (UTC)
  • Endorse close. It accurately reflects the discussion and the state of consensus (or lack thereof) on the topic; and the arguments it mentions are summarizing ones from the discussion, not new ones presented by the closer. The WP:QUO / WP:ONUS argument doesn't make sense to me - those policies are for article space, where we have no choice but to decide on one version even when we lack consensus. RSP isn't an article, it's a summary documenting where the community stands on specific sources; a lack of consensus can and should be documented there. No-consensus outcomes get lodged there as a matter of course; AFAIK that's how it has always worked. It would be misleading to do otherwise and would lead to disputes where people attempt to rely heavily on a source only to face conflicts and be told that there's no consensus on it. There is an entire category for no-consensus outcomes on RSP, and numerous entries on the table that use that specifically in their language; it makes no sense to not use that here. -- Aquillion ( talk) 19:25, 9 July 2024 (UTC)
    Summarizing a minority opinion that was strongly refuted, and the refutation of which was agreed with by a majority of editors commenting after the refutation, does not a no consensus finding make. Even if you believe that SM was not imposing their own opinion on the closure, the summary of the opinions presented and their relative strength was insufficient as it did not take into account the "turn of the tide" in !votes after the refutation, and in fact it tries to claim that after the refutation the reliable camp's arguments got worse - the exact opposite of what happened. -bɜ:ʳkənhɪmez ( User/ say hi!) 21:05, 9 July 2024 (UTC)
  • endorse close. I think the language used could have appeared to be more neutral, but it is clear that there is no consensus on the telegraphs reliability on this topic. That some people seem to think consensus is needed to confirm there is no consensus seems nonsensical, unless we all do a close that could never be decided. I don't think the close is perfect but it's certainly good enough and every editor involved could probably be more useful spending time elsewhere. For transparency's sake I voted option 3 on the RFC and was deemed a SPA. LunaHasArrived ( talk) 21:02, 9 July 2024 (UTC)
  • Overturn The assumption that people saying that mistakes happen were conceding that the specific example brought up was actually a mistake was not supported. That leaves a fundamentally damaged evaluation of the wider consensus as to whether there were mistakes in this area, which is a key aspect of changing the assumed reliability of this source. The result is an artificially strong consensus not supported by the arguments. CoffeeCrumbs ( talk) 22:58, 9 July 2024 (UTC)
  • Overturn. The only policy-based reason S Marshall's close was based on is whether or not The Daily Telegraph endorsed the Litter boxes in schools hoax. The conclusion S Marshall reached is that The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax is discussed at great length. This is a WP:SUPERVOTE because it sides with Loki's original claim without any explanation. One of the central disputes of the RfC was whether or not the "Litter boxes in schools hoax" encompassed a student merely identifying as a cat, which is the falsehood The Telegraph supposedly said. The assumption that these were equivalent made it impossible to reach any other conclusion than Option 2 or 3, which I will show below.
    S Marshall's only mention of specific Option 1 arguments is that the "generally reliable" camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes, which I receive as a concession that the article is misleading. This misses the point, which is that The Telegraph promoting a blatant hoax is not equivalent to getting a detail in a story wrong. S Marshall did not address this in this point in their close because of the aforementioned SUPERVOTE, which assumed equivalence between kids using litter boxes and kids identifying as cats. If the equivalence was treated as a disputed point, the concession that the article is misleading matters much less, since it is no longer a concession that The Telegraph promoted a blatant hoax.
    Closers are also supposed to disregard votes not based on policy per WP:DISCARD, and not judge on headcount. S Marshall's close does not obey this. Consensus is not determined by counting heads or counting votes, but S Marshall says Although some members of the community have confidence that the Daily Telegraph is reliable on trans issues, this view is strongly disputed by significant numbers. as an explanation of their decision. [14] The close also makes references to the controversy over homophobia, transgender breast milk, and other factors, but does not explain how those subpoints helped reach a decision. If the closer does not analyze a point I will assume it did not play a part in the decision.
    To summarize, the close began by assuming that Option 3 was correct on the most significant part of the discussion, and then judged the entire rest of the RfC on those grounds. This assumption should not have been made and a proper close would fairly summarize the dispute over whether implying a student identified as a cat is equivalent to saying students are using litter boxes in schools. Chess ( talk) (please mention me on reply) 00:21, 10 July 2024 (UTC)
    It's actually worse, as S Marshall claims that the close is not based on the finding on whether the Daily Telegraph embraced the litterbox hoax. So there was no policy-based reason for the close. Samuelshraga ( talk) 15:55, 10 July 2024 (UTC)
  • Overturn close. It is clear from this edit [15] that the closer had a POV that should have been declared. Xxanthippe ( talk) 02:51, 10 July 2024 (UTC).
    The community has already found in a similar situation that voting in an RFC in the topic area does not make a closer WP:INVOLVED. Loki ( talk) 03:03, 10 July 2024 (UTC)
    This isn't just two discussions in the same topic area; it's two discussions about the reliability of the same source. BilledMammal ( talk) 03:09, 10 July 2024 (UTC)
    Yes, and in the previous situation I had !voted in an RFC whose result was directly relevant to the close. However, the community very clearly endorsed the close and overwhelmingly said I was not WP:INVOLVED.
    The thing you're missing here is that WP:INVOLVED is not about bias or opinion. It's closer to WP:COI: the point is that you cannot close a discussion that you participated in. But having an opinion on the discussion doesn't matter, that doesn't make you involved at all.
    In general, Wikipedia policies don't prevent an editor from doing something due to having expressed an opinion on that topic. Instead, they prevent editors from doing things because of concrete relationships with discussions or topic areas: you can't cite your own research and you can't close a discussion you !voted in, regardless of what you think of it. This is also the case over at the perennial WikiProject dispute where community consensus soundly rejected your interpretation, which I bring up to make the point that you appear to have similar misinterpretations of Wikipedia policy in multiple areas. Loki ( talk) 03:59, 10 July 2024 (UTC)
    There's situations where there's only one correct POV. This is one of them. LilianaUwU ( talk / contributions) 19:35, 10 July 2024 (UTC)
    Whatever the criticisms of the body of the closure may be, and there seem to be some, the closure is tainted because the closer did not declare a POV (whether that POV was "correct" or not). Xxanthippe ( talk) 04:42, 13 July 2024 (UTC).
  • Overturn (Option 5, but I would be happy with 2 too). Reading the original discussion, I thought that the accusations about inaccurate reporting of "litter boxes in schools" had been well argued against. In their initial statement, the closer appears not to consider these arguments, but simply labels the Telegraph's statements as misrepresentations. At the least the closer should have addressed these prominent arguments and explained why they did not agree with them. This implies to me an insufficiently in-depth analysis. The closer's revised statement says a little more on this topic, but I was shocked that the decisive step of their reasoning is an obvious non-sequitor: "The 'generally reliable' camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes, which I receive as a concession that the article is misleading." This seems almost flippant; Wikipedia should be able to do better than this in analysing the evidence and arguments. JMCHutchinson ( talk) 10:07, 10 July 2024 (UTC)
  • Endorse and overturn (I did 'participate' in the RFC although I didn't comment on the reliability of the Telegraph in this RFC, but I did comment on a previous RFC that the Telegraph was unreliable on this specific issue). The close that 'there is no consensus on the reliability of the Telegraph on transgender issue' (or WP:MREL), is IMO the correct reading of the discussion (so I endorse it). However, with apologies to an editor I respect, I do think the reasoning in getting there is flawed. The close doesn't engage with all the arguments and rebuttals in the discussion, dissatisfaction with which has lead to this review (not helped with how the RSP was updated). Given this is now the third RFC on the matter in a short space of time, a close that satisfies all involved (even if it doesn't agree with them) is sorely needed. I do wonder if the RSP had simply been updated with the plain "In regards to transgender issues the reliability of The Daily Telegraph is disputed.", without the additional details then we wouldn't be here. -- LCU ActivelyDisinterested « @» ° ∆t° 11:00, 10 July 2024 (UTC)
  • Overturn. I appreciate the sincere attempt on such a divided issue, but I believe that such a contentious non-consensus warranted a more conservative close, both in resolution and in wording.
    As others have noted, the close turned largely on one story, the notorious "cat" drama. That the closer refers to a story that categorically was not a "widely debunked litterbox hoax" in such terms does not inspire confidence that the arguments have been properly weighed. A story featuring elements of otherkin in schools is not automatically a "litterbox hoax". The incident in question happened, and absolutely nobody denies that. The school acknowledged it and reviewed its processes in the aftermath. I wrote out a transcript of the recording here for anyone still for some reason curious about this debacle. I won't rehash the arguments yet again but I don't think any fair weighting of the refutations can support a close describing this as a "debunked litterbox hoax" when there has been no hoax, no litterbox, and no debunking.
    As for the specific wording, as I raised on talk, the closer needlessly inserted the text "and gender critical views" into the closing statement, widening the unreliability notice beyond what was suggested. This was not part of the original RFC, and no evidence was presented either way as to the reliability of The Telegraph for "gender critical views".
    Editors may have personal opinions on how separable "gender critical views" are from trans issues or what the closer even means by "gender critical views", but that is a discussion in an of itself, and one which simply did not take place and whose outcome should not be assumed like this. This unsolicited addition is unwise in an already polarised RFC, and if this is overturned I would suggest a future closer stick to the wording of the RFC only and leave this particular can of worms unopened. Void if removed ( talk) 11:51, 10 July 2024 (UTC)

Support overall close because of what it isn't Overturn....needs another look per my post lower down Folks, let's look at what the structural result of the overall close is, which I think many folks have missed. It is "no consensus on trans issues" and "generally reliable on non-trans issues" I can't see people arguing for a close other than this. The "embrace of the cat story" statement should not be in there but that really doesn't change anything. And it probably needs a shorter more direct summary such as I just gave. If they were an admin, SMarshall would be in the top 5% of admins regarding knowledge and expertise to close this type of thing, so NAC is not an issue except maybe for the optics of it. North8000 ( talk) 18:49, 10 July 2024 (UTC)

Arguing that the close is fine because while it misrepresents the discussion, it gets you the answer you want is ... refreshingly direct, though sadly not unique here. If you can't see people arguing for a close other than this, you might read this comment above. Not to mention many of the other comments supporting overturn. Are we not people? Or can you just not see us? Samuelshraga ( talk) 19:05, 10 July 2024 (UTC)
I encourage you to review the problems many of us have with this close. Similar to how an RfA that (pre-recent-changes to RfA) had a significant early support but was then followed by a “bombshell” that caused a turn of the tide, this discussion was started based on inaccurate representations of the source, which I will assume was not Loki’s intent. This was not called out immediately, and many people !voted while discussion of the initial claims was continuing. But a clear consensus emerged that the initial claims of misinformation were, to put it bluntly, wrong. They claimed the Telegraph said in their own voice things they didn’t, they claimed the Telegraph didn’t retract what other people had said and it merely reported on. And that refutation was widely accepted by a clear majority of editors who posted substantive comments after it was done.
That is why people are believing there was a consensus here - after properly considering how to weight the !votes that were based on the initial inaccurate information, and/or solely based on their personal opinion whether they like the source or not, or of if the source is “biased” or not. -bɜ:ʳkənhɪmez ( User/ say hi!) 20:16, 10 July 2024 (UTC)
@ Samuelshraga: @ Berchanhimez: I'd be happy to take a deeper dive on this and revisit but would like clarity on what I think you are saying that the correct close should have been. Is it that there was (simply) a consensus that they are a generally reliable source? (without the separate wording for trans issues) Sincerely, North8000 ( talk) 20:47, 10 July 2024 (UTC)
My personal reading of it, which I accept is not necessarily in line with what others may read, is that yes - those !voting for option 3/4, and many (but not necessarily most) for option 2, did not care about the veracity of the claims in the initial filing by Loki, and took them at face value. Very few of that group as a whole either provided clear arguments as to why the refutation by Chess and others should be discounted, and many of them admitted that their arguments fell apart once the refutations started coming through. Further, the “turn of the tide” to significantly more option 1 votes, and significantly more (if not all) votes for option 3/4 being based solely on bias or flat out lies, I believe that this all comes together to lead to a consensus that the source is, by our own policies, biased but generally reliable, even on the subject of transgender issues. -bɜ:ʳkənhɪmez ( User/ say hi!) 20:52, 10 July 2024 (UTC)
Ugh, wrong link there, it’s supposed to go to the page about bias of a source not generally affecting its reliability, but mobile. Hopefully you know where I’m talking about, will fix later when I’m home. -bɜ:ʳkənhɪmez ( User/ say hi!) 20:54, 10 July 2024 (UTC)
@ North8000, I'm probably one of the less experienced editors here. I didn't come because I felt I would have been competent to close myself (had I not been involved), but because the close we got was so clearly flawed. That said, I agree with Berchanhimez's reading of the discussion. Samuelshraga ( talk) 21:13, 10 July 2024 (UTC)
So the difference between your thoughts and the close which I supported is that the close said that there was no consensus on trans issues and your thought was that the result was that they are reliable on trans issues. (BTW my sentiment expressed at the RFC was that it should be #1, with #2 also being OK.) I took a harder look. IMO there was a plurality for #1 between #1 and #3 bordering on a consensus and if you include #2 sentiments regarding suitability to use on trans issues (a sort of "sufficiently reliable") then there would be a clear consensus for confirmed usability ("generally reliable") on trans issues. So now I think thhis sould get a second look. North8000 ( talk) 21:32, 10 July 2024 (UTC)
Yes, that was my “rough count” too (remembering that it’s not a vote count). Combine that rough plurality for “reliable but biased” with the fact that the main arguments in favor of unreliability were contested and refuted and many editors agreed with the refutation, there is really no path to “no consensus” here. -bɜ:ʳkənhɪmez ( User/ say hi!) 23:53, 10 July 2024 (UTC)
The analysis that caused me to reverse my position is this: The operative results regarding trans issues were in essence: 1. Prohibit use on trans issues (RFC choice #'s 3 & 4) 2. (RFC choice #'s 1 & 2) Don't prohibit use on trans issues. By this analysis (if arguments roughly follow head count) "don't prohibit" was overwhelmingly favored by a factor of 1.73 to 1.
No, those weren't the options. There were four options, three if you exclude 4 for being essentially impossible to implement. 1 != 2 != 3, and people who voted 2 should not be assumed to support 1. Indeed many of those people explicitly said they were voting 2 because they did not support 1. Loki ( talk) 17:26, 11 July 2024 (UTC)
  • Support close, this is a very tough debate to find any resolution for and I think that S Marshall's decision is a pretty fair and balanced choice. S Marshall highlighted the key aspect of the debate which is a general agreement on the bias of the Telegraph but a disagreement on how much that bias affects the paper's journalistic integrity. Saying that when dealing with the subject of trans people the Telegraph should be used carefully seems like a reasonable precaution. (I voted for option 2 on the basis that reviewing a number of the linked articles showed a fairly strong bias on the topic, my primary concerns being their deliberate misrepresentation and laundering of sources. If I was working on material related to the subject, I would want to cite more neutral and nuanced sources that had clarity and more journalistic integrity.) Gnisacc ( talk) 20:51, 10 July 2024 (UTC)
  • Overturn per JoeJShmo, The Wordsmith, Berchanhimez, Samuelshraga, Teratix, Chess, Void if removed, etc. The close is frankly an inadequate and inaccurate summary of the discussion. Others have already noted multiple issues with the "litterbox hoax" paragraph, which treats one side of a hotly disputed point as fact and proceeds from there. Almost no weight is given to the rebuttals, which disputed not only whether the Telegraph "embraced" the story, but whether the story was an instance of the hoax and whether it even was a hoax at all. I do not believe the original text supports the bizarre claim that these users were "reduced" to arguing that the Telegraph is "allowed to make mistakes". The next paragraph that summarizes the rest of the RfC is equally bizarre. It devotes no attention to the handful of journal articles which were held up multiple times as evidence of the Telegraph’s supposed "unreliability", but in actuality explored only the source’s bias. It highlights a single brief comment one user made about Julie Bindel (whose "platforming" as an opinion columnist would indicate bias, not reliability) but fails to mention more significant points of debate such as the Thoughtful Therapists issue, which was brought up in the RfC's opening statement and rebutted at length by multiple users. And it elides the well-reasoned rebuttals by simply saying that "there was discussion", while neglecting to evaluate the relative merits of those discussions. I do not have confidence that the close properly engaged with the strengths and weaknesses of the arguments being made on both sides. Rather, the close seems to treat the fact that the source's reliability was vociferously disputed as justification enough. Astaire ( talk) 21:59, 10 July 2024 (UTC)
  • Endorse - The close was a reasonable read of the discussion and came to a very narrow decision. All of the arguments for overturning focus entirely on process wonkery & nitpicking word choice in order to try and unravel the close by tugging on a loose thread. — The Hand That Feeds You: Bite 16:53, 11 July 2024 (UTC)
    I brought this here because the closer refused to amend his egregious word choice on his user talk page and insisted that he came to it after weighing all arguments. Aaron Liu ( talk) 03:19, 12 July 2024 (UTC)
    "egregious," please, let's not be hyperbolic. — The Hand That Feeds You: Bite 19:57, 12 July 2024 (UTC)
    Okay, so you think that unashamed embrace of the widely-debunked [conspiracy theory] in place of saying A teacher at Rye College, a state secondary in East Sussex, was recorded telling a pupil who refused to accept her classmate was a cat that she was despicable., of which all they got wrong was that the cat was a rhetorical device, the latter being consensus, is a mostly fair and accurate representation of the discussion. I do not see how one could arrive at that conclusion. Aaron Liu ( talk) 22:08, 12 July 2024 (UTC)
  • Endorse. Look, I'm not going to lose sleep over some minor changes to the wording per the OP's concerns, if that's the ultimate result here, but for my part, I think this was a mostly reasonable summary of the results of the discussion. Did I feel there was a bit of unnecessary color commentary with pointed observations about the source frame as objective facts? Yeah, I did get some twinges about that while reading the close, and I think it's worth S Marshal taking that into consideration in the future. But I rather suspect that, rather than this being a case of the closer trying to interject unnecessary personal perspective into the result, it was a conscious rhetorical method for acknowledging the understandable and unavoidable emotional subtext of the dispute. I get the feeling that S Marshal recognized that there was really only one way to close this discussion under existing policy and consensus of the discussion itself, but was uncomfortable doing so without paying some recognition to the circumstances under which some editors have come to dislike the source. So he called the spade for the spade in a way that would make the Telegraph skeptics at least marginally less likely to feel that their sentiments had been dismissed wholesale.
    But any caveats not withstanding, I think S Marshal did an adequate job with this close, given the complexity of the issues and the highly divisive nature of the discussion. Personally I would have been marginally more supportive of a straight "no consensus" result as opposed to "reliability disputed", but this a fraught area, and we have to start finding a way to come together on these issues (or at least reigning in the constant relitigation of habitual issues. In that light, I think we could have gotten a lot worse here. I understand the quibbles, and I came close to casting a different !vote here, but considering all factors, I don't think S Marshal's something-for-everyone approach here was arbitrary, unintentional, or ill-advised.
    Further, I think there's more to be gained by just embracing an overall reasonable close than by micromanaging every last sentence into a form that is most pleasing to the majority, even if I was a part of that majority and even if I feel that the result would be more ideal. For the benefit of procedural efficiency and community harmony, I think we need to start leaning back towards the traditional tendency of just letting the initial close stay, warts and all, so long as it does not obviously and massively misrepresent the actual consensus. I don't love every syllable of S Marshal's close, but I still think that it was a well-executed one made under difficult circumstances, in the final analysis, and I don't blame him for trying to pay some lip service to the concerns of the minority. SnowRise let's rap 19:40, 11 July 2024 (UTC)
  • Endorse: I don't want to spend too long saying things which have already been said, but I know in recent discussions and here some users have opined that anyone saying ~"I'd just be using the same rationale as X, let me just say 'per X'" should be discounted and people should be required to be repetitive, so with apologies to whichever panel of three admins has to close this discussion (to avoid it being challenged) for making it longer ¯\_(ツ)_/¯ : both the "involved" argument and the argument that the close was a supervote are unconvincing. The "involvement" is not only tangential (as amply discussed above), but in the other direction, so unless the implication is that another closer would've found outright consensus that the source was unreliable(?), the argument doesn't make sense. In turn, as many users have noted above, while closing this as either "option 1 because I know option 2 voters really meant option 1" or "option 3 because I know option 2 voters really meant option 3" (as some people want) would've been a supervote, "there was no consensus →means→ close as no consensus" is just reading the arguments (and "no consensus →means→ no consensus" is just following WP:MREL).
    It is unsurprising that much discussion here is relitigating the same points as the RFC, as if saying "actually they were never wrong, it was proven they were never wrong, by me saying they weren't wrong" several more times will make it true. Indeed, re the suggestions below about ways to align how closes should occur and be reacted to vs how closes are actually reacted to, and the issues with those suggestions (e.g.: mandating multiple people volunteer to find time to close discussions would mean discussions go unclosed for even longer, potentially until stale, wasting/filibustering the effort), the other obvious possibility is to write down in the guidelines that all closures are only "prospective, non-finalized" closures until sustained by an AN discussion where the participants relitigate positions a second time: while I'm not sure that would be the best option, it seems like it could be the easiest one to get people on board with because it's how we see many people already operate... -sche ( talk) 02:42, 12 July 2024 (UTC)
    If you say "per X" and X's original claims have been proven inaccurate/misleading, and you don't address that fact, then your !vote will be downweighted accordingly - just as the initial claims should be downweighted when a refutation that enjoys broad support from those actually discussing the topic (rather than drive by !voting) would. -bɜ:ʳkənhɪmez ( User/ say hi!) 00:38, 13 July 2024 (UTC)
  • Endorse close - As has now become clear after further discussion here, while some people had issue with some of the wording of the close, the ultimate outcome of it being a "no consensus" seems to be agreed upon here and is a good reading of the original discussion, since there simply was no consensus on the topic, so the close to no consensus and marking it MREL for transgender issues is the appropriate outcome. Raladic ( talk) 15:51, 12 July 2024 (UTC)
  • At least amend the third and fourth paragraphs to reflect the actual consensus. In cases where there are comparable numbers of good-faith !votes, finding in favor of either of them (or splitting the difference) should necessitate a close summary mentioning why a given argument did not prevail. The close should summarize the reasoning of any significant minority/non-plurality, but should also make it clear what the major arguments against that reasoning were and how they were weighted. In cases where the closer finds consensus that does not align with a non-trivial majority of good-faith !votes, it is particularly imperative they explain why arguments in the majority camp were downweighted.
    In this close, only a rationale of Option 3 !voters is presented at any length, and it is implied there was consensus agreement with this rationale. However, the close does not address the various refutations of that rationale that, necessarily, were strong and numerous enough to result in Option 3 not gaining consensus. This is especially problematic given that there was a solid majority against Option3/4. Even if we count every "Option 1/2" !vote toward Option 2 and count every "Option 2/3" and "Option 4" !vote towards Option 3, we still have roughly 60 Option 1 to 49 Option 3 (and ~16 Option 2). A more charitable accounting (for example, assigning any "Option 1 or maybe 2" !votes, like my own, to "Option 1") yields a more lopsided result, and splitting the options into 1/2 vs 3/4 reveals something approaching a 60% supermajority ~75 1/2 to 49 3/4 (and that's still counting all "2/3" !votes toward Option 3). Any finding against Option 1 should thus expand on why this wasn't enough for consensus (which could be perfectly reasonable if the strength of the !votes just wasn't there--but that still should be explained!), meanwhile any finding for Option 3 would absolutely need to demonstrate a very substantial imbalance in argument strength. JoelleJay ( talk) 00:50, 13 July 2024 (UTC)
    I agree that there was not consensus for Option 3, but the closer did not claim there was. Meanwhile, you've missed the obvious reason why there wasn't consensus for Option 1: by your own count, there were 60 Option 1 voters but 65 voters who were against it. Since there wasn't a consensus for any option, there was no consensus, which has special meaning at WP:RSP and isn't just "status quo wins". Loki ( talk) 05:27, 13 July 2024 (UTC)
    I’m interested, since you seem to want to vote count, for you to do a few things. First, split the proportion up into “before the refutation” and “after the refutation” to examine how the discussion evolved over time. Second, count up how many of the 65 votes on the “against it” side were based solely on bias, or did not address the refutation of the claims at all. Thirdly, count up how many people agreed with the refutation after it was posted versus disagreed - without assuming what anyone who didn’t comment directly on why would’ve said.
    If you do this, rather than trying to shoehorn the vote count to your favor, you will see why many people are arguing there actually was a consensus present. -bɜ:ʳkənhɪmez ( User/ say hi!) 06:19, 13 July 2024 (UTC)
    What "refutation"?
    Also, obviously all the things you are saying are simply not how closing discussions works. The closer can evaluate the arguments but they are under no obligation to pretend that an argument that you happened to find particularly convincing was objectively strong. Loki ( talk) 19:25, 13 July 2024 (UTC)
    Closers are expected to determine consensus based on the quality of the arguments given on the various sides of an issue, as viewed through the lens of Wikipedia policy.
    In this context, a good close will need to give little to no weight to !votes that argued the Telegraph endorsed the litter boxes in schools hoax (as this was disproved by the articles provided in support of it, and thus is not a quality argument), and little to no weight to !votes that argued that it should be considered unreliable on grounds of bias (as this is contradicted by policy). BilledMammal ( talk) 19:32, 13 July 2024 (UTC)
    Whether or not it "was disproved" is a matter for the closer to decide. The closer decided it was not disproved. All you are saying is that you disagree with the closer. Loki ( talk) 22:44, 13 July 2024 (UTC)
    This case is unusually clear cut. You said "this source endorses this hoax", and provided an article where the source said "this is a hoax". It is not possible for a reasonable close to say that it was not disproved. BilledMammal ( talk) 00:03, 14 July 2024 (UTC)
    If I say that a source endorses the conspiracy theory that the moon landings were faked, and the source says "There's a common conspiracy theory that the moon landings were faked, which is not true. However, look at this evidence that the 1969 moon landing was filmed on a sound stage in California.", is that or is that not "endorsing the conspiracy theory"? Loki ( talk) 00:12, 14 July 2024 (UTC)
    Obviously not. It's called presenting all sides of a story. Otherwise, we'd only hear half the story. You may think that hoaxes are never newsworthy - what would the news report on if not saying "it's a hoax, but look at the evidence that the other side uses to try and convince you it's not a hoax"? -bɜ:ʳkənhɪmez ( User/ say hi!) 00:15, 14 July 2024 (UTC)
    It could, depending on the specifics. However, it's a false equivalence.
    What the Telegraph said after calling it a hoax was say that people do identify as animals. This is true, and nobody in the RfC claimed otherwise. BilledMammal ( talk) 00:24, 14 July 2024 (UTC)
    Ah, but they said this specific student identified as an animal at this specific school with the support of the administration, all of which is false and which fulfills all the pillars of the hoax except for the literal litter boxes. Loki ( talk) 01:27, 14 July 2024 (UTC)
    Everyone, regardless of your views regarding this, it is clear that (maybe a little less than) half of the RfC participants agreed with Chess's refutation against that incident being an endorsement of the litterbox hoax. Let's accept that and move on without directly arguing the RfC again. Aaron Liu ( talk) 02:09, 14 July 2024 (UTC)
    ( edit conflict) The issue is you proved none of that:
    • they said this specific student identified as an animal - based on your mistaken understanding of presuppositions
    • with the support of the administration - based on your definition of "support" (which you extend to "calling students despicable" - in other words "telling students off for bullying")
    • all of which is false - The school said one thing, parents said another, and the Ofsted report declined to comment
    • fulfills all the pillars of the hoax - based on your definition of the pillars
    For a closer to say that your close was not disproved they would need to say that every one of these four claims was true. No reasonable close can do that. Aaron Liu does make a good point, and so I will step back from this discussion now, but I felt it was important to make this point clear. BilledMammal ( talk) 02:12, 14 July 2024 (UTC)
    I agree that no reasonable person who reviews all the facts could conclude Loki's claimd (there's a freakin' TAPE RECORDING OF THE TEACHER calling the girl "dispicable" for not accepting a cat identity, FFS! How much more evidence is needed here?!).
    I suppose the real question here is, what happens when a large MINORITY of Wikipe#ians all assert something that is objectively false, in lock step with each other? (Which does not have to be in bad faith, and I do not say that it is, here). I'm not sure the mechanisms exist to deal with this effectively, which is a dangerous precedent, and expect more of it, and not only on this topic from this POV, either. 73.2.86.132 ( talk) 04:16, 14 July 2024 (UTC)
    It was later clarified that the recorder brought up the scenario of a student identifying as a cat for her rhetorical devices.
    If that happens, the WMF and checkusers first see if sockpuppetry or states are involved. If not, then we simply assert that "something" is true, since the scenario of them all being wrong at that specific time is unlikely and we have WP:NOTTRUTH. Aaron Liu ( talk) 14:28, 14 July 2024 (UTC)
    I think if you really wanted to step back you wouldn't have insisted on getting the last word, but regardless I think that this argument is going in circles enough that I'm not even bothering to read your comment fully. Loki ( talk) 04:28, 14 July 2024 (UTC)
  • Overturn per @ JoeJShmo—and maybe we need some language in policy discouraging NACs on RfC’s of certain length or impact. Zanahary 04:32, 14 July 2024 (UTC)
    This should be posted in the Participants section. Parabolist ( talk) 18:41, 14 July 2024 (UTC)
    @ Parabolist: WP:Be bold. I've moved it to the correct place. Aaron Liu ( talk) 20:54, 14 July 2024 (UTC)

Discussion

  • @ Aaron Liu: If you are only concerned with amending that sentence, do you mind withdrawing this request so that those of us are who are concerned with the close more broadly can submit? The issue is that it makes it difficult to focus on the broader issues if you start the discussion with a narrow scope, while the opposite is less true. BilledMammal ( talk) 05:21, 9 July 2024 (UTC)
    If we really need multiple requests, then maybe those could be in parallel? I feel like we could do all of them here and hopefully find "express" consensus for that sentence while the rest of the discussion continues.
    Unfortunately I'm ill-equipped to discuss this out right now as I have to go to sleep, sorry. I sure have planned my day well. Aaron Liu ( talk) 05:25, 9 July 2024 (UTC)
    I've attempted to make it parallel as you propose; if you feel that isn't an appropriate way to handle it, please move my comment. I've also renamed the sections "participant", "non-participant", and "closer". BilledMammal ( talk) — Preceding undated comment added 05:57, 09 July 2024 (UTC)
    The original sections were how {{ RfC closure review}} prefilled it. Aaron Liu ( talk) 12:41, 9 July 2024 (UTC)
    A close review can and should result in discussion of all the issues present, as I've done in my comment above. Ultimately, the one issue Aaron Liu identified should be grounds enough to overturn this close, as it amounts to a supervote, but I doubt this is going to be closed quickly and you (BilledMammall) should feel free to identify your issues in your !vote for people to consider. -bɜ:ʳkənhɪmez ( User/ say hi!) 05:29, 9 July 2024 (UTC)
  • @ Aaron Liu: you wrote a couple of times in your reasoning that you want amendment to the first paragraph with reference to the litterbox claim. Just wanted to nitpick that it actually appears in the third paragraph, if you want to edit for us pernickety types. Samuelshraga ( talk) 06:56, 9 July 2024 (UTC)
    By first paragraph, I meant the first paragraph of my statement. It seems that this has been... misrepresented! I'll fix that soon. Aaron Liu ( talk) 12:41, 9 July 2024 (UTC)
  • @ BilledMammal: You commented 44 times in the original RfC; now you've opened this close review and you are already badgering people here, seven replies in a few hours. It's wearysome. Black Kite (talk) 11:58, 9 July 2024 (UTC)
    I didn’t open this, and I’ve commented less than other editors involved here - I don’t think my participation has been unreasonable, although if you disagree I encourage you to raise the issue on my talk page as this is the wrong location for that discussion and I won’t reply further on that topic here. BilledMammal ( talk) 12:02, 9 July 2024 (UTC)
    The threading makes it look as though yourself and AaronLiu opened the close review together. If that's not the case, then perhaps your long section should be under a separate Level 3 subheading. Black Kite (talk) 12:44, 9 July 2024 (UTC)
    To simplify the maybe-confusing structure of this, I think claiming that we both opened it would be for the best, as with retaining the current formatting of rationales. Aaron Liu ( talk) 12:47, 9 July 2024 (UTC)
  • Comment As a close review I think we need to focus on the mechanics of the close. An editor who endorses or rejects the close because they agree with the outcome doesn't add weight to the discussion. Specific concerns were raised with the closing. Endorse responses that address the concerns with reason should be given weight in these discussions. Responses that simply endorse (or reject) the outcome without addressing the concerns raised should be discounted. This is like a legal appeal where we aren't arguing the case, rather we are arguing that the process was or wasn't followed (with supporting evidence). I feel this is a standard that should apply to all close reviews which often seem to devolve into a second round of litigating the original question. Springee ( talk) 12:27, 9 July 2024 (UTC)
  • Just a comment for non-British editors who might not know: The Daily Telegraph is one of the most prominent newspapers in a country where a large proportion of the population still read newspapers. I think you'd struggle to find an adult British person who doesn't have some sort of opinion on it, even if it's just "as absorbent as the rest of them, in a pinch." If the contention is that nobody with an opinion on the Torygraph (damn, there's me out) should have closed this discussion, you're likely disqualifying all British editors. Kind of like saying that an RfC on Fox News couldn't be closed by an American. Which may be fine, I just thought I'd mention it. –  Joe ( talk) 14:05, 9 July 2024 (UTC)
    As a Brit, I can confirm this sentiment. This is also true of The Guardian, The Independent and The Times. We have a small selection of notable left-leaning and right-leaning broadsheets, and most Britons have an opinion on them. This is potentially similar to WaPo and NYT that are widely known, as I assume most Americans have an opinion on these either way as well. CNC ( talk) 14:15, 9 July 2024 (UTC)
    I assume that most Americans have never heard of, or would not recognize, the majority of British newspapers. I would even wager that more would confuse The Times with The New York Times than would know what The Daily Telegraph is. — Red-tailed hawk  (nest) 14:19, 9 July 2024 (UTC)
    Precisely. The point was that S Marshall is from the UK (maybe that wasn't obvious), so naturally they would have some sort of opinion on The Telegraph without necessarily being bias. The "as well" was in reference to the overall comparison, not Americans knowing British newspapers. There's a rationale for having non-British editors close this one. CNC ( talk) 14:25, 9 July 2024 (UTC)
    I don't think that (non-)Britishness is required here; it isn't reasonable for us to ask people to not close something on the basis of nationality. Instead, As WP:INVOLVED reminds us, people are at times incapable of making objective decisions in disputes to which they have been a party or about which they have strong feelings. When one is able to put their feelings aside and objectively read a discussion, this is less of a problem, but having strong opinions to such an extent that one's ability to faithfully summarize a discussion become colo(u)red by them is incompatible with our expectations for a closer. — Red-tailed hawk  (nest) 14:31, 9 July 2024 (UTC)
    But nobody has demonstrated that Smarshall does have such strong opinions. Thryduulf ( talk) 14:35, 9 July 2024 (UTC)
    I've admitted in this discussion to having strong opinions about some of the Daily Telegraph's political columnists. Fact is, the Telegraph gives platforms to people who want to privatize the NHS and bring back the death penalty, and I find that abhorrent. I don't (and still don't) have a personal opinion about the Telegraph's view on transgender people, and I deny that gender and politics are the same thing.— S Marshall  T/ C 15:09, 9 July 2024 (UTC)
  • Just thought I'd point out that the (now-reverted) new entry on RSP has already been used to justify content removal with unwarranted stridency: [16]. Barnards.tar.gz ( talk) 15:14, 9 July 2024 (UTC)
    I mean, yes? WP:MREL is not WP:GREL. Almost everyone in the RFC including the vast majority of Option 1 voters agreed that the Telegraph is biased, which would mean that citing them without attribution is inappropriate. So I don't know what your point is here. Loki ( talk) 16:39, 9 July 2024 (UTC)
    There was WP:INTEXT: "The organisation has said". Based on attribution, it's not necessary to state the source if you are stating the author(s) of the claim. Overall, kind of a moot point when it's not due in the lead anyway. CNC ( talk) 16:48, 9 July 2024 (UTC)
    I agree the text was undue, and I have removed it. The point of mentioning it here was that the wording of the RSP entry was being used to support strident assertions about reliability that were in no way reflective of the much more circumspect discussion. If that's what people take away from all this, the process has failed. Barnards.tar.gz ( talk) 17:06, 9 July 2024 (UTC)
    While I see your point, the misinterpretation of source reliability listed at RSP isn't exclusive to that entry (as you may well agree). The RfC itself was also used a source, which is merely what the RSP entry was summarising. It's fair to say that misinterpretation of MREL sources is widespread, and this example just provides more weight to that argument. CNC ( talk) 17:36, 9 July 2024 (UTC)
    I think what's notable is that it took a mere 2 hours from the update to Perennial Sources to an edit war breaking out, and this does not lend to an interpretation of "no consensus" that favoured stability. Void if removed ( talk) 18:19, 9 July 2024 (UTC)
    I agree to a degree, but also don't think any GREL to MREL change ever intends to favour stability, or necessarily makes things unstable. Personally I think we should favour reliability of sources over stability, meaning context-based rationales in this case. I don't believe editors misinterpretation of MREL is a good reason to change the status quo though; the cause of the problem is a lack of understanding, the edit warring is just a symptom of that. CNC ( talk) 18:32, 9 July 2024 (UTC)
    The issue is how RSP works; its very subjective how we assess sources, and that means that the interpretation of our assessments is also very subjective. I think we should rework the process, but that's a different discussion. BilledMammal ( talk) 18:46, 9 July 2024 (UTC)
    Given that the party employing that rationale was WP:INVOLVED in this RFC and voted 3/ WP:GUNREL, I wonder: if you don't understand what it is you're voting for, is the vote valid? Void if removed ( talk) 18:58, 9 July 2024 (UTC)
    Yellow doesn't mean attribution is required nor does it mean Green source beats Yellow source. Instead it means we need to use caution when deciding if the material is being given undue weight by the source in question (which can effect how much weight it should be given on Wikipedia). It also means we shouldn't take interpretations as always correct. However, it doesn't mean we should question basic facts taken from the source. If they say 500 people attended or the topics were X, we should assume they are correct. This by the way is a general issue issue with RSP's buckets, not specific to this topic. Springee ( talk) 17:15, 9 July 2024 (UTC)
    WP:MREL is questionable as it stands because it is unable to distinguish "no consensus on whether a source should be used" from "consensus that it's unclear when a source is used". Chess ( talk) (please mention me on reply) 00:31, 10 July 2024 (UTC)
    What is the practical difference between them? Thryduulf ( talk) 00:49, 10 July 2024 (UTC)
    @ Thryduulf: None, right now. That's the problem, since WP:MREL is seen as "unreliable with exceptions" in practice. Editors !voting "Option 2" can win by default simply by preventing a consensus from emerging. Chess ( talk) (please mention me on reply) 02:53, 10 July 2024 (UTC)
    Well, why would that be harmful? If numbers are filtered and weighed into a close, I don't see what's wrong with that. Aaron Liu ( talk) 04:20, 10 July 2024 (UTC)
    If there is no consensus, why is it harmful for RSP to state that there is no consensus? If there is no difference in practice between between "no consensus for general reliability or general unreliability therefore it's medium reliability" and "consensus that it's medium reliability", why is not distinguishing between the two harmful? Thryduulf ( talk) 09:26, 10 July 2024 (UTC)
  • Are RfC participants supposed to reply in the Non-participants section, or should they keep comments in their own section and/or §Discussion? Firefangledfeathers ( talk / contribs) 16:51, 9 July 2024 (UTC)
    I’ve never seen a close appeal where it doesn’t happen, so I assume they are allowed to. BilledMammal ( talk) 16:57, 9 July 2024 (UTC)
    In fact, I haven't seen any close review with the headings format of the {{ RfC closure review}} template, lol. Aaron Liu ( talk) 18:20, 9 July 2024 (UTC)
    I have no objection to participants replying in the non-participants section. I think the goal of the headings is to group the top level comments together, which is accomplished even if those top level comments are getting replied to. – Novem Linguae ( talk) 07:15, 11 July 2024 (UTC)
  • As expected, people are already using this outcome to try to shift the balance of articles, and are also angling to go down the slippery slope and get other UK news media also declared unreliable on this issue, so that ultimately only one side of this active political debate can be covered as mainstream and non-fringe. *Dan T.* ( talk) 18:08, 9 July 2024 (UTC)
    That's completely irrelevant to the close. Thryduulf ( talk) 18:29, 9 July 2024 (UTC)
    Not entirely. That this was the motivation of certain editors on the RfC and the expected result of a non- WP:GREL close was brought up in the discussion. The fact that the closer ignored this in their close (and that it immediately turned out to be spot on) is yet another demonstration that the closer didn't do a very good job of weighing arguments. If they did, they certainly didn't show their working. Samuelshraga ( talk) 19:00, 9 July 2024 (UTC)
  • Editors are putting a lot of thought into closer's arguments about whether a "No consensus" finding on the RfC moves the Telegraph into WP:MREL or preserves the status quo. I think this discussion is premature, given that the closer has given next to no justification for a "No consensus" close - they explicitly disavow that it depends on the (misrepresented) summary of the litterbox hoax discussion in the close, and in their expanded close their only argument is a count of votes ( which they also explicitly disavow on their talk).
First we can determine whether we have a valid close - and if not we vacate and somebody else can close by weighing the arguments. Maybe they too will conclude "No consensus". Then the discussion of what exactly that means will be ripe. Samuelshraga ( talk) 18:55, 9 July 2024 (UTC)
There is no discussion needed about what a no-consensus close means - it's explicitly defined at WP:RSP (that wouldn't make sense if the lack of consensus was only between options 3 and 4, but that's unarguably not relevant to this discussion). Thryduulf ( talk) 19:03, 9 July 2024 (UTC)
Wonderful. I very clearly said that I don't think we should have that discussion now, and the first issue at hand is whether the close itself, meaning the judgement of "No consensus" and the reasoning given (or not given) for it should stand. Afterwards we can discuss, or not discuss, whether further discussions are or aren't needed on any topic that becomes germane. Samuelshraga ( talk) 19:06, 9 July 2024 (UTC)
I've requested clarity below due to the popular argument of "no consensus = no change". It seems pretty clear that this is a discussion that needs to take place, based on support for this proposal. CNC ( talk) 19:10, 9 July 2024 (UTC)
@ CommunityNotesContributor I understand that. However I think that relevant points unrelated to the "no consensus = no change" debate have been raised, and call into question the validity of the "no consensus" finding itself. This seems to me to be a logically prior discussion that could potentially make the "no consensus = no change" discussion moot. Samuelshraga ( talk) 19:14, 9 July 2024 (UTC)
Granted, and if anything it's intended to draw these arguments out of this discussion and instead clarified below. Even with the RfC overturned, in the meantime, there is a valid discussion of whether this RfC should be exempt from the RSP status quo, or whether there needs to be a more thorough discussion on reviewing how RSP lists sources. Given this discussion has already surfaced, I see no reason why it wouldn't surface again regarding another NC close. CNC ( talk) 19:22, 9 July 2024 (UTC)
True. I just don't want the discussion about this close - especially the arguments about it's basic failure to in any way weigh the arguments from the discussion - to get lost in the procedural discussion in what to do if the NC close is upheld. Of course that's more complicated because some people have now supported Overturn referencing closer's positions on what the outcome of NC is... and anyway now we're in a discussion about discussions about discussions.
Hopefully people coming to this review will still put appropriate weight on those who point out that the close is a supervote, that it doesn't weigh arguments, that it counts votes, and other failings, notwithstanding that more and more of the discussion is about the "NC = change or no change" issue. Samuelshraga ( talk) 19:31, 9 July 2024 (UTC)

A lot of the comments here seem to be implying that partially overturning by amending language isn’t an option? Can we at least obtain consensus that the language I mention should be amended? Aaron Liu ( talk) 21:06, 9 July 2024 (UTC)

I don't object to removing the language you want amended. I just think this is very secondary to the much more serious problem. There is no argument here that the close weighed the sides of the discussion in any way. Some people endorsing the close have asserted that it was reasoned, but they haven't elaborated on its reasons. Samuelshraga ( talk) 05:19, 10 July 2024 (UTC)
I was talking about many of the endorse !votes. Aaron Liu ( talk) 15:47, 10 July 2024 (UTC)
Personally, I think at minimum the removal of "and gender critical views" from the note, else what's the point in having a per topic discussion if a closer can unilaterally widen it?
For example, this is a story in The Telegraph about a social worker who won an employment tribunal on the grounds of her gender-critical views. There seems to be no exaggeration or inaccuracy. It also does not mention the word "trans" at all. It is entirely a story about the legal protection of those views, and the discriminatory acts of the council and regulatory body. It is a notable legal case (ie, the first time a regulatory body has been found to have committed unlawful discrimination) and as such not given undue prominence.
As written, this would come under the purview of this note, because the note has been expanded beyond anything discussed in the RFC. Why? Void if removed ( talk) 08:29, 12 July 2024 (UTC)
Without commenting on whether is should come under the close, a single accurate story (assuming it is, I haven't looked) is not at all incompatible with a finding of MREL or even GUNREL. Neither category is saying that all stories (in the relevant topic area) are inaccurate, heck even the Daily Mail gets things right at times. At the most basic level GUNREL means they are generally unreliable, MREL means they are sometimes unreliable - often enough that they are not generally reliable but not often enough that they are generally unreliable. In the same way generally reliable doesn't mean infallible. Thryduulf ( talk) 08:48, 12 July 2024 (UTC)
The point is that this is a story that is not a "trans issue", it is a "gender critical views" issue. The RFC was "unreliable on trans issues". If people wanted this to be part of the RFC, it should have been part of the RFC. Adding it in in the close without it being raised in the RFC and with no discussion is a WP:SUPERVOTE. Void if removed ( talk) 09:31, 12 July 2024 (UTC)
That is nonsense, Gender critical, or its original non-whitewashed term TERF, which even has it in the name, is a trans issue and whether specifically called out or not, it's implicitly covered under the topic.
There is no change in scope, so the accusation of a supervote for this is arbitrary, but simply WP:COMPETENCY is assumed on an obviously linked subtopic that the closer simply chose to call out. Raladic ( talk) 15:45, 12 July 2024 (UTC)
And all of that is of course extensively disputed (including the crack about "whitewashed") and none of this was discussed in the RFC, and your framing of the issues in this particular POV exemplifies the problem with closing in this way. ("call out"? is that the role of closer?).
To make this clear, consider a hypothetical RFC brought claiming that "Pink News is unreliable on gender-critical views", which plays out as a mirror opposite of the Telegraph one.
Ie, where the Telegraph is claimed to present trans issues in a biased and misleading way, and overly focuses on trans people in a negative light, inflating non-stories into breathless ragebait, the inverse claim is made that Pink News behaves the same about people with "gender critical views". Lets say that the arguments all play out exactly the same, in the same proportions and a closer decides it is a no-consensus result.
Do you think it would be defensible to say that the reliability of Pink News was therefore disputed on "gender-critical views and trans issues"?
These are distinct subjects with some overlap, and with a huge amount of conflict where they meet and even what terms mean, but here the POV of the closer has widened the scope of the close beyond the question that was asked. Void if removed ( talk) 15:54, 12 July 2024 (UTC)
Just simply no, it is consensus on Wikipedia (and as such the wider world, since we simply summarize the RS) that Gender critical views are a subtopic of transgender issues, as is very clear from the lead of Gender critical, so there is simply no leap here.
There is also no crack about whitewashing, again, we discuss this in Gender-critical feminism#Terminology, so I simply re-stated the consensus on Wikipedia on the issue.
Picking on words that were included in the close doesn't change the fact. Raladic ( talk) 16:00, 12 July 2024 (UTC)
But WP:NOTSOURCE so, no. And given these are exactly the arguments the closer has presumed the conclusion to, based on no evidence, and the many, many protracted discussions on talk there, it would be much simpler not to have needlessly expanded the close to include this completely undiscussed POV, for no good reason. Void if removed ( talk) 16:21, 12 July 2024 (UTC)
I believe that this is much less damaging than "unashamed embrace of the widely-debunked Litter boxes in schools hoax". Aaron Liu ( talk) 15:34, 12 July 2024 (UTC)

Request for clarity

Part 1

To those of you who say "Overturn" -- overturn to what? Please be clearer. It would help if you distinguished between:

  1. Overturn to a consensus. Please specify what consensus you see.
  2. Overturn to no consensus, defaulting to no change. This means you feel that WP:RSP should still say "generally reliable".
  3. Overturn to no consensus, defaulting to a change, but not the change that I specified in my close.
  4. Overturn to no consensus, defaulting to the change that I specified in my close, but change the summary of the discussion.
  5. Overturn by reverting the close, leaving someone else to close with no guidance from the community on how.

Thank you.— S Marshall  T/ C 15:17, 9 July 2024 (UTC)

I haven't read enough of the relevant policies to have an opinion on the Wikipedia:ONUS questions behind option 2-3. My sympathy is to 1, as I think the Wikipedia:GREL choice got the better side of the argument once @ Chess stepped in, and I saw many other editors thought the same, but I'm not nearly experienced enough in these to attempt to judge a consensus myself. So by default I will go to Option 5, because as I have argued here - the only reason you gave (and you only gave it in your expanded close) for giving weight to the view that the Telegraph was unreliable was this view is strongly disputed by significant numbers, but you told me on your talk page that the point is not to count votes, and I didn't, but to weigh arguments, which I did. There is no evidence of argument-weighing, and the close was not remotely a reasonable reading of the discussion, so the policy questions relied on to implement its outcome don't need to be addressed in my opinion. Samuelshraga ( talk) 15:29, 9 July 2024 (UTC)
Overturn to allow someone who intends to actually address the problems with your close to re-close the discussion with the consensus (or lack thereof) they find after doing so. If a closer actually weights arguments appropriately and explains how their close takes into account that, aside from the “it’s biased” and “I don’t like it” !voters, the majority was solidly swayed by the refutations of the initial discussion, then that close will be sufficient. -bɜ:ʳkənhɪmez ( User/ say hi!) 15:53, 9 July 2024 (UTC)
aside from the “it’s biased” and “I don’t like it” !voters, the majority was solidly swayed by the refutations of the initial discussion I think you must be reading a different discussion to me. Many people were swayed, to a greater or lesser extent, by some or all of the refutations. Many people were not. Even if you discount all of the "it's biased" comments (many of which were actually more complex than that and accompanied !votes of all options) calling that "a majority was solidly swayed" is a misleading oversimplification. Thryduulf ( talk) 16:12, 9 July 2024 (UTC)
When the refutations were based on the actual text, and nobody was able to actually present cognizant and clear refutation of the refutation, it does matter. Anyone !voting based on “I disagree with the refutation, even though it’s English language facts and provides the exact text of the article to support it, but I can’t say why I disagree” should have that opinion decreased in weight accordingly. Otherwise, those commenting early in a discussion have absolutely no reason to continue in the discussion to form a consensus - since their opinion, no matter how badly it’s proven wrong, will still count just as much.
If someone is proven to have based their opinion on inaccurate/misleading information, as many people commenting both before and after the refutation did, and they refuse to clarify/update to explain their opinion in light of new information, their opinion must be weighted accordingly. And that is what happened here, with people - including the closer himself - subscribing to an outright falsehood that the Telegraph said something that they didn’t, and nobody could ever provide proof that they did. If people are allowed to “win” discussions by blatantly lying and not providing proof just because enough people agree with that lie in furtherance of their political goals, then this is no longer an encyclopedia, but a propaganda machine.
The new close needs to take into account the fact that many (to use your preferred word) !votes for unreliability were based on falsehoods, that many more were based on not liking it, and that many more were based solely on bias in combination with these other things. And this goes for both sides - but the unreliable camp had significantly more !votes that were inaccurate at best. -bɜ:ʳkənhɪmez ( User/ say hi!) 19:08, 9 July 2024 (UTC)
  • Option 2, as I stated above. You closed as no consensus but then inserted your own opinion on what should happen instead of just leaving the status quo in place. Cheers  —  Amakuru ( talk) 16:20, 9 July 2024 (UTC)
    Your opinion regarding Option 2 is appreciated below in Part 2. CNC ( talk) 19:05, 9 July 2024 (UTC)
  • Option 5, since I thought the close rationale was flawed. starship .paint ( RUN) 16:29, 9 July 2024 (UTC)
  • If the close is reverted, then it should be reclosed by someone else based on their reading of the arguments presented in the discussion, taking into account any relevant comments here. So sort of option 5 but not exactly. Thryduulf ( talk) 16:29, 9 July 2024 (UTC)
  • Option 5. – Tera tix 16:33, 9 July 2024 (UTC)
Option 3/4 The result of no consensus can't be ignored by RSP as the status quo of RSP is to categorise sources (or topics by sources) with the relevant consensus established or lack of. The Telegraph can't be used as an example of "there was no consensus so there is no change", as this would have broader implications on other sources listed at RSP; Fox News and HuffPost (politics) come to mind as examples of GREL turned NC, but I imagine there are many others that were GREL by default prior to NC. It's unclear whether editors believe we should be making an exception for The Telegraph, or whether the proposal is to re-format how RSP categorises source discussions. If it's the latter, this requires a broader RfC on how RSP categorises sources and has little to do with this RfC. CNC ( talk) 16:34, 9 July 2024 (UTC)
Given that this section was opened as a way of disambiguating the intentions of people who support Overturn, I think it's a little unhelpful to have people who endorse the close choosing options as well (not that I think your arguments are unwelcome at all - I already said that I don't as yet feel confident or experienced to get involved on this issue and what you write seems cogent, even if it prejudges the idea that "No consensus" close will be retained). Samuelshraga ( talk) 19:10, 9 July 2024 (UTC)
That's a very good point and had overlooked that, apologies. I've struck my comment and encourage anyone to collapse this discussion. CNC ( talk) 19:13, 9 July 2024 (UTC)
I'm neutral to Option 4 and would oppose everything else. I think the conclusion was the only reasonable reading of the discussion, and closing to any consensus (including, by the way RSP works, WP:GREL) would be inappropriate. I'm not particularly attached to the summary though, and honestly do think that the exact phrasing was stronger than was reflected in the discussion. Loki ( talk) 16:35, 9 July 2024 (UTC)
@ LokiTheLiar, this section was to disambiguate the intentions of people who support Overturn, it could be a bit misleading to include the opinions of people who endorse the close. Samuelshraga ( talk) 19:38, 9 July 2024 (UTC)
Option 2. The default in a case of no-consensus is to maintain the previous status quo. *Dan T.* ( talk) 17:58, 9 July 2024 (UTC)
It's not, see comment above re status quo of RfC closures regarding source reliability. Are you suggesting that it should be, and should it be enacted retrospectively as well? This isn't the right venue for that proposal, but I'd appreciate clarity from the "no consensus means no change" crowd as to what they are proposing, so we can draft up an RfC for it and move forward. CNC ( talk) 18:16, 9 July 2024 (UTC)
For WP:RSP that is not true. Look at the page; it has an entire category for sources on which there is no consensus, and sources are described as lacking consensus repeatedly throughout the table. Its purpose is to document the current consensus of the community (or lack thereof); it doesn't have the same need for stability or the need to reach a hard decision on some version that applies to article-space. We can't realistically leave an article in no-consensus state, but for RSP we can and frequently do. -- Aquillion ( talk) 19:33, 9 July 2024 (UTC)
Option 2 CoffeeCrumbs ( talk) 23:02, 9 July 2024 (UTC)
Since my preferred option isn't there, my ideal would be overturning the close for a re-evaluation, with no assumption that anyone who didn't assert that the specific examples of alleged reliability presented was conceding the unreliability of those specific examples. CoffeeCrumbs ( talk) 23:12, 9 July 2024 (UTC)
I think that's 5? Samuelshraga ( talk) 11:11, 10 July 2024 (UTC)
I didn't think so since I'm not suggesting no guidance, but no guidance with the direction of making sure not to make what I personally feel was a particular previous error in determining consensus. I think a closer needs to approach the arguments about reliability more than the feelings about reliability, which I believe (again, my personal opinion) is more in line with establishing consensus and decreasing the chances that this becomes a whole new dreary casus belli in what is already a controversial area. CoffeeCrumbs ( talk) 00:41, 11 July 2024 (UTC)
Option 5. Chess ( talk) (please mention me on reply) 00:32, 10 July 2024 (UTC)
Option 4 as per my statement above. I think you got the result right, but the reasoning (especially introducing ONUS) is wrong. Also to note I reject the premise behind Option 2. The RSP (and so RSN) does have a way of indicating that editors don't agree on the reliability of a source (MREL), so I also don't agree with editors that no consensus means no change. The RSP is not article content, and this wasn't an RFC on how to update the RSP. The RFC was on the reliability of the source, on which there isn't agreement. -- LCU ActivelyDisinterested « @» ° ∆t° 11:11, 10 July 2024 (UTC)
  • Option 5 Sweet6970 ( talk) 12:36, 10 July 2024 (UTC)
  • Well, okay then. I see nothing that tempts me to revert myself, so when, after the requisite amount of wrangling, someone else comes along and closes this, their entire menu of options seems to be either (1) no consensus to overturn or (2) consensus to overturn but no consensus what to overturn to, in which case the next closer has a great big problem. If you want, you can make this less of a headache for that hypothetical person by supplying with reasoned arguments for what the close should have been. It would help even more if you could take the trouble to ensure that these arguments are compatible with the rather idiosyncratic way that WP:RSP works.— S Marshall  T/ C 16:08, 10 July 2024 (UTC)
The closer requirements involve being compatible with policies and guidelines. WP:RSP is neither so no arguer or new closer would have any obligation to be compatible with its idiosyncracies. Peter Gulutzan ( talk) 16:59, 10 July 2024 (UTC)
Thank you. I'm certainly refreshed and challenged by your unique point of view.— S Marshall  T/ C 17:44, 10 July 2024 (UTC)
What polices and guidelines is RSP not compatible with? Thryduulf ( talk) 17:58, 10 July 2024 (UTC)
Irrelevant. Peter Gulutzan ( talk) 22:36, 10 July 2024 (UTC)
If you would like to overturn a ton of our existing consensus and system, you may open that as a separate proposal. For now, let's please operate within the status quo. Aaron Liu ( talk) 22:40, 10 July 2024 (UTC)
Perhaps I've caused a misunderstanding, see reply to Thryduulf below. Peter Gulutzan ( talk) 23:08, 10 July 2024 (UTC)
You explicitly claim that RSP is not compatible with policies and guidelines. It is not irrelevant to ask you to substantiate that claim by listing which policies and guidelines it is not compatible with (and ideally explaining why). Thryduulf ( talk) 22:44, 10 July 2024 (UTC)
I think I belatedly see where you got that idea and it's my fault. After the sentence "The closer requirements involve being compatible with policies and guidelines." I said "WP:RSP is neither ..." i.e. "WP:RSP is neither a policy nor a guideline ...". You seem to have taken it as "WP:RSP is neither compatible with policies nor with guidelines ..." So I should have written more carefully. Anyway, it's true that WP:RSP is neither a policy nor a guideline and your question doesn't relate to that. Peter Gulutzan ( talk) 23:08, 10 July 2024 (UTC)
You're welcome to explain how you think RSP should be changed in discussion below. CNC ( talk) 22:46, 10 July 2024 (UTC)
Perhaps I've caused a misunderstanding, see reply to Thryduulf above. Peter Gulutzan ( talk) 23:08, 10 July 2024 (UTC)
Policies and guidelines aren't the only kind of consensus out there. RSP's consensus is not overridden by any broader consensus, thus it stands. Aaron Liu ( talk) 18:30, 12 July 2024 (UTC)
Not sure what that's arguing for, it remains true that no arguer or new closer would have any obligation to be compatible with its idiosyncracies. Peter Gulutzan ( talk) 00:44, 13 July 2024 (UTC)
The word you're looking for with "idiosyncrasies" is "consensus". Aaron Liu ( talk) 04:53, 13 July 2024 (UTC)
The next closer does not have a great big problem, because presumably they will actually evaluate and weight the discussion appropriately, rather than taking the initial commenter’s claims at face value, ignoring the amount of support for the refutation of those claims, and in fact repeating those inaccurate claims as part of the close.
I respect you a lot S_Marshall, I really do, and your closes tend to be quite well crafted and explain your decision making very well. This one missed the mark woefully, however, as seems to be clear looking at the consensus forming above that your close was not appropriate. I don’t want you to think that I’m trying to say you intentionally supervoted here - but the fact is you seem to be unable to accept that your close amounted to a supervote, and you, to use your words, “unashamedly embraced” the initial, refuted claims, the refutation of which was agreed to in large part by most editors providing substantive comment after it. You also basically begged it to be taken here - I’m not sure if you did that because you felt confident that your close was not a supervote (when it was), or whether you just didn’t want to deal with it. But you were given the chance to expand on your claims in your close - and you instead posted basically the same closing statement with only a couple additions that did nothing to address the significant plurality (if not majority) of editors who directly discounted the claims you took as fact in your closure. -bɜ:ʳkənhɪmez ( User/ say hi!) 20:22, 10 July 2024 (UTC)
Well said. I believe S_Marshall almost always does a terrific job, and is extremely valuable to the movement. I disagree with the close, for a similar reason you do, but I really hope it's not taken as a personal attack, but as a polite disagreement on something that is important to get right. CoffeeCrumbs ( talk) 00:43, 11 July 2024 (UTC)
  • Option 4 per my !vote above. Option 2 is against current policy and would require changing WP:RSP or establishing a specific carve-out for this case, neither of which are palatable. Pinguinn  🐧 11:43, 11 July 2024 (UTC)
  • Option 4, if that wasn't obvious yet. Aaron Liu ( talk) 03:22, 12 July 2024 (UTC)
Option 5. Levivich ( talk) 18:21, 13 July 2024 (UTC)

Part 2

For !voters of Option 2, could you also clarify how "no consensus, defaulting to no change" should work based on the status quo at RSP:

  • Option 1: The Telegraph RfC should be an exception to the status quo, therefore the no consensus close wouldn't change previous consensus
  • Option 2: The Telegraph RfC and future no consensus RfCs should no longer replace any previously established consensus
  • Option 3: All sources with no consensus should default back to any previously established consensus, retrospectively
  • Option 4: No consensus RfCs should only be included on a case by case basis
  • Option 5: Disagree that this is how RSP categorises sources

This is not an RfC, simply trying to clarify how "defaulting to no change" is supported. Pinging additional editors who expressed this view or touched upon it for comment: @ Amakuru @ Walsh90210 @ *Dan T.* @ BilledMammal CNC ( talk) 20:13, 9 July 2024 (UTC)

I'm not sure there is an easy answer here. If we had say 50% (by numbers and quality of argument) say a source is 1 while the other 50% say 2, I would be inclined to go with status que. However, if things are the same ratios but we are dealing with 1 vs 3 (green vs red) then it seems hard to justify status quo. Perhaps I'm thinking about it a bit mathematically, but if nocon shifts it a half point I would err on the side of no change. If nocon shifts a whole point, I would move it. I would also note that if we are talking about moving the source up vs down I would err on the side of more general source inclusion vs less. As this applies to the discussion above, I would say such a clear divide should be yellow with an understanding that we really mean case by case, not yellow is generally excluded but perhaps could be used here or there. Springee ( talk) 19:29, 9 July 2024 (UTC)
WP:MREL does state "may be usable depending on context." but nonetheless you make valid points, even if it's a big can of worms. If I understand correctly, what you're suggesting is a "case by case" assessment based on the RfC itself? The next question would be should this be decided by the closer, or by discussion and consensus at RSP? I've otherwise included another option for "case by case" basis of inclusion, which while I still think is a CoW, appears a relevant option based on your comment. CNC ( talk) 19:44, 9 July 2024 (UTC)
Sorry, when I was talking about case by case I was referring to a source that is decided to be yellow and how we use it in articles. This is a general complaint about how yellow sources are sometimes treated as less legitimate than green ones. Sometimes editors play a game of green source beats yellow source and ignore case by case usage context. For example, if a green source briefly said, "this is bad" while a yellow source offers 3 detailed paragraphs discussing pros/cons but mostly pros in detail I wouldn't presume the green source article proves the yellow source wrong. In this case I would say the yellow source is the stronger of the two. As for RSN closings, I think they will always be case by case but hopefully most cases will be easier to untangle. Springee ( talk) 20:54, 9 July 2024 (UTC)
My mistake. Naturally I agree that a compilation or MREL sources is more reliable than a single GREL, depending on the context of course, but generally I agree with the concept. I'm not sure what you mean by "As for RSN closings, I think they will always be case by case but hopefully most cases will be easier to untangle". CNC ( talk) 20:59, 9 July 2024 (UTC)
Looking at WP:RSP, for several of the first "no consensus" colored topics, the discussions were closed with consensus ( Anadolu Agency, AllSides Media, Apple Daily, Arab News). This "no consensus" supervote is not inline with general practice, and cannot stand. Walsh90210 ( talk) 20:17, 9 July 2024 (UTC)
So Fox News and HuffPost (politics), among others, should be overturned, per Option 3? CNC ( talk) 20:19, 9 July 2024 (UTC)
From Wikipedia:Reliable_sources/Noticeboard/Archive_406#RfC:_downgrade_Fox_News_for_politics?: It is clear the overwhelming consensus is to downgrade Fox News to generally unreliable for politics starting in November 2020. Once again, there is consensus in the close. If the result here is "no consensus", it cannot be used to justify any change in treatment. Walsh90210 ( talk) 20:21, 9 July 2024 (UTC)
No. Per WP:FOXNEWS: "Historically, there has been consensus that Fox News is generally reliable for news coverage on topics other than politics and science. However, many editors expressed concerns about the reliability of Fox News for any topic in a 2023 RFC. No formal consensus was reached on the matter, though." Should it be overturned then? Please tell me you otherwise looked past RSP entries beginning with A. CNC ( talk) 20:23, 9 July 2024 (UTC)
Would you like me to reference WP:HUFFPOLITICS as well? CNC ( talk) 20:35, 9 July 2024 (UTC)
I am strong on assuming that the status quo for no consensus at RSP holds for this discussion. I don't think we should be questioning the long-standing tradition at RSP, which has its own reason, to derail this CRV. If someone would like to change that, they should start their own proposal. Aaron Liu ( talk) 20:41, 9 July 2024 (UTC)
I'm also of the strong opinion that "the status quo for no consensus at RSP" is relevant, but the reality is many editors have expressed their concern over RSP listing prcoess and therefore it requires evaluation, here and now. This section of "Request for clarity" is not an attempt to "derail this CRV", but instead to refine discussion of this topic to this section. CNC ( talk) 20:53, 9 July 2024 (UTC)
Yeah, I know that nobody wanted to destroy our efforts here. However, in my opinion, if we try and bite off more than we may chew, that is what's going to happen. Aaron Liu ( talk) 00:06, 10 July 2024 (UTC)
Putting aside policy questions around privileging "status quo vs MREL", I think it's relevant that many editors who supported Option 1 and Option 2 in the RfC found that - especially after the detailed rebuttals (by Chess and others) - that there was simply no case to answer on unreliability, notwithstanding that some editors continued to allege it.
The discussion wasn't framed around an open discussion of the question "Is the Telegraph reliable?" It was framed as "Do the examples brought by (mainly) Loki establish that the Telegraph is not generally reliable?"
Editors who supported GREL clearly thought that the case for GUNREL had been refuted, and saw little need to make positive arguments in favour of GREL. If a finding of MREL is really the outcome of this close (or the close which follows it after overturning) of this RfC, it's implausible to me that a new RfC will not quickly be generated to make the positive case for reliability on transgender issues (and gender-critical views, which the closer inexplicably included).
Quantitative arguments to do with the volume of articles published and number of factual inaccuracies, any retractions or corrections which have been published, Wikipedia:USEBYOTHERS and others spring to mind. I am sure that such evidence would have been raised if GREL supporting editors thought that the discussion would be interpreted this way. Samuelshraga ( talk) 16:16, 10 July 2024 (UTC)
UBO was actually raised, though sources supplied to evince UBO were disputed; the dispute was not resolved by the time the second month came in and discussion fizzled out. Aaron Liu ( talk) 20:14, 10 July 2024 (UTC)

An unrelated, modest proposal

Between this imbroglio and the one about the ADL RfC a few days ago, maybe we should just write down somewhere that any RfC with more than (500kb? 1mb?) of crap in it ought to be closed by a panel. Obviously not as a requirement, but it just seems practical. Is this anything? Does this have legs? jp× g 🗯️ 21:13, 9 July 2024 (UTC)

Agree . Because based on your threshold, it will always be contested. CNC ( talk) 21:16, 9 July 2024 (UTC)
Before some offsite brane-geniouse[ sick [ sic] adds to the red-string corkboard that this is some kind of veiled attempt at shady political ministration, I already commented in the RfC, and furthermore I do not particularly give a rat's what parliamentary hocus-pocus ends up happening here (or at XRV), it's just taxing to see one person try and sit down to close a Tolstoy-length RfC, immediately get massively BTFO at AN over the close, and then all their effort is wasted when a separate group of people sit down to write a panel close. jp× g 🗯️ 21:19, 9 July 2024 (UTC)
This now sound like some kind of veiled attempt at shady political ministration. CNC ( talk) 21:29, 9 July 2024 (UTC)
Back in 2006 the phrase "muhahahahahahaha" was considered extremely random and funny, and I think we should have a revival. jp× g 🗯️ 21:56, 9 July 2024 (UTC)
I'm not sure about absolutely requiring a panel close, since that would mean that some of these discussions would take months and months to be closed, but I do think I'd support a requirement for either an admin or a panel close. I think this particular close was good, but I'd really rather skip the inevitable-closure-review part of the process in the future as much as possible. Loki ( talk) 21:38, 9 July 2024 (UTC)
I think recommending (not mandating) that such discussions are closed by a panel or highly experienced, clearly uninvolved single admin would be good. Not because non-admin closures are inherently bad (they aren't - some non-admins are better closers than some admins) but because close reviews based on alleged minor procedural errors or the admin status of the closer (which are becoming more common) are a bad thing. Maybe some sort of restriction that said someone who was involved in a discussion may not initiate a review of such a discussion within 48 hours of the close unless they get agreement from someone uninvolved or someone who supported a different outcome to them that a review is justified. However I don't know whether this would actually work or how it could be enforced - it would need more thought before it could be a viable proposal. Thryduulf ( talk) 21:53, 9 July 2024 (UTC)
I do think recommending an admin or panel close would be good for RFCs over a certain length, but it would also be a good idea to tack on RFCs in WP:CTOP areas. Most of the contested closes I see are in WP:AP2, WP:ARBPIA, or WP:GENSEX; for those we actually could require it and I think it would help significantly. There are a lot of CTOP areas and many of them are pretty quiet nowadays, so we might just want to do it in certain ones like what I listed here. The Wordsmith Talk to me 22:03, 9 July 2024 (UTC)
I don't think there is solid evidence that panels (even admin panels) are less likely to be challenged these days. Also given the difficulties we already face in finding closers for such discussions I do not think it wise to add an additional procedural hurdle. Best, Barkeep49 ( talk) 22:07, 9 July 2024 (UTC)
Sure, it would be bureaucratic mumbo-jumbo in some cases, but I don't think the alternative is having no bureaucratic mumbo-jumbo. The alternative, which we are currently posting in, is a hundred-thousand-byte AN thread paired with a twenty-six-thousand byte XRV thread (and this is just on the first day of both). jp× g 🗯️ 22:38, 9 July 2024 (UTC)
  • If you do the heavy lifting then you're going to get close reviews, panel or admin or bureaucrat or founder. We need to think about how we conduct them. I've noticed that someone who doesn't like your close virtually always alleges involvement, as well as supervoting and all the other things that challengers pretty much have to say, because we have this weird culture where saying "I think the closer was wrong" always fails but "the closer made a technical procedural error" often succeeds. If we change that culture we'll make better decisions.— S Marshall  T/ C 22:26, 9 July 2024 (UTC)
    Yeah, this is the most annoying part: even if the close is (imo) a correct interpretation of consensus, a single closer will often give rise to all sorts of objections along the lines of "well how do we know this random person is correct?" or "but they aren't even an admin!" or "they said while instead of whilst!" et cetera. This can give people a ready-made rationale to disregard or overturn the result later on because "well the close was half-assed" etc... in the example of the ADL RfC, there were actual think tanks and newspapers talking shit about the close, so I think that making it more difficult to raise objections to the manner of the close is overall better for the decisionmaking process.
    Of course this doesn't need to be done in all cases, but I think it would be condign to at least point out that people are prone to demanding it. jp× g 🗯️ 22:36, 9 July 2024 (UTC)
    I think the root of the issue is that closers are often vague. For example, in this close you say on the basis of scholarly sources and an Ofsted report, various misrepresentations contained in that article are noted. You don't explain what those misrepresentations were, which ones were supported with scholarly sources and an Ofsted report, or what the community consensus was on each of them. This makes it very difficult for editors to determine if your close is correct.
    Sometimes this is even done deliberately, to make it harder to challenge the close, something I very much disagree with - if there is something wrong with a close we want to be able to identify it. I'm not saying you do this but some closers, by their own admission, do.
    Because this makes it difficult to determine whether the closer is actually wrong editors need to consider the information that is available to them - whether the close appears to be a supervote, and whether the closer has previously expressed opinions on the topic that might have tainted their reading of consensus. I think if we fix that issue, if we expect closers to provide more detail, then I think the rest will fix itself.
    That's not to say every close needs such detail, but some, including this one and the ADL one, would have benefited from it. BilledMammal ( talk) 22:39, 9 July 2024 (UTC)
    Nobody at all is ever satisfied by providing more detail about the closing method, in any circumstances.
    In the 10+ years I've been closing RfCs on Wikipedia, I've been asked to expand on my close more than a few times. Exactly 100% of the people who asked for this have gone on to issue a close challenge, and exactly 0% of them have been satisfied.
    I'm afraid that long experience of this tells me the only reason anyone ever asks for more detail is because they're hoping you'll say something they can attack at AN.— S Marshall  T/ C 15:49, 10 July 2024 (UTC)
    I haven't been closing discussions for as long, and I focus more on RM's, but my experience differs - I find that sometimes the editors are satisfied by my expansion.
    Other times, they do go on to use what I said in a close appeal - but personally, I think that's a good thing. If I said something wrong then that means I probably made an error in my close and I want the community to be able to find and rectify that error. When closing, my goal isn't to write a close that will survive a close review, but to write a close that will accurately reflect consensus. BilledMammal ( talk) 00:49, 11 July 2024 (UTC)
    To expand on this, I wanted to use the example of a question I asked you: What misrepresentations are you referring to here? As far as I can recall ... the only alleged misrepresentation raised was whether a student actually identified as a cat.
    If I was asked a question like this as closer I would be happy to answer it. This is because the nature of it means only two things can happen; either I can satisfy at least that concern, preventing or at least reducing the scope of any close review, or can I discover that my close was flawed. I see both these results as a positive.
    Honestly, I greatly respect you as a closer. In discussions about NACs I've previously cited you, along with Paine Ellsworth, as two of our best closers. In this case, however, I think you made a (very rare!) mistake. BilledMammal ( talk) 03:57, 11 July 2024 (UTC)
    The legal system has tried to solve this problem by having a standard of review. We should implement this on Wikipedia by clarifying what level of deference we give to closers, given that we already have this as an informal policy. In my opinion, we should only defer to the closer when a closing statement considered an issue being disputed, and when the closer's judgement is based on the arguments people have made. Chess ( talk) (please mention me on reply) 02:51, 10 July 2024 (UTC)
  • I agree with Barkeep49 that there is no evidence that having a group of evaluators of consensus leads to less followup discussion. I also don't think it's appropriate to treat admins as being specially privileged to evaluate consensus. In my view, the problem is that the community has certain expectations regarding how consensus is evaluated, and typically there'll be someone whose viewpoint didn't prevail that chooses to point out any deficiencies they see. I know the community historically dislikes bureaucracy, but if we were to introduce some, I'd suggest building up a list of experienced evaluators of consensus who can be asked to determine the result of divisive discussions. Note that the only way to become experienced is to evaluate some discussions, so the community needs to be tolerant of users stepping up to do so, even if they make mistakes. Wikipedia:Discussions for discussion could serve as a place to foster greater experience in evaluating discussions (at its genesis, I had feared it would be just another place to where disputes would spread, but up until now, that hasn't happened). isaacl ( talk) 22:58, 9 July 2024 (UTC)
    At one point I had thought about proposing a userright flag called discussioncloser that could be given out to trusted users like template editor and rollback. It wouldn't have any technical permissions, but maybe there could be an edit filter restriction non-discussioncloser users from using our close templates on certain pages. The Wordsmith Talk to me 01:45, 10 July 2024 (UTC)
Closes are legitimate when they consider the necessary facts and provide clear reasons for decision. Panels assist greatly in this, because editors can compare notes and ensure they're not missing any relevant information. Obviously, people are going to complain no matter what, but a good close will explain why certain !votes were disregarded and others were not. Chess ( talk) (please mention me on reply) 02:19, 10 July 2024 (UTC)
I agree with this too. And especially when a discussion becomes lengthy, it is much more likely that whether intentionally or not, a closer misses significant portions of the discussion, or in other words, unintentionally falls into a vote-count just because one side may have significantly more words than another. It is not reasonable to expect one person to be able to read a lengthy discussion and not error in some way even if they take hours or days to read through it and attempt a closure. The beauty of a panel is that if one person, or even two, miss something, it is likely that the third/further person will catch it. -bɜ:ʳkənhɪmez ( User/ say hi!) 03:08, 10 July 2024 (UTC)
While panel closes have their uses, I think that generally the best way to catch issues is by having the closer be more verbose. It doesn't increase their workload significantly, and it makes it easy for participants to catch errors and raise them with the closer. BilledMammal ( talk) 03:22, 10 July 2024 (UTC)
One of the main benefits I found in doing a panel close on the ADL RfC was being able to workshop the close statement. Any of the three of us could have closed the thing in a way that was within a reasonable closer's discretion, but together we were able to talk through how the close statement would read to participants on both sides, to non-participants, to people looking back later, and to catch statements that might be too easy to take out of context, could be twisted to claim bias in one direction or the other, etc.
The downside of a panel close is you need to find multiple people willing to take the same level of heat—all three of us in the ADL close panel have been criticized in multiple publications—and then get those people to coördinate. We spent hours on voice calls. Others may exchange many emails. With most things in life, teamwork reduces the total number of person-hours required, but with panel closes it actually increases it. Because of that, I'm not sure to what extent our volunteer ecosystem can support a greater number of panel closes than organically emerges. -- Tamzin[ cetacean needed] ( they|xe) 03:16, 10 July 2024 (UTC)
I think you make an important point about having at least a bit of review in the closing process, something the panel allows. Is there a way that we could have something like a RfC close, pre-close discussion for some of these topics? I think sometimes there is a level of momentum once the close is "official" but if the closer could state what they are thinking and allow editors some ability to chime in before the ink is dry, would that reduce some of the issues that you pointed out? I'm not sure if this is a practical idea or one that might cause more issues than it solves but perhaps it would help. Springee ( talk) 03:26, 10 July 2024 (UTC)
As someone else noted somewhere in here, WP:Discussions for discussion exists. That said, when a major concern in closing a sensitive RfC is avoiding becoming part of anyone's narrative (to the extent it can be avoided), having a public drafting/review process, where everyone can see suboptimally-phrased past wording, would defeat a lot of that. But I think it's still better than nothing. -- Tamzin[ cetacean needed] ( they|xe) 03:52, 10 July 2024 (UTC)
@ JPxG, there's already often a backlog of RFCs for close at WP:CR. I don't see adding a suggestion that any RFC over certain length be closed by panel is going to help that, in fact it may just give challengers more ammunition in their claims that entirely reasonable closes are somehow bad. TarnishedPath talk 03:30, 10 July 2024 (UTC)
  • I can think of 3 panel closes off the top of my head that I strongly disagreed with. I won't name them because I don't want to call anyone out, but my impression is that panel closes do not help improve RFC closing accuracy, so I don't think it'd be a good idea to require them. – Novem Linguae ( talk) 04:01, 10 July 2024 (UTC)
What would be helpful would be a way to stop editors turning RFCs into huge walls of text. In every RFC that ends up this way there are always a small handful of editors (not the same editors, but rather the editors who most care about the issue) that generate the most text. The rebuttal of an argument happens each time that argument is used, but that shouldn't be necessary (it not being a vote). -- LCU ActivelyDisinterested « @» ° ∆t° 11:18, 10 July 2024 (UTC)
Yet it basically was necessary here, and the closer still didn’t account for the rebuttal in their closure of the discussion. So if anything, this close, even if overturned, and the number of people supporting it shows that it is necessary to ensure people whose !vote is based on inaccurate information or an idea that has been disproven/rebutted strongly are aware of the fact their opinion is based on that and given a chance to review and expand upon it. And if they don’t, it can’t be claimed “they didn’t see the rebuttal” - it would have to be seen that they did see it, since pointed out to them, and chose to ignore it - which should result in a significant down weighting of their !vote indeed, as it’s basically an admission that “I can’t rebut that rebuttal”. -bɜ:ʳkənhɪmez ( User/ say hi!) 15:33, 10 July 2024 (UTC)
Outside of Wikipedia, this is done by having someone moderate the discussion. The English Wikipedia community has so far placed a higher priority on ensuring everyone gets to weigh in, out of a concern that any moderation would be unduly strict. isaacl ( talk) 17:32, 10 July 2024 (UTC)
I mean, WP:BLUDGEON is a conduct issue; people can and have been ejected from topic areas for repeatedly bludgeoning discussions. (If it's just one discussion where they lost their cool then it's probably not worth worrying about.) There's always the option to look up repeat offenders, nudge them to stop bludgeoning discussions, then drag them to AE or ANI if they don't listen. Doing that more often would encourage people to not be so bludgeon-y in general. Another thing that might discourage bludgeoning: Make it unambiguous that closers may, at their discretion, ignore all non-top-level comments in an RFC, if the RFC is already massive (of course this would have to be combined by making it clear to everyone that if they feel some point is vital, they need to edit it into their one top-level comment), and should even say that they're doing so so people understand that their elaborate back-and-forth arguments aren't even being read - to be clear, I'm not saying "exclude them when determining consensus", I'm saying closers should be specifically empowered to say "I'm not reading all that, I'm only reading the top-level comments." RFCs aren't supposed to devolve into threaded discussion anyway, so "at a glance this all looks like pointless natter between people who just want the last word and I'm going to disregard it" seems like a reasonable thing to encourage. Maybe even some sort of "just the main argument" viewer that specifically removes all responses. Or we could flatly forbid threaded responses in RFCs, confining them to a separate comment section that the closer is not required to read. -- Aquillion ( talk) 00:37, 11 July 2024 (UTC)
I don't think there is a consensus agreement in the community that requests for comments aren't supposed to have threaded discussion. Many of the editors who like to weigh in on how decisions are made think threading is important for facilitating efficient communications. (My variant on this is that I think we should consolidate discussion so the same topics aren't discussed in multiple threads, but that hasn't gotten a lot of support.) Since English Wikipedia's decision-making traditions are based on the idea of building consensus, I don't think enabling evaluators to say "I'm going to ignore the discussion" would gain favour.
Yes, extreme cases of swamping discussion can get addressed. But communications rapidly bogs down way before that point, and before any point where sanctions would be deemed reasonable. The N-squared problem of trying to hold a large, unmoderated group conversation (where there are up to N-squared interactions that can occur) means that everyone can be acting in good faith and yet it becomes very difficult to follow all the points being made. isaacl ( talk) 00:54, 11 July 2024 (UTC)
Bludgeoning is a lot different than asking someone to reconsider their opinion or explain it further in light of information that they did not address in their original comment - regardless of whether that information was already present or not. Closers should certainly not be permitted to ignore the threaded discussion - because that in and of itself results in "first mover advantage". People would be able to make whatever claims they want, or make their initial !vote based on inaccurate information, and then the closer should just be allowed to ignore the replies/discussion that points that out? Absurdity. -bɜ:ʳkənhɪmez ( User/ say hi!) 01:52, 11 July 2024 (UTC)
You have to let people seek consensus by talking to each other and you have to pay particular attention when someone changes their mind after being persuaded by a convincing point. But you can't allow a passionate editor to have a disproportionate effect on the discussion by sheer volume of text when they're not convincing anyone.— S Marshall  T/ C 07:16, 11 July 2024 (UTC)
If I infodump a wall of text and a dozen other editors cite it, that's not bludgeoning. Neither is posting rebuttals on their own.
Bludgeoning is when an editor repeatedly makes the same argument. This is disruptive because redundant information does not add value to the conversation. Chess ( talk) (please mention me on reply) 13:09, 11 July 2024 (UTC)
I've been trying to think of the way to address this - you say you have to pay particular attention when someone changes their mind after being persuaded by a convincing point - that is exactly what happened in this discussion, yet you not only ignored it in your close, you actually found the opposite to have happened. You took those not commenting on the refutations to be claiming that they were wrong, you viewed those arguments to be "stronger" than those refuting the original claims (when the discussion makes clear it was considered opposite by a clear majority of those commenting on the refutations, rather than ignoring them), and you then impressed your personal opinion of the claims onto the close. You seem to be trying to claim that you ignored the refutations and their support because the editors supporting that view were passionate - that's absurd. Just because someone is passionate and/or points out and asks for others to address a comment that a significant plurality of editors not only addressed but agreed with (and in quite a few cases, changed their !vote after reading) does not make it bludgeoning, and even if it was bludgeoning, it does not make their opinions null and void. -bɜ:ʳkənhɪmez ( User/ say hi!) 00:36, 13 July 2024 (UTC)
I'm not a fan of panel closes either. The only concrete effect they seem to have is to make things take a lot longer. I also often get the feeling that the summaries suffer from the lack of a single author. Instead I'd encourage closers to make greater use of WP:DFD to workshop and solicit feedback on contentious closes before they post them. –  Joe ( talk) 11:43, 10 July 2024 (UTC)
  • For the concerns about backlogs noted above, I’m not sure mandating a panel closure for these long sorts of RfCs would be the best idea (having one person close it takes long enough, mandating that 3-4 negotiate a close would be a bit excessive) - that said, I’m supportive of mandating or strongly recommending that an uninvolved admin handle these closures. Yes, admins aren’t infallible, but it feels more appropriate to have someone who the community’s already entrusted with responsibility handle lengthy/contentious RfCs in CTOPs, rather than a normal user. The Kip ( contribs) 18:07, 11 July 2024 (UTC)
    The credibility of people like S. Marshall should be the least of our concerns here. Aaron Liu ( talk) 03:24, 12 July 2024 (UTC)
    I don’t have any opinion on the Telegraph RFC specifically as I didn’t participate nor have I read it - just giving my 2¢ on the proposal regarding large RFCs in CTOPs and such. The Kip ( contribs) 06:07, 12 July 2024 (UTC)
    We have many credible non-admin closers, so I don't think this is something we should "hunt down". Aaron Liu ( talk) 15:35, 12 July 2024 (UTC)
Also not a fan of panel closes. It's anecdotal, but I think the ratio of bad-closes/all-closes is worse for panel closes than individual closes. At the very least, anybody thinking about mandating panel closes in any situation should first gather some data about whether panel closes are any less likely to be wrong, challenged, or overturned, than non-panel closes. My impression is that Wikipedia has a lot of non-panel closes -- like dozens or hundreds or thousands, depending on the time scale -- and like less than 1% are wrong/challenged/overturned. Whereas Wikipedia has very few panel closes -- like single digits, maybe a dozen or two dozen in the last like 5 or 10 years? -- and a huge proportion of them (like half) are wrong, challenged, and/or overturned. But my anecdotal impressions aren't data; data would be useful. Levivich ( talk) 18:20, 13 July 2024 (UTC)
Any idea where to start looking to gather that data? Thryduulf ( talk) 18:35, 13 July 2024 (UTC)
It's not useful data to have. People don't even ask for panel closes unless it's really super-contentious, so it shouldn't surprise anyone that more panel closes get challenged or overturned (which I don't know if it's true, but it does seem likely to me).— S Marshall  T/ C 19:02, 13 July 2024 (UTC)
For individual closes, maybe Legobot's contribs, and/or the page history of WP:CR, to gather a list of RfCs/discussions. But then after that I don't know, seems like a difficult task to calculate the total number of closed discussions vs. how many of them were challenged (AN archives will find some official close reviews, but that wouldn't include those that never went past the closer's talk page).
As for panel closes, I don't even know... probably manually plucking them out of the gathered list of RFCs/discussions.
Overall it strikes me as something that would basically have to be done manually and would take many hours. For a single year, it's maybe doable, but that would leave a tiny sample size of panel closes (maybe low single digits). For this reason, the efficacy of panel closes may never be fully understood. Levivich ( talk) 19:29, 13 July 2024 (UTC)

Subpage?

At the time of typing we're just over 30,000 words. I'm minded to move it to its own subpage?— S Marshall  T/ C 13:51, 12 July 2024 (UTC)

Honestly, I think the relevant discussion has already run its course, and now it's mostly people just venting their personal dislikes of each side at one another. Probably better to just shut down the side discussions. — The Hand That Feeds You: Bite 20:21, 12 July 2024 (UTC)

I think it's worth adding that I read much of the discussion, researched some of the references given by the proposer, came the conclusion that they did not support what was claimed, saw that the inaccuracies had already been pointed out by other editors and decided not to contribute.

I'm now very confused. Since the allegations against the Telegraph were shown to be incorrect, I can't see how I could have added to the discussion according to Wikipedia practice, which is (or is supposed to be) don't simply repeat what has already been said. Perhaps the idea of consensus has now swung so far into the realms of "guess the majority" or perhaps it's "follow your political nose". The close to this RfC is not neutrally written - that's a shame. And it seems a political campaign has succeeded here, where it should not have.

All the best: Rich Farmbrough 23:48, 12 July 2024 (UTC).

Withdrawing deletion nomination

I have withdrawn the deletion nomination of a page, see this, an administrator must talk. Hamwal ( talk) 10:49, 10 July 2024 (UTC)

Given that two people have weighed in on the discussion with something other than a keep !vote, the nomination is no longer eligible for withdrawal. -- Blablubbs ( talk) 11:22, 10 July 2024 (UTC)
Well you can add a keep vote with reason and state that you are withdrawing your delete nomination. But that will not trigger close in this case. Graeme Bartlett ( talk) 12:29, 11 July 2024 (UTC)

Opinion sought

A small edit war occurred at LGB Alliance leading directly from the closure of The Telegraph reliability RFC. While no intervention is, at present, required, as parties appear to have stopped warring, two editors are under the impression that it is other editors who were edit warring, not them. There has been discussion of this, with diffs, at Talk:LGB Alliance#Dubious source and at User talk:Amanda A. Brant#Talk:LGB Alliance#Dubious source. As you can see from these pages, both I, BilledMammal and WhatamIdoing have offered our opinions and all of us have been rebuffed. Both Amanda and BilledMammal have thrown WP:EDITWAR at each other during the article talk page discussion. I'm including BilledMammal as among the participants of the edit war, as their edit was warring back to "status quo". Furthermore that "status quo" includes text sourced to The Telegraph, and therefore aligned with BilledMammal's position being very upset about the Telegraph RFC closure, and they had not previously edited this article or talk page.

I would appreciate an admin/admins who will be respected as neutral by all participants (i.e. not those whose position wrt trans/GCF topics is well known and can therefore be rebuffed as biased by one party) to briefly describe what occurred in terms of our Edit warring policy. No editor even remotely reached 3RR. This is simply about what edit warring is, what constitutes participation in that war, not whether their edit warring needed sanctions or whether the content or absence of content was correct. I'm hoping for enlightenment and better future behaviour as a result, rather than anyone to get into trouble. -- Colin° Talk 13:43, 10 July 2024 (UTC)

(Non-administrator comment) Whatever the result of the review above that's a misinterpretation of WP:MREL. Marginal or disputed reliability is not the same as WP:Generally unreliable.
This was edit warring, reverting reverts of other reverts, even multipole editors only each reverting once could still constitute edit warring. After WP:3RR editors may very well get blocked, but that's not a reasont to get right up to that point.
As with most issue more discussion on the talk page, and less in edit summaries, would likely solve the problem. -- LCU ActivelyDisinterested « @» ° ∆t° 14:45, 10 July 2024 (UTC)
Small correction; I didn't say that Amanda was edit warring - while if they had reverted again I think they would have crossed the line, as it was I don't think that was one of the issues with their conduct there. BilledMammal ( talk) 19:53, 10 July 2024 (UTC)
You're comment "I’m just here because people are misusing RSP. I’m not interested in joining the discussion beyond objecting to that." might as well have read "I'm only here to join the edit war". CNC ( talk) 20:04, 10 July 2024 (UTC)
I disagreed with the specified reason for removal - you can't remove a source on the grounds of unreliability if you're not actually claiming that its reporting is incorrect. Editors later raised other reasons for removal, and I wasn't interested in getting more involved in the discussion.
This isn't an unreasonable position, per WP:SATISFY and WP:VOLUNTARY. Editors are allowed to address one issue without becoming permanently involved in a dispute. BilledMammal ( talk) 20:10, 10 July 2024 (UTC)
Your argument has helped to confirm my suggestion as now you are trying to justify your reason for edit warring, rather than any acknowledgement that is was the wrong action: you made no attempt to avoid edit warring and your revert wasn't necessary. On 9 July, you joined the edit war with Amanda A. Brant, reverting at 15:18 [17], making your first comment on the topic 5 minutes later. [18] This is a clear case of "revert first, ask questions later". Then at 16:50 after stating "I’m just here because people are misusing RSP. I’m not interested in joining the discussion beyond objecting to that. [19], failed to revert your edit. I say "failed" because once you no longer claimed to have an issue with the removed content based on the argument presented by YFNS, you let your revert stand. It seems you've ignored the concerns Colin has raised in this topic. CNC ( talk) 11:43, 11 July 2024 (UTC)
Where's the problem? Someone removed an unreliable source from a page. Fairly reasonable thing to do. LilianaUwU ( talk / contributions) 19:58, 10 July 2024 (UTC)
WP:MREL is not WP:GUNREL, I'm shocked you haven't understood this yet. Likewise regarding edit warring and WP:BRD. It's unfortunately got to the point where an admin needs to explain to you the basics. CNC ( talk) 20:02, 10 July 2024 (UTC)
Fair enough, MREL is not GUNREL. But if a source isn't appropriate (as in here), it shouldn't be used. LilianaUwU ( talk / contributions) 20:14, 10 July 2024 (UTC)
Even if the source isn't appropriate, editors shouldn't be edit warring over whether it should be used (in that place, in that way). The dispute involves the repeated removal and restoration of this sentence:
  • "The organisation has said that lesbians are facing "extinction" because of the "disproportionate" focus on transgender identities in schools."
along with one out of the seven uses of this source in the LGB Alliance article:
The first sentence of the source says:
  • "Lesbian are facing “extinction” because of the “disproportionate” focus on transgenderism in schools, a controversial campaign group for gay rights has claimed."
which could perhaps be faulted on grounds of Wikipedia:Close paraphrasing, but I think it is inarguable that the cited source WP:Directly supports the statement which it was being cited for.
I think this ought to proceed as an ordinary content dispute over whether the organization in question actually did espouse this POV, and (if so) whether that fact is DUE for the lead or should only be placed lower in the article. I don't think this should be considered a dispute solely about whether a source that is still used six other times in the article is inappropriate for citing a seventh time.
Also, I don't think that we should be thinking about this in terms of "sides". An editor who seems to oppose everything this organization stands for has removed damaging information about that org from the lead. Their PR team is probably very happy with her right now. WhatamIdoing ( talk) 20:42, 10 July 2024 (UTC)
This is not just about the fact that The Daily Telegraph is no longer considered "generally reliable" on transgender issues and gender-critical views, and was listed as yellow on Wikipedia:Reliable sources/Perennial sources. There is a nuanced discussion of whether it is appropriate in the specific context (which I addressed) and whether it is WP:DUE in the first paragraph (whether the source is good enough in the specific context is part of that discussion). As I explain on Talk:LGB Alliance, I have reverted exactly once, and only after offering a detailed rationale on the talk page that the other party did not respond to, after being given an opportunity to do so. That is not edit-warring. That is normal editing. Pretty much all the other participants in the discussion routinely do the same thing. I don't think the most recent edit by User:Barnards.tar.gz that basically reinstated my edit with some tweaks is edit-warring either. There now seems to be general agreement to remove the material in question. The only really unacceptable behavior in relation to this minor incident was the abuse of templates and personal attacks by one editor. -- Amanda A. Brant ( talk) 20:37, 10 July 2024 (UTC)
Depending on where one chooses to start counting, you have reverted either once or twice. The question here isn't really "Did User:_____, personally and individually, do anything that should be punished?" The question is more like "Do we have one of those situations in which editors [note the plural] keep flipping back and forth between the same two versions of the article?"
If you click through the relevant diffs ( [12] [13] [14] [15] [16] [17] [18]), then I'd say we have an edit war, even if no single individual has broken any bright-line rules. WhatamIdoing ( talk) 20:46, 10 July 2024 (UTC)

- Just to say that I did ask for neutral admin (or experienced user) to comment as a third opinion, not for existing participants to continue to argue whether they did or did not edit war, or for folk to offer their opinions about which warring edit was the right one. I think such a wise authoritative voice would still be very welcome, as editors are continuing to argue they were not edit warring because they were Right and everyone else was Wrong, on the article talk page. -- Colin° Talk 21:46, 10 July 2024 (UTC)

It does look like an edit war, at least the early stages of one. Unofficially, I'd encourage all parties to stop reverting and discuss on the talk page. That's exactly what happened, so I don't think it needs to go any further at this point. The rest seems like a content dispute which isn't really suitable for WP:AN. The Wordsmith Talk to me 21:55, 10 July 2024 (UTC)
  • I would be more concerned about the reliability of anything written by Camilla Tominey (stick "Camilla Tominey trans" into Google and have a look at that - don't bother looking at the hagiography that is Camilla Tominey) rather than the fact she happened to write it in the Telegraph. And as far as I can see, regardless of its source, it certainly isn't WP:DUE in a lead paragraph. As a second point, articles such as LGB Alliance are covered by WP:GENSEX so I'd suggest that editors who are pushing their POV consistently across multiple noticeboards and articles have a think about where pushing too hard ad nauseam might lead. Black Kite (talk) 07:23, 11 July 2024 (UTC)
    Can we please not have comments on the content/sources. Go to the article talk page if you want to do that. The concern here is some editors are unaware (or unwilling to accept) what constitutes edit warring. The actual topic is irrelevant. -- Colin° Talk 11:41, 11 July 2024 (UTC)
    No, the issue here is the material, that was dubious from the start (dubious in the sense that its use in the first paragraph unduly promoted a biased narrative), and that has in fact been removed from the article by various editors. This harping on a supposed "edit war" after a couple of editors "reverted" exactly once each – in my case with a detailed justification and rationale that the other party had been given an opportunity to respond to, and in Barnards.tar.gz's case to attempt some sort of compromise, that now seems to be widely accepted by everyone – is not productive use of our time. -- Amanda A. Brant ( talk) 16:03, 11 July 2024 (UTC)
    I appreciate the uninvolved parties offering opinions, so I don't want to rehash all this and I won't add any more than this, but as "the other party" I would like to offer context as I saw it.
    • The page in question is exceptionally hard to attain consensus on for any changes, due to the divisive nature of the subject
    • The content we're talking about has been in the lede unchanged for (I believe) couple of years
    • The change you wanted, you justified based on an updated note on The Telegraph on Perennial Sources that was barely 2 hours old at this point, after a lengthy and polarising RFC we were both involved in, on opposite sides
    • You used this very recent change not only to argue in talk for this removal, wrongly claiming that the Telegraph was WP:GUNREL and should not be used, but also elsewhere on that talk that it should not be usable WRT other disputed neutral wording in the lede
    • Your rationale, aside from being a misreading of the note, cast aspersions about essentially the entire UK media
    • When I pointed out you were overstating things, you replied with what was a restatement of the same claim. At this point, my impression was we were at loggerheads, so wait and see if someone else weighs in. I don't see the point in repeating myself ad nauseum.
    • When you then reverted my revert, it was 2:30am my time. I'm sorry but I don't keep tabs on this 24/7, nor do I see the desperate urgency to remove ancient content such that it cannot be discussed by more editors first.
    • When your change was reverted to restore the status quo ante, I was personally glad of an uninvolved intervention and considered it a call to actually discuss the change per BRD, which I felt your revert had not been in the spirit of. However, with the issue subsequently being raised here as an edit war, I now see things like WP:DONTREVERT say Wikipedia does not have a bias toward the status quo so I guess my understanding of norms about this sort of thing are not correct. Every day is a school day, and I'll certainly bear this in mind in future.
    • FWIW, I have since chucked my 2p in on talk after the fact and endorsed the actual change as subsequently performed by Barnards, for the rationale that emerged on talk which I agree with, but I do understand the concerns about the process.
    At this point I think, despite how it was arrived at, there is actual unanimity about the content, which on that page is a cause for either celebration or to check its not April 1st. Void if removed ( talk) 21:50, 11 July 2024 (UTC)

Scott's use of revision deletion

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Scott ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)

Hello. Following discussion on Scott's talk page, I am asking for review of Scott's revision deletions. Despite another administrator and I attempting to explain that RD3 should not be used for all vandalism, Scott has misrepresented previous consensus (the discussion specifically stated that "it was also generally agreed that most vandalism was out of scope for RevDel"), changed the text of policy to suit their interpretation of it, and responded to the other administrator's concerns with " my God, stop being so melodramatic ... This is absolutely pathetic".

Much of Scott's revision deletions have been of run-of-the-mill instances of vandalism from years ago, such as ' When people eat Pringles, it is very yummy according to the people who eat/ate it', ' WORST WEB PAGE ON THE WEB "LULZ!"', and keysmashing. As revision deletion should not be used for such "basic" instances of vandalism, they should be undone. I would also point out that the tone of responses have been deeply disappointing. Thank you, Sdrqaz ( talk) 21:39, 11 July 2024 (UTC)

Accusing me of "spamming the logs" by deleting (hiding) 3 revisions is melodramatic and doing so as a transparent attempt to get me in trouble (based on an idiosyncratic personal interpretation of long-established policy) is pathetic.
I already responded to your concern on my user talk page where you raised it, to remind you that "purely disruptive material" is the definition of WP:RD3 as established community practice, and the last RfC on the topic ( Wikipedia:Requests for comment/Clarification of RD3 in 2011) failed to establish otherwise.
You accuse me of "changing the text of policy to suit my interpretation" when in fact, I simply corrected a contradictory statement in the preamble (which you highlighted) which had been sitting there invalidating every RevDel criterion except RD2 since 2009. Obviously, nobody interpreted it literally enough to prevent them from using any of the other criteria, but it does seem to have been sufficiently confusing to cause you to think that it should.
As I said to you before, if you disagree with the definition of RD3 then the appropriate place to gain consensus for a change is WT:Revision deletion.  — Scott talk 21:52, 11 July 2024 (UTC)
Do not endorse. Those are definitely not suitable uses for revision deletion. There's a reason why "vandalism" isn't one of the examples provided for RD3: includes harassment, grossly inappropriate threats or attacks, browser-crashing or malicious HTML or CSS, shock pages, phishing pages, known virus-proliferating pages, and links to any of these or to web pages that disparage or threaten some person or entity and serve no valid purpose. More concerning, though, is Scott's attitude towards this. When someone asks on your talk page why you decided to take admin actions, calling their concern "absolutely pathetic" is not acceptable. — Ingenuity ( t •  c) 21:59, 11 July 2024 (UTC)
Perhaps you could explain how the diffs provided above are not describable as "purely disruptive material"?
Also I'll thank you not to misrepresent my words - aggressively accusing me of "spamming the logs" is what's pathetic, rather than civilly opening a talk page conversation over the interpretation of RevDel criteria. I choose not to be bullied, thanks.  — Scott talk 22:09, 11 July 2024 (UTC)
The only person who was aggressive in that conversation was you. And you think that this is bullying? Wow. — Ingenuity ( t •  c) 22:18, 11 July 2024 (UTC)
What kind of topsy-turvy world is it where someone comes into your talk page yelling about at you that you're "spamming" and standing up for yourself in the face of that makes you aggressive?
Anyway, I guess you're choosing not to answer my question.  — Scott talk 22:21, 11 July 2024 (UTC)
Until you changed it earlier today, the revdel policy also stated that "material must be grossly offensive". Maybe RD3 should now be renamed to "purely and grossly disruptive material". — Ingenuity ( t •  c) 22:41, 11 July 2024 (UTC)
The "misuse" section of the preamble, not the criteria themselves which define the use of revision deletion, said that for revision deletion to be used, the "material must be grossly offensive". As I have pointed out multiple times now, that invalidates every single criterion except RD2. Somehow nobody noticed that since 2009 the revision deletion policy has been contradicting itself.  — Scott talk 22:54, 11 July 2024 (UTC)
From a review of his last 10 revdel's, Scott seems to understand RD2, but doesn't seem to understand RD3. We have never revdel'd run of the mill vandalism, and we certainly don't revdel 20 year old run of the mill vandalism. Contrary to Scott's claim, doing so is not long-established standard practice. I also agree with Ingenuity above that Scott's snarky attitude in response to a very reasonable request is unjustified. If he's just having a shitty day, then it's not a big deal; I've acted like a jerk when I'm having a bad day too. But it should stop, as should the RD3 revdels. Floquenbeam ( talk) 22:06, 11 July 2024 (UTC)
Hello Floq. If you're going to make a sweeping statement like "we have never... and we certainly don't..." then perhaps you could contribute some evidence towards that, perhaps in the form of a written policy which explicitly supports your interpretation, or a discussion which established consensus?
Regarding snark, if someone comes onto my user talk page with a shitty attitude then what do you expect? Come on now.  — Scott talk 22:14, 11 July 2024 (UTC)
Per above. RD3 is not for regular vandalism. These deletions should be reversed. – bradv 22:13, 11 July 2024 (UTC)
( edit conflict) Scott, I think you're the admin with the idiosyncratic view of what RevDel covers. Run-of-the-mill vandalism is reverted, not revdeleted. I don't believe the community has or ever would explicitly agree for it to be used this way, especially on lame throw away edits from years ago.-- Ponyo bons mots 22:14, 11 July 2024 (UTC)
Hi Ponyo. If you look at the RfC I linked to above, it was noted in the closing summary that "The overriding agreement appears that admin discretion still has strong support in these cases. But it was also generally agreed that most vandalism was out of scope for RevDel." [Emphasis in original.] Most vandalism certainly is out of scope, and I've used my discretion to hide a minority of purely disruptive rubbish that has no place on public view. This is in keeping with both the written policy and consensus as previously established.  — Scott talk 22:19, 11 July 2024 (UTC)
I don't see how the deletions highlighted by Sdrqaz cross the line between basic vandalism and "purely disruptive rubbish". It's just childish scrawling in comparison to the grossly inappropriate edits REVDEL is meant to cover. I think you have it wrong in this specific instance.-- Ponyo bons mots 22:28, 11 July 2024 (UTC)
Are you saying that basic vandalism isn't purely disruptive? Then what is it? Genuine question.  — Scott talk 22:31, 11 July 2024 (UTC)
If the community had as broad an interpretation as you as to what is purely disruptive, the policy would simply state that any vandalism is fair game for revision deletion. I repeat what I said above, the community would never approve such a liberal use of the tool. You appear to have dug in here; I'm not sure if there is any point in debating further. You are using an admin tool in a way that is not approved by the community and, based on your replies here, don't appear open to considering you may be incorrectly applying RD3. I really hope I'm wrong. You don't have to agree, but please consider that you might have it wrong.-- Ponyo bons mots 22:49, 11 July 2024 (UTC)
I'm open to considering it - that's exactly why we have collective discussions to elaborate upon and refine policies. You say "the community would never approve" - to add to what I've just said below to Floquenbeam, policy is set by what the community did approve. This seems like the perfect opportunity for another RfC on the topic to get the current consensus formalized, and ideally reflected in a well-written and unambiguous criterion to be understood and followed by all.  — Scott talk 23:15, 11 July 2024 (UTC)
Discretion is for borderline cases, it is not limitless. Just because you're an admin does not mean that you can do whatever you want because you have "discretion". Every admin who comments here is going to say they don't routinely revdel this stuff. That needs to mean something to you. If people revdel'd only stuff 10 times as bad as that, our revdel logs would still increase by several orders of magnitude. There are easily 100 more vandal edits on that page just as bad, and that's only one page. Among other reasons, we limit the use of revdel because non-admins can't tell what's going on, and that's a bad thing. We should only do it when removing the material being revdel'd is a bigger benefit than the cost of hiding revisions. More importantly, "Scott vs. All You Insane People" is not an appropriate approach. Consider the possibility that you drastically mistook the tone of the original message. I can assure you, for what it's worth, that you are the one who appears unreasonably aggressive there, not Sdrqaz. Floquenbeam ( talk) 22:32, 11 July 2024 (UTC)
Try reading what I wrote again. Sdrqaz's message to me was absolutely fine. I was talking about Thryduulf.
Anyway, regarding your comments - you've just illustrated how our admin corps aren't doing enough to suppress vandalism. I doubt that you could quantify "the cost" as it's entirely nebulous. Your argument also doesn't hold up - regular admins can't see what the higher level ones with oversight have hidden, and that's not a "bad thing" even though it's far less accountable.  — Scott talk 22:44, 11 July 2024 (UTC)
Ah, my mistake, I thought Sdrqaz started the thread on your talk page, his was just the last comment there. It is starting to make more sense why you assumed Thrydulf's initial comment was an attack, you had a recent run-in elsewhere. Anyway, you started out saying Thyrdulf was out of touch with long established procedures. Now the whole admin corps is out of touch with long established procedures? That's kind of impossible by definition. I will never understand why people can't just say "OK, my thoughts on this are apparently different than the consensus, so I'll suck it up and change what I do." Floquenbeam ( talk) 22:54, 11 July 2024 (UTC)
What can I say here? There are apparently loads and loads of people who seem determined to interpret one of our policies in their own way rather than following it to the letter as written, and their response to that is to do everything except take to the policy venues to clarify what exactly an ambiguous policy really means and establish a firm consensus. You say "long established procedures" and "the consensus", but so far nobody has managed to produce a single written record of these that trumps WP:RD3, which itself would be different as a result of such a consensus, by definition. 🤷🏼‍♂️  — Scott talk 23:07, 11 July 2024 (UTC)
I think we're probably done here, we're just going around in circles. Ingenuity answered your question. There is more to RD3 than the initial wording; the followup clarification counts too. Ponyo answered your question. And you don't need policy to determine "long established procedure", instead you look at what all the other admins have been doing long term. By definition. A bunch of non-Thryduulf admins have told you that no one interprets this the way you do. I don't think anyone is asking for grovelling, but if you continue to misuse RD3, someone is probably going to take you to ArbCom for misuse of the tool. You don't have to agree, but you should be aware. Floquenbeam ( talk) 23:14, 11 July 2024 (UTC)
I am aware, and I'm waiting for the one single person who actually cares about procedure enough to fix this weak criterion by kicking off the process which establishes consensus to narrow the wording. Until then, everything is just "well I think it means".  — Scott talk 23:18, 11 July 2024 (UTC)
If you decide to do this, please let me know. Floquenbeam ( talk) 23:26, 11 July 2024 (UTC)
I closed Wikipedia:Deletion review/Log/2024 June 28 recently and was struck by both Scott's tone (e.g., In summary, get stuffed.) and the fact that the deletion was unanimously overturned. I'm concerned that this is more than just a one-time issue. Extraordinary Writ ( talk) 22:15, 11 July 2024 (UTC)
Ah yes, when Thryduulf chose to call me a liar in public with absolutely zero consequences. I guess having been on ArbCom gives you a free pass exempting you from WP:AGF right? I can think of a whole bunch of people here who'd have responded with something far more fruity than "get stuffed".  — Scott talk 22:28, 11 July 2024 (UTC)
Perhaps the fact that not a single other person has taken issue with my describing intentionally leaving incorrect deletion summaries as "lying" should cause you to reflect that it actually is? Thryduulf ( talk) 22:53, 11 July 2024 (UTC)
Now that I see it, I take issue with it. For what it's worth. But Let's stay on track here. Floquenbeam ( talk) 22:58, 11 July 2024 (UTC)
If it isn't lying, what is it? Thryduulf ( talk) 23:01, 11 July 2024 (UTC)
Oh stop it. "Lying" has connotations that do not apply to every instance of "intentionally leaving incorrect deletion summaries" (note that I have no idea if even that is true, but assuming it is for the sake of argument), and you know it. You've been around long enough to know that calling someone a liar basically shuts down future legit discussion. Case in point: if anyone else had left an identically worded initial message on Scott's page, Scott possibly would have interpreted it differently, and maybe we wouldn't even be here. Floquenbeam ( talk) 23:08, 11 July 2024 (UTC)
Thank you.  — Scott talk 23:16, 11 July 2024 (UTC)
That's your response? Just doubling down? Absolutely incredible. Well, at least everyone can see your true colours.  — Scott talk 22:58, 11 July 2024 (UTC)
  • I do hope that we're not going to spend volunteer time on undeleting blatant vandalism for procedural reasons.— S Marshall  T/ C 22:40, 11 July 2024 (UTC)
    Yes, that would be silly. I'd be satisfied if the unnecessary RD3 revdel's just stop. Floquenbeam ( talk) 22:42, 11 July 2024 (UTC)
    ( edit conflict) I certainly wouldn't want to mandate that (or even recommend that), but if someone chooses to spend their time reversing out-of-process deletions I'm not going to spend my time complaining about it. Thryduulf ( talk) 22:52, 11 July 2024 (UTC)
  • I'm glad it's not just me who feels that these RD3 deletions were incorrect, in isolation not badly enough to merit more than a note that they have misinterpreted the deletion policy. However the tone of their responses here, on their talk page and in the recent DRV are grossly inappropriate. If they don't start listening then we'll have no choice but to go to arbcom and that would be a real shame as most of their admin work is correct and good, but the communication is that big a deal. Thryduulf ( talk) 22:52, 11 July 2024 (UTC)
  • This sort of revdel, if it were to become commonplace, would be highly disruptive to those of us who create edit filters, and for that matter, to the thousands and thousands of people who patrol recent changes. We need to see the big picture. We need to see patterns of vandalism. What's common enough to warrant a filter? What are the "tells" of that sneaky LTA? If everything disappears behind a struck-out diff, then we're just left reacting to what's in front of our nose. Now revdel is, sometimes, a necessary evil. The libeled BLP subject doesn't care about any of this, nor should they. But if you can't answer the question "what harm will come if J Random User views this diff?" the diff probably should remain visible. Suffusion of Yellow ( talk) 23:19, 11 July 2024 (UTC)
    Thank you for making a contribution to this debate based upon actual, quantifiable reasons. Although the instances of RD3 under discussion here were in application to 20-year-old vandalism, I'll commit to cease using it in such a fashion specifically on the basis of your demonstrated need, rather than that of the kind of unprovable assertions about the "true meaning" of a policy we've been seeing until now.
    As a side note, your comment completely demonstrates that the permissions you have are insufficient for the job. Filter managers should be able to see deleted revisions. Yes, I know the WMF's position on who gets that permission and I don't agree with it.  — Scott talk 23:49, 11 July 2024 (UTC)
    @ Suffusion of Yellow and Scott: On just the strict idea of what the WMF requires for access to deleted revisions, filter managers already arguably go through an election process (2 in fact, usually, since most filter managers have gone through an EFH consensus process as well). Now, I expect the idea of adding viewdeleted to EFM would likely end up mired in debate since it isn't necessarily RfA-level given there's usually only 10 people who actually follow the notice links that get posted to noticeboards whenever someone puts a candidacy up as a non-admin, but as a theoretical I somewhat wonder about the practicality of whether an RfC to add the rights would succeed. I guess that's a bit off-topic for this AN thread, though it would certainly help given that RevDelling revisions essentially roadblock any non-admin from building a filter regarding it. EggRoll97 ( talk) 04:25, 13 July 2024 (UTC)
    For a long time there was a bug where even admins couldn't see filter logs corresponding to revdelled edits! Not sure if that's been fixed. Suffusion of Yellow ( talk) 00:02, 12 July 2024 (UTC)
    Yikes. Well... I have minor feature requests for our admin tools on Phabricator which are old enough to go to secondary school now, so the pace of development in that area really isn't helping.  — Scott talk 00:22, 12 July 2024 (UTC)
    Hmmm, seems fixed now at least on testwiki. Suffusion of Yellow ( talk) 00:38, 12 July 2024 (UTC)
Do not endorse. 61 edit summaries in a row of all caps FUCK YOU FUCK YOU FUCK YOU.... maxing out the edit summary length is purely disruptive. Changing a redirect to HAGGER???? is normal vandalism. -- SarekOfVulcan (talk) 23:57, 11 July 2024 (UTC)
  • What I'm seeing here is an administrator who's not interested in using the tools on behalf of the community, but instead based on their own whims, and responds by attacking anyone who challenges their actions. Seems like a case of "would not be trusted with the tools if their RfA were today", but that's the nature of lifetime appointments. Even in the 2007 RfA, the support/oppose ratio dropped significantly based on temperament concerns. Thebiguglyalien ( talk) 00:15, 12 July 2024 (UTC)
    Cool attacks on my character! 👍🏻  — Scott talk 00:23, 12 July 2024 (UTC)
  • Quite apart from any questions about (mis)interpretations of RD3, I'm just perplexed why anyone would be concerned about vandalism from 20 years ago. Editors can focus on what they want--it's their time, after all--but why was this considered a priority over vandalism from, say, 20 minutes ago? That's by far the oddest part of all of this to me. Is it deliberately to make a point about the RD3 wording? I'm genuinely mystified. Grandpallama ( talk) 00:28, 12 July 2024 (UTC)
    "Why was this considered a priority over vandalism from, say, 20 minutes ago?" It wasn't. You do know that not everyone is patrolling things, right? I use tools exclusively in the areas that I'm working in.  — Scott talk 00:38, 12 July 2024 (UTC) P.S. I'll choose to ignore that intimation of bad faith on my part.  — Scott talk 00:40, 12 July 2024 (UTC)
    There was no intimation of bad faith; there was genuine puzzlement about why you would be concerned about something that is, by internet standards, ancient. What was the purpose? You didn't actually answer that question, you just responded with more snark. Whatever, I guess. Grandpallama ( talk) 02:24, 12 July 2024 (UTC)
    That wasn't snark. And regarding bad faith, you literally suggested the possibility that I was purposefully making a point violation. So yeah, whatever.  — Scott talk 10:42, 12 July 2024 (UTC)
    You do know that not everyone is patrolling things, right? is unambiguous snark. -- JBL ( talk) 18:00, 12 July 2024 (UTC)
    No, it isn't. Maybe spend less time on the angry noticeboards so they don't color your reading ability so much.  — Scott talk 18:18, 12 July 2024 (UTC)
    With all due respect, I think you may be dealing with a different definition of 'snark' than some of us. Cheers. Dumuzid ( talk) 18:25, 12 July 2024 (UTC)
    Astonishing. -- JBL ( talk) 18:48, 12 July 2024 (UTC)
I noticed one of the revdels on a page I worked on and it was a completely disproportionate reaction to juvenile harmless vandalism that took .2 seconds to revert. I don't get why, that's very clearly not what RD3 is written to mean (or else why would it except "most vandalism??"), so I have no idea what the motive even is here. What is the point of this except needlessly cutting parts out of the page history?
Of course if it's harassment-based vandalism that's a different thing, but I really don't think this is what RD3 is used for or meant to be used for. I prefer when page history is intact unless there is a dire need for revdel. PARAKANYAA ( talk) 00:47, 12 July 2024 (UTC)

I think all we're looking for from Scott is an acknowledgement that their interpretation of RD3 is out of step with current practice and that they'll change their approach going forward. This shouldn't escalate, and shouldn't have gotten this far in the first place. It's okay to be wrong and it's okay to admit it. Mackensen (talk) 00:41, 12 July 2024 (UTC)

Kindly read my response to Suffusion of Yellow. Thanks.  — Scott talk 00:46, 12 July 2024 (UTC)
I have to agree with Mackensen here, I think we just need a small change of perspective and maybe a little more time to do some calm learning. The defensiveness is a bit too far, but I'll hope that Scott is a little less aggressive in the case that a similar case occurs in the future. We all could take to heart a commitment to take things slower and more-open mindedly, myself included. The Night Watch (talk) 17:23, 13 July 2024 (UTC)

@ Scott: Perhaps this will help clarify the issue: how do you decide which vandalism (recent or old) warrants rev-deletion and which does not? Thanks, Newyorkbrad ( talk) 00:50, 12 July 2024 (UTC)

Short answer: vibes. Longer answer: gut feeling on on a combination of the questions "is there more than a fractional chance that this vandal would be motivated to return later to see the mess they made?" and "how annoying was the vandalism?" and "how jarring to the experience of someone looking through page history would it it to see the vandalism?"
Anyway, per my response to Suffusion of Yellow, this is now moot.  — Scott talk 00:57, 12 July 2024 (UTC)
Thank you for the quick response. I agree that Suffusion of Yellow made an important contribution to this discussion. Newyorkbrad ( talk) 01:01, 12 July 2024 (UTC)
No worries. It's 2am here (which to be fair is when I sleep a lot of the time anyway), so I hope that by the time when I check back in tomorrow there won't be lots more people who piled on without having read that.  — Scott talk 01:17, 12 July 2024 (UTC)

I'm hopeful that Scott's comment, "I'll commit to cease using it in such a fashion" will be enough for those who were looking for just such a commitment. After the dust settles a bit, we should have a discussion about the wording of our RD policy, as the "must be grossly offensive" line that Scott changed does in fact need some changing. If someone starts that up before me, I'd appreciate a ping. Firefangledfeathers ( talk / contribs) 01:17, 12 July 2024 (UTC)

My hope for settled dust was too optimistic, and the discussion has started already. Anyone interested should pop on over to WT:REVDEL#"Material must be grossly offensive". Firefangledfeathers ( talk / contribs) 02:06, 12 July 2024 (UTC)

I suggest we close this. As noted above, Scott has said he'll stop doing this. Editing WP:REVDEL to support his position was probably a troutable offense, but let's all just take a deep breath and move on to something productive. If Scott is true to his word, then no more need be said. If not, then we can take things from there. I would close this myself but the close script I use was thursday'ed a while back and I've long since forgotten how to close these things the manual way. If people want to get hot and bothered, breaking essential scripts might be a place to start. RoySmith (talk) 01:47, 12 July 2024 (UTC)

That's what I would have said a week ago at DRV, when there was the same level of aggressiveness/incivility in defending an action everyone agreed was well out of bounds. But now the same thing has happened again, just with a different policy. I guess it's good that Scott is going to defer to Suffusion of Yellow's demonstrated need, but I'm far from convinced that we're not just going to end up back here soon with a different form of the same problem. Hopefully I'm wrong. Extraordinary Writ ( talk) 03:36, 12 July 2024 (UTC)

I just came upon this thread during my daily skim-reading of these boards. I have a fairly unusual perspective here. Scott and I have talked about wiki-archaeology many times over the years and I actually had a discussion with him about this very issue back in 2022 (search for "That's actually led me to something else"). We were talking about the page Wikipedia:Deletion log/28 February – 19 July 2002 (then at the title Wikipedia:Old deletion log); here's the relevant diff and the log of revision deletion/undeletion. I'm relatively extreme about trying to preserve edits where possible and 100% agree with Suffusion of Yellow here, for slightly different reasons, and am glad that Scott has agreed to change his practices here. Graham87 ( talk) 04:29, 12 July 2024 (UTC)

Yeah. I mean setting aside the discussion about the letter and spirit of the law, you can boil down the whole issue to one of our software not being good enough. I think that vandalism should be hidden away (not "deleted" - the fact of the system being called "revision deletion" is just one of many issues with it) for two reasons: to deny recognition to vandals, and to minimize disruption to people reading page history. RevDel as it exists today is a crude and blunt tool with almost no nuance whatsoever. You have two options for a given unit of data (actor, revision text, edit summary) - leave it on public view, or punt it into the Phantom Zone where only admins can read it. There's no gradation that can be applied when hiding revisions.
By contrast, consider a system where applying, for example, RD2 would make an item inaccessible to anyone without elevated privileges, but RD3 would hide it behind an additional interface element until a button is clicked. Minimal visibility for disruptive material without presenting any barrier to edit filter managers, recent changes patrollers, etc. This isn't a new idea at all: various social media apps have had it for a long time in the form of "hidden replies". Even in the current system, we could unbundle the right to see hidden revisions and give it to reasonable interested users so that staying tidy doesn't impede research. I believe this actually was the case with the "researcher" user group until the WMF nixed it for some reason? I didn't hear about it until afterwards.
Similarly, other objections raised above included noise in the logs... once again utterly trivial to resolve technically. But the WMF has chosen to spend its giant budget on "increasing engagement" features, and leave our tools languishing pretty much exactly where they were fifteen years ago. The sheer amount of precious human time wasted by having to both use our incredibly out of date tools and debate extensively about the way to use them because of how crude they are is heartbreaking.
By the way, it's "them" now rather than "him". 😊  — Scott talk 10:32, 12 July 2024 (UTC)
Sorry about the misgendering. Revision deletion is a great improvement on what was previously the only option, selective deletion. You were editing Wikipedia (but not yet an admin) when even that wasn't an option. This is the wrong place to debate the merits of hypothetical revision hiding options, but I don't really see the use of such gradation; I'd maintain that most people don't even look at page history and many readers understand that minor vandalism is often part of the life-cycle of Wikipedia pages (we even have a main namespace article on the topic). Graham87 ( talk) 14:36, 12 July 2024 (UTC)
No need at all to apologize. Yeah, I'm sure there's a better venue to talk about it than here. But you're quite right in that selective deletion was a massive pain in the neck and RD's arrival in 2009 really helped. Just now that we're 15 years down the line, I personally reckon it's overdue for a rethink based on lessons learned.  — Scott talk 18:11, 12 July 2024 (UTC)

IMO there was a problem of too broad of use of the tool and Scott has agreed to change accordingly. I think we're done here. North8000 ( talk) 18:26, 12 July 2024 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Some Help with Bot-Like Editing

I ran into OpalYosutebito with this edit. They were trying to address a citation error by removing |agency= from {{ Cite journal}}, but also removed all other |agency= parameters from the other citation templates (which are valid parameters in those templates). I reverted and left a message, but then looked at the user's edits and saw what appears to be an abuse of AWB with bot-like editing. Over a recent 40 minute period, they completed 499 edits making AWB changes to unsupported parameters (about 12 edits a minute). However, looking at these edits, they are either making mistakes (like the one I noted above or this one) or are removing valid reference material from the citation template that should be fixed, not outright deleted. As an example this edit, the template should be changed to {{ Cite news}}, which would correct the issue while retaining the correct parameter. There appears to be hundreds, if not thousands of recent edits that could be introducing issues like this. My gut says they all just need to be outright reverted. I removed the user's AWB privileges for now and was close to blocking for running an unapproved bot, but just don't have the time to dive into this anymore today. Can another admin take a look and review my actions so far, and take additional ad warranted? Thank you! « Gonzo fan2007 (talk) @ 15:25, 12 July 2024 (UTC)

(Non-administrator comment) Checking OpalYosutebito's contribs, they appear to have begun self-reverting, which is certainly called for. Unsupported parameters in citation templates almost always contain valid bibliographic information, and are usually the result of bot action, template updates, or translations from a sister project. Just removing them rather than attempting to incorporate the information properly into the citations is incredibly destructive.
I'll keep looking, if I can remember, since an AWB run this ill-conceived and deleterious may require a mass rollback while the edits are still fresh. Folly Mox ( talk) 23:29, 12 July 2024 (UTC)
(Non-administrator comment) I'm about halfway done with fixing the mistakes I made. They're my errors, my responsibility - OpalYosutebito ( talk) 22:29, 13 July 2024 (UTC)

98.115.164.53's Numerous Minor Edits

98.115.164.53 ( talk · contribs · WHOIS)

This editor has made numerous minor edits to articles. Most of them seem innocuous, but others, particularly the ones that remove terms like "to date," seem problematic for contextual POV. There seem to be hundreds of account-less edits, despite the suggestion to create an account already being made, but what do I know.

This user made a personal attack [20] after I reverted their edit on a page I had watchlisted. And then they put their edit back [21].

So far, they seem to have stopped editing for now, after being warned. I've gone through some edits to see what edits can go or stay, but they're just too numerous. Anyone have thoughts on what to do next?⸺ RandomStaplers 19:57, 12 July 2024 (UTC)

You could ignore the user and move on. If the edit is truly problematic, you could revert it anyway, and/or you could ask an administrator to protect the page. 98.115.164.53 ( talk) 20:08, 12 July 2024 (UTC)
What of the middle line in the report, the one where they say that they did revert one of your edits and you personally attacked them back and restored your edit?
Also, are you saying that the way to stop you from making problematic edits is to protect the pages you're being problematic in? Are you unwilling to change or discuss your behaviour?
2804:F14:8081:3201:9827:3072:74BC:2770 ( talk) 20:22, 12 July 2024 (UTC)
  • 98.115.164.53, what account or accounts have you used here and are any of those accounts currently blocked? -- Yamla ( talk) 20:26, 12 July 2024 (UTC)
    @ Yamla I've opened a checkuser request. [22]RandomStaplers 20:29, 12 July 2024 (UTC)
    98.115.164.53 is CU-blocked by Ponyo. -- Yamla ( talk) 20:39, 12 July 2024 (UTC)
    @ Yamla IP 2804:F14:8081:3201:9827:3072:74BC:2770 has responded to the CU request.⸺ RandomStaplers 20:40, 12 July 2024 (UTC)
  • @ Yamla I'm looking through the edit filter log... this person was tripping rate warnings left and right. It's amazing this person wasn't caught sooner.⸺ RandomStaplers 21:12, 12 July 2024 (UTC)

Arbitration motion regarding Durova

The Arbitration Committee has resolved by motion that:

Principle 2 of Wikipedia:Requests for arbitration/Durova, Private correspondence, is changed from
2) In the absence of permission from the author (including of any included prior correspondence) or their lapse into public domain, the contents of private correspondence, including e-mails, should not be posted on-wiki. See Wikipedia:Copyrights.
to
2) In the absence of permission from the author (including of any included prior correspondence), the contents of private correspondence, including e-mails, should not be posted on-wiki.

For the Arbitration Committee, SilverLocust  💬 23:23, 12 July 2024 (UTC)

Poggies. jp× g 🗯️ 06:38, 13 July 2024 (UTC)
Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard § Arbitration motion regarding Durova

my discussion was deleted

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


@ Antandrus closed my discussion because someone accused im a banned user. im not. please revert the closure /info/en/?search=Talk:September_11_attacks Gsgdd ( talk) 06:18, 13 July 2024 (UTC)

i have made valid arguments which merits discussion. it shouldn't be closed because of pure accusations. is there any proof im banned? can two people not have same idea? Gsgdd ( talk) 06:20, 13 July 2024 (UTC)
The discussion was closed, for reasons, none of which was anything to do with the allegation that you are a sock account. You made a proposal and virtually all the respondents disagreed with you. Therefore the closure was simply that your proposal did not gain a consensus.
Please don't try and relitigate the same argument here, it won't get any traction. Nthep ( talk) 06:32, 13 July 2024 (UTC)
There is one editor who didn't disagreed. I'm trying to build consensus. why are you trying to block it? Gsgdd ( talk) 06:36, 13 July 2024 (UTC)
and one editor opposed. what are you talking about ? Gsgdd ( talk) 06:38, 13 July 2024 (UTC)
also there is no Consensus to delete it. i accidentally put rfc tag - which i removed and it shoudnt be the cause of deletion. then another user accused of being a blocked account Gsgdd ( talk) 06:45, 13 July 2024 (UTC)
Thanks for raising this, but unfortunately this isn't the place to resolve your concern. The issue is a content dispute and the close was not an action requiring admin tools. It's not within the scope of this noticeboard to overturn content decisions. If you disagree with the consensus outcome please do feel free to seek a new consensus at the article talkpage in due course (ie not today or tomorrow or next month but eventually). Please note you will probably need to have new reliable sources that back your view, or an alternative set of words to propose which might gain more support than that available in this current RfC. -- Euryalus ( talk) 06:53, 13 July 2024 (UTC)
see this is a controversial topic. obviously people who follow this page will be quick to disagree. i need more time. i made some mistakes in the arguments, but its a learning process. i need to know people objections so i can research how to refute them. where can i seek arbitration ? Gsgdd ( talk) 07:04, 13 July 2024 (UTC)
also an admin blocked closed it. Gsgdd ( talk) 07:08, 13 July 2024 (UTC)
You don't need to be an admin to close an RFC, so this close is really just by Antandrus in their capacity as an experienced regular editor. I get what you're saying re more time to prepare arguments, but ideally the argument is fully prepared before opening the RfC rather than during it. There really didn't seem to be much support for your proposal, but if you do have some additional arguments or sources to present than maybe put them together over time (say, a few months?)and feel free to re-test consensus for the word "Islamist" in a future talkpage discussion or RfC. -- Euryalus ( talk) 07:15, 13 July 2024 (UTC)
why do i have to wait few months. i already have reliable sources https://www.brookings.edu/articles/rethinking-language-islamism-as-a-dirty-word/ and others to support my arguments... this is crazy - why my voices are being shut down and prevented from being heard Gsgdd ( talk) 07:23, 13 July 2024 (UTC)
Per this policy section, consensus can change but repeated or rapid attempts to relitigate the same issue can be a bit disruptive. As above I get that you hadn't fully assembled your arguments before posting the rfc. That's unfortunate as maybe it would have led to a different outcome. Or maybe not. Either way it's probably better to take some time putting those arguments together and then starting a new discussion in due course, versus starting a new RfC or discussion on the same topic immediately after the previous one has closed. -- Euryalus ( talk) 07:37, 13 July 2024 (UTC)
I took part in the thread the OP is complaining about. They wanted the 9/11 hijackers to not be described as "Islamist". Around 6 or 7 editors were against the OP. One editor made a compromise suggestion which involved retaining the word but the OP rejected that. No one supported their proposal. They say above "one editor opposed". That is the same WP:IDHT we saw on display from them in that thread. I think they are best advised to follow WP:STICK rather than keep pursuing. DeCausa ( talk) 08:08, 13 July 2024 (UTC)
The strength of arguments is crucial in the consensus process. no one other than you has made a strong case. so please stop that 6 or 7 editors against me argument Gsgdd ( talk) 08:19, 13 July 2024 (UTC)
Many people commented for sure, probably disapproved. but no valid reasoning imo Gsgdd ( talk) 08:19, 13 July 2024 (UTC)
anayway... ill be back after sometime Gsgdd ( talk) 08:29, 13 July 2024 (UTC)
You, as proposer, are not arbiter of what reasoning is valid or not. Acroterion (talk) 13:05, 13 July 2024 (UTC)
As Astropulse, to be clear. Doug Weller talk 15:18, 13 July 2024 (UTC)
Both those are ironic statements given that your argument in the thread was that we shouldn't be following the RS: " Just because RS promote hatred,racism etc.. does it mean wiki should do it as well?" DeCausa ( talk) 10:30, 13 July 2024 (UTC)
What makes you think the discussion was closed because someone accused you of being a banned user? There is nothing about that in the close. Phil Bridger ( talk) 08:56, 13 July 2024 (UTC)
One person wanted the word "Islamist" removed, no one agreed with them, but instead of letting it go it went on and on and on, and on, and I closed it. All in a day's work. And no, this had absolutely nothing to do with a suggestion this was a banned user (I personally don't think it is, but did not look into it). Also (as above) this was not an administrative action. Antandrus (talk) 14:45, 13 July 2024 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Misuse of Revdel

Recently, several revisions were deleted using Revision Deletion (Revdel) by AirshipJungleman29 in Draft:Gupta–Hunnic Wars, which I humbly believe they were not justified properly as they only found close paraphrasing in "The Huna Volkerwanderung" section and "Rise of Kidara Kushans" sub-section [23]. I'd rewrite the whole contents in these section/subsection but kindly please restore the appropriate contents so that I do not need to spend a lot of time to re-write it for months all over again. Also the user has only found few scanty grammatical mistakes in such a massive article but it was still drafted by them which was quite harsh in my humble opinion. I would like to request any admin to help me in restoring this article, because I have earnestly worked a lot before and spent months for the article already. Thank you. Jonharojjashi ( talk) 13:58, 14 July 2024 (UTC)

AirshipJungleman29 is not an administrator and can not delete revisions. I have notified them of this report. ScottishFinnishRadish ( talk) 14:02, 14 July 2024 (UTC)
The revdeletions were performed by Robertsky. — Cryptic 14:09, 14 July 2024 (UTC)
@ Jonharojjashi:(Non-administrator comment) That will not happen. That—substantial—chunk of text was a verbatim copyright violation which is an absolute on Wikipedia. See Wp:COPYRIGHT, which is a policy policy with legal considerations. For why it will not be restored, see WP:UNDELETE: Copyright violations and attack pages will not be provided. In any case, since the source and text were effectively the same, you only need access to the original to rewrite in your own words. But it cannot be hosted anywhere on Wikipedia—talk pages, draft, email—as the deleting admin— Robertsky—would have told you had you asked.
In fact, instead of relitigating it now, at a noticeboard, it would be more productive to simply take AirshipJungleman29's original advice and "take this issue seriously in the future". ——Serial Number 54129 14:17, 14 July 2024 (UTC)
@ Serial Number 54129 Yes I know that the section "The Huna Volkerwanderung" and sub-section "Rise of Kidara Kushans" are highly identical and I'd rewrite it in my own words, but what about the rest of the article? Even the attributed contents from parent articles were not spared. The article was massive and it's possible that there would be some grammatical mistakes and copyright violation but instead of removing the particular concern they have deleted more than 120k bytes of contents. I am not asking for restoration of those closely paraphrased section/sub-section but the restoration of the fair contents, please look into this. Kind regards. Jonharojjashi ( talk) 14:51, 14 July 2024 (UTC)
That's not possible. Specific sections of a page can't be revision-deleted, only entire revisions. — Cryptic 14:53, 14 July 2024 (UTC)
So I guess I have to manually restore non plagiarised contents? Jonharojjashi ( talk) 15:21, 14 July 2024 (UTC)
I have nothing further to add to Serial Number 54129's comment above. They have stated in a succinct manner what I would have conveyed. – robertsky ( talk) 01:43, 15 July 2024 (UTC)
  • The examples listed by AirshipJungleman29 at the talkpage are egregiously bad; essentially close-paraphrasing by (nonsensical) word-substitution. Given Jonharojjashi's poor record of content-creation in the IPA-history topic-area (see their talkpage, including several copyvio-related notices) and the amount of effort required to save their work on a notable topic from deletion (see this AFD), I believe a topic-ban or block from mainspace should be considered. Abecedare ( talk) 14:32, 14 July 2024 (UTC)
    I agree, Abecedare. Unfortunately, a topic ban the simple way (=placed by one uninvolved admin) seems to be off the table, since Jonharojjashi has not been alerted to the contentious topics restrictions, or even to discretionary sanctions. A pity. A topic ban by the community (=placed by consensus at this board) would be an unreasonable hassle and waste of time, IMO — there has been enough waste of the community's time by this user, surely. Therefore, I recommend an indefinite block from article space, which can be appealed in the usual way on their page, or, no sooner than in six months, to the community at this board. Bishonen | tålk 18:23, 14 July 2024 (UTC).
    Agree w/ Bishonen. Enough time has passed, and enough energy has been wasted. You can PB at will can't you? Carry on, captain. ——Serial Number 54129 18:33, 14 July 2024 (UTC)
    @ Bishonen: Jonharojjashi was alerted of IPA DS in Aug 2023, so a (non-community imposed) topic ban remains an option. Abecedare ( talk) 18:43, 14 July 2024 (UTC)
    Ah, I missed that. I've never seen such an alert not appear in the edit summary before - I thought that happened automatically. Well, in that case... do you think a t-ban or a mainspace block would be best and most relevant to the disruption, Abecedare and Serial Number 54129? Bishonen | tålk 19:52, 14 July 2024 (UTC).
    @ Bishonen: IMO a topic-ban would be preferable in order to not simply shift the burden of spotting copyright, paraphrasing, POVforking, source quality and source misrepresentation issues onto AFC reviewers. See this, this, this and the many abandoned drafts to get an idea of the concerns that have been previously raised. Abecedare ( talk) 20:15, 14 July 2024 (UTC)
    I hear you, Abe. On the other side, blocks are conveniently self-enforcing, while the user has ample opportunity to violate a topic ban through (perhaps innocently) misunderstanding how it works. I'm going by the difficulties they have demonstrated in understanding our copyright and sourcing policies. But you're right, a mainspace block wouldn't be fair on AFC reviewers. I have topic banned Jonharojjashi from India, Pakistan and Afghanistan. Bishonen | tålk 21:01, 14 July 2024 (UTC).

Error on page - Cannot add topic

https://en.m.wikipedia.org/wiki/Disappearance_of_Joshua_Guimond

I apologize if this is the wrong way to go about reporting this. I have never actually done this on Wikipedia before. On the page titled "Disappearance of Joshua Guimond" it states:

Around the time of the disappearance, there were two reports of a man driving an orange Pontiac Sunfire on campus, dropping off other men. Before the disappearance, when campus security approached the vehicle, one of the men who were dropped off ran away. After the disappearance, the driver was contacted, and he gave no more information than saying the car was destroyed.[30]

However, the article that is linked as reference# 30 makes no mention of this at all. I have been unable to find the correct article that mentions this info about that car being destroyed.

I attempted to add a topic on the Talk page as recommended, however there is no topic button on the Talk page and it seems as if the Talk section is prohibited for some reason. 71.251.236.155 ( talk) 22:40, 14 July 2024 (UTC)

I'm sorry you were unable to start a conversation on the talk page, no idea what's up with that. The cited ref actually does support the content (open ref #30 and do a find for "orange") but it's badly worded in the article so I'm going to update that. Schazjmd  (talk) 22:58, 14 July 2024 (UTC)
  • ( edit conflict) Hi, welcome to Wikipedia. I'm sorry you couldn't add a topic to the talk page. There's nothing the matter with the talk page. The problem is that our mobile interface doesn't work properly. Reference #30 (which is this article) does say the driver gave no more information and the car was destroyed. Both pieces of information are in the third paragraph from the bottom.— S Marshall  T/ C 23:00, 14 July 2024 (UTC)

Problematic rollover text

On this page /info/en/?search=I_can't_breathe The first hyperlinked instance of "George Floyd" in the section George Floyd shows text "George Floyd" when logged in, but an entirely different and problematic rollover preview when not logged in. I'm unable to figure out how to erase it myself. Eunoia666 ( talk) 22:45, 14 July 2024 (UTC)

Are you still getting this? (It was caused by vandalism to George Floyd, now reverted and revdeleted.) I'm properly seeing the preview of the unvandalized article both logged-in and -out. — Cryptic 23:04, 14 July 2024 (UTC)
Main case page ( Talk) — Evidence ( Talk) — Workshop ( Talk) — Proposed decision ( Talk)

Case clerk: Hahc21 ( Talk) Drafting arbitrators: Worm That Turned ( Talk) & David Fuchs ( Talk)

Arbitrators active on this case

Active:

  1. AGK
  2. Courcelles
  3. David Fuchs
  4. Newyorkbrad
  5. NuclearWarfare
  6. Salvio giuliano
  7. SilkTork
  8. Timotheus Canens
  9. Worm That Turned
  10. Carcharoth

Inactive:

  1. Roger Davies

Recused:

  1. Risker
  2. Kirill Lokshin

PD update

Giving a heads-up that at this point it's unlikely the PD will be posted tomorrow today. We'll keep you appraised of any other delays. Der Wohltemperierte Fuchs( talk) 03:31, 14 August 2013 (UTC)

Yes, apologies for that. We hope to have it ready soon. WormTT( talk) 07:35, 14 August 2013 (UTC)
  • Thank you both for keeping us updated - I appreciate that. — Ched :  ?  16:14, 14 August 2013 (UTC)
  • Same here. Lord Sjones23 ( talk - contributions) 16:24, 14 August 2013 (UTC)
  • Thank you, this is exactly the sort of communication that takes almost no effort but goes a long way towards maintaining good relations :) Thryduulf ( talk) 17:53, 14 August 2013 (UTC)
  • Thank you, that gave us time to ponder another of Andy's good ideas (and to experience more reverts), awaiting The Judgment ;) -- Gerda Arendt ( talk) 07:18, 15 August 2013 (UTC)
As a form of update, we've punted a working draft of the PD over to the committee as a whole. Giving ample time to wordsmith and fine-tune things, and in the spirit of under-promising I hope to have the full PD posted by early Saturday UTC if not sooner. Der Wohltemperierte Fuchs( talk) 14:55, 15 August 2013 (UTC)
Very good. Lord Sjones23 ( talk - contributions) 16:01, 15 August 2013 (UTC)
Take all the time you need - better to make the right decision than to rush, after all. Ritchie333 (talk) (cont) 17:47, 15 August 2013 (UTC)
  • It's a bit harsh to label the IP an "edit warrior" for one reversion when Pigsonthewing has ignored WP:BRD and reverted against the status quo twice... - SchroCat ( talk) 11:50, 16 August 2013 (UTC)
  • see also, stay calm and factual, - forgive me for seeing a team at work, I must be biased, -- Gerda Arendt ( talk) 12:01, 16 August 2013 (UTC)
  • I am calm and factual, and yes, you are biased, as am I, but throwing around accusations of edit warring against people cranks up the tension in a debate, not defuses it. - SchroCat ( talk) 12:08, 16 August 2013 (UTC)

Ched comment 1

  • First: I will be having some strongly worded comments on this PD in the near future.
  • Second: per "As Gerda has herself noted, she's been adding far more infoboxes as of late than Pigs; it hasn't been very constructive, especially when adding ones unilaterally is clearly going to create a kerfluffle. Der Wohltemperierte Fuchs(talk) 02:01, 17 August 2013 (UTC)" ... I would kindly request that David refrain to referring to the editor as "Pigs". I would suspect that Andy, or PotW would be acceptable, and I am familiar with the moniker that Andy has chosen; still, I think it is quite unbecoming to shorten the user name in the fashion that you have. Please make appropriate adjustments. Thank you. — Ched :  ?  02:22, 17 August 2013 (UTC)
  • Also: "Gerda Arendt is indefinitely restricted from removing | or |" ... I'm pretty sure Gerda will agree to refraining from removing infoboxes. typo? — Ched :  ?  02:45, 17 August 2013 (UTC)
    • Thanks for the catch. I malformed the very end of the PD in my initial copy and paste. Der Wohltemperierte Fuchs( talk) 03:01, 17 August 2013 (UTC)

PSky comment on the most one-sided decision ever

Hmm, let's see, you smack Andy and Gerda, the pro-box side, and leave the anti-box side, Klein and Smerus, totally alone? Do you guys realize it takes two sides to have a dispute, edit war, etc, and that Klein and Smerus deserve smacking far more than Gerda? This is the most one-sided decision ever. I'd ask if this PD was a joke, but nothing AC does anymore surprises me. I didn't think my opinion of AC could get lower but it just did. An editor with one-month wiki experience could have written a better decision. As far as I'm concerned, AC should be abolished; and in case you missed it, I've said that before onwiki. PumpkinSky talk 02:55, 17 August 2013 (UTC)

I think the proposal to sanction Gerda is ill-founded, even though I disagree with every infobox she's added at classical music-related bios. If she had been edit warring over infoboxes, yes, or if she'd repeatedly proposed infoboxes at the same article ad WP:IDHT, yes, but I've seen no evidence of such behaviour. Adding infoboxes to articles where it's likely to be controversial strikes me as bad practice, but I know of no policy it breaches. Sanctioning people for bad practice is not the way to go. Having said that, we do only have one arb currently supporting this sanction, and NYB seems to be questioning the FoF supporting the sanction, so this doesn't seem like a done deal. I hope the other arbs will read this and consider when voting. Heimstern Läufer (talk) 03:55, 17 August 2013 (UTC)
May I add here that I never added an infobox where I expected it to be controversial. I stand corrected in several cases, mostly operas where I still believe an infobox on the given works would be superior to a side navbox duplicating information from a footer navbox, illustrated in The Ban on Love. I don't recall adding any infobox to a classical music bio unless I wrote the article myself. I would not call "reignite" to point out that factually looking at The Rite of Spring might be a good idea, -- Gerda Arendt ( talk) 15:15, 17 August 2013 (UTC)
I agree with the AC proposal. It's the relentlessness which Gerda has shown in starting multiple infobox debates which is the problem. She's even tried to reignite some of the most contentious disputes (e.g. Rite of Spring, Georg Solti) while this Arb Case was open. -- Folantin ( talk) 08:12, 17 August 2013 (UTC)
I would like to understand what you mean by reigniting. I used The Ban on Love as an example how consensus could be achieved (or - so far - not). Only after The Rite of Spring was mentioned in the discussion did I also show that one. As for Solti, I have no idea what you mean. I approached an author of a TFA with the proposal of an infobox, he wanted me to insert it and I asked him to do it himself as I could be banned for disrupting the TFA. Is that what you summarize as "reignite"? For the whole case, I hoped for more looking at the actual evidence, rather than going by such summaries. -- Gerda Arendt ( talk) 15:25, 17 August 2013 (UTC)
The Georg Solti dispute had lain dormant since December 2012. You attempted to re-ignite the dispute on 2 August. You solicited an unsuspecting fellow editor to re-open the debate on the Georg Solti infobox: [30]. You must have known how inflammatory this was as this was one of the two pages which earned Pigsonthewing his topic ban on TFAs. Your comment even demonstrates you were aware of this. The other user went ahead, re-activating a debate which had been dormant for eight months: [31]. You then thanked him and tried to get him to do the same for Carmen [32]. -- Folantin ( talk) 15:30, 17 August 2013 (UTC)
We use the very same diff, only you see it differently. I explained that I could not do add the box because of a danger that I illustrated, - the danger is what I was aware of. What he did was a complete surprise to me, unsolicited. I did not comment on Georg Solti, not then, not now. -- Gerda Arendt ( talk) 15:36, 17 August 2013 (UTC)
No, you said "the editor who disrupted Georg Solti 25 July 2012 (mind the year!) is threatened to be banned." That's clearly Pigsonthewing, not you. -- Folantin ( talk) 15:41, 17 August 2013 (UTC)
That's what I said, meaning that I - if I disrupted the TFA of that day, Duino Elegies - might be treated the same way. Do I have a language problem? - How is that "reigniting" and "inflammatory"? -- Gerda Arendt ( talk) 15:47, 17 August 2013 (UTC)
That makes no sense to me. It's clear from those comments you were pleased the Georg Solti debate had re-started and wanted the same to happen with Carmen. -- Folantin ( talk) 15:50, 17 August 2013 (UTC)
I invite everybody to look. -- Gerda Arendt ( talk) 16:00, 17 August 2013 (UTC)
I too invite neutral observers to look. -- Folantin ( talk) 16:02, 17 August 2013 (UTC)
I'm rather inclined to agree with PSky on this. There is no sanction for those on the anti side, despite the principles explicitly rejecting tactics used by that side far more often than the pro side. The evidence shows that there is no way of telling in most cases what will be controversial until one of the anti people show up to a debate, making some proposed remedies unworkable in practice. Finally it sets up the classical music and opera projects as a walled garden where the normal rules of Wikipedia discussions about content do not apply, and you're banning Andy and Gerda to enforce it! This really is the most inappropriately one-sided outcome I've ever seen from ArbCom and I've been observing it for years. Please go back and try again. Thryduulf ( talk) 09:28, 17 August 2013 (UTC)
@Folantin, Klein and Smerus have been doing that too during this case so where's the difference? There is none. This is the worst AC group ever and I no longer recognize their legitimacy. @Thryduult, precisely, the only-pro-side sanctions violate the very walled garden principle they've posted because it sets up the anti-side as a walled garden just as you've said. PumpkinSky talk 10:01, 17 August 2013 (UTC)
"Klein and Smerus have been doing that too during this case". No they haven't. Kleinzach has barely edited Wikipedia during this case as you well know. -- Folantin ( talk) 10:35, 17 August 2013 (UTC)
Yes they have. Even if not, they most certainly did during the events leading to this, so again where's the difference? PumpkinSky talk 11:32, 17 August 2013 (UTC)
Unless you can back your accusations, you should stop repeating them. This case began on 17 July. Where have they been "starting multiple infobox debates" during that time? Kleinzach has made precisely five edits to Wikipedia during this period, two of them to your user talk page. -- Folantin ( talk) 11:41, 17 August 2013 (UTC)
I'll say whatever I want. And how convenient of you to ignore my last question. PumpkinSky talk 11:53, 17 August 2013 (UTC)
Your lack of concern for factual accuracy is duly noted as is the fact you appear to be the founder of WP:QAI. -- Folantin ( talk) 11:56, 17 August 2013 (UTC)
Oh? And your clear bias and lack of concern for factual accuracy is also duly note; you did clearly ignore my question about their behavior leading to this case. We clearly won't agree so let's just move on. But also note the other two commenting here seem to agree with me. PumpkinSky talk 12:01, 17 August 2013 (UTC)
You clearly have no evidence for your claims. I'm going to supply some regarding Gerda Arendt during this case. -- Folantin ( talk) 12:15, 17 August 2013 (UTC)
Can we please stop? If you want to discuss about something not related to the case, like you've been doing in your latest four posts, there are more suitable places than the Proposed decision talk page. Thanks. — ΛΧΣ 21 14:54, 17 August 2013 (UTC)
It's relevant to what David Fuchs says on the Proposed Decision here [33]. -- Folantin ( talk) 15:17, 17 August 2013 (UTC)
I agree with PunkinSky's surprise (while not agreeing with all points.) The AC felt the need to include the Levels of consensus principle. Did the committee miss that the very reason this needs to be asserted is the wholesale violation of the principle by many editors who invoked local consensus to remove infoboxes? Those removals, without citation of an actual policy, led to much frustration by Andy. While he did not handle it well, is it really the case that the committee finds nothing to say to any of the editors practicing it? Not a ban, not an admonition, not even a reminder?-- SPhilbrick (Talk) 21:24, 18 August 2013 (UTC)
Just as Andy may have been frustrated by the non-policy removal of infoboxes that he added, so those on the other side were frustrated by the initial non-policy addition of the infoboxes. A wikiproject does not own an article, but likewise a group promoting infoboxes does not own the top-right corner of the page. Rather than relying on attrition, the proper procedure for anyone wanting to spread infoboxes would be to establish a policy that an infobox cannot be removed. Johnuniq ( talk) 04:51, 19 August 2013 (UTC)

Request for evidence relating to Kleinzach and Smerus

PumpkinSky has suggested that the committee is wrong not to bring findings and remedies against Kleinzach and Smerus. However, little or no evidence has been submitted against these editors. Therefore, if anybody knows of any such evidence, I would request that they (pithily) submit it below. Unless it is entirely unavoidable, a simple list of diffs followed by your signature will be sufficient. Thank you, AGK [•] 15:19, 23 August 2013 (UTC)

I have intentionally not supplied any evidence against (!) any editor, many of whom I respect, and still don't want to do that. (Was it a mistake? I am interested in understanding, not "remedies".) I have supplied ample evidence for (!) an editor, Andy, and would like that to be considered. The shortest way is my list of "systematic" reverts/changes of infoboxes, most of them in 2013. I trusted that the arbs are able to read a version history such as Sparrow Mass. The latest revert was yesterday, BWV 71: an infobox that I added and Nikkimaria edited was reverted by Eusebeus, see talk and history. -- Gerda Arendt ( talk) 15:36, 23 August 2013 (UTC)
I have VERY limited time today, and limited internet access on weekends, but I will begin to go back through things. These two are subtle in their slaps, but the use of the old "with all due respect" phrasing should not keep folks from seeing the snide snaps and snarks going on here. Montanabw (talk) 20:53, 23 August 2013 (UTC)
More to come as I have time. Montanabw (talk) 20:53, 23 August 2013 (UTC)
  • To note that I plan on offering alternatives and/or new remedies and FoF this weekend. If you have any final comments I would make them soon. Der Wohltemperierte Fuchs( talk) 23:15, 23 August 2013 (UTC)
  • We are pandering Satan here by suggesting the things plainly seen are not even viewable unless restated here with a diff. It is much better to pardon the server load than to provide additional web hosting; for the sake of redundancy. This; compounded with intentions of an unwanted hammering sanction; in clear contrast of the community's desire, and indeed, her needs! We ask for guidance on protocols of civil discussion; expecting usable precedent to enhance our ability to move beyond impasse, with propriety to Wikipedia's institutional aims. We can agree to disagree (called no consensus), and close a discussion by default, to some neutral parameter; like the preference established by the earliest contributor, quite often the article's creator. This works for everything from the serial comma, to measuring time itself. Let me attempt to convey this in succinct candor; We don't really need sanctions here, we need authoritative guidance. If a sanction must levy; employ the "swift kick sanction"—that's the one where after self administering a swift kick in the ass, we see the light and get it right. :)  John Cline ( talk) 06:44, 24 August 2013 (UTC)
  • I support that view. I said so already in the workshop phase. Repeating in optimism some don't understand: We need to find a better way to discuss, and sometimes accept "no consensus", - not exclude excellent contributors with valid arguments from the discussion. I supply two diffs, both by uninvolved editors of this case, as food for thought:
  • Infoboxes are useful tools that should be encouraged in classical music articles. They sum up the main points of an article, allowing for readers of these articles (such as myself) access to some of the most commonly sought-after material. That they be in standard place in most articles would allow readers an easy go-to place for birth/death dates, places of occupation, and a general synoposis of the individual. I feel some in the classical music wikiproject get offended thinking that infoboxes encourage readers to skip over some admittedly great articles. But those who come here just to see a basic sketch of an individual aren't going to read the article from top to bottom. Those who do that will continue to do so whether or not there is an infobox present. Infoboxes, written correctly (omitting information that cannot be summarized, such as which "period" Beethoven belongs to), offer no drawbacks to an article and quite a few benefits. 10 August 2012
  • Consensus does not mean that stupidity and ignorance be given equal weight to common sense and knowledge. 22 August 2013
-- Gerda Arendt ( talk) 08:03, 24 August 2013 (UTC)
  • Not only for this case, but the future, I started a list of frequently raised concerns against infoboxes and what I would answer. It seems not well known that Kleinzach, mentioned above, said "I have no objection per se to boxes for compositions," and initiated infobox orchestra. It is a myth that Classical music is against infoboxes, a myth that seems to be widely believed for no good reason. - I don't mind an occasional bollocks or bullshit, having a history of linking to one of these in some other editor's comment myself. - If I may have a final word here (while I will keep adding to the list): I looked at the discussion Talk:Sparrow Mass again and found no lack of dignity in Andy's contributions to it. Let's not continue The Ban on Love. -- Gerda Arendt ( talk) 12:10, 24 August 2013 (UTC)

Section break 1

  • May I respectfully point out that the evidence for this arb case closed about two weeks ago? Arbs may wish to consider the consistent attempts of Montanabw, Rexss, PumpkinSky and Pigsonthewing to turn this investigation into their behaviour into an attack against others. I don't have time or inclination to respond to Montana's latest effusions, save to point out that virtually all the links she points out relating to me are repsonses to unprovoked, hostile and agressive comments from the four above mentioned editors. Gerda's optimism , which is what I clearly referred to, has been to me exactly as irritating as F-T's, although I am glad to say we are now cooperating with each other as per normal; I believe that Gerda and I understand very well each other's virtues and limitations and we don't need outsiders to kibitz on our Wikirelationship (Ahh.....). I am not at all ashamed of referring to the futile attempt of Pigsonthewing and Rexss to get an ANI judgement against me as 'bollocks' - which is exactly what it turned out to be. Unlike them, I am not a Wikilawyer, do not seek to build the encyclopaedia by vengeful attacks on fellow editors, and have not sought to escalate their war to these upper regions. Thanks, -- Smerus ( talk) 07:23, 24 August 2013 (UTC)
This case is not an investigation of my behaviour. You need to take responsibility for your systematic reversions of the addition of inboxes inside your walled garden - without any justification beyond 'nobody asked your permission first'. Then you need to consider the effects of stonewalling any attempts to reach a consensus by canvassing your WikiProject to trot out the same tired irrelevant, arguments. You count opinions on talk pages and call that a 'consensus'. At no point anywhere in this sorry business have you made any attempt whatsoever to look for consensus. You should be ashamed of the way in which you insulted and belittled one respected female editor and accused another one of libel. That's so far beyond the pale that any conclusion to this case that fails to acknowledge your central role in causing the problems will have simply given you a licence to continue bullying female editors and stifling any attempts at consensus. That has to stop if we are ever to move forward. Your lie above is plain: from the start, you have singled out Andy and Gerda as scapegoats, while I and others have deliberately refrained from mentioning your name in our evidence, as I would have preferred to have dealt with your behaviour as a general issue, not a personal one. It seems the Arbs would prefer to have it spelled out in detail and that's what those diffs above show. -- RexxS ( talk) 14:10, 24 August 2013 (UTC)

Comment I have to intercede here as a longstanding member of the WP:CM wikiproject. The description above by User:RexxS is simply histrionic. 1) We have discussed the use of infoboxes for classical music topics at WP:CM for a very long time now and have raised a number of arguments that members of that project find compelling and germane. That other users who do not edit classical music articles do not find them compelling may be true, but it is ridiculous to suggest that referencing and soliciting the opinion of interested editors through the relevant wikiproject is "stonewalling any attempts to reach a consensus by canvassing your WikiProject to trot out the same tired irrelevant, arguments." This seems arrogant. (2) You describe an engagement between two editors which is mere fiction given how the two editors concerned on this very page have undertaken to describe their dynamic. You may see it as insulting and bullying, but you are not the editor being addressed. Who are you to take umbrage on someone else's behalf? This seems remarkably arrogant. (3) Andy has been singled out because Andy is problematic. This may offend your sense of justice because you happen to agree with him, but I don't see Smerus, Kleinzach or anyone else wading over to other wikiproject article series willy nilly to bray schoolmarmishly about how we are guilty of owning all these articles (that we create, edit and maintain) because we refuse to concede the value of his point of view. To suggest that our interest in maintaining the quality of articles under the project's umbrella is somehow "stifling attempt at consensus" is ridiculous and seems quite unbelievably arrogant. (4) We have engaged, repeatedly and extensively and in good faith the question of infoboxes for classical topics. We will do so again. There is no policy mandating infoboxes. Absent such a policy it is reasonable that the editors who have common interest in these articles, demonstrated by the fact that they have edited and maintained them, should offer their opinion and be solicited to do so. That you contribute to such debates is salutary. That you then insult the integrity, motivations and sincerity of those of us who labour hard over our wikiproject articles is, however, not. It seems, dare I say, exceptionally arrogant. Personally, I see nothing in the evidence that has been presented "against" Kleinzach or Smerus that in any way whatsoever compares to the longstanding, repeated disruptive history of User:PigsontheWing. Eusebeus ( talk) 15:38, 24 August 2013 (UTC)

Eusebeus, please differentiate. Project Classical music has reservation concerning infoboxes for biographies, and I am willing to accept that. However, the project developed infoboxes for orchestras, Bach compositions and musical compositions, project opera developed an infobox for opera, all ready to be used. The fact that many of them were reverted and questioned brought us here. I don't want to point out evidence against any esteemed editor. Today I read again several interesting discussions, notably The Rite of Spring, Sparrow Mass and Don Carlos. I found no disruption by Andy in those discussions, instead an admirable hope for improving content: "One always hopes that fellow editors will raise issues with articles in order to improve them, rather than to try to score points in a different argument; perhaps disappointment should be expected. Nonetheless, if there is an error in the article, overlooked by those who have spent so many hours working on it and those who have subsequently reviewed it, it should be fixed sooner, rather than later. That said, if a term has been "employed by significant scholars in the field", then that, not your personal preference, has precedence. regarding your final question, you might like to read WP:NOTDEMOCRACY." One always hopes, -- Gerda Arendt ( talk) 21:03, 24 August 2013 (UTC)
I have to inform you that the option of infobox opera, installed by Voceditenore in the project's Manual of Style, was just changed, in Voceditenore's absence and without a discussion. (It makes me think if "Infoboxes" is the right name for this case. It seems to grow more and more to a matter of ownership and protection of the status quo, here: the traditional side nabox. You can speak up at the project talk or at the example The Ban on Love.) -- Gerda Arendt ( talk) 09:40, 27 August 2013 (UTC)
Voceditenore reverted and called for a discussion, -- Gerda Arendt ( talk) 19:11, 27 August 2013 (UTC)
[ec] You refer to "arguments that members of that project find compelling and germane". What about the project members who do not; and who like infoboxes? Does Gerda not count? Have the rest, like User:GFHandel and User:Melodia, et al, been driven off by the intransigence of the remaining project members? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:05, 24 August 2013 (UTC)

Further evidence

Like Gerda and RexxS, I was reluctant to pile on diffs of editor behaviour in my evidence, feeling that it would just fan the flames, rather than enable proper arbitration and the attainment of an an amicable resolution. But since you request them, I'll post some now. Noting your request for brevity (while giving necessary context, especially for long edits), and Der Wohltemperierte Fuchs' request for haste, this is still just a sample:

  • 10 March 2008 Kleinzach adds the words "non-classical" to the scope of {{ Infobox musical artist}}, which includes an explicit classical_ensemble configuration and code.
    • 31 August 2009 I removed that caveat
    • 21 October 2009 Kleinzach comments on this, in a conversation in which I was not yet involved, detailing my blocklog and Arb history, in a clear ad hominem response.
    • In the poll which followed, Kleinzach accuses others (in edit sumamry) of a transparent attempt at splitting the consensus against using the box for 'classical' musicians.
  • 31 July 2011 In response to my making a suggestion to improve the accessibility of navboxes (since adopted for all navboxes on Wikipedia), Kleinzach's reply is Is this to do with microformats? There is at least four years of back history to this issue as searching the archives of WP:Composers will show [42]. The suggestion was nothing to do with microformats.
  • 16 April 2012 Kleinzach says I was dismayed to see Andy Mabbett's involvement; also false allegation of breaking an undertaking (which I never made).
    • 16 April Kleinzach declares AGF is simply not appropriate here — unfortunately we have assume the worst
    • 16 April 2012 Kleinzach partisan canvassing
  • 19 March 2013 Smerus refers to the insane proposals to weld all the world's knowledge into a virtual nugget amd attempts to bully editors by alleging huge techno revolutions going on somewhere
  • 22 March 2013 Smerus opposes (on an article talk page) an infobox, citing WP:COMPOSERS policy and continues It is rather naughty to use Bach as a catspaw in trying to change this - it would be more polite to engage discussion at the project page. Remember that the composer's project's RfC concluded that consensus should be formed on article talk pages.
    • 23 March Kleinzach Closing an ongoing discussion, with a particularly biased summary, despite being an involved party. He was immediately reverted by User:GFHandel. Kleinzach then complained that his summary had been deleted in the reversion, rather than refactoring it as a general comment (i.e. removing phrases rendered nonsensical by the revert, like "I am now archiving this") and reposting it. Immediately after this, GFHandel, a long-standing editor in classical music realm (whose user name belies his interest); and a supporter of the use of infoboxes in such articles, retired from and ceased editing Wikipedia.
  • March 2013: Infobox orchestra is created, in draft. I add some fields to it, and
    • Despite the fact that the template is a draft, not used in any articles, Kleinzach objects that I am opposed to any changes to the template made without discussion. These shouldn't be happening — as I have said here. ("here" link updated to archive; diffs from that are in my earlier evidence. That whole discussion, and the template talk page, are worth reading for examples of Kleinzach objecting to (and often reverting) every change I made (most have been kept), and reporting every edit I make to the classical music project to canvass support).
    • During construction of the template, I made the observation: This new infobox looks promising, but should not replace infoboxes with additional, useful, parameters, such as those in City of Birmingham Symphony Orchestra, until it can handle similar detail (with better labels, of course). At that time the CBSO article looked like this
    • Nonetheless Kleinzach proceeded to replace ( seemingly) every instance of {{ Infobox musical artist}} on an article about an orchestra - edits well into three figures, ignoring objections. In most cases, cited and otherwise undisputed information was lost from the infobox, as can be seen from the current state of the CBSO article. That's a Fait accompli, apparently.
  • 19 May Smerus places a Do not feed the trolls graphic on the Richard Wagner talk page, during discussion of a proposed infobox.
    • 22 May Smerus made a bogus attempt to claim that I was not allowed to edit the talk page of a TFA (Richard Wagner; the discussion has been listed in others' evidence). He pushed this repeatedly in later edits. In This he refers claims I am Wikipedia 'reductionists' lke Mr. Mabbett, who see WP as means of crystallising the world's information to an essential nucleus from which all can be extrapolated (rather like, as I have mentioned elsewhere in a debate on Mr. Mabbett's obsessions, the desire of Mr. Casaubon in 'Middlemarch' to construct a key to all mythologies),and 'expansionists' like myself who like to create and expand articles, thereby both misrepresenting my work on metadata and dismissing the considerable number of articles I have created and/ or expanded. (Both ANI and then AN later rebuffed the attempt.)
  • 8 July Kleinzach falsely asserts that an infobox must summarise the article, i.e the article as a whole, attempting to correct Gerda, who rightly points out that they are supposed to summarise key facts. ( MOS:INFOBOX: 'to summarize key facts in the article in which it appears)
  • 8 July Kleinzach describes the addition of an infobox as "pretty close to vandalism"
  • 8 July Smerus describes infoboxes as the " end of civilization" and comaplins about Gerda doing so "without consulting on the relevant talk pages" while asking "whether it's "OK to revert these with a request for discussion on each talk page".
  • 8 July Kleinzach described the addition of an infobox as a WP:POINT attack
  • 9 July Kleinzach falsely accuses Gerda of going through my edits reverting them one after another
  • 11 July Kleinzach deletes an infobox which was part of Gerda's comment, from an article talk page.
  • 12 July Kleinzach attempts to pressure Gerda into falsely confirming that he did not delete part of her comment.
  • 11 July Kleinzach falsely claims As everyone here probably already knows, the editor involved here follows me around Wikipedia reverting and refactoring my edits He means me (see my earlier evidence for other examples from the period when he insisted on not using my name or user name). The diffs he gives are all pages I'd previously edited and are on my watchlist. He also accuses me of "hacking" (repeated in edit summary)
  • 12 July (and others) Kleinzach logging my edits

More may follow; or on request.

I repeat my comments in evidence and workshop that the "involved" projects include other editors, not yet named here (and some who have posted evidence or comments). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:49, 24 August 2013 (UTC)

Couple of thoughts

As I went active on this case rather late (after the workshop closed), I'm leaving some comments here. I've read through the evidence and workshop pages (and talk pages), and there are some interesting discussions and suggestions there. One thing that needs to be kept in mind is that it is not possible (or desirable) for ArbCom to rule on the wider aspects of the matter, such as what infoboxes are for, and how they should be used and the various points related to metadata. Those sort of issues need well-ordered and widespread discussion by the editing community, while at the same time recognising existing practices and any inconsistencies in current editing practices.

Looking at the bigger picture here: many elements can be incorporated on the same Wikipedia article page (article text, lead section, tables, references, categories, navboxes, infoboxes, succession boxes, images and other media). Some of those elements are optional, others are found in all articles. How these sometimes disparate elements mesh together is part of the process of building and writing an article. Sometimes that requires discussion. If editors disagree over how an article should be written, and which of these elements should be used or how they should be used, then they need to discuss that. When editors fail to discuss (or edit war), or discussions fail, that is the point at which either wider input from the editorial community is needed, or formal dispute resolution.

When you have meta-philosophical disputes like this that have lasted years, one approach is to identify the productive community discussions that have taken place over the years and to identify the discussions that got widespread input from a large number of editors. And if those discussions haven't taken place, to try and encourage such discussions (after suitable planning and preparation).

One thing I have noticed recently is the large number of discussions taking place at WP:TFD, with infoboxes being discussed there. As far as I can tell, those discussions appear to be mostly aimed at merging infoboxes, but it is interesting to see the wide range of opinions expressed in those discussions. Even if this case does succeed in calming things down here, it is obvious that the wider issues still need fuller discussion. This is the sort of case where I'm tempted to say that those who disagree (as shown on the workshop page) should be instructed to write essays explaining their positions, and that a widely-advertised request for comment would then help form community-wide consensus on the best way to move forward. Carcharoth ( talk) 11:16, 17 August 2013 (UTC)

One-sided rulings in such cases never calm things down, they exacerbate the issue. You should know that by now. Not to mention making AC look ever worse. PumpkinSky talk 11:34, 17 August 2013 (UTC)
Your comment is a response to my saying "Even if this case does succeed in calming things down here"? Fair enough, but that wasn't really the point of what I said and you are only responding to a very small part of what I said. Your comment seems to relate more to the section you started above (which I may comment on later). I'd be interested in constructive comments on the other things I said in this section. Carcharoth ( talk) 11:50, 17 August 2013 (UTC)
Wiki has become completely dysfunctional as it is a reflection of the real world, which is also totally dysfunctional. These things can't be fixed. For example, you can't stop people from socking--the sock policy is joke as it's a total waste of time, AC is pointless anymore because their rulings are wildly inconsistent and contradictory--towit putting up a principle against walled gardens here and yet setting one up for the anti-box crowd by ignoring their actions, AC and other wiki DR efforts are pointless because you can't change people's nature, those in power in wiki and RL protect their own and crap all over other people. So, I think we should do away with AC and DR and just work on content. Nothing has changed in the almost 8 years I've been on wiki. It just gets worse every year. AC and DR is all pointless and taking sides in a case makes it even worse. PumpkinSky talk 11:59, 17 August 2013 (UTC)
Wiki has become completely dysfunctional - admins have been far, far too lenient with disruptive editors such as Pigsonthewing who have turned massive areas of the project into battlegrounds and driven away productive editors and this has been going on for years. Many people who could make valuable contributions do not want to spend their spare time volunteering to take part in an activity that involves constant arguing and participation in bitter feuds. I am an active blogger on opera, I have taught history of classical music professionally, I made a conscious decision several years ago not to edit in the area on WP for the very reason that I could see I would get involved in this long-running controversy on infoboxes and it would be an unproductive waste of time. I never commented on the issue until it came to arbcom. It looks like a good decision is shaping up here, the essential thing is that Pigsonthewing is permanently removed from any involvement in anything to do with infoboxes. Smeat75 ( talk) 13:10, 17 August 2013 (UTC)

Comments from Gerda

2) About myself

You know Findings Gerda Arendt: Yes, I have added infoboxes to articles systematically and without prior discussion. The first link goes to works by Kafka, the day before he was TFA, - I am proud of it. The second link shows me adding one infobox to one opera which was a FA, right after the option of {{ infobox opera}} became available, which I understood as an invitation to use it, whereas others regarded it as the end of civilisation. I was told that it was not wise to do so and have only suggested (not added) to Carmen. - I believe that adding infoboxes to operas, literature, compositions etc. don't require previous discussion. I would go further and say that no edit requires to first ask permission, - and who's permission?

For quite a while already, I am on a voluntary 1RR rule: if an added infobox is questioned I go to the talk page. I offered to find out how consensus can be achieved in two cases, The Ban on Love and The Rite of Spring, in an attempt to get from "I don't like it"-arguments to factual one. I invite everyone, arbitrators and watchers, to enter those discussions, to find a way how conflicts can be resolved in the future, rather than looking at errors of the past. There are some 50 other cases to look at. Note: not one of them is a composer where I added an infobox. For the infamous case Richard Wagner: I didn't even suggest to add an infobox to the article, only to show it on the talk, according to the advice from an arbitrator. Why the reaction was as if I had committed a sacrilege is beyond my understanding. -- Gerda Arendt ( talk) 12:25, 17 August 2013 (UTC)

1) About Andy

I still haven't seen any evidence of Andy editing disruptively in 2013. I found him always helpful, creative, open for suggestions and considerate of an editor's personal situation. Restrict such editors? What do you want to accomplish? -- Gerda Arendt ( talk) 12:25, 17 August 2013 (UTC)

1.1) As said above, there are countless topics where infoboxes are quite normal. Why restrict Andy - of all people - from adding infoboxes there? (Same question for me, of course.) -- Gerda Arendt ( talk) 12:37, 17 August 2013 (UTC)

1.2) As said above, where is the evidence for recent disruption? I see no reason to ban for something that was regarded disruptive in the past, if it is not repeated. -- Gerda Arendt ( talk) 12:37, 17 August 2013 (UTC)

Gerda, I'm sorry to 'butt in' and contradict your defense of Andy. But only in the last day or so, not having had any previous dealings with Andy until I encountered him on the Peter Warlock article, I have personally found him aggressive, confrontational and quite oblivious to appeals to actually discuss an issue and collaborate. This can be seen here where, even as you and I are having a civil discussion about infoboxes, he butts in and tries (not for the first time, as you can see further up the talk page) to goad me into 'reporting' him after I'd called him out for breaching BRD - I can't help feeling as if to say "so you say - what are you going to do about it?". In short, he was behaving like a bully who's been caught out and has no intention of making amends but would rather turn this into an intractable confrontation, presumably in the hope that his 'opponent' will 'lose his cool'. Alfietucker ( talk) 18:59, 18 August 2013 (UTC)

3) About "remedies"

The term "not very constructive" has been used, - forgive me for finding all so-called remedies not very constructive. Nikkimaria and I not to add, revert, discuss infoboxes at all? Please see that only in a a very small field infoboxes are contentious, and these are not contentious because of Nikkimaria and me. I should not be permitted to add an infobox to a Bach cantata I write? ... to a church I find without one? Come on. - It's easy to ban an editor whose arguments you don't like. I don't see yet one factual (!) argument why "The Rite of Spring" should not have an infobox, - please join the discussion and give me one. -- Gerda Arendt ( talk) 13:15, 17 August 2013 (UTC)

Actually, your last comment is a very interesting point that should be clarified. If you create an article, you might be allowed to add an infobox, I think. However, there proposed remedies have yet to pass (or not). — ΛΧΣ 21 14:58, 17 August 2013 (UTC)
Assuming it complies with Wikipedia's content policies, then yes. The reverse should also apply: if you create an article (or provide the bulk of its content) then you shouldn't have to have an infobox imposed on it. For instance, on The Rite of Spring, the biggest contributor by far is Brian Boulton [43] and he's opposed to an infobox there. -- Folantin ( talk) 15:03, 17 August 2013 (UTC)
Why do you mention that here where we talk about me adding infoboxes? I didn't add one to "The Rite of Spring", nor did Andy, no infobox was "imposed" on it. Andy asked (!) why it doesn't have one, and that was the most "disruptive" edit I saw him making in 2013, - needless to say that I don't find it disruptive at all. - I am in friendly discussion with Brian on the infobox of another article, see Talk:Peter Warlock (again not added by Andy or me). One question is if an infobox is supposed to contain "the key facts" of an article or "key facts". Brian, who wrote an excellent Signpost article, is more open than you assume, and discussion, not banning and restricting, is the way forward that I hope for. - The agreement between Nikkimaria and me is that she doesn't revert infoboxes in "my" articles, I leave "hers" without one, - it's not a great agreement (a reader may wonder why some Bach cantatas have an infobox and other's don't, Nikkimaria's and Mathsci's), but is better than none. -- Gerda Arendt ( talk) 07:31, 18 August 2013 (UTC)
Gerda, I respect your content work and your Precious awards to build community here, and I think that you should be able to add infoboxes to articles you start. However, you seem at least a bit tone deaf when it comes to infoboxes. For example, when the discussion at Talk:The Rite of Spring had clearly reached consensus against adding an infobox to the article [44], you went ahead and added The Rite of Spring as an example in the Infobox musical composition documentation ( diff). When there is a clear consensus against using an infobox, using it as an documentation example makes no sense, and invites well-meaning editors who are ignorant of the article's history to add it to the article. Ruhrfisch ><>°° 15:20, 18 August 2013 (UTC)
Please follow the sequence: It was not my choice of an example, I chose The Ban on Love above it. The Rite was mentioned there, I thought we better illustrate it for those who don't know. I still believe that we should not "vote" on infoboxes but find other ways of discussion, - I keep dreaming and searching, please help. -- Gerda Arendt ( talk) 05:52, 19 August 2013 (UTC)
I am sorry Gerda, but I have no idea what you mean with your comments directly above this. I tried to "follow the sequence" by looking at your edit history. On June 1, 2013 at 19:10 you made your first edit in nearly six hours (to Wikipedia:Administrators' noticeboard/Requests for closure to the thread ‎"Talk:The Rite of Spring#Infobox" with the edit summary That's how you can look at a ramp for the disabled ( diff)). Your next edit was at 19:21 to Talk:The Rite of Spring to the thread "‎‎Closing discussion?" with the edit summary some things can't be decided by voting ( diff). Your next edit was at 19:36 to Template:Infobox musical composition/doc with the edit summary ‎‎Examples: add one where you added The Rite of Spring infobox as an example ( diff). I looked at several of your other edits before and after these, but none of them mention the Ban on Love.

Just to be clear, I have no problem with proposing and showing examples of infoboxes on the talk page for the article where the box would be included.

However, I think that it makes absolutely no sense to show a specific article's infobox as an example in that box's documentation when the talk page for that article twice showed clear consensus against including any infobox. That is like using Mitt Romney or John Kerry as an example of a US President in {{ Infobox officeholder}} (since there was pretty clear consensus against either of them actually becoming President).

I also think it makes absolutely no sense to show an unused infobox as an example anywhere outside the article's talk page (or a personal sandbox). The problem is that an uninvolved editor who sees the example box and finds it is not used in the article may well not read the article talk page. They may well think that the box should be included in the article, and add it despite consensus not to do so. It is a little like a leaving a loaded gun lying around unattended - it may lead to unexpected noise and injury.

I hope this explains my concern at your "tone deafness" when it comes to infoboxes more clearly. Ruhrfisch ><>°° 21:43, 19 August 2013 (UTC)

I try to follow but think that we speak of different things- which doesn't make understanding easier. After the workshop closed, I installed The Ban on Love on its talk, side navbox vs. infobox, to "practise" with an example how consensus might be achieved, on 8 August. In the discussion The Rite was mentioned, therefore I added it 9 August. - I am a bit surprised to see an infobox compared to a gun ;) - If someone sees it and adds it, simply revert. - Decision by voting: I believe that to look at flaws and merits of a proposal is better than counting people who come with arguments such "Oppose any infobox" (yours), "An infobox is not needed" (well, of course not, it is never "needed"), "redundant to a properly-written first paragraph" (well, it has to be redundant by definition), and better than all these " infoboxes are contentious". -- Gerda Arendt ( talk) 22:10, 19 August 2013 (UTC)
@ Ruhrfisch: we spoke of different things, now I know. I was absorbed in the case, you spoke about the example in the infobox template. You were quite clear, I didn't get it, sorry. I replaced the example now by a Bruckner Symphony, which has an infobox since 2007. -- Gerda Arendt ( talk) 15:59, 23 August 2013 (UTC)
You forgot the "Google should not be allowed to easily benefit from our work" argument that was sported at Jimbo's Agathoclea ( talk) 07:50, 20 August 2013 (UTC)
WHAT? — Ched :  ?  04:42, 21 August 2013 (UTC)
The above summary is mistaken. The discussion was here and concerned an essay expressing extreme frustration with the infobox wars, and particularly for one justification to include infoboxes, namely "Watson, SIRI, and Google all use the infobox data." The author objects to having their opinion that some infoboxes are not helpful subjugated by an imperative that data must be provided for Google (and inserting metadata into the article is not sufficient because editors won't keep hidden data updated, therefore an infobox must be present and visible). Johnuniq ( talk) 07:40, 21 August 2013 (UTC)
The "Watson" quote (though factually correct; and acceptable, as WTT points out elsewhere)) is a paraphrase of part of a much longer comment by User:Richard Arthur Norton (1958- ) in a November 2012 discussion at Talk:Stephen H. Wendover/Archive 1. For the record, I posted only three short comments there, and one of those was to point out that the page had been refactored, changing the meaning of my other two comments. There is no "imperative", and noting is being done "for Google". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:59, 23 August 2013 (UTC)

We start today

I keep dreaming of a new discussion style in the future, instead of looking back at who made what mistake in the past. My suggestions for arbitration:

  1. I restrict myself: I don't revert the revert of an infobox. (I started doing so a while ago.)
  2. Andy restricts himself: he doesn't make more than one comment per day in any given infobox discussion.
  3. Nikkimaria keeps doing what she does, follow our edits, and Wikipedia will be clean.
  4. Kleinzach restricts himself: he doesn't say again "The talk page is not the place for an info box".
  5. Smerus restricts himself: he doesn't mention "(mental) health" again in an infobox discussion.

We all don't start new discussions, but try to solve the open ones. I suggest Siegfried first, if you don't like The Ban on Love ;) -- Gerda Arendt ( talk) 06:46, 19 August 2013 (UTC)

Could you please cite exactly where I have made any mention of health, mental or otherwise, in any infobox discussion? I do not recall any such occasion. I ask so that I can make apologies if appropriate if I have in any way transgressed the bounds of courtesy.-- Smerus ( talk) 07:07, 19 August 2013 (UTC)
Siegfried, link above, -- Gerda Arendt ( talk) 07:39, 19 August 2013 (UTC)
I see that I wrote there ' I join the plea for dignity and (mental) health'. This is not an imputation against anybody, it is a simple plea for sanity. This is the secondtime in a few days that you have made unwarranted imputations against against me, once by suggesting that I set up a tag-tema, and now by apparently implying that I made comments about the mental health of other editors. I suggest that the principle new start that can be made here is by editors refraining from making allegations against others and/or telling other editors what words they should or should not use in their general commemts, as long as those words are not insulting or vicious. I dream of such a day.-- Smerus ( talk) 08:09, 19 August 2013 (UTC)
I have not. I have not made any imputation. I have not said that you set up a team-tag. I have not implied anything here, I have only asked you to not use the phrase in the future. Let's keep it simple, please, -- Gerda Arendt ( talk) 08:22, 19 August 2013 (UTC)

Invitation

I invite every arb (and everybody else interested) to visit one open discussion, perhaps even take part in it. You know where to find the choices on top of Verdi, Siegfried, The Ban on Love (mentioned in the case or above): here. -- Gerda Arendt ( talk) 11:33, 19 August 2013 (UTC)

I invite everyone to stop talking about infoboxes for at least a month because no benefit would arise from adding further fuel at the moment. Johnuniq ( talk) 00:17, 20 August 2013 (UTC)
Excellent idea - I will stop talking about infoboxes for at least a month (as of now ;-) ). Ruhrfisch ><>°° 00:39, 20 August 2013 (UTC)
I thoroughly approve of this proposed moratorium. -- Folantin ( talk) 08:24, 20 August 2013 (UTC)

Comments from the reader?

We can not ask "the readers" how they feel about the unspeakable things - let's call them "summary" for the moment. We can not ask them especially when they got reverted. But we all are readers. Please let me know if my "summary" serves you, compared to no summary. From the more than 50 cases (linked above) I chose an opera (o), a composition (c) and a person (p). Easy poll: if "with summary" (or without) is the same for all three cases, simply sign, if not the same for all three take the two initials for which you react the same way and sign those. I would love something playful today.

  1. opera: Fatinitza - with - without
  2. composition: Sparrow Mass - with - without
  3. person: Andreas Scholl - with - without

I prefer with summary

  1. -- Gerda Arendt ( talk) 08:42, 21 August 2013 (UTC)

I prefer without summary

Feel free to discuss, -- Gerda Arendt ( talk) 08:42, 21 August 2013 (UTC)

Discussion

This Arbcom case concerns the long-term disruption caused by a clash between two sets of editors—it is not relevant whether infoboxes are good or bad. Let's suppose some new arguments were produced to conclusively show that infoboxes must (or must not) be included in every article—would that resolve the problem? The answer is no because after all the bitterness of the infobox wars, neither side is going to accept a new opinion. It really would be best to stop talking about infoboxes—wait a couple of months, then if wanted, start a community-wide discussion to get a general consensus so future discussions can rely on a policy, or at least a guideline. Johnuniq ( talk) 10:20, 21 August 2013 (UTC)
So you think, about what this case concerns. Please note that I never said "must" or "must not", and never will. I use an option. -- Gerda Arendt ( talk) 11:57, 21 August 2013 (UTC)
This case is called "infoboxes", yes, but as someone who has watched the dispute for a couple of years without getting involved in it until now, I agree with Johnnuiq that it is not actually about infoboxes but more about one editor's (Pigsonthewing) obsession with "metadata" and his pushing of it onto unwilling editors in a highly argumentative way that alienates others. There are many examples where he has put an infobox into an article, or attempted to, and the people who have built the article say" that does not add anything", to which the all-purpose reply is "Yes, it does, it emits metadata", just for instance in this discussion [45].I can say for myself that I made a deliberate decision not to edit in the area of classical music because I could see it would involve me in this bitter feud, and I have better ways to spend my spare time. Smeat75 ( talk) 22:52, 21 August 2013 (UTC)
Smeat75 misquotes me. I was actually replying to Brianboulton, who said, addressing me, You obviously think that an infobox would enhance this article; let us have the arguments for this., and what I actually said was The benefits of an infobox in this article, as for the many thousands of other articles that include one, are that it summarises key information from elsewhere in the article, including material not suitable for the lede, for the convenience of readers wanting a quick overview, not least those accessing the collapsed view on mobile devices. It makes that information available as machine-readable metadata on the page; and for use in dbpedia. And it will, shortly, provide an interface with Wikidata. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:21, 21 August 2013 (UTC)
I provided a link to the whole discussion, anybody can follow it to see exactly what you say.I find you a very intimidating and bullying presence and made a conscious decision to avoid any articles that might bring me into dispute with you. Smeat75 ( talk) 23:27, 21 August 2013 (UTC)
You have your view, I have mine (and this is my section of the discussion). I repeat from below: I find Andy not intimidating, patiently explaining, with a sense of humour (note: I did so already when I did not share his view). - I liked to enter his latest article to the DYK statistics. I like that he (of all participants in the Bach discussion) came to my talk when I mentioned that a friend died. - "Intimidating" is a difficult term, - would you have a link to something you would describe like that? - I am not intimidated, although I was warned. - "Obsession" is also a difficult term. I am for infoboxes without using the term metadata, and I don't feel that I am obsessed. - What this case should be about and is about are very different things. It should be about systematic reverts of infoboxes, latest example BWV 71, see discussion. - The way this case goes (so far) makes me think of a "deliberate decision" not to edit Wikipedia. I didn't want a case, but really hoped arbitration would look at recent evidence, not history, and reach for understanding. Recent evidence has it that Andy and I did the same things, so please treat us the same. I am not afraid. -- Gerda Arendt ( talk) 12:41, 23 August 2013 (UTC)

We need to know what to do in the future

For the future, we need to know precisely "what is perceived to be some editors' aggressive addition or reverting of infoboxes to articles without discussion", as the SignPost summarized.

Please mark the following 2013 examples as "aggressive" if you perceive them so. (Note that I excluded operas, because we will deal with it on the project level, started already, after 17.000 words of discussion were archived.)

Added later: After Voceditenore's remark below, I change the question to: what is perceived to be problematic and should be avoided in the future? (Not using "aggressive", "tendentious", "disruptive", "detrimental to our content", "a nuisance".) All cases turned out to be controversial, to my surprise. -- Gerda Arendt ( talk) 10:53, 1 September 2013 (UTC)

  1. Addition of an infobox without prior discussion to a church ( Cathedral of Blessed Mother Teresa in Pristina, St. Severin, Keitum)
  2. Revert of the same
  3. Addition of an infobox without prior discussion to an orchestra ( Russian Symphony Orchestra Society)
  4. Revert of the same
  5. Addition of an infobox without prior discussion to an art work ( Forsbrook Pendant)
  6. Revert of the same
  7. Addition of an infobox without prior discussion to a company ( Renaissance Theatre Company)
  8. Revert of the same
  9. Addition of an infobox without prior discussion to a person not in classical music ( Aspinwall)
  10. Revert of the same
  11. Addition of an infobox without prior discussion to a building ( Holzhausenschlösschen)
  12. Revert of the same
  13. Addition of an infobox without prior discussion to a composition ( Sparrow Mass, Cantata academica)
  14. Revert of the same
  15. Addition of an infobox without prior discussion to a Bach cantata ( Geist und Seele wird verwirret, BWV 35, Gott ist mein König, BWV 71)
  16. Revert of the same
  17. Proposing an infobox for a composer ( Handel)
  18. Addition of an infobox without prior discussion to a composer if you wrote the article ( Planyavsky)
  19. Revert of the same
  20. Asking why an article doesn't have an infobox ( The Rite of Spring)

Needless to say, as I am unaware that any of these actions (not even the reverts) are "aggressive", problematic, please clarify. What did I miss? -- Gerda Arendt ( talk) 08:52, 1 September 2013 (UTC)

The quote is a Signpost editor's individual take on the case. It has nothing to do with the proposed decisions in this case. You will note that nowhere in the proposed decision is the term "aggressive" used except in SilkTork's comment under Editorial process:
"Reverting of anything other than obvious vandalism or harm should be considered very carefully as reverting can often be perceived as an act of aggression which then provokes a negative response. Consideration, politeness and discussion go a long way to assisting everyone to build this encyclopaedia appropriately."
As for WikiProject Opera "starting already" on the discussion you propose here, I'm afraid you've rather missed the key thrust of my "17,000 words" comment there:
[...] Several members are so sick of these constant, fruitless, and at times personalised discussions dominating our project talk page that they've taken it off their watch lists. Lord knows how many prospective members we may have lost in the last few months after they've seen this talk page. It's quite clear that at the moment some editors have fairly entrenched positions and there is simply not sufficient common ground for us as a collective to come anywhere near an agreed "general recommendation". The world is not going to come to an end if we have to proceed without one for now. However, the relentless attempts to continue rehashing this may well be the death of this project. Can we please take a break from all this and revisit it in a few months (if anyone wants to) when people have had time to reflect on their positions and the dust has settled on the current arbitration proceedings and their aftermath. [...]
Voceditenore ( talk) 10:10, 1 September 2013 (UTC)
I don't think I missed it, I responded that I will not add an infobox where a side navbox is in place, - adding here: I will not even suggest one in such a case, - five months were mentioned, fine with me, -- Gerda Arendt ( talk) 10:33, 1 September 2013 (UTC)
I am aware that you responded with your five months offer, but since you have described your response as "starting" (yet another) discussion of how to proceed with infoboxes, well, I'm afraid you did rather miss my point. In any case, you can (and undoubtedly will) do what you think is best. Voceditenore ( talk) 10:52, 1 September 2013 (UTC)
I try, -- Gerda Arendt ( talk) 11:06, 1 September 2013 (UTC)
I did not start "yet another discussion", - I opened the discussion on The Ban on Love on 8 August, only moved it to the talk of the article on 26 August. -- Gerda Arendt ( talk) 11:20, 1 September 2013 (UTC)
??? What does Talk:Das Liebesverbot have to do with it? That is an individual talk page discussion, not a "project level" discussion and not carried out on the project talk page. Your statement: "Note that I excluded operas, because we will deal with it on the project level, started already, after 17.000 words of discussion were archived" (and your subsequent comment) implied pretty clearly to me that you considered Wikipedia talk:WikiProject Opera#17,000 words and your response to it to be the "already started" new project-level discussion on how to proceed on infoboxes, when actually it was my individual plea to both sides for a project-level moratorium on the subject. Perhaps you don't see the damage these discussions have done to the project in terms of both productivity and our former collegial atmosphere, but I do, and so do the members who have taken the project talk page off their watchlists. Voceditenore ( talk) 14:23, 1 September 2013 (UTC)
I won't "damage" productivity and atmosphere anymore, leaving projects opera and classical music, -- Gerda Arendt ( talk) 11:53, 2 September 2013 (UTC)

Comments from Montanabw

I see several problems with the proposed decision.

  1. Klienzach and Smerus should be subject to - at a minimum - identical or parallel restrictions to those imposed on Nikki, Gerda and Andy. I will elaborate more on this below
  2. Andy needs to be evaluated on 2013, not 2006 or whenever. To the extent he made mistakes, he did his time, he's paid his debt to wikipedia society, and that should be water under the bridge. Drop the stick, look only at the present.
  3. Also, Andy clearly has an interest and passion for infoboxes and metadata, and that interest is not a bad thing; he provides a useful service to wikipedia and shouldn't have the thing he cares about most taken away. He has learned and grown from what has happened in the past, and I believe that the PD is basically giving him a life sentence for a misdemeanor. I think that if people are concerned, any proposed decision should be time-limited and narrowly targeted to specific, CURRENT concerns, perhaps only within the Classical Music project.
  4. Any restriction on Gerda of any sort makes absolutely no sense whatsoever. She has never violated one single policy or guideline on wiki and where she has ruffled feathers. she has apologized. In addition, most infoboxes she initially added were to INDIVIDUAL articles (which the PD says is OK) that she herself either created or did a 5x expansion on (I don't have time to correlate her DYK record to infobox additions, but I think I'm correct on this). Basically, all she has done was annoy the Old Guard "we don't want any infoboxes anywhere never lalalalala" clique at WP Opera.
  5. The proposed sanctions on Nikki seem about right, though perhaps definitely a time frame after which she can reapply for adminship (6 months, perhaps?) would be good so that we don't have a situation of the wiki life sentence that I have criticized above for Andy where a RfA would result in a chorus of "OMG! She was desysoped 10 years ago and how dare she return now? It's too soon!" and put her under a cloud forever.
  6. I am concerned that Nikki is being subjected to sanctions when Smerus and Klienzach aren't even mentioned, even though their behavior and attitudes are a very large part of why we are here in the first place. I am wondering if this is an example of the systemic bias against women that is a problem in parts of wiki. Nikki did overstep, but she also should not be the only person on the anti-infobox side (particularly where she isn't 100% anti-infobox anyway); in some ways, she showed more willingness to collaborate and work with Gerda than did Smerus or Klienzach.
  7. I think that if we are looking at levels of remedies, those imposed on Andy should parallel those on Nikki (save that he isn't an admin, but perhaps a discussion of appropriate but time-limited ( a month or so, maybe) editing restrictions would be in line.
  8. I believe that there should be some action taken against Kleinzach and Smerus for their behavior as the "old guard" and how UNBELIEVABLY unkind and incivil they have been to Gerda who, in my view, has always been nothing but civil. In particular, Kleinzach seems to be skipping off scott free because he simply has not responded here. Although Folantin and I personally reached a truce as to each other, I will note that I continue to be troubled by his attitude and responses here, it's one thing to defend his friend Smerus, but his tone has been problematic.
  9. Any restrictions on people adding or removing infoboxes should be confined mostly to the classical music topics, because this seems to be the only place where the existence of infoboxes themselves are the problem (most other disputes in other areas seem to be more over form than existence). To say that people cannot add ANY infobox anywhere is ludicrous; what if we have 10 new articles that need, say Infobox Mineral added - a wikiproject that strongly supports infoboxes in every article? Or if I ask Andy or Gerda to tune up or fix me up a fancy new infobox design for, say, the equine "biographies" where we have an infobox in all of them?

I am concerned that the proposed ArbCom decision unfairly targets a user, Andy/Pigsonthewing, as a scapegoat, and lets two playground bullies, Klienzach and Smerus, off scott-free to continue their bullying and domination of WikiProject Opera and WikiProject classical music unabated. This situation illustrates the worst weakness of "teh wiki" - it never forgets and it never forgives. Montanabw (talk) 15:57, 17 August 2013 (UTC)

@Worm, others: I am quite concerned by the "disinclined to use infoboxes" tone of the comments below and the implication that, somehow, they are not a standard feature of wikipedia articles, or that the "pro-infobox" contingent is a minority. Infoboxes are pretty much standard operating procedure for many wikiprojects, and as far as I can tell most of the C-class and better biographies, most C-class and better animal articles, gem and mineral articles, health and disease articles, chemistry articles, movies, TV shows, popular music, and so on. I think in Andy's evidence he showed some links that at least HALF and maybe more of wikipedia's articles - and this counts stubs and everything - already have infoboxes. While there is plenty (I'd argue too much) "drahmahz" over the content and appearance of infoboxes, the rabid OMG NO! response to them is rather unique to the Classical music project. For that reason, I don't think it wise to view infoboxes as a "creation" issue nor am I confortable having their absence any kind of implied default position. Montanabw (talk) 21:28, 19 August 2013 (UTC)

NEW: For anyone not thinking there is evidence of the behavior of Smerus that I think needs sanctions, he just posted this on the 16th (been ut of twon, haven't been following the drama chapter and verse for a while...): User_talk:Gerda_Arendt#Team. Montanabw (talk) 22:56, 19 August 2013 (UTC)
Just in case anyone takes this latest provocation seriously, I suggest they read the entire thread concerned.-- Smerus ( talk) 07:35, 21 August 2013 (UTC)
Most definitely. And I also strongly recommend reading Smerus' talk page as well. Don't start, my friend; WP:BOOMERANG. Montanabw (talk) 15:52, 21 August 2013 (UTC)

Comments from RexxS

I'm very disappointed that the PD has failed to find any viable way forward in resolving these issues. The idea that simply banning a few editors from the dispute will solve the problems is akin to the concept of cutting off an arm to cure left-handedness. You have the ability and the encouragement to look for better means, but have spurned the opportunity.

There is clearly a principle missing as Silk Tork has hinted - something along the lines of:

  • Editors making bold, good-faith edits to articles or article talk pages that others consider contentious may be judged to be editing disruptively.

because without that, the FoF and remedy concerning Gerda are hung on a non-existent premise - one that I'm not at all sure has the consensus of the community. You won't put the above up for debate, of course, because you know it has no grounding in our current policies and guidelines.

You will know that I have collaborated with Andy on numerous technical issues over the last couple of years, not least the development of {{ hlist}} and the improvements made to the accessibility of our articles, so you will expect me to be dismayed at the suggestion of banning Andy, thereby losing all of his hugely valuable contributions in so many areas - including classical music (how many of the regulars at WPCM can boast of having written a monthly column for a classical music magazine, as Andy can?). I accept that it would be better for Andy to step away from the conflicts over infoboxes, as they tend to bring out the worst in him, but why do you pick the bluntest of tools to do the job? "... indefinitely banned from adding or discussing the addition of infoboxes"? That implies a ban from any namespace, yet Andy is one of the small fraction of editors with the technical know-how to create and improve infoboxes, and you suggest removing him from that as well? Why? What does it accomplish besides damaging the encyclopedia? If you want to remove Andy from the conflict, then forbid him from adding or discussing infoboxes in mainspace; get him a mentor; look for some constructive, not destructive remedies.

I've known Nikki since she worked her socks off to save Geogre's Ormulum, and I've had both agreements and disagreements with her, but I've always found her willing to debate the issues and look for compromise - the last time she was blocked for edit-warring, I was able to successfully petition the blocking admin to unblock her as we had already made progress in resolving that particular issue. I know that she has regularly reached compromise with Gerda, and I'd point others to those interactions as one model of resolving differences. I do find her abbreviated edit summaries problematical, but I haven't seen any evidence of misuse of her admin tools. I therefore find the proposed desysop as unfounded, and I'd strongly suggest you look at ways of helping her contribute - why not 1RR and obligatory explanational edit summaries, as those are where the problems lie? The present drafting is reminiscent of curing headaches by decapitation.

Ok my rant is finished, and so am I. -- RexxS ( talk) 17:04, 17 August 2013 (UTC)

Comment from Olive to the arbs

I have no experience with the info box debate. I am familiar with Gerda's work, although not with Pigsonthewing. I did attempt to talk to Nikki after watching what appeared to be on-going stalking. What struck me when reading this Arbitration case was that it seemed out of focus, blurred, and with no clarity. The remedies for the most part are those saved for the worst offenses and all of it was lopsided ignoring the work of multiple editors which should have been scrutinized.

I would like the arbs to consider a few general points:

There are two kinds of issues which seem to come to the arbs. Wikipedia is a designated collaborative community. Its legs are the family of editors the encyclopedia stands on. As in any family behaviours arise which make editing unpleasant. Still, those behaviours while unacceptable can be remedied usually, as in a family, with strategies that do not require that the family member be asked to leave and set up a tent down the street. Members of this community are valuable, take a long time to train and for the kind of issues that create unpleasantness but which do not undermine the very fabric of the community lesser remedies are always best.

The second kind of issue is that which eats away at the legs of the community, destroying, not making unpleasant, but destroying the fabric of Wikipedia. That kind of behaviour is directed directly at other editors, is thoughtful, premeditated and is meant to damage editors so they eventually will leave. I mean more specifically the creation of narratives that create a false sense of an editor, fatiguing them deliberately, harassment, retaliation, bullying, talk page lynchings, and the lack of basic values most of us agree allow communities to function optimally like honesty and integrity ... and the list goes on. I'd add that these tactics have been applied to both editors and arbs. wearying the arbs as well as the editor.

I do not see that a general over arching distinction has been made that separates problematic behaviour from behaviours that are meant to deliberately harm other editors, undermining Wikipedia in the long run, in part because the behaviours which truly undermine are hard to see, the cases, high profile, and all of it harder still to believe. And I do not think the arbs have made this distinction either. Maybe I'm wrong. Once behaviours have been placed in either the "bickering family" slot or the more serious "undermining the fabric of the collaborative community" slot, remedies are easier to apply.

In this arbitration what struck me was that the bickering family had been treated to remedies that belong to more serious transgressions like the eventual undermining of the community creating that immediate out of focus sense I had. I don't see in the list of concerns in the Pigsonthewing remedy that indicate he/she has deliberately causing the kind of damage that requires an indef ban, and Gerda seems to be relatively blameless so I have to ask, please reconsider the nature of the problems and into which of these two categories the editors named in this case belong. I know this is tough job, and I can't imagine what the arbs deal with so this is not an attack, just an attempt to analyze and define, should that make the arb job easier and the remedies more likely to be fair.( olive ( talk) 19:24, 17 August 2013 (UTC))

Closing statement by Ched

  • First: Being concise is not my strong suit.
  • Second: I must take responsibility for my lack of direction in my original request (as pointed out by User:Giano), my lack of participation in the evidence stage, and perhaps most regrettably in my lack of participation in the workshop stage. For these failings I do apologize to both the committee and the community. (Worm That Turned and 2 other wikipedians are aware of the specifics as to the "why", but the reasons are not germane to wikipedia). I would also offer apologies to Gerda and Andy; as well as Nikkimaria and the other named parties of the composer group in requesting their attention to this case. Still, it was something I saw as a problem, and I thought could only be resolved by a full case.
  • Third: Montanbw above summarizes my thoughts well in the sense that I fully agree with much of what PumpkinSky, Heimstern Läufer, Thryduulf, and others say in that this PD falls short of an optimal solution to the infobox debate. Still, perhaps it is best I speak my peace in my own words.


  • To say that I am disappointed in this PD would be an understatement. I was hoping for a fair and equatable disposition to all sides. This is not it. It may well chill any discussions or inclusions of infoboxes in the near future; I would certainly hesitate to add an infobox to ANY musician, let alone "composer" after reading our ruling body's suggestions to a solution. In fact, I won't be the least bit surprised if infoboxes now begin to disappear from articles such as Paul McCartney, Tupac Shakur, Andy Williams, and others. Fortunately while our own article fails to offer certain amenities, Google does provide an "infobox" of sorts to things like Bach, in that quick date and place of birth, date and place of death, compositions, children, and spouses can be found without having to read an en.wp page.
I'm not attempting to commit wikicide by Arbcom, but I must say that frankly: After reading the original posting I must wonder if the Arbs even bothered to look at any links, comprehensively review any background, and actually follow through with clicking on "diffs" to determine a full picture of the forest. Often I see a "recidivism" statement, and I wonder if even the very basics were reviewed in this case. I do not dispute that this has been a "wp:battle" on wiki, but I remind all that it takes TWO sides to have a battle - one does not have battles on their own. Quite frankly this looks like a case of: "Hmmm .. there's 5 people in the composer project opposed to infoboxes (actually there are 25 regulars), and 2 people supporting infoboxes. Let's go with the bigger number, and hopefully that will translate to 'votes' in December". I apologize for the WP:ABF - and I'm not actually making that accusation, but the thought did cross my mind.
As far as specifics, the PD does mention in the FoF 2 blocks acquired by Nikkimaria for edit wars. Sorry .. but the actuall number is 3. Also, while "stalking" is a term that's fallen out of favor, here, still the harassment #hounding is not even addressed. (I also feel that addressing Wikipedia:Canvassing and Wikipedia:Tag team could have benefited the project here) Added to that the lack of any inclusion or mention of Kleinzach and Smerus, who's postings have been every bit as inflamitory and confrontational as Andy's, from this PD is somewhat puzzling. Indeed I would say that the committee is well on its way to declaring a "WINNER" in this debate. And no I would not support a permenant removal of Nikkimaria's tools absent evidence of misuse of those tools; however, I would support a time limited removal to recover the understanding of what the non-superuser editors must labor under. I understand there are members of the committee who do not favor this as it can be viewed as punitive; however, having worked under those very circumstances, I can say that it can be enlightening.
After long consideration I can now say that I suppose I felt that some sort of 1RR restriction on composer and infobox items would have been my preferred way forward here. I would also mention that Dave and David may want to add a "recidivisim" clause to the PD as it is often done in other cases. I'll also say that while I don't fully understand the "wikidata, metadata, microdata, what.ever.data" .. I do wonder if it positions Wikipedia better in the future of search engines. I also appreciate the Levels of consensus principle, but I'm not sure it's strong enough to explain the three levels. 1. Community 2. Group/Project 3. Article I feel that there's enough ambiguity there to further muddy the waters, and feel that further clarification would be of benefit.
Now, having berated the committee - I must also mention a few things that I found to be positive. I very much appreciate that both Dave and David were responsive to concerns, and communicated well with us. I also commend the lack of "legalese" in the PD - much easier to understand that way. While I have and do find many faults with the committee as a whole, there is not a single member of the committee that I do not respect both as wikipedians and as people. My own view is that the committee has grown far to large (and by extension: diverse) to be efficient, consistent, and productive; but I do appreciate the effort that all of you put in here. I know it's a tough job with little reward beyond the title.
Question: I have two pages I'd like to either delete or move to a public area:
  • User:Ched/RfC - Infobox - as this is a discussion with multiple people, it should likely be preserved - suggestions welcome.
  • This page should definitely be preserved and there is absolutely no reason why the discussion there shouldn't be continued, though you will need a strong guiding hand to produce an end result. If you read my comments up above and elsewhere, and those of some of my fellow arbitrators, you will see that there is very definitely a recognition of a need for such discussions to take place, even after this case has ended. The true resolution to meta-philosophical disputes such as this arise from widespread and well-planned community discussions, not from arbitration cases. The community need to continue discussing things and moving forward on this and other issues. But the discussion needs to be better planned than what took place there, and more widely advertised. Have a look at the 2010 RfC on microformats that is mentioned on the PD page for an example. Carcharoth ( talk) 22:34, 17 August 2013 (UTC)
  • User:Ched/infoboxes - a page I was working on to organize evidence, unless prohibited I will do a "user requested deletion" upon case closure.
Finally, Thanks to all. Apologies to all. Hopefully if/when I feel the desire to return to editing I will never hear the word "infobox" again. I will also be avoiding any of the Admin. related drama boards if/when I return. (at least for the foreseeable future) Cheers. — Ched :  ?  20:20, 17 August 2013 (UTC)


suggestions

  • "5) Wikipedia's mission is to built an encyclopedia" ... should this not be "build"? Built is a past tense. — Ched :  ?  21:04, 17 August 2013 (UTC)
  • "2) There is no general rule on infoboxes, meaning there are regularly debates regarding the use of infoboxes on articles. The debates are overwhelmed by a number of editors, who have been listed as parties on this case.". Very much a nit-pick, but I personally would say " ... some of whom have been listed in this case." I say this because I don't believe, in fact I know that not everyone involved was listed as a party here. — Ched :  ?  22:15, 17 August 2013 (UTC)
  • "6) Gerda Arendt (talk · contribs · deleted contribs · logs · edit filter log · block user · block log) has added infoboxes to many articles systematically,[12] and without prior discussion.[13]" I think you are getting dangerously close to choosing one essay over the other, and I suspect a "remedy" outside some clear and documented "warnings" falls well outside Arbcom remit. — Ched :  ?  22:25, 17 August 2013 (UTC)

Why no mention of User:Pigsonthewing's possible Conflict of Interest?

Pigsonthewing self-identifies as Andy Mabbett. On his User Page, Pigsonthewing links to his interests page: User:Pigsonthewing/interests. On that page he writes "My paid work includes delivering advice and workshops on and training in the use of Wikipedia and sister projects, for example and links to this page, where a short biography of Andy Mabbett includes the sentence "His [i.e. Andy Mabbett's] advice has been sought recently by organisations including Google and FourSquare (on their use of Wikipedia data); and The BBC, Facebook and the London Assembly (on microformats)." When I asked him if he had a WP:Conflict of Interest, Pigsonthewing twice referred me to this Interests page ( diff), but would not say if he has a COI.

I raised this possible COI in my evidence, and it was mentioned by Smeat 75 in their evidence, and mentioned by Riggr Mortis. Despite the fact that Pigsonthewing and his defenders wrote at length in the Evidence and Workshop and associated talk pages, no one else mentioned this apparent COI. To me this at least meets the criteria for reasonable suspicion, and I assumed that ArbCom would address this issue in some way.

Ruhrfisch ><>°° 13:12, 18 August 2013 (UTC)

Note also that in Resolute's evidence, they stated " I think Ruhrfisch's questions about potential COI and his relationship with those organizations are valid, and should be answered". Delicious carbuncle ( talk) 03:05, 19 August 2013 (UTC)

Comment from Choess

As an uninvolved party who's watched this with some interest, I think the PD is generally shaping up along reasonable lines. A few thoughts:

  1. If ArbCom is looking to restrict Andy in a closely tailored fashion to prevent disruption, I think the language of Remedy 1.1 is sufficient. Perhaps amending it to "adding infoboxes to articles or their talk pages or discussing the addition of infoboxes to articles or classes of articles" would make the scope clear. As I read it, this would not prevent him from developing new infobox templates or suggesting changes to existing ones, but their acceptance by the community would determine whether they were actually added to articles.
  2. I'm not convinced Remedy 1.2 should be off the table. Looking back at ArbCom's dealings with Jack Merridew/Alarbus/Br'er Rabbit and Rich Farmbrough, in both cases, ArbCom attempted to impose carefully tailored restrictions on technically talented contributors who engaged in disruptive behavior, hoping to retain their contributions. The subsequent history of both editors suggests that this approach may not be entirely fruitful.
  3. Contra Carcharoth, I think there's a very clear line between Andy's second RfArb and the current case. While the ad hominem conduct evident in the first RfArb and to some extent in the second has largely been replaced by parliamentary tactics, a quick perusal of the evidence in the second case will show the same essential problems (battleground behavior, inability to acknowledge adverse consensus), occurring in substantially the same topics (classical music, composers, opera) now before ArbCom.
  4. I tend to agree that the conduct of other parties rises to the level of admonishment at worst, but Gerda's recent statement that "To ban Andy is no solution at all, because - as I pointed out in June already - you will still have to deal with me until you ban me also ;)" suggests that Remedy 3.1 may be warranted as a preventative measure. Hopefully Gerda will clarify her intentions and make this unnecessary. Choess ( talk) 17:46, 18 August 2013 (UTC)
I clarify that you can ban a person, but not an idea. I believe that for almost every article, an infobox is not damaging it, but is a service to readers. I respect an individual editor's wish to not have an infobox, ask Tim riley. I am looking at opera articles where an infobox was made available but is opposed by some editors who don't like any infobox, - one of them mentioned dung. I am waiting for some more factual pros for keeping the present side navbox, which duplicates facts from a footer navbox, instead of an infobox for the specific article, example The Ban on Love. I am waiting to see how consensus can be established in case of disagreement. I believe that arbitration should serve this purpose. -- Gerda Arendt ( talk) 19:23, 18 August 2013 (UTC)
I saw my name pop up on the new notification gizmo. I confirm that wherever Gerda and I have disagreed over info-boxes it has always been in the most colleaguely and reciprocal way. Gerda is one of my most cherished colleagues, and our disagreement over this one matter is a side issue as far as I am concerned. I abandoned editing WP for some months last year in the face of what seemed to me to be bullying over info-boxes, but Gerda was assuredly not the culprit. Tim riley ( talk) 19:40, 18 August 2013 (UTC)
Duly stricken. I think you are the person most likely to be successful in promoting infoboxes in classical music and opera articles, because a) you know and write a great deal about these subjects and b) you're capable of backing down and working on other things when you find that other people don't agree with you. Good luck, and I hope we'll be reading your lovely articles about music for a while. Choess ( talk) 00:13, 20 August 2013 (UTC)

Uninvolved party

I know that this decision has the potential to impact editors' lives and may even shape policy about Infobox but after reading this talk page I went to go look at the Proposed Decision page and was surprised to see that only 3 or 4 Arbiters have weighed in, they haven't agreed on or objected to every single proposal (many are skipped) and it is very possible that minds could be changed if someone comes in with a compelling argument. I take the delay in other Arbiters posting their views is because it isn't a simple case (or they could all be on vacation!).

This is all to say that none of the proposals that impact specific editors has a majority of votes and a lot can change (for or against) in the next 24-48 hours. I would hold off celebrating or despairing until all of the votes roll in. NewJerseyLiz Let's Talk 21:16, 18 August 2013 (UTC)

Comments from Worm That Turned

I must apologise to everyone that I haven't had as much time as I would have liked to come up with a solution here. David and I were working together on a decision, then unfortunately real life stole me away from Wikipedia. I will be going on an indefinite wikibreak as soon as I've tied up a few loose ends.

So, here's a few thoughts, which might hopefully help the creation of a solution. Bear in mind that I came to this case unaware that there had been years of infobox wars.

  • Infoboxes, in general, appear to be a good thing. They allow information to be offer key facts about an article to our readers and facilitate reuse of our content. They are customisable to allow editors to decide what to put in or leave out.
  • Articles do not need infoboxes. If after discussion at a talk page it is decided that an infobox is not needed, that should be accepted.
  • The use of an infobox in an article is a content decision, not a maintenance decision. It should be added as part of content creation, and they should not be added systematically to articles.
  • Edit warring over infoboxes should not happen. Ever.

If anyone can create a solution out of those thoughts, please do!

Now, to a few editors specifically.

@ Pigsonthewing: I do see that you've managed to keep yourself from falling off the edge into an arbitration case for 5 years, since the end of your ban. However, you've carried on with many of the same behaviours, especially around infoboxes. I attempted to craft a solution whereby you could be removed from any discussion if you were dominating it, but it was pointed out that you are still on article probation and that clearly isn't working.
@ Gerda Arendt: I have seen systematic additions from you, please do keep in mind that infoboxes are a content decision, not a maintenance decision.
@ Kleinzach:@ Smerus: I have been unimpressed by the attitude you have both taken reading around the discussions, though little evidence was provided regarding it. You have tarred discussions with the same brush, refused to assume good faith about the actions of editors. Suggestions that infoboxes cannot be put on the talk page for discussion because someone might copy it onto the main page is clearly stifling discussion. There have been more incidents and if I have more time, I'll be adding something regarding them.
@ Nikkimaria: Again, I have been quite unimpressed by your actions, especially coming from an administrator. Reverting without discussion or explanation even in the edit summary is unacceptable. As is edit warring over these matters. I haven't looked far enough into the allegation of following edits to add that to the list, but overall it doesn't make for a good picture.

I believe that covers everything. I'll try to find some time to vote and possibly add some more bits over the next few days WormTT( talk) 09:05, 19 August 2013 (UTC)

(Reply from Gerda - to where I am addressed above)
I don't add where I think it's contentious (learning slowly...). I don't believe to add an infobox to a composition or story - my only cases of "systematic additions", like Schubert's masses, Kafka's short stories - are a content decision. - The newly developed infoboxes for opera should not be contentious, but I realize that they are and am more cautious. (Please see Siegfried: I only proposed on the talk.) - I am on 1RR, take any revert, there were many. I could have provided evidence against other editors but didn't want to. -- Gerda Arendt ( talk) 09:26, 19 August 2013 (UTC)
@Worm, re Klein and Smerus...they should have been part of the original proposed remedies, but glad you seem the need. Real life is more important, but within the AC world, I'd submit it's better to delay a PD and case closing in order to get a sound and fair decision that to rush and leave a swiss cheese decision. The problem of long term issues is a tough one. The only real solution is to for the parties on all sides to realize the problem and change and within the wiki world that's very difficult to do. PumpkinSky talk 10:01, 19 August 2013 (UTC)
Part of the reason for the delay we had was that I was unable to keep working on the PD. As time went on, I became less available, not more. I'm not going to hold up the case for an indefinite period on the vague hope that I might suddenly get more time, especially given that it is unlikely to happen. WormTT( talk) 10:18, 19 August 2013 (UTC)
Well, some arb needs to pick this up because right now this is an atrocious PD. It's better to delay against than make a bad ruling. PumpkinSky talk 21:16, 19 August 2013 (UTC)
The committee is tasked with making a decision which resolves the problem. I may see areas for improvement in the PD, but I'd hardly call it atrocious. WormTT( talk) 09:30, 20 August 2013 (UTC)
@Worm: I reverted without edit summary on a single occasion, and had already long agreed not to do so again. And yet there is no mention in the PD of rollback being abused to revert me. The PD also characterizes my participation in discussions as "sniping", based on a talk page demonstrating neither incivility from me (though one comment was admittedly sarcastic) and worse behaviour from others not mentioned, and ignores multiple diffs of both incivility and gross personal attacks presented by a variety of people in Evidence. I admit that some of my actions with regards to these debates were suboptimal, and have endeavoured to improve my responses more recently and reach a compromise with those on the "other side". But if the PD as presented reflects the overall picture, it's missing a few pieces, and is unlikely to either solve the problem or encourage a more collaborative approach. There were a few good ideas on both "sides" in the workshop - isn't it possible to consider more of them? Nikkimaria ( talk) 16:30, 19 August 2013 (UTC)
I apologise, I had not seen that you had agreed not to do so again and that does make the situation better. Could you provide diffs for rollback abuse? I appear to have missed that too. I'm afraid the reason that you've been singled out is that you are an administrator, you should be setting the example for the rest of the community. Effectively, you should know better. WormTT( talk) 09:30, 20 August 2013 (UTC)
(watching and involved) Nikkimaria and I arrived at an agreement of mutual respect, so much better than restrictions if you ask me. She has been singled out because she did most reverts of infoboxes (about 20). As you can see here, her edit summaries improved greatly from "cleanup" (#28 Sparrow Mass) to "rm: several errors or oversimplifications, net negative; also per previous agreement. feel free to discuss on talk" (#49 Cantata academica). Both discussions are open. -- Gerda Arendt ( talk) 09:49, 20 August 2013 (UTC)
This one was presented in Evidence, same paragraph as some CIV/NPA diffs. Nikkimaria ( talk) 03:47, 21 August 2013 (UTC)
Thank you Nikkimaria, that has helped, sorry I missed it. WormTT( talk) 09:54, 22 August 2013 (UTC)

@Worm: See my comments in "my" section above. I am concerned about your comment "and they should not be added systematically to articles..." - MANY wikiprojects have a standard article design that DOES in fact ask - nicely and informally - that an infobox be part of the standard article layout (note WP Horse racing, for example, see, e.g. Paynter (horse)). While I suppose someone who is an anti-infobox fanatic may insist that they "own" an article in project and demand removal of an infobox there, I really do think that the projects can be allowed to recommend a starter template and a standard design, even if they can't "demand" it. Ditto things like chemistry ( oxygen) or gems like the Yogo sapphire. Just saying. Montanabw (talk) 21:33, 19 August 2013 (UTC)

I think that's a very sensible position, but should not the reverse also be true, that WikiProjects can recommend, if not demand, that an infobox be omitted from the "standard" article on the grounds that infoboxes usually do a poor job of representing that subject's articles? (cf. the recent removal of the "influences" parameter from Template:Infobox person: I'm sure there are a few cases where it could be used reasonably, but consensus seemed to be that it was more an attractive nuisance than a useful tool.) Choess ( talk) 00:35, 20 August 2013 (UTC)
Indeed. I have long supported the ability of projects, not set in stone, to either mandate and deprecate infoboxes for particular types of articles. But in the types of articles that are expected to add them, someone else will come along and do it. Johnbod ( talk) 01:31, 20 August 2013 (UTC)
"Sensible position": the name of my project is opera. The project made an {{ infobox opera}} available in June, concise and in keeping with the recommendations in Brianboulton's Signpost essay. I tried it in operas. Some are accepted, others were (rather systematically) opposed and reverted by those who don't like infoboxes for composers. See for example Götterdämmerung and feel free to join the discussion. -- Gerda Arendt ( talk) 08:30, 20 August 2013 (UTC)
I had an initial (not positive) reaction to Worm's ".. not be added systematically…' comment. However, after thinking about it, I believe Worm has a good point. Some of the concerns here are founded in a different interpretation of "systematic" than I came to have after reading carefully. We have many editors who perform valuable maintenance tasks. In many cases, those edits can be done "systematically" and without needing an expert's understanding of the subject matter of the article. I'll give an example. I recently created a task force on women's basketball. We do not yet have a template for the talk pages, but once one is created, I can imagine an editor finding an appropriate cat, and "systematically" adding the template to all articles in the cat. That can be done by an editor who knows little about the subject. In contrast, I think Worm is suggesting that such a "systematic" edit is not such a good idea with infoboxes. Even if some Wikiproject identifies the inclusion of an infobox as best practice, and an editor finds a cat whose every entry is within the project, it would not be wise to " systematically" add the infoboxes. Why? Because infoboxes take parameters. If an editor plunks a blank infobox into an article, it will make the article look unfinished until someone populates the fields. If the editor chooses to populate the fields, they might get some right, but might blunder on others. In many cases, it take an editor who is conversant with the subject matter to properly populate the infobox. An empty infobox is arguing worse than nothing at all , an improperly filled one is arguably worse than an empty one. If a maintenance editor wants to do something, perhaps they should add a note to a talk page informing editors that there is a suitable infobox, but leave the actual adding of the box to the editors who know how to populate it. Worm is suggesting that infobox addition be part of the content creation process, not part of a maintenance edit. -- SPhilbrick (Talk) 18:47, 20 August 2013 (UTC)
Dave does make an interesting point, but there is no policy or guideline that supports the notion that "systematic" addition or removal of infoboxes is frowned upon (other than a local RfC at one WikiProject) - indeed, such a recommendation would hinge upon each person's idea of "systematic". We need to discuss what is best to do whenever either a new infobox template is created to meet a particular demand (such as {{ infobox opera}}), but also we need to consider how to make use of a database that has been created. What if I come into possession of a verified database of notable monuments in Bavaria as used in ? May I use {{ infobox monument}} to make use of that data where we have an article already, or would that be "systematic"? Could we systematically translate the articles from de-wp, adding infoboxes as we go along? Commons:Wiki Loves Monuments generates many such databases from many countries and there's a debate to be had about how we can best use such data, so I think that a ban on "systematic" additions would be premature, and certainly far too early to base a sanction upon. -- RexxS ( talk) 01:05, 21 August 2013 (UTC)
I would disagree that no policy or guideline supports the notion. The very fact that infoboxes should be discussed at each individual article makes it a content creation decision. Assuming we can divide the types of edits people make into content creation and maintenance, then the addition of an infobox falls into the former, not the latter. For clarity, I would consider maintenance to be tasks such as categorisation, stub sorting, adding wikilinks, formatting and stylistic changes such as number and position of headers or placement of images, and simple copyediting such as grammar and spelling fixes. In general, these should not change the meaning of the article for the casual reader. Content creation on the other hand, would include addition and removal of text, images, tables, references and so on. The addition of an infobox should be considered part of the latter. The distinction is important as the former can be done by any editor on any article with minimal knowledge of the subject, whilst the latter should be done by an editor who has some knowledge of the subject, more than a cursory glance at the article.

As to your questions, RexxS, if you are creating the articles and have sufficient knowledge and understanding to write a stub based on the verified database, I see no reason why you should not be adding an infobox at the same time. That is part of content creation, and it is recognised that diligent mass content creation is acceptable. Similarly with translation, if you are diligently checking sources, you will have sufficient understanding to add the infobox. WormTT( talk) 09:54, 22 August 2013 (UTC)

And yet there still is no policy or guideline that recommends against systematic addition of content. For example, there are a lot of stubs about plants and Indonesian administrative regions (if I recall correctly) that were created from a database. There were complaints, of course, but the overall opinion was that once we get a basis for an article, then other editors will improve what is there. So it is with infoboxes; if one is added, then it is likely that its content can be refined by adding or removing parameters. I was actually posing the question about adding {{ infobox monument}} to make use of a database where we have an article already - is the answer the same as if we were creating a stub? If so, then I have to take issue with your underlying assumption: that there is a binary division between an editor with "minimal knowledge" and an editor who has "some knowledge of the subject". There is a continuous spectrum of knowledge on any subject and it is a recipe for conflict to allow editing only from those who claim to know the most. By that logic, if Andy were an expert on classical music, you'd be perfectly happy with him adding infoboxes - and yet he wrote a monthly column for a classical music magazine, so he demonstrably has more than "minimal knowledge". In the first half of this year, he added about 60 infoboxes, and more than 50 of those were accepted without a problem. Nikkimaria reverted 6 and Andy walked away from each of them, as I had advised him to previously. I'm sorry but that is not a battlefield mentality. The problem I complain about is that additions of infoboxes - no matter by whom - in one small area are invariably met with a revert by the same handful of editors with the only reason being that it wasn't notified to WikiProject Composers first. If you don't tackle that ownership problem (tq|"Please clear this with WikiProject X first"}}, we'll just be back here in a month's time. -- RexxS ( talk) 12:57, 22 August 2013 (UTC)
I see no issue with a starter template, or a general explanation that infoboxes are recommended or not by any WikiProject. The ultimate decision though comes down to discussion at the article. Editors should not go through a group of articles, adding infoboxes to each systematically, or indeed removing them in the same manner. There's a difference between "recommending" and enforcing the recommendation. WormTT( talk) 09:30, 20 August 2013 (UTC)
I am not sure I understand what you mean by "adding systematically". As it has been used in findings about me, I guess I better understand. When I add an infobox, I know how to fill the fields, be it an opera, a short story or a church. I typically don't have time to add infoboxes to articles other than my own, those related to them or otherwise of interest to me. Is that "systematic? Unwanted? Once the template for operas became available I tried to use it, because I am interested in operas and sincerely believe that opera articles are better with an infobox instead of a navbox that is uniform for all articles by the same composer. Look at GA (as of today) Fatinitza and compare to before. -- Gerda Arendt ( talk) 19:32, 20 August 2013 (UTC)

Comment from Giano

Ched is a friend of mine and one of Wikipedia's good people, so I sincerely hope he won't be offended by me saying that the bringing of this case was somewhat naive - especially, as the obvious conclusion has to be the exclusion of the main player and protagonist, Andy Mabbitt; something I wholeheartedly support and that I suspect Ched does not. However, Ched should not be too downhearted: some good can come of the case and it should be the unequivocal endorsement by the Arbcom of this finding [46], regarding the 'Use of infoboxes', because it gives those of us who feel downtrodden by the pro-infobox crowd something concrete to quote in all the many future debates/wars on this subject on pages from music and architecture to outer space. As a postscript, I would ask the Arbcom to go gently with Gerda; she's a good editor and she means no harm - she's a little hung-up with the use of infoboxes, but I think she amicably accepts that they are not everyone's choice. Anyhow, that's my view on what is probably an unsolvable problem.  Giano  20:46, 19 August 2013 (UTC)

Offended? Absolutely not Giano. In fact, I'm outright honored to be considered a friend - and I do very much appreciate you trying to guide me to take some sort of direction in the beginning. Naive? Yes, I do have to plead guilty to/of that. Sadder yet is the fact that I actually communicated with a former arb, and was told exactly what to expect. (quite accurately I might add) My request was born out of frustration at all so many discussions on the topic. I did learn a few things though. First: have a target in mind, be willing to point fingers, have the diffs, and be willing to go for the throat. Use the diffs in evidence - then give what you want in the workshop with the FoF, and ask for bans in the remedy. There should have been at least a dozen other parties to this case (on both sides) which I was reluctant to name. Not really my style, so I doubt I'll ever return here. Yes, you're right - I do NOT want to see Andy banned - I think he has far too much positive impact to offer the project, so I guess we'll just disagree on that part of it. Not that I'm a full-blown "add infoboxes to everything" person - in fact your examples of a historic building is a good example where I'd agree that it would be counterproductive to add one. Still, when it comes to people - I do favor them (generally).
I do feel bad for the position that I put Dave/Worm and David in though. I dumped everything in Arbcom's lap, stepped back and let the chips fall where they may (partly out of necessity due to unforeseen things in real life) and hoped they would find or invent some sort of 1RR thing, and state that "Projects" can not "own" things, "canvass" and "tag-team" editors who are trying to improve articles. While being creative has happened in the past (Delta/Betacommand) - apparently that is not S.O.P. It seems that the Arbs must work with what is presented in the workshop, and without anyone building a case against the composer group ... there was only so much they could do. I am encouraged that Nikkimaria and Gerda are working together, and I even see signs of Nikki taking things on board - that I am very happy about. I'm also very encouraged by the fact that Dave/Worm and David stayed with us, were responsive and communicated and updated everyone thoroughout. Add to that the fact that Carcharoth put quite a bit of time into reviewing things, and offering suggestions to a way forward? Yes, as much as I see this particular committee as one of the most inept I've ever seen (the Malleus/George situation is a good example of that), the individuals are impressive to me.
I'll continue to login and check my talk page until this is closed. I'll continue to fix typo and syntax items where I can, even if I'm not logged in. I am tired though. Over the last year I have alienated people who were friends. I took sides against people who were friends because I thought it was right for the project. I was not "loyal". I did what I thought was right in my heart. I'm tired of admins. being "super-users". <aside> I know that a lot of kids will shortly be returning to school (which should alleviate some things). Still, I am tired of the bullshit. Years ago I was very proud of what I did here. The work I put into WP:RIP is something I will always be proud of. In the beginning I was even proud of being an admin. ... not so much anymore. I've met a lot of great people here, and I am happy about that. Still, I think when this case closes I will need a break. But I am rambling here .. so I'll close with "Best to all" Thank you for the kind words you've offered me Giano. I do consider it high praise indeed. — Ched :  ?  04:09, 21 August 2013 (UTC)

Comment from John Cline

I had resolved to stay out of this discussion; to observe and learn if you will. All I managed to learn however was more about my own weaknesses. I find I am incapable of observing the mistreatment of an esteemed colleague without intervening aid. Also I find, if I reply to provocation, I am not proud of my prose; instead—ashamed!

Please understand that when not discombobulated, my stringent endeavor is to publish prose that I can be proud of; even succeeding at times. Yet the error is mine for having not further endured.

Help me to better endure by allowing that I edit under the enduring principles that founded this great site. Principles that do not embrace debase provocation; allowing one to withhold their own indignation in favor of observing the institutional retribution that is all but assured in policy.

It is well known that a plethora of policy insight is ignored, so the belligerent can edit this encyclopedia. Perhaps this is not an unsolvable problem after all? Instead, simply an example of one that can not resolve by ignoring all rules:)  John Cline ( talk) 09:04, 20 August 2013 (UTC)

Couple more thoughts

A couple more thoughts here to try and help clarify some things (see also the section above that I added earlier).

  • Firstly, unlike Worm That Turned (who "came to this case unaware that there had been years of infobox wars"), I and several other arbitrators have been very aware for years of the tensions surrounding infoboxes. But this doesn't mean that we are able to provide a panacea or that an arbitration case will provide a 'silver bullet' that will magically resolve these tensions.
  • The only thing that will help improve matters in the long-term, and it is worth repeating this again and again until people actually get it, is to have productive 'big picture' discussions that help editors settle on best practice and sort through any differences and disagreements they may have, and then people can carry on with writing articles and curating article content. Some people are able to discuss things calmly and work through their differences, or explain clearly why they disagree. Some are not able to do this, and need the help of others (or to be kept away from such discussions).
  • Infoboxes are templates designed to summarise key points, not just in a single article but across a range of articles. This is why there is a difference between systematically adding infoboxes at random (e.g. to a list of articles created by a single editor) and systematically adding infoboxes to articles in an area an editor (or group of editors) have some knowledge of and have considered carefully the best way to present the information in an article. This is why infoboxes tailored to specific subject areas can be helpful - it shows that a group of people have considered the various options and how best to present the information common to a range of articles within the same topic area. When you get broader infoboxes such as those for people in general (most of my experience with infoboxes has been on biographical articles), then it becomes more difficult to handle and a case-by-case approach is usually needed. Ditto for other topics.
  • The key point is to also have discussions about groups of articles, not just individual articles. To form consensus at a group level as well (to avoid endless discussions on individual articles), but to still strike a balance that allows maximum flexibility and exceptions where needed (such as not using an infobox if that is desired). Sometimes the merging of infoboxes helps focus such discussions, sometimes excessive merging hinders such discussions. What you don't want to do is end up with the bureaucracy that is sometimes associated with the requested move process - that evolved to help people resolve differences over article titles, hopefully people can resolve their differences over infoboxes without needing anything like that.
  • It may help to draw an analogy with discussions about whether to include an image in an article or not, or whether to include an article in a particular category, or how to write the lead section. Those discussions can get contentious, but the nature of infoboxes, placed at the top of an article and performing a similar but different function to the lead section, makes them particularly prone to causing certain types of arguments.

The whole argument about metadata and data in articles is something else again. That needs several rounds of proper community discussion. Anyway, most of the above isn't anything new, but the community absolutely needs to have proper, structured discussions, planned and properly publicised. A key part of the planning is sorting out where to publicise discussions, and having a representative selection of people working together to produce a summary and questions suitable for a community-wide request for comments (some of the workshop material is a good start). This can be a long and difficult process, but it would be better than endless low-level arguing. ArbCom can suggest that this should happen (I've suggested it to my colleagues), but we can't (and shouldn't) require that to happen - the real impetus needs to come from those willing to participate in such a process. Carcharoth ( talk) 23:31, 19 August 2013 (UTC)

Looking at the PD, it seems like the decision will actually have little to do with Infoboxes and everything to do with conduct and a lack of collaboration (conduct, not content). It's about how differences are settled (or mishandled) and the fundamental content/policy issue could be almost anything - Infoboxes, COI, NPOV, anything that causes division among people (which is almost everything).
It reminds me of political scandals where the scandal isn't the news but the cover-up is. I'm not sure how much it would help but I think more should be written, policy-wise, on negotiating conflict when trying to come to a consensus. Mostly I see consensus arriving when one of the parties decides the fight isn't worth it, not because anyone has changed their mind about the issue of contention.
I think WP policies on consensus underestimate how difficult it is to arrive at, how conflict is to be expected and what should happen when differences appear to be irreconcilable. I'm not sure what the solution is but I think if people saw conflict as predictable and not exceptional, a lot fewer cases might arrive at the ARBCOM doorstep. Liz Let's Talk 00:56, 20 August 2013 (UTC)
I am rather new to the topic of infoboxes - as you all know from my evidence I was against them and converted, - very dangerous ;) - I believe we need a better way to discuss their flaws and merits. Sorry, I don't think that it happened (yet) in the often quoted Rite of Spring discussion which Andy started by only asking "Why ... no infobox?" (Now how disruptive is that?) - I started to discuss a very simple example, article type opera, template new and concise: The Ban on Love, - help there please, let's make it a model discussion! - I don't believe that we achieve progress by restrictions. -- Gerda Arendt ( talk) 08:48, 20 August 2013 (UTC)
@Carcharoth: yes, I hope that the model discussion could serve operas in general on a "group level".
@Liz: no, I did not foresee conflict on operas as predictable, - and still nobody could point out why a side navbox duplicating information from a footer navbox would be superior to an infobox on the specific article, - but I am open to learning. -- Gerda Arendt ( talk) 08:56, 20 August 2013 (UTC)
One of the articles where infobox opera was installed was just promoted to GA: Fatinitza. -- Gerda Arendt ( talk) 09:58, 20 August 2013 (UTC)

Comment from Victoriaearle/Truthkeeper88

Reading all these comments, and well-aware I'm not one of the people who can discuss calmly as per Carcharoth's statement above, it occurs to me that this case is about pure frustration and that's a tough one for the Committee to address.

Some background for Committee members unfamiliar, because a pattern exists and it's not only about classical music - that's simply the arena where it ended up. It began in early 2012 and is still ongoing, and honestly my own frustration has boiled over more than a few times during that period. Some examples for those of you unfamiliar with the tactics and the players: Ezra Pound in February 2012, Murasaki Shikibu February 2012, Ian Fleming July 2012, George Solti July 2012, Melville Island August 2012, Pilgrim at Tinker Creek September 2012, AN Br'er Rabbit community ban, October 2012, Andreas Sholl March 2013, Sparrow Mass March 2013, followed by many more in the classical music project, one of the more notable being The Rite of Spring, the day after TFA, May 2013 and now referred to as the "Ban on Love" on multiple pages. This then progressed to various music related articles which I didn't follow but was vaguely aware of.

The issue, however, in my view is not about infoboxes. The issues are deeper, more entrenched, causing enormous damage in terms of attrition of highly productive editors, and for at least a year and a half has needed attention.

In terms of how the arbiters are to handle this, I'd suggest to follow your inclinations, ignore pleas (including this), do the job you were elected to do (and like all the rest of us, it's frustrating to work for free), and decide how to eliminate the disruption.

In terms of individual editors, I'd suggest looking at their overall record. For example, Nikkimaria has a record of pitching in ceaselessly to keep copyvio from the mainpage, in checking sources at FAC (for a while she was the only person there doing that and as far as I know singlehandedly checked each nomination) and is an enormous asset to the project. Look at each editor's contributions, assets, and weigh it up. I think this is very tough and important case. If it needs to go back to the drawing board, do so. If you all know how to vote, do so and put us out of our misery. But realize that a lot of content producing editors who could be reviewing and writing are currently tied up here, or just plain frustrated and work has ceased. That is not good for the project.

Thanks. Victoria ( talk) 05:53, 20 August 2013 (UTC)

May I factually clarify that you seem to confuse The Rite of Spring and "The Ban on Love". One is a ballet by Stravinsky, the other the translation of Das Liebesverbot, an opera by Wagner. Both articles are no biography. I tried to initiate a model for how reaching consensus might work in an infobox discussion, The Ban on Love. Please take a look. You may also want to look at a comparable work, where an infobox was accepted without disruption and frustration: Fatinitza, a GA nominee. For discussion as I like it see Peter Warlock. I agree that Infoboxes is not the topic of the case, - reasonable discussion about infoboxes should be. There is hope. -- Gerda Arendt ( talk) 08:03, 20 August 2013 (UTC)
There may be hope, but I fear that it, and any remaining goodwill towards you and your mission, Gerda, is dwindling fast as a result of your relentless persistence. For example, I have engaged in a perfectly civilised debate with you concerning infoboxes on the Peter Warlock talkpage; I understand your position, and have made my views clear there. So why, the very next day, did you have to introduce the same issue into the peer review of my current music project, Symphony No. 8 (Sibelius)? This fanning of the flames is a tiresome and unnecessary provocation. I do not wish to stifle debate, and I think it possible that a form of infobox might eventually be devised that is appropriate to the character of all Wikipedia articles. But this will require some wholesale rethinking on the concept itself, not just the adaptation of the existing model. My recent Dispatches article was a contribution to that discussion. However, very few positive steps will be taken in the atmosphere of antagonism and mutual annoyance that envelops this whole topic. And I entirely endorse Victoria's sentiment: we all have better and more productive things we should be doing. Brianboulton ( talk) 11:14, 20 August 2013 (UTC)
I am sorry that you see a proposal as "relentless" that I thought was a reasonable solution to the problem to show at a glance that the Eighth Symphony by Jean Sibelius is a composition project, not a composition. I am fine with your decision to look for a different way to show that. I was fine with your decision not to change Warlock now. - Sorry, I didn't see a problem (fanning of flames, provocation, annoyance), but will avoid it now, with respect for your view. - What do you suggest we do until that future concept will be developed? And how do we develop it if not by thinking about the options we have now? How do we overcome an atmosphere of antagonism that I - late to the topic - obviously don't take into account enough, and certainly don't want? -- Gerda Arendt ( talk) 11:42, 20 August 2013 (UTC)
I think the best thing would be to let the issue rest for a while. It is sucking too much creative energy out of the process. As I have said, there are more issues related to infoboxes than that of the reluctance of music and opera editors to adopt them, and the matter will not go away (I intend to return to it in a future Dispatches article). But if anything positive is to be achieved, there needs to be a calmer atmosphere, so if I were you I would adopt an informal temporary vow of silence on this issue. You can continue of course to work on your ideas in your sandboxes, and can invite comments there, but you should steer clear of initiating any new discussions and should generally avoid article talkpages and reviews. That would do a lot to defuse the atmosphere of antagonism to which you refer. Brianboulton ( talk) 15:52, 20 August 2013 (UTC)
Thank you, taken. I said before that I don't add any more Wagner opera infoboxes until Götterdämmerung is resolved etc. - Please forgive me Sibelius. I saw you hesitating for the composer, but thought a composition was not the same problem, mea culpa. The same way I expected operas to be less of a problem than composers, especially with an infobox developed by the project which - I think - fits the requirements for conciseness your article pointed out. But obviously I was wrong. Why - that may be part of your next article. In expectation, -- Gerda Arendt ( talk) 16:20, 20 August 2013 (UTC)
I note that Victoria has yet to address the demonstrably false statements made in her evidence, which she reinstated (after an earlier deletion), unaltered, after their falsehood was demonstrated. . Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:32, 21 August 2013 (UTC)
It is currently impossible for Victoria to edit Wikipedia outside her talk page, since she has been blocked for three months (by me, at her request). Ruhrfisch ><>°° 13:48, 21 August 2013 (UTC)
Not only did Victoria post a lengthy comment, above, yesterday, but she made 32 other edits in the last week. In none of these did she address the clear discrepancy between her false claims and the demonstrated facts. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:11, 21 August 2013 (UTC)
Pigsonthewing, let's look at your statement and then do some counting of edits.

At Wikipedia:Arbitration/Requests/Case/Infoboxes/Workshop#Evidence_by_Victoriaearle you wrote: Victoriaearle asserts that, following the Pilgrim at Tinker Creek discussion in September 2012, the "primary editor", User:Yllosubmarine, "became discouraged and left the project" and that we thus "lost a prolific female content editor". As can be seen by examining the edit logs, Yllosubmarine was editing as recently as two or three of weeks ago; as she continued to do throughout October and November 2012. The evidence appears to be blatant falsehood. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:21, 3 August 2013 (UTC)

While I agree that Yllosubmarine has not entirely "left the project", look at her contributions before and after her encounter with you over Pilgrim at Tinker Creek: X!'s Edit counter for User:Yllosubmarine. By my count, in the 10 months before your exchange in Sept. 2012 (i.e. Nov. 2011 to Aug. 2012) Yllosubmarine made 914 edits or 91.4 edits per month. In the 10 months after (Oct. 2012 to Jul. 2013) she made 88 edits or 8.8 per month on average (a decrease of just over 90%). Please note that I do not count her 90 edits in Sept. 2012 (as that month was split in terms of before her encounter with you vs. after), nor do I count her 0 edits to date in Aug. 2013 (as the month is not complete). How is this not a case where Wikipedia "lost a prolific female content editor"?

Counting another way, Yllosubmarine was a major contributor to 14 FAs and 14 GAs. She started editing in Jan. 2006 and really started contributing around Jul. 2006, so to Sep. 2012 this averages out to roughly two FAs and two GAs where she was a major contributor per year. in the 11 months since her encounter with you over Pilgrim at Tinker Creek, she has been a major contributor to zero FAs and zero GAs and a quick look at her contributions shows the vast majority are maintenance edits (things like reverting vandalism or minor copyedits). Yes, she technically did not leave, but I ask you again, how is this not a case where Wikipedia "lost a prolific female content editor"?

Pigsonthewing, I think you owe Victoria an apology. Ruhrfisch ><>°° 20:23, 21 August 2013 (UTC)

I note that you choose to start your count in November 2011. In October 2011, Yllosubmarine made only 34 edits; in September 2011, just 27 (fewer than in October 2012); August, 31. In July, it was as low as 18; in June, only 20 (again, both fewer than in October 2012). Lies, damn lies and statistics, eh? But thank you for proving my point: Yllosubmarine did not "leave" " Wikipedia. Victoria's evidence is false. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:37, 21 August 2013 (UTC)
What part of my statement that I agree that Yllosubmarine has not entirely "left the project" do you not understand? Yes, her output varies over time, but I chose two periods of equal length to compare. Do you maintain she is still a prolific content editor? (The "female" part is not in dispute - that is a joke on my part)? Can you not see that your fighting every jot and tittle to the bitter end is precisely why you have twice been banned for two years and are now in this mess? Give it a rest. Ruhrfisch ><>°° 20:47, 21 August 2013 (UTC)

PS For my own mental health, I am removing this page from my watchlist. I will be without internet over most of the weekend, but if my input is required, please let me know on my talk page and I will comment as soon as I am able. Sorry, Ruhrfisch ><>°° 20:38, 21 August 2013 (UTC)

Invitation to AGK

@ AGK: Regarding [47]: despite the arbitrators' duty to examine evidence presented in a case, It sees that you may have missed this, in which I say:

Some editors have referred to my block log. Block logs are notoriously crude and errors in them are rarely corrected. In reverse order:

  • 31 December 2012 - erroneous, for a supposed edit war, 27 hours after making my first and only edit to Hans-Joachim Hessler in five days. He [ Mark Arsten ] subsequently apologised to me off-wiki, confirming this via the summary of a null edit, in evidence.
  • 22 March 2012 - Future Perfect at Sunrise blocked me for supposed BLP concerns, undoing his contentious block with the summary "clear emerging consensus for topic ban". In fact ANI levied no sanctions for my editing, which was within policy.
  • 25 January 2009 JzG blocked for 3RR, then undid this after just twelve minutes, admitting he had miscounted.

That means that the last valid block (again that's disputable, but I won't labour the point here) was five years ago. (21:50, 3 August 2013 (UTC))

Further to the above, the "BLP concerns" were discussed here; and continued here. At the latter, Kim Dent-Brown makes clear of the former, in his opening comment (21:08, 3 April 2012; my emboldening):

There was a similar proposal at AN which can be seen here [link to that earlier discussion] but this was never agreed upon.

and the second discussion was closed (over a year ago) by CambridgeBayWeather (19:37, 7 April 2012) with the summary (again, my emboldening):

There appears to be no consensus here to do anything. I would suggest that everybody take a few days off from throwing things at each other, which is what this has degenerated into, and go make some useful edits.

There was no topic ban; and the block was clearly contested by other editors and admins. I therefore invite you to remove or strike your false statement and recast your vote accordingly. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:22, 20 August 2013 (UTC)

Pigsonthewing: Thanks for your comments. I'll look at the links you have provided regarding your block log, and then reconsider my vote, okay? (You will have to forgive me for forgetting about the evidence submission you quote above; the evidence page is one of the longest we've had in a case for some time.) AGK [•] 23:38, 20 August 2013 (UTC)
@ AGK: I notice that you have just commented on your vote, and made a minor copy edit to it, but have - remarkably - let the false claim of a topic ban stand. Why? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:39, 27 August 2013 (UTC)
@ Pigsonthewing: Is this not a topic ban? AGK [•] 09:57, 27 August 2013 (UTC)
Your vote says Blocked then topic banned for inappropriate edits to a BLP in 2012. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:02, 27 August 2013 (UTC)
Okay, I understand your objection. I thought you were claiming that there was no 2012 topic ban. In order to resolve this thread, I've corrected my comment. AGK [•] 10:11, 27 August 2013 (UTC)

Invitation to Pigsonthewing

@ Pigsonthewing: Regarding your statement above that "arbitrators" have a "duty to examine evidence presented in a case" and your often expressed concern that no one make false statements, would you please address my concerns about your possible conflicts of interest, especially with regard to WP:COI? If needed, I will gladly point you to the relevant evidence I gave or my query above, or to the requests by multiple other editors that this issue be addressed. Thanks in advance for your cooperation in this matter, Ruhrfisch ><>°° 17:45, 20 August 2013 (UTC)

I have responded to your request more than once, with a link to my published declaration of interests in my userspace. However, since you either fail to understand that, or insist on attempting to smear me with innuendo, or both, I will explain: I have no conflict of interest regarding my infobox-, microformat-, or metadata-related editing. I have received no payment from any organisation in regard to such editing. My potential conflicts of interested are all listed at that page. If you have evidence to the contrary, or in any way showing malfeasance on my part, you will no doubt now provide it; as you have provided none so far. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:00, 20 August 2013 (UTC)
Thank you for providing a more detailed answer than previously. I have no other evidence than your own words and links, but just to be clear (since, as you note, I "fail to understand" what is going on here), I want to ask another question. You write on your interests page: "My paid work includes delivering advice and workshops on and training in the use of Wikipedia and sister projects, for example" and then you link to this page, where your short biography includes the sentence "His [i.e. Andy Mabbett's] advice has been sought recently by organisations including Google and FourSquare (on their use of Wikipedia data); and The BBC, Facebook and the London Assembly (on microformats)." To me, this sounds very much like you are paid for your advice by these organizations. Since you are also a strong advocate of the commercial re-use of Wikipedia data and Wikipedia's use of microformats, how is this not "paid advocacy"? Please note that WP:COI says "paid advocacy is considered to be an especially egregious form of advocacy. Paid advocates are very strongly discouraged from direct article editing, and should instead propose changes on the talk page of the article in question.". Yours in failed understanding, and thanks again in advance for your cooperation in this matter, Ruhrfisch ><>°° 18:34, 20 August 2013 (UTC)
PS I originally used the British spelling of "organisations" and a [sic] above, as an attempt at humor. I did not think that it might be taken as unkind, and apologize (as that was not my intent). 21:17, 20 August 2013 (UTC)
I'm not sure how you can read Andy's "I have received no payment from any organisation in regard to such editing" and still maintain that you think he's been paid, based merely on a surmise you've made from reading his brief biography. I have some experience with dealing with CoI and as it happens I spoke to Andy today. During the conversation, I asked him "have you received any payment from any of those organisations you named as having sought your advice?" and his reply was "No". I checked we understood each other by naming 'Google', 'BBC', 'Facebook', etc. and he was equally clear that he had never received money from them, but he supplies his advice freely. He confirmed to me that his paid work has been in connection with helping museums and other GLAM institutions in making use of the Wikmedia projects as a Wikimedian-in-Residence. I'll tell you this in case you still can't understand it: you simply cannot generate a conflict of interest from that, because his paid work is not in conflict, but in alignment with our object of producing a free, neutral encyclopedia that is available for all - otherwise you are going to be accusing all of our Wikimedians-in-Residence (not to mention all of the WMF staff and contractors) of "paid advocacy". Now if you want him to confirm what he said to me today, please feel to ask him whether I have accurately summarised our conversation; but I am becoming increasingly worried by your obsession with this non-issue, as it is starting to look like a smear; repeat an untruth often enough and people start to believe it. You need to consider carefully before making any further unsupported accusations. -- RexxS ( talk) 00:30, 21 August 2013 (UTC)
I agree - it is hard to imagine who would have any incentive to pay for infoboxes to be created on 19th-century composers etc! Johnbod ( talk) 00:59, 21 August 2013 (UTC)
(after ec) Thank you RexxS. Just to be clear, "I have received no payment from any organisation in regard to such editing" is not the same statement as "I have received no payment from any [of those] organisation[s]" (which is why I asked for further clarification, which you have now provided). Also to be clear, I never mentioned any of his Wikipedian-in-Residence work as a potential COI. If Andy (who is quite capable of writing lengthy responses and who did not respond to my Evidence post or previous post on this page) would have made such a categtorical denial on Wikipedia several weeks ago, I would not have repeatedly raised the issue. Ruhrfisch ><>°° 01:20, 21 August 2013 (UTC)
Johnbod - I imagine a company might well pay for inclusion of metadata or insuring that all articles (regardless of topic) had infoboxes which their computers could read more easily. But RexxS has spoken and the issue is resolved. Ruhrfisch ><>°° 01:20, 21 August 2013 (UTC)
I can't see that myself at all, but whatever. Johnbod ( talk) 03:42, 21 August 2013 (UTC)
You might want to read Riggr Mortis' comments at Wikipedia talk:Arbitration/Requests/Case/Infoboxes/Evidence ( diff) or Riggr's essay at User:Riggr Mortis for more on Wikipedia as a database. Ruhrfisch ><>°° 04:36, 21 August 2013 (UTC)
I have. There's a huge difference between what people will use when it's available for free & what they will pay for. That's rather the point of open content. Johnbod ( talk) 13:14, 21 August 2013 (UTC)
I tried to discuss conflict of interest with Pigsonthewong in relation to QRpedia, following the release of the WMUK Governance Review. I didn't find his answers very satisfying. The last people I would look to for statements on conflict of interest would be people who were trustees of the WMUK board which failed to deal with the rather clear-cut case involving Roger Bamkin which sparked the governance review. Delicious carbuncle ( talk) 04:40, 21 August 2013 (UTC)
You do realize that pulling in that whole WMUK thing is WAY outside the scope of this particular case? Not that it doesn't have merit, I'm just saying it's a lot bigger can of worms than what has been presented here. — Ched :  ?  04:49, 21 August 2013 (UTC)
Of course I do, but since former WMUK trustees RexxS and Johnbod showed up here to vouch for Pigsonthewing, I thought it would be a timely reminder. Delicious carbuncle ( talk) 14:10, 21 August 2013 (UTC)
If you bothered to read the rest of the case pages, you would see that "showed up here to vouch for Pigsonthewing" is a strange way of describing my comments in this case, even by your standards. Johnbod ( talk) 14:14, 21 August 2013 (UTC)

My view on payment, which informs (though not decides) my perspective on COI matters, is that I am less concerned if an editor is an amateur or professional than if their editing is of benefit to the encyclopaedia, within policy, and is not disruptive. In my view, an editor, for example, who is repeatedly adding a template to articles against consensus, and is not being appropriately responsive to concerns on the article talkpages, is being disruptive regardless of if they are being paid. To me it doesn't matter if the writer is left or right handed - what matters is the quality and impact of their writing. I find slightly odious people inquiring into the personal life of others. SilkTork ✔Tea time 08:21, 21 August 2013 (UTC)

Comments by Andy Mabbett

Adding infoboxes

There is a proposal to ban me "from adding or discussing the addition of infoboxes". there is no justification for this; and no allegation, much less no evidence, that the addition of infoboxes, in general or by me in particular, is controversial or has caused disputes, outside of a very narrow set of pages owned by one project and related editors. There have been no ANI sanctions resulting from the additions listed below; an no blocks or warnings issued.

In the first six months of this year (i.e. all of this year, excluding the months in which this case has been proposed or active, lest anyone accuse me of modifying my behaviour disingenuously), I added approximately (I don't promise not have missed one, when reviewing my edits) 60 infoboxes. Note that this figure is only for additions to pre-existing articles. It does not include the probably greater number I included in new articles which I created; nor a couple of changes from one infobox to another.

With a few exceptions, which I shall discuss below, none were disputed or reverted; or where they were, unusually, reverted they were reinstated by other editors. They are still, at the time of writing, in the articles concerned.

Of the infoboxes listed above, which are no longer in the articles concerned six of them (that's ten percent of all the infoboxes I added in half a year; four of them on one day) were removed by Nikkimaria during the stalking of my edits by her, about which I commented in my evidence:

  • [105] - I walked away after her second revert
  • [106] - edit summary "m, cleanup, tag"; I did not revert.
  • [107] - edit summary "org"; I did not revert.
  • [108] - edit summary "rm, cleanup"; I did not revert.
  • [109] - edit summary "rm, cleanup"; I did not revert.
  • [110] - edit summary "rm, cleanup"; I did not revert.

(Those particular removals were not included in the evidence cited in the case, and presented at ANI, which was representative, not complete.)

Three further infobox additions were disputed:

  • [111] - the infobox was hidden in a collapsed wrapper, with a set pixel width, contrary to the MoS, rendering it less accessible, and moved to the foot of the article. I later reverted that, but when it was collapsed again, I walked away.
  • [112] - reverted by Cassianto with the edit summary "..as you were". I did not re-revet, but please see the discussion on the talk page. When that discussion proved fruitless (both RexxS and I tried, in vain, to find out what the specific objections to the infobox in that article were), I walked away.
  • [113] - My only revert was to replace {{ Infobox invisible}}, which was shortly after deleted as it was styled to display:none;; and I replaced it after deletion. Nikkimaria eventually hid the infobox at the bottom of the article, styling it bodystyle=width:10px;font-size:10%;. This is contrary to the MoS and makes it inaccessible. I walked away.

So, where is the issue that the proposed ban on me adding infoboxes is intended to prevent? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:59, 21 August 2013 (UTC)

I'm sure it was just an oversight, but a few days before you posted this you also added a box to Café de Paris (London). I'm not stalking, btw, I was looking at the article for something unconnected. - SchroCat ( talk) 07:37, 27 August 2013 (UTC)
The oversight is yours. As I say above, this list covers "the first six months of this year (i.e. all of this year, excluding the months in which this case has been proposed or active, lest anyone accuse me of modifying my behaviour disingenuously)". But thank you for pointing out yet another of my many uncontroversial infobox additions. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:51, 27 August 2013 (UTC)
Yes, my mistake (not an oversight, a mistake, but thank you for highlighting errors), although I would not call it uncontroversial: I am not sure the article is made any stronger by the box, but far be it from me to start removing them, especially while the case is rolling on. - SchroCat ( talk) 09:17, 27 August 2013 (UTC)
Good point. The remedy is inadequate if it would not prevent the tendentious, argumentative and disruptive behaviour at, to pick one example, Little Moreton Hall and Talk:Little Moreton Hall that spilled over into Talk:Montacute House and (now archived at) Wikipedia talk:Manual of Style/Infoboxes/Archive 7 — Preceding unsigned comment added by 82.132.219.102 ( talk) 19:54, 21 August 2013 (UTC)
  • I think Andy is mistaken about his edits in the first six months of the year. As the anon (above) mentions and I say in my evidence, Andy was certainly causing trouble in February 2013, and going out of his way to cause it too, which is why he showed up at Montacute House. Initially, I believed an infobox topic ban might be enough to curb his zealousness for infoboxes, now I am less sure.  Giano  20:29, 21 August 2013 (UTC)

I invite the arbitrators to review the entire, and short, discussion at Talk:Montacute House/Archive 1#Infobox (only eight short posts), which was not about the addition of an infobox. The first two posts there were:

The infobox on this article is hidden. This is unhelpful to our readers. I un-hid it, but I have been reverted, with no explanation. The infobox should be displayed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:35, 14 February 2013 (UTC)

You are trolling from another page and another discussion! Go away or you will be blocked for disruption. Giano ( talk) 16:40, 14 February 2013 (UTC)

-- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:51, 21 August 2013 (UTC)

.....and indeed you were trolling for trouble from yet another of your many infobox disputes; or have you suddenly become an expert of 16th century English domestic architecture? No, the truth is that you just cannot resist bombastically trying to impose your will and views on pages about which you know nothing. Wherever you show up, there's trouble.  Giano  21:01, 21 August 2013 (UTC)
Hmmm. This seems to rest on three premises, all questionable: that the persistence of the infoboxes is a good indicator that their addition was not disruptive; that the controversy is caused by "ownership by one project"; that if, arguendo, the project has displayed unacceptable ownership, Andy's conduct has not in itself been disruptive. Judge for yourself. Choess ( talk) 00:13, 22 August 2013 (UTC)

eerrmmm... " [114] - reverted by Cassianto with the edit summary "..as you were". I did not re-revet, but please see the discussion on the talk page. When that discussion proved fruitless (both RexxS and I tried, in vain, to find out what the specific objections to the infobox in that article were), I walked away." Sorry to dip my little fly into the ointment, but that's not strictly true that you walked away. I tried to come to a compromise: you dismissed it on spurious grounds, saying "each [[WP:POINT|deployed]] by vehement opponents of infoboxes". That's falling well short of any attempts at good faith and evidence of a battlefield approach, rather than any serious attempts to come to a collective agreement - oh, and yes, as per the usual tactics, spurious allegations of ad hominem comments were thrown out to both me and Cassianto - simply for daring to have a different opinion to you, it seems. I find that your evidence on this one is extremely lacking and I don't have the spirit to go back through the others to see what has taken place in those arguments. - SchroCat ( talk) 00:45, 22 August 2013 (UTC)

Ownership

Choess raises, above, the question of ownership by the classical music project(s); I'd widen that to include some of their like-minded allies. I and others touched upon the matter in the evidence stage. WhatamIdoing said:

One of the main complaints in the music area is <!-- hidden comments --> demanding that editors respect the (dis)infobox POV of one particular group of editors, merely because the one group of editors has decided that they're interested in the article's subject. Some of the hidden comments say things like After lengthy consideration at the Wikipedia Composers project, it has been determined that infoboxes are not appropriate for composer articles. Before adding an infobox, please review the discussion at Wikipedia talk:WikiProject Composers/Infobox debates. Text similar to this appears in a substantial number of composer-related articles. This editor behavior needs to be addressed directly. A significant example of the debate can be read at Wikipedia talk:Manual of Style/Infoboxes/Archive 8#Routine_use_of_infoboxes_for_biographical_articles.

(some of the other hidden comments are more forceful than that; I'll add an example later see below).

My evidence includes:

infobox opponents (IOs) have represented... guidelines as binding (hidden comments; see above; " adding infoboxes... against guidelines") and/or representing consensus (ditto), or " instructions", even after being asked not to. They cite them in edit summaries.

and;

IOs have frequently exhibited, or supported, ownership, in contravention of core polices; in talk, and even here: ("WP:IAR trumps WP:OWN", "use of infoboxes ... more than settled ... in terms of a clear project consensus"; proposed findings)

The "views of creators and maintainers of articles (and of projects relating to them)" have not "been summarily dismissed as WP:OWN", references to OWN have followed examples or suggestions of breaches of it. e.g. Folantin's examples:

I repeat this here, in the light of AGK's comment about having forgotten my evidence.

RexxS, Moxy ( here) and others also touched on it. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 01:08, 22 August 2013 (UTC)

I find it more than a little rich that you accuse members of the classical music project of thinking they WP:OWN articles, an accusation I have seen you make numerous times, since it seems to me that you think you WP:OWN Wikipedia itself and are on a mission to make every article emit "machine-readable metadata", as in this edit from February this year, only one of many many such, [119],I recently fixed this article's infobox, which was not displaying. Another editor has now removed it, saying "it adds nothing anyway". That is patently false, as the infobox, in addition to providing a summary of key points for the benefit of our readers, cases the article to emit machine-readable metadata, such as is used by DBpedia, search engines, and, soon, Wikidata. The infobox should be restored. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:49, 11 February 2013" — Preceding unsigned comment added by Smeat75 ( talkcontribs) 02:28, 22 August 2013‎
Nothing in the comments above indicate ownership nor are beyond standard discussion. And "it seems to me that you think" is so clearly the entry to laying out an personal opinion that it is alarming to see this presented either as rebuttal or evidence of wrong doing.( olive ( talk) 01:44, 22 August 2013 (UTC))
Andy says - "[77] Not about infoboxes", no it isn't, you provide a perfect example there of what I said earlier on this page, this is not actually about infoboxes at all, it is about your fanatical drive for "metadata" as a diff from just a little before the one you quote shows: [120] Somebody has just said "it doesn't add anything" and you reply "That's patently untrue. It's adding coordinates and distances which are not otherwise in the article, as well as emitting the former as metadata, which can be understood by machines, and mapped. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:54, 19 July 2012 " Not everyone who edits WP is obliged to arrange articles so that machines can read them, there is no policy that says that. Smeat75 ( talk) 02:03, 22 August 2013 (UTC)
You appear to have missed the part of the comment, in your quote, which says adding coordinates and distances which are not otherwise in the article. That's adding them in a human readable form, so that our readers can see them with their eyes. Ownership on Wikipedia has a specific and clearly-defined meaning - clearly evidenced as having been breached by those opposed to having infoboxes on "their" articles - which is not "he says something I don't like". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:48, 22 August 2013 (UTC)

We are all working on machines. This is a wiki, machine driven. And nothing being said in the quotes you offer suggest "require", and by extension ownership. This encyclopedia some think should be edited so it can be handled easily and read easily, while suggesting that is not ownership. One is free to dislike the suggestion even the editor but extending that as somehow proof of ownership is fallacious logic, and to sanction an editor based on that kind of evidence or any like it is wrong and unfair.( olive ( talk) 02:17, 22 August 2013 (UTC))

The more forceful hidden comment, to which I referred above, is <!-- please do not add an infobox, per [[Wikipedia:WikiProject Classical music#Biographical_infoboxes]]-->. AIUI, well over 300 articles include that comment. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:58, 22 August 2013 (UTC)

Question

The only arbitration in my personal Wikipedia history where I have seen remedies this severe were with Will Beback in the Timid Guy case. Is this in any way even remotely comparable?Remember that you are laying out the worst possible remedy for Pigsonthewing. As a committee you have established where the most extreme outcome applies, have created a scale. How does this situation compare? Since I was very familiar with the TG case, I can tell you this does not compare. Where do you go from here if editors transgress on a level comparable to the worst case. There must be a consistent gradation and scale out of fairness, but also to make your job/decisions easier the next time and the next. ( olive ( talk) 01:54, 22 August 2013 (UTC))

A more apt comparison might be to Wikipedia:Arbitration/Requests/Case/Doncram: one user repeatedly engaged in an activity that he finds constructive but annoys other people, brushing off criticism, and a group of other editors interested in the subject matter responding to that intransigence with increasingly bad behavior. The two seem broadly comparable in terms of severity of the proposed remedies. Choess ( talk) 02:46, 22 August 2013 (UTC)
This is a project in which people volunteer their time and knowledge, for fun, I would imagine, in most cases. The vast majority of us are not doing it for money, anyway. Where is the fun in being confronted with an aggressive editor like Pigsonthewing, constantly insisting that articles be arranged so that machines can read metadata? Most WP editors care nothing about that and there is no reason why they should. Smeat75 ( talk) 03:43, 22 August 2013 (UTC)
This is a project in which I volunteer, so far it was fun. Where is your evidence that Andy is "aggressive". I never found him aggressive. Don't say that's because I am on his side. I wasn't always. I disagreed with his view on Samuel Barber (March 2012), but found him factual, patiently explaining, with a sense of humour even: "Unless, of course, someone wishes to argue that Barber was not a person...". I don't have time for more right now, but to see labels such as "intimidating", "belligerent", "battleground mentatality" etc. with no evidence apparent to me, simply repetition of experiences from a time past, makes me question why arbitration in the true sense of the word (as I understand it) is not even tried. - This is a project in which I volunteer, so far it was fun. Stress on "was". I know well what "frustration" means right now. -- Gerda Arendt ( talk) 14:52, 22 August 2013 (UTC)
Well, just as one example of his aggression, you could look at a discussion he himself references above - [121] where he put a table of distances into an article the day it was on the front page of the site, after literally years of arguing for such a table and being told that the creators of the article did not feel it was useful, or valuable. Yes, I think that is very belligerent, very intimidating and shows a battleground mentality, and it is not anything to do with infoboxes either, it is his obsession with metadata. There would be a dispute about infoboxes without Andy but no one else argues for them with such obsessive fanaticism, that is why I say this feud is not actually about infoboxes but about his disruption to the project and inability to collaborate amicably with others. Smeat75 ( talk) 15:59, 22 August 2013 (UTC)
The discussion to which you point was again in 2012, right? I fail to see how adding a table is an "aggression". - Andy is collaborating amicably with me, with people developing templates, with people working on templates, etc. You may want to try yourself. I love his latest article, peace and reconciliation, -- Gerda Arendt ( talk) 18:00, 25 August 2013 (UTC)
No fun so we sanction the editor? I understand frustration, frustration though, does not equal sanctions especially of the kind I see here, further, your insistence is as direct as anyone else's. This is a squabble long term yes, but a squabble, and squabbles require more than one side to even exist. The sanction should be of the kind, "Don't make me stop this car", not, "you're out of the family."( olive ( talk) 03:52, 22 August 2013 (UTC))
This would all be true if it were the first time. This has been going on for eight. bloody. years. The exact same issues over three arbitration cases including a year long ban. MLauba ( Talk) 07:10, 22 August 2013 (UTC)
Please see above. Define "this" more precisely. That a project introduced an infobox which is opposed is new! It has nothing to do with Andy. -- Gerda Arendt ( talk) 14:52, 22 August 2013 (UTC)
The context changes, the behaviour doesn't. No feedback registers. When an issue is pointed out, Andy endlessly finagles around details and takes nothing in. There is not a iota of difference in the way he handled the feedback regarding his multi-year long obsession with inserting a BLP's date of birth at Jim Hawkins (radio presenter) against the subject's wishes and annoyance, the behaviour that led to his topic ban from TFA, or what he displays in discussions around every single infobox feud listed in the whole evidence section. Heck the ANI report he filed a few months back complaining he was being stalked is a perfect illustration. Nothing registers. He's right, no matter how many uninvolved people tell him otherwise, and he will grind on and on and on. This is what has been going on for 8 years. The only relationship to infoboxes is that it so happens that this is the most common obsessive subject of his. MLauba ( Talk) 15:16, 22 August 2013 (UTC)
Once again I invite the Arbitrators to review my edits and comments at Manchester Ship Canal. In the cited discussion, it is pointed out by Tagishsimon (another editor driven off the project by ownership) that the table of coordinates and distances had been in the article, uncontested for four years. Having found it recently removed without discussion on the talk page, I restored it. When I was reverted, I joined the discussion on the talk page, where I was accused of making drive-by edits, despite my along association with the article. If I intimidated Malleus Fatuorum there, I shall of course apologise to him.

Likewise, I repast my invitation to them to review the Hawkins case, which polarised both editors and admins, but where it was again decided that there was to be no sanction against me. Both cases were over a year ago. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:34, 22 August 2013 (UTC)

Pigsonthewing is Andy Mabbett

Carcharoth comments It is worth noting somewhere for the benefit of those reading the decision that are not familiar with the background, that Andy Mabbett is User:Pigsonthewing (and vice-versa of course).. This is something that I agree would be worthwhile, and could probably most easily be done by copyediting the start of FoF3 to read " pigsonthewing ( talk · contribs · deleted contribs · logs · filter log · block user · block log) (who signs as "Andy Mabbett")". This is consistent with Wikipedia:Arbitration/Requests/Case/Gibraltar#Justin A Kuntz, which begins " Justin A Kuntz ( talk · contribs) (who signs as "Justin the Evil Scotsman")". Thryduulf ( talk) 01:31, 23 August 2013 (UTC)

Number of Arbitrators

It seems like this decision has taken so long because it's taken so long to get a quorum. Are a lot of Arbitrators gone for the summer? It seems like this hasn't gotten the attention from the entire committee it deserves. Liz Read! Talk! 18:47, 23 August 2013 (UTC)

For a complex case with loads to read, this doesn't seem to have taken an unusually long time to me, though there may be a bit of an August effect. Johnbod ( talk) 19:21, 23 August 2013 (UTC)
Thanks for your perspective, Johnbod. I saw that the case was due to be decided on Aug. 14th so I was wondering what was causing the delay. At this point, unless new motions are made, it's a matter of casting votes. Liz Read! Talk! 03:25, 24 August 2013 (UTC)
Hi Liz, nice to meet you (so to speak). Actually many of the Arbs have had a look around here. Roger is really the only one that hasn't weighed in at all yet. It's a very complex issue, so as individuals they are all going to have their own views. Several things come to mind for me though - 1. Trying to sanction some scapegoat is not going to resolve anything. 2. While most arbs can agree on the "Principles", and even many of the "FoF" things (some of which I would dispute), there seems to be virtually NO agreement on any "Remedy". That makes things tough, or more to the point - unresolved. We all want to present ourselves in the best possible light, and since arbs are people too - that include them. 3. AGK is still looking and even asking for some diffs (which if I have time I'll try to offer this weekend). 4. One forward thinking arb (Carcharoth) is looking beyond this case, and suggesting a global discussion. How much time he would have to actually guide that only he can say. But he does see the need for it. The thing is that it would need to be structured to achieve an end result rather than a circular "I like it", "I don't like it" type of thing we've seen for years.
As an aside - one thing that has troubled me in this case is the "bully" aspect. Intimidation is a very subjective thing, and is as much befalling on the the subject, as it is on the so called bully. As someone who was small in stature growing up, I learned that if I wasn't going to stick up for myself .. then I would be subjected to bullying tactic all my life. So I refused to be intimidated at ANY level; and especially over the internet. And standing up for one's beliefs is not an attempt to intimidate. I also understand that there are quiet, shy, and timid people in life who are easily hurt and intimidated. Good, kind, caring, loving people who simply choose not to battle others; either in debate or argument. But when a group of people get together to try to force a situation through in their own walled garden, outside the global consensus, then yes, I do consider that intimidation. So it all boils down to talking to one-another and getting to know the people we write with. But the "Wikipedia is not a social network" stigma sometimes thwarts those efforts. But I'm drifting into "lecture mode" again, so I'll close here. (so much for my " Closing statement" eh? Later all. — Ched :  ?  05:14, 24 August 2013 (UTC)
Thank you for your response, Ched. Although I've been editing on & off for 6 years, paying attention to Arbitration Cases is new to me so when I read that the decision is due Aug. 14th and it's Aug. 23rd and only a few Arbs have voted on solutions, it just got me wondering whether people were on vacation or something. Now that I've been told that this rate of progress finishing up a case is the norm and believing, as I do, that a better resolution is preferable to a faster resolution, I feel like my question has been answered.
As for your statement about "bullying", having worked in the area of conflict before, I'll just say that consensus building does not come naturally to people. It's slow, it delays an individual from taking action that they believe is necessary while one waits for people with different opinions to weigh in. It can be maddening to Type A personalities who just want to get the work done and not spend a lot of time talking about the process. I truly believe that aside from vandals, most editors that might be seen as bullies truly believe what they are doing is for the good of Wikipedia but that doesn't justify any effort to silence, badger, ignore or intimidate other users so one gets one way. But aside from a few personal feuds (which end up finding their way to AN/I), I don't think bullies are malicious in intent, they think they know better and trust their own instincts rather than the judgment of others. It's an unfortunate byproduct of their sense of rightness that their pursuit often results in alienating or, at worse, driving away some of their fellow editors. Liz Read! Talk! 19:35, 26 August 2013 (UTC)

Suggestion

I agree with Montana above that one editor may have been made a scapegoat here. This is a difficulty that arises with a case like this when its difficult to see where the problems are coming from. What I see is that a group of editors have been interacting in a less than positive style. Some have maintained a collaborative posture throughout as Gerda has. Others like Andy have shown improvement over his past editing practices and that must be noted.

The standard way of dealing with arbitration cases, doling out individual sanctions seems illogical here given all parties were involved in the squabbles surrounding info boxes. What Id' like to see is some out of the box thinking about how to deal with this kind of situation. Is there something that will fairly treat everyone, is not punitive while supporting ongoing work by knowledgable editors.

Suggestion: A restriction (time out) on all editors on infoboxes for one month. None of the editors named here touch an info box or comment on them. Further if any one editor does deal with infoboxes in any way, the whole group of editors will be restricted for another month. I am suggesting true collaborative work here, that those in this group be responsible to and for each other. I've worked with people in collaborative situations and used this technique, and found that the group begins to police itself, draw closer together, and those not willing to collaborate stand out in a hurry. Probably nothing new here but some thoughts on this case.

All sanctions should be specified per each editor as they are now. Editors who are not willing to improve in their collaborative skills will given this system show up immediately and that point sanctions may be applied. I realize this will be considered impractical but thought it might trigger novel thought. This is a collaborative community and collaborative remedies may be meaningful.

My concern is that three editors that I know of show a willingness to improve this situation. That in my mind is the best and most important aspect of this case.( olive ( talk) 01:05, 24 August 2013 (UTC))

Nikkimaria

I am sorry to note that I don't see attempts to improve when an editor who is being scrutinized during an arbitration continues to make this kind of edit. [122] which seems very like the pattern of edits made before the arbitration [123] . ( olive ( talk) 23:26, 26 August 2013 (UTC))

Thank you for notifying us of this (I have taken the liberty of correcting the username spelling in your heading). I'm not at all impressed that all three editors involved there (Gerda, Andy and Nikkimaria) have engaged in a discussion and sequence of editing like that during the case. The evidence presented was ample already. I will draw this to the attention of my colleagues. Carcharoth ( talk) 00:09, 27 August 2013 (UTC)
Thank you for correcting my spelling, No disrespect meant to Nikki( olive ( talk) 05:24, 27 August 2013 (UTC))
Er, my sole edit on that page during this case (I have not posted on the talk page since 9 April) was a technical fix, made on the (apparently mistaken) assumption that the renewed and seemingly resolved talk page discussion had settled the dispute. Whether we have an infobox or not; we certainly don't need two copies of the same one (I doubt even my most strident critics would argue for that!), so I removed the one which (no doubt because it was styled |bodystyle=width:10px;font-size:10%;) Gerda had obviously missed when she re-added the other infobox in the immediately preceding edit. (I also made a minor tweak to the position of some parenthetical text for readability at the same time.) In what way was that disruptive? I trust that will draw this reply to your colleagues' attention, also. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 00:42, 27 August 2013 (UTC) - added @ Carcharoth:. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:45, 27 August 2013 (UTC)
Olive, your second diff is from months ago, well before this case was open. As to the first: Gerda suggested on talk that we change the type of infobox that was being used; I agreed and made the change, noting on talk that I had done so. Gerda then added a second reformatted and expanded version of the same infobox; I disagreed and reverted, once, with a pointer to my explanation on talk. Can you explain why you see that as problematic? Nikkimaria ( talk) 02:02, 27 August 2013 (UTC)
I apologize. I left out part of the comment which unfairly created evidence of two diffs instead of one. Nikki I'vw watched your edits for quite a while and as you know commented to you on them. I thought that with this arbitration you might move towards a less aggressive style of interacting, with less a sense of ownership, but I'm not seeing that in the thread I linked to. I hope I'm wrong.( olive ( talk) 05:24, 27 August 2013 (UTC))
Thanks for amending your comment; however, I'm still not understanding your objection. The earlier edit used an edit summary which I agree was suboptimal; however, the edit summary of the more recent edit was IMO clear and based on an ongoing discussion. Furthermore, the more recent sequence shows that I implemented a suggestion by Gerda, objecting only to her subsequent addition of a second and inappropriately expanded template. Can you explain further how this sequence demonstrates aggression and ownership? Nikkimaria ( talk) 13:27, 27 August 2013 (UTC)

@Carcharoth. I don't see a concern with Gerda's or Andy's comments on this thread. I was concerned about Nikki's. With respect, I think its mistake to tar all editors with the same brush.( olive ( talk) 05:24, 27 August 2013 (UTC))

The orchestra: I found the article in the list AN/I list, an infobox added by Andy, reverted/hidden by Nikkimaria, one case of several. I restored an open version, It looked reverted the same day to me. I failed to see a collapsed version. What should an invisible infobox be good for, anyway? - No, I would not call this style "aggressive", but it's no clear communication, leading to waste of time. (Spare me the other steps, it's all in the history and on the talk.) - None of us is an "owner" of this article. If you ask me it should simply look like other orchestras, with {{ infobox orchestra}} developed by Kleinzach in 2013, for example Lautten Compagney. -- Gerda Arendt ( talk) 09:12, 27 August 2013 (UTC)

Problems beyond infoboxes

As both Newyorkbrad and WormThatTurned have cited Andy's behavior outside of the infobox realm as a factor in their decisions, I would point to the following as evidence of disruptive activity outside of infoboxes. There appears to be a similar issue over Andy's use, or overuse of Template:Coord, which is discussed in Rschen's evidence (roughly Sep 2011 – Mar 2012), with continued sniping here Apr 2013 and here Jun 2013. Wikipedia:Requests for arbitration/Pigsonthewing 2/Evidence#Evidence presented by Roundhouse0 is arguably connected (both revolve around the "coord" template.) Compare also the behavior at Wikipedia talk:Manual of Style/Accessibility#Discussion of recent controversial changes to this guideline and Talk:Jim_Hawkins (radio presenter)/Archive 2#Edit request, neither of which, in my eyes, covered him in glory. On the other hand, Wikipedia talk:Five pillars#Accessibility and equality shows Andy quite restrained and civil when a number of people contradict his policy proposal.

I'm not quite sure what the arbs are looking for or expecting here. (The scope and title of the case have probably influenced the nature of the evidence presented, both about Andy and other parties.) None of these, coordinates included, are on the scale of infoboxes in terms of disruption caused; the non-coordinate incidents aren't anything I would have kicked up to AN/I, let alone arbitration (indeed, I agree with Andy's position on accessibility and avoiding definition lists); and the last link makes it clear that Andy is capable of accepting criticism of his proposals with equanimity on some occasions. All that said, I do think there is evidence of Andy's battleground mentality and difficulty accepting consensus, mentioned elsewhere in this case, extending at least to other metadata and markup-related topics. Make of it what you will. Choess ( talk) 08:05, 24 August 2013 (UTC)

Yes, as I have said several times in this discussion, this is not just about infoboxes, but about Pigsonthewing's obsession with "metadata" and several arbitrators say on the PD page that there needs to be wider discussion of this issue. I agree, otherwise this problem will not be solved, even absent Pigsonthewing.Just as the guidelines for infoboxes state "The use of infoboxes is neither required nor prohibited for any article by site policies or guidelines" so they should state something like "It is neither required nor prohibited for any article to be arranged so that it emits metadata" and "put this-or-that into the article we are talking about because it emits metadata" should never,never be accepted as a reason for altering the visible appearance of any article. There is no requirement, and there should not be either, for any WP editor to care two hoots about microformats, or metadata, or machine readability, or Wikidata, or anything of the kind, or even to have any idea what those things are. Smeat75 ( talk) 15:54, 24 August 2013 (UTC)
I agree with much of what you postulate, but with very few of your conclusions. Surely none of us would want to see editors compelled to enable metadata, just as we don't require them to use inline citations or make articles accessible. Nevertheless, improving accessibility, enabling metadata and converting raw sources to inline citations are part of the natural development of articles that improves them. Wikipedia is a collaborative project and we don't need editors to have expertise in every aspect in order to contribute. Many editors are quite capable of writing excellent prose, but rely on others to upgrade rough sourcing into more maintainable formats, or to ensure that their work is usable by a screen reader, or to enable third-parties to read our information in a format that is appropriate for their needs. Each good-faith change to an article - whether it be converting raw urls to citations, or identifying row and column headers in tables, or converting a bare image into an infobox - needs to be considered for the impact that it makes on the other aspects of the article, of course. But I reject the proposition, so often assumed here, that the self-proclaimed experts on a topic should be the only ones who are entitled to an opinion on such changes. Editors must be able to propose what they believe to be improvements to an article, even if the owners of that article don't care two hoots about microformats, or metadata, or machine readability, or Wikidata, or anything of the kind, or even to have any idea what those things are. Ignorance is seldom a good starting point for having a sensible debate on any issue and Ludditism isn't actually a cool stance to take. -- RexxS ( talk) 19:09, 24 August 2013 (UTC)

Update and reminder

A brief update pointing to what David Fuchs said here. Please be patient until any new findings are posted. A reminder to everyone to please maintain decorum on these pages. Robust debating has its place, but please hold off on that while the case is still going. I said on the proposed decision page:

"I think several of the parties to this case are quite capable of changing their conduct without the need to pass formal remedies. I would like to see how things go after the case closes and wait to see if further remedies are needed."

I also said:

"Overall, I think a 'parties reminded' clause is needed here. And (after a period of some quiet) a way for people to discuss these issues in a calm manner at a central venue, building on some of the proposals made in the workshop, without tensions rising again."

I am still hoping this will be possible (my colleagues may in any case disagree with this approach that I have suggested), but it does depend in large part on people being able to discuss things calmly and being patient as we finish voting. I've asked the case clerk and the other clerks to keep an eye on this talk page over the weekend. Carcharoth ( talk) 23:25, 24 August 2013 (UTC)

Proposed principle 'Mission' and metadata

I think that the comments on this principle, and particularly the recent one from SilkTork, reflect a microcosm of the issues faced here. I would invite the Arbs - or anyone else - to examine these propositions to try to get a sense of what we need to understand in order to make progress:

  1. The very act of emitting accurate metadata helps others use our data. It cannot per se be harmful to the project and its current mission, and will most probably be helpful.
  2. As data is inherently dynamic, the metadata will only stay accurate if it is updated when the data changes. For that reason, an invisible mechanism for emitting metadata will always be inferior to one that is visible.
  3. Infoboxes are a feature of the majority of our articles and already contain both the structure and content needed to emit accurate metadata. They are therefore an obvious candidate for implementing metadata, as they require no duplication of data entry, nor special effort to update.
  4. In many articles, some particular key facts are too nuanced for a summary to be accurate metadata. In those cases it is not helpful to include that data in an infobox.
  5. There will be other valid, often aesthetic, reasons against including an infobox in a given article, but the job of seeking consensus is to balance the advantages (of which metadata is just one factor) against the disadvantages (which may be manifold or entirely absent). Both the issue of having an infobox and its content if one is included are properly subject to the process of consensus.

I believe those propositions reflect reality. I don't know whether SilkTork would on reflection modify his present stance, but I'd be more than happy to debate the points he raises in a broader forum, at a later date. -- RexxS ( talk) 16:49, 25 August 2013 (UTC)

I very much agree with what Silk Tork says in that comment you refer to, and agree with you that the issue needs discussion in a broader forum. Smeat75 ( talk) 18:05, 25 August 2013 (UTC)
One point that I think was raised in the workshop or in evidence (or in earlier discussions) is that the placement of the infoboxes may be what causes some of the friction. In desktop view, the infobox is at top right, next to the lead section. In mobile phone views, infoboxes are above the article and the first thing you see. If infoboxes were placed further down the article, or down the bottom of the article, the way categories are, the way navboxes (footer navboxes, not the sidebar ones), and the way some succession boxes, and some 'invisible' metadata (such as 'persondata' and DEFAULTSORT values) are, then infoboxes might be a lot less contentious. You would still get some arguments (over accuracy), as people do still argue over categories and navboxes, but from what I've seen, the arguments are less - possibly because the visibility is less (my general observation is that some people get rather annoyed with five or six collapsed navbox templates at the bottom of an article, but suffer it because it is 'down the bottom and after the article'). The reduced visibility means that updates may not be as accurate or timely, but what I wanted to ask is whether any serious attempt has been made to explore other possible positions for infoboxes? (I've only seen the examples where infoboxes have been placed invisibly right at the bottom of an article - not showing but still emitting metadata, and the visible but collapsed examples - with arguments against both these attempted solutions). Do examples exist where the default location for an item on a page (not just infoboxes) can be changed if needed? Has anyone tried to do an alternative infobox design that would fit across the whole page like a navbox footer template? Carcharoth ( talk) 20:47, 25 August 2013 (UTC)
Yes, I think that was tried at one of the country house articles, but is disliked, as you note. I hope someone has the link(s). I'm not sure if any such as in place now. Andy's note in this case that the lead image can be above an infobox has some potential to help where a landscape image is the natural lead pic (not composers, but very often in art and architecture), though I suspect keen infoboxers (not really those in this case) would be forever coming along and changing it. Johnbod ( talk) 20:56, 25 August 2013 (UTC)
(1) There are a few articles that have infoboxes embedded lower down within the article (eg Mini and many other vehicle articles), but none (afaik) that place the infobox at the bottom. Nor are there any that use a full-width layout - this would be very difficult to design, given the succinct nature of each field/value pair. Moving them would also have to be done site-wide for consistency (otherwise readers won't know where to find them) and it would no longer match the way all other language Wikipedias are setup. It would also make the {{ sidebar}}-navboxes more prominent, which is a can-of-worms itself.
(2) Collapsing has been tried in various places, from Ponte Vechio (2010) to Little Moreton Hall (current). I've tried to enumerate all the problems with collapsing in my evidence.
(3) I think I was the first to suggest that lead-images could/should display above the infobox. At my sandbox4, I made a mockup of that (and a few other changes). I gave further details about this idea in response to one of Andy's workshop proposals - particularly "Ideally, the image could (would?) still be "part" of the infobox's code, it would just display above the box-outline - this would allow all sorts of articles to use larger images, without making the box extra-wide." I tentatively suggest that this should become the default for all lead/infobox-images - this wouldn't require changing any articles, it would simply require changing the templates.
HTH. – Quiddity ( talk) 22:12, 25 August 2013 (UTC)
With a lead image above an infobox, we have the "Rite of Spring" problem: a picture suggesting that it is an article about a painting, instead of telling the reader prominently that it is a ballet by Stravinsky. I tried a new approach which I called "title box" as a certain word is not to be mentioned. -- Gerda Arendt ( talk) 07:32, 26 August 2013 (UTC)
Not if it is an article about a painting, Gerda. And why is that more of a problem when it is above rather than in the infobox? One might argue it is less likely to confuse that way. Johnbod ( talk) 16:52, 26 August 2013 (UTC)
I am confused now. At present (no infobox) The Rite of Spring looks (!) like about a painting, The Ban on Love looks like about a person. What do you think of my title box? -- Gerda Arendt ( talk) 17:14, 26 August 2013 (UTC)
This debate notwithstanding, Arbcom does not have the power to dictate to the community whether to accept or reject the use or inclusion of metadata. That is a content decision. Even if passed, this proposed principle should simply be ignored lacking an actual community mandate for it. Reso lute 13:47, 26 August 2013 (UTC)

Proposed remedy 'Parties reminded'

I wonder if it might be worth renaming this remedy to "Editors reminded" and making a corresponding update to the wording. I'm conscious of being as much caught up in the arguments surrounding infoboxes as many of the parties and there will be others in the same position as me. I'd willingly sign up to this proposed remedy and hope that everyone else can. -- RexxS ( talk) 23:40, 25 August 2013 (UTC)

  • The reminder certainly serves my benefit as well; which by the way, I intend also to heed. :)  John Cline ( talk) 00:56, 26 August 2013 (UTC)

Arbcom needs to decide on rationales for edits: does the tail wag the dog?

Arbcom needs a finding on whether debates regarding Wikipedia content that postulate benefits to "downstream re-users"—the argument ad Google—which Riggr Mortis outlined as a common feature of pro-infobox debate ( diff), should be allowed, or have any standing in content discussions. Such a clarification is surely within the committee's remit, since it would seem foundational that Wikipedia volunteers do not get to re-define who Wikipedia's "client" is. This cannot become a case of the tail wagging the dog. We again provide the following diffs as examples, quoting here from Riggr Mortis' post on Wikipedia talk:Arbitration/Requests/Case/Infoboxes/Evidence (and showing only comments by User:Pigsonthewing; there are more there from User:RexxS):

The methodology is simple: I searched the talk page namespace for "Google" and "Pigsonthewing". Here is what I found (emphasis mine):

  1. "We make our information (machine-)readable to Google and others, because they want us to, because they do good and useful things with it, and because it serves our mission."
  2. "Using an infobox makes metadata about the subject downloadable from the browser, or to partner sites which use it, such as Google[,] Yahoo and DBpedia"
  3. "parter [sic] organisations such as Google also make use of them"
  4. "The [meta]data emitted by our infoboxes is already used by Google and Bing and has been praised by Yahoo."
  5. "the metadata emitted by infoboxes, the hCard microformat, is a generic, open standard understood by tools such as Google and Yahoo."

Who is Pigsonthewing's "we" and "our" referring to? He is not speaking for us. He is not speaking for Wikipedia. He is speaking to his agenda.

Signed, User:Ruhrfisch, User:Riggr Mortis, User:Victoriaearle 02:35, 26 August 2013 (UTC)

Combined response in section below. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:06, 26 August 2013 (UTC)

Missing—an understanding of the huge scope of Andy Mabbett's agenda and activity

A few of us have discussed by email what we think is missing from this case to date. We are issuing one comment.

Andy Mabbett (User:Pigsonthewing) has made hundreds of thousands of edits (via bot requests) to Wikipedia over the years that have no conventional effect on article content, yet there doesn't appear to be an understanding in the Arbcom's comments to date about the scope of Mabbett's agenda, which put briefly is to create templates and insert them into as many articles as possible so that "metadata" can be read from the articles more easily by computers. The Arbcom does not appear to realize that a remedy that, for example, disallows infobox editing, does not prevent Mabbett from continuing to build the infrastructure that supports his agenda. Indeed, arbtitrator David Fuchs has written "I'm hopeful that forcing him [Andy Mabbett] away entirely from the infobox issue would alleviate the cause of conflict for this case"! The "infobox prevention" remedy is not sufficient. We will explain this below.

Mabbett's entire project is to overlay his infrastructure of templates (not just infoboxes!) upon millions of Wikipedia articles so that they can be better "parsed" by computers. Mabbett must want Wikipedia to act like a database, and databases must have very defined structures. So every article (or template like {{ Geobox}}, or "non-conforming" (e.g. collapsible) infobox) that deviates from his strategy and his structures is a potential battleground for him. An article edit that deviates from his template build-out, wherever he notices it, will be met with a revert, which regular editors are expected to accept, without policy grounds, for reasons that "they just can't understand"—it "emits metadata this way, you see"—it feeds third-party computer systems. His project is nothing less than re-defining Wikipedia for his own out-of-scope purposes. His "walled garden" of templates overlay the conventional editorial process and provide him with a self-reinforcing pseudo-technical rationale for controlling what appears in the wikitext of an article.

We must observe that Mabbett is perhaps Wikipedia's ultimate article owner, because his owning occurs via an entire infrastructure developed in the template space and applied to millions of articles. His methods have the effect of taking away editorial control from regular editors who may see no value in a template that adds complexity to the wiki-text without benefit to the reader. We all recently witnessed him attempt to take editorial control away from people who maintain articles about composers, for example, because their choices didn't fit his grand "data-feed" plan.

We will highlight one current initiative within Mabbett's project as an example of how he builds his infrastructure through templates and bot requests, to show why he must be stopped at the root. This recent bot request initiated by Mabbett proposes that dates already in infoboxes be put inside a new template—his template, ({{ start date}}, created by him—so that the affected articles will output data that is easier for computers to parse. The infobox aspect is irrelevant, being only the container for the template, which in turn "emits" a microformat, another major part of Mabbett's infrastructural plans. (One can go back to 2007 and find quotes such as the following: "Mabbett's campaign to push through microformats in the face of any opposition has caused untold friction around Wikipedia and has been the origin of many incidents appearing on this page [ ANI], including the classical music infobox debates. This editor is clearly a disruptive influence on Wikipedia and something should be done about him".) You see, infoboxes are nothing special here—they are just another template involved in Mabbett's strategy; infoboxes and "microformats" and so on are all part of the same agenda that dates back half a decade, and involve the same battlegrounds. How will a simple "infobox ban" affect his behavior? Not at all. If Mabbett's behavior has caused controversy, it is because it stems from his agenda—probably the strongest agenda a single Wikipedian has ever attempted to implement without a fairly quick ban following. The solution is to prevent the agenda, by preventing the person holding it from implementing it.

The bot request linked above demonstrates everything this case is really about. It demonstrates that Mabbett will continue to find battlegrounds regardless of being "banned from infoboxes". In that discussion, he accuses the most thoughtful commentator on the page of "filibustering"; he refers to minor documents somewhere else to discount the informed opinions of the people who have taken the most time to respond. And so on. We see that, even when the topic isn't literally infoboxes, he's still doing the same thing, years on, and still acting the same way toward others.

Does the Arbcom see how wide-ranging and problematic Mabbett's agenda is? The Arbcom will not accomplish anything by preventing Mabbett from editing a given infobox on a given article. His battleground encompasses all articles, and the template space. He must be banned from all activity relating to templates, including edit requests on the protected templates he frequents, and from asking for or participating in bot requests, because these are the methods by which he establishes his agenda on Wikipedia. His agenda and his "enforcement" style are why we are here. No other named party on either side of the debate demonstrates the aggression and tenacious enforcement of Mabbett. To not ban Mabbett from all template and bot activity is simply to move Mabbett's battleground a little. The battleground behavior and agenda-pushing will not stop until the Arbcom introduces a very broad restrictive remedy.

Signed, User:Ruhrfisch, User:Riggr Mortis, User:Victoriaearle 02:35, 26 August 2013 (UTC)

P.S. This hardly starts to examine how Mabbett achieves his goal via poor behavior. It does not focus on his bullying behavior, his ignoring any argument which he cannot attack, the behavior which discourages and drives away content editors (who are the lifeblood of this project).

P.P.S. If others agree with these statements, please sign your names below.

Responses

Thank you for this input, which relates to an issue I've been trying to read up on, but had trouble getting my arms around. The input raises a few questions in my mind. What community discussions have been held concerning the desirability of including microformatted information in articles? With greater specificity, what practical uses does the computer-readable microformatted information have, either within or outside Wikipedia (i.e., what are the actual or claimed benefits of including the microformats)? Can the microformatted information be included without visual effect on an article, as opposed to via an infobox, when the inclusion of one is disputed? I may have more comments later. Newyorkbrad ( talk) 07:20, 26 August 2013 (UTC)

The small scope of my agenda (forgive me that I don't understand all of the above): part of a microformat is for example {{ start date}}. You enter year/month/day as yyyy/mm/dd, and worldwide can be understood "this is a date" and the single elements, which different cultures can represent with month names in their languages and their order of rendition. It's a great concept! I support that! More on microformats by RexxS on the specific example of Talk:Mont Juic (suite). Nikkimaria reverted the infobox, but the principal author liked it. Please note that Andy didn't argue in the discussion, only answered questions and explained. -- Gerda Arendt ( talk) 08:58, 26 August 2013 (UTC)
If Brad (or others) are interested in what the above contributors are describing, I suggest he takes a look at what independent scholars have to say about it, rather than taking the word of those who simply wish to keep us in the world of a paper encyclopedia. Tim Berners-Lee, the inventor of the World-Wide Web, wrote an article for Scientific American in 2001, where he describes his vision of a Semantic Web - it's available as a pdf here. After describing a brother and sister finding a specialist to treat their mother he writes:
Sorry to interrupt but is there a more legible version of that article? All I see is a page of "}A³Rҝ¬�^ät/�ßξ÷®g½ë›iï�Ä„‡³dHéøŒ" when I tried to open it. Liz Read! Talk! 19:42, 26 August 2013 (UTC)
Try saving it to your hard drive and opening it from there, in a PDF reader, rather than in a browser. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:46, 26 August 2013 (UTC)
  • "Pete and Lucy could use their agents to carry out all these tasks thanks not to the World Wide Web of today but rather the Semantic Web that it will evolve into tomorrow. Most of the Web's content today is designed for humans to read, not for computer programs to manipulate meaningfully. Computers can adeptly parse Web pages for layout and routine processing—here a header, there a link to another page—but in general, computers have no reliable way to process the semantics: this is the home page of the Hartman and Strauss Physio Clinic, this link goes to Dr. Hartman's curriculum vitae. The Semantic Web will bring structure to the meaningful content of Web pages, creating an environment where software agents roaming from page to page can readily carry out sophisticated tasks for users."
So the concept of adding meaning to web pages is nothing new and doesn't belong just to Andy. Have a look at some of the results from this search on Google Scholar and you'll see that building the semantic web has been a task embraced by many scholars, designers and engineers over more than a decade of progress.
Nor is building the semantic web confined to microformats. For those of you who want to learn how our structured content is being used to train new generations of natural language processing programs, there is a video entitled "Intelligence in Wikipedia".
Every single web designer is aware of the potential of adding meaning to web pages. Our problem as a crowd-sourced website is in enabling everyone to contribute without throwing away all the other aspects of web design that most contributors will not be interested in. On the whole, we have made a good job of that, by using templates to hide the complexities of web-design inside a simpler wrapper. Even so, the fear of the unknown will still drive some to reject any sort of progress.
I submit that the essay above is nothing more than a device to stigmatise Andy's desire to see Wikipedia evolve into a resource that is usable in far more ways than simply reading an encyclopedia - I have the Encyclopedia Brittanica on my bookshelves if that's all I want to do. Let the three authors above honestly answer a simple question: "Would their opposition to infoboxes be any less if they did not emit metadata?" I think we already know the answer to that.
The authors also repeat a lie: that Andy has driven away editors. Not one single jot of truthful evidence has backed up that smear. In fact, Victoriaearle made that claim in her evidence, but had to retract it when it was shown that the editor whom she claimed had "left the project" had edited continuously ever since.
ArbCom should look carefully at the agenda of these editors: they have employed smear, innuendo and fabrication to create a caricature of an editor with whom they disagree. There is nothing sinister about wanting Wikipedia to be used as more than a paper encyclopedia; most editors share the goal of broader use and dissemination of our content; and there is no reason whatsoever why those goals should run contrary to the process of writing good content. -- RexxS ( talk) 11:40, 26 August 2013 (UTC)
I would like to endorse everything in RexxS' rebuttal to the three editors above. It is true that not everything can be accurately summarised in an infobox, but there has been no reliable evidence presented anywhere that emitting metadata for things that can is anything other than a Good Thing. Thryduulf ( talk) 12:03, 26 August 2013 (UTC)
I think the argument is not that metadata is a Bad Thing, but whether the approach Andy takes is helpful or causes problems. Is it better to have 100 editors doing what Andy does in small amounts, or Andy doing what he does in large volumes, as a speciality, and persistently, over many years? When people take a de facto leadership role in over-arching matters like this, is that a good thing or not? And how responsive are they to community concerns? That is my understanding of the argument being made here. Carcharoth ( talk) 12:41, 26 August 2013 (UTC)

Thank you from me too for this. It does clearly lay out the concerns that I've seen expressed elsewhere as well. Could Ruhrfisch clarify whether the postscripts (PS'es) are from him or all three editors issuing the joint statement? NYB, to answer one of your questions, I believe that when you Google for something that has a Wikipedia article, the Google summary that comes up to the right on the standard search results screen is based on what Google can read from machine-readable sources, including Wikipedia articles. I believe the other questions you ask have been mostly answered in the evidence and workshop pages, though it can be difficult to find the links among the other material there. I too may have more comments to make later, but the closest ArbCom can come to limiting scope of activity is if the overall editing is bot-like or aimed at achieving a fait accompli against existing community consensus. Beyond that, it would be the role of members of the editorial community to initiate discussion within the community on whether consensus exists for such wide-ranging activities. Carcharoth ( talk) 11:39, 26 August 2013 (UTC)

@ Newyorkbrad, There are other methods of obtaining this information, including the {{ Persondata}} template. Interestingly a Google search for Terry-Thomas carries one of these side boxes, even though our corresponding FA article doesn't; the same is also true for a Google search of John Le Mesurier and again our (FA) article doesn't carry the box. Metadata in itself is not necessarily a bad thing: if we can provide a method of disseminating microformats in a hidden form (even if that is a collapsed box) then that can only be a benefit. - SchroCat ( talk) 19:34, 26 August 2013 (UTC)
A couple more comments, based on what I've read about this while looking into some aspects of this case:
  • My understanding is that metadata here means data that can be included in and extracted from articles. This can take the form of infoboxes, but can take other forms as well. Microformats are ways of using existing html tags to mark and allow extraction of this data. You don't need to edit pages direct but the tagging is included elsewhere. It is a technical back-end allowing computers to 'recognise' what is on the page (i.e. semantic markup).
  • In an attempt to get a feel for the sort of work Andy does on this, I looked at some of his edits this year:
    • An example of his microformat work is here. Change made to sandbox here. This is (as far as I can tell) an example of allowing external data reusers to more easily access the data contained in Wikipedia articles.
    • An example of Andy's outreach and consulting(?) roles is here (from May 2013, about the ORCID "works metadata" working group), though I'm still not clear on the full scope of what Andy does outside Wikipedia on this sort of thing.
    • I noted the extent of the work done on data-related issues, templates, and infoboxes on some of his user pages: to-do and infoboxes.
    • I noted an example of a recent infobox merging discussion that drew a fair amount of attention: Template:Infobox journal.
    • I noted an example of a discussion on gender here.
My overall conclusions from this were that many people do lots of work of this nature (on templates and infoboxes), but most manage to do it without causing waves. Either because they are more sensitive to concerns, or because they edit less, or because they restrict themselves to a narrower area and don't edit across the whole gamut of infoboxes. What I'm trying to articulate here is whether there is justification for a principle that sometime less is more (to put it crudely)? I'm not sure there is justification for that, but there is a long track record within Wikipedia of individuals trying to do too much themselves, over-reaching, and running into problems with various parts of the community. It is very difficult to edit widely across a large number of areas without eventually running into those sorts of problems. It would help to be able to compare the participation in such discussions of all the editors named in or participating this case. Who participates in the most discussions, and who contributes most productively to such discussions? Carcharoth ( talk) 13:06, 26 August 2013 (UTC)
  • I would like to note that I completely endorse the statement of the three editors above. My own evidence touched on the edges of Andy's metadata obsession, but having not looked at it as deeply as they have, I felt that an infobox ban would have been sufficient. They quite eloquently and convincingly (imo) argue that such a topic ban would not be sufficient in this case. Metadata by itself may not be a bad thing - this seems exactly what Wikidata was set up to achieve - but Andy's behaviour around it has been a continual and significant source of wasted time for pretty much as long as I've been here. Reso lute 14:01, 26 August 2013 (UTC)
  • I also endorse the statement, and thank the editors for laying out with clarity the real problem here. I should note that the inclusion of metadata seems to me an important goal (I've said as much before in the debates about infoboxes), but that is not what is at issue here. Eusebeus ( talk) 14:15, 26 August 2013 (UTC)
  • I add my thanks and endorsement to the three editors' statement above. Smeat75 ( talk) 17:00, 26 August 2013 (UTC)
It sounds like the metadata isn't the problem here, it's the zealousness which an editor approached the task he saw before himself. Building consensus and handling conflict is messy and time-consuming but an essential aspect of how Wikipedia works. I can see how anyone who believes they are working for greater functionality of Wikipedia would become impatient with ever present debates. But, I think for WP, the ends (greater functionality) doesn't justify the means of overcoming resistance by either steamrolling over it, denying it exists or bypassing the debate altogether.
I need to say this is a general observation about editor conduct on WP that may or may not apply to Andy. I only have these proceedings to go on and it seems like there are some conflicting statements in the lengthy proceedings. Liz Read! Talk! 19:20, 26 August 2013 (UTC)
  • I fully endorse the statement above; this is further supported by my evidence that I submitted a few weeks ago. -- Rs chen 7754 20:13, 26 August 2013 (UTC)
  • I emphatically OPPOSE the witch hunt against Andy and the character assassination above. Here you have an editor who has clearly learned from his mistakes over the years, but is being hounded to death for a mere passion for a topic. The merits of the issue itself are being drowned in a sea of scapegoating. I see nothing of excessive "ownership" or some sort of dark agenda in Andy's behavior over the last year, and though he gets a little intense at times, he is merely a fellow editor with a strong area of interest. This is character assassination at its worst and it seems that any attempts by Andy to defend himself are met with the same chorus of outrage. The logic of the above statement is ludicrous: "let's ban people who care about improving the encyclopedia." Hmmph. Next thing you know, someone will want to ban Jimbo for his passion for wikipedia! Montanabw (talk) 00:14, 27 August 2013 (UTC)

Further responses

Note: I also endorse RexxS' rebuttal.

So much for Carcharoth's request for the maintenance of decorum. What we see in two sections above, as others have noted, are further attempts to misrepresent and smear, devoid of any actual evidence of wrongdoing or ill-intent - exactly the kind of behaviour seen (and evidenced in earlier stages of this process), from those opposed to infoboxes, or metadata, or having our content reused by external partners, or objecting in some other way to normal Wikipedia practices.

Ruhrfisch has found some instances of me discussing the reuse of our content by Google, Yahoo, Bing, DBpedia and others. So what? A similar attempt to spread FUD in that regard, also referring to Riggr Mortis' ill-conceived essay was given very short shrift by the wider community when brought up on Jimbo Wales' talk page during this case. One editor there, User:Equazcion, commented:

"I fail to see the difference. Services that benefit people should be hindered because a company is also profiting from it? Why? To prove a point? To stick it to the man? Wikipedia is about providing your knowledge for free to whoever might use it for whatever purpose. What's the difference if it's structured data or prose? The same argument holds either way. I guess it sounds scarier when you throw around words like 'Google' (big ie. evil) and metadata (automated ie. evil), but really, it's all the same"

adding

"the wishes of the "primary" contributors shouldn't take any kind of precedence; The counter-arguments based on WP:OWN are perfectly valid in response to arguments referencing the amount of time or effort contributors spent creating or developing articles. We have that policy to deal precisely with these types of situations. You shouldn't contribute here if you think you have some sort of right to maintain control because it was 'your' work."

Ruhrfisch quotes me as saying "We make our information (machine-)readable to Google and others, because they want us to" (emphasis newly added). What he does not reveal, is that I was replying to the question (from Toccata quarta) "why should we shove our information down Google's throat?".

He also neglects to mention that my comment "The [meta]data emitted by our infoboxes is already used by Google and Bing and has been praised by Yahoo" is a reply to the assertion that "[that] microformats... will one day facilitate the development of the Semantic Web, [is] just a leap of faith".

The "we and "us" I use refer to Wikipedia. Wikipedia shares its content using metadata. Wikipedia invites its reuse. Wikipedia's mission is enhanced by that reuse. And if I've done more than my fair share of the laborious and unexciting work to make that possible, for which I've been thanked by WMF staff and numerous fellow editors, then I'm very proud of it. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:03, 26 August 2013 (UTC)

Ruhrfisch responses

Newyorkbrad - I know that User:Pigsonthewing cited the existence (since 2007) of the category Category:Templates generating microformats as evidence that "The use of infoboxes to emit microformat metadata has been supported ... in practice" (take that as you will). As for actual RfC's, he cited two:

I do not know of any other RfCs which support inclusion of microformats. I do know that when the start date template was proposed to be added by bot to about 40,000 articles on listed properties in the National Register of Historic Places, it was done as a bot request and Pigsonthewing made only one post to the NRHP WikiProject web page about this - see here. I think it would have been much better if the NRHP WikiProject (to which I belong and which includes infoboxes in articles as a matter of course) had been asked directly for its input by User:Pigsonthewing. [Please note Pigsonthewing says below that he did not make the original bot request. I apologize for my error, as I said I am quite busy in real life and just recalled his comment on the NRHP talk page.]

If microformatting is desired, it can be incorporated in articles in places other than an infobox (to be very clear, infoboxes and microformats do not have to go together). One possibility would be Template:Persondata which is hidden from readers and is already included in over one million articles. As for microformats changing an article's appearance, they should not if done correctly, but even something as simple as a date runs into issues with the different date formats used around the world and in articles here which might cause it to change appearances (see the discussions above). I also worry that editors will not understand what the microformat templates are asking for which may lead to issues - again an issue raised in the NRHP page and touched on by us as part of the ever-growing complexity.

As for practical uses, I do not know of any within Wikipedia (Persondata is used for categories, perhaps microformats could be too?). Many third-party data-reusers can and do make use of machine-readable data (from microformats). As we asked, does the tail (Google, et al.) wag the dog (Wikipedia)? Ruhrfisch ><>°° 16:13, 26 August 2013 (UTC)

Comment - I have little time in real life today, and will reply to the other arb comments / questions next as I am able. Ruhrfisch ><>°° 16:13, 26 August 2013 (UTC)

Persondata is only for people (hence the name), not buildings, events, and the many other things for which our infoboxes emit microformats. Please provide an example of a microformatted persondata template for a person, so that it can be tested. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:18, 26 August 2013 (UTC)
And again Ruhrfisch misrepresents what was said, this time at the NRHP project talk page. I was replying to Doncram, a project member, who said "Please see wp:botrequest#Mark a lot of pages for microformatting. Not sure if they should be discussed here or there" and I replied "I've answered these questions at BOTREQ; I suggest we centralise discussion there.". Doncram and others joined the BOTREQ discussion; there were no posts objecting to the suggestion to hold it there. Note also that the bot request was not made by me but by User:Nyttend and the aforesaid comments are in reply to his notification of it. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:32, 26 August 2013 (UTC)

Carcharoth - the PPS is all mine. The PS reflects things that we discussed via email, but I will take responsibility for it now. I have asked Victoria (who has asked for a block) to comment on her talk page about the PS (since she cannot edit elsewhere). I assume Riggr Mortis will comment here if needed. More later. Ruhrfisch ><>°° 16:20, 26 August 2013 (UTC)

I keep on hearing the argument that we could incorporate microformats into something that isn't an infobox. Yet the truth is that nobody has ever done it with any success. {{ Persondata}} could emit microformats, yet it doesn't. Any number of invisible data structures could be embedded into our articles, yet they are not. Why? Because anybody who actually sits down to the task quickly realises that the problem with invisible structures is that they don't get updated on a crowd-sourced site. Then they spot that they want a structure with a number of label/data pairs, like a table with two columns that's relatively easy to create and update, and it needs to be a template so that we can hide the classes needed to emit microformats. And voilà! they've re-invented an infobox. There are already well over 2 million of them in use on our Wikipedia, so why not just use them as the basis for emitting the metadata? The only reason why not is that some folks just don't like 'em. I'll start to take seriously Ruhrfisch's assertion that we could incorporate microformats in some other way when he manages to create one of these other ways and shows how it will be adopted in our articles. Have a look at Ruhrfisch's recent contributions and at my recent contributions. Which one of us is more likely to be producing technical solutions to problems? -- RexxS ( talk) 18:04, 26 August 2013 (UTC)
I do not pretend to be a template or coding expert, nor do I wish to engage in a pissing contest with RexxS (and if I did, I would direct him to look at WP:WBFAN or at the number of peer reviews we've each done ;-) )(the smiley face means I am trying to use humor here). All I said was that infoboxes and metadata do NOT have to go together. To prove this, I have used {{ Start date}} and put a microformatted datum into an article on a covered bridge without resorting to its infobox or a hidden template or anything hidden - diff.
On a more general note, members of ArbCom are asking for clarification and more information, and all Pigsonthewing and RexxS can do is resort to their usual tactics of attacking the messenger (me), pointing out one error (Pigsonthewing did not initiate the NRHP bot request, so I struck that and apologize), and challenging me to a code off (or whatever you call it). Why not give them what they ask for? Or could it be that the best evidence for consensus to add microformats everywhere across the whole encyclopedia is really a category (but hey, it is 7 years old!), a no consensus RfC, and 10 editors who could out-code me saying yeah, you can try this with a bot. Ruhrfisch ><>°° 20:51, 26 August 2013 (UTC)
No-one attacked you; its just that the flimsiness of your arguments and falseness of your claims was (again) exposed. I don't know of any outstanding requests from Arbcom for clarification or more information about microformats, metadata or infoboxes, but if there are and someone points them out, I shall be happy to answer them. And no, you have not added "a microformatted datum" to that article, You have added a template which emits one element of a microformat, without a parent microformatted container to give it context (i.e. the start date for what - the page? Consider also a page with two infoboxes). The template documentation explains this. No microformat-aware tool will recognise it, because it does not conform to any published microformat standard. So you have not proved your assertion. ( I have fixed your error) And do you really think inline templates, in running prose, are preferable to, or more likely to find favour with the wider community than, those in infoboxes? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:18, 26 August 2013 (UTC)
( edit conflict) @Ruhrfisch: I don't remember trying to tell you that you should be doing peer reviews in a different way - the way that you tell me I should be writing metadata-emitting templates in a different way. In fact, I'm happy to acknowledge and commend your work in doing peer reviews because I know it improves the encyclopedia. But then you keep making the claim that we could put metadata elsewhere, and ignore my explanation of why it's a bad idea - based on what? Your expertise in doing peer reviews? I agree that it has a certain humorous quality. -- RexxS ( talk) 21:54, 26 August 2013 (UTC)
@Pigsonthwing - So just to be clear, you, Pigsonthewing are the author of {{ Start date}}, a template specifically made for emitting microformatted data. However, and here's the catch, it only works when embedded inside other "microformat-emitting templates". So you made it so it won't work unless it is in an infobox or other appropriate template - how does this not conform to our arguments above? i.e. you OWN Startdate, and it has to be in a box to work, so then you OWN the box too? Ruhrfisch ><>°° 01:49, 27 August 2013 (UTC)
I don't own any of them. Where is your evidence that I attempt to? Please explain how you would have {{Start date}} work outside a parent container. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:19, 27 August 2013 (UTC)
@Ruhrfisch: you need to actually read WP:OWN. It's not about creating articles or templates; it's about stopping other editors from contributing to work that you feel you own. It is exactly what has happened with biographies of classical composers. It is exactly what has not happened with {{ Start date}} - another half dozen editors have contributed and Edene is now the main contributor. For information: many infoboxes allow dates such as "about 212 BC", "15 or 17 December" which are not suitable for emitting metadata. So the way that we emit metadata for dates that are sufficiently precise, like "27 August 2013" is to wrap them in a template that adds a microformat - which is what {{ Start date}} does. It works sensibly when the date it wraps with the classes "bday dtstart published updated" is inside another class like "event" which names the event that it is the start date for (or the person whose birthday it is, etc.) Please try not to use {{ Start date}} outside of suitable containers like infoboxes otherwise re-users can't tell what it relates to. -- RexxS ( talk) 12:19, 27 August 2013 (UTC)
RexxS and Pigsonthewing, I have read it - I was referring to our joint argument about OWNership above. Ruhrfisch ><>°° 16:27, 27 August 2013 (UTC)

Carcharoth - Riggr Mortis indicated to me on email that he is fine with the PS. Victoria posted the following on here talk page: Yes, per Carcharoth's question, I agree with the PS. It's been amply demonstrated on the pages of the arb case and on other pages where I've witnessed these discussions and is in my view the reasons it's difficult to impossible to discuss these matters elsewhere, which goes to Newyorkbrad's question. Only one more thing, in response to RexxS assertion that I accused Andy Mabbett of driving away editors: the evidence states editors become discouraged and leave. But - and this is important - I don't wish to engage on that level because frequently in these discussions the concept or the main point of the discussion devolves quickly into a "he said, she said" scenario which is almost always counterproductive. Feel free to copy over, or to link, or to point to this post. Victoria ( talk) 18:08, 26 August 2013 (UTC) End of quote posted here by Ruhrfisch ><>°° 20:08, 26 August 2013 (UTC)

Well of course Victoriaearle doesn't want to engage in discussion after she's been caught out in a lie. But her so-called evidence is still there on the talk page of Evidence even now for anyone to see and she hasn't had the decency to retract those untruths. Here's what she says referring to Yllosubmarine: "In September 2012 ... She became discouraged and left the project. ... . Keep in mind, too, we lost a prolific female content editor from the Pilgrim at Tinker's Creek episode." It's pure fabrication. Yllosubmarine never left the project. Here's a link to her contributions so you can see for yourself. Count the monthly contributions since last October when she was supposed to have left the project: 28, 10, 6, 11, 3, 7, 11, 2, 7, 3. She even edited today. It's on the back of this sort of mendacity that we get the smear "the behavior which discourages and drives away content editors". There is zero evidence. Strike it if you have an ounce of honesty left. -- RexxS ( talk) 21:54, 26 August 2013 (UTC)
Please see my comments above in the #Comment from Victoriaearle/Truthkeeper88 section. While I agree that Yllosubmarine has not left entirely, her edits dropped by just over 90% in the 10 months after Pigsonthewing's Pilgrim at Tinker Creek infobox argument (compared to the 10 months before) and she has not written any new articles I could see or brought any to GAN or FAC (and this from an editor averaging over two GAs and FAs per year from starting here to Tinker Creek as TFA. As I said above, how is this not the loss of a productive editor? I know you won't answer that, because you can't. I will repeat what I said to Pigsonthewing and now say to you, you owe Victoria an apology. Ruhrfisch ><>°° 01:49, 27 August 2013 (UTC)
That would be the section where I disproved your and (not for the first time) Victoria's bogus claims by showing that Yllosubmarine had edited more times in some of the months after the Tinker's Creek discussion than in several of the months before it? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:10, 27 August 2013 (UTC)
@Ruhrfisch. Rubbish. Yllosubmarine made more edits in the month after the Pilgrim's Creek debate (October 2012 = 28) than she made in any of the four months prior to it (May, June, July, August 1012) and she was busily contributing to Today's Featured Article requests during the rest of the year. It is disgusting that you try to spin that into evidence of Andy chasing editors off the project. -- RexxS ( talk) 12:01, 27 August 2013 (UTC)

newyorkbrad and Carcharoth and any other members of ArbCom reading this - I see further attempts at discussion will get nowhere, since I cannot code templates and mendacity is supposedly rampant. I hope that our arguments offer a useful way for you to look at this whole mess. Ask yourselves this: if infoboxes and metadata and microformats are a content issue (as many have argued) and we have a small group of editors who are pushing this content everywhere they can, despite a lack of broad consensus for it, isn't this really a WP:POV case too? If this were some content on the Middle East or (Northern) Ireland that was being pushed, wouldn't the solution be obvious? In POV cases, ArbCom has topic banned or site banned the POV pushers. Is this that much different?

And now, since Carcharoth has asked for a break (as it were), I bid you all adieu. Good night and good luck, Ruhrfisch ><>°° 01:49, 27 August 2013 (UTC)

[I've cut this way down, Carcharoth]

On the lying accusation: Don't call people liars. I had the same impression about Maria/yllosubmarine--that she was gone, I mean. It's an easy mistake to make, in general, about people you've encountered a tiny bit. Maria certainly has cut back on editing, having made maybe 70 edits since the infobox debate she participated in almost a year ago, which went something like this: Talk:Pilgrim_at_Tinker_Creek#Infobox.

"Give example of an editor leaving because of Pigsonthewing?": OK, me. Not as a matter of direct conflict, but in the way that one has an instinct to walk away from something they think might explode. Or worse, stick to them and explode. Wouldn't want to be within a country mile of the next Tinker Creek Box Battle.

(Why am I back? I participated in proposing the remedy we gave above (that bold part), because if it passed I would feel much better about the culture and editing environment of Wikipedia.)

Metadata misdirection: All cut—except for a short comment on semantics and retro-fitting. I didn't know that buildings and bridges had birthdays, were "published", were "updated", or fit into a calendar event, but the HTML source of one example tells me so: <span class="bday dtstart published updated">1872</span>; the Eiffel Tower has a "nickname" that happens to be in French: <span class="nickname" lang="fr"...>La Tour Eiffel</span>; Chelsea Manning was also going to have a "nickname" that consisted of their prior name (sounds controversial in any other context, doesn't it: [124]); and biographic metadata for the most part "emits" contact card data. "Semantic"? Hehe. Not so much. This "tail wagging dog" concept comes up again. What to do with it... Riggr Mortis ( talk) 06:53, 27 August 2013 (UTC)

Where has anyone called anyone else a liar? The HTML class names used in microformats are just labels,; (they could easily be in the style "parameter23"), but were chosen by the authors of the microformat standards to match the internationally used vCard standard, and as already discussed, are widely and interoperably recognised by a large number of organisations, web services and software tools. In the case of the bridge, the classes "published" and "updated" are disregarded, because the parent microformat includes no definition of them, unlike the "dtstart". Since they are not exposed to our readers, there is little chance of them being cased any confusion. I've already suggested that people read the archived section of Jimbo's talk page, where your user-page essay got very short shrift, and quoted some of the response to it, above. In that essay, you give your reason for leaving as "As long as Wikipedia drifts from its origins as a tool for human learning to a second-rate quasi-database—apparently to the benefit of ADD-inducing tech companies—I will no longer participate as a volunteer". Let's have another quote from the discussion of that on Jimbo's talk page, from User:Cyclopia: "So someone is led to retiring because we're making it easier to reuse data and make Wikipedia interoperable with other tools? I am sorry but I can't think of anything else but 'insane' when reading this essay... Licensing is how we deal with wishes of people who wrote the data. If you don't want your contributions to be used in ways you wouldn't think of, you better not contributing to a project under a free license." Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:00, 27 August 2013 (UTC)
@Riggr Mortis: I call someone a liar when they are clearly telling lies and damaging another editor as a result. Did Yllosubmarine leave the project - yes or no? Is Victoriaearle a liar? Of course it's easy to make mistakes, but honest people withdraw the accusation when they realise they've made a mistake. Victoriaearle's mistruths lie on the Evidence talk page to this day and you use them to call for sanctions on another editor. You suffer no damage by defending such lies, but for the person who is maligned as a result, it may possibly result in an indefinite ban for something that you've helped to fabricate. Shame on you. -- RexxS ( talk) 12:01, 27 August 2013 (UTC)
RexxS - everyone makes mistakes (my recollection is that Pigsonthewing said I found quotes by him, when all I did was copy what Riggr actually found, you referred to me still doing peer reviews when I got burned out and basically do not do them anymore). Yet I am not calling either of you liars. Victoria cannot edit any page but her own, and has chosen to leave the project. I said above that while Yllosubmarine did not technically leave Wikipedia, it is also clear she is not contributing at anywhere near the level she did before. You have an excellent FA nom; you know the effort involved in writing and researching and getting an article through FAC. Look at Yllosubmarine's edits - she still cares enough to revert vandalism and good faith cruft additions, she still participates in a few discussions if any article she took to FA is nominated to be on the Main Page, but that is it. She went from 14 GAs and 14 FAs in less than 7 years to ZERO in the year since the infobox posse showed up at the Tinker Creek article. Address that part of Victoria's statement, why don't you? Yes, Yllosubmarine still pops up from time to time, but she is not the editor she used to be. Why can't you admit that too? Or do you want to provide yet one more example of how you and Pigsonthewing attack one small part of an argument (IT'S A LIE!!!!) so no one will focus on the rest: that Wikipedia has lost a valued content contributor? Ruhrfisch ><>°° 16:27, 27 August 2013 (UTC)
PS In the interest of not contributing anymore to the avalanche here, and to give the Arbs a break so they can sift through all this, I am done - ping me if needed. Please play nice with each other while I'm away. Ruhrfisch ><>°° 16:27, 27 August 2013 (UTC)
Honest people correct mistakes, not rehash them to tar others unreasonably. Victoriaearle still makes the untruthful claim that "Yllosubmarine left the project" - do I need to supply you with the diff again? She could easily ask for that to be refactored, but chooses not to, so that you can repeat the smear on Andy that has no basis in fact whatsoever. Why did Yllosubmarine cut down on her GA/FA work? Why did you cut down on peer reviews? Peoples' circumstances change, and it's utterly inappropriate to heap the blame on Andy when there is nothing that supports it. The Tinker's Creek discussion occurred mid-September and Yllosubmarine edited 28 times in October - that's more than she had in the previous April, May, June or July. How on earth does that support your wild assertion about "behavior which discourages and drives away content editors"? You simply made it up. Address that fact first instead of making ad hominems about honest editors who have caught you out in a smear campaign based on a tissue of lies. -- RexxS ( talk) 16:00, 28 August 2013 (UTC)

Information on microformats

If anyone still needs information on microformats, as suggested above, please see microformat; my statement in the 2010 RfC; and my essay giving a comparison with persondata.

As I said in the second of those, Erik Möller, Deputy Director of the Wikimedia Foundation [spoke], in an article called Wikipedia to Add Meaning to Its Pages, about "making some of the data on Wikipedia's 15 million (and counting) articles understandable to computers as well as humans". Note, in particular, the part about "allow[ing] software to know, for example, that the numbers shown in one of the columns in this table listing U.S. presidents are dates". That's exactly what microformats do.

The cited article is also a very accessible overview.

I'm happy to answer any questions.

I would also add that I am firm believer in the benefit of infoboxes to our human readers; I added them before we started to use microformats, and I have worked hard to ensure their readability by humans, both visually and for those with visual impairments requiring them to use screen readers. And I would still add and improve them if they did not emit microformats. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:45, 26 August 2013 (UTC)

Smerus

I note the arb opinions that I have degraded infobox discussions and the examples cited of my comments against Gerda; I apologise for these and certainly intend not to indulge in such behaviour or employ such techniques again. May I ask then whether the unprompted incivilities (and sometimes gross incivilities) of Rexxs,(examples of whose handiwork I gave in my original evidence), Montanabw and PumpkinSky against myself during infobox discussions are also to be considered? There is PotW as well of course but his general behaviour is adequately covered in other aspects of this arb case. Thanks, -- Smerus ( talk) 07:06, 26 August 2013 (UTC)

I accept the apology. - I said before that I didn't need one and would like to only look forward. Thanks for expressing it anyway, -- Gerda Arendt ( talk) 11:49, 26 August 2013 (UTC)
Gerda is very gracious, and between the two of you, I hope you've patched things up. However, that leaves Andy and also your overall attitude toward anyone who proposes an infobox anywhere that you claim ownership in the topic. if you fail to see your own incivility, Smerus, and still cannot even when it has been pointed out to you (and others) with diffs and examples, then it proves my point that you are a mere bully who is mean to people who you think are weaker than you, but when called on your own behavior can only cry crocodile tears and claim that you are the victim. Montanabw (talk) 15:33, 26 August 2013 (UTC)
I hope it is clear from the above edit what I mean. I have not anywhere claimed that I am a victim. The abuse, name calling, unsabstantiated allegations and pose of moral superiority, is part of the culture of PotW, Montana, Rexxs and PumpkinSky, and if this arb case is about editors' polite behaviour towards others, then what is sauce for the goose is sauce for the ganders. In Wikilawyering capacity I am a six-stone weakling compared to the professional intimidation carried out by these characters. But I do not seek, like Montanabw, to be a moral touchstone, exonerate myself or to be claim to be heroically intervening on behalf of others; I only ask that all participants be evaluated as I have been. It seems from the recent request for diffs about me and Montana's ready response to this that the closing date for evidence has become irrelevant to this case; I can see it for extending for several months or years yet at this rate; so if arbs request me to produce diffs, there is no shortage of them and I shall be glad to oblige. Meanwhile, as Montanabw seems to note, Gerda and myself have taken constructive steps to make things work, which is more than most other contributors to this discussion have done. -- Smerus ( talk) 10:37, 27 August 2013 (UTC)
I'll be glad to see the diffs, particularly of my unprompted incivility. If I see you bullying Gerda, or saying that Montana is "libelling other editors", or attacking other women editors again, you can be sure I won't be civil when I take you to task for it. But that won't be unprompted. I am perfectly civil when I'm interacting with those who debate in a collegial and constructive manner, but a lifetime involved in resolving disputes has left me with little tolerance for those who deliberately don't. Mea culpa. -- RexxS ( talk) 12:46, 27 August 2013 (UTC)
But you are not an arb. I will gladly list them, as I clearly state, if an arb indicates that s/he will be willing to take them into consideration.-- Smerus ( talk) 13:18, 27 August 2013 (UTC)

Limited number of comments in discussions

While I completely understand why this has been proposed, and I can see that it will be a big help to curtail some of the unproductive discussions, it has as I see it two potential downsides:

  • Hampering productive discussions about content.
    In pretty much every area of Wikipedia that is not watched by those members of the classical music project who dislike infoboxes, the existence of an infobox is not at all controversial. Sometimes though the content of an infobox is not always clear cut and it requires discussion between various parties until everyone is happy that the information is correctly summarised, this can sometimes take several comments until people understand each other. Now imagine that there are three fields of an infobox that require discussion but you're limited to two comments. How do you proceed?
  • Discouraging productive discussions about infoboxes or their content.
    Evidence presented shows that a not infrequent sequence of happenings in the classical music sphere is that someone proposes an infobox for a given article, whether they know (or can know) it is likely to be controversial or not. This is either reverted or responded to with a comment along the lines of "No infoboxes on this article!", the proposer then responds with the reasonable question, "Why do you not want an infobox?" gathering only the response "I said no!". If someone has a maximum of two comments to make then this sort of behaviour is encouraged because it means you get to keep the infobox off 'your' article without having to explain why you don't want something that other editors think will improve the article.

As Carcharoth notes, "The fault (if any) seems to be more a frustration that others won't discuss things fully.". This is the crux of the matter, those who think infoboxes on articles improve them generally seem to want to discuss them and get them right. They are generally interested in why someone thinks that something is incorrect or too nuanced so they can understand the objection in order to work around it (by which I mean either correct the information, present it in a different way so it doesn't mislead or omit that bit of information from the infobox). In far too many cases this has been met with a refusal to discuss - often the infobox in its entirety or sometimes the objections to specific aspects of it ("piece of information X cannot be accurately represented in an infobox, therefore we must not have an infobox", rather than "piece of information X cannot be accurately represented in an infobox therefore the infobox will include on information ABCDEF which can be accurately summarised.").

It is not possible to have a productive discussion when one side refuses to discuss anything, and I don't see these proposed restrictions as helping that. Some things that I think would help would be:

  • A ruling that no party to this case may revert the addition or removal of an infobox from any article or talk page
  • A ruling that proposing an infobox on the talk page of any article where there has not been recent discussion of one is disruptive only when the proposal makes no reference to that article.
  • A ruling that arguments about a (proposed) infobox on a specific article are disruptive if they make no reference to why the infobox is or would be or not be beneficial to that specific article; and that such arguments may be removed by any uninvolved [editor|administrator].
  • Imposing a limit on the number of concurrent discussions about infoboxes that may be initiated by any party to this case. If that number was 3, then an editor must wait for the first discussion they initiated to conclude before they my start a fourth discussion.

As for more general alternatives, would the committee regard any of the following to be within their remit?

  • Mandating that discussions of individual infoboxes must take place only at the level of the individual article, and take into account only arguments related to that article?
  • Mandating that WikiProjects may not impose a blanket requirement for or against infoboxes on 'their' articles?
  • Mandating that discussion of whether articles should emit metadata is irrelevant to whether a given article should have an infobox?
  • Rule that WikiProjects do not own articles?

This is not a recommendation that the committee should do any of these things, it is asking whether they could do so if they felt it would be beneficial. Thryduulf ( talk) 11:56, 26 August 2013 (UTC)

Thank you for your thoughts for better collaboration! As for wording: "by those members of the classical music project who dislike infoboxes", it seems a bit too general, for example Kleinzach initiated infobox orchestra, infoboxes for compositions have a tradition to at least back to 2007, project opera initiated an infobox opera. The restriction is for biographies in the field. But you are right that some members dislike infoboxes, period. - We can practise consensus at The Ban on Love which I moved (for this purpose) from the case workshop back to the article where an infobox had been reverted twice. I just left the discussion for today with my self-imposed limit of only one entry to one discussion a day. -- Gerda Arendt ( talk) 13:03, 26 August 2013 (UTC)
I think something like a 1RR restriction might be useful. The problem with "consensus" is that no one knows what it is or when it has been achieved...for example, the WP Classical Music project claims a "consensus" against infoboxes, but that claim is then used to bludgeon anyone, anywhere, who proposes one. Yet, to have 10,000 individual article discussions seems other fruitless also. I DO think your comment about "one side refuses to discuss anything" is the crux of the matter, you can't reach consensus if one side covers their ears and shouts "lalalalalalalalaaaa!" or if there is a Greek chorus drowning out everything. If that can be addressed, the rest might fall into place. Montanabw (talk) 15:33, 26 August 2013 (UTC)

Propose that a community-wide discussion be held to determine global consensus on infoboxes

Apologies if this has been mentioned, as I've only been peripherally involved in this. I was reading through the proposed decisions and saw @ Newyorkbrad:'s Locus of dispute. I honestly don't see any way for the infobox question to be resolved on an article-by-article basis. The first bullet point reads:

"It is not clear how infobox disputes are to be resolved (e.g. if 5 editors favor including an infobox in a given article and 5 disfavor it, there is no default rule and no policy guidance for determining how the consensus is to be determined, so the dispute continues indefinitely)."

Setting aside the question of how to handle a tie, are we really content to resign consensus down to a vote at each individual article where it might arise? It seems like that's what this comes down to, and if that's the case, it would actually save everyone a lot of grief to state it plainly and simply: Do not discuss, but rather simply vote, as this comes down to individual preference, so majority therefore rules in each case. As far as each individual article is concerned, there is really nothing to argue about. It doesn't seem like the infobox question is actually all that article-dependent, beyond the infeasibility at certain topics (an article about an author is feasible, while something like dystopia might not be), and the fact that different people with different opinions on infoboxes might be editing at those respective articles. Again, it comes down to individual preference.

The above really doesn't seem like any sort of Wikipedia-style solution though. If any semblance of actual WP:Consensus currently seems impossible as there is no relevant policy or guideline, nor even a logic to point to on a per-article basis, maybe this is the time to start answering the question by putting it to the community at large. I'd like to see that as one proposed decision, assuming those can still be added. Equazcion (talk) 17:20, 26 Aug 2013 (UTC)

There's no reason why someone can't independently launch an RfC at a village pump, or some other appropriate location. That being said, for myself, I support the use of infoboxes, but oppose making them mandatory. There are always exceptions to the rule. Reso lute 17:27, 26 August 2013 (UTC)
I'm with Reso. I update Infoboxes all of the time but don't think they should be mandatory, especially on articles that are not biographical. I can't see there being a straight "Yea for Infoboxes", "Nay against Infoboxes" vote because however it was decided, it wouldn't reflect a consensus, just a majority for those editors who cared enough to cast a vote. I'm not sure if there any solution other than deciding this article-by-article. Liz Read! Talk! 18:55, 26 August 2013 (UTC)
Quite. Some if us have been trying that. Look where it's got us. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:58, 26 August 2013 (UTC)
[ec] "I support the use of infoboxes, but oppose making them mandatory" - Me too. Who is it, remind me again, who wants to make them mandatory? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:57, 26 August 2013 (UTC)
Well me for one, for certain types of article where the Wikiproject so decides, and with a certain allowance for IAR, as I've said more than once in the case. And the 31 users of Template:User Infobox pref - "This user believes that all articles should have an infobox". But certainly not for all biographies - biographies are one of the problematic areas for infoboxes. A pertinent example today, from my watchlist. Johnbod ( talk) 21:07, 26 August 2013 (UTC)

Kinda getting off point. I think rehashing the opinions of all involved here on the infobox question isn't going to be all that helpful. We've seen arbitration decisions before that a community discussion be held to gauge a broad consensus, and I think such a decision would be appropriate here. Equazcion (talk) 19:44, 26 Aug 2013 (UTC)

( edit conflict) It would be an appropriate remedy in the sense that nobody would object to either its relevance to the case or disagree that it is within the committee's remit to pass such a remedy. I don't think that it would be useful though - at the end of it I would be prepared to bet a significant amount of money that the answer would come back "The community supports infoboxes but doesn't think they should be mandatory" - i.e. exactly where we are now. This is because other than a very small minority of people who dislike infoboxes per se, almost everybody agrees with the status quo. Even if anybody wanted to make them mandatory (which I've never seen any evidence of) there are some articles where its just not possible (e.g. Orthogonality and Types of inhabited localities in Russia), and there are other articles that are structured by their very nature and so any infobox would just be duplicative (e.g. List of Justices of the Supreme Court of the United Kingdom). You would therefore have to mandate them only on articles where they were appropriate - which gets us back to exactly where we are now. What needs to happen is for the discussions about infoboxes on pages within the sphere of classical music to become detoxified such that they are as productive as the discussions about infoboxes on the other 99.99% of Wikipedia. Thryduulf ( talk) 19:48, 26 August 2013 (UTC)
I wasn't really suggesting only those two questions be asked. We could additionally ask the question, "Should infoboxes be mandatory on every article about a person"? I think that would produce interesting and useful results, just as an example. Let's start fleshing out some guidelines here (not literally here, but at a global discussion) so that people arguing at articles actually have something to discuss. Equazcion (talk) 19:54, 26 Aug 2013 (UTC)
I don't support mandating their use even for articles about a person because there will always be edge cases where an infobox is not appropriate and other cases where it is debatable whether the article is about a person. The first example that comes to mind (although there will be better ones) is Piltdown Man. Thryduulf ( talk) 20:21, 26 August 2013 (UTC)
It's great to know what you think, but I wasn't really asking, with all due respect. I'm again suggesting a community discussion. But just as an aside, yes, if infoboxes were mandated for "person" articles, there would be some scattered instances where the article topic is ambiguous, and that would need to be discussed at the article. As is the case for most guidelines, they're not always easy across-the-board answers, but can rather be a place to start, whereas right now there is nothing on which to base a discussion. Equazcion (talk) 20:36, 26 Aug 2013 (UTC)

I'm not suggesting this be a straight yes-or-no question; only that it be a community discussion on what to do. We can make room for several possibilities. The point is, it seems arbitrary to leave it up to the "i like infoboxes" or "i don't like infoboxes" stances of whomever might be at a particular article at a particular time (that's essentially what it will come down to). Centralized community discussions (especially those commenced by arb decision) tend to make room for several possibilities, not simply a yea or nay. Let's see what we can come up with. Equazcion (talk) 19:44, 26 Aug 2013 (UTC)

Considering that ArbCom is close to banning a user for advocacy of infoboxes and thus singling one user out as a scapegoat, against an "old guard" of rather mean and nasty-acting sorts who continue to do anything (including collapsible side navboxes) to avoid having "teh dreaded infoboxen" appear on "their" articles - you may have a valid point. If "consensus" leans toward infoboxes, then the sanctions toward this user would be moot. Montanabw (talk) 20:22, 26 August 2013 (UTC)
Any sanctions imposed on Andy Mabbitt will be an indication of his behavior alone - nothing more or less. Any great debate on the general usefulness of infoboxes will be millions of wasted words of waffle - most of them written by editors who have never written a useful page in their lives. The present system of adding an infobox only after debate with the primary editors on the talk page is the most satisfactory and least aggressive way of obtaining consensus that there's likely to be. The problem has always been Andy Mabbitt's inability to accept this.  Giano  20:31, 26 August 2013 (UTC)
I'm still struggling with this notion of "primary" editors, and how this concept could have possibly gained even moderate acceptance in a discussion here, of all places, where there's a policy called WP:OWN. But I digress. This should be put to a community discussion. I don't care about how various editors have behaved and don't have an opinion one way or the other on sanctions (because frankly I'm not familiar with their history) but the way these things are handled in general should be discussed broadly, as this is a broad-reaching issue, regardless of how lowly you regard the opinions of those who might respond. Equazcion (talk) 20:41, 26 Aug 2013 (UTC)
On Wikipedia, those seeking to bombastically impose their own views on others have always erroneously invoked WP:OWN. Fortunately, most people see the flaws in such false reasoning.  Giano  20:49, 26 August 2013 (UTC)
( edit conflict) It's not erroneous. If someone is imposing their own views on others then they could be wrong too, but if you counter with any argument based on "primary" editors or anything synonymous with that, you're just as wrong, as you're doing precisely what WP:OWN warns against. It is the very purpose of the policy to prevent such stances from being credible. You may have a point that an editor acted inappropriately, but if that's the case then you've got the reasoning wrong. Equazcion (talk) 20:57, 26 Aug 2013 (UTC)

It is abundantly clear that a community-wide discussion about some of the issues raised in this case is needed. The trouble is that in the past when ArbCom have stated that explicitly, the response is at times a resounding silence. Literally. I may have missed it, but in the Doncram case earlier this year, ArbCom suggested (in relation to the stub guideline) that "this question may need to be decided through a deliberate attempt at conducting focussed, structured discussions in the usual way." I am not sure if that ever happened. In part, this is human nature as the last thing most people want to do after a lengthy ArbCom case is to carry on the discussions. You can take a break for a month or so, but people are often still reluctant to return to things especially if some of the ArbCom remedies may have calmed things down. Bit of a Catch-22 really. The other problems are that many casual editors will be completely unaware of WP:INFOBOXUSE, and many editors will have widely varying experiences and expectations in relation to infoboxes, which makes centralised discussion not as easy as it looks. You need to prepare such an RfC and gain input from all those who have strong views on the matter, otherwise the results won't be accepted. Carcharoth ( talk) 20:54, 26 August 2013 (UTC)

If the decision is made to put the question to the community, and no one is mandated to actually create it, then yes it could result in silence. I think if an RfC actually appeared, with a watchlist notice, there would be widespread participation. I would create one myself right now if I thought I could make a good one, but I was hoping someone smarter and more capable than myself could craft a good one. It needs to present all the right information and distill all the issues into a viable group of questions, and if that happened I think it could work. I have a feeling the infobox issue isn't quite as contentious in the broader community as it is with those vocal few present currently. Equazcion (talk) 21:04, 26 Aug 2013 (UTC)
Go ahead. Almost anything would be better than the way we deal with disagreement now. Today I looked at the history of Sparrow Mass again, and I suggest you do the same, it's short. I added an infobox, after doing so to the liking of the principal author for Schubert's masses. Was that aggressive? Less than two hours later it was reverted, edit summary "cleanup". Was that aggressive? It looked to me not very thoughtful, so I reverted, asking for discussion on the talk. Edit conflict war, page protected. Andy was not on the scene. -- Gerda Arendt ( talk) 21:22, 26 August 2013 (UTC)
See, here's the issue. Per WP:BRD, you never should have restored the infobox after being reverted, regardless of whether you agreed with Nikkimaria's removal being characterized as "cleanup". Rexxs (with an ironic edit summary) and Diannaa should not have tag teamed to try and force its inclusion, nor should Nikki have edit warred against the three of you. But all of that came about because you incorrectly figured the guideline was bold, revert, revert, discuss. Once the page protection was lifted, the infobox was again removed to restore status quo ante, and you were right there to restore it yet again. Why? What did you expect to gain when there was already a discussion on the talk page, involving the usual suspects? Reso lute 23:33, 26 August 2013 (UTC)
You are right, I should not have reverted. But was it "aggressive". It was a spontaneous angry reaction to something unexpected I could not believe. By now, I am on 1RR, voluntarily so. Looking back to April and June gives you a wrong picture, I improved. So did Andy, no? (He didn't touch that article, sorry I was not precise about the meaning of "scene"). -- Gerda Arendt ( talk) 07:30, 27 August 2013 (UTC)
It should also be noted that Andy was, in fact, on the scene, apparently misrepresenting the outcome of his microformats RFC to try and gain the upper hand in that discussion. Reso lute 23:36, 26 August 2013 (UTC)
What I said was We've had RfCs which have shown community consensus to use infoboxes to emit microformats}}; and though I commented on the talk page, I did not edit the article, which is what Gerda is referring to. [Note Gerda means edit war, not edit conflict. Corrected.] Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:53, 26 August 2013 (UTC)
Yes, and SilkTork's closure of that RFC made it clear that no such consensus existed on the use of microformats, let alone the use of infoboxes as the delivery system. They only noted an indication of support of considering the use of microformats in general. Unless, of course, there is a different RFC that I am not aware of. Reso lute 23:55, 26 August 2013 (UTC)
There are other RfCs, yes, one cited above; and the Composers Project RfC authorised the use of {{ Infobox classical composer}}, which has emitted a microformat from the get-go. Your reading of ST's admittedly ambiguous-in-part closing statement also omits some important detail: "In general people felt that microformats had a place on Wikipedia, and there were no views calling for an outright exclusion". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 00:04, 27 August 2013 (UTC)
Err, no, I quite clearly said "They only noted an indication of support of considering the use of microformats in general." Reso lute 00:08, 27 August 2013 (UTC)

Section of Propose that...

I think it's important to note what ArbCom can and can't do. The Committee can impose binding decisions regarding inappropriate behaviour - such as users consistently ignoring consensus. The Committee cannot make decisions regarding content or policy or guidelines, nor force the community to have discussions regarding content or policies (the Committee can recommend or suggest such discussions, and the community can quite rightly ignore such recommendations). We have community wide consensus on the use of infoboxes which has been quoted in the findings: WP:INFOBOXUSE. This has been in existence since October 2011. If people feel this needs amending then the appropriate place to open a discussion would be on the talkpage of Wikipedia:Manual of Style/Infoboxes. What this case is partly about is not that we don't have a guideline regarding the use of infoboxes, but that some users may not be appropriately following that guideline - that is to say that some users may be urging either the consistent use of infoboxes on all articles as standard, or conversely, some users may be insisting that infoboxes are not to be applied to a certain section of articles. The guideline indicates that use of infoboxes on a particular article, if contested, is decided by discussion and consensus on the talkpage of that article. Discussion has been taking place. The decision for the Committee is whether such discussion has been handled appropriately, whether those taking part in the discussions are taking on board the concerns of others, and whether certain users are having contentious discussions regarding the use of infoboxes so often as to be considered disruptive. The Committee's considerations on these matters will be informed by awareness of existing guidelines and consensus, but it is outside the scope of the Committee to alter consensus or to ask the community to set about altering consensus. My own view on infoboxes broadly aligns with consensus - properly used they provide useful information, but they are not always required, so making them mandatory would be inappropriate. If editors cannot reach agreement in a discussion regarding the use of an infobox in an article, they should avail themselves of the Wikipedia:Dispute resolution procedures we have in place.

However, making a focus on infoboxes is perhaps taking the spotlight off the real issue, which is the use of metadata. Infoboxes come into the picture, it seems, because they are regarded as the best means of employing the metadata software. The issue is that those in favour of employing the metadata software wish to place an infobox on articles which don't have one. Some users are objecting to having an infobox on an article where it may not be appropriate merely in order to employ the metadata software. If there is to be a community discussion on something, it should be on the use of metadata software on Wikipedia. Infoboxes would come into that discussion, as they are seen as fairly indispensable to the employment of metadata. My understanding of the metadata software is that it is able to encode certain basic information, such as the date of construction of a building, its location and size and type, and that can be translated into whatever readable format is appropriate by compatible software. This means that information can be transferred by means other than text. In previous discussion on metadata there is a consensus that it would be appropriate to explore this technology. Where there hasn't been consensus is how to use this technology - and how much we should be adjusting Wikipedia to fit the technology (such as employing infoboxes on all articles, regardless of local consensus on the appropriateness of such infoboxes).

That is, however, only the background. This case is not about should Wikipedia be using this technology. It is about whether some users have behaved inappropriately in attempting to get this technology accepted everywhere on Wikipedia, or whether some users have behaved inappropriately in attempting to block this technology being employed in certain places on Wikipedia. Andy Mabbett is the expert on this technology, and if we are to fully explore it, his knowledge and experience would be invaluable. However, it appears that in his enthusiasm for the technology, he has been irritating a number of other users, and he has perhaps not been spending enough time on Wikipedia getting the community to buy into his vision. It is a grave error, and one that may prove costly both to him, and to the advancement of this technology. It is frustrating that this is the third time he has been involved in an ArbCom case related to the same issue. Though a user may be pursuing the right end, the means are also very important, and the community cannot work well if some users are allowed to ignore consensus because they have a good idea.

My view is that I am inclined to support a site-ban for Andy Mabbett, but I also see the need for the community to have a full and detailed discussion on the metadata technology, and such a discussion would benefit from the involvement of Andy Mabbett. I am wondering if a suspended site-ban would be appropriate. Allow Mabbett time on Wikipedia to get others to buy into his vision. Build some bridges. Explain more clearly how the technology works. And listen carefully to the concerns of the community. Perhaps get the site developers and the Foundation involved. While doing that, there would be certain conditions which if he broke would trigger an indef ban. Conditions such as: edit warring; arguing over using an infobox in an article (if someone objects, simply back off - there are over 4 million other articles on Wikipedia to work on); and being dismissive or incivil to other users (think twice before clicking "Save page" - has that comment the potential to be read as offensive or hostile? As an example - repeating in bold three times "Why are you making pronouncements on the validity of this request if you do not understand such things?" has the potential to be read as offensive and hostile). I haven't decided yet to simply support the current site-ban, or to propose a suspended one. SilkTork ✔Tea time 03:00, 27 August 2013 (UTC)

"Why are you making pronouncements on the validity of this request if you do not understand such things?" has the potential to be read as offensive and hostile. It can also be read as helplessness when faced with missing a basic common ground in a discussion, which needs to be established before you can reasonably talk. See (from Don Carlos):
  • My general thoughts on the Infobox (including that in my personal history I argued exactly as shown above) is found on Wikipedia:QAI/Infobox, short: the infobox is meant to repeat, in structured form, -- Gerda Arendt ( talk) 11:49, 7 July 2013 (UTC)
That's not consistent with WP guidelines on infoboxes which stress that they are to summarise not repeat. -- Klein zach 14:46, 8 July 2013 (UTC)
Without looking: How would you "summarize" a date of first performance, a subtitle, the name of a librettist, etc? If the guideline does not allow to repeat those key facts it needs to be changed, -- Gerda Arendt ( talk) 14:51, 8 July 2013 (UTC)
No, Gerda, the box is supposed to summarise the article, i.e the article as a whole. Klein zach 15:07, 8 July 2013 (UTC)
How can one say politely that a key player in the infobox discussions has a misunderstanding of what they are? I wonder how much conflict could have been avoided if it was accepted that infoboxes hold key facts, not a summary of the article. Wikipedia:Manual of Style/Infoboxes#Purpose of an infobox: "When considering any aspect of infobox design, keep in mind the purpose of an infobox: to summarize key facts in the article in which it appears." I understand that this means only key facts, avoid trivia. - What do you think? - Do you think an infobox on Verdi has to capture his genius? It's a myth. Not even an article can do that. - A common understanding of such basics is crucial for a discussion. -- Gerda Arendt ( talk) 06:16, 27 August 2013 (UTC)
While particular users' behavior in these particular cases is certainly a big part, if not the focus of the case, I think the arbitration committee has an opportunity to make a recommendation regarding the larger underlying issue that causes these conflicts to arise, even if until now they've taken place on a smaller and less noticeable scale. The guideline we have really offers no guidance at all -- it is in the end merely a negative statement: that there is no policy, so just decide amongst yourselves, using no criteria in particular. In addition to deciding what sanctions to impose on users, I think making broader recommendations when an underlying issue is present seems to have always been within the purview of arbcom. Equazcion (talk) 03:37, 27 Aug 2013 (UTC)
The "Why are you making pronouncements on the validity of this request if you do not understand such things?" comment was in this discussion, where (as Gerda suggests) it seemed a proportionate response to the wall of the demonstrably ill-informed and ad hominem dismissal of a proposed action which already has unequivocal support at an RfC (and which as a result of that unfounded intervention is currently stalled). Since that's not how it read to you or others, at whom it was not addressed, I apologise. I wonder if you, @ SilkTork: would like to comment on similarly worded, "offensive and hostile" comments addressed to me and others on various talk pages, by parties and commenters in this case, along the lines of "you clearly have no interest in..." or "you clearly have no knowledge of...", which, unlike my comment under discussion, are not accompanied by evidence and have no basis in fact? Also, which are the other two "metadata arbcom cases" to which you allude? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:31, 27 August 2013 (UTC)
I would be more reassured Andy if you were reflecting and taking on board concerns that people raise rather than arguing against them. If any user proposes something - regardless of what it is - they will likely meet some concerns. Some of these concerns will be valid. Some will arise out of a lack of clarity regarding some aspects of the proposal. Some may well be wide of the mark. All concerns need to be met with the same politeness and genuine attempts to allay the concerns. If after several reasonable attempts to allay the concerns they are simply repeated without showing signs of understanding, and if after reflecting on the adequacy of the explanations, perhaps asking what aspects are not clear, possibly rephrasing if needed, the same concerns are again repeated and it starts to appear as though the person asking is being disruptive, then it is better to ask for assistance rather than resorting to be impolite. If at this stage you don't understand that, then I am concerned. SilkTork ✔Tea time 09:37, 27 August 2013 (UTC)
In general, a fair point, and one I'm taking on board as a a result of this case (if you will, consensus not only has to be done, but be seen to be done), and I would indeed seek third party assistance in such cases in the future (you can read that as a formal undertaking if it helps). You appear to have missed my question about similarly worded, "offensive and hostile" comments. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:54, 27 August 2013 (UTC)
Andy, you are close to drowning, Silktork tosses out a lifeline, and you are essentially complaining that it didn't precisely hit the mark. Astounding. SPhilbrick (Talk) 18:13, 28 August 2013 (UTC)

( edit conflict) [This case] is about whether some users have behaved inappropriately in attempting to get this technology accepted everywhere on Wikipedia, or whether some users have behaved inappropriately in attempting to block this technology being employed in certain places on Wikipedia. Andy Mabbett is the expert on this technology, and if we are to fully explore it, his knowledge and experience would be invaluable. However, it appears that in his enthusiasm for the technology, he has been irritating a number of other users, and he has perhaps not been spending enough time on Wikipedia getting the community to buy into his vision. This to me is the heart of your apparent misunderstanding. As evidence has repeatedly shown, it is not Andy who is failing to get the community to buy into his vision, the problems all stem from a small number of users who have a dislike of infoboxes and who refuse to engage in discussion about it. You can continue to try to ban Andy for having been banned before if you want, but you can't expect people who have actually read all the evidence in this case to support your "grand vision" for an Andy-free project, nor can you expect it to solve the actual problems in this case. Thryduulf ( talk) 09:43, 27 August 2013 (UTC)

Is there an article showing an infobox edit war with only arguments from infobox supporters on the talk page? Why are those who oppose infoboxes considered to "refuse" discussion, whereas supporters are just trying to help? Some editors are able to propose change in a manner that is not disruptive. When such an editor encounters stiff opposition, they adapt, assuming that the opposers are acting in good faith, and that assistance or time is needed so others can understand the benefits of the proposal. A good editor might even contemplate whether the opposers have a valid point of view. Some editors can collaborate, while disruption seems to follow others. Johnuniq ( talk) 11:23, 27 August 2013 (UTC)
There is ample evidence in this case of where I or others have attempted to open a dialogue, and been met with a blank refusal. There is no evidence of the reverse. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:31, 27 August 2013 (UTC)
That's not strictly true Andy. In the Frank Matcham discussion you were offered an alternative compromise version, which you refused to even consider "because it finds no favour". To say there "is no evidence of the reverse" is just misleading, I'm afraid, although I'm sure it may have just slipped your mind. - SchroCat ( talk) 11:39, 27 August 2013 (UTC)
Yes, SchroCat, it is strictly true. In the Matcham discussion, I replied: "...the collapsed infobox, with hidden content, hasn't been implemented across WP because it finds no favour, unlike the million-plus uncollapsed infoboxes we have... Collapsing the infobox not only defeats its primary purpose, of providing a quick and convenient fact-list for those readers who desire or find useful such a thing (and there is evidence that readers [...] do), but also hampers the usefulness of providing accurate machine readable metadata, since hidden content is more likely to be overlooked when pages are updated. However, if you still think we should adopt that model despite such shortcomings, then - again - a centralised RfC should be the way forward." (of course, I should have said "2.5 million-plus uncollapsed infoboxes". Mea culpa). That might be a discussion that you find inconvenient, or even dislike intensely, but for you to attempt to portray it as a blank refusal to open a dialogue is at best misleading and quite possibly disingenuous. You continue to throw out false allegations, based on either no evidence or blatant misrepresentation of evidence. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:03, 27 August 2013 (UTC)
I'm afraid we are going to have to agree to disagree on this, as we do on so many things. You were offered a compromise solution on Matcham: you rejected it out of hand with a line of argument that a)smacks of WP:IDONTLIKEIT, and b) I am not sure I believe ("hampers the usefulness of providing accurate machine readable metadata"? Not at all true). It's not a question about an argument that I find inconvenient or dislike, so please don't try and double guess my rationale again: try to stick to the more concrete things people can understand, without trying to look into the psyche of others. I'll ignore your regular passing (and baseless) ad hominem comment, I find them part of the scenery in discussions with you, so there's no point in trying to rile me with such silliness. - SchroCat ( talk) 12:29, 27 August 2013 (UTC)
Like something or not is one thing, but accepting something that "defeats its primary purpose" seems strange. I also have to disagree with you on this, SchroCat, as I disagreed with Nikkimaria on it, see? Dealing with a cantata "There is a contrary and despairing thing" (illustrating my present feelings quite well) I phrased about collapsing: I "regard (crossed out stronger term for dislike) the other as against the spirit of an infobox as openly accessible information. I don't revert it in articles of others (Little Moreton Hall comes to mind), but please please please don't do that to me in my articles, - it's against my sense of quality." The reply was: "functionally, there is little difference", which told me that I was not understood. -- Gerda Arendt ( talk) 12:50, 27 August 2013 (UTC)
( edit conflict) Please feel free to disagree all you like with my reasoning in the cited comment, and the basis for it; and even to wrongly doubt my sincerity. But to pretend for a minute that it is evidence of refusal to engage in dialogue is fatuous in the extreme, and to describe it in such terms and link it to a pattern of similar incidents is not ad hominem. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:55, 27 August 2013 (UTC)
"You continue to throw out false allegations, based on either no evidence or blatant misrepresentation of evidence." There was no false allegation and I find your words an ad hominem that are, at best, unhelpful, as is following it up by accusing me of being "fatuous". I stick by what I first said, that you were not being entirely accurate when you said "I or others have attempted to open a dialogue, and been met with a blank refusal. There is no evidence of the reverse." There was evidence of the reverse, it's just that you didn't like what was being offered to you and rejected it out of hand. I'm taking this off my watchlist (again), so feel free to write whatever you want: others will judge your words for what they are. I find interacting with you utterly frustrating and demoralising: you can't see beyond beyond your own opinions on things and cannot behave like discussion is anything but a battlefield for you to smear and wound your opponents - and well done for beating another person away from a discussion. I'm utterly sick and tired of it and hope that I never see another petty, supid and pointless infobox argument break out again. - SchroCat ( talk) 13:12, 27 August 2013 (UTC)
I don't know what you mean by "infobox edit war with only arguments from infobox supporters on the talk page", it seems logically impossible, - it's war or it's only one side. Wars are rare, thank goodness, we try to learn, really. More frequent are discussions with repetitions of similar arguments, see [[ Rigoletto, reaching no consensus. We need a procedure to solve those cases, and banning one contributor will not solve them. However, as mentioned above, one protector of the status quo found a simple solution: change the Manual of Style. (Rigoletto would fall into a category which has no more option for an infobox.) Can we please come up with something more constructive? -- Gerda Arendt ( talk) 11:55, 27 August 2013 (UTC)
I'm going to have to respectfully disagree with you, SilkTork, about what ArbCom can and can't do. In WP:ARBDATE, a protracted and difficult case that occupied seven months of 2009, ArbCom passed the following Enforcement:
  • Stability review: "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 that has broad community consensus."

Ryan Postlethwaite (God bless him) put a huge effort into organising and conducting a grand RfC to settle the content issues. It succeeded and there has been no war over any form of date de/linking to this day. I agree that ArbCom can't settle the content issues itself, but as you have indicated, it could go a long way to making sure it's in the interests of all involved for the warring to stop. -- RexxS ( talk) 13:13, 27 August 2013 (UTC)

Further update

By my estimation, it is likely to take at least another week before the case is close to closing (possibly longer). I'm aware that there has been a large amount of debate on this page in recent days, but can I ask that everyone please show restraint and focus purely on the proposed decision from now on? That will help those arbitrators who have yet to vote or complete voting, as there is a lot on this page for them to read. Carcharoth ( talk) 23:50, 26 August 2013 (UTC)

It is to be hoped, not least given AGK's undertaking and his request for additional evidence, that those who have voted will also be reconsidering. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:55, 26 August 2013 (UTC)
I can speak from bitter experience that if you're going to railroad somebody in an arbitration proceeding you need to do it fast before people notice what you're up to and start asking pesky questions about evidence and motives. By all means, let's drag this out and see if some clueless administrator will block one of the participants while you all decide whether or not to jump off the ledge. Mackensen (talk) 00:40, 27 August 2013 (UTC)

Better a well-thought out and consider decision, Carcharoth, than one made to hastily made. As far people posting, I'm not sure what can be done about that. People want to talk about this case and they will look for an appropriate forum to discuss it. If not here, it has to be on another page. Liz Read! Talk! 00:50, 27 August 2013 (UTC)

I understand Carcharoth's frustration quite well. He's trying to get the stupid case in the can (whether it's just or not is beside the point now) but no one dithers more than a half-active arbitrator who has just realized this job isn't what s/he signed up for and can't bear taking an unpopular stand. In the meantime, the talk page is exploding and he knows sooner rather than later someone's going to say something rash enough to earn a civility block, and then we'll have to hold a whole other arbitration case to deal with the inevitable fallout. Clock's ticking.
As to the merits, it's clear from the proposed decision that the committee should never have taken the case in the first place. None of the proposed bans are really supported by the evidence; if that's all it takes to get someone banned these days I've some scores to settle and some cases of my own to bring, although somehow I don't think I'll be as successful. No one's indispensable, but that doesn't mean prolific editors should be banned, blocked, or restricted lightly. This is ultimately a content dispute, not a personal one, and it'll have to be settled in the usual, painful way. You ought to just dismiss it, or water it down with the usual adjuration that we should all be nice to each other. Mackensen (talk) 00:58, 27 August 2013 (UTC)
Mackensen (a former arbitrator) makes some good points. Liz, it would be a good idea to centralise 'overflow' discussion at another page and leave links from here (anyone is welcome to do that). Specific commentary about aspects of the proposed decision is what is really needed. Some wider debate has been helpful initially, but that can only go on for so long before it detracts from the specifics of discussing the proposed decision. More specifically, those facing sanctions need the time and space to respond to what is being decided here. Carcharoth ( talk) 01:10, 27 August 2013 (UTC)
You know, I beginning to wonder why anyone would want to be an Arbitrator. Seems like a thankless job. Thanks for plugging away at it, even in mid-August. Liz Read! Talk! 01:51, 27 August 2013 (UTC)
Just to give an update from me; I'm one of the dithering Arbitrators referred to above. I have been trying to keep up with this case, but I have other Arbitration work too: CheckUser/Oversight appointments, Ban Appeals work, and the Tea Party Movement case. All three have been neglected just as this case has. I'll try to get this done by next week, but realistically that may or may not happen. For now, my preliminary analysis it to support the first several paragraphs of what SilkTork wrote above but again, there are a billion RFCs and talk page discussions to read and for someone who found out that there was a serious problem with infoboxes on Wikipedia in July 2013, it's not exactly the easiest thing to immediately grasp. NW ( Talk) 03:15, 27 August 2013 (UTC)
If you want a gentle suggestion, it looks really bad when your (the committee's) proposed decision essentially ignores one side of a dispute, even though ample evidence was presented. Arbcom isn't supposed to take sides in a content dispute, but you are here. Mackensen (talk) 04:38, 27 August 2013 (UTC)
If you want to take another gentle suggestion: don't look at a billion RFCs but at 2013, it would make your life easier and mine. Remember:
@ NW: your wording "ban the worst offenders" reminds me of " arrest the usual suspects". As one of them, I urge you to go beyond suspicion, to facts, -- Gerda Arendt ( talk) 18:56, 15 July 2013 (UTC)"
That's an excellent point, Gerda. That was me looking at the situation in July, never having understood that there was a problem with infoboxes. Having extensively read the evidence since, I understand that my first impression was entirely wrong. I'm still not entirely sure how I'm going to vote on the case but I know "arrest the usual suspects" is not on the table. NW ( Talk) 17:00, 27 August 2013 (UTC)
Thank you! There should be no problem with infoboxes, meant to be help and service. Repeating: if someone added infoboxes to my articles, I would say thank you. It is hard to understand for a newcomer - I am relatively new to the topic - why most works by Kafka have an infobox, no problem, but the addition of one to a book article in September 2012 is still remembered as a (insert the terms you heard) discussion, believed by some to have driven away a precious editor. This is not the fault of the infobox, which is rather simple in case of a book. The Rite of Spring, similar, a composition, - Bruckner's symphonies have infoboxes since 2007. - I have good news for you and all: the unilateral change of the MoS of project opera, aiming to keep the operas of all major composers free from an infobox, was reverted, a discussion is called for. -- Gerda Arendt ( talk) 19:07, 27 August 2013 (UTC)
@ NW: I'm not really surprised that you didn't know of problems with infoboxes because over most of Wikipedia, there's no concern. However at WikiProject Composers, infoboxes have been a problem for many years. If you're feeling masochistic, take at look at the 2010 Wikipedia talk:WikiProject Composers/Infoboxes RfC - 219 kB of text where you see the same anti-infoboxers rehearsing the same weak arguments ("redundancy", "consensus amongst the main contributors", etc.) against a different bunch of pro-infoboxers (many of whom have since moved away). You find DGG patiently explaining about the value of metadata and about building the semantic web, and you even find Kleinzach complaining about canvassing, because the pro-infoboxers hadn't notified all of the other relevant wikiprojects. What's the word I'm looking for? -- RexxS ( talk) 14:57, 28 August 2013 (UTC)
I am not concerned about myself, and I haven't seen recent facts that would justify banning. -- Gerda Arendt ( talk) 07:09, 27 August 2013 (UTC)

Infoboxes and new articles

Any restriction on adding/not adding infoboxes to articles should specifically exempt creating new articles. As it currently reads, the first Pigsonthewing remedy seems to say that he cannot add an infobox to an article that he creates. –  Philosopher  Let us reason together. 03:12, 27 August 2013 (UTC)

Nor an eight-word stub that I turn into a proper article. Nor an article on a subject well away from classical music and he other parties in this case, where there is no dispute on the use of infoboxes; or even where infoboxes are the norm. Note my evidence higher up on this page, listing the 60 infoboxes I added to existing articles in the first six months of this year. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:15, 27 August 2013 (UTC)
I didn't look closely enough at the case to see if a restriction on the other cases you mentioned would be merited or not. My only thought was that since this is about conflict between users, a restriction where there was only one user would be irrelevant. –  Philosopher  Let us reason together. 02:18, 2 September 2013 (UTC)
See the section "Proposed remedy 1.1" currently at the bottom of the page, where I have proposed wording that allows for this. Johnbod ( talk) 03:03, 2 September 2013 (UTC)

Finding of Fact No. 4

Could I prevail on whomever's drafting this decision to clarify the problematic behavior? I see much forceful arguing, yes, but that's not impermissible and in general appears to be within the bounds of civil discourse. The evidence linked is also rife with personal attacks, bad faith, and innuendo from editors not named Pigsonthewing, none of whom are themselves subject of findings of fact or "remedies." If I were looking at those linked pages as a matter of first impression it would not occur to me that it was Pigsonthewing who was being sanctioned, and I'm still not sure what policy he's alleged to have violated. Thanks, Mackensen (talk) 12:31, 27 August 2013 (UTC)

  • Still waiting for an answer here. Surely the ten who endorsed it and five who (presumably, given no other findings of fact) consider it the basis for a ban can quickly explain. If there's confusion about why you're banning someone then maybe it's not a great idea. Mackensen (talk) 12:31, 28 August 2013 (UTC)
  • I am deeply concerned that an arb decided to vote for banning Andy, mentioning the Peter Planyavsky case. Andy helped me (!) there, as often, on "my own" article where I wanted an infobox (and still don't have it). -- Gerda Arendt ( talk) 12:49, 28 August 2013 (UTC)
    • I'm put in mind of Henry's apocryphal plea, "Will no one rid me of this turbulent priest?" This case now borders on the farcical. Mackensen (talk) 13:31, 28 August 2013 (UTC)
  • As is quite apparent to me, and as the finding states, Andy's contributions to the theatre of infobox disputes have been broadly unhelpful. The diffs show a sample of the evidence to support that conclusion; and they are illustrative, not exhaustive. Bearing in mind that this has been a heated and protracted dispute (where level-headedness is basically mandatory, if the whole thing isn't to descend into chaos), I don't think it's reasonable to contend that Andy's conduct illustrated by these diffs was helpful; is that what you're trying to suggest in your first few sentences?

    I was under the impression that anybody else who is a prolific party to this dispute has been appropriately sanctioned, if they have had a negative effect on the dispute, but even if there were other people whose conduct has been wrongly overlooked, that would not excuse Andy's truculent interactions with the other disputants, nor make his previous influence on the dispute less disruptive. Debating whether he's earned a site ban is fair enough, but suggesting that he's conducted himself appropriately on all, or even on many, occasions is pretty out there. AGK [•] 18:07, 28 August 2013 (UTC)

  • Well, I think you're asking me to prove a negative. What would helpful look like? Reading over the discussion truculent may be apposite, but he's not uncivil, he's not name-calling, and he's generally advancing the idea of why a particular edit ought to be made. I'm not aware of anyone else being sanctioned in this dispute, and I think that if you're going to ban someone outright you need to go a lot further than characterize comments as "unhelpful", especially when you have other editors specifically disputing that characterization. Above all you need specifics. Let me ask another question: do you see any other unhelpful people on those talk pages? I do. Do you think they're going to be helpful to the next editor who rolls around if you ban Andy? I don't. Mackensen (talk) 18:14, 28 August 2013 (UTC)

Continued collaboration?

What I like best on Wikipedia is collaboration.

  • Did you know that Andy and I created {{ infobox Bach composition}}?
  • Did you know that it was copied to the German Wikipedia, first installed recently?
  • Did you know that there's an an article on which Giano, Eric Corbett, Andy and I collaborated?
  • Did you know that there's another one by Nikkimaria, Tim riley and me?
  • Did you know that The Company of Heaven, Benjamin Britten's 1937 composition for speakers, soloists, choir and orchestra, contains "metrical spoken (shouted) male chorus"?
  • Did you know that Ben Gunn, imprisoned 32 years for killing a friend when he was 14, earned a Master of Arts degree in peace and reconciliation?

Let us continue collaboration with Andy.

  1. -- Gerda Arendt ( talk) 12:49, 28 August 2013 (UTC)
  2. -- Khazar2 ( talk) 13:40, 28 August 2013 (UTC)
  3. No. Since you mention my name, I will comment. I accepted an infobox (without question for its need, although I did question some of its dubious content [125]) on Holzhausenschlösschen because you, Gerda, were the major concerned editor [126](if I recall correctly, you posted on my talk-page requesting my input [127]). I respect your views on pages where you are a major content contributor - I never comment in these infobox disputes on pages where I feel my input has been non-existent or negligible. Unfortunately, Andy Mabbit does not reciprocate that view where his input is minimal. My solution of leaving these disputes to those writing and maintaining the pages is the obvious peaceable solution.  Giano  18:55, 28 August 2013 (UTC)

Comments and a suggestion from Harry Mitchell

Please forgive me if if this might have been better presented in he evidence or workshop stages; I missed those, mostly as I have limited access to the Internet at present, but also because I think the whole thing is a bit silly. However, after a heated conversation with a friend at the weekend, I wanted to offer a few thoughts. For the sake of transparency, I should declare that Andy Mabbett is a personal friend in real life and Nikkimaria is a fellow coordinator of the military history project whom I've worked with in the past and hold in very high esteem. I am less familiar with the other parties, but this seems to me not to be the typical arbitration case.

This isn't a political or nationalistic dispute spilling over onto Wikipedia (like Armenia/Azerbaijan, Israel/Palestine, etc, etc); it's a group of very intelligent and otherwise rational editors who have made immense contributions to this project but who seem to have lost the plot a bit. I actually intended to be quite scathing of several of the parties, but they have all presented themselves well in this case, made reasonable comments, and suggested that they are willing to sit down and discuss the issues with infoboxes like adults. They're not children who need disciplining, nor zealots who are incapable of putting the needs of the encyclopaedia above their own personal biases, so the optimist in me hopes that the discussions around infoboxes can continue without anybody (pro- or anti-infobox) having to be forcibly removed from the discussions or the project as a whole. What needs to end and what is totally unacceptable and unconducive to productive discussion is:

  • The snarkiness, sniping, sarcasm, condescension. Editors need to behave like adults and not resort to juvenile name-calling, or thinly veiled remarks about opponents' mental health, intelligence, etc.
  • Similarly, the contempt in which the parties hold each other (of which the above is a symptom). Folks need to wipe the slate clean and remember that we're all working to the same end. We're entitled to disagree on the route we take to that end (it's inevitable, and ArbCom should not seek to suppress honest disagreement), but no progress will be made through petty bickering.
  • The belligerence of the parties, the passive-aggressive behaviour, and the spoiling for fight. This includes the attempts to railroad infoboxes in by force and the continual hammering on the same door, which only heightens the bad feeling, intensifies the dispute, and only makes the anti-box parties dig their heels in even further. It also includes reverts with cryptic or inaccurate edit summaries, and any other behaviour which is intended to avoid or derail discussion.
  • Adding infoboxes to articles where previous contributors have opted to omit one (or removing long-standing infoboxes) without establishing a consensus on the article's talk page. The parties have all been around the block enough times to know that this causes more problems than it solves.
  • Attempts to undermine or demean opponents by manufacturing a divide between "content creators" and "others". The idea that there would be such a divide is anathema to the principles of Wikipedia, and, more importantly, it's a fallacy—many (most, even?) Wikipedians write articles and do other things. Defining oneself as belonging to one camp or the other in an attempt to belittle the other demeans every contributor to this project and serves no purpose towards addressing the resolving disagreements.
  • Flash mobs (whether recruited on-wiki or off, ie including but not limited to wikiprojects and ad-hoc groups of friends) turning up en masse as if to fight in a battle. Wikipedia is not a battleground, and editorial decisions are not made by volume of advocates, so attempting to drown out opponents with vast numbers of "me too" comments is unhelpful at best.

My suggestion would be to be liberal with the admonishments/reminders/cautions if ArbCom wants to be seen to be doing something, but really this is a content dispute. It can only be resolved through discussion. Perhaps once all the parties have had a dressing down for their various misdemeanours, they could attempt to work out their differences on a centralised talk page (for issues around infoboxes in general) and on article talk pages (for issues concerning infoboxes on a specific article). A small group of mediators (experienced editors who have or can earn the respect of both groups) could be appointed to keep order, and could be given the power to caution editors and then remove comments or ban them from a specific discussion or all infobox discussions if their comments continue to degrade the quality of the discussion. It won't resolve the questions about whether and where to use infoboxes (that's for editorial discussion), but it might improve the quality of the discussion. And if it doesn't, the case can be revisited in a few months with liberal application of bans for those who refuse to engage in civilised discussion. HJ Mitchell | Penny for your thoughts? 15:45, 27 August 2013 (UTC)

Amen.( olive ( talk) 16:26, 27 August 2013 (UTC))
  • Fine thoughts that we can all agree on, except that there is a distinction between content creators and others (I'm an other). Magnificent articles do not evolve from people like me correcting typos or adding factoids—someone with a deep understanding of the topic needs to devote large effort and energy in an act of creation that is fundamentally different from 100 passers-by adding a sentence each. In this case (where infoboxes are not mandatory, and where good arguments exist on both sides), the most collaborative approach is to employ the WP:ENGVAR idea of leaving an article the way it was built. Battling content creators is very unhelpful for the encyclopedia. Johnuniq ( talk) 00:49, 28 August 2013 (UTC)
    • I'm going to vehemently disagree with that, Johnuniq. Content creators who take so much pride in their work that they don't expect to have to argue the issues on equal footing with everyone else are best suited to non-wiki venues. I'm not even sure how feasible this kind of attitude would be, as not everyone who comes across such an article will be familiar with the special treatment these people are to be afforded. Shall we make a template that reads, "This page was created by a beloved content creator, so tough calls fall by default to them"? Equazcion (talk) 01:43, 28 Aug 2013 (UTC)
      • I don't see how that conclusion can be reached from my statement—of course ownership is wrong and needs to be stamped out if encountered. However, having a group of technical editors say that infoboxes are mother's milk is not sufficient reason for the group of editors who maintain an article to accept that an infobox is necessary. Apparently some third-parties view infoboxes as obviously desirable, and so regard the reversion of a new infobox as an ownership problem, but there is not even a guideline to support that view. Johnuniq ( talk) 02:29, 28 August 2013 (UTC)
          • This is an interesting discussion but - in my view - is mistaken at the premise. Show me one person who likes infoboxes who would say they are "necessary" ("mandatory")? I would say: helpful yes, necessary no. Look at The Rite of Spring (if you dare): Do you see "necessary"? "Why doesn't this article have an infobox?" - that was all, and two versions suggested. How is that "imposing an infobox" (a term I often read and don't understand, as I don't get how that would be "disruptive")? - The question is still open, btw, even if the discussion was closed. -- Gerda Arendt ( talk) 07:51, 28 August 2013 (UTC)
        • I'm not drawing any conclusions about who should win the infobox debate in those or any instances. But when people attempt to answer that question by drawing a distinction between how the opinions of "creators" should be regarded versus those of others, that is an ownership problem. Every article on Wikipedia is a collaboration between editors who all have varying levels of devotion to a topic, from gnome to wizard (or whatever the nomenclature is) -- none of which should dictate their level of control over the fate of articles. How much content an editor is responsible for in a given article should never enter into any debate as proof that their opinion should weigh more than anyone else's. It's always been one of the supreme challenges of the Wikipedia editor to vigilantly let go of those natural notions that creation entitles one to any modicum of control. That's just how this place works, like it or not. Those who can't accept that fact, or simply refuse to, don't get a pass to ignore it. Equazcion (talk) 02:33, 28 Aug 2013 (UTC)
          • Infobox are not compulsory, yet their persistent promotion has caused enormous disuption to a group of content creators—that's about the most damaging thing that can be done at Wikipedia. From frustration, perhaps someone has said that the views of content creators have primacy—that's incorrect, but hardly a hanging offense. If an infoboxes-cannot-be-removed policy is enacted, so be it, but meanwhile maximum benefit arises from defending content creators. Johnuniq ( talk) 03:30, 28 August 2013 (UTC)
            • "meanwhile maximum benefit arises from defending content creators" -- How so? Because we don't have an answer it's best to keep the peace by choosing someone to side with arbitrarily? Or if it's not arbitrary, is it that we need so urgently to keep content creators happy that we should ignore a basic tenet of Wikipedia? The need for content is not so dire that we should bend Wikipedia around those few content creators who seem less satisfied with the way things are actually supposed to work here. Equazcion (talk) 03:55, 28 Aug 2013 (UTC)
              • There is no consensus mandating infoboxes, and both sides have presented sound arguments. Are you suggesting that a good way to resolve the conflict would be to reject the views of those who maintain the article, in order to promote our basic tenets? Supporting content creators is not arbitrary—it is a choice that is likely to result in more good content being created. Johnuniq ( talk) 04:15, 28 August 2013 (UTC)
                • I've made no claims as to how the issue should be resolved, other than somewhere above where I suggested a community-wide RfC to start crafting an actual guideline on the topic. And as Olive below points out, all contributors should be supported equally. Supporting content creators over other editors so that more good content can come about is a tactic best left to independent publications. It has no place on Wikipedia. The ends do not justify the means here. Equazcion (talk) 04:32, 28 Aug 2013 (UTC)
                  • The issue should be resolved by both sides – and I make no apologies for stating that unfortunately there are "sides" – discussing the issues with an view to reaching an agreement, rather than aiming for a "win" for their views. Equazcion expresses some of the frustration I have found when I've seen an infobox reverted with the only reason given being that a particular project was not notified first. Nevertheless, the principal contributors to an article do have an advantage – they almost certainly understand the nuances of the subject better than others. What that means is that we should respect their expertise: they are in the best position to help decide on the content of an infobox. If someone who has guided an article through FAC tells me that key fact A is misleading because XYZ, then I make sure that fact A doesn't go in the infobox. That doesn't mean that their opinion of the value of metadata or accessibility, for example, is worth more than anybody else's. The so-called "content creators" (and I have written featured content, but I'm still unsure whether I'm counted as a content creator or not) are the best folks to improve content and curate it - and that includes the content of an infobox. The sad thing about all of this is that in one small area the very folks who would be of most value in making sure an infobox would improve an article are the ones who are so dead set against having any infoboxes in their walled garden that they have opposed them blindly. There is even an article on a composer which was promoted to FA with an infobox but five years later had the infobox removed (edit summary: "Removing infobox per Wikipedia:WikiProject Classical Music#Biographical infoboxes". The infobox had been there for five years and it was promoted with it - now please read the "discussion" on the talk page. The infobox was of course removed again and is still absent. Then in the next breath, we get told to defend the "content creators". What hypocrisy. -- RexxS ( talk) 12:29, 28 August 2013 (UTC)

Supporting Wikipedians is necessary whatever they do. Good is a subjective judgement. ( olive ( talk) 04:25, 28 August 2013 (UTC))

Unsupported finding /sanctions (Gerda)

This is "controversial"??? Given that many of the additions are from July 2 and are "current," and the other handful I checked show the boxes still there, obviously the boxes aren't very controversial. NE Ent 23:50, 27 August 2013 (UTC)

My infoboxes are very controversial, but the arbs possibly didn't find them. I presented them as evidence. The list also contains some "controversial" infoboxes by Andy, such as Russian Symphony Orchestra Society, Cathedral of Blessed Mother Teresa in Pristina, Reginald Aspinwall. I am interested in a broad participation of one case, to find out how we can reach consensus (or not) amicably and with respect, The Ban on Love, -- Gerda Arendt ( talk) 07:30, 28 August 2013 (UTC)

Infoboxes for discussion

I like the idea of "Infoboxes for discussion", rather like other contentious areas where opinions might be divided and progress is not being made, to have a venue where discussion can take place, and an uninvolved editor/admin makes the final decision. Might be worth folks having a discussion on the Village pump or a RfC page regarding if "Infoboxes for discussion" would be viable. SilkTork ✔Tea time 09:17, 28 August 2013 (UTC)

They are currently on Project QAI. I am willing to open a new subpage for centralized discussions if wanted, but the normal thing would be to go to the article's talk page. Don Carlos is open on QAI since it was deleted from the talk of Don Carlos with the edit summary " The talk page is not the place for an info box. - Typically an infobox is added and reverted, period. It would be a nice service if the one who cleans an article from an infobox would place it on the talk for discussion. Recent examples where I placed it on the talk are Cantata academica (infobox was added by me) and Russian Symphony Orchestra Society (infobox was added by Andy). In the latter case, discussed above, I didn't find an infobox in the article. I wonder if you will ;) -- Gerda Arendt ( talk) 09:55, 28 August 2013 (UTC)
I invite all the arbs to visit the current version of the RSOS article and look at the infobox there (n.b. not the image/ caption set in the top right), then to tell us here what they think of it, its accessibility and usability. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:45, 28 August 2013 (UTC)
- Question re "Editors reminded" section of PD - it says editors are reminded "to avoid turning discussions about a single article's infobox into a discussion about infoboxes in general." In that case, in my opinion "this article needs an infobox because it emits metadata (or wikimarkup, etc)" should never be accepted, or even introduced into discussions about a single article's infobox, is that what is intended? Can this be clarified in the final decision? Smeat75 ( talk) 12:47, 28 August 2013 (UTC)
As I see this "reminder", comments such as this [128] on the Don Carlos talk page, which have nothing to do with the specific article, should never appear again on single article talk pages, I wonder if the arbs agree that is the implication of this "reminder". Smeat75 ( talk) 13:28, 28 August 2013 (UTC)
No, you have it the wrong way round. Any article will benefit from emitting accurate metadata, so that needs to be considered in every case, just as every article benefits from having a quick overview summary of the key facts for the casual reader. It's nonsense like "the infobox is redundant" and "the information is already in the article" that needs to be stamped on strongly. It is obvious that the lead itself suffers from exactly those problems, but we still encourage editors to add leads to articles, because it improves them. Millions of Wikipedia articles benefit from having redundant information in their infoboxes, and there's nothing special about composers that makes their redundant information any smellier than other peoples' redundant information. Redundancy of information is not in itself a disadvantage to any article, but it sure makes a good target for those who don't have any real arguments to muster. -- RexxS ( talk) 15:13, 28 August 2013 (UTC)
This isn't the venue to discuss the merits of infoboxes, and even if it were, it's producing more heat than light. HJ Mitchell | Penny for your thoughts? 13:47, 29 August 2013 (UTC)
The following discussion has been closed. Please do not modify it.
That would indicate to me that nothing will change."Why will an infobox improve the article on Don Carlos", answer "Because it emits metadata" has nothing to do with Don Carlos. Smeat75 ( talk) 15:48, 28 August 2013 (UTC)
Indeed, Rex's frank statement (not his first) that he is implacable that there are never good reasons not to have an infobox for the vast majority of articles shows why this is unlikely to work. There is little point in a "X for discussion" set-up where there are entrenched views among a high proportion of the small minority interested. It just becomes a matter of stamina. Those interested in metadata need to find another, and better way of handling it, linking to the vast amount of work being done outside WP on standard vocabularies, digitizing standard sources with more authority than WP, and so on. Then metadata on WP would become an input and a positive benefit for WP, rather than an output, and a nuisance for us and a benefit for the likes of Google. Johnbod ( talk) 20:10, 28 August 2013 (UTC)
It doesn't have to be so radical or purely black and white. Non-infobox templates could emit the metadata just as well. Collapsible infoboxes that do emit the metadata seemed to gather quite a few votes among those traditionally opposed to them - it's the pro crowd that rejects them out of hand. Infoboxes could have a supplemental flag parameter that trigger a bot which copies to or updates wikidata entries then removes those flagged infoboxes from articles, avoiding recoding non-infoboxes that emit the same metadata - I'm quite sure again that people traditionally opposed to infoboxes for non-metadata related motives could live with 24 hours of infobox presence that gets removed. Or the bot could comment out the infobox once it has done its work, leaving it still present for updating purposes later on. Solutions abound. The willingness to compromise is what is lacking. MLauba ( Talk) 22:02, 28 August 2013 (UTC)
( edit conflict) That's the complete opposite of what I've said, John. I have never intimated "that are never good reasons not to have an infobox" for whatever set of articles you care to choose. I have consistently and patiently explained that there advantages and disadvantages and both need to be balanced when making decisions. See my evidence for starters. I do get rather sick of having words put into my mouth by those whose only goal is get rid of all infoboxes from Wikipedia for no other reason than not liking them. I do believe that an infobox would bring some advantages to Don Carlos: (i) it would provide a quick overview of key facts for the casual reader; (ii) it would enable outside data users to quickly and easily index those key facts about Don Carlos; (iii) it would help improve the accuracy of natural language processors which are trying to glean further information from the text of Don Carlos - which in turn helps spread our content beyond the traditional boundaries of paper encyclopedias. I also can see that having an infobox with wrong or misleading information in it would work against those goals; and I'm even able to accept the argument that so little information about a particular article is presentable as a key fact that an infobox would be a net disadvantage. But that's because I can see both sides of the argument and I'm willing to search for compromises. Your crew hasn't budged an inch with your ownership issues since before 2010 and if you carry on like that, of course you'll find nothing has changed. -- RexxS ( talk) 22:21, 28 August 2013 (UTC)
@ Mlauba: Have you written a "Non-infobox template" that "could emit the metadata just as well"? If you produce one that's as easy to edit and maintain as an infobox, I'll be happy to see it used where infoboxes are unwelcome. Until then though, I hope you'll allow me some skepticism of another pie-in-the-sky idea being thrown around as if it were fact. We usually call it "vapourware". As for infoboxes with collapsible sections, I'm lukewarm although I've created some as examples of the technique. They make life harder for anybody who can't use a mouse, and frankly, if the infobox is getting so big that some of its content needs to be hidden, I'd rather exclude that content from the infobox anyway. -- RexxS ( talk) 22:21, 28 August 2013 (UTC)
"By those whose only goal is get rid of all infoboxes from Wikipedia for no other reason than not liking them."—There is no such person. (One said, e.g., [129].) Your comment may have been said in anger, as we all over-generalize when angry, but such statements make me wonder what the point of ever "debating" or "trying to finding compromise" with you would be, when you misrepresent the situation that much. (Am I supposed to be one of the people who wants all infoboxes removed? Garbage. Hell, I've commented in four or five infobox debates in my life, all in the humanities area (humanities bios, art, lit). This is the main scope of the infobox problem, though it would be hard to tell from the presentation here.)
One tends to stop "debating" when all of one's positions are considered "refuted" by the strident infobox supporters a priori. (Here's a talk-page search of Andy Mabbett saying "refuted". All those top results are him. "Bogus / refuted / misleading / bogus ..."). This case happened because, in the history of the entire infobox debate on Wikipedia, people have questioned infoboxes on perhaps 50-100 specific article talk pages. There was a common factor to most of those cases, as this case has clearly shown. No person was ever present, in the numerous discussions I've seen, who suggested that all infoboxes should be deleted.
RexxS, you called someone a liar [130] and shamed me [131] higher up on this page. Observing that such is permissible, I'm going to stretch my wings and say to you: shame on you for lying (which is to say, knowingly misrepresenting the degree of infobox opposition). This bird has flown. Riggr Mortis ( talk) 23:44, 28 August 2013 (UTC)
Rubbish - there's a whole bunch of people who have never advanced more than the most fatuous of reasons for removing infoboxes - even you could see that if you took your blinkers off. Yes, I am angry, because I can see that all you've been doing here is playing a game to get rid of your principal opponent. There's been no attempt to look at ways of resolving the issues over infoboxes and all you've achieved is damage to the encyclopedia. You must be really proud of yourself. -- RexxS ( talk) 10:11, 29 August 2013 (UTC)
The latest version of an infobox for Don Carlos is here, because it was deleted on the talk of the opera. (Andy restored it there.) Note that it is a double, showing French and Italian version which have different names. For me (foreigner), that's much more obvious than any prose, - feel free to discuss there. -- Gerda Arendt ( talk) 22:35, 28 August 2013 (UTC)
@RexxS You can spare the condescending remarks, thanks all the same. The point is that there are several potential solutions that could dissociate metadata from the present infoboxes, whereas goodwill is manifestly lacking. Fully visible, present-state infoboxes as the sole emitter of metadata is not a permanent truth. It's a matter of convenience. Dissociation of metadata from full infoboxes could be a good way to give all sides what they want. It would also definitely separate both matters, which in reality is probably for the best. MLauba ( Talk) 22:41, 28 August 2013 (UTC)
Yes of course, it's fine to promise all these technological solutions when you haven't a clue about the problems of creating and maintaining them - not to mention the Luddites who will fight you tooth and nail before they'll let you make changes to the articles that they own. Anyway, if you ever look, you'll find that it's not just a matter of convenience, it's a matter of maintenance - or are you going to write a bot that keeps these invisible structures updated as well? It's ok to make promises relying on work from other volunteers as long as you don't have to do it yourself. And I'll tell you this: valuable as it is, metadata is only a minor reason for having infoboxes; the principal reason remains the value that they give to the casual reader who wants a quick fact, or the visitor who doesn't understand a lot of English but can still pick up some key concepts. So you're a very long way off the mark by thinking that stripping metadata from infoboxes would solve anything. The walled garden brigade would still be removing perfectly good infoboxes from their articles just because they don't like them. Or is that the only solution that acceptable to you? -- RexxS ( talk) 10:11, 29 August 2013 (UTC)
You seem intent to pick a fight with whoever doesn't share your absolutist world view. What you are amply demonstrating is that neither the pro-infobox nor the anti-infobox crowd are capable of envisioning a reality that doesn't conform to their narrow vision of what is possible and feasible. You think every single article should have an infobox? Go ahead, get a site-wide consensus to implement one. And lastly stop ascribing opinions to people when you have no idea what their opinion on infoboxes are. If the subject is so emotional to you that you are unable to maintain a semblance of decorum, a wikibreak might do you good. Voluntary or not. MLauba ( Talk) 10:26, 29 August 2013 (UTC)
( edit conflict) And you're pretty quick to leap to the ad hominems when somebody tells you something you find unpalatable. Address the comments, not the commentator. I'm quite happy to stand up for myself and for reason, and if you want to claim that's an intention to pick a fight, you'd better start finding some examples of where I've started it. If someone wants to debate sensibly, I'm more than willing to engage at that level. But when someone starts spouting drivel, I'm going to be telling them so. You know nothing about me, but you want to smear me with an "absolutist world view" - complete and utter bollocks. Have you read any of my evidence or contributions? Thought not. If you had, you'd see I have never suggested that every article should have an infobox, but have given examples of where I've agreed that an infobox is not an improvement - at least one of us understands that we have to debate pros and cons to reach a consensus. Read up on what a strawman is before you engage again. Folks like me have been willing to see both sides of the argument and look for compromise through reasoned discussion, but you come along and pontificate about technical solutions without any understanding of what is involved. I am very angry right now at the most one-sided decision that I've seen from ArbCom in the five years that I've followed them, so if you want to threaten me with a block, bring it on, and show us just how abusive an admin can be when involved in an argument. Why on earth we promote trigger-happy kids to a position where they can threaten other editors that disagree with them is beyond me. -- RexxS ( talk) 13:56, 29 August 2013 (UTC)

Unsupported finding /sanctions (Andy)

@ Carcharoth: asked for comments on the proposed findings.

My detractors have posted a carefully chosen selection of diffs and links to discussions, attempting to portray me and others who share some of my views in the most negative light they could. That is, of course, their right, and they would no doubt say I and others have done the same to them. This arena has, after all, evolved over the years into being an exceedingly adversarial process (the debate about whether and how to remedy that is for another time).

Unfortunately, those who drafted the proposed findings have drawn from these partisan examples some very broad brush conclusions, which others have taken on board at face value. For instance, there are already sufficient votes to pass the finding that my "contributions to discussions about the inclusion of infoboxes are generally unhelpful and tend to inflame the situation". I beg to disagree, and suggest that dispute only occurs in the narrow focus of this case; that is, in articles edited by members of the classical music projects and a small group of others who (for want of a better way of referring to them collectively) are those who see themselves as a "content creator" faction described by Harry. Most of my talk page edits regarding infoboxes were not mentioned in the evidence or workshop stages, because they did not seem relevant, but I believe I have a reputation among many editors for being helpful in that regard - at least, many ask for my advice or assistance, (and I recall being "thanked" in notifications, though I quickly turned that off as a distraction), and I am often engaged in unremarkable talk page discussions which result in undisputed improvements to templates, their content and the articles on which they sit. If Arbcom want it, I would be willing to collate evidence of this, but that would be both time consuming and voluminous.

Even in the discussion cited as evidence in that finding, I contend that my comments, while forceful, are not generally unhelpful. I also note that the finding ignores the comments to which I was subjected in those cited conversations, such as "I suggest you go away and finds a spot where your input is more welcome", "I would have expected you to have had more sense...", and so on.

There is also the contention that I "selectively choose what discussions I consider consensus". This later claim is evidenced solely to the linked discussion about {{ Geobox}}; where a TfD found "no consensus" for a merge proposal, and I have been painstaking to propose small, incremental changes in discussion on its talk page, those of related templates and interested editors, and with related projects Note that in that debate, Ruhrfisch, the cited editor who accuses me of ignoring consensus, said at the TfD "if you want to get rid of Geobox, then 1) fix the infoboxes so they can do everything Geobox can, and 2) make sure it is as easy as possible to convert from one to the other, then ask again"; which is exactly what have been doing (again, I can furnish diffs on request).

As a result of the above finding, there is a proposal, already with enough votes to pass, albeit slated for rewording, which would have me "indefinitely banned from adding or discussing the addition or removal of infoboxes" across all of Wikipedia. I have provided ample evidence, above, that the vast majority of my infobox additions are outside the area of this case as described, and are non-controversial. The project will drive no benefit from preventing them.

I have already indicated my willingness to further moderate my tone in discussions; and I am of course willing to take note of and abide by the "all parties reminded" findings recently suggested. If it is necessary for me to give an undertaking to avoid certain areas of Wikipedia involved in this case, then I shall of course do so. But, as Mackensen notes above in a currently-unanswered question, the evidence presented in this case does not support the findings and the proposed, extensive restriction on my editing or commenting, much less a site ban. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:40, 28 August 2013 (UTC)

I will reply later today as I am ultra busy in real life and for now refer people to my evidence on the Evidence page, which offers much more than Pigsonthewing mentions above. I also ask the ArbCom to decide if the proposed topic ban includes 1) "infoboxes" without the name "Infobox" (such as Geobox) and 2) editing Infoboxes in general (otherwise I foresee a can of worms). Ruhrfisch ><>°° 12:15, 28 August 2013 (UTC)
That does need clarification from the Arbs. As it passes now, the ban is on 'adding or discussing the addition or removal of infoboxs'. On the face of it, that does not include - altering the templates, adding/removing sections to them or nominating them for removal outright. Is this deliberate in order to allow Andy to continue to work on infoboxs? Or is it an oversight? Because I would refer to Ruhrfisch's evidence if its the former. Only in death does duty end ( talk) 13:11, 28 August 2013 (UTC)
As I said I have very little time today, so here to start are the pertinent sections of my evidence on Pigsonthewing's selective use of "consensus" (copied from the Evidence page):

"In my experience, Pigsonthewing seems to try to wear people down, arguing long after consensus against his position been reached. Despite his single-minded pursuit of his goals, he can be frustratingly inconsistent in his arguments. For example, his evidence (above) cites a no-consensus, nearly three-year-old RFC to support adding Microformats on WP. But when I pointed out six-month-old opposition to adding an Infobox at Talk:Rite of Spring, he basically dismissed it as "based on false claims" diff. He did not object to my citing numbers (6-1 against) then, and when I gave a tally/percentage (as is done at WP:RfA) of those opposed to an Infobox in the article (myself included) and those in favor diff, he wrote "So we are making progress!" diff. However when Gerda abstained, I recalculated the tally, and Pigsonthewing called my actions "asinine" and accused me of "rig[ging] the figures in your favour" diff."

"Pigsonthewing is also out to delete Template:Geobox despite "no consensus to merge" (with Infoboxes) on his TfD. He then tried to delete the Geobox piecemeal, starting with the Mountains and Mountain ranges functions here, and here. Next he turned to Geobox|River, by proposing it be "deprecated" at Template talk:Infobox river (and no notice from him on Geobox talk)."

I also note that I later told Pigsonthewing that I had changed my mind on replacing Geobox, but he didn't quote that and I have no time to dig it up now. I will comment more later, no time now. Ruhrfisch ><>°° 19:08, 28 August 2013 (UTC)

My reply to Pigsonthewing is at Template_talk:Infobox_river#Geobox.2C_again and reads in part ". I have changed my mind (especially as I would have to do the work of updating the river articles I am the chief contributor to if this comes to pass). Wikipedia allows editors fairly wide leeway on how they do many different things here (please see WP:IAR). One example is that there are at least three different ways to cite references (with many similar but not identical templates). Are you going to "unify" those too?"
There are over 20,000 articles which use Geobox River - I know how long it took me to convert when the current version of the Geobox was introduced ( diff) and assume conversion to Infobox River would be at least as time consuming. Even if it took only 1 minute per conversion, that would be about two weeks of work to convert all 20,000 plus Geobox River articles. Nor did Pigsonthewing bother to notify the users of Geobox River about his plan to deprecate that version of the Geobox.
In addition, please note that both {{ Infobox mountain}} nor {{ Infobox mountain range}} still CANNOT do everything that Geobox Mountain and Geobox mountain range did (i.e. Geobox mountain had parameters on the geology and geological period and who made the first ascent) [132]. So much for my request that they first "fix the infoboxes so they can do everything Geobox can" and Pigsonthewings claim that this "is exactly what have been doing" sic. Ruhrfisch ><>°° 03:13, 30 August 2013 (UTC)
I (Ruhrfisch) close by quoting Finetooth at the Infobox River discussion "Andy, the issue that concerns me here is editorial control, which should never be ceded to a subset of the whole collective. By consensus, the collective has already rejected your proposal to eliminate geoboxes entirely. Your proposal to deprecate geoboxes is essentially the same proposal. The English Wikipedia and the Commons are parts of a commons managed collectively; anyone, including Google, may reuse the product (encyclopedia articles, data, images) under the terms of the GFDL and other licenses and may participate in seeking changes to existing policies and guidelines. However, participating in policy discussions is not the same as setting policy. That power should remain in the hands of the collective, which has already spoken on this matter. ... "
Ruhrfisch ><>°° 03:22, 30 August 2013 (UTC)

@ Rhurficsh: so because one infobox is suboptimal then all infoboxes are bad and anyone who promotes them needs to be banned? According to my understanding of the way wikis work, an infobox being suboptimal is simply a reason to fix that infobox. If you can't do it yourself you should explain to someone who can what needs fixing, if they don't understand what needs fixing or why then you need to have a civil discussion until you understand each other and come to an agreement. Thryduulf ( talk) 13:02, 30 August 2013 (UTC)

Hi Thryduulf, by no means is that what I was trying to say, sorry to be unclear. Pigsonthewing mentioned me and my evidence, so I tried to clarify. To beat the proverbial dead horse, Geobox was nominated for deletion (by Pigsonthewing), but that TfD was closed as no consensus to merge with the appropriate Infoboxes. Despite that clear consensus, Pigsonthewing succeeded in deprecating the mountain and mountain range functions of Geobox, and tried to do the same for the River function (in the latter case not even bothering to post a notice on the Geobox talk page for a proposal that would wipe out over 20,000 uses of the Geobox had it passed). My problem with Pigsonthewing has everything to do with his repeated bad behavior, and only involves Infoboxes (and Geoboxes) because that is where most of our interactions have taken place.
Just to be clear, I am not "anti-infobox". If you look at the 28 articles I helped bring to FA, about 90% have some sort of box (though I suspect most of those are Geoboxes). In most cases, a box is OK by me, but there are some like Waterfalls in Ricketts Glen State Park or the 3 FLs I have been a co-nom on at FLC that either have no box, or where a box would not add anything useful. To me it is an editorial decision, just like which photos best illustrate an article and what level of detail to go into on different topics. And, for the record, I did support improving Infobox River (see further down its talk page), I just choose not to use it in stream articles I write (and as RexxS can tell you, I can't code templates). Ruhrfisch ><>°° 16:00, 30 August 2013 (UTC)

Silly remedy

"All editors are reminded to maintain decorum and civility when engaged in discussions about infoboxes, ..."

  • So when the case is closed, are the clerks going to put a notice on every editor's talk page?
  • Shouldn't editors maintain decorum and civility when engaged in discussions about ... anything?

While I respect the committee's willingness to settle the issues no one else wants to actually figure out, I've never figured out how vague sweeping remedies like this are intended to improve WP? NE Ent 02:15, 29 August 2013 (UTC)

It's really not so silly. One purpose enshrined in such General Purpose Criterion is its effect on future incarnations of "behavior"; impossible to list for being unknown, and for such GPC, unnecessary. :)  John Cline ( talk) 02:30, 29 August 2013 (UTC)
So what's equivalent to Chemical weapons, committee decisions or haggling over infoboxes??? NE Ent 21:58, 30 August 2013 (UTC)
It's a concept, is all. :)  John Cline ( talk) 22:04, 30 August 2013 (UTC)
NE Ent, that remedy originally referred to the parties to the case, rather than editors in general. The change was made here. See also the comments made by arbs. Strictly speaking, the remedy should refer to editors who participated in this case who would reasonably have read that remedy. It's a warning for people who participated here to keep calm as their conduct will likely be judged more harshly than others if a future case is needed if things flare up again. Though hopefully that won't happen. Your point about how editors in general should maintain decorum in discussions about anything, not just infoboxes, is well made. The wording could be tweaked (e.g. "All editors engaged in discussions about infoboxes are reminded to maintain decorum and civility"), but the current wording is unlikely to be misunderstood. Carcharoth ( talk) 00:25, 31 August 2013 (UTC)

Perspective from Kleinzach

A cluster of issues — personal, publishing-related and technical, (if not philosophical) — are involved in the infobox question. Confusing these issues has made it difficult, if not impossible, to resolve them.

Unfortunately I think the lack of structure and preparation for this ArbCom case (as freely admitted by the initiator), has doomed it to the repetition of old arguments, limiting the prospect of positive outcomes. (If only the energy that has gone into this case could be recycled in the actual encyclopedia! Perhaps we could even start reversing the decline of Wikipedia!)

I’d like to make some quick points:

1. Personal disputes have been discussed in detail. It should be simple enough to determine who has been edit warring and sanction them accordingly. Sanctions should be proportionate. They should be based on how users behave, not on how they think.

2. The ‘publishing issue' — of how to coordinate ancillary material with main text — is important for all encyclopedias, on and offline. This could be usefully discussed in separation from general and technical matters. AFAIK no one is advocating putting wrong information in infoboxes, so there is no reason for a dispute on this aspect of the box question.

3. Technical issues have not been adequately opened up for discussion. We need to look at how the boxes are structured within pages, and used to extract what data, for what purpose. Assumptions have been made by both sides (pro-box and box-sceptic) without any real examination of how the boxes should be coded and applied. In the future, improved, better-linked infoboxes (‘smart boxes’) may obviate some of the present difficulties and help address GIGO concerns (e.g. boxed information missing from articles might be highlighted etc. etc.) I think we should be looking in this direction.

(I’ve been travelling during the last couple of months. I haven’t had time to read all the submissions above and on other pages. I'm only taking this opportunity to make these brief comments because the page has been left open (past its expiry date?). I'm not intending to add anything later. )

Klein zach 08:11, 29 August 2013 (UTC)

This is a talk page for discussing the proposed decision. It will remain open at least until a decision is finalised.
The personal dispute problems are not a matter of edit warring, so more nuanced remedies are required.
The publishing issue really does need to be discussed outside of this case. I wish you luck with it.
It is pretty obvious nobody will advocate putting wrong information into infoboxes, but you seem to have conveniently forgotten those who have complained about other people putting wrong information into infoboxes. (It's always other people, right?) To refresh your memory, here are a few snippets of those complaints:
  • "if boxes are a possibility, no matter which ones are out there, I expect that editors who think everything from plainchant to Mahler's "Resurrection" Sym. is a "song" will persist in afflicting us with The Wrong Box, and, if history is any guide, will then get upset and combattively launch new discussions like this one when others remove them"
  • "editors will continue to use inappropriate boxes or even create a composer/musician box themselves without consulting us."
  • "First, look at the existing article on genre, to which the box gives a link and to which an ingenu might be expected to refer. It's an utter dog's breakfast. (And don't advise me please to rewrite it if it upsets me so, I have other things in life to do). Then let me take issue, as I think many others would, as to ecosaisses etc. being considered as genres. If he has a genre, it's perhaps 'early romantic pianism', but don't quote me on that, I am sure many will disagree."
  • "if the exact same description appears in the lede, then why is there a problem with having it in the infobox? Infoboxes and ledes can and should be edited if a summary description is problematic or wrong for a particular composer."
  • "the project's issue you raise above is not quite right - the primary concern has always been inaccuracy not duplication"
  • "Liszt might get a litle hairy, too: many people assume his was a priest but he only took minor orders, hence he was called 'Abbé Liszt'"
And so on. But those are all from Wikipedia talk:WikiProject Composers/Infoboxes RfC, so you may have forgotten them.
I've spent more than my fair share of time explaining how boxes are structured, and used to extract data, and for what purposes. I have studiously examined how the boxes are and should be coded. I am perfectly willing to repeat any explanations that you feel remain unclear to you. I have over the last few days coded a mechanism for retrieving information from Wikidata into a Wikipedia page ( Module:Wikidata) so that all language wikis can make use of the data from a central repository. So I find it somewhat insulting to be told that I have been making assumptions without any real examination. Some of us have actually been looking forward for a very long time now. -- RexxS ( talk) 10:50, 29 August 2013 (UTC)
Point number 3 is quite true, but it is really not within our scope. We can try to pass a remedy that leads to a binding discussion on it, but the structure is probably not even there for that yet. NW ( Talk) 11:45, 29 August 2013 (UTC)
I generally agree with Kleinzach. More discussion is needed on various issues. The most useful thing ArbCom can do (in my opinion) is set the stage for those discussions, and then sanction anybody who prevents those discussions from progressing. There's nothing wrong with two groups of editors disagreeing or even having a dispute; the problem comes when—through gamesmanship, loss of temper, bad attitude or anything else—people prevent the dispute from being resolved. Forcibly removing people from the discussions at this stage only guarantees that the dispute will continue—perhaps more quietly for a while, but eventually it will come back to haunt all of us. HJ Mitchell | Penny for your thoughts? 14:10, 29 August 2013 (UTC)

Clarification of the 'publishing issue'

It’s been pointed out that my Point 2 (The ‘publishing issue’ above) needs clarification. When I wrote “AFAIK no one is advocating putting wrong information in infoboxes, so there is no reason for a dispute on this aspect of the box question.” I was thinking this issue could be usefully separated from the general debate, and examined objectively and in detail by editors with a view to writing some rigorous guidelines (for an improved and expanded MOS:Infobox).

The ‘publishing, or copy-editing issue’ is about consistence, clarity and coherence, relevance, appropriateness, balance, and presentation, including things like: 1. position of infoboxes within articles, 2. size/text length of infoboxes in absolute/relative terms, 3. box/lead content relationship, 4. box/article content relationship, 5. collapsed or non-appearing fields and field names, 6. appearing field name rules, 7. linking and referencing within boxes, 8. rules on avoiding anachronism, 9. material exclusive to the box (i.e. not in the article), 10. illustrations, 11. use of technical, scientific and foreign languages, abbreviations etc. etc.

The ‘Proposed decision’ states “All editors are reminded . . . to avoid turning discussions about a single article's infobox into a discussion about infoboxes in general.” If centralized discussions of key aspects of “infoboxes in general” have never taken place, then that avoidance will be difficult, if not impossible, to achieve. Klein zach 07:03, 3 September 2013 (UTC)

Thoughts from Quiddity

My thoughts echo a variety of users above (HJ Mitchell and Kleinzach in particular). I sent a variant of this message to arbcom-l, but it was deemed inappropriate for private evidence, so I'm going to post an edited version here.

The current proposed decision is not going to solve the underlying dispute, and is not going to move the community towards solving it ourselves.

As Ched said, "We need leadership".

I would suggest that what we specifically need is: a simple question and answer session - i.e. Someone good at mediating (not just someone enthusiastic about trying to help), reads until they understand the entire issue, and then asks smart questions, and the editors acting-on-best-behaviour *actually answer*, rather than tangenting or sniping - which is what often happens when direct/uncomfortable/backed-into-a-corner questions are asked.

This might also, perhaps even mostly, involve asking editors privately, in order to keep the dialogue unhurried/calm/unreserved/honest/etc. This is why we need someone utterly trustworthy to lead it.

Relatedly, a public RfC will almost certainly not help matters - it will devolve into argument, and !vote counting - we already know all of the issues, we just need to determine whether solving them will actually help.

(Note: The only item I purposefully left out of my "Legitimate problems" list (in Evidence), is the issue of "distraction" - I suspect that this is one of the major reasons that some editors are infobox-skeptics; not wanting anyone to be tempted-away-from reading the hard-worked-upon entire introduction/article - this is a hot-button issue (some editors previously mockingly referred to it as teh Brilliant Prose), and I don't raise it willingly, but it does need to be out in the open.)

Therefore, We need to know:

  • Would an aesthetic redesign/tweaks help?
  • Would reinforcing the template-documentation help?
  • Would anything help?

This is what we need to know, if we want to prevent an eternal-stalemate, and/or individual argumentsdiscussions at the thousands of articles where anyone might object to the inclusion of an infobox.

This is what I was trying to get at, with my Evidence and Workshop suggestions. I'd hoped that arbcom members would simply ask those questions on these talkpages; or in private, amongst themselves, and to the editors; and perhaps the latter is still possible.

I've tried hard to limit the extra content that I oblige arbcom to read, and I will endeavour to not discuss it further here (and I hope nobody replies at length), but I hope this last post helps. – Quiddity ( talk) 03:27, 30 August 2013 (UTC)

I very much doubt that the wider issues are known by everyone: one of the arbs (NW I think) remarked that until July they were unaware infoboxes were an issue, and equally I'm sure that most of the editors who do the normally useful work of adding infoboxes to articles without them are unaware both of the hostility to them in some cases (until they run into it) and also of the "metadata agenda" that drives some of the editors here. The core issue for the infobox sceptics is accuracy - I think I coined "misinfobox" some years ago, which User:Wetman and some others used too (also "disinfobox"). There are things that would help in a small way, but really the way forward has to be to treat metadata separately and more seriously, and as an input rather than an output (see above). I don't think a private mediation that involves choosing whether the online encyclopedia or the metadata output is more important will attract community support. Johnbod ( talk) 11:22, 30 August 2013 (UTC)
"Online encyclopaedia" vs "metadata" is not a helpful thing to be saying, because they are not in the slightest way opposites. The relevant question is "Do we want an online encyclopaedia or an online encyclopaedia?" Thryduulf ( talk) 12:56, 30 August 2013 (UTC)
John, is there any reason why you and Andy (and everyone else with strong feelings on infoboxes) can't sit down and have a rational discussion about these issues with a neural third party moderating the discussion to keep it constructive and on-topic? From where I'm sitting, there are good arguments for and against infoboxes, and you're all intelligent enough to reach a solution, if only both sides would stop bickering and engage in serious, level-headed discussion. HJ Mitchell | Penny for your thoughts? 14:55, 30 August 2013 (UTC)
@ Thryduulf, Rexx's comment above about: "...Andy's desire to see Wikipedia evolve into a resource that is usable in far more ways than simply reading an encyclopedia - I have the Encyclopedia Brittanica on my bookshelves if that's all I want to do" shows a fundamentally different attitude to the project to that of most Wikipedians, I would suggest.
@ Harry - surely that is what the various case pages have been doing for most of the time? It has I think produced considerable elucidation of the issues, and will be educative for any outsider with the patience to read it, but I see little sign of "a solution" emerging. I notice that Rexx, who began the discussions saying discussion would solve everything (if only the other side would stop using "bogus" arguments), has rather changed his tune, as on your talk recently. Johnbod ( talk) 15:43, 30 August 2013 (UTC)
We are not a paper encyclopaedia. If you want to remove all metadata you need to remove all page history, all categories, all page titles and headings, many (if not all) redirects, many templates, most (if not all) tables, etc. All of these either are metadata or produce metadata by virtue of their existence. Metadata and human readable information are not exclusive, indeed far from it. There is no diachotemy between improving the encyclopaedia for human readers of the Wikipedia website and improving the encyclopaedia for those using our content in other contexts. Thryduulf ( talk) 16:11, 30 August 2013 (UTC)
Straw man. Who is proposing that? Nobody. Johnbod ( talk) 16:18, 30 August 2013 (UTC)
    Yes (to "straw man"). Thryduulf, your posts above conflate issues in a rather scary way. You've conflated metadata and data. You stated that to have concerns about the "data emission" agenda is to oppose "metadata", meaning we must delete page histories, etc. Do I need to point out how absurd this contention is? I fear I might, which is why I will spend some time on this post and attempt to tie it back to our original joint statement.
    Thryduulf has given some examples of what " metadata" actually is: it is data about data, in the common definition. The "metadata of a Wikipedia article" would include its size in bytes, its article assessments, and some of the things Thryduulf mentions, like page history. "Metadata" and "data" are different concepts, and you've given evidence that it might be generally useful to clarify this. Someone involved with the "metadata emission" project must have adopted the term " metadata" in a loose sense to refer to data about the article subject that is encapsulated in various ways using HTML attributes. This emission happens most conveniently by wrapping a template around a date or other atomic data point which makes the system output a bit of extra information in HTML source; in turn giving computer programmers more confidence that they are retrieving what they want to retrieve.
    When we speak of "metadata emission" in the sense that its most ardent supporters use the term, we're speaking of "data" about the article subject. Those supporters appear to have originated the use of the term "metadata" for these data emission things they do, and for better or worse we've adopted the term in discussion so that, at least in a local sense, there is an understanding that we're referring to the same thing. But the extra syllables do make it sound more important, I suppose. In short: page history is metadata and (really!!) no one ones to delete the page history. On the other hand, an example of "metadata emission" goes like this: "{{Birthdate|1940}}". That template wraps one piece of article subject data (inside an infobox template) so that a computer can read the data by recognizing HTML code like "<span class="bday">1940</span>". The "1940", the article content, would be in the HTML source either way; the wrapper is meant to help computer programmers. It is easy to imagine every computer programmer saying "yes, that's great!", but they're not the ones who have to measure the goal against its costs. They're not the ones considering project scope. Adding that wrapper to every "data point" in the encyclopedia is no small feat and quite obviously encompasses the creation of a large template infrastructure, plus millions of edits, that some people might consider beyond the scope of the Wikipedia project. When those edits are largely the work of someone who engenders conflict, trouble's a-brew.
    I would suggest that in favour of a "debate" about "[meta]data", the community realize that the entire project of Wikidata was set up to accomplish this task. No, not in exactly the same way as its main supporters have implemented it here—but ultimately in a much better, scalable, computer-friendly way. (It's even multi-lingual, meaning no need to repeat this "data emission" project on each Wikipedia.) Two expected counter-arguments: 1) "The technical means differ." That doesn't matter; to argue that is only to suggest that you are more concerned with the implementation methods you've chosen than the conceptual goal (semantic web, parseable data). Which would suggest an underlying motivation for implementing it all a certain way on Wikipedia. 2) "Wikidata can't accomplish x yet." That would be a reason to help on Wikidata, including in development, and not a reason to continue the build-out of the infrastructure here. We now have a sister project designed to accomplish the equivalent of the "data emission" goal on Wikipedia. The work belongs there, would be welcomed there.
    I justify the length of this post on an arbcom talk page as follows: 1) I hope it may help clarify some concepts and their relations for some arbcom members. 2) I hope it may shed light on our original joint post, by showing in a bit more detail how large and encompassing the infobox agenda is here—how intertwined it is with related concepts (by the primary advocate's design, I mean)—and how easy it will be for the agenda's primary and most active advocate—the one with documented repeated issues of engendering conflict—to just move on to a slightly different area of the "build-out" if topic-banned from only one piece of the puzzle. Riggr Mortis ( talk) 22:54, 30 August 2013 (UTC)
I was hoping that I had finished posting here, but as Riggr Mortis has decided to prolong the discussion, I suppose I might as well add the information he leaves out. There is a standard defined for emitting data in that the names of the data-wrapping classes are standardised. When the template outputs "<span class="bday dtstart published updated>1940</span>" each of those class names is the same as for data similarly encapsulated on thousands of other websites, so that common agents can 'understand' it as perhaps a birthday if it's inside a " hCard" microformat, or perhaps as a date of publication if inside a " hAudio" microformat, and so on. The classes are not only common across websites, but are designed to exist inside a container that gives context - a person, an event, a piece of music, etc. That's one of the reasons why {{ Persondata}} falls short: neither the container, nor the items inside are assigned standard classnames, so they remain invisible to the readers that can read the information inside our infoboxes or their equivalent on other websites.
It would be nice to think that one day every data point in Wikipedia could have a descriptive name (for example a date is marked as a birthday, not just any old date). Adding meaning to content is part of Berners-Lee's vision of building a semantic web and it's something that most people who think about it would see as a "good thing™". But the point about cost is well-made, and on a crowd-sourced site, it is not feasible to expect every contributor to mark up data meaningfully. All is not lost, though; on a crowd-sourced site we should be able to allow other editors with the skills to apply the semantic markup. If they're really clever, they mark it up in such a way that future editors don't have to see the internals - and so that's why we use templates to hide the scary bits. It's also the reason why I find it so annoying when somebody tells me that marking data with microformats doesn't add value to an article. And at the present moment, we only have infoboxes to do that, so it's even more annoying when I'm told there's lots of other ways of doing it. Yes I know that, but at present none of them work.
I would wondering when somebody would raise the issue of Wikidata in an attempt to tell us that we can offload all our data emission to there. I've actually been working over there so I know a bit about it, and I've just spent my most of final contributions here on creating a means of importing Wikidata back into a Wikipedia with full local control, in the hope that somebody in the future will find that useful. But I digress; what I should be telling you is where Wikidata gets its data from. Did you guess? - it gets it from infoboxes. I'm not kidding you. That's where the vast majority of data comes from because a bot can import it fairly automatically and accurately - did I mention that infoboxes also have the advantage of very regularly structured data as well? The downside is that the collection is patchy. I was doing some testing a few days ago and found that Wikidata thought that Richard Burton was born in Wales (hint: there is actually a place called Pontrhydyfen) and only had two wives, one of whom was also one of his childen - they must have confused him with some other actor. I corrected the error manually, but was unable to add three of his four children as they didn't have articles. So Wikidata has a long way to go before it's anywhere near as useful, flexible or accurate as our infoboxes. And if you think the the cost of infoboxes isn't negligible, you'll have a fit about the cost of cleaning the data in Wikidata that you're proposing as a replacement. One day maybe, but that day is not today.
And that's it from me. Goodbye and good luck. -- RexxS ( talk) 00:10, 31 August 2013 (UTC)
I dont known know Rexx, but perhalps if you had used less agressive stalking horses. I know I'm one to talk, but I was only ever provoked, I never wandered out and said "this is the way it should be, if you disagree, I'll have people who will, over years and months, grind you down". Ceoil ( talk) 00:45, 31 August 2013 (UTC)

Implementation Notes

Why do the implementation notes say that 1.2 "cannot pass" and that "1.1 is passing instead"? The maths seem to allow it to pass with one more vote which hasn't been cast yet, and at least two arbitrators explicitly say in their votes that the two are not alternative to one another 92.39.207.86 ( talk) 22:05, 31 August 2013 (UTC)

Only one of those can pass. Actually the second Locus of dispute principle was presented as an alternative to the first one. — ΛΧΣ 21 22:13, 31 August 2013 (UTC)
Thanks, I've misread it horribly - I think it's having more than one row numbered 1.1 that's confused me - why do that? In some ways I suppose it's not as bad as having four 5s, two of them adjacent in the same section. And likewise three 6s, two of them adjacent. But at least there aren't any notes mentioning 5 or 6 by number. 92.39.207.86 ( talk) 22:21, 31 August 2013 (UTC)
Oh I see. I should have written "Finding of fact #1 cannot pass." instead of just "Cannot pass". Let me fix it. — ΛΧΣ 21 22:46, 31 August 2013 (UTC)

Uninvolved user, late to this discussion

Premise 1: I hope we agree that Wikipedia's mission and values make no distinction between first- and second-class readers. We bring free knowledge to the widest possible audience, without discrimination.

Premise 2: I hope we agree that Wikipedia is non-paternalistic; that it does not decide for the readers how they should use information. This is reflected in the policy against censorship, in the provision of an open API so developers can make new ways of viewing and interacting with Wikipedia, and in the licensing which allows adaptation and reuse by anyone, for any purpose.

Premise 3: As a consequence of (2), a lot of the access to Wikipedia's free and open knowledge is via DBpedia and similar harvesting projects, which in turn feed sites such as the BBC. I hope everyone here is familiar with DBpedia's prime importance in the web of Linked Open Data.

Premise 4: People who remove an infobox (or other semantic markup) from an article are, in effect, deleting a page of information. They are not deleting it from Wikipedia itself, but from DBpedia, Google, the BBC, or many other sites and apps

However, as per premise #1 those audiences are no less valid readers of Wikipedia than those that come to the site. They are no less entitled to benefit from free and open knowledge. We're not like commercial web sites where it's all about getting "eyeballs" on your site rather than "competitor" sites: that commercial mentality does not belong here. This isn't a matter of subjective preference: it's core to Wikipedia having a distinctive mission as a free and open encyclopaedia.

So I've come late to this discussion and a lot of what I see is very worrying. Andy Mabbett's statements about making data reusable and accessible are cited against him as evidence of a harmful agenda, rather than of him advancing the Wikimedia mission. The fact that we enable for-profit companies to harvest metadata is cited as if it were against Wikipedia's mission, rather than fulfilling it. I see "the reader" of Wikipedia being defined as those that come to the site, bluntly denying both Wikipedia's mission and licensing (as made clear by RexxS) and the way the Web has evolved over the years.

Whether or not we make information and knowledge open and free, removing barriers so that the greatest audience can participate in it, is not a matter of personal preference. It's not something to be weighed against the aesthetics of how particular users view Wikipedia. It's definitely not something that has yet to be worked out by community discussion. For Wikipedia, it has already been decided. There are clearly vocal users that disagree, but they have a huge uphill struggle if they want to change Wikimedia's mission to fit their preference, and in fairness they need to warn all contributors that "Wikipedia is about knowledge that anyone may freely use for any purpose, with these exceptions..." MartinPoulter ( talk) 10:54, 1 September 2013 (UTC)

Given such confidence that the pro-infobox case is obviously correct, why not propose that a policy prohibiting the removal of infoboxes? The problem with this case is that infobox enthusiasts have not taken a policy approach, possibly expecting that adding infoboxes would become de facto policy after wearing down a few obstacles. Further, the arguments are rather more subtle than assumed in the above. Johnuniq ( talk) 12:18, 1 September 2013 (UTC)
Indeed. Based on MartinPoulter perspicuous reading, those who object to the inclusion of infoboxes are ruining it for everybody; hence, the case for making their inclusion a matter of fundamental policy (up there with RS and V) should be straightforward, compelling and unstoppable. Eusebeus ( talk) 14:24, 1 September 2013 (UTC)
There are good grounds for removing infoboxes, if they contain only wrong or misleading information. I edit mainly in the area of psychology, and I don't think many psychological articles merit infoboxes. So you're both hacking at a straw man. On the other hand, there aren't good grounds for treating the increased availability of free and open knowledge (one form of which is putting information in semantic formats) as an agenda to be resisted on Wikipedia. As to "[T]he arguments are rather more subtle." Why? What are they? As I said, I think the key decision has already been taken and it's the anti-semantic users who want to change the status quo. MartinPoulter ( talk) 10:25, 2 September 2013 (UTC)
Why? What are they? It's not helpful to post summations to write off good editors (very good editors) in a complex case without studying the background. This case is about the consequences for the encyclopedia of a battle—it's not about whether infoboxes are good or bad. The only fact concerning infoboxes of any relevance to this case is that infoboxes are not mandatory. Johnuniq ( talk) 00:11, 3 September 2013 (UTC)

This is not the venue for discussing the rights and wrongs of infoboxes. This is the venue to discuss the way the Committee is dealing with conduct issues arising from those who have been battling over infoboxes. There have been several suggestions made by various people (including a formal one by the Committee) that discussions on various aspects of infoboxes should be held. Hopefully at some point people will start doing that at a more appropriate venue than this one, so a broad range of views can be heard. SilkTork ✔Tea time 14:34, 3 September 2013 (UTC)

The problem that I see is that much of "conduct" was caused by the lack of agreement about infoboxes and who decides in which article they go, causing conflict that would not exist otherwise. (Example: if there was a guideline about infobox in a book article, a traumatic discussion on Pilgrim at Tinker Creek - 2012 and remembered - would not have happened.) - I will bore you but suggest: be easy on conduct of the past, especially of years ago, and work in respect for each other, starting today. -- Gerda Arendt ( talk) 14:51, 3 September 2013 (UTC)

Proposed remedy 1.1

Several of the arbitrators have expressed a desire for remedy 1.1 to be fine-tuned, particularly those who see it as an alternative to 1.2. For my part, I see that remedy as an excellent opportunity to determine whether Andy should be site-banned or not. If his behavior is restricted and things run along okay, then we need not go further. Finding of fact 4 identified Andy's engagement on article talk pages, usually right after an infobox had been added or removed, as problematic. I haven't seen any suggestion that there's a problem in the template namespace itself. If I were tasked with enforcing that remedy I'd understand it, even as written now, to be restricted to the article and talk namespaces, but that may not be clear enough. I'm thinking giving uninvolved administrators (perhaps designated beforehand) the power to ban Andy from a talk page might work, though that would mean specifying unacceptable behavior. The remedy as written though would even prevent Andy from adding an infobox to an article he creates. Sometimes arbitration rulings have perverse outcomes; the committee should probably acknowledge that issue upfront if there's no way to avoid it now. I suppose you could try this:

"Pigsonthewing is indefinitely banned from adding or discussing the addition or removal of infoboxes on articles where he is not already a major contributor."

Open to interpretation and I'm a little uncomfortable with a remedy that more or less endorses WP:OWN. You could also add in the implementation notes "Administrators, don't be stupid when enforcing this" but I don't know if that would work. You might also want to consider a sunset clause or opportunity for appeal, such as was found in 1.2. All bans area appealable of course, but it's best to state these things openly. Mackensen (talk) 15:03, 1 September 2013 (UTC)

Alternatively, on re-reading the decision, the remedy for rejected for several others might represent the desired tailoring:

"Pigsonthewing is indefinitely restricted from: adding or deleting infoboxes; restoring an infobox that has been deleted; or making more than two comments in discussing the inclusion or exclusion of an infobox on a given article. They may participate in wider policy discussions regarding infoboxes with no restriction."

That remedy would have essentially the same effect as the current one, but with a tiny amount of give which hopefully prevents misunderstandings. Mackensen (talk) 15:17, 1 September 2013 (UTC)

For the first bit, how about: ""Pigsonthewing is indefinitely restricted from: adding infoboxes to established articles or deleting infoboxes..." If a definition of "established" is needed, then "articles in existence (under any title) for over one year that are not classed as stubs" should do. I don't think anyone wants to prevent him adding boxes to general articles of types that normally have them, and given he can't restore any reversion, I hope everyone will be happy with this. Do we need to prevent him from "deleting infoboxes" actually? No-one has complained about him doing this.... Why is he "they" at the end? Redrafted whole thing:
  • "Pigsonthewing is indefinitely restricted from: adding infoboxes to established articles (defined as articles in existence under any title for over one year that are not classed as stubs); restoring an infobox that has been deleted; or making more than two comments in discussing the inclusion or exclusion of an infobox on any given article. He may participate in wider policy discussions regarding infoboxes with no restriction." Johnbod ( talk) 15:36, 1 September 2013 (UTC)
    • Per my earlier comments at #Limited number of comments in discussions I think that restricting the number of comments one person can make in a discussion will have the effect of preventing productive discussion while doing little or nothing to prevent unproductive ones (even possibly encouraging them). Thryduulf ( talk) 16:32, 1 September 2013 (UTC)
Well, I expect there will be some lengthy comments, & Andy should finally start using preview. Johnbod ( talk) 17:41, 1 September 2013 (UTC)
That wont help where the conversation is: Andy: "I think this infobox would help this article", Bob: "Generally I agree, but I think nationality is wrong, because...", Andy: "Bob: Would putting 'Austo-Hungarian' there be more accurate?", Carole: "I like this, but I think it's worth putting there that her husband was her third cousin, can the template do that?". Andy (on Carole's talk page): "I'm sorry but I'm not allowed to answer the question you asked me about the infobox.". Thryduulf ( talk) 18:57, 1 September 2013 (UTC)
That's not entirely the way conversations have tended to go. Maybe he could start a user subpage with a) standard FAQ (or FMA - "frequently-made arguments"), and also b) notes re individual cases. It's not entirely clear how many times he could edit one comment - and he often takes a number of edits on a single comment as it is, hence my preview remark. I don't think such a subpage would be covered. I accept it is not a standard remedy, but surely better for him than a full topic ban, which seems to be the most likely alternative. Johnbod ( talk) 19:43, 1 September 2013 (UTC)
That is how conversations about infoboxes tend to go everywhere the classical music/opera editors aren't involved, and it is how we want conversations to go. An FAQ would be useful (if one doesn't already exist?) but only if editors actually read it and understand it (I have no confidence certain editors named on this page would). I would not be at all useful for questions such as this about specific entries in an individual infobox. Thryduulf ( talk) 20:22, 1 September 2013 (UTC)

(Outdent). It might also be appropriate to tailor this remedy to certain projects. My impression is that this dispute is mostly localized to articles which fall under the purview of WP:OPERA and WP:COMPOSER. In most parts of the article space the use of infoboxes isn't controversial and I don't know that any evidence has been brought forth suggesting otherwise. Under those circumstances a more narrowly-tailored project/interaction ban might be appropriate. E.g. (and building on the suggestiosn from Johnbod and Thryduulf):

"Pigsonthewing is indefinitely restricted from the following actions involving articles which fall under the purview of WP:OPERA and WP:COMPOSER: adding infoboxes to established articles (defined as articles in existence under any title for over one year that are not classed as stubs), restoring an infobox that has been deleted; or making more than two comments in discussing the inclusion or exclusion of an infobox on any given article. He may participate in wider policy discussions regarding infoboxes with no restriction."

I've retained the "wider policy discussion" boilerplate to make it clear that he can mention a "covered" article in the context of a wider discussion. In essence, this is an article-space interaction ban but limited to those areas which Arbcom has actually found disruption. Additional narrow findings of fact concerning those projects would be appropriate if this alternative is considered. Mackensen (talk) 20:55, 1 September 2013 (UTC)

  • Oh for God's sake: it's simple mathematics. Pigsonthewing + Infoboxes = Trouble. Whereas, Pigsonthewing - Infoboxes = a Quiet life for all.  Giano  21:01, 1 September 2013 (UTC)
  • Giano, I sympathize, but that's not true for the entire encyclopedia. The committee does no one any favors by painting with too broad a brush. In the areas where I usually work neither Andy nor infoboxes are controversial. This remedy attempts to get at the actual root of the problem, which is the interaction between Andy and a few select projects. If you can suggest improvements to this concept I'm open to them, but full-blown remedies such as what you're proposing are already in the decision and voted upon. Several of the arbitrators are interested in a more tailored remedy, and that's what we're discussing here. All the best, Mackensen (talk) 21:10, 1 September 2013 (UTC)
  • I disagree: Andy's obsessional views on infoboxes (in all subjects from music to architecture) have been a complete pain in the backside for too many for too long; he needs removing from the equation altogether - then others can all be allowed to reach reasonable compromises. He's had dozens of chances and he's blown the lot, I don't care if he's banned from the project of just banned from infoboxes; just so long as he stops causing all this trouble and disharmony.  Giano  21:16, 1 September 2013 (UTC)
  • Giano's got the maths right here: "Pigsonthewing + Infoboxes = Trouble. Whereas, Pigsonthewing - Infoboxes = a Quiet life for all." QED. That's the last thing I'm going to say on this case (I hope). He had his chances. -- Folantin ( talk) 21:32, 1 September 2013 (UTC)
  • I think we must simply disagree on that. There are many subjects on this project where infoboxes are not controversial nor is Andy's involvement in them. Andy is a regular at Templates for Discussion where he is one of many editors pushing for standardization of templates. This isn't considered disruptive by any of the regulars there. If Andy were truly disruptive sitewide I would have expected broader participation in this discussion. If this was truly a sitewide problem and not localized to a connected set of projects I would expect to see evidence of it, but none was adduced. Much has been made of his bad behavior from six years ago. If we were to constantly hold bad behavior from six years ago against editors then this project would be consumed by hatred and be destroyed. People change and grow. The only thing that's apposite from six years is that Andy doesn't deal well with wikiprojects which reject infoboxes. Fine. An interaction ban solves that problem by removing Andy from that equation. We can then see how that discussion proceeds without him. The results should be indicative.
  • Anyway, this thread is about helping Arbcom craft a narrow remedy. If they think it's warranted they'll take it up. If they don't they'll do something else. I don't think it helps anyone to reiterate how we feel about certain editors. Mackensen (talk) 21:39, 1 September 2013 (UTC)
  • So Mackensen, how are your posts anything but "how [you] feel about certain editors"? ;-) Be that as it may, please read the finding "Pigsonthewing's contribution to discussions", which has unanimous support from all 11 active Arbs, cites recent evidence (including disputes outside Music articles) and cites my evidence. You might also find Choess' and some of the other editors contributions on Pigsonthewings behavior useful.
  • Even RexxS, one of Pigsonthewing's strongest supporters, has a more realistic view of his behavior. RexxS wrote on SilkTork's talk page that "You could insist on him having a mentor starting now. What he needs more than anything is someone to tell him "walk away - it's not worth the pain", because he's glaringly bad at recognising when that point has come. ... But if you don't get someone who can help him spot when his best option is to step away - even when he's right - then you might as well ban him forever." ( diff). Frankly, my opinion is if someone can't learn in nearly a decade on WP how to play nice with others almost all the time, then maybe it is time for them to leave the project (voluntarily or not). Ruhrfisch ><>°° 23:05, 1 September 2013 (UTC)
  • You should have quoted the next sentence from RexxS, because it's even more telling: "Over the last few weeks, he's often emailed me to ask my opinion on a given debate and most often I've told him to walk away - to his credit has done that each time." I've found that whenever we try to get into this question of "playing nice" (not patronizing, just quoting) and whathot we get bogged down in the level of disagreeability a person's contributions warrant. I got out of that business a long time ago because it's an impossible question. Mackensen (talk) 12:28, 2 September 2013 (UTC)
  • I could also have quoted Samuel Johnson "Depend upon it, Sir, when a man knows he is to be hanged in a fortnight, it concentrates his mind wonderfully." We shall see how long the good behavior lasts, though I hope it is a permanent change of heart. Ruhrfisch ><>°° 12:36, 2 September 2013 (UTC)
I don't think this will fly, not least because the Arbs are reluctant to take a position favouring "states rights" for Wikiprojects, which this proposal will tend towards. Several areas have come up in the case, in particular literature, architecture, the visual arts, and historical biographies. There's a long-running infobox row at Peter Sellers, with an entirely different cast (ok, largely different, since some here including myself & Andy commented briefly, mostly back in 2012 - Archive 1). The attempts of Thryduulf & others to paint infobox scepticism as very localised are wrong, though there are large areas like sports and taxons where it presumably doesn't exist. Johnbod ( talk) 03:11, 2 September 2013 (UTC)
Maybe so, but that's the practical effect of this decision regardless. The Committee is free to claim otherwise, but sanctioning one side of the dispute and one side only is taking sides and endorsing the position taken by those projects. Can I gently suggest that you broaden your horizons with regard to the project's scope? There are numerous areas: transportation, sports, the hard sciences, politics, languages (just to name a few) where infoboxes are in my experience widely accepted. I don't claim this to be troublesome or difficult; I claim this because I believe it to be true and because it has a significant bearing on this case. Broad remedies are justified by broad problems, not narrow ones. Mackensen (talk) 12:28, 2 September 2013 (UTC)
I said "large areas like..." (and had already mentioned sport) and back on the evidence page and way up above here have briefly attempted to define what distinguishes those trouble-free areas from the troublesome ones. But someone up above suggested biographies in general were a trouble-free area, which is very much not the case. Johnbod ( talk) 13:42, 2 September 2013 (UTC)
Define "trouble-free". I fail to see trouble in the infobox for Verdi's work that will be shown on the Main page, DYK. I fail to see trouble for a symphony that will appear these days. -- Gerda Arendt ( talk) 05:57, 3 September 2013 (UTC)
Mackensen, it is a mere coincidence that the most prolific pro-infoboxer is being sanctioned. I find it quite unreasonable to read a remedy that says "for [consistently unacceptable conduct], Andy is topic banned", then infer that we are sanctioning him because he's a pro-infoboxer. If we also consider that one anti-infoboxer has been sanctioned, and that evidence for misconduct by other anti-infoboxers has not been supplied despite a request for it, I find it quite obvious that the notion the committee has taken a side – or can even reasonably be perceived to have taken a side – is nonsense.

On the request that we write a narrower remedy, I am not persuaded. Even a brief review of the evidence demonstrates that Andy's conduct with respect to infoboxes has been unsatisfactory on several topic areas, not merely on opera articles. The first diff I opened illustrated him misbehaving on an architecture article, for example. The problem is also with Andy and infoboxes in general (cf here), not Andy's views on whether certain subjects are best presented with an infobox. His attitude in general is problematic, not his content views, which is why a wholescale removal is required. If we restrict him from infoboxes in certain topic areas, the committee is only going to have to chase around after him over the next year, adding more and more topics to the topic ban. AGK [•] 12:42, 2 September 2013 (UTC)

AGK, I never said that you were sanctioning him for being a pro-infoboxer; I think you're sanctioning him for being Andy. I'm unfamiliar with anyone on the "anti" side being sanctioned, unless you mean the admonishment of Nikkimaria. I can't really consider an admonishment in the same breath is a site-ban which appears to be very much on the table, or an infobox-ban which is still a very serious remedy. You'll note that I mentioned several projects above. You might also note that many of the same editors frequent those projects. Whether you draw a conclusion from that is your own affair. Plenty of evidence has been adduced of intractable, uncollegial behavior on the part of other editors which has gone unremarked. Gerda Arendt has raised these issues repeatedly on this talk page and on some arbitrators' talk pages, and has been rewarded by a renewed effort to sanction her (remedy 3.3). Principle #6, concerning ownership, is failing, though I note you haven't taken a position on it. The effect of this decision is to endorse one side of the argument by sanctioning the other. If that's unintended then maybe the decision should be redrafted. All I'm trying to do at this point is limit the effect of this decision to the areas of the project that are actually disputed. I think, however, that I'm wasting everyone's time. You can't see what you don't want to see. Just remember that in your evidence for Andy's disruptive behavior you link to a page where he's the subject of multiple personal attacks. If you're still wondering why many of us are appalled by the direction this arbitration took, that may be your starting point. Best, Mackensen (talk) 12:57, 2 September 2013 (UTC)
  • I should also say that the wording points here should apply to any other topic ban remedies, as appropriate. Johnbod ( talk) 12:11, 3 September 2013 (UTC)

Pronouns

In the finding of fact, Gerda Arendt is referred to using "she". But in the proposed remedies, "they" is used. It sounds a bit silly when read as a whole. Could this please be made consistent? — This, that and the other (talk) 07:26, 2 September 2013 (UTC)

The pronoun concerns me less than the "remedies". The "wider than classical music evidence" is dated. At the moment I am on a voluntary 1RR rule, walk away if an infobox is reverted. I have never added an infobox to a classical music bio other than one I wrote myself, and try to find out in which areas precisely I should avoid to serve the reader by an infobox (see above). - I see that there is a battle but my goal is peace. I respect the personal wishes of editors if I know them. How can we define the "territories" to avoid unintended battle? -- Gerda Arendt ( talk) 07:40, 2 September 2013 (UTC)
  • In the context: Did you know ... that Ben Gunn, imprisoned 32 years for killing a friend when he was 14, earned a Master of Arts degree in peace and reconciliation? (now on the Main page). -- Gerda Arendt ( talk) 08:21, 2 September 2013 (UTC)
  • I left the two most controversial projects, opera and classical music. -- Gerda Arendt ( talk) 11:41, 2 September 2013 (UTC)

Comment by BrownHairedGirl

This is also a comment rather than evidence, and I hope it is acceptable to use the page in this way. Please tell me if it isn't.

I share Kosboot's view that the root of the problem lies is structural, and that is what I want to comment on. (I have had good and bad experiences of parties on both sides of the dispute, and have nothing to add about individual conduct.).

This dispute is one of several areas where there is tendency for a structural clash between 2 sets of parties:

  • some wikiprojects which have a strongly normative culture, which they seek to apply to all topics within their scope
  • editors who work on more technical aspects of the project, such as navigational boxes, categories, succession boxes, or infoboxes. (Similar, tho slightly different issues, have also arisen with some bot owners)

Unsurprisingly, clashes have also occurred with other forms of metadata such as co-ordinates, categories, and navigational templates. Disagreements over the use of co-ordinates have rarely been long-lived, and those over categories and navboxes also tend to be resolved without prolonged drama because in each there is a structured process for achieving a consensus: WP:TFD and WP:CFD, with appeal to WP:DRV. Similarly, there are processes for reviewing and constraining the authorisation and uses of bots, such as WP:BRFA ... and in all cases, the centralised and structured decision-making has allowed a body of precedent to be accumulated, which helps to stabilise consensus.

No such structured process exists for achieving a consensus on infoboxes, which has left the various parties to rehash their fundamental disagreements on the non-prescriptive MOS:INFOBOX. The result is sometimes a cold war and sometimes a war of attrition. Regardless of any action which might be taken wrt individual misconduct, the structural clash will continue.

Others have pointed to the ambiguous status of Wikiprojects. Theoretically, they are vehicles for collaboration; but in practice they assume some degree of WP:OWNership over their subject areas. The community is fluid in how much ownership it accepts, and the unresolved boundaries of both scope and ownership make them an impractical vehicle for deciding on the use of infoboxes. (Some topics may be core articles for 2 or more projects.)

One possible solution is to adopt a rigid global policy on infoboxes, to end the individual disputes. However, the community usually rejects rigid rules.

I see two other solutions, which may be implemented separately or together.

Community solution
Create a central forum for discussing the inclusion of an infobox on an article (possibly Wikipedia:Infoboxes for discussion). That would help the wider community to join in infobox discussions, broadening participation between the two most involved camps (i.e. the infobox specialists and the Wikiprojects)
Technical solution
Modify the mediawiki software to allow readers to set their preferences to enable or disable the display of infoboxes. A community decision would be needed on the default display setting, but giving readers a choice would help defuse some of the tension. -- BrownHairedGirl (talk) • ( contribs) 15:39, 2 September 2013 (UTC)
Versions of the "community solution" are discussed above, in this and other sections. I doubt the "technical solution" will please infobox-sceptics as we know the awareness & take-up will be miniscule. Johnbod ( talk) 16:18, 2 September 2013 (UTC)
A community discussion to determine whether WikiProjects should be purely a collaborative venue or have power to dictate rules across article categories might not be a bad idea either. Equazcion (talk) 16:26, 2 Sep 2013 (UTC)
There are a lot of interesting ideas and possible solutions mooted here; however nothing is going to be solved happily and collegiatly while Andy Mabbitt is on the loose. Too many of us have been there with him too many times. For as long as he is allowed to run rampantly and arrogantly through the infobox subject nothing will ever be happily resolved. He has made himself a red rag to too many bulls/cows  Giano  19:09, 2 September 2013 (UTC)
I disagree there, Giano. I see plenty of evidence that many users, including Andy, can grow and change. I do think that sometimes when people who have clashed in the past run into each other, they may be more prone to revert to old patterns, but it's important to look at the user's overall growth. A ban on Andy won't solve the real problem here, which are some other editors who WP:OWN the classical music projects and run off anyone who dares to question their authoritah. I think that's the tragedy here. (Note the action of Gerda, above, and also Ched, who has quit WP altogether because of all this) — Preceding unsigned comment added by Montanabw ( talkcontribs) 21:07, 2 September 2013‎
Smerus has left Wikipedia as well. – Voceditenore ( talk) 21:18, 2 September 2013 (UTC)
There is no evidence at all that Andy can change or is even, indeed, willing to change. It's sad, but he has to be removed fron the subject/project - there is no alternative.  Giano  21:15, 2 September 2013 (UTC)

AGK: Request for evidence relating to Kleinzach and Smerus

was posted here and includes sub sections: [133] ( olive ( talk) 17:01, 2 September 2013 (UTC))

The drafter looked at that evidence. He found the Smerus evidence persuasive, and proposed an appropriate finding (which was followed by my remedy). The Kleinzach evidence was not so persuasive, but the point is that all the anti-infoboxer submissions were dealt with and there are none outstanding. AGK [•] 21:10, 2 September 2013 (UTC)
I was confused by, "little or no evidence" in your statement and assumed the previously posted evidence had been missed. No comment one way or the other was meant which is different discussion.( olive ( talk) 21:56, 2 September 2013 (UTC))

Joseph Priestley article and Infoboxes

I am not sure what else to do with this information, so I am posting it here.

The article on Joseph Priestley is a FA and has no infobox. In June 2007, as a group of editors were improving it with an eye to FAC, the infobox was removed after a talk page discussion, and discussed again later that month. The lack of an infobox was raised next in its October 2007 WP Biography peer review, and none of the 5 editors commenting there were in favor of a box. No mention was made of infoboxes in the GA review, in October 2007 a box was added, then removed and discussed - for both see here. Inoboxes were not mentioned in its Scientific peer review or FAC.

In 2009 there was an extensive discussion and RfC on both the alignment of the lead image (it used to be left aligned, until the MOS changed) and the lack of an infobox - here. The RfC closed with no consensus to add a box, and although the MOS change meant the image became right aligned), from Oct. to Dec. 2011, there was a discussion that again came to the consensus that no infobox was required, at least at that time.

Earlier today, User:Pigsonthewing made a series of edits to the article, some of which added an infobox with edit summaries including "Template" and "ce" and "("( diff). I reverted citing WP:BRD and previous consensus against a box ( diff). I opened a discussion on the article's talk page here where we each commented briefly and Pigsonthewing said he was done with the infobox. Ruhrfisch ><>°° 22:31, 2 September 2013 (UTC)

Questions for arbitrators only

Please could the arbitrators (and please only arbitrators) answer the following questions in as succinct manner as they can manage. Having re-read all their comments on the decision page I still do not understand why this decision is as it is:

  1. How will banning Andy improve the encyclopaedia, taking into account all his contributions?
  2. Why do you think that this decision will not lead to ownership of articles by the Classical Music and related wikiprojects, contrary to the opinions expressed on this page by (almost?) everyone not involved with those projects?
  3. Why have you chosen not to make any mention of the personal attacks against Andy presented in evidence and on this page?
  4. Why do you think that this proposed decision has generated so much opposition relative to almost every other? The Tea Party case is the only comparable one I am aware of, and that was in the Committee's own words an extraordinary proposal).

These are not flippant questions, and I would like answers please from all the arbs active on this case before it closes. I am normally very supportive of the committee but I am genuinely struggling to understand how you came to a proposed decision that is so seriously out of line with the evidence as most uninvolved commenters here read the case. Thryduulf ( talk) 14:57, 3 September 2013 (UTC)

@ David Fuchs, Salvio giuliano, SilkTork, Carcharoth, and NuclearWarfare:,@ Timotheus Canens, AGK, Newyorkbrad, and Roger Davies: Please would you have the decency to respond to direct questions. Thryduulf ( talk) 00:54, 6 September 2013 (UTC)
Ah, I missed this earlier (I remember reading it, but replying to your questions slipped my mind). First, a word on responsiveness of arbitrators. Contrary to popular belief, it is not the norm for all 15 (currently 13, and only 11 on this case) active arbitrators to respond to direct questions aimed at the committee as a whole. If all 15 arbitrators participated in every such set of questions (and you and others replied to all that was said), we would be here a very long time. Until a proper moderated way to have discussions without them running out of control is available, that will always be the case (this is, incidentally, one of the reasons for the 'comment only in your own sections and avoid threaded discussions' set-up at WP:RFAR). Having said that, the talk pages of a proposed decision is a place for threaded discussion, and some responses are warranted. I will do my best to answer your questions.
  • (1) Andy is not being banned. But if anyone is banned during a case it is usually to prevent disruption caused by that editor's presence, or that editor's actions, regardless of their levels of contributions.
  • (2) I supported the principle referencing WP:OWN that did not pass, but I can understand the reasons given in the comments by my colleagues that opposed it. Editing is often a balancing act between (i) editors that range widely across articles in many different topics who may (or may not) have extensive knowledge of a specific topic area; and (ii) editors that focus on narrower topics or areas (sometimes only one article) and build up that area or article. This can lead to tensions if both types of editors (and I know many editors do both sorts of editing) clash over some aspect of article editing. The key is to be able to discuss things productively when that happens, and respect each other as fellow editors, rather than end up in circular and endlessly repeating arguments that reduce the productivity of all editors that end up involved in such disputes.
  • (3) No comment. I will leave that for the drafters of the case to answer if they choose to do so.
  • (4) This case has not really generated more debate than other cases. You need to look back to earlier in the year and to 2012 and 2011 to compare with cases back then.
I hope this helps, Thryduulf. Apologies for not replying earlier. Carcharoth ( talk) 01:23, 6 September 2013 (UTC)
I agree with what Carcharoth said. 3 cont) I didn't draft this case and there is only so much time I could spend on it. NW ( Talk) 02:34, 6 September 2013 (UTC)
A subject that comes up time and time again at arbitration is the "worth" of contributors--namely, the rationale that X editor, having broken Y policies or guidelines, should receive "less punishment" because of the good work they do in various areas.
I don't subscribe to that idea.
If an editor is disruptive, and preventing other editors from contributing effectively, then they should be addressed. Anything else becomes a bizarre game of editing worth. Let's engage in a thought experiment: who is worth more as an editor, Pigsonthewing or me. Andy has roughly three times as many edits. He has more mainspace edits than me. Does that make him worth more? I have more featured articles, more substantial edit\ to a smaller core of articles. Is that better than editing tens of thousands of articles like Andy? Or is my quality outweighed by quantity of smaller fixes, typos, and formatting? A lot of my featured articles are on pop culture topics, so are they worth less than a classical composer? If so, how many FA video games articles would it take to make a Wagner? A Liszt? A Mozart? What's the exchange rate on template edits to meaningful content additions? To vandalism cleanup? To admin backlog tasks? What about factoring in yourself, Thryduulf? Have your 43 edits to Spain, the most you've sunk into any article, been worth less than what I've done, or what Andy has done? Is true "editing worth" the proportion of article edits to non-articlespace edits, in which case you would be found wanting?
I hope this exercise conveys my point: there's no agreeable metric to decide when an editor's worth is greater, or less, than the trouble or disruption they cause.
We are all volunteers, and (despite biological or emotional ages) Wikipedia's principles are set up so that we are all treated as equals and adults. As an arbitrator, I often try and focus on minimizing fuss and trying to get quality edits out of editors without causing trouble; if a banned user appeals, I'm more inclined to try and suggest a topic ban from problematic areas than throw away the key. But there is a point where no amount of gamesmanship can thread the eye of the needle, that perfect sweet spot of disruption-free quality contributions. And so one has to make the call about whether cutting off some good contributions to avoid the bad is worth it. That threshold may often be higher for quality contributors and long-term editors, simply because there are more fields they partake in, more topics they edit, more namespaces they benefit. However that threshold is, fundamentally, an issue every arbitration case grapples with in its remedies.
As for your mentions of "seriously out of line" and estimation of whatever you could possibly term "popular opinion", I think we will have to disagree on your interpretation. Der Wohltemperierte Fuchs( talk) 03:39, 6 September 2013 (UTC)

My answers to the questions above:

  1. I did not vote to ban Pigsonthewing, precisely because I concluded that the drawbacks to doing so outweighed the benefits. That being said, I think there is wide agreement that aspects of his behavior have been problematic and need to change.
  2. One of the issues to be addressed in the hoped-for community discussion, I believe (and have indicated on the decision page) is the degree of deference due, in deciding whether an infobox is useful in a given article, to the users most familiar with the article or the subject-matter. I expect the conclusion will be that their input is relevant but not necessarily dispositive. The reasons that contributors to a given article or members of a wikiproject believe inboxes are unsuited to the articles in that area also bear consideration. Sometimes those reasons might be convincing to other editors, and sometimes they might not.
  3. Not every instance of poor or debatable conduct presented in evidence needs to be or can be included in the final decision; the drafters, and other arbitrators who add to the draft, wind up prioritizing in every case. Although the drafters may speak for themselves, presumably they concluded that this was not an area that required focus in the decision. It remains unacceptable for any editor to personally attack any other, although not every instance of doing so can or will result in a sanction.
  4. I agree with Carcharoth's response to the last question. Sorry these responses were delayed. Newyorkbrad ( talk) 16:29, 6 September 2013 (UTC)

Thank you to those who answered, I haven't got time now to read all your answers but I would like to appologise for my tone earlier - a good example of when I should have previewed and then not saved. Thryduulf ( talk) 21:59, 6 September 2013 (UTC)

Principle 3.1.5 Mission

I am concerned that the Arbcom appears to advance a view on content in principle 3.1.5 Mission: "Wikipedia's mission is to build an encyclopedia that can be modified and distributed freely. To facilitate access to this information, we should provide as few barriers to its use and dissemination as possible. Additional information, such as metadata, aligns with the goals of the encyclopedia where it is not detrimental to our content or our scope. [+emphasis]"

Whatever the perceptions of my opinions on the matter might be, my point is that I would be equally concerned if the pronouncement in the last sentence were the opposite. The italicized portion could be used as a rhetorical weapon (or more than that) in community debate, and influence what should be unbiased discussions from the beginning. NW is perceptive in saying that " 'detrimental' would have to be able to be interpreted so widely as to make [the principle] useless". That nuance would undoubtedly be lost when this principle was taken up by a community in debate. Since any hypothetical debate would obviously examine the pros and cons, I'm not seeing the point of this statement other than to inadvertently set up a context for content debate which amounts to "The Arbcom said...". And If I'm not mistaken, the Arbcom is actively recommending in another finding that community discussion should occur on these issues. Regards, Riggr Mortis ( talk) 15:36, 3 September 2013 (UTC)

  • Support. I’ve already commented on this above, see Perspective from Kleinzach, 3. Technical issues. If metadata is a form of content, and content is outside the scope of Arbcom, then the second sentence of 3.1.5 (Mission) is mistaken. Most of recognise that we need to look at the subject of metadata much more closely. I’d hope ArbCom would encourage, not discourage, this. Can they think again? Klein zach 00:39, 4 September 2013 (UTC)
  • Support per Riggr and Kleinzach. Ruhrfisch ><>°° 01:04, 4 September 2013 (UTC)

Impressive

"Indefinitely separating an long-term dedicated editor from this project should take more than the closest possible vote of a divided committee. For this reason alone, I'm striking my support. T. Canens (talk) 00:03, 4 September 2013 (UTC)" Now that is impressive. PumpkinSky talk 01:54, 4 September 2013 (UTC)

  • Indeed!— John Cline ( talk) 02:20, 4 September 2013 (UTC)
  • Gonna pile on my kudos too. I'm completely unfamiliar with Pigsonthewing's history so I can't say if his banning would've been a good or bad thing. Either way this is a refreshingly wise statement. Equazcion (talk) 03:18, 4 Sep 2013 (UTC)
  • I also am pleased and impressed to see this expression of wisdom. -- Orlady ( talk) 03:24, 4 September 2013 (UTC)
  • Yes, we elect the Arbs to make the hard abstentions for us. I especially like the last minute bait-and-switch, so no one realizes what a bizarre decision this now is. As it currently stands, Arbcom has voted to...
    • ...admonish Nikkimaria for edit warring with Pigsonthewing, but not to admonish Pigsonthewing for edit warring.
    • ...indefinitely restrict Gerda Arendt from restoring an infobox that has been deleted, but not to restrict Pigsonthewing in this way.
    • ...admonish Gerda Arendt for treating Wikipedia as if it were a battleground and advise her to better conduct herself, but not to admonish Pigsonthewing or advise him in any way.
    • ...remind Smerus to conduct himself in a civil manner, but not to remind Pigsonthewing how to conduct himself.
  • What exactly do you find impressive about this again? Ruhrfisch ><>°° 03:35, 4 September 2013 (UTC)
    • The decision to indefinitely ban Pigsonthewing from adding or discussing the addition or removal of infoboxes seems to have passed though. I think that covers the restrictions others got, and maybe covers admonishment as well; though perhaps an explicit admonishment should also be proposed for Pigsonthewing, seeing as the site ban is defeated -- I don't have an opinion on whether he should be admonished, but it looks like something that could pass. What is impressive, Ruhrfisch, is T. Canens lone act, even if fault can be found in the way the totality of the case stands at the moment. Equazcion (talk) 04:21, 4 Sep 2013 (UTC)
      Exactly; and the stuff you didn't say too!— John Cline ( talk) 04:31, 4 September 2013 (UTC)
  • Mabbitt be site banned, for breaking his restrictions, in a few weeks or months just as surely as evening follows day. The Arbs know this, but the current passing motion allows them not to appear too Draconian.  Giano  07:12, 4 September 2013 (UTC)
  • Impressed and relieved. Everybody who knows me a bit knows that "battleground" is kafkaesque, but I couldn't care less about "imposed" restrictions. I learned, not only this new word. (You don't add the unspeakable thing, you impose it, I didn't know that.) - For clarity: "care less" means 1) I was not worried at all about myself, 2) I am not worried about sticking to restrictions as I left the conflict areas - classical music and opera - already.
@Equazcion: from Andy's recent history: Ben Gunn and "Let us not forget that even one book, one pen, one teacher can change the world". I am happy that more of that can come.
@Giano: Everybody afraid can simply watch his edits and revert, it's so easy.
A hymn is in order. -- Gerda Arendt ( talk) 07:25, 4 September 2013 (UTC)
Dearest Gerda, it appears that someone may have used our differences in language to play a cruel joke on you—indicative of child's play. There is actually no relationship with your manner of editing and the verb form of impose—yet somehow you've used it in correct context with "restrictions". I'm impressed again.— John Cline ( talk) 08:35, 4 September 2013 (UTC)
  • T. Canens's action is certainly a good thing, and I thank him for it. However it shouldn't be regarded as impressive for an arb to take such action - doing it shouldn't be needed in the first place, but if it is it should be normal. Thryduulf ( talk) 09:18, 4 September 2013 (UTC)
  • My take (short version): bullet unbitten, inevitable postponed. This pulled punch is only going to work if you have the stamina to enforce it properly. -- Folantin ( talk) 12:10, 4 September 2013 (UTC)

Already a dead letter?

This morning Gerda Arendt has gone straight ahead and added yet another infobox to a Bach article [134]. As far as I can see, this is not a page she herself created. I don't see how this is stepping away and disengaging from the infobox furore. -- Folantin ( talk) 10:22, 4 September 2013 (UTC)

It's a cantata where I am the main contributor, as for most Bach cantatas. I created about half of them, expanded several others from a stub. With some 150 articles in question, I didn't improve all at the same time, but since December routinely add an infobox for the cantatas of the upcoming Sunday. - For consistent style to the reader, I would prefer if all looked the same, but I respect other editors ( BWV 105) and the cleanup of editors who are no contributors ( BWV 71), as now also the one you mention ( BWV 51), - I will not fight it, but does it make sense? -- Gerda Arendt ( talk) 10:45, 4 September 2013 (UTC)
Doesn't seem consistent with: "Gerda Arendt is indefinitely restricted from: adding or deleting infoboxes; restoring an infobox that has been deleted; or making more than two comments in discussing the inclusion or exclusion of an infobox on a given article. They may participate in wider policy discussions regarding infoboxes with no restriction, and include infoboxes in new articles which they create." -- Folantin ( talk) 10:48, 4 September 2013 (UTC)
Nor is yours ↑ consistent with "All editors are reminded to maintain decorum and civility when engaged in discussions about infoboxes, and to avoid turning discussions about a single article's infobox into a discussion about infoboxes in general.", nor Bencherlite's below ↓.— John Cline ( talk) 11:14, 4 September 2013 (UTC)
(after several edit conflicts) You are right. - Perhaps that "letter" can change, to make more sense? How about templates such as {{ infobox Bach composition}}, that were developed within the project and are not contentious? -- Gerda Arendt ( talk) 11:08, 4 September 2013 (UTC)
Gerda is obviously trying to get as many infoboxes in as possible before the restrictions start, despite her empty words to me this morning: "I left projects classical music and opera, the areas of conflict. If I added an infobox you could simply revert it, and now I will not even add one." Clearly she and I have a different view on how many infoboxes make "one". Bencherlite Talk 10:54, 4 September 2013 (UTC)
What seems obvious to you, isn't true. It's a routine since December, I do three a week, normally on Mondays, as you can see in my contribs, - this week I was held up. I don't only add an infobox, but also update them, improve wording, format references and add the lang-template to articles for which I feel responsible. -- Gerda Arendt ( talk) 11:08, 4 September 2013 (UTC)
( edit conflict) She may not have "created" the page (again: is that a criteria? Under what policy?) but she is a major contributor to it, having first contributed in 2010. Indeed, she has added more volume of content to it than the colleague who did create it, and who has not edited it since the day they did so, in September 2005. I note that Eusebeus has removed the infobox, with the edit summary "rm info box pending determination for consensus via talk", but started no such discussion on the talk page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:59, 4 September 2013 (UTC)
( edit conflict)×3 :I note that the addition was reverted by user:Eusebeus with the summary "rm info box pending determination for consensus via talk." but the only comments on the talk page are from 2011 and no attempt has been made to explain why the infobox might not be beneficial to this article. This is important because, to summarise and generalise RexxS' comments, the benefits of infoboxes are generally the same for every article accross the project but the downsides are not, and so they need to be expressed and weighed up on an individual article - sometimes they exceed the benefits and sometimes they don't, but you can't evaluate that without knowing what they are.
While she didn't create the article, the revision history statistics show Gerda is the most frequent contributor to the article by some way (38 edits, one editor has 7 and no others have more than 3). Although she is about 10th by average edit size, she has added a lot of information to the article (including referencing it), so it is in no way fair to say that she is not one of the principle editors. From memory (and I haven't double checked this) Bach compositions are cited in evidence as articles where additions of infoboxes have been uncontroversial in the past (in the context of it being impossible to know in advance where they will be controversial).
So what we have here is one of the principle contributors to an article adding an infobox to it, and being reverted by someone making their first edit to the article without discussing why. Which is the exact opposite of what we are told always happens by those not wanting infoboxes. Thryduulf ( talk) 11:06, 4 September 2013 (UTC)
I was quoting this proposed restriction: "Gerda Arendt is indefinitely restricted from: adding or deleting infoboxes... [she may] include infoboxes in new articles which [she] create[s]."
It's funny to see Andy Mabbett now stressing that the opinions of the principal content contributor should be given the most weight. Had he actually espoused this principle before, we might have been spared all the endless wrangling over Cosima Wagner or The Rite of Spring, to take just two examples. It's even possible that this very Arb Case need never have arisen. -- Folantin ( talk) 11:16, 4 September 2013 (UTC)
That's actually not what is being suggested at all. Andy (and I) are simply saying that you can't have it both ways - if you insist that the views of the principle contributor are respected when they don't want an infobox then you have no leg to stand on when views of a principle contributor who adds an infobox are not respected. Thryduulf ( talk) 11:23, 4 September 2013 (UTC)
That's not what Andy's saying. See below. I would have no problem giving weight to the opinion of the creator/primary contributor (assuming it was in line with our core content policies). -- Folantin ( talk) 11:51, 4 September 2013 (UTC)
Yes, that is what I'm saying. While the basis of your position is false, it's still being applied hypocritically. And we do have a core content policy which precludes giving additional weight to one editor or group of editors: WP:OWN. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:35, 4 September 2013 (UTC)
( edit conflict) It's funny to see Andy Mabbett now stressing that the opinions of the principal content contributor should be given the most weight. - That would indeed be "funny", and not in the humorous sense. I didn't say that, nor do I think it, so please don't attempt to put words in my mouth. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:27, 4 September 2013 (UTC)
I think those referring to principle editors above are doing so in the context of interpreting the proposed decision on this page, as in, what might constitute an article that Gerda "created" (rather than the more general principle that anti-infobox editors tend to reference). I have to say though I don't think the allowance that Gerda can "include infoboxes in new articles which they create" is served by her adding an infobox to an article she did not create, and is not new. The case hasn't concluded yet but those likely facing infobox restrictions might be wise to keep a distance from individual article infobox issues at the moment. Just my take. Equazcion (talk) 11:30, 4 Sep 2013 (UTC)
Warum betrübst du dich, mein Herz
BWV 138
church cantata by J. S. Bach
Relatedmovement 5 base for Missa, BWV 236
Occasion15th Sunday after Trinity
Cantata textanonymous
Choraleby anonymous, formerly attributed to Hans Sachs
Performed5 September 1723 (1723-09-05): Leipzig
Movements7
Vocal SATB solo and choir
Instrumental
You are right, but
  • if we go strictly by the letter the restriction is not in place yet
  • in the light of this discussion, perhaps the restriction can be worded differently?
  • the articles in question are not "individual articles" but a series in which most articles have infoboxes
  • for these articles there is no author whose feelings are hurt
  • the topic is not contentious
  • the parameters are not contentious
I ask our esteemed arbitrators for a solution, perhaps with our readers in mind, - hopefully before Sunday. Until then, I will not add to Warum betrübst du dich, mein Herz, BWV 138 (Why do you trouble yourself, my heart), -- Gerda Arendt ( talk) 11:48, 4 September 2013 (UTC)
I have to doubt that the arbitrators will think it beneficial to make the restriction contingent on how contentious a particular situation is/whether or not you're a principle contributor/whether or not an article series has an established form. Those would add layers of ambiguity and interpretation ripe for fighting over later. The choice of words ("new" and "create") was likely intentional as it is less likely to produce conflicting interpretations. Equazcion (talk) 12:10, 4 Sep 2013 (UTC)
Gerda, infoboxes on classical music articles are somewhat contentious. I think everyone following this case has realised that by now. -- Folantin ( talk) 12:15, 4 September 2013 (UTC)
I show the missing infobox which will hopefully make it to the article until Sunday, better tomorrow because the premiere was 5 September. Folantin, the template {{ infobox Bach composition}} has been discussed first on the project talk, further on the template talk. There is also {{ infobox orchestra}}, initiated by Kleinzach, - your generalisation "infoboxes on classical music articles are somewhat contentious" is not quite to the point. It's more some classical music authors, who - not wanting infoboxes in biographies - extend this dislike to compositions. -- Gerda Arendt ( talk) 12:34, 4 September 2013 (UTC)
Gerda, I don't think what this case needs is yet another infobox discussion. Please. -- Folantin ( talk) 12:49, 4 September 2013 (UTC)
It isn't. It is a discussion about how to supply our readers with unrestricted information, for example by a different wording. -- Gerda Arendt ( talk) 12:52, 4 September 2013 (UTC)
Remember, in the workshop I tried to find a way to reach consensus. In this case I don't even see a conflict, author wants infobox, no former author objects, why not then? Whom would a restriction serve in such a case? -- Gerda Arendt ( talk) 13:28, 4 September 2013 (UTC)
Please compare GA BWV 103, GA review by Smerus with whom I liked to work and hope to do it again, -- Gerda Arendt ( talk) 14:42, 4 September 2013 (UTC)

New day: I found messages on my talk which made me reply, thoughts also for this context:

  • I would love to eventually not talk about infoboxes for individual articles, but groups of them, for example orchestras and Bach cantatas, two topics where I don't see the slightest conflict.
  • All French, Norsk and German Wikipedia Bach cantatas have an infobox, the German derived from our English example.
  • Infoboxes in Bach cantatas (template developed and usage established with help from Kleinzach, Voceditenore and Nikkimaria) help the reader understand at a glance that the long German title, followed by a translation and a catalogue number, is a work by Bach; they provide year/date and location, let him know the sources of the hybrid text (typically three different sources) and the voice parts and instrumental scoring?
  • Regardless of how good or bad the article is, and by whom, these are facts important for a reader. Please let him have them at least for articles for which I feel responsible, - accepting that it is impossible at present for the several that Nikkimaria wrote. How can we get reverted infobox of BWV 51 and the one proposed for BWV 138 here to the respective article? -- Gerda Arendt ( talk) 11:30, 5 September 2013 (UTC)

Mabbett and infoboxes

I was trying to stay away from this subject as it annoys me intensely and the whole brouhaha that surrounds the discussions generate far too much heat and little in the way of light. I do feel uncomfortable with the wording restricting POTW's remedy 1.1 (currently passing): ("Pigsonthewing is indefinitely banned from adding or discussing the addition or removal of infoboxes.") While I support the spirit of this proposal, it does mean that even if POTW starts a new article from scratch, he is unable to add an infobox. This seems to be an unwanted aspect to the proposal and I advocate a minor tweak to allow him to add an infobox at article creation stage:

"Pigsonthewing is indefinitely banned from adding or discussing the addition or removal of infoboxes: he may include infoboxes in new articles which he creates."

SchroCat ( talk) 11:29, 4 September 2013 (UTC)

If we're going down that road (and I agree with your comments about the existing proposed restriction, and it exist also for Smerus' proposed restriction) then using the same language as used for Gerda would be good for consistency. But please per my comments elsewhere on this page, drop the maximum two comments language from all of them, it will just make things worse. Thryduulf ( talk) 11:47, 4 September 2013 (UTC)
Please see #Infoboxes and new articles and #Proposed remedy 1.1, above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:44, 4 September 2013 (UTC)
I see Courcelles has taken the step (although using the awful singular they). Many thanks Courcelles. - SchroCat ( talk) 14:33, 4 September 2013 (UTC)
That does not address the points raised in #Infoboxes and new articles and #Proposed remedy 1.1. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:47, 4 September 2013 (UTC)

RfC

per the committee recommendation I started a page at Wikipedia:WikiProject Infoboxes/2013 RfC draft. Play nice. — Ched ZILLA 08:55, 5 September 2013 (UTC)

I hope this isn't some kind of joke. Any community discussions that are set up following this ArbCom should be done by established, respected editors who are willing to do the necessary detailed drafting. Editors who have taken a moderate position on the controversy will be best suited to this job. It shouldn't be undertaken lightly. Klein zach 09:41, 5 September 2013 (UTC)
Chedzilla is an alternate account of User:Ched, who requested this arbitration case and had previously started User:Ched/RfC - Infobox. Despite the comments on User talk:Ched, he has not left Wikipedia. Voceditenore ( talk) 10:17, 5 September 2013 (UTC)
I've removed the WP:OWN mention on the page and put it into more neutral language: there was no finding of ownership in the decision, so I'm not sure why the RfC decided to lead with it. - SchroCat ( talk) 09:56, 5 September 2013 (UTC)
I think there is much that is useful and possibly helpful at User:Geogre/Templates and suggest all interested parties read it for ideas. Ruhrfisch ><>°° 10:18, 5 September 2013 (UTC)

I completely agree with Kleinzach and with the comments made by Carcharoth and Johnuniq in the sections below. This is extremely ill-advised. If an RfC is to have any chance of not becoming a complete train wreck:

  1. Before even embarking on a draft, at least three months are needed for all involved to return to normal editing, reflect both on this decision and on their own positions, gain some perspective, and drop the (understandable but counterproductive) recriminations and posturing.
  2. Not only does the drafting need to be initiated and undertaken by established, respected editors with hitherto moderate positions on the controversy (preferably no one who has given evidence in this case nor any of the parties, including the filing party), they must also be willing to put in the considerable time necessary to create a detailed and thoughtful draft.
  3. The draft and the eventual RfC should be held in a "neutral location", possibly on a sub-page of Wikipedia talk:Manual of Style/Infoboxes, but certainly not on the pages of WikiProject Infoboxes.

Voceditenore ( talk) 09:28, 6 September 2013 (UTC)

I agree with all of the above comments. Please delete this RfC "draft" before it spirals into another series of mistakes. You can't just throw a handful of stuff at a wall and hope other people turn into something useful. It didn't work with this arbcom case, why would it work with an RfC? Productive RfCs require a lot of hard work and mediation skills. Please leave it for someone who is willing to put in that effort. – Quiddity ( talk) 20:12, 6 September 2013 (UTC)

WikiBreak

In case anyone has a question for me, please note that I am facilitating two conferences over the next five days; so shall have limited and unpredictable opportunity to edit here until Tuesday. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:35, 5 September 2013 (UTC)

Thanks very much for letting us know. If any developments require your input, we will try to hold them off until your return on Tuesday. AGK [•] 11:55, 5 September 2013 (UTC)

The letter of the finding

We speak already of the letter of the restrictions, let me please ask a question regarding the findings about me. It reads at present:

6) Gerda Arendt ... has added infoboxes to many articles systematically, and without prior discussion. including articles where she knew or should have known that adding an infobox would be controversial.

Gerda, this is about the fifth time you've said you were "following the advice of Brad". Can you actually point to where he gave you this alleged advice? NYB would be the first to admit that he has virtually no content-writing, page layout or template markup experience, and as far as I'm aware the only time he ever discussed infoboxes was this comment, in a private discussion with me on my talkpage about how to head off this very RFAR—not any kind of policy debate—in which he specifically prefaced his suggestion with a note that doing this would "probably please noone". –  iridescent 20:40, 5 September 2013 (UTC)
He didn't give me the advice. The link to where he gave it is above, Brad on Boxes. I met it in a list, trying to find solutions for infobox controversies, added there by Nikkimaria, which is linked in my entry "No infobox" (link above), repeated once more. I thought it was a good idea and tried it, without digging into the context where it was mentioned. I wish now I had not. -- Gerda Arendt ( talk) 22:00, 5 September 2013 (UTC)
Reading NYB's full comment, it seems in saying it "would probably please no one", that Brad was merely presenting the definition of the word "compromise", not recommending against the measure. He was presenting talk page-hosted infoboxes as something that both parties might at least tolerate even though neither got their way entirely. That's what compromises generally are. Equazcion (talk) 21:33, 5 Sep 2013 (UTC)

Advice on post-case discussions

The case is close to closing now. Feelings have been running high. My advice to the parties and all those who participated is to step back for a bit and find something else to do. Way up above, Brianboulton said: "My recent Dispatches article was a contribution to that discussion. However, very few positive steps will be taken in the atmosphere of antagonism and mutual annoyance that envelops this whole topic. [...] we all have better and more productive things we should be doing." My suggestion, for those who want to sort through their thoughts on this while they are still fresh, would be for people to make notes or mini-essays offline or in their userspace, and to leave articles and talk page discussions well alone for a bit (or for longer if someone is restricted). Don't rush into post-case discussions, but let things calm down, and find other things to do in the meantime. It's not like the issues are going to go away (the essay by Geogre that someone posted above is from seven years ago). Carcharoth ( talk) 22:55, 5 September 2013 (UTC)

Questions and time

  • It's close to closing and not one of the arbitrators has seen fit to answer any my explicit questions to them, or respond to any of the comments regarding the perceived weakness of several proposed remedies (by both sides of the dispute in some cases). Those are not the actions of a committee that is interested in maintaining the respect of parties in this case. I'm honestly shocked to think that any arbitrator can read this talk page and still genuinely expect collegiate discussions about infoboxes to stem from this decision. Thryduulf ( talk) 00:49, 6 September 2013 (UTC)
    • I've answered your questions above as best I can. Could I ask you to consider putting your post above (which isn't really anything to do with post-case discussions) into a new section separate from what I said (you could title it something like 'questions need answering before case closes')? The point I was making about post-case discussions is really important, and I don't want it to get lost because you feel affronted that your questions were not answered. Carcharoth ( talk) 01:30, 6 September 2013 (UTC)
  • I agree with Carcharoth and was surprised to see the recent RfC section above which pointed to a new RfC draft. I would much prefer that the Community discussion recommended remedy state that it would be counter-productive to start an RfC discussion in under three months. There are good editors on both sides, and very strong feelings on both sides—conducting another knock-down battle at the moment is the last thing that should occur. It would be impossible to hold any discussion in the next three months that is not seen as "Arbitration part 2", and the entire case would be refought—perhaps not the entire case because variations on "editor X was disruptive" would be squelched, but everyone involved would know that this was the ultimate winner-takes-all argument, and only two outcomes would be possible: my side wins, or your side wins—in each case, a significant group of editors is made to feel even more bitter. Johnuniq ( talk) 02:58, 6 September 2013 (UTC)
Sorry - my bad, my fault. I saw the suggestion of a discussion, and not being able to be consistently active on wiki, I missed the "wait" idea. Feel free to delete. I'm doing my best to follow this through to the end, and I screwed up - sorry. Feel free to delete it, I won't object. — Ched ZILLA 04:51, 6 September 2013 (UTC)

Mercy

Smerus retired. I would like to see no actions against him, for decency. (I had no problem with his arguing, minded only one phrase. He and I were ready to keep working together. The term "battleground" is a myth, if you ask me.) I don't know if the rules would permit that.

  1. -- Gerda Arendt ( talk) 10:12, 6 September 2013 (UTC)
  2. Quiddity ( talk) 20:24, 6 September 2013 (UTC)
I'd actually be in favor of reversing the sanctions against Smerus, but not out of mercy. The quoted evidence just seems rather thin for imposing restrictions: [135] [136] [137]. The third diff is really the only example of unacceptable behavior that I'm seeing. The other two seem at most like impatient words in a heated exchange, as is par for the course on Wikipedia. I've seen people get away with far worse both in cases that did and did not end up at arbitration. Unless there's something I'm missing (which is entirely possible as I've not done any digging beyond reading those three diffs), I'm inclined to ask the arbitrators to rethink this or at least explain their votes a little more than they have. Equazcion (talk) 13:54, 6 Sep 2013 (UTC)
I'm sad that I never managed to successfully communicate to Andy that he has to acknowledge the perspectives of others when they have legitimate subjective objections (I still think that would've solved almost everything, in this and previous heated-discussions). Acknowledging the diverse perspectives and problems, cannot be undervalued, as a part of resolving team-disputes.
However, I'm also frustrated that any other editors seem to be getting more than an admonishment - restricting gerda or smerus from infoboxes completely isn't a good solution - they just need to be given a better structure to work within - ie. better infobox guidelines. They're both willing to admit mistakes and move towards compromise/consensus positions and templates, when not backed into a corner. These two split decisions, that are leading to one retirement and widespread frustration, could be usefully re-examined. – Quiddity ( talk) 20:24, 6 September 2013 (UTC)
Quiddity, the problem is that we lack the authority to unilaterally create better infobox guidelines. We may suggest or even urge the community to discuss the issue and come up with a new solution, but, right now, we have to apply the policies as currently written, even if we were to consider them unwise. Salvio Let's talk about it! 20:59, 6 September 2013 (UTC)
Salvio, I suppose I was thinking of this as the rationale/answer: "We're going to admonish editors x and y, but not restrict them, because they are currently working based on fundamentally [flawed/ambiguous/lacking/inadequate] guidelines and MoS pages. We will try to assist the community in its search for a suitable individual to help put together an RfC aimed towards improving these areas of documentation, in an effort to move this forward in the normal community process, but in as well-researched and balanced a manner as possible." (Note: That's not meant to be in the standard-legalese; my wording is flawed; I'm just trying to get across the general idea. :) – Quiddity ( talk) 00:30, 7 September 2013 (UTC)
Quiddity, I like your proposal as an alternative to restricting Gerda and Smerus (but not Andy, whom I still think needs to be site banned, but that's neither here nor there); and I have mentioned it on the mailing list. Let's see if any of my colleagues agree. Salvio Let's talk about it! 12:32, 7 September 2013 (UTC)
What has always been a problem and is becoming more so here and around Wikipedia is loss of understanding of what a community is. We are so intrenched in a punitive mind set that we do not have the vision or skills to work through problems that have arisen in a group, that depend on collaboration rather than separation. Our arb committee, not their fault and in good part because of what the community is clamoring for may be stuck in an outdated model. Problems will always arise when people are working together. Even as editors here are working out their problems, find solutions, and this is the real outcome of this arbitration, sadly the sanctions stay in place. Something rather important has happened here due in good part to Gerda's open heartedness and ability to work things out with people. A strategy that supports community growth has occurred, if only we could see it.( olive ( talk) 21:22, 6 September 2013 (UTC))
Understandably, people view arbcom decisions as "punishments". But another way of looking at all this is that the protagonists have been given an "opportunity" by the arbitrators to step back from the trajectory they were all caught in—instead of plowing ahead with disputes in article after article and becoming more and more frustrated with each other. I'm not sure it was an opportunity they would have chosen themselves before these proceedings began—in fact six more infobox discussions were initiated on article talk pages by the parties involved here during these proceedings: [138], [139], [140], [141], [142], [143]. In any case, people now have the space to reflect and to break the cycle. I hope it will be used constructively. Voceditenore ( talk) 21:56, 6 September 2013 (UTC)
Please also see Pigsonthewing adding an infobox to Joseph Priestley with the fairly misleading edit summary "template" ( diff). I reverted it, citing WP:BRD and the previous consensus not to include an infobox ( diff). I then opened a discussion on the talk page where I linked to 4 of the 6 archives where infoboxes are discussed (there is also clear consensus against a box from late 2011 on the current talk page) here and was told by Pigsonthewing "I note that you dismiss my addition of an infobox without making any arguments against it" (which he had not even labeled as an infobox on adding it to the article).
Arbs, please read your Proposed findings of fact again. Then read the Proposed remedies. Does it really seem, based on your own findings of fact, that Smerus and Pigsonthewing deserve essentially the same remedies? I would argue that Smerus' remedy is worse - he is also "reminded" (and Gerda and Nikkimaria are admonished) while Pigsonthewing is neither admonished nor reminded. I know these are neither crimes not punishments, but if they were, would the "punishments" fit the "crimes"? Ruhrfisch ><>°° 18:56, 7 September 2013 (UTC)
what is striking me here in many of the above comments (clear up to the top of the page, is that it appears that presenting evidence in one's defense is considered a whole new "crime" rather than a defense -- supposedly sought by ArbCom -- for the previous set of actions. Does no one see how the tag team of Smerus and Kleinzach paired up to WP:BAIT Gerda in particular, but also gave aid and comfort to Nikkimaria to the point that she made some serious mistakes in stalking Gerda and Andy, and how Andy's behavior, if it was anyone other than Andy, would be deemed mildly overeager wikignoming at most? Seriously, Smerus and Kleinzach really should not scoot out of this scott-free. They DID exacerbate the situation! Montanabw (talk) 00:32, 8 September 2013 (UTC)
Montanabw - with due respect, as an outside observer, no I do not see that Smerus and Kleinzach "paired up to WP:BAIT Gerda"; rather, I see you have done your bit to do this, even as Gerda and Smerus were building bridges, by being outraged ostensibly on Gerda's behalf (though she has not invited this from anyone), accumulating evidence - most of it quite trivial - against Smerus in particular, despite Gerda's continued collegial attitude to Smerus. I notice that since Smerus has been driven away from Wikipedia, Gerda has joined the [ vote of thanks to Smerus]. Perhaps you hadn't noticed he had departed? Forgive my saying, but your actions increasingly appear to be driven by some kind of vendetta. Please prove me wrong. Alfietucker ( talk) 01:28, 8 September 2013 (UTC)
You didn't read all the diffs, then. They were requested, and submitted. As for the rest, Gerda did a good job to work with Smerus, and Nikki, and had they been left alone and not tag teamed by others at the classical music project who owned everything, they may have worked things out. But the reality is that Kleinzach, by simply refusing to respond at all, is scooting off more scott free than Smerus, and he was, if anything, the more egregious offender in the "lalalalalalala no infoboxes everevereverever" department. My only concern here was seeing how bad Gerda was being ganged up on and bullied. People showed her little good faith and were saying terribly mean things about her. I think she's a wonderful, kind, decent human being and she did not deserve any of this. Montanabw (talk) 19:12, 9 September 2013 (UTC)
Yes, I have read all the diffs (at least the ones proffered and a bit more, plus there's what I have happened to encounter in the course of working on classical music articles on Wikipedia). I'm not sure I'm convinced by your change or at least modulation of tune over Smerus, Montanabw - or at least you give no explanation of what you meant by your previous accusation that he "tag teamed" with Kleinzach. It would seem to me a more likely explanation of them often being on the same talk page is simply that they work on several of the same projects. Otherwise can't the same accusation of "tag teaming" be applied with even greater pertinence to you and Andy? It also seems disingenuous of you to now claim your main beef was against Kleinzach, when the majority of your evidence was against Smerus: furthermore, your evidence against him was both pettifogging and luridly presented ('scream(s) bloody murder'; 'describes Gerda as "an effete and loathed sissy"'; 'dripping with sarcasm'; etc.). This, frankly, does look like vengeful action rather than a dispassionate presentation of the facts. Alfietucker ( talk) 20:46, 9 September 2013 (UTC)
I should not have backed off on Kleinzach, who was the worse offender, but I only have 24 hours in a day, and because everyone was saying the poor Kleinzach wasn gone and didn't have the ability to defend himself, I backed off on him more than I should, probably. I'm not saying that I'm backing off on Smerus, only that if Gerda feels he was the lesser problem and she believes that she can work with him, I have respect for Gerda's views on the matter. Gerda is not the "offender" in any of this, my view is that if Gerda is "admonished," then those on the other side should be equally admonished for their behavior. Montanabw (talk) 22:46, 9 September 2013 (UTC)
"I'm not saying that I'm backing off on Smerus...Gerda is not the "offender" in any of this, my view is that if Gerda is "admonished," then those on the other side should be equally admonished for their behavior." Since when did two wrongs make a right? Alfietucker ( talk) 22:53, 9 September 2013 (UTC)
"[X] really should not scoot out of this scott-free. They DID exacerbate the situation! [Y]". X<Y. And while I appreciate any "aid and comfort" offered, particularly in the face of egregious personal attacks, only I am responsible for the choices I make to accept invitations and act on concerns. Nikkimaria ( talk) 04:25, 8 September 2013 (UTC)
No, Nikki, X=Y or X>Y. If you get smacked for what you did, (and I have already made my comments on that issue, I have nothing more to add there) justice demands that the punishment fit the crime and all "offenders" be appropriately approached. Smerus, Kleinzach (and possibly others) certainly contributed to the mess and you should not be carrying that alone. Scapegoating someone as the sole offender is not justice, nor appropriate, particularly when, as noted here, you and Gerda actually were working stuff out between you. I consider the others with the "lalalalalalanoinfoboxevereverever" attitude to be the far greater problem here. At most, you had a few bad days where you started stalking edits and lost your usual good judgement. They have a longstanding premeditated ownership problem. That's a much deeper concern. Montanabw (talk) 19:12, 9 September 2013 (UTC)
"your actions increasingly appear to be driven by some kind of vendetta". Driving Smerus (one of our best classical music editors) off Wikipedia is not enough. After all, Smerus and Kleinzach messed with core members of WP:QAI and must be punished. I have a strong suspicion they aren't the first to receive this kind of treatment. -- Folantin ( talk) 09:21, 8 September 2013 (UTC)
Folantin, you and I agreed to a truce on discussing one another's behavior and your QAI conspiracy theories. As we agreed, you struck some of the things you said, particularly about me, and I struck my concerns about you. So let's just keep that hatchet buried. Your stirring the pot was not calming down the situation. If you really want to crank this up again, though, be aware of the WP:BOOMERANG effect. Montanabw (talk) 19:12, 9 September 2013 (UTC)

I return to this after two days off, and again can't believe what I read above. I - a core QAI member - ask for Smerus, a colleague with whom would like to continue working and who accepted a comprise solution on Symphony No. 1 (Sibelius), to not be admonished/restricted. I had no problem with his arguing, minding only one term. Is anything not clear about this? -- Gerda Arendt ( talk) 12:22, 8 September 2013 (UTC)

I don't think Smerus should be sanctioned to any greater degree than you, Gerda. And I don't think you should be sanctioned at all. But if they are going to treat you like the villain, then the eye needs to be focused on all players equally. However, if left alone, you three would have worked things out between yourselves, but others were not going to allow the sacred ground of the classical music wikiproject local consensus to be altered and were more than willing to bully, intimidate, snark and threaten anyone who challenged the status quo. So really. Montanabw (talk) 19:12, 9 September 2013 (UTC)

Pigsonthewing and Joseph Priestley

I'd just like to highlight what Ruhrfisch wrote above: "Please also see Pigsonthewing adding an infobox to Joseph Priestley with the fairly misleading edit summary "template" ( diff). I reverted it, citing WP:BRD and the previous consensus not to include an infobox ( diff). I then opened a discussion on the talk page where I linked to 4 of the 6 archives where infoboxes are discussed (there is also clear consensus against a box from late 2011 on the current talk page) here and was told by Pigsonthewing "I note that you dismiss my addition of an infobox without making any arguments against it" (which he had not even labeled as an infobox on adding it to the article)."

This shows Andy Mabbett's persistence. I remember bringing up evidence of his warring on the very same very article in the Pigsonthewing2 Arb Case back in 2007 [144]. If it wasn't obvious already, this is why the previous Arb Cases are relevant to this one.

If Mabbett isn't sanctioned properly, we can expect more of the same. -- Folantin ( talk) 15:00, 8 September 2013 (UTC)

Dance

You read it on the Main page: ... that when rehearsing Dvořák's Eighth Symphony, conductor Rafael Kubelík said: "Gentlemen, in Bohemia the trumpets never call to battle – they always call to the dance!"?

  • I recommend a closer look at the above mentioned "six more infobox discussions were initiated on article talk pages by the parties involved here during these proceedings", six diffs provided. Yes, I started a few, not for battle, but to see if we can actually argue in decency, as a model for future discussions. I inserted an infobox for Götterdämmerung, for example, - it was reverted and discussed, - have a look what the parties did and if there is anything in it that requires restriction. (I confirm again that I will not add an infobox to another opera, it's enough.) The infobox on Peter Warlock was added by none of the parties. The following discussion reads to me as if the principal author was ready to accept a short infobox. The two discussions on Verdi and Das Liebesverbot were started as part of the arbcom case and only taken to the respective talk pages. Rigoletto was started before the case. Siegfried (opera) was a suggestion on the talk page, a very short eye-opening discussion which I actually enjoyed for literary skill displayed. Don't miss it.
  • I am by now bold enough to recommend a closer look at a diff that was at one point given as a reason to ban Andy. He moved an existing infobox from the bottom up to the top and uncollapsed it. He did that in an article written by me where I wanted an infobox. - Looking at his contributions in 2013, I don't see a reason to restrict him, - what do I miss? -- Gerda Arendt ( talk) 06:32, 9 September 2013 (UTC)
  • I recommend a look at the top of my talk: links to several articles, including the symphony mentioned above which has an infobox shaped after the 2007 Buckner model, and some of Andy's recent article work. Enjoy, -- Gerda Arendt ( talk) 06:32, 9 September 2013 (UTC)
Gerda, a couple of points. The constant reference to Main Page material (and recent article work) is becoming rather wearisome. There is really no point constantly emphasising that and using DYKs (or other Main Page content) as examples. Main Page content is good, but it doesn't have a special or hallowed place on Wikipedia. Things appear on the Main Page only briefly, and far more important is long-term stability and quality. Quoting a DYK hook in an attempt to recast a battle as a dance is distracting and annoying. If you want to say that you think this area should be less a battle and more an area for calm discussion, then just say that without dressing it up as a dance.

I am sure many of the discussions associated with infoboxes are fascinating, but at the end of the day are they really productive and useful? Can you see that some people think that the amount of time and effort that goes into them may outweigh the benefits? Why do people spend so much time on the details, when there is so much other (arguably more productive) work that can be done on Wikipedia? Some people like discussing things like infoboxes, but people have differing tolerance levels: some would like to get back to doing other things, while some seem quite happy to spend weeks and months (even years) discussing infoboxes over many articles (essentially specialising in infoboxes). Can you see how that can end up being be a problem? Imagine this amount of discussion over a category, an article title, an image, the balance of the lead section, the precise wording used at any point in the article itself, or even the quality of the sources used (or not used).

Those discussions do happen (and people do 'specialise' in category work and article title discussions - not always terribly productively in my opinion, but that is their choice), but like the discussions over infoboxes, they need to be focused and not overwhelm the other work that needs doing. My inclination when something is disputed is to recognise that fact and consciously attempt to minimise the impact discussions can have on others, plus (and this is critical) focusing on improving other aspects of the article before even considering returning to previous discussions. If things show no sign of improving after this case, it is extremely likely that those mentioned in the decision (if they continue to contribute to the overall deterioration) will face further sanctions later on, such as topic bans or even site bans. Those named in this decision absolutely need to step back and let others have their say in the post-case discussions. Please consider that. Carcharoth ( talk) 08:11, 9 September 2013 (UTC)

  • I can speak only for myself. I repeat that I don't add infoboxes to "contentious" Classical composers unless they are "my own". I repeat that for articles on operas and Classical music, I stepped back from adding infoboxes and starting discussions on talk pages, unless they are "my own", as this symphony. I confess that I would prefer to see more consistency, all symphonies treated similarly, or at least those by one composer, but will spend no time fighting for that. I hope that consistency may be an aspect in future thoughts on the topic. - I would have chosen a different word than "dance", but could not change a quotation ;) -- Gerda Arendt ( talk) 09:47, 9 September 2013 (UTC)
  • Gerda, first of all, please note that I'm speaking only in my personal capacity, but would you be willing to enter a gentlemen's agreement under which, for the moment, you accept to refrain from adding infoboxes to single articles, with the exception of those you start, until a better guideline regarding infoboxes is adopted? Salvio Let's talk about it! 11:59, 9 September 2013 (UTC)
  • I offered above my way to avoid conflict. Why would you think the project wins if I stop adding infoboxes in the estimated 95% of articles where an infobox is the normal thing to have? (Not that I would have time for it, just curious.) -- Gerda Arendt ( talk) 22:14, 9 September 2013 (UTC)

Time to close

Isn't this whole case now rather going around pointlessly in circles? The Arbcom has accepted and established, that which most of us already knew: infoboxes are not mandatory. Furthermore, the Arbcom has established, again what most of us already knew, that certain editors (one in particular) have been vehemently arguing and trying to impose infoboxes on pages against consensus and policy and in doing so, causing disruption. Arbitrators are now themselves becoming guilty of deviation and in danger of exceeding their remit.  Giano  09:14, 9 September 2013 (UTC)

They should probably dot their i's and cross their t's, though. Gerda Arendt restricted (2) and Smerus prohibited are now both marked in the implementation notes as "cannot pass", but each has 5 supports, 5 opposes, and no abstentions. User:Roger Davies's previous votes have been struck but he has not "re-voted" in either of them. Voceditenore ( talk) 11:30, 9 September 2013 (UTC)
Roger's votes were struck not because he changed his mind, but rather because he went inactive. Salvio Let's talk about it! 11:47, 9 September 2013 (UTC)
Ah. Thanks for that explanation. Best, Voceditenore ( talk) 11:57, 9 September 2013 (UTC)
(ec) I don't think it's time to close as long as the proposed "remedy" for Andy ("Pigsonthewing is indefinitely banned from adding, or discussing the addition or removal of, infoboxes.") would prohibit him from adding an infobox to "his own" articles, such as Francis John Williamson and Selly Manor. -- Gerda Arendt ( talk) 11:51, 9 September 2013 (UTC)
Well he should have thought of that before he caused all this trouble. If there was any sensible justice in the world, he would be be completely banned and therefore not writing anything at all. He should count himself lucky that he's not.  Giano  11:53, 9 September 2013 (UTC)
I happen to like his writing, this edit especially, -- Gerda Arendt ( talk) 12:01, 9 September 2013 (UTC)
( edit conflict)Gerda, as far as I'm concerned, Andy is getting off lightly, here; however, having caused enough disruption wrt infoboxes, it's best if he keeps as far away from the topic as humanly possible without exceptions. So, no, I would oppose authorising him add infoboxes to "his own" articles.

Also, as a side note, in the spirit of patti chiari, amicizia lunga, as they say in Italy, (which means "clear understanding breed long friendships", by which I mean that I'm not assuming bad faith of you or anyone else, but just want to make this clear to avoid unpleasant surprises for anybody), if Andy was to ask another editor to add an infobox to an article on his behalf, that may be construed as an attempt to game the restriction and may lead to sanctions. Salvio Let's talk about it! 12:08, 9 September 2013 (UTC)

Here you are, Gerda, encouraging people to go arownd and arownd in circles again. We are not discussing the quality of Andy Mabbitt's writing - that is not the issue. This case is about the hectoring and bullying that has surrounded the implementation of infoboxes against policy. That has been proven. Now it would help this case enormously if you and others would try and stick to the relevant facts of the case.  Giano  12:12, 9 September 2013 (UTC)
Giano, "it's the irrational hatred of a clique of editors" as noted below that IS the relevant facts of the case and what got us here. Not Gerda. She is the person who was hectored and bullied. Can't anyone understand that? Montanabw (talk) 19:36, 9 September 2013 (UTC)
You need to make very sure there is no leeway for Mabbett to game the sanctions. You also need to make sure you have the stamina to enforce them - please, Arbs, no offloading the responsibility for enforcement onto the shoulders of some poor admin who will be mobbed by Mabbett's fan club. As far as I'm concerned, Mabbett's already tried a breaching experiment with his addition of an infobox to Joseph Priestley, as noted in the section above. I predict more of the same, unless he's properly supervised. -- Folantin ( talk) 13:05, 9 September 2013 (UTC)
Folantin, there is no cabal, and they are not after anyone. Drop the stick, please. Montanabw (talk) 19:36, 9 September 2013 (UTC)
Sorry, I don't understand "implementation of infoboxes against policy" (there is no policy against them) and "mobbed by Mabbett's fan club". Everybody can check Andy's edits, no? Many will. -- Gerda Arendt ( talk) 13:38, 9 September 2013 (UTC)
Gerda, as you well know, it's not policy to enforce an infobox: Mabbett frequently wandered in off the street and dictatorially tried to impose them - that's against policy. While your loyalty to Mabbett is to be admired - you really need to accept that he was in the wrong behaving as he did.  Giano  18:18, 9 September 2013 (UTC)
I thought I had said more than enough but you addressed me personally. So, as gently as I can (imitating the ways of the sadly missed George Ponderevo) I ask as I asked consistently since the beginning of the case: when did Andy add an infobox to an article that was meant to be infobox-free and behave "dictatorially" (however you would reference that term)? You have experiences from a past that I don't share, but the last time I observed him adding an infobox, followed by a long discussion was Cosima Wagner, 25 December 2012 (Please note that the lady isn't even a classical music composer.). What I observed now (see below) is add, make one comment and walk away, see below. I trust that he can do it from now on, that's all. -- Gerda Arendt ( talk) 06:59, 10 September 2013 (UTC)
Not to preclude any answer Giano might provide, but I have to say my very first encounter of Andy here totally chimes with what others, including Giano, have said about his dictatorial behavior. On Talk: Peter Warlock Andy suddenly appeared, intervening in what appeared to be a reasonably civil if candid exchange between Smerus and another editor, who had just posted "I consider myself wrist-slapped. Sorry." Andy's very first comment was: "Don't. Smerus is bullshitting. "no infobox should be added without a formal justification" is utter bunkum." I should add that Andy had latched onto a phrase of Smerus's, which in context has a quite different flavor: "I considered tinkering with the added infobox to remove the irrelevant information included in it. However, on further consideration I believe that, as this article obtained FA status (the highest classification possible for a WP article), no infbox should be added without a formal justification and evdience that it improves the article." i.e. Smerus meant no more or less - it seems clear to me - than anyone wanting to add an infobox should present a written justification for doing so and demonstrate "that it improves the article". Furthermore, Smerus had indeed, as I'd seen from the edits on the article, attempted to improve the content of the infobox before deciding - quite rightly in my opinion - that the infobox was a poor introductory tool for this particular article.
Anyway, Andy proceeded to edit-war over the info box, twice reverting within 70 minutes to reinstate it without offering any justification, and only desisting when a *third* editor (neither Smerus or myself) intervened and removed the infobox. If anyone cares to check the talk page, they will see that - quite apart from my being offended by Andy's rude appearance and attitude - I actually went over the objections Smerus had raised against the box, pointing out that he had at least tried to make it work, whereas Andy by contrast offered no argument or attempt to demonstrate the efficacy of the box but was, as I said at that time, "imposing the infobox for no stated reason whatsoever". I wrote this based entirely on what I had seen him write on that talk page (I've just checked, and that was absolutely his first post there), and his edits on the article. Andy continued to refuse to answer any points either Smerus or I had raised about the article and the infobox, but simply brandished the straw man he had made - i.e. his selective quotation from Smerus.
I have since understood there was a past "history" between Andy and Smerus. Still, that does not excuse Andy's behavior on that (still quite recent) occasion. Alfietucker ( talk) 07:39, 10 September 2013 (UTC)
You describe your perception well, and everybody interested can follow the discussion. You might have mentioned that Andy had not added the box, - we were talking about "wandered in off the street and dictatorially tried to impose them". (I think I mentioned already somewhere that I don't mind bullshit here, bollocks there. Telling someone - possibly a user who never heard that an infobox can be a problem and who felt "wrist-slapped" by a revert: "don't" [feel wrist-slapped], - how do you describe that?) You might have added that the further discussion with the main author (Smerus had made only one edit before) reached acceptance for a shorter infobox. This - discussing the content (!) of the infobox - could have been achieved without a revert. The only reason why an infobox is not in the article seems to be that the author is waiting for " less volatile times". I wish him patience. -- Gerda Arendt ( talk) 08:24, 10 September 2013 (UTC)
I'm aware of what was being discussed. In the Peter Warlock instance Andy certainly "wandered in off the street and dictatorially tried to impose" an infobox: the fact he was not the original author is not the issue; what is relevant is that he twice reverted within 70 minutes to keep it there, which *was* an imposition (and disregarded BRD), and the fact he refused to offer any explanation to justify this makes his actions dictatorial. I'm afraid Giano's description of Andy's behaviour matches this case fairly exactly. Alfietucker ( talk) 08:43, 10 September 2013 (UTC)
I don't think it's a coincidence that Mabbett chose Joseph Priestley at this particular time.-- Folantin ( talk) 14:46, 9 September 2013 (UTC)
There is already talk of gaming the system (or not gaming the system) here]. My view is that Andy Mabbett's continued presence will be disruptive by its very existence. How will we know that infoboxes are not being added by his many 'students of Wikipedia' and what influence will he exert as Wikipedian in residence (the Wikipedian in Residence at Queen Street Textile Mill Museum, Burnley; also the Wikipedian in Residence at The New Art Gallery Walsall; Wikipedian in Residence at Staffordshire Archives and Heritage Service (winter 2012/2013) and Wikipedia Outreach Ambassador). If he's allowed to remain a 'Wikipedian', the whole thing is unpoliceable.  Giano  13:19, 9 September 2013 (UTC)
The difficulty of monitoring infoboxes added by 'students" would by just the same even if he was banned. Now I - in a way a student - restricted myself, will not infoboxes for opera and classical music other than "my own". But for a building such as Selly Manor: where's a problem with a 'student' adding an infobox? Then why not allow the author to add it himself? -- Gerda Arendt ( talk) 13:38, 9 September 2013 (UTC)
Gerda, you really are not getting it are you? The whole point of this case seems to have passed you by in some sort of fluffy cloud of cotton wool. I shall say no more and leave it to the Arbs to see that this case needs wrapping up tightly before we are all suffocated by any more thick fog.  Giano  13:43, 9 September 2013 (UTC)
Giano, you have just exemplified the locus of this dispute. It's not the infoboxes, it's the irrational hatred of a clique of editors who are so vehemently opposed to the great unwashed editing "their" articles that they feel it gives them the right to talk to other editors like something they just stepped in. This is an encyclopaedia built by collaboration, and no editor has the right to take the sort of tone your posts above take with Gerda. There is no need for it, and its only purpose is demean other editors, so kindly knock it off. I'm not going to sit here and defend Andy—he knows his conduct has been unacceptable and it's up to him to see the error of his ways—but nothing he or any of the pro-infobox crowd have done gives you license to attempt to patronise and demean Gerda or anybody else like that. I'm firmly of the belief that if both sides stopped stopped bickering like children and stopped trying to get one-up on each other, you might actually find some common ground. HJ Mitchell | Penny for your thoughts? 17:39, 9 September 2013 (UTC)
👍 Like You got it in one, HJ. That is EXACTLY what I have been trying to explain all along! Montanabw (talk) 19:36, 9 September 2013 (UTC)
  • This case would have been simply and quickly resolved if people were capable of (and advised)to sticking to relevant facts. Instead we have had millions of words going of at tangents. You say, User:HJ Mitchell, "Andy knows his conduct has been unacceptable" - well you seem to be the only person who has spotted that amid the huge smokescreen of waffle that's been created. So don't you come here preaching like some puritanical Sir Gallahad telling us what we all should have seen and how to behave because you appear to be alone in your observations.  Giano  20:08, 9 September 2013 (UTC)
  • I don't think HJ Mitchell is all that alone in how he believes people should be behaving, Giano. I've found your comments to be consistently derisive too. As for Andy, HJ is not alone there either. Several people, including arbitrators, have acknowledged Andy's own acknowledgment that his behavior needs improvement. equazcion (talk) 20:16, 9 Sep 2013 (UTC)
  • Drowning people invariably learn to swim a few strokes before they sink for the third time - and I believe it will be Andy's third time. I admre your faith and trust, but really its naivety is worrying.  Giano  20:21, 9 September 2013 (UTC)
  • I don't have any trust or faith. It's not myself who thinks Andy will get better. I don't know anything about him and have no experience with him. But you said HJ was alone in his observations, and I just wanted to correct you. equazcion (talk) 20:25, 9 Sep 2013 (UTC)
  • ".I don't know anything about him and have no experience with him" Then why on earth are you here? Sitting like a little old woman knitting at the foot of the guillotine.  Giano  20:28, 9 September 2013 (UTC)
  • I'm here because I wanted to refocus a little of this case on the larger underlying issue, and suggested a proposed decision recommending a community RfC, which was subsequently added and passed. I may not know anything about the involved parties prior to this case, but solving the greater issue interests me. Some of us do make appearances in the interest of something other than interpersonal drama. equazcion (talk) 20:33, 9 Sep 2013 (UTC)
"Andy knows his conduct has been unacceptable". His addition of an infobox to Joseph Priestley on 2 September would suggest otherwise, especially given the history of his prior involvement in that article. -- Folantin ( talk) 20:36, 9 September 2013 (UTC)
Andy's friends are currently bestowing him with the gifts of humility and remorse that his actions don't seem to portray. Throughout this has been a strong theme of the case - I wonder if the Arbs are clever enough to see through the fog and cotton wool. Time will tell.  Giano  20:42, 9 September 2013 (UTC)
So people who don't know Andy shouldn't be commenting here, and anyone who supports him must be his friend. I have to say, Giano, without being privy to this conflict, if I had to ascertain who might be most responsible for its escalation, you'd be at the top of my list, based on what I'm seeing on this page. It's a shame the case is nearly concluded without a decision regarding you, as I have a feeling your continued involvement in infobox issues will cause continued problems. equazcion (talk) 22:57, 9 Sep 2013 (UTC)
You can't base a judgement on this case only by what you see on this page, that's the point. Smeat75 ( talk) 00:59, 10 September 2013 (UTC)
As you say, Equazcion, you are not privy to this conflict. Were you informed on this subject, you would be aware that Mabbett and I have only come into contact when you has wandered off the street onto pages where I have been a significant editor (note: I do not say my pages) on one occasion I would go as far as to say he was provocatively trolling a page. I have frequently declined to comment on his edits to musical pages because, while I sympathise, I have not edited those pages. However, My advice to Mr Mabbett is if you don't want trouble don't go looking for it. Like most editors here, I woudl quite like a quiet life without being ordered and dictated to by misinformed editors who have already been banned twice (without any help from me) because of their behavior on this subject.  Giano  06:11, 10 September 2013 (UTC)
Well, this is the crux of the conflict, is it not? My understanding is that the way "significant" editors react when someone from "outside" comes along to make changes is central. Referring to the them as "coming in off the street" and "looking for trouble", etc, is the stance from the involved parties in opposition to Andy, rather than being some special circumstance that precludes your being referred to as involved. equazcion (talk) 06:22, 10 Sep 2013 (UTC)
I can see that this is very difficult for you to grasp. Let me try to explain it simply: Arriving on a page upon which one has never edited (but is often still in progress by a group of dedicated and knowledgeable editors) and then making major changes without at least minor consultation is at the least extreme bad manners, at worst disruptive. When the dedicated and knowledgeable editors unanimously reject Andy's changes, he edit wars and causes trouble and distress. Often he plonks his infobox on a fully formed page which has attained or is attaining GA or FA status (again without consultation) and then wanders off and expect others to maintain it. That this causes resentment and anger is hardly surprising. Your "crux" of this matter is that Mr Mabbett is the architect of his own misfortune and attempts by his supporters to try and shift the blame are misguided.  Giano  06:41, 10 September 2013 (UTC)
Allow me to make my stance easier to grasp as well: I'm more than aware of your stance and who you think is to blame. That's not in contention at the moment. Perhaps Andy has acted inappropriately, or perhaps not -- I wouldn't presume to know this without delving deeper into several page histories. Your own manner in dealing with it, if the comments on this page are any indication, tells me it is likely that he is far from the sole reason this conflict has escalated to an arbitration case; and I suspect the conflict will survive any measures implemented against him if you continue to act in the future the way you are here. equazcion (talk) 06:51, 10 Sep 2013 (UTC)
  • I rather think you will find, if you bother to research before further commenting, that compared to the long term trouble that Mr Mabbett has caused others, my involvement with him has been minimal. In fact, I have often felt guilty for not doing more to support the many beleaguered musical editors who have suffered from his behavior. However, my own personal view is that editors should not become involved in pages about which they know nothing. This is a public page, so it is right that all who have experience of the subject can bring their grievances here - providing they understand what they are talking about. It seems to me that you belong to a class, once known as the Peanut Gallery. I suggest that you read up before commenting further.  Giano  07:58, 10 September 2013 (UTC)
I'm commenting on your behavior on this page, Giano, which I'm equipped to do, having been involved here and read the entire thing. You're free to dismiss me using whichever personal criteria you deem acceptable, although I seem to not be alone in my assessment, among at least one person who does appear to meet your criteria. equazcion (talk) 08:06, 10 Sep 2013 (UTC)
You are actually wasting time and space by deliberately deviating and obscuring with hot air; so I shall cut off your oxygen and not engage further here with you.  Giano  08:10, 10 September 2013 (UTC)
I don't think this exchange has deviated from the point, and I don't have any interest in wasting time (I'm not sure what possible motivation I would have in doing so deliberately). If most of the people here have come in order to assess the conflict from a user behavior standpoint, I think this is a rather relevant discussion, even though it's not my own primary reason for being here. Your responses here have demonstrated that you handle disagreements by responding derisively, resorting to name calling and attempting to "score hits", as they say; quite the opposite of attempting to defuse the situation. I do hope this is a unique result of my somehow having inadvertently pushed your buttons (if so, I do apologize), and I similarly hope this isn't how you normally engage those with whom you have disagreements. If this is how you've been handling infobox conflicts, then I think something needs to change there if the matter is to progress better in the future. equazcion (talk) 08:27, 10 Sep 2013 (UTC)

@ Salvio and Hahc21, since Roger Davies is now listed as inactive, shouldn't all of his votes have been struck? I notice that his "oppose" at Pigsonthewing banned remains. Not that it makes any difference to the outcome, but there should be an accurate record of how the final vote was split. Voceditenore ( talk) 13:45, 9 September 2013 (UTC)

That was just an oversight, which I have just corrected. Thanks for pointing this out! Salvio Let's talk about it! 10:13, 10 September 2013 (UTC)

Request clarification re "Editors reminded" section

I would still like arbitrators to clarify, preferably in the decision itself, what exactly is meant when it says "All editors are reminded ....to avoid turning discussions about a single article's infobox into a discussion about infoboxes in general" which would seem to me to mean that any discussion of "metadata" or machine readability or wikidata etc should never be introduced into discussions about whether a specific article should have an infobox or not as that is exactly an issue "about infoboxes in general". Thanks Smeat75 ( talk) 02:14, 10 September 2013 (UTC)

This is similar to the point I made on 3 September: " . . . If centralized discussions of key aspects of “infoboxes in general” have never taken place, then that avoidance will be difficult, if not impossible, to achieve.". So I support Smeat75's call for clarification. Klein zach 03:32, 10 September 2013 (UTC)
The way I read it, the principle invites editors to discuss each case on its merits, i.e. why an infobox would be a good or a bad addition to the article in question. This may include references to metadata and machine readability.

In my opinion, this remedy was only meant to indicate that generalisations such as "infoboxes are always good, no article should go without one" and its opposite "infoboxes are the worst thing ever" should be avoided at all times. Salvio Let's talk about it! 10:22, 10 September 2013 (UTC)

"A discussion about infoboxes in general" is not quite the same thing as "a generalisation about infoboxes". Arguably generalizations are always bad . . . . but in reality the arguments have related to specific templates rather than individual articles, e.g. the use of Infobox musical artist for classical composers, so they haven't normally been about infoboxes in general, or about individual articles either. Klein zach 12:07, 10 September 2013 (UTC)
"infoboxes are always good" because they emit metadata, etc., is just what has been said in hundreds of these arguments which, if anything is going to change, should not be acceptable any more in discussions of specific articles, in my opinion. Smeat75 ( talk) 13:11, 10 September 2013 (UTC)

What this case is about: The right to say no (and have it stick)

Many of our basic rights can be expressed as a right to say no. An election allows voters to say no to the candidates or leaders they do not want. Free speech is the right to disagree, to say "no, that is not what I think". Many protections of a civil society involve the rights of minorities to say no to the majority (no, children cannot work in factories; or no, you cannot enslave others; or no, you cannot stop me from voting, etc.).

On Wikipedia, ALL of the Five Pillars can be seen in some way as rights to say no:

What Wikipedia is not (No to all things not encyclopedic);
Neutral point of view (No to bias);
Wikipedia is free content (No to payment for or restrictions on use and re-use)
Civility (No to offensive language, no to ignoring the positions and conclusions of others, and no to attacking others)
Ignore all rules (No to any rule that prevents you from improving or maintaining Wikipedia)

As far as infoboxes go, WP:INFOBOXUSE says in part "The use of infoboxes is neither required nor prohibited for any article. Whether to include an infobox, which infobox to include, and which parts of the infobox to use, is determined through discussion and consensus among the editors at each individual article." To me that says that editors have the right to say no (on occasion) to infoboxes. This applies to all sorts of articles, not just classical music. So Waterfalls in Ricketts Glen State Park and Horse Protection Act of 1970 and British military intervention in the Sierra Leone Civil War are all FAs and none of them have infoboxes, and that's OK.

I am not against infoboxes, per se (and most of the aticles I've nominated at FAC have a box of some sort). I am against any "one size fits all" solution, and I am in favor of editors having the right to say no to an infobox. I am also in favor of decisions being decided by consensus, and then allowed to stay that way. Let it stick, and don't bring it up over and over and over and over and over again ...

This is the last thing I plan to say about infoboxes for the next three months.1 I invite everyone to take a break, think things over, and hopefully let things calm down. Ruhrfisch ><>°° 02:33, 10 September 2013 (UTC)

1If someone adds an infobox to an article on my watchlist without one, I reserve the right to discuss it there, or to comment on a RfC on this topic.

  • Very reasonable and well expressed - I agree. Alfietucker ( talk) 06:56, 10 September 2013 (UTC)
  • This should form part of the Decision. I've yet to read a better expression of the moderate infobox-sceptic position. Klein zach 00:39, 11 September 2013 (UTC)

Include infoboxes in new articles which they create

"They may ... include infoboxes in new articles which they create." is a clause in the planned restriction for me, and I can live with that. This clause is still not in one of the restrictions for Andy. please think about it. Philosopher, with a background of law, noticed this ( see above, "My only thought was that since this is about conflict between users, a restriction where there was only one user would be irrelevant."), improved wordings were suggested by Mackensen, supported by SchroCat.

I support that Andy may add infoboxes to his own new articles.

  1. -- Gerda Arendt ( talk) 10:41, 10 September 2013 (UTC)
  2. -- I would agree. -- ColonelHenry ( talk) 13:16, 10 September 2013 (UTC)
  3. Support, Though I think my modification of Mackensen's proposal above is better still. He would not be able to revert or argue against any subsequent removal so there is no risk of extended argie-bargie. Johnbod ( talk) 14:19, 10 September 2013 (UTC)
    @Johnbod: I agree that your version is better, also Mackensen's proposals. This is more an idea than a specific wording. -- Gerda Arendt ( talk) 14:27, 10 September 2013 (UTC)
  4. I'm going to go out of my way and AGF here, with some additional criterion: articles which Andy has personally started (first edit) and the infobox may only be included in that first edit. —  Crisco 1492 ( talk) 16:01, 10 September 2013 (UTC)
  5. I'd support; also if I were to create an article and ask Andy to help me, I'd sure prefer that optionL there are dozens of wikiprojects where infoboxes are standard operating procedure and the local consensus is to encourage them; more than not, in fact. Is there any project other than the classical music ones that have such an anti-infobox position? (Wondering) Montanabw (talk) 17:02, 10 September 2013 (UTC)

I support Andy having nothing to do with infoboxes whatsoever anywhere.

  1. --  Giano  15:11, 10 September 2013 (UTC)
  2. What Giano said. I can already guess how this concession might be gamed. -- Folantin ( talk) 15:20, 10 September 2013 (UTC)
    I can't - how? Johnbod ( talk) 16:05, 10 September 2013 (UTC)
Well, I should be careful of WP:BEANS, but one way would be the creation of dozens of stubby one- or two-line articles in certain subject areas, just so those pages can have obligatory infoboxes. -- Folantin ( talk) 16:17, 10 September 2013 (UTC)
Which anyone not restricted can remove without comeback. I think this is pretty far-fetched, and would it be the end of the world? Johnbod ( talk) 16:28, 10 September 2013 (UTC)
I'm afraid that I agree with Folantin, John, as you say anyone could remove infoboxes that Mabbett inserted; his pages would become a playground for trolls and anons and cause even more trouble. Personally, I would keep a lot of spave between me and any page he created, but you know what Wikipedia can be like....  Giano  08:09, 11 September 2013 (UTC)
Comments by ColonelHenry

If Andy creates an article, he should be able to add whatever he wants by way of infoboxes, templates, widgets, whatever. Telling an editor "you can't do this" when other editors can violates the spirit of Wikipedia. Personally, even though I'm not a big fan of infoboxes, a good infobox is a benefit to an article. Where the infobox is lacking, I can understand the desire some editors in deciding against adding one. But it is nonsensical where there's a net improvement to article to avoid adding one. I wish the infobox policies on Wikipedia would change...especially in the classical music area. Infoboxes should be on a case by case basis (balancing the informativeness of infobox with the needs of the article), there shouldn't be any blanket edicts banning them by either a WikiProject or a well-organised clique of determined editors intransigently insisting one way or the other irregardless of the facts or rationale. Further, I don't see the point of irrational arbitration cases giving edicts of "thou shalt not add infoboxes." A dictum of "we're not going to provide infoboxes because the information's already in the article" doesn't address all users....while I like reading the articles, I have to acknowledge that 90% of readers give an article 30 seconds despite our best efforts and useless arguing. And penalizing Andy for improving an article is a ludicrous position just because someone is vehemently anti-infobox. Apparently, I wouldn't be surprised the same people who refuse editors to classical music articles the freedom to choose whether or not to infobox are probably listening to Shostakovich and know Stalin denounced him for exercising freedom in creating and almost silenced him over insistence on similar bullshit. -- ColonelHenry ( talk) 13:16, 10 September 2013 (UTC)

I'm confused; was Shostakovich for or against infoboxes? -- Michael Bednarek ( talk) 13:34, 10 September 2013 (UTC)
( edit conflict)Rather *against*, I'd say. Seriously, though, if we're going to evoke Stalin it could be argued with more pertinence that those who insist on infoboxes being inserted in an article - against the wishes of those editors who are familiar with the subject - are rather like Stalin insisting that every artist should work within the aesthetic of Socialist Realism. More to the point, isn't it usually argued (by Gerda, for instance) that infoboxes are *not* meant to be, and cannot be, a 30 second summary of an article? It's precisely your confusion on this matter which adds grist to the mill to those who are concerned that infoboxes, rather than enhancing, can short-circuit an article: i.e. you've just demonstrated the mindset of those readers who think all they need to crib up on the subject is to read the infobox, rather than the lead/lede which demonstrably - when well written - does that job much more efficiently. Alfietucker ( talk) 13:37, 10 September 2013 (UTC)
You called me: what do you think I argued? Summary not of the article, but key facts? Yes. Any time in seconds given? No. - I believe an infobox serves an article like a cover a book, but I don't insist, and I respect the wish of a main author, even if I don't understand it. - Yesterday I was pleasantly surprised seeing the main author of Peter Warlock experimenting with an operatic infobox, - if a new era begins with a small step, I can easily leave the scene ;) -- Gerda Arendt ( talk) 13:58, 10 September 2013 (UTC)
I was responding to the implication of "ColonelHenry's statement: "A dictum of "we're not going to provide infoboxes because the information's already in the article" doesn't address all users....while I like reading the articles, I have to acknowledge that 90% of readers give an article 30 seconds despite our best efforts and useless arguing." Sorry, I didn't mean to misrepresent your argument - I guess I should have written something like "infoboxes are *not* meant to be, and cannot be, a summary of an article ("30 seconds" or otherwise)". My point - about the evident danger of readers treating infoboxes as a "crib" for an article - still stands. Alfietucker ( talk) 14:11, 10 September 2013 (UTC)
(Aside: Actually, the Stalin page is a brilliant demonstration of the uselessness of biographical infoboxes. The box contains tons of trainspotterish information while completely failing to get to the essence of the man's "achievements" (Ukrainian famine or Great Purge, anyone?). I think I've already mentioned Adolf Eichmann as another example of the box's ability to miss the point in a crashingly offensive, anal retentive way). -- Folantin ( talk) 15:33, 10 September 2013 (UTC)
Nazi Germany and Adolf Hitler are further gems in this respect. Johnbod ( talk) 16:31, 10 September 2013 (UTC)
"Actually, the Stalin page is a brilliant demonstration of the uselessness of biographical infoboxes." - I think this is too general. If one box is bad, it doesn't demonstrate the uselessness of others. If one is bad because the wrong parameters were chosen and filled badly, it can be discussed and adjusted on article level. If the template doesn't provide the right parameters, that can be discussed and fixed on the template level. We improved infobox book by providing wikisource in other languages, not only English, for example, and working on the publishing (next thread there), -- Gerda Arendt ( talk) 16:50, 10 September 2013 (UTC)
Oh great, Stalin and the Nazis. We've now invoked Godwin's Law. Sheesh. I love those biography infoboxes in general, the one for Stalin is a bit long and overdone, but "trainspotterish" info is helpful and often what people ARE looking for in the "cover" of the article (nice analogy, Gerda, I like it). Let's NOT start in on this in other wikiprojects, I beg you! Montanabw (talk) 17:09, 10 September 2013 (UTC)
Montanabw - just to politely point out, in case it's escaped anyone's notice, that Stalin was first evoked by one of the *pro* infobox supporters: make of that what you will. Alfietucker ( talk) 12:51, 11 September 2013 (UTC)
As I keep saying: it really is about time this case was closed.  Giano  17:15, 10 September 2013 (UTC)
It really is time to knock this on the head. -- Folantin ( talk) 18:12, 10 September 2013 (UTC)
Hmmm, given that they are waiting for a 24 hour stable consensus (people keep changing their votes), we can't quite get there, but perhaps as far as the wall of text on THIS page, where we non-ArbCom members have been debating forever and I doubt any minds have changed much, perhaps we finally have said something we can all agree on for this page, at least? Montanabw (talk) 18:32, 10 September 2013 (UTC)

Case is closing

A brief note to let those posting here know that the case is now closing. Please read what I said earlier above. There may be some more discussion at the arbitration noticeboard once the case is closed, but other than that, please let things calm down and allow people to work out in their own time what to do next (if anything). In particular, if any editors sanctioned in this case decide to seek clarification from the committee (at WP:ARCA), please give them time and space to do so by themselves without extraneous commentary. Carcharoth ( talk) 23:44, 10 September 2013 (UTC)

You keep telling us it's closing, but it never seems to. Viewing the Arb's voting is as thrilling as sitting in the middle row at the opera, desperate to go to the loo, and watching Tosca repeatedly trampolining above the parapet. Get a move.  Giano  08:16, 11 September 2013 (UTC)
I'm assuming this is now closed, given the parties have been handed final decision notices. My view: some promising points, but it's too early to tell. The real test will be whether this is enforced properly and what a certain editor decides to do with yet another last chance he has been given. Also, there's the question of whether Smerus returns to editing at some point in the future (let's hope so). I think we should have a moratorium on the infobox issue of, say, three months (I believe something of the kind has been suggested elsewhere on this page). Even that will be too soon.-- Folantin ( talk) 08:42, 11 September 2013 (UTC)
This user has autopatrolled rights on the English Wikipedia.
This user has file mover rights on the English Wikipedia
This user has pending changes reviewer rights on the English Wikipedia.
This user has rollback rights on the English Wikipedia.
From Wikipedia, the free encyclopedia
John Cline
Originally known as user:My76Strat


Userpage


Talkpage


Aboutme


Mypages


Myawards


Subpages


Openone


Mytools

Open discussions Information

Closed discussions Information

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


RfC for reviewer permission criteria

At Wikipedia:WikiProject Articles for creation/RfC Reviewer permission a consensus was reached to introduce a permission system for reviewers. The topics on what the permission threshold should be, and how it would be implemented, were deliberately left open.

  1. This RfC discusses suggestions for the threshold of experience for users to demonstrate that they are adequately versed in the policies and guidelines involved for an article that can exist uncontentiously in mainspace.
  2. This RfC does not discuss how this threshold will be granted and/or implemented. That will be the topic of a further discussion, when the threshold itself has been established.
  3. This RfC is not a vote. Participants are invited to discuss what would be a reasonable threshold. The closer will assess the outcome based on the discussion.
  4. Consensus has been reached for this permission, this RfC is not for rediscussing whether a permission is needed.

Background examples

  • Reviewer (Pending Changes Reviewer): Quick check to ensure edits don't contain vandalism, violations of the policy on living people, copyright violations, or other obviously inappropriate content. The threshold is deliberately low but Reviewers are not expected to be subject experts and their review is not a guarantee in any way of an error-free article. They are expected to have a reasonable editing history, distinguish what is and what is not vandalism, and be familiar with basic content policies.

Reviewer permission are specified as follows:

  1. You have an account, and routinely edit.
  2. You have a reasonable editing history – as a guide, enough edits that a track record can be established.
  3. You have read our policy on vandalism and understand what is and what is not vandalism.
  4. You are familiar with the basic content policies: Biographies of living persons, Neutral point of view, No original research, Verifiability and What Wikipedia is not.
  5. You are familiar with the basic legal policy: Wikipedia:Copyrights.
  6. You have read the guideline on reviewing.
Permission is granted by an admin.
  • Rollbacker: While there is no fixed requirement, a request is unlikely to be successful without a contribution history that demonstrates an ability to distinguish well intentioned edits with minor issues from unconstructive vandalism. Users with 200 edits (generally discounting those to their own user space) can apply for training to the WP:CVUA. Admins rarely grant the tool for less than a clear run of at least 100 reverts of clearly identifiable vandalism without errors. Significant experience is needed to identify the kind of edits that may not appear to vandalism at first sight e.g. inappropriate edits missed by the bots and abuse filters.
Permission is granted by an admin.
  • Stiki: The account must have either: (1) the rollback permission/right, (2) at least 1000 article edits (in the article namespace, not talk/user pages), or be approved after discussion with the developer.
  • Huggle: Requires rollback permission in order to function but does not otherwise have an approvals system.
  • AWB: Users must be added to a whitelist in order to use AWB. Only admins can edit the whitelist, and admins automatically have access. As a general rule, only users with more than 500 mainspace edits will be registered, and admins tend to only give access if a user has specified a task they want to use AWB for.

Discussion

Suggestion by Kudpung

  • I'll start the ball rolling here with a fairly low threshold. Having seen plenty of the kind of errors that are made by editors who review AfC, I suggest that the minimum should be based on candidates having the choice of satisfying either of these two criteria (but not a lower mix of each).
1. Must have both Reviewer and Rollbacker rights, and have demonstrated that they have used these correctly within a minimum of 500 mainspace edits, and a minimum of one month tenure.
or
2. Must have patrolled at least 200 pages at WP:New pages patrol without recent error and demonstrated that they are a) familiar with the tags and deletion criteria offered by the Page Curation Toolbar without error. b) made significant use of the 'message to the creator' tool.
3. Above all, candidates must have demonstrated that they understand WP:PROD, WP:AfD, and WP:Notability, and are able to interact with other users in a polite, friendly, and helpful manner.
Kudpung กุดผึ้ง ( talk) 02:25, 18 October 2013 (UTC)
Does Page Curation need to be singled out? Don't a lot of users do NPP with other tools, like Twinkle? I think you should refer to NPP-related tags and criteria in general. Also, I think reviewer/rollbacker would be fine with one-or-the-other, rather than needing both. Jackmcbarn ( talk) 03:21, 18 October 2013 (UTC)
NPP should only be done nowadays with the Special:NewPagesFeed which does not use Twinkle. There may be a few editors still using the old page feed, but that system has been redundant now for a long time. Kudpung กุดผึ้ง ( talk) 04:39, 18 October 2013 (UTC)
I happened to just ask Dragonfly67 on IRC the other day, and he doesn't use the curation tool... Not implying one way or the other whether or not he would want AfC reviewer (yes, I obviously realize as an admin it doesn't really make much difference), just wondering if someone like him that doesn't use page curation but has patrolled thousands of pages should really be excluded. TL;DR, I think that saying that curation tool use is a requirement of proper page patrolling is inaccurate. Technical 13 ( talk) 04:49, 18 October 2013 (UTC)
Ditto... I patrol off WP:SCV and #wikipedia-en-spam. What we are looking for are speedy deletion accuracy and PROD/AFD nominations getting deleted. MER-C 05:19, 18 October 2013 (UTC)
MER-C, That's probably what you do, and naturally you are perfectly free to pick and choose how, what, and when you do, but patrollers should be aware of the recommendations at WP:NPP otherwise they are not really helping the project. I, for example, generally only look for blatant candidates for ultra speedy - and some of them I then summarily delete already - leaving the rest for other patrollers to figure out and learn from; I certainly don't plod systematically through the list, well, not these days - three years ago I cleared about 20,000 from the backlog in as many days, but I guess I was still full of Wikithusiasm. IMHO the new page feed and its curation tool is a brilliant piece of software; the only problem is that it's only any good in the hands of users who know what they are doing. Kudpung กุดผึ้ง ( talk) 07:02, 18 October 2013 (UTC)
  • I would like to see a certain number of articles created, perhaps 20, as a criterion for this user right. This would allow a fair assessment of the user's understanding with regard to article creation in my opinion. Additionally, I think the right could be bundled with autopatrolled just as well as sysop.— John Cline ( talk) 03:23, 18 October 2013 (UTC)
While I like the idea of requiring some article creation experience I'm afraid 20 is far too high a threshold. I had been active here for 5 years and logged about 20,000 edits by the time I created my 20th article. Many of the most suitable candidates for AfC reviewer are those editors who have a lot of "wikignome"-editing experience - they generally don't create many articles. In any case "articles" is not a very useful unit of measurement - because both a 50-word stub about a village in Uzbekistan and a comprehensive GA-rated article about an obscure disease count as "1". I would give the right to the creator of one comprehensive article before I give it to a stub-mill with hundreds of three-sentence stubs, that just barely scrape past the minimum standards, on their scorecard. Roger (Dodger67) ( talk) 06:47, 18 October 2013 (UTC)
Dodger67, for 'Autopatrolled' the default criterion is 50 articles. However, admins review these carefully, discount redirects and dab pages, and and don't generally accord the right to '100 stub wonders'. 1-line stubs about one specific topic area do not demonstrate a sufficiently broad knowledge of policies and guidelines, especially the mass creators who use AWB or their first stub as a template. Kudpung กุดผึ้ง ( talk) 09:26, 18 October 2013 (UTC)
When I saw the topic, I was going to suggest article creation as a possible prerequisite. If as high as 20, I'd recommend that it replace one or more other requirements. If standalone, I would recommend a lower threshold, perhaps 5, but those articles must demonstrate knowledge of notability, reliability, independence, etc. If more than 5 articles are created, not all need to pass this criteria (some should could be stubs), but there must be 5 that do, and there must not be recent creations that demonstrate lack of knowledge in the critical areas. 78.26 ( I'm no IP, talk to me!) 12:09, 18 October 2013 (UTC)
That largely echos my thinking. Article creation is good, but expansion of a stub to a full-blown article may be worth as much or more.-- SPhilbrick (Talk) 13:40, 18 October 2013 (UTC)
While creating content within an existing article is an important measure, it presumes the existence of a notable article, rife for improvement. Article creation better demonstrates the all important ability of identifying notable subjects. AfD participation is perhaps another good way to gage clue in this regard.— John Cline ( talk) 14:03, 18 October 2013 (UTC)
  • Question as I'm seeing a lot of numbers or other rights being required here, which would be a major hurdle for many existing reviewers without of "grandfathering" of some kind. I'm not saying that these requirements are necessarily bad, just that they may be overzealous. Along the same lines as WP:CVUA for Rollbacker, I would like to think that a user without any of Reviewer or Rollbacker or 500 mainspace edits or 200 WP:New pages patrol or 20 created articles but who has demonstrated that they understand all of the proper policies (especially WP:Notability) via an AfC specific training program would be eligible. Technical 13 ( talk) 03:35, 18 October 2013 (UTC)
  • Kudpung said:

    Above all, candidates must have demonstrated that they understand WP:PROD, WP:AfD, and WP:Notability, and are able to interact with other users in a polite, friendly, and helpful manner.

You nailed it right there.
Any counts or other criteria we come up with are just ways to tell those who have done this from those who haven't, without having to spend hours wading through prospective reviewer's wiki-histories. davidwr/( talk)/( contribs) 00:47, 19 October 2013 (UTC)
@ Kudpung: I hope you don't mind, I turned it into the {{ tmbox}} at the top. davidwr/( talk)/( contribs) 01:08, 19 October 2013 (UTC)
I mind. Promoting one person's comment above all others with a big flashy spotlight is not conducive to consensus-building. -- ShinmaWa( talk) 01:19, 19 October 2013 (UTC)

Suggestion by Anne Delong

  • There was a lot of concern during the previous discussion that this would be a privilege which would be bestowed on some editors by others. This is how I envision the process working:
  • The Afc helper script be changed to only function for those on the Wikiproject AfC reviewer list.
  • The list could be on a protected page so that someone with regular reviewer rights would be needed to add names.
  • On request, an editor would automatically be added if they had reached a certain level of editing (for example, 2000 edits and one year of experience).
  • Editors wanting to review sooner or with less experience would have to meet the lower numbers of edits and time served mentioned above, and also convince a reviewer to add them to the list by demonstrating such items as Kudpung has mentioned above.
  • Names could be removed if problems cropped up (such as frivolous or frequently incorrect reviews).
The reason I suggest the addition of an automatic pass level is that I believe that many of the people who supported the previous Rfc only did so because they believed that it would be an automatic rather than requested permission. — Anne Delong ( talk) 03:50, 18 October 2013 (UTC)
Consensus not to implement, due to concerns about threshold being too high. -- Mdann 52 talk to me! 13:32, 13 January 2014 (UTC) ( non-admin closure)
The following discussion has been closed. Please do not modify it.
  • There were absolutely no mentions in the proposal on the previous RfC that the right would be automatically conferred. Criteria for the right, and how it would be granted were deliberately left open for further discussions. This discussion is to determine those criteria. What was clear on that RfC was the typical phenomenon on Wkipedia discussions that many people, especially those commenting later, do not fully read the preamble and proposition correctly and the following discussion and go off at half-tack - even introducing items that were expressly not required in the discussion.
I didn't mention it above, but but I would assume that current active reviewers who have not demonstrated any controversial issues with their reviewing would be grandfathered in.
I think requiring 20 article creations would be setting the bar too high. This is not required for NPP which has a similar need for knowledge of policies and practice but which does not require a permission (yet) and still suffers from the same problems: not enough patrollers, and often too little experience. I know I keep drawing these comparisons with NPP but I do feel it's relevant. Kudpung กุดผึ้ง ( talk) 04:31, 18 October 2013 (UTC)
  • Oppose criteria 2 New pages patrol is quite tedious and many users that could do it choose not to. I have to believe that asking people to do 300 NPPs will deter a ton of people from asking for AfC reviewer permission because there are plenty of other things most people would rather do than spend 20 hours doing NPP. Sven Manguard Wha? 06:15, 18 October 2013 (UTC)
I agree it is tedious. I did some quite some time ago and hated it. That said, it is eye-opening, and I wouldn't mind inclusion at a much lower level. -- SPhilbrick (Talk) 13:44, 18 October 2013 (UTC)
  • Given the exceedingly limited use of pending changes, what does reviewer actually signify? I agree with Sven's comments regarding NPP, as a long-standing patroller: 300 reviews is exceedingly high, both as something for the candidate to achieve and as something for anyone reviewing the candidacy to actually triage and check. Ironholds ( talk) 06:37, 18 October 2013 (UTC)
Ironholds, I don't see anywhere that anyone has suggested 300 new page patrols. Perhaps if people would read discussions before they participate. I disagree most strongly that at NPP it is so difficult to attain a number of patrolls, I have done thousands and so have you. At the rate at which some patrollers review new articles, 200 patrols can be done in 200 minutes - alebeit probably as slipshod as some of the reviewing at AfC. Kudpung กุดผึ้ง ( talk) 06:47, 18 October 2013 (UTC)
As usual, I'm going to ignore the pointless (and pointed) elements of your comment. To the remainder: the argument seems to boil down to "hey, you did it", which would be great if I wasn't the most active patroller for a solid two years by an order of magnitude I was even in a research study, how about that - "you can do it and I can do it" simply proves we can do it, not that it's achievable by anyone else. You know full well that our work on NPP is non-standard even for patrollers.
Sure, it's possible in a few hours, or days, or weeks if you actually want to put some effort in: that's not the point. It's a lot of work to put in to an activity you may actually have zero interest in - your interest is in AfC, not in NPP. It'd be like saying that for someone to be autopatrolled, they need to have extensive experience patrolling articles: sure, it's indicative of knowing what makes a good or bad article. It's also something that may bore them silly. I'm not entirely sure how excluding the people who don't enjoy NPP is going to help improve the quality or frequency of AfC work. I'd appreciate if you could address the reviewer comment as well. Ironholds ( talk) 06:53, 18 October 2013 (UTC)
There are dozens of patrollers who have made 200 or more patrols - if you only do one a day that's about half a year, so please let's keep this in perspective. If the task is as thankless and boring as some have pointed out (which IMO it is), armed with that qualification they may find AfC more rewarding. No one is excluding those who have not done NPP - but you probably missed the alternative qualifications that were suggested. Whilst I see many parallels in the work of AfC and NPP, I see little or no correlation with PC reviewing. Kudpung กุดผึ้ง ( talk) 07:18, 18 October 2013 (UTC)
Then I'm rather confused as to why you've recommended 'reviewer' as part of a qualification to get this right, since it's a PC-centric userright (unless someone can explain other uses it has, other than AFT5). Ironholds ( talk) 07:24, 18 October 2013 (UTC)
Ironholds, it should be quite obvious that these are listed as examples of criteria for permissions that are accorded based on prior general experience and as incremental stages of user experience that demonstrate some metrics of knowledge of guidelines, policies, and practice for the purpose of access to different levels of meta tasks. We naturally have to start somewhere. You appear to be confused that we are discussing a MedWiki 'user right' according to the semantics of the Foundation, rather than a 'permission' as applied to this exercise. Kudpung กุดผึ้ง ( talk) 08:46, 18 October 2013 (UTC)
Actually, it wasn't that obvious. I had to read it twice, after being initially puzzled that these were being designated as prerequisites. Then I realized they were examples of other rights, along with the criteria, so people could see example of criteria which could be used to think through the criteria for this right.-- SPhilbrick (Talk) 13:49, 18 October 2013 (UTC)
Thanks, Sphilbrick. The text is indeed pretty confusing. Ironholds ( talk) 16:40, 18 October 2013 (UTC)
  • Support except for criterion 2 - but only because I have never done NPP at all. I've just thought of a way to imlplement "Criterion 3". Basically it ammounts to putting new reviewers "on probation". We use a mechanism similar to the "re-review" that is currently used as a "quality control" check during backlog elimination drives. Thus someone who meets the (deliberately low) technical threshold has their first reviews logged at a special page from where they are rechecked by experienced reviewers. The "probation" is lifted once the new reviewer has demonstrated comptence to the satisfation of the other reviewers.. Roger (Dodger67) ( talk) 07:32, 18 October 2013 (UTC)
Dodger67, that's why aspiring candidates can choose between the two sets of criteria that fits their situation best. They don't need to satisfy them both. Essentially however, exactly what we are trying to do here is to avoid having to monitor the work of new reviewers as much as possible. This is currently being done on an ad hoc basis, but only when issues come to light. It would be impossible to do a double-control on all new reviewers - AfC resources are stretched too far already. Kudpung กุดผึ้ง ( talk) 09:05, 18 October 2013 (UTC)
I think RogerDodger67 has the right mindset ... but I agree with Kudpung that manually reviewing past work, by having existing AfC folks manually monitor some please-check-me-for-accuracy queue, is not the way to go. Methinks the only approach that can put new reviewers on probation, and also automatically check their competence *without* requiring any additional effort from existing AfC folks, is to use an auto-test setup ... where the candidate AfC reviewer attempts to pass judgement on a stream of submissions, which some existing AfC folks have already judged. If the candidate gives the same answers as the existing folks, then the candidate has proven their worth. See my detailed suggestion-section, below. 74.192.84.101 ( talk) 07:27, 19 October 2013 (UTC)
  • Oppose rollback requirement. There are other ways to revert vandalism, for example by using Twinkle's rollback function. I find Twinkle's rollback feature superior to the standard rollback feature as it allows specifying an edit summary, and for that reason, I haven't even seen any need to apply for rollback permission on this project, although I occasionally use the rollback function on Commons. A user's choice to use alternative tools shouldn't affect the chances of becoming an AfC reviewer. -- Stefan2 ( talk) 13:11, 18 October 2013 (UTC)
  • Oppose setting the bar wildly higher for WP:AFC than for WP:NPP as both largely compete for attention of the same volunteers. The requirements for both, while not identical, should be close. It's reasonable to ask that a reviewer be someone who has written an article or two which didn't get deleted, and understands the basic policies (particularly notability and sources), but set the bar arbitrarily high and the only result is to make an already-bad AFC backlog worse. That does no one any favours. K7L ( talk) 13:43, 18 October 2013 (UTC)
Ironically there is no bar for NPP. That's why they have problems there too. I campaigned for years for a solution for the control of new articles which accumulated in the ill fated WP:ACTRIAL, and for improvement of NPP, and that was why we ultimately got the Page Curation system, but it still did not address the two issues: too few patrollers, and too little experience - and there is still an unacceptable backlog with some less easy articles not getting patrolled for months. Kudpung กุดผึ้ง ( talk) 17:26, 18 October 2013 (UTC)

Suggestion by Sven Manguard

Despite "Consensus has been reached for this permission, this RfC is not for rediscussing whether a permission is needed." I still think that this is an incredibly bad idea and will ultimately complicate a process that is already so heavily bureaucratized and understaffed that it has had to come and beg people to help multiple times.

That being said, my suggestion is that rather than make the criterion based on vandalism fighting, we make it based on content creation. The permission would be given to:

  • Autopatrolled (automatically, by making adding it to the autopatrolled package)
  • Anyone with at least one GA or at least two DYKs
  • Anyone that has a track record of positive work doing AfC reviews (before the RfC)

Admins should feel free to assign the permission to anyone that qualifies. Rather than set up a request board, the AfC instructions should instruct people looking for reviewer permission to ask an admin already involved in AfC.

Finally, and I can't stress this enough, the AfC reviewer userright group should never be used to determine recipients for mass messages. AfC has, in my opinion, a shockingly bad track record when it comes to soliciting participation from people that don't want to hear from AfC, and no matter what the ultimate decision about what the AfC reviewer criteria is, plenty of people are going to be given the userright despite having no interest in AfC reviewing (not least because admins will get the right automatically, as they do with almost every other right).

Cheers, Sven Manguard Wha? 06:32, 18 October 2013 (UTC)

  • I'm still confused as to why we're talking about a userright. What technical privilege would it confer, and has anyone taken the time to ask the developers if this would actually be possible or even desirable as MediaWiki functionality? Ironholds ( talk) 06:38, 18 October 2013 (UTC)
We can restrict use of the AfC tool. I'm not sure if that conforms to the definition of a userright. Re: "Has anyone taken the time..." Would you mind being a bit less combative? In the previous RfC, linked above, someone with (WMF) in their sig, who seemed to know technical stuff chimed in. -- Anthonyhcole ( talk · contribs · email) 07:03, 18 October 2013 (UTC)
Ahh. Me or Sven? Sorry if I'm coming off as combative; that's not the intent. Userrights are software-recognised things that permit or restrict MediaWiki actions; admin is a userright that allows access to things like Special:Block, autopatrolled lets MediaWiki automatically mark a page as reviewed, so on and so forth. From a MediaWiki point of view, AfC does not exist; it's not special functionality, just a set of pages. So I'm trying to ascertain if people have actually spoken to the developers and asked if this makes sense as a technically-implemented userright. If not, some of the comments above (rolling it in with autopatrolled, for example) seem unnecessary, and people might want to use less confusing terminology. Userright == MW-recognised status that grants access to special functionality. AfC is not software-recognised functionality.
The WMF-person I can see is Steven Walling; his statement was "I have no idea whether it will be even possible to fulfill the request from a technical perspective". So, this probably needs further investigation before rather than after criteria are established. Ironholds ( talk) 07:08, 18 October 2013 (UTC)
Thanks for clarifying userright. We should probably determine what level of competence a person needs to have demonstrated before being permitted to review AfCs, before discussing whether we need to enforce it with a technical fix. I proposed earlier in this discussion that we use Wikipedia:Reviewer as a marker for adequate competence, and use social control to enforce it along with changing the AFC tool script to prevent anyone not on Special:ListUsers/reviewer from using the tool. But I pulled it, wondering whether that's setting the bar too low. Regardless, we can probably do what we want here without involving MediaWiki development. -- Anthonyhcole ( talk · contribs · email) 07:32, 18 October 2013 (UTC)
I don't know the plans for how to implement this, but a user right does not necessarily need to give access to extra special pages. For example, Commons has the OTRS-member, and the only difference between "OTRS-member" and "autopatrolled" is that an "OTRS-member" can add certain templates to a page without triggering Commons:Special:AbuseFilter/69. This user right could potentially be used in a similar abuse filter to prevent addition of certain AfC templates. -- Stefan2 ( talk) 13:17, 18 October 2013 (UTC)

( edit conflict)Once again, as there is little likelihood that a MedWiki solution will be granted - or even asked for, the question is moot. Some non MedWki methods have already been suggested and even by Brandon himself with whom I had a lengthy (and exceptionally friendly) discussion in Hong Kong. It's been mentioned dozens of times that permissions are needed for several MedWiki-independent actions. They are however listed at WP:PERM as the portal for permissions that are granted by admins. So again, we are discussing something that is not on the agenda of this RfC. Implementation/deployment comes later. Kudpung กุดผึ้ง ( talk) 07:35, 18 October 2013 (UTC)

I am befuddled by this counsel! Considering notes 1 thru 3 of the original RfC, how can one say another's suggestion is moot upon its rendering? Otherwise, this is not a request for comment, but instead, a request for support; of ideas apparently already decided.— John Cline ( talk) 09:35, 18 October 2013 (UTC)
Absolutely not, John. This is a think tank with an objective to define some criteria of experience for reviewing articles submitted to AfC. As stated in the previous RfC, what these criteria would be are for discussion (now here), and how it would be implemented will be discussed when the criteria have been established. One of the reasons that Wikipedia RfC fail or become overly convoluted is that there is often a tendency to discuss tangential issues at the same time, or ones that are not yet up for debate. Ironholds has made it perfectly clear that he will resist any suggestions to make this a MedWiki based 'user right', but has mistakenly assumed that that was the intention (on both this and the previous RfC). That said, if indeed any of the senior staff at the WMF decide that this 'permission' is of significant interest to entertain a MedWiki solution, we would be most pleased to hear about it, but we are not aware of any such offers as yet - in fact a closer look at my comments will reveal that I concur entirely with Ironholds that this is not a MedWiki operation, hence such suggestions are off topic as being evidently unworkable. Kudpung กุดผึ้ง ( talk) 10:27, 18 October 2013 (UTC)
In my opinion it would greatly serve this discussion if there was a definitive answer regarding MediaWiki support. If the entire modification is to be implemented at the WikiProject level, then yes, we are straying off topic by suggesting a new userright, whether automatic or granted; and should therefore focus the eye of our brain storm locally. That said, the best solution to my eyes involves MediaWiki support, and I for one wish we had garnered that support already. Otherwise I think Graeme Bartlett is correct that a blacklist is the way to segregate bad apples and I suppose we could use discretionary sanctions to ban individual involvement where cause has been shown. Notwithstanding, I am optimistic that better ideas are forthcoming, provided we don't stifle the creative flow of ideas by the heavy hand of pessimism.— John Cline ( talk) 13:24, 18 October 2013 (UTC)
Sorry to keep coming back to this John, but I think Ironholds (whichever hat he is wearing) has made it already abundantly clear. We're essentially discussing a set of criteria for a 'permission' rather than a 'User Right' per per Foundation semantics. I had an interesting in-depth discussion on this very topic with Brandon Harris, Erik Möller, and Steven Walling in Hong Kong and although they made some very interesting suggestions how we could approach an improvement to the AfC process, I do not believe there would be a spark of optimism for a MedWiki solution unless this were to have a cross-Wiki rollout. Personally I think it's best for us to find our own solutions locally. There is a faint chance that if they see we're making a superb effort in the right direction ourselves (as they did with NPP) they may step in towards the end bearing gifts, but I wouldn't bank on it. That said, although we want to avoid hat-collecting, I'm very suspicious that one of the reasons why NPP performs badly is that it ironically doesn't have a hat to collect although it demands far more knowledge than PC Reviewer or Rollbacker. Only today I came across a blatant long copyvio synthesis of multiple academic papers completely wrongly tagged by a 14-year-old patroller, who even apologised to the creator and removed the tag again! How many 100s of users would we need to blacklist before we have a few dozen reliable AfC reviewers left? A blacklist only shuts the barn door after the horse has bolted. Kudpung กุดผึ้ง ( talk) 14:54, 18 October 2013 (UTC)
What were their suggestions? And this isn't a Foundation POV, this is a software POV - the two are very much distinct. Ironholds ( talk) 16:39, 18 October 2013 (UTC)
Their suggestions are for a different discussion. As to WMF vs Software, you are best placed to know these things, but as far as the community is probably concerned, the Foundation holds the keys to development priorities, the human resources, the servers, and the funds. Please note that I support your theory that this is most unlikely to be accepted as a MedWiki request and I'm doing my best to stifle any sidetracking on the assumptions that it will. That said, from what I have heard from the Foundation staff and from competent programmers among the volunteer community, it won't be too difficult to find a local en.Wiki solution, whether a social one or one governed by some kind of script(s). Kudpung กุดผึ้ง ( talk) 17:53, 18 October 2013 (UTC)
If all that we want from this is to limit who uses the Afc Helper script, I don't see why any WMF changes are needed. The script is developed by our volunteer coders here. As I mentioned in my suggestions above, to enforce this all that would be needed is (1) The list of reviewers on the "Participants" page would be protected so that someone with Reviewer status would be needed to add a username, and (2) The script would check the list and only work for a username on the list. Whatever criteria we decide to use, this combination should prevent random new users from coming along and adding themselves to the list. — Anne Delong ( talk) 22:42, 18 October 2013 (UTC)
And what does that solve? The AfC Helper script is just a helper. There's no requirement to use it. It provides no functionality that a user can't do without it. AfC went a long time without having it, so I'm not sure what restricting it from some users accomplishes. If this whole RfC is about limiting a helper script, we really don't need an RfC at all. Just code it. However, the initial RfC made it very clear that this isn't just about the script. So, if it isn't a bit and it isn't just the script -- what is it? -- ShinmaWa( talk) 23:42, 18 October 2013 (UTC)
I was just about to redirect this deep thread to ShinmaWa's question-section at the bottom. Agreed that there is no software-enforced requirement that only threshold-approved official AfC folks are permitted to perform AfC actions... but we can make that the *default* way that AfC is handled, and folks doing it *outside* the default way (with exceptions made to grandfather-in people with 10k edits that are using old-school tools or their own custom workflow or whatever) will therefore stick out. This makes it easier to see who is 'officially' doing AfC within the threshold-limits, of course... and if needed, we can tell people doing it *badly* outside the threshold helper-script world to please stop, right? I think enforcement without no cracks in the security is *not* the goal here, because WP:AGF. 74.192.84.101 ( talk) 23:58, 18 October 2013 (UTC)

Suggestion by Lukeno94

  • In my eyes, an AfC reviewer should experienced enough that they would easily qualify for the rollback tool. Putting that aside, I would agree that having at least 1000 mainspace edits is a good idea for an AfC reviewer. I would not say that the conventional reviewer right was enough; it's one thing reviewing and rejecting vandalism, and a whole other one reviewing a whole article. I don't see how GA/DYK/FA count should be relevant. The "autopatrolled" bar is too high for the AfC reviewer right; and as I've said before, you can be a great article writer but very poor at reviewing other's works. Having to patrol 200 things at NPP is excessive, although I agree that some experience is required (maybe 25-50?), due to that being one of the more relevant comparisons. I'll come up with my own proposal later, if I have time. Lukeno94 (tell Luke off here) 07:26, 18 October 2013 (UTC)
"Rollback" is a vandalism tool; it allows multiple edits to be undone quickly where a vandal has randomly hit multiple articles. "Autopatrolled" is intended to keep extremely prolific but otherwise harmless new page authors from flooding WP:NPP. Neither necessarily infer a better AFC reviewer, although they normally are given to someone who is doing no harm. A good or featured article usually has multiple contributors instead of being WP:OWNed by one primary author; someone who'd submitted a pile of stubs in 2002 on valid topics, left the project for a decade and then returned to find some were expanded to GA/FA level would be given more credit than due. An editor which pulls a topic off the WP:AFD pile and rewrites it to WP:FA status, conversely, is not credited with creating an article. All of these metrics have their limitations - preview nothing before you save it and you can run up edit count more quickly, for instance. Experience writing valid articles or bringing existing articles up to some standard (off AfD to viable, off stub/start to B/A/GA, ordinary article to FA) is valuable but collecting privilege flags or edit count just for the sake of doing so does not always guarantee a better reviewer. K7L ( talk) 14:18, 18 October 2013 (UTC)

Ideas by Graeme Bartlett

We should consider what we are trying to achieve here:

  • Firstly we want to build the encyclopedia. So such a person should show that they can recognise the useful content for Wikipedia. The person should be able to understand what is and is not a suitable topic. They should be able to find a duplicte topic.
  • Secondly we want to encourage the contributors, so we want the candidate to be able to talk to the contributors to explain what is needed to improve or to make an acceptable article. The person should be civil in their communication.
  • Thirdly we want to keep it legal, so the candidate should be able to recognise a copyright infringement, or an attack page.
  • Fourthly some nice to have features: The person can add categories and stub tags. The script seems entirely cabable of adding the almost useless orphan tag, so I hope our person can also show that they can edit articles to link to pages, including use of piped links.

Graeme Bartlett ( talk) 07:59, 18 October 2013 (UTC)

Pretty accurately sums up what I said in my suggestion, Graeme. What we're looking for now are some metrics that define those qualities for the purpose of according the permission. Kudpung กุดผึ้ง ( talk) 08:56, 18 October 2013 (UTC)
So I am not so demanding in predefined standards, but the candidate should be able to show these capabilities. If a person is asking for it they can show diffs that illustrate these capabilities. I do agree that NPP is quite a useful precursor experience for AfC reviewer. The other flags such as rollback and reviewer are not directly relevant, but certainly would show that the editor is constructive. If the person does not want to do 400 NPP items, perhaps they could do some apprenticeship work, perhaps checking AFC contributions and giving feedback to a mentor that would prove that they are on the right track. Graeme Bartlett ( talk) 10:11, 18 October 2013 (UTC)
I see that 200 has grown to 300 and now to 400. Sounds a bit Falstaffian ;) Mine were but the first suggestions to get the ball rolling and I knew it would entrain some discontent; let's lurk awhile and see what others may suggest. Kudpung กุดผึ้ง ( talk) 10:38, 18 October 2013 (UTC)
I like Graeme's ideas, and as a submitter I would love to work with an AfC person who met all these criteria... but I am very hesitant that some of them can be decided without fawning, interviewing, role-playing sessions, and other expensive overhead. (Yes, we are all volunteers for the most part, I'm talking about opportunity cost here... every minute an existing AfC person spends interviewing an AfC candidate, is *two* minutes that those people could have been actually whittling down the AfC queue backlog.)
   In particular, Graeme's point#2 about being an encouraging person, explaining things well, invariably civil, good looking, well dressed... okay, not those last two. But I hope the point is clear: there is no way to automatically test and verify those things. Just because somebody is good with those things in a one-hour interview is also no guarantee they will be that way *every* day, to more or less *every* contributor they happen to work with. Some people have a naturally sunny, cheerful, helpful disposition: I've met a few librarians like that, and many teachers. But for every one of those, I've interacted with hundreds if not thousands of fast-food clerks, waiters in restaurants, checkout clerks at the grocery store, floor assistants in retail stores, tech support folks via telephone or IM, and so on and so forth. It is *hard* to be consistently nice, consistently helpful, explain intricate details fully, and all that. Such people are diamonds in the rough, not grains of sand lying on the beach. If we *do* get a gemstone in AfC, I'd recommend we use them as a second-tier, for when contributors have trouble with their first tier person for whatever reason, they can be passed to the sunny cheery natural teacher sitting in the tier-two chair.
   Since point#2 took so much verbosity, I'll hit point#3 super-lightly: don't we have copyvio bots? And aren't BLP articles a specialist niche, given their legal-kryptonite-status, which ought be directed to *only* the AfC folks most experienced with such things? Point#1 methinks we *can* auto-test, see my 74-whatever comment below, and some of point#4 is also either auto-testable, or demonstrable in a three-minute (as opposed to three-hour) interview process. 74.192.84.101 ( talk) 06:58, 19 October 2013 (UTC)
74 it sounds like you are raising the quality bar on the point 2, I was not expecting the behaviour always, but enough to do the job and encourage the contributors. The idea was not to have just gamers that can only push buttons. BLPs are most of what we have (may be companies too) so we need people to handle them too. But perhaps also we need people who can recognise their own limitations and not attempt something the mess up. So even someone that can decline a joke or vandalism can be useful if they just stick to that. Graeme Bartlett ( talk) 21:33, 19 October 2013 (UTC)
Well... I'm not really trying to raise the bar, so much as point out that cheerfulness is a spectrum, but with some pretty well-defined focus-areas. I'm actually trying to lower the bar, if anything. I think we want the tier-one AfC candidates to be the equivalent of the sales-associates at the designer clothing store: efficient-n-quick with straightforward purchases, at least minimally friendly, but do not really have time (and thus do not really need to have the skillset) for solving difficult sticky-wicket cases. If you are trying to create an article about a BLP, who was formerly a relatively unknown business owner, but just announced their candidacy for the mayorship of a large city, and leapt to frontrunner status in the polls, then the sales-associate can send your article on through. If your little brother has a garage band, and the school newspaper mentioned their name once, and that is it so far, then the sales-associate can politely tell you WP:NOTNOW.
   The grey areas are more tricky, where something is borderline-Notable, but requires more depth in the sources, or whatever. I want those types of grey-area cases to be quickly glanced over by the first-tier sales-associate, and then passed back to the second-tier cheerful-librarian-associate. If the second-tier folks cannot solve the issues in a timely fashion, I want the third-tier to be, that the submitter is redirected to the WP:TEAHOUSE to find help doing the rewrite, and their AfC submission goes to the back of the queue. TLDR, rather than insist that our sales-associates aka AfC reviewers *must* be "interviewed for cheerfulness and tested on how sunny their disposition is", methinks we just need to remind everybody to be WP:NICE, which is required of *all* wikipedians anyways. If we happen to run across somebody that is *naturally* cheery and sunny, then we should then 'promote' them to tier-two work, where their special skill is extra-applicable: handling grey-areas. HTH. 74.192.84.101 ( talk) 20:57, 4 November 2013 (UTC)
  • We have copyvio bots, but they probably can't be used until AfC submissions are made on a namepage e.g; 'Draft', instead of a talk page or sub page. Kudpung กุดผึ้ง ( talk) 02:59, 20 October 2013 (UTC)
  • User:MadmanBot already scans AFCs (it misses at least some copyvios) when it's working. Patroller recognition of copyvios is still a must. MER-C 04:34, 21 October 2013 (UTC)
Okay... and how do we test whether an AfC reviewer-candidate possesses that special skill, ability to sniff WP:COPYVIO? There is a tool for analyzing whether URL#1 and URL#2 have copyvio problems. And there are bots that detect plagiarism, kinda-sorta. But short of glancing over the output of such tools, can humans really detect COPYVIO? I guess some things will be obvious, like a submission that says "copyright New York Times" at the top or the bottom of the text, or more subtly, text that has a bunch of internal links that are not wikilinks, but look like they came from a view-source-cut-n-paste job. But baretext submission, that was cut-n-pasted from the middle of some obscure website? Seems unlikely an AfC reviewer will detect the plagiarism with their spidey-senses. Maybe it's not that hard, because the plagiarized portion sticks out as a different 'voice' from the other portions of the AfC submission? (If there is a knack to copyvio-sniffing, methinks the parallel-primary-criteria scheme is useful training.) 74.192.84.101 ( talk) 21:06, 4 November 2013 (UTC)

Suggestion by Andy Dingley

Oppose any creation of a new right that resembles a "collectable hat" in any way, or that makes editors of this, "the encyclopedia that anyone can edit" more dependent upon bureaucracy.

We have a vandalism problem that ab initio editors can pop up, trash an article, post spam links and wander off. We have no checks on this. We allow unregistered editing and we allow unregistered editors to wreak all manner of havoc on established articles. I thus fail to see why we should start narrowing down AfC in particular to a subset of editors willing to jump through hoops.

In particular, making AfC review dependent upon a discretionary permission like rollback. I don't have rollback. I did have, and it was removed for a disagreement over regarding this edit / User_talk:Andy_Dingley/Archive_2009_September#Reversion as vandalism or not. Ever since then I've made a point of never asking for such a discretionary permission, lest it be pulled by some teenage admin with an axe to grind.

I can see some virtue to restricting AfC review (and think a lot more things, up to basic editing) should be restricted. But can we please keep this to a very lightweight, automatically-granted permission, not one dependent on cliques and fawning. Andy Dingley ( talk) 09:39, 18 October 2013 (UTC)

This idea of a automatic permission, or one that is very easy to get, appears to have overall support. -- Mdann 52 talk to me! 13:38, 13 January 2014 (UTC)
The following discussion has been closed. Please do not modify it.
To clarify a point raised off-line, there is a genuine concern that "editors who can't accurately review" shouldn't have this permission (that being it's point). We can attempt to judge this before granting it (which seems difficult to judge) but we can just as readily judge it after it has been awarded. If awarding the permission is a simple edit-count as a first filter, then it's easier to judge real skill by seeing some AfC reviews (and most editors just won't get involved anyway). Andy Dingley ( talk) 11:20, 18 October 2013 (UTC)
On the matter of (pre-)judging-ability-to-accurately-review, see this section -- Wikipedia:WikiProject_Articles_for_creation/RfC_for_AfC_reviewer_permission_criteria#An_idea_from_Ross_Hill 74.192.84.101 ( talk) 06:38, 19 October 2013 (UTC)
  • I support these sentiments.— John Cline ( talk) 09:43, 18 October 2013 (UTC)
  • Support. AfC is desperately understaffed as it is, and unless the permission is automatic this already understaffed project will become a huge bottleneck for the encylopedia. At the very least, everyone who has previously done favourable work at AfC (10 or more good reviews) should have this permission from the outset. -- LukeSurl t c 10:32, 18 October 2013 (UTC)
  • Support this view. Any limitation on Articles for Creation will end up shutting out more good contributors than bad, and AfC is horrible backlogged already. Howicus (Did I mess up?) 14:16, 18 October 2013 (UTC)
Where are the hoards of volunteers 'without' a criteria who are already prepared to step in and review AfC submissions competently? AfC is indeed desperately understaffed as it is, and does not have the person-power to review every reviewer's work. That would only make the bottleneck worse. Some are obviously getting it wrong and yet others blatantly abuse the system for their own ends. We either want reviewers or we don't, but appointing them through some arbitrary automated selection method without any real control would probably lead to greater disaster. The permission has been created by consensus. This is an RfC to determine the criteria for that permission and not to re-debate the need for it. Once the criteria have been established, it will be further discussed how to implement them specifically in a way that it does not become a trophy for the hat-collectors, with as little 'cliques and fawning' as possible, and avoid being pulled by the (fortunately) ever dwindling corps of teenage admins with an axe to grind. Kudpung กุดผึ้ง ( talk) 11:03, 18 October 2013 (UTC)
I think getting more AfC candidates is a job for WP:RETENTION, and similar anti- WP:BITE organizations like the teahouse. Bluntly, it is very difficult to *increase* the percentage of editors that will want to get involved with AfC work, by demanding they first meet some threshold-criteria. (That is not strictly the case, which is why I said 'very difficult' and not flat impossible... one could imagine threshold-criteria like 'willing to accept USD$100/hour from wikimedia foundation for their AfC work' that would *dramatically* increase the pool of editors willing to fight for an AfC slot, but as a class those tend to be unrealistic).
   I think what Andy and LukeSurl are trying to say is that the point of the threshold-criteria is to keep from accidentally reducing the number of AfC candidates *too* much, while still satisfying the basic goal that the threshold-criteria gives us a usable metric from separating the wheat from the chaff. We want the threshold to prevent COUNTERPRODUCTIVE folks from becoming AfC workers, where their net contribution is negative, because they make so many mistakes which other folks end up needing to clean up later on. But if we require fawning, or non-automatic AfC-permbit acquisition, or tons of paperwork, or running the gauntlet ("in order to get the AfC-permbit you must undergo RfA -- even if you already have the admin-bit"), or significant friction-slash-overhead, we shoot ourselves in the foot. Too much friction, and the overall benefit of having a threshold (eliminating N counterproductive candidates) will not outstrip the overall disadvantage of having a threshold (eliminating M productive candidates!). Agreed that we don't want an "arbitrary automated selection method without any real control" ... but we do need it automated, preferably non-arbitrary, and with as little bureaucratic friction as possible, both to keep from tying up existing AfC folks in resume-review-and-interview stuff, plus also to keep from tying up AfC candidates in fawning-and-paperwork. 74.192.84.101 ( talk) 06:35, 19 October 2013 (UTC)
I think we do need a human assessment rather than an automated one. Perhaps it can be easy to get but then easy to remove if there are stuff ups. Perhaps a list such as for AWB can be useful, and alternative could be that we just have a black list. The kind of hat that people would not want to collect is a possible. The hat could be "restricted from AFC review" and only stop people from doing it. We could have other bits for vandals or clueless or copyright infringers. Then these are the people that don't get to operate it. for the axegrinders, we need an axeginder bit too! Though I think I am stretching this to non-seriousness here. Graeme Bartlett ( talk) 11:21, 18 October 2013 (UTC)
The Eric Corbett CIVILity-inapplicable bit. Andy Dingley ( talk) 11:25, 18 October 2013 (UTC)
For the axegrinders we need an angle-grinder. Kudpung กุดผึ้ง ( talk) 11:40, 18 October 2013 (UTC)
  • support as best idea I've seen thus far. Hobit ( talk) 12:23, 6 December 2013 (UTC)

An idea from Ross Hill

I agree with all the goals put forward by Graeme Bartlett.

So far the suggestions have mentioned edit count, rollback, AWC, etc. as prerequisites. However none of those things truly show that one can review articles well. What is a better way to prove your worth at reviewing articles, than reviewing articles? I propose that every candidate find 5 pending articles they would decline, and 5 they would accept and they would have to explain their reasoning, citing policy. They should also be able to explain WP:BLP, WP:NOTABILITY, WP:VERIFIABILITY, etc. An admin would then review their responses and choose whether to accept them as a reviewer. Thoughts? Ross Hill ( talk) 16:30, 18 Oct 2013 ( UTC) 16:30, 18 October 2013 (UTC)

It's a bit hard to find acceptable articles...how about 5-8 articles total, whether acceptable or not? Howicus (Did I mess up?) 23:46, 18 October 2013 (UTC)
Oppose "admin would then review". I don't see any reason why administrators are required for this process, unless there's a technical implementation requirement for them to be. -- ShinmaWa( talk) 23:48, 18 October 2013 (UTC)
I wasn't really focussing on any specifics. I don't care if it's an admin, or an experienced reviewer. 5 articles, or 3. I just want feedback on the idea. Ross Hill ( talk) 23:52, 18 Oct 2013 ( UTC) 23:52, 18 October 2013 (UTC)
Fair enough. Of course, how feasible this suggestion is depends upon the implementation (which is why it is folly to attempt to separate criteria from implementation). However, given all the social-based implementation ideas presented so far, including AfC mentoring, elaborate testing, and the like, this one is the best so far, I think. However, it would need to be fleshed out quite a bit on the specifics of who gets to review, based on what objective criteria, and -- to beat the dead horse -- how approving an applicant would be implemented. -- ShinmaWa( talk) 00:03, 19 October 2013 (UTC)
I have fleshed out an implementation plan for Ross Hill's idea, which I believe is the only truly fair (and predictive) basis for 'testing'. (My answers to ShinmaWa's questions are nobody, based on the objective performance of existing trusted AfC folks, and automatically based on the specified X-and-Y values at the time -- or perhaps retroactively.) The other criteria being discussed (editcount/etc) are all secondary criteria, which might be useful as a way to pass-the-test-without-testing, but cannot replace the trial by fire of AfC work itself. Rather than choosing articles at random, and let possibly-biased editors make the call on whether the candidate judged correctly, I suggest using real articles that are really going through AfC. If the candidate gets right answers (where 'right' is defined by the answers the actual AfC person gave) on enough of the articles, they too become an official AfC person. See here -- Wikipedia:WikiProject_Articles_for_creation/RfC_for_AfC_reviewer_permission_criteria#Suggestion_by_74-whatever
support this. If we must have a 'crat allocated privilege, then at least let's bind it to the real task in hand. Candidates review some (clarification needed) unreviewed AfC candidates, of which at least a couple must be judged pass/fail as a result. Andy Dingley ( talk) 19:26, 19 October 2013 (UTC)

Suggestion from Sj

It's distracting to separate criteria from implementation here, since they are closely tied together. (The criteria you use affect how you can implement it, and v-v.) So here's a joint suggestion:

Simple option
Maintain a list of reviewers on a wikipage. Let anyone add themselves; remove those who aren't working out yet. Add a feature to one of the popular review-tools that checks to see if new articles on an AfC topic are created by users who aren't on the list -- a flag that someone else should doublecheck the work.
Tying this right to 'edit count' or 'rollback' seems like a terrible idea to me. The number of people willing and able to do this work is tiny; you can interact with them all personally. Instead, tie it to a single back-and-forth welcoming interest and asking people if they feel comfortable they know what a good article looks like [with pointers].
Future technical option
Combine this with the Reviewer flag. Make this the Flagged-Revs workflow for the very first rev of an article. Make it something that is given automatically to people meeting certain threshholds, and to anyone else who asks. Allow it to be removed for misuse; but most granting of the right should be automatic, other than time spent welcoming new collaborators.
The flag should allow access to tools that make AfC work streamlined and easy, and that update any special pages that track requested articles. (In comparison: anyone, with or without this right, can browse the AfC requests and create articles based on them. But it won't be checked off of the queue until a reviewer checks that work.)

Aside: it seems to me that the impact of the Reviewer flag has been weakened by the requirement that admins apply the right, with no automatic way to get the flag. This is unlike basically every other reputation-ladder I know of. Our lack of automatic activity-based rights (other than autoconfirmation) is a waste of energy, and seems self-perpetuating. –  SJ  + 17:14, 18 October 2013 (UTC)

I totally agree. I am still against a user right for this, and reading over what is written here, it looks like what we need is a "reviewer block" for bad reviewers, not an extra reviewer right. All of the criteria I have read above just reinforces my scepticism, because whenever someone talks about "grandfathering in" they really mean "let's keep this cabal small, trusted and among ourselves". We really need to start trusting newbies again like we did back in 2006, or the editor retention rate is going to drop more and more rapidly as the "grandfathers" start to drop off, for whatever reason. Jane ( talk) 10:16, 28 October 2013 (UTC)

Suggestion for Buffbills7701

Alright, I'm going to cut right to the chase. I think that in order to get the reviewer right, you need to get past this. The mentoring program is currently a work in progress, but when it's done, it would be the perfect solution for the new AFC reviewer right. buff bills 7701 20:29, 18 October 2013 (UTC)

This should be one way to get the access to the AFC Helper Script. It should not be the only way (e.g. most very experienced editors with good reputations shouldn't have to "go to school" to get access to the tool). davidwr/( talk)/( contribs) 23:49, 18 October 2013 (UTC)
Seems like a great way to open a hatshop for the currently inexperienced. No, or at least very few, long term editors would go near it. Andy Dingley ( talk) 00:40, 19 October 2013 (UTC)
Andy, I'm sure Buffbills meant 'one way' as David expanded. Every single user right from Confirmed through to Bureaucrat is a millinery in our information mall, but generally only on the lower floors - anyone who has worked extensively at WP:PERM and WP:RfA knows this. However, the systems of scrutiny that accord those rights generally function well but there will always be a tiny few who loose their flags - especially admins who have an axe to grind. At the lower levels, it is even more rare for PC reviwers, Rollbackers, File Movers, Autopatrolled, etc. to be demoted, but it does happen. I've never been subject to sanctions, but as one who was bullied by two teenage admins early in my Wiki career, and completely bullied away by an admin (now desyoped) from one topic area, never to return, where I had most to offer the encyclopedia, I do follow the ANI/AN, RfC/U, and Arbcom rituals very closely even if I don't participate much there. As an admin however, I don't have any axes to grind.
Let's not get too uptight or paranoid about the occasional hat-collector slipping through the net, a system of control over who can process AfC submissions is far better than none at all or one that is accorded automatically based simply on editcount/tenure, etc. Possibly those who work regularly at AfC and its maintenance are more aware of the issues than those who don't, but what we are here to do is ask the broader community for their opinion on, and to suggest, a set of criteria that would largely contribute to improving the quality of AfC reviewing, ensure that all reviewers are singing from the same page, and are friendly to the the submitters. The permission does not grant any further rights or hamper the work of article creators who know what is expected from an article that will survive legitimately in the encyclopedia. Kudpung กุดผึ้ง ( talk) 04:47, 19 October 2013 (UTC)
I would agree with David here. We have a need to solve the current problem of poor quality reviewing. I believe we need this right, but it should be very low, based on a simple mileage count – then if needs be, withdrawn from poor reviewers, based on the quality of their reviews. Secondly we can achieve this by encouraging experienced editors to take more part (AfC review is not rocket science) and anything that could be seen as "patronising" is hardly likely to achieve that. How many 5+ year / 10s of kedits editors want to be "mentored" by someone who has maybe 6 months of springy-tailed editing inbetween school? I spent a chunk of last week being lectured on 1950s motor racing history by someone who's barely old enough to have a driving licence, but here they have the free time to do a lot of typing, so they get to shout loudly and often. Andy Dingley ( talk) 10:15, 19 October 2013 (UTC)
Buffbills7701, editors with only double digit edits regularly add their names to WP:WPAFC/P list and due to the immense workload we're not always quick enough to do something about it. Last week one registered with the sole purpose of passing their own articles. One of our concerns therefore is for the grey area of editors who review, but whom we are not aware of. I support the idea of a school for aspiring reviewers and I'm currently working with other editors to set one up. I don't believe genuine hat-collectors are very interested in going through the rigours of our various training systems (I completely redesigned the WP:CVUA from the ground up and also set up an NPP school) . One of our standard answers at WP:PERM (Rollbacker) is "Hi, I appreciate your enthusiasm but with only 46 edits to mainspace I don't think you have sufficient experience yet. When you have made at least 200 edits, you may wish to enroll at the Wikipedia:Counter-Vandalism Unit/Academy to learn more about it." Kudpung กุดผึ้ง ( talk) 04:47, 19 October 2013 (UTC)
Here's what I don't understand about all this. You've brought up this editor who registered an account to "pass his own articles" on a number of occasions. So. What. You act as if this is some kind of real crime against the project. In reality is that once he's a registered user, he has every right to create his own articles in mainspace as much as every other user does. If he wants to clear the duplicate article out of AFC in the process, there might have been better ways to do it, but overall, he didn't hurt the project at all and he certainly didn't hurt AFC one bit in doing so. That argument is completely a red herring and I do wish you'd stop using it. -- ShinmaWa( talk) 19:06, 3 November 2013 (UTC)

Suggestion by 74-whatever

temporarily delayed as my suggestion is for auto-testing and auto-confirming *technical* competence at AfC specifically, and kudpung is after *moral* competence and ethical commitment to wikipedia generally

Kudpung and Anne and others have suggested various secondary criteria for the threshold: edit-count, NPP, and so on. Lukeno pointed out that some secondary criteria (like participation bringing something to GA status) have little relevance, because most of the AfC stuff is nowhere *near* that status. Several people have pointed out an automatic-grant-the-bit solution is the best way to minimize bureaucracy, but other people have countered that the human element is crucial, for most secondary characteristics do not really tell us if the candidate will be any good at judging AfC submissions. It is important that they be good at this task, because too many false-negatives will cause a dramatic amount of work downstream, and of course a lot of drama if an 'accepted' article is then speedy-AfD'd the following week. I believe there is a way AfC folks can have their cake and eat it too. We should judge the worth of potential AfC folks, based on how they would do on real-world AfC submissions, compared to current AfC folks on those same submissions.

  • Candidates wishing to get the authorized-for-AfC bit test their skills against real-world AfC submissions
  • Threshold should be an X% success rate on a minimum of Y real-world AfC decisions
  • In parallel, and blind to such candidates, the already-authorized AfC folks do their normal work
  • Example test: on Wednesday evening, Anne Delong judges ten AfC submissions from the queue; I do the same, without seeing any of her decisions
  • Example math: Anne's answers were yyNNyyNNyy to those ten, and my answers were yyNNyyNNNN , which means I made two mistakes (Anne is perfect -- good work Anne :-)
  • Example fail: if the threshold chosen is X>=90% and Y>=10_decisions, I satisfied my_Y>=10 but I failed to satisfy my_X>=90.
  • Example learn: determined to get there, I study Anne's answers (now visible to me after my test-session), and keep trying.
  • Example win: in my next test-session, I judge ten more of Anne's cases in parallel, and make no mistakes. Now my_Y=20 and my_X=18/20, which means I just auto-passed with my_Y>=10 and my_X>=90%.

Disadvantages:

  • the test-session itself is duplication of 'real' work (Anne is working -- I'm only *simulating* work she already did)
  • somewhat difficult to explain the concept of auto-testing in parallel (cf verbosity of this proposal)
  • may be *quite* difficult to implement the concept of auto-testing in parallel, since Q&A with the submitter is not something we can simulate
  • likely impossible slash infeasible to really make the 'blindness' of the auto-test secure (if Anne emails me the answers I *will* pass)
  • even if we posit that security is not a big deal, and Q&A can be elided, still need a dev to write some code for auto-testing (not true of e.g. simplistic editCount>=1000 threshold or similar)
  • hard to pick the initial Y ... make it too high, and nobody will try, make it too low, nobody will fail
  • hard to pick the initial X ... make it too high, and *existing* AfC folks will be eliminated, unless grandfathered in
  • just because you crammed, and memorized the policies long enough to pass a test-session, does not mean you really are good at AfC later on
    • "Kudpung: Last week one registered with the sole purpose of passing their own articles." Somebody could cram for the test-session with that purpose in mind, too. Only an admin can catch that.
  • scoring well on the auto-test does *not* necessarily make you a good AfC judge... it depends on whose answers you correctly mimic'd!

Advantages:

  • threshold is real-world *primary* criteria, not secondary
  • although no humans are involved with granting the bit once I pass, a real human is doing the testing (Anne is testing me)
  • as with anything in wikipedia, WP:IAR means that even if I auto-pass, some admin can always *manually* remove my authorized-bit later on
  • fair nature of the automated testing means no complaints about bias/fawning/etc
  • easy to auto-grant the permbit when the threshold is met , with a database table of people-who-passed-the-automated-testing
  • easy to auto-warn an 'official' AfC person when their ongoing work falls below the testing-threshold at any point
  • easy to retroactively adjust the threshold-values of X and Y upwards to improve quality, or downwards to improve reserve-troop-strength
  • difficult to explain 'on paper' but in practice easy to explain... watch what Anne does today, tomorrow do what Anne does, if you do well you pass, if you don't you can try again.

Hope this helps. 74.192.84.101 ( talk) 23:00, 18 October 2013 (UTC)

p.s. Forgot to mention that I agree that *some* sorts of work should automatically be given the AfC-permbit. Have three years and 10k edits with no blocks in the past year? You get the AfC-permbit without needing to pass the X-out-of-Y-auto-testing-threshold. 42 edits on enWiki, but 10k edits on deWiki? Prolly you have to take the auto-test, as a real-world check on your ESL skill. Have 333 NPP credits? Ditto. Have 10 new articles in existence, each older than a month without being deleted? Ditto. Member of arbcom, passed an RfA (regardless of whether you still hold the admin-bit), surname Wales? Ditto ditto ditto. But these secondary criteria should be, well, secondary. What matters is not your edit-count, but how your judgement matches up against Anne Delong's judgement. Our existing AfC personnel should be the gold standard, both now, and five years from now. Auto-testing is a self-reinforcing metric of 'goodness' methinks. 74.192.84.101 ( talk) 23:17, 18 October 2013 (UTC)

And in particular, one group that should automatically get the AfC-permbit was mentioned by Anthonyhcole (besides the 1500 admins), namely, the 6000 people with the Reviewer-permbit. Much like I'm suggesting here, there is a trial period. However, the threshold-criteria for Reviewer-permbits are not numerical and automatic, but require an interview process: knowledge of the reviewing-guide & vandalism-policy, familiarity with WP:COPYVIO / WP:BLP / WP:NPOV / WP:OR / WP:V / WP:NOT, and finally "have an account with track-record of routine editing". 74.192.84.101 ( talk) 07:14, 19 October 2013 (UTC)

The above suggestion that at first the new reviewer would review "in parallel" seems overly complicated, but there would be a simple way to implement this. A new reviewer could pick out a submission to review, and instead of actually reviewing it, leave a message on the Afc talk page saying something like "I think that XXX is ready to be accepted" or "I think that XXX should be declined with this decline reason ___ and I would leave this message:___". Then any of the regular reviewers could say "Looks good to me, go ahead". That way we'd all be "mentors" and the new reviewer would safely get practice. — Anne Delong ( talk) 23:24, 19 October 2013 (UTC)
Anne, similar ideas have been posited above in other sections. I personally do not support any solutions that will: eiher increase the workload of other reviewers or project editors working at AfC, and/or slow down the reviewing procerss; What this RfC asks for is not alternative solutions, but for a set of criteria of experience. Although the rights Rollbacker, reviewer, template editor, File mover, etc., may in some instances not be a good parallel, thier granting system is not dependent on any form of probation or monitoring of their progress. I think we need to look for a similar, simple 'granting' process here based on experience than can be quickly investigated (edit count, type of edits, talk page comments, block logs, etc.,) rather than look towards implementing a more complex and time consuming process. An AfC Academy has now been developd and any aspiring reviewers who fall short of the criteria that we will set here can be referred to that for training if they are serious about becoming reviewers in much the same way as we have a CVU school and an NPP school - bearing in mind that this latter is generally only used when NPPers (who don't need any quals at all) persistently get their patrolling wrong and are asked by an admin to stop. Kudpung กุดผึ้ง ( talk) 03:18, 20 October 2013 (UTC)
I've already given my opinion about the qualifications above, but you didn't like that either, so I will go back to reviewing now. — Anne Delong ( talk) 03:24, 20 October 2013 (UTC)
Hello again Anne, thanks for the comments. Yes, my suggestion is obviously quite complex, to understand and to implement, whereas your mentor-by-humans approach is straightforward and easy to implement. But the worry for Kudpung is that you and the other AfC regulars are *already* overloaded, so mentor-by-humans is going to pull expert AfC reviewers into mentoring (and thus necessarily out of AfC work), and I share that worry. My complex review-in-parallel scheme is designed to let the computer be the mentor, so that a beginning AfC candidate can test their mettle against your known skill, *without* you needing to directly mentor them. Once the top candidates were known, then mentoring would be the next phase. Anyways, as Kudpung points out, my solution is not what this RfC is for... this RfC is for coming up with a bunch of secondary criteria, that can be used for autogranting the AfC kinda-sorta-like-a-permbit-yet-not-really. (My scheme attempts to dispense with secondary criteria, and directly measure How Good The Candidate Is At AfC Work Itself.) Appreciate the criticism, danke. 74.192.84.101 ( talk) 20:38, 4 November 2013 (UTC)

Question from ShinmaWa

While this RfC is primarily about the criteria, which I fully recognise, some thought into implementation needs to take place lest we paint ourselves into a corner that can't be implemented. A lot of discussion is about a UserRight bit, which has technical issues which Ironholds discussed above. There's also been a lot about restricting scripts and tools. However, while there are a number of scripts and tools available to assist with AfC, they are 100% optional. Everything done at AfC can be done without a single tool in place and was for a very, very long time.

When boiled down to its essence, AfC requires that users be able to 1) Move pages from the "Wikipedia talk" namespace into article space and/or create new pages in article space and 2) Edit existing pages in the Wikipedia namespace. That's it. Every autoconfirmed user on the planet has the capability to do this. Restricting the tooling will just restrict the tooling. It won't actually keep a single user from participating in AfC.

So, the question is this: For this criteria/permission/etc to be meaningful, failure to meet this criteria somehow has to prevent users from creating articles nominated in AfC (which has all kinds of bad second-order impacts) and prevent users from editing articles in the "Wikipedia talk" namespace that "belong" to AfC (ditto). Just how are we going to go about this? -- ShinmaWa( talk) 23:15, 18 October 2013 (UTC)

"if it isn't a bit and it isn't just the script what is it?" From what I understand, it is a community standard, used by enWiki, to see who is 'qualified' to be an AfC person. It is like the ISO standard for papersizes, where there are tolerances plus-and-minus a few micrometers, but if you are within the tolerances you can say you are ISO-standard-sized A4 paper, or whatever. That does not mean that *every* piece of paper is ISO-standard, nor even that ISO-standardized paper is the best (arguably vellum is the best). It just means that, if you have satisfied whatever threshold this discussion ends up recommending, that you become a Recognized Official AfC Member In Good Standing, subject of course to other admin-actions that might keep you from acting on your over-the-threshold qualifications. Maybe someday it will be a 'real' permbit like the admin bit, where security matters... for at present, methinks it is just metaphorically an AfC-permbit, loosely enforced by community standards rather than strictly enforced by software. 74.192.84.101 ( talk) 00:03, 19 October 2013 (UTC)
"For this criteria/permission/etc to be meaningful, failure to meet this criteria somehow has to prevent users from creating articles nominated in AfC" (emphasis added). I think the 'somehow' is going to be, by manual admin intervention. If you have not satisfied the threshold, and you keep submitting perfect articles as AfC, which always pass with flying colors, who cares? If you have not satisfied the threshold, and you 'manually' create articles without the AfC helper-script, sooner or later an admin will make it their business to care, and call you out for disruption. 74.192.84.101 ( talk) 00:06, 19 October 2013 (UTC)
So, a completely social-based implementation. How does criteria play into this then? This approach winds up being a no-op and bringing us right back to where we started. Specifically, "If you don't meet our criteria, you can't play in our sandbox" just becomes "If you are being disruptive, an admin will intervene". However, that's already the case. We don't need an RfC or a bit or criteria or any of that to have admins deal with disruptive users. So, I'm quite confused as to what that accomplishes realistically. -- ShinmaWa( talk) 00:16, 19 October 2013 (UTC)
Those who do not meet the criteria will be slowed down significantly, and those who make mistakes and are warned and continue to make mistakes can rightfully be called disruptive. Likewise, those who have been given access to the tool and had it later revoked and who come back and "do it by hand" in a substandard way can also rightfully be called disruptive. Wikipedia already had mechanisms for dealing with disruptive editors. Revoking access to the tools for editors who are merely incompetent can slow them down enough to encourage them to think about what they are doing, which will hopefully mean they will have a higher rate of competent reviews. Let's suppose Joe Novice Wikipedian is trying to help out and somehow gets access to the tools and makes 30 reviews in 2 days, but botches half of them. He gets access to the tools revoked but he is determined to help out. Over the next 2 days he does only 10 reviews because he's been slowed down for lack of access to the tools. At worst, we have 10 reviews to re-review and 5 to clean up. But hopefully he'll be more accurate becuase he's working slower (and gaining experience as he goes) and only flub 2 or 3. davidwr/( talk)/( contribs) 00:42, 19 October 2013 (UTC)
I can certainly respect that. In fact, I even support this approach. It doesn't take the gun away, but it removes the fully automatic selector switch. There's certainly precedence for this with Twinkle and the like. However, this begs the question if this actually meets the consensus formed in the original RfC. While I opposed that RfC, many people didn't, and I suspect some supporters might see restricting just the script as being a half-measure. *shrug* Thanks for responding, davidwr. -- ShinmaWa( talk) 01:10, 19 October 2013 (UTC)
There are some very relevant comments in this thread, and I'll just reiterate that the consensus in the previous RfC was There is community consensus for the introduction of a requestable permission which will be required to review articles at Articles for Creation. - nothing more, nothing less, and that is what was asked for. Firstly, I believe even a half-measure is better than none at all, to the exclusion of any arbitrary automated granting of the access. Having a list of users who are 'authorised' to use the script is also a kind of 'half way' that we already have, but as I mentioned somewhere above, we need to get all reviewers on a list. Naturally if they get their flag removed, under the current technological aspect of the process, there is nothing to stop them continuing to do manual reviews; it would certainly slow them down, but we would know who they are. Secondly however, with a couple of thousand submissions in the queue, we don't know who is actually doing the reviews at all - we just don't have the person-power to do a double check on every submission that gets declined, moved to mainspace, or CSDd under an appropriate criterion. But we are diverging here - we need to set the criteria for permission first - and that shouldn't really be too difficult (we have enough examples cited above for the granting of various user 'rights' that do need official WMF approval) , then see how they can be technically or socially implemented. 06:06, 19 October 2013 (UTC) Kudpung กุดผึ้ง ( talk)
As mentioned by me and several other people, it is folly to attempt to separate the criteria from the implementation and it is awkward to attempt discuss one without the other. One impacts the other at a fundamental level. Further, many of the suggestions demand a certain implementation and/or precludes others. So, if we can't talk about implementation, then our criteria options become severely limited to stuff like edit counts and other similar statistics. In essence, the "no implementation" restriction steers down a very narrow set of options -- namely the options that you suggested at the top at the RfC. I think we need to look beyond that scope. -- ShinmaWa( talk) 02:55, 20 October 2013 (UTC)

What Shinmawa raises is a fundamental flaw, this RfC is invalid

A userright represents the ability to use a technical feature. Since this userright won't place any technical restrictions on anyone, there is no point at all in creating it. Access to the common scripts could be toggled with or without a userright. But they could still load the same exact script via their custom JS interface, and we can't stop them from doing that. So in my mind, the prior consensus is irrelevant because it is not possible to implement.

If there is a desire to create a socially enforced white or blacklist, then we should be talking about creating a process for that, and this RfC should be closed and reframed properly, with first a discussion about whether it should be a whitelist or a blacklist, before any criteria are proposed.

A blacklist makes the most sense to me, because there is nothing at all stopping someone who isn't whitelisted from processing AfCs, and if they do it correctly, are we going to really block them for failing to participate in the bureaucracy? Gigs ( talk) 18:31, 28 October 2013 (UTC)

Suggestion by Davidwr - Leave access to "AFC Comment" unrestricted

Leave the "Comment" button on for everyone by default.

If an editor abuses it, they can be blacklisted.

The kinds of comments editors leave are probably the best judge of whether they should get access to the rest of the buttons. davidwr/( talk)/( contribs) 00:31, 19 October 2013 (UTC)

I do not think that new people will bother activating the tool jsut to get the comment button. However I don't think that being able to comment is harmful. After all it is not that hard to edit the article and add a comment, even using the correct afc comment template is not that hard to do. Blacklisting against adding comments I suspect would be about equivalent to a topic ban. Since it is so easy to bypass I would not suggest implementing a comment blacklist. Graeme Bartlett ( talk) 21:01, 19 October 2013 (UTC)

Suggestion by Davidwr - Make it a "throttle" like AccountCreator

Tweak the AFC Helper Script so everyone can use the full set of tools on no more than a handful of different submissions in a rolling 2-3 day period.

Those who abuse the tools can be blacklisted. davidwr/( talk)/( contribs) 00:31, 19 October 2013 (UTC)

I assume that you do not want to rate limit it for every one, so the users with the permission can review faster. Although I suspect our bulk and speedy reviewers do make some errors too, such as we can see by the number of AFDs and prods that pop up. Also the stuff declined for a weak reason will not show as a problem that way, but just drive away contributors and content. However I do like the idea to do a rate limit for the people with no permission, but then also add their work to a special list for extra review by others. Graeme Bartlett ( talk) 20:54, 19 October 2013 (UTC)

Suggestion by Davidwr - many routes to full access to the tools

There shouldn't just be one route to get access to the full AFC Helper Script.

I'd give access to these buttons to anyone requesting them who:

  • is a long-time Wikipedia editor with no recent relevant problems
  • is grandfathered in because of significant recent AFC participation and no recent relevant problems
  • demonstrated competence through intelligent, accurate AFC comments or direct feedback to editors over an extended period of time and a significant number of articles
  • demonstrates competence through intelligent collaborative content-improvement in other areas of Wikipedia over an extended period of time and over a significant number of articles
  • is under the training or sponsorship of another experienced AFC editor, editors, "acadamy," or similar, or has been declared to be competent to have the tools by their sponsor
  • while not clearly making the cut on any one of the above, goes through a short (1-3 days?) discussion period and get the rights if there is a consensus to give it to them.

Revocation should be relatively easy, with the typical "appeal" taking the form of the 1-3 day discussion period outlined above.

Even after adoption, this list should not be cast in stone. davidwr/( talk)/( contribs) 00:31, 19 October 2013 (UTC)

This idea has overwhelming support. -- Mdann 52 talk to me! 13:42, 13 January 2014 (UTC)
The following discussion has been closed. Please do not modify it.
This sounds like a reasonable idea. It is better than a hard list of requirements that may seriously limit the numbers of new reviewers. Graeme Bartlett ( talk) 20:49, 19 October 2013 (UTC)
I particularly like davidwr's mentorship idea. When I started reviewing I hardly knew how to do anything, so I just started out asking questions and reporting problems on the Afc talk page and at the Teahouse, and other more experienced editors (usually Huon), would take action and I would see what was done and know what to do next time in that situation. — Anne Delong ( talk) 23:14, 19 October 2013 (UTC)
The mentorship idea is just a special "private tutoring" case of Buffbills7701's school idea (see "his" section above). I'm not sure if the original idea of a training program is Buffbill7701's or someone else's, it's been floating around for weeks if not months. davidwr/( talk)/( contribs) 01:59, 20 October 2013 (UTC)
This is entirely reasonable. MER-C 04:35, 21 October 2013 (UTC)
I like it. 78.26 ( I'm no IP, talk to me!) 11:54, 24 October 2013 (UTC)
Support This "many routes" idea sounds like the best suggestion yet. (I assume that, aside from the sixth or "discussion" option, the right could be awarded by any administrator.) -- MelanieN ( talk) 14:43, 24 October 2013 (UTC)
Complete and total support - This is the greatest idea I've seen. While there should be some kind of sieve to limit inexperienced or even malevolent editors from reviewing articles and destroying things, you cannot ignore the major backlog of AfC articles. Writing up a rigid list of requirements that admins must dig through edits to find is laborious for all parties involved and will make the backlog worse. The new "right" should be more to keep bad reviewers out than let good reviewers in. ö Brambleberry of RiverClan 15:11, 31 October 2013 (UTC)
Support, per Brambleberry; this is a really good idea. APerson ( talk!) 02:49, 11 November 2013 (UTC)
Support. At this point, it does not seem likely that any one of the proposals at the foot of the page will gain sufficient support for a consensus to emerge; instead, I'll endorse this "open access" or "flexibility" principle as the way forward. If a software-based AfC Reviewer permission is not going to be technically feasible, perhaps restrict access to the reviewing script dependent on being added to an official whitelist, in a manner similar to how access to AWB is currently regulated. Super Mario Man 02:43, 21 November 2013 (UTC)

Implementation detail suggestion by Davidwr - preventing moves

Withdrawn per "law of unintended consequences" as pointed out below by stefan2 at 13:23, 19 October 2013 (UTC). How did I miss that possibility? davidwr/( talk)/( contribs) 15:44, 19 October 2013 (UTC)
The following discussion has been closed. Please do not modify it.


Should there be a consensus to prevent non-approved editors from accepting articles, one way to do this is to bot-move-protect the WT:AFC page shortly after creation, then allow the AFC Helper Script to trigger a bot to do any required moves. This would not require any changes to MediaWiki software. davidwr/( talk)/( contribs) 01:21, 19 October 2013 (UTC)

I'm not sure I understand this suggestion. Isn't there more than one way to skin a cat, as ShinmaWa's question-section above points out? Use of the helper-script is optional, and I guess I don't understand why bot-move-protecting the WT:AFC page will add security. Is there really no other way to get an article created (or take an existing stub and get it renamed) without going through WT:AFC at all? 74.192.84.101 ( talk) 06:15, 19 October 2013 (UTC)
  • Oy vey... All of these unproductive subheadings and then multitudes of comments about stuff in other subheadings... I can't follow the thread of any of these discussions and this page has gotten way TL;DR overnight. Unless someone who has been following can create a convenience break with an overview summary of all the ideas in one section or get rid of all of the subsections above or re-arrange comments so that comments are in the proper section headings (very bad wiki-etiquette, please don't), I'm afraid I can't contribute to this discussion at this time. I just don't have two days to try and piece mail all of the badly fragmented discussions back together. Technical 13 ( talk) 12:25, 19 October 2013 (UTC)
  • Oppose If moves are made more difficult, then we are likely to get more copy & paste moves which violate the attribution requirement. -- Stefan2 ( talk) 13:23, 19 October 2013 (UTC)
I disagree with encumbrances necessitated by the weakest link or worst-case scenario. We ought instead to fortify an imaginable breech with effective countermeasures; which do exist.— John Cline ( talk) 03:20, 20 October 2013 (UTC)

Comment by James500

I was not aware of the existence of the previous RfC and I suspect that many others were not aware either. Consensus can change, so there is no reason why we cannot now discuss whether any new permissions are needed at all. James500 ( talk) 20:03, 19 October 2013 (UTC)

Well alternatives could be a whitelist or a blacklist of those who can or those who can't. Other ideas were a series of awards to indicate progress or achievement. And there should be hat for the hat collectors. We already have barnstars and a listing of project participants. Perhaps someone can vet the newly added names to see how they are going. Graeme Bartlett ( talk) 20:44, 19 October 2013 (UTC)
That's been dicussed further up. The problem is that currently, no reviewers are obliged to enter their names on that lit, hence we do nots always even know who is reviewing until problems come to light and are brought to the AfC talk page. Most issues are handled locally on the reviewer's talk page: 'Why did you decline my submission?' which begs the question: Why was the creator not provided with more detailed information?.
Hat collecting is an unavoidable but necessary evil. We get plenty of them at WP:PERM but we are fairly good at filtering them out. Kudpung กุดผึ้ง ( talk) 03:23, 20 October 2013 (UTC)
The 'why did you decline my submission' enquiries occur even if you do explain the reasons when declining. Particularly troublesome are autobiography and WP:COI as a decline (even on material previously declined by another reviewer) often gets a flood of WP:OTHERSTUFFEXISTS and "but I worked so hard" pleas as to why the author really deserves to have their own article. This will continue even if you create roadblocks to entry for new reviewers. K7L ( talk) 21:56, 20 October 2013 (UTC)

I don't like any of the proposals that have been made, but I think that a blacklist of those who have demonstrated that they are incompetent, compiled by human beings, would be the least worst option. James500 ( talk) 07:06, 24 October 2013 (UTC)

Suggestion by TheOriginalSoni

Of all the solutions, I found Ross Hill's solution to be the most practical and useful, and hence I propose the following steps for selecting the AFC reviewers, based on a few adjustments I think should be made on it

  • A selected few active and/or trusted reviewers will be grandfathered in. The exact details of how it will be done will be decided later.
  • Anyone who wishes to become an AFC reviewer would be submitting their reviews of at least 10 articles currently at AFC. This would be done at a special requests page for
    • The review must be clear on why it is rejected, and any other such comments.
    • There must be at least 3 declines and 3 approvals among those submitted reviews
    • The reviews should be among pending submissions at the time of submission
    • Once any particular review is submitted, there should be no changes to it.
  • These reviews are all open for comment from any current AFC Reviewers, who may choose to "Endorse" or "Disagree" with a particular review.
  • Any article among the list which gets rejected or accepted externally would auto-count as an endorse or disagree by itself.
  • After a period of time/ after all the reviews have been looked into, a designated person (the qualifications of which will be decided in future discussions) would close the request as pass or fail. In general, 8 or more correct reviews would count as pass, and 6 or less correct ones would be a fail.
  • [Additional proposal under discussion] Any sufficiently trust candidates who have demonstated enough competence might not be required to go through this process, but handed over the tools directly on request.

This is the general schematic of how I think it should proceed. Every specific point in this suggestion is open for discussion, and would be altered as per consensus and common sense. TheOriginalSoni ( talk) 00:42, 21 October 2013 (UTC)

Support Because reviewing skill is what matters, so that should be what we test. Ross Hill ( talk) 00:59, 21 Oct 2013 ( UTC) 00:59, 21 October 2013 (UTC)
Support as ONE way Oppose as THE ONLY way. Anyone who comes in having already demonstrated competence regarding content guidelines/policies and who doesn't have anything negative should be given a pass on this. Basically, any editor who has an edit history that would make them a credible candidate at RfA (I didn't say he would pass, just that he wouldn't be WP:SNOW-closed or otherwise fail miserably) and who doesn't have any thing negative in their recent history should not be required to do more than ask for access to the tools. The same goes for editors who might fail miserably at RfA only for reasons not relevant to AFC work. davidwr/( talk)/( contribs) 01:57, 21 October 2013 (UTC)
  • I failed to notice this point. I agree that WP:IAR should apply to obviously trusted candidates and they shouldn't have to go through the entire process. But at the same time, I wonder if there is any harm in having them go through this simple enough process. If others also agree to the additional proposal, I'd be willing to add it. TheOriginalSoni ( talk) 09:33, 21 October 2013 (UTC)
Neutral Overall those points look good, however the no more than "7/10 one direction" rule is going to jump up and bite a lot of hopefuls. Hasteur ( talk) 13:55, 21 October 2013 (UTC)
I'm assuming that the intent is for the candidate to have at least 3 approves and at least 3 declines among the 10 reviews, so that his competency on both approvals and declines can be evaluated. A person may be fine when evaluating an article that should be declined but he may routinely over-decline and mis-evaluate things that should be approved, or vice-versa. Too many errors in either direction is counter-productive. davidwr/( talk)/( contribs) 16:14, 21 October 2013 (UTC)
The problem I was trying to indicate is ast least in my experience, I do about 80 to 90% decline simply because it takes a lot of effort to get a submission up to the level that I would pledge my reputation to the submission by accepting it. Hasteur ( talk) 23:43, 21 October 2013 (UTC)
  • Even then, I am of the opinion that there should be some limit of this sort to check for both sides of whether the reviewer knows the policies. If your concern is indeed correct, maybe we could lower it to at least 2, but I wouldn't want to remove it. TheOriginalSoni ( talk) 13:07, 22 October 2013 (UTC)
Sure, we need proof that the person can approve at least 3, and decline at least 3, and we want to have at least 10 example-decisions to look over. Rather than saying that they must have ten cases, and they must approve 3 of *those* ten, and decline at least three of *those* ten, instead make this the rule: There must be no more than 7 declines or approvals among those 10 reviews The ten selected example-reviews *must* include at least 3 approves, and at least 3 denials; note that the reviewer-candidate often may actually need to review more than ten actual cases, to achieve 3 of each type... but only ten selected cases (including at least 3 approves and at least 3 denials) will really "count" when determining whether the reviewer-candidate passes the examination. HTH. 74.192.84.101 ( talk) 21:21, 4 November 2013 (UTC)
  • @74 Does the current wording of the proposal make more sense, or should there be further rewording on it? TheOriginalSoni ( talk) 07:45, 6 November 2013 (UTC)
Looks fixed to me. I noticed a spelling error and fixed it, while I was here. That said... I think your idea, like my own suggestion elsewhere on this same page, is testing the "wrong" thing for what Kudpung is really trying to accomplish. See my TLDR explanation below. At this time, I've collapsed mine, for resubmission as part of a future RfC discussion.
  The motivating problem (unstated in the RfC-intro-text which was a mistake) seems to be that Kudpung only want editors that are Ethically Committed To Wikipedia's Values to be able to perform AfC-review-approvals. There are incidents where a spammer will create an account, 'review' a small set of AfC submissions -- often given *randomized* answers which is awful for both the submitters and for the NPP folks that have to clean up the mess later -- and then approve ten of their own blatantly promotional submissions. This is particular bad when socking is involved, because without checkuser (which everybody is rightly *very* hesitant to go handing out all over the place), you end up with what looks like one username submitting to AfC, another seemingly-unrelated username adding some cites, a third username reviewing-and-approving using the AfC-helper-script, and then several 'other' usernames which make more changes to the article once it is in mainspace. But it is all the same person, or same spambot!
  Very tough to fight, right now. Even worse, the sockpuppet could pass *your* quiz, though, right? Because it only takes 8 out of 10... and then they are free to approve several hundred spamvertisments, before they finally get caught. The same problem applies to my suggestion: a motivated spammer can pass my ten-or-more quiz, just like yours. Anyways, long story short, it turns out this RfC is not about passing the 80%-correct-mark... though that skill is still crucially important, it is orthogonal. This specific RfC is about moral-n-ethical *secondary* criteria (e.g. min-edit-count to prove you love wikipedia), whereas what you and I are testing is technical-n-policy *primary* criteria (e.g. ability to get 8 out of 10 reviews correct). Suggest we submit our ideas to another, future RfC. Hope this helps. 74.192.84.101 ( talk) 22:31, 18 November 2013 (UTC)

Suggestion by Pol430

I worry that asking potential reviewers to conduct trial reviews leaves too much room for 'instructor creep' and who will assess their performance? One person or more than one? The idea strikes me as fertile ground for creating a 'priesthood of gatekeepers' or turning the process into pseudo-RfA. I think we need to keep the process as simple as possible with a fairly black and white set of metrics to work to. Also, whatever form this permission takes, it should be transparently requestable via a noticeboard in the same way as other permissions. In my involvement at AfC, I have found that reviewers need to be able to demonstrate the following essential qualities:

  1. Must be able to judge what constitutes vandalism, attack pages, and wholly negative unsourced BLPs
  2. Must be able to identify copyright violations
  3. Must be able to recognise WP:ARTSPAM and blatant hoaxes
  4. Must demonstrate a sound understanding of notability, verifiability/reliable sourcing, and the BLP policy
  5. Must be able to communicate with patience and clarity with new editors

I believe that these qualities would be best evidenced against the following criteria:

  1. Must have carried out at least 50 good vandalism reverts -- a common threshold for granting of rollback (includes the speedy deletion of pages as blatant vandalism).
  2. Must have correctly identified more than 5 attack pages or wholly negative BLPs, by whatever means.
  3. Must have correctly cleaned up 20 articles with copyright concerns or correctly nominated 15 pages for speedy deletion as blatant copyright violations.
  4. Must have copy edited/cleaned up at least 20 articles to make them NPOV compliant or correctly nominated 15 pages for speedy deletion as blatant spam/advertising.
  5. Must have participated in at least 20 AfD discussions and !voted/commented with correct policy-based observations that demonstrate knowledge of notability, verifiability and reliable sourcing.
  6. Must have demonstrated a sound knowledge of BLP Policy issues, by whatever means. For example, working at the BLP noticeboard.
  7. Must have demonstrated an ability to help and work patiently with newer editors. For example, tea house host, adoption, help boards, user talk page assistance.

These minimum criteria could be assessed by any administrator patrolling the noticeboard, but should be rigidly applied. In the case of the right/permission being abused, any administrator may remove the right as a discretionary sanction in the same manner as other rights. Pol430 talk to me 18:00, 21 October 2013 (UTC)

I've been an editor and AFC-participant for many years and I don't think I meet all seven of the items on the bottom list, and I know that I have weaknesses in notability in certain subject areas and an inability to communicate with patience and clarity with certain editors. I'm also not as good at detecting advertisements disguised as articles as I would like, but I am getting better at that with experience. davidwr/( talk)/( contribs) 19:51, 21 October 2013 (UTC)
I'm pretty sure that you have made 50 good reverts in your Wiki career and most of the CSD criteria would be easily evidenced by someone who spent a few months patrolling new pages. Equally, participation in 20 AfD discussions is not hard for most long-serving Wikipedians to evidence. Knowledge of BLP policy can be demonstrated by various means and I think your interaction with users on your talk page demonstrates point 7 just fine. I think notability is an area that AfC can sometimes get a little hung up on. In terms of notability, AfC's job is to keep out articles about obviously non-notable subjects; this includes cases where a very solid policy-based argument for not including a subject can be made. Where notability is borderline, then articles need to have the opportunity to receive community discussion about their inclusion in Wikipedia, this means accepting a submission without prejudice to it being nominated at AfD. In cases where notability is difficult to establish because of the specialised nature of the subject area then help may be forthcoming from a relevant Wikiproject. If not, we still have an obligation to AGF and accept a submission without prejudice to an AfD nomination -- that is where the responsibility for ruling definitively on a subject's notability lays. Pol430 talk to me 16:40, 22 October 2013 (UTC)
Huh? First you said "keep it simple" and then you came up with the most complicated possible process. You laid out seven specific numerical criteria which you think should be "rigidly applied". Who in the world (either applicant or administrator) is going to go through histories counting how often someone has cleaned up copyvio or identified attack pages? This process would be unworkable, and furthermore it is not based on any evidence that these things would matter. I agree with "keep it simple", namely, let administrators review the person's contributions and decide if they seem competent enough for the task. Period. -- MelanieN ( talk) 21:39, 23 October 2013 (UTC)
Good luck with trying to search my 30,000+ contributions to check that I pass all seven "must have" criteria. Roger (Dodger67) ( talk) 09:58, 29 October 2013 (UTC)
I recognise that cross-checking those seven criteria would be laborious, but I thought the purpose of the exercise was to ensure high standards rather than dish out a new hat as quickly and widely as possible. I have struck out the criteria that were so evidently wide of the mark. Thanks for your feedback. Bellerophon talk to me 00:10, 31 October 2013 (UTC) (formerly Pol430)

Comment by Brambleberry of RiverClan

The list of articles waiting to be reviewed is backlogged enough, so while I agree that we do need something to make sure reviewers are qualified, those standards should not be so high that only a select few can access them. I think that the criteria should be rather vague, leaving it up to a case-by-case basis. There can be a few strict ones, like a certain amount of article space edits, but things such as "must have rollback and/or reviewer rights" seem a bit too constricting and would be thoroughly unconstructive to the main purpose: reviewing articles to add to Wikipedia. ö Brambleberry of RiverClan 23:48, 21 October 2013 (UTC)

I agree with this. The process should be simple, not stringent; we are simply trying to stop the current situation where unsuitable and/or inexperienced editors are trying (mostly in good faith) to review at AfC without sufficient knowledge of Wikipedia policies. IMO the AfC Reviewer right should be awardable by any administrator who believes the user has sufficient relevant experience to know an acceptable Wikipedia article when they see one. We trust administrators to make far more difficult/controversial decisions than this, and I don't really think Wikipedia will suffer any harm from letting them use their judgment in awarding this right. The qualifications for Reviewer, as listed at the top of this discussion by Kudpung, would serve equally well as qualifications for AfC Reviewer, but the one should not be a prerequisite for the other. As for Rollbacker, that right is both trivial and annoying; personally after having it (and cussing at it) for six months I asked that it be removed. Presence or absence of a Rollbacker right does not in any way reflect the user's ability to review submitted articles. -- MelanieN ( talk) 21:31, 23 October 2013 (UTC)
Part of the reason for the backlog is that many experienced users will not participate. One reason is the many useless, complicated ,and counterproductive procedures in the AfC process, for which see my user talk special archive. But the main reason is that unless most reviewers are moderately competent, what a good reviewer can contribute will be wasted. there's no point in contributing to processes which work poorly and on which one can not make an impact. Otherwise there is a much higher priority for anyone who knows what to do--which is checking their work, and trying to teach those who most need it. Ten good people without interference from the unqualified can do the process better than ten good ones trying also to cope with fifty unqualified.
If we cannot get high standards, we will need to see this only as a first screen, and the accepted articles are going to have to go into NPP so they will be checked a second time. As for the wrongly rejected, they will mostly continue to be lost to us. DGG ( talk ) 04:58, 25 October 2013 (UTC)
If the commonly used tools do not maintain a log page, they could be modified to do so. Gigs ( talk) 18:43, 28 October 2013 (UTC)
DGG, a very accurate summary, and so much of it applies equally to NPP. Allowing them through to NPP would be counter productive, the NPP system has the same kind of flaws as AfC and there is no guarantee that the patrollers, who need no qualifications at all, will pass or tag such an article correctly. Most worrying of course, are the 'lost' incorrectly rejected articles, while a significant concern is whether articles are correctly checked for spam or copyvio etc. (BTW: I have taken the liberty of correcting the link to your talk page archive - that thread is very important and although long, I would recommend the participants here to read it). Kudpung กุดผึ้ง ( talk) 07:09, 29 October 2013 (UTC)
A quick note regarding wrongfully rejected articles – that is also an editor retention issue ... if newcomers are being encouraged to send articles to AfC under the guise that "an experienced reviewer will double-check everything before sending it to mainspace" (which is usually what they are told at places like the Teahouse, and I at times am the one telling them that), then that is a problem. I think DGG's comment regarding sending pages to NPP may have a valid point, however agreeing with Kudpung, NPP draws inexperienced reviewers as well, but at least if you have two chances to catch a problem, that is better than only one. Nevertheless, the more I read about this and think about this, the more I am convinced that the new AFC academy is a good idea if people actually use it and have a desire to do things correctly, and frankly, perhaps a user right is in order. I would think anyone trusted with reviewer or autopatrolled would have necessary qualifications to review new articles, but I don't know for sure. I know user rights mean more bureaucracy, and a manufactured debate over the haves and have nots, but at the end of the day, bad reviewing of AfC and NPP has ramifications on copyright, editor retention, and, perhaps most importantly, missing content that can fit into the breadth of the world's knowledge; that is what we need to protect in these discussions. We can discuss whether someone should have 500 edits or 750 all day long, but that is not what is important. We need people who simply know what they are doing, and if they are doing things wrong, we can firmly, yet gently suggest they utilize training of some kind, and if they refuse that, they simply must be told to stop, as they hinder progress. I think the best way to maintain our NPP and AFC processes would be if experienced editors – article writers, content gnomes, admin, etc. – would all simply commit to reviewing x articles per week, and keep up with it. That would prevent massive backlogs, improve the quality of the reviews, and reduce potential ensuing burnout from one person trying to simply bust the backlog on their own. Go Phightins ! 10:46, 29 October 2013 (UTC)
Another very appropriate comment. However, have you tried herding cats? It works, but you have to give them something. Kudpung กุดผึ้ง ( talk) 11:04, 29 October 2013 (UTC)
@ Go Phightins!: totally agreed. -- phoebe / ( talk to me) 19:29, 30 October 2013 (UTC)

Comment from Phoebe

I don't have an opinion on the technical details of a right, how it is implemented, what the threshold is, etc. But I am worried, in general, about the impact of AfC on new users. The difference between a constructive, welcoming review -- even if the article isn't really up to par, a constructive review can still be made -- and a snarky or brusque one (made for whatever reason, including working fast because of the backlog) is huge for a new contributor. If a right can help with standards-setting among AfC reviewers on interacting with new users -- and maybe even make AfC a more attractive place to participate for experienced editors -- then I'm all for it.

I am well aware of our backlogs and the huge amounts of spam etc. But AfC is also a touchpoint for hundreds of new contributors who if they make it to AfC in the first place are generally also well-meaning and interested enough to perhaps be converted into active editors. Currently, AfC is sort of a Wikipedia backwater, and I feel like it should be front-and-center as a place for us to triage and work. I think a right if done well *might* help with this -- so to the extent it does, I'd support it. (If, however, it turns into simply 'one more collectible thing' as someone else pointed out, or somehow limits participation in AfC by existing helpful reviewers, then I wouldn't). -- phoebe / ( talk to me) 19:27, 30 October 2013 (UTC)

I certainly agree that it should be a 'front-and-center' operation and akin to the importance of NPP which was granted a complex set of tools by the Foundation. However, alone the 60,000 abandoned G13 drafts, of which I have physically deleted several hundred, demonstrate that what comes through AfC includes a vast amount of totally unacceptable junk, often far worse that what comes through NPP, and the fact that the creators have gone through the Article Wizard or AfC does not prove at all, unfortunately, that they are all good faith submissions. At AfC there is a cohesive and supportive dedicated team driving things forward; NPP has nothing of the kind bar its instruction page, has a talk page that sees a message once in a blue moon, needs no qualifications, and suffers from the same ailments as AfC. Kudpung กุดผึ้ง ( talk) 04:42, 31 October 2013 (UTC)
NPP has one advantage over AFC: By definition, every page they looked at was created by an autoconfirmed or confirmed editor. davidwr/( talk)/( contribs) 15:21, 31 October 2013 (UTC)
by G13 drafts you mean random userpage drafts, right? 1) If so, I don't know why you or anyone else would delete these; userpages are meant for drafts, and perhaps except in extreme libel situations or similar are doing no one any harm even if they're not destined to be good articles. 2) Not sure how this relates to the good-faith-edness of AfC. When I teach people how to edit, I tell them to start in their sandboxes. By your measure, if their userpage drafts aren't up to speed they're not contributing in good faith? That makes no sense; these are two different measures. Good faith is largely unrelated to whether the article is complete, referenced, notable, etc. And I've looked at enough AfC submissions myself to be pretty sure they're not all "Johnny sucks" or similar. -- phoebe / ( talk to me) 15:43, 31 October 2013 (UTC)
See WP:CSD#G13, a relatively recent speedy deletion criterion which specifies that AfC submissions which have not been edited at all (not even a keystroke) in more than 6 months may be deleted. DES (talk) 16:00, 31 October 2013 (UTC)
Yes, there are many good (or eventually good) submissions to Afc. As well as beginning editors, it's also widely used by COI editors who want to make sure that their articles won't be deleted as advertising. Afc reviewers help tone these down. To date there have been over 34,000 successful accepted submissions, and most of them left Afc in far better condition than when they arrived. Here are the ones accepted this month: CatScan report Also, articles eligible for deletion under the G13 criteria aren't always deleted; there are a number of editors who are checking through them and picking out ones to improve. — Anne Delong ( talk) 08:20, 1 November 2013 (UTC)
Thanks for the pointer to the CatScan tool Anne. That's very useful. Steven Walling (WMF) •  talk 05:52, 7 November 2013 (UTC)

Research needed?

Hey all. I don't have an opinion about the RFC in question, at least in an official WMF capacity. However, my team is just barely beginning to explore potential improvements to article creation. As a part of this, myself and our research scientist are working on measuring the current state of article creations and creators each month. That includes the volume at AfC, which though unique to English Wikipedia, is obviously an important route for new authors here. If you can help us think of strategies for accurately measuring the number of submissions, as well as decline/accept rates, that would be most welcome. Our notes are at Research:Wikipedia article creation. Many thanks, Steven Walling (WMF) •  talk 05:57, 7 November 2013 (UTC)

As one Foundation staff member has emphatically suggested that AfC is niether in the interest of nor within the remit of the WMF, I'm rather surprised to see this. AFAICS, the community has therefore accepted to investigatigate the possibilities of its own local solutions for improvement to AfC. However, any research that can save volunteers' time would be most welcome. That said, the project you linked to may appear to be a duplication in part of the buried(?) project here and here which, along with Page Curation, was offered as an olive branch to WP:ACTRIAL; it saw no further development. Kudpung กุดผึ้ง ( talk) 18:09, 7 November 2013 (UTC)
Yeah I don't mean to suggest that we're interested in making software updates to AfC as it exists now. Rather, that any new article creation software support we build needs to take in to account lessons from AfC, and the beginning of that is understanding the volume of submissions, the success rate, and so on. Steven Walling (WMF) •  talk 20:34, 7 November 2013 (UTC)
@ Steven (WMF): The feedback from en's AFC team to you would probably be best done in a central location. Where would you like us to do it? davidwr/( talk)/( contribs) 20:45, 7 November 2013 (UTC)
@ Davidwr: A good question to which I don't have the perfect answer. Most helpful for us is going to Research talk:Wikipedia article creation. But if people have comments and want to stick to WT:AFC for now, I'd be okay with that. Steven Walling (WMF) •  talk 00:28, 8 November 2013 (UTC)
@ Steven (WMF): - then perhaps you should take a look in your talk page archives at the thread you allowed to die out. Kudpung กุดผึ้ง ( talk) 04:52, 9 November 2013 (UTC)
Stevan, we do not want or expect the WMF to know how to improve page creation, except by implementing whatever requests for technical features the community here decides on. But it is always helpful if people new to a problem take a look at it, because they may well see things those of us who have been specializing in it may miss. DGG ( talk ) 05:59, 10 November 2013 (UTC)
Given that A) many people at the WMF are community members B) we spend countless hours doing research in to the quantitative and qualitative characteristics of activities like article I think you probably would be surprised how much we know about activities like page creation. ;) We're not just janitors sweeping things up and taking requests these days. Steven Walling (WMF) •  talk 01:23, 20 November 2013 (UTC)

Yet another suggestion

What if, were this change to be implemented, we only allowed people with the AFC reviewing userright to view the AFC submissions, not just review them? Because they can be potential copyright violations, and, given that anyone can create one, may also contain defamatory material. Jinkinson talk to me What did he do now? 23:10, 14 December 2013 (UTC)

This would "break the wiki" - even if those who had edited the page before were allowed to see it, if I submit an article with a dynamic IP address then come back the next day with a different IP address, I would be unable to improve the submission, defeating the whole point of AFC. davidwr/( talk)/( contribs) 02:10, 15 December 2013 (UTC)

Technicalities

Back on track, or partly - because there are mixed opinions whether an MedWiki-independent solution could be achieved, there is something for our resident programmers to look at: here. Other ideas may be coming soon, but I still feel that a set of criteria comes first, then to see how they can best bee implemented. Kudpung กุดผึ้ง ( talk) 03:05, 5 November 2013 (UTC)

In looking at your question to this user, you specifically asked We are having a discussion on how to implent[sic] a local user permission system for a script that is used at WP:AfC. (Emphasis mine.) I'm sorry, but when did this discussion get reframed to be just the script? That is a broad departure and narrowing of the stated purpose of both this RfC and its predecessor. Additionally, you keep saying that we should not be talking about implementation (even though 3 of the 5 of your own examples at the top speak directly to implementation), but then you frame this RfC as an implementation discussion (and specifically, your preferred implementation) to people like West.andrew.g. Frankly, this RfC is fundamentally flawed and really needs to be blown up and redone. -- ShinmaWa( talk) 23:02, 8 November 2013 (UTC)
I can't agree. This RfC is about setting a suitable criterion or criteria for permission to review article submissions at AfC. You have incorrectly interpreted the examples of permissions cited in the preamble as being suggestions for the creation of a MedWiki solution, which the Foundation has clearly stated will not be entertained anyway. I have repeated many times that when those criteria have been agreed on, then we should look at how they could be technically or socially implemented. Any preemptive research into possible local or non MedWiki technical solutions has nothing to do with setting the criteria. And BTW, there is more research going on than only the message to Andrew. Kudpung กุดผึ้ง ( talk) 04:49, 9 November 2013 (UTC)
"You have incorrectly interpreted the examples of permissions cited in the preamble as being suggestions for the creation of a MedWiki solution". No, I didn't. Not once. Not in thought, not in words. That's a complete fabrication on your part. I was actually referring to the fact that your background examples include implementation details such as admin interaction, script developer interactions, and whitelists, which conveniently enough seem to overlap with the implementation solution that you are "preemptively researching". Funny that. However, in addition to completely fabricating my words and intent, you have also failed to address my main point that you have framed this discussion externally as how to "implement a local user permission system for a script" while at the same time insisting that no one else discuss any competing implementation ideas, which seems to me that you are using this RfC as nothing more than a thin facade of consensus building to force the implementation of your preferred solution. -- ShinmaWa( talk) 05:57, 9 November 2013 (UTC)
I don't have a preferred solution other than hoping that the community will come up with some criteria for sufficient experience for reviewers. All I have done is cited some examples as possible leads, but they are absolutely neither my recommendations nor preferences, I simply made the first suggestion to get the ball rolling, and I am as entitled to make a suggestion there are you are. Having reviewed every further comment I have made, I don't see me insisting on them; more to the point, I have simply attempted to keep this discussion on track. I stress again that any possible implementation of such criteria should/would come later. There is no harm whatsoever in looking into how permissions for Stiki, Huggle, or AWB are locally implemented - it's called 'gathering knowledge'. I don't see how you or anyone can suggest I have claimed otherwise. I am tempted to view your accusations as lacking in good faith. If you have some suggestions for criteria, please make them, but this RfC is not for redebating whether AfC needs competent reviewers or not. Kudpung กุดผึ้ง ( talk) 06:49, 9 November 2013 (UTC)
Where have I redebated whether AfC needs competent reviewers? Again, you are putting words in my mouth. While I came to this discussion assuming good faith, you have shaken that assumption. I am moving on to other things and will no longer participate here as this RfC is not a request for comments but a request for confirmation. -- ShinmaWa( talk) 18:34, 9 November 2013 (UTC)
ShinmaWa, methinks I can understand the ongoing back-and-forth here. I was personally confused about what Kudpung was trying to accomplish, myself, also, but believe I'm on the same page with them now. (Due to my confusion, earlier, my suggestion-by-74 above absolutely positively demands a very specific implementation -- very different from what Kudpung envisions I will not -- but more importantly solves a completely different problem!) See deeper explanation below. Hope this helps. 74.192.84.101 ( talk) 21:23, 18 November 2013 (UTC)
As I understand it, *this* discussion, on *this* page, is about trying to find consensus for a reasonably *specific* set of secondary criteria (like edit-counts) that are specific to helping guarantee that editors that sign up to be AfC reviewers are morally competent for that role. 74.192.84.101 ( talk) 21:23, 18 November 2013 (UTC)

What is the motivation for this RfC?

The motivation is, reading between the lines, there are plenty of examples -- of increasing frequency if I correctly read between the lines -- of new editors with WP:COI difficulties signing up as AfC-reviewers, and then approving the blatantly-policy-violating-articles of their buddies, or in some cases of themselves. To stop such shenanigans, we need to agree on a set of secondary criteria (minimum edit-count being the most obvious). Then, once we have got consensus on the thing we will be using to secure the AfC process against abuse, there would be a discussion about how to best implement -- in software or in human-administered-policy or whatever -- some sort of security mechanism that *enforces* those secondary criteria.

  The mechanism itself, Kudpung does not wish to get bogged down in, as yet... but that topic is supposed to be the very next RfC, right after this one! Also, since Kudpung is not a programmer, that makes it hard for them to be the host a mechanism-oriented discussion (as opposed to this current policy-oriented RfC). But the point is, that the nuts-n-bolts implementation mechanism... although it will clearly have *something* to do with software that *some* sort of programmer will have to mess with at least some of it... would ideally be out of scope (aka "off track" or perhaps rather "cart ahead of the horse" or somesuch homely metaphor), at least until we decide upon what specific secondary-criteria we are actually trying to secure! Note well the careful use of ideally. Furthermore, we do have a few relevant facts, that are "implementation" facts, but which may influence our discussions here about "criteria-slash-policy" decisions.

  1. First, the WMF will not be footing the bill. That means, the implementation has to be simple enough that volunteer hackers, here on enWiki (like perhaps User:mabdul) to implement on a spare-time no-pay basis. That is why suggestions to modify mediawiki are out of line: we do not want to fork mediawiki just for enWiki's use!
  2. Second, *most* of the folks already working in AfC today, are already using the existing javascript-based AfC-helper-script-gadget (which is maintained by User:mabdul and others), and it makes sense that whatever secondary-criteria-security-solution we come up with, should interface with our existing wiki-tools. That is the 'script' that Kudpung speaks of, nothing more, nothing sneaky going on here.
  3. Third, and finally, it is a plain-and-indisputable-fact that we would like whatever 'implementation' mechanism is chosen to be low-bureaucracy-required, because there are literally thousands of AfC-submissions pending in the queue, and anything that takes our AfC reviewers away from that queue, is a Bad Thing. That is why any solution involving laborious additional tasks for the existing AfC reviewers is seen as strongly counterproductive; they are already under too much pressure now, and adding these criteria cannot help, and might easily hurt.

Finally, in terms of out-of-scope discussions, we have my own suggestion, which I now understand is "off topic". The separate issue, which I concentrated on in my suggestions, is whether it is possible to assess *primary* criteria, namely, whether a given AfC-reviewer-job-candidate is actually any good aka technically-competent at performing reviews (without later getting reverted for mistakes). This is my main concern... but this question is utterly orthogonal to the question of whether an AfC-reviewer-job-candidate is any Good aka morally-competent at performing reviews (without later getting banned for abuse). Both types of competence are important, sure... but only the morally-competent secondary-criteria are under discussion here. Well, that is to say, those are what ought to be under discussion here.

  Kudpung tried valiantly to explain what was going on, but most people misinterpreted the actual intro of the RfC, which used examples in a way that looked like preferred-outcome, and which failed to inform newcomers like myself that the motivation for the whole shebang is prevention of WP:PUPPET folks abusing the AfC queue. Stopping that sort of behavior requires moral-competence, and technical-competence is a distinct issue. Most discussions above are trying to solve all three problems simultaneously: implementation details, technical prowess at AfC duties via primary/secondary criteria (in the relevant decision-areas), and moral competence at AfC duties via secondary-criteria (in terms of ethical-commitment-to-wikipedia-metrics).

  Anyways, while I disagree that Kudpung has tried to ramrod some particular implementation down our throats, I cannot disagree that the current RfC is in trouble. Either we need to have an arbitrary-section-break, with a rewritten-motivation-and-examples section, so we can then copy the proposals down there that *specifically* address the moral-competence and the ethical-commitment-to-wikipedia angles (only!), or alternatively, maybe even take ShinmaWa's suggestion to deploy the WP:TNT, and reopen round-two of this RfC with the rewritten-motivation-and-examples. I will ping ShinmaWa about this long-winded explanation, and hope that they return to assist us. 74.192.84.101 ( talk) 21:23, 18 November 2013 (UTC)

Better alternative - Close AfC

It's outlived its usefulness and is run by a clique of editors who treat it like a personal fiefdom operating under its own rules, ignoring rules that govern the project as a whole, and beat away those contributors who think differently (despite being well-supported by those ignored policies and guidelines). If anyone wants to create an article, let them open an account and create the article already--let speedy deletion or AfD deal with it if it should be deleted. Clear out the backlog, get rid of the endless drama and fiefdom-ownership politics, and let this dinosaur finally die. -- ColonelHenry ( talk) 21:09, 30 December 2013 (UTC)

Round 2: Straw poll

We've had the discussion, now it's time to gather consensus. To reiterate, the above discussion was about setting criteria for allowing users to review pages submitted to AfC. There was no mention in the proposal that the methods of implementation or other methods of reviewer control were up for discussion. It was stated that the criteria should come first, then the community can discuss how best to implement them. This straw poll is not for discussing the implementation either. The criteria mentioned in the preamble were cited strictly as examples only and were not suggestions either for what we should do, nor for a traditional 'user right' implementauion.

There are two major issues concerning reviewing at AfC:

  • Poor quality of reviewing.
  • Abuse of the system.

Proposal 1

To review pages at Articles for Creation, users should have made a minimum of 500 non-automated edits to en.Wikipedia mainspace, with an account registered for at least 90 days.

  • Support, as proposer. Kudpung กุดผึ้ง ( talk) 23:49, 18 November 2013 (UTC)
  • Support - a sensible amalgamation of the aforementioned ideas. Not too stringent, not too lenient. Ultimately, I think this is the best way to go. Go Phightins ! 01:22, 19 November 2013 (UTC)
  • Support Let's take into account that before this, there was basically no requirement. This proposal screens out obvious new users and does not create an opportunity for a backlog to occur of those seeking the AfC reviewer permission and is objective, not subjective. Ramaksoud2000 ( Talk to me) 03:22, 19 November 2013 (UTC)
  • Oppose any requirement on second thought. If someone wants policy-violating material in the mainspace, they can simply create it themselves. autoconfirmed to move the page is enough and is more than the requirement to create articles the normal way. Ramaksoud2000 ( Talk to me) 18:37, 30 December 2013 (UTC)
  • Support - It's simple, unambiguous and straightforward, and anyone who doesn't meet the criteria can do so with time and experience. Ritchie333 (talk) (cont) 14:50, 19 November 2013 (UTC)
  • Support - I like it because it assumes good faith and allows everyone with a little experience to take part. There needs to be a way to prevent misuse, but there is already the "topic ban", which could be used in case of problems with specific editors. I assume that these would be 500 undeleted edits, so that spam and copyvios wouldn't count. — Anne Delong ( talk) 15:26, 19 November 2013 (UTC)
  • Oppose as I feel this is too lenient. See proposal 3 below (as much as I hate to make another proposal splitting up the votes...) Technical 13 ( talk) 15:56, 19 November 2013 (UTC)
  • Support. It's a low bar, but at least it's a bar. The documentation should indicate somehow that this is not an entitlement to review. -- Anthonyhcole ( talk · contribs · email) 03:03, 21 November 2013 (UTC)
  • Support - A nice bar that will allow anyone with good faith and a decent handle on Wikipedia to work. Will prevent an insane backlog from forming. Nice and simple. ö Brambleberry of RiverClan 16:09, 27 November 2013 (UTC)
  • Support, as the lowest proposed bar. Ironholds ( talk) 07:41, 2 December 2013 (UTC)
  • Support low bar with minimal "overhead". All it requires is a "filter" to be added to the AFCH script that simply checks the user's mainspace edit count and registration date. It doesn't add to the workload of the existing reviewers. This criterion will also be easy to carry over to whatever review mechanisms will be implemented for the upcoming Drafts namespace. Roger (Dodger67) ( talk) 09:40, 2 December 2013 (UTC)
  • Support- minimal standard. Rankersbo ( talk) 10:51, 9 December 2013 (UTC)
  • Support with one addition, namely this: any two approved-at-the-time AfC reviewers X and Y, can by mutual agreement, appoint a third person Z, thereby making Z an AfC reviewer, despite Z not meeting the criteria. 74.192.84.101 ( talk) 16:15, 9 December 2013 (UTC)
  • Support. This is certainly not burdensome, and if anything is too lenient. I think the second proposal, just below, would create additional workload for whoever does the reviewing, and the third proposal really isn't a significant improvement on this one, so I support this one as a step in the right direction. -- Tryptofish ( talk) 21:02, 12 December 2013 (UTC)
  • Monumental oppose for the reasons I have given in proposal 5. James500 ( talk) 13:57, 31 December 2013 (UTC)
  • Support, This is the only practical workable proposal I see. Alanl ( talk) 08:15, 12 January 2014 (UTC)
  • Support - Quite simple, users with these requirements show knowledge in the policies and guidelines. ///EuroCar GT 00:32, 13 January 2014 (UTC)

Proposal 2

Reviewers at Articles for Creation will be selected after evaluation of 10 sample reviews performed (as detailed out at the relevant suggestion section from TheOriginalSoni above)

  • Kudpung There is no overload on the existing pool of reviewers, if you look at the proposal carefully. TheOriginalSoni ( talk) 02:31, 19 November 2013 (UTC)
Too complex and someone still needs to control it. Kudpung กุดผึ้ง ( talk) 05:53, 19 November 2013 (UTC)
My now-collapsed proposal is very similar to what OriginalSoni proposes, except fully automated (no burden on existing AfC folks at all)... but therefore dramatically more complex (adds burden to mabdul/Technical_13/Theopolisme/etc who are the AfC devs right now. See below, suggest we finish implementing the Kudpung approach, and then later open another RfC about the OriginalSoni approach, as complementary (not conflicting). This is not a zero-sum-game, we can actually have our cake an eat it too, in this rare case.  :-)   — 74.192.84.101 ( talk) 16:08, 9 December 2013 (UTC)
  • Oppose Too stringent and long and creates the opportunity for a backlog to form. It is also subjective, and not objective. Ramaksoud2000 ( Talk to me) 03:25, 19 November 2013 (UTC)
  • Oppose as I feel this is too stringent. I agree that it requires too much reviewer time UNLESS there is someone (like me) that doesn't spend a lot of time on reviews and focuses on AfC project management (like helper script development) that has the time to go through and review these users. See proposal 3 below (as much as I hate to make another proposal splitting up the votes...) Technical 13 ( talk) 15:56, 19 November 2013 (UTC)
  • Are you suggesting that we start a new proposal for a "reviewer reviewer" hat? Noooo..... — Anne Delong ( talk) 16:40, 19 November 2013 (UTC)
  • Defer proposal#2, for consideration as a future RfC. The point of OriginalSoni's proposal is to grade potential reviewers on the *merits* of their technical proficiency at reviewing. If they are good at it, they will get 9 out of 10 correct, on the quiz. This is not only different from, but orthogonal to Kudpung's proposal, which is primarily intended to prevent *abuse* of the AfC reviewer infrastructure, by folks that are not committed to the long-term goals of wikipedia. 500 edits and 90 days is a security-system, in other words. Getting 9 out of 10 correct is a competence-check. As Technical_13 points out below, it is theoretically possible to perform 6 spelling-corrections each day for three months, and thus "pass" the security-system, yet still be Not Very Good at correctly reviewing submissions.
  But my suggestion is that we should be careful to neither confuse nor conflate the two goals. Testing competence at correctly reviewing submissions should be *ongoing* and not just an "interview" which means there is a need for what OriginalSoni is proposing, that directly test competence in actual reviewing-work. At the same time, plenty of COI sockpuppets will be able to pass the 10-question-quiz with flying colors, so we also need some sort of morality-quiz that proves a minimal dedication to the five pillars. This necessarily will have to be a secondary criterion: 90+ days editing, and 500+ edits, seems like a reasonable proxy-for-commitment. HTH. 74.192.84.101 ( talk) 16:08, 9 December 2013 (UTC)
  • Monumental oppose for the reasons I have given in proposal 5. James500 ( talk) 13:57, 31 December 2013 (UTC)
  • Oppose . A good idea, but alas we don't have enough experienced reviewers doing AfC to devote to do the auditing. Alanl ( talk) 08:18, 12 January 2014 (UTC)

Proposal 3

To review pages at Articles for Creation, users should have made a minimum of 500 non-automated, non-minor edits to the English Wikipedia mainspace, with an account registered for at least 90 days with regular activity.

  • Support as proposer. Technical 13 ( talk) 15:56, 19 November 2013 (UTC)
  • Oppose - I think this is too restrictive. Spelling fixes may be marked as minor edits, but they're most definitely helping the project. What's "regular activity"? I took a Wikibreak in April this year - would that count against me? Ritchie333 (talk) (cont) 16:17, 19 November 2013 (UTC)
  • What's the point of a 90 day requirement if the user creates an account, makes a couple hundred punctuation fixes, goes away for 85 days, comes back and gets their edit count to 500 fixing spelling and what not. There are no significant edits and they have maybe 10-15 days of editing. I think we gain nothing by this, and this minor adjustment to P1 rectifies this. Technical 13 ( talk) 16:32, 19 November 2013 (UTC)
Do you think that's a likely scenario? Anyone can game the system if they want. You can run for RfA the minute you score 500 on Scottywong's tool - it doesn't mean you'll succeed! For those people, we can simply nudge them in the right direction, and topic ban them if necessary. Ritchie333 (talk) (cont) 16:43, 19 November 2013 (UTC)
When I first had 500 mainspace edits on the English Wikipedia, I would've had no place reviewing AfC submissions. I think it is a very likely scenario. If there are going to be count and time restrictions, let's make sure they actually do something other than look pretty. Technical 13 ( talk) 18:16, 19 November 2013 (UTC)
  • Comment (edit conflict) - I don't think that this proposal is significantly less lenient than Proposal 1, since the user chooses whether or not to mark edits as "minor". Please explain why you think that evenly spaced edits are better than bunched-up ones. I suppose that you are hoping to ensure that they are five hundred substantive edits (rather than, say, adding a piece of spam to 500 articles...) — Anne Delong ( talk) 16:26, 19 November 2013 (UTC)
  • Anne, I do believe you misunderstood what I wrote about minor edits. I did not mean necessarily edits marked as minor, I meant edits that qualify as minor in that only superficial differences exist between the current and previous versions. Examples include typographical corrections, formatting and presentational changes, and rearrangements of text without modification of its content. Whether or not the editor knows how to properly mark such edits may be out of scope (other than I would question a user with the first 500 sequential edits and having none marked as minor as really having any CLUE about policies and how to review articles). Technical 13 ( talk) 18:29, 19 November 2013 (UTC)
  • Oppose, after the above explanation. Not because I disagree with with anything you've said above, but I wouldn't be willing to do the work of measuring the value and complexity of hundreds of edits, so I can't !vote to put that work on someone else. — Anne Delong ( talk) 18:55, 19 November 2013 (UTC)
    • Administrators already do this at WP:RFPERM to hand out rights like reviewer and rollback. (Personally I don't think any rights should be necessary to review AfC nominations. If you wish to clamber through Wikipedia's crap pile to find the odd gem, have at it. Rather them than me.) — Tom Morris ( talk) 13:56, 27 December 2013 (UTC)
  • Oppose Anybody at all can create articles. Anybody. So why would you think someone would try to game the system as you said above and accept or deny a review if they can go ahead and create an article. Ramaksoud2000 ( Talk to me) 18:15, 30 December 2013 (UTC)
  • Monumental oppose for the reasons I have given in proposal 5. James500 ( talk) 13:57, 31 December 2013 (UTC)

Proposal 4: Piggy-back on rollback or PC reviewer

We already have two user rights we give out to people who have reached minimal competence with Wikipedia: pending changes reviewer and rollback. Because of the potential for hat collecting, it seems generally preferable to not duplicate entities beyond mere necessity. At a time when we have few enough people willing to delve through the ever-regrowing crap pile not only at WP:AFC but at a wide number of backlogs across the 'pedia. The main problem with AFC isn't bad reviewers, it's no reviewers. Adding another layer of gate-keeping on the front of an already backlogged process seems rather pointless. Instead, use the existing permissions structure: rollback, or pending changes reviewer. This isn't unheard of: when Article Feedback Tool v5 was still in operation on English Wikipedia, we reused the "reviewer" permission for reviewing AFT5 comments.

The advantage of this: administrators don't have to start handing out new permissions. The number of hats on offer is kept to an absolute minimum. We neatly sidestep the addition of more bureaucracy. — Tom Morris ( talk) 14:41, 27 December 2013 (UTC)

  • Support As proposer. — Tom Morris ( talk) 14:41, 27 December 2013 (UTC)
  • Oppose: This RfC does not discuss how this threshold will be granted and/or implemented. That will be the topic of a further discussion, when the threshold itself has been established. Kudpung กุดผึ้ง ( talk) 21:36, 27 December 2013 (UTC)
  • Kudpung, I do not think Tom made any statement towards that context. All he stated was to use a simple Reviewer or Rollbacker as the required permission threshold. (Correct me if I'm wrong on the reviewer-rollbacker part.) TheOriginalSoni ( talk) 22:21, 27 December 2013 (UTC)
  • Support This proposal neatly sidesteps any possible hat-collection issues we had, while still solving our basic competence requirements, like Proposal 1. It also makes it technically simple to implement any such requirements. TheOriginalSoni ( talk) 22:21, 27 December 2013 (UTC)
  • Question. What is being suggested here, exactly? That we dramatically reduce the count of viable candidates for AfC duty? Or that we dramatically increase the count of people with the R&R userRight?
explanation of my question
  Proposal#1 sets the low-but-not-too-low bar of 500+edits and 90+days, not to increase hat-count, but to keep out spammers that approve their sockpuppet's spam, and buddies who approved their friend's non-Notable garage-band. It is basically a minimum-morals qualification-criteria, indicating some level of commitment to wikipedia's goals. It is one step up from autoconfirmed. Now clearly, the current user-rights of reviewer && rollbacker *are* morally qualified. But currently, it is a *lot* more effort than 500 edits, and a lot more time invested than 90 days, before an editor is "whitelisted" by being given the R&R bits. Are we setting the bar too high, for being an AfC reviewer, if we demand only R&R-quality folks and above?
  How many of our existing hard-working AfC reviewers have the R&R bits, right now today? More pragmatically, I will point out that we already have plenty of folks with R&R bits... and any of them, or all of them, would be welcomed with open arms, if they showed up to help with the AfC queue tomorrow morning. And yet, there are still well over 1k articles in the main queue, and well over 10k in the G13 backlog. If we want those backlog-numbers to decrease, we would need to vastly expand the number of people who are given R&R bits. I think there are two possibilities for what proposal#4 means.
  Possibility#1, Tom_Morris is putting forth Proposal#4, and saying that only existing R&R bit-holders ought be allowed to become AfC reviewers... in which case, I oppose proposal four, on the grounds that there are simply not enough existing R&R bit-holders to solve the AfC backlog. 5992 reviewers and/or 4981 rollbackers, with significant overlap, plus 1423 admins that have those powers and more. Only 45% of admins are "active" aka ~15+edits/mo... conservative assumptions about overlap & activeness, means we might have 2700-to-3700 active R&R folks today, plus 600 active admins... aka roughly one R&R-or-admin for every 7 active editors. We also have 3000 very-active-editors making 100+edits/mo, [1] and an educated guess is that these 1-to-9-folks are the basically the *same* editors as the 1-to-7-folks that already have the R&R user-right.
  Possibility#2, Tom_Morris is suggesting that we dramatically increase the number of people who are given R&R bits... and in fact, might even be saying that every person with 500+edits and 90+days should automagically be given the pending-changes-reviewer bit, which could then also double as the AfC-submission-reviewer bit. Possibility#2 is something I could support... but as Kudpung says, that is an implementation question (we could also implement the 500-n-90 restriction purely as a jscript hack inside AFCH or as a custom server-side PHP kludge or as a pure social system using moral suasion or in various other ways). It's not clear that it will be easy to gain consensus for dramatically lowering the traditionally-pretty-dern-high level of experience that R&R bits have demanded in the past, to just 500-n-90. Therefore, if possibility#2 is the aim, in that case I would suggest deferring proposal#4 as an implementation-question, to the next phase of this RfC-sequence. 74.192.84.101 ( talk) 00:52, 30 December 2013 (UTC)
My point is that "500 edits + 90 days" (plus a quick manual check to make sure they aren't mad as a hatter) is about the rough guideline that admins use to hand out rollback or reviewer. I'm simply saying that we already have a process to determine whether or not new users are sensible enough to start reviewing (and indeed rolling back) other people's edits. — Tom Morris ( talk) 11:02, 30 December 2013 (UTC)
Remember that anybody can create articles with an account. Suggesting that you need rollback and reviewer is kind of too much. Ramaksoud2000 ( Talk to me) 18:10, 30 December 2013 (UTC)
  • Ramaksoud2000, this discussion is for who can review AFC submissions. I think a large number of our current AFC reviewers will have either of these priviledges, and almost all of the rest would be given the permission should they request it. TheOriginalSoni ( talk) 21:58, 30 December 2013 (UTC)
  • I'm saying what's the point of making the requirement so high when they can just create the article another way. Ramaksoud2000 ( Talk to me) 05:56, 31 December 2013 (UTC)
  • Ramaksoud2000, AFC Reviewers do not write the articles. The articles are written by newcomers, and reviewers "review" them, thus approving or declining the article. As I said, most current AFC reviewers alaready have this right. TheOriginalSoni ( talk) 10:54, 31 December 2013 (UTC)
  • In all fairness, there is no difference in principle between accepting an AFC submission and creating a new page from scratch. James500 ( talk) 12:29, 31 December 2013 (UTC)
  • Monumental oppose for the reasons I have given in proposal 5. James500 ( talk) 13:57, 31 December 2013 (UTC)

Proposal 5: Maintain consistency with rights to create articles from scratch

Any registered user can accept an AFC submission. Only users with either the reviewer or rollbacker user right can decline an AFC submission.

  • Support as proposer. It would be absurd to prohibit users who can create new pages in the mainspace from accepting an AFC submission. It would not be consistent with existing user rights at all. James500 ( talk) 11:37, 31 December 2013 (UTC) In fact you could argue that, in order to be completely consistent, only admins should have the right to reject an AFC submission, because they are the only ones who, at present, have the authority to remove an article from the mainspace by deletion or otherwise. James500 ( talk) 12:10, 31 December 2013 (UTC)
  • Oppose as that is entirely inaccurate. Any autoconfirmed user can move a page from mainspace to a subpage of a user's space or to Draft: effectively removing from mainspace. Allowing any user to accept, is also counter productive as AfC is intended to help new users create an article with out it getting speedily deleted half a dozen times for simple issues like promotional tone or lack of indication of importance, allowing all users unable to see these things or whom are unfamiliar with the policies/essays/guidelines that can give constructive feedback is a bad idea. Technical 13 ( talk) 12:48, 31 December 2013 (UTC)
I disagee. What WP:USERFY actually says is "Except for self-userfying and obvious non articles such as accidentally-created user pages in the main namespace, it is generally inappropriate to userfy an article without a deletion process". The recommended process is AfD. So, assuming the essay you have linked to is accurate, a non-admin cannot userfy an attempt at a proper article that someone else has created. James500 ( talk) 13:08, 31 December 2013 (UTC) And the other limb of your argument is absurd. James500 ( talk) 13:17, 31 December 2013 (UTC) And "promotional tone" is not a criteria for speedy deletion. What is required is blatant advertising. James500 ( talk) 13:27, 31 December 2013 (UTC)
  • Oppose - Any confirmed user can move an article out of Afc and into mainspace to create an article (at risk of being reverted, or course). The above proposals 1-4 won't prevent that. They are only about limiting the use of the Afc reviewing tools and Afc review templates which give the appearance that the person placing them is an experienced and knowledgeable editor, and not someone who joined Wikipedia last week. There are exceptions, of course; a use with a new account could have been editing under another name, or as an IP, for years, but as usual the application of the criteria will be tempered by common sense. — Anne Delong ( talk) 14:32, 31 December 2013 (UTC)
As far as I am aware, a page move from AFC to the mainspace cannot be reverted without a deletion process (such as AfD), except in very limited circumstances. James500 ( talk) 15:11, 31 December 2013 (UTC) If the proposals above are only about access to scripts and templates, their wording needs to be made much clearer. I can't actually find a project page that defines the meaning of "review" and "reviewer" in this context. It sounds like "move into the mainspace". It is clear to me from the foregoing discussion that I am not the only one who thinks this. James500 ( talk) 15:59, 31 December 2013 (UTC)
I hope some others will weigh in about the meaning or "reviewer". And yes, you are right; I shouldn't have said "revert". The more likely (and more serious) results of an inexperienced editor moving a draft prematurely to mainspace would be: (1) speedy deletion under a number of categories from which the draft submissions are protected so that the problems can be fixed, and (2) being dragged to Afd. In either case the poor draft creator, usually a beginning user, could be very bewildered and have an unnecessarily negative experience, all so that some other new user can have the freedom of creating an article out of someone else's draft without having to take the time to learn any of Wikipedia's policies. — Anne Delong ( talk) 19:16, 31 December 2013 (UTC)
Prohibiting "inexperienced" users from moving drafts into the mainspace might help deletionists in their mission to prevent the creation of perfectly valid stubs. James500 ( talk) 20:35, 31 December 2013 (UTC)
  • Oppose as already detailed by Anne and Technical13. The need for this RFC is to make sure AFC performs better in making sure it's articles survive Mainspace, not the other way round. The current proposal is detrimental to the AFC process, and will work against getting better articles out of here. TheOriginalSoni ( talk) 21:26, 31 December 2013 (UTC)
I disagree. It is clear to me that AFC reviewers are rejecting submissions that would survive (and have survived) an AfD. In any event, if you are worried about articles on valid topics surviving in the mainspace, what you need to look at are the deletion processes, because that is where the problem will be. James500 ( talk) 07:34, 1 January 2014 (UTC)
  • Oppose. I seriously doubt any AfD proposal will survive, and there been many attempts over the years. There are enough orphaned stubs out there in mainspace, and as a mature project, the whole point of AfC is to improve the quality of new articles. If you allow this, then you might as well disband AfC altogether. Alanl ( talk) 08:26, 12 January 2014 (UTC)

Proposal 6: Complete consistency with other deletion processes

Any registered user can move an AFC submission into the mainspace, whereupon it will be treated like any other article. Only users with either the reviewer or rollbacker user right can use AFC scripts and templates. Subject to the following exception, only users with the admin user right can decline an AFC submission. The exception is AFC submissions that are clearly not intended to be articles (ie those that , if created in the mainspace, could be legitimately userfied by a non-admin). Non-admins can nominate an AFC submission for rejection, using a template created for this purpose.

  • Support as proposer. This is probably my first choice on grounds that rejecting an AFC submission is equivalent to deleting an article from the mainspace. James500 ( talk) 07:34, 1 January 2014 (UTC)
  • Strong Oppose This isn't even consistent with deletion processes as your title claims. Ramaksoud2000 ( Talk to me) 05:20, 7 January 2014 (UTC)
This is proposal is exactly consistent with deletion processes. In what way is it not consistent? James500 ( talk) 08:47, 12 January 2014 (UTC)
  • Absolutely Oppose the proposers completely erroneous claim that "rejecting an AFC submission is equivalent to deleting an article from the mainspace" only shows that the proposer has no clue at all about how AFC actually works. An AFC rejection is simply: "this draft isn't ready yet because of this problem, here is a guideline on how to fix it. When you've fixed it please resubmit it. If you need further assistance you can get it here". Roger (Dodger67) ( talk) 08:29, 12 January 2014 (UTC)
My claim that "rejecting an AFC submission is equivalent to deleting an article from the mainspace" is based on similar reasoning in WP:USERFY, and I don't believe that there is any difference in principle. Bear in mind that rejection also facilitates CSD G13, so we don't want it done in error. G13 does not, in express words, require the admin to vouch for the correctness of the rejection. It seems to me that he could just rubber stamp it. So, if you allow reviewers and rollbackers to reject submissions you are potentially giving a user with 500 edits the power in effect to speedy delete large numbers of articles at his discretion with no questions asked. James500 ( talk) 08:38, 12 January 2014 (UTC)

Proposal 7

Amend CSD G13 so that it authorizes the speedy deletion of a rejected AFC submission only if that submission was correctly rejected.

  • Support as proposer. This would remove what is, in my view, a potentially serious problem with allowing non-admins to reject AFC submissions. See my comments under proposal 6. James500 ( talk) 04:03, 13 January 2014 (UTC)


Pages recently put under extended-confirmed protection

Report
Pages recently put under extended confirmed protection (24 out of 8013 total) ( Purge)
Page Protected Expiry Type Summary Admin
Template:Dune franchise 2024-07-15 01:57 2024-10-15 01:57 edit Persistent sock puppetry NinjaRobotPirate
That's Entertainment (Hazbin Hotel) 2024-07-15 01:43 2024-10-15 01:43 edit Persistent sock puppetry NinjaRobotPirate
July 2024 al-Shati refugee camp attack 2024-07-15 00:00 indefinite edit,move Arbitration enforcement, see Wikipedia:Contentious topics/Arab–Israeli conflict Bradv
Ruth Westheimer 2024-07-14 21:35 2024-08-14 21:35 edit,move Contentious topic restriction: WP:A/I/PIA ToBeFree
Template:Fa top 2024-07-14 18:00 indefinite edit,move High-risk template or module: 2501 transclusions ( more info) MusikBot II
Zionism 2024-07-14 16:31 indefinite edit,move Arbitration enforcement: Removing full protection per progress on talk page Bradv
Thomas Matthew Crooks 2024-07-14 16:00 indefinite edit Disruption magnet; requested at WP:RFPP; WP:ARBAP2 Abecedare
Template:Current event 2024-07-14 07:39 indefinite edit,move High risk template Zzuuzz
File:Shooting of Donald Trump.webp 2024-07-14 02:07 indefinite edit,move,upload Irrespective of whether this gets kept or deleted at Wikipedia:Files for discussion/2024 July 14, it is a risk to have it unprotected on such a high visibility article. Protecting in line with the main article. Daniel
2024 shooting at a Donald Trump rally 2024-07-14 00:01 2025-01-13 23:20 edit Immediate risk of move warring Fences and windows
2024 assassination attempt of Donald Trump 2024-07-13 22:56 2025-01-13 23:20 edit Persistent vandalism ScottishFinnishRadish
Death Shelters 2024-07-13 22:55 indefinite edit,move Contentious topics enforcement for WP:CT/A-I; requested at WP:RfPP Daniel Quinlan
2024 targeted assassination of Muhammad Deif 2024-07-13 19:54 indefinite edit,move Contentious topics enforcement for WP:CT/A-I; requested at WP:RfPP Daniel Quinlan
13 July 2024 Al-Mawasi airstrikes 2024-07-13 19:47 indefinite edit,move Contentious topics enforcement for WP:CT/A-I; requested at WP:RfPP Daniel Quinlan
Aaron Maté 2024-07-13 18:09 2025-07-13 18:09 edit,move Contentious topics enforcement for WP:CT/BLP; requested at WP:RfPP Daniel Quinlan
Hruso people 2024-07-12 21:05 indefinite edit,move Persistent disruptive editing: per RFPP; will log at WP:GS/CASTE Daniel Case
Koli Samaj 2024-07-12 14:06 indefinite edit Persistent sock puppetry by warring sock-farms including Wikipedia:Sockpuppet investigations/Thakor Sumant Sinhji Jhala Abecedare
Levantine Arabic 2024-07-12 12:30 indefinite edit,move Contentious topic restriction: Arab–Israeli conflict K6ka
Antioch International Movement of Churches 2024-07-12 02:37 2025-01-12 02:37 edit Persistent sock puppetry The Wordsmith
Mohsin Hossain Bablu 2024-07-12 00:47 indefinite create Repeatedly recreated BusterD
Adult Swim (Latin American TV channel) 2024-07-11 20:54 2024-08-11 12:00 edit,move persistent disruptive editing & block-evasion JBW
Draft:Suck my dick 2024-07-11 16:31 indefinite create Offensive name BusterD
Draft:Ari 2024-07-11 16:24 indefinite create Repeatedly recreated BusterD
Draft:Saeed Khan Bozdar 2024-07-11 12:19 indefinite create Repeatedly recreated Amortias

ARBPIA gaming?

The user Amayorov, despite having an eight-year-old account, made their first edit on 3 July 2024 before proceeding to pass 500 edits and receive extended confirmed permissions on 6 July 2024. All of the edits made, 100s a day, were on European politics and history. Shortly after achieving EC permissions, suddenly it's all 1948 Palestine war, specifically inserting Benny Morris as a source all over the place and doing some work on the Benny Morris biography. Apparently European content has lost its appeal. Make of this what you will. I also have to wonder if, despite having an extant account for 8 years, achieving 500 edits in three days (rather than the 30 days as envisaged in the ECR rule set) is somewhat of a violation of the spirit of the restrictions, even if not the technical function. Iskandar323 ( talk) 19:08, 7 July 2024 (UTC)

Were there any issues with the edits?
Discussions recently have come to the conclusion that absent obvious abuse - unproductive or disruptive edits, or repeatedly making a dozen edits to do what could be done in one or two - it’s acceptable for editors to work towards ECP.
To an extent, this makes sense - if we tell people "this is what you need to edit this topic area" we can’t reasonably expect editors interested in the topic area to not work towards it. BilledMammal ( talk) 19:16, 7 July 2024 (UTC)
see my reply Amayorov ( talk) 19:19, 7 July 2024 (UTC)
Issues other than that pushing Benny Morris here there any everywhere with little regard for any other sources is a terrible form of disregard for NPOV? That alone, in a contentious topic area, is pretty disruptive. The 500/30 rule is aimed at ensuring a minimum level of understanding and competency. Yes, some are encouraged to rush the requirements, but we shouldn't encourage editors to rush the requirements. Iskandar323 ( talk) 19:20, 7 July 2024 (UTC)
I did not "push Benny Morris" but rather expanded on the already existing citations to his work. Recall that Benny Morris' 2008 book had already been the most quoted reference on that page. When necessary, I've added phrases such as "some scholars allege that" etc.
When you and other users disagreed with my edits, I didn't proceed, but rather created sections on the Talk page. Unlike other users, you didn't engage.
I think the extensive sourcing I use in any of my edits illustrate that I at least possess "a minimum level of competency". Amayorov ( talk) 19:26, 7 July 2024 (UTC)
I have engaged. As of the time of me writing this, there are at least two comments from me to you that you have not responded to. Again, this can be checked. I suggest you desist from misrepresenting very verifiable information in this forum. Iskandar323 ( talk) 19:39, 7 July 2024 (UTC)
You wrote those comments less than an hour before reporting me on the Admin board. Yes –– all of this can be checked.
I suggest you desist from misrepresenting very verifiable information in this forum. Amayorov ( talk) 19:51, 7 July 2024 (UTC)
I meant in regardless to the substance of this complaint - with the edits to reach 500.
If we don’t tell editors that they can’t work towards 500/30, then how should they know we don’t want them to work towards them? If the goal is to ensure a minimum level of understanding and competency, and 500 edits isn’t sufficient for that, then let’s modify the requirements - for example, require edits to be a minimum byte size to count, as I have proposed in the past. BilledMammal ( talk) 19:28, 7 July 2024 (UTC)
I think that would be a good idea. However, I have clearly written plenty of bytes in my 500 edits, in some cases going as far as copy-editing entire pages that had been poorly translated or unsourced. You can see all that in my edit history. Amayorov ( talk) 19:30, 7 July 2024 (UTC)
This is patently false. I have made extensive edits to various topics, including military history and Central Asian history, paganism, and engineering. All my corrections were extensively referenced. I have also rewritten several large articles, requiring copy-edit and verification.
It is true that I have re-activated my account in the week. This is simply a reflection of the fact that I have free time, and have grown fond of Wikipedia.
Benny Morris' 1948 book has always been the most referenced book on the topic. I have used not only that book but also others by different authors, as well as sourcing UN archives.
I have added corrections and more references on the subject, including 1948 Palestinian expulsion and flight and Palestinian nationalism. None of the other users had an issue with my work.
By contrast, @ Iskandar323 has reverted my edits without giving a justification. They also ignored my attempts at a discussion in the Talk pages. Amayorov ( talk) 19:19, 7 July 2024 (UTC)
I had a justification, and I have responded on talk. I suggest that you avoid misrepresenting things that can be checked up on (on an administrative noticeboard). And yes, other users have taken up issue with your edits. I'm not sure why you would misrepresent this. Iskandar323 ( talk) 19:24, 7 July 2024 (UTC)
Your justification was RV gf edits - unfortunately, adding random titbits of background information from Morris, removing dates and badly rephrasing other parts is not an improvement.
This is not specific or constructive. In order to clarify your objections, I created discussion topics on the Talk page – which you have ignored. Amayorov ( talk) 19:27, 7 July 2024 (UTC)
I have responded to some, not all of your posts. However, I would prefer to see what administrators think of this situation before potentially unduly spending more time on explaining why expanding claims from a single source that is, in your own words, already the most [(over-)]quoted reference on the page, is not particularly in the service of NPOV. Iskandar323 ( talk) 19:35, 7 July 2024 (UTC)
You have responded to them half an hour ago, almost immediately posting on the Admin board.
Yes, Benny Morris is the most quoted historian on the 1948 war. I barely added new references to him, usually simply extending the existing ones. Amayorov ( talk) 19:37, 7 July 2024 (UTC)
I suppose I should be grateful that you've helped illustrate quite how over-represented Benny Morris is (more than 50 citations and mentions), but again, that begs the question of why you think this clear imbalance problem should be worsened. If you can't see that there might be an imbalance problem there, that somewhat illustrates why the 500/30 rule exists and why a month of actual editing is, in spirit, what is expected of it. Iskandar323 ( talk) 19:47, 7 July 2024 (UTC)
Because Morris has written multiple, highly regarded books on the 1948 war. He's cited by plenty of other authors, such as Shlaim, Khalidi, Ben-Ami, and others.
Besides, and as I've previously explained, I didn't add much new material. I've clarified previous references and added qualifications to partisan statements. Amayorov ( talk) 19:53, 7 July 2024 (UTC)
This seems like a content dispute, Iskandar323, moreso than any actual gaming. It seems like it might be better to have discussed this with the editor on a talk page, not hauled them to AN. The editor's contributions appear to be in good faith, and while I haven't gone into a full deep-dive or anything of the sort, they don't seem to be unconstructive at first glance. Favoring a specific historian isn't necessarily a behavioral issue, so long as they are willing to discuss inclusion and abide by the results of consensus. Building a culture of continually questioning those who take the time to build a constructive editing history in order to prove they can be trusted with access to contentious topics is a terrifying idea. If I was to accuse someone of gaming for rollback, for example, because they spent a lot of time reverting vandals, it would likely be considered at the very least rude, and at worst a personal attack. EggRoll97 ( talk) 21:18, 7 July 2024 (UTC)
There is a content dispute for sure, which I will continue in good faith. At the same time, there is only one type of account that I have ever seen that goes from 0 to 100 edits a day on some random topic before switching (after 3 frenetic days) to almost pure ARBPIA edits, and it isn't the constructive variety. There are plenty of dubious accounts that have just passed this threshold currently operating in the contentious topic area. This account, however, caught my eye due to the rapid edit aggregation and glaring topic switch. I have raised the issue of quite a few gaming accounts on this noticeboard, and to date, most of them have raised eyebrows for admins too. Iskandar323 ( talk) 21:39, 7 July 2024 (UTC)

FWIW, from my perspective there appears to be some unnecessary edit farming in this user's background. For instance, Sukhoi Shkval did not require 40 edits in a row to achieve this relatively minimal difference, while not managing to add a single in-line citation or new source. On 9К512 Uragan-1M we got some extremely minor, non-substantive copyediting that frankly didn't change the readability of the article much. An improvement? Perhaps trivially, but reasonable editors could disagree there. Worth sanctioning over? IMO probably not, but I don't think Iskandar323's concerns are without merit. SWATJester Shoot Blues, Tell VileRat! 22:44, 7 July 2024 (UTC)

Regarding 9K512 Uragan-1M, the article had been marked as “roughly translated.” I did my best to correct residual grammatical errors, before marking the issue as resolved.

Regarding Sukhoi-Shkval, I agree that 40 edits were excessive. One reason for this was that I was still learning about the editing tools, discovering new templates and features. Another justification is that I had to decipher some unclear text, such as “Each wing has a rudder that functions as a rudder and aileron.” Here, the first “rudder” is in fact not a rudder at all, but a flap. I had only figured that out once I read through the sources. Amayorov ( talk) 18:03, 8 July 2024 (UTC)
It wouldn't require 40 edits from an experienced editor who knew everything about how wikitext worked, but for somebody figuring it out for the first time I am inclined to assume good faith. jp× g 🗯️ 20:36, 9 July 2024 (UTC)
There may be something going on with ARBPIA, perhaps unrelated to this, but worth thinking about. We had a recently compromised account jump into ARBPIA in the past week, threatening to report other editors if reverted, then reporting a prominent ‘opponent’ to WP:AE, volunteering to be topic banned if the ‘opponent’ is also topic banned, before being Checkuser blocked by an Arb. starship .paint ( RUN) 23:24, 7 July 2024 (UTC)

I was going to report this user as well. Account created in 2016 but first edit made a few days ago and quickly put in 500 edits, immediately jumps into Israeli-Palestinian conflict topic area, seemingly POV-pushing. Seems to be an experienced user as well. I agree with @ Starship.paint that there seems to be something going on with ARBPIA, specifically a surge in sock accounts. IOHANNVSVERVS ( talk) 05:25, 8 July 2024 (UTC)

I don't know whether these plots can provide any illumination. The dramatic change in slope and shape of the bytes added and page byte size change curves after extendedconfirmed has been granted at 500 edits is consistent with the notion of gaming to obtain the privilege in order to enter the contentious PIA topic area. These kind of signal shapes for users that enter the PIA topic area can often be seen for sockpuppets of AndresHerutJaim/יניב הורון, not that that suggests this is an AHJ sock. Wikipedia provides tools to help new users rapidly gain EC. Sometimes this kind of impressive efficiency is thanks to the Wikimedia Foundation Growth team's "Newcomer tasks" project. Also, their first edit being an WP:ARBECR violation is not great. Sean.hoyland ( talk) 09:42, 8 July 2024 (UTC)

When I was doing my edits, I was using almost exclusively Wiki’s backlog. I chose the issues that I could conceivably help with, such as Rough Translation from Russian and French (the languages I speak), and lead rewrite requests. I intend to continue on with this work in the future.
And, yes, I’m interested in the IP history, about which I’ve read a lot. Since gaining extended privileges, I’ve made improvements to those articles. Those edits have arguably been better-sources than any of my other work, due to my having more knowledge to my having more knowledge on the topic. I do not deny that I wanted to contribute to these topics from the start. Amayorov ( talk) 10:47, 8 July 2024 (UTC)
Thanks for the info Amayorov but you don't need to defend yourself to me. I'm nobody. I'm just providing information. Either way, the notion of gaming in Wikipedia and its relationship to the WP:ARBECR barrier is currently rather vague. Sean.hoyland ( talk) 11:12, 8 July 2024 (UTC)
Where did you learn to add a colon prefix to the category name in your busy schedule by the way e.g. :Category:Wikipedia backlog|Wiki’s backlog? Sean.hoyland ( talk) 05:02, 9 July 2024 (UTC)
The visual editor adds it automatically, when I link to the url /info/en/?search=Category:Wikipedia_backlog Amayorov ( talk) 13:45, 9 July 2024 (UTC)

Either way, regardless of the specifics of this editor, it's important for the community to acknowledge that a) WP:ARBECR was introduced as an entry barrier for good reasons and b) highly motivated people have already discovered ways to essentially tunnel through that barrier. Sean.hoyland ( talk) 10:17, 8 July 2024 (UTC)

Not being a tech wizard, I can only judge by what I see over time. I am in the habit of adding awareness notices if I notice new editors (non EC or EC) making edits in the topic area and off the top of my head, I would say that occurs 3 or 4 times a month at least, there appears to be an increase in the number of such editors in recent times, as to what proportion of them are WP:NOTHERE I couldn't say but experience tells me that some at least are in that category. Selfstudier ( talk) 10:57, 8 July 2024 (UTC)
I think you are underestimating your contribution. This year I think you have provided the awareness notices to 202 users, or thereabouts. That is based on your revisions to user talk pages where the byte size change is in a range consistent with the awareness template size. Sean.hoyland ( talk) 16:08, 8 July 2024 (UTC)
The top of my head is very unreliable then, lol. Selfstudier ( talk) 16:13, 8 July 2024 (UTC)
@ Sean.hoyland: There is an easier way to check; see this log search. Selfstudier has posted 210 this year. BilledMammal ( talk) 21:41, 9 July 2024 (UTC)
Ah, that's useful to know. Thanks. I've not really spent any time looking at the filters, despite them being a likely information goldmine. On the other hand, the pointlessly harder path is often more fun. Sean.hoyland ( talk) 04:08, 10 July 2024 (UTC)

No comment about the gaming accusation, but the ARBPIA edits themselves seem fine. Morris is arguably the most prominent historian in this area, and one of the more neutral ones, with critics from both sides. It's debatable whether some of the added content is important enough to include, but it's reasonable enough, and Amayorov seems open to feedback and compromise. POV pushing involves aggression, which I don't see here. If we were to expect some kind of strict symmetry in editing behavior, the vast majority of us ARBPIA editors would fail that standard. — xDanielx T/ C\ R 18:19, 8 July 2024 (UTC)

I think it's quite natural that hot topics attract new editors trying to fix (perceived) gaps or biases. I myself got to 500 edits within two months after getting involved in another contentious area. At the end of the day the question should be whether an editor understands and follows the rules. Alaexis ¿question? 21:28, 11 July 2024 (UTC)
I would say, at the start of the day the test should be - is an editor violating the rules merely by being here evading a block or ban. Unfortunately, it's not possible to tell whether an editor understands and follows the rules, all of the rules, not just a subset, by looking at the content they generate and the image they present. If an editor violates the rule against sockpuppetry by employing deception, a very common occurrence in the PIA topic area, it's reasonable to assume they will likely violate other rules while generating content or interacting with editors at some point. Sean.hoyland ( talk) 02:50, 12 July 2024 (UTC)
  • Amayorov can you explain why your account was created on July 8, 2016, but your very first edit [13] is on July 3, 2024? To me that's a red flag. A proposed remedy is that Amayorov's 30 days start from July 3, 2024. VR (Please ping on reply) 19:59, 12 July 2024 (UTC)
    I explained it here. In 2016, I created an account for a university practical that required me to create a web page about a chemical compound on Wikidata. In my case, it was a terpenoid, Q44009079‬. I don't know why the page doesn't exist anymore, but I found emails from 2018, notifying that other pages have been linked to it (see screenshots).
    A couple weeks ago, I started to be interested in trying out Wikipedia editing. I'm currently waiting to start a new job, and have plenty of time. Amayorov ( talk) 20:23, 12 July 2024 (UTC)
    Actually, I've been able to retrace this a bit more, and what I said wasn't entirely accurate. In 2017, I created a new account, @ Alexmayorov, specifically for that practical. I used it to create Q44009079. Both Amayorov and Alexmayorov are registered on the same email address. Regarding @ Amayorov, created in 2016, I can't recall why I made it.
    In April 2023, I decided to restore access to my account. I couldn't recall my username, and requested a password reset using my email. That reset came back with Amayorov as the user. Amayorov ( talk) 20:41, 12 July 2024 (UTC)
    Hello, this is my second account, which I've only just realised I had! Alexmayorov ( talk) 20:43, 12 July 2024 (UTC)
    I'm confused. It says "20:42, July 12, 2024 User account Alexmayorov talk contribs was created automatically", as opposed to 2017. VR (Please ping on reply) 23:18, 12 July 2024 (UTC)
    https://m.wikidata.org/wiki/Special:Contributions/Alexmayorov IOHANNVSVERVS ( talk) 23:25, 12 July 2024 (UTC)
    Because it was a wikidata only account. So the en.wiki one poofed into existence when they logged in here. Iskandar323 ( talk) 05:31, 13 July 2024 (UTC)
    @ Vice regent 🏓 Amayorov ( talk) 11:57, 13 July 2024 (UTC)
    Got it, thanks! VR (Please ping on reply) 18:04, 13 July 2024 (UTC)
    @ Vice regent Ping as requested Amayorov ( talk) 22:05, 12 July 2024 (UTC)

Conflict of interest VRT consultations, July 2024

The Arbitration Committee has received applications for conflict of interest VRT queue access and has reviewed them in consultation with the functionaries team. The Community is invited to evaluate the candidacies and comment here until the end of 17 July 2024 (UTC).

On behalf of the Committee, Sdrqaz ( talk) 00:01, 8 July 2024 (UTC)

Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard § Conflict of interest VRT consultations, July 2024

Multiple reverts

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


A user has reverted my edits two times each in First Dutch Military Aggression and Second Dutch Military Aggression. Can someone please prevent him from reverting it. I'm trying to avoid violating WP:3RR. Desertasad ( talk) 01:25, 8 July 2024 (UTC)

I've blocked the OP for 72 hours for their homophobic comments they posted at NFSreloaded's Talk page, whom they failed to notify of this complaint. Any administrator is free to block Desertasad for longer.-- Bbb23 ( talk) 01:42, 8 July 2024 (UTC)
I can tell you that if I were an admin, I'd indef. Saying that the legalisation of LGBTQIA+ is a bad thing is extremely disruptive. I've seen users indeffed for less. LilianaUwU ( talk / contributions) 01:47, 8 July 2024 (UTC)
I agree and have made it an indef. –  Joe ( talk) 10:29, 9 July 2024 (UTC)

Appreciate the tag. In response to this complaint: the manual reverts in question are here and there on Operation Product, and here and there on Operation Kraai. On the former article OP duplicated information already present in the lead section, on the latter article they moved the informal non-English terms for the military operation up to the first sentence. I considered both contributions redundant and undid them, ultimately resulting in the exchange on my talk page. That said, I don't feel I was pushing any kind of nationalist narrative in this situation or elsewhere. -- NFSreloaded ( talk) 02:24, 8 July 2024 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

https://zh.wikipedia.org/zh-hant/蔡瑞月

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Hi Administrators,

Someone upload a wrong portrait of Madam Tsai Jui-yueh on the Traditional Chinese Wikipedia page. https://zh.wikipedia.org/zh-hant/蔡瑞月

Someone uploaded using the reference below, Madam was tagged in that News article photo album, but photo is someone else in a group photo https://ahonline.drnh.gov.tw/index.php?act=Display/image/4359360wg9foOB#d6C


The same news article and album you can see Madam Tsai Jui-yueh is in this photo https://ahonline.drnh.gov.tw/index.php?act=Display/image/4359360wg9foOB#0Osa

Can someone please check the reference and correct this page.

該封禁的查封ID是#560409。--Tjyfoundation(留言) 2024年7月8日 (一) 11:27 (UTC) Tjyfoundation ( talk) 12:05, 8 July 2024 (UTC)

zh.wikipedia.org is a different project. There's nothing that en.wikipedia.org can do for you, you need to raise your concern on that project. -- Yamla ( talk) 12:07, 8 July 2024 (UTC)
How to raise my concern on that project? Tjyfoundation ( talk) 12:24, 8 July 2024 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


RfC closure review request at Wikipedia:Reliable sources/Noticeboard#RFC: The Telegraph on trans issues

WP:RSN ( talk| | history| logs| links| cache| watch) ( RfC closure in question) ( Discussion with closer)
Page now archived at /info/en/?search=Wikipedia:Reliable_sources/Noticeboard/Archive_444#RFC%3A_The_Telegraph_on_trans_issues

Closer: S Marshall ( talk · contribs · deleted contribs · logs · filter log · block user · block log)

Notified: User talk:S Marshall#Closure review

Background: There are two separate objections. One to the close as a whole, and the other to the third paragraph. We present both here, and ask editors to say whether they support overturning the whole close, only the third paragraph, or none.

Reasoning - Third paragraph: Overall, I am satisfied with this closure. However, the closer claims that the Telgraph has an unashamed embrace of the widely-debunked Litter boxes in schools hoax, which is really misleading. That part of the debate centered over the Telegraph's unretracted claim that a student identified as a cat at a certain school (evinced by a viral argument in which a student brings up the "cat student" part as a rhetorical device), which is to be way less than what "embracing the litter boxes in schools hoax" implies; the Telegraph didn't even give that fact much weight anyways.
Now, someone has quoted this part of the closing summary on the Telegraph's WP:RSP entry, thus enabling this misleading part to inflict a lot more damage on those wishing to use RSP for a quick summary of existing consensus. If nothing else, I'd like at least this part to be amended.

As seen on the closer's talk page, at least 3 others are a lot more unsatisfied, believing that the closer falsely made claims of other misrepresentations being brought up and evinced. See BilledMammal's comment for details of this argument. Meanwhile, commenters here may want to consider the magnitude of !voters for deprecation who weren't convinced by the lack of factual misrepresentation. In the end, however, I personally am only concerned with removing or amending the misleading language I mention in the first paragraph. Aaron Liu ( talk) 04:19, 9 July 2024 (UTC)

Note that by "first paragraph", I meant the problematic language that I bring up in the first paragraph of my statement, not the first paragraph of the actual close. Aaron Liu ( talk) 12:43, 9 July 2024 (UTC)

Reasoning - Close as a whole: There are two issues with this closure; the closer has substantially misread the discussion, and the closer is WP:INVOLVED.

The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax is discussed at great length. The disputed article, here, is exhaustively dissected by the community, and, on the basis of scholarly sources and an Ofsted report, various misrepresentations contained in that article are noted. It's questioned whether these are really "misrepresentations" or confusions between fact and opinion. Towards the end of this, the "generally reliable" camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes, which I receive as a concession that the article is misleading. And if the Telegraph has published a correction, then the "generally reliable" camp hasn't unearthed it.

This quoted paragraph, which is the only part of the close which focuses on the arguments made, is rife with inaccuracies. They say that various misrepresentations contained in that article are noted, but as far as I can tell only two misrepresentations were alleged; that the Telegraph endorsed the litter boxes in schools hoax, and that the Telegraph falsely claimed that a student identified as a cat.

The closer says that these allegations are proven on the basis of scholarly sources and an Ofsted report, but this in incorrect. As far as I can tell no scholarly papers were presented in relation to these allegations, and while the Ofsted report was presented, it was presented by those arguing "generally reliable", who pointed out that it took no position on whether a student actually identified as a cat.

They also interpret the consensus of the discussion on this as that the Telegraph has unashamed[ly] embrace[d] the widely-debunked Litter boxes in schools hoax. This is not a reasonable reading of discussion; editors rejected that claim on the basis that the Telegraph explicitly called claims of litter boxes in schools a hoax, and this counter-argument was endorsed by the majority of editors who commented on the claim.

Finally, they say towards the end of this, the "generally reliable" camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes. While a few editors on both the "generally reliable" and "generally unreliable" side said that reliable sources are allowed to make occasional mistakes, it doesn't appear that this statement was especially common among the "generally reliable" camp, and to interpret this statement as meaning that those editors are recognizing that this specific example is a mistake is to read something into these !votes that is not there.

Given the number of factual errors made in the closer's summary of the discussion it is clear that it needs to be overturned and reclosed. This is particularly true because the closer is WP:INVOLVED, having argued in a previous discussion at RSN about the Telegraph in relation to politics that, while they considered it reliable for that sub-topic, it employs people with ghastly and abhorrent opinions. BilledMammal ( talk) 05:55, 9 July 2024 (UTC)

Closer

This is a no-consensus close, and there are two possible approaches to no-consensus. The first is the one usual at WP:AFD, where no consensus means no change. AFD puts the burden to achieve consensus on the pro-change side. User:Seraphimblade, below, clearly sees the discussion as being in this category.

The second is the one usual with content decisions, at WP:ONUS. ONUS puts the burden to achieve consensus on the anti-change side, and authorizes the removal of disputed material.

In closing this, I decided that the community doesn't have widespread confidence in the Daily Telegraph's coverage of trans issues, and therefore it shouldn't be listed as generally reliable. In other words, I decided to treat this as more like a content decision governed by WP:ONUS than a procedural one governed by AFD consensus. In doing this, I removed the first mover advantage that the "generally reliable" side expected and I think relied on. At issue here is the question: was I right to do that? If you think I was, you belong in the "endorse" column, and if you think I wasn't, then you belong at "overturn".

It's very arguable, and I won't object if the community overturns me here on that point. But I do think I'm right. My position is that we shouldn't be listing sources as generally reliable when the community has real doubts.

The claim that I was INVOLVED is much less arguable. INVOLVED means you can't close a discussion you've voted in, and it means you can't close a discussion about an article you've made non-trivial edits to. And that's all it says. If you stretch INVOLVED to allow claims that you're INVOLVED because you participated in a tangentially-related RFC on RSN the thick end of a year ago on the other side of the debate from your closure, then you've pulled it a long way out of its original shape, haven't you?

We as a community need to clarify what's INVOLVED and what isn't, because I've noticed that pretty much every time you make a disputed closure someone mentions it.— S Marshall  T/ C 07:25, 9 July 2024 (UTC)

I think you misread INVOLVED. It’s not about single discussions, but disputes as a whole - and you’ve been involved in disputes in relation to the reliability of The Telegraph, and given the part of your comment I quoted you clearly also have strong feelings on the subject. BilledMammal ( talk) 07:35, 9 July 2024 (UTC)
No, I don't have strong feelings about the Daily Telegraph. It employs people with ghastly and abhorrent opinions, and I certainly do have my views and opinions about some of those people, but that's not what's at issue here and the Daily Telegraph as a whole isn't a subject I care about.— S Marshall  T/ C 07:41, 9 July 2024 (UTC)
That's not what ONUS says - it doesn't put the burden on "the anti-change side". It puts the burden on "those seeking to include disputed content". "Seeking to include" means the ones adding it. It doesn't say "seeking to include or retain". DeCausa ( talk) 13:23, 9 July 2024 (UTC)
The policy issue is where I said this: My position is that we shouldn't be listing sources as generally reliable when the community has real doubts.S Marshall  T/ C 13:46, 9 July 2024 (UTC)
I don't have a view on that. I was just pointing out you've misread ONUS. DeCausa ( talk) 15:51, 9 July 2024 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


S Marshall, I had not seen the indications of your involvement in this close, but you have even shown those here. WP:BADNAC states as the first reversal reason for a bad non-admin closure: The non-admin has demonstrated a potential conflict of interest, or lack of impartiality, by having expressed an opinion in the discussion or being otherwise involved, with the exception of closing their own withdrawn nomination as a speedy keep[a] when all other viewpoints expressed were for keeping as well. You have indicated an opinion even here, and did so beforehand as well. So I will give you the option of reversing your closure, or I will, but it's going to be reversed. A discussion like this should be closed by an impartial closer, or perhaps a panel of them, but you have shown yourself not to be that. If you do not reverse your closure, I will do so. Seraphimblade Talk to me 09:41, 9 July 2024 (UTC)
That would be an unwise and deeply controversial thing to do. I am not involved in this matter. At issue is whether the Daily Telegraph is reliable for statements about trans issues. I have never expressed a view on that. Historically I did express a view on the Daily Telegraph's reliability on politics. I said it was reliable for that, and it remains my view that the Daily Telegraph is reliable for politics. This doesn't make me involved in its reliability on other things and you do not get to unilaterally reverse a RFC close on your own judgment. That is not one of the powers the community has granted sysops.— S Marshall  T/ C 09:50, 9 July 2024 (UTC)
Either reverse or don't, coercing the closure to do so with an ultimatum is not ok. CNC ( talk) 10:20, 9 July 2024 (UTC)
That is, in fact, one of the powers the community has granted sysops. WP:NAC specifically states that NACs are not appropriate in either of the following two situations: The non-admin has demonstrated a potential conflict of interest, or lack of impartiality, by having expressed an opinion in the discussion or being otherwise involved, with the exception of closing their own withdrawn nomination as a speedy keep[a] when all other viewpoints expressed were for keeping as well., and The outcome is a close call (especially where there are several valid outcomes) or likely to be controversial. This closure at least arguably fails the two, but it dead clearly fails the second. It further states: Per Wikipedia:Deletion process § Non-administrators closing discussions,[b] inappropriate early closures of deletion debates may either be reopened by an uninvolved administrator. So, I intend to reopen it. For clarity, I don't intend to close it; I will leave that to others. I don't have a preferred outcome here, but this close was not appropriate. Seraphimblade Talk to me 10:53, 9 July 2024 (UTC)
You won't do that without pushback. This wasn't a deletion decision so you don't get to rely on rules about deletion decisions, and I'm rather self-evidently not involved. Politics is not gender.— S Marshall  T/ C 10:56, 9 July 2024 (UTC)
I don't imagine I'll do it without pushback or without having people shouting at me. I've got a pretty thick skin by now. But I still think it needs to be done. Seraphimblade Talk to me 11:01, 9 July 2024 (UTC)
I've reopened the discussion. As above, I do not intend to close it or in any way be involved with deciding on the outcome, but that outcome does need to be decided properly. Seraphimblade Talk to me 11:09, 9 July 2024 (UTC)
Overturning the close might be premature. Is it normal to short circuit an AN RFC review in such a manner? Doesn't seem very efficient to have a big discussion here if the outcome is already ordained. – Novem Linguae ( talk) 11:20, 9 July 2024 (UTC)
( edit conflict)Do you also believe, per WP:NAC, that all of S Marshall's RfC closes on controversial topics should be reverted? Do you really want to set the precedent that all controversial closes must be handled by administrators? Do you think we have that capacity? I think this is a spectacularly bad exercise of judgement. ~~ AirshipJungleman29 ( talk) 11:23, 9 July 2024 (UTC)
So you've overturned and relisted as an involved admin in this request, because you deem the closure was involved? I can't be the only one who sees the irony in this. CNC ( talk) 11:25, 9 July 2024 (UTC)
I saw a supervote/BADNAC here, and overturned it. I think that's what should be done. I wasn't involved in the discussion; I was upset by it because of how clearly unacceptable it was. That close didn't summarize the opinions in the discussions, it expressed the opinions of the closer. If that's not a bad close, I don't know what is. Seraphimblade Talk to me 11:30, 9 July 2024 (UTC)
And why do you think your 'upset' trumps the opinions of other editors who have expressed support for this close, or indeed those that agree that it should be overturned, but have decided to express that through discussion? This was very poor judgement. –  Joe ( talk) 11:33, 9 July 2024 (UTC)
BADNAC or not, your decision makes a mockery of this RfC review process. You expressed your opinion below to overturn and are clearly involved in the dispute here, then went ahead and supervoted the outcome. Being upset is no excuse for this, it's shocking. CNC ( talk) 11:39, 9 July 2024 (UTC)
@ Seraphimblade: Please restore the close and follow process here. voorts ( talk/ contributions) 12:11, 9 July 2024 (UTC)
Jesus Christ, what arrogance. Okay someone close this close review, although the AN certainly hasn't seen the last of this.— S Marshall  T/ C 11:35, 9 July 2024 (UTC)
I'm stunned, Seraphimblade. Not only did you choose to ignore all the editors telling you that this was a bad idea and do it anyway, but you're now edit warring over it. Do you think this is how contentious decisions should be carried out? –  Joe ( talk) 11:44, 9 July 2024 (UTC)
The close review shouldn't be closed. Seraphimblade should either do the right thing or a new discussion should he started here about the unilaterak overturn. voorts ( talk/ contributions) 12:14, 9 July 2024 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Non-participants

  • Overturn. Firstly, the close strikes me as making an argument rather than summarizing them, which raises at least substantial concerns of a supervote. But, that aside, the close seems to be a "no consensus", which means no change to the status quo, yet it then calls for a change in the status quo. Given these concerns and the incoherent nature in general, I think the discussion needs to be reclosed in terms of first, determining if there is any consensus whatsoever (if "no", no changes are made), and, if so, what it is and why. While I have not exhaustively reviewed the discussion, I did take a look over it, and I don't think a clear consensus could be discerned from it, so I think a "no consensus, therefore no change" closure would be the most appropriate result. But certainly "No consensus, but make a change anyway" is an incoherent one, so that can't stand. Seraphimblade Talk to me 06:03, 9 July 2024 (UTC)
  • Comment. Responding to I decided to treat this as more like a content decision governed by WP:ONUS than a procedural one governed by AFD consensus. In doing this, I removed the first mover advantage that the "generally reliable" side expected and I think relied on. At issue here is the question: was I right to do that? It is my opinion that "no consensus" often means "no change", even outside of AFD. But RSP is a clear exception to this, as stated in WP:MREL. No consensus, unclear, or additional considerations apply. The words "no consensus" are literally in the title/definition of what is frequently "option 2" in RSN RFCs. Unfortunately, my opinion on this does not add clarity here, but instead suggests that an RFC like this one, which had a lot of option 1 and option 3 !votes, could reasonably be closed as "no consensus" and become a consensus for option 2. Because of the murkiness of all of this, I leave this as a comment rather than a bolded endorse/overturn, and I simply leave this as food for thought. – Novem Linguae ( talk) 08:57, 9 July 2024 (UTC)
    Agree. RSP is simply a place where summaries of discussions are documented, not much else. We can't omit NC discussions because there was previously consensus for X, Y and Z. Whether previous consensus should remain, or be prioritised over a NC discussion, is another topic that effects more RSP entries than just The Telegraph. CNC ( talk) 09:47, 9 July 2024 (UTC)
    As to where the boundary of WP:INVOLVED is, it is my opinion that one is involved if reasonable editors perceive the closer as having an obvious bias. Even if the closer is not actually biased, the perception of such is important, imo. Is S Marshall involved here? I don't know. It will depend on if more than a couple editors feel that he has an obvious bias. A couple clearly think he does, but I think more input is needed before deciding that. – Novem Linguae ( talk) 11:28, 9 July 2024 (UTC)
    While your obviously entitled to your opinion, INVOLVED is not based on having a perceived bias. You have to prove that bias makes the closure impartial based on disputes or conflicts with other editors within that topic area. CNC ( talk) 11:42, 9 July 2024 (UTC)
  • Endorse close, but can understand re-listing in order to be re-closed by a group of editors to satisfy all these "extra" issues, specifically regarding the closing summary. From a look at the discussion, I don't think any other close could have reasonably ascertained that there was consensus for GR or GU while remaining impartial, and thus no consensus was the correct assessment by default. I found the closing rationale very reasonable, even if I do understand concerns regarding some of the wording. In my opinion the weight given to the dispute of reliability in the closing summary otherwise makes sense. If the RfC failed to gain consensus, it makes sense to use more words explaining why there wasn't consensus from those who disputed reliability, as opposed to elaborating on why editors believed it was reliable, similar to the closure summaries of other contentious RfCs. Concerns over the closure's involvement otherwise need to be supported with diffs, specifically of the closure's involvement in disputes regarding The Telegraph or trans issues, otherwise this "fall back" argument is meaningless. CNC ( talk) 10:06, 9 July 2024 (UTC)
    @ CommunityNotesContributor: I think you overlooked this diff I provided - sorry, I should have made its presence clearer rather than including it as a WP:EASTEREGG. BilledMammal ( talk) 10:10, 9 July 2024 (UTC)
    So no dispute then? Having an opinion is not being involved. Anything else? CNC ( talk) 10:13, 9 July 2024 (UTC)
    The dispute was regarding the reliability of the Telegraph. Having an opinion made them a party to that dispute. Editors who are parties to a dispute are forbidden from closing discussions broadly related to that dispute, and whether the Telegraph is reliable for politics is a dispute very closely related to whether it is reliable for trans issues. BilledMammal ( talk) 10:20, 9 July 2024 (UTC)
    "Having an opinion made them a party to that dispute." That's a huge stretch. CNC ( talk) 10:24, 9 July 2024 (UTC)
    To clarify; they expressed their opinion while participating in the dispute. That makes them a party to the dispute. BilledMammal ( talk) 10:27, 9 July 2024 (UTC)
    The discussion was "What do we think of the reliability of this story", the editor provided an opinion on that. They didn't engage in any dispute with other editors, ie argue with other editors, it was an isolated comment. To clarify, this discussion is a dispute, because we are arguing. See the difference? CNC ( talk) 10:33, 9 July 2024 (UTC)
    The discussion was Reliability of the Daily Telegraph for politics?, and the notion that it is only a dispute if there is arguing is... novel. Interpreting it that way would mean that editors would even be able to close RfC's they participate in, so long as they don't engage in any back-and-forth discussion.
    This discussion is getting a little deep, so I'll step out now. BilledMammal ( talk) 10:40, 9 July 2024 (UTC)
    WP:INVOLVED does have novel wording: " Involvement is construed broadly by the community to include current or past conflicts with an editor (or editors), and disputes on topics,...". This is not a " conflict" with other editors, nor based on trans topics. The wording at WP:CLOSE arguably has a higher bar for contesting: "if the closing editor may have become inextricably involved through previous experience in the conflict area", so a throwaway opinion isn't going to cut it here. CNC ( talk) 11:19, 9 July 2024 (UTC)
  • Endorse. I found the close very reasoned. I can understand that some may take issue with the description "unashamed embrace", however the crux of the issue is that the paper published a hoax in the area of gender identity and when it was demonstrated that it was hoax they didn't publish a correction. To me that seems perfectly relevant to the question of whether The Telegraph is reliable on trans issues regardless of the specific wording. TarnishedPath talk 11:35, 9 July 2024 (UTC)
    What hoax are you referring to with the paper published a hoax? BilledMammal ( talk) 11:38, 9 July 2024 (UTC)
    The kitty litter hoax, the claim that accommodations were being made to children who identified as animals. Is there something else that the close referred to as an "unashamed embrace" of? TarnishedPath talk 03:36, 10 July 2024 (UTC)
    The paper did not make that claim, it reported on others making that claim, cited to them. It did not report that as fact. We don't expect reliable sources to avoid reporting on others spouting falsehoods - otherwise every US news source that has reported on all of Trump's falsehoods would have to be unreliable, since they reported them! -bɜ:ʳkənhɪmez ( User/ say hi!) 04:12, 10 July 2024 (UTC)
    (however many do expect newspapers to issue updates when falsehoods come to light, but we're going off-topic here. point is, that part of the close unduly exaggerates the consensus on the nature of the issue discussed.) Aaron Liu ( talk) 04:16, 10 July 2024 (UTC)
    There was a recent discussion about Al Jazeera that many of the editors commenting here had to have seen (and quite a few participated in) where the conclusion I observed is that is not expected for "news" that was accurate at the time and cited/attributed to another source that later updates itself - so long as their future news stories are in compliance with the updated information. I agree with you that it unduly exaggerates the amount of consensus for "unreliable" to make it a "no consensus". -bɜ:ʳkənhɪmez ( User/ say hi!) 05:34, 10 July 2024 (UTC)
    That the newspaper published a hoax is not a summary of the discussion. It is one contention that was strongly disputed within the discussion. The term "unashamed embrace" shouldn't be an issue for some, it should be an issue for all, as it wasn't even argued during the discussion. Editors who claimed the Telegraph was knowingly printing false material also often argued that they snuck it in through quotes by dubious actors rather than putting it in their own voice. Samuelshraga ( talk) 14:35, 9 July 2024 (UTC)
  • Overturn. Closer says that WP:ONUS applies to editors who object to adding a rule so "those who want the status quo need to achieve positive consensus for it", it will be good if admins comment that's not how it works. It's fine to agree with the minority that the cat affair justifies action but that's a vote not an evaluation of consensus. However, adding twaddle to the essay-class WP:RSP page needn't concern admins. Peter Gulutzan ( talk) 13:59, 9 July 2024 (UTC)
  • Overturn. Given that the closer assessed this as "no consensus", the correct and only outcome is to retain the status quo, which is that the Telegraph is "generally reliable". The spiel above about WP:ONUS mandating some other outcome is not supported by WP guidelines and effectively takes the close into WP:SUPERVOTE territory. This should be reclosed properly, with no consensus meaning no change to the status. That's not to say we would always have to follow the Telegraph on trans issues, of course, ONUS does apply at individual article level across the project, and where claims in the Telegraph represent WP:FRINGE viewpoints when compared with other sources, it's correct to ignore them. That's a far cry from there being a consensus to label it as "reliability disputed" though.  —  Amakuru ( talk) 14:52, 9 July 2024 (UTC)
    Note that "no consensus" for a source evaluation brings it into WP:MREL, its own status for "no consensus". Aaron Liu ( talk) 15:41, 9 July 2024 (UTC)
    That would apply if the matter had never been discussed before, with no status quo, and this were to establish a new position. But that's not the case. There was an RFC in 2022 which concluded that the Telegraph is generally reliable. This RFC here sought to amend that prior consensus and add a new caveat for trans issues specifically. Altering previous consensus requires consensus, not a lack thereof. Lack of consensus means retain status quo.  —  Amakuru ( talk) 16:10, 9 July 2024 (UTC)
    Lack of consensus that a source is generally reliable means that it isn't generally reliable. Thryduulf ( talk) 16:13, 9 July 2024 (UTC)
    It means nothing of the sort. It means nobody could agree if it is or not. You don't get to "win" the argument by default just because some people agreed with you and some people didn't. This principle would also apply if it had previously been declared unreliable. The status quo remains.  —  Amakuru ( talk) 16:15, 9 July 2024 (UTC)
    If nobody can agree if it is or is not reliable, then it can't, by definition, be generally reliable. WP:RSP#Legend defines "Generally reliable" as Editors show consensus that the source is reliable in most cases Thryduulf ( talk) 16:18, 9 July 2024 (UTC)
    The status quo of RSP is categorising discussions based on consensus or lack of. CNC ( talk) 16:19, 9 July 2024 (UTC)
    It's been referenced before but RSP is a summary of discussions. If there is no consensus over the reliability of a source, or over a particular topic from a source, then it will be documented as such. The reliability of The Telegraph was otherwise previously discussed prior to the RfC. What your implying has broader implications on RSP categorisation. CNC ( talk) 16:17, 9 July 2024 (UTC)
  • Overturn. Potential involvement aside, the bit about WP:ONUS on the closer's talk page takes this into supervote territory. I will leave it to the new closer or closers to decide the outcome. ~~ Jessintime ( talk) 15:28, 9 July 2024 (UTC)
  • Endorse. This was a good close. Firstly I don't see how a single past opinion about a separate topic that The Daily Telegraph covers would then indicate the closer is therefore WP:INVOLVED in this topical circumstance (i.e., this single opinion doesn't make the closer " inextricably involved... in the conflict area"). This is especially true in this case, where the closer's broader comment was essentially about the apparent ability of the newspaper to still remain factual despite the individual biases of of a subset of employees. Secondly, about the close itself, the legend for Perennial Sources list entries labeled "No consensus, unclear, or additional considerations apply" (i.e. Option 2 of RSN RfCs) provides the relevant detail for evaluation here: "Editors may not have been able to agree on whether the source is appropriate, or may have agreed that it is only reliable in certain circumstances." The discussion in this RfC clearly fits the description of "may not have been able to agree on whether the source is appropriate". If discussions are split between Options 1 and 3 (or 4) and no consensus emerges, as was the case here, the discussion then pretty clearly renders into Option 2 territory when it's time to close. It's clear to me the Option 2 of active RfC discussions is for considering the "unclear" and "additional considerations apply" aspects of the label during such discussions, but needn't be explicitly invoked at a level that cements 'consensus for a lack of consensus', so to speak, for it to be the correct outcome. This case shakes out as no consensus about the reliability of The Daily Telegraph for the subject of trans issues, exactly as the closer found it. -- Pinchme123 ( talk) 20:56, 9 July 2024 (UTC)
  • Endorse as far as I am concerned, closes deserve some minor presumption of regularity, and there should be a showing of some meaningful issue or bias before we go about overturning one. I see nothing of the sort here, and the close strikes me as well within the range of possibilities that a reasonable closer might choose. Cheers, all. Dumuzid ( talk) 21:18, 9 July 2024 (UTC)
  • Overturn. The closer's summary is rife with misleading claims and analysis, along with real concerns of a supervote, as many others have pointed out at length. I'd like to put specific emphasis on what the closer should have, but did not mention in the summary:
    • 1. The sheer amount of sensationalist claims the original poster had listed that went on to be directly and irrefutibly shown to be either false or misleading. See discussion there at length
    • 2. Directly following that, a re-evaluation of the merits of the one remaining possible 'single mistake' (the child's identity as a cat) to even possibly warrant this RfD to result in a characterization of 'reliability disputed'
    • 3. An accurate presentation of the terms of that misrepresented 'one mistake', which was revealed in discussion to be a mistaken assumption based on information the paper was provided with
    • 4. The major amount of support in the 'unreliable' camp that were either based on non-arguments or used language suggesting they had taken all of the original poster's assertions at face value. A sampling: "it was extensively proven that the Telegraph propagates blatant lies"; another user says "we should never use a newspaper for almost anything"; yet another states "the Telegraph is not a source of expert opinion on this topic... there's no reason Wikipedia needs to publish anything they say about it". There are many more !votes that are non-starters when you read the reasoning.
The closer did not recognize the importance of depreciating the value of any editors' votes that were not based on any evidence discussed in the RfC, besides the other issues raised above and by other editors. I hope the next close will be fairer. JoeJShmo 💌 06:26, 10 July 2024 (UTC)
  • Overturn While I think I agree with the closer, the way it was phrased makes it fairly clear this was a supervote at best. Lulfas ( talk) 17:57, 10 July 2024 (UTC)
  • Overturn First, I don't find the WP:INVOLVED argument compelling. Commenting on a previous RFC about the Telegraph's reliability as a whole is approaching the line, but I think it is firmly on the "acceptable" side of it. Reading the close itself, I see substantial defects on the merits to the point that it looks like a WP:SUPERVOTE. The close seems to take assertions made by the 3/4 camp at face value (especially the litter box thing, which was a clear point of disagreement as to what facts they were stating), while minimizing or totally glossing over arguments made by the 1 !voters, especially the comprehensive refutations of the RFC basis by Chess. The weighting applied to these arguments is also strange. Editors on both sides made some poor arguments, but a lot of the 3 and most of the 4 !voters made arguments that were weak or totally irrelevant. Those addressing the opinion pieces or "platforming" certain views mean nothing for reliability, since those are already unusable for statements of fact. Some accepted the litter box claims at face value, totally ignoring the refutations to them much like the close itself did. Other !votes were bare statements of opinion, such as I'd barely trust the Telegraph with the weather, let alone any politics, and least of all any kind of gender politics. When these non-arguments are down-weighted or discarded, I believe the consensus becomes very clear. I would have closed it as WP:GREL, but with an additional note that while factually reliable, there was consensus that their coverage of trans issues is biased and special attention should be given to WP:DUE. The Wordsmith Talk to me 18:29, 10 July 2024 (UTC)
    But that clearly would have been a WP:SUPERVOTE, since there obviously wasn't a consensus in the discussion. The idea that a "refutation" must be accepted by everyone else who !votes subsequent to it is obviously silly. The "refutation" just wasn't convincing to many editors. Loki ( talk) 18:38, 10 July 2024 (UTC)
    It was not convincing or not - many editors chose to ignore it completely, rather than explain why they were not convinced. As I stated elsewhere, if an editor wishes to express their view that a refutation is not convincing, that is fine and could be given weight as appropriate, as the person you replied to did. But if all they do is ignore it, their vote must be seen in light of the fact they are ignoring the discussion on it, and only commenting with their opinion. -bɜ:ʳkənhɪmez ( User/ say hi!) 19:02, 10 July 2024 (UTC)
    In which case we must also regard every comment that does not explicitly mention every piece of evidence or (claimed) refutations of that evidence as ignoring that evidence and/or refutation. i.e. the same standards must be applied to everyone. Thryduulf ( talk) 19:06, 10 July 2024 (UTC)
    I don't think it is especially controversial to say that a !vote that considers the counter arguments and rejects them is stronger than one that simply repeats the claims with nothing showing they've done any actual analysis of it. I didn't say those should be totally ignored, just weighted accordingly. The Wordsmith Talk to me 19:11, 10 July 2024 (UTC)
    I think it's more controversial than you think it is. Imagine the following two !votes:
    • Support I think we should only include a mention of Darwin's Origin of Species, because of the many reliable sources that support it, and the zero that support the "aliens did it" hypothesis advanced by the OP. - Alice
    • Oppose Alice claims that no reliable sources support the "aliens did it" hypothesis, but what about "Aliens Did It" by Quacky McQuackerson? - Bob
    Which of these !votes is stronger? Which should be weighted more highly? Loki ( talk) 19:56, 10 July 2024 (UTC)
    Considering that in this hypothetical you're "Bob" (Alice claims that the Telegraph doesn't endorse the Litter boxes in schools hoax, but what about this article where they call it a hoax?), that isn't exactly a counter-argument. BilledMammal ( talk) 20:00, 10 July 2024 (UTC)
    You are indeed Bob in this case. You are saying that the source says something that everyone with eyes can read for themselves is not what the source is saying. You’ve claimed that the source “states that the litter boxes in schools happened” - but that was clearly refuted as they merely reported on the hoax that was stated by others, with attribution. Ditto for the other things you’ve claimed. To be quite blunt, when an editor is as misleading as your initial claims in the RfC are, and they are so clearly refuted that there is virtually nobody arguing after the fact that isn’t equally misrepresenting the sources, all of the !votes based on the misrepresentation need to be weighted heavily down, or given no weight if they provide zero other justification than the misinformation.
    In other words, we should not be in the habit of rewarding people who promote quackery (such as Bob), or who promote misinformation/misleading reading of a source to try and “win” the argument (like you did). -bɜ:ʳkənhɪmez ( User/ say hi!) 20:09, 10 July 2024 (UTC)
    You say "everyone with eyes" agrees with you, ignoring the many people with eyes who disagree with you. Loki ( talk) 20:15, 10 July 2024 (UTC)
    ...which is what many option 3 !voters did. The difference between these sides which both didn't mention refutations is that more option 3 !voters often did not provide refutations. Aaron Liu ( talk) 20:16, 10 July 2024 (UTC)
    And what I'm saying here is that a weak refutation should not be more heavily weighted than no refutation. If anything it should be weighted less, because it reveals a fundamentally weak argument. Loki ( talk) 20:20, 10 July 2024 (UTC)
    That’s absolutely absurd. Someone who is expressing their opinion with reasoning/rationale will always be weighted higher than someone who drives by and “throws a !vote at the house”. You claim it’s weak, then care to explain why a majority of “non drive by” editors after the refutation agreed with it? And of those who didn’t, very few bothered to actually explain what they found wrong with it? Those two things are, in fact, the sign of a strong refutation. -bɜ:ʳkənhɪmez ( User/ say hi!) 20:25, 10 July 2024 (UTC)
    I disagree wholeheartedly. This contention seems entirely misconceived to me, and also somewhat oppressive. Giving full reasons can't be mandatory. If I'm at AfD, I shouldn't have to type out, "I concur with the nominator. I too have carried out an exhausive search for sources and I too have not been able to locate an acceptable one. Like the nominator, I don't agree that this person's blog is a useful source for their biography." I should be allowed to type "Delete per nom" in the happy expectation that my contribution will get full weight. People must not be made to feel they have to type out arguments that have already been well made, in full, before their view is counted.— S Marshall  T/ C 22:23, 10 July 2024 (UTC)
    It depends on the context. If at the AfD the nom says "Fails GNG", and an editor subsequently posts a list of sources, saying "per nom" is a very weak argument - you need to address the rebuttal.
    It's similar here. If you say "Per Loki", you need to address the rebuttal that argued Loki not only failed to provide sources for the claim that the Telegraph endorsed the Litter boxes in schools hoax, but that one of the sources they did provide explicitly called it a hoax. BilledMammal ( talk) 22:27, 10 July 2024 (UTC)
    It's long been understood that WP:PERX is a weak argument. While WP:ATA is an essay, it has broad community support. As mentioned on that page, Where reasonable counter-arguments to the nomination have been raised in the discussion, you may wish to explain how you justify your support in your own words and, where possible, marshalling your own evidence. At least giving some evidence that you've read the opposing arguments and disagree with them shows that you've done some kind of analysis. If we don't weigh arguments according to how comprehensive, informed, and well-grounded they are then all we have left is a headcount. To also quote from WP:CRFC, The degree to which arguments have been rebutted by other editors may be relevant, as long as the rebuttals themselves carry sufficient weight. If one group is responding directly to the other’s arguments but the other isn’t, that may be relevant to determining which group has better reasoning. The Wordsmith Talk to me 23:38, 10 July 2024 (UTC)
    When the arguments they are citing have been solidly refuted with significant agreement with that refutation, then yes, the editor should be expected to justify their agreement or have their argument down weighted accordingly. -bɜ:ʳkənhɪmez ( User/ say hi!) 23:50, 10 July 2024 (UTC)
    Considering almost all of nom's original arguments were at best misrepresentations, votes along the lines of "delete per nom" should've been- and should be- majority depreciated. The litter box hoax was a non starter, and nom was reduced to "claims along the lines of a litter box hoax". Further claims were shown to be non-starters as well. Any vote relying on nom's presentation of the issues stated quite possibly could've been completely disqualified, and at the least depreciated. JoeJShmo 💌 01:21, 11 July 2024 (UTC)
    @ S Marshall, is your reading of the discussion that Loki's opening stood more or less unrebutted? Nominator brought 14 links to the Telegraph in their nomination. 9 were described by nominator as directly saying false things. All 9 by my count conclusively refuted farther in the discussion as nothing more than biased presentation at most.
    The 5 others were to do with the cat-gate at Rye College. Nominator brought two articles from the Guardian and Pink News to show Telegraph coverage was proven false. In fact, while the Pink News at least states that the Telegraph's reporting is false, it certainly doesn't prove it. The Guardian simply carries the school's denial that a student identifies as a cat.
    And then the rub. No one has actually proven that a student did or didn't identify as a cat. But editors continue to dispute whether demonstrating factual inaccuracy is an important part of a finding of unreliability, so there's that.
    Nominator also brought up some academic sources which I haven't had time to look into as deeply but which were strongly contested in discussion (and which you didn't mention in your close anyway).
    So out of 14 Telegraph articles, and 2 articles in the Guardian and Pink News, nominator managed to directly misrepresent the content of 11, and there is, at the very least, a significant case that nominator directly misrepresented the content of the other 5. This was spelled out clearly early in the discussion. But you think "Per Loki" and "Per Chess" should be given equal weight, because Loki actually made the misrepresentations, while Chess only pointed them out? Samuelshraga ( talk) 06:02, 11 July 2024 (UTC)
Loki's nomination statement was exhaustively analyzed by the community in that RFC. It enjoyed significant support and received significant opposition, and overall there was no consensus about its accuracy. The question at issue in that RFC was: Where does bias become unreliability? The community doesn't agree on the answer, but there certainly is not a consensus that the Telegraph is general reliable about trans people.
I did not say and do not think that all Loki's arguments were unrefuted. I do think it's proven that the Telegraph's reporting on the litter boxes in schools hoax was inflammatory in the extreme, that it published the report using reported speech but otherwise uncritically, and that it failed to publish a correction.— S Marshall  T/ C 07:06, 11 July 2024 (UTC)
This is just not a reasonable, policy-informed reading of the RfC. The question at issue was not Where does bias become unreliability. Bias does not become unreliability. One can be biased without being unreliable and vice versa. The question was "What is the reliability of the Telegraph on trans issues?". Being inflammatory is not evidence of unreliability. Failing to publish a correction is not evidence of unreliability if it can't be demonstrated that the paper published a falsehood.
The nomination statement enjoyed significant support and received significant opposition, and overall there was no consensus about its accuracy. Is this more vote counting? Where have you weighed arguments? Samuelshraga ( talk) 07:41, 11 July 2024 (UTC)
...and now we're getting somewhere. You don't have to be caught in a lie to be deceptive. Those appalling fundraising banners that the Wikimedia Foundation displays on our site are a really good example of this: being deceptive without actually lying. This practice of misleading people by telling the absolute truth, in an incredibly selective way, is called paltering and it's widely used by marketers, politicians, lawyers, pressure groups, and at least here in the UK, in newspapers. And if you could read what the "unreliable" camp said without understanding this, then I would gently suggest that you have an opportunity to re-read the debate more carefully.
The "unreliable" camp did not have to catch the Daily Telegraph in a falsehood. They just had to catch them telling the truth so selectively that bias becomes actual deception.
They didn't have to prove the Daily Telegraph intends to deceive. Deception can be inadvertent, particularly when it's by editors who're checking facts rather than checking for balance. We know all about this from Wikipedian content disputes: it's possible to deceive in good faith.
All the "unreliable" camp had to do was convince Wikipedians (1) that it's possible to be mislead by the Telegraph's coverage and (2) this happens often enough to affect the Daily Telegraph's reliability about trans people.
In my judgment, they failed. They did not achieve a consensus that the Daily Telegraph is unreliable.
I then had to decide what to do in the absence of a consensus.— S Marshall  T/ C 08:57, 11 July 2024 (UTC)
It's fascinating if this was the basis for your ruling, given that you don't seem to have mentioned this in either your original or expanded close.
Had you mentioned it, doubtless you would have given an excellent explanation of how when editors rebutted charges of "misleading" with a defence of factual accuracy (e.g. here), they were missing the point. And pointed to discussants who actually said that being accurate but misleading was the basis of their case for GUNREL.
And when it was argued that the bar for reliability should be rooted in what false/misleading claims could be cited in articles rather than uncitable misleading implications (first sentence here and last 2 paragraphs here), you would have explained which counter-arguments you found to this point and how you weighted them, to reach a No Consensus finding.
I also note that this is the 3rd separate explanation I've seen you give for your close. It still doesn't contain a weighing of arguments, but I'll grant you that it's less egregious than the previous two. I look forward to the next one. Samuelshraga ( talk) 10:46, 11 July 2024 (UTC)
I'm clearly never going to convince you, but I have a chance at convincing your audience, so I'll deal with that too.
I'm allowed to explain my close in different ways, because you're allowed to spend thousands of words attacking it in different ways.
It's not for me to decide which counterarguments are persuasive. That's not the closer's role.
The RFC isn't a closer's suggestion box. It's an exhaustive dive into what the community thinks.
I don't decide who was right. I decide what the community as a whole thinks about the subject.
I believe that the community as a whole is at "no consensus" on the Daily Telegraph's reliability on trans issues.
And I believe that RSP should say so.
And if I'd weighted the arguments the way you want, I really would have been supervoting.— S Marshall  T/ C 11:42, 11 July 2024 (UTC)
If I thought you'd weighed arguments in a way that I don't like - if I thought you'd weighed arguments at all - then I would have just grumbled about Wikipedia in my head, and not come to a big central forum like this.
People on this noticeboard seem to have plenty of respect for your track record as a closer, even if they think you missed the mark here. As someone who is new to these discussions, I don't see much to respect about this close. In fact I don't see much evidence that you even gave the RfC more than a cursory skim. I wasn't one of the people who invested a lot of time in the arguments at the RfC, but if I were I would be pretty livid that someone would come on and clearly count votes without reference to arguments or policy. If I encounter your future closes I will endeavour to keep an open mind, in deference to the people who seem to value your contributions in general, though not in this case. Samuelshraga ( talk) 13:06, 11 July 2024 (UTC)
  • The idea that a "refutation" must be accepted by everyone else who !votes subsequent to it is not what's being proposed here. I also don't expect S Marshall to take every unrefuted point as fact,
    The ask is that a closing statement explain why an evaluation of consensus was made.
    S Marshall accepted your view that The Telegraph promoted the litter boxes in schools hoax, but did not provide an explanation for why your claim was the consensus and why refutations of it were not. Because your claim was accepted at face value, the consensus was for Option 2.
    I expect closes to explain why opposing views were rejected in addition to summarizing consensus. Otherwise, there is no indication that a closer considered viewpoints other than the one they ultimately endorsed. Chess ( talk) (please mention me on reply) 21:02, 10 July 2024 (UTC)
    Very, very well put. -bɜ:ʳkənhɪmez ( User/ say hi!) 21:09, 10 July 2024 (UTC)
    Note that this was originally a reply to Loki's comment above, starting with But that clearly would have been a WP:SUPERVOTE. Aaron Liu ( talk) 03:14, 12 July 2024 (UTC)
  • Endorse. As Novem Linguae notes in their comment above, no consensus on source reliability is not the same thing as no change or keeping the status quo. We have here a source which where reliability is a matter of contention among editors, with dozens of well explained and policy-grounded arguments for both declaring the source as unreliable and reliable. Even discounting arguments focused on bias instead of reliability, I can see no weighing of the arguments that comes to any conclusion besides that editors do not agree on the reliability of The Telegraph on transgender topics. WP:MREL exists for a reason. RSP provides guidance on whether there is broad consensus on the reliability of common sources. Source evaluation within articles is always a matter of judging the specific claims and context. Dylnuge ( TalkEdits) 02:12, 11 July 2024 (UTC)
  • Overturn and reclose to same result. People have already pointed out the problems with the close statement itself, but I think "no consensus" is the correct conclusion to be drawn from that discussion. WP:MREL says Editors may not have been able to agree on whether the source is appropriate which I think is certainly the case here. It would be very hard to close the discussion for one side or the other without that close being a supervote itself. Pinguinn  🐧 11:38, 11 July 2024 (UTC)
  • Endorse outside of paragraph 3 The INVOLVED concerns do not move me per CNC, and I think S Marshall's interpretation of RSP (that a lack of consensus for reliability should be explicitly noted, not keep the status quo) is correct. With that being said, no consensus was found that the Telegraph articles about the Rye College debacle constituted promotion of a "hoax"; the closer writes about it as if the proposition there was hoax-promotion was agreed upon, and editors disagreed whether that alone was enough to make the Telegraph unreliable. Still, there was definitely not consensus the Telegraph is reliable for these issues; Aquillion's presentation of academic sources that criticize the Telegraph's reporting on this subject was never adequately rebutted, for one.
Even if S Marshall's close was flawed, I really do not want to go through the whole song and dance of reclosing with what will almost certainly be the same result, stated more verbosely. Sometimes I feel as if the consensus model tends toward rule by CAVE people. Mach61 13:05, 11 July 2024 (UTC)
  • Overturn Agree with the those who have argued that this should be reclosed properly. Even some of the editors who endorse the close recognize there's problems with wording of the close. The best way forward is to overturn the close and close it correctly. I realize this might seem like a waste of time, but when editors invest this much time into a review we might as well get it right. Thanks! Nemov ( talk) 14:39, 11 July 2024 (UTC)
  • Endorse Its pretty clear from above that many agree with the close substance, like I do as well. It seems that the closer made a comment in the close that led to this discussion, but that doesnt lead me to question the substance of the close. I do not find the supervote nor involved arguments to be convincing either. If the source isnt generally reliable, which clearly it isnt from this and other discussions, then it starts to look more like a drop the stick or SOAP issue to me. Jtbobwaysf ( talk) 20:03, 11 July 2024 (UTC)
    • @ Jtbobwaysf: - regardless of the substance of the close, the controversial comment I suppose you are referring to was explictly referred to in the added RSN entry: ("In the 2024 RfC, The Telegraph's "unashamed embrace of the widely-debunked litter boxes in schools hoax" was discussed, and it was noted that the misrepresentations about this remain unretracted.) How do we solve this issue if the close is endorsed? starship .paint ( RUN) 00:05, 12 July 2024 (UTC)
      The obvious place would be discussing it at RSP, to discuss how a summary should read. I don't think you'll find any support for including that quote in future, based on this discussion alone. Common sense can simply prevail here. CNC ( talk) 01:28, 12 July 2024 (UTC)
      I don't question the substance either, but it is extremely bad for what's supposed to be a neutral summary that saves peoples' time to mislead its readers on such an important point. Aaron Liu ( talk) 03:15, 12 July 2024 (UTC)
      I agree with CNC that this additional and unnecessary summary of the close should be trimmed over at RSP. The fact that we are discussing such far off theories (even if untrue) associated with this source should point to the validity of the close. Again I endorse, I am confident the additional comment can be struck without needing to re-run the discussion. Just do what is simple rather than making it complicated. I believe whoever closes this discussion can just find that the close comment as a matter of fact is incorrect (while the overall close is non-controversial), strike it, and thus subsequently remove the summary over at at RSP. Seems simple enough to me Jtbobwaysf ( talk) 09:57, 12 July 2024 (UTC)
      So now we've got the nominator at this close review who wants to overturn, and an uninvolved contributor who endorses, both giving exactly the same reasoning for their position.— S Marshall  T/ C 10:36, 12 July 2024 (UTC)
      Important to note that I dont agree that the closer was involved, so we disagree on a key policy issue. We can be clear from this review discussion as well as the original discussion that there is clearly no-consensus that the source is reliable, or anywhere close to reliable for that matter. This isnt a matter where this discussion is going to be overturned and then spontaneously the source will be viewed in the next discussion as reliable. So common sense means we would not need to overturn this to put it back to another discussion, as if the matter was undecided. We are only dealing with a close summary that was a bit off, but the close itself is correct. Thanks! Jtbobwaysf ( talk) 11:28, 12 July 2024 (UTC)
      I think that overturning that paragraph counts as overturning the close. It seems Jtbob feels like the biggest damages can be resolved without amending the close statement and that the summary isn't damaging enough to amend, the latter of which I definitely disagree with. Aaron Liu ( talk) 15:33, 12 July 2024 (UTC)
      You're right that directly amending the close would be overturning. Hence for example I endorse the close as the correct outcome, but can understand overturning based on the summary. The reality is this RfC could be closed specifying that parts of the closing summary X, Y and Z, were inappropriate and/or inaccurate, while not directly overturning that RfC, only adding an additional summary to it, based on the discussion that has occurred here. Ie as a note to the top of that RfC, but not within it, thus not actually overturning the close itself. Sometimes it'd be nice to simply think outside the box to avoid a lot of legwork of re-closing such a long RfC. CNC ( talk) 16:17, 12 July 2024 (UTC)
      I don't see how the additional summary would work. If it doesn't mention that the close's language on Rye College is inaccurate, then it won't really be effective. If it does, I feel like we'd need consensus that it's inaccurate. Aaron Liu ( talk) 18:21, 12 July 2024 (UTC)
      Consensus based on the close of this RfC, attached above the previous. It would be the same concept as re-closing with the same result, without the extra hassle. A new concept you might say. CNC ( talk) 19:54, 12 July 2024 (UTC)
      I feel like that would require the same level of consensus as a closure review. Aaron Liu ( talk) 22:09, 12 July 2024 (UTC)
      It wouldn't no. It would be another RfC closure, as this is an RfC. CNC ( talk) 22:22, 12 July 2024 (UTC)
    This isn't an RfC, and if it requires consensus here anyway I'd rather we just amend the original language than invent something untested and potentially confusing. Aaron Liu ( talk) 22:31, 12 July 2024 (UTC)
  • Endorse except paragraph 3. S Marshall's interpretation of RSP is right. However, 'unashamed embrace' of the litter boxes hoax is an inaccurate summary of consensus. That incorrect phrasing was immediately being used in RSP for anyone looking-up the source. Rewriting that part might be the simplest way of resolving this, some editors have helpfully suggested alternative wording. I can believe the closer is usually good, I agree with much of what they say and know closing detail is tricky, but the summary currently doesn't do justice to the editors who spent time analysing the sources. It makes sense to bring up the further explanation added by the closer afterward, up into the main summary, so it's all easily accessible without further clicks, Tom B ( talk) 22:42, 12 July 2024 (UTC)
  • Overturn The close was no doubt in good faith, however it is not well argued, and indeed it should not really be argued at all. It also isn't really a close.
    • It gives platform to the most flagrantly gender-critical tracts by anti-woke activists. This is irrelevant. Tracts by activists are opinion pieces, and whether they are the "most flagrant" or the "most Satanic" or the "most wonderful" they should not be cited for anything other than the opinion of their authors.
    • widely-debunked Litter boxes in schools hoax - as remarked elsewhere the Telegraph pointed out that it was a hoax. The only factual error seems to have revolved around whether there was a cat identifying pupil, which to me seems irrelevant. The crux of the story is the, undisputed, unkind criticism of the child who thought such a thing would be silly.
    • We label a source as "generally reliable" when there's widespread consensus that the source can be trusted to publish fact and retract error. I think this is overegging the pudding. In general there is consensus among relatively few editors, which we believe would be widely shared.
    • We must say […] that the Daily Telegraph is generally reliable, except as regards trans issues and gender-critical views, where the Daily Telegraph's reliability is disputed. This is really not a close. It's a continuation of the RfC by other means.
All the best: Rich Farmbrough 00:43, 13 July 2024 (UTC).
  • Overturn - too much of the closer's own opinion on the issue in dispute was in the closing statement; not enough of the statement was spent summarizing the discussion and explaining how votes were weighed. Let someone else close it; no comment on how it should be closed. But a "no consensus" result at RSN (for a perennial source) should mean a 2 (yellow) listing at RSP. That's what "2" means: no consensus on reliability. "1" if there is consensus it's reliabile, "3" if there is consensus it's not, and otherwise, 2. Levivich ( talk) 18:13, 13 July 2024 (UTC)
  • Overturn. I did not participate in the discussion and have no interest in this dispute other than an interest in broadsheet newspapers generally. The close misrepresents consensus. For example, the close says that the Telegraph embraced the hoax. In reality, there is at least no consensus that the Telegraph embraced the hoax, and a lengthy argument about whether it did. Similarly, the close misrepresents and displays a failure to understand policy. For example, the close claims that a source is not "generally reliable" unless there is widespread consensus that it is. In reality, the policy WP:NEWSORG says that news reporting from well-established news outlets is "generally" reliable for statements of fact. If it is possible under that policy to dispute the "general" reliabilty of the Telegraph at all (and it is not obvious that it is possible to dispute it under the policy, if you accept that the Telegraph is "well-established" as a national daily quality broadsheet newspaper of record established in 1855, and one of at most five such newspapers still published in England), the policy must create a presumption that it is generally reliable and place the burden of proof on those who seek to rebut that presumption. Likewise the closer claims that WP:ONUS applies to disputes over the reliability of sources. In fact, WP:ONUS applies to the disputes about the inclusion of content in articles, which is a completely different matter concerned with the exclusion of verifiable content on grounds of "due weight" and similar issues. Likewise the closer claims that the question in the RfC was where does bias become unreliability? In reality, policy WP:BIASED says that reliable sources are not required to be unbiased. Finally, the closer misrepresents the effect of no consensus in a discussion where there are already policies, namely WP:NEWSORG and WP:BIASED. If there are policies, there is an existing site consensus. WP:DETCON says "consensus is ascertained by the quality of the arguments given on the various sides of an issue, as viewed through the lens of Wikipedia policy" (my emphasis). That appears to mean viewed through the lens of the policy WP:NEWSORG. I think I should also point out that WP:RSP is not a policy or guideline, does not override the policy WP:NEWSORG, and should have been weighted accordingly. I think it could also be reasonably argued that no consensus is capable of meaning "no consensus to change the text of RSP", but I express no opinion about whether it does mean that. James500 ( talk) 07:52, 14 July 2024 (UTC)
    WP:NEWSORG isn't policy, and it doesn't say all newspapers are reliable unless there's consensus otherwise. We've rightly found parts of the British mainstream press, notably but not only the Daily Mail, properly unreliable in the past. The burden of proof doesn't lie where you say it does.— S Marshall  T/ C 09:27, 14 July 2024 (UTC)
    Okay, upon closer inspection, I find that WP:NEWSORG is in fact a guideline, and not a policy. However, if WP:DETCON does not apply to guidelines, the effect would be to throw all guidelines out of the window. I am not aware that we have ever found a quality broadsheet print newspaper to be unreliable. The Daily Mail is a tabloid, and it is not, and as far as I am aware, never has been, quality press. It is not apparent that the Daily Mail is "well established" within the meaning of WP:NEWSORG. I think I should point out that NEWSORG makes a distiction between news sources being reliable and their being generally reliable. I am not saying that the Telegraph cannot be unreliable for a particular fact or statement, or even for a particular topic. I am saying that "generally reliable" means something different to that in NEWSORG. James500 ( talk) 09:43, 14 July 2024 (UTC)
    Well, exactly so. The discussion we're analysing is about whether the Telegraph is unreliable for a particular topic, to whit, trans people. My position is that there's no consensus about whether it's reliable for that topic, and that WP:RSP should say so. Do you think there's a consensus it's reliable?— S Marshall  T/ C 11:08, 14 July 2024 (UTC)
    Even if all well-established broadsheet newspapers are presumed to be generally reliable until found otherwise, this requires that there be some mechanism by which such newspapers can be found otherwise (otherwise we would be saying they are always generally reliable regardless of any evidence to the contrary). That mechanism is a discussion at RSN, and this RFC was an example of such a discussion. It follows that it must be possible for that discussion to find that a well-established broadsheet newspaper is something other than generally reliable, either for all topics or for some subset of topics. Whether this discussion did establish that is the point of this discussion. Additionally, the reliability of a source can change over time - just because the Telegraph has a long history of being regarded as reliable does not imply anything about whether it is or is not reliable today. Thryduulf ( talk) 11:34, 14 July 2024 (UTC)
    I am going to strike my !vote, since it appears that it might actually be unitelligible. I was not asserting that the newspaper was reliable on this topic, a matter on which I have no personal opinion. All that I objected to was to was certain reasoning and wording used in the closing statement and by the closer to produce a particular outcome. I did not mean to express any opinion on the outcome itself. James500 ( talk) 11:55, 14 July 2024 (UTC)
    I don't think it was unintelligible. The close mispresents consensus. For example, the close says that the Telegraph embraced the hoax. In reality, there is at least no consensus that the Telegraph embraced the hoax, and a lengthy argument about whether it did. This on its own is a perfectly reasonable and widely shared opinion that argues for overturn, before any weighing of the second part of your comment.
    Your opinion about the relative weight of the status quo in the presumption of reliability in established news organisations should not have been read by anyone as an argument that the Telegraph was reliable. I think it was an important response, especially that you pointed out that no consensus is capable of meaning "no consensus to change the text of the RSP". It was certainly my understanding of the RfC, and the way that I framed my contribution to it, that the question was whether the evidence presented merited downgrading the Telegraph, and that positive arguments for its reliability were assumed. I'm sure some editors would have put those arguments had the discussion been framed in the way that some people in this review now interpret it. Samuelshraga ( talk) 14:27, 14 July 2024 (UTC)
    The question was "What is the reliability of the Telegraph on trans issues?". If the outcome of that discussion is "no consensus", how can an RSP entry saying "Editors show consensus that the source is reliable in most cases" on trans issues be accurate or appropriate? This is a genuine question - I am trying to understand the arguments for that position because I currently do not. Thryduulf ( talk) 16:51, 14 July 2024 (UTC)
    The RSN RFC question was exceedingly clear, and is the standard question for RSN RFCs: What is the reliability of the Telegraph on trans issues? The questions was not "should it be downgraded," or "should the RSP entry be changed", in which case, one could argue that no-consensus means no change. But since the question was "What is the reliability?" with the standard 4 options, no consensus on the reliability means Option 2, at least in my view. And that's true for all RSN "What is the reliability?" 4-question RFCs. Levivich ( talk) 19:16, 14 July 2024 (UTC)
    I didn't think it was unintelligible either; seemed well-reasoned to me. Levivich ( talk) 19:13, 14 July 2024 (UTC)

Participants

  • Support close. So, technically speaking, the Telegraph may have "only" supported a clearly false assertion that is very similar to the litter boxes in schools hoax, depending on how narrowly you read that page. However, IMO this is a nitpick. In practice what they said has all the important elements of the litter boxes in schools hoax: the important bit is that they claim a school officially supported students identifying as animals, and not the literal litter box part. If you object to the wording at WP:RSP, then edit that. Loki ( talk) 05:05, 9 July 2024 (UTC)
    I object to the wording of the part of the close quoted at RSP. As long as the quoted content remains part of the close, I'm pretty sure arguments for removing it are unlikely the gain ground.
    Regardless of whether the hoax includes the situation in the articles mentioned, casual readers are likely to misinterpret what the misrepresentation is at first glance, which is something a summary should avoid. This "nitpick" has been raised at the closer's talk page and he has refused to change this wording. Aaron Liu ( talk) 05:10, 9 July 2024 (UTC)
    As was clearly and prominently refuted during the discussion, the Telegraph did not claim a school officially supported students identifying as animals. They reported, as a reliable source is allowed to, that the parents of a suspended student claimed that the school was doing that, and citing that belief to the parents themselves. -bɜ:ʳkənhɪmez ( User/ say hi!) 05:30, 9 July 2024 (UTC)
    If you think that was refuted at all, much less clearly, you're wrong. In fact I personally think you're lying, since it very clearly wasn't. Loki ( talk) 14:06, 9 July 2024 (UTC)
    It very clearly was, based on the relative amount of “legitimate” !votes for 1/3/4 after it was (legitimate meaning not based on “it’s biased” or “I don’t like it”), and for you to accuse me of lying shows a massive lack of AGF. -bɜ:ʳkənhɪmez ( User/ say hi!) 14:19, 9 July 2024 (UTC)
    It should be pretty clear that you can't just count votes to decide on a factual claim. Many people weren't convinced by my argument as a whole, but also many were, including several who were specifically convinced by the Rye College thing. Conversely many Option 1 voters, like the closer noted, waved off the Rye College articles as a single mistake without denying they were false. Loki ( talk) 14:23, 9 July 2024 (UTC)
    Yet significantly more people were either not convinced by your claims in the first place, or - and this is the important part - were convinced by the refutations. The mere fact that a relatively small proportion of editors claimed to still be convinced by your evidence does not change the fact that there can be consensus on reliability. If 10% of editors think it’s unreliable, but 90% were happy with the refutation, then it’s laughable to suggest it should be listed as “unclear” - that would be one of the clearest consensuses possible. Yet the closer didn’t even attempt to evaluate how the discussion evolved or the relative strength of the arguments. -bɜ:ʳkənhɪmez ( User/ say hi!) 14:29, 9 July 2024 (UTC)
    I've just re-read every bolded "Option 1" !vote, and and while I may have missed something I can't see any who waved off the Rye College articles as a single mistake without denying they were false. If I did miss something, can you link the !votes? BilledMammal ( talk) 14:35, 9 July 2024 (UTC)
    For the record, I also do not think that S Marshall is INVOLVED based off personal experience closing an RFC while having previously participated in an RFC in the topic area, and having that firmly upheld on close review. Loki ( talk) 14:08, 9 July 2024 (UTC)
  • Overturn, and reclose. The closer did not take into account, or at a minimum failed to explain how they took into account, the number of !votes (primarily on the "unreliable/deprecate" side, but also a few on the reliable side) that were based solely on "I don't like it" or "it's biased thus by default unreliable" standpoints. That fact alone should merit overturning the close, since the closer did not take the strength of those arguments into account and down-weight them accordingly. However, the closer also admits on their talk page that they basically supervoted. They didn't assess the community's belief, and especially Chess's refutation, of the claims regarding the "cat" hoax/"litterbox" hoax. They assessed, without explaining how they felt the community came to that consensus, that it was blatant misinformation, and they based their close in large part on the fact that, since the source published information about that, all arguments for unreliability must be accurate. In fact, Chess and other users (including myself), refuted the fact that it was a "hoax" published by the Telegraph - the Telegraph published what others were saying about it, and cited their sources accordingly when they did report the views/opinions of others. However, the closer did not take into account any of these arguments made. Lastly, there was a clear turn of the discussion after Chess and others discussed and refuted the claims at length during the discussion. Before Chess's comments and the ensuing discussions, there were people claiming that the evidence presented at the start was grounds for unreliability on its own. Many of these people admitted that Chess's refutation was valid, and that their arguments were much less strong. But even more damning for this close, after Chess's refutations and the ensuing discussions had been discussed, there were virtually no !votes for unreliable/deprecate that were actually based on the evidence presented at the beginning. The vast majority, if not all, of the !votes after the discussions were based on the improper arguments such as "I don't like it" or "It's biased thus unreliable", which were not properly weighted by the closer. Ultimately, I thank the closer for making an attempt, but it is clear that the close failed in three primary ways: It did not evaluate the strength of the arguments, it did not evaluate the "turn of the tide" after the opening arguments were largely refuted, and the closer injected their personal opinion as to the "cat/litterbox" hoax into their evaluation. For these reasons, the close should be overturned. -bɜ:ʳkənhɪmez ( User/ say hi!) 05:27, 9 July 2024 (UTC)
  • Overturn. The close is not close to a faithful conclusion of the discussion. The issues with this close are in the third and fourth paragraphs. In the third, the close takes as a fact The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax. Any reading whatsoever of the discussion will show that the idea that the Telegraph promoted some version of the litterbox hoax is contested, with many editors subscribing to refutations of this point.
    The next paragraph goes on to assert that On trans issues, Wikipedians simply do not have this level of confidence in the Daily Telegraph. The only argument referenced to this point has been the litterbox one. Editors who took issue with the third paragraph therefore found the fourth, which finds that reliability is disputed, to be invalid. However, the closer clarifies on talk that Fourth paragraph is independent of the third.
    The assessment that reliability is disputed was therefore not given any justification in the close itself, so closer expanded the close. The expansion provides but one reason why to give weight to the argument that the Telegraph is not generally reliable on trans issues: Although some members of the community have confidence that the Daily Telegraph is reliable on trans issues, this view is strongly disputed by significant numbers. In other words, closer is counting votes. Except closer tells me on talk that the point is not to count votes, and I didn't, but to weigh arguments, which I did.
    Closer has shown no evidence of weighing arguments (except in the case of the litterbox hoax claim, in which closer showed no evidence of weighing arguments fairly). Closer claims both not to have counted votes, but also bases their close of "Reliability disputed" on the claim that the view that the Telegraph is reliable "is strongly disputed by significant numbers". If closer is not willing to revert, close should be overturned as closer won't give a consistent account of what the reason is for the close. Samuelshraga ( talk) 06:51, 9 July 2024 (UTC)
  • Support close because I think it's a perfectly reasonable close despite me thinking very negatively of The Telegraph. My emotions want it deprecated, but I know that this is the best we can get. LilianaUwU ( talk / contributions) 07:36, 9 July 2024 (UTC)
    Seraphimblade, you can't reopen the discussion when it's still at AN... I would say the same if I wanted it overturned. LilianaUwU ( talk / contributions) 11:48, 9 July 2024 (UTC)
    Oh, and that's misuse of rollback. LilianaUwU ( talk / contributions) 12:21, 9 July 2024 (UTC)
  • Support close, but what the hell is (The Telegraph) is a willing warrior in the war on wokery. It gives platform to the most flagrantly gender-critical tracts by anti-woke activists. I'm not sure what "woke" is being used as a synonym for here, but there are better words for the Telegraphs "anti-woke activists". They are called transphobes. Most of them even call themselves "gender-critical", which is the same thing. Also, radical feminists like Julie Bindel are not "anti-woke". Black Kite (talk) 10:18, 9 July 2024 (UTC)
    I don't see gender-critical and transphobic as 100% synonymous although Julie Bindel certainly qualifies as both. I specifically wanted to say that the Telegraph is activist on this issue.— S Marshall  T/ C 10:23, 9 July 2024 (UTC)
  • Overturn - first I would like to thank S Marshall for their effort in closing such a large RfC, as they have done so many times before. Unfortunately despite that, I share the concerns of Berchanhimez and Samuelshraga particularly regarding the litterbox issue, it was far more disputed by editors than what the original and extended closures portrayed. Since this was a significant and prominent part of the close, that causes the entire closure to fall into doubt. starship .paint ( RUN) 12:12, 9 July 2024 (UTC)
  • Kind of overturn I agree with the closing in that when we have such a clear 1 or 3 split we can't just say no consensus so no change. Certainly such a gap means on this topic we need to use caution. I also agree that the closing was not a summary of the arguments and for that reason the closing statement either needs to be changed to align with a true summary of the discussion or another editor should close the discussion. That the source was biased seemed to have consensus but how much did not have a consensus. The closing suggests there was agreement on how biased the source was. I also agree that some of the language used in that part of the closing appeared to be expressing an opinion rather than summarizing the discussion. Since much of the discussion centered on the litter box hoax it is important to get that part of the close correct. I think all would agree that there was a clear dispute regarding if the source was just reporting or if they were embracing. As such the claim that the statement, "The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax" is clearly inaccurate. I don't have a strong view on the involved claim but I'm not sure I view that as disqualifying in this case. Springee ( talk) 12:19, 9 July 2024 (UTC)
  • Overturn
    The close expansion includes: Towards the end of this, the "generally reliable" camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes, which I receive as a concession that the article is misleading. I don’t see this in the discussion.
    Also, there is no mention of the general disparity between those who supported Option 1, who generally discussed the question of whether the Telegraph is reliable on transgender matters - which is what the RfC was supposed to be about - and those who supported Option 3, who mostly said we should not use the Telegraph on transgender matters because it is biased – which is not what the RfC was supposed to be about.
    On the contrary, the closing comment summarises the attitude of those who preferred Option 3, It is a willing warrior in the war on wokery. It gives platform to the most flagrantly gender-critical tracts by anti-woke activists.without making the obvious conclusion that such views are irrelevant to an RfC on reliability. Sweet6970 ( talk) 12:39, 9 July 2024 (UTC)
  • Overturn, the weighting and evaluation of the arguments was done poorly, and the tone of the original close leaves much to be desired. Unfortunately, some of the summaries of the arguments (like the cat story) was either done poorly, or added onto through the closers own arguments trending towards a supervote. Lastly, whether or not the closer is clearly involved, there is definitely a strong appearance of involvement, which is enough IMO. FortunateSons ( talk) 12:56, 9 July 2024 (UTC)
  • Support closer, oppose close. It's a real stretch to accuse S Marshall of being involved for having an opinion on a related matter (or even on this matter). We're not robots nor should we pretend to be - and I have previously seen S Marshall demonstrate high competence in separating personal views from the principles at hand in a discussion. However, I do agree that the close rationale erred in endorsing a point that had been thoroughly rebutted in the discussion, and in taking a bold interpretation of WP:ONUS. It is not clear to me that the policy on onus with respect to article content should automatically apply to discussions of general reliability. This is a point that could potentially be argued in the abstract, but in this specific case, when our starting point is a previous RfC finding general reliability, then the onus should very much be on bringing new evidence, and the focus of the close should be on whether or not that evidence has been successfully rebutted - not on whether there was a dispute. If there's no consensus that the new charges are valid, then they should be considered unproven, and the status quo should remain. Proving unreliability should be hard, as a countermeasure to the chilling effect of a downgrade. Barnards.tar.gz ( talk) 12:58, 9 July 2024 (UTC)
  • Overturn. The closer was WP:INVOLVED with respect to The Telegraph's reliability in the context of political topics, as their comment from April 2024 shows. And the sort of involvement does somewhat show in the close; the close does not faithfully represent the consensus attained on key points, and it doesn't appear to attempt to summarize what the arguments on each side were. Instead, the close reads much more as if it were a !vote in the RfC, where the closer inserts his own analysis of the source (It is a willing warrior in the war on wokery) and appears to give definitive weight to one questionable interpretation of The Telegraph's reporting (unashamed embrace of the widely-debunked Litter boxes in schools hoax) as if it were to have reflected the broad consensus of the discussion.
    Because the closure should represent the discussion faithfully, and this closing summary is more of an argument than an attempt to do so, it should be overturned. — Red-tailed hawk  (nest) 13:56, 9 July 2024 (UTC)
  • SMarshall was not INVOLVED. I'm not going to express an opinion about the close as a whole as I fear I would fail to avoid the relitigation that multiple editors here are doing) but I see absolutely no evidence that SMarshall was INVOLVED within the meaning of that policy and so that allegation should not be factored into the assessment of the close. Thryduulf ( talk) 14:38, 9 July 2024 (UTC)
  • Overturn - the finding that there was no consensus the Telegraph is not reliable, but the source should still be considered "not generally reliable" (in some unspecified way) is unreasonable. It is probably better to vacate it entirely rather than modify it to a pure "no consensus" close. Walsh90210 ( talk) 15:47, 9 July 2024 (UTC)
    No consensus (MREL) also means "not generally reliable" (GREL). It does not mean "generally unreliable" (GUNREL). Everything that isn't GREL is not generally reliable to put it simply, such as a "pure no consensus close". CNC ( talk) 15:53, 9 July 2024 (UTC)
    That's just how WP:RSP works. The normal rule of no consensus = no change doesn't apply. Instead "no consensus" is a status, and it's WP:MREL. Loki ( talk) 16:33, 9 July 2024 (UTC)
    This is ridiculous. If there is "consensus for no consensus" that is one thing, but a "no consensus at all so a specific change must happen" is a supervote. Walsh90210 ( talk) 18:26, 9 July 2024 (UTC)
    You might think it's ridiculous but that's how RSP works. "Generally reliable" is defined to mean "there is a consensus that this source is generally reliable". There is a specific category for sources about which there is no consensus. Thryduulf ( talk) 18:32, 9 July 2024 (UTC)
    I think we're at the point of " beating a dead horse". I've asked below in the clarity section on whether this RfC should be an exception to the status quo, or whether RSP should be changed, and if so whether it should be retrospectively; but so far there are no proposals. Any closer of this discussion is surely aware of how RSP operates by now. CNC ( talk) 18:39, 9 July 2024 (UTC)
  • Support close to prevent time-wasting: I supported option 3 but find the close a clear reading of the discussion. While it's not a vote count, we should be on the same page about the trend of the discussion. By a quick count: ~55 editors said option 1 (with many arguing it was biased but not enough to effect reliability), ~8 supported option 2, ~50 said option 3/4, ~8 said 1/2, and ~4 said 2/3. That leaves us with a clear majority in favor of "there are issues with calling this straight up reliable" (~8070(fixed per starship) v ~55, with, as I noted, many in the latter camp acknowledging it does have a GC slant). Editors presented RS that supported the claims of bias as well. When such a large outpouring of editors have significant concerns regarding a source's reliability, that must be reflected in the close - there was no earthly way this could have been closed with "the community agrees this is reliable on trans topics". WRT claims that those questioning it's reliability did so on WP:IDLI grounds - editors considered platforming anti-trans activists and talking points in every article a clear sign of unreliability/bias just as if their editorial line was obviously pro-flat earth or pro-race realism (please note that regardless of your opinions on whether the GC movement is correct or not, RS do overwhelmingly say it's a hate-based movement supportive of disinformation). Your Friendly Neighborhood Sociologist ⚧ Ⓐ ( talk) 15:59, 9 July 2024 (UTC)
    • Addition error. 70 per your numbers. Not 80. starship .paint ( RUN) 16:26, 9 July 2024 (UTC)
    • P.S. Everyone should disclose how they voted Your Friendly Neighborhood Sociologist ⚧ Ⓐ ( talk) 15:59, 9 July 2024 (UTC)
      I simply don't see how you think counting votes is an argument in support of a close, especially when the closer's only justification is that they counted votes. (Leaving aside the fact that counting 1/2 !votes as against calling it WP:GREL is a stretch. Those votes explicitly support calling it generally reliable, and are broadly saying they would accept/support adding a note in RSP, not downgrading the source. I conclude this by actually reading those comments, rather than counting them.) Samuelshraga ( talk) 18:02, 9 July 2024 (UTC)
    • Could you address the reasons we, or at least I, brought up the close review? Aaron Liu ( talk) 18:18, 9 July 2024 (UTC)
      Gladly: to start, please take my comment in the context that the close review grew beyond your point.
      • Regarding the "overturn whole close": I do not believe the closer was involved (which would, in my view, entail either participating in the discussion or being generally active in GENSEX). I do not believe he misread the discussion in finding MREL.
      • Regarding your specific note on the litter box hoax: I actually agree with you it could have been better (though on procedural grounds I think it was fine and this 2 pronged close review is wasteful of editor labor). Being more specific:
        • The litterboxes were extensively discussed and would inevitably have been mentioned in the close. An uninvolved editor weighed up the arguments on both sides, and believed that the "hoax promotion" had better ones - but it could have been the other way or more equivocal and still be a valid close imo. To be clear, I think The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax is discussed could have been better phrased as Whether the Telegraph embraced the widely-debunked ...
        • That being said, I think it should have been a more general statement on misinformation: misrepresenting the Cass Review, incorrect statements on "desistance", use of meaningless scarewords like "gender ideology" or "trans agenda" in its voice, and etc. Particularly, as many noted, platforming FRINGE groups to make false statements on issues while portraying them as experts and disregarding more mainstream ones.
          • Sidenote to that, I disagreed with the extended close's statement about its historic homophobia and advocacy for conversion therapy (neither of which is the paper's current editorial position). - They no longer support LGB conversion therapy, but its blatant in practically every article that they support it for trans people, and I would further argue that their repeated framing of issues as LGB v T, as if they're mutually exclusive, is homophobic in itself.
      Your Friendly Neighborhood Sociologist ⚧ Ⓐ ( talk) 20:53, 9 July 2024 (UTC)
      To your point on the "litterbox hoax" and their reporting on it, your recommended alternative sentence starting with "whether" changes the meaning completely. SM's close referred explicitly to the fact that many people "believed" they "embraced" the hoax, and did not address the fact that, aside from those whose !votes were based on their opinions on the underlying subject as a whole, the majority of editors did not see it as being reported as truthful in the reporting - and in fact a reading of the articles in question confirms that they are right to not see it that way. If editors base their !votes on "facts" that are disproven, whether before or after their !vote, then their !vote needs to be weighted down accordingly - not given full/extra weight as SM did. -bɜ:ʳkənhɪmez ( User/ say hi!) 21:08, 9 July 2024 (UTC)
      This seems to be a bit of a point of dispute in these discussions. I think some of the endorse editors look at the yellow rating and reasonably say, "with arguments on both sides and a clear 1 vs 3 division yellow is the only reasonable outcome." I can get behind that. However, I also agree with editors who note that there were clear errors in the summary of the arguments. I don't see how a reasonable close could state as fact that the source embraced the litter box hoax. That was a clear point of contention and if neither side convinced the other then we shouldn't treat it as some sort of consensus outcome. When doing a closing it's not just that the color needs to be right, the summaries need to be accurate as well. We don't have that here. At minimum editing the summary to reflect the actual state of the discussion is warranted. Personally, I think having a new closing is better. Springee ( talk) 21:16, 9 July 2024 (UTC)
  • Overturn. Two distinct issues here:
    1. Imbalance and inaccuracy in the summary. Rather than fairly sum up both sides of the discussion, the close is weighted towards the unreliability perspective to an extent that does not reflect the genuine course of discussion. Vigorously contested assertions (e.g. the notion of The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax) are treated as fact. At times S Marshall appears to be carrying on the argument in his own close (e.g. Towards the end of this, the "generally reliable" camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes, which I receive as a concession that the article is misleading. And if the Telegraph has published a correction, then the "generally reliable" camp hasn't unearthed it.)
    2. The, um, let's call it "novel" interpretation of ONUS such that a supposedly "no consensus" close somehow ends up in effect a consensus to downgrade? I don't have much to add to what Barnards has already said: (1) ONUS is geared towards discussions about whether to include specific things like an image or a certain paragraph in an article, not broad discussions about the reliability of a source; and (2) there's an existing RfC finding consensus for general reliability, so that should be the assumed baseline we're working from.
  • S Marshall made an odd comment about the decision to adopt this interpretation: In doing this, I removed the first mover advantage that the "generally reliable" side expected and I think relied on. The part about editors advocating for reliability "relying on" a supposed first-mover advantage comes across to me as if he is taking the view these editors are abusing or at least leaning on procedure to get a preferred result. This does not seem to be a fair characterisation to me.
  • I don't see how S Marshall is INVOLVED, though. – Tera tix 16:26, 9 July 2024 (UTC)
  • Support close. It was a very reasoned, balanced close. I would have preferred a "generally unreliable" close, but I accept that S Marshall made a good faith effort to close this RfC in a balanced and impartial manner. -- Amanda A. Brant ( talk) 17:39, 9 July 2024 (UTC)
  • Overturn, and reclose per Berchanhimez. S. Marshall deserves some credit for stepping in where angels fear to tread, but a no-consensus outcome doesn't justify changes to the status quo. *Dan T.* ( talk) 17:56, 9 July 2024 (UTC)
    It explicitly does at WP:RSP, and in fact "no consensus" is part of the definition of WP:MREL. Loki ( talk) 19:48, 9 July 2024 (UTC)
    Let's leave it for Part 2 to deal with. CNC ( talk) 20:04, 9 July 2024 (UTC)
  • Endorse close and this relentless badgering of closers when a consensus doesn't go someone's way needs to stop. I've seen it a lot in the last year and if it's not stamped down on it's going to be next to impossible to find anyone to volunteer to close anything but the most obvious community discussion. Daveosaurus ( talk) 18:21, 9 July 2024 (UTC)
  • Endorse close. It accurately reflects the discussion and the state of consensus (or lack thereof) on the topic; and the arguments it mentions are summarizing ones from the discussion, not new ones presented by the closer. The WP:QUO / WP:ONUS argument doesn't make sense to me - those policies are for article space, where we have no choice but to decide on one version even when we lack consensus. RSP isn't an article, it's a summary documenting where the community stands on specific sources; a lack of consensus can and should be documented there. No-consensus outcomes get lodged there as a matter of course; AFAIK that's how it has always worked. It would be misleading to do otherwise and would lead to disputes where people attempt to rely heavily on a source only to face conflicts and be told that there's no consensus on it. There is an entire category for no-consensus outcomes on RSP, and numerous entries on the table that use that specifically in their language; it makes no sense to not use that here. -- Aquillion ( talk) 19:25, 9 July 2024 (UTC)
    Summarizing a minority opinion that was strongly refuted, and the refutation of which was agreed with by a majority of editors commenting after the refutation, does not a no consensus finding make. Even if you believe that SM was not imposing their own opinion on the closure, the summary of the opinions presented and their relative strength was insufficient as it did not take into account the "turn of the tide" in !votes after the refutation, and in fact it tries to claim that after the refutation the reliable camp's arguments got worse - the exact opposite of what happened. -bɜ:ʳkənhɪmez ( User/ say hi!) 21:05, 9 July 2024 (UTC)
  • endorse close. I think the language used could have appeared to be more neutral, but it is clear that there is no consensus on the telegraphs reliability on this topic. That some people seem to think consensus is needed to confirm there is no consensus seems nonsensical, unless we all do a close that could never be decided. I don't think the close is perfect but it's certainly good enough and every editor involved could probably be more useful spending time elsewhere. For transparency's sake I voted option 3 on the RFC and was deemed a SPA. LunaHasArrived ( talk) 21:02, 9 July 2024 (UTC)
  • Overturn The assumption that people saying that mistakes happen were conceding that the specific example brought up was actually a mistake was not supported. That leaves a fundamentally damaged evaluation of the wider consensus as to whether there were mistakes in this area, which is a key aspect of changing the assumed reliability of this source. The result is an artificially strong consensus not supported by the arguments. CoffeeCrumbs ( talk) 22:58, 9 July 2024 (UTC)
  • Overturn. The only policy-based reason S Marshall's close was based on is whether or not The Daily Telegraph endorsed the Litter boxes in schools hoax. The conclusion S Marshall reached is that The Telegraph's unashamed embrace of the widely-debunked Litter boxes in schools hoax is discussed at great length. This is a WP:SUPERVOTE because it sides with Loki's original claim without any explanation. One of the central disputes of the RfC was whether or not the "Litter boxes in schools hoax" encompassed a student merely identifying as a cat, which is the falsehood The Telegraph supposedly said. The assumption that these were equivalent made it impossible to reach any other conclusion than Option 2 or 3, which I will show below.
    S Marshall's only mention of specific Option 1 arguments is that the "generally reliable" camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes, which I receive as a concession that the article is misleading. This misses the point, which is that The Telegraph promoting a blatant hoax is not equivalent to getting a detail in a story wrong. S Marshall did not address this in this point in their close because of the aforementioned SUPERVOTE, which assumed equivalence between kids using litter boxes and kids identifying as cats. If the equivalence was treated as a disputed point, the concession that the article is misleading matters much less, since it is no longer a concession that The Telegraph promoted a blatant hoax.
    Closers are also supposed to disregard votes not based on policy per WP:DISCARD, and not judge on headcount. S Marshall's close does not obey this. Consensus is not determined by counting heads or counting votes, but S Marshall says Although some members of the community have confidence that the Daily Telegraph is reliable on trans issues, this view is strongly disputed by significant numbers. as an explanation of their decision. [14] The close also makes references to the controversy over homophobia, transgender breast milk, and other factors, but does not explain how those subpoints helped reach a decision. If the closer does not analyze a point I will assume it did not play a part in the decision.
    To summarize, the close began by assuming that Option 3 was correct on the most significant part of the discussion, and then judged the entire rest of the RfC on those grounds. This assumption should not have been made and a proper close would fairly summarize the dispute over whether implying a student identified as a cat is equivalent to saying students are using litter boxes in schools. Chess ( talk) (please mention me on reply) 00:21, 10 July 2024 (UTC)
    It's actually worse, as S Marshall claims that the close is not based on the finding on whether the Daily Telegraph embraced the litterbox hoax. So there was no policy-based reason for the close. Samuelshraga ( talk) 15:55, 10 July 2024 (UTC)
  • Overturn close. It is clear from this edit [15] that the closer had a POV that should have been declared. Xxanthippe ( talk) 02:51, 10 July 2024 (UTC).
    The community has already found in a similar situation that voting in an RFC in the topic area does not make a closer WP:INVOLVED. Loki ( talk) 03:03, 10 July 2024 (UTC)
    This isn't just two discussions in the same topic area; it's two discussions about the reliability of the same source. BilledMammal ( talk) 03:09, 10 July 2024 (UTC)
    Yes, and in the previous situation I had !voted in an RFC whose result was directly relevant to the close. However, the community very clearly endorsed the close and overwhelmingly said I was not WP:INVOLVED.
    The thing you're missing here is that WP:INVOLVED is not about bias or opinion. It's closer to WP:COI: the point is that you cannot close a discussion that you participated in. But having an opinion on the discussion doesn't matter, that doesn't make you involved at all.
    In general, Wikipedia policies don't prevent an editor from doing something due to having expressed an opinion on that topic. Instead, they prevent editors from doing things because of concrete relationships with discussions or topic areas: you can't cite your own research and you can't close a discussion you !voted in, regardless of what you think of it. This is also the case over at the perennial WikiProject dispute where community consensus soundly rejected your interpretation, which I bring up to make the point that you appear to have similar misinterpretations of Wikipedia policy in multiple areas. Loki ( talk) 03:59, 10 July 2024 (UTC)
    There's situations where there's only one correct POV. This is one of them. LilianaUwU ( talk / contributions) 19:35, 10 July 2024 (UTC)
    Whatever the criticisms of the body of the closure may be, and there seem to be some, the closure is tainted because the closer did not declare a POV (whether that POV was "correct" or not). Xxanthippe ( talk) 04:42, 13 July 2024 (UTC).
  • Overturn (Option 5, but I would be happy with 2 too). Reading the original discussion, I thought that the accusations about inaccurate reporting of "litter boxes in schools" had been well argued against. In their initial statement, the closer appears not to consider these arguments, but simply labels the Telegraph's statements as misrepresentations. At the least the closer should have addressed these prominent arguments and explained why they did not agree with them. This implies to me an insufficiently in-depth analysis. The closer's revised statement says a little more on this topic, but I was shocked that the decisive step of their reasoning is an obvious non-sequitor: "The 'generally reliable' camp is reduced to a bold-face statement that reliable sources are allowed to make mistakes, which I receive as a concession that the article is misleading." This seems almost flippant; Wikipedia should be able to do better than this in analysing the evidence and arguments. JMCHutchinson ( talk) 10:07, 10 July 2024 (UTC)
  • Endorse and overturn (I did 'participate' in the RFC although I didn't comment on the reliability of the Telegraph in this RFC, but I did comment on a previous RFC that the Telegraph was unreliable on this specific issue). The close that 'there is no consensus on the reliability of the Telegraph on transgender issue' (or WP:MREL), is IMO the correct reading of the discussion (so I endorse it). However, with apologies to an editor I respect, I do think the reasoning in getting there is flawed. The close doesn't engage with all the arguments and rebuttals in the discussion, dissatisfaction with which has lead to this review (not helped with how the RSP was updated). Given this is now the third RFC on the matter in a short space of time, a close that satisfies all involved (even if it doesn't agree with them) is sorely needed. I do wonder if the RSP had simply been updated with the plain "In regards to transgender issues the reliability of The Daily Telegraph is disputed.", without the additional details then we wouldn't be here. -- LCU ActivelyDisinterested « @» ° ∆t° 11:00, 10 July 2024 (UTC)
  • Overturn. I appreciate the sincere attempt on such a divided issue, but I believe that such a contentious non-consensus warranted a more conservative close, both in resolution and in wording.
    As others have noted, the close turned largely on one story, the notorious "cat" drama. That the closer refers to a story that categorically was not a "widely debunked litterbox hoax" in such terms does not inspire confidence that the arguments have been properly weighed. A story featuring elements of otherkin in schools is not automatically a "litterbox hoax". The incident in question happened, and absolutely nobody denies that. The school acknowledged it and reviewed its processes in the aftermath. I wrote out a transcript of the recording here for anyone still for some reason curious about this debacle. I won't rehash the arguments yet again but I don't think any fair weighting of the refutations can support a close describing this as a "debunked litterbox hoax" when there has been no hoax, no litterbox, and no debunking.
    As for the specific wording, as I raised on talk, the closer needlessly inserted the text "and gender critical views" into the closing statement, widening the unreliability notice beyond what was suggested. This was not part of the original RFC, and no evidence was presented either way as to the reliability of The Telegraph for "gender critical views".
    Editors may have personal opinions on how separable "gender critical views" are from trans issues or what the closer even means by "gender critical views", but that is a discussion in an of itself, and one which simply did not take place and whose outcome should not be assumed like this. This unsolicited addition is unwise in an already polarised RFC, and if this is overturned I would suggest a future closer stick to the wording of the RFC only and leave this particular can of worms unopened. Void if removed ( talk) 11:51, 10 July 2024 (UTC)

Support overall close because of what it isn't Overturn....needs another look per my post lower down Folks, let's look at what the structural result of the overall close is, which I think many folks have missed. It is "no consensus on trans issues" and "generally reliable on non-trans issues" I can't see people arguing for a close other than this. The "embrace of the cat story" statement should not be in there but that really doesn't change anything. And it probably needs a shorter more direct summary such as I just gave. If they were an admin, SMarshall would be in the top 5% of admins regarding knowledge and expertise to close this type of thing, so NAC is not an issue except maybe for the optics of it. North8000 ( talk) 18:49, 10 July 2024 (UTC)

Arguing that the close is fine because while it misrepresents the discussion, it gets you the answer you want is ... refreshingly direct, though sadly not unique here. If you can't see people arguing for a close other than this, you might read this comment above. Not to mention many of the other comments supporting overturn. Are we not people? Or can you just not see us? Samuelshraga ( talk) 19:05, 10 July 2024 (UTC)
I encourage you to review the problems many of us have with this close. Similar to how an RfA that (pre-recent-changes to RfA) had a significant early support but was then followed by a “bombshell” that caused a turn of the tide, this discussion was started based on inaccurate representations of the source, which I will assume was not Loki’s intent. This was not called out immediately, and many people !voted while discussion of the initial claims was continuing. But a clear consensus emerged that the initial claims of misinformation were, to put it bluntly, wrong. They claimed the Telegraph said in their own voice things they didn’t, they claimed the Telegraph didn’t retract what other people had said and it merely reported on. And that refutation was widely accepted by a clear majority of editors who posted substantive comments after it was done.
That is why people are believing there was a consensus here - after properly considering how to weight the !votes that were based on the initial inaccurate information, and/or solely based on their personal opinion whether they like the source or not, or of if the source is “biased” or not. -bɜ:ʳkənhɪmez ( User/ say hi!) 20:16, 10 July 2024 (UTC)
@ Samuelshraga: @ Berchanhimez: I'd be happy to take a deeper dive on this and revisit but would like clarity on what I think you are saying that the correct close should have been. Is it that there was (simply) a consensus that they are a generally reliable source? (without the separate wording for trans issues) Sincerely, North8000 ( talk) 20:47, 10 July 2024 (UTC)
My personal reading of it, which I accept is not necessarily in line with what others may read, is that yes - those !voting for option 3/4, and many (but not necessarily most) for option 2, did not care about the veracity of the claims in the initial filing by Loki, and took them at face value. Very few of that group as a whole either provided clear arguments as to why the refutation by Chess and others should be discounted, and many of them admitted that their arguments fell apart once the refutations started coming through. Further, the “turn of the tide” to significantly more option 1 votes, and significantly more (if not all) votes for option 3/4 being based solely on bias or flat out lies, I believe that this all comes together to lead to a consensus that the source is, by our own policies, biased but generally reliable, even on the subject of transgender issues. -bɜ:ʳkənhɪmez ( User/ say hi!) 20:52, 10 July 2024 (UTC)
Ugh, wrong link there, it’s supposed to go to the page about bias of a source not generally affecting its reliability, but mobile. Hopefully you know where I’m talking about, will fix later when I’m home. -bɜ:ʳkənhɪmez ( User/ say hi!) 20:54, 10 July 2024 (UTC)
@ North8000, I'm probably one of the less experienced editors here. I didn't come because I felt I would have been competent to close myself (had I not been involved), but because the close we got was so clearly flawed. That said, I agree with Berchanhimez's reading of the discussion. Samuelshraga ( talk) 21:13, 10 July 2024 (UTC)
So the difference between your thoughts and the close which I supported is that the close said that there was no consensus on trans issues and your thought was that the result was that they are reliable on trans issues. (BTW my sentiment expressed at the RFC was that it should be #1, with #2 also being OK.) I took a harder look. IMO there was a plurality for #1 between #1 and #3 bordering on a consensus and if you include #2 sentiments regarding suitability to use on trans issues (a sort of "sufficiently reliable") then there would be a clear consensus for confirmed usability ("generally reliable") on trans issues. So now I think thhis sould get a second look. North8000 ( talk) 21:32, 10 July 2024 (UTC)
Yes, that was my “rough count” too (remembering that it’s not a vote count). Combine that rough plurality for “reliable but biased” with the fact that the main arguments in favor of unreliability were contested and refuted and many editors agreed with the refutation, there is really no path to “no consensus” here. -bɜ:ʳkənhɪmez ( User/ say hi!) 23:53, 10 July 2024 (UTC)
The analysis that caused me to reverse my position is this: The operative results regarding trans issues were in essence: 1. Prohibit use on trans issues (RFC choice #'s 3 & 4) 2. (RFC choice #'s 1 & 2) Don't prohibit use on trans issues. By this analysis (if arguments roughly follow head count) "don't prohibit" was overwhelmingly favored by a factor of 1.73 to 1.
No, those weren't the options. There were four options, three if you exclude 4 for being essentially impossible to implement. 1 != 2 != 3, and people who voted 2 should not be assumed to support 1. Indeed many of those people explicitly said they were voting 2 because they did not support 1. Loki ( talk) 17:26, 11 July 2024 (UTC)
  • Support close, this is a very tough debate to find any resolution for and I think that S Marshall's decision is a pretty fair and balanced choice. S Marshall highlighted the key aspect of the debate which is a general agreement on the bias of the Telegraph but a disagreement on how much that bias affects the paper's journalistic integrity. Saying that when dealing with the subject of trans people the Telegraph should be used carefully seems like a reasonable precaution. (I voted for option 2 on the basis that reviewing a number of the linked articles showed a fairly strong bias on the topic, my primary concerns being their deliberate misrepresentation and laundering of sources. If I was working on material related to the subject, I would want to cite more neutral and nuanced sources that had clarity and more journalistic integrity.) Gnisacc ( talk) 20:51, 10 July 2024 (UTC)
  • Overturn per JoeJShmo, The Wordsmith, Berchanhimez, Samuelshraga, Teratix, Chess, Void if removed, etc. The close is frankly an inadequate and inaccurate summary of the discussion. Others have already noted multiple issues with the "litterbox hoax" paragraph, which treats one side of a hotly disputed point as fact and proceeds from there. Almost no weight is given to the rebuttals, which disputed not only whether the Telegraph "embraced" the story, but whether the story was an instance of the hoax and whether it even was a hoax at all. I do not believe the original text supports the bizarre claim that these users were "reduced" to arguing that the Telegraph is "allowed to make mistakes". The next paragraph that summarizes the rest of the RfC is equally bizarre. It devotes no attention to the handful of journal articles which were held up multiple times as evidence of the Telegraph’s supposed "unreliability", but in actuality explored only the source’s bias. It highlights a single brief comment one user made about Julie Bindel (whose "platforming" as an opinion columnist would indicate bias, not reliability) but fails to mention more significant points of debate such as the Thoughtful Therapists issue, which was brought up in the RfC's opening statement and rebutted at length by multiple users. And it elides the well-reasoned rebuttals by simply saying that "there was discussion", while neglecting to evaluate the relative merits of those discussions. I do not have confidence that the close properly engaged with the strengths and weaknesses of the arguments being made on both sides. Rather, the close seems to treat the fact that the source's reliability was vociferously disputed as justification enough. Astaire ( talk) 21:59, 10 July 2024 (UTC)
  • Endorse - The close was a reasonable read of the discussion and came to a very narrow decision. All of the arguments for overturning focus entirely on process wonkery & nitpicking word choice in order to try and unravel the close by tugging on a loose thread. — The Hand That Feeds You: Bite 16:53, 11 July 2024 (UTC)
    I brought this here because the closer refused to amend his egregious word choice on his user talk page and insisted that he came to it after weighing all arguments. Aaron Liu ( talk) 03:19, 12 July 2024 (UTC)
    "egregious," please, let's not be hyperbolic. — The Hand That Feeds You: Bite 19:57, 12 July 2024 (UTC)
    Okay, so you think that unashamed embrace of the widely-debunked [conspiracy theory] in place of saying A teacher at Rye College, a state secondary in East Sussex, was recorded telling a pupil who refused to accept her classmate was a cat that she was despicable., of which all they got wrong was that the cat was a rhetorical device, the latter being consensus, is a mostly fair and accurate representation of the discussion. I do not see how one could arrive at that conclusion. Aaron Liu ( talk) 22:08, 12 July 2024 (UTC)
  • Endorse. Look, I'm not going to lose sleep over some minor changes to the wording per the OP's concerns, if that's the ultimate result here, but for my part, I think this was a mostly reasonable summary of the results of the discussion. Did I feel there was a bit of unnecessary color commentary with pointed observations about the source frame as objective facts? Yeah, I did get some twinges about that while reading the close, and I think it's worth S Marshal taking that into consideration in the future. But I rather suspect that, rather than this being a case of the closer trying to interject unnecessary personal perspective into the result, it was a conscious rhetorical method for acknowledging the understandable and unavoidable emotional subtext of the dispute. I get the feeling that S Marshal recognized that there was really only one way to close this discussion under existing policy and consensus of the discussion itself, but was uncomfortable doing so without paying some recognition to the circumstances under which some editors have come to dislike the source. So he called the spade for the spade in a way that would make the Telegraph skeptics at least marginally less likely to feel that their sentiments had been dismissed wholesale.
    But any caveats not withstanding, I think S Marshal did an adequate job with this close, given the complexity of the issues and the highly divisive nature of the discussion. Personally I would have been marginally more supportive of a straight "no consensus" result as opposed to "reliability disputed", but this a fraught area, and we have to start finding a way to come together on these issues (or at least reigning in the constant relitigation of habitual issues. In that light, I think we could have gotten a lot worse here. I understand the quibbles, and I came close to casting a different !vote here, but considering all factors, I don't think S Marshal's something-for-everyone approach here was arbitrary, unintentional, or ill-advised.
    Further, I think there's more to be gained by just embracing an overall reasonable close than by micromanaging every last sentence into a form that is most pleasing to the majority, even if I was a part of that majority and even if I feel that the result would be more ideal. For the benefit of procedural efficiency and community harmony, I think we need to start leaning back towards the traditional tendency of just letting the initial close stay, warts and all, so long as it does not obviously and massively misrepresent the actual consensus. I don't love every syllable of S Marshal's close, but I still think that it was a well-executed one made under difficult circumstances, in the final analysis, and I don't blame him for trying to pay some lip service to the concerns of the minority. SnowRise let's rap 19:40, 11 July 2024 (UTC)
  • Endorse: I don't want to spend too long saying things which have already been said, but I know in recent discussions and here some users have opined that anyone saying ~"I'd just be using the same rationale as X, let me just say 'per X'" should be discounted and people should be required to be repetitive, so with apologies to whichever panel of three admins has to close this discussion (to avoid it being challenged) for making it longer ¯\_(ツ)_/¯ : both the "involved" argument and the argument that the close was a supervote are unconvincing. The "involvement" is not only tangential (as amply discussed above), but in the other direction, so unless the implication is that another closer would've found outright consensus that the source was unreliable(?), the argument doesn't make sense. In turn, as many users have noted above, while closing this as either "option 1 because I know option 2 voters really meant option 1" or "option 3 because I know option 2 voters really meant option 3" (as some people want) would've been a supervote, "there was no consensus →means→ close as no consensus" is just reading the arguments (and "no consensus →means→ no consensus" is just following WP:MREL).
    It is unsurprising that much discussion here is relitigating the same points as the RFC, as if saying "actually they were never wrong, it was proven they were never wrong, by me saying they weren't wrong" several more times will make it true. Indeed, re the suggestions below about ways to align how closes should occur and be reacted to vs how closes are actually reacted to, and the issues with those suggestions (e.g.: mandating multiple people volunteer to find time to close discussions would mean discussions go unclosed for even longer, potentially until stale, wasting/filibustering the effort), the other obvious possibility is to write down in the guidelines that all closures are only "prospective, non-finalized" closures until sustained by an AN discussion where the participants relitigate positions a second time: while I'm not sure that would be the best option, it seems like it could be the easiest one to get people on board with because it's how we see many people already operate... -sche ( talk) 02:42, 12 July 2024 (UTC)
    If you say "per X" and X's original claims have been proven inaccurate/misleading, and you don't address that fact, then your !vote will be downweighted accordingly - just as the initial claims should be downweighted when a refutation that enjoys broad support from those actually discussing the topic (rather than drive by !voting) would. -bɜ:ʳkənhɪmez ( User/ say hi!) 00:38, 13 July 2024 (UTC)
  • Endorse close - As has now become clear after further discussion here, while some people had issue with some of the wording of the close, the ultimate outcome of it being a "no consensus" seems to be agreed upon here and is a good reading of the original discussion, since there simply was no consensus on the topic, so the close to no consensus and marking it MREL for transgender issues is the appropriate outcome. Raladic ( talk) 15:51, 12 July 2024 (UTC)
  • At least amend the third and fourth paragraphs to reflect the actual consensus. In cases where there are comparable numbers of good-faith !votes, finding in favor of either of them (or splitting the difference) should necessitate a close summary mentioning why a given argument did not prevail. The close should summarize the reasoning of any significant minority/non-plurality, but should also make it clear what the major arguments against that reasoning were and how they were weighted. In cases where the closer finds consensus that does not align with a non-trivial majority of good-faith !votes, it is particularly imperative they explain why arguments in the majority camp were downweighted.
    In this close, only a rationale of Option 3 !voters is presented at any length, and it is implied there was consensus agreement with this rationale. However, the close does not address the various refutations of that rationale that, necessarily, were strong and numerous enough to result in Option 3 not gaining consensus. This is especially problematic given that there was a solid majority against Option3/4. Even if we count every "Option 1/2" !vote toward Option 2 and count every "Option 2/3" and "Option 4" !vote towards Option 3, we still have roughly 60 Option 1 to 49 Option 3 (and ~16 Option 2). A more charitable accounting (for example, assigning any "Option 1 or maybe 2" !votes, like my own, to "Option 1") yields a more lopsided result, and splitting the options into 1/2 vs 3/4 reveals something approaching a 60% supermajority ~75 1/2 to 49 3/4 (and that's still counting all "2/3" !votes toward Option 3). Any finding against Option 1 should thus expand on why this wasn't enough for consensus (which could be perfectly reasonable if the strength of the !votes just wasn't there--but that still should be explained!), meanwhile any finding for Option 3 would absolutely need to demonstrate a very substantial imbalance in argument strength. JoelleJay ( talk) 00:50, 13 July 2024 (UTC)
    I agree that there was not consensus for Option 3, but the closer did not claim there was. Meanwhile, you've missed the obvious reason why there wasn't consensus for Option 1: by your own count, there were 60 Option 1 voters but 65 voters who were against it. Since there wasn't a consensus for any option, there was no consensus, which has special meaning at WP:RSP and isn't just "status quo wins". Loki ( talk) 05:27, 13 July 2024 (UTC)
    I’m interested, since you seem to want to vote count, for you to do a few things. First, split the proportion up into “before the refutation” and “after the refutation” to examine how the discussion evolved over time. Second, count up how many of the 65 votes on the “against it” side were based solely on bias, or did not address the refutation of the claims at all. Thirdly, count up how many people agreed with the refutation after it was posted versus disagreed - without assuming what anyone who didn’t comment directly on why would’ve said.
    If you do this, rather than trying to shoehorn the vote count to your favor, you will see why many people are arguing there actually was a consensus present. -bɜ:ʳkənhɪmez ( User/ say hi!) 06:19, 13 July 2024 (UTC)
    What "refutation"?
    Also, obviously all the things you are saying are simply not how closing discussions works. The closer can evaluate the arguments but they are under no obligation to pretend that an argument that you happened to find particularly convincing was objectively strong. Loki ( talk) 19:25, 13 July 2024 (UTC)
    Closers are expected to determine consensus based on the quality of the arguments given on the various sides of an issue, as viewed through the lens of Wikipedia policy.
    In this context, a good close will need to give little to no weight to !votes that argued the Telegraph endorsed the litter boxes in schools hoax (as this was disproved by the articles provided in support of it, and thus is not a quality argument), and little to no weight to !votes that argued that it should be considered unreliable on grounds of bias (as this is contradicted by policy). BilledMammal ( talk) 19:32, 13 July 2024 (UTC)
    Whether or not it "was disproved" is a matter for the closer to decide. The closer decided it was not disproved. All you are saying is that you disagree with the closer. Loki ( talk) 22:44, 13 July 2024 (UTC)
    This case is unusually clear cut. You said "this source endorses this hoax", and provided an article where the source said "this is a hoax". It is not possible for a reasonable close to say that it was not disproved. BilledMammal ( talk) 00:03, 14 July 2024 (UTC)
    If I say that a source endorses the conspiracy theory that the moon landings were faked, and the source says "There's a common conspiracy theory that the moon landings were faked, which is not true. However, look at this evidence that the 1969 moon landing was filmed on a sound stage in California.", is that or is that not "endorsing the conspiracy theory"? Loki ( talk) 00:12, 14 July 2024 (UTC)
    Obviously not. It's called presenting all sides of a story. Otherwise, we'd only hear half the story. You may think that hoaxes are never newsworthy - what would the news report on if not saying "it's a hoax, but look at the evidence that the other side uses to try and convince you it's not a hoax"? -bɜ:ʳkənhɪmez ( User/ say hi!) 00:15, 14 July 2024 (UTC)
    It could, depending on the specifics. However, it's a false equivalence.
    What the Telegraph said after calling it a hoax was say that people do identify as animals. This is true, and nobody in the RfC claimed otherwise. BilledMammal ( talk) 00:24, 14 July 2024 (UTC)
    Ah, but they said this specific student identified as an animal at this specific school with the support of the administration, all of which is false and which fulfills all the pillars of the hoax except for the literal litter boxes. Loki ( talk) 01:27, 14 July 2024 (UTC)
    Everyone, regardless of your views regarding this, it is clear that (maybe a little less than) half of the RfC participants agreed with Chess's refutation against that incident being an endorsement of the litterbox hoax. Let's accept that and move on without directly arguing the RfC again. Aaron Liu ( talk) 02:09, 14 July 2024 (UTC)
    ( edit conflict) The issue is you proved none of that:
    • they said this specific student identified as an animal - based on your mistaken understanding of presuppositions
    • with the support of the administration - based on your definition of "support" (which you extend to "calling students despicable" - in other words "telling students off for bullying")
    • all of which is false - The school said one thing, parents said another, and the Ofsted report declined to comment
    • fulfills all the pillars of the hoax - based on your definition of the pillars
    For a closer to say that your close was not disproved they would need to say that every one of these four claims was true. No reasonable close can do that. Aaron Liu does make a good point, and so I will step back from this discussion now, but I felt it was important to make this point clear. BilledMammal ( talk) 02:12, 14 July 2024 (UTC)
    I agree that no reasonable person who reviews all the facts could conclude Loki's claimd (there's a freakin' TAPE RECORDING OF THE TEACHER calling the girl "dispicable" for not accepting a cat identity, FFS! How much more evidence is needed here?!).
    I suppose the real question here is, what happens when a large MINORITY of Wikipe#ians all assert something that is objectively false, in lock step with each other? (Which does not have to be in bad faith, and I do not say that it is, here). I'm not sure the mechanisms exist to deal with this effectively, which is a dangerous precedent, and expect more of it, and not only on this topic from this POV, either. 73.2.86.132 ( talk) 04:16, 14 July 2024 (UTC)
    It was later clarified that the recorder brought up the scenario of a student identifying as a cat for her rhetorical devices.
    If that happens, the WMF and checkusers first see if sockpuppetry or states are involved. If not, then we simply assert that "something" is true, since the scenario of them all being wrong at that specific time is unlikely and we have WP:NOTTRUTH. Aaron Liu ( talk) 14:28, 14 July 2024 (UTC)
    I think if you really wanted to step back you wouldn't have insisted on getting the last word, but regardless I think that this argument is going in circles enough that I'm not even bothering to read your comment fully. Loki ( talk) 04:28, 14 July 2024 (UTC)
  • Overturn per @ JoeJShmo—and maybe we need some language in policy discouraging NACs on RfC’s of certain length or impact. Zanahary 04:32, 14 July 2024 (UTC)
    This should be posted in the Participants section. Parabolist ( talk) 18:41, 14 July 2024 (UTC)
    @ Parabolist: WP:Be bold. I've moved it to the correct place. Aaron Liu ( talk) 20:54, 14 July 2024 (UTC)

Discussion

  • @ Aaron Liu: If you are only concerned with amending that sentence, do you mind withdrawing this request so that those of us are who are concerned with the close more broadly can submit? The issue is that it makes it difficult to focus on the broader issues if you start the discussion with a narrow scope, while the opposite is less true. BilledMammal ( talk) 05:21, 9 July 2024 (UTC)
    If we really need multiple requests, then maybe those could be in parallel? I feel like we could do all of them here and hopefully find "express" consensus for that sentence while the rest of the discussion continues.
    Unfortunately I'm ill-equipped to discuss this out right now as I have to go to sleep, sorry. I sure have planned my day well. Aaron Liu ( talk) 05:25, 9 July 2024 (UTC)
    I've attempted to make it parallel as you propose; if you feel that isn't an appropriate way to handle it, please move my comment. I've also renamed the sections "participant", "non-participant", and "closer". BilledMammal ( talk) — Preceding undated comment added 05:57, 09 July 2024 (UTC)
    The original sections were how {{ RfC closure review}} prefilled it. Aaron Liu ( talk) 12:41, 9 July 2024 (UTC)
    A close review can and should result in discussion of all the issues present, as I've done in my comment above. Ultimately, the one issue Aaron Liu identified should be grounds enough to overturn this close, as it amounts to a supervote, but I doubt this is going to be closed quickly and you (BilledMammall) should feel free to identify your issues in your !vote for people to consider. -bɜ:ʳkənhɪmez ( User/ say hi!) 05:29, 9 July 2024 (UTC)
  • @ Aaron Liu: you wrote a couple of times in your reasoning that you want amendment to the first paragraph with reference to the litterbox claim. Just wanted to nitpick that it actually appears in the third paragraph, if you want to edit for us pernickety types. Samuelshraga ( talk) 06:56, 9 July 2024 (UTC)
    By first paragraph, I meant the first paragraph of my statement. It seems that this has been... misrepresented! I'll fix that soon. Aaron Liu ( talk) 12:41, 9 July 2024 (UTC)
  • @ BilledMammal: You commented 44 times in the original RfC; now you've opened this close review and you are already badgering people here, seven replies in a few hours. It's wearysome. Black Kite (talk) 11:58, 9 July 2024 (UTC)
    I didn’t open this, and I’ve commented less than other editors involved here - I don’t think my participation has been unreasonable, although if you disagree I encourage you to raise the issue on my talk page as this is the wrong location for that discussion and I won’t reply further on that topic here. BilledMammal ( talk) 12:02, 9 July 2024 (UTC)
    The threading makes it look as though yourself and AaronLiu opened the close review together. If that's not the case, then perhaps your long section should be under a separate Level 3 subheading. Black Kite (talk) 12:44, 9 July 2024 (UTC)
    To simplify the maybe-confusing structure of this, I think claiming that we both opened it would be for the best, as with retaining the current formatting of rationales. Aaron Liu ( talk) 12:47, 9 July 2024 (UTC)
  • Comment As a close review I think we need to focus on the mechanics of the close. An editor who endorses or rejects the close because they agree with the outcome doesn't add weight to the discussion. Specific concerns were raised with the closing. Endorse responses that address the concerns with reason should be given weight in these discussions. Responses that simply endorse (or reject) the outcome without addressing the concerns raised should be discounted. This is like a legal appeal where we aren't arguing the case, rather we are arguing that the process was or wasn't followed (with supporting evidence). I feel this is a standard that should apply to all close reviews which often seem to devolve into a second round of litigating the original question. Springee ( talk) 12:27, 9 July 2024 (UTC)
  • Just a comment for non-British editors who might not know: The Daily Telegraph is one of the most prominent newspapers in a country where a large proportion of the population still read newspapers. I think you'd struggle to find an adult British person who doesn't have some sort of opinion on it, even if it's just "as absorbent as the rest of them, in a pinch." If the contention is that nobody with an opinion on the Torygraph (damn, there's me out) should have closed this discussion, you're likely disqualifying all British editors. Kind of like saying that an RfC on Fox News couldn't be closed by an American. Which may be fine, I just thought I'd mention it. –  Joe ( talk) 14:05, 9 July 2024 (UTC)
    As a Brit, I can confirm this sentiment. This is also true of The Guardian, The Independent and The Times. We have a small selection of notable left-leaning and right-leaning broadsheets, and most Britons have an opinion on them. This is potentially similar to WaPo and NYT that are widely known, as I assume most Americans have an opinion on these either way as well. CNC ( talk) 14:15, 9 July 2024 (UTC)
    I assume that most Americans have never heard of, or would not recognize, the majority of British newspapers. I would even wager that more would confuse The Times with The New York Times than would know what The Daily Telegraph is. — Red-tailed hawk  (nest) 14:19, 9 July 2024 (UTC)
    Precisely. The point was that S Marshall is from the UK (maybe that wasn't obvious), so naturally they would have some sort of opinion on The Telegraph without necessarily being bias. The "as well" was in reference to the overall comparison, not Americans knowing British newspapers. There's a rationale for having non-British editors close this one. CNC ( talk) 14:25, 9 July 2024 (UTC)
    I don't think that (non-)Britishness is required here; it isn't reasonable for us to ask people to not close something on the basis of nationality. Instead, As WP:INVOLVED reminds us, people are at times incapable of making objective decisions in disputes to which they have been a party or about which they have strong feelings. When one is able to put their feelings aside and objectively read a discussion, this is less of a problem, but having strong opinions to such an extent that one's ability to faithfully summarize a discussion become colo(u)red by them is incompatible with our expectations for a closer. — Red-tailed hawk  (nest) 14:31, 9 July 2024 (UTC)
    But nobody has demonstrated that Smarshall does have such strong opinions. Thryduulf ( talk) 14:35, 9 July 2024 (UTC)
    I've admitted in this discussion to having strong opinions about some of the Daily Telegraph's political columnists. Fact is, the Telegraph gives platforms to people who want to privatize the NHS and bring back the death penalty, and I find that abhorrent. I don't (and still don't) have a personal opinion about the Telegraph's view on transgender people, and I deny that gender and politics are the same thing.— S Marshall  T/ C 15:09, 9 July 2024 (UTC)
  • Just thought I'd point out that the (now-reverted) new entry on RSP has already been used to justify content removal with unwarranted stridency: [16]. Barnards.tar.gz ( talk) 15:14, 9 July 2024 (UTC)
    I mean, yes? WP:MREL is not WP:GREL. Almost everyone in the RFC including the vast majority of Option 1 voters agreed that the Telegraph is biased, which would mean that citing them without attribution is inappropriate. So I don't know what your point is here. Loki ( talk) 16:39, 9 July 2024 (UTC)
    There was WP:INTEXT: "The organisation has said". Based on attribution, it's not necessary to state the source if you are stating the author(s) of the claim. Overall, kind of a moot point when it's not due in the lead anyway. CNC ( talk) 16:48, 9 July 2024 (UTC)
    I agree the text was undue, and I have removed it. The point of mentioning it here was that the wording of the RSP entry was being used to support strident assertions about reliability that were in no way reflective of the much more circumspect discussion. If that's what people take away from all this, the process has failed. Barnards.tar.gz ( talk) 17:06, 9 July 2024 (UTC)
    While I see your point, the misinterpretation of source reliability listed at RSP isn't exclusive to that entry (as you may well agree). The RfC itself was also used a source, which is merely what the RSP entry was summarising. It's fair to say that misinterpretation of MREL sources is widespread, and this example just provides more weight to that argument. CNC ( talk) 17:36, 9 July 2024 (UTC)
    I think what's notable is that it took a mere 2 hours from the update to Perennial Sources to an edit war breaking out, and this does not lend to an interpretation of "no consensus" that favoured stability. Void if removed ( talk) 18:19, 9 July 2024 (UTC)
    I agree to a degree, but also don't think any GREL to MREL change ever intends to favour stability, or necessarily makes things unstable. Personally I think we should favour reliability of sources over stability, meaning context-based rationales in this case. I don't believe editors misinterpretation of MREL is a good reason to change the status quo though; the cause of the problem is a lack of understanding, the edit warring is just a symptom of that. CNC ( talk) 18:32, 9 July 2024 (UTC)
    The issue is how RSP works; its very subjective how we assess sources, and that means that the interpretation of our assessments is also very subjective. I think we should rework the process, but that's a different discussion. BilledMammal ( talk) 18:46, 9 July 2024 (UTC)
    Given that the party employing that rationale was WP:INVOLVED in this RFC and voted 3/ WP:GUNREL, I wonder: if you don't understand what it is you're voting for, is the vote valid? Void if removed ( talk) 18:58, 9 July 2024 (UTC)
    Yellow doesn't mean attribution is required nor does it mean Green source beats Yellow source. Instead it means we need to use caution when deciding if the material is being given undue weight by the source in question (which can effect how much weight it should be given on Wikipedia). It also means we shouldn't take interpretations as always correct. However, it doesn't mean we should question basic facts taken from the source. If they say 500 people attended or the topics were X, we should assume they are correct. This by the way is a general issue issue with RSP's buckets, not specific to this topic. Springee ( talk) 17:15, 9 July 2024 (UTC)
    WP:MREL is questionable as it stands because it is unable to distinguish "no consensus on whether a source should be used" from "consensus that it's unclear when a source is used". Chess ( talk) (please mention me on reply) 00:31, 10 July 2024 (UTC)
    What is the practical difference between them? Thryduulf ( talk) 00:49, 10 July 2024 (UTC)
    @ Thryduulf: None, right now. That's the problem, since WP:MREL is seen as "unreliable with exceptions" in practice. Editors !voting "Option 2" can win by default simply by preventing a consensus from emerging. Chess ( talk) (please mention me on reply) 02:53, 10 July 2024 (UTC)
    Well, why would that be harmful? If numbers are filtered and weighed into a close, I don't see what's wrong with that. Aaron Liu ( talk) 04:20, 10 July 2024 (UTC)
    If there is no consensus, why is it harmful for RSP to state that there is no consensus? If there is no difference in practice between between "no consensus for general reliability or general unreliability therefore it's medium reliability" and "consensus that it's medium reliability", why is not distinguishing between the two harmful? Thryduulf ( talk) 09:26, 10 July 2024 (UTC)
  • Are RfC participants supposed to reply in the Non-participants section, or should they keep comments in their own section and/or §Discussion? Firefangledfeathers ( talk / contribs) 16:51, 9 July 2024 (UTC)
    I’ve never seen a close appeal where it doesn’t happen, so I assume they are allowed to. BilledMammal ( talk) 16:57, 9 July 2024 (UTC)
    In fact, I haven't seen any close review with the headings format of the {{ RfC closure review}} template, lol. Aaron Liu ( talk) 18:20, 9 July 2024 (UTC)
    I have no objection to participants replying in the non-participants section. I think the goal of the headings is to group the top level comments together, which is accomplished even if those top level comments are getting replied to. – Novem Linguae ( talk) 07:15, 11 July 2024 (UTC)
  • As expected, people are already using this outcome to try to shift the balance of articles, and are also angling to go down the slippery slope and get other UK news media also declared unreliable on this issue, so that ultimately only one side of this active political debate can be covered as mainstream and non-fringe. *Dan T.* ( talk) 18:08, 9 July 2024 (UTC)
    That's completely irrelevant to the close. Thryduulf ( talk) 18:29, 9 July 2024 (UTC)
    Not entirely. That this was the motivation of certain editors on the RfC and the expected result of a non- WP:GREL close was brought up in the discussion. The fact that the closer ignored this in their close (and that it immediately turned out to be spot on) is yet another demonstration that the closer didn't do a very good job of weighing arguments. If they did, they certainly didn't show their working. Samuelshraga ( talk) 19:00, 9 July 2024 (UTC)
  • Editors are putting a lot of thought into closer's arguments about whether a "No consensus" finding on the RfC moves the Telegraph into WP:MREL or preserves the status quo. I think this discussion is premature, given that the closer has given next to no justification for a "No consensus" close - they explicitly disavow that it depends on the (misrepresented) summary of the litterbox hoax discussion in the close, and in their expanded close their only argument is a count of votes ( which they also explicitly disavow on their talk).
First we can determine whether we have a valid close - and if not we vacate and somebody else can close by weighing the arguments. Maybe they too will conclude "No consensus". Then the discussion of what exactly that means will be ripe. Samuelshraga ( talk) 18:55, 9 July 2024 (UTC)
There is no discussion needed about what a no-consensus close means - it's explicitly defined at WP:RSP (that wouldn't make sense if the lack of consensus was only between options 3 and 4, but that's unarguably not relevant to this discussion). Thryduulf ( talk) 19:03, 9 July 2024 (UTC)
Wonderful. I very clearly said that I don't think we should have that discussion now, and the first issue at hand is whether the close itself, meaning the judgement of "No consensus" and the reasoning given (or not given) for it should stand. Afterwards we can discuss, or not discuss, whether further discussions are or aren't needed on any topic that becomes germane. Samuelshraga ( talk) 19:06, 9 July 2024 (UTC)
I've requested clarity below due to the popular argument of "no consensus = no change". It seems pretty clear that this is a discussion that needs to take place, based on support for this proposal. CNC ( talk) 19:10, 9 July 2024 (UTC)
@ CommunityNotesContributor I understand that. However I think that relevant points unrelated to the "no consensus = no change" debate have been raised, and call into question the validity of the "no consensus" finding itself. This seems to me to be a logically prior discussion that could potentially make the "no consensus = no change" discussion moot. Samuelshraga ( talk) 19:14, 9 July 2024 (UTC)
Granted, and if anything it's intended to draw these arguments out of this discussion and instead clarified below. Even with the RfC overturned, in the meantime, there is a valid discussion of whether this RfC should be exempt from the RSP status quo, or whether there needs to be a more thorough discussion on reviewing how RSP lists sources. Given this discussion has already surfaced, I see no reason why it wouldn't surface again regarding another NC close. CNC ( talk) 19:22, 9 July 2024 (UTC)
True. I just don't want the discussion about this close - especially the arguments about it's basic failure to in any way weigh the arguments from the discussion - to get lost in the procedural discussion in what to do if the NC close is upheld. Of course that's more complicated because some people have now supported Overturn referencing closer's positions on what the outcome of NC is... and anyway now we're in a discussion about discussions about discussions.
Hopefully people coming to this review will still put appropriate weight on those who point out that the close is a supervote, that it doesn't weigh arguments, that it counts votes, and other failings, notwithstanding that more and more of the discussion is about the "NC = change or no change" issue. Samuelshraga ( talk) 19:31, 9 July 2024 (UTC)

A lot of the comments here seem to be implying that partially overturning by amending language isn’t an option? Can we at least obtain consensus that the language I mention should be amended? Aaron Liu ( talk) 21:06, 9 July 2024 (UTC)

I don't object to removing the language you want amended. I just think this is very secondary to the much more serious problem. There is no argument here that the close weighed the sides of the discussion in any way. Some people endorsing the close have asserted that it was reasoned, but they haven't elaborated on its reasons. Samuelshraga ( talk) 05:19, 10 July 2024 (UTC)
I was talking about many of the endorse !votes. Aaron Liu ( talk) 15:47, 10 July 2024 (UTC)
Personally, I think at minimum the removal of "and gender critical views" from the note, else what's the point in having a per topic discussion if a closer can unilaterally widen it?
For example, this is a story in The Telegraph about a social worker who won an employment tribunal on the grounds of her gender-critical views. There seems to be no exaggeration or inaccuracy. It also does not mention the word "trans" at all. It is entirely a story about the legal protection of those views, and the discriminatory acts of the council and regulatory body. It is a notable legal case (ie, the first time a regulatory body has been found to have committed unlawful discrimination) and as such not given undue prominence.
As written, this would come under the purview of this note, because the note has been expanded beyond anything discussed in the RFC. Why? Void if removed ( talk) 08:29, 12 July 2024 (UTC)
Without commenting on whether is should come under the close, a single accurate story (assuming it is, I haven't looked) is not at all incompatible with a finding of MREL or even GUNREL. Neither category is saying that all stories (in the relevant topic area) are inaccurate, heck even the Daily Mail gets things right at times. At the most basic level GUNREL means they are generally unreliable, MREL means they are sometimes unreliable - often enough that they are not generally reliable but not often enough that they are generally unreliable. In the same way generally reliable doesn't mean infallible. Thryduulf ( talk) 08:48, 12 July 2024 (UTC)
The point is that this is a story that is not a "trans issue", it is a "gender critical views" issue. The RFC was "unreliable on trans issues". If people wanted this to be part of the RFC, it should have been part of the RFC. Adding it in in the close without it being raised in the RFC and with no discussion is a WP:SUPERVOTE. Void if removed ( talk) 09:31, 12 July 2024 (UTC)
That is nonsense, Gender critical, or its original non-whitewashed term TERF, which even has it in the name, is a trans issue and whether specifically called out or not, it's implicitly covered under the topic.
There is no change in scope, so the accusation of a supervote for this is arbitrary, but simply WP:COMPETENCY is assumed on an obviously linked subtopic that the closer simply chose to call out. Raladic ( talk) 15:45, 12 July 2024 (UTC)
And all of that is of course extensively disputed (including the crack about "whitewashed") and none of this was discussed in the RFC, and your framing of the issues in this particular POV exemplifies the problem with closing in this way. ("call out"? is that the role of closer?).
To make this clear, consider a hypothetical RFC brought claiming that "Pink News is unreliable on gender-critical views", which plays out as a mirror opposite of the Telegraph one.
Ie, where the Telegraph is claimed to present trans issues in a biased and misleading way, and overly focuses on trans people in a negative light, inflating non-stories into breathless ragebait, the inverse claim is made that Pink News behaves the same about people with "gender critical views". Lets say that the arguments all play out exactly the same, in the same proportions and a closer decides it is a no-consensus result.
Do you think it would be defensible to say that the reliability of Pink News was therefore disputed on "gender-critical views and trans issues"?
These are distinct subjects with some overlap, and with a huge amount of conflict where they meet and even what terms mean, but here the POV of the closer has widened the scope of the close beyond the question that was asked. Void if removed ( talk) 15:54, 12 July 2024 (UTC)
Just simply no, it is consensus on Wikipedia (and as such the wider world, since we simply summarize the RS) that Gender critical views are a subtopic of transgender issues, as is very clear from the lead of Gender critical, so there is simply no leap here.
There is also no crack about whitewashing, again, we discuss this in Gender-critical feminism#Terminology, so I simply re-stated the consensus on Wikipedia on the issue.
Picking on words that were included in the close doesn't change the fact. Raladic ( talk) 16:00, 12 July 2024 (UTC)
But WP:NOTSOURCE so, no. And given these are exactly the arguments the closer has presumed the conclusion to, based on no evidence, and the many, many protracted discussions on talk there, it would be much simpler not to have needlessly expanded the close to include this completely undiscussed POV, for no good reason. Void if removed ( talk) 16:21, 12 July 2024 (UTC)
I believe that this is much less damaging than "unashamed embrace of the widely-debunked Litter boxes in schools hoax". Aaron Liu ( talk) 15:34, 12 July 2024 (UTC)

Request for clarity

Part 1

To those of you who say "Overturn" -- overturn to what? Please be clearer. It would help if you distinguished between:

  1. Overturn to a consensus. Please specify what consensus you see.
  2. Overturn to no consensus, defaulting to no change. This means you feel that WP:RSP should still say "generally reliable".
  3. Overturn to no consensus, defaulting to a change, but not the change that I specified in my close.
  4. Overturn to no consensus, defaulting to the change that I specified in my close, but change the summary of the discussion.
  5. Overturn by reverting the close, leaving someone else to close with no guidance from the community on how.

Thank you.— S Marshall  T/ C 15:17, 9 July 2024 (UTC)

I haven't read enough of the relevant policies to have an opinion on the Wikipedia:ONUS questions behind option 2-3. My sympathy is to 1, as I think the Wikipedia:GREL choice got the better side of the argument once @ Chess stepped in, and I saw many other editors thought the same, but I'm not nearly experienced enough in these to attempt to judge a consensus myself. So by default I will go to Option 5, because as I have argued here - the only reason you gave (and you only gave it in your expanded close) for giving weight to the view that the Telegraph was unreliable was this view is strongly disputed by significant numbers, but you told me on your talk page that the point is not to count votes, and I didn't, but to weigh arguments, which I did. There is no evidence of argument-weighing, and the close was not remotely a reasonable reading of the discussion, so the policy questions relied on to implement its outcome don't need to be addressed in my opinion. Samuelshraga ( talk) 15:29, 9 July 2024 (UTC)
Overturn to allow someone who intends to actually address the problems with your close to re-close the discussion with the consensus (or lack thereof) they find after doing so. If a closer actually weights arguments appropriately and explains how their close takes into account that, aside from the “it’s biased” and “I don’t like it” !voters, the majority was solidly swayed by the refutations of the initial discussion, then that close will be sufficient. -bɜ:ʳkənhɪmez ( User/ say hi!) 15:53, 9 July 2024 (UTC)
aside from the “it’s biased” and “I don’t like it” !voters, the majority was solidly swayed by the refutations of the initial discussion I think you must be reading a different discussion to me. Many people were swayed, to a greater or lesser extent, by some or all of the refutations. Many people were not. Even if you discount all of the "it's biased" comments (many of which were actually more complex than that and accompanied !votes of all options) calling that "a majority was solidly swayed" is a misleading oversimplification. Thryduulf ( talk) 16:12, 9 July 2024 (UTC)
When the refutations were based on the actual text, and nobody was able to actually present cognizant and clear refutation of the refutation, it does matter. Anyone !voting based on “I disagree with the refutation, even though it’s English language facts and provides the exact text of the article to support it, but I can’t say why I disagree” should have that opinion decreased in weight accordingly. Otherwise, those commenting early in a discussion have absolutely no reason to continue in the discussion to form a consensus - since their opinion, no matter how badly it’s proven wrong, will still count just as much.
If someone is proven to have based their opinion on inaccurate/misleading information, as many people commenting both before and after the refutation did, and they refuse to clarify/update to explain their opinion in light of new information, their opinion must be weighted accordingly. And that is what happened here, with people - including the closer himself - subscribing to an outright falsehood that the Telegraph said something that they didn’t, and nobody could ever provide proof that they did. If people are allowed to “win” discussions by blatantly lying and not providing proof just because enough people agree with that lie in furtherance of their political goals, then this is no longer an encyclopedia, but a propaganda machine.
The new close needs to take into account the fact that many (to use your preferred word) !votes for unreliability were based on falsehoods, that many more were based on not liking it, and that many more were based solely on bias in combination with these other things. And this goes for both sides - but the unreliable camp had significantly more !votes that were inaccurate at best. -bɜ:ʳkənhɪmez ( User/ say hi!) 19:08, 9 July 2024 (UTC)
  • Option 2, as I stated above. You closed as no consensus but then inserted your own opinion on what should happen instead of just leaving the status quo in place. Cheers  —  Amakuru ( talk) 16:20, 9 July 2024 (UTC)
    Your opinion regarding Option 2 is appreciated below in Part 2. CNC ( talk) 19:05, 9 July 2024 (UTC)
  • Option 5, since I thought the close rationale was flawed. starship .paint ( RUN) 16:29, 9 July 2024 (UTC)
  • If the close is reverted, then it should be reclosed by someone else based on their reading of the arguments presented in the discussion, taking into account any relevant comments here. So sort of option 5 but not exactly. Thryduulf ( talk) 16:29, 9 July 2024 (UTC)
  • Option 5. – Tera tix 16:33, 9 July 2024 (UTC)
Option 3/4 The result of no consensus can't be ignored by RSP as the status quo of RSP is to categorise sources (or topics by sources) with the relevant consensus established or lack of. The Telegraph can't be used as an example of "there was no consensus so there is no change", as this would have broader implications on other sources listed at RSP; Fox News and HuffPost (politics) come to mind as examples of GREL turned NC, but I imagine there are many others that were GREL by default prior to NC. It's unclear whether editors believe we should be making an exception for The Telegraph, or whether the proposal is to re-format how RSP categorises source discussions. If it's the latter, this requires a broader RfC on how RSP categorises sources and has little to do with this RfC. CNC ( talk) 16:34, 9 July 2024 (UTC)
Given that this section was opened as a way of disambiguating the intentions of people who support Overturn, I think it's a little unhelpful to have people who endorse the close choosing options as well (not that I think your arguments are unwelcome at all - I already said that I don't as yet feel confident or experienced to get involved on this issue and what you write seems cogent, even if it prejudges the idea that "No consensus" close will be retained). Samuelshraga ( talk) 19:10, 9 July 2024 (UTC)
That's a very good point and had overlooked that, apologies. I've struck my comment and encourage anyone to collapse this discussion. CNC ( talk) 19:13, 9 July 2024 (UTC)
I'm neutral to Option 4 and would oppose everything else. I think the conclusion was the only reasonable reading of the discussion, and closing to any consensus (including, by the way RSP works, WP:GREL) would be inappropriate. I'm not particularly attached to the summary though, and honestly do think that the exact phrasing was stronger than was reflected in the discussion. Loki ( talk) 16:35, 9 July 2024 (UTC)
@ LokiTheLiar, this section was to disambiguate the intentions of people who support Overturn, it could be a bit misleading to include the opinions of people who endorse the close. Samuelshraga ( talk) 19:38, 9 July 2024 (UTC)
Option 2. The default in a case of no-consensus is to maintain the previous status quo. *Dan T.* ( talk) 17:58, 9 July 2024 (UTC)
It's not, see comment above re status quo of RfC closures regarding source reliability. Are you suggesting that it should be, and should it be enacted retrospectively as well? This isn't the right venue for that proposal, but I'd appreciate clarity from the "no consensus means no change" crowd as to what they are proposing, so we can draft up an RfC for it and move forward. CNC ( talk) 18:16, 9 July 2024 (UTC)
For WP:RSP that is not true. Look at the page; it has an entire category for sources on which there is no consensus, and sources are described as lacking consensus repeatedly throughout the table. Its purpose is to document the current consensus of the community (or lack thereof); it doesn't have the same need for stability or the need to reach a hard decision on some version that applies to article-space. We can't realistically leave an article in no-consensus state, but for RSP we can and frequently do. -- Aquillion ( talk) 19:33, 9 July 2024 (UTC)
Option 2 CoffeeCrumbs ( talk) 23:02, 9 July 2024 (UTC)
Since my preferred option isn't there, my ideal would be overturning the close for a re-evaluation, with no assumption that anyone who didn't assert that the specific examples of alleged reliability presented was conceding the unreliability of those specific examples. CoffeeCrumbs ( talk) 23:12, 9 July 2024 (UTC)
I think that's 5? Samuelshraga ( talk) 11:11, 10 July 2024 (UTC)
I didn't think so since I'm not suggesting no guidance, but no guidance with the direction of making sure not to make what I personally feel was a particular previous error in determining consensus. I think a closer needs to approach the arguments about reliability more than the feelings about reliability, which I believe (again, my personal opinion) is more in line with establishing consensus and decreasing the chances that this becomes a whole new dreary casus belli in what is already a controversial area. CoffeeCrumbs ( talk) 00:41, 11 July 2024 (UTC)
Option 5. Chess ( talk) (please mention me on reply) 00:32, 10 July 2024 (UTC)
Option 4 as per my statement above. I think you got the result right, but the reasoning (especially introducing ONUS) is wrong. Also to note I reject the premise behind Option 2. The RSP (and so RSN) does have a way of indicating that editors don't agree on the reliability of a source (MREL), so I also don't agree with editors that no consensus means no change. The RSP is not article content, and this wasn't an RFC on how to update the RSP. The RFC was on the reliability of the source, on which there isn't agreement. -- LCU ActivelyDisinterested « @» ° ∆t° 11:11, 10 July 2024 (UTC)
  • Option 5 Sweet6970 ( talk) 12:36, 10 July 2024 (UTC)
  • Well, okay then. I see nothing that tempts me to revert myself, so when, after the requisite amount of wrangling, someone else comes along and closes this, their entire menu of options seems to be either (1) no consensus to overturn or (2) consensus to overturn but no consensus what to overturn to, in which case the next closer has a great big problem. If you want, you can make this less of a headache for that hypothetical person by supplying with reasoned arguments for what the close should have been. It would help even more if you could take the trouble to ensure that these arguments are compatible with the rather idiosyncratic way that WP:RSP works.— S Marshall  T/ C 16:08, 10 July 2024 (UTC)
The closer requirements involve being compatible with policies and guidelines. WP:RSP is neither so no arguer or new closer would have any obligation to be compatible with its idiosyncracies. Peter Gulutzan ( talk) 16:59, 10 July 2024 (UTC)
Thank you. I'm certainly refreshed and challenged by your unique point of view.— S Marshall  T/ C 17:44, 10 July 2024 (UTC)
What polices and guidelines is RSP not compatible with? Thryduulf ( talk) 17:58, 10 July 2024 (UTC)
Irrelevant. Peter Gulutzan ( talk) 22:36, 10 July 2024 (UTC)
If you would like to overturn a ton of our existing consensus and system, you may open that as a separate proposal. For now, let's please operate within the status quo. Aaron Liu ( talk) 22:40, 10 July 2024 (UTC)
Perhaps I've caused a misunderstanding, see reply to Thryduulf below. Peter Gulutzan ( talk) 23:08, 10 July 2024 (UTC)
You explicitly claim that RSP is not compatible with policies and guidelines. It is not irrelevant to ask you to substantiate that claim by listing which policies and guidelines it is not compatible with (and ideally explaining why). Thryduulf ( talk) 22:44, 10 July 2024 (UTC)
I think I belatedly see where you got that idea and it's my fault. After the sentence "The closer requirements involve being compatible with policies and guidelines." I said "WP:RSP is neither ..." i.e. "WP:RSP is neither a policy nor a guideline ...". You seem to have taken it as "WP:RSP is neither compatible with policies nor with guidelines ..." So I should have written more carefully. Anyway, it's true that WP:RSP is neither a policy nor a guideline and your question doesn't relate to that. Peter Gulutzan ( talk) 23:08, 10 July 2024 (UTC)
You're welcome to explain how you think RSP should be changed in discussion below. CNC ( talk) 22:46, 10 July 2024 (UTC)
Perhaps I've caused a misunderstanding, see reply to Thryduulf above. Peter Gulutzan ( talk) 23:08, 10 July 2024 (UTC)
Policies and guidelines aren't the only kind of consensus out there. RSP's consensus is not overridden by any broader consensus, thus it stands. Aaron Liu ( talk) 18:30, 12 July 2024 (UTC)
Not sure what that's arguing for, it remains true that no arguer or new closer would have any obligation to be compatible with its idiosyncracies. Peter Gulutzan ( talk) 00:44, 13 July 2024 (UTC)
The word you're looking for with "idiosyncrasies" is "consensus". Aaron Liu ( talk) 04:53, 13 July 2024 (UTC)
The next closer does not have a great big problem, because presumably they will actually evaluate and weight the discussion appropriately, rather than taking the initial commenter’s claims at face value, ignoring the amount of support for the refutation of those claims, and in fact repeating those inaccurate claims as part of the close.
I respect you a lot S_Marshall, I really do, and your closes tend to be quite well crafted and explain your decision making very well. This one missed the mark woefully, however, as seems to be clear looking at the consensus forming above that your close was not appropriate. I don’t want you to think that I’m trying to say you intentionally supervoted here - but the fact is you seem to be unable to accept that your close amounted to a supervote, and you, to use your words, “unashamedly embraced” the initial, refuted claims, the refutation of which was agreed to in large part by most editors providing substantive comment after it. You also basically begged it to be taken here - I’m not sure if you did that because you felt confident that your close was not a supervote (when it was), or whether you just didn’t want to deal with it. But you were given the chance to expand on your claims in your close - and you instead posted basically the same closing statement with only a couple additions that did nothing to address the significant plurality (if not majority) of editors who directly discounted the claims you took as fact in your closure. -bɜ:ʳkənhɪmez ( User/ say hi!) 20:22, 10 July 2024 (UTC)
Well said. I believe S_Marshall almost always does a terrific job, and is extremely valuable to the movement. I disagree with the close, for a similar reason you do, but I really hope it's not taken as a personal attack, but as a polite disagreement on something that is important to get right. CoffeeCrumbs ( talk) 00:43, 11 July 2024 (UTC)
  • Option 4 per my !vote above. Option 2 is against current policy and would require changing WP:RSP or establishing a specific carve-out for this case, neither of which are palatable. Pinguinn  🐧 11:43, 11 July 2024 (UTC)
  • Option 4, if that wasn't obvious yet. Aaron Liu ( talk) 03:22, 12 July 2024 (UTC)
Option 5. Levivich ( talk) 18:21, 13 July 2024 (UTC)

Part 2

For !voters of Option 2, could you also clarify how "no consensus, defaulting to no change" should work based on the status quo at RSP:

  • Option 1: The Telegraph RfC should be an exception to the status quo, therefore the no consensus close wouldn't change previous consensus
  • Option 2: The Telegraph RfC and future no consensus RfCs should no longer replace any previously established consensus
  • Option 3: All sources with no consensus should default back to any previously established consensus, retrospectively
  • Option 4: No consensus RfCs should only be included on a case by case basis
  • Option 5: Disagree that this is how RSP categorises sources

This is not an RfC, simply trying to clarify how "defaulting to no change" is supported. Pinging additional editors who expressed this view or touched upon it for comment: @ Amakuru @ Walsh90210 @ *Dan T.* @ BilledMammal CNC ( talk) 20:13, 9 July 2024 (UTC)

I'm not sure there is an easy answer here. If we had say 50% (by numbers and quality of argument) say a source is 1 while the other 50% say 2, I would be inclined to go with status que. However, if things are the same ratios but we are dealing with 1 vs 3 (green vs red) then it seems hard to justify status quo. Perhaps I'm thinking about it a bit mathematically, but if nocon shifts it a half point I would err on the side of no change. If nocon shifts a whole point, I would move it. I would also note that if we are talking about moving the source up vs down I would err on the side of more general source inclusion vs less. As this applies to the discussion above, I would say such a clear divide should be yellow with an understanding that we really mean case by case, not yellow is generally excluded but perhaps could be used here or there. Springee ( talk) 19:29, 9 July 2024 (UTC)
WP:MREL does state "may be usable depending on context." but nonetheless you make valid points, even if it's a big can of worms. If I understand correctly, what you're suggesting is a "case by case" assessment based on the RfC itself? The next question would be should this be decided by the closer, or by discussion and consensus at RSP? I've otherwise included another option for "case by case" basis of inclusion, which while I still think is a CoW, appears a relevant option based on your comment. CNC ( talk) 19:44, 9 July 2024 (UTC)
Sorry, when I was talking about case by case I was referring to a source that is decided to be yellow and how we use it in articles. This is a general complaint about how yellow sources are sometimes treated as less legitimate than green ones. Sometimes editors play a game of green source beats yellow source and ignore case by case usage context. For example, if a green source briefly said, "this is bad" while a yellow source offers 3 detailed paragraphs discussing pros/cons but mostly pros in detail I wouldn't presume the green source article proves the yellow source wrong. In this case I would say the yellow source is the stronger of the two. As for RSN closings, I think they will always be case by case but hopefully most cases will be easier to untangle. Springee ( talk) 20:54, 9 July 2024 (UTC)
My mistake. Naturally I agree that a compilation or MREL sources is more reliable than a single GREL, depending on the context of course, but generally I agree with the concept. I'm not sure what you mean by "As for RSN closings, I think they will always be case by case but hopefully most cases will be easier to untangle". CNC ( talk) 20:59, 9 July 2024 (UTC)
Looking at WP:RSP, for several of the first "no consensus" colored topics, the discussions were closed with consensus ( Anadolu Agency, AllSides Media, Apple Daily, Arab News). This "no consensus" supervote is not inline with general practice, and cannot stand. Walsh90210 ( talk) 20:17, 9 July 2024 (UTC)
So Fox News and HuffPost (politics), among others, should be overturned, per Option 3? CNC ( talk) 20:19, 9 July 2024 (UTC)
From Wikipedia:Reliable_sources/Noticeboard/Archive_406#RfC:_downgrade_Fox_News_for_politics?: It is clear the overwhelming consensus is to downgrade Fox News to generally unreliable for politics starting in November 2020. Once again, there is consensus in the close. If the result here is "no consensus", it cannot be used to justify any change in treatment. Walsh90210 ( talk) 20:21, 9 July 2024 (UTC)
No. Per WP:FOXNEWS: "Historically, there has been consensus that Fox News is generally reliable for news coverage on topics other than politics and science. However, many editors expressed concerns about the reliability of Fox News for any topic in a 2023 RFC. No formal consensus was reached on the matter, though." Should it be overturned then? Please tell me you otherwise looked past RSP entries beginning with A. CNC ( talk) 20:23, 9 July 2024 (UTC)
Would you like me to reference WP:HUFFPOLITICS as well? CNC ( talk) 20:35, 9 July 2024 (UTC)
I am strong on assuming that the status quo for no consensus at RSP holds for this discussion. I don't think we should be questioning the long-standing tradition at RSP, which has its own reason, to derail this CRV. If someone would like to change that, they should start their own proposal. Aaron Liu ( talk) 20:41, 9 July 2024 (UTC)
I'm also of the strong opinion that "the status quo for no consensus at RSP" is relevant, but the reality is many editors have expressed their concern over RSP listing prcoess and therefore it requires evaluation, here and now. This section of "Request for clarity" is not an attempt to "derail this CRV", but instead to refine discussion of this topic to this section. CNC ( talk) 20:53, 9 July 2024 (UTC)
Yeah, I know that nobody wanted to destroy our efforts here. However, in my opinion, if we try and bite off more than we may chew, that is what's going to happen. Aaron Liu ( talk) 00:06, 10 July 2024 (UTC)
Putting aside policy questions around privileging "status quo vs MREL", I think it's relevant that many editors who supported Option 1 and Option 2 in the RfC found that - especially after the detailed rebuttals (by Chess and others) - that there was simply no case to answer on unreliability, notwithstanding that some editors continued to allege it.
The discussion wasn't framed around an open discussion of the question "Is the Telegraph reliable?" It was framed as "Do the examples brought by (mainly) Loki establish that the Telegraph is not generally reliable?"
Editors who supported GREL clearly thought that the case for GUNREL had been refuted, and saw little need to make positive arguments in favour of GREL. If a finding of MREL is really the outcome of this close (or the close which follows it after overturning) of this RfC, it's implausible to me that a new RfC will not quickly be generated to make the positive case for reliability on transgender issues (and gender-critical views, which the closer inexplicably included).
Quantitative arguments to do with the volume of articles published and number of factual inaccuracies, any retractions or corrections which have been published, Wikipedia:USEBYOTHERS and others spring to mind. I am sure that such evidence would have been raised if GREL supporting editors thought that the discussion would be interpreted this way. Samuelshraga ( talk) 16:16, 10 July 2024 (UTC)
UBO was actually raised, though sources supplied to evince UBO were disputed; the dispute was not resolved by the time the second month came in and discussion fizzled out. Aaron Liu ( talk) 20:14, 10 July 2024 (UTC)

An unrelated, modest proposal

Between this imbroglio and the one about the ADL RfC a few days ago, maybe we should just write down somewhere that any RfC with more than (500kb? 1mb?) of crap in it ought to be closed by a panel. Obviously not as a requirement, but it just seems practical. Is this anything? Does this have legs? jp× g 🗯️ 21:13, 9 July 2024 (UTC)

Agree . Because based on your threshold, it will always be contested. CNC ( talk) 21:16, 9 July 2024 (UTC)
Before some offsite brane-geniouse[ sick [ sic] adds to the red-string corkboard that this is some kind of veiled attempt at shady political ministration, I already commented in the RfC, and furthermore I do not particularly give a rat's what parliamentary hocus-pocus ends up happening here (or at XRV), it's just taxing to see one person try and sit down to close a Tolstoy-length RfC, immediately get massively BTFO at AN over the close, and then all their effort is wasted when a separate group of people sit down to write a panel close. jp× g 🗯️ 21:19, 9 July 2024 (UTC)
This now sound like some kind of veiled attempt at shady political ministration. CNC ( talk) 21:29, 9 July 2024 (UTC)
Back in 2006 the phrase "muhahahahahahaha" was considered extremely random and funny, and I think we should have a revival. jp× g 🗯️ 21:56, 9 July 2024 (UTC)
I'm not sure about absolutely requiring a panel close, since that would mean that some of these discussions would take months and months to be closed, but I do think I'd support a requirement for either an admin or a panel close. I think this particular close was good, but I'd really rather skip the inevitable-closure-review part of the process in the future as much as possible. Loki ( talk) 21:38, 9 July 2024 (UTC)
I think recommending (not mandating) that such discussions are closed by a panel or highly experienced, clearly uninvolved single admin would be good. Not because non-admin closures are inherently bad (they aren't - some non-admins are better closers than some admins) but because close reviews based on alleged minor procedural errors or the admin status of the closer (which are becoming more common) are a bad thing. Maybe some sort of restriction that said someone who was involved in a discussion may not initiate a review of such a discussion within 48 hours of the close unless they get agreement from someone uninvolved or someone who supported a different outcome to them that a review is justified. However I don't know whether this would actually work or how it could be enforced - it would need more thought before it could be a viable proposal. Thryduulf ( talk) 21:53, 9 July 2024 (UTC)
I do think recommending an admin or panel close would be good for RFCs over a certain length, but it would also be a good idea to tack on RFCs in WP:CTOP areas. Most of the contested closes I see are in WP:AP2, WP:ARBPIA, or WP:GENSEX; for those we actually could require it and I think it would help significantly. There are a lot of CTOP areas and many of them are pretty quiet nowadays, so we might just want to do it in certain ones like what I listed here. The Wordsmith Talk to me 22:03, 9 July 2024 (UTC)
I don't think there is solid evidence that panels (even admin panels) are less likely to be challenged these days. Also given the difficulties we already face in finding closers for such discussions I do not think it wise to add an additional procedural hurdle. Best, Barkeep49 ( talk) 22:07, 9 July 2024 (UTC)
Sure, it would be bureaucratic mumbo-jumbo in some cases, but I don't think the alternative is having no bureaucratic mumbo-jumbo. The alternative, which we are currently posting in, is a hundred-thousand-byte AN thread paired with a twenty-six-thousand byte XRV thread (and this is just on the first day of both). jp× g 🗯️ 22:38, 9 July 2024 (UTC)
  • If you do the heavy lifting then you're going to get close reviews, panel or admin or bureaucrat or founder. We need to think about how we conduct them. I've noticed that someone who doesn't like your close virtually always alleges involvement, as well as supervoting and all the other things that challengers pretty much have to say, because we have this weird culture where saying "I think the closer was wrong" always fails but "the closer made a technical procedural error" often succeeds. If we change that culture we'll make better decisions.— S Marshall  T/ C 22:26, 9 July 2024 (UTC)
    Yeah, this is the most annoying part: even if the close is (imo) a correct interpretation of consensus, a single closer will often give rise to all sorts of objections along the lines of "well how do we know this random person is correct?" or "but they aren't even an admin!" or "they said while instead of whilst!" et cetera. This can give people a ready-made rationale to disregard or overturn the result later on because "well the close was half-assed" etc... in the example of the ADL RfC, there were actual think tanks and newspapers talking shit about the close, so I think that making it more difficult to raise objections to the manner of the close is overall better for the decisionmaking process.
    Of course this doesn't need to be done in all cases, but I think it would be condign to at least point out that people are prone to demanding it. jp× g 🗯️ 22:36, 9 July 2024 (UTC)
    I think the root of the issue is that closers are often vague. For example, in this close you say on the basis of scholarly sources and an Ofsted report, various misrepresentations contained in that article are noted. You don't explain what those misrepresentations were, which ones were supported with scholarly sources and an Ofsted report, or what the community consensus was on each of them. This makes it very difficult for editors to determine if your close is correct.
    Sometimes this is even done deliberately, to make it harder to challenge the close, something I very much disagree with - if there is something wrong with a close we want to be able to identify it. I'm not saying you do this but some closers, by their own admission, do.
    Because this makes it difficult to determine whether the closer is actually wrong editors need to consider the information that is available to them - whether the close appears to be a supervote, and whether the closer has previously expressed opinions on the topic that might have tainted their reading of consensus. I think if we fix that issue, if we expect closers to provide more detail, then I think the rest will fix itself.
    That's not to say every close needs such detail, but some, including this one and the ADL one, would have benefited from it. BilledMammal ( talk) 22:39, 9 July 2024 (UTC)
    Nobody at all is ever satisfied by providing more detail about the closing method, in any circumstances.
    In the 10+ years I've been closing RfCs on Wikipedia, I've been asked to expand on my close more than a few times. Exactly 100% of the people who asked for this have gone on to issue a close challenge, and exactly 0% of them have been satisfied.
    I'm afraid that long experience of this tells me the only reason anyone ever asks for more detail is because they're hoping you'll say something they can attack at AN.— S Marshall  T/ C 15:49, 10 July 2024 (UTC)
    I haven't been closing discussions for as long, and I focus more on RM's, but my experience differs - I find that sometimes the editors are satisfied by my expansion.
    Other times, they do go on to use what I said in a close appeal - but personally, I think that's a good thing. If I said something wrong then that means I probably made an error in my close and I want the community to be able to find and rectify that error. When closing, my goal isn't to write a close that will survive a close review, but to write a close that will accurately reflect consensus. BilledMammal ( talk) 00:49, 11 July 2024 (UTC)
    To expand on this, I wanted to use the example of a question I asked you: What misrepresentations are you referring to here? As far as I can recall ... the only alleged misrepresentation raised was whether a student actually identified as a cat.
    If I was asked a question like this as closer I would be happy to answer it. This is because the nature of it means only two things can happen; either I can satisfy at least that concern, preventing or at least reducing the scope of any close review, or can I discover that my close was flawed. I see both these results as a positive.
    Honestly, I greatly respect you as a closer. In discussions about NACs I've previously cited you, along with Paine Ellsworth, as two of our best closers. In this case, however, I think you made a (very rare!) mistake. BilledMammal ( talk) 03:57, 11 July 2024 (UTC)
    The legal system has tried to solve this problem by having a standard of review. We should implement this on Wikipedia by clarifying what level of deference we give to closers, given that we already have this as an informal policy. In my opinion, we should only defer to the closer when a closing statement considered an issue being disputed, and when the closer's judgement is based on the arguments people have made. Chess ( talk) (please mention me on reply) 02:51, 10 July 2024 (UTC)
  • I agree with Barkeep49 that there is no evidence that having a group of evaluators of consensus leads to less followup discussion. I also don't think it's appropriate to treat admins as being specially privileged to evaluate consensus. In my view, the problem is that the community has certain expectations regarding how consensus is evaluated, and typically there'll be someone whose viewpoint didn't prevail that chooses to point out any deficiencies they see. I know the community historically dislikes bureaucracy, but if we were to introduce some, I'd suggest building up a list of experienced evaluators of consensus who can be asked to determine the result of divisive discussions. Note that the only way to become experienced is to evaluate some discussions, so the community needs to be tolerant of users stepping up to do so, even if they make mistakes. Wikipedia:Discussions for discussion could serve as a place to foster greater experience in evaluating discussions (at its genesis, I had feared it would be just another place to where disputes would spread, but up until now, that hasn't happened). isaacl ( talk) 22:58, 9 July 2024 (UTC)
    At one point I had thought about proposing a userright flag called discussioncloser that could be given out to trusted users like template editor and rollback. It wouldn't have any technical permissions, but maybe there could be an edit filter restriction non-discussioncloser users from using our close templates on certain pages. The Wordsmith Talk to me 01:45, 10 July 2024 (UTC)
Closes are legitimate when they consider the necessary facts and provide clear reasons for decision. Panels assist greatly in this, because editors can compare notes and ensure they're not missing any relevant information. Obviously, people are going to complain no matter what, but a good close will explain why certain !votes were disregarded and others were not. Chess ( talk) (please mention me on reply) 02:19, 10 July 2024 (UTC)
I agree with this too. And especially when a discussion becomes lengthy, it is much more likely that whether intentionally or not, a closer misses significant portions of the discussion, or in other words, unintentionally falls into a vote-count just because one side may have significantly more words than another. It is not reasonable to expect one person to be able to read a lengthy discussion and not error in some way even if they take hours or days to read through it and attempt a closure. The beauty of a panel is that if one person, or even two, miss something, it is likely that the third/further person will catch it. -bɜ:ʳkənhɪmez ( User/ say hi!) 03:08, 10 July 2024 (UTC)
While panel closes have their uses, I think that generally the best way to catch issues is by having the closer be more verbose. It doesn't increase their workload significantly, and it makes it easy for participants to catch errors and raise them with the closer. BilledMammal ( talk) 03:22, 10 July 2024 (UTC)
One of the main benefits I found in doing a panel close on the ADL RfC was being able to workshop the close statement. Any of the three of us could have closed the thing in a way that was within a reasonable closer's discretion, but together we were able to talk through how the close statement would read to participants on both sides, to non-participants, to people looking back later, and to catch statements that might be too easy to take out of context, could be twisted to claim bias in one direction or the other, etc.
The downside of a panel close is you need to find multiple people willing to take the same level of heat—all three of us in the ADL close panel have been criticized in multiple publications—and then get those people to coördinate. We spent hours on voice calls. Others may exchange many emails. With most things in life, teamwork reduces the total number of person-hours required, but with panel closes it actually increases it. Because of that, I'm not sure to what extent our volunteer ecosystem can support a greater number of panel closes than organically emerges. -- Tamzin[ cetacean needed] ( they|xe) 03:16, 10 July 2024 (UTC)
I think you make an important point about having at least a bit of review in the closing process, something the panel allows. Is there a way that we could have something like a RfC close, pre-close discussion for some of these topics? I think sometimes there is a level of momentum once the close is "official" but if the closer could state what they are thinking and allow editors some ability to chime in before the ink is dry, would that reduce some of the issues that you pointed out? I'm not sure if this is a practical idea or one that might cause more issues than it solves but perhaps it would help. Springee ( talk) 03:26, 10 July 2024 (UTC)
As someone else noted somewhere in here, WP:Discussions for discussion exists. That said, when a major concern in closing a sensitive RfC is avoiding becoming part of anyone's narrative (to the extent it can be avoided), having a public drafting/review process, where everyone can see suboptimally-phrased past wording, would defeat a lot of that. But I think it's still better than nothing. -- Tamzin[ cetacean needed] ( they|xe) 03:52, 10 July 2024 (UTC)
@ JPxG, there's already often a backlog of RFCs for close at WP:CR. I don't see adding a suggestion that any RFC over certain length be closed by panel is going to help that, in fact it may just give challengers more ammunition in their claims that entirely reasonable closes are somehow bad. TarnishedPath talk 03:30, 10 July 2024 (UTC)
  • I can think of 3 panel closes off the top of my head that I strongly disagreed with. I won't name them because I don't want to call anyone out, but my impression is that panel closes do not help improve RFC closing accuracy, so I don't think it'd be a good idea to require them. – Novem Linguae ( talk) 04:01, 10 July 2024 (UTC)
What would be helpful would be a way to stop editors turning RFCs into huge walls of text. In every RFC that ends up this way there are always a small handful of editors (not the same editors, but rather the editors who most care about the issue) that generate the most text. The rebuttal of an argument happens each time that argument is used, but that shouldn't be necessary (it not being a vote). -- LCU ActivelyDisinterested « @» ° ∆t° 11:18, 10 July 2024 (UTC)
Yet it basically was necessary here, and the closer still didn’t account for the rebuttal in their closure of the discussion. So if anything, this close, even if overturned, and the number of people supporting it shows that it is necessary to ensure people whose !vote is based on inaccurate information or an idea that has been disproven/rebutted strongly are aware of the fact their opinion is based on that and given a chance to review and expand upon it. And if they don’t, it can’t be claimed “they didn’t see the rebuttal” - it would have to be seen that they did see it, since pointed out to them, and chose to ignore it - which should result in a significant down weighting of their !vote indeed, as it’s basically an admission that “I can’t rebut that rebuttal”. -bɜ:ʳkənhɪmez ( User/ say hi!) 15:33, 10 July 2024 (UTC)
Outside of Wikipedia, this is done by having someone moderate the discussion. The English Wikipedia community has so far placed a higher priority on ensuring everyone gets to weigh in, out of a concern that any moderation would be unduly strict. isaacl ( talk) 17:32, 10 July 2024 (UTC)
I mean, WP:BLUDGEON is a conduct issue; people can and have been ejected from topic areas for repeatedly bludgeoning discussions. (If it's just one discussion where they lost their cool then it's probably not worth worrying about.) There's always the option to look up repeat offenders, nudge them to stop bludgeoning discussions, then drag them to AE or ANI if they don't listen. Doing that more often would encourage people to not be so bludgeon-y in general. Another thing that might discourage bludgeoning: Make it unambiguous that closers may, at their discretion, ignore all non-top-level comments in an RFC, if the RFC is already massive (of course this would have to be combined by making it clear to everyone that if they feel some point is vital, they need to edit it into their one top-level comment), and should even say that they're doing so so people understand that their elaborate back-and-forth arguments aren't even being read - to be clear, I'm not saying "exclude them when determining consensus", I'm saying closers should be specifically empowered to say "I'm not reading all that, I'm only reading the top-level comments." RFCs aren't supposed to devolve into threaded discussion anyway, so "at a glance this all looks like pointless natter between people who just want the last word and I'm going to disregard it" seems like a reasonable thing to encourage. Maybe even some sort of "just the main argument" viewer that specifically removes all responses. Or we could flatly forbid threaded responses in RFCs, confining them to a separate comment section that the closer is not required to read. -- Aquillion ( talk) 00:37, 11 July 2024 (UTC)
I don't think there is a consensus agreement in the community that requests for comments aren't supposed to have threaded discussion. Many of the editors who like to weigh in on how decisions are made think threading is important for facilitating efficient communications. (My variant on this is that I think we should consolidate discussion so the same topics aren't discussed in multiple threads, but that hasn't gotten a lot of support.) Since English Wikipedia's decision-making traditions are based on the idea of building consensus, I don't think enabling evaluators to say "I'm going to ignore the discussion" would gain favour.
Yes, extreme cases of swamping discussion can get addressed. But communications rapidly bogs down way before that point, and before any point where sanctions would be deemed reasonable. The N-squared problem of trying to hold a large, unmoderated group conversation (where there are up to N-squared interactions that can occur) means that everyone can be acting in good faith and yet it becomes very difficult to follow all the points being made. isaacl ( talk) 00:54, 11 July 2024 (UTC)
Bludgeoning is a lot different than asking someone to reconsider their opinion or explain it further in light of information that they did not address in their original comment - regardless of whether that information was already present or not. Closers should certainly not be permitted to ignore the threaded discussion - because that in and of itself results in "first mover advantage". People would be able to make whatever claims they want, or make their initial !vote based on inaccurate information, and then the closer should just be allowed to ignore the replies/discussion that points that out? Absurdity. -bɜ:ʳkənhɪmez ( User/ say hi!) 01:52, 11 July 2024 (UTC)
You have to let people seek consensus by talking to each other and you have to pay particular attention when someone changes their mind after being persuaded by a convincing point. But you can't allow a passionate editor to have a disproportionate effect on the discussion by sheer volume of text when they're not convincing anyone.— S Marshall  T/ C 07:16, 11 July 2024 (UTC)
If I infodump a wall of text and a dozen other editors cite it, that's not bludgeoning. Neither is posting rebuttals on their own.
Bludgeoning is when an editor repeatedly makes the same argument. This is disruptive because redundant information does not add value to the conversation. Chess ( talk) (please mention me on reply) 13:09, 11 July 2024 (UTC)
I've been trying to think of the way to address this - you say you have to pay particular attention when someone changes their mind after being persuaded by a convincing point - that is exactly what happened in this discussion, yet you not only ignored it in your close, you actually found the opposite to have happened. You took those not commenting on the refutations to be claiming that they were wrong, you viewed those arguments to be "stronger" than those refuting the original claims (when the discussion makes clear it was considered opposite by a clear majority of those commenting on the refutations, rather than ignoring them), and you then impressed your personal opinion of the claims onto the close. You seem to be trying to claim that you ignored the refutations and their support because the editors supporting that view were passionate - that's absurd. Just because someone is passionate and/or points out and asks for others to address a comment that a significant plurality of editors not only addressed but agreed with (and in quite a few cases, changed their !vote after reading) does not make it bludgeoning, and even if it was bludgeoning, it does not make their opinions null and void. -bɜ:ʳkənhɪmez ( User/ say hi!) 00:36, 13 July 2024 (UTC)
I'm not a fan of panel closes either. The only concrete effect they seem to have is to make things take a lot longer. I also often get the feeling that the summaries suffer from the lack of a single author. Instead I'd encourage closers to make greater use of WP:DFD to workshop and solicit feedback on contentious closes before they post them. –  Joe ( talk) 11:43, 10 July 2024 (UTC)
  • For the concerns about backlogs noted above, I’m not sure mandating a panel closure for these long sorts of RfCs would be the best idea (having one person close it takes long enough, mandating that 3-4 negotiate a close would be a bit excessive) - that said, I’m supportive of mandating or strongly recommending that an uninvolved admin handle these closures. Yes, admins aren’t infallible, but it feels more appropriate to have someone who the community’s already entrusted with responsibility handle lengthy/contentious RfCs in CTOPs, rather than a normal user. The Kip ( contribs) 18:07, 11 July 2024 (UTC)
    The credibility of people like S. Marshall should be the least of our concerns here. Aaron Liu ( talk) 03:24, 12 July 2024 (UTC)
    I don’t have any opinion on the Telegraph RFC specifically as I didn’t participate nor have I read it - just giving my 2¢ on the proposal regarding large RFCs in CTOPs and such. The Kip ( contribs) 06:07, 12 July 2024 (UTC)
    We have many credible non-admin closers, so I don't think this is something we should "hunt down". Aaron Liu ( talk) 15:35, 12 July 2024 (UTC)
Also not a fan of panel closes. It's anecdotal, but I think the ratio of bad-closes/all-closes is worse for panel closes than individual closes. At the very least, anybody thinking about mandating panel closes in any situation should first gather some data about whether panel closes are any less likely to be wrong, challenged, or overturned, than non-panel closes. My impression is that Wikipedia has a lot of non-panel closes -- like dozens or hundreds or thousands, depending on the time scale -- and like less than 1% are wrong/challenged/overturned. Whereas Wikipedia has very few panel closes -- like single digits, maybe a dozen or two dozen in the last like 5 or 10 years? -- and a huge proportion of them (like half) are wrong, challenged, and/or overturned. But my anecdotal impressions aren't data; data would be useful. Levivich ( talk) 18:20, 13 July 2024 (UTC)
Any idea where to start looking to gather that data? Thryduulf ( talk) 18:35, 13 July 2024 (UTC)
It's not useful data to have. People don't even ask for panel closes unless it's really super-contentious, so it shouldn't surprise anyone that more panel closes get challenged or overturned (which I don't know if it's true, but it does seem likely to me).— S Marshall  T/ C 19:02, 13 July 2024 (UTC)
For individual closes, maybe Legobot's contribs, and/or the page history of WP:CR, to gather a list of RfCs/discussions. But then after that I don't know, seems like a difficult task to calculate the total number of closed discussions vs. how many of them were challenged (AN archives will find some official close reviews, but that wouldn't include those that never went past the closer's talk page).
As for panel closes, I don't even know... probably manually plucking them out of the gathered list of RFCs/discussions.
Overall it strikes me as something that would basically have to be done manually and would take many hours. For a single year, it's maybe doable, but that would leave a tiny sample size of panel closes (maybe low single digits). For this reason, the efficacy of panel closes may never be fully understood. Levivich ( talk) 19:29, 13 July 2024 (UTC)

Subpage?

At the time of typing we're just over 30,000 words. I'm minded to move it to its own subpage?— S Marshall  T/ C 13:51, 12 July 2024 (UTC)

Honestly, I think the relevant discussion has already run its course, and now it's mostly people just venting their personal dislikes of each side at one another. Probably better to just shut down the side discussions. — The Hand That Feeds You: Bite 20:21, 12 July 2024 (UTC)

I think it's worth adding that I read much of the discussion, researched some of the references given by the proposer, came the conclusion that they did not support what was claimed, saw that the inaccuracies had already been pointed out by other editors and decided not to contribute.

I'm now very confused. Since the allegations against the Telegraph were shown to be incorrect, I can't see how I could have added to the discussion according to Wikipedia practice, which is (or is supposed to be) don't simply repeat what has already been said. Perhaps the idea of consensus has now swung so far into the realms of "guess the majority" or perhaps it's "follow your political nose". The close to this RfC is not neutrally written - that's a shame. And it seems a political campaign has succeeded here, where it should not have.

All the best: Rich Farmbrough 23:48, 12 July 2024 (UTC).

Withdrawing deletion nomination

I have withdrawn the deletion nomination of a page, see this, an administrator must talk. Hamwal ( talk) 10:49, 10 July 2024 (UTC)

Given that two people have weighed in on the discussion with something other than a keep !vote, the nomination is no longer eligible for withdrawal. -- Blablubbs ( talk) 11:22, 10 July 2024 (UTC)
Well you can add a keep vote with reason and state that you are withdrawing your delete nomination. But that will not trigger close in this case. Graeme Bartlett ( talk) 12:29, 11 July 2024 (UTC)

Opinion sought

A small edit war occurred at LGB Alliance leading directly from the closure of The Telegraph reliability RFC. While no intervention is, at present, required, as parties appear to have stopped warring, two editors are under the impression that it is other editors who were edit warring, not them. There has been discussion of this, with diffs, at Talk:LGB Alliance#Dubious source and at User talk:Amanda A. Brant#Talk:LGB Alliance#Dubious source. As you can see from these pages, both I, BilledMammal and WhatamIdoing have offered our opinions and all of us have been rebuffed. Both Amanda and BilledMammal have thrown WP:EDITWAR at each other during the article talk page discussion. I'm including BilledMammal as among the participants of the edit war, as their edit was warring back to "status quo". Furthermore that "status quo" includes text sourced to The Telegraph, and therefore aligned with BilledMammal's position being very upset about the Telegraph RFC closure, and they had not previously edited this article or talk page.

I would appreciate an admin/admins who will be respected as neutral by all participants (i.e. not those whose position wrt trans/GCF topics is well known and can therefore be rebuffed as biased by one party) to briefly describe what occurred in terms of our Edit warring policy. No editor even remotely reached 3RR. This is simply about what edit warring is, what constitutes participation in that war, not whether their edit warring needed sanctions or whether the content or absence of content was correct. I'm hoping for enlightenment and better future behaviour as a result, rather than anyone to get into trouble. -- Colin° Talk 13:43, 10 July 2024 (UTC)

(Non-administrator comment) Whatever the result of the review above that's a misinterpretation of WP:MREL. Marginal or disputed reliability is not the same as WP:Generally unreliable.
This was edit warring, reverting reverts of other reverts, even multipole editors only each reverting once could still constitute edit warring. After WP:3RR editors may very well get blocked, but that's not a reasont to get right up to that point.
As with most issue more discussion on the talk page, and less in edit summaries, would likely solve the problem. -- LCU ActivelyDisinterested « @» ° ∆t° 14:45, 10 July 2024 (UTC)
Small correction; I didn't say that Amanda was edit warring - while if they had reverted again I think they would have crossed the line, as it was I don't think that was one of the issues with their conduct there. BilledMammal ( talk) 19:53, 10 July 2024 (UTC)
You're comment "I’m just here because people are misusing RSP. I’m not interested in joining the discussion beyond objecting to that." might as well have read "I'm only here to join the edit war". CNC ( talk) 20:04, 10 July 2024 (UTC)
I disagreed with the specified reason for removal - you can't remove a source on the grounds of unreliability if you're not actually claiming that its reporting is incorrect. Editors later raised other reasons for removal, and I wasn't interested in getting more involved in the discussion.
This isn't an unreasonable position, per WP:SATISFY and WP:VOLUNTARY. Editors are allowed to address one issue without becoming permanently involved in a dispute. BilledMammal ( talk) 20:10, 10 July 2024 (UTC)
Your argument has helped to confirm my suggestion as now you are trying to justify your reason for edit warring, rather than any acknowledgement that is was the wrong action: you made no attempt to avoid edit warring and your revert wasn't necessary. On 9 July, you joined the edit war with Amanda A. Brant, reverting at 15:18 [17], making your first comment on the topic 5 minutes later. [18] This is a clear case of "revert first, ask questions later". Then at 16:50 after stating "I’m just here because people are misusing RSP. I’m not interested in joining the discussion beyond objecting to that. [19], failed to revert your edit. I say "failed" because once you no longer claimed to have an issue with the removed content based on the argument presented by YFNS, you let your revert stand. It seems you've ignored the concerns Colin has raised in this topic. CNC ( talk) 11:43, 11 July 2024 (UTC)
Where's the problem? Someone removed an unreliable source from a page. Fairly reasonable thing to do. LilianaUwU ( talk / contributions) 19:58, 10 July 2024 (UTC)
WP:MREL is not WP:GUNREL, I'm shocked you haven't understood this yet. Likewise regarding edit warring and WP:BRD. It's unfortunately got to the point where an admin needs to explain to you the basics. CNC ( talk) 20:02, 10 July 2024 (UTC)
Fair enough, MREL is not GUNREL. But if a source isn't appropriate (as in here), it shouldn't be used. LilianaUwU ( talk / contributions) 20:14, 10 July 2024 (UTC)
Even if the source isn't appropriate, editors shouldn't be edit warring over whether it should be used (in that place, in that way). The dispute involves the repeated removal and restoration of this sentence:
  • "The organisation has said that lesbians are facing "extinction" because of the "disproportionate" focus on transgender identities in schools."
along with one out of the seven uses of this source in the LGB Alliance article:
The first sentence of the source says:
  • "Lesbian are facing “extinction” because of the “disproportionate” focus on transgenderism in schools, a controversial campaign group for gay rights has claimed."
which could perhaps be faulted on grounds of Wikipedia:Close paraphrasing, but I think it is inarguable that the cited source WP:Directly supports the statement which it was being cited for.
I think this ought to proceed as an ordinary content dispute over whether the organization in question actually did espouse this POV, and (if so) whether that fact is DUE for the lead or should only be placed lower in the article. I don't think this should be considered a dispute solely about whether a source that is still used six other times in the article is inappropriate for citing a seventh time.
Also, I don't think that we should be thinking about this in terms of "sides". An editor who seems to oppose everything this organization stands for has removed damaging information about that org from the lead. Their PR team is probably very happy with her right now. WhatamIdoing ( talk) 20:42, 10 July 2024 (UTC)
This is not just about the fact that The Daily Telegraph is no longer considered "generally reliable" on transgender issues and gender-critical views, and was listed as yellow on Wikipedia:Reliable sources/Perennial sources. There is a nuanced discussion of whether it is appropriate in the specific context (which I addressed) and whether it is WP:DUE in the first paragraph (whether the source is good enough in the specific context is part of that discussion). As I explain on Talk:LGB Alliance, I have reverted exactly once, and only after offering a detailed rationale on the talk page that the other party did not respond to, after being given an opportunity to do so. That is not edit-warring. That is normal editing. Pretty much all the other participants in the discussion routinely do the same thing. I don't think the most recent edit by User:Barnards.tar.gz that basically reinstated my edit with some tweaks is edit-warring either. There now seems to be general agreement to remove the material in question. The only really unacceptable behavior in relation to this minor incident was the abuse of templates and personal attacks by one editor. -- Amanda A. Brant ( talk) 20:37, 10 July 2024 (UTC)
Depending on where one chooses to start counting, you have reverted either once or twice. The question here isn't really "Did User:_____, personally and individually, do anything that should be punished?" The question is more like "Do we have one of those situations in which editors [note the plural] keep flipping back and forth between the same two versions of the article?"
If you click through the relevant diffs ( [12] [13] [14] [15] [16] [17] [18]), then I'd say we have an edit war, even if no single individual has broken any bright-line rules. WhatamIdoing ( talk) 20:46, 10 July 2024 (UTC)

- Just to say that I did ask for neutral admin (or experienced user) to comment as a third opinion, not for existing participants to continue to argue whether they did or did not edit war, or for folk to offer their opinions about which warring edit was the right one. I think such a wise authoritative voice would still be very welcome, as editors are continuing to argue they were not edit warring because they were Right and everyone else was Wrong, on the article talk page. -- Colin° Talk 21:46, 10 July 2024 (UTC)

It does look like an edit war, at least the early stages of one. Unofficially, I'd encourage all parties to stop reverting and discuss on the talk page. That's exactly what happened, so I don't think it needs to go any further at this point. The rest seems like a content dispute which isn't really suitable for WP:AN. The Wordsmith Talk to me 21:55, 10 July 2024 (UTC)
  • I would be more concerned about the reliability of anything written by Camilla Tominey (stick "Camilla Tominey trans" into Google and have a look at that - don't bother looking at the hagiography that is Camilla Tominey) rather than the fact she happened to write it in the Telegraph. And as far as I can see, regardless of its source, it certainly isn't WP:DUE in a lead paragraph. As a second point, articles such as LGB Alliance are covered by WP:GENSEX so I'd suggest that editors who are pushing their POV consistently across multiple noticeboards and articles have a think about where pushing too hard ad nauseam might lead. Black Kite (talk) 07:23, 11 July 2024 (UTC)
    Can we please not have comments on the content/sources. Go to the article talk page if you want to do that. The concern here is some editors are unaware (or unwilling to accept) what constitutes edit warring. The actual topic is irrelevant. -- Colin° Talk 11:41, 11 July 2024 (UTC)
    No, the issue here is the material, that was dubious from the start (dubious in the sense that its use in the first paragraph unduly promoted a biased narrative), and that has in fact been removed from the article by various editors. This harping on a supposed "edit war" after a couple of editors "reverted" exactly once each – in my case with a detailed justification and rationale that the other party had been given an opportunity to respond to, and in Barnards.tar.gz's case to attempt some sort of compromise, that now seems to be widely accepted by everyone – is not productive use of our time. -- Amanda A. Brant ( talk) 16:03, 11 July 2024 (UTC)
    I appreciate the uninvolved parties offering opinions, so I don't want to rehash all this and I won't add any more than this, but as "the other party" I would like to offer context as I saw it.
    • The page in question is exceptionally hard to attain consensus on for any changes, due to the divisive nature of the subject
    • The content we're talking about has been in the lede unchanged for (I believe) couple of years
    • The change you wanted, you justified based on an updated note on The Telegraph on Perennial Sources that was barely 2 hours old at this point, after a lengthy and polarising RFC we were both involved in, on opposite sides
    • You used this very recent change not only to argue in talk for this removal, wrongly claiming that the Telegraph was WP:GUNREL and should not be used, but also elsewhere on that talk that it should not be usable WRT other disputed neutral wording in the lede
    • Your rationale, aside from being a misreading of the note, cast aspersions about essentially the entire UK media
    • When I pointed out you were overstating things, you replied with what was a restatement of the same claim. At this point, my impression was we were at loggerheads, so wait and see if someone else weighs in. I don't see the point in repeating myself ad nauseum.
    • When you then reverted my revert, it was 2:30am my time. I'm sorry but I don't keep tabs on this 24/7, nor do I see the desperate urgency to remove ancient content such that it cannot be discussed by more editors first.
    • When your change was reverted to restore the status quo ante, I was personally glad of an uninvolved intervention and considered it a call to actually discuss the change per BRD, which I felt your revert had not been in the spirit of. However, with the issue subsequently being raised here as an edit war, I now see things like WP:DONTREVERT say Wikipedia does not have a bias toward the status quo so I guess my understanding of norms about this sort of thing are not correct. Every day is a school day, and I'll certainly bear this in mind in future.
    • FWIW, I have since chucked my 2p in on talk after the fact and endorsed the actual change as subsequently performed by Barnards, for the rationale that emerged on talk which I agree with, but I do understand the concerns about the process.
    At this point I think, despite how it was arrived at, there is actual unanimity about the content, which on that page is a cause for either celebration or to check its not April 1st. Void if removed ( talk) 21:50, 11 July 2024 (UTC)

Scott's use of revision deletion

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Scott ( talk · contribs · blocks · protections · deletions · page moves · rights · RfA)

Hello. Following discussion on Scott's talk page, I am asking for review of Scott's revision deletions. Despite another administrator and I attempting to explain that RD3 should not be used for all vandalism, Scott has misrepresented previous consensus (the discussion specifically stated that "it was also generally agreed that most vandalism was out of scope for RevDel"), changed the text of policy to suit their interpretation of it, and responded to the other administrator's concerns with " my God, stop being so melodramatic ... This is absolutely pathetic".

Much of Scott's revision deletions have been of run-of-the-mill instances of vandalism from years ago, such as ' When people eat Pringles, it is very yummy according to the people who eat/ate it', ' WORST WEB PAGE ON THE WEB "LULZ!"', and keysmashing. As revision deletion should not be used for such "basic" instances of vandalism, they should be undone. I would also point out that the tone of responses have been deeply disappointing. Thank you, Sdrqaz ( talk) 21:39, 11 July 2024 (UTC)

Accusing me of "spamming the logs" by deleting (hiding) 3 revisions is melodramatic and doing so as a transparent attempt to get me in trouble (based on an idiosyncratic personal interpretation of long-established policy) is pathetic.
I already responded to your concern on my user talk page where you raised it, to remind you that "purely disruptive material" is the definition of WP:RD3 as established community practice, and the last RfC on the topic ( Wikipedia:Requests for comment/Clarification of RD3 in 2011) failed to establish otherwise.
You accuse me of "changing the text of policy to suit my interpretation" when in fact, I simply corrected a contradictory statement in the preamble (which you highlighted) which had been sitting there invalidating every RevDel criterion except RD2 since 2009. Obviously, nobody interpreted it literally enough to prevent them from using any of the other criteria, but it does seem to have been sufficiently confusing to cause you to think that it should.
As I said to you before, if you disagree with the definition of RD3 then the appropriate place to gain consensus for a change is WT:Revision deletion.  — Scott talk 21:52, 11 July 2024 (UTC)
Do not endorse. Those are definitely not suitable uses for revision deletion. There's a reason why "vandalism" isn't one of the examples provided for RD3: includes harassment, grossly inappropriate threats or attacks, browser-crashing or malicious HTML or CSS, shock pages, phishing pages, known virus-proliferating pages, and links to any of these or to web pages that disparage or threaten some person or entity and serve no valid purpose. More concerning, though, is Scott's attitude towards this. When someone asks on your talk page why you decided to take admin actions, calling their concern "absolutely pathetic" is not acceptable. — Ingenuity ( t •  c) 21:59, 11 July 2024 (UTC)
Perhaps you could explain how the diffs provided above are not describable as "purely disruptive material"?
Also I'll thank you not to misrepresent my words - aggressively accusing me of "spamming the logs" is what's pathetic, rather than civilly opening a talk page conversation over the interpretation of RevDel criteria. I choose not to be bullied, thanks.  — Scott talk 22:09, 11 July 2024 (UTC)
The only person who was aggressive in that conversation was you. And you think that this is bullying? Wow. — Ingenuity ( t •  c) 22:18, 11 July 2024 (UTC)
What kind of topsy-turvy world is it where someone comes into your talk page yelling about at you that you're "spamming" and standing up for yourself in the face of that makes you aggressive?
Anyway, I guess you're choosing not to answer my question.  — Scott talk 22:21, 11 July 2024 (UTC)
Until you changed it earlier today, the revdel policy also stated that "material must be grossly offensive". Maybe RD3 should now be renamed to "purely and grossly disruptive material". — Ingenuity ( t •  c) 22:41, 11 July 2024 (UTC)
The "misuse" section of the preamble, not the criteria themselves which define the use of revision deletion, said that for revision deletion to be used, the "material must be grossly offensive". As I have pointed out multiple times now, that invalidates every single criterion except RD2. Somehow nobody noticed that since 2009 the revision deletion policy has been contradicting itself.  — Scott talk 22:54, 11 July 2024 (UTC)
From a review of his last 10 revdel's, Scott seems to understand RD2, but doesn't seem to understand RD3. We have never revdel'd run of the mill vandalism, and we certainly don't revdel 20 year old run of the mill vandalism. Contrary to Scott's claim, doing so is not long-established standard practice. I also agree with Ingenuity above that Scott's snarky attitude in response to a very reasonable request is unjustified. If he's just having a shitty day, then it's not a big deal; I've acted like a jerk when I'm having a bad day too. But it should stop, as should the RD3 revdels. Floquenbeam ( talk) 22:06, 11 July 2024 (UTC)
Hello Floq. If you're going to make a sweeping statement like "we have never... and we certainly don't..." then perhaps you could contribute some evidence towards that, perhaps in the form of a written policy which explicitly supports your interpretation, or a discussion which established consensus?
Regarding snark, if someone comes onto my user talk page with a shitty attitude then what do you expect? Come on now.  — Scott talk 22:14, 11 July 2024 (UTC)
Per above. RD3 is not for regular vandalism. These deletions should be reversed. – bradv 22:13, 11 July 2024 (UTC)
( edit conflict) Scott, I think you're the admin with the idiosyncratic view of what RevDel covers. Run-of-the-mill vandalism is reverted, not revdeleted. I don't believe the community has or ever would explicitly agree for it to be used this way, especially on lame throw away edits from years ago.-- Ponyo bons mots 22:14, 11 July 2024 (UTC)
Hi Ponyo. If you look at the RfC I linked to above, it was noted in the closing summary that "The overriding agreement appears that admin discretion still has strong support in these cases. But it was also generally agreed that most vandalism was out of scope for RevDel." [Emphasis in original.] Most vandalism certainly is out of scope, and I've used my discretion to hide a minority of purely disruptive rubbish that has no place on public view. This is in keeping with both the written policy and consensus as previously established.  — Scott talk 22:19, 11 July 2024 (UTC)
I don't see how the deletions highlighted by Sdrqaz cross the line between basic vandalism and "purely disruptive rubbish". It's just childish scrawling in comparison to the grossly inappropriate edits REVDEL is meant to cover. I think you have it wrong in this specific instance.-- Ponyo bons mots 22:28, 11 July 2024 (UTC)
Are you saying that basic vandalism isn't purely disruptive? Then what is it? Genuine question.  — Scott talk 22:31, 11 July 2024 (UTC)
If the community had as broad an interpretation as you as to what is purely disruptive, the policy would simply state that any vandalism is fair game for revision deletion. I repeat what I said above, the community would never approve such a liberal use of the tool. You appear to have dug in here; I'm not sure if there is any point in debating further. You are using an admin tool in a way that is not approved by the community and, based on your replies here, don't appear open to considering you may be incorrectly applying RD3. I really hope I'm wrong. You don't have to agree, but please consider that you might have it wrong.-- Ponyo bons mots 22:49, 11 July 2024 (UTC)
I'm open to considering it - that's exactly why we have collective discussions to elaborate upon and refine policies. You say "the community would never approve" - to add to what I've just said below to Floquenbeam, policy is set by what the community did approve. This seems like the perfect opportunity for another RfC on the topic to get the current consensus formalized, and ideally reflected in a well-written and unambiguous criterion to be understood and followed by all.  — Scott talk 23:15, 11 July 2024 (UTC)
Discretion is for borderline cases, it is not limitless. Just because you're an admin does not mean that you can do whatever you want because you have "discretion". Every admin who comments here is going to say they don't routinely revdel this stuff. That needs to mean something to you. If people revdel'd only stuff 10 times as bad as that, our revdel logs would still increase by several orders of magnitude. There are easily 100 more vandal edits on that page just as bad, and that's only one page. Among other reasons, we limit the use of revdel because non-admins can't tell what's going on, and that's a bad thing. We should only do it when removing the material being revdel'd is a bigger benefit than the cost of hiding revisions. More importantly, "Scott vs. All You Insane People" is not an appropriate approach. Consider the possibility that you drastically mistook the tone of the original message. I can assure you, for what it's worth, that you are the one who appears unreasonably aggressive there, not Sdrqaz. Floquenbeam ( talk) 22:32, 11 July 2024 (UTC)
Try reading what I wrote again. Sdrqaz's message to me was absolutely fine. I was talking about Thryduulf.
Anyway, regarding your comments - you've just illustrated how our admin corps aren't doing enough to suppress vandalism. I doubt that you could quantify "the cost" as it's entirely nebulous. Your argument also doesn't hold up - regular admins can't see what the higher level ones with oversight have hidden, and that's not a "bad thing" even though it's far less accountable.  — Scott talk 22:44, 11 July 2024 (UTC)
Ah, my mistake, I thought Sdrqaz started the thread on your talk page, his was just the last comment there. It is starting to make more sense why you assumed Thrydulf's initial comment was an attack, you had a recent run-in elsewhere. Anyway, you started out saying Thyrdulf was out of touch with long established procedures. Now the whole admin corps is out of touch with long established procedures? That's kind of impossible by definition. I will never understand why people can't just say "OK, my thoughts on this are apparently different than the consensus, so I'll suck it up and change what I do." Floquenbeam ( talk) 22:54, 11 July 2024 (UTC)
What can I say here? There are apparently loads and loads of people who seem determined to interpret one of our policies in their own way rather than following it to the letter as written, and their response to that is to do everything except take to the policy venues to clarify what exactly an ambiguous policy really means and establish a firm consensus. You say "long established procedures" and "the consensus", but so far nobody has managed to produce a single written record of these that trumps WP:RD3, which itself would be different as a result of such a consensus, by definition. 🤷🏼‍♂️  — Scott talk 23:07, 11 July 2024 (UTC)
I think we're probably done here, we're just going around in circles. Ingenuity answered your question. There is more to RD3 than the initial wording; the followup clarification counts too. Ponyo answered your question. And you don't need policy to determine "long established procedure", instead you look at what all the other admins have been doing long term. By definition. A bunch of non-Thryduulf admins have told you that no one interprets this the way you do. I don't think anyone is asking for grovelling, but if you continue to misuse RD3, someone is probably going to take you to ArbCom for misuse of the tool. You don't have to agree, but you should be aware. Floquenbeam ( talk) 23:14, 11 July 2024 (UTC)
I am aware, and I'm waiting for the one single person who actually cares about procedure enough to fix this weak criterion by kicking off the process which establishes consensus to narrow the wording. Until then, everything is just "well I think it means".  — Scott talk 23:18, 11 July 2024 (UTC)
If you decide to do this, please let me know. Floquenbeam ( talk) 23:26, 11 July 2024 (UTC)
I closed Wikipedia:Deletion review/Log/2024 June 28 recently and was struck by both Scott's tone (e.g., In summary, get stuffed.) and the fact that the deletion was unanimously overturned. I'm concerned that this is more than just a one-time issue. Extraordinary Writ ( talk) 22:15, 11 July 2024 (UTC)
Ah yes, when Thryduulf chose to call me a liar in public with absolutely zero consequences. I guess having been on ArbCom gives you a free pass exempting you from WP:AGF right? I can think of a whole bunch of people here who'd have responded with something far more fruity than "get stuffed".  — Scott talk 22:28, 11 July 2024 (UTC)
Perhaps the fact that not a single other person has taken issue with my describing intentionally leaving incorrect deletion summaries as "lying" should cause you to reflect that it actually is? Thryduulf ( talk) 22:53, 11 July 2024 (UTC)
Now that I see it, I take issue with it. For what it's worth. But Let's stay on track here. Floquenbeam ( talk) 22:58, 11 July 2024 (UTC)
If it isn't lying, what is it? Thryduulf ( talk) 23:01, 11 July 2024 (UTC)
Oh stop it. "Lying" has connotations that do not apply to every instance of "intentionally leaving incorrect deletion summaries" (note that I have no idea if even that is true, but assuming it is for the sake of argument), and you know it. You've been around long enough to know that calling someone a liar basically shuts down future legit discussion. Case in point: if anyone else had left an identically worded initial message on Scott's page, Scott possibly would have interpreted it differently, and maybe we wouldn't even be here. Floquenbeam ( talk) 23:08, 11 July 2024 (UTC)
Thank you.  — Scott talk 23:16, 11 July 2024 (UTC)
That's your response? Just doubling down? Absolutely incredible. Well, at least everyone can see your true colours.  — Scott talk 22:58, 11 July 2024 (UTC)
  • I do hope that we're not going to spend volunteer time on undeleting blatant vandalism for procedural reasons.— S Marshall  T/ C 22:40, 11 July 2024 (UTC)
    Yes, that would be silly. I'd be satisfied if the unnecessary RD3 revdel's just stop. Floquenbeam ( talk) 22:42, 11 July 2024 (UTC)
    ( edit conflict) I certainly wouldn't want to mandate that (or even recommend that), but if someone chooses to spend their time reversing out-of-process deletions I'm not going to spend my time complaining about it. Thryduulf ( talk) 22:52, 11 July 2024 (UTC)
  • I'm glad it's not just me who feels that these RD3 deletions were incorrect, in isolation not badly enough to merit more than a note that they have misinterpreted the deletion policy. However the tone of their responses here, on their talk page and in the recent DRV are grossly inappropriate. If they don't start listening then we'll have no choice but to go to arbcom and that would be a real shame as most of their admin work is correct and good, but the communication is that big a deal. Thryduulf ( talk) 22:52, 11 July 2024 (UTC)
  • This sort of revdel, if it were to become commonplace, would be highly disruptive to those of us who create edit filters, and for that matter, to the thousands and thousands of people who patrol recent changes. We need to see the big picture. We need to see patterns of vandalism. What's common enough to warrant a filter? What are the "tells" of that sneaky LTA? If everything disappears behind a struck-out diff, then we're just left reacting to what's in front of our nose. Now revdel is, sometimes, a necessary evil. The libeled BLP subject doesn't care about any of this, nor should they. But if you can't answer the question "what harm will come if J Random User views this diff?" the diff probably should remain visible. Suffusion of Yellow ( talk) 23:19, 11 July 2024 (UTC)
    Thank you for making a contribution to this debate based upon actual, quantifiable reasons. Although the instances of RD3 under discussion here were in application to 20-year-old vandalism, I'll commit to cease using it in such a fashion specifically on the basis of your demonstrated need, rather than that of the kind of unprovable assertions about the "true meaning" of a policy we've been seeing until now.
    As a side note, your comment completely demonstrates that the permissions you have are insufficient for the job. Filter managers should be able to see deleted revisions. Yes, I know the WMF's position on who gets that permission and I don't agree with it.  — Scott talk 23:49, 11 July 2024 (UTC)
    @ Suffusion of Yellow and Scott: On just the strict idea of what the WMF requires for access to deleted revisions, filter managers already arguably go through an election process (2 in fact, usually, since most filter managers have gone through an EFH consensus process as well). Now, I expect the idea of adding viewdeleted to EFM would likely end up mired in debate since it isn't necessarily RfA-level given there's usually only 10 people who actually follow the notice links that get posted to noticeboards whenever someone puts a candidacy up as a non-admin, but as a theoretical I somewhat wonder about the practicality of whether an RfC to add the rights would succeed. I guess that's a bit off-topic for this AN thread, though it would certainly help given that RevDelling revisions essentially roadblock any non-admin from building a filter regarding it. EggRoll97 ( talk) 04:25, 13 July 2024 (UTC)
    For a long time there was a bug where even admins couldn't see filter logs corresponding to revdelled edits! Not sure if that's been fixed. Suffusion of Yellow ( talk) 00:02, 12 July 2024 (UTC)
    Yikes. Well... I have minor feature requests for our admin tools on Phabricator which are old enough to go to secondary school now, so the pace of development in that area really isn't helping.  — Scott talk 00:22, 12 July 2024 (UTC)
    Hmmm, seems fixed now at least on testwiki. Suffusion of Yellow ( talk) 00:38, 12 July 2024 (UTC)
Do not endorse. 61 edit summaries in a row of all caps FUCK YOU FUCK YOU FUCK YOU.... maxing out the edit summary length is purely disruptive. Changing a redirect to HAGGER???? is normal vandalism. -- SarekOfVulcan (talk) 23:57, 11 July 2024 (UTC)
  • What I'm seeing here is an administrator who's not interested in using the tools on behalf of the community, but instead based on their own whims, and responds by attacking anyone who challenges their actions. Seems like a case of "would not be trusted with the tools if their RfA were today", but that's the nature of lifetime appointments. Even in the 2007 RfA, the support/oppose ratio dropped significantly based on temperament concerns. Thebiguglyalien ( talk) 00:15, 12 July 2024 (UTC)
    Cool attacks on my character! 👍🏻  — Scott talk 00:23, 12 July 2024 (UTC)
  • Quite apart from any questions about (mis)interpretations of RD3, I'm just perplexed why anyone would be concerned about vandalism from 20 years ago. Editors can focus on what they want--it's their time, after all--but why was this considered a priority over vandalism from, say, 20 minutes ago? That's by far the oddest part of all of this to me. Is it deliberately to make a point about the RD3 wording? I'm genuinely mystified. Grandpallama ( talk) 00:28, 12 July 2024 (UTC)
    "Why was this considered a priority over vandalism from, say, 20 minutes ago?" It wasn't. You do know that not everyone is patrolling things, right? I use tools exclusively in the areas that I'm working in.  — Scott talk 00:38, 12 July 2024 (UTC) P.S. I'll choose to ignore that intimation of bad faith on my part.  — Scott talk 00:40, 12 July 2024 (UTC)
    There was no intimation of bad faith; there was genuine puzzlement about why you would be concerned about something that is, by internet standards, ancient. What was the purpose? You didn't actually answer that question, you just responded with more snark. Whatever, I guess. Grandpallama ( talk) 02:24, 12 July 2024 (UTC)
    That wasn't snark. And regarding bad faith, you literally suggested the possibility that I was purposefully making a point violation. So yeah, whatever.  — Scott talk 10:42, 12 July 2024 (UTC)
    You do know that not everyone is patrolling things, right? is unambiguous snark. -- JBL ( talk) 18:00, 12 July 2024 (UTC)
    No, it isn't. Maybe spend less time on the angry noticeboards so they don't color your reading ability so much.  — Scott talk 18:18, 12 July 2024 (UTC)
    With all due respect, I think you may be dealing with a different definition of 'snark' than some of us. Cheers. Dumuzid ( talk) 18:25, 12 July 2024 (UTC)
    Astonishing. -- JBL ( talk) 18:48, 12 July 2024 (UTC)
I noticed one of the revdels on a page I worked on and it was a completely disproportionate reaction to juvenile harmless vandalism that took .2 seconds to revert. I don't get why, that's very clearly not what RD3 is written to mean (or else why would it except "most vandalism??"), so I have no idea what the motive even is here. What is the point of this except needlessly cutting parts out of the page history?
Of course if it's harassment-based vandalism that's a different thing, but I really don't think this is what RD3 is used for or meant to be used for. I prefer when page history is intact unless there is a dire need for revdel. PARAKANYAA ( talk) 00:47, 12 July 2024 (UTC)

I think all we're looking for from Scott is an acknowledgement that their interpretation of RD3 is out of step with current practice and that they'll change their approach going forward. This shouldn't escalate, and shouldn't have gotten this far in the first place. It's okay to be wrong and it's okay to admit it. Mackensen (talk) 00:41, 12 July 2024 (UTC)

Kindly read my response to Suffusion of Yellow. Thanks.  — Scott talk 00:46, 12 July 2024 (UTC)
I have to agree with Mackensen here, I think we just need a small change of perspective and maybe a little more time to do some calm learning. The defensiveness is a bit too far, but I'll hope that Scott is a little less aggressive in the case that a similar case occurs in the future. We all could take to heart a commitment to take things slower and more-open mindedly, myself included. The Night Watch (talk) 17:23, 13 July 2024 (UTC)

@ Scott: Perhaps this will help clarify the issue: how do you decide which vandalism (recent or old) warrants rev-deletion and which does not? Thanks, Newyorkbrad ( talk) 00:50, 12 July 2024 (UTC)

Short answer: vibes. Longer answer: gut feeling on on a combination of the questions "is there more than a fractional chance that this vandal would be motivated to return later to see the mess they made?" and "how annoying was the vandalism?" and "how jarring to the experience of someone looking through page history would it it to see the vandalism?"
Anyway, per my response to Suffusion of Yellow, this is now moot.  — Scott talk 00:57, 12 July 2024 (UTC)
Thank you for the quick response. I agree that Suffusion of Yellow made an important contribution to this discussion. Newyorkbrad ( talk) 01:01, 12 July 2024 (UTC)
No worries. It's 2am here (which to be fair is when I sleep a lot of the time anyway), so I hope that by the time when I check back in tomorrow there won't be lots more people who piled on without having read that.  — Scott talk 01:17, 12 July 2024 (UTC)

I'm hopeful that Scott's comment, "I'll commit to cease using it in such a fashion" will be enough for those who were looking for just such a commitment. After the dust settles a bit, we should have a discussion about the wording of our RD policy, as the "must be grossly offensive" line that Scott changed does in fact need some changing. If someone starts that up before me, I'd appreciate a ping. Firefangledfeathers ( talk / contribs) 01:17, 12 July 2024 (UTC)

My hope for settled dust was too optimistic, and the discussion has started already. Anyone interested should pop on over to WT:REVDEL#"Material must be grossly offensive". Firefangledfeathers ( talk / contribs) 02:06, 12 July 2024 (UTC)

I suggest we close this. As noted above, Scott has said he'll stop doing this. Editing WP:REVDEL to support his position was probably a troutable offense, but let's all just take a deep breath and move on to something productive. If Scott is true to his word, then no more need be said. If not, then we can take things from there. I would close this myself but the close script I use was thursday'ed a while back and I've long since forgotten how to close these things the manual way. If people want to get hot and bothered, breaking essential scripts might be a place to start. RoySmith (talk) 01:47, 12 July 2024 (UTC)

That's what I would have said a week ago at DRV, when there was the same level of aggressiveness/incivility in defending an action everyone agreed was well out of bounds. But now the same thing has happened again, just with a different policy. I guess it's good that Scott is going to defer to Suffusion of Yellow's demonstrated need, but I'm far from convinced that we're not just going to end up back here soon with a different form of the same problem. Hopefully I'm wrong. Extraordinary Writ ( talk) 03:36, 12 July 2024 (UTC)

I just came upon this thread during my daily skim-reading of these boards. I have a fairly unusual perspective here. Scott and I have talked about wiki-archaeology many times over the years and I actually had a discussion with him about this very issue back in 2022 (search for "That's actually led me to something else"). We were talking about the page Wikipedia:Deletion log/28 February – 19 July 2002 (then at the title Wikipedia:Old deletion log); here's the relevant diff and the log of revision deletion/undeletion. I'm relatively extreme about trying to preserve edits where possible and 100% agree with Suffusion of Yellow here, for slightly different reasons, and am glad that Scott has agreed to change his practices here. Graham87 ( talk) 04:29, 12 July 2024 (UTC)

Yeah. I mean setting aside the discussion about the letter and spirit of the law, you can boil down the whole issue to one of our software not being good enough. I think that vandalism should be hidden away (not "deleted" - the fact of the system being called "revision deletion" is just one of many issues with it) for two reasons: to deny recognition to vandals, and to minimize disruption to people reading page history. RevDel as it exists today is a crude and blunt tool with almost no nuance whatsoever. You have two options for a given unit of data (actor, revision text, edit summary) - leave it on public view, or punt it into the Phantom Zone where only admins can read it. There's no gradation that can be applied when hiding revisions.
By contrast, consider a system where applying, for example, RD2 would make an item inaccessible to anyone without elevated privileges, but RD3 would hide it behind an additional interface element until a button is clicked. Minimal visibility for disruptive material without presenting any barrier to edit filter managers, recent changes patrollers, etc. This isn't a new idea at all: various social media apps have had it for a long time in the form of "hidden replies". Even in the current system, we could unbundle the right to see hidden revisions and give it to reasonable interested users so that staying tidy doesn't impede research. I believe this actually was the case with the "researcher" user group until the WMF nixed it for some reason? I didn't hear about it until afterwards.
Similarly, other objections raised above included noise in the logs... once again utterly trivial to resolve technically. But the WMF has chosen to spend its giant budget on "increasing engagement" features, and leave our tools languishing pretty much exactly where they were fifteen years ago. The sheer amount of precious human time wasted by having to both use our incredibly out of date tools and debate extensively about the way to use them because of how crude they are is heartbreaking.
By the way, it's "them" now rather than "him". 😊  — Scott talk 10:32, 12 July 2024 (UTC)
Sorry about the misgendering. Revision deletion is a great improvement on what was previously the only option, selective deletion. You were editing Wikipedia (but not yet an admin) when even that wasn't an option. This is the wrong place to debate the merits of hypothetical revision hiding options, but I don't really see the use of such gradation; I'd maintain that most people don't even look at page history and many readers understand that minor vandalism is often part of the life-cycle of Wikipedia pages (we even have a main namespace article on the topic). Graham87 ( talk) 14:36, 12 July 2024 (UTC)
No need at all to apologize. Yeah, I'm sure there's a better venue to talk about it than here. But you're quite right in that selective deletion was a massive pain in the neck and RD's arrival in 2009 really helped. Just now that we're 15 years down the line, I personally reckon it's overdue for a rethink based on lessons learned.  — Scott talk 18:11, 12 July 2024 (UTC)

IMO there was a problem of too broad of use of the tool and Scott has agreed to change accordingly. I think we're done here. North8000 ( talk) 18:26, 12 July 2024 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Some Help with Bot-Like Editing

I ran into OpalYosutebito with this edit. They were trying to address a citation error by removing |agency= from {{ Cite journal}}, but also removed all other |agency= parameters from the other citation templates (which are valid parameters in those templates). I reverted and left a message, but then looked at the user's edits and saw what appears to be an abuse of AWB with bot-like editing. Over a recent 40 minute period, they completed 499 edits making AWB changes to unsupported parameters (about 12 edits a minute). However, looking at these edits, they are either making mistakes (like the one I noted above or this one) or are removing valid reference material from the citation template that should be fixed, not outright deleted. As an example this edit, the template should be changed to {{ Cite news}}, which would correct the issue while retaining the correct parameter. There appears to be hundreds, if not thousands of recent edits that could be introducing issues like this. My gut says they all just need to be outright reverted. I removed the user's AWB privileges for now and was close to blocking for running an unapproved bot, but just don't have the time to dive into this anymore today. Can another admin take a look and review my actions so far, and take additional ad warranted? Thank you! « Gonzo fan2007 (talk) @ 15:25, 12 July 2024 (UTC)

(Non-administrator comment) Checking OpalYosutebito's contribs, they appear to have begun self-reverting, which is certainly called for. Unsupported parameters in citation templates almost always contain valid bibliographic information, and are usually the result of bot action, template updates, or translations from a sister project. Just removing them rather than attempting to incorporate the information properly into the citations is incredibly destructive.
I'll keep looking, if I can remember, since an AWB run this ill-conceived and deleterious may require a mass rollback while the edits are still fresh. Folly Mox ( talk) 23:29, 12 July 2024 (UTC)
(Non-administrator comment) I'm about halfway done with fixing the mistakes I made. They're my errors, my responsibility - OpalYosutebito ( talk) 22:29, 13 July 2024 (UTC)

98.115.164.53's Numerous Minor Edits

98.115.164.53 ( talk · contribs · WHOIS)

This editor has made numerous minor edits to articles. Most of them seem innocuous, but others, particularly the ones that remove terms like "to date," seem problematic for contextual POV. There seem to be hundreds of account-less edits, despite the suggestion to create an account already being made, but what do I know.

This user made a personal attack [20] after I reverted their edit on a page I had watchlisted. And then they put their edit back [21].

So far, they seem to have stopped editing for now, after being warned. I've gone through some edits to see what edits can go or stay, but they're just too numerous. Anyone have thoughts on what to do next?⸺ RandomStaplers 19:57, 12 July 2024 (UTC)

You could ignore the user and move on. If the edit is truly problematic, you could revert it anyway, and/or you could ask an administrator to protect the page. 98.115.164.53 ( talk) 20:08, 12 July 2024 (UTC)
What of the middle line in the report, the one where they say that they did revert one of your edits and you personally attacked them back and restored your edit?
Also, are you saying that the way to stop you from making problematic edits is to protect the pages you're being problematic in? Are you unwilling to change or discuss your behaviour?
2804:F14:8081:3201:9827:3072:74BC:2770 ( talk) 20:22, 12 July 2024 (UTC)
  • 98.115.164.53, what account or accounts have you used here and are any of those accounts currently blocked? -- Yamla ( talk) 20:26, 12 July 2024 (UTC)
    @ Yamla I've opened a checkuser request. [22]RandomStaplers 20:29, 12 July 2024 (UTC)
    98.115.164.53 is CU-blocked by Ponyo. -- Yamla ( talk) 20:39, 12 July 2024 (UTC)
    @ Yamla IP 2804:F14:8081:3201:9827:3072:74BC:2770 has responded to the CU request.⸺ RandomStaplers 20:40, 12 July 2024 (UTC)
  • @ Yamla I'm looking through the edit filter log... this person was tripping rate warnings left and right. It's amazing this person wasn't caught sooner.⸺ RandomStaplers 21:12, 12 July 2024 (UTC)

Arbitration motion regarding Durova

The Arbitration Committee has resolved by motion that:

Principle 2 of Wikipedia:Requests for arbitration/Durova, Private correspondence, is changed from
2) In the absence of permission from the author (including of any included prior correspondence) or their lapse into public domain, the contents of private correspondence, including e-mails, should not be posted on-wiki. See Wikipedia:Copyrights.
to
2) In the absence of permission from the author (including of any included prior correspondence), the contents of private correspondence, including e-mails, should not be posted on-wiki.

For the Arbitration Committee, SilverLocust  💬 23:23, 12 July 2024 (UTC)

Poggies. jp× g 🗯️ 06:38, 13 July 2024 (UTC)
Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard § Arbitration motion regarding Durova

my discussion was deleted

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


@ Antandrus closed my discussion because someone accused im a banned user. im not. please revert the closure /info/en/?search=Talk:September_11_attacks Gsgdd ( talk) 06:18, 13 July 2024 (UTC)

i have made valid arguments which merits discussion. it shouldn't be closed because of pure accusations. is there any proof im banned? can two people not have same idea? Gsgdd ( talk) 06:20, 13 July 2024 (UTC)
The discussion was closed, for reasons, none of which was anything to do with the allegation that you are a sock account. You made a proposal and virtually all the respondents disagreed with you. Therefore the closure was simply that your proposal did not gain a consensus.
Please don't try and relitigate the same argument here, it won't get any traction. Nthep ( talk) 06:32, 13 July 2024 (UTC)
There is one editor who didn't disagreed. I'm trying to build consensus. why are you trying to block it? Gsgdd ( talk) 06:36, 13 July 2024 (UTC)
and one editor opposed. what are you talking about ? Gsgdd ( talk) 06:38, 13 July 2024 (UTC)
also there is no Consensus to delete it. i accidentally put rfc tag - which i removed and it shoudnt be the cause of deletion. then another user accused of being a blocked account Gsgdd ( talk) 06:45, 13 July 2024 (UTC)
Thanks for raising this, but unfortunately this isn't the place to resolve your concern. The issue is a content dispute and the close was not an action requiring admin tools. It's not within the scope of this noticeboard to overturn content decisions. If you disagree with the consensus outcome please do feel free to seek a new consensus at the article talkpage in due course (ie not today or tomorrow or next month but eventually). Please note you will probably need to have new reliable sources that back your view, or an alternative set of words to propose which might gain more support than that available in this current RfC. -- Euryalus ( talk) 06:53, 13 July 2024 (UTC)
see this is a controversial topic. obviously people who follow this page will be quick to disagree. i need more time. i made some mistakes in the arguments, but its a learning process. i need to know people objections so i can research how to refute them. where can i seek arbitration ? Gsgdd ( talk) 07:04, 13 July 2024 (UTC)
also an admin blocked closed it. Gsgdd ( talk) 07:08, 13 July 2024 (UTC)
You don't need to be an admin to close an RFC, so this close is really just by Antandrus in their capacity as an experienced regular editor. I get what you're saying re more time to prepare arguments, but ideally the argument is fully prepared before opening the RfC rather than during it. There really didn't seem to be much support for your proposal, but if you do have some additional arguments or sources to present than maybe put them together over time (say, a few months?)and feel free to re-test consensus for the word "Islamist" in a future talkpage discussion or RfC. -- Euryalus ( talk) 07:15, 13 July 2024 (UTC)
why do i have to wait few months. i already have reliable sources https://www.brookings.edu/articles/rethinking-language-islamism-as-a-dirty-word/ and others to support my arguments... this is crazy - why my voices are being shut down and prevented from being heard Gsgdd ( talk) 07:23, 13 July 2024 (UTC)
Per this policy section, consensus can change but repeated or rapid attempts to relitigate the same issue can be a bit disruptive. As above I get that you hadn't fully assembled your arguments before posting the rfc. That's unfortunate as maybe it would have led to a different outcome. Or maybe not. Either way it's probably better to take some time putting those arguments together and then starting a new discussion in due course, versus starting a new RfC or discussion on the same topic immediately after the previous one has closed. -- Euryalus ( talk) 07:37, 13 July 2024 (UTC)
I took part in the thread the OP is complaining about. They wanted the 9/11 hijackers to not be described as "Islamist". Around 6 or 7 editors were against the OP. One editor made a compromise suggestion which involved retaining the word but the OP rejected that. No one supported their proposal. They say above "one editor opposed". That is the same WP:IDHT we saw on display from them in that thread. I think they are best advised to follow WP:STICK rather than keep pursuing. DeCausa ( talk) 08:08, 13 July 2024 (UTC)
The strength of arguments is crucial in the consensus process. no one other than you has made a strong case. so please stop that 6 or 7 editors against me argument Gsgdd ( talk) 08:19, 13 July 2024 (UTC)
Many people commented for sure, probably disapproved. but no valid reasoning imo Gsgdd ( talk) 08:19, 13 July 2024 (UTC)
anayway... ill be back after sometime Gsgdd ( talk) 08:29, 13 July 2024 (UTC)
You, as proposer, are not arbiter of what reasoning is valid or not. Acroterion (talk) 13:05, 13 July 2024 (UTC)
As Astropulse, to be clear. Doug Weller talk 15:18, 13 July 2024 (UTC)
Both those are ironic statements given that your argument in the thread was that we shouldn't be following the RS: " Just because RS promote hatred,racism etc.. does it mean wiki should do it as well?" DeCausa ( talk) 10:30, 13 July 2024 (UTC)
What makes you think the discussion was closed because someone accused you of being a banned user? There is nothing about that in the close. Phil Bridger ( talk) 08:56, 13 July 2024 (UTC)
One person wanted the word "Islamist" removed, no one agreed with them, but instead of letting it go it went on and on and on, and on, and I closed it. All in a day's work. And no, this had absolutely nothing to do with a suggestion this was a banned user (I personally don't think it is, but did not look into it). Also (as above) this was not an administrative action. Antandrus (talk) 14:45, 13 July 2024 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Misuse of Revdel

Recently, several revisions were deleted using Revision Deletion (Revdel) by AirshipJungleman29 in Draft:Gupta–Hunnic Wars, which I humbly believe they were not justified properly as they only found close paraphrasing in "The Huna Volkerwanderung" section and "Rise of Kidara Kushans" sub-section [23]. I'd rewrite the whole contents in these section/subsection but kindly please restore the appropriate contents so that I do not need to spend a lot of time to re-write it for months all over again. Also the user has only found few scanty grammatical mistakes in such a massive article but it was still drafted by them which was quite harsh in my humble opinion. I would like to request any admin to help me in restoring this article, because I have earnestly worked a lot before and spent months for the article already. Thank you. Jonharojjashi ( talk) 13:58, 14 July 2024 (UTC)

AirshipJungleman29 is not an administrator and can not delete revisions. I have notified them of this report. ScottishFinnishRadish ( talk) 14:02, 14 July 2024 (UTC)
The revdeletions were performed by Robertsky. — Cryptic 14:09, 14 July 2024 (UTC)
@ Jonharojjashi:(Non-administrator comment) That will not happen. That—substantial—chunk of text was a verbatim copyright violation which is an absolute on Wikipedia. See Wp:COPYRIGHT, which is a policy policy with legal considerations. For why it will not be restored, see WP:UNDELETE: Copyright violations and attack pages will not be provided. In any case, since the source and text were effectively the same, you only need access to the original to rewrite in your own words. But it cannot be hosted anywhere on Wikipedia—talk pages, draft, email—as the deleting admin— Robertsky—would have told you had you asked.
In fact, instead of relitigating it now, at a noticeboard, it would be more productive to simply take AirshipJungleman29's original advice and "take this issue seriously in the future". ——Serial Number 54129 14:17, 14 July 2024 (UTC)
@ Serial Number 54129 Yes I know that the section "The Huna Volkerwanderung" and sub-section "Rise of Kidara Kushans" are highly identical and I'd rewrite it in my own words, but what about the rest of the article? Even the attributed contents from parent articles were not spared. The article was massive and it's possible that there would be some grammatical mistakes and copyright violation but instead of removing the particular concern they have deleted more than 120k bytes of contents. I am not asking for restoration of those closely paraphrased section/sub-section but the restoration of the fair contents, please look into this. Kind regards. Jonharojjashi ( talk) 14:51, 14 July 2024 (UTC)
That's not possible. Specific sections of a page can't be revision-deleted, only entire revisions. — Cryptic 14:53, 14 July 2024 (UTC)
So I guess I have to manually restore non plagiarised contents? Jonharojjashi ( talk) 15:21, 14 July 2024 (UTC)
I have nothing further to add to Serial Number 54129's comment above. They have stated in a succinct manner what I would have conveyed. – robertsky ( talk) 01:43, 15 July 2024 (UTC)
  • The examples listed by AirshipJungleman29 at the talkpage are egregiously bad; essentially close-paraphrasing by (nonsensical) word-substitution. Given Jonharojjashi's poor record of content-creation in the IPA-history topic-area (see their talkpage, including several copyvio-related notices) and the amount of effort required to save their work on a notable topic from deletion (see this AFD), I believe a topic-ban or block from mainspace should be considered. Abecedare ( talk) 14:32, 14 July 2024 (UTC)
    I agree, Abecedare. Unfortunately, a topic ban the simple way (=placed by one uninvolved admin) seems to be off the table, since Jonharojjashi has not been alerted to the contentious topics restrictions, or even to discretionary sanctions. A pity. A topic ban by the community (=placed by consensus at this board) would be an unreasonable hassle and waste of time, IMO — there has been enough waste of the community's time by this user, surely. Therefore, I recommend an indefinite block from article space, which can be appealed in the usual way on their page, or, no sooner than in six months, to the community at this board. Bishonen | tålk 18:23, 14 July 2024 (UTC).
    Agree w/ Bishonen. Enough time has passed, and enough energy has been wasted. You can PB at will can't you? Carry on, captain. ——Serial Number 54129 18:33, 14 July 2024 (UTC)
    @ Bishonen: Jonharojjashi was alerted of IPA DS in Aug 2023, so a (non-community imposed) topic ban remains an option. Abecedare ( talk) 18:43, 14 July 2024 (UTC)
    Ah, I missed that. I've never seen such an alert not appear in the edit summary before - I thought that happened automatically. Well, in that case... do you think a t-ban or a mainspace block would be best and most relevant to the disruption, Abecedare and Serial Number 54129? Bishonen | tålk 19:52, 14 July 2024 (UTC).
    @ Bishonen: IMO a topic-ban would be preferable in order to not simply shift the burden of spotting copyright, paraphrasing, POVforking, source quality and source misrepresentation issues onto AFC reviewers. See this, this, this and the many abandoned drafts to get an idea of the concerns that have been previously raised. Abecedare ( talk) 20:15, 14 July 2024 (UTC)
    I hear you, Abe. On the other side, blocks are conveniently self-enforcing, while the user has ample opportunity to violate a topic ban through (perhaps innocently) misunderstanding how it works. I'm going by the difficulties they have demonstrated in understanding our copyright and sourcing policies. But you're right, a mainspace block wouldn't be fair on AFC reviewers. I have topic banned Jonharojjashi from India, Pakistan and Afghanistan. Bishonen | tålk 21:01, 14 July 2024 (UTC).

Error on page - Cannot add topic

https://en.m.wikipedia.org/wiki/Disappearance_of_Joshua_Guimond

I apologize if this is the wrong way to go about reporting this. I have never actually done this on Wikipedia before. On the page titled "Disappearance of Joshua Guimond" it states:

Around the time of the disappearance, there were two reports of a man driving an orange Pontiac Sunfire on campus, dropping off other men. Before the disappearance, when campus security approached the vehicle, one of the men who were dropped off ran away. After the disappearance, the driver was contacted, and he gave no more information than saying the car was destroyed.[30]

However, the article that is linked as reference# 30 makes no mention of this at all. I have been unable to find the correct article that mentions this info about that car being destroyed.

I attempted to add a topic on the Talk page as recommended, however there is no topic button on the Talk page and it seems as if the Talk section is prohibited for some reason. 71.251.236.155 ( talk) 22:40, 14 July 2024 (UTC)

I'm sorry you were unable to start a conversation on the talk page, no idea what's up with that. The cited ref actually does support the content (open ref #30 and do a find for "orange") but it's badly worded in the article so I'm going to update that. Schazjmd  (talk) 22:58, 14 July 2024 (UTC)
  • ( edit conflict) Hi, welcome to Wikipedia. I'm sorry you couldn't add a topic to the talk page. There's nothing the matter with the talk page. The problem is that our mobile interface doesn't work properly. Reference #30 (which is this article) does say the driver gave no more information and the car was destroyed. Both pieces of information are in the third paragraph from the bottom.— S Marshall  T/ C 23:00, 14 July 2024 (UTC)

Problematic rollover text

On this page /info/en/?search=I_can't_breathe The first hyperlinked instance of "George Floyd" in the section George Floyd shows text "George Floyd" when logged in, but an entirely different and problematic rollover preview when not logged in. I'm unable to figure out how to erase it myself. Eunoia666 ( talk) 22:45, 14 July 2024 (UTC)

Are you still getting this? (It was caused by vandalism to George Floyd, now reverted and revdeleted.) I'm properly seeing the preview of the unvandalized article both logged-in and -out. — Cryptic 23:04, 14 July 2024 (UTC)
Main case page ( Talk) — Evidence ( Talk) — Workshop ( Talk) — Proposed decision ( Talk)

Case clerk: Hahc21 ( Talk) Drafting arbitrators: Worm That Turned ( Talk) & David Fuchs ( Talk)

Arbitrators active on this case

Active:

  1. AGK
  2. Courcelles
  3. David Fuchs
  4. Newyorkbrad
  5. NuclearWarfare
  6. Salvio giuliano
  7. SilkTork
  8. Timotheus Canens
  9. Worm That Turned
  10. Carcharoth

Inactive:

  1. Roger Davies

Recused:

  1. Risker
  2. Kirill Lokshin

PD update

Giving a heads-up that at this point it's unlikely the PD will be posted tomorrow today. We'll keep you appraised of any other delays. Der Wohltemperierte Fuchs( talk) 03:31, 14 August 2013 (UTC)

Yes, apologies for that. We hope to have it ready soon. WormTT( talk) 07:35, 14 August 2013 (UTC)
  • Thank you both for keeping us updated - I appreciate that. — Ched :  ?  16:14, 14 August 2013 (UTC)
  • Same here. Lord Sjones23 ( talk - contributions) 16:24, 14 August 2013 (UTC)
  • Thank you, this is exactly the sort of communication that takes almost no effort but goes a long way towards maintaining good relations :) Thryduulf ( talk) 17:53, 14 August 2013 (UTC)
  • Thank you, that gave us time to ponder another of Andy's good ideas (and to experience more reverts), awaiting The Judgment ;) -- Gerda Arendt ( talk) 07:18, 15 August 2013 (UTC)
As a form of update, we've punted a working draft of the PD over to the committee as a whole. Giving ample time to wordsmith and fine-tune things, and in the spirit of under-promising I hope to have the full PD posted by early Saturday UTC if not sooner. Der Wohltemperierte Fuchs( talk) 14:55, 15 August 2013 (UTC)
Very good. Lord Sjones23 ( talk - contributions) 16:01, 15 August 2013 (UTC)
Take all the time you need - better to make the right decision than to rush, after all. Ritchie333 (talk) (cont) 17:47, 15 August 2013 (UTC)
  • It's a bit harsh to label the IP an "edit warrior" for one reversion when Pigsonthewing has ignored WP:BRD and reverted against the status quo twice... - SchroCat ( talk) 11:50, 16 August 2013 (UTC)
  • see also, stay calm and factual, - forgive me for seeing a team at work, I must be biased, -- Gerda Arendt ( talk) 12:01, 16 August 2013 (UTC)
  • I am calm and factual, and yes, you are biased, as am I, but throwing around accusations of edit warring against people cranks up the tension in a debate, not defuses it. - SchroCat ( talk) 12:08, 16 August 2013 (UTC)

Ched comment 1

  • First: I will be having some strongly worded comments on this PD in the near future.
  • Second: per "As Gerda has herself noted, she's been adding far more infoboxes as of late than Pigs; it hasn't been very constructive, especially when adding ones unilaterally is clearly going to create a kerfluffle. Der Wohltemperierte Fuchs(talk) 02:01, 17 August 2013 (UTC)" ... I would kindly request that David refrain to referring to the editor as "Pigs". I would suspect that Andy, or PotW would be acceptable, and I am familiar with the moniker that Andy has chosen; still, I think it is quite unbecoming to shorten the user name in the fashion that you have. Please make appropriate adjustments. Thank you. — Ched :  ?  02:22, 17 August 2013 (UTC)
  • Also: "Gerda Arendt is indefinitely restricted from removing | or |" ... I'm pretty sure Gerda will agree to refraining from removing infoboxes. typo? — Ched :  ?  02:45, 17 August 2013 (UTC)
    • Thanks for the catch. I malformed the very end of the PD in my initial copy and paste. Der Wohltemperierte Fuchs( talk) 03:01, 17 August 2013 (UTC)

PSky comment on the most one-sided decision ever

Hmm, let's see, you smack Andy and Gerda, the pro-box side, and leave the anti-box side, Klein and Smerus, totally alone? Do you guys realize it takes two sides to have a dispute, edit war, etc, and that Klein and Smerus deserve smacking far more than Gerda? This is the most one-sided decision ever. I'd ask if this PD was a joke, but nothing AC does anymore surprises me. I didn't think my opinion of AC could get lower but it just did. An editor with one-month wiki experience could have written a better decision. As far as I'm concerned, AC should be abolished; and in case you missed it, I've said that before onwiki. PumpkinSky talk 02:55, 17 August 2013 (UTC)

I think the proposal to sanction Gerda is ill-founded, even though I disagree with every infobox she's added at classical music-related bios. If she had been edit warring over infoboxes, yes, or if she'd repeatedly proposed infoboxes at the same article ad WP:IDHT, yes, but I've seen no evidence of such behaviour. Adding infoboxes to articles where it's likely to be controversial strikes me as bad practice, but I know of no policy it breaches. Sanctioning people for bad practice is not the way to go. Having said that, we do only have one arb currently supporting this sanction, and NYB seems to be questioning the FoF supporting the sanction, so this doesn't seem like a done deal. I hope the other arbs will read this and consider when voting. Heimstern Läufer (talk) 03:55, 17 August 2013 (UTC)
May I add here that I never added an infobox where I expected it to be controversial. I stand corrected in several cases, mostly operas where I still believe an infobox on the given works would be superior to a side navbox duplicating information from a footer navbox, illustrated in The Ban on Love. I don't recall adding any infobox to a classical music bio unless I wrote the article myself. I would not call "reignite" to point out that factually looking at The Rite of Spring might be a good idea, -- Gerda Arendt ( talk) 15:15, 17 August 2013 (UTC)
I agree with the AC proposal. It's the relentlessness which Gerda has shown in starting multiple infobox debates which is the problem. She's even tried to reignite some of the most contentious disputes (e.g. Rite of Spring, Georg Solti) while this Arb Case was open. -- Folantin ( talk) 08:12, 17 August 2013 (UTC)
I would like to understand what you mean by reigniting. I used The Ban on Love as an example how consensus could be achieved (or - so far - not). Only after The Rite of Spring was mentioned in the discussion did I also show that one. As for Solti, I have no idea what you mean. I approached an author of a TFA with the proposal of an infobox, he wanted me to insert it and I asked him to do it himself as I could be banned for disrupting the TFA. Is that what you summarize as "reignite"? For the whole case, I hoped for more looking at the actual evidence, rather than going by such summaries. -- Gerda Arendt ( talk) 15:25, 17 August 2013 (UTC)
The Georg Solti dispute had lain dormant since December 2012. You attempted to re-ignite the dispute on 2 August. You solicited an unsuspecting fellow editor to re-open the debate on the Georg Solti infobox: [30]. You must have known how inflammatory this was as this was one of the two pages which earned Pigsonthewing his topic ban on TFAs. Your comment even demonstrates you were aware of this. The other user went ahead, re-activating a debate which had been dormant for eight months: [31]. You then thanked him and tried to get him to do the same for Carmen [32]. -- Folantin ( talk) 15:30, 17 August 2013 (UTC)
We use the very same diff, only you see it differently. I explained that I could not do add the box because of a danger that I illustrated, - the danger is what I was aware of. What he did was a complete surprise to me, unsolicited. I did not comment on Georg Solti, not then, not now. -- Gerda Arendt ( talk) 15:36, 17 August 2013 (UTC)
No, you said "the editor who disrupted Georg Solti 25 July 2012 (mind the year!) is threatened to be banned." That's clearly Pigsonthewing, not you. -- Folantin ( talk) 15:41, 17 August 2013 (UTC)
That's what I said, meaning that I - if I disrupted the TFA of that day, Duino Elegies - might be treated the same way. Do I have a language problem? - How is that "reigniting" and "inflammatory"? -- Gerda Arendt ( talk) 15:47, 17 August 2013 (UTC)
That makes no sense to me. It's clear from those comments you were pleased the Georg Solti debate had re-started and wanted the same to happen with Carmen. -- Folantin ( talk) 15:50, 17 August 2013 (UTC)
I invite everybody to look. -- Gerda Arendt ( talk) 16:00, 17 August 2013 (UTC)
I too invite neutral observers to look. -- Folantin ( talk) 16:02, 17 August 2013 (UTC)
I'm rather inclined to agree with PSky on this. There is no sanction for those on the anti side, despite the principles explicitly rejecting tactics used by that side far more often than the pro side. The evidence shows that there is no way of telling in most cases what will be controversial until one of the anti people show up to a debate, making some proposed remedies unworkable in practice. Finally it sets up the classical music and opera projects as a walled garden where the normal rules of Wikipedia discussions about content do not apply, and you're banning Andy and Gerda to enforce it! This really is the most inappropriately one-sided outcome I've ever seen from ArbCom and I've been observing it for years. Please go back and try again. Thryduulf ( talk) 09:28, 17 August 2013 (UTC)
@Folantin, Klein and Smerus have been doing that too during this case so where's the difference? There is none. This is the worst AC group ever and I no longer recognize their legitimacy. @Thryduult, precisely, the only-pro-side sanctions violate the very walled garden principle they've posted because it sets up the anti-side as a walled garden just as you've said. PumpkinSky talk 10:01, 17 August 2013 (UTC)
"Klein and Smerus have been doing that too during this case". No they haven't. Kleinzach has barely edited Wikipedia during this case as you well know. -- Folantin ( talk) 10:35, 17 August 2013 (UTC)
Yes they have. Even if not, they most certainly did during the events leading to this, so again where's the difference? PumpkinSky talk 11:32, 17 August 2013 (UTC)
Unless you can back your accusations, you should stop repeating them. This case began on 17 July. Where have they been "starting multiple infobox debates" during that time? Kleinzach has made precisely five edits to Wikipedia during this period, two of them to your user talk page. -- Folantin ( talk) 11:41, 17 August 2013 (UTC)
I'll say whatever I want. And how convenient of you to ignore my last question. PumpkinSky talk 11:53, 17 August 2013 (UTC)
Your lack of concern for factual accuracy is duly noted as is the fact you appear to be the founder of WP:QAI. -- Folantin ( talk) 11:56, 17 August 2013 (UTC)
Oh? And your clear bias and lack of concern for factual accuracy is also duly note; you did clearly ignore my question about their behavior leading to this case. We clearly won't agree so let's just move on. But also note the other two commenting here seem to agree with me. PumpkinSky talk 12:01, 17 August 2013 (UTC)
You clearly have no evidence for your claims. I'm going to supply some regarding Gerda Arendt during this case. -- Folantin ( talk) 12:15, 17 August 2013 (UTC)
Can we please stop? If you want to discuss about something not related to the case, like you've been doing in your latest four posts, there are more suitable places than the Proposed decision talk page. Thanks. — ΛΧΣ 21 14:54, 17 August 2013 (UTC)
It's relevant to what David Fuchs says on the Proposed Decision here [33]. -- Folantin ( talk) 15:17, 17 August 2013 (UTC)
I agree with PunkinSky's surprise (while not agreeing with all points.) The AC felt the need to include the Levels of consensus principle. Did the committee miss that the very reason this needs to be asserted is the wholesale violation of the principle by many editors who invoked local consensus to remove infoboxes? Those removals, without citation of an actual policy, led to much frustration by Andy. While he did not handle it well, is it really the case that the committee finds nothing to say to any of the editors practicing it? Not a ban, not an admonition, not even a reminder?-- SPhilbrick (Talk) 21:24, 18 August 2013 (UTC)
Just as Andy may have been frustrated by the non-policy removal of infoboxes that he added, so those on the other side were frustrated by the initial non-policy addition of the infoboxes. A wikiproject does not own an article, but likewise a group promoting infoboxes does not own the top-right corner of the page. Rather than relying on attrition, the proper procedure for anyone wanting to spread infoboxes would be to establish a policy that an infobox cannot be removed. Johnuniq ( talk) 04:51, 19 August 2013 (UTC)

Request for evidence relating to Kleinzach and Smerus

PumpkinSky has suggested that the committee is wrong not to bring findings and remedies against Kleinzach and Smerus. However, little or no evidence has been submitted against these editors. Therefore, if anybody knows of any such evidence, I would request that they (pithily) submit it below. Unless it is entirely unavoidable, a simple list of diffs followed by your signature will be sufficient. Thank you, AGK [•] 15:19, 23 August 2013 (UTC)

I have intentionally not supplied any evidence against (!) any editor, many of whom I respect, and still don't want to do that. (Was it a mistake? I am interested in understanding, not "remedies".) I have supplied ample evidence for (!) an editor, Andy, and would like that to be considered. The shortest way is my list of "systematic" reverts/changes of infoboxes, most of them in 2013. I trusted that the arbs are able to read a version history such as Sparrow Mass. The latest revert was yesterday, BWV 71: an infobox that I added and Nikkimaria edited was reverted by Eusebeus, see talk and history. -- Gerda Arendt ( talk) 15:36, 23 August 2013 (UTC)
I have VERY limited time today, and limited internet access on weekends, but I will begin to go back through things. These two are subtle in their slaps, but the use of the old "with all due respect" phrasing should not keep folks from seeing the snide snaps and snarks going on here. Montanabw (talk) 20:53, 23 August 2013 (UTC)
More to come as I have time. Montanabw (talk) 20:53, 23 August 2013 (UTC)
  • To note that I plan on offering alternatives and/or new remedies and FoF this weekend. If you have any final comments I would make them soon. Der Wohltemperierte Fuchs( talk) 23:15, 23 August 2013 (UTC)
  • We are pandering Satan here by suggesting the things plainly seen are not even viewable unless restated here with a diff. It is much better to pardon the server load than to provide additional web hosting; for the sake of redundancy. This; compounded with intentions of an unwanted hammering sanction; in clear contrast of the community's desire, and indeed, her needs! We ask for guidance on protocols of civil discussion; expecting usable precedent to enhance our ability to move beyond impasse, with propriety to Wikipedia's institutional aims. We can agree to disagree (called no consensus), and close a discussion by default, to some neutral parameter; like the preference established by the earliest contributor, quite often the article's creator. This works for everything from the serial comma, to measuring time itself. Let me attempt to convey this in succinct candor; We don't really need sanctions here, we need authoritative guidance. If a sanction must levy; employ the "swift kick sanction"—that's the one where after self administering a swift kick in the ass, we see the light and get it right. :)  John Cline ( talk) 06:44, 24 August 2013 (UTC)
  • I support that view. I said so already in the workshop phase. Repeating in optimism some don't understand: We need to find a better way to discuss, and sometimes accept "no consensus", - not exclude excellent contributors with valid arguments from the discussion. I supply two diffs, both by uninvolved editors of this case, as food for thought:
  • Infoboxes are useful tools that should be encouraged in classical music articles. They sum up the main points of an article, allowing for readers of these articles (such as myself) access to some of the most commonly sought-after material. That they be in standard place in most articles would allow readers an easy go-to place for birth/death dates, places of occupation, and a general synoposis of the individual. I feel some in the classical music wikiproject get offended thinking that infoboxes encourage readers to skip over some admittedly great articles. But those who come here just to see a basic sketch of an individual aren't going to read the article from top to bottom. Those who do that will continue to do so whether or not there is an infobox present. Infoboxes, written correctly (omitting information that cannot be summarized, such as which "period" Beethoven belongs to), offer no drawbacks to an article and quite a few benefits. 10 August 2012
  • Consensus does not mean that stupidity and ignorance be given equal weight to common sense and knowledge. 22 August 2013
-- Gerda Arendt ( talk) 08:03, 24 August 2013 (UTC)
  • Not only for this case, but the future, I started a list of frequently raised concerns against infoboxes and what I would answer. It seems not well known that Kleinzach, mentioned above, said "I have no objection per se to boxes for compositions," and initiated infobox orchestra. It is a myth that Classical music is against infoboxes, a myth that seems to be widely believed for no good reason. - I don't mind an occasional bollocks or bullshit, having a history of linking to one of these in some other editor's comment myself. - If I may have a final word here (while I will keep adding to the list): I looked at the discussion Talk:Sparrow Mass again and found no lack of dignity in Andy's contributions to it. Let's not continue The Ban on Love. -- Gerda Arendt ( talk) 12:10, 24 August 2013 (UTC)

Section break 1

  • May I respectfully point out that the evidence for this arb case closed about two weeks ago? Arbs may wish to consider the consistent attempts of Montanabw, Rexss, PumpkinSky and Pigsonthewing to turn this investigation into their behaviour into an attack against others. I don't have time or inclination to respond to Montana's latest effusions, save to point out that virtually all the links she points out relating to me are repsonses to unprovoked, hostile and agressive comments from the four above mentioned editors. Gerda's optimism , which is what I clearly referred to, has been to me exactly as irritating as F-T's, although I am glad to say we are now cooperating with each other as per normal; I believe that Gerda and I understand very well each other's virtues and limitations and we don't need outsiders to kibitz on our Wikirelationship (Ahh.....). I am not at all ashamed of referring to the futile attempt of Pigsonthewing and Rexss to get an ANI judgement against me as 'bollocks' - which is exactly what it turned out to be. Unlike them, I am not a Wikilawyer, do not seek to build the encyclopaedia by vengeful attacks on fellow editors, and have not sought to escalate their war to these upper regions. Thanks, -- Smerus ( talk) 07:23, 24 August 2013 (UTC)
This case is not an investigation of my behaviour. You need to take responsibility for your systematic reversions of the addition of inboxes inside your walled garden - without any justification beyond 'nobody asked your permission first'. Then you need to consider the effects of stonewalling any attempts to reach a consensus by canvassing your WikiProject to trot out the same tired irrelevant, arguments. You count opinions on talk pages and call that a 'consensus'. At no point anywhere in this sorry business have you made any attempt whatsoever to look for consensus. You should be ashamed of the way in which you insulted and belittled one respected female editor and accused another one of libel. That's so far beyond the pale that any conclusion to this case that fails to acknowledge your central role in causing the problems will have simply given you a licence to continue bullying female editors and stifling any attempts at consensus. That has to stop if we are ever to move forward. Your lie above is plain: from the start, you have singled out Andy and Gerda as scapegoats, while I and others have deliberately refrained from mentioning your name in our evidence, as I would have preferred to have dealt with your behaviour as a general issue, not a personal one. It seems the Arbs would prefer to have it spelled out in detail and that's what those diffs above show. -- RexxS ( talk) 14:10, 24 August 2013 (UTC)

Comment I have to intercede here as a longstanding member of the WP:CM wikiproject. The description above by User:RexxS is simply histrionic. 1) We have discussed the use of infoboxes for classical music topics at WP:CM for a very long time now and have raised a number of arguments that members of that project find compelling and germane. That other users who do not edit classical music articles do not find them compelling may be true, but it is ridiculous to suggest that referencing and soliciting the opinion of interested editors through the relevant wikiproject is "stonewalling any attempts to reach a consensus by canvassing your WikiProject to trot out the same tired irrelevant, arguments." This seems arrogant. (2) You describe an engagement between two editors which is mere fiction given how the two editors concerned on this very page have undertaken to describe their dynamic. You may see it as insulting and bullying, but you are not the editor being addressed. Who are you to take umbrage on someone else's behalf? This seems remarkably arrogant. (3) Andy has been singled out because Andy is problematic. This may offend your sense of justice because you happen to agree with him, but I don't see Smerus, Kleinzach or anyone else wading over to other wikiproject article series willy nilly to bray schoolmarmishly about how we are guilty of owning all these articles (that we create, edit and maintain) because we refuse to concede the value of his point of view. To suggest that our interest in maintaining the quality of articles under the project's umbrella is somehow "stifling attempt at consensus" is ridiculous and seems quite unbelievably arrogant. (4) We have engaged, repeatedly and extensively and in good faith the question of infoboxes for classical topics. We will do so again. There is no policy mandating infoboxes. Absent such a policy it is reasonable that the editors who have common interest in these articles, demonstrated by the fact that they have edited and maintained them, should offer their opinion and be solicited to do so. That you contribute to such debates is salutary. That you then insult the integrity, motivations and sincerity of those of us who labour hard over our wikiproject articles is, however, not. It seems, dare I say, exceptionally arrogant. Personally, I see nothing in the evidence that has been presented "against" Kleinzach or Smerus that in any way whatsoever compares to the longstanding, repeated disruptive history of User:PigsontheWing. Eusebeus ( talk) 15:38, 24 August 2013 (UTC)

Eusebeus, please differentiate. Project Classical music has reservation concerning infoboxes for biographies, and I am willing to accept that. However, the project developed infoboxes for orchestras, Bach compositions and musical compositions, project opera developed an infobox for opera, all ready to be used. The fact that many of them were reverted and questioned brought us here. I don't want to point out evidence against any esteemed editor. Today I read again several interesting discussions, notably The Rite of Spring, Sparrow Mass and Don Carlos. I found no disruption by Andy in those discussions, instead an admirable hope for improving content: "One always hopes that fellow editors will raise issues with articles in order to improve them, rather than to try to score points in a different argument; perhaps disappointment should be expected. Nonetheless, if there is an error in the article, overlooked by those who have spent so many hours working on it and those who have subsequently reviewed it, it should be fixed sooner, rather than later. That said, if a term has been "employed by significant scholars in the field", then that, not your personal preference, has precedence. regarding your final question, you might like to read WP:NOTDEMOCRACY." One always hopes, -- Gerda Arendt ( talk) 21:03, 24 August 2013 (UTC)
I have to inform you that the option of infobox opera, installed by Voceditenore in the project's Manual of Style, was just changed, in Voceditenore's absence and without a discussion. (It makes me think if "Infoboxes" is the right name for this case. It seems to grow more and more to a matter of ownership and protection of the status quo, here: the traditional side nabox. You can speak up at the project talk or at the example The Ban on Love.) -- Gerda Arendt ( talk) 09:40, 27 August 2013 (UTC)
Voceditenore reverted and called for a discussion, -- Gerda Arendt ( talk) 19:11, 27 August 2013 (UTC)
[ec] You refer to "arguments that members of that project find compelling and germane". What about the project members who do not; and who like infoboxes? Does Gerda not count? Have the rest, like User:GFHandel and User:Melodia, et al, been driven off by the intransigence of the remaining project members? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:05, 24 August 2013 (UTC)

Further evidence

Like Gerda and RexxS, I was reluctant to pile on diffs of editor behaviour in my evidence, feeling that it would just fan the flames, rather than enable proper arbitration and the attainment of an an amicable resolution. But since you request them, I'll post some now. Noting your request for brevity (while giving necessary context, especially for long edits), and Der Wohltemperierte Fuchs' request for haste, this is still just a sample:

  • 10 March 2008 Kleinzach adds the words "non-classical" to the scope of {{ Infobox musical artist}}, which includes an explicit classical_ensemble configuration and code.
    • 31 August 2009 I removed that caveat
    • 21 October 2009 Kleinzach comments on this, in a conversation in which I was not yet involved, detailing my blocklog and Arb history, in a clear ad hominem response.
    • In the poll which followed, Kleinzach accuses others (in edit sumamry) of a transparent attempt at splitting the consensus against using the box for 'classical' musicians.
  • 31 July 2011 In response to my making a suggestion to improve the accessibility of navboxes (since adopted for all navboxes on Wikipedia), Kleinzach's reply is Is this to do with microformats? There is at least four years of back history to this issue as searching the archives of WP:Composers will show [42]. The suggestion was nothing to do with microformats.
  • 16 April 2012 Kleinzach says I was dismayed to see Andy Mabbett's involvement; also false allegation of breaking an undertaking (which I never made).
    • 16 April Kleinzach declares AGF is simply not appropriate here — unfortunately we have assume the worst
    • 16 April 2012 Kleinzach partisan canvassing
  • 19 March 2013 Smerus refers to the insane proposals to weld all the world's knowledge into a virtual nugget amd attempts to bully editors by alleging huge techno revolutions going on somewhere
  • 22 March 2013 Smerus opposes (on an article talk page) an infobox, citing WP:COMPOSERS policy and continues It is rather naughty to use Bach as a catspaw in trying to change this - it would be more polite to engage discussion at the project page. Remember that the composer's project's RfC concluded that consensus should be formed on article talk pages.
    • 23 March Kleinzach Closing an ongoing discussion, with a particularly biased summary, despite being an involved party. He was immediately reverted by User:GFHandel. Kleinzach then complained that his summary had been deleted in the reversion, rather than refactoring it as a general comment (i.e. removing phrases rendered nonsensical by the revert, like "I am now archiving this") and reposting it. Immediately after this, GFHandel, a long-standing editor in classical music realm (whose user name belies his interest); and a supporter of the use of infoboxes in such articles, retired from and ceased editing Wikipedia.
  • March 2013: Infobox orchestra is created, in draft. I add some fields to it, and
    • Despite the fact that the template is a draft, not used in any articles, Kleinzach objects that I am opposed to any changes to the template made without discussion. These shouldn't be happening — as I have said here. ("here" link updated to archive; diffs from that are in my earlier evidence. That whole discussion, and the template talk page, are worth reading for examples of Kleinzach objecting to (and often reverting) every change I made (most have been kept), and reporting every edit I make to the classical music project to canvass support).
    • During construction of the template, I made the observation: This new infobox looks promising, but should not replace infoboxes with additional, useful, parameters, such as those in City of Birmingham Symphony Orchestra, until it can handle similar detail (with better labels, of course). At that time the CBSO article looked like this
    • Nonetheless Kleinzach proceeded to replace ( seemingly) every instance of {{ Infobox musical artist}} on an article about an orchestra - edits well into three figures, ignoring objections. In most cases, cited and otherwise undisputed information was lost from the infobox, as can be seen from the current state of the CBSO article. That's a Fait accompli, apparently.
  • 19 May Smerus places a Do not feed the trolls graphic on the Richard Wagner talk page, during discussion of a proposed infobox.
    • 22 May Smerus made a bogus attempt to claim that I was not allowed to edit the talk page of a TFA (Richard Wagner; the discussion has been listed in others' evidence). He pushed this repeatedly in later edits. In This he refers claims I am Wikipedia 'reductionists' lke Mr. Mabbett, who see WP as means of crystallising the world's information to an essential nucleus from which all can be extrapolated (rather like, as I have mentioned elsewhere in a debate on Mr. Mabbett's obsessions, the desire of Mr. Casaubon in 'Middlemarch' to construct a key to all mythologies),and 'expansionists' like myself who like to create and expand articles, thereby both misrepresenting my work on metadata and dismissing the considerable number of articles I have created and/ or expanded. (Both ANI and then AN later rebuffed the attempt.)
  • 8 July Kleinzach falsely asserts that an infobox must summarise the article, i.e the article as a whole, attempting to correct Gerda, who rightly points out that they are supposed to summarise key facts. ( MOS:INFOBOX: 'to summarize key facts in the article in which it appears)
  • 8 July Kleinzach describes the addition of an infobox as "pretty close to vandalism"
  • 8 July Smerus describes infoboxes as the " end of civilization" and comaplins about Gerda doing so "without consulting on the relevant talk pages" while asking "whether it's "OK to revert these with a request for discussion on each talk page".
  • 8 July Kleinzach described the addition of an infobox as a WP:POINT attack
  • 9 July Kleinzach falsely accuses Gerda of going through my edits reverting them one after another
  • 11 July Kleinzach deletes an infobox which was part of Gerda's comment, from an article talk page.
  • 12 July Kleinzach attempts to pressure Gerda into falsely confirming that he did not delete part of her comment.
  • 11 July Kleinzach falsely claims As everyone here probably already knows, the editor involved here follows me around Wikipedia reverting and refactoring my edits He means me (see my earlier evidence for other examples from the period when he insisted on not using my name or user name). The diffs he gives are all pages I'd previously edited and are on my watchlist. He also accuses me of "hacking" (repeated in edit summary)
  • 12 July (and others) Kleinzach logging my edits

More may follow; or on request.

I repeat my comments in evidence and workshop that the "involved" projects include other editors, not yet named here (and some who have posted evidence or comments). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:49, 24 August 2013 (UTC)

Couple of thoughts

As I went active on this case rather late (after the workshop closed), I'm leaving some comments here. I've read through the evidence and workshop pages (and talk pages), and there are some interesting discussions and suggestions there. One thing that needs to be kept in mind is that it is not possible (or desirable) for ArbCom to rule on the wider aspects of the matter, such as what infoboxes are for, and how they should be used and the various points related to metadata. Those sort of issues need well-ordered and widespread discussion by the editing community, while at the same time recognising existing practices and any inconsistencies in current editing practices.

Looking at the bigger picture here: many elements can be incorporated on the same Wikipedia article page (article text, lead section, tables, references, categories, navboxes, infoboxes, succession boxes, images and other media). Some of those elements are optional, others are found in all articles. How these sometimes disparate elements mesh together is part of the process of building and writing an article. Sometimes that requires discussion. If editors disagree over how an article should be written, and which of these elements should be used or how they should be used, then they need to discuss that. When editors fail to discuss (or edit war), or discussions fail, that is the point at which either wider input from the editorial community is needed, or formal dispute resolution.

When you have meta-philosophical disputes like this that have lasted years, one approach is to identify the productive community discussions that have taken place over the years and to identify the discussions that got widespread input from a large number of editors. And if those discussions haven't taken place, to try and encourage such discussions (after suitable planning and preparation).

One thing I have noticed recently is the large number of discussions taking place at WP:TFD, with infoboxes being discussed there. As far as I can tell, those discussions appear to be mostly aimed at merging infoboxes, but it is interesting to see the wide range of opinions expressed in those discussions. Even if this case does succeed in calming things down here, it is obvious that the wider issues still need fuller discussion. This is the sort of case where I'm tempted to say that those who disagree (as shown on the workshop page) should be instructed to write essays explaining their positions, and that a widely-advertised request for comment would then help form community-wide consensus on the best way to move forward. Carcharoth ( talk) 11:16, 17 August 2013 (UTC)

One-sided rulings in such cases never calm things down, they exacerbate the issue. You should know that by now. Not to mention making AC look ever worse. PumpkinSky talk 11:34, 17 August 2013 (UTC)
Your comment is a response to my saying "Even if this case does succeed in calming things down here"? Fair enough, but that wasn't really the point of what I said and you are only responding to a very small part of what I said. Your comment seems to relate more to the section you started above (which I may comment on later). I'd be interested in constructive comments on the other things I said in this section. Carcharoth ( talk) 11:50, 17 August 2013 (UTC)
Wiki has become completely dysfunctional as it is a reflection of the real world, which is also totally dysfunctional. These things can't be fixed. For example, you can't stop people from socking--the sock policy is joke as it's a total waste of time, AC is pointless anymore because their rulings are wildly inconsistent and contradictory--towit putting up a principle against walled gardens here and yet setting one up for the anti-box crowd by ignoring their actions, AC and other wiki DR efforts are pointless because you can't change people's nature, those in power in wiki and RL protect their own and crap all over other people. So, I think we should do away with AC and DR and just work on content. Nothing has changed in the almost 8 years I've been on wiki. It just gets worse every year. AC and DR is all pointless and taking sides in a case makes it even worse. PumpkinSky talk 11:59, 17 August 2013 (UTC)
Wiki has become completely dysfunctional - admins have been far, far too lenient with disruptive editors such as Pigsonthewing who have turned massive areas of the project into battlegrounds and driven away productive editors and this has been going on for years. Many people who could make valuable contributions do not want to spend their spare time volunteering to take part in an activity that involves constant arguing and participation in bitter feuds. I am an active blogger on opera, I have taught history of classical music professionally, I made a conscious decision several years ago not to edit in the area on WP for the very reason that I could see I would get involved in this long-running controversy on infoboxes and it would be an unproductive waste of time. I never commented on the issue until it came to arbcom. It looks like a good decision is shaping up here, the essential thing is that Pigsonthewing is permanently removed from any involvement in anything to do with infoboxes. Smeat75 ( talk) 13:10, 17 August 2013 (UTC)

Comments from Gerda

2) About myself

You know Findings Gerda Arendt: Yes, I have added infoboxes to articles systematically and without prior discussion. The first link goes to works by Kafka, the day before he was TFA, - I am proud of it. The second link shows me adding one infobox to one opera which was a FA, right after the option of {{ infobox opera}} became available, which I understood as an invitation to use it, whereas others regarded it as the end of civilisation. I was told that it was not wise to do so and have only suggested (not added) to Carmen. - I believe that adding infoboxes to operas, literature, compositions etc. don't require previous discussion. I would go further and say that no edit requires to first ask permission, - and who's permission?

For quite a while already, I am on a voluntary 1RR rule: if an added infobox is questioned I go to the talk page. I offered to find out how consensus can be achieved in two cases, The Ban on Love and The Rite of Spring, in an attempt to get from "I don't like it"-arguments to factual one. I invite everyone, arbitrators and watchers, to enter those discussions, to find a way how conflicts can be resolved in the future, rather than looking at errors of the past. There are some 50 other cases to look at. Note: not one of them is a composer where I added an infobox. For the infamous case Richard Wagner: I didn't even suggest to add an infobox to the article, only to show it on the talk, according to the advice from an arbitrator. Why the reaction was as if I had committed a sacrilege is beyond my understanding. -- Gerda Arendt ( talk) 12:25, 17 August 2013 (UTC)

1) About Andy

I still haven't seen any evidence of Andy editing disruptively in 2013. I found him always helpful, creative, open for suggestions and considerate of an editor's personal situation. Restrict such editors? What do you want to accomplish? -- Gerda Arendt ( talk) 12:25, 17 August 2013 (UTC)

1.1) As said above, there are countless topics where infoboxes are quite normal. Why restrict Andy - of all people - from adding infoboxes there? (Same question for me, of course.) -- Gerda Arendt ( talk) 12:37, 17 August 2013 (UTC)

1.2) As said above, where is the evidence for recent disruption? I see no reason to ban for something that was regarded disruptive in the past, if it is not repeated. -- Gerda Arendt ( talk) 12:37, 17 August 2013 (UTC)

Gerda, I'm sorry to 'butt in' and contradict your defense of Andy. But only in the last day or so, not having had any previous dealings with Andy until I encountered him on the Peter Warlock article, I have personally found him aggressive, confrontational and quite oblivious to appeals to actually discuss an issue and collaborate. This can be seen here where, even as you and I are having a civil discussion about infoboxes, he butts in and tries (not for the first time, as you can see further up the talk page) to goad me into 'reporting' him after I'd called him out for breaching BRD - I can't help feeling as if to say "so you say - what are you going to do about it?". In short, he was behaving like a bully who's been caught out and has no intention of making amends but would rather turn this into an intractable confrontation, presumably in the hope that his 'opponent' will 'lose his cool'. Alfietucker ( talk) 18:59, 18 August 2013 (UTC)

3) About "remedies"

The term "not very constructive" has been used, - forgive me for finding all so-called remedies not very constructive. Nikkimaria and I not to add, revert, discuss infoboxes at all? Please see that only in a a very small field infoboxes are contentious, and these are not contentious because of Nikkimaria and me. I should not be permitted to add an infobox to a Bach cantata I write? ... to a church I find without one? Come on. - It's easy to ban an editor whose arguments you don't like. I don't see yet one factual (!) argument why "The Rite of Spring" should not have an infobox, - please join the discussion and give me one. -- Gerda Arendt ( talk) 13:15, 17 August 2013 (UTC)

Actually, your last comment is a very interesting point that should be clarified. If you create an article, you might be allowed to add an infobox, I think. However, there proposed remedies have yet to pass (or not). — ΛΧΣ 21 14:58, 17 August 2013 (UTC)
Assuming it complies with Wikipedia's content policies, then yes. The reverse should also apply: if you create an article (or provide the bulk of its content) then you shouldn't have to have an infobox imposed on it. For instance, on The Rite of Spring, the biggest contributor by far is Brian Boulton [43] and he's opposed to an infobox there. -- Folantin ( talk) 15:03, 17 August 2013 (UTC)
Why do you mention that here where we talk about me adding infoboxes? I didn't add one to "The Rite of Spring", nor did Andy, no infobox was "imposed" on it. Andy asked (!) why it doesn't have one, and that was the most "disruptive" edit I saw him making in 2013, - needless to say that I don't find it disruptive at all. - I am in friendly discussion with Brian on the infobox of another article, see Talk:Peter Warlock (again not added by Andy or me). One question is if an infobox is supposed to contain "the key facts" of an article or "key facts". Brian, who wrote an excellent Signpost article, is more open than you assume, and discussion, not banning and restricting, is the way forward that I hope for. - The agreement between Nikkimaria and me is that she doesn't revert infoboxes in "my" articles, I leave "hers" without one, - it's not a great agreement (a reader may wonder why some Bach cantatas have an infobox and other's don't, Nikkimaria's and Mathsci's), but is better than none. -- Gerda Arendt ( talk) 07:31, 18 August 2013 (UTC)
Gerda, I respect your content work and your Precious awards to build community here, and I think that you should be able to add infoboxes to articles you start. However, you seem at least a bit tone deaf when it comes to infoboxes. For example, when the discussion at Talk:The Rite of Spring had clearly reached consensus against adding an infobox to the article [44], you went ahead and added The Rite of Spring as an example in the Infobox musical composition documentation ( diff). When there is a clear consensus against using an infobox, using it as an documentation example makes no sense, and invites well-meaning editors who are ignorant of the article's history to add it to the article. Ruhrfisch ><>°° 15:20, 18 August 2013 (UTC)
Please follow the sequence: It was not my choice of an example, I chose The Ban on Love above it. The Rite was mentioned there, I thought we better illustrate it for those who don't know. I still believe that we should not "vote" on infoboxes but find other ways of discussion, - I keep dreaming and searching, please help. -- Gerda Arendt ( talk) 05:52, 19 August 2013 (UTC)
I am sorry Gerda, but I have no idea what you mean with your comments directly above this. I tried to "follow the sequence" by looking at your edit history. On June 1, 2013 at 19:10 you made your first edit in nearly six hours (to Wikipedia:Administrators' noticeboard/Requests for closure to the thread ‎"Talk:The Rite of Spring#Infobox" with the edit summary That's how you can look at a ramp for the disabled ( diff)). Your next edit was at 19:21 to Talk:The Rite of Spring to the thread "‎‎Closing discussion?" with the edit summary some things can't be decided by voting ( diff). Your next edit was at 19:36 to Template:Infobox musical composition/doc with the edit summary ‎‎Examples: add one where you added The Rite of Spring infobox as an example ( diff). I looked at several of your other edits before and after these, but none of them mention the Ban on Love.

Just to be clear, I have no problem with proposing and showing examples of infoboxes on the talk page for the article where the box would be included.

However, I think that it makes absolutely no sense to show a specific article's infobox as an example in that box's documentation when the talk page for that article twice showed clear consensus against including any infobox. That is like using Mitt Romney or John Kerry as an example of a US President in {{ Infobox officeholder}} (since there was pretty clear consensus against either of them actually becoming President).

I also think it makes absolutely no sense to show an unused infobox as an example anywhere outside the article's talk page (or a personal sandbox). The problem is that an uninvolved editor who sees the example box and finds it is not used in the article may well not read the article talk page. They may well think that the box should be included in the article, and add it despite consensus not to do so. It is a little like a leaving a loaded gun lying around unattended - it may lead to unexpected noise and injury.

I hope this explains my concern at your "tone deafness" when it comes to infoboxes more clearly. Ruhrfisch ><>°° 21:43, 19 August 2013 (UTC)

I try to follow but think that we speak of different things- which doesn't make understanding easier. After the workshop closed, I installed The Ban on Love on its talk, side navbox vs. infobox, to "practise" with an example how consensus might be achieved, on 8 August. In the discussion The Rite was mentioned, therefore I added it 9 August. - I am a bit surprised to see an infobox compared to a gun ;) - If someone sees it and adds it, simply revert. - Decision by voting: I believe that to look at flaws and merits of a proposal is better than counting people who come with arguments such "Oppose any infobox" (yours), "An infobox is not needed" (well, of course not, it is never "needed"), "redundant to a properly-written first paragraph" (well, it has to be redundant by definition), and better than all these " infoboxes are contentious". -- Gerda Arendt ( talk) 22:10, 19 August 2013 (UTC)
@ Ruhrfisch: we spoke of different things, now I know. I was absorbed in the case, you spoke about the example in the infobox template. You were quite clear, I didn't get it, sorry. I replaced the example now by a Bruckner Symphony, which has an infobox since 2007. -- Gerda Arendt ( talk) 15:59, 23 August 2013 (UTC)
You forgot the "Google should not be allowed to easily benefit from our work" argument that was sported at Jimbo's Agathoclea ( talk) 07:50, 20 August 2013 (UTC)
WHAT? — Ched :  ?  04:42, 21 August 2013 (UTC)
The above summary is mistaken. The discussion was here and concerned an essay expressing extreme frustration with the infobox wars, and particularly for one justification to include infoboxes, namely "Watson, SIRI, and Google all use the infobox data." The author objects to having their opinion that some infoboxes are not helpful subjugated by an imperative that data must be provided for Google (and inserting metadata into the article is not sufficient because editors won't keep hidden data updated, therefore an infobox must be present and visible). Johnuniq ( talk) 07:40, 21 August 2013 (UTC)
The "Watson" quote (though factually correct; and acceptable, as WTT points out elsewhere)) is a paraphrase of part of a much longer comment by User:Richard Arthur Norton (1958- ) in a November 2012 discussion at Talk:Stephen H. Wendover/Archive 1. For the record, I posted only three short comments there, and one of those was to point out that the page had been refactored, changing the meaning of my other two comments. There is no "imperative", and noting is being done "for Google". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:59, 23 August 2013 (UTC)

We start today

I keep dreaming of a new discussion style in the future, instead of looking back at who made what mistake in the past. My suggestions for arbitration:

  1. I restrict myself: I don't revert the revert of an infobox. (I started doing so a while ago.)
  2. Andy restricts himself: he doesn't make more than one comment per day in any given infobox discussion.
  3. Nikkimaria keeps doing what she does, follow our edits, and Wikipedia will be clean.
  4. Kleinzach restricts himself: he doesn't say again "The talk page is not the place for an info box".
  5. Smerus restricts himself: he doesn't mention "(mental) health" again in an infobox discussion.

We all don't start new discussions, but try to solve the open ones. I suggest Siegfried first, if you don't like The Ban on Love ;) -- Gerda Arendt ( talk) 06:46, 19 August 2013 (UTC)

Could you please cite exactly where I have made any mention of health, mental or otherwise, in any infobox discussion? I do not recall any such occasion. I ask so that I can make apologies if appropriate if I have in any way transgressed the bounds of courtesy.-- Smerus ( talk) 07:07, 19 August 2013 (UTC)
Siegfried, link above, -- Gerda Arendt ( talk) 07:39, 19 August 2013 (UTC)
I see that I wrote there ' I join the plea for dignity and (mental) health'. This is not an imputation against anybody, it is a simple plea for sanity. This is the secondtime in a few days that you have made unwarranted imputations against against me, once by suggesting that I set up a tag-tema, and now by apparently implying that I made comments about the mental health of other editors. I suggest that the principle new start that can be made here is by editors refraining from making allegations against others and/or telling other editors what words they should or should not use in their general commemts, as long as those words are not insulting or vicious. I dream of such a day.-- Smerus ( talk) 08:09, 19 August 2013 (UTC)
I have not. I have not made any imputation. I have not said that you set up a team-tag. I have not implied anything here, I have only asked you to not use the phrase in the future. Let's keep it simple, please, -- Gerda Arendt ( talk) 08:22, 19 August 2013 (UTC)

Invitation

I invite every arb (and everybody else interested) to visit one open discussion, perhaps even take part in it. You know where to find the choices on top of Verdi, Siegfried, The Ban on Love (mentioned in the case or above): here. -- Gerda Arendt ( talk) 11:33, 19 August 2013 (UTC)

I invite everyone to stop talking about infoboxes for at least a month because no benefit would arise from adding further fuel at the moment. Johnuniq ( talk) 00:17, 20 August 2013 (UTC)
Excellent idea - I will stop talking about infoboxes for at least a month (as of now ;-) ). Ruhrfisch ><>°° 00:39, 20 August 2013 (UTC)
I thoroughly approve of this proposed moratorium. -- Folantin ( talk) 08:24, 20 August 2013 (UTC)

Comments from the reader?

We can not ask "the readers" how they feel about the unspeakable things - let's call them "summary" for the moment. We can not ask them especially when they got reverted. But we all are readers. Please let me know if my "summary" serves you, compared to no summary. From the more than 50 cases (linked above) I chose an opera (o), a composition (c) and a person (p). Easy poll: if "with summary" (or without) is the same for all three cases, simply sign, if not the same for all three take the two initials for which you react the same way and sign those. I would love something playful today.

  1. opera: Fatinitza - with - without
  2. composition: Sparrow Mass - with - without
  3. person: Andreas Scholl - with - without

I prefer with summary

  1. -- Gerda Arendt ( talk) 08:42, 21 August 2013 (UTC)

I prefer without summary

Feel free to discuss, -- Gerda Arendt ( talk) 08:42, 21 August 2013 (UTC)

Discussion

This Arbcom case concerns the long-term disruption caused by a clash between two sets of editors—it is not relevant whether infoboxes are good or bad. Let's suppose some new arguments were produced to conclusively show that infoboxes must (or must not) be included in every article—would that resolve the problem? The answer is no because after all the bitterness of the infobox wars, neither side is going to accept a new opinion. It really would be best to stop talking about infoboxes—wait a couple of months, then if wanted, start a community-wide discussion to get a general consensus so future discussions can rely on a policy, or at least a guideline. Johnuniq ( talk) 10:20, 21 August 2013 (UTC)
So you think, about what this case concerns. Please note that I never said "must" or "must not", and never will. I use an option. -- Gerda Arendt ( talk) 11:57, 21 August 2013 (UTC)
This case is called "infoboxes", yes, but as someone who has watched the dispute for a couple of years without getting involved in it until now, I agree with Johnnuiq that it is not actually about infoboxes but more about one editor's (Pigsonthewing) obsession with "metadata" and his pushing of it onto unwilling editors in a highly argumentative way that alienates others. There are many examples where he has put an infobox into an article, or attempted to, and the people who have built the article say" that does not add anything", to which the all-purpose reply is "Yes, it does, it emits metadata", just for instance in this discussion [45].I can say for myself that I made a deliberate decision not to edit in the area of classical music because I could see it would involve me in this bitter feud, and I have better ways to spend my spare time. Smeat75 ( talk) 22:52, 21 August 2013 (UTC)
Smeat75 misquotes me. I was actually replying to Brianboulton, who said, addressing me, You obviously think that an infobox would enhance this article; let us have the arguments for this., and what I actually said was The benefits of an infobox in this article, as for the many thousands of other articles that include one, are that it summarises key information from elsewhere in the article, including material not suitable for the lede, for the convenience of readers wanting a quick overview, not least those accessing the collapsed view on mobile devices. It makes that information available as machine-readable metadata on the page; and for use in dbpedia. And it will, shortly, provide an interface with Wikidata. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:21, 21 August 2013 (UTC)
I provided a link to the whole discussion, anybody can follow it to see exactly what you say.I find you a very intimidating and bullying presence and made a conscious decision to avoid any articles that might bring me into dispute with you. Smeat75 ( talk) 23:27, 21 August 2013 (UTC)
You have your view, I have mine (and this is my section of the discussion). I repeat from below: I find Andy not intimidating, patiently explaining, with a sense of humour (note: I did so already when I did not share his view). - I liked to enter his latest article to the DYK statistics. I like that he (of all participants in the Bach discussion) came to my talk when I mentioned that a friend died. - "Intimidating" is a difficult term, - would you have a link to something you would describe like that? - I am not intimidated, although I was warned. - "Obsession" is also a difficult term. I am for infoboxes without using the term metadata, and I don't feel that I am obsessed. - What this case should be about and is about are very different things. It should be about systematic reverts of infoboxes, latest example BWV 71, see discussion. - The way this case goes (so far) makes me think of a "deliberate decision" not to edit Wikipedia. I didn't want a case, but really hoped arbitration would look at recent evidence, not history, and reach for understanding. Recent evidence has it that Andy and I did the same things, so please treat us the same. I am not afraid. -- Gerda Arendt ( talk) 12:41, 23 August 2013 (UTC)

We need to know what to do in the future

For the future, we need to know precisely "what is perceived to be some editors' aggressive addition or reverting of infoboxes to articles without discussion", as the SignPost summarized.

Please mark the following 2013 examples as "aggressive" if you perceive them so. (Note that I excluded operas, because we will deal with it on the project level, started already, after 17.000 words of discussion were archived.)

Added later: After Voceditenore's remark below, I change the question to: what is perceived to be problematic and should be avoided in the future? (Not using "aggressive", "tendentious", "disruptive", "detrimental to our content", "a nuisance".) All cases turned out to be controversial, to my surprise. -- Gerda Arendt ( talk) 10:53, 1 September 2013 (UTC)

  1. Addition of an infobox without prior discussion to a church ( Cathedral of Blessed Mother Teresa in Pristina, St. Severin, Keitum)
  2. Revert of the same
  3. Addition of an infobox without prior discussion to an orchestra ( Russian Symphony Orchestra Society)
  4. Revert of the same
  5. Addition of an infobox without prior discussion to an art work ( Forsbrook Pendant)
  6. Revert of the same
  7. Addition of an infobox without prior discussion to a company ( Renaissance Theatre Company)
  8. Revert of the same
  9. Addition of an infobox without prior discussion to a person not in classical music ( Aspinwall)
  10. Revert of the same
  11. Addition of an infobox without prior discussion to a building ( Holzhausenschlösschen)
  12. Revert of the same
  13. Addition of an infobox without prior discussion to a composition ( Sparrow Mass, Cantata academica)
  14. Revert of the same
  15. Addition of an infobox without prior discussion to a Bach cantata ( Geist und Seele wird verwirret, BWV 35, Gott ist mein König, BWV 71)
  16. Revert of the same
  17. Proposing an infobox for a composer ( Handel)
  18. Addition of an infobox without prior discussion to a composer if you wrote the article ( Planyavsky)
  19. Revert of the same
  20. Asking why an article doesn't have an infobox ( The Rite of Spring)

Needless to say, as I am unaware that any of these actions (not even the reverts) are "aggressive", problematic, please clarify. What did I miss? -- Gerda Arendt ( talk) 08:52, 1 September 2013 (UTC)

The quote is a Signpost editor's individual take on the case. It has nothing to do with the proposed decisions in this case. You will note that nowhere in the proposed decision is the term "aggressive" used except in SilkTork's comment under Editorial process:
"Reverting of anything other than obvious vandalism or harm should be considered very carefully as reverting can often be perceived as an act of aggression which then provokes a negative response. Consideration, politeness and discussion go a long way to assisting everyone to build this encyclopaedia appropriately."
As for WikiProject Opera "starting already" on the discussion you propose here, I'm afraid you've rather missed the key thrust of my "17,000 words" comment there:
[...] Several members are so sick of these constant, fruitless, and at times personalised discussions dominating our project talk page that they've taken it off their watch lists. Lord knows how many prospective members we may have lost in the last few months after they've seen this talk page. It's quite clear that at the moment some editors have fairly entrenched positions and there is simply not sufficient common ground for us as a collective to come anywhere near an agreed "general recommendation". The world is not going to come to an end if we have to proceed without one for now. However, the relentless attempts to continue rehashing this may well be the death of this project. Can we please take a break from all this and revisit it in a few months (if anyone wants to) when people have had time to reflect on their positions and the dust has settled on the current arbitration proceedings and their aftermath. [...]
Voceditenore ( talk) 10:10, 1 September 2013 (UTC)
I don't think I missed it, I responded that I will not add an infobox where a side navbox is in place, - adding here: I will not even suggest one in such a case, - five months were mentioned, fine with me, -- Gerda Arendt ( talk) 10:33, 1 September 2013 (UTC)
I am aware that you responded with your five months offer, but since you have described your response as "starting" (yet another) discussion of how to proceed with infoboxes, well, I'm afraid you did rather miss my point. In any case, you can (and undoubtedly will) do what you think is best. Voceditenore ( talk) 10:52, 1 September 2013 (UTC)
I try, -- Gerda Arendt ( talk) 11:06, 1 September 2013 (UTC)
I did not start "yet another discussion", - I opened the discussion on The Ban on Love on 8 August, only moved it to the talk of the article on 26 August. -- Gerda Arendt ( talk) 11:20, 1 September 2013 (UTC)
??? What does Talk:Das Liebesverbot have to do with it? That is an individual talk page discussion, not a "project level" discussion and not carried out on the project talk page. Your statement: "Note that I excluded operas, because we will deal with it on the project level, started already, after 17.000 words of discussion were archived" (and your subsequent comment) implied pretty clearly to me that you considered Wikipedia talk:WikiProject Opera#17,000 words and your response to it to be the "already started" new project-level discussion on how to proceed on infoboxes, when actually it was my individual plea to both sides for a project-level moratorium on the subject. Perhaps you don't see the damage these discussions have done to the project in terms of both productivity and our former collegial atmosphere, but I do, and so do the members who have taken the project talk page off their watchlists. Voceditenore ( talk) 14:23, 1 September 2013 (UTC)
I won't "damage" productivity and atmosphere anymore, leaving projects opera and classical music, -- Gerda Arendt ( talk) 11:53, 2 September 2013 (UTC)

Comments from Montanabw

I see several problems with the proposed decision.

  1. Klienzach and Smerus should be subject to - at a minimum - identical or parallel restrictions to those imposed on Nikki, Gerda and Andy. I will elaborate more on this below
  2. Andy needs to be evaluated on 2013, not 2006 or whenever. To the extent he made mistakes, he did his time, he's paid his debt to wikipedia society, and that should be water under the bridge. Drop the stick, look only at the present.
  3. Also, Andy clearly has an interest and passion for infoboxes and metadata, and that interest is not a bad thing; he provides a useful service to wikipedia and shouldn't have the thing he cares about most taken away. He has learned and grown from what has happened in the past, and I believe that the PD is basically giving him a life sentence for a misdemeanor. I think that if people are concerned, any proposed decision should be time-limited and narrowly targeted to specific, CURRENT concerns, perhaps only within the Classical Music project.
  4. Any restriction on Gerda of any sort makes absolutely no sense whatsoever. She has never violated one single policy or guideline on wiki and where she has ruffled feathers. she has apologized. In addition, most infoboxes she initially added were to INDIVIDUAL articles (which the PD says is OK) that she herself either created or did a 5x expansion on (I don't have time to correlate her DYK record to infobox additions, but I think I'm correct on this). Basically, all she has done was annoy the Old Guard "we don't want any infoboxes anywhere never lalalalala" clique at WP Opera.
  5. The proposed sanctions on Nikki seem about right, though perhaps definitely a time frame after which she can reapply for adminship (6 months, perhaps?) would be good so that we don't have a situation of the wiki life sentence that I have criticized above for Andy where a RfA would result in a chorus of "OMG! She was desysoped 10 years ago and how dare she return now? It's too soon!" and put her under a cloud forever.
  6. I am concerned that Nikki is being subjected to sanctions when Smerus and Klienzach aren't even mentioned, even though their behavior and attitudes are a very large part of why we are here in the first place. I am wondering if this is an example of the systemic bias against women that is a problem in parts of wiki. Nikki did overstep, but she also should not be the only person on the anti-infobox side (particularly where she isn't 100% anti-infobox anyway); in some ways, she showed more willingness to collaborate and work with Gerda than did Smerus or Klienzach.
  7. I think that if we are looking at levels of remedies, those imposed on Andy should parallel those on Nikki (save that he isn't an admin, but perhaps a discussion of appropriate but time-limited ( a month or so, maybe) editing restrictions would be in line.
  8. I believe that there should be some action taken against Kleinzach and Smerus for their behavior as the "old guard" and how UNBELIEVABLY unkind and incivil they have been to Gerda who, in my view, has always been nothing but civil. In particular, Kleinzach seems to be skipping off scott free because he simply has not responded here. Although Folantin and I personally reached a truce as to each other, I will note that I continue to be troubled by his attitude and responses here, it's one thing to defend his friend Smerus, but his tone has been problematic.
  9. Any restrictions on people adding or removing infoboxes should be confined mostly to the classical music topics, because this seems to be the only place where the existence of infoboxes themselves are the problem (most other disputes in other areas seem to be more over form than existence). To say that people cannot add ANY infobox anywhere is ludicrous; what if we have 10 new articles that need, say Infobox Mineral added - a wikiproject that strongly supports infoboxes in every article? Or if I ask Andy or Gerda to tune up or fix me up a fancy new infobox design for, say, the equine "biographies" where we have an infobox in all of them?

I am concerned that the proposed ArbCom decision unfairly targets a user, Andy/Pigsonthewing, as a scapegoat, and lets two playground bullies, Klienzach and Smerus, off scott-free to continue their bullying and domination of WikiProject Opera and WikiProject classical music unabated. This situation illustrates the worst weakness of "teh wiki" - it never forgets and it never forgives. Montanabw (talk) 15:57, 17 August 2013 (UTC)

@Worm, others: I am quite concerned by the "disinclined to use infoboxes" tone of the comments below and the implication that, somehow, they are not a standard feature of wikipedia articles, or that the "pro-infobox" contingent is a minority. Infoboxes are pretty much standard operating procedure for many wikiprojects, and as far as I can tell most of the C-class and better biographies, most C-class and better animal articles, gem and mineral articles, health and disease articles, chemistry articles, movies, TV shows, popular music, and so on. I think in Andy's evidence he showed some links that at least HALF and maybe more of wikipedia's articles - and this counts stubs and everything - already have infoboxes. While there is plenty (I'd argue too much) "drahmahz" over the content and appearance of infoboxes, the rabid OMG NO! response to them is rather unique to the Classical music project. For that reason, I don't think it wise to view infoboxes as a "creation" issue nor am I confortable having their absence any kind of implied default position. Montanabw (talk) 21:28, 19 August 2013 (UTC)

NEW: For anyone not thinking there is evidence of the behavior of Smerus that I think needs sanctions, he just posted this on the 16th (been ut of twon, haven't been following the drama chapter and verse for a while...): User_talk:Gerda_Arendt#Team. Montanabw (talk) 22:56, 19 August 2013 (UTC)
Just in case anyone takes this latest provocation seriously, I suggest they read the entire thread concerned.-- Smerus ( talk) 07:35, 21 August 2013 (UTC)
Most definitely. And I also strongly recommend reading Smerus' talk page as well. Don't start, my friend; WP:BOOMERANG. Montanabw (talk) 15:52, 21 August 2013 (UTC)

Comments from RexxS

I'm very disappointed that the PD has failed to find any viable way forward in resolving these issues. The idea that simply banning a few editors from the dispute will solve the problems is akin to the concept of cutting off an arm to cure left-handedness. You have the ability and the encouragement to look for better means, but have spurned the opportunity.

There is clearly a principle missing as Silk Tork has hinted - something along the lines of:

  • Editors making bold, good-faith edits to articles or article talk pages that others consider contentious may be judged to be editing disruptively.

because without that, the FoF and remedy concerning Gerda are hung on a non-existent premise - one that I'm not at all sure has the consensus of the community. You won't put the above up for debate, of course, because you know it has no grounding in our current policies and guidelines.

You will know that I have collaborated with Andy on numerous technical issues over the last couple of years, not least the development of {{ hlist}} and the improvements made to the accessibility of our articles, so you will expect me to be dismayed at the suggestion of banning Andy, thereby losing all of his hugely valuable contributions in so many areas - including classical music (how many of the regulars at WPCM can boast of having written a monthly column for a classical music magazine, as Andy can?). I accept that it would be better for Andy to step away from the conflicts over infoboxes, as they tend to bring out the worst in him, but why do you pick the bluntest of tools to do the job? "... indefinitely banned from adding or discussing the addition of infoboxes"? That implies a ban from any namespace, yet Andy is one of the small fraction of editors with the technical know-how to create and improve infoboxes, and you suggest removing him from that as well? Why? What does it accomplish besides damaging the encyclopedia? If you want to remove Andy from the conflict, then forbid him from adding or discussing infoboxes in mainspace; get him a mentor; look for some constructive, not destructive remedies.

I've known Nikki since she worked her socks off to save Geogre's Ormulum, and I've had both agreements and disagreements with her, but I've always found her willing to debate the issues and look for compromise - the last time she was blocked for edit-warring, I was able to successfully petition the blocking admin to unblock her as we had already made progress in resolving that particular issue. I know that she has regularly reached compromise with Gerda, and I'd point others to those interactions as one model of resolving differences. I do find her abbreviated edit summaries problematical, but I haven't seen any evidence of misuse of her admin tools. I therefore find the proposed desysop as unfounded, and I'd strongly suggest you look at ways of helping her contribute - why not 1RR and obligatory explanational edit summaries, as those are where the problems lie? The present drafting is reminiscent of curing headaches by decapitation.

Ok my rant is finished, and so am I. -- RexxS ( talk) 17:04, 17 August 2013 (UTC)

Comment from Olive to the arbs

I have no experience with the info box debate. I am familiar with Gerda's work, although not with Pigsonthewing. I did attempt to talk to Nikki after watching what appeared to be on-going stalking. What struck me when reading this Arbitration case was that it seemed out of focus, blurred, and with no clarity. The remedies for the most part are those saved for the worst offenses and all of it was lopsided ignoring the work of multiple editors which should have been scrutinized.

I would like the arbs to consider a few general points:

There are two kinds of issues which seem to come to the arbs. Wikipedia is a designated collaborative community. Its legs are the family of editors the encyclopedia stands on. As in any family behaviours arise which make editing unpleasant. Still, those behaviours while unacceptable can be remedied usually, as in a family, with strategies that do not require that the family member be asked to leave and set up a tent down the street. Members of this community are valuable, take a long time to train and for the kind of issues that create unpleasantness but which do not undermine the very fabric of the community lesser remedies are always best.

The second kind of issue is that which eats away at the legs of the community, destroying, not making unpleasant, but destroying the fabric of Wikipedia. That kind of behaviour is directed directly at other editors, is thoughtful, premeditated and is meant to damage editors so they eventually will leave. I mean more specifically the creation of narratives that create a false sense of an editor, fatiguing them deliberately, harassment, retaliation, bullying, talk page lynchings, and the lack of basic values most of us agree allow communities to function optimally like honesty and integrity ... and the list goes on. I'd add that these tactics have been applied to both editors and arbs. wearying the arbs as well as the editor.

I do not see that a general over arching distinction has been made that separates problematic behaviour from behaviours that are meant to deliberately harm other editors, undermining Wikipedia in the long run, in part because the behaviours which truly undermine are hard to see, the cases, high profile, and all of it harder still to believe. And I do not think the arbs have made this distinction either. Maybe I'm wrong. Once behaviours have been placed in either the "bickering family" slot or the more serious "undermining the fabric of the collaborative community" slot, remedies are easier to apply.

In this arbitration what struck me was that the bickering family had been treated to remedies that belong to more serious transgressions like the eventual undermining of the community creating that immediate out of focus sense I had. I don't see in the list of concerns in the Pigsonthewing remedy that indicate he/she has deliberately causing the kind of damage that requires an indef ban, and Gerda seems to be relatively blameless so I have to ask, please reconsider the nature of the problems and into which of these two categories the editors named in this case belong. I know this is tough job, and I can't imagine what the arbs deal with so this is not an attack, just an attempt to analyze and define, should that make the arb job easier and the remedies more likely to be fair.( olive ( talk) 19:24, 17 August 2013 (UTC))

Closing statement by Ched

  • First: Being concise is not my strong suit.
  • Second: I must take responsibility for my lack of direction in my original request (as pointed out by User:Giano), my lack of participation in the evidence stage, and perhaps most regrettably in my lack of participation in the workshop stage. For these failings I do apologize to both the committee and the community. (Worm That Turned and 2 other wikipedians are aware of the specifics as to the "why", but the reasons are not germane to wikipedia). I would also offer apologies to Gerda and Andy; as well as Nikkimaria and the other named parties of the composer group in requesting their attention to this case. Still, it was something I saw as a problem, and I thought could only be resolved by a full case.
  • Third: Montanbw above summarizes my thoughts well in the sense that I fully agree with much of what PumpkinSky, Heimstern Läufer, Thryduulf, and others say in that this PD falls short of an optimal solution to the infobox debate. Still, perhaps it is best I speak my peace in my own words.


  • To say that I am disappointed in this PD would be an understatement. I was hoping for a fair and equatable disposition to all sides. This is not it. It may well chill any discussions or inclusions of infoboxes in the near future; I would certainly hesitate to add an infobox to ANY musician, let alone "composer" after reading our ruling body's suggestions to a solution. In fact, I won't be the least bit surprised if infoboxes now begin to disappear from articles such as Paul McCartney, Tupac Shakur, Andy Williams, and others. Fortunately while our own article fails to offer certain amenities, Google does provide an "infobox" of sorts to things like Bach, in that quick date and place of birth, date and place of death, compositions, children, and spouses can be found without having to read an en.wp page.
I'm not attempting to commit wikicide by Arbcom, but I must say that frankly: After reading the original posting I must wonder if the Arbs even bothered to look at any links, comprehensively review any background, and actually follow through with clicking on "diffs" to determine a full picture of the forest. Often I see a "recidivism" statement, and I wonder if even the very basics were reviewed in this case. I do not dispute that this has been a "wp:battle" on wiki, but I remind all that it takes TWO sides to have a battle - one does not have battles on their own. Quite frankly this looks like a case of: "Hmmm .. there's 5 people in the composer project opposed to infoboxes (actually there are 25 regulars), and 2 people supporting infoboxes. Let's go with the bigger number, and hopefully that will translate to 'votes' in December". I apologize for the WP:ABF - and I'm not actually making that accusation, but the thought did cross my mind.
As far as specifics, the PD does mention in the FoF 2 blocks acquired by Nikkimaria for edit wars. Sorry .. but the actuall number is 3. Also, while "stalking" is a term that's fallen out of favor, here, still the harassment #hounding is not even addressed. (I also feel that addressing Wikipedia:Canvassing and Wikipedia:Tag team could have benefited the project here) Added to that the lack of any inclusion or mention of Kleinzach and Smerus, who's postings have been every bit as inflamitory and confrontational as Andy's, from this PD is somewhat puzzling. Indeed I would say that the committee is well on its way to declaring a "WINNER" in this debate. And no I would not support a permenant removal of Nikkimaria's tools absent evidence of misuse of those tools; however, I would support a time limited removal to recover the understanding of what the non-superuser editors must labor under. I understand there are members of the committee who do not favor this as it can be viewed as punitive; however, having worked under those very circumstances, I can say that it can be enlightening.
After long consideration I can now say that I suppose I felt that some sort of 1RR restriction on composer and infobox items would have been my preferred way forward here. I would also mention that Dave and David may want to add a "recidivisim" clause to the PD as it is often done in other cases. I'll also say that while I don't fully understand the "wikidata, metadata, microdata, what.ever.data" .. I do wonder if it positions Wikipedia better in the future of search engines. I also appreciate the Levels of consensus principle, but I'm not sure it's strong enough to explain the three levels. 1. Community 2. Group/Project 3. Article I feel that there's enough ambiguity there to further muddy the waters, and feel that further clarification would be of benefit.
Now, having berated the committee - I must also mention a few things that I found to be positive. I very much appreciate that both Dave and David were responsive to concerns, and communicated well with us. I also commend the lack of "legalese" in the PD - much easier to understand that way. While I have and do find many faults with the committee as a whole, there is not a single member of the committee that I do not respect both as wikipedians and as people. My own view is that the committee has grown far to large (and by extension: diverse) to be efficient, consistent, and productive; but I do appreciate the effort that all of you put in here. I know it's a tough job with little reward beyond the title.
Question: I have two pages I'd like to either delete or move to a public area:
  • User:Ched/RfC - Infobox - as this is a discussion with multiple people, it should likely be preserved - suggestions welcome.
  • This page should definitely be preserved and there is absolutely no reason why the discussion there shouldn't be continued, though you will need a strong guiding hand to produce an end result. If you read my comments up above and elsewhere, and those of some of my fellow arbitrators, you will see that there is very definitely a recognition of a need for such discussions to take place, even after this case has ended. The true resolution to meta-philosophical disputes such as this arise from widespread and well-planned community discussions, not from arbitration cases. The community need to continue discussing things and moving forward on this and other issues. But the discussion needs to be better planned than what took place there, and more widely advertised. Have a look at the 2010 RfC on microformats that is mentioned on the PD page for an example. Carcharoth ( talk) 22:34, 17 August 2013 (UTC)
  • User:Ched/infoboxes - a page I was working on to organize evidence, unless prohibited I will do a "user requested deletion" upon case closure.
Finally, Thanks to all. Apologies to all. Hopefully if/when I feel the desire to return to editing I will never hear the word "infobox" again. I will also be avoiding any of the Admin. related drama boards if/when I return. (at least for the foreseeable future) Cheers. — Ched :  ?  20:20, 17 August 2013 (UTC)


suggestions

  • "5) Wikipedia's mission is to built an encyclopedia" ... should this not be "build"? Built is a past tense. — Ched :  ?  21:04, 17 August 2013 (UTC)
  • "2) There is no general rule on infoboxes, meaning there are regularly debates regarding the use of infoboxes on articles. The debates are overwhelmed by a number of editors, who have been listed as parties on this case.". Very much a nit-pick, but I personally would say " ... some of whom have been listed in this case." I say this because I don't believe, in fact I know that not everyone involved was listed as a party here. — Ched :  ?  22:15, 17 August 2013 (UTC)
  • "6) Gerda Arendt (talk · contribs · deleted contribs · logs · edit filter log · block user · block log) has added infoboxes to many articles systematically,[12] and without prior discussion.[13]" I think you are getting dangerously close to choosing one essay over the other, and I suspect a "remedy" outside some clear and documented "warnings" falls well outside Arbcom remit. — Ched :  ?  22:25, 17 August 2013 (UTC)

Why no mention of User:Pigsonthewing's possible Conflict of Interest?

Pigsonthewing self-identifies as Andy Mabbett. On his User Page, Pigsonthewing links to his interests page: User:Pigsonthewing/interests. On that page he writes "My paid work includes delivering advice and workshops on and training in the use of Wikipedia and sister projects, for example and links to this page, where a short biography of Andy Mabbett includes the sentence "His [i.e. Andy Mabbett's] advice has been sought recently by organisations including Google and FourSquare (on their use of Wikipedia data); and The BBC, Facebook and the London Assembly (on microformats)." When I asked him if he had a WP:Conflict of Interest, Pigsonthewing twice referred me to this Interests page ( diff), but would not say if he has a COI.

I raised this possible COI in my evidence, and it was mentioned by Smeat 75 in their evidence, and mentioned by Riggr Mortis. Despite the fact that Pigsonthewing and his defenders wrote at length in the Evidence and Workshop and associated talk pages, no one else mentioned this apparent COI. To me this at least meets the criteria for reasonable suspicion, and I assumed that ArbCom would address this issue in some way.

Ruhrfisch ><>°° 13:12, 18 August 2013 (UTC)

Note also that in Resolute's evidence, they stated " I think Ruhrfisch's questions about potential COI and his relationship with those organizations are valid, and should be answered". Delicious carbuncle ( talk) 03:05, 19 August 2013 (UTC)

Comment from Choess

As an uninvolved party who's watched this with some interest, I think the PD is generally shaping up along reasonable lines. A few thoughts:

  1. If ArbCom is looking to restrict Andy in a closely tailored fashion to prevent disruption, I think the language of Remedy 1.1 is sufficient. Perhaps amending it to "adding infoboxes to articles or their talk pages or discussing the addition of infoboxes to articles or classes of articles" would make the scope clear. As I read it, this would not prevent him from developing new infobox templates or suggesting changes to existing ones, but their acceptance by the community would determine whether they were actually added to articles.
  2. I'm not convinced Remedy 1.2 should be off the table. Looking back at ArbCom's dealings with Jack Merridew/Alarbus/Br'er Rabbit and Rich Farmbrough, in both cases, ArbCom attempted to impose carefully tailored restrictions on technically talented contributors who engaged in disruptive behavior, hoping to retain their contributions. The subsequent history of both editors suggests that this approach may not be entirely fruitful.
  3. Contra Carcharoth, I think there's a very clear line between Andy's second RfArb and the current case. While the ad hominem conduct evident in the first RfArb and to some extent in the second has largely been replaced by parliamentary tactics, a quick perusal of the evidence in the second case will show the same essential problems (battleground behavior, inability to acknowledge adverse consensus), occurring in substantially the same topics (classical music, composers, opera) now before ArbCom.
  4. I tend to agree that the conduct of other parties rises to the level of admonishment at worst, but Gerda's recent statement that "To ban Andy is no solution at all, because - as I pointed out in June already - you will still have to deal with me until you ban me also ;)" suggests that Remedy 3.1 may be warranted as a preventative measure. Hopefully Gerda will clarify her intentions and make this unnecessary. Choess ( talk) 17:46, 18 August 2013 (UTC)
I clarify that you can ban a person, but not an idea. I believe that for almost every article, an infobox is not damaging it, but is a service to readers. I respect an individual editor's wish to not have an infobox, ask Tim riley. I am looking at opera articles where an infobox was made available but is opposed by some editors who don't like any infobox, - one of them mentioned dung. I am waiting for some more factual pros for keeping the present side navbox, which duplicates facts from a footer navbox, instead of an infobox for the specific article, example The Ban on Love. I am waiting to see how consensus can be established in case of disagreement. I believe that arbitration should serve this purpose. -- Gerda Arendt ( talk) 19:23, 18 August 2013 (UTC)
I saw my name pop up on the new notification gizmo. I confirm that wherever Gerda and I have disagreed over info-boxes it has always been in the most colleaguely and reciprocal way. Gerda is one of my most cherished colleagues, and our disagreement over this one matter is a side issue as far as I am concerned. I abandoned editing WP for some months last year in the face of what seemed to me to be bullying over info-boxes, but Gerda was assuredly not the culprit. Tim riley ( talk) 19:40, 18 August 2013 (UTC)
Duly stricken. I think you are the person most likely to be successful in promoting infoboxes in classical music and opera articles, because a) you know and write a great deal about these subjects and b) you're capable of backing down and working on other things when you find that other people don't agree with you. Good luck, and I hope we'll be reading your lovely articles about music for a while. Choess ( talk) 00:13, 20 August 2013 (UTC)

Uninvolved party

I know that this decision has the potential to impact editors' lives and may even shape policy about Infobox but after reading this talk page I went to go look at the Proposed Decision page and was surprised to see that only 3 or 4 Arbiters have weighed in, they haven't agreed on or objected to every single proposal (many are skipped) and it is very possible that minds could be changed if someone comes in with a compelling argument. I take the delay in other Arbiters posting their views is because it isn't a simple case (or they could all be on vacation!).

This is all to say that none of the proposals that impact specific editors has a majority of votes and a lot can change (for or against) in the next 24-48 hours. I would hold off celebrating or despairing until all of the votes roll in. NewJerseyLiz Let's Talk 21:16, 18 August 2013 (UTC)

Comments from Worm That Turned

I must apologise to everyone that I haven't had as much time as I would have liked to come up with a solution here. David and I were working together on a decision, then unfortunately real life stole me away from Wikipedia. I will be going on an indefinite wikibreak as soon as I've tied up a few loose ends.

So, here's a few thoughts, which might hopefully help the creation of a solution. Bear in mind that I came to this case unaware that there had been years of infobox wars.

  • Infoboxes, in general, appear to be a good thing. They allow information to be offer key facts about an article to our readers and facilitate reuse of our content. They are customisable to allow editors to decide what to put in or leave out.
  • Articles do not need infoboxes. If after discussion at a talk page it is decided that an infobox is not needed, that should be accepted.
  • The use of an infobox in an article is a content decision, not a maintenance decision. It should be added as part of content creation, and they should not be added systematically to articles.
  • Edit warring over infoboxes should not happen. Ever.

If anyone can create a solution out of those thoughts, please do!

Now, to a few editors specifically.

@ Pigsonthewing: I do see that you've managed to keep yourself from falling off the edge into an arbitration case for 5 years, since the end of your ban. However, you've carried on with many of the same behaviours, especially around infoboxes. I attempted to craft a solution whereby you could be removed from any discussion if you were dominating it, but it was pointed out that you are still on article probation and that clearly isn't working.
@ Gerda Arendt: I have seen systematic additions from you, please do keep in mind that infoboxes are a content decision, not a maintenance decision.
@ Kleinzach:@ Smerus: I have been unimpressed by the attitude you have both taken reading around the discussions, though little evidence was provided regarding it. You have tarred discussions with the same brush, refused to assume good faith about the actions of editors. Suggestions that infoboxes cannot be put on the talk page for discussion because someone might copy it onto the main page is clearly stifling discussion. There have been more incidents and if I have more time, I'll be adding something regarding them.
@ Nikkimaria: Again, I have been quite unimpressed by your actions, especially coming from an administrator. Reverting without discussion or explanation even in the edit summary is unacceptable. As is edit warring over these matters. I haven't looked far enough into the allegation of following edits to add that to the list, but overall it doesn't make for a good picture.

I believe that covers everything. I'll try to find some time to vote and possibly add some more bits over the next few days WormTT( talk) 09:05, 19 August 2013 (UTC)

(Reply from Gerda - to where I am addressed above)
I don't add where I think it's contentious (learning slowly...). I don't believe to add an infobox to a composition or story - my only cases of "systematic additions", like Schubert's masses, Kafka's short stories - are a content decision. - The newly developed infoboxes for opera should not be contentious, but I realize that they are and am more cautious. (Please see Siegfried: I only proposed on the talk.) - I am on 1RR, take any revert, there were many. I could have provided evidence against other editors but didn't want to. -- Gerda Arendt ( talk) 09:26, 19 August 2013 (UTC)
@Worm, re Klein and Smerus...they should have been part of the original proposed remedies, but glad you seem the need. Real life is more important, but within the AC world, I'd submit it's better to delay a PD and case closing in order to get a sound and fair decision that to rush and leave a swiss cheese decision. The problem of long term issues is a tough one. The only real solution is to for the parties on all sides to realize the problem and change and within the wiki world that's very difficult to do. PumpkinSky talk 10:01, 19 August 2013 (UTC)
Part of the reason for the delay we had was that I was unable to keep working on the PD. As time went on, I became less available, not more. I'm not going to hold up the case for an indefinite period on the vague hope that I might suddenly get more time, especially given that it is unlikely to happen. WormTT( talk) 10:18, 19 August 2013 (UTC)
Well, some arb needs to pick this up because right now this is an atrocious PD. It's better to delay against than make a bad ruling. PumpkinSky talk 21:16, 19 August 2013 (UTC)
The committee is tasked with making a decision which resolves the problem. I may see areas for improvement in the PD, but I'd hardly call it atrocious. WormTT( talk) 09:30, 20 August 2013 (UTC)
@Worm: I reverted without edit summary on a single occasion, and had already long agreed not to do so again. And yet there is no mention in the PD of rollback being abused to revert me. The PD also characterizes my participation in discussions as "sniping", based on a talk page demonstrating neither incivility from me (though one comment was admittedly sarcastic) and worse behaviour from others not mentioned, and ignores multiple diffs of both incivility and gross personal attacks presented by a variety of people in Evidence. I admit that some of my actions with regards to these debates were suboptimal, and have endeavoured to improve my responses more recently and reach a compromise with those on the "other side". But if the PD as presented reflects the overall picture, it's missing a few pieces, and is unlikely to either solve the problem or encourage a more collaborative approach. There were a few good ideas on both "sides" in the workshop - isn't it possible to consider more of them? Nikkimaria ( talk) 16:30, 19 August 2013 (UTC)
I apologise, I had not seen that you had agreed not to do so again and that does make the situation better. Could you provide diffs for rollback abuse? I appear to have missed that too. I'm afraid the reason that you've been singled out is that you are an administrator, you should be setting the example for the rest of the community. Effectively, you should know better. WormTT( talk) 09:30, 20 August 2013 (UTC)
(watching and involved) Nikkimaria and I arrived at an agreement of mutual respect, so much better than restrictions if you ask me. She has been singled out because she did most reverts of infoboxes (about 20). As you can see here, her edit summaries improved greatly from "cleanup" (#28 Sparrow Mass) to "rm: several errors or oversimplifications, net negative; also per previous agreement. feel free to discuss on talk" (#49 Cantata academica). Both discussions are open. -- Gerda Arendt ( talk) 09:49, 20 August 2013 (UTC)
This one was presented in Evidence, same paragraph as some CIV/NPA diffs. Nikkimaria ( talk) 03:47, 21 August 2013 (UTC)
Thank you Nikkimaria, that has helped, sorry I missed it. WormTT( talk) 09:54, 22 August 2013 (UTC)

@Worm: See my comments in "my" section above. I am concerned about your comment "and they should not be added systematically to articles..." - MANY wikiprojects have a standard article design that DOES in fact ask - nicely and informally - that an infobox be part of the standard article layout (note WP Horse racing, for example, see, e.g. Paynter (horse)). While I suppose someone who is an anti-infobox fanatic may insist that they "own" an article in project and demand removal of an infobox there, I really do think that the projects can be allowed to recommend a starter template and a standard design, even if they can't "demand" it. Ditto things like chemistry ( oxygen) or gems like the Yogo sapphire. Just saying. Montanabw (talk) 21:33, 19 August 2013 (UTC)

I think that's a very sensible position, but should not the reverse also be true, that WikiProjects can recommend, if not demand, that an infobox be omitted from the "standard" article on the grounds that infoboxes usually do a poor job of representing that subject's articles? (cf. the recent removal of the "influences" parameter from Template:Infobox person: I'm sure there are a few cases where it could be used reasonably, but consensus seemed to be that it was more an attractive nuisance than a useful tool.) Choess ( talk) 00:35, 20 August 2013 (UTC)
Indeed. I have long supported the ability of projects, not set in stone, to either mandate and deprecate infoboxes for particular types of articles. But in the types of articles that are expected to add them, someone else will come along and do it. Johnbod ( talk) 01:31, 20 August 2013 (UTC)
"Sensible position": the name of my project is opera. The project made an {{ infobox opera}} available in June, concise and in keeping with the recommendations in Brianboulton's Signpost essay. I tried it in operas. Some are accepted, others were (rather systematically) opposed and reverted by those who don't like infoboxes for composers. See for example Götterdämmerung and feel free to join the discussion. -- Gerda Arendt ( talk) 08:30, 20 August 2013 (UTC)
I had an initial (not positive) reaction to Worm's ".. not be added systematically…' comment. However, after thinking about it, I believe Worm has a good point. Some of the concerns here are founded in a different interpretation of "systematic" than I came to have after reading carefully. We have many editors who perform valuable maintenance tasks. In many cases, those edits can be done "systematically" and without needing an expert's understanding of the subject matter of the article. I'll give an example. I recently created a task force on women's basketball. We do not yet have a template for the talk pages, but once one is created, I can imagine an editor finding an appropriate cat, and "systematically" adding the template to all articles in the cat. That can be done by an editor who knows little about the subject. In contrast, I think Worm is suggesting that such a "systematic" edit is not such a good idea with infoboxes. Even if some Wikiproject identifies the inclusion of an infobox as best practice, and an editor finds a cat whose every entry is within the project, it would not be wise to " systematically" add the infoboxes. Why? Because infoboxes take parameters. If an editor plunks a blank infobox into an article, it will make the article look unfinished until someone populates the fields. If the editor chooses to populate the fields, they might get some right, but might blunder on others. In many cases, it take an editor who is conversant with the subject matter to properly populate the infobox. An empty infobox is arguing worse than nothing at all , an improperly filled one is arguably worse than an empty one. If a maintenance editor wants to do something, perhaps they should add a note to a talk page informing editors that there is a suitable infobox, but leave the actual adding of the box to the editors who know how to populate it. Worm is suggesting that infobox addition be part of the content creation process, not part of a maintenance edit. -- SPhilbrick (Talk) 18:47, 20 August 2013 (UTC)
Dave does make an interesting point, but there is no policy or guideline that supports the notion that "systematic" addition or removal of infoboxes is frowned upon (other than a local RfC at one WikiProject) - indeed, such a recommendation would hinge upon each person's idea of "systematic". We need to discuss what is best to do whenever either a new infobox template is created to meet a particular demand (such as {{ infobox opera}}), but also we need to consider how to make use of a database that has been created. What if I come into possession of a verified database of notable monuments in Bavaria as used in ? May I use {{ infobox monument}} to make use of that data where we have an article already, or would that be "systematic"? Could we systematically translate the articles from de-wp, adding infoboxes as we go along? Commons:Wiki Loves Monuments generates many such databases from many countries and there's a debate to be had about how we can best use such data, so I think that a ban on "systematic" additions would be premature, and certainly far too early to base a sanction upon. -- RexxS ( talk) 01:05, 21 August 2013 (UTC)
I would disagree that no policy or guideline supports the notion. The very fact that infoboxes should be discussed at each individual article makes it a content creation decision. Assuming we can divide the types of edits people make into content creation and maintenance, then the addition of an infobox falls into the former, not the latter. For clarity, I would consider maintenance to be tasks such as categorisation, stub sorting, adding wikilinks, formatting and stylistic changes such as number and position of headers or placement of images, and simple copyediting such as grammar and spelling fixes. In general, these should not change the meaning of the article for the casual reader. Content creation on the other hand, would include addition and removal of text, images, tables, references and so on. The addition of an infobox should be considered part of the latter. The distinction is important as the former can be done by any editor on any article with minimal knowledge of the subject, whilst the latter should be done by an editor who has some knowledge of the subject, more than a cursory glance at the article.

As to your questions, RexxS, if you are creating the articles and have sufficient knowledge and understanding to write a stub based on the verified database, I see no reason why you should not be adding an infobox at the same time. That is part of content creation, and it is recognised that diligent mass content creation is acceptable. Similarly with translation, if you are diligently checking sources, you will have sufficient understanding to add the infobox. WormTT( talk) 09:54, 22 August 2013 (UTC)

And yet there still is no policy or guideline that recommends against systematic addition of content. For example, there are a lot of stubs about plants and Indonesian administrative regions (if I recall correctly) that were created from a database. There were complaints, of course, but the overall opinion was that once we get a basis for an article, then other editors will improve what is there. So it is with infoboxes; if one is added, then it is likely that its content can be refined by adding or removing parameters. I was actually posing the question about adding {{ infobox monument}} to make use of a database where we have an article already - is the answer the same as if we were creating a stub? If so, then I have to take issue with your underlying assumption: that there is a binary division between an editor with "minimal knowledge" and an editor who has "some knowledge of the subject". There is a continuous spectrum of knowledge on any subject and it is a recipe for conflict to allow editing only from those who claim to know the most. By that logic, if Andy were an expert on classical music, you'd be perfectly happy with him adding infoboxes - and yet he wrote a monthly column for a classical music magazine, so he demonstrably has more than "minimal knowledge". In the first half of this year, he added about 60 infoboxes, and more than 50 of those were accepted without a problem. Nikkimaria reverted 6 and Andy walked away from each of them, as I had advised him to previously. I'm sorry but that is not a battlefield mentality. The problem I complain about is that additions of infoboxes - no matter by whom - in one small area are invariably met with a revert by the same handful of editors with the only reason being that it wasn't notified to WikiProject Composers first. If you don't tackle that ownership problem (tq|"Please clear this with WikiProject X first"}}, we'll just be back here in a month's time. -- RexxS ( talk) 12:57, 22 August 2013 (UTC)
I see no issue with a starter template, or a general explanation that infoboxes are recommended or not by any WikiProject. The ultimate decision though comes down to discussion at the article. Editors should not go through a group of articles, adding infoboxes to each systematically, or indeed removing them in the same manner. There's a difference between "recommending" and enforcing the recommendation. WormTT( talk) 09:30, 20 August 2013 (UTC)
I am not sure I understand what you mean by "adding systematically". As it has been used in findings about me, I guess I better understand. When I add an infobox, I know how to fill the fields, be it an opera, a short story or a church. I typically don't have time to add infoboxes to articles other than my own, those related to them or otherwise of interest to me. Is that "systematic? Unwanted? Once the template for operas became available I tried to use it, because I am interested in operas and sincerely believe that opera articles are better with an infobox instead of a navbox that is uniform for all articles by the same composer. Look at GA (as of today) Fatinitza and compare to before. -- Gerda Arendt ( talk) 19:32, 20 August 2013 (UTC)

Comment from Giano

Ched is a friend of mine and one of Wikipedia's good people, so I sincerely hope he won't be offended by me saying that the bringing of this case was somewhat naive - especially, as the obvious conclusion has to be the exclusion of the main player and protagonist, Andy Mabbitt; something I wholeheartedly support and that I suspect Ched does not. However, Ched should not be too downhearted: some good can come of the case and it should be the unequivocal endorsement by the Arbcom of this finding [46], regarding the 'Use of infoboxes', because it gives those of us who feel downtrodden by the pro-infobox crowd something concrete to quote in all the many future debates/wars on this subject on pages from music and architecture to outer space. As a postscript, I would ask the Arbcom to go gently with Gerda; she's a good editor and she means no harm - she's a little hung-up with the use of infoboxes, but I think she amicably accepts that they are not everyone's choice. Anyhow, that's my view on what is probably an unsolvable problem.  Giano  20:46, 19 August 2013 (UTC)

Offended? Absolutely not Giano. In fact, I'm outright honored to be considered a friend - and I do very much appreciate you trying to guide me to take some sort of direction in the beginning. Naive? Yes, I do have to plead guilty to/of that. Sadder yet is the fact that I actually communicated with a former arb, and was told exactly what to expect. (quite accurately I might add) My request was born out of frustration at all so many discussions on the topic. I did learn a few things though. First: have a target in mind, be willing to point fingers, have the diffs, and be willing to go for the throat. Use the diffs in evidence - then give what you want in the workshop with the FoF, and ask for bans in the remedy. There should have been at least a dozen other parties to this case (on both sides) which I was reluctant to name. Not really my style, so I doubt I'll ever return here. Yes, you're right - I do NOT want to see Andy banned - I think he has far too much positive impact to offer the project, so I guess we'll just disagree on that part of it. Not that I'm a full-blown "add infoboxes to everything" person - in fact your examples of a historic building is a good example where I'd agree that it would be counterproductive to add one. Still, when it comes to people - I do favor them (generally).
I do feel bad for the position that I put Dave/Worm and David in though. I dumped everything in Arbcom's lap, stepped back and let the chips fall where they may (partly out of necessity due to unforeseen things in real life) and hoped they would find or invent some sort of 1RR thing, and state that "Projects" can not "own" things, "canvass" and "tag-team" editors who are trying to improve articles. While being creative has happened in the past (Delta/Betacommand) - apparently that is not S.O.P. It seems that the Arbs must work with what is presented in the workshop, and without anyone building a case against the composer group ... there was only so much they could do. I am encouraged that Nikkimaria and Gerda are working together, and I even see signs of Nikki taking things on board - that I am very happy about. I'm also very encouraged by the fact that Dave/Worm and David stayed with us, were responsive and communicated and updated everyone thoroughout. Add to that the fact that Carcharoth put quite a bit of time into reviewing things, and offering suggestions to a way forward? Yes, as much as I see this particular committee as one of the most inept I've ever seen (the Malleus/George situation is a good example of that), the individuals are impressive to me.
I'll continue to login and check my talk page until this is closed. I'll continue to fix typo and syntax items where I can, even if I'm not logged in. I am tired though. Over the last year I have alienated people who were friends. I took sides against people who were friends because I thought it was right for the project. I was not "loyal". I did what I thought was right in my heart. I'm tired of admins. being "super-users". <aside> I know that a lot of kids will shortly be returning to school (which should alleviate some things). Still, I am tired of the bullshit. Years ago I was very proud of what I did here. The work I put into WP:RIP is something I will always be proud of. In the beginning I was even proud of being an admin. ... not so much anymore. I've met a lot of great people here, and I am happy about that. Still, I think when this case closes I will need a break. But I am rambling here .. so I'll close with "Best to all" Thank you for the kind words you've offered me Giano. I do consider it high praise indeed. — Ched :  ?  04:09, 21 August 2013 (UTC)

Comment from John Cline

I had resolved to stay out of this discussion; to observe and learn if you will. All I managed to learn however was more about my own weaknesses. I find I am incapable of observing the mistreatment of an esteemed colleague without intervening aid. Also I find, if I reply to provocation, I am not proud of my prose; instead—ashamed!

Please understand that when not discombobulated, my stringent endeavor is to publish prose that I can be proud of; even succeeding at times. Yet the error is mine for having not further endured.

Help me to better endure by allowing that I edit under the enduring principles that founded this great site. Principles that do not embrace debase provocation; allowing one to withhold their own indignation in favor of observing the institutional retribution that is all but assured in policy.

It is well known that a plethora of policy insight is ignored, so the belligerent can edit this encyclopedia. Perhaps this is not an unsolvable problem after all? Instead, simply an example of one that can not resolve by ignoring all rules:)  John Cline ( talk) 09:04, 20 August 2013 (UTC)

Couple more thoughts

A couple more thoughts here to try and help clarify some things (see also the section above that I added earlier).

  • Firstly, unlike Worm That Turned (who "came to this case unaware that there had been years of infobox wars"), I and several other arbitrators have been very aware for years of the tensions surrounding infoboxes. But this doesn't mean that we are able to provide a panacea or that an arbitration case will provide a 'silver bullet' that will magically resolve these tensions.
  • The only thing that will help improve matters in the long-term, and it is worth repeating this again and again until people actually get it, is to have productive 'big picture' discussions that help editors settle on best practice and sort through any differences and disagreements they may have, and then people can carry on with writing articles and curating article content. Some people are able to discuss things calmly and work through their differences, or explain clearly why they disagree. Some are not able to do this, and need the help of others (or to be kept away from such discussions).
  • Infoboxes are templates designed to summarise key points, not just in a single article but across a range of articles. This is why there is a difference between systematically adding infoboxes at random (e.g. to a list of articles created by a single editor) and systematically adding infoboxes to articles in an area an editor (or group of editors) have some knowledge of and have considered carefully the best way to present the information in an article. This is why infoboxes tailored to specific subject areas can be helpful - it shows that a group of people have considered the various options and how best to present the information common to a range of articles within the same topic area. When you get broader infoboxes such as those for people in general (most of my experience with infoboxes has been on biographical articles), then it becomes more difficult to handle and a case-by-case approach is usually needed. Ditto for other topics.
  • The key point is to also have discussions about groups of articles, not just individual articles. To form consensus at a group level as well (to avoid endless discussions on individual articles), but to still strike a balance that allows maximum flexibility and exceptions where needed (such as not using an infobox if that is desired). Sometimes the merging of infoboxes helps focus such discussions, sometimes excessive merging hinders such discussions. What you don't want to do is end up with the bureaucracy that is sometimes associated with the requested move process - that evolved to help people resolve differences over article titles, hopefully people can resolve their differences over infoboxes without needing anything like that.
  • It may help to draw an analogy with discussions about whether to include an image in an article or not, or whether to include an article in a particular category, or how to write the lead section. Those discussions can get contentious, but the nature of infoboxes, placed at the top of an article and performing a similar but different function to the lead section, makes them particularly prone to causing certain types of arguments.

The whole argument about metadata and data in articles is something else again. That needs several rounds of proper community discussion. Anyway, most of the above isn't anything new, but the community absolutely needs to have proper, structured discussions, planned and properly publicised. A key part of the planning is sorting out where to publicise discussions, and having a representative selection of people working together to produce a summary and questions suitable for a community-wide request for comments (some of the workshop material is a good start). This can be a long and difficult process, but it would be better than endless low-level arguing. ArbCom can suggest that this should happen (I've suggested it to my colleagues), but we can't (and shouldn't) require that to happen - the real impetus needs to come from those willing to participate in such a process. Carcharoth ( talk) 23:31, 19 August 2013 (UTC)

Looking at the PD, it seems like the decision will actually have little to do with Infoboxes and everything to do with conduct and a lack of collaboration (conduct, not content). It's about how differences are settled (or mishandled) and the fundamental content/policy issue could be almost anything - Infoboxes, COI, NPOV, anything that causes division among people (which is almost everything).
It reminds me of political scandals where the scandal isn't the news but the cover-up is. I'm not sure how much it would help but I think more should be written, policy-wise, on negotiating conflict when trying to come to a consensus. Mostly I see consensus arriving when one of the parties decides the fight isn't worth it, not because anyone has changed their mind about the issue of contention.
I think WP policies on consensus underestimate how difficult it is to arrive at, how conflict is to be expected and what should happen when differences appear to be irreconcilable. I'm not sure what the solution is but I think if people saw conflict as predictable and not exceptional, a lot fewer cases might arrive at the ARBCOM doorstep. Liz Let's Talk 00:56, 20 August 2013 (UTC)
I am rather new to the topic of infoboxes - as you all know from my evidence I was against them and converted, - very dangerous ;) - I believe we need a better way to discuss their flaws and merits. Sorry, I don't think that it happened (yet) in the often quoted Rite of Spring discussion which Andy started by only asking "Why ... no infobox?" (Now how disruptive is that?) - I started to discuss a very simple example, article type opera, template new and concise: The Ban on Love, - help there please, let's make it a model discussion! - I don't believe that we achieve progress by restrictions. -- Gerda Arendt ( talk) 08:48, 20 August 2013 (UTC)
@Carcharoth: yes, I hope that the model discussion could serve operas in general on a "group level".
@Liz: no, I did not foresee conflict on operas as predictable, - and still nobody could point out why a side navbox duplicating information from a footer navbox would be superior to an infobox on the specific article, - but I am open to learning. -- Gerda Arendt ( talk) 08:56, 20 August 2013 (UTC)
One of the articles where infobox opera was installed was just promoted to GA: Fatinitza. -- Gerda Arendt ( talk) 09:58, 20 August 2013 (UTC)

Comment from Victoriaearle/Truthkeeper88

Reading all these comments, and well-aware I'm not one of the people who can discuss calmly as per Carcharoth's statement above, it occurs to me that this case is about pure frustration and that's a tough one for the Committee to address.

Some background for Committee members unfamiliar, because a pattern exists and it's not only about classical music - that's simply the arena where it ended up. It began in early 2012 and is still ongoing, and honestly my own frustration has boiled over more than a few times during that period. Some examples for those of you unfamiliar with the tactics and the players: Ezra Pound in February 2012, Murasaki Shikibu February 2012, Ian Fleming July 2012, George Solti July 2012, Melville Island August 2012, Pilgrim at Tinker Creek September 2012, AN Br'er Rabbit community ban, October 2012, Andreas Sholl March 2013, Sparrow Mass March 2013, followed by many more in the classical music project, one of the more notable being The Rite of Spring, the day after TFA, May 2013 and now referred to as the "Ban on Love" on multiple pages. This then progressed to various music related articles which I didn't follow but was vaguely aware of.

The issue, however, in my view is not about infoboxes. The issues are deeper, more entrenched, causing enormous damage in terms of attrition of highly productive editors, and for at least a year and a half has needed attention.

In terms of how the arbiters are to handle this, I'd suggest to follow your inclinations, ignore pleas (including this), do the job you were elected to do (and like all the rest of us, it's frustrating to work for free), and decide how to eliminate the disruption.

In terms of individual editors, I'd suggest looking at their overall record. For example, Nikkimaria has a record of pitching in ceaselessly to keep copyvio from the mainpage, in checking sources at FAC (for a while she was the only person there doing that and as far as I know singlehandedly checked each nomination) and is an enormous asset to the project. Look at each editor's contributions, assets, and weigh it up. I think this is very tough and important case. If it needs to go back to the drawing board, do so. If you all know how to vote, do so and put us out of our misery. But realize that a lot of content producing editors who could be reviewing and writing are currently tied up here, or just plain frustrated and work has ceased. That is not good for the project.

Thanks. Victoria ( talk) 05:53, 20 August 2013 (UTC)

May I factually clarify that you seem to confuse The Rite of Spring and "The Ban on Love". One is a ballet by Stravinsky, the other the translation of Das Liebesverbot, an opera by Wagner. Both articles are no biography. I tried to initiate a model for how reaching consensus might work in an infobox discussion, The Ban on Love. Please take a look. You may also want to look at a comparable work, where an infobox was accepted without disruption and frustration: Fatinitza, a GA nominee. For discussion as I like it see Peter Warlock. I agree that Infoboxes is not the topic of the case, - reasonable discussion about infoboxes should be. There is hope. -- Gerda Arendt ( talk) 08:03, 20 August 2013 (UTC)
There may be hope, but I fear that it, and any remaining goodwill towards you and your mission, Gerda, is dwindling fast as a result of your relentless persistence. For example, I have engaged in a perfectly civilised debate with you concerning infoboxes on the Peter Warlock talkpage; I understand your position, and have made my views clear there. So why, the very next day, did you have to introduce the same issue into the peer review of my current music project, Symphony No. 8 (Sibelius)? This fanning of the flames is a tiresome and unnecessary provocation. I do not wish to stifle debate, and I think it possible that a form of infobox might eventually be devised that is appropriate to the character of all Wikipedia articles. But this will require some wholesale rethinking on the concept itself, not just the adaptation of the existing model. My recent Dispatches article was a contribution to that discussion. However, very few positive steps will be taken in the atmosphere of antagonism and mutual annoyance that envelops this whole topic. And I entirely endorse Victoria's sentiment: we all have better and more productive things we should be doing. Brianboulton ( talk) 11:14, 20 August 2013 (UTC)
I am sorry that you see a proposal as "relentless" that I thought was a reasonable solution to the problem to show at a glance that the Eighth Symphony by Jean Sibelius is a composition project, not a composition. I am fine with your decision to look for a different way to show that. I was fine with your decision not to change Warlock now. - Sorry, I didn't see a problem (fanning of flames, provocation, annoyance), but will avoid it now, with respect for your view. - What do you suggest we do until that future concept will be developed? And how do we develop it if not by thinking about the options we have now? How do we overcome an atmosphere of antagonism that I - late to the topic - obviously don't take into account enough, and certainly don't want? -- Gerda Arendt ( talk) 11:42, 20 August 2013 (UTC)
I think the best thing would be to let the issue rest for a while. It is sucking too much creative energy out of the process. As I have said, there are more issues related to infoboxes than that of the reluctance of music and opera editors to adopt them, and the matter will not go away (I intend to return to it in a future Dispatches article). But if anything positive is to be achieved, there needs to be a calmer atmosphere, so if I were you I would adopt an informal temporary vow of silence on this issue. You can continue of course to work on your ideas in your sandboxes, and can invite comments there, but you should steer clear of initiating any new discussions and should generally avoid article talkpages and reviews. That would do a lot to defuse the atmosphere of antagonism to which you refer. Brianboulton ( talk) 15:52, 20 August 2013 (UTC)
Thank you, taken. I said before that I don't add any more Wagner opera infoboxes until Götterdämmerung is resolved etc. - Please forgive me Sibelius. I saw you hesitating for the composer, but thought a composition was not the same problem, mea culpa. The same way I expected operas to be less of a problem than composers, especially with an infobox developed by the project which - I think - fits the requirements for conciseness your article pointed out. But obviously I was wrong. Why - that may be part of your next article. In expectation, -- Gerda Arendt ( talk) 16:20, 20 August 2013 (UTC)
I note that Victoria has yet to address the demonstrably false statements made in her evidence, which she reinstated (after an earlier deletion), unaltered, after their falsehood was demonstrated. . Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:32, 21 August 2013 (UTC)
It is currently impossible for Victoria to edit Wikipedia outside her talk page, since she has been blocked for three months (by me, at her request). Ruhrfisch ><>°° 13:48, 21 August 2013 (UTC)
Not only did Victoria post a lengthy comment, above, yesterday, but she made 32 other edits in the last week. In none of these did she address the clear discrepancy between her false claims and the demonstrated facts. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:11, 21 August 2013 (UTC)
Pigsonthewing, let's look at your statement and then do some counting of edits.

At Wikipedia:Arbitration/Requests/Case/Infoboxes/Workshop#Evidence_by_Victoriaearle you wrote: Victoriaearle asserts that, following the Pilgrim at Tinker Creek discussion in September 2012, the "primary editor", User:Yllosubmarine, "became discouraged and left the project" and that we thus "lost a prolific female content editor". As can be seen by examining the edit logs, Yllosubmarine was editing as recently as two or three of weeks ago; as she continued to do throughout October and November 2012. The evidence appears to be blatant falsehood. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:21, 3 August 2013 (UTC)

While I agree that Yllosubmarine has not entirely "left the project", look at her contributions before and after her encounter with you over Pilgrim at Tinker Creek: X!'s Edit counter for User:Yllosubmarine. By my count, in the 10 months before your exchange in Sept. 2012 (i.e. Nov. 2011 to Aug. 2012) Yllosubmarine made 914 edits or 91.4 edits per month. In the 10 months after (Oct. 2012 to Jul. 2013) she made 88 edits or 8.8 per month on average (a decrease of just over 90%). Please note that I do not count her 90 edits in Sept. 2012 (as that month was split in terms of before her encounter with you vs. after), nor do I count her 0 edits to date in Aug. 2013 (as the month is not complete). How is this not a case where Wikipedia "lost a prolific female content editor"?

Counting another way, Yllosubmarine was a major contributor to 14 FAs and 14 GAs. She started editing in Jan. 2006 and really started contributing around Jul. 2006, so to Sep. 2012 this averages out to roughly two FAs and two GAs where she was a major contributor per year. in the 11 months since her encounter with you over Pilgrim at Tinker Creek, she has been a major contributor to zero FAs and zero GAs and a quick look at her contributions shows the vast majority are maintenance edits (things like reverting vandalism or minor copyedits). Yes, she technically did not leave, but I ask you again, how is this not a case where Wikipedia "lost a prolific female content editor"?

Pigsonthewing, I think you owe Victoria an apology. Ruhrfisch ><>°° 20:23, 21 August 2013 (UTC)

I note that you choose to start your count in November 2011. In October 2011, Yllosubmarine made only 34 edits; in September 2011, just 27 (fewer than in October 2012); August, 31. In July, it was as low as 18; in June, only 20 (again, both fewer than in October 2012). Lies, damn lies and statistics, eh? But thank you for proving my point: Yllosubmarine did not "leave" " Wikipedia. Victoria's evidence is false. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:37, 21 August 2013 (UTC)
What part of my statement that I agree that Yllosubmarine has not entirely "left the project" do you not understand? Yes, her output varies over time, but I chose two periods of equal length to compare. Do you maintain she is still a prolific content editor? (The "female" part is not in dispute - that is a joke on my part)? Can you not see that your fighting every jot and tittle to the bitter end is precisely why you have twice been banned for two years and are now in this mess? Give it a rest. Ruhrfisch ><>°° 20:47, 21 August 2013 (UTC)

PS For my own mental health, I am removing this page from my watchlist. I will be without internet over most of the weekend, but if my input is required, please let me know on my talk page and I will comment as soon as I am able. Sorry, Ruhrfisch ><>°° 20:38, 21 August 2013 (UTC)

Invitation to AGK

@ AGK: Regarding [47]: despite the arbitrators' duty to examine evidence presented in a case, It sees that you may have missed this, in which I say:

Some editors have referred to my block log. Block logs are notoriously crude and errors in them are rarely corrected. In reverse order:

  • 31 December 2012 - erroneous, for a supposed edit war, 27 hours after making my first and only edit to Hans-Joachim Hessler in five days. He [ Mark Arsten ] subsequently apologised to me off-wiki, confirming this via the summary of a null edit, in evidence.
  • 22 March 2012 - Future Perfect at Sunrise blocked me for supposed BLP concerns, undoing his contentious block with the summary "clear emerging consensus for topic ban". In fact ANI levied no sanctions for my editing, which was within policy.
  • 25 January 2009 JzG blocked for 3RR, then undid this after just twelve minutes, admitting he had miscounted.

That means that the last valid block (again that's disputable, but I won't labour the point here) was five years ago. (21:50, 3 August 2013 (UTC))

Further to the above, the "BLP concerns" were discussed here; and continued here. At the latter, Kim Dent-Brown makes clear of the former, in his opening comment (21:08, 3 April 2012; my emboldening):

There was a similar proposal at AN which can be seen here [link to that earlier discussion] but this was never agreed upon.

and the second discussion was closed (over a year ago) by CambridgeBayWeather (19:37, 7 April 2012) with the summary (again, my emboldening):

There appears to be no consensus here to do anything. I would suggest that everybody take a few days off from throwing things at each other, which is what this has degenerated into, and go make some useful edits.

There was no topic ban; and the block was clearly contested by other editors and admins. I therefore invite you to remove or strike your false statement and recast your vote accordingly. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:22, 20 August 2013 (UTC)

Pigsonthewing: Thanks for your comments. I'll look at the links you have provided regarding your block log, and then reconsider my vote, okay? (You will have to forgive me for forgetting about the evidence submission you quote above; the evidence page is one of the longest we've had in a case for some time.) AGK [•] 23:38, 20 August 2013 (UTC)
@ AGK: I notice that you have just commented on your vote, and made a minor copy edit to it, but have - remarkably - let the false claim of a topic ban stand. Why? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:39, 27 August 2013 (UTC)
@ Pigsonthewing: Is this not a topic ban? AGK [•] 09:57, 27 August 2013 (UTC)
Your vote says Blocked then topic banned for inappropriate edits to a BLP in 2012. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:02, 27 August 2013 (UTC)
Okay, I understand your objection. I thought you were claiming that there was no 2012 topic ban. In order to resolve this thread, I've corrected my comment. AGK [•] 10:11, 27 August 2013 (UTC)

Invitation to Pigsonthewing

@ Pigsonthewing: Regarding your statement above that "arbitrators" have a "duty to examine evidence presented in a case" and your often expressed concern that no one make false statements, would you please address my concerns about your possible conflicts of interest, especially with regard to WP:COI? If needed, I will gladly point you to the relevant evidence I gave or my query above, or to the requests by multiple other editors that this issue be addressed. Thanks in advance for your cooperation in this matter, Ruhrfisch ><>°° 17:45, 20 August 2013 (UTC)

I have responded to your request more than once, with a link to my published declaration of interests in my userspace. However, since you either fail to understand that, or insist on attempting to smear me with innuendo, or both, I will explain: I have no conflict of interest regarding my infobox-, microformat-, or metadata-related editing. I have received no payment from any organisation in regard to such editing. My potential conflicts of interested are all listed at that page. If you have evidence to the contrary, or in any way showing malfeasance on my part, you will no doubt now provide it; as you have provided none so far. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:00, 20 August 2013 (UTC)
Thank you for providing a more detailed answer than previously. I have no other evidence than your own words and links, but just to be clear (since, as you note, I "fail to understand" what is going on here), I want to ask another question. You write on your interests page: "My paid work includes delivering advice and workshops on and training in the use of Wikipedia and sister projects, for example" and then you link to this page, where your short biography includes the sentence "His [i.e. Andy Mabbett's] advice has been sought recently by organisations including Google and FourSquare (on their use of Wikipedia data); and The BBC, Facebook and the London Assembly (on microformats)." To me, this sounds very much like you are paid for your advice by these organizations. Since you are also a strong advocate of the commercial re-use of Wikipedia data and Wikipedia's use of microformats, how is this not "paid advocacy"? Please note that WP:COI says "paid advocacy is considered to be an especially egregious form of advocacy. Paid advocates are very strongly discouraged from direct article editing, and should instead propose changes on the talk page of the article in question.". Yours in failed understanding, and thanks again in advance for your cooperation in this matter, Ruhrfisch ><>°° 18:34, 20 August 2013 (UTC)
PS I originally used the British spelling of "organisations" and a [sic] above, as an attempt at humor. I did not think that it might be taken as unkind, and apologize (as that was not my intent). 21:17, 20 August 2013 (UTC)
I'm not sure how you can read Andy's "I have received no payment from any organisation in regard to such editing" and still maintain that you think he's been paid, based merely on a surmise you've made from reading his brief biography. I have some experience with dealing with CoI and as it happens I spoke to Andy today. During the conversation, I asked him "have you received any payment from any of those organisations you named as having sought your advice?" and his reply was "No". I checked we understood each other by naming 'Google', 'BBC', 'Facebook', etc. and he was equally clear that he had never received money from them, but he supplies his advice freely. He confirmed to me that his paid work has been in connection with helping museums and other GLAM institutions in making use of the Wikmedia projects as a Wikimedian-in-Residence. I'll tell you this in case you still can't understand it: you simply cannot generate a conflict of interest from that, because his paid work is not in conflict, but in alignment with our object of producing a free, neutral encyclopedia that is available for all - otherwise you are going to be accusing all of our Wikimedians-in-Residence (not to mention all of the WMF staff and contractors) of "paid advocacy". Now if you want him to confirm what he said to me today, please feel to ask him whether I have accurately summarised our conversation; but I am becoming increasingly worried by your obsession with this non-issue, as it is starting to look like a smear; repeat an untruth often enough and people start to believe it. You need to consider carefully before making any further unsupported accusations. -- RexxS ( talk) 00:30, 21 August 2013 (UTC)
I agree - it is hard to imagine who would have any incentive to pay for infoboxes to be created on 19th-century composers etc! Johnbod ( talk) 00:59, 21 August 2013 (UTC)
(after ec) Thank you RexxS. Just to be clear, "I have received no payment from any organisation in regard to such editing" is not the same statement as "I have received no payment from any [of those] organisation[s]" (which is why I asked for further clarification, which you have now provided). Also to be clear, I never mentioned any of his Wikipedian-in-Residence work as a potential COI. If Andy (who is quite capable of writing lengthy responses and who did not respond to my Evidence post or previous post on this page) would have made such a categtorical denial on Wikipedia several weeks ago, I would not have repeatedly raised the issue. Ruhrfisch ><>°° 01:20, 21 August 2013 (UTC)
Johnbod - I imagine a company might well pay for inclusion of metadata or insuring that all articles (regardless of topic) had infoboxes which their computers could read more easily. But RexxS has spoken and the issue is resolved. Ruhrfisch ><>°° 01:20, 21 August 2013 (UTC)
I can't see that myself at all, but whatever. Johnbod ( talk) 03:42, 21 August 2013 (UTC)
You might want to read Riggr Mortis' comments at Wikipedia talk:Arbitration/Requests/Case/Infoboxes/Evidence ( diff) or Riggr's essay at User:Riggr Mortis for more on Wikipedia as a database. Ruhrfisch ><>°° 04:36, 21 August 2013 (UTC)
I have. There's a huge difference between what people will use when it's available for free & what they will pay for. That's rather the point of open content. Johnbod ( talk) 13:14, 21 August 2013 (UTC)
I tried to discuss conflict of interest with Pigsonthewong in relation to QRpedia, following the release of the WMUK Governance Review. I didn't find his answers very satisfying. The last people I would look to for statements on conflict of interest would be people who were trustees of the WMUK board which failed to deal with the rather clear-cut case involving Roger Bamkin which sparked the governance review. Delicious carbuncle ( talk) 04:40, 21 August 2013 (UTC)
You do realize that pulling in that whole WMUK thing is WAY outside the scope of this particular case? Not that it doesn't have merit, I'm just saying it's a lot bigger can of worms than what has been presented here. — Ched :  ?  04:49, 21 August 2013 (UTC)
Of course I do, but since former WMUK trustees RexxS and Johnbod showed up here to vouch for Pigsonthewing, I thought it would be a timely reminder. Delicious carbuncle ( talk) 14:10, 21 August 2013 (UTC)
If you bothered to read the rest of the case pages, you would see that "showed up here to vouch for Pigsonthewing" is a strange way of describing my comments in this case, even by your standards. Johnbod ( talk) 14:14, 21 August 2013 (UTC)

My view on payment, which informs (though not decides) my perspective on COI matters, is that I am less concerned if an editor is an amateur or professional than if their editing is of benefit to the encyclopaedia, within policy, and is not disruptive. In my view, an editor, for example, who is repeatedly adding a template to articles against consensus, and is not being appropriately responsive to concerns on the article talkpages, is being disruptive regardless of if they are being paid. To me it doesn't matter if the writer is left or right handed - what matters is the quality and impact of their writing. I find slightly odious people inquiring into the personal life of others. SilkTork ✔Tea time 08:21, 21 August 2013 (UTC)

Comments by Andy Mabbett

Adding infoboxes

There is a proposal to ban me "from adding or discussing the addition of infoboxes". there is no justification for this; and no allegation, much less no evidence, that the addition of infoboxes, in general or by me in particular, is controversial or has caused disputes, outside of a very narrow set of pages owned by one project and related editors. There have been no ANI sanctions resulting from the additions listed below; an no blocks or warnings issued.

In the first six months of this year (i.e. all of this year, excluding the months in which this case has been proposed or active, lest anyone accuse me of modifying my behaviour disingenuously), I added approximately (I don't promise not have missed one, when reviewing my edits) 60 infoboxes. Note that this figure is only for additions to pre-existing articles. It does not include the probably greater number I included in new articles which I created; nor a couple of changes from one infobox to another.

With a few exceptions, which I shall discuss below, none were disputed or reverted; or where they were, unusually, reverted they were reinstated by other editors. They are still, at the time of writing, in the articles concerned.

Of the infoboxes listed above, which are no longer in the articles concerned six of them (that's ten percent of all the infoboxes I added in half a year; four of them on one day) were removed by Nikkimaria during the stalking of my edits by her, about which I commented in my evidence:

  • [105] - I walked away after her second revert
  • [106] - edit summary "m, cleanup, tag"; I did not revert.
  • [107] - edit summary "org"; I did not revert.
  • [108] - edit summary "rm, cleanup"; I did not revert.
  • [109] - edit summary "rm, cleanup"; I did not revert.
  • [110] - edit summary "rm, cleanup"; I did not revert.

(Those particular removals were not included in the evidence cited in the case, and presented at ANI, which was representative, not complete.)

Three further infobox additions were disputed:

  • [111] - the infobox was hidden in a collapsed wrapper, with a set pixel width, contrary to the MoS, rendering it less accessible, and moved to the foot of the article. I later reverted that, but when it was collapsed again, I walked away.
  • [112] - reverted by Cassianto with the edit summary "..as you were". I did not re-revet, but please see the discussion on the talk page. When that discussion proved fruitless (both RexxS and I tried, in vain, to find out what the specific objections to the infobox in that article were), I walked away.
  • [113] - My only revert was to replace {{ Infobox invisible}}, which was shortly after deleted as it was styled to display:none;; and I replaced it after deletion. Nikkimaria eventually hid the infobox at the bottom of the article, styling it bodystyle=width:10px;font-size:10%;. This is contrary to the MoS and makes it inaccessible. I walked away.

So, where is the issue that the proposed ban on me adding infoboxes is intended to prevent? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:59, 21 August 2013 (UTC)

I'm sure it was just an oversight, but a few days before you posted this you also added a box to Café de Paris (London). I'm not stalking, btw, I was looking at the article for something unconnected. - SchroCat ( talk) 07:37, 27 August 2013 (UTC)
The oversight is yours. As I say above, this list covers "the first six months of this year (i.e. all of this year, excluding the months in which this case has been proposed or active, lest anyone accuse me of modifying my behaviour disingenuously)". But thank you for pointing out yet another of my many uncontroversial infobox additions. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:51, 27 August 2013 (UTC)
Yes, my mistake (not an oversight, a mistake, but thank you for highlighting errors), although I would not call it uncontroversial: I am not sure the article is made any stronger by the box, but far be it from me to start removing them, especially while the case is rolling on. - SchroCat ( talk) 09:17, 27 August 2013 (UTC)
Good point. The remedy is inadequate if it would not prevent the tendentious, argumentative and disruptive behaviour at, to pick one example, Little Moreton Hall and Talk:Little Moreton Hall that spilled over into Talk:Montacute House and (now archived at) Wikipedia talk:Manual of Style/Infoboxes/Archive 7 — Preceding unsigned comment added by 82.132.219.102 ( talk) 19:54, 21 August 2013 (UTC)
  • I think Andy is mistaken about his edits in the first six months of the year. As the anon (above) mentions and I say in my evidence, Andy was certainly causing trouble in February 2013, and going out of his way to cause it too, which is why he showed up at Montacute House. Initially, I believed an infobox topic ban might be enough to curb his zealousness for infoboxes, now I am less sure.  Giano  20:29, 21 August 2013 (UTC)

I invite the arbitrators to review the entire, and short, discussion at Talk:Montacute House/Archive 1#Infobox (only eight short posts), which was not about the addition of an infobox. The first two posts there were:

The infobox on this article is hidden. This is unhelpful to our readers. I un-hid it, but I have been reverted, with no explanation. The infobox should be displayed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:35, 14 February 2013 (UTC)

You are trolling from another page and another discussion! Go away or you will be blocked for disruption. Giano ( talk) 16:40, 14 February 2013 (UTC)

-- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:51, 21 August 2013 (UTC)

.....and indeed you were trolling for trouble from yet another of your many infobox disputes; or have you suddenly become an expert of 16th century English domestic architecture? No, the truth is that you just cannot resist bombastically trying to impose your will and views on pages about which you know nothing. Wherever you show up, there's trouble.  Giano  21:01, 21 August 2013 (UTC)
Hmmm. This seems to rest on three premises, all questionable: that the persistence of the infoboxes is a good indicator that their addition was not disruptive; that the controversy is caused by "ownership by one project"; that if, arguendo, the project has displayed unacceptable ownership, Andy's conduct has not in itself been disruptive. Judge for yourself. Choess ( talk) 00:13, 22 August 2013 (UTC)

eerrmmm... " [114] - reverted by Cassianto with the edit summary "..as you were". I did not re-revet, but please see the discussion on the talk page. When that discussion proved fruitless (both RexxS and I tried, in vain, to find out what the specific objections to the infobox in that article were), I walked away." Sorry to dip my little fly into the ointment, but that's not strictly true that you walked away. I tried to come to a compromise: you dismissed it on spurious grounds, saying "each [[WP:POINT|deployed]] by vehement opponents of infoboxes". That's falling well short of any attempts at good faith and evidence of a battlefield approach, rather than any serious attempts to come to a collective agreement - oh, and yes, as per the usual tactics, spurious allegations of ad hominem comments were thrown out to both me and Cassianto - simply for daring to have a different opinion to you, it seems. I find that your evidence on this one is extremely lacking and I don't have the spirit to go back through the others to see what has taken place in those arguments. - SchroCat ( talk) 00:45, 22 August 2013 (UTC)

Ownership

Choess raises, above, the question of ownership by the classical music project(s); I'd widen that to include some of their like-minded allies. I and others touched upon the matter in the evidence stage. WhatamIdoing said:

One of the main complaints in the music area is <!-- hidden comments --> demanding that editors respect the (dis)infobox POV of one particular group of editors, merely because the one group of editors has decided that they're interested in the article's subject. Some of the hidden comments say things like After lengthy consideration at the Wikipedia Composers project, it has been determined that infoboxes are not appropriate for composer articles. Before adding an infobox, please review the discussion at Wikipedia talk:WikiProject Composers/Infobox debates. Text similar to this appears in a substantial number of composer-related articles. This editor behavior needs to be addressed directly. A significant example of the debate can be read at Wikipedia talk:Manual of Style/Infoboxes/Archive 8#Routine_use_of_infoboxes_for_biographical_articles.

(some of the other hidden comments are more forceful than that; I'll add an example later see below).

My evidence includes:

infobox opponents (IOs) have represented... guidelines as binding (hidden comments; see above; " adding infoboxes... against guidelines") and/or representing consensus (ditto), or " instructions", even after being asked not to. They cite them in edit summaries.

and;

IOs have frequently exhibited, or supported, ownership, in contravention of core polices; in talk, and even here: ("WP:IAR trumps WP:OWN", "use of infoboxes ... more than settled ... in terms of a clear project consensus"; proposed findings)

The "views of creators and maintainers of articles (and of projects relating to them)" have not "been summarily dismissed as WP:OWN", references to OWN have followed examples or suggestions of breaches of it. e.g. Folantin's examples:

I repeat this here, in the light of AGK's comment about having forgotten my evidence.

RexxS, Moxy ( here) and others also touched on it. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 01:08, 22 August 2013 (UTC)

I find it more than a little rich that you accuse members of the classical music project of thinking they WP:OWN articles, an accusation I have seen you make numerous times, since it seems to me that you think you WP:OWN Wikipedia itself and are on a mission to make every article emit "machine-readable metadata", as in this edit from February this year, only one of many many such, [119],I recently fixed this article's infobox, which was not displaying. Another editor has now removed it, saying "it adds nothing anyway". That is patently false, as the infobox, in addition to providing a summary of key points for the benefit of our readers, cases the article to emit machine-readable metadata, such as is used by DBpedia, search engines, and, soon, Wikidata. The infobox should be restored. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:49, 11 February 2013" — Preceding unsigned comment added by Smeat75 ( talkcontribs) 02:28, 22 August 2013‎
Nothing in the comments above indicate ownership nor are beyond standard discussion. And "it seems to me that you think" is so clearly the entry to laying out an personal opinion that it is alarming to see this presented either as rebuttal or evidence of wrong doing.( olive ( talk) 01:44, 22 August 2013 (UTC))
Andy says - "[77] Not about infoboxes", no it isn't, you provide a perfect example there of what I said earlier on this page, this is not actually about infoboxes at all, it is about your fanatical drive for "metadata" as a diff from just a little before the one you quote shows: [120] Somebody has just said "it doesn't add anything" and you reply "That's patently untrue. It's adding coordinates and distances which are not otherwise in the article, as well as emitting the former as metadata, which can be understood by machines, and mapped. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:54, 19 July 2012 " Not everyone who edits WP is obliged to arrange articles so that machines can read them, there is no policy that says that. Smeat75 ( talk) 02:03, 22 August 2013 (UTC)
You appear to have missed the part of the comment, in your quote, which says adding coordinates and distances which are not otherwise in the article. That's adding them in a human readable form, so that our readers can see them with their eyes. Ownership on Wikipedia has a specific and clearly-defined meaning - clearly evidenced as having been breached by those opposed to having infoboxes on "their" articles - which is not "he says something I don't like". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:48, 22 August 2013 (UTC)

We are all working on machines. This is a wiki, machine driven. And nothing being said in the quotes you offer suggest "require", and by extension ownership. This encyclopedia some think should be edited so it can be handled easily and read easily, while suggesting that is not ownership. One is free to dislike the suggestion even the editor but extending that as somehow proof of ownership is fallacious logic, and to sanction an editor based on that kind of evidence or any like it is wrong and unfair.( olive ( talk) 02:17, 22 August 2013 (UTC))

The more forceful hidden comment, to which I referred above, is <!-- please do not add an infobox, per [[Wikipedia:WikiProject Classical music#Biographical_infoboxes]]-->. AIUI, well over 300 articles include that comment. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:58, 22 August 2013 (UTC)

Question

The only arbitration in my personal Wikipedia history where I have seen remedies this severe were with Will Beback in the Timid Guy case. Is this in any way even remotely comparable?Remember that you are laying out the worst possible remedy for Pigsonthewing. As a committee you have established where the most extreme outcome applies, have created a scale. How does this situation compare? Since I was very familiar with the TG case, I can tell you this does not compare. Where do you go from here if editors transgress on a level comparable to the worst case. There must be a consistent gradation and scale out of fairness, but also to make your job/decisions easier the next time and the next. ( olive ( talk) 01:54, 22 August 2013 (UTC))

A more apt comparison might be to Wikipedia:Arbitration/Requests/Case/Doncram: one user repeatedly engaged in an activity that he finds constructive but annoys other people, brushing off criticism, and a group of other editors interested in the subject matter responding to that intransigence with increasingly bad behavior. The two seem broadly comparable in terms of severity of the proposed remedies. Choess ( talk) 02:46, 22 August 2013 (UTC)
This is a project in which people volunteer their time and knowledge, for fun, I would imagine, in most cases. The vast majority of us are not doing it for money, anyway. Where is the fun in being confronted with an aggressive editor like Pigsonthewing, constantly insisting that articles be arranged so that machines can read metadata? Most WP editors care nothing about that and there is no reason why they should. Smeat75 ( talk) 03:43, 22 August 2013 (UTC)
This is a project in which I volunteer, so far it was fun. Where is your evidence that Andy is "aggressive". I never found him aggressive. Don't say that's because I am on his side. I wasn't always. I disagreed with his view on Samuel Barber (March 2012), but found him factual, patiently explaining, with a sense of humour even: "Unless, of course, someone wishes to argue that Barber was not a person...". I don't have time for more right now, but to see labels such as "intimidating", "belligerent", "battleground mentatality" etc. with no evidence apparent to me, simply repetition of experiences from a time past, makes me question why arbitration in the true sense of the word (as I understand it) is not even tried. - This is a project in which I volunteer, so far it was fun. Stress on "was". I know well what "frustration" means right now. -- Gerda Arendt ( talk) 14:52, 22 August 2013 (UTC)
Well, just as one example of his aggression, you could look at a discussion he himself references above - [121] where he put a table of distances into an article the day it was on the front page of the site, after literally years of arguing for such a table and being told that the creators of the article did not feel it was useful, or valuable. Yes, I think that is very belligerent, very intimidating and shows a battleground mentality, and it is not anything to do with infoboxes either, it is his obsession with metadata. There would be a dispute about infoboxes without Andy but no one else argues for them with such obsessive fanaticism, that is why I say this feud is not actually about infoboxes but about his disruption to the project and inability to collaborate amicably with others. Smeat75 ( talk) 15:59, 22 August 2013 (UTC)
The discussion to which you point was again in 2012, right? I fail to see how adding a table is an "aggression". - Andy is collaborating amicably with me, with people developing templates, with people working on templates, etc. You may want to try yourself. I love his latest article, peace and reconciliation, -- Gerda Arendt ( talk) 18:00, 25 August 2013 (UTC)
No fun so we sanction the editor? I understand frustration, frustration though, does not equal sanctions especially of the kind I see here, further, your insistence is as direct as anyone else's. This is a squabble long term yes, but a squabble, and squabbles require more than one side to even exist. The sanction should be of the kind, "Don't make me stop this car", not, "you're out of the family."( olive ( talk) 03:52, 22 August 2013 (UTC))
This would all be true if it were the first time. This has been going on for eight. bloody. years. The exact same issues over three arbitration cases including a year long ban. MLauba ( Talk) 07:10, 22 August 2013 (UTC)
Please see above. Define "this" more precisely. That a project introduced an infobox which is opposed is new! It has nothing to do with Andy. -- Gerda Arendt ( talk) 14:52, 22 August 2013 (UTC)
The context changes, the behaviour doesn't. No feedback registers. When an issue is pointed out, Andy endlessly finagles around details and takes nothing in. There is not a iota of difference in the way he handled the feedback regarding his multi-year long obsession with inserting a BLP's date of birth at Jim Hawkins (radio presenter) against the subject's wishes and annoyance, the behaviour that led to his topic ban from TFA, or what he displays in discussions around every single infobox feud listed in the whole evidence section. Heck the ANI report he filed a few months back complaining he was being stalked is a perfect illustration. Nothing registers. He's right, no matter how many uninvolved people tell him otherwise, and he will grind on and on and on. This is what has been going on for 8 years. The only relationship to infoboxes is that it so happens that this is the most common obsessive subject of his. MLauba ( Talk) 15:16, 22 August 2013 (UTC)
Once again I invite the Arbitrators to review my edits and comments at Manchester Ship Canal. In the cited discussion, it is pointed out by Tagishsimon (another editor driven off the project by ownership) that the table of coordinates and distances had been in the article, uncontested for four years. Having found it recently removed without discussion on the talk page, I restored it. When I was reverted, I joined the discussion on the talk page, where I was accused of making drive-by edits, despite my along association with the article. If I intimidated Malleus Fatuorum there, I shall of course apologise to him.

Likewise, I repast my invitation to them to review the Hawkins case, which polarised both editors and admins, but where it was again decided that there was to be no sanction against me. Both cases were over a year ago. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:34, 22 August 2013 (UTC)

Pigsonthewing is Andy Mabbett

Carcharoth comments It is worth noting somewhere for the benefit of those reading the decision that are not familiar with the background, that Andy Mabbett is User:Pigsonthewing (and vice-versa of course).. This is something that I agree would be worthwhile, and could probably most easily be done by copyediting the start of FoF3 to read " pigsonthewing ( talk · contribs · deleted contribs · logs · filter log · block user · block log) (who signs as "Andy Mabbett")". This is consistent with Wikipedia:Arbitration/Requests/Case/Gibraltar#Justin A Kuntz, which begins " Justin A Kuntz ( talk · contribs) (who signs as "Justin the Evil Scotsman")". Thryduulf ( talk) 01:31, 23 August 2013 (UTC)

Number of Arbitrators

It seems like this decision has taken so long because it's taken so long to get a quorum. Are a lot of Arbitrators gone for the summer? It seems like this hasn't gotten the attention from the entire committee it deserves. Liz Read! Talk! 18:47, 23 August 2013 (UTC)

For a complex case with loads to read, this doesn't seem to have taken an unusually long time to me, though there may be a bit of an August effect. Johnbod ( talk) 19:21, 23 August 2013 (UTC)
Thanks for your perspective, Johnbod. I saw that the case was due to be decided on Aug. 14th so I was wondering what was causing the delay. At this point, unless new motions are made, it's a matter of casting votes. Liz Read! Talk! 03:25, 24 August 2013 (UTC)
Hi Liz, nice to meet you (so to speak). Actually many of the Arbs have had a look around here. Roger is really the only one that hasn't weighed in at all yet. It's a very complex issue, so as individuals they are all going to have their own views. Several things come to mind for me though - 1. Trying to sanction some scapegoat is not going to resolve anything. 2. While most arbs can agree on the "Principles", and even many of the "FoF" things (some of which I would dispute), there seems to be virtually NO agreement on any "Remedy". That makes things tough, or more to the point - unresolved. We all want to present ourselves in the best possible light, and since arbs are people too - that include them. 3. AGK is still looking and even asking for some diffs (which if I have time I'll try to offer this weekend). 4. One forward thinking arb (Carcharoth) is looking beyond this case, and suggesting a global discussion. How much time he would have to actually guide that only he can say. But he does see the need for it. The thing is that it would need to be structured to achieve an end result rather than a circular "I like it", "I don't like it" type of thing we've seen for years.
As an aside - one thing that has troubled me in this case is the "bully" aspect. Intimidation is a very subjective thing, and is as much befalling on the the subject, as it is on the so called bully. As someone who was small in stature growing up, I learned that if I wasn't going to stick up for myself .. then I would be subjected to bullying tactic all my life. So I refused to be intimidated at ANY level; and especially over the internet. And standing up for one's beliefs is not an attempt to intimidate. I also understand that there are quiet, shy, and timid people in life who are easily hurt and intimidated. Good, kind, caring, loving people who simply choose not to battle others; either in debate or argument. But when a group of people get together to try to force a situation through in their own walled garden, outside the global consensus, then yes, I do consider that intimidation. So it all boils down to talking to one-another and getting to know the people we write with. But the "Wikipedia is not a social network" stigma sometimes thwarts those efforts. But I'm drifting into "lecture mode" again, so I'll close here. (so much for my " Closing statement" eh? Later all. — Ched :  ?  05:14, 24 August 2013 (UTC)
Thank you for your response, Ched. Although I've been editing on & off for 6 years, paying attention to Arbitration Cases is new to me so when I read that the decision is due Aug. 14th and it's Aug. 23rd and only a few Arbs have voted on solutions, it just got me wondering whether people were on vacation or something. Now that I've been told that this rate of progress finishing up a case is the norm and believing, as I do, that a better resolution is preferable to a faster resolution, I feel like my question has been answered.
As for your statement about "bullying", having worked in the area of conflict before, I'll just say that consensus building does not come naturally to people. It's slow, it delays an individual from taking action that they believe is necessary while one waits for people with different opinions to weigh in. It can be maddening to Type A personalities who just want to get the work done and not spend a lot of time talking about the process. I truly believe that aside from vandals, most editors that might be seen as bullies truly believe what they are doing is for the good of Wikipedia but that doesn't justify any effort to silence, badger, ignore or intimidate other users so one gets one way. But aside from a few personal feuds (which end up finding their way to AN/I), I don't think bullies are malicious in intent, they think they know better and trust their own instincts rather than the judgment of others. It's an unfortunate byproduct of their sense of rightness that their pursuit often results in alienating or, at worse, driving away some of their fellow editors. Liz Read! Talk! 19:35, 26 August 2013 (UTC)

Suggestion

I agree with Montana above that one editor may have been made a scapegoat here. This is a difficulty that arises with a case like this when its difficult to see where the problems are coming from. What I see is that a group of editors have been interacting in a less than positive style. Some have maintained a collaborative posture throughout as Gerda has. Others like Andy have shown improvement over his past editing practices and that must be noted.

The standard way of dealing with arbitration cases, doling out individual sanctions seems illogical here given all parties were involved in the squabbles surrounding info boxes. What Id' like to see is some out of the box thinking about how to deal with this kind of situation. Is there something that will fairly treat everyone, is not punitive while supporting ongoing work by knowledgable editors.

Suggestion: A restriction (time out) on all editors on infoboxes for one month. None of the editors named here touch an info box or comment on them. Further if any one editor does deal with infoboxes in any way, the whole group of editors will be restricted for another month. I am suggesting true collaborative work here, that those in this group be responsible to and for each other. I've worked with people in collaborative situations and used this technique, and found that the group begins to police itself, draw closer together, and those not willing to collaborate stand out in a hurry. Probably nothing new here but some thoughts on this case.

All sanctions should be specified per each editor as they are now. Editors who are not willing to improve in their collaborative skills will given this system show up immediately and that point sanctions may be applied. I realize this will be considered impractical but thought it might trigger novel thought. This is a collaborative community and collaborative remedies may be meaningful.

My concern is that three editors that I know of show a willingness to improve this situation. That in my mind is the best and most important aspect of this case.( olive ( talk) 01:05, 24 August 2013 (UTC))

Nikkimaria

I am sorry to note that I don't see attempts to improve when an editor who is being scrutinized during an arbitration continues to make this kind of edit. [122] which seems very like the pattern of edits made before the arbitration [123] . ( olive ( talk) 23:26, 26 August 2013 (UTC))

Thank you for notifying us of this (I have taken the liberty of correcting the username spelling in your heading). I'm not at all impressed that all three editors involved there (Gerda, Andy and Nikkimaria) have engaged in a discussion and sequence of editing like that during the case. The evidence presented was ample already. I will draw this to the attention of my colleagues. Carcharoth ( talk) 00:09, 27 August 2013 (UTC)
Thank you for correcting my spelling, No disrespect meant to Nikki( olive ( talk) 05:24, 27 August 2013 (UTC))
Er, my sole edit on that page during this case (I have not posted on the talk page since 9 April) was a technical fix, made on the (apparently mistaken) assumption that the renewed and seemingly resolved talk page discussion had settled the dispute. Whether we have an infobox or not; we certainly don't need two copies of the same one (I doubt even my most strident critics would argue for that!), so I removed the one which (no doubt because it was styled |bodystyle=width:10px;font-size:10%;) Gerda had obviously missed when she re-added the other infobox in the immediately preceding edit. (I also made a minor tweak to the position of some parenthetical text for readability at the same time.) In what way was that disruptive? I trust that will draw this reply to your colleagues' attention, also. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 00:42, 27 August 2013 (UTC) - added @ Carcharoth:. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:45, 27 August 2013 (UTC)
Olive, your second diff is from months ago, well before this case was open. As to the first: Gerda suggested on talk that we change the type of infobox that was being used; I agreed and made the change, noting on talk that I had done so. Gerda then added a second reformatted and expanded version of the same infobox; I disagreed and reverted, once, with a pointer to my explanation on talk. Can you explain why you see that as problematic? Nikkimaria ( talk) 02:02, 27 August 2013 (UTC)
I apologize. I left out part of the comment which unfairly created evidence of two diffs instead of one. Nikki I'vw watched your edits for quite a while and as you know commented to you on them. I thought that with this arbitration you might move towards a less aggressive style of interacting, with less a sense of ownership, but I'm not seeing that in the thread I linked to. I hope I'm wrong.( olive ( talk) 05:24, 27 August 2013 (UTC))
Thanks for amending your comment; however, I'm still not understanding your objection. The earlier edit used an edit summary which I agree was suboptimal; however, the edit summary of the more recent edit was IMO clear and based on an ongoing discussion. Furthermore, the more recent sequence shows that I implemented a suggestion by Gerda, objecting only to her subsequent addition of a second and inappropriately expanded template. Can you explain further how this sequence demonstrates aggression and ownership? Nikkimaria ( talk) 13:27, 27 August 2013 (UTC)

@Carcharoth. I don't see a concern with Gerda's or Andy's comments on this thread. I was concerned about Nikki's. With respect, I think its mistake to tar all editors with the same brush.( olive ( talk) 05:24, 27 August 2013 (UTC))

The orchestra: I found the article in the list AN/I list, an infobox added by Andy, reverted/hidden by Nikkimaria, one case of several. I restored an open version, It looked reverted the same day to me. I failed to see a collapsed version. What should an invisible infobox be good for, anyway? - No, I would not call this style "aggressive", but it's no clear communication, leading to waste of time. (Spare me the other steps, it's all in the history and on the talk.) - None of us is an "owner" of this article. If you ask me it should simply look like other orchestras, with {{ infobox orchestra}} developed by Kleinzach in 2013, for example Lautten Compagney. -- Gerda Arendt ( talk) 09:12, 27 August 2013 (UTC)

Problems beyond infoboxes

As both Newyorkbrad and WormThatTurned have cited Andy's behavior outside of the infobox realm as a factor in their decisions, I would point to the following as evidence of disruptive activity outside of infoboxes. There appears to be a similar issue over Andy's use, or overuse of Template:Coord, which is discussed in Rschen's evidence (roughly Sep 2011 – Mar 2012), with continued sniping here Apr 2013 and here Jun 2013. Wikipedia:Requests for arbitration/Pigsonthewing 2/Evidence#Evidence presented by Roundhouse0 is arguably connected (both revolve around the "coord" template.) Compare also the behavior at Wikipedia talk:Manual of Style/Accessibility#Discussion of recent controversial changes to this guideline and Talk:Jim_Hawkins (radio presenter)/Archive 2#Edit request, neither of which, in my eyes, covered him in glory. On the other hand, Wikipedia talk:Five pillars#Accessibility and equality shows Andy quite restrained and civil when a number of people contradict his policy proposal.

I'm not quite sure what the arbs are looking for or expecting here. (The scope and title of the case have probably influenced the nature of the evidence presented, both about Andy and other parties.) None of these, coordinates included, are on the scale of infoboxes in terms of disruption caused; the non-coordinate incidents aren't anything I would have kicked up to AN/I, let alone arbitration (indeed, I agree with Andy's position on accessibility and avoiding definition lists); and the last link makes it clear that Andy is capable of accepting criticism of his proposals with equanimity on some occasions. All that said, I do think there is evidence of Andy's battleground mentality and difficulty accepting consensus, mentioned elsewhere in this case, extending at least to other metadata and markup-related topics. Make of it what you will. Choess ( talk) 08:05, 24 August 2013 (UTC)

Yes, as I have said several times in this discussion, this is not just about infoboxes, but about Pigsonthewing's obsession with "metadata" and several arbitrators say on the PD page that there needs to be wider discussion of this issue. I agree, otherwise this problem will not be solved, even absent Pigsonthewing.Just as the guidelines for infoboxes state "The use of infoboxes is neither required nor prohibited for any article by site policies or guidelines" so they should state something like "It is neither required nor prohibited for any article to be arranged so that it emits metadata" and "put this-or-that into the article we are talking about because it emits metadata" should never,never be accepted as a reason for altering the visible appearance of any article. There is no requirement, and there should not be either, for any WP editor to care two hoots about microformats, or metadata, or machine readability, or Wikidata, or anything of the kind, or even to have any idea what those things are. Smeat75 ( talk) 15:54, 24 August 2013 (UTC)
I agree with much of what you postulate, but with very few of your conclusions. Surely none of us would want to see editors compelled to enable metadata, just as we don't require them to use inline citations or make articles accessible. Nevertheless, improving accessibility, enabling metadata and converting raw sources to inline citations are part of the natural development of articles that improves them. Wikipedia is a collaborative project and we don't need editors to have expertise in every aspect in order to contribute. Many editors are quite capable of writing excellent prose, but rely on others to upgrade rough sourcing into more maintainable formats, or to ensure that their work is usable by a screen reader, or to enable third-parties to read our information in a format that is appropriate for their needs. Each good-faith change to an article - whether it be converting raw urls to citations, or identifying row and column headers in tables, or converting a bare image into an infobox - needs to be considered for the impact that it makes on the other aspects of the article, of course. But I reject the proposition, so often assumed here, that the self-proclaimed experts on a topic should be the only ones who are entitled to an opinion on such changes. Editors must be able to propose what they believe to be improvements to an article, even if the owners of that article don't care two hoots about microformats, or metadata, or machine readability, or Wikidata, or anything of the kind, or even to have any idea what those things are. Ignorance is seldom a good starting point for having a sensible debate on any issue and Ludditism isn't actually a cool stance to take. -- RexxS ( talk) 19:09, 24 August 2013 (UTC)

Update and reminder

A brief update pointing to what David Fuchs said here. Please be patient until any new findings are posted. A reminder to everyone to please maintain decorum on these pages. Robust debating has its place, but please hold off on that while the case is still going. I said on the proposed decision page:

"I think several of the parties to this case are quite capable of changing their conduct without the need to pass formal remedies. I would like to see how things go after the case closes and wait to see if further remedies are needed."

I also said:

"Overall, I think a 'parties reminded' clause is needed here. And (after a period of some quiet) a way for people to discuss these issues in a calm manner at a central venue, building on some of the proposals made in the workshop, without tensions rising again."

I am still hoping this will be possible (my colleagues may in any case disagree with this approach that I have suggested), but it does depend in large part on people being able to discuss things calmly and being patient as we finish voting. I've asked the case clerk and the other clerks to keep an eye on this talk page over the weekend. Carcharoth ( talk) 23:25, 24 August 2013 (UTC)

Proposed principle 'Mission' and metadata

I think that the comments on this principle, and particularly the recent one from SilkTork, reflect a microcosm of the issues faced here. I would invite the Arbs - or anyone else - to examine these propositions to try to get a sense of what we need to understand in order to make progress:

  1. The very act of emitting accurate metadata helps others use our data. It cannot per se be harmful to the project and its current mission, and will most probably be helpful.
  2. As data is inherently dynamic, the metadata will only stay accurate if it is updated when the data changes. For that reason, an invisible mechanism for emitting metadata will always be inferior to one that is visible.
  3. Infoboxes are a feature of the majority of our articles and already contain both the structure and content needed to emit accurate metadata. They are therefore an obvious candidate for implementing metadata, as they require no duplication of data entry, nor special effort to update.
  4. In many articles, some particular key facts are too nuanced for a summary to be accurate metadata. In those cases it is not helpful to include that data in an infobox.
  5. There will be other valid, often aesthetic, reasons against including an infobox in a given article, but the job of seeking consensus is to balance the advantages (of which metadata is just one factor) against the disadvantages (which may be manifold or entirely absent). Both the issue of having an infobox and its content if one is included are properly subject to the process of consensus.

I believe those propositions reflect reality. I don't know whether SilkTork would on reflection modify his present stance, but I'd be more than happy to debate the points he raises in a broader forum, at a later date. -- RexxS ( talk) 16:49, 25 August 2013 (UTC)

I very much agree with what Silk Tork says in that comment you refer to, and agree with you that the issue needs discussion in a broader forum. Smeat75 ( talk) 18:05, 25 August 2013 (UTC)
One point that I think was raised in the workshop or in evidence (or in earlier discussions) is that the placement of the infoboxes may be what causes some of the friction. In desktop view, the infobox is at top right, next to the lead section. In mobile phone views, infoboxes are above the article and the first thing you see. If infoboxes were placed further down the article, or down the bottom of the article, the way categories are, the way navboxes (footer navboxes, not the sidebar ones), and the way some succession boxes, and some 'invisible' metadata (such as 'persondata' and DEFAULTSORT values) are, then infoboxes might be a lot less contentious. You would still get some arguments (over accuracy), as people do still argue over categories and navboxes, but from what I've seen, the arguments are less - possibly because the visibility is less (my general observation is that some people get rather annoyed with five or six collapsed navbox templates at the bottom of an article, but suffer it because it is 'down the bottom and after the article'). The reduced visibility means that updates may not be as accurate or timely, but what I wanted to ask is whether any serious attempt has been made to explore other possible positions for infoboxes? (I've only seen the examples where infoboxes have been placed invisibly right at the bottom of an article - not showing but still emitting metadata, and the visible but collapsed examples - with arguments against both these attempted solutions). Do examples exist where the default location for an item on a page (not just infoboxes) can be changed if needed? Has anyone tried to do an alternative infobox design that would fit across the whole page like a navbox footer template? Carcharoth ( talk) 20:47, 25 August 2013 (UTC)
Yes, I think that was tried at one of the country house articles, but is disliked, as you note. I hope someone has the link(s). I'm not sure if any such as in place now. Andy's note in this case that the lead image can be above an infobox has some potential to help where a landscape image is the natural lead pic (not composers, but very often in art and architecture), though I suspect keen infoboxers (not really those in this case) would be forever coming along and changing it. Johnbod ( talk) 20:56, 25 August 2013 (UTC)
(1) There are a few articles that have infoboxes embedded lower down within the article (eg Mini and many other vehicle articles), but none (afaik) that place the infobox at the bottom. Nor are there any that use a full-width layout - this would be very difficult to design, given the succinct nature of each field/value pair. Moving them would also have to be done site-wide for consistency (otherwise readers won't know where to find them) and it would no longer match the way all other language Wikipedias are setup. It would also make the {{ sidebar}}-navboxes more prominent, which is a can-of-worms itself.
(2) Collapsing has been tried in various places, from Ponte Vechio (2010) to Little Moreton Hall (current). I've tried to enumerate all the problems with collapsing in my evidence.
(3) I think I was the first to suggest that lead-images could/should display above the infobox. At my sandbox4, I made a mockup of that (and a few other changes). I gave further details about this idea in response to one of Andy's workshop proposals - particularly "Ideally, the image could (would?) still be "part" of the infobox's code, it would just display above the box-outline - this would allow all sorts of articles to use larger images, without making the box extra-wide." I tentatively suggest that this should become the default for all lead/infobox-images - this wouldn't require changing any articles, it would simply require changing the templates.
HTH. – Quiddity ( talk) 22:12, 25 August 2013 (UTC)
With a lead image above an infobox, we have the "Rite of Spring" problem: a picture suggesting that it is an article about a painting, instead of telling the reader prominently that it is a ballet by Stravinsky. I tried a new approach which I called "title box" as a certain word is not to be mentioned. -- Gerda Arendt ( talk) 07:32, 26 August 2013 (UTC)
Not if it is an article about a painting, Gerda. And why is that more of a problem when it is above rather than in the infobox? One might argue it is less likely to confuse that way. Johnbod ( talk) 16:52, 26 August 2013 (UTC)
I am confused now. At present (no infobox) The Rite of Spring looks (!) like about a painting, The Ban on Love looks like about a person. What do you think of my title box? -- Gerda Arendt ( talk) 17:14, 26 August 2013 (UTC)
This debate notwithstanding, Arbcom does not have the power to dictate to the community whether to accept or reject the use or inclusion of metadata. That is a content decision. Even if passed, this proposed principle should simply be ignored lacking an actual community mandate for it. Reso lute 13:47, 26 August 2013 (UTC)

Proposed remedy 'Parties reminded'

I wonder if it might be worth renaming this remedy to "Editors reminded" and making a corresponding update to the wording. I'm conscious of being as much caught up in the arguments surrounding infoboxes as many of the parties and there will be others in the same position as me. I'd willingly sign up to this proposed remedy and hope that everyone else can. -- RexxS ( talk) 23:40, 25 August 2013 (UTC)

  • The reminder certainly serves my benefit as well; which by the way, I intend also to heed. :)  John Cline ( talk) 00:56, 26 August 2013 (UTC)

Arbcom needs to decide on rationales for edits: does the tail wag the dog?

Arbcom needs a finding on whether debates regarding Wikipedia content that postulate benefits to "downstream re-users"—the argument ad Google—which Riggr Mortis outlined as a common feature of pro-infobox debate ( diff), should be allowed, or have any standing in content discussions. Such a clarification is surely within the committee's remit, since it would seem foundational that Wikipedia volunteers do not get to re-define who Wikipedia's "client" is. This cannot become a case of the tail wagging the dog. We again provide the following diffs as examples, quoting here from Riggr Mortis' post on Wikipedia talk:Arbitration/Requests/Case/Infoboxes/Evidence (and showing only comments by User:Pigsonthewing; there are more there from User:RexxS):

The methodology is simple: I searched the talk page namespace for "Google" and "Pigsonthewing". Here is what I found (emphasis mine):

  1. "We make our information (machine-)readable to Google and others, because they want us to, because they do good and useful things with it, and because it serves our mission."
  2. "Using an infobox makes metadata about the subject downloadable from the browser, or to partner sites which use it, such as Google[,] Yahoo and DBpedia"
  3. "parter [sic] organisations such as Google also make use of them"
  4. "The [meta]data emitted by our infoboxes is already used by Google and Bing and has been praised by Yahoo."
  5. "the metadata emitted by infoboxes, the hCard microformat, is a generic, open standard understood by tools such as Google and Yahoo."

Who is Pigsonthewing's "we" and "our" referring to? He is not speaking for us. He is not speaking for Wikipedia. He is speaking to his agenda.

Signed, User:Ruhrfisch, User:Riggr Mortis, User:Victoriaearle 02:35, 26 August 2013 (UTC)

Combined response in section below. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:06, 26 August 2013 (UTC)

Missing—an understanding of the huge scope of Andy Mabbett's agenda and activity

A few of us have discussed by email what we think is missing from this case to date. We are issuing one comment.

Andy Mabbett (User:Pigsonthewing) has made hundreds of thousands of edits (via bot requests) to Wikipedia over the years that have no conventional effect on article content, yet there doesn't appear to be an understanding in the Arbcom's comments to date about the scope of Mabbett's agenda, which put briefly is to create templates and insert them into as many articles as possible so that "metadata" can be read from the articles more easily by computers. The Arbcom does not appear to realize that a remedy that, for example, disallows infobox editing, does not prevent Mabbett from continuing to build the infrastructure that supports his agenda. Indeed, arbtitrator David Fuchs has written "I'm hopeful that forcing him [Andy Mabbett] away entirely from the infobox issue would alleviate the cause of conflict for this case"! The "infobox prevention" remedy is not sufficient. We will explain this below.

Mabbett's entire project is to overlay his infrastructure of templates (not just infoboxes!) upon millions of Wikipedia articles so that they can be better "parsed" by computers. Mabbett must want Wikipedia to act like a database, and databases must have very defined structures. So every article (or template like {{ Geobox}}, or "non-conforming" (e.g. collapsible) infobox) that deviates from his strategy and his structures is a potential battleground for him. An article edit that deviates from his template build-out, wherever he notices it, will be met with a revert, which regular editors are expected to accept, without policy grounds, for reasons that "they just can't understand"—it "emits metadata this way, you see"—it feeds third-party computer systems. His project is nothing less than re-defining Wikipedia for his own out-of-scope purposes. His "walled garden" of templates overlay the conventional editorial process and provide him with a self-reinforcing pseudo-technical rationale for controlling what appears in the wikitext of an article.

We must observe that Mabbett is perhaps Wikipedia's ultimate article owner, because his owning occurs via an entire infrastructure developed in the template space and applied to millions of articles. His methods have the effect of taking away editorial control from regular editors who may see no value in a template that adds complexity to the wiki-text without benefit to the reader. We all recently witnessed him attempt to take editorial control away from people who maintain articles about composers, for example, because their choices didn't fit his grand "data-feed" plan.

We will highlight one current initiative within Mabbett's project as an example of how he builds his infrastructure through templates and bot requests, to show why he must be stopped at the root. This recent bot request initiated by Mabbett proposes that dates already in infoboxes be put inside a new template—his template, ({{ start date}}, created by him—so that the affected articles will output data that is easier for computers to parse. The infobox aspect is irrelevant, being only the container for the template, which in turn "emits" a microformat, another major part of Mabbett's infrastructural plans. (One can go back to 2007 and find quotes such as the following: "Mabbett's campaign to push through microformats in the face of any opposition has caused untold friction around Wikipedia and has been the origin of many incidents appearing on this page [ ANI], including the classical music infobox debates. This editor is clearly a disruptive influence on Wikipedia and something should be done about him".) You see, infoboxes are nothing special here—they are just another template involved in Mabbett's strategy; infoboxes and "microformats" and so on are all part of the same agenda that dates back half a decade, and involve the same battlegrounds. How will a simple "infobox ban" affect his behavior? Not at all. If Mabbett's behavior has caused controversy, it is because it stems from his agenda—probably the strongest agenda a single Wikipedian has ever attempted to implement without a fairly quick ban following. The solution is to prevent the agenda, by preventing the person holding it from implementing it.

The bot request linked above demonstrates everything this case is really about. It demonstrates that Mabbett will continue to find battlegrounds regardless of being "banned from infoboxes". In that discussion, he accuses the most thoughtful commentator on the page of "filibustering"; he refers to minor documents somewhere else to discount the informed opinions of the people who have taken the most time to respond. And so on. We see that, even when the topic isn't literally infoboxes, he's still doing the same thing, years on, and still acting the same way toward others.

Does the Arbcom see how wide-ranging and problematic Mabbett's agenda is? The Arbcom will not accomplish anything by preventing Mabbett from editing a given infobox on a given article. His battleground encompasses all articles, and the template space. He must be banned from all activity relating to templates, including edit requests on the protected templates he frequents, and from asking for or participating in bot requests, because these are the methods by which he establishes his agenda on Wikipedia. His agenda and his "enforcement" style are why we are here. No other named party on either side of the debate demonstrates the aggression and tenacious enforcement of Mabbett. To not ban Mabbett from all template and bot activity is simply to move Mabbett's battleground a little. The battleground behavior and agenda-pushing will not stop until the Arbcom introduces a very broad restrictive remedy.

Signed, User:Ruhrfisch, User:Riggr Mortis, User:Victoriaearle 02:35, 26 August 2013 (UTC)

P.S. This hardly starts to examine how Mabbett achieves his goal via poor behavior. It does not focus on his bullying behavior, his ignoring any argument which he cannot attack, the behavior which discourages and drives away content editors (who are the lifeblood of this project).

P.P.S. If others agree with these statements, please sign your names below.

Responses

Thank you for this input, which relates to an issue I've been trying to read up on, but had trouble getting my arms around. The input raises a few questions in my mind. What community discussions have been held concerning the desirability of including microformatted information in articles? With greater specificity, what practical uses does the computer-readable microformatted information have, either within or outside Wikipedia (i.e., what are the actual or claimed benefits of including the microformats)? Can the microformatted information be included without visual effect on an article, as opposed to via an infobox, when the inclusion of one is disputed? I may have more comments later. Newyorkbrad ( talk) 07:20, 26 August 2013 (UTC)

The small scope of my agenda (forgive me that I don't understand all of the above): part of a microformat is for example {{ start date}}. You enter year/month/day as yyyy/mm/dd, and worldwide can be understood "this is a date" and the single elements, which different cultures can represent with month names in their languages and their order of rendition. It's a great concept! I support that! More on microformats by RexxS on the specific example of Talk:Mont Juic (suite). Nikkimaria reverted the infobox, but the principal author liked it. Please note that Andy didn't argue in the discussion, only answered questions and explained. -- Gerda Arendt ( talk) 08:58, 26 August 2013 (UTC)
If Brad (or others) are interested in what the above contributors are describing, I suggest he takes a look at what independent scholars have to say about it, rather than taking the word of those who simply wish to keep us in the world of a paper encyclopedia. Tim Berners-Lee, the inventor of the World-Wide Web, wrote an article for Scientific American in 2001, where he describes his vision of a Semantic Web - it's available as a pdf here. After describing a brother and sister finding a specialist to treat their mother he writes:
Sorry to interrupt but is there a more legible version of that article? All I see is a page of "}A³Rҝ¬�^ät/�ßξ÷®g½ë›iï�Ä„‡³dHéøŒ" when I tried to open it. Liz Read! Talk! 19:42, 26 August 2013 (UTC)
Try saving it to your hard drive and opening it from there, in a PDF reader, rather than in a browser. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:46, 26 August 2013 (UTC)
  • "Pete and Lucy could use their agents to carry out all these tasks thanks not to the World Wide Web of today but rather the Semantic Web that it will evolve into tomorrow. Most of the Web's content today is designed for humans to read, not for computer programs to manipulate meaningfully. Computers can adeptly parse Web pages for layout and routine processing—here a header, there a link to another page—but in general, computers have no reliable way to process the semantics: this is the home page of the Hartman and Strauss Physio Clinic, this link goes to Dr. Hartman's curriculum vitae. The Semantic Web will bring structure to the meaningful content of Web pages, creating an environment where software agents roaming from page to page can readily carry out sophisticated tasks for users."
So the concept of adding meaning to web pages is nothing new and doesn't belong just to Andy. Have a look at some of the results from this search on Google Scholar and you'll see that building the semantic web has been a task embraced by many scholars, designers and engineers over more than a decade of progress.
Nor is building the semantic web confined to microformats. For those of you who want to learn how our structured content is being used to train new generations of natural language processing programs, there is a video entitled "Intelligence in Wikipedia".
Every single web designer is aware of the potential of adding meaning to web pages. Our problem as a crowd-sourced website is in enabling everyone to contribute without throwing away all the other aspects of web design that most contributors will not be interested in. On the whole, we have made a good job of that, by using templates to hide the complexities of web-design inside a simpler wrapper. Even so, the fear of the unknown will still drive some to reject any sort of progress.
I submit that the essay above is nothing more than a device to stigmatise Andy's desire to see Wikipedia evolve into a resource that is usable in far more ways than simply reading an encyclopedia - I have the Encyclopedia Brittanica on my bookshelves if that's all I want to do. Let the three authors above honestly answer a simple question: "Would their opposition to infoboxes be any less if they did not emit metadata?" I think we already know the answer to that.
The authors also repeat a lie: that Andy has driven away editors. Not one single jot of truthful evidence has backed up that smear. In fact, Victoriaearle made that claim in her evidence, but had to retract it when it was shown that the editor whom she claimed had "left the project" had edited continuously ever since.
ArbCom should look carefully at the agenda of these editors: they have employed smear, innuendo and fabrication to create a caricature of an editor with whom they disagree. There is nothing sinister about wanting Wikipedia to be used as more than a paper encyclopedia; most editors share the goal of broader use and dissemination of our content; and there is no reason whatsoever why those goals should run contrary to the process of writing good content. -- RexxS ( talk) 11:40, 26 August 2013 (UTC)
I would like to endorse everything in RexxS' rebuttal to the three editors above. It is true that not everything can be accurately summarised in an infobox, but there has been no reliable evidence presented anywhere that emitting metadata for things that can is anything other than a Good Thing. Thryduulf ( talk) 12:03, 26 August 2013 (UTC)
I think the argument is not that metadata is a Bad Thing, but whether the approach Andy takes is helpful or causes problems. Is it better to have 100 editors doing what Andy does in small amounts, or Andy doing what he does in large volumes, as a speciality, and persistently, over many years? When people take a de facto leadership role in over-arching matters like this, is that a good thing or not? And how responsive are they to community concerns? That is my understanding of the argument being made here. Carcharoth ( talk) 12:41, 26 August 2013 (UTC)

Thank you from me too for this. It does clearly lay out the concerns that I've seen expressed elsewhere as well. Could Ruhrfisch clarify whether the postscripts (PS'es) are from him or all three editors issuing the joint statement? NYB, to answer one of your questions, I believe that when you Google for something that has a Wikipedia article, the Google summary that comes up to the right on the standard search results screen is based on what Google can read from machine-readable sources, including Wikipedia articles. I believe the other questions you ask have been mostly answered in the evidence and workshop pages, though it can be difficult to find the links among the other material there. I too may have more comments to make later, but the closest ArbCom can come to limiting scope of activity is if the overall editing is bot-like or aimed at achieving a fait accompli against existing community consensus. Beyond that, it would be the role of members of the editorial community to initiate discussion within the community on whether consensus exists for such wide-ranging activities. Carcharoth ( talk) 11:39, 26 August 2013 (UTC)

@ Newyorkbrad, There are other methods of obtaining this information, including the {{ Persondata}} template. Interestingly a Google search for Terry-Thomas carries one of these side boxes, even though our corresponding FA article doesn't; the same is also true for a Google search of John Le Mesurier and again our (FA) article doesn't carry the box. Metadata in itself is not necessarily a bad thing: if we can provide a method of disseminating microformats in a hidden form (even if that is a collapsed box) then that can only be a benefit. - SchroCat ( talk) 19:34, 26 August 2013 (UTC)
A couple more comments, based on what I've read about this while looking into some aspects of this case:
  • My understanding is that metadata here means data that can be included in and extracted from articles. This can take the form of infoboxes, but can take other forms as well. Microformats are ways of using existing html tags to mark and allow extraction of this data. You don't need to edit pages direct but the tagging is included elsewhere. It is a technical back-end allowing computers to 'recognise' what is on the page (i.e. semantic markup).
  • In an attempt to get a feel for the sort of work Andy does on this, I looked at some of his edits this year:
    • An example of his microformat work is here. Change made to sandbox here. This is (as far as I can tell) an example of allowing external data reusers to more easily access the data contained in Wikipedia articles.
    • An example of Andy's outreach and consulting(?) roles is here (from May 2013, about the ORCID "works metadata" working group), though I'm still not clear on the full scope of what Andy does outside Wikipedia on this sort of thing.
    • I noted the extent of the work done on data-related issues, templates, and infoboxes on some of his user pages: to-do and infoboxes.
    • I noted an example of a recent infobox merging discussion that drew a fair amount of attention: Template:Infobox journal.
    • I noted an example of a discussion on gender here.
My overall conclusions from this were that many people do lots of work of this nature (on templates and infoboxes), but most manage to do it without causing waves. Either because they are more sensitive to concerns, or because they edit less, or because they restrict themselves to a narrower area and don't edit across the whole gamut of infoboxes. What I'm trying to articulate here is whether there is justification for a principle that sometime less is more (to put it crudely)? I'm not sure there is justification for that, but there is a long track record within Wikipedia of individuals trying to do too much themselves, over-reaching, and running into problems with various parts of the community. It is very difficult to edit widely across a large number of areas without eventually running into those sorts of problems. It would help to be able to compare the participation in such discussions of all the editors named in or participating this case. Who participates in the most discussions, and who contributes most productively to such discussions? Carcharoth ( talk) 13:06, 26 August 2013 (UTC)
  • I would like to note that I completely endorse the statement of the three editors above. My own evidence touched on the edges of Andy's metadata obsession, but having not looked at it as deeply as they have, I felt that an infobox ban would have been sufficient. They quite eloquently and convincingly (imo) argue that such a topic ban would not be sufficient in this case. Metadata by itself may not be a bad thing - this seems exactly what Wikidata was set up to achieve - but Andy's behaviour around it has been a continual and significant source of wasted time for pretty much as long as I've been here. Reso lute 14:01, 26 August 2013 (UTC)
  • I also endorse the statement, and thank the editors for laying out with clarity the real problem here. I should note that the inclusion of metadata seems to me an important goal (I've said as much before in the debates about infoboxes), but that is not what is at issue here. Eusebeus ( talk) 14:15, 26 August 2013 (UTC)
  • I add my thanks and endorsement to the three editors' statement above. Smeat75 ( talk) 17:00, 26 August 2013 (UTC)
It sounds like the metadata isn't the problem here, it's the zealousness which an editor approached the task he saw before himself. Building consensus and handling conflict is messy and time-consuming but an essential aspect of how Wikipedia works. I can see how anyone who believes they are working for greater functionality of Wikipedia would become impatient with ever present debates. But, I think for WP, the ends (greater functionality) doesn't justify the means of overcoming resistance by either steamrolling over it, denying it exists or bypassing the debate altogether.
I need to say this is a general observation about editor conduct on WP that may or may not apply to Andy. I only have these proceedings to go on and it seems like there are some conflicting statements in the lengthy proceedings. Liz Read! Talk! 19:20, 26 August 2013 (UTC)
  • I fully endorse the statement above; this is further supported by my evidence that I submitted a few weeks ago. -- Rs chen 7754 20:13, 26 August 2013 (UTC)
  • I emphatically OPPOSE the witch hunt against Andy and the character assassination above. Here you have an editor who has clearly learned from his mistakes over the years, but is being hounded to death for a mere passion for a topic. The merits of the issue itself are being drowned in a sea of scapegoating. I see nothing of excessive "ownership" or some sort of dark agenda in Andy's behavior over the last year, and though he gets a little intense at times, he is merely a fellow editor with a strong area of interest. This is character assassination at its worst and it seems that any attempts by Andy to defend himself are met with the same chorus of outrage. The logic of the above statement is ludicrous: "let's ban people who care about improving the encyclopedia." Hmmph. Next thing you know, someone will want to ban Jimbo for his passion for wikipedia! Montanabw (talk) 00:14, 27 August 2013 (UTC)

Further responses

Note: I also endorse RexxS' rebuttal.

So much for Carcharoth's request for the maintenance of decorum. What we see in two sections above, as others have noted, are further attempts to misrepresent and smear, devoid of any actual evidence of wrongdoing or ill-intent - exactly the kind of behaviour seen (and evidenced in earlier stages of this process), from those opposed to infoboxes, or metadata, or having our content reused by external partners, or objecting in some other way to normal Wikipedia practices.

Ruhrfisch has found some instances of me discussing the reuse of our content by Google, Yahoo, Bing, DBpedia and others. So what? A similar attempt to spread FUD in that regard, also referring to Riggr Mortis' ill-conceived essay was given very short shrift by the wider community when brought up on Jimbo Wales' talk page during this case. One editor there, User:Equazcion, commented:

"I fail to see the difference. Services that benefit people should be hindered because a company is also profiting from it? Why? To prove a point? To stick it to the man? Wikipedia is about providing your knowledge for free to whoever might use it for whatever purpose. What's the difference if it's structured data or prose? The same argument holds either way. I guess it sounds scarier when you throw around words like 'Google' (big ie. evil) and metadata (automated ie. evil), but really, it's all the same"

adding

"the wishes of the "primary" contributors shouldn't take any kind of precedence; The counter-arguments based on WP:OWN are perfectly valid in response to arguments referencing the amount of time or effort contributors spent creating or developing articles. We have that policy to deal precisely with these types of situations. You shouldn't contribute here if you think you have some sort of right to maintain control because it was 'your' work."

Ruhrfisch quotes me as saying "We make our information (machine-)readable to Google and others, because they want us to" (emphasis newly added). What he does not reveal, is that I was replying to the question (from Toccata quarta) "why should we shove our information down Google's throat?".

He also neglects to mention that my comment "The [meta]data emitted by our infoboxes is already used by Google and Bing and has been praised by Yahoo" is a reply to the assertion that "[that] microformats... will one day facilitate the development of the Semantic Web, [is] just a leap of faith".

The "we and "us" I use refer to Wikipedia. Wikipedia shares its content using metadata. Wikipedia invites its reuse. Wikipedia's mission is enhanced by that reuse. And if I've done more than my fair share of the laborious and unexciting work to make that possible, for which I've been thanked by WMF staff and numerous fellow editors, then I'm very proud of it. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:03, 26 August 2013 (UTC)

Ruhrfisch responses

Newyorkbrad - I know that User:Pigsonthewing cited the existence (since 2007) of the category Category:Templates generating microformats as evidence that "The use of infoboxes to emit microformat metadata has been supported ... in practice" (take that as you will). As for actual RfC's, he cited two:

I do not know of any other RfCs which support inclusion of microformats. I do know that when the start date template was proposed to be added by bot to about 40,000 articles on listed properties in the National Register of Historic Places, it was done as a bot request and Pigsonthewing made only one post to the NRHP WikiProject web page about this - see here. I think it would have been much better if the NRHP WikiProject (to which I belong and which includes infoboxes in articles as a matter of course) had been asked directly for its input by User:Pigsonthewing. [Please note Pigsonthewing says below that he did not make the original bot request. I apologize for my error, as I said I am quite busy in real life and just recalled his comment on the NRHP talk page.]

If microformatting is desired, it can be incorporated in articles in places other than an infobox (to be very clear, infoboxes and microformats do not have to go together). One possibility would be Template:Persondata which is hidden from readers and is already included in over one million articles. As for microformats changing an article's appearance, they should not if done correctly, but even something as simple as a date runs into issues with the different date formats used around the world and in articles here which might cause it to change appearances (see the discussions above). I also worry that editors will not understand what the microformat templates are asking for which may lead to issues - again an issue raised in the NRHP page and touched on by us as part of the ever-growing complexity.

As for practical uses, I do not know of any within Wikipedia (Persondata is used for categories, perhaps microformats could be too?). Many third-party data-reusers can and do make use of machine-readable data (from microformats). As we asked, does the tail (Google, et al.) wag the dog (Wikipedia)? Ruhrfisch ><>°° 16:13, 26 August 2013 (UTC)

Comment - I have little time in real life today, and will reply to the other arb comments / questions next as I am able. Ruhrfisch ><>°° 16:13, 26 August 2013 (UTC)

Persondata is only for people (hence the name), not buildings, events, and the many other things for which our infoboxes emit microformats. Please provide an example of a microformatted persondata template for a person, so that it can be tested. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:18, 26 August 2013 (UTC)
And again Ruhrfisch misrepresents what was said, this time at the NRHP project talk page. I was replying to Doncram, a project member, who said "Please see wp:botrequest#Mark a lot of pages for microformatting. Not sure if they should be discussed here or there" and I replied "I've answered these questions at BOTREQ; I suggest we centralise discussion there.". Doncram and others joined the BOTREQ discussion; there were no posts objecting to the suggestion to hold it there. Note also that the bot request was not made by me but by User:Nyttend and the aforesaid comments are in reply to his notification of it. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:32, 26 August 2013 (UTC)

Carcharoth - the PPS is all mine. The PS reflects things that we discussed via email, but I will take responsibility for it now. I have asked Victoria (who has asked for a block) to comment on her talk page about the PS (since she cannot edit elsewhere). I assume Riggr Mortis will comment here if needed. More later. Ruhrfisch ><>°° 16:20, 26 August 2013 (UTC)

I keep on hearing the argument that we could incorporate microformats into something that isn't an infobox. Yet the truth is that nobody has ever done it with any success. {{ Persondata}} could emit microformats, yet it doesn't. Any number of invisible data structures could be embedded into our articles, yet they are not. Why? Because anybody who actually sits down to the task quickly realises that the problem with invisible structures is that they don't get updated on a crowd-sourced site. Then they spot that they want a structure with a number of label/data pairs, like a table with two columns that's relatively easy to create and update, and it needs to be a template so that we can hide the classes needed to emit microformats. And voilà! they've re-invented an infobox. There are already well over 2 million of them in use on our Wikipedia, so why not just use them as the basis for emitting the metadata? The only reason why not is that some folks just don't like 'em. I'll start to take seriously Ruhrfisch's assertion that we could incorporate microformats in some other way when he manages to create one of these other ways and shows how it will be adopted in our articles. Have a look at Ruhrfisch's recent contributions and at my recent contributions. Which one of us is more likely to be producing technical solutions to problems? -- RexxS ( talk) 18:04, 26 August 2013 (UTC)
I do not pretend to be a template or coding expert, nor do I wish to engage in a pissing contest with RexxS (and if I did, I would direct him to look at WP:WBFAN or at the number of peer reviews we've each done ;-) )(the smiley face means I am trying to use humor here). All I said was that infoboxes and metadata do NOT have to go together. To prove this, I have used {{ Start date}} and put a microformatted datum into an article on a covered bridge without resorting to its infobox or a hidden template or anything hidden - diff.
On a more general note, members of ArbCom are asking for clarification and more information, and all Pigsonthewing and RexxS can do is resort to their usual tactics of attacking the messenger (me), pointing out one error (Pigsonthewing did not initiate the NRHP bot request, so I struck that and apologize), and challenging me to a code off (or whatever you call it). Why not give them what they ask for? Or could it be that the best evidence for consensus to add microformats everywhere across the whole encyclopedia is really a category (but hey, it is 7 years old!), a no consensus RfC, and 10 editors who could out-code me saying yeah, you can try this with a bot. Ruhrfisch ><>°° 20:51, 26 August 2013 (UTC)
No-one attacked you; its just that the flimsiness of your arguments and falseness of your claims was (again) exposed. I don't know of any outstanding requests from Arbcom for clarification or more information about microformats, metadata or infoboxes, but if there are and someone points them out, I shall be happy to answer them. And no, you have not added "a microformatted datum" to that article, You have added a template which emits one element of a microformat, without a parent microformatted container to give it context (i.e. the start date for what - the page? Consider also a page with two infoboxes). The template documentation explains this. No microformat-aware tool will recognise it, because it does not conform to any published microformat standard. So you have not proved your assertion. ( I have fixed your error) And do you really think inline templates, in running prose, are preferable to, or more likely to find favour with the wider community than, those in infoboxes? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:18, 26 August 2013 (UTC)
( edit conflict) @Ruhrfisch: I don't remember trying to tell you that you should be doing peer reviews in a different way - the way that you tell me I should be writing metadata-emitting templates in a different way. In fact, I'm happy to acknowledge and commend your work in doing peer reviews because I know it improves the encyclopedia. But then you keep making the claim that we could put metadata elsewhere, and ignore my explanation of why it's a bad idea - based on what? Your expertise in doing peer reviews? I agree that it has a certain humorous quality. -- RexxS ( talk) 21:54, 26 August 2013 (UTC)
@Pigsonthwing - So just to be clear, you, Pigsonthewing are the author of {{ Start date}}, a template specifically made for emitting microformatted data. However, and here's the catch, it only works when embedded inside other "microformat-emitting templates". So you made it so it won't work unless it is in an infobox or other appropriate template - how does this not conform to our arguments above? i.e. you OWN Startdate, and it has to be in a box to work, so then you OWN the box too? Ruhrfisch ><>°° 01:49, 27 August 2013 (UTC)
I don't own any of them. Where is your evidence that I attempt to? Please explain how you would have {{Start date}} work outside a parent container. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:19, 27 August 2013 (UTC)
@Ruhrfisch: you need to actually read WP:OWN. It's not about creating articles or templates; it's about stopping other editors from contributing to work that you feel you own. It is exactly what has happened with biographies of classical composers. It is exactly what has not happened with {{ Start date}} - another half dozen editors have contributed and Edene is now the main contributor. For information: many infoboxes allow dates such as "about 212 BC", "15 or 17 December" which are not suitable for emitting metadata. So the way that we emit metadata for dates that are sufficiently precise, like "27 August 2013" is to wrap them in a template that adds a microformat - which is what {{ Start date}} does. It works sensibly when the date it wraps with the classes "bday dtstart published updated" is inside another class like "event" which names the event that it is the start date for (or the person whose birthday it is, etc.) Please try not to use {{ Start date}} outside of suitable containers like infoboxes otherwise re-users can't tell what it relates to. -- RexxS ( talk) 12:19, 27 August 2013 (UTC)
RexxS and Pigsonthewing, I have read it - I was referring to our joint argument about OWNership above. Ruhrfisch ><>°° 16:27, 27 August 2013 (UTC)

Carcharoth - Riggr Mortis indicated to me on email that he is fine with the PS. Victoria posted the following on here talk page: Yes, per Carcharoth's question, I agree with the PS. It's been amply demonstrated on the pages of the arb case and on other pages where I've witnessed these discussions and is in my view the reasons it's difficult to impossible to discuss these matters elsewhere, which goes to Newyorkbrad's question. Only one more thing, in response to RexxS assertion that I accused Andy Mabbett of driving away editors: the evidence states editors become discouraged and leave. But - and this is important - I don't wish to engage on that level because frequently in these discussions the concept or the main point of the discussion devolves quickly into a "he said, she said" scenario which is almost always counterproductive. Feel free to copy over, or to link, or to point to this post. Victoria ( talk) 18:08, 26 August 2013 (UTC) End of quote posted here by Ruhrfisch ><>°° 20:08, 26 August 2013 (UTC)

Well of course Victoriaearle doesn't want to engage in discussion after she's been caught out in a lie. But her so-called evidence is still there on the talk page of Evidence even now for anyone to see and she hasn't had the decency to retract those untruths. Here's what she says referring to Yllosubmarine: "In September 2012 ... She became discouraged and left the project. ... . Keep in mind, too, we lost a prolific female content editor from the Pilgrim at Tinker's Creek episode." It's pure fabrication. Yllosubmarine never left the project. Here's a link to her contributions so you can see for yourself. Count the monthly contributions since last October when she was supposed to have left the project: 28, 10, 6, 11, 3, 7, 11, 2, 7, 3. She even edited today. It's on the back of this sort of mendacity that we get the smear "the behavior which discourages and drives away content editors". There is zero evidence. Strike it if you have an ounce of honesty left. -- RexxS ( talk) 21:54, 26 August 2013 (UTC)
Please see my comments above in the #Comment from Victoriaearle/Truthkeeper88 section. While I agree that Yllosubmarine has not left entirely, her edits dropped by just over 90% in the 10 months after Pigsonthewing's Pilgrim at Tinker Creek infobox argument (compared to the 10 months before) and she has not written any new articles I could see or brought any to GAN or FAC (and this from an editor averaging over two GAs and FAs per year from starting here to Tinker Creek as TFA. As I said above, how is this not the loss of a productive editor? I know you won't answer that, because you can't. I will repeat what I said to Pigsonthewing and now say to you, you owe Victoria an apology. Ruhrfisch ><>°° 01:49, 27 August 2013 (UTC)
That would be the section where I disproved your and (not for the first time) Victoria's bogus claims by showing that Yllosubmarine had edited more times in some of the months after the Tinker's Creek discussion than in several of the months before it? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:10, 27 August 2013 (UTC)
@Ruhrfisch. Rubbish. Yllosubmarine made more edits in the month after the Pilgrim's Creek debate (October 2012 = 28) than she made in any of the four months prior to it (May, June, July, August 1012) and she was busily contributing to Today's Featured Article requests during the rest of the year. It is disgusting that you try to spin that into evidence of Andy chasing editors off the project. -- RexxS ( talk) 12:01, 27 August 2013 (UTC)

newyorkbrad and Carcharoth and any other members of ArbCom reading this - I see further attempts at discussion will get nowhere, since I cannot code templates and mendacity is supposedly rampant. I hope that our arguments offer a useful way for you to look at this whole mess. Ask yourselves this: if infoboxes and metadata and microformats are a content issue (as many have argued) and we have a small group of editors who are pushing this content everywhere they can, despite a lack of broad consensus for it, isn't this really a WP:POV case too? If this were some content on the Middle East or (Northern) Ireland that was being pushed, wouldn't the solution be obvious? In POV cases, ArbCom has topic banned or site banned the POV pushers. Is this that much different?

And now, since Carcharoth has asked for a break (as it were), I bid you all adieu. Good night and good luck, Ruhrfisch ><>°° 01:49, 27 August 2013 (UTC)

[I've cut this way down, Carcharoth]

On the lying accusation: Don't call people liars. I had the same impression about Maria/yllosubmarine--that she was gone, I mean. It's an easy mistake to make, in general, about people you've encountered a tiny bit. Maria certainly has cut back on editing, having made maybe 70 edits since the infobox debate she participated in almost a year ago, which went something like this: Talk:Pilgrim_at_Tinker_Creek#Infobox.

"Give example of an editor leaving because of Pigsonthewing?": OK, me. Not as a matter of direct conflict, but in the way that one has an instinct to walk away from something they think might explode. Or worse, stick to them and explode. Wouldn't want to be within a country mile of the next Tinker Creek Box Battle.

(Why am I back? I participated in proposing the remedy we gave above (that bold part), because if it passed I would feel much better about the culture and editing environment of Wikipedia.)

Metadata misdirection: All cut—except for a short comment on semantics and retro-fitting. I didn't know that buildings and bridges had birthdays, were "published", were "updated", or fit into a calendar event, but the HTML source of one example tells me so: <span class="bday dtstart published updated">1872</span>; the Eiffel Tower has a "nickname" that happens to be in French: <span class="nickname" lang="fr"...>La Tour Eiffel</span>; Chelsea Manning was also going to have a "nickname" that consisted of their prior name (sounds controversial in any other context, doesn't it: [124]); and biographic metadata for the most part "emits" contact card data. "Semantic"? Hehe. Not so much. This "tail wagging dog" concept comes up again. What to do with it... Riggr Mortis ( talk) 06:53, 27 August 2013 (UTC)

Where has anyone called anyone else a liar? The HTML class names used in microformats are just labels,; (they could easily be in the style "parameter23"), but were chosen by the authors of the microformat standards to match the internationally used vCard standard, and as already discussed, are widely and interoperably recognised by a large number of organisations, web services and software tools. In the case of the bridge, the classes "published" and "updated" are disregarded, because the parent microformat includes no definition of them, unlike the "dtstart". Since they are not exposed to our readers, there is little chance of them being cased any confusion. I've already suggested that people read the archived section of Jimbo's talk page, where your user-page essay got very short shrift, and quoted some of the response to it, above. In that essay, you give your reason for leaving as "As long as Wikipedia drifts from its origins as a tool for human learning to a second-rate quasi-database—apparently to the benefit of ADD-inducing tech companies—I will no longer participate as a volunteer". Let's have another quote from the discussion of that on Jimbo's talk page, from User:Cyclopia: "So someone is led to retiring because we're making it easier to reuse data and make Wikipedia interoperable with other tools? I am sorry but I can't think of anything else but 'insane' when reading this essay... Licensing is how we deal with wishes of people who wrote the data. If you don't want your contributions to be used in ways you wouldn't think of, you better not contributing to a project under a free license." Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:00, 27 August 2013 (UTC)
@Riggr Mortis: I call someone a liar when they are clearly telling lies and damaging another editor as a result. Did Yllosubmarine leave the project - yes or no? Is Victoriaearle a liar? Of course it's easy to make mistakes, but honest people withdraw the accusation when they realise they've made a mistake. Victoriaearle's mistruths lie on the Evidence talk page to this day and you use them to call for sanctions on another editor. You suffer no damage by defending such lies, but for the person who is maligned as a result, it may possibly result in an indefinite ban for something that you've helped to fabricate. Shame on you. -- RexxS ( talk) 12:01, 27 August 2013 (UTC)
RexxS - everyone makes mistakes (my recollection is that Pigsonthewing said I found quotes by him, when all I did was copy what Riggr actually found, you referred to me still doing peer reviews when I got burned out and basically do not do them anymore). Yet I am not calling either of you liars. Victoria cannot edit any page but her own, and has chosen to leave the project. I said above that while Yllosubmarine did not technically leave Wikipedia, it is also clear she is not contributing at anywhere near the level she did before. You have an excellent FA nom; you know the effort involved in writing and researching and getting an article through FAC. Look at Yllosubmarine's edits - she still cares enough to revert vandalism and good faith cruft additions, she still participates in a few discussions if any article she took to FA is nominated to be on the Main Page, but that is it. She went from 14 GAs and 14 FAs in less than 7 years to ZERO in the year since the infobox posse showed up at the Tinker Creek article. Address that part of Victoria's statement, why don't you? Yes, Yllosubmarine still pops up from time to time, but she is not the editor she used to be. Why can't you admit that too? Or do you want to provide yet one more example of how you and Pigsonthewing attack one small part of an argument (IT'S A LIE!!!!) so no one will focus on the rest: that Wikipedia has lost a valued content contributor? Ruhrfisch ><>°° 16:27, 27 August 2013 (UTC)
PS In the interest of not contributing anymore to the avalanche here, and to give the Arbs a break so they can sift through all this, I am done - ping me if needed. Please play nice with each other while I'm away. Ruhrfisch ><>°° 16:27, 27 August 2013 (UTC)
Honest people correct mistakes, not rehash them to tar others unreasonably. Victoriaearle still makes the untruthful claim that "Yllosubmarine left the project" - do I need to supply you with the diff again? She could easily ask for that to be refactored, but chooses not to, so that you can repeat the smear on Andy that has no basis in fact whatsoever. Why did Yllosubmarine cut down on her GA/FA work? Why did you cut down on peer reviews? Peoples' circumstances change, and it's utterly inappropriate to heap the blame on Andy when there is nothing that supports it. The Tinker's Creek discussion occurred mid-September and Yllosubmarine edited 28 times in October - that's more than she had in the previous April, May, June or July. How on earth does that support your wild assertion about "behavior which discourages and drives away content editors"? You simply made it up. Address that fact first instead of making ad hominems about honest editors who have caught you out in a smear campaign based on a tissue of lies. -- RexxS ( talk) 16:00, 28 August 2013 (UTC)

Information on microformats

If anyone still needs information on microformats, as suggested above, please see microformat; my statement in the 2010 RfC; and my essay giving a comparison with persondata.

As I said in the second of those, Erik Möller, Deputy Director of the Wikimedia Foundation [spoke], in an article called Wikipedia to Add Meaning to Its Pages, about "making some of the data on Wikipedia's 15 million (and counting) articles understandable to computers as well as humans". Note, in particular, the part about "allow[ing] software to know, for example, that the numbers shown in one of the columns in this table listing U.S. presidents are dates". That's exactly what microformats do.

The cited article is also a very accessible overview.

I'm happy to answer any questions.

I would also add that I am firm believer in the benefit of infoboxes to our human readers; I added them before we started to use microformats, and I have worked hard to ensure their readability by humans, both visually and for those with visual impairments requiring them to use screen readers. And I would still add and improve them if they did not emit microformats. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:45, 26 August 2013 (UTC)

Smerus

I note the arb opinions that I have degraded infobox discussions and the examples cited of my comments against Gerda; I apologise for these and certainly intend not to indulge in such behaviour or employ such techniques again. May I ask then whether the unprompted incivilities (and sometimes gross incivilities) of Rexxs,(examples of whose handiwork I gave in my original evidence), Montanabw and PumpkinSky against myself during infobox discussions are also to be considered? There is PotW as well of course but his general behaviour is adequately covered in other aspects of this arb case. Thanks, -- Smerus ( talk) 07:06, 26 August 2013 (UTC)

I accept the apology. - I said before that I didn't need one and would like to only look forward. Thanks for expressing it anyway, -- Gerda Arendt ( talk) 11:49, 26 August 2013 (UTC)
Gerda is very gracious, and between the two of you, I hope you've patched things up. However, that leaves Andy and also your overall attitude toward anyone who proposes an infobox anywhere that you claim ownership in the topic. if you fail to see your own incivility, Smerus, and still cannot even when it has been pointed out to you (and others) with diffs and examples, then it proves my point that you are a mere bully who is mean to people who you think are weaker than you, but when called on your own behavior can only cry crocodile tears and claim that you are the victim. Montanabw (talk) 15:33, 26 August 2013 (UTC)
I hope it is clear from the above edit what I mean. I have not anywhere claimed that I am a victim. The abuse, name calling, unsabstantiated allegations and pose of moral superiority, is part of the culture of PotW, Montana, Rexxs and PumpkinSky, and if this arb case is about editors' polite behaviour towards others, then what is sauce for the goose is sauce for the ganders. In Wikilawyering capacity I am a six-stone weakling compared to the professional intimidation carried out by these characters. But I do not seek, like Montanabw, to be a moral touchstone, exonerate myself or to be claim to be heroically intervening on behalf of others; I only ask that all participants be evaluated as I have been. It seems from the recent request for diffs about me and Montana's ready response to this that the closing date for evidence has become irrelevant to this case; I can see it for extending for several months or years yet at this rate; so if arbs request me to produce diffs, there is no shortage of them and I shall be glad to oblige. Meanwhile, as Montanabw seems to note, Gerda and myself have taken constructive steps to make things work, which is more than most other contributors to this discussion have done. -- Smerus ( talk) 10:37, 27 August 2013 (UTC)
I'll be glad to see the diffs, particularly of my unprompted incivility. If I see you bullying Gerda, or saying that Montana is "libelling other editors", or attacking other women editors again, you can be sure I won't be civil when I take you to task for it. But that won't be unprompted. I am perfectly civil when I'm interacting with those who debate in a collegial and constructive manner, but a lifetime involved in resolving disputes has left me with little tolerance for those who deliberately don't. Mea culpa. -- RexxS ( talk) 12:46, 27 August 2013 (UTC)
But you are not an arb. I will gladly list them, as I clearly state, if an arb indicates that s/he will be willing to take them into consideration.-- Smerus ( talk) 13:18, 27 August 2013 (UTC)

Limited number of comments in discussions

While I completely understand why this has been proposed, and I can see that it will be a big help to curtail some of the unproductive discussions, it has as I see it two potential downsides:

  • Hampering productive discussions about content.
    In pretty much every area of Wikipedia that is not watched by those members of the classical music project who dislike infoboxes, the existence of an infobox is not at all controversial. Sometimes though the content of an infobox is not always clear cut and it requires discussion between various parties until everyone is happy that the information is correctly summarised, this can sometimes take several comments until people understand each other. Now imagine that there are three fields of an infobox that require discussion but you're limited to two comments. How do you proceed?
  • Discouraging productive discussions about infoboxes or their content.
    Evidence presented shows that a not infrequent sequence of happenings in the classical music sphere is that someone proposes an infobox for a given article, whether they know (or can know) it is likely to be controversial or not. This is either reverted or responded to with a comment along the lines of "No infoboxes on this article!", the proposer then responds with the reasonable question, "Why do you not want an infobox?" gathering only the response "I said no!". If someone has a maximum of two comments to make then this sort of behaviour is encouraged because it means you get to keep the infobox off 'your' article without having to explain why you don't want something that other editors think will improve the article.

As Carcharoth notes, "The fault (if any) seems to be more a frustration that others won't discuss things fully.". This is the crux of the matter, those who think infoboxes on articles improve them generally seem to want to discuss them and get them right. They are generally interested in why someone thinks that something is incorrect or too nuanced so they can understand the objection in order to work around it (by which I mean either correct the information, present it in a different way so it doesn't mislead or omit that bit of information from the infobox). In far too many cases this has been met with a refusal to discuss - often the infobox in its entirety or sometimes the objections to specific aspects of it ("piece of information X cannot be accurately represented in an infobox, therefore we must not have an infobox", rather than "piece of information X cannot be accurately represented in an infobox therefore the infobox will include on information ABCDEF which can be accurately summarised.").

It is not possible to have a productive discussion when one side refuses to discuss anything, and I don't see these proposed restrictions as helping that. Some things that I think would help would be:

  • A ruling that no party to this case may revert the addition or removal of an infobox from any article or talk page
  • A ruling that proposing an infobox on the talk page of any article where there has not been recent discussion of one is disruptive only when the proposal makes no reference to that article.
  • A ruling that arguments about a (proposed) infobox on a specific article are disruptive if they make no reference to why the infobox is or would be or not be beneficial to that specific article; and that such arguments may be removed by any uninvolved [editor|administrator].
  • Imposing a limit on the number of concurrent discussions about infoboxes that may be initiated by any party to this case. If that number was 3, then an editor must wait for the first discussion they initiated to conclude before they my start a fourth discussion.

As for more general alternatives, would the committee regard any of the following to be within their remit?

  • Mandating that discussions of individual infoboxes must take place only at the level of the individual article, and take into account only arguments related to that article?
  • Mandating that WikiProjects may not impose a blanket requirement for or against infoboxes on 'their' articles?
  • Mandating that discussion of whether articles should emit metadata is irrelevant to whether a given article should have an infobox?
  • Rule that WikiProjects do not own articles?

This is not a recommendation that the committee should do any of these things, it is asking whether they could do so if they felt it would be beneficial. Thryduulf ( talk) 11:56, 26 August 2013 (UTC)

Thank you for your thoughts for better collaboration! As for wording: "by those members of the classical music project who dislike infoboxes", it seems a bit too general, for example Kleinzach initiated infobox orchestra, infoboxes for compositions have a tradition to at least back to 2007, project opera initiated an infobox opera. The restriction is for biographies in the field. But you are right that some members dislike infoboxes, period. - We can practise consensus at The Ban on Love which I moved (for this purpose) from the case workshop back to the article where an infobox had been reverted twice. I just left the discussion for today with my self-imposed limit of only one entry to one discussion a day. -- Gerda Arendt ( talk) 13:03, 26 August 2013 (UTC)
I think something like a 1RR restriction might be useful. The problem with "consensus" is that no one knows what it is or when it has been achieved...for example, the WP Classical Music project claims a "consensus" against infoboxes, but that claim is then used to bludgeon anyone, anywhere, who proposes one. Yet, to have 10,000 individual article discussions seems other fruitless also. I DO think your comment about "one side refuses to discuss anything" is the crux of the matter, you can't reach consensus if one side covers their ears and shouts "lalalalalalalalaaaa!" or if there is a Greek chorus drowning out everything. If that can be addressed, the rest might fall into place. Montanabw (talk) 15:33, 26 August 2013 (UTC)

Propose that a community-wide discussion be held to determine global consensus on infoboxes

Apologies if this has been mentioned, as I've only been peripherally involved in this. I was reading through the proposed decisions and saw @ Newyorkbrad:'s Locus of dispute. I honestly don't see any way for the infobox question to be resolved on an article-by-article basis. The first bullet point reads:

"It is not clear how infobox disputes are to be resolved (e.g. if 5 editors favor including an infobox in a given article and 5 disfavor it, there is no default rule and no policy guidance for determining how the consensus is to be determined, so the dispute continues indefinitely)."

Setting aside the question of how to handle a tie, are we really content to resign consensus down to a vote at each individual article where it might arise? It seems like that's what this comes down to, and if that's the case, it would actually save everyone a lot of grief to state it plainly and simply: Do not discuss, but rather simply vote, as this comes down to individual preference, so majority therefore rules in each case. As far as each individual article is concerned, there is really nothing to argue about. It doesn't seem like the infobox question is actually all that article-dependent, beyond the infeasibility at certain topics (an article about an author is feasible, while something like dystopia might not be), and the fact that different people with different opinions on infoboxes might be editing at those respective articles. Again, it comes down to individual preference.

The above really doesn't seem like any sort of Wikipedia-style solution though. If any semblance of actual WP:Consensus currently seems impossible as there is no relevant policy or guideline, nor even a logic to point to on a per-article basis, maybe this is the time to start answering the question by putting it to the community at large. I'd like to see that as one proposed decision, assuming those can still be added. Equazcion (talk) 17:20, 26 Aug 2013 (UTC)

There's no reason why someone can't independently launch an RfC at a village pump, or some other appropriate location. That being said, for myself, I support the use of infoboxes, but oppose making them mandatory. There are always exceptions to the rule. Reso lute 17:27, 26 August 2013 (UTC)
I'm with Reso. I update Infoboxes all of the time but don't think they should be mandatory, especially on articles that are not biographical. I can't see there being a straight "Yea for Infoboxes", "Nay against Infoboxes" vote because however it was decided, it wouldn't reflect a consensus, just a majority for those editors who cared enough to cast a vote. I'm not sure if there any solution other than deciding this article-by-article. Liz Read! Talk! 18:55, 26 August 2013 (UTC)
Quite. Some if us have been trying that. Look where it's got us. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:58, 26 August 2013 (UTC)
[ec] "I support the use of infoboxes, but oppose making them mandatory" - Me too. Who is it, remind me again, who wants to make them mandatory? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:57, 26 August 2013 (UTC)
Well me for one, for certain types of article where the Wikiproject so decides, and with a certain allowance for IAR, as I've said more than once in the case. And the 31 users of Template:User Infobox pref - "This user believes that all articles should have an infobox". But certainly not for all biographies - biographies are one of the problematic areas for infoboxes. A pertinent example today, from my watchlist. Johnbod ( talk) 21:07, 26 August 2013 (UTC)

Kinda getting off point. I think rehashing the opinions of all involved here on the infobox question isn't going to be all that helpful. We've seen arbitration decisions before that a community discussion be held to gauge a broad consensus, and I think such a decision would be appropriate here. Equazcion (talk) 19:44, 26 Aug 2013 (UTC)

( edit conflict) It would be an appropriate remedy in the sense that nobody would object to either its relevance to the case or disagree that it is within the committee's remit to pass such a remedy. I don't think that it would be useful though - at the end of it I would be prepared to bet a significant amount of money that the answer would come back "The community supports infoboxes but doesn't think they should be mandatory" - i.e. exactly where we are now. This is because other than a very small minority of people who dislike infoboxes per se, almost everybody agrees with the status quo. Even if anybody wanted to make them mandatory (which I've never seen any evidence of) there are some articles where its just not possible (e.g. Orthogonality and Types of inhabited localities in Russia), and there are other articles that are structured by their very nature and so any infobox would just be duplicative (e.g. List of Justices of the Supreme Court of the United Kingdom). You would therefore have to mandate them only on articles where they were appropriate - which gets us back to exactly where we are now. What needs to happen is for the discussions about infoboxes on pages within the sphere of classical music to become detoxified such that they are as productive as the discussions about infoboxes on the other 99.99% of Wikipedia. Thryduulf ( talk) 19:48, 26 August 2013 (UTC)
I wasn't really suggesting only those two questions be asked. We could additionally ask the question, "Should infoboxes be mandatory on every article about a person"? I think that would produce interesting and useful results, just as an example. Let's start fleshing out some guidelines here (not literally here, but at a global discussion) so that people arguing at articles actually have something to discuss. Equazcion (talk) 19:54, 26 Aug 2013 (UTC)
I don't support mandating their use even for articles about a person because there will always be edge cases where an infobox is not appropriate and other cases where it is debatable whether the article is about a person. The first example that comes to mind (although there will be better ones) is Piltdown Man. Thryduulf ( talk) 20:21, 26 August 2013 (UTC)
It's great to know what you think, but I wasn't really asking, with all due respect. I'm again suggesting a community discussion. But just as an aside, yes, if infoboxes were mandated for "person" articles, there would be some scattered instances where the article topic is ambiguous, and that would need to be discussed at the article. As is the case for most guidelines, they're not always easy across-the-board answers, but can rather be a place to start, whereas right now there is nothing on which to base a discussion. Equazcion (talk) 20:36, 26 Aug 2013 (UTC)

I'm not suggesting this be a straight yes-or-no question; only that it be a community discussion on what to do. We can make room for several possibilities. The point is, it seems arbitrary to leave it up to the "i like infoboxes" or "i don't like infoboxes" stances of whomever might be at a particular article at a particular time (that's essentially what it will come down to). Centralized community discussions (especially those commenced by arb decision) tend to make room for several possibilities, not simply a yea or nay. Let's see what we can come up with. Equazcion (talk) 19:44, 26 Aug 2013 (UTC)

Considering that ArbCom is close to banning a user for advocacy of infoboxes and thus singling one user out as a scapegoat, against an "old guard" of rather mean and nasty-acting sorts who continue to do anything (including collapsible side navboxes) to avoid having "teh dreaded infoboxen" appear on "their" articles - you may have a valid point. If "consensus" leans toward infoboxes, then the sanctions toward this user would be moot. Montanabw (talk) 20:22, 26 August 2013 (UTC)
Any sanctions imposed on Andy Mabbitt will be an indication of his behavior alone - nothing more or less. Any great debate on the general usefulness of infoboxes will be millions of wasted words of waffle - most of them written by editors who have never written a useful page in their lives. The present system of adding an infobox only after debate with the primary editors on the talk page is the most satisfactory and least aggressive way of obtaining consensus that there's likely to be. The problem has always been Andy Mabbitt's inability to accept this.  Giano  20:31, 26 August 2013 (UTC)
I'm still struggling with this notion of "primary" editors, and how this concept could have possibly gained even moderate acceptance in a discussion here, of all places, where there's a policy called WP:OWN. But I digress. This should be put to a community discussion. I don't care about how various editors have behaved and don't have an opinion one way or the other on sanctions (because frankly I'm not familiar with their history) but the way these things are handled in general should be discussed broadly, as this is a broad-reaching issue, regardless of how lowly you regard the opinions of those who might respond. Equazcion (talk) 20:41, 26 Aug 2013 (UTC)
On Wikipedia, those seeking to bombastically impose their own views on others have always erroneously invoked WP:OWN. Fortunately, most people see the flaws in such false reasoning.  Giano  20:49, 26 August 2013 (UTC)
( edit conflict) It's not erroneous. If someone is imposing their own views on others then they could be wrong too, but if you counter with any argument based on "primary" editors or anything synonymous with that, you're just as wrong, as you're doing precisely what WP:OWN warns against. It is the very purpose of the policy to prevent such stances from being credible. You may have a point that an editor acted inappropriately, but if that's the case then you've got the reasoning wrong. Equazcion (talk) 20:57, 26 Aug 2013 (UTC)

It is abundantly clear that a community-wide discussion about some of the issues raised in this case is needed. The trouble is that in the past when ArbCom have stated that explicitly, the response is at times a resounding silence. Literally. I may have missed it, but in the Doncram case earlier this year, ArbCom suggested (in relation to the stub guideline) that "this question may need to be decided through a deliberate attempt at conducting focussed, structured discussions in the usual way." I am not sure if that ever happened. In part, this is human nature as the last thing most people want to do after a lengthy ArbCom case is to carry on the discussions. You can take a break for a month or so, but people are often still reluctant to return to things especially if some of the ArbCom remedies may have calmed things down. Bit of a Catch-22 really. The other problems are that many casual editors will be completely unaware of WP:INFOBOXUSE, and many editors will have widely varying experiences and expectations in relation to infoboxes, which makes centralised discussion not as easy as it looks. You need to prepare such an RfC and gain input from all those who have strong views on the matter, otherwise the results won't be accepted. Carcharoth ( talk) 20:54, 26 August 2013 (UTC)

If the decision is made to put the question to the community, and no one is mandated to actually create it, then yes it could result in silence. I think if an RfC actually appeared, with a watchlist notice, there would be widespread participation. I would create one myself right now if I thought I could make a good one, but I was hoping someone smarter and more capable than myself could craft a good one. It needs to present all the right information and distill all the issues into a viable group of questions, and if that happened I think it could work. I have a feeling the infobox issue isn't quite as contentious in the broader community as it is with those vocal few present currently. Equazcion (talk) 21:04, 26 Aug 2013 (UTC)
Go ahead. Almost anything would be better than the way we deal with disagreement now. Today I looked at the history of Sparrow Mass again, and I suggest you do the same, it's short. I added an infobox, after doing so to the liking of the principal author for Schubert's masses. Was that aggressive? Less than two hours later it was reverted, edit summary "cleanup". Was that aggressive? It looked to me not very thoughtful, so I reverted, asking for discussion on the talk. Edit conflict war, page protected. Andy was not on the scene. -- Gerda Arendt ( talk) 21:22, 26 August 2013 (UTC)
See, here's the issue. Per WP:BRD, you never should have restored the infobox after being reverted, regardless of whether you agreed with Nikkimaria's removal being characterized as "cleanup". Rexxs (with an ironic edit summary) and Diannaa should not have tag teamed to try and force its inclusion, nor should Nikki have edit warred against the three of you. But all of that came about because you incorrectly figured the guideline was bold, revert, revert, discuss. Once the page protection was lifted, the infobox was again removed to restore status quo ante, and you were right there to restore it yet again. Why? What did you expect to gain when there was already a discussion on the talk page, involving the usual suspects? Reso lute 23:33, 26 August 2013 (UTC)
You are right, I should not have reverted. But was it "aggressive". It was a spontaneous angry reaction to something unexpected I could not believe. By now, I am on 1RR, voluntarily so. Looking back to April and June gives you a wrong picture, I improved. So did Andy, no? (He didn't touch that article, sorry I was not precise about the meaning of "scene"). -- Gerda Arendt ( talk) 07:30, 27 August 2013 (UTC)
It should also be noted that Andy was, in fact, on the scene, apparently misrepresenting the outcome of his microformats RFC to try and gain the upper hand in that discussion. Reso lute 23:36, 26 August 2013 (UTC)
What I said was We've had RfCs which have shown community consensus to use infoboxes to emit microformats}}; and though I commented on the talk page, I did not edit the article, which is what Gerda is referring to. [Note Gerda means edit war, not edit conflict. Corrected.] Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:53, 26 August 2013 (UTC)
Yes, and SilkTork's closure of that RFC made it clear that no such consensus existed on the use of microformats, let alone the use of infoboxes as the delivery system. They only noted an indication of support of considering the use of microformats in general. Unless, of course, there is a different RFC that I am not aware of. Reso lute 23:55, 26 August 2013 (UTC)
There are other RfCs, yes, one cited above; and the Composers Project RfC authorised the use of {{ Infobox classical composer}}, which has emitted a microformat from the get-go. Your reading of ST's admittedly ambiguous-in-part closing statement also omits some important detail: "In general people felt that microformats had a place on Wikipedia, and there were no views calling for an outright exclusion". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 00:04, 27 August 2013 (UTC)
Err, no, I quite clearly said "They only noted an indication of support of considering the use of microformats in general." Reso lute 00:08, 27 August 2013 (UTC)

Section of Propose that...

I think it's important to note what ArbCom can and can't do. The Committee can impose binding decisions regarding inappropriate behaviour - such as users consistently ignoring consensus. The Committee cannot make decisions regarding content or policy or guidelines, nor force the community to have discussions regarding content or policies (the Committee can recommend or suggest such discussions, and the community can quite rightly ignore such recommendations). We have community wide consensus on the use of infoboxes which has been quoted in the findings: WP:INFOBOXUSE. This has been in existence since October 2011. If people feel this needs amending then the appropriate place to open a discussion would be on the talkpage of Wikipedia:Manual of Style/Infoboxes. What this case is partly about is not that we don't have a guideline regarding the use of infoboxes, but that some users may not be appropriately following that guideline - that is to say that some users may be urging either the consistent use of infoboxes on all articles as standard, or conversely, some users may be insisting that infoboxes are not to be applied to a certain section of articles. The guideline indicates that use of infoboxes on a particular article, if contested, is decided by discussion and consensus on the talkpage of that article. Discussion has been taking place. The decision for the Committee is whether such discussion has been handled appropriately, whether those taking part in the discussions are taking on board the concerns of others, and whether certain users are having contentious discussions regarding the use of infoboxes so often as to be considered disruptive. The Committee's considerations on these matters will be informed by awareness of existing guidelines and consensus, but it is outside the scope of the Committee to alter consensus or to ask the community to set about altering consensus. My own view on infoboxes broadly aligns with consensus - properly used they provide useful information, but they are not always required, so making them mandatory would be inappropriate. If editors cannot reach agreement in a discussion regarding the use of an infobox in an article, they should avail themselves of the Wikipedia:Dispute resolution procedures we have in place.

However, making a focus on infoboxes is perhaps taking the spotlight off the real issue, which is the use of metadata. Infoboxes come into the picture, it seems, because they are regarded as the best means of employing the metadata software. The issue is that those in favour of employing the metadata software wish to place an infobox on articles which don't have one. Some users are objecting to having an infobox on an article where it may not be appropriate merely in order to employ the metadata software. If there is to be a community discussion on something, it should be on the use of metadata software on Wikipedia. Infoboxes would come into that discussion, as they are seen as fairly indispensable to the employment of metadata. My understanding of the metadata software is that it is able to encode certain basic information, such as the date of construction of a building, its location and size and type, and that can be translated into whatever readable format is appropriate by compatible software. This means that information can be transferred by means other than text. In previous discussion on metadata there is a consensus that it would be appropriate to explore this technology. Where there hasn't been consensus is how to use this technology - and how much we should be adjusting Wikipedia to fit the technology (such as employing infoboxes on all articles, regardless of local consensus on the appropriateness of such infoboxes).

That is, however, only the background. This case is not about should Wikipedia be using this technology. It is about whether some users have behaved inappropriately in attempting to get this technology accepted everywhere on Wikipedia, or whether some users have behaved inappropriately in attempting to block this technology being employed in certain places on Wikipedia. Andy Mabbett is the expert on this technology, and if we are to fully explore it, his knowledge and experience would be invaluable. However, it appears that in his enthusiasm for the technology, he has been irritating a number of other users, and he has perhaps not been spending enough time on Wikipedia getting the community to buy into his vision. It is a grave error, and one that may prove costly both to him, and to the advancement of this technology. It is frustrating that this is the third time he has been involved in an ArbCom case related to the same issue. Though a user may be pursuing the right end, the means are also very important, and the community cannot work well if some users are allowed to ignore consensus because they have a good idea.

My view is that I am inclined to support a site-ban for Andy Mabbett, but I also see the need for the community to have a full and detailed discussion on the metadata technology, and such a discussion would benefit from the involvement of Andy Mabbett. I am wondering if a suspended site-ban would be appropriate. Allow Mabbett time on Wikipedia to get others to buy into his vision. Build some bridges. Explain more clearly how the technology works. And listen carefully to the concerns of the community. Perhaps get the site developers and the Foundation involved. While doing that, there would be certain conditions which if he broke would trigger an indef ban. Conditions such as: edit warring; arguing over using an infobox in an article (if someone objects, simply back off - there are over 4 million other articles on Wikipedia to work on); and being dismissive or incivil to other users (think twice before clicking "Save page" - has that comment the potential to be read as offensive or hostile? As an example - repeating in bold three times "Why are you making pronouncements on the validity of this request if you do not understand such things?" has the potential to be read as offensive and hostile). I haven't decided yet to simply support the current site-ban, or to propose a suspended one. SilkTork ✔Tea time 03:00, 27 August 2013 (UTC)

"Why are you making pronouncements on the validity of this request if you do not understand such things?" has the potential to be read as offensive and hostile. It can also be read as helplessness when faced with missing a basic common ground in a discussion, which needs to be established before you can reasonably talk. See (from Don Carlos):
  • My general thoughts on the Infobox (including that in my personal history I argued exactly as shown above) is found on Wikipedia:QAI/Infobox, short: the infobox is meant to repeat, in structured form, -- Gerda Arendt ( talk) 11:49, 7 July 2013 (UTC)
That's not consistent with WP guidelines on infoboxes which stress that they are to summarise not repeat. -- Klein zach 14:46, 8 July 2013 (UTC)
Without looking: How would you "summarize" a date of first performance, a subtitle, the name of a librettist, etc? If the guideline does not allow to repeat those key facts it needs to be changed, -- Gerda Arendt ( talk) 14:51, 8 July 2013 (UTC)
No, Gerda, the box is supposed to summarise the article, i.e the article as a whole. Klein zach 15:07, 8 July 2013 (UTC)
How can one say politely that a key player in the infobox discussions has a misunderstanding of what they are? I wonder how much conflict could have been avoided if it was accepted that infoboxes hold key facts, not a summary of the article. Wikipedia:Manual of Style/Infoboxes#Purpose of an infobox: "When considering any aspect of infobox design, keep in mind the purpose of an infobox: to summarize key facts in the article in which it appears." I understand that this means only key facts, avoid trivia. - What do you think? - Do you think an infobox on Verdi has to capture his genius? It's a myth. Not even an article can do that. - A common understanding of such basics is crucial for a discussion. -- Gerda Arendt ( talk) 06:16, 27 August 2013 (UTC)
While particular users' behavior in these particular cases is certainly a big part, if not the focus of the case, I think the arbitration committee has an opportunity to make a recommendation regarding the larger underlying issue that causes these conflicts to arise, even if until now they've taken place on a smaller and less noticeable scale. The guideline we have really offers no guidance at all -- it is in the end merely a negative statement: that there is no policy, so just decide amongst yourselves, using no criteria in particular. In addition to deciding what sanctions to impose on users, I think making broader recommendations when an underlying issue is present seems to have always been within the purview of arbcom. Equazcion (talk) 03:37, 27 Aug 2013 (UTC)
The "Why are you making pronouncements on the validity of this request if you do not understand such things?" comment was in this discussion, where (as Gerda suggests) it seemed a proportionate response to the wall of the demonstrably ill-informed and ad hominem dismissal of a proposed action which already has unequivocal support at an RfC (and which as a result of that unfounded intervention is currently stalled). Since that's not how it read to you or others, at whom it was not addressed, I apologise. I wonder if you, @ SilkTork: would like to comment on similarly worded, "offensive and hostile" comments addressed to me and others on various talk pages, by parties and commenters in this case, along the lines of "you clearly have no interest in..." or "you clearly have no knowledge of...", which, unlike my comment under discussion, are not accompanied by evidence and have no basis in fact? Also, which are the other two "metadata arbcom cases" to which you allude? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:31, 27 August 2013 (UTC)
I would be more reassured Andy if you were reflecting and taking on board concerns that people raise rather than arguing against them. If any user proposes something - regardless of what it is - they will likely meet some concerns. Some of these concerns will be valid. Some will arise out of a lack of clarity regarding some aspects of the proposal. Some may well be wide of the mark. All concerns need to be met with the same politeness and genuine attempts to allay the concerns. If after several reasonable attempts to allay the concerns they are simply repeated without showing signs of understanding, and if after reflecting on the adequacy of the explanations, perhaps asking what aspects are not clear, possibly rephrasing if needed, the same concerns are again repeated and it starts to appear as though the person asking is being disruptive, then it is better to ask for assistance rather than resorting to be impolite. If at this stage you don't understand that, then I am concerned. SilkTork ✔Tea time 09:37, 27 August 2013 (UTC)
In general, a fair point, and one I'm taking on board as a a result of this case (if you will, consensus not only has to be done, but be seen to be done), and I would indeed seek third party assistance in such cases in the future (you can read that as a formal undertaking if it helps). You appear to have missed my question about similarly worded, "offensive and hostile" comments. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:54, 27 August 2013 (UTC)
Andy, you are close to drowning, Silktork tosses out a lifeline, and you are essentially complaining that it didn't precisely hit the mark. Astounding. SPhilbrick (Talk) 18:13, 28 August 2013 (UTC)

( edit conflict) [This case] is about whether some users have behaved inappropriately in attempting to get this technology accepted everywhere on Wikipedia, or whether some users have behaved inappropriately in attempting to block this technology being employed in certain places on Wikipedia. Andy Mabbett is the expert on this technology, and if we are to fully explore it, his knowledge and experience would be invaluable. However, it appears that in his enthusiasm for the technology, he has been irritating a number of other users, and he has perhaps not been spending enough time on Wikipedia getting the community to buy into his vision. This to me is the heart of your apparent misunderstanding. As evidence has repeatedly shown, it is not Andy who is failing to get the community to buy into his vision, the problems all stem from a small number of users who have a dislike of infoboxes and who refuse to engage in discussion about it. You can continue to try to ban Andy for having been banned before if you want, but you can't expect people who have actually read all the evidence in this case to support your "grand vision" for an Andy-free project, nor can you expect it to solve the actual problems in this case. Thryduulf ( talk) 09:43, 27 August 2013 (UTC)

Is there an article showing an infobox edit war with only arguments from infobox supporters on the talk page? Why are those who oppose infoboxes considered to "refuse" discussion, whereas supporters are just trying to help? Some editors are able to propose change in a manner that is not disruptive. When such an editor encounters stiff opposition, they adapt, assuming that the opposers are acting in good faith, and that assistance or time is needed so others can understand the benefits of the proposal. A good editor might even contemplate whether the opposers have a valid point of view. Some editors can collaborate, while disruption seems to follow others. Johnuniq ( talk) 11:23, 27 August 2013 (UTC)
There is ample evidence in this case of where I or others have attempted to open a dialogue, and been met with a blank refusal. There is no evidence of the reverse. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:31, 27 August 2013 (UTC)
That's not strictly true Andy. In the Frank Matcham discussion you were offered an alternative compromise version, which you refused to even consider "because it finds no favour". To say there "is no evidence of the reverse" is just misleading, I'm afraid, although I'm sure it may have just slipped your mind. - SchroCat ( talk) 11:39, 27 August 2013 (UTC)
Yes, SchroCat, it is strictly true. In the Matcham discussion, I replied: "...the collapsed infobox, with hidden content, hasn't been implemented across WP because it finds no favour, unlike the million-plus uncollapsed infoboxes we have... Collapsing the infobox not only defeats its primary purpose, of providing a quick and convenient fact-list for those readers who desire or find useful such a thing (and there is evidence that readers [...] do), but also hampers the usefulness of providing accurate machine readable metadata, since hidden content is more likely to be overlooked when pages are updated. However, if you still think we should adopt that model despite such shortcomings, then - again - a centralised RfC should be the way forward." (of course, I should have said "2.5 million-plus uncollapsed infoboxes". Mea culpa). That might be a discussion that you find inconvenient, or even dislike intensely, but for you to attempt to portray it as a blank refusal to open a dialogue is at best misleading and quite possibly disingenuous. You continue to throw out false allegations, based on either no evidence or blatant misrepresentation of evidence. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:03, 27 August 2013 (UTC)
I'm afraid we are going to have to agree to disagree on this, as we do on so many things. You were offered a compromise solution on Matcham: you rejected it out of hand with a line of argument that a)smacks of WP:IDONTLIKEIT, and b) I am not sure I believe ("hampers the usefulness of providing accurate machine readable metadata"? Not at all true). It's not a question about an argument that I find inconvenient or dislike, so please don't try and double guess my rationale again: try to stick to the more concrete things people can understand, without trying to look into the psyche of others. I'll ignore your regular passing (and baseless) ad hominem comment, I find them part of the scenery in discussions with you, so there's no point in trying to rile me with such silliness. - SchroCat ( talk) 12:29, 27 August 2013 (UTC)
Like something or not is one thing, but accepting something that "defeats its primary purpose" seems strange. I also have to disagree with you on this, SchroCat, as I disagreed with Nikkimaria on it, see? Dealing with a cantata "There is a contrary and despairing thing" (illustrating my present feelings quite well) I phrased about collapsing: I "regard (crossed out stronger term for dislike) the other as against the spirit of an infobox as openly accessible information. I don't revert it in articles of others (Little Moreton Hall comes to mind), but please please please don't do that to me in my articles, - it's against my sense of quality." The reply was: "functionally, there is little difference", which told me that I was not understood. -- Gerda Arendt ( talk) 12:50, 27 August 2013 (UTC)
( edit conflict) Please feel free to disagree all you like with my reasoning in the cited comment, and the basis for it; and even to wrongly doubt my sincerity. But to pretend for a minute that it is evidence of refusal to engage in dialogue is fatuous in the extreme, and to describe it in such terms and link it to a pattern of similar incidents is not ad hominem. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:55, 27 August 2013 (UTC)
"You continue to throw out false allegations, based on either no evidence or blatant misrepresentation of evidence." There was no false allegation and I find your words an ad hominem that are, at best, unhelpful, as is following it up by accusing me of being "fatuous". I stick by what I first said, that you were not being entirely accurate when you said "I or others have attempted to open a dialogue, and been met with a blank refusal. There is no evidence of the reverse." There was evidence of the reverse, it's just that you didn't like what was being offered to you and rejected it out of hand. I'm taking this off my watchlist (again), so feel free to write whatever you want: others will judge your words for what they are. I find interacting with you utterly frustrating and demoralising: you can't see beyond beyond your own opinions on things and cannot behave like discussion is anything but a battlefield for you to smear and wound your opponents - and well done for beating another person away from a discussion. I'm utterly sick and tired of it and hope that I never see another petty, supid and pointless infobox argument break out again. - SchroCat ( talk) 13:12, 27 August 2013 (UTC)
I don't know what you mean by "infobox edit war with only arguments from infobox supporters on the talk page", it seems logically impossible, - it's war or it's only one side. Wars are rare, thank goodness, we try to learn, really. More frequent are discussions with repetitions of similar arguments, see [[ Rigoletto, reaching no consensus. We need a procedure to solve those cases, and banning one contributor will not solve them. However, as mentioned above, one protector of the status quo found a simple solution: change the Manual of Style. (Rigoletto would fall into a category which has no more option for an infobox.) Can we please come up with something more constructive? -- Gerda Arendt ( talk) 11:55, 27 August 2013 (UTC)
I'm going to have to respectfully disagree with you, SilkTork, about what ArbCom can and can't do. In WP:ARBDATE, a protracted and difficult case that occupied seven months of 2009, ArbCom passed the following Enforcement:
  • Stability review: "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 that has broad community consensus."

Ryan Postlethwaite (God bless him) put a huge effort into organising and conducting a grand RfC to settle the content issues. It succeeded and there has been no war over any form of date de/linking to this day. I agree that ArbCom can't settle the content issues itself, but as you have indicated, it could go a long way to making sure it's in the interests of all involved for the warring to stop. -- RexxS ( talk) 13:13, 27 August 2013 (UTC)

Further update

By my estimation, it is likely to take at least another week before the case is close to closing (possibly longer). I'm aware that there has been a large amount of debate on this page in recent days, but can I ask that everyone please show restraint and focus purely on the proposed decision from now on? That will help those arbitrators who have yet to vote or complete voting, as there is a lot on this page for them to read. Carcharoth ( talk) 23:50, 26 August 2013 (UTC)

It is to be hoped, not least given AGK's undertaking and his request for additional evidence, that those who have voted will also be reconsidering. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:55, 26 August 2013 (UTC)
I can speak from bitter experience that if you're going to railroad somebody in an arbitration proceeding you need to do it fast before people notice what you're up to and start asking pesky questions about evidence and motives. By all means, let's drag this out and see if some clueless administrator will block one of the participants while you all decide whether or not to jump off the ledge. Mackensen (talk) 00:40, 27 August 2013 (UTC)

Better a well-thought out and consider decision, Carcharoth, than one made to hastily made. As far people posting, I'm not sure what can be done about that. People want to talk about this case and they will look for an appropriate forum to discuss it. If not here, it has to be on another page. Liz Read! Talk! 00:50, 27 August 2013 (UTC)

I understand Carcharoth's frustration quite well. He's trying to get the stupid case in the can (whether it's just or not is beside the point now) but no one dithers more than a half-active arbitrator who has just realized this job isn't what s/he signed up for and can't bear taking an unpopular stand. In the meantime, the talk page is exploding and he knows sooner rather than later someone's going to say something rash enough to earn a civility block, and then we'll have to hold a whole other arbitration case to deal with the inevitable fallout. Clock's ticking.
As to the merits, it's clear from the proposed decision that the committee should never have taken the case in the first place. None of the proposed bans are really supported by the evidence; if that's all it takes to get someone banned these days I've some scores to settle and some cases of my own to bring, although somehow I don't think I'll be as successful. No one's indispensable, but that doesn't mean prolific editors should be banned, blocked, or restricted lightly. This is ultimately a content dispute, not a personal one, and it'll have to be settled in the usual, painful way. You ought to just dismiss it, or water it down with the usual adjuration that we should all be nice to each other. Mackensen (talk) 00:58, 27 August 2013 (UTC)
Mackensen (a former arbitrator) makes some good points. Liz, it would be a good idea to centralise 'overflow' discussion at another page and leave links from here (anyone is welcome to do that). Specific commentary about aspects of the proposed decision is what is really needed. Some wider debate has been helpful initially, but that can only go on for so long before it detracts from the specifics of discussing the proposed decision. More specifically, those facing sanctions need the time and space to respond to what is being decided here. Carcharoth ( talk) 01:10, 27 August 2013 (UTC)
You know, I beginning to wonder why anyone would want to be an Arbitrator. Seems like a thankless job. Thanks for plugging away at it, even in mid-August. Liz Read! Talk! 01:51, 27 August 2013 (UTC)
Just to give an update from me; I'm one of the dithering Arbitrators referred to above. I have been trying to keep up with this case, but I have other Arbitration work too: CheckUser/Oversight appointments, Ban Appeals work, and the Tea Party Movement case. All three have been neglected just as this case has. I'll try to get this done by next week, but realistically that may or may not happen. For now, my preliminary analysis it to support the first several paragraphs of what SilkTork wrote above but again, there are a billion RFCs and talk page discussions to read and for someone who found out that there was a serious problem with infoboxes on Wikipedia in July 2013, it's not exactly the easiest thing to immediately grasp. NW ( Talk) 03:15, 27 August 2013 (UTC)
If you want a gentle suggestion, it looks really bad when your (the committee's) proposed decision essentially ignores one side of a dispute, even though ample evidence was presented. Arbcom isn't supposed to take sides in a content dispute, but you are here. Mackensen (talk) 04:38, 27 August 2013 (UTC)
If you want to take another gentle suggestion: don't look at a billion RFCs but at 2013, it would make your life easier and mine. Remember:
@ NW: your wording "ban the worst offenders" reminds me of " arrest the usual suspects". As one of them, I urge you to go beyond suspicion, to facts, -- Gerda Arendt ( talk) 18:56, 15 July 2013 (UTC)"
That's an excellent point, Gerda. That was me looking at the situation in July, never having understood that there was a problem with infoboxes. Having extensively read the evidence since, I understand that my first impression was entirely wrong. I'm still not entirely sure how I'm going to vote on the case but I know "arrest the usual suspects" is not on the table. NW ( Talk) 17:00, 27 August 2013 (UTC)
Thank you! There should be no problem with infoboxes, meant to be help and service. Repeating: if someone added infoboxes to my articles, I would say thank you. It is hard to understand for a newcomer - I am relatively new to the topic - why most works by Kafka have an infobox, no problem, but the addition of one to a book article in September 2012 is still remembered as a (insert the terms you heard) discussion, believed by some to have driven away a precious editor. This is not the fault of the infobox, which is rather simple in case of a book. The Rite of Spring, similar, a composition, - Bruckner's symphonies have infoboxes since 2007. - I have good news for you and all: the unilateral change of the MoS of project opera, aiming to keep the operas of all major composers free from an infobox, was reverted, a discussion is called for. -- Gerda Arendt ( talk) 19:07, 27 August 2013 (UTC)
@ NW: I'm not really surprised that you didn't know of problems with infoboxes because over most of Wikipedia, there's no concern. However at WikiProject Composers, infoboxes have been a problem for many years. If you're feeling masochistic, take at look at the 2010 Wikipedia talk:WikiProject Composers/Infoboxes RfC - 219 kB of text where you see the same anti-infoboxers rehearsing the same weak arguments ("redundancy", "consensus amongst the main contributors", etc.) against a different bunch of pro-infoboxers (many of whom have since moved away). You find DGG patiently explaining about the value of metadata and about building the semantic web, and you even find Kleinzach complaining about canvassing, because the pro-infoboxers hadn't notified all of the other relevant wikiprojects. What's the word I'm looking for? -- RexxS ( talk) 14:57, 28 August 2013 (UTC)
I am not concerned about myself, and I haven't seen recent facts that would justify banning. -- Gerda Arendt ( talk) 07:09, 27 August 2013 (UTC)

Infoboxes and new articles

Any restriction on adding/not adding infoboxes to articles should specifically exempt creating new articles. As it currently reads, the first Pigsonthewing remedy seems to say that he cannot add an infobox to an article that he creates. –  Philosopher  Let us reason together. 03:12, 27 August 2013 (UTC)

Nor an eight-word stub that I turn into a proper article. Nor an article on a subject well away from classical music and he other parties in this case, where there is no dispute on the use of infoboxes; or even where infoboxes are the norm. Note my evidence higher up on this page, listing the 60 infoboxes I added to existing articles in the first six months of this year. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:15, 27 August 2013 (UTC)
I didn't look closely enough at the case to see if a restriction on the other cases you mentioned would be merited or not. My only thought was that since this is about conflict between users, a restriction where there was only one user would be irrelevant. –  Philosopher  Let us reason together. 02:18, 2 September 2013 (UTC)
See the section "Proposed remedy 1.1" currently at the bottom of the page, where I have proposed wording that allows for this. Johnbod ( talk) 03:03, 2 September 2013 (UTC)

Finding of Fact No. 4

Could I prevail on whomever's drafting this decision to clarify the problematic behavior? I see much forceful arguing, yes, but that's not impermissible and in general appears to be within the bounds of civil discourse. The evidence linked is also rife with personal attacks, bad faith, and innuendo from editors not named Pigsonthewing, none of whom are themselves subject of findings of fact or "remedies." If I were looking at those linked pages as a matter of first impression it would not occur to me that it was Pigsonthewing who was being sanctioned, and I'm still not sure what policy he's alleged to have violated. Thanks, Mackensen (talk) 12:31, 27 August 2013 (UTC)

  • Still waiting for an answer here. Surely the ten who endorsed it and five who (presumably, given no other findings of fact) consider it the basis for a ban can quickly explain. If there's confusion about why you're banning someone then maybe it's not a great idea. Mackensen (talk) 12:31, 28 August 2013 (UTC)
  • I am deeply concerned that an arb decided to vote for banning Andy, mentioning the Peter Planyavsky case. Andy helped me (!) there, as often, on "my own" article where I wanted an infobox (and still don't have it). -- Gerda Arendt ( talk) 12:49, 28 August 2013 (UTC)
    • I'm put in mind of Henry's apocryphal plea, "Will no one rid me of this turbulent priest?" This case now borders on the farcical. Mackensen (talk) 13:31, 28 August 2013 (UTC)
  • As is quite apparent to me, and as the finding states, Andy's contributions to the theatre of infobox disputes have been broadly unhelpful. The diffs show a sample of the evidence to support that conclusion; and they are illustrative, not exhaustive. Bearing in mind that this has been a heated and protracted dispute (where level-headedness is basically mandatory, if the whole thing isn't to descend into chaos), I don't think it's reasonable to contend that Andy's conduct illustrated by these diffs was helpful; is that what you're trying to suggest in your first few sentences?

    I was under the impression that anybody else who is a prolific party to this dispute has been appropriately sanctioned, if they have had a negative effect on the dispute, but even if there were other people whose conduct has been wrongly overlooked, that would not excuse Andy's truculent interactions with the other disputants, nor make his previous influence on the dispute less disruptive. Debating whether he's earned a site ban is fair enough, but suggesting that he's conducted himself appropriately on all, or even on many, occasions is pretty out there. AGK [•] 18:07, 28 August 2013 (UTC)

  • Well, I think you're asking me to prove a negative. What would helpful look like? Reading over the discussion truculent may be apposite, but he's not uncivil, he's not name-calling, and he's generally advancing the idea of why a particular edit ought to be made. I'm not aware of anyone else being sanctioned in this dispute, and I think that if you're going to ban someone outright you need to go a lot further than characterize comments as "unhelpful", especially when you have other editors specifically disputing that characterization. Above all you need specifics. Let me ask another question: do you see any other unhelpful people on those talk pages? I do. Do you think they're going to be helpful to the next editor who rolls around if you ban Andy? I don't. Mackensen (talk) 18:14, 28 August 2013 (UTC)

Continued collaboration?

What I like best on Wikipedia is collaboration.

  • Did you know that Andy and I created {{ infobox Bach composition}}?
  • Did you know that it was copied to the German Wikipedia, first installed recently?
  • Did you know that there's an an article on which Giano, Eric Corbett, Andy and I collaborated?
  • Did you know that there's another one by Nikkimaria, Tim riley and me?
  • Did you know that The Company of Heaven, Benjamin Britten's 1937 composition for speakers, soloists, choir and orchestra, contains "metrical spoken (shouted) male chorus"?
  • Did you know that Ben Gunn, imprisoned 32 years for killing a friend when he was 14, earned a Master of Arts degree in peace and reconciliation?

Let us continue collaboration with Andy.

  1. -- Gerda Arendt ( talk) 12:49, 28 August 2013 (UTC)
  2. -- Khazar2 ( talk) 13:40, 28 August 2013 (UTC)
  3. No. Since you mention my name, I will comment. I accepted an infobox (without question for its need, although I did question some of its dubious content [125]) on Holzhausenschlösschen because you, Gerda, were the major concerned editor [126](if I recall correctly, you posted on my talk-page requesting my input [127]). I respect your views on pages where you are a major content contributor - I never comment in these infobox disputes on pages where I feel my input has been non-existent or negligible. Unfortunately, Andy Mabbit does not reciprocate that view where his input is minimal. My solution of leaving these disputes to those writing and maintaining the pages is the obvious peaceable solution.  Giano  18:55, 28 August 2013 (UTC)

Comments and a suggestion from Harry Mitchell

Please forgive me if if this might have been better presented in he evidence or workshop stages; I missed those, mostly as I have limited access to the Internet at present, but also because I think the whole thing is a bit silly. However, after a heated conversation with a friend at the weekend, I wanted to offer a few thoughts. For the sake of transparency, I should declare that Andy Mabbett is a personal friend in real life and Nikkimaria is a fellow coordinator of the military history project whom I've worked with in the past and hold in very high esteem. I am less familiar with the other parties, but this seems to me not to be the typical arbitration case.

This isn't a political or nationalistic dispute spilling over onto Wikipedia (like Armenia/Azerbaijan, Israel/Palestine, etc, etc); it's a group of very intelligent and otherwise rational editors who have made immense contributions to this project but who seem to have lost the plot a bit. I actually intended to be quite scathing of several of the parties, but they have all presented themselves well in this case, made reasonable comments, and suggested that they are willing to sit down and discuss the issues with infoboxes like adults. They're not children who need disciplining, nor zealots who are incapable of putting the needs of the encyclopaedia above their own personal biases, so the optimist in me hopes that the discussions around infoboxes can continue without anybody (pro- or anti-infobox) having to be forcibly removed from the discussions or the project as a whole. What needs to end and what is totally unacceptable and unconducive to productive discussion is:

  • The snarkiness, sniping, sarcasm, condescension. Editors need to behave like adults and not resort to juvenile name-calling, or thinly veiled remarks about opponents' mental health, intelligence, etc.
  • Similarly, the contempt in which the parties hold each other (of which the above is a symptom). Folks need to wipe the slate clean and remember that we're all working to the same end. We're entitled to disagree on the route we take to that end (it's inevitable, and ArbCom should not seek to suppress honest disagreement), but no progress will be made through petty bickering.
  • The belligerence of the parties, the passive-aggressive behaviour, and the spoiling for fight. This includes the attempts to railroad infoboxes in by force and the continual hammering on the same door, which only heightens the bad feeling, intensifies the dispute, and only makes the anti-box parties dig their heels in even further. It also includes reverts with cryptic or inaccurate edit summaries, and any other behaviour which is intended to avoid or derail discussion.
  • Adding infoboxes to articles where previous contributors have opted to omit one (or removing long-standing infoboxes) without establishing a consensus on the article's talk page. The parties have all been around the block enough times to know that this causes more problems than it solves.
  • Attempts to undermine or demean opponents by manufacturing a divide between "content creators" and "others". The idea that there would be such a divide is anathema to the principles of Wikipedia, and, more importantly, it's a fallacy—many (most, even?) Wikipedians write articles and do other things. Defining oneself as belonging to one camp or the other in an attempt to belittle the other demeans every contributor to this project and serves no purpose towards addressing the resolving disagreements.
  • Flash mobs (whether recruited on-wiki or off, ie including but not limited to wikiprojects and ad-hoc groups of friends) turning up en masse as if to fight in a battle. Wikipedia is not a battleground, and editorial decisions are not made by volume of advocates, so attempting to drown out opponents with vast numbers of "me too" comments is unhelpful at best.

My suggestion would be to be liberal with the admonishments/reminders/cautions if ArbCom wants to be seen to be doing something, but really this is a content dispute. It can only be resolved through discussion. Perhaps once all the parties have had a dressing down for their various misdemeanours, they could attempt to work out their differences on a centralised talk page (for issues around infoboxes in general) and on article talk pages (for issues concerning infoboxes on a specific article). A small group of mediators (experienced editors who have or can earn the respect of both groups) could be appointed to keep order, and could be given the power to caution editors and then remove comments or ban them from a specific discussion or all infobox discussions if their comments continue to degrade the quality of the discussion. It won't resolve the questions about whether and where to use infoboxes (that's for editorial discussion), but it might improve the quality of the discussion. And if it doesn't, the case can be revisited in a few months with liberal application of bans for those who refuse to engage in civilised discussion. HJ Mitchell | Penny for your thoughts? 15:45, 27 August 2013 (UTC)

Amen.( olive ( talk) 16:26, 27 August 2013 (UTC))
  • Fine thoughts that we can all agree on, except that there is a distinction between content creators and others (I'm an other). Magnificent articles do not evolve from people like me correcting typos or adding factoids—someone with a deep understanding of the topic needs to devote large effort and energy in an act of creation that is fundamentally different from 100 passers-by adding a sentence each. In this case (where infoboxes are not mandatory, and where good arguments exist on both sides), the most collaborative approach is to employ the WP:ENGVAR idea of leaving an article the way it was built. Battling content creators is very unhelpful for the encyclopedia. Johnuniq ( talk) 00:49, 28 August 2013 (UTC)
    • I'm going to vehemently disagree with that, Johnuniq. Content creators who take so much pride in their work that they don't expect to have to argue the issues on equal footing with everyone else are best suited to non-wiki venues. I'm not even sure how feasible this kind of attitude would be, as not everyone who comes across such an article will be familiar with the special treatment these people are to be afforded. Shall we make a template that reads, "This page was created by a beloved content creator, so tough calls fall by default to them"? Equazcion (talk) 01:43, 28 Aug 2013 (UTC)
      • I don't see how that conclusion can be reached from my statement—of course ownership is wrong and needs to be stamped out if encountered. However, having a group of technical editors say that infoboxes are mother's milk is not sufficient reason for the group of editors who maintain an article to accept that an infobox is necessary. Apparently some third-parties view infoboxes as obviously desirable, and so regard the reversion of a new infobox as an ownership problem, but there is not even a guideline to support that view. Johnuniq ( talk) 02:29, 28 August 2013 (UTC)
          • This is an interesting discussion but - in my view - is mistaken at the premise. Show me one person who likes infoboxes who would say they are "necessary" ("mandatory")? I would say: helpful yes, necessary no. Look at The Rite of Spring (if you dare): Do you see "necessary"? "Why doesn't this article have an infobox?" - that was all, and two versions suggested. How is that "imposing an infobox" (a term I often read and don't understand, as I don't get how that would be "disruptive")? - The question is still open, btw, even if the discussion was closed. -- Gerda Arendt ( talk) 07:51, 28 August 2013 (UTC)
        • I'm not drawing any conclusions about who should win the infobox debate in those or any instances. But when people attempt to answer that question by drawing a distinction between how the opinions of "creators" should be regarded versus those of others, that is an ownership problem. Every article on Wikipedia is a collaboration between editors who all have varying levels of devotion to a topic, from gnome to wizard (or whatever the nomenclature is) -- none of which should dictate their level of control over the fate of articles. How much content an editor is responsible for in a given article should never enter into any debate as proof that their opinion should weigh more than anyone else's. It's always been one of the supreme challenges of the Wikipedia editor to vigilantly let go of those natural notions that creation entitles one to any modicum of control. That's just how this place works, like it or not. Those who can't accept that fact, or simply refuse to, don't get a pass to ignore it. Equazcion (talk) 02:33, 28 Aug 2013 (UTC)
          • Infobox are not compulsory, yet their persistent promotion has caused enormous disuption to a group of content creators—that's about the most damaging thing that can be done at Wikipedia. From frustration, perhaps someone has said that the views of content creators have primacy—that's incorrect, but hardly a hanging offense. If an infoboxes-cannot-be-removed policy is enacted, so be it, but meanwhile maximum benefit arises from defending content creators. Johnuniq ( talk) 03:30, 28 August 2013 (UTC)
            • "meanwhile maximum benefit arises from defending content creators" -- How so? Because we don't have an answer it's best to keep the peace by choosing someone to side with arbitrarily? Or if it's not arbitrary, is it that we need so urgently to keep content creators happy that we should ignore a basic tenet of Wikipedia? The need for content is not so dire that we should bend Wikipedia around those few content creators who seem less satisfied with the way things are actually supposed to work here. Equazcion (talk) 03:55, 28 Aug 2013 (UTC)
              • There is no consensus mandating infoboxes, and both sides have presented sound arguments. Are you suggesting that a good way to resolve the conflict would be to reject the views of those who maintain the article, in order to promote our basic tenets? Supporting content creators is not arbitrary—it is a choice that is likely to result in more good content being created. Johnuniq ( talk) 04:15, 28 August 2013 (UTC)
                • I've made no claims as to how the issue should be resolved, other than somewhere above where I suggested a community-wide RfC to start crafting an actual guideline on the topic. And as Olive below points out, all contributors should be supported equally. Supporting content creators over other editors so that more good content can come about is a tactic best left to independent publications. It has no place on Wikipedia. The ends do not justify the means here. Equazcion (talk) 04:32, 28 Aug 2013 (UTC)
                  • The issue should be resolved by both sides – and I make no apologies for stating that unfortunately there are "sides" – discussing the issues with an view to reaching an agreement, rather than aiming for a "win" for their views. Equazcion expresses some of the frustration I have found when I've seen an infobox reverted with the only reason given being that a particular project was not notified first. Nevertheless, the principal contributors to an article do have an advantage – they almost certainly understand the nuances of the subject better than others. What that means is that we should respect their expertise: they are in the best position to help decide on the content of an infobox. If someone who has guided an article through FAC tells me that key fact A is misleading because XYZ, then I make sure that fact A doesn't go in the infobox. That doesn't mean that their opinion of the value of metadata or accessibility, for example, is worth more than anybody else's. The so-called "content creators" (and I have written featured content, but I'm still unsure whether I'm counted as a content creator or not) are the best folks to improve content and curate it - and that includes the content of an infobox. The sad thing about all of this is that in one small area the very folks who would be of most value in making sure an infobox would improve an article are the ones who are so dead set against having any infoboxes in their walled garden that they have opposed them blindly. There is even an article on a composer which was promoted to FA with an infobox but five years later had the infobox removed (edit summary: "Removing infobox per Wikipedia:WikiProject Classical Music#Biographical infoboxes". The infobox had been there for five years and it was promoted with it - now please read the "discussion" on the talk page. The infobox was of course removed again and is still absent. Then in the next breath, we get told to defend the "content creators". What hypocrisy. -- RexxS ( talk) 12:29, 28 August 2013 (UTC)

Supporting Wikipedians is necessary whatever they do. Good is a subjective judgement. ( olive ( talk) 04:25, 28 August 2013 (UTC))

Unsupported finding /sanctions (Gerda)

This is "controversial"??? Given that many of the additions are from July 2 and are "current," and the other handful I checked show the boxes still there, obviously the boxes aren't very controversial. NE Ent 23:50, 27 August 2013 (UTC)

My infoboxes are very controversial, but the arbs possibly didn't find them. I presented them as evidence. The list also contains some "controversial" infoboxes by Andy, such as Russian Symphony Orchestra Society, Cathedral of Blessed Mother Teresa in Pristina, Reginald Aspinwall. I am interested in a broad participation of one case, to find out how we can reach consensus (or not) amicably and with respect, The Ban on Love, -- Gerda Arendt ( talk) 07:30, 28 August 2013 (UTC)

Infoboxes for discussion

I like the idea of "Infoboxes for discussion", rather like other contentious areas where opinions might be divided and progress is not being made, to have a venue where discussion can take place, and an uninvolved editor/admin makes the final decision. Might be worth folks having a discussion on the Village pump or a RfC page regarding if "Infoboxes for discussion" would be viable. SilkTork ✔Tea time 09:17, 28 August 2013 (UTC)

They are currently on Project QAI. I am willing to open a new subpage for centralized discussions if wanted, but the normal thing would be to go to the article's talk page. Don Carlos is open on QAI since it was deleted from the talk of Don Carlos with the edit summary " The talk page is not the place for an info box. - Typically an infobox is added and reverted, period. It would be a nice service if the one who cleans an article from an infobox would place it on the talk for discussion. Recent examples where I placed it on the talk are Cantata academica (infobox was added by me) and Russian Symphony Orchestra Society (infobox was added by Andy). In the latter case, discussed above, I didn't find an infobox in the article. I wonder if you will ;) -- Gerda Arendt ( talk) 09:55, 28 August 2013 (UTC)
I invite all the arbs to visit the current version of the RSOS article and look at the infobox there (n.b. not the image/ caption set in the top right), then to tell us here what they think of it, its accessibility and usability. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:45, 28 August 2013 (UTC)
- Question re "Editors reminded" section of PD - it says editors are reminded "to avoid turning discussions about a single article's infobox into a discussion about infoboxes in general." In that case, in my opinion "this article needs an infobox because it emits metadata (or wikimarkup, etc)" should never be accepted, or even introduced into discussions about a single article's infobox, is that what is intended? Can this be clarified in the final decision? Smeat75 ( talk) 12:47, 28 August 2013 (UTC)
As I see this "reminder", comments such as this [128] on the Don Carlos talk page, which have nothing to do with the specific article, should never appear again on single article talk pages, I wonder if the arbs agree that is the implication of this "reminder". Smeat75 ( talk) 13:28, 28 August 2013 (UTC)
No, you have it the wrong way round. Any article will benefit from emitting accurate metadata, so that needs to be considered in every case, just as every article benefits from having a quick overview summary of the key facts for the casual reader. It's nonsense like "the infobox is redundant" and "the information is already in the article" that needs to be stamped on strongly. It is obvious that the lead itself suffers from exactly those problems, but we still encourage editors to add leads to articles, because it improves them. Millions of Wikipedia articles benefit from having redundant information in their infoboxes, and there's nothing special about composers that makes their redundant information any smellier than other peoples' redundant information. Redundancy of information is not in itself a disadvantage to any article, but it sure makes a good target for those who don't have any real arguments to muster. -- RexxS ( talk) 15:13, 28 August 2013 (UTC)
This isn't the venue to discuss the merits of infoboxes, and even if it were, it's producing more heat than light. HJ Mitchell | Penny for your thoughts? 13:47, 29 August 2013 (UTC)
The following discussion has been closed. Please do not modify it.
That would indicate to me that nothing will change."Why will an infobox improve the article on Don Carlos", answer "Because it emits metadata" has nothing to do with Don Carlos. Smeat75 ( talk) 15:48, 28 August 2013 (UTC)
Indeed, Rex's frank statement (not his first) that he is implacable that there are never good reasons not to have an infobox for the vast majority of articles shows why this is unlikely to work. There is little point in a "X for discussion" set-up where there are entrenched views among a high proportion of the small minority interested. It just becomes a matter of stamina. Those interested in metadata need to find another, and better way of handling it, linking to the vast amount of work being done outside WP on standard vocabularies, digitizing standard sources with more authority than WP, and so on. Then metadata on WP would become an input and a positive benefit for WP, rather than an output, and a nuisance for us and a benefit for the likes of Google. Johnbod ( talk) 20:10, 28 August 2013 (UTC)
It doesn't have to be so radical or purely black and white. Non-infobox templates could emit the metadata just as well. Collapsible infoboxes that do emit the metadata seemed to gather quite a few votes among those traditionally opposed to them - it's the pro crowd that rejects them out of hand. Infoboxes could have a supplemental flag parameter that trigger a bot which copies to or updates wikidata entries then removes those flagged infoboxes from articles, avoiding recoding non-infoboxes that emit the same metadata - I'm quite sure again that people traditionally opposed to infoboxes for non-metadata related motives could live with 24 hours of infobox presence that gets removed. Or the bot could comment out the infobox once it has done its work, leaving it still present for updating purposes later on. Solutions abound. The willingness to compromise is what is lacking. MLauba ( Talk) 22:02, 28 August 2013 (UTC)
( edit conflict) That's the complete opposite of what I've said, John. I have never intimated "that are never good reasons not to have an infobox" for whatever set of articles you care to choose. I have consistently and patiently explained that there advantages and disadvantages and both need to be balanced when making decisions. See my evidence for starters. I do get rather sick of having words put into my mouth by those whose only goal is get rid of all infoboxes from Wikipedia for no other reason than not liking them. I do believe that an infobox would bring some advantages to Don Carlos: (i) it would provide a quick overview of key facts for the casual reader; (ii) it would enable outside data users to quickly and easily index those key facts about Don Carlos; (iii) it would help improve the accuracy of natural language processors which are trying to glean further information from the text of Don Carlos - which in turn helps spread our content beyond the traditional boundaries of paper encyclopedias. I also can see that having an infobox with wrong or misleading information in it would work against those goals; and I'm even able to accept the argument that so little information about a particular article is presentable as a key fact that an infobox would be a net disadvantage. But that's because I can see both sides of the argument and I'm willing to search for compromises. Your crew hasn't budged an inch with your ownership issues since before 2010 and if you carry on like that, of course you'll find nothing has changed. -- RexxS ( talk) 22:21, 28 August 2013 (UTC)
@ Mlauba: Have you written a "Non-infobox template" that "could emit the metadata just as well"? If you produce one that's as easy to edit and maintain as an infobox, I'll be happy to see it used where infoboxes are unwelcome. Until then though, I hope you'll allow me some skepticism of another pie-in-the-sky idea being thrown around as if it were fact. We usually call it "vapourware". As for infoboxes with collapsible sections, I'm lukewarm although I've created some as examples of the technique. They make life harder for anybody who can't use a mouse, and frankly, if the infobox is getting so big that some of its content needs to be hidden, I'd rather exclude that content from the infobox anyway. -- RexxS ( talk) 22:21, 28 August 2013 (UTC)
"By those whose only goal is get rid of all infoboxes from Wikipedia for no other reason than not liking them."—There is no such person. (One said, e.g., [129].) Your comment may have been said in anger, as we all over-generalize when angry, but such statements make me wonder what the point of ever "debating" or "trying to finding compromise" with you would be, when you misrepresent the situation that much. (Am I supposed to be one of the people who wants all infoboxes removed? Garbage. Hell, I've commented in four or five infobox debates in my life, all in the humanities area (humanities bios, art, lit). This is the main scope of the infobox problem, though it would be hard to tell from the presentation here.)
One tends to stop "debating" when all of one's positions are considered "refuted" by the strident infobox supporters a priori. (Here's a talk-page search of Andy Mabbett saying "refuted". All those top results are him. "Bogus / refuted / misleading / bogus ..."). This case happened because, in the history of the entire infobox debate on Wikipedia, people have questioned infoboxes on perhaps 50-100 specific article talk pages. There was a common factor to most of those cases, as this case has clearly shown. No person was ever present, in the numerous discussions I've seen, who suggested that all infoboxes should be deleted.
RexxS, you called someone a liar [130] and shamed me [131] higher up on this page. Observing that such is permissible, I'm going to stretch my wings and say to you: shame on you for lying (which is to say, knowingly misrepresenting the degree of infobox opposition). This bird has flown. Riggr Mortis ( talk) 23:44, 28 August 2013 (UTC)
Rubbish - there's a whole bunch of people who have never advanced more than the most fatuous of reasons for removing infoboxes - even you could see that if you took your blinkers off. Yes, I am angry, because I can see that all you've been doing here is playing a game to get rid of your principal opponent. There's been no attempt to look at ways of resolving the issues over infoboxes and all you've achieved is damage to the encyclopedia. You must be really proud of yourself. -- RexxS ( talk) 10:11, 29 August 2013 (UTC)
The latest version of an infobox for Don Carlos is here, because it was deleted on the talk of the opera. (Andy restored it there.) Note that it is a double, showing French and Italian version which have different names. For me (foreigner), that's much more obvious than any prose, - feel free to discuss there. -- Gerda Arendt ( talk) 22:35, 28 August 2013 (UTC)
@RexxS You can spare the condescending remarks, thanks all the same. The point is that there are several potential solutions that could dissociate metadata from the present infoboxes, whereas goodwill is manifestly lacking. Fully visible, present-state infoboxes as the sole emitter of metadata is not a permanent truth. It's a matter of convenience. Dissociation of metadata from full infoboxes could be a good way to give all sides what they want. It would also definitely separate both matters, which in reality is probably for the best. MLauba ( Talk) 22:41, 28 August 2013 (UTC)
Yes of course, it's fine to promise all these technological solutions when you haven't a clue about the problems of creating and maintaining them - not to mention the Luddites who will fight you tooth and nail before they'll let you make changes to the articles that they own. Anyway, if you ever look, you'll find that it's not just a matter of convenience, it's a matter of maintenance - or are you going to write a bot that keeps these invisible structures updated as well? It's ok to make promises relying on work from other volunteers as long as you don't have to do it yourself. And I'll tell you this: valuable as it is, metadata is only a minor reason for having infoboxes; the principal reason remains the value that they give to the casual reader who wants a quick fact, or the visitor who doesn't understand a lot of English but can still pick up some key concepts. So you're a very long way off the mark by thinking that stripping metadata from infoboxes would solve anything. The walled garden brigade would still be removing perfectly good infoboxes from their articles just because they don't like them. Or is that the only solution that acceptable to you? -- RexxS ( talk) 10:11, 29 August 2013 (UTC)
You seem intent to pick a fight with whoever doesn't share your absolutist world view. What you are amply demonstrating is that neither the pro-infobox nor the anti-infobox crowd are capable of envisioning a reality that doesn't conform to their narrow vision of what is possible and feasible. You think every single article should have an infobox? Go ahead, get a site-wide consensus to implement one. And lastly stop ascribing opinions to people when you have no idea what their opinion on infoboxes are. If the subject is so emotional to you that you are unable to maintain a semblance of decorum, a wikibreak might do you good. Voluntary or not. MLauba ( Talk) 10:26, 29 August 2013 (UTC)
( edit conflict) And you're pretty quick to leap to the ad hominems when somebody tells you something you find unpalatable. Address the comments, not the commentator. I'm quite happy to stand up for myself and for reason, and if you want to claim that's an intention to pick a fight, you'd better start finding some examples of where I've started it. If someone wants to debate sensibly, I'm more than willing to engage at that level. But when someone starts spouting drivel, I'm going to be telling them so. You know nothing about me, but you want to smear me with an "absolutist world view" - complete and utter bollocks. Have you read any of my evidence or contributions? Thought not. If you had, you'd see I have never suggested that every article should have an infobox, but have given examples of where I've agreed that an infobox is not an improvement - at least one of us understands that we have to debate pros and cons to reach a consensus. Read up on what a strawman is before you engage again. Folks like me have been willing to see both sides of the argument and look for compromise through reasoned discussion, but you come along and pontificate about technical solutions without any understanding of what is involved. I am very angry right now at the most one-sided decision that I've seen from ArbCom in the five years that I've followed them, so if you want to threaten me with a block, bring it on, and show us just how abusive an admin can be when involved in an argument. Why on earth we promote trigger-happy kids to a position where they can threaten other editors that disagree with them is beyond me. -- RexxS ( talk) 13:56, 29 August 2013 (UTC)

Unsupported finding /sanctions (Andy)

@ Carcharoth: asked for comments on the proposed findings.

My detractors have posted a carefully chosen selection of diffs and links to discussions, attempting to portray me and others who share some of my views in the most negative light they could. That is, of course, their right, and they would no doubt say I and others have done the same to them. This arena has, after all, evolved over the years into being an exceedingly adversarial process (the debate about whether and how to remedy that is for another time).

Unfortunately, those who drafted the proposed findings have drawn from these partisan examples some very broad brush conclusions, which others have taken on board at face value. For instance, there are already sufficient votes to pass the finding that my "contributions to discussions about the inclusion of infoboxes are generally unhelpful and tend to inflame the situation". I beg to disagree, and suggest that dispute only occurs in the narrow focus of this case; that is, in articles edited by members of the classical music projects and a small group of others who (for want of a better way of referring to them collectively) are those who see themselves as a "content creator" faction described by Harry. Most of my talk page edits regarding infoboxes were not mentioned in the evidence or workshop stages, because they did not seem relevant, but I believe I have a reputation among many editors for being helpful in that regard - at least, many ask for my advice or assistance, (and I recall being "thanked" in notifications, though I quickly turned that off as a distraction), and I am often engaged in unremarkable talk page discussions which result in undisputed improvements to templates, their content and the articles on which they sit. If Arbcom want it, I would be willing to collate evidence of this, but that would be both time consuming and voluminous.

Even in the discussion cited as evidence in that finding, I contend that my comments, while forceful, are not generally unhelpful. I also note that the finding ignores the comments to which I was subjected in those cited conversations, such as "I suggest you go away and finds a spot where your input is more welcome", "I would have expected you to have had more sense...", and so on.

There is also the contention that I "selectively choose what discussions I consider consensus". This later claim is evidenced solely to the linked discussion about {{ Geobox}}; where a TfD found "no consensus" for a merge proposal, and I have been painstaking to propose small, incremental changes in discussion on its talk page, those of related templates and interested editors, and with related projects Note that in that debate, Ruhrfisch, the cited editor who accuses me of ignoring consensus, said at the TfD "if you want to get rid of Geobox, then 1) fix the infoboxes so they can do everything Geobox can, and 2) make sure it is as easy as possible to convert from one to the other, then ask again"; which is exactly what have been doing (again, I can furnish diffs on request).

As a result of the above finding, there is a proposal, already with enough votes to pass, albeit slated for rewording, which would have me "indefinitely banned from adding or discussing the addition or removal of infoboxes" across all of Wikipedia. I have provided ample evidence, above, that the vast majority of my infobox additions are outside the area of this case as described, and are non-controversial. The project will drive no benefit from preventing them.

I have already indicated my willingness to further moderate my tone in discussions; and I am of course willing to take note of and abide by the "all parties reminded" findings recently suggested. If it is necessary for me to give an undertaking to avoid certain areas of Wikipedia involved in this case, then I shall of course do so. But, as Mackensen notes above in a currently-unanswered question, the evidence presented in this case does not support the findings and the proposed, extensive restriction on my editing or commenting, much less a site ban. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:40, 28 August 2013 (UTC)

I will reply later today as I am ultra busy in real life and for now refer people to my evidence on the Evidence page, which offers much more than Pigsonthewing mentions above. I also ask the ArbCom to decide if the proposed topic ban includes 1) "infoboxes" without the name "Infobox" (such as Geobox) and 2) editing Infoboxes in general (otherwise I foresee a can of worms). Ruhrfisch ><>°° 12:15, 28 August 2013 (UTC)
That does need clarification from the Arbs. As it passes now, the ban is on 'adding or discussing the addition or removal of infoboxs'. On the face of it, that does not include - altering the templates, adding/removing sections to them or nominating them for removal outright. Is this deliberate in order to allow Andy to continue to work on infoboxs? Or is it an oversight? Because I would refer to Ruhrfisch's evidence if its the former. Only in death does duty end ( talk) 13:11, 28 August 2013 (UTC)
As I said I have very little time today, so here to start are the pertinent sections of my evidence on Pigsonthewing's selective use of "consensus" (copied from the Evidence page):

"In my experience, Pigsonthewing seems to try to wear people down, arguing long after consensus against his position been reached. Despite his single-minded pursuit of his goals, he can be frustratingly inconsistent in his arguments. For example, his evidence (above) cites a no-consensus, nearly three-year-old RFC to support adding Microformats on WP. But when I pointed out six-month-old opposition to adding an Infobox at Talk:Rite of Spring, he basically dismissed it as "based on false claims" diff. He did not object to my citing numbers (6-1 against) then, and when I gave a tally/percentage (as is done at WP:RfA) of those opposed to an Infobox in the article (myself included) and those in favor diff, he wrote "So we are making progress!" diff. However when Gerda abstained, I recalculated the tally, and Pigsonthewing called my actions "asinine" and accused me of "rig[ging] the figures in your favour" diff."

"Pigsonthewing is also out to delete Template:Geobox despite "no consensus to merge" (with Infoboxes) on his TfD. He then tried to delete the Geobox piecemeal, starting with the Mountains and Mountain ranges functions here, and here. Next he turned to Geobox|River, by proposing it be "deprecated" at Template talk:Infobox river (and no notice from him on Geobox talk)."

I also note that I later told Pigsonthewing that I had changed my mind on replacing Geobox, but he didn't quote that and I have no time to dig it up now. I will comment more later, no time now. Ruhrfisch ><>°° 19:08, 28 August 2013 (UTC)

My reply to Pigsonthewing is at Template_talk:Infobox_river#Geobox.2C_again and reads in part ". I have changed my mind (especially as I would have to do the work of updating the river articles I am the chief contributor to if this comes to pass). Wikipedia allows editors fairly wide leeway on how they do many different things here (please see WP:IAR). One example is that there are at least three different ways to cite references (with many similar but not identical templates). Are you going to "unify" those too?"
There are over 20,000 articles which use Geobox River - I know how long it took me to convert when the current version of the Geobox was introduced ( diff) and assume conversion to Infobox River would be at least as time consuming. Even if it took only 1 minute per conversion, that would be about two weeks of work to convert all 20,000 plus Geobox River articles. Nor did Pigsonthewing bother to notify the users of Geobox River about his plan to deprecate that version of the Geobox.
In addition, please note that both {{ Infobox mountain}} nor {{ Infobox mountain range}} still CANNOT do everything that Geobox Mountain and Geobox mountain range did (i.e. Geobox mountain had parameters on the geology and geological period and who made the first ascent) [132]. So much for my request that they first "fix the infoboxes so they can do everything Geobox can" and Pigsonthewings claim that this "is exactly what have been doing" sic. Ruhrfisch ><>°° 03:13, 30 August 2013 (UTC)
I (Ruhrfisch) close by quoting Finetooth at the Infobox River discussion "Andy, the issue that concerns me here is editorial control, which should never be ceded to a subset of the whole collective. By consensus, the collective has already rejected your proposal to eliminate geoboxes entirely. Your proposal to deprecate geoboxes is essentially the same proposal. The English Wikipedia and the Commons are parts of a commons managed collectively; anyone, including Google, may reuse the product (encyclopedia articles, data, images) under the terms of the GFDL and other licenses and may participate in seeking changes to existing policies and guidelines. However, participating in policy discussions is not the same as setting policy. That power should remain in the hands of the collective, which has already spoken on this matter. ... "
Ruhrfisch ><>°° 03:22, 30 August 2013 (UTC)

@ Rhurficsh: so because one infobox is suboptimal then all infoboxes are bad and anyone who promotes them needs to be banned? According to my understanding of the way wikis work, an infobox being suboptimal is simply a reason to fix that infobox. If you can't do it yourself you should explain to someone who can what needs fixing, if they don't understand what needs fixing or why then you need to have a civil discussion until you understand each other and come to an agreement. Thryduulf ( talk) 13:02, 30 August 2013 (UTC)

Hi Thryduulf, by no means is that what I was trying to say, sorry to be unclear. Pigsonthewing mentioned me and my evidence, so I tried to clarify. To beat the proverbial dead horse, Geobox was nominated for deletion (by Pigsonthewing), but that TfD was closed as no consensus to merge with the appropriate Infoboxes. Despite that clear consensus, Pigsonthewing succeeded in deprecating the mountain and mountain range functions of Geobox, and tried to do the same for the River function (in the latter case not even bothering to post a notice on the Geobox talk page for a proposal that would wipe out over 20,000 uses of the Geobox had it passed). My problem with Pigsonthewing has everything to do with his repeated bad behavior, and only involves Infoboxes (and Geoboxes) because that is where most of our interactions have taken place.
Just to be clear, I am not "anti-infobox". If you look at the 28 articles I helped bring to FA, about 90% have some sort of box (though I suspect most of those are Geoboxes). In most cases, a box is OK by me, but there are some like Waterfalls in Ricketts Glen State Park or the 3 FLs I have been a co-nom on at FLC that either have no box, or where a box would not add anything useful. To me it is an editorial decision, just like which photos best illustrate an article and what level of detail to go into on different topics. And, for the record, I did support improving Infobox River (see further down its talk page), I just choose not to use it in stream articles I write (and as RexxS can tell you, I can't code templates). Ruhrfisch ><>°° 16:00, 30 August 2013 (UTC)

Silly remedy

"All editors are reminded to maintain decorum and civility when engaged in discussions about infoboxes, ..."

  • So when the case is closed, are the clerks going to put a notice on every editor's talk page?
  • Shouldn't editors maintain decorum and civility when engaged in discussions about ... anything?

While I respect the committee's willingness to settle the issues no one else wants to actually figure out, I've never figured out how vague sweeping remedies like this are intended to improve WP? NE Ent 02:15, 29 August 2013 (UTC)

It's really not so silly. One purpose enshrined in such General Purpose Criterion is its effect on future incarnations of "behavior"; impossible to list for being unknown, and for such GPC, unnecessary. :)  John Cline ( talk) 02:30, 29 August 2013 (UTC)
So what's equivalent to Chemical weapons, committee decisions or haggling over infoboxes??? NE Ent 21:58, 30 August 2013 (UTC)
It's a concept, is all. :)  John Cline ( talk) 22:04, 30 August 2013 (UTC)
NE Ent, that remedy originally referred to the parties to the case, rather than editors in general. The change was made here. See also the comments made by arbs. Strictly speaking, the remedy should refer to editors who participated in this case who would reasonably have read that remedy. It's a warning for people who participated here to keep calm as their conduct will likely be judged more harshly than others if a future case is needed if things flare up again. Though hopefully that won't happen. Your point about how editors in general should maintain decorum in discussions about anything, not just infoboxes, is well made. The wording could be tweaked (e.g. "All editors engaged in discussions about infoboxes are reminded to maintain decorum and civility"), but the current wording is unlikely to be misunderstood. Carcharoth ( talk) 00:25, 31 August 2013 (UTC)

Perspective from Kleinzach

A cluster of issues — personal, publishing-related and technical, (if not philosophical) — are involved in the infobox question. Confusing these issues has made it difficult, if not impossible, to resolve them.

Unfortunately I think the lack of structure and preparation for this ArbCom case (as freely admitted by the initiator), has doomed it to the repetition of old arguments, limiting the prospect of positive outcomes. (If only the energy that has gone into this case could be recycled in the actual encyclopedia! Perhaps we could even start reversing the decline of Wikipedia!)

I’d like to make some quick points:

1. Personal disputes have been discussed in detail. It should be simple enough to determine who has been edit warring and sanction them accordingly. Sanctions should be proportionate. They should be based on how users behave, not on how they think.

2. The ‘publishing issue' — of how to coordinate ancillary material with main text — is important for all encyclopedias, on and offline. This could be usefully discussed in separation from general and technical matters. AFAIK no one is advocating putting wrong information in infoboxes, so there is no reason for a dispute on this aspect of the box question.

3. Technical issues have not been adequately opened up for discussion. We need to look at how the boxes are structured within pages, and used to extract what data, for what purpose. Assumptions have been made by both sides (pro-box and box-sceptic) without any real examination of how the boxes should be coded and applied. In the future, improved, better-linked infoboxes (‘smart boxes’) may obviate some of the present difficulties and help address GIGO concerns (e.g. boxed information missing from articles might be highlighted etc. etc.) I think we should be looking in this direction.

(I’ve been travelling during the last couple of months. I haven’t had time to read all the submissions above and on other pages. I'm only taking this opportunity to make these brief comments because the page has been left open (past its expiry date?). I'm not intending to add anything later. )

Klein zach 08:11, 29 August 2013 (UTC)

This is a talk page for discussing the proposed decision. It will remain open at least until a decision is finalised.
The personal dispute problems are not a matter of edit warring, so more nuanced remedies are required.
The publishing issue really does need to be discussed outside of this case. I wish you luck with it.
It is pretty obvious nobody will advocate putting wrong information into infoboxes, but you seem to have conveniently forgotten those who have complained about other people putting wrong information into infoboxes. (It's always other people, right?) To refresh your memory, here are a few snippets of those complaints:
  • "if boxes are a possibility, no matter which ones are out there, I expect that editors who think everything from plainchant to Mahler's "Resurrection" Sym. is a "song" will persist in afflicting us with The Wrong Box, and, if history is any guide, will then get upset and combattively launch new discussions like this one when others remove them"
  • "editors will continue to use inappropriate boxes or even create a composer/musician box themselves without consulting us."
  • "First, look at the existing article on genre, to which the box gives a link and to which an ingenu might be expected to refer. It's an utter dog's breakfast. (And don't advise me please to rewrite it if it upsets me so, I have other things in life to do). Then let me take issue, as I think many others would, as to ecosaisses etc. being considered as genres. If he has a genre, it's perhaps 'early romantic pianism', but don't quote me on that, I am sure many will disagree."
  • "if the exact same description appears in the lede, then why is there a problem with having it in the infobox? Infoboxes and ledes can and should be edited if a summary description is problematic or wrong for a particular composer."
  • "the project's issue you raise above is not quite right - the primary concern has always been inaccuracy not duplication"
  • "Liszt might get a litle hairy, too: many people assume his was a priest but he only took minor orders, hence he was called 'Abbé Liszt'"
And so on. But those are all from Wikipedia talk:WikiProject Composers/Infoboxes RfC, so you may have forgotten them.
I've spent more than my fair share of time explaining how boxes are structured, and used to extract data, and for what purposes. I have studiously examined how the boxes are and should be coded. I am perfectly willing to repeat any explanations that you feel remain unclear to you. I have over the last few days coded a mechanism for retrieving information from Wikidata into a Wikipedia page ( Module:Wikidata) so that all language wikis can make use of the data from a central repository. So I find it somewhat insulting to be told that I have been making assumptions without any real examination. Some of us have actually been looking forward for a very long time now. -- RexxS ( talk) 10:50, 29 August 2013 (UTC)
Point number 3 is quite true, but it is really not within our scope. We can try to pass a remedy that leads to a binding discussion on it, but the structure is probably not even there for that yet. NW ( Talk) 11:45, 29 August 2013 (UTC)
I generally agree with Kleinzach. More discussion is needed on various issues. The most useful thing ArbCom can do (in my opinion) is set the stage for those discussions, and then sanction anybody who prevents those discussions from progressing. There's nothing wrong with two groups of editors disagreeing or even having a dispute; the problem comes when—through gamesmanship, loss of temper, bad attitude or anything else—people prevent the dispute from being resolved. Forcibly removing people from the discussions at this stage only guarantees that the dispute will continue—perhaps more quietly for a while, but eventually it will come back to haunt all of us. HJ Mitchell | Penny for your thoughts? 14:10, 29 August 2013 (UTC)

Clarification of the 'publishing issue'

It’s been pointed out that my Point 2 (The ‘publishing issue’ above) needs clarification. When I wrote “AFAIK no one is advocating putting wrong information in infoboxes, so there is no reason for a dispute on this aspect of the box question.” I was thinking this issue could be usefully separated from the general debate, and examined objectively and in detail by editors with a view to writing some rigorous guidelines (for an improved and expanded MOS:Infobox).

The ‘publishing, or copy-editing issue’ is about consistence, clarity and coherence, relevance, appropriateness, balance, and presentation, including things like: 1. position of infoboxes within articles, 2. size/text length of infoboxes in absolute/relative terms, 3. box/lead content relationship, 4. box/article content relationship, 5. collapsed or non-appearing fields and field names, 6. appearing field name rules, 7. linking and referencing within boxes, 8. rules on avoiding anachronism, 9. material exclusive to the box (i.e. not in the article), 10. illustrations, 11. use of technical, scientific and foreign languages, abbreviations etc. etc.

The ‘Proposed decision’ states “All editors are reminded . . . to avoid turning discussions about a single article's infobox into a discussion about infoboxes in general.” If centralized discussions of key aspects of “infoboxes in general” have never taken place, then that avoidance will be difficult, if not impossible, to achieve. Klein zach 07:03, 3 September 2013 (UTC)

Thoughts from Quiddity

My thoughts echo a variety of users above (HJ Mitchell and Kleinzach in particular). I sent a variant of this message to arbcom-l, but it was deemed inappropriate for private evidence, so I'm going to post an edited version here.

The current proposed decision is not going to solve the underlying dispute, and is not going to move the community towards solving it ourselves.

As Ched said, "We need leadership".

I would suggest that what we specifically need is: a simple question and answer session - i.e. Someone good at mediating (not just someone enthusiastic about trying to help), reads until they understand the entire issue, and then asks smart questions, and the editors acting-on-best-behaviour *actually answer*, rather than tangenting or sniping - which is what often happens when direct/uncomfortable/backed-into-a-corner questions are asked.

This might also, perhaps even mostly, involve asking editors privately, in order to keep the dialogue unhurried/calm/unreserved/honest/etc. This is why we need someone utterly trustworthy to lead it.

Relatedly, a public RfC will almost certainly not help matters - it will devolve into argument, and !vote counting - we already know all of the issues, we just need to determine whether solving them will actually help.

(Note: The only item I purposefully left out of my "Legitimate problems" list (in Evidence), is the issue of "distraction" - I suspect that this is one of the major reasons that some editors are infobox-skeptics; not wanting anyone to be tempted-away-from reading the hard-worked-upon entire introduction/article - this is a hot-button issue (some editors previously mockingly referred to it as teh Brilliant Prose), and I don't raise it willingly, but it does need to be out in the open.)

Therefore, We need to know:

  • Would an aesthetic redesign/tweaks help?
  • Would reinforcing the template-documentation help?
  • Would anything help?

This is what we need to know, if we want to prevent an eternal-stalemate, and/or individual argumentsdiscussions at the thousands of articles where anyone might object to the inclusion of an infobox.

This is what I was trying to get at, with my Evidence and Workshop suggestions. I'd hoped that arbcom members would simply ask those questions on these talkpages; or in private, amongst themselves, and to the editors; and perhaps the latter is still possible.

I've tried hard to limit the extra content that I oblige arbcom to read, and I will endeavour to not discuss it further here (and I hope nobody replies at length), but I hope this last post helps. – Quiddity ( talk) 03:27, 30 August 2013 (UTC)

I very much doubt that the wider issues are known by everyone: one of the arbs (NW I think) remarked that until July they were unaware infoboxes were an issue, and equally I'm sure that most of the editors who do the normally useful work of adding infoboxes to articles without them are unaware both of the hostility to them in some cases (until they run into it) and also of the "metadata agenda" that drives some of the editors here. The core issue for the infobox sceptics is accuracy - I think I coined "misinfobox" some years ago, which User:Wetman and some others used too (also "disinfobox"). There are things that would help in a small way, but really the way forward has to be to treat metadata separately and more seriously, and as an input rather than an output (see above). I don't think a private mediation that involves choosing whether the online encyclopedia or the metadata output is more important will attract community support. Johnbod ( talk) 11:22, 30 August 2013 (UTC)
"Online encyclopaedia" vs "metadata" is not a helpful thing to be saying, because they are not in the slightest way opposites. The relevant question is "Do we want an online encyclopaedia or an online encyclopaedia?" Thryduulf ( talk) 12:56, 30 August 2013 (UTC)
John, is there any reason why you and Andy (and everyone else with strong feelings on infoboxes) can't sit down and have a rational discussion about these issues with a neural third party moderating the discussion to keep it constructive and on-topic? From where I'm sitting, there are good arguments for and against infoboxes, and you're all intelligent enough to reach a solution, if only both sides would stop bickering and engage in serious, level-headed discussion. HJ Mitchell | Penny for your thoughts? 14:55, 30 August 2013 (UTC)
@ Thryduulf, Rexx's comment above about: "...Andy's desire to see Wikipedia evolve into a resource that is usable in far more ways than simply reading an encyclopedia - I have the Encyclopedia Brittanica on my bookshelves if that's all I want to do" shows a fundamentally different attitude to the project to that of most Wikipedians, I would suggest.
@ Harry - surely that is what the various case pages have been doing for most of the time? It has I think produced considerable elucidation of the issues, and will be educative for any outsider with the patience to read it, but I see little sign of "a solution" emerging. I notice that Rexx, who began the discussions saying discussion would solve everything (if only the other side would stop using "bogus" arguments), has rather changed his tune, as on your talk recently. Johnbod ( talk) 15:43, 30 August 2013 (UTC)
We are not a paper encyclopaedia. If you want to remove all metadata you need to remove all page history, all categories, all page titles and headings, many (if not all) redirects, many templates, most (if not all) tables, etc. All of these either are metadata or produce metadata by virtue of their existence. Metadata and human readable information are not exclusive, indeed far from it. There is no diachotemy between improving the encyclopaedia for human readers of the Wikipedia website and improving the encyclopaedia for those using our content in other contexts. Thryduulf ( talk) 16:11, 30 August 2013 (UTC)
Straw man. Who is proposing that? Nobody. Johnbod ( talk) 16:18, 30 August 2013 (UTC)
    Yes (to "straw man"). Thryduulf, your posts above conflate issues in a rather scary way. You've conflated metadata and data. You stated that to have concerns about the "data emission" agenda is to oppose "metadata", meaning we must delete page histories, etc. Do I need to point out how absurd this contention is? I fear I might, which is why I will spend some time on this post and attempt to tie it back to our original joint statement.
    Thryduulf has given some examples of what " metadata" actually is: it is data about data, in the common definition. The "metadata of a Wikipedia article" would include its size in bytes, its article assessments, and some of the things Thryduulf mentions, like page history. "Metadata" and "data" are different concepts, and you've given evidence that it might be generally useful to clarify this. Someone involved with the "metadata emission" project must have adopted the term " metadata" in a loose sense to refer to data about the article subject that is encapsulated in various ways using HTML attributes. This emission happens most conveniently by wrapping a template around a date or other atomic data point which makes the system output a bit of extra information in HTML source; in turn giving computer programmers more confidence that they are retrieving what they want to retrieve.
    When we speak of "metadata emission" in the sense that its most ardent supporters use the term, we're speaking of "data" about the article subject. Those supporters appear to have originated the use of the term "metadata" for these data emission things they do, and for better or worse we've adopted the term in discussion so that, at least in a local sense, there is an understanding that we're referring to the same thing. But the extra syllables do make it sound more important, I suppose. In short: page history is metadata and (really!!) no one ones to delete the page history. On the other hand, an example of "metadata emission" goes like this: "{{Birthdate|1940}}". That template wraps one piece of article subject data (inside an infobox template) so that a computer can read the data by recognizing HTML code like "<span class="bday">1940</span>". The "1940", the article content, would be in the HTML source either way; the wrapper is meant to help computer programmers. It is easy to imagine every computer programmer saying "yes, that's great!", but they're not the ones who have to measure the goal against its costs. They're not the ones considering project scope. Adding that wrapper to every "data point" in the encyclopedia is no small feat and quite obviously encompasses the creation of a large template infrastructure, plus millions of edits, that some people might consider beyond the scope of the Wikipedia project. When those edits are largely the work of someone who engenders conflict, trouble's a-brew.
    I would suggest that in favour of a "debate" about "[meta]data", the community realize that the entire project of Wikidata was set up to accomplish this task. No, not in exactly the same way as its main supporters have implemented it here—but ultimately in a much better, scalable, computer-friendly way. (It's even multi-lingual, meaning no need to repeat this "data emission" project on each Wikipedia.) Two expected counter-arguments: 1) "The technical means differ." That doesn't matter; to argue that is only to suggest that you are more concerned with the implementation methods you've chosen than the conceptual goal (semantic web, parseable data). Which would suggest an underlying motivation for implementing it all a certain way on Wikipedia. 2) "Wikidata can't accomplish x yet." That would be a reason to help on Wikidata, including in development, and not a reason to continue the build-out of the infrastructure here. We now have a sister project designed to accomplish the equivalent of the "data emission" goal on Wikipedia. The work belongs there, would be welcomed there.
    I justify the length of this post on an arbcom talk page as follows: 1) I hope it may help clarify some concepts and their relations for some arbcom members. 2) I hope it may shed light on our original joint post, by showing in a bit more detail how large and encompassing the infobox agenda is here—how intertwined it is with related concepts (by the primary advocate's design, I mean)—and how easy it will be for the agenda's primary and most active advocate—the one with documented repeated issues of engendering conflict—to just move on to a slightly different area of the "build-out" if topic-banned from only one piece of the puzzle. Riggr Mortis ( talk) 22:54, 30 August 2013 (UTC)
I was hoping that I had finished posting here, but as Riggr Mortis has decided to prolong the discussion, I suppose I might as well add the information he leaves out. There is a standard defined for emitting data in that the names of the data-wrapping classes are standardised. When the template outputs "<span class="bday dtstart published updated>1940</span>" each of those class names is the same as for data similarly encapsulated on thousands of other websites, so that common agents can 'understand' it as perhaps a birthday if it's inside a " hCard" microformat, or perhaps as a date of publication if inside a " hAudio" microformat, and so on. The classes are not only common across websites, but are designed to exist inside a container that gives context - a person, an event, a piece of music, etc. That's one of the reasons why {{ Persondata}} falls short: neither the container, nor the items inside are assigned standard classnames, so they remain invisible to the readers that can read the information inside our infoboxes or their equivalent on other websites.
It would be nice to think that one day every data point in Wikipedia could have a descriptive name (for example a date is marked as a birthday, not just any old date). Adding meaning to content is part of Berners-Lee's vision of building a semantic web and it's something that most people who think about it would see as a "good thing™". But the point about cost is well-made, and on a crowd-sourced site, it is not feasible to expect every contributor to mark up data meaningfully. All is not lost, though; on a crowd-sourced site we should be able to allow other editors with the skills to apply the semantic markup. If they're really clever, they mark it up in such a way that future editors don't have to see the internals - and so that's why we use templates to hide the scary bits. It's also the reason why I find it so annoying when somebody tells me that marking data with microformats doesn't add value to an article. And at the present moment, we only have infoboxes to do that, so it's even more annoying when I'm told there's lots of other ways of doing it. Yes I know that, but at present none of them work.
I would wondering when somebody would raise the issue of Wikidata in an attempt to tell us that we can offload all our data emission to there. I've actually been working over there so I know a bit about it, and I've just spent my most of final contributions here on creating a means of importing Wikidata back into a Wikipedia with full local control, in the hope that somebody in the future will find that useful. But I digress; what I should be telling you is where Wikidata gets its data from. Did you guess? - it gets it from infoboxes. I'm not kidding you. That's where the vast majority of data comes from because a bot can import it fairly automatically and accurately - did I mention that infoboxes also have the advantage of very regularly structured data as well? The downside is that the collection is patchy. I was doing some testing a few days ago and found that Wikidata thought that Richard Burton was born in Wales (hint: there is actually a place called Pontrhydyfen) and only had two wives, one of whom was also one of his childen - they must have confused him with some other actor. I corrected the error manually, but was unable to add three of his four children as they didn't have articles. So Wikidata has a long way to go before it's anywhere near as useful, flexible or accurate as our infoboxes. And if you think the the cost of infoboxes isn't negligible, you'll have a fit about the cost of cleaning the data in Wikidata that you're proposing as a replacement. One day maybe, but that day is not today.
And that's it from me. Goodbye and good luck. -- RexxS ( talk) 00:10, 31 August 2013 (UTC)
I dont known know Rexx, but perhalps if you had used less agressive stalking horses. I know I'm one to talk, but I was only ever provoked, I never wandered out and said "this is the way it should be, if you disagree, I'll have people who will, over years and months, grind you down". Ceoil ( talk) 00:45, 31 August 2013 (UTC)

Implementation Notes

Why do the implementation notes say that 1.2 "cannot pass" and that "1.1 is passing instead"? The maths seem to allow it to pass with one more vote which hasn't been cast yet, and at least two arbitrators explicitly say in their votes that the two are not alternative to one another 92.39.207.86 ( talk) 22:05, 31 August 2013 (UTC)

Only one of those can pass. Actually the second Locus of dispute principle was presented as an alternative to the first one. — ΛΧΣ 21 22:13, 31 August 2013 (UTC)
Thanks, I've misread it horribly - I think it's having more than one row numbered 1.1 that's confused me - why do that? In some ways I suppose it's not as bad as having four 5s, two of them adjacent in the same section. And likewise three 6s, two of them adjacent. But at least there aren't any notes mentioning 5 or 6 by number. 92.39.207.86 ( talk) 22:21, 31 August 2013 (UTC)
Oh I see. I should have written "Finding of fact #1 cannot pass." instead of just "Cannot pass". Let me fix it. — ΛΧΣ 21 22:46, 31 August 2013 (UTC)

Uninvolved user, late to this discussion

Premise 1: I hope we agree that Wikipedia's mission and values make no distinction between first- and second-class readers. We bring free knowledge to the widest possible audience, without discrimination.

Premise 2: I hope we agree that Wikipedia is non-paternalistic; that it does not decide for the readers how they should use information. This is reflected in the policy against censorship, in the provision of an open API so developers can make new ways of viewing and interacting with Wikipedia, and in the licensing which allows adaptation and reuse by anyone, for any purpose.

Premise 3: As a consequence of (2), a lot of the access to Wikipedia's free and open knowledge is via DBpedia and similar harvesting projects, which in turn feed sites such as the BBC. I hope everyone here is familiar with DBpedia's prime importance in the web of Linked Open Data.

Premise 4: People who remove an infobox (or other semantic markup) from an article are, in effect, deleting a page of information. They are not deleting it from Wikipedia itself, but from DBpedia, Google, the BBC, or many other sites and apps

However, as per premise #1 those audiences are no less valid readers of Wikipedia than those that come to the site. They are no less entitled to benefit from free and open knowledge. We're not like commercial web sites where it's all about getting "eyeballs" on your site rather than "competitor" sites: that commercial mentality does not belong here. This isn't a matter of subjective preference: it's core to Wikipedia having a distinctive mission as a free and open encyclopaedia.

So I've come late to this discussion and a lot of what I see is very worrying. Andy Mabbett's statements about making data reusable and accessible are cited against him as evidence of a harmful agenda, rather than of him advancing the Wikimedia mission. The fact that we enable for-profit companies to harvest metadata is cited as if it were against Wikipedia's mission, rather than fulfilling it. I see "the reader" of Wikipedia being defined as those that come to the site, bluntly denying both Wikipedia's mission and licensing (as made clear by RexxS) and the way the Web has evolved over the years.

Whether or not we make information and knowledge open and free, removing barriers so that the greatest audience can participate in it, is not a matter of personal preference. It's not something to be weighed against the aesthetics of how particular users view Wikipedia. It's definitely not something that has yet to be worked out by community discussion. For Wikipedia, it has already been decided. There are clearly vocal users that disagree, but they have a huge uphill struggle if they want to change Wikimedia's mission to fit their preference, and in fairness they need to warn all contributors that "Wikipedia is about knowledge that anyone may freely use for any purpose, with these exceptions..." MartinPoulter ( talk) 10:54, 1 September 2013 (UTC)

Given such confidence that the pro-infobox case is obviously correct, why not propose that a policy prohibiting the removal of infoboxes? The problem with this case is that infobox enthusiasts have not taken a policy approach, possibly expecting that adding infoboxes would become de facto policy after wearing down a few obstacles. Further, the arguments are rather more subtle than assumed in the above. Johnuniq ( talk) 12:18, 1 September 2013 (UTC)
Indeed. Based on MartinPoulter perspicuous reading, those who object to the inclusion of infoboxes are ruining it for everybody; hence, the case for making their inclusion a matter of fundamental policy (up there with RS and V) should be straightforward, compelling and unstoppable. Eusebeus ( talk) 14:24, 1 September 2013 (UTC)
There are good grounds for removing infoboxes, if they contain only wrong or misleading information. I edit mainly in the area of psychology, and I don't think many psychological articles merit infoboxes. So you're both hacking at a straw man. On the other hand, there aren't good grounds for treating the increased availability of free and open knowledge (one form of which is putting information in semantic formats) as an agenda to be resisted on Wikipedia. As to "[T]he arguments are rather more subtle." Why? What are they? As I said, I think the key decision has already been taken and it's the anti-semantic users who want to change the status quo. MartinPoulter ( talk) 10:25, 2 September 2013 (UTC)
Why? What are they? It's not helpful to post summations to write off good editors (very good editors) in a complex case without studying the background. This case is about the consequences for the encyclopedia of a battle—it's not about whether infoboxes are good or bad. The only fact concerning infoboxes of any relevance to this case is that infoboxes are not mandatory. Johnuniq ( talk) 00:11, 3 September 2013 (UTC)

This is not the venue for discussing the rights and wrongs of infoboxes. This is the venue to discuss the way the Committee is dealing with conduct issues arising from those who have been battling over infoboxes. There have been several suggestions made by various people (including a formal one by the Committee) that discussions on various aspects of infoboxes should be held. Hopefully at some point people will start doing that at a more appropriate venue than this one, so a broad range of views can be heard. SilkTork ✔Tea time 14:34, 3 September 2013 (UTC)

The problem that I see is that much of "conduct" was caused by the lack of agreement about infoboxes and who decides in which article they go, causing conflict that would not exist otherwise. (Example: if there was a guideline about infobox in a book article, a traumatic discussion on Pilgrim at Tinker Creek - 2012 and remembered - would not have happened.) - I will bore you but suggest: be easy on conduct of the past, especially of years ago, and work in respect for each other, starting today. -- Gerda Arendt ( talk) 14:51, 3 September 2013 (UTC)

Proposed remedy 1.1

Several of the arbitrators have expressed a desire for remedy 1.1 to be fine-tuned, particularly those who see it as an alternative to 1.2. For my part, I see that remedy as an excellent opportunity to determine whether Andy should be site-banned or not. If his behavior is restricted and things run along okay, then we need not go further. Finding of fact 4 identified Andy's engagement on article talk pages, usually right after an infobox had been added or removed, as problematic. I haven't seen any suggestion that there's a problem in the template namespace itself. If I were tasked with enforcing that remedy I'd understand it, even as written now, to be restricted to the article and talk namespaces, but that may not be clear enough. I'm thinking giving uninvolved administrators (perhaps designated beforehand) the power to ban Andy from a talk page might work, though that would mean specifying unacceptable behavior. The remedy as written though would even prevent Andy from adding an infobox to an article he creates. Sometimes arbitration rulings have perverse outcomes; the committee should probably acknowledge that issue upfront if there's no way to avoid it now. I suppose you could try this:

"Pigsonthewing is indefinitely banned from adding or discussing the addition or removal of infoboxes on articles where he is not already a major contributor."

Open to interpretation and I'm a little uncomfortable with a remedy that more or less endorses WP:OWN. You could also add in the implementation notes "Administrators, don't be stupid when enforcing this" but I don't know if that would work. You might also want to consider a sunset clause or opportunity for appeal, such as was found in 1.2. All bans area appealable of course, but it's best to state these things openly. Mackensen (talk) 15:03, 1 September 2013 (UTC)

Alternatively, on re-reading the decision, the remedy for rejected for several others might represent the desired tailoring:

"Pigsonthewing is indefinitely restricted from: adding or deleting infoboxes; restoring an infobox that has been deleted; or making more than two comments in discussing the inclusion or exclusion of an infobox on a given article. They may participate in wider policy discussions regarding infoboxes with no restriction."

That remedy would have essentially the same effect as the current one, but with a tiny amount of give which hopefully prevents misunderstandings. Mackensen (talk) 15:17, 1 September 2013 (UTC)

For the first bit, how about: ""Pigsonthewing is indefinitely restricted from: adding infoboxes to established articles or deleting infoboxes..." If a definition of "established" is needed, then "articles in existence (under any title) for over one year that are not classed as stubs" should do. I don't think anyone wants to prevent him adding boxes to general articles of types that normally have them, and given he can't restore any reversion, I hope everyone will be happy with this. Do we need to prevent him from "deleting infoboxes" actually? No-one has complained about him doing this.... Why is he "they" at the end? Redrafted whole thing:
  • "Pigsonthewing is indefinitely restricted from: adding infoboxes to established articles (defined as articles in existence under any title for over one year that are not classed as stubs); restoring an infobox that has been deleted; or making more than two comments in discussing the inclusion or exclusion of an infobox on any given article. He may participate in wider policy discussions regarding infoboxes with no restriction." Johnbod ( talk) 15:36, 1 September 2013 (UTC)
    • Per my earlier comments at #Limited number of comments in discussions I think that restricting the number of comments one person can make in a discussion will have the effect of preventing productive discussion while doing little or nothing to prevent unproductive ones (even possibly encouraging them). Thryduulf ( talk) 16:32, 1 September 2013 (UTC)
Well, I expect there will be some lengthy comments, & Andy should finally start using preview. Johnbod ( talk) 17:41, 1 September 2013 (UTC)
That wont help where the conversation is: Andy: "I think this infobox would help this article", Bob: "Generally I agree, but I think nationality is wrong, because...", Andy: "Bob: Would putting 'Austo-Hungarian' there be more accurate?", Carole: "I like this, but I think it's worth putting there that her husband was her third cousin, can the template do that?". Andy (on Carole's talk page): "I'm sorry but I'm not allowed to answer the question you asked me about the infobox.". Thryduulf ( talk) 18:57, 1 September 2013 (UTC)
That's not entirely the way conversations have tended to go. Maybe he could start a user subpage with a) standard FAQ (or FMA - "frequently-made arguments"), and also b) notes re individual cases. It's not entirely clear how many times he could edit one comment - and he often takes a number of edits on a single comment as it is, hence my preview remark. I don't think such a subpage would be covered. I accept it is not a standard remedy, but surely better for him than a full topic ban, which seems to be the most likely alternative. Johnbod ( talk) 19:43, 1 September 2013 (UTC)
That is how conversations about infoboxes tend to go everywhere the classical music/opera editors aren't involved, and it is how we want conversations to go. An FAQ would be useful (if one doesn't already exist?) but only if editors actually read it and understand it (I have no confidence certain editors named on this page would). I would not be at all useful for questions such as this about specific entries in an individual infobox. Thryduulf ( talk) 20:22, 1 September 2013 (UTC)

(Outdent). It might also be appropriate to tailor this remedy to certain projects. My impression is that this dispute is mostly localized to articles which fall under the purview of WP:OPERA and WP:COMPOSER. In most parts of the article space the use of infoboxes isn't controversial and I don't know that any evidence has been brought forth suggesting otherwise. Under those circumstances a more narrowly-tailored project/interaction ban might be appropriate. E.g. (and building on the suggestiosn from Johnbod and Thryduulf):

"Pigsonthewing is indefinitely restricted from the following actions involving articles which fall under the purview of WP:OPERA and WP:COMPOSER: adding infoboxes to established articles (defined as articles in existence under any title for over one year that are not classed as stubs), restoring an infobox that has been deleted; or making more than two comments in discussing the inclusion or exclusion of an infobox on any given article. He may participate in wider policy discussions regarding infoboxes with no restriction."

I've retained the "wider policy discussion" boilerplate to make it clear that he can mention a "covered" article in the context of a wider discussion. In essence, this is an article-space interaction ban but limited to those areas which Arbcom has actually found disruption. Additional narrow findings of fact concerning those projects would be appropriate if this alternative is considered. Mackensen (talk) 20:55, 1 September 2013 (UTC)

  • Oh for God's sake: it's simple mathematics. Pigsonthewing + Infoboxes = Trouble. Whereas, Pigsonthewing - Infoboxes = a Quiet life for all.  Giano  21:01, 1 September 2013 (UTC)
  • Giano, I sympathize, but that's not true for the entire encyclopedia. The committee does no one any favors by painting with too broad a brush. In the areas where I usually work neither Andy nor infoboxes are controversial. This remedy attempts to get at the actual root of the problem, which is the interaction between Andy and a few select projects. If you can suggest improvements to this concept I'm open to them, but full-blown remedies such as what you're proposing are already in the decision and voted upon. Several of the arbitrators are interested in a more tailored remedy, and that's what we're discussing here. All the best, Mackensen (talk) 21:10, 1 September 2013 (UTC)
  • I disagree: Andy's obsessional views on infoboxes (in all subjects from music to architecture) have been a complete pain in the backside for too many for too long; he needs removing from the equation altogether - then others can all be allowed to reach reasonable compromises. He's had dozens of chances and he's blown the lot, I don't care if he's banned from the project of just banned from infoboxes; just so long as he stops causing all this trouble and disharmony.  Giano  21:16, 1 September 2013 (UTC)
  • Giano's got the maths right here: "Pigsonthewing + Infoboxes = Trouble. Whereas, Pigsonthewing - Infoboxes = a Quiet life for all." QED. That's the last thing I'm going to say on this case (I hope). He had his chances. -- Folantin ( talk) 21:32, 1 September 2013 (UTC)
  • I think we must simply disagree on that. There are many subjects on this project where infoboxes are not controversial nor is Andy's involvement in them. Andy is a regular at Templates for Discussion where he is one of many editors pushing for standardization of templates. This isn't considered disruptive by any of the regulars there. If Andy were truly disruptive sitewide I would have expected broader participation in this discussion. If this was truly a sitewide problem and not localized to a connected set of projects I would expect to see evidence of it, but none was adduced. Much has been made of his bad behavior from six years ago. If we were to constantly hold bad behavior from six years ago against editors then this project would be consumed by hatred and be destroyed. People change and grow. The only thing that's apposite from six years is that Andy doesn't deal well with wikiprojects which reject infoboxes. Fine. An interaction ban solves that problem by removing Andy from that equation. We can then see how that discussion proceeds without him. The results should be indicative.
  • Anyway, this thread is about helping Arbcom craft a narrow remedy. If they think it's warranted they'll take it up. If they don't they'll do something else. I don't think it helps anyone to reiterate how we feel about certain editors. Mackensen (talk) 21:39, 1 September 2013 (UTC)
  • So Mackensen, how are your posts anything but "how [you] feel about certain editors"? ;-) Be that as it may, please read the finding "Pigsonthewing's contribution to discussions", which has unanimous support from all 11 active Arbs, cites recent evidence (including disputes outside Music articles) and cites my evidence. You might also find Choess' and some of the other editors contributions on Pigsonthewings behavior useful.
  • Even RexxS, one of Pigsonthewing's strongest supporters, has a more realistic view of his behavior. RexxS wrote on SilkTork's talk page that "You could insist on him having a mentor starting now. What he needs more than anything is someone to tell him "walk away - it's not worth the pain", because he's glaringly bad at recognising when that point has come. ... But if you don't get someone who can help him spot when his best option is to step away - even when he's right - then you might as well ban him forever." ( diff). Frankly, my opinion is if someone can't learn in nearly a decade on WP how to play nice with others almost all the time, then maybe it is time for them to leave the project (voluntarily or not). Ruhrfisch ><>°° 23:05, 1 September 2013 (UTC)
  • You should have quoted the next sentence from RexxS, because it's even more telling: "Over the last few weeks, he's often emailed me to ask my opinion on a given debate and most often I've told him to walk away - to his credit has done that each time." I've found that whenever we try to get into this question of "playing nice" (not patronizing, just quoting) and whathot we get bogged down in the level of disagreeability a person's contributions warrant. I got out of that business a long time ago because it's an impossible question. Mackensen (talk) 12:28, 2 September 2013 (UTC)
  • I could also have quoted Samuel Johnson "Depend upon it, Sir, when a man knows he is to be hanged in a fortnight, it concentrates his mind wonderfully." We shall see how long the good behavior lasts, though I hope it is a permanent change of heart. Ruhrfisch ><>°° 12:36, 2 September 2013 (UTC)
I don't think this will fly, not least because the Arbs are reluctant to take a position favouring "states rights" for Wikiprojects, which this proposal will tend towards. Several areas have come up in the case, in particular literature, architecture, the visual arts, and historical biographies. There's a long-running infobox row at Peter Sellers, with an entirely different cast (ok, largely different, since some here including myself & Andy commented briefly, mostly back in 2012 - Archive 1). The attempts of Thryduulf & others to paint infobox scepticism as very localised are wrong, though there are large areas like sports and taxons where it presumably doesn't exist. Johnbod ( talk) 03:11, 2 September 2013 (UTC)
Maybe so, but that's the practical effect of this decision regardless. The Committee is free to claim otherwise, but sanctioning one side of the dispute and one side only is taking sides and endorsing the position taken by those projects. Can I gently suggest that you broaden your horizons with regard to the project's scope? There are numerous areas: transportation, sports, the hard sciences, politics, languages (just to name a few) where infoboxes are in my experience widely accepted. I don't claim this to be troublesome or difficult; I claim this because I believe it to be true and because it has a significant bearing on this case. Broad remedies are justified by broad problems, not narrow ones. Mackensen (talk) 12:28, 2 September 2013 (UTC)
I said "large areas like..." (and had already mentioned sport) and back on the evidence page and way up above here have briefly attempted to define what distinguishes those trouble-free areas from the troublesome ones. But someone up above suggested biographies in general were a trouble-free area, which is very much not the case. Johnbod ( talk) 13:42, 2 September 2013 (UTC)
Define "trouble-free". I fail to see trouble in the infobox for Verdi's work that will be shown on the Main page, DYK. I fail to see trouble for a symphony that will appear these days. -- Gerda Arendt ( talk) 05:57, 3 September 2013 (UTC)
Mackensen, it is a mere coincidence that the most prolific pro-infoboxer is being sanctioned. I find it quite unreasonable to read a remedy that says "for [consistently unacceptable conduct], Andy is topic banned", then infer that we are sanctioning him because he's a pro-infoboxer. If we also consider that one anti-infoboxer has been sanctioned, and that evidence for misconduct by other anti-infoboxers has not been supplied despite a request for it, I find it quite obvious that the notion the committee has taken a side – or can even reasonably be perceived to have taken a side – is nonsense.

On the request that we write a narrower remedy, I am not persuaded. Even a brief review of the evidence demonstrates that Andy's conduct with respect to infoboxes has been unsatisfactory on several topic areas, not merely on opera articles. The first diff I opened illustrated him misbehaving on an architecture article, for example. The problem is also with Andy and infoboxes in general (cf here), not Andy's views on whether certain subjects are best presented with an infobox. His attitude in general is problematic, not his content views, which is why a wholescale removal is required. If we restrict him from infoboxes in certain topic areas, the committee is only going to have to chase around after him over the next year, adding more and more topics to the topic ban. AGK [•] 12:42, 2 September 2013 (UTC)

AGK, I never said that you were sanctioning him for being a pro-infoboxer; I think you're sanctioning him for being Andy. I'm unfamiliar with anyone on the "anti" side being sanctioned, unless you mean the admonishment of Nikkimaria. I can't really consider an admonishment in the same breath is a site-ban which appears to be very much on the table, or an infobox-ban which is still a very serious remedy. You'll note that I mentioned several projects above. You might also note that many of the same editors frequent those projects. Whether you draw a conclusion from that is your own affair. Plenty of evidence has been adduced of intractable, uncollegial behavior on the part of other editors which has gone unremarked. Gerda Arendt has raised these issues repeatedly on this talk page and on some arbitrators' talk pages, and has been rewarded by a renewed effort to sanction her (remedy 3.3). Principle #6, concerning ownership, is failing, though I note you haven't taken a position on it. The effect of this decision is to endorse one side of the argument by sanctioning the other. If that's unintended then maybe the decision should be redrafted. All I'm trying to do at this point is limit the effect of this decision to the areas of the project that are actually disputed. I think, however, that I'm wasting everyone's time. You can't see what you don't want to see. Just remember that in your evidence for Andy's disruptive behavior you link to a page where he's the subject of multiple personal attacks. If you're still wondering why many of us are appalled by the direction this arbitration took, that may be your starting point. Best, Mackensen (talk) 12:57, 2 September 2013 (UTC)
  • I should also say that the wording points here should apply to any other topic ban remedies, as appropriate. Johnbod ( talk) 12:11, 3 September 2013 (UTC)

Pronouns

In the finding of fact, Gerda Arendt is referred to using "she". But in the proposed remedies, "they" is used. It sounds a bit silly when read as a whole. Could this please be made consistent? — This, that and the other (talk) 07:26, 2 September 2013 (UTC)

The pronoun concerns me less than the "remedies". The "wider than classical music evidence" is dated. At the moment I am on a voluntary 1RR rule, walk away if an infobox is reverted. I have never added an infobox to a classical music bio other than one I wrote myself, and try to find out in which areas precisely I should avoid to serve the reader by an infobox (see above). - I see that there is a battle but my goal is peace. I respect the personal wishes of editors if I know them. How can we define the "territories" to avoid unintended battle? -- Gerda Arendt ( talk) 07:40, 2 September 2013 (UTC)
  • In the context: Did you know ... that Ben Gunn, imprisoned 32 years for killing a friend when he was 14, earned a Master of Arts degree in peace and reconciliation? (now on the Main page). -- Gerda Arendt ( talk) 08:21, 2 September 2013 (UTC)
  • I left the two most controversial projects, opera and classical music. -- Gerda Arendt ( talk) 11:41, 2 September 2013 (UTC)

Comment by BrownHairedGirl

This is also a comment rather than evidence, and I hope it is acceptable to use the page in this way. Please tell me if it isn't.

I share Kosboot's view that the root of the problem lies is structural, and that is what I want to comment on. (I have had good and bad experiences of parties on both sides of the dispute, and have nothing to add about individual conduct.).

This dispute is one of several areas where there is tendency for a structural clash between 2 sets of parties:

  • some wikiprojects which have a strongly normative culture, which they seek to apply to all topics within their scope
  • editors who work on more technical aspects of the project, such as navigational boxes, categories, succession boxes, or infoboxes. (Similar, tho slightly different issues, have also arisen with some bot owners)

Unsurprisingly, clashes have also occurred with other forms of metadata such as co-ordinates, categories, and navigational templates. Disagreements over the use of co-ordinates have rarely been long-lived, and those over categories and navboxes also tend to be resolved without prolonged drama because in each there is a structured process for achieving a consensus: WP:TFD and WP:CFD, with appeal to WP:DRV. Similarly, there are processes for reviewing and constraining the authorisation and uses of bots, such as WP:BRFA ... and in all cases, the centralised and structured decision-making has allowed a body of precedent to be accumulated, which helps to stabilise consensus.

No such structured process exists for achieving a consensus on infoboxes, which has left the various parties to rehash their fundamental disagreements on the non-prescriptive MOS:INFOBOX. The result is sometimes a cold war and sometimes a war of attrition. Regardless of any action which might be taken wrt individual misconduct, the structural clash will continue.

Others have pointed to the ambiguous status of Wikiprojects. Theoretically, they are vehicles for collaboration; but in practice they assume some degree of WP:OWNership over their subject areas. The community is fluid in how much ownership it accepts, and the unresolved boundaries of both scope and ownership make them an impractical vehicle for deciding on the use of infoboxes. (Some topics may be core articles for 2 or more projects.)

One possible solution is to adopt a rigid global policy on infoboxes, to end the individual disputes. However, the community usually rejects rigid rules.

I see two other solutions, which may be implemented separately or together.

Community solution
Create a central forum for discussing the inclusion of an infobox on an article (possibly Wikipedia:Infoboxes for discussion). That would help the wider community to join in infobox discussions, broadening participation between the two most involved camps (i.e. the infobox specialists and the Wikiprojects)
Technical solution
Modify the mediawiki software to allow readers to set their preferences to enable or disable the display of infoboxes. A community decision would be needed on the default display setting, but giving readers a choice would help defuse some of the tension. -- BrownHairedGirl (talk) • ( contribs) 15:39, 2 September 2013 (UTC)
Versions of the "community solution" are discussed above, in this and other sections. I doubt the "technical solution" will please infobox-sceptics as we know the awareness & take-up will be miniscule. Johnbod ( talk) 16:18, 2 September 2013 (UTC)
A community discussion to determine whether WikiProjects should be purely a collaborative venue or have power to dictate rules across article categories might not be a bad idea either. Equazcion (talk) 16:26, 2 Sep 2013 (UTC)
There are a lot of interesting ideas and possible solutions mooted here; however nothing is going to be solved happily and collegiatly while Andy Mabbitt is on the loose. Too many of us have been there with him too many times. For as long as he is allowed to run rampantly and arrogantly through the infobox subject nothing will ever be happily resolved. He has made himself a red rag to too many bulls/cows  Giano  19:09, 2 September 2013 (UTC)
I disagree there, Giano. I see plenty of evidence that many users, including Andy, can grow and change. I do think that sometimes when people who have clashed in the past run into each other, they may be more prone to revert to old patterns, but it's important to look at the user's overall growth. A ban on Andy won't solve the real problem here, which are some other editors who WP:OWN the classical music projects and run off anyone who dares to question their authoritah. I think that's the tragedy here. (Note the action of Gerda, above, and also Ched, who has quit WP altogether because of all this) — Preceding unsigned comment added by Montanabw ( talkcontribs) 21:07, 2 September 2013‎
Smerus has left Wikipedia as well. – Voceditenore ( talk) 21:18, 2 September 2013 (UTC)
There is no evidence at all that Andy can change or is even, indeed, willing to change. It's sad, but he has to be removed fron the subject/project - there is no alternative.  Giano  21:15, 2 September 2013 (UTC)

AGK: Request for evidence relating to Kleinzach and Smerus

was posted here and includes sub sections: [133] ( olive ( talk) 17:01, 2 September 2013 (UTC))

The drafter looked at that evidence. He found the Smerus evidence persuasive, and proposed an appropriate finding (which was followed by my remedy). The Kleinzach evidence was not so persuasive, but the point is that all the anti-infoboxer submissions were dealt with and there are none outstanding. AGK [•] 21:10, 2 September 2013 (UTC)
I was confused by, "little or no evidence" in your statement and assumed the previously posted evidence had been missed. No comment one way or the other was meant which is different discussion.( olive ( talk) 21:56, 2 September 2013 (UTC))

Joseph Priestley article and Infoboxes

I am not sure what else to do with this information, so I am posting it here.

The article on Joseph Priestley is a FA and has no infobox. In June 2007, as a group of editors were improving it with an eye to FAC, the infobox was removed after a talk page discussion, and discussed again later that month. The lack of an infobox was raised next in its October 2007 WP Biography peer review, and none of the 5 editors commenting there were in favor of a box. No mention was made of infoboxes in the GA review, in October 2007 a box was added, then removed and discussed - for both see here. Inoboxes were not mentioned in its Scientific peer review or FAC.

In 2009 there was an extensive discussion and RfC on both the alignment of the lead image (it used to be left aligned, until the MOS changed) and the lack of an infobox - here. The RfC closed with no consensus to add a box, and although the MOS change meant the image became right aligned), from Oct. to Dec. 2011, there was a discussion that again came to the consensus that no infobox was required, at least at that time.

Earlier today, User:Pigsonthewing made a series of edits to the article, some of which added an infobox with edit summaries including "Template" and "ce" and "("( diff). I reverted citing WP:BRD and previous consensus against a box ( diff). I opened a discussion on the article's talk page here where we each commented briefly and Pigsonthewing said he was done with the infobox. Ruhrfisch ><>°° 22:31, 2 September 2013 (UTC)

Questions for arbitrators only

Please could the arbitrators (and please only arbitrators) answer the following questions in as succinct manner as they can manage. Having re-read all their comments on the decision page I still do not understand why this decision is as it is:

  1. How will banning Andy improve the encyclopaedia, taking into account all his contributions?
  2. Why do you think that this decision will not lead to ownership of articles by the Classical Music and related wikiprojects, contrary to the opinions expressed on this page by (almost?) everyone not involved with those projects?
  3. Why have you chosen not to make any mention of the personal attacks against Andy presented in evidence and on this page?
  4. Why do you think that this proposed decision has generated so much opposition relative to almost every other? The Tea Party case is the only comparable one I am aware of, and that was in the Committee's own words an extraordinary proposal).

These are not flippant questions, and I would like answers please from all the arbs active on this case before it closes. I am normally very supportive of the committee but I am genuinely struggling to understand how you came to a proposed decision that is so seriously out of line with the evidence as most uninvolved commenters here read the case. Thryduulf ( talk) 14:57, 3 September 2013 (UTC)

@ David Fuchs, Salvio giuliano, SilkTork, Carcharoth, and NuclearWarfare:,@ Timotheus Canens, AGK, Newyorkbrad, and Roger Davies: Please would you have the decency to respond to direct questions. Thryduulf ( talk) 00:54, 6 September 2013 (UTC)
Ah, I missed this earlier (I remember reading it, but replying to your questions slipped my mind). First, a word on responsiveness of arbitrators. Contrary to popular belief, it is not the norm for all 15 (currently 13, and only 11 on this case) active arbitrators to respond to direct questions aimed at the committee as a whole. If all 15 arbitrators participated in every such set of questions (and you and others replied to all that was said), we would be here a very long time. Until a proper moderated way to have discussions without them running out of control is available, that will always be the case (this is, incidentally, one of the reasons for the 'comment only in your own sections and avoid threaded discussions' set-up at WP:RFAR). Having said that, the talk pages of a proposed decision is a place for threaded discussion, and some responses are warranted. I will do my best to answer your questions.
  • (1) Andy is not being banned. But if anyone is banned during a case it is usually to prevent disruption caused by that editor's presence, or that editor's actions, regardless of their levels of contributions.
  • (2) I supported the principle referencing WP:OWN that did not pass, but I can understand the reasons given in the comments by my colleagues that opposed it. Editing is often a balancing act between (i) editors that range widely across articles in many different topics who may (or may not) have extensive knowledge of a specific topic area; and (ii) editors that focus on narrower topics or areas (sometimes only one article) and build up that area or article. This can lead to tensions if both types of editors (and I know many editors do both sorts of editing) clash over some aspect of article editing. The key is to be able to discuss things productively when that happens, and respect each other as fellow editors, rather than end up in circular and endlessly repeating arguments that reduce the productivity of all editors that end up involved in such disputes.
  • (3) No comment. I will leave that for the drafters of the case to answer if they choose to do so.
  • (4) This case has not really generated more debate than other cases. You need to look back to earlier in the year and to 2012 and 2011 to compare with cases back then.
I hope this helps, Thryduulf. Apologies for not replying earlier. Carcharoth ( talk) 01:23, 6 September 2013 (UTC)
I agree with what Carcharoth said. 3 cont) I didn't draft this case and there is only so much time I could spend on it. NW ( Talk) 02:34, 6 September 2013 (UTC)
A subject that comes up time and time again at arbitration is the "worth" of contributors--namely, the rationale that X editor, having broken Y policies or guidelines, should receive "less punishment" because of the good work they do in various areas.
I don't subscribe to that idea.
If an editor is disruptive, and preventing other editors from contributing effectively, then they should be addressed. Anything else becomes a bizarre game of editing worth. Let's engage in a thought experiment: who is worth more as an editor, Pigsonthewing or me. Andy has roughly three times as many edits. He has more mainspace edits than me. Does that make him worth more? I have more featured articles, more substantial edit\ to a smaller core of articles. Is that better than editing tens of thousands of articles like Andy? Or is my quality outweighed by quantity of smaller fixes, typos, and formatting? A lot of my featured articles are on pop culture topics, so are they worth less than a classical composer? If so, how many FA video games articles would it take to make a Wagner? A Liszt? A Mozart? What's the exchange rate on template edits to meaningful content additions? To vandalism cleanup? To admin backlog tasks? What about factoring in yourself, Thryduulf? Have your 43 edits to Spain, the most you've sunk into any article, been worth less than what I've done, or what Andy has done? Is true "editing worth" the proportion of article edits to non-articlespace edits, in which case you would be found wanting?
I hope this exercise conveys my point: there's no agreeable metric to decide when an editor's worth is greater, or less, than the trouble or disruption they cause.
We are all volunteers, and (despite biological or emotional ages) Wikipedia's principles are set up so that we are all treated as equals and adults. As an arbitrator, I often try and focus on minimizing fuss and trying to get quality edits out of editors without causing trouble; if a banned user appeals, I'm more inclined to try and suggest a topic ban from problematic areas than throw away the key. But there is a point where no amount of gamesmanship can thread the eye of the needle, that perfect sweet spot of disruption-free quality contributions. And so one has to make the call about whether cutting off some good contributions to avoid the bad is worth it. That threshold may often be higher for quality contributors and long-term editors, simply because there are more fields they partake in, more topics they edit, more namespaces they benefit. However that threshold is, fundamentally, an issue every arbitration case grapples with in its remedies.
As for your mentions of "seriously out of line" and estimation of whatever you could possibly term "popular opinion", I think we will have to disagree on your interpretation. Der Wohltemperierte Fuchs( talk) 03:39, 6 September 2013 (UTC)

My answers to the questions above:

  1. I did not vote to ban Pigsonthewing, precisely because I concluded that the drawbacks to doing so outweighed the benefits. That being said, I think there is wide agreement that aspects of his behavior have been problematic and need to change.
  2. One of the issues to be addressed in the hoped-for community discussion, I believe (and have indicated on the decision page) is the degree of deference due, in deciding whether an infobox is useful in a given article, to the users most familiar with the article or the subject-matter. I expect the conclusion will be that their input is relevant but not necessarily dispositive. The reasons that contributors to a given article or members of a wikiproject believe inboxes are unsuited to the articles in that area also bear consideration. Sometimes those reasons might be convincing to other editors, and sometimes they might not.
  3. Not every instance of poor or debatable conduct presented in evidence needs to be or can be included in the final decision; the drafters, and other arbitrators who add to the draft, wind up prioritizing in every case. Although the drafters may speak for themselves, presumably they concluded that this was not an area that required focus in the decision. It remains unacceptable for any editor to personally attack any other, although not every instance of doing so can or will result in a sanction.
  4. I agree with Carcharoth's response to the last question. Sorry these responses were delayed. Newyorkbrad ( talk) 16:29, 6 September 2013 (UTC)

Thank you to those who answered, I haven't got time now to read all your answers but I would like to appologise for my tone earlier - a good example of when I should have previewed and then not saved. Thryduulf ( talk) 21:59, 6 September 2013 (UTC)

Principle 3.1.5 Mission

I am concerned that the Arbcom appears to advance a view on content in principle 3.1.5 Mission: "Wikipedia's mission is to build an encyclopedia that can be modified and distributed freely. To facilitate access to this information, we should provide as few barriers to its use and dissemination as possible. Additional information, such as metadata, aligns with the goals of the encyclopedia where it is not detrimental to our content or our scope. [+emphasis]"

Whatever the perceptions of my opinions on the matter might be, my point is that I would be equally concerned if the pronouncement in the last sentence were the opposite. The italicized portion could be used as a rhetorical weapon (or more than that) in community debate, and influence what should be unbiased discussions from the beginning. NW is perceptive in saying that " 'detrimental' would have to be able to be interpreted so widely as to make [the principle] useless". That nuance would undoubtedly be lost when this principle was taken up by a community in debate. Since any hypothetical debate would obviously examine the pros and cons, I'm not seeing the point of this statement other than to inadvertently set up a context for content debate which amounts to "The Arbcom said...". And If I'm not mistaken, the Arbcom is actively recommending in another finding that community discussion should occur on these issues. Regards, Riggr Mortis ( talk) 15:36, 3 September 2013 (UTC)

  • Support. I’ve already commented on this above, see Perspective from Kleinzach, 3. Technical issues. If metadata is a form of content, and content is outside the scope of Arbcom, then the second sentence of 3.1.5 (Mission) is mistaken. Most of recognise that we need to look at the subject of metadata much more closely. I’d hope ArbCom would encourage, not discourage, this. Can they think again? Klein zach 00:39, 4 September 2013 (UTC)
  • Support per Riggr and Kleinzach. Ruhrfisch ><>°° 01:04, 4 September 2013 (UTC)

Impressive

"Indefinitely separating an long-term dedicated editor from this project should take more than the closest possible vote of a divided committee. For this reason alone, I'm striking my support. T. Canens (talk) 00:03, 4 September 2013 (UTC)" Now that is impressive. PumpkinSky talk 01:54, 4 September 2013 (UTC)

  • Indeed!— John Cline ( talk) 02:20, 4 September 2013 (UTC)
  • Gonna pile on my kudos too. I'm completely unfamiliar with Pigsonthewing's history so I can't say if his banning would've been a good or bad thing. Either way this is a refreshingly wise statement. Equazcion (talk) 03:18, 4 Sep 2013 (UTC)
  • I also am pleased and impressed to see this expression of wisdom. -- Orlady ( talk) 03:24, 4 September 2013 (UTC)
  • Yes, we elect the Arbs to make the hard abstentions for us. I especially like the last minute bait-and-switch, so no one realizes what a bizarre decision this now is. As it currently stands, Arbcom has voted to...
    • ...admonish Nikkimaria for edit warring with Pigsonthewing, but not to admonish Pigsonthewing for edit warring.
    • ...indefinitely restrict Gerda Arendt from restoring an infobox that has been deleted, but not to restrict Pigsonthewing in this way.
    • ...admonish Gerda Arendt for treating Wikipedia as if it were a battleground and advise her to better conduct herself, but not to admonish Pigsonthewing or advise him in any way.
    • ...remind Smerus to conduct himself in a civil manner, but not to remind Pigsonthewing how to conduct himself.
  • What exactly do you find impressive about this again? Ruhrfisch ><>°° 03:35, 4 September 2013 (UTC)
    • The decision to indefinitely ban Pigsonthewing from adding or discussing the addition or removal of infoboxes seems to have passed though. I think that covers the restrictions others got, and maybe covers admonishment as well; though perhaps an explicit admonishment should also be proposed for Pigsonthewing, seeing as the site ban is defeated -- I don't have an opinion on whether he should be admonished, but it looks like something that could pass. What is impressive, Ruhrfisch, is T. Canens lone act, even if fault can be found in the way the totality of the case stands at the moment. Equazcion (talk) 04:21, 4 Sep 2013 (UTC)
      Exactly; and the stuff you didn't say too!— John Cline ( talk) 04:31, 4 September 2013 (UTC)
  • Mabbitt be site banned, for breaking his restrictions, in a few weeks or months just as surely as evening follows day. The Arbs know this, but the current passing motion allows them not to appear too Draconian.  Giano  07:12, 4 September 2013 (UTC)
  • Impressed and relieved. Everybody who knows me a bit knows that "battleground" is kafkaesque, but I couldn't care less about "imposed" restrictions. I learned, not only this new word. (You don't add the unspeakable thing, you impose it, I didn't know that.) - For clarity: "care less" means 1) I was not worried at all about myself, 2) I am not worried about sticking to restrictions as I left the conflict areas - classical music and opera - already.
@Equazcion: from Andy's recent history: Ben Gunn and "Let us not forget that even one book, one pen, one teacher can change the world". I am happy that more of that can come.
@Giano: Everybody afraid can simply watch his edits and revert, it's so easy.
A hymn is in order. -- Gerda Arendt ( talk) 07:25, 4 September 2013 (UTC)
Dearest Gerda, it appears that someone may have used our differences in language to play a cruel joke on you—indicative of child's play. There is actually no relationship with your manner of editing and the verb form of impose—yet somehow you've used it in correct context with "restrictions". I'm impressed again.— John Cline ( talk) 08:35, 4 September 2013 (UTC)
  • T. Canens's action is certainly a good thing, and I thank him for it. However it shouldn't be regarded as impressive for an arb to take such action - doing it shouldn't be needed in the first place, but if it is it should be normal. Thryduulf ( talk) 09:18, 4 September 2013 (UTC)
  • My take (short version): bullet unbitten, inevitable postponed. This pulled punch is only going to work if you have the stamina to enforce it properly. -- Folantin ( talk) 12:10, 4 September 2013 (UTC)

Already a dead letter?

This morning Gerda Arendt has gone straight ahead and added yet another infobox to a Bach article [134]. As far as I can see, this is not a page she herself created. I don't see how this is stepping away and disengaging from the infobox furore. -- Folantin ( talk) 10:22, 4 September 2013 (UTC)

It's a cantata where I am the main contributor, as for most Bach cantatas. I created about half of them, expanded several others from a stub. With some 150 articles in question, I didn't improve all at the same time, but since December routinely add an infobox for the cantatas of the upcoming Sunday. - For consistent style to the reader, I would prefer if all looked the same, but I respect other editors ( BWV 105) and the cleanup of editors who are no contributors ( BWV 71), as now also the one you mention ( BWV 51), - I will not fight it, but does it make sense? -- Gerda Arendt ( talk) 10:45, 4 September 2013 (UTC)
Doesn't seem consistent with: "Gerda Arendt is indefinitely restricted from: adding or deleting infoboxes; restoring an infobox that has been deleted; or making more than two comments in discussing the inclusion or exclusion of an infobox on a given article. They may participate in wider policy discussions regarding infoboxes with no restriction, and include infoboxes in new articles which they create." -- Folantin ( talk) 10:48, 4 September 2013 (UTC)
Nor is yours ↑ consistent with "All editors are reminded to maintain decorum and civility when engaged in discussions about infoboxes, and to avoid turning discussions about a single article's infobox into a discussion about infoboxes in general.", nor Bencherlite's below ↓.— John Cline ( talk) 11:14, 4 September 2013 (UTC)
(after several edit conflicts) You are right. - Perhaps that "letter" can change, to make more sense? How about templates such as {{ infobox Bach composition}}, that were developed within the project and are not contentious? -- Gerda Arendt ( talk) 11:08, 4 September 2013 (UTC)
Gerda is obviously trying to get as many infoboxes in as possible before the restrictions start, despite her empty words to me this morning: "I left projects classical music and opera, the areas of conflict. If I added an infobox you could simply revert it, and now I will not even add one." Clearly she and I have a different view on how many infoboxes make "one". Bencherlite Talk 10:54, 4 September 2013 (UTC)
What seems obvious to you, isn't true. It's a routine since December, I do three a week, normally on Mondays, as you can see in my contribs, - this week I was held up. I don't only add an infobox, but also update them, improve wording, format references and add the lang-template to articles for which I feel responsible. -- Gerda Arendt ( talk) 11:08, 4 September 2013 (UTC)
( edit conflict) She may not have "created" the page (again: is that a criteria? Under what policy?) but she is a major contributor to it, having first contributed in 2010. Indeed, she has added more volume of content to it than the colleague who did create it, and who has not edited it since the day they did so, in September 2005. I note that Eusebeus has removed the infobox, with the edit summary "rm info box pending determination for consensus via talk", but started no such discussion on the talk page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:59, 4 September 2013 (UTC)
( edit conflict)×3 :I note that the addition was reverted by user:Eusebeus with the summary "rm info box pending determination for consensus via talk." but the only comments on the talk page are from 2011 and no attempt has been made to explain why the infobox might not be beneficial to this article. This is important because, to summarise and generalise RexxS' comments, the benefits of infoboxes are generally the same for every article accross the project but the downsides are not, and so they need to be expressed and weighed up on an individual article - sometimes they exceed the benefits and sometimes they don't, but you can't evaluate that without knowing what they are.
While she didn't create the article, the revision history statistics show Gerda is the most frequent contributor to the article by some way (38 edits, one editor has 7 and no others have more than 3). Although she is about 10th by average edit size, she has added a lot of information to the article (including referencing it), so it is in no way fair to say that she is not one of the principle editors. From memory (and I haven't double checked this) Bach compositions are cited in evidence as articles where additions of infoboxes have been uncontroversial in the past (in the context of it being impossible to know in advance where they will be controversial).
So what we have here is one of the principle contributors to an article adding an infobox to it, and being reverted by someone making their first edit to the article without discussing why. Which is the exact opposite of what we are told always happens by those not wanting infoboxes. Thryduulf ( talk) 11:06, 4 September 2013 (UTC)
I was quoting this proposed restriction: "Gerda Arendt is indefinitely restricted from: adding or deleting infoboxes... [she may] include infoboxes in new articles which [she] create[s]."
It's funny to see Andy Mabbett now stressing that the opinions of the principal content contributor should be given the most weight. Had he actually espoused this principle before, we might have been spared all the endless wrangling over Cosima Wagner or The Rite of Spring, to take just two examples. It's even possible that this very Arb Case need never have arisen. -- Folantin ( talk) 11:16, 4 September 2013 (UTC)
That's actually not what is being suggested at all. Andy (and I) are simply saying that you can't have it both ways - if you insist that the views of the principle contributor are respected when they don't want an infobox then you have no leg to stand on when views of a principle contributor who adds an infobox are not respected. Thryduulf ( talk) 11:23, 4 September 2013 (UTC)
That's not what Andy's saying. See below. I would have no problem giving weight to the opinion of the creator/primary contributor (assuming it was in line with our core content policies). -- Folantin ( talk) 11:51, 4 September 2013 (UTC)
Yes, that is what I'm saying. While the basis of your position is false, it's still being applied hypocritically. And we do have a core content policy which precludes giving additional weight to one editor or group of editors: WP:OWN. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:35, 4 September 2013 (UTC)
( edit conflict) It's funny to see Andy Mabbett now stressing that the opinions of the principal content contributor should be given the most weight. - That would indeed be "funny", and not in the humorous sense. I didn't say that, nor do I think it, so please don't attempt to put words in my mouth. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:27, 4 September 2013 (UTC)
I think those referring to principle editors above are doing so in the context of interpreting the proposed decision on this page, as in, what might constitute an article that Gerda "created" (rather than the more general principle that anti-infobox editors tend to reference). I have to say though I don't think the allowance that Gerda can "include infoboxes in new articles which they create" is served by her adding an infobox to an article she did not create, and is not new. The case hasn't concluded yet but those likely facing infobox restrictions might be wise to keep a distance from individual article infobox issues at the moment. Just my take. Equazcion (talk) 11:30, 4 Sep 2013 (UTC)
Warum betrübst du dich, mein Herz
BWV 138
church cantata by J. S. Bach
Relatedmovement 5 base for Missa, BWV 236
Occasion15th Sunday after Trinity
Cantata textanonymous
Choraleby anonymous, formerly attributed to Hans Sachs
Performed5 September 1723 (1723-09-05): Leipzig
Movements7
Vocal SATB solo and choir
Instrumental
You are right, but
  • if we go strictly by the letter the restriction is not in place yet
  • in the light of this discussion, perhaps the restriction can be worded differently?
  • the articles in question are not "individual articles" but a series in which most articles have infoboxes
  • for these articles there is no author whose feelings are hurt
  • the topic is not contentious
  • the parameters are not contentious
I ask our esteemed arbitrators for a solution, perhaps with our readers in mind, - hopefully before Sunday. Until then, I will not add to Warum betrübst du dich, mein Herz, BWV 138 (Why do you trouble yourself, my heart), -- Gerda Arendt ( talk) 11:48, 4 September 2013 (UTC)
I have to doubt that the arbitrators will think it beneficial to make the restriction contingent on how contentious a particular situation is/whether or not you're a principle contributor/whether or not an article series has an established form. Those would add layers of ambiguity and interpretation ripe for fighting over later. The choice of words ("new" and "create") was likely intentional as it is less likely to produce conflicting interpretations. Equazcion (talk) 12:10, 4 Sep 2013 (UTC)
Gerda, infoboxes on classical music articles are somewhat contentious. I think everyone following this case has realised that by now. -- Folantin ( talk) 12:15, 4 September 2013 (UTC)
I show the missing infobox which will hopefully make it to the article until Sunday, better tomorrow because the premiere was 5 September. Folantin, the template {{ infobox Bach composition}} has been discussed first on the project talk, further on the template talk. There is also {{ infobox orchestra}}, initiated by Kleinzach, - your generalisation "infoboxes on classical music articles are somewhat contentious" is not quite to the point. It's more some classical music authors, who - not wanting infoboxes in biographies - extend this dislike to compositions. -- Gerda Arendt ( talk) 12:34, 4 September 2013 (UTC)
Gerda, I don't think what this case needs is yet another infobox discussion. Please. -- Folantin ( talk) 12:49, 4 September 2013 (UTC)
It isn't. It is a discussion about how to supply our readers with unrestricted information, for example by a different wording. -- Gerda Arendt ( talk) 12:52, 4 September 2013 (UTC)
Remember, in the workshop I tried to find a way to reach consensus. In this case I don't even see a conflict, author wants infobox, no former author objects, why not then? Whom would a restriction serve in such a case? -- Gerda Arendt ( talk) 13:28, 4 September 2013 (UTC)
Please compare GA BWV 103, GA review by Smerus with whom I liked to work and hope to do it again, -- Gerda Arendt ( talk) 14:42, 4 September 2013 (UTC)

New day: I found messages on my talk which made me reply, thoughts also for this context:

  • I would love to eventually not talk about infoboxes for individual articles, but groups of them, for example orchestras and Bach cantatas, two topics where I don't see the slightest conflict.
  • All French, Norsk and German Wikipedia Bach cantatas have an infobox, the German derived from our English example.
  • Infoboxes in Bach cantatas (template developed and usage established with help from Kleinzach, Voceditenore and Nikkimaria) help the reader understand at a glance that the long German title, followed by a translation and a catalogue number, is a work by Bach; they provide year/date and location, let him know the sources of the hybrid text (typically three different sources) and the voice parts and instrumental scoring?
  • Regardless of how good or bad the article is, and by whom, these are facts important for a reader. Please let him have them at least for articles for which I feel responsible, - accepting that it is impossible at present for the several that Nikkimaria wrote. How can we get reverted infobox of BWV 51 and the one proposed for BWV 138 here to the respective article? -- Gerda Arendt ( talk) 11:30, 5 September 2013 (UTC)

Mabbett and infoboxes

I was trying to stay away from this subject as it annoys me intensely and the whole brouhaha that surrounds the discussions generate far too much heat and little in the way of light. I do feel uncomfortable with the wording restricting POTW's remedy 1.1 (currently passing): ("Pigsonthewing is indefinitely banned from adding or discussing the addition or removal of infoboxes.") While I support the spirit of this proposal, it does mean that even if POTW starts a new article from scratch, he is unable to add an infobox. This seems to be an unwanted aspect to the proposal and I advocate a minor tweak to allow him to add an infobox at article creation stage:

"Pigsonthewing is indefinitely banned from adding or discussing the addition or removal of infoboxes: he may include infoboxes in new articles which he creates."

SchroCat ( talk) 11:29, 4 September 2013 (UTC)

If we're going down that road (and I agree with your comments about the existing proposed restriction, and it exist also for Smerus' proposed restriction) then using the same language as used for Gerda would be good for consistency. But please per my comments elsewhere on this page, drop the maximum two comments language from all of them, it will just make things worse. Thryduulf ( talk) 11:47, 4 September 2013 (UTC)
Please see #Infoboxes and new articles and #Proposed remedy 1.1, above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:44, 4 September 2013 (UTC)
I see Courcelles has taken the step (although using the awful singular they). Many thanks Courcelles. - SchroCat ( talk) 14:33, 4 September 2013 (UTC)
That does not address the points raised in #Infoboxes and new articles and #Proposed remedy 1.1. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:47, 4 September 2013 (UTC)

RfC

per the committee recommendation I started a page at Wikipedia:WikiProject Infoboxes/2013 RfC draft. Play nice. — Ched ZILLA 08:55, 5 September 2013 (UTC)

I hope this isn't some kind of joke. Any community discussions that are set up following this ArbCom should be done by established, respected editors who are willing to do the necessary detailed drafting. Editors who have taken a moderate position on the controversy will be best suited to this job. It shouldn't be undertaken lightly. Klein zach 09:41, 5 September 2013 (UTC)
Chedzilla is an alternate account of User:Ched, who requested this arbitration case and had previously started User:Ched/RfC - Infobox. Despite the comments on User talk:Ched, he has not left Wikipedia. Voceditenore ( talk) 10:17, 5 September 2013 (UTC)
I've removed the WP:OWN mention on the page and put it into more neutral language: there was no finding of ownership in the decision, so I'm not sure why the RfC decided to lead with it. - SchroCat ( talk) 09:56, 5 September 2013 (UTC)
I think there is much that is useful and possibly helpful at User:Geogre/Templates and suggest all interested parties read it for ideas. Ruhrfisch ><>°° 10:18, 5 September 2013 (UTC)

I completely agree with Kleinzach and with the comments made by Carcharoth and Johnuniq in the sections below. This is extremely ill-advised. If an RfC is to have any chance of not becoming a complete train wreck:

  1. Before even embarking on a draft, at least three months are needed for all involved to return to normal editing, reflect both on this decision and on their own positions, gain some perspective, and drop the (understandable but counterproductive) recriminations and posturing.
  2. Not only does the drafting need to be initiated and undertaken by established, respected editors with hitherto moderate positions on the controversy (preferably no one who has given evidence in this case nor any of the parties, including the filing party), they must also be willing to put in the considerable time necessary to create a detailed and thoughtful draft.
  3. The draft and the eventual RfC should be held in a "neutral location", possibly on a sub-page of Wikipedia talk:Manual of Style/Infoboxes, but certainly not on the pages of WikiProject Infoboxes.

Voceditenore ( talk) 09:28, 6 September 2013 (UTC)

I agree with all of the above comments. Please delete this RfC "draft" before it spirals into another series of mistakes. You can't just throw a handful of stuff at a wall and hope other people turn into something useful. It didn't work with this arbcom case, why would it work with an RfC? Productive RfCs require a lot of hard work and mediation skills. Please leave it for someone who is willing to put in that effort. – Quiddity ( talk) 20:12, 6 September 2013 (UTC)

WikiBreak

In case anyone has a question for me, please note that I am facilitating two conferences over the next five days; so shall have limited and unpredictable opportunity to edit here until Tuesday. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:35, 5 September 2013 (UTC)

Thanks very much for letting us know. If any developments require your input, we will try to hold them off until your return on Tuesday. AGK [•] 11:55, 5 September 2013 (UTC)

The letter of the finding

We speak already of the letter of the restrictions, let me please ask a question regarding the findings about me. It reads at present:

6) Gerda Arendt ... has added infoboxes to many articles systematically, and without prior discussion. including articles where she knew or should have known that adding an infobox would be controversial.

Gerda, this is about the fifth time you've said you were "following the advice of Brad". Can you actually point to where he gave you this alleged advice? NYB would be the first to admit that he has virtually no content-writing, page layout or template markup experience, and as far as I'm aware the only time he ever discussed infoboxes was this comment, in a private discussion with me on my talkpage about how to head off this very RFAR—not any kind of policy debate—in which he specifically prefaced his suggestion with a note that doing this would "probably please noone". –  iridescent 20:40, 5 September 2013 (UTC)
He didn't give me the advice. The link to where he gave it is above, Brad on Boxes. I met it in a list, trying to find solutions for infobox controversies, added there by Nikkimaria, which is linked in my entry "No infobox" (link above), repeated once more. I thought it was a good idea and tried it, without digging into the context where it was mentioned. I wish now I had not. -- Gerda Arendt ( talk) 22:00, 5 September 2013 (UTC)
Reading NYB's full comment, it seems in saying it "would probably please no one", that Brad was merely presenting the definition of the word "compromise", not recommending against the measure. He was presenting talk page-hosted infoboxes as something that both parties might at least tolerate even though neither got their way entirely. That's what compromises generally are. Equazcion (talk) 21:33, 5 Sep 2013 (UTC)

Advice on post-case discussions

The case is close to closing now. Feelings have been running high. My advice to the parties and all those who participated is to step back for a bit and find something else to do. Way up above, Brianboulton said: "My recent Dispatches article was a contribution to that discussion. However, very few positive steps will be taken in the atmosphere of antagonism and mutual annoyance that envelops this whole topic. [...] we all have better and more productive things we should be doing." My suggestion, for those who want to sort through their thoughts on this while they are still fresh, would be for people to make notes or mini-essays offline or in their userspace, and to leave articles and talk page discussions well alone for a bit (or for longer if someone is restricted). Don't rush into post-case discussions, but let things calm down, and find other things to do in the meantime. It's not like the issues are going to go away (the essay by Geogre that someone posted above is from seven years ago). Carcharoth ( talk) 22:55, 5 September 2013 (UTC)

Questions and time

  • It's close to closing and not one of the arbitrators has seen fit to answer any my explicit questions to them, or respond to any of the comments regarding the perceived weakness of several proposed remedies (by both sides of the dispute in some cases). Those are not the actions of a committee that is interested in maintaining the respect of parties in this case. I'm honestly shocked to think that any arbitrator can read this talk page and still genuinely expect collegiate discussions about infoboxes to stem from this decision. Thryduulf ( talk) 00:49, 6 September 2013 (UTC)
    • I've answered your questions above as best I can. Could I ask you to consider putting your post above (which isn't really anything to do with post-case discussions) into a new section separate from what I said (you could title it something like 'questions need answering before case closes')? The point I was making about post-case discussions is really important, and I don't want it to get lost because you feel affronted that your questions were not answered. Carcharoth ( talk) 01:30, 6 September 2013 (UTC)
  • I agree with Carcharoth and was surprised to see the recent RfC section above which pointed to a new RfC draft. I would much prefer that the Community discussion recommended remedy state that it would be counter-productive to start an RfC discussion in under three months. There are good editors on both sides, and very strong feelings on both sides—conducting another knock-down battle at the moment is the last thing that should occur. It would be impossible to hold any discussion in the next three months that is not seen as "Arbitration part 2", and the entire case would be refought—perhaps not the entire case because variations on "editor X was disruptive" would be squelched, but everyone involved would know that this was the ultimate winner-takes-all argument, and only two outcomes would be possible: my side wins, or your side wins—in each case, a significant group of editors is made to feel even more bitter. Johnuniq ( talk) 02:58, 6 September 2013 (UTC)
Sorry - my bad, my fault. I saw the suggestion of a discussion, and not being able to be consistently active on wiki, I missed the "wait" idea. Feel free to delete. I'm doing my best to follow this through to the end, and I screwed up - sorry. Feel free to delete it, I won't object. — Ched ZILLA 04:51, 6 September 2013 (UTC)

Mercy

Smerus retired. I would like to see no actions against him, for decency. (I had no problem with his arguing, minded only one phrase. He and I were ready to keep working together. The term "battleground" is a myth, if you ask me.) I don't know if the rules would permit that.

  1. -- Gerda Arendt ( talk) 10:12, 6 September 2013 (UTC)
  2. Quiddity ( talk) 20:24, 6 September 2013 (UTC)
I'd actually be in favor of reversing the sanctions against Smerus, but not out of mercy. The quoted evidence just seems rather thin for imposing restrictions: [135] [136] [137]. The third diff is really the only example of unacceptable behavior that I'm seeing. The other two seem at most like impatient words in a heated exchange, as is par for the course on Wikipedia. I've seen people get away with far worse both in cases that did and did not end up at arbitration. Unless there's something I'm missing (which is entirely possible as I've not done any digging beyond reading those three diffs), I'm inclined to ask the arbitrators to rethink this or at least explain their votes a little more than they have. Equazcion (talk) 13:54, 6 Sep 2013 (UTC)
I'm sad that I never managed to successfully communicate to Andy that he has to acknowledge the perspectives of others when they have legitimate subjective objections (I still think that would've solved almost everything, in this and previous heated-discussions). Acknowledging the diverse perspectives and problems, cannot be undervalued, as a part of resolving team-disputes.
However, I'm also frustrated that any other editors seem to be getting more than an admonishment - restricting gerda or smerus from infoboxes completely isn't a good solution - they just need to be given a better structure to work within - ie. better infobox guidelines. They're both willing to admit mistakes and move towards compromise/consensus positions and templates, when not backed into a corner. These two split decisions, that are leading to one retirement and widespread frustration, could be usefully re-examined. – Quiddity ( talk) 20:24, 6 September 2013 (UTC)
Quiddity, the problem is that we lack the authority to unilaterally create better infobox guidelines. We may suggest or even urge the community to discuss the issue and come up with a new solution, but, right now, we have to apply the policies as currently written, even if we were to consider them unwise. Salvio Let's talk about it! 20:59, 6 September 2013 (UTC)
Salvio, I suppose I was thinking of this as the rationale/answer: "We're going to admonish editors x and y, but not restrict them, because they are currently working based on fundamentally [flawed/ambiguous/lacking/inadequate] guidelines and MoS pages. We will try to assist the community in its search for a suitable individual to help put together an RfC aimed towards improving these areas of documentation, in an effort to move this forward in the normal community process, but in as well-researched and balanced a manner as possible." (Note: That's not meant to be in the standard-legalese; my wording is flawed; I'm just trying to get across the general idea. :) – Quiddity ( talk) 00:30, 7 September 2013 (UTC)
Quiddity, I like your proposal as an alternative to restricting Gerda and Smerus (but not Andy, whom I still think needs to be site banned, but that's neither here nor there); and I have mentioned it on the mailing list. Let's see if any of my colleagues agree. Salvio Let's talk about it! 12:32, 7 September 2013 (UTC)
What has always been a problem and is becoming more so here and around Wikipedia is loss of understanding of what a community is. We are so intrenched in a punitive mind set that we do not have the vision or skills to work through problems that have arisen in a group, that depend on collaboration rather than separation. Our arb committee, not their fault and in good part because of what the community is clamoring for may be stuck in an outdated model. Problems will always arise when people are working together. Even as editors here are working out their problems, find solutions, and this is the real outcome of this arbitration, sadly the sanctions stay in place. Something rather important has happened here due in good part to Gerda's open heartedness and ability to work things out with people. A strategy that supports community growth has occurred, if only we could see it.( olive ( talk) 21:22, 6 September 2013 (UTC))
Understandably, people view arbcom decisions as "punishments". But another way of looking at all this is that the protagonists have been given an "opportunity" by the arbitrators to step back from the trajectory they were all caught in—instead of plowing ahead with disputes in article after article and becoming more and more frustrated with each other. I'm not sure it was an opportunity they would have chosen themselves before these proceedings began—in fact six more infobox discussions were initiated on article talk pages by the parties involved here during these proceedings: [138], [139], [140], [141], [142], [143]. In any case, people now have the space to reflect and to break the cycle. I hope it will be used constructively. Voceditenore ( talk) 21:56, 6 September 2013 (UTC)
Please also see Pigsonthewing adding an infobox to Joseph Priestley with the fairly misleading edit summary "template" ( diff). I reverted it, citing WP:BRD and the previous consensus not to include an infobox ( diff). I then opened a discussion on the talk page where I linked to 4 of the 6 archives where infoboxes are discussed (there is also clear consensus against a box from late 2011 on the current talk page) here and was told by Pigsonthewing "I note that you dismiss my addition of an infobox without making any arguments against it" (which he had not even labeled as an infobox on adding it to the article).
Arbs, please read your Proposed findings of fact again. Then read the Proposed remedies. Does it really seem, based on your own findings of fact, that Smerus and Pigsonthewing deserve essentially the same remedies? I would argue that Smerus' remedy is worse - he is also "reminded" (and Gerda and Nikkimaria are admonished) while Pigsonthewing is neither admonished nor reminded. I know these are neither crimes not punishments, but if they were, would the "punishments" fit the "crimes"? Ruhrfisch ><>°° 18:56, 7 September 2013 (UTC)
what is striking me here in many of the above comments (clear up to the top of the page, is that it appears that presenting evidence in one's defense is considered a whole new "crime" rather than a defense -- supposedly sought by ArbCom -- for the previous set of actions. Does no one see how the tag team of Smerus and Kleinzach paired up to WP:BAIT Gerda in particular, but also gave aid and comfort to Nikkimaria to the point that she made some serious mistakes in stalking Gerda and Andy, and how Andy's behavior, if it was anyone other than Andy, would be deemed mildly overeager wikignoming at most? Seriously, Smerus and Kleinzach really should not scoot out of this scott-free. They DID exacerbate the situation! Montanabw (talk) 00:32, 8 September 2013 (UTC)
Montanabw - with due respect, as an outside observer, no I do not see that Smerus and Kleinzach "paired up to WP:BAIT Gerda"; rather, I see you have done your bit to do this, even as Gerda and Smerus were building bridges, by being outraged ostensibly on Gerda's behalf (though she has not invited this from anyone), accumulating evidence - most of it quite trivial - against Smerus in particular, despite Gerda's continued collegial attitude to Smerus. I notice that since Smerus has been driven away from Wikipedia, Gerda has joined the [ vote of thanks to Smerus]. Perhaps you hadn't noticed he had departed? Forgive my saying, but your actions increasingly appear to be driven by some kind of vendetta. Please prove me wrong. Alfietucker ( talk) 01:28, 8 September 2013 (UTC)
You didn't read all the diffs, then. They were requested, and submitted. As for the rest, Gerda did a good job to work with Smerus, and Nikki, and had they been left alone and not tag teamed by others at the classical music project who owned everything, they may have worked things out. But the reality is that Kleinzach, by simply refusing to respond at all, is scooting off more scott free than Smerus, and he was, if anything, the more egregious offender in the "lalalalalalala no infoboxes everevereverever" department. My only concern here was seeing how bad Gerda was being ganged up on and bullied. People showed her little good faith and were saying terribly mean things about her. I think she's a wonderful, kind, decent human being and she did not deserve any of this. Montanabw (talk) 19:12, 9 September 2013 (UTC)
Yes, I have read all the diffs (at least the ones proffered and a bit more, plus there's what I have happened to encounter in the course of working on classical music articles on Wikipedia). I'm not sure I'm convinced by your change or at least modulation of tune over Smerus, Montanabw - or at least you give no explanation of what you meant by your previous accusation that he "tag teamed" with Kleinzach. It would seem to me a more likely explanation of them often being on the same talk page is simply that they work on several of the same projects. Otherwise can't the same accusation of "tag teaming" be applied with even greater pertinence to you and Andy? It also seems disingenuous of you to now claim your main beef was against Kleinzach, when the majority of your evidence was against Smerus: furthermore, your evidence against him was both pettifogging and luridly presented ('scream(s) bloody murder'; 'describes Gerda as "an effete and loathed sissy"'; 'dripping with sarcasm'; etc.). This, frankly, does look like vengeful action rather than a dispassionate presentation of the facts. Alfietucker ( talk) 20:46, 9 September 2013 (UTC)
I should not have backed off on Kleinzach, who was the worse offender, but I only have 24 hours in a day, and because everyone was saying the poor Kleinzach wasn gone and didn't have the ability to defend himself, I backed off on him more than I should, probably. I'm not saying that I'm backing off on Smerus, only that if Gerda feels he was the lesser problem and she believes that she can work with him, I have respect for Gerda's views on the matter. Gerda is not the "offender" in any of this, my view is that if Gerda is "admonished," then those on the other side should be equally admonished for their behavior. Montanabw (talk) 22:46, 9 September 2013 (UTC)
"I'm not saying that I'm backing off on Smerus...Gerda is not the "offender" in any of this, my view is that if Gerda is "admonished," then those on the other side should be equally admonished for their behavior." Since when did two wrongs make a right? Alfietucker ( talk) 22:53, 9 September 2013 (UTC)
"[X] really should not scoot out of this scott-free. They DID exacerbate the situation! [Y]". X<Y. And while I appreciate any "aid and comfort" offered, particularly in the face of egregious personal attacks, only I am responsible for the choices I make to accept invitations and act on concerns. Nikkimaria ( talk) 04:25, 8 September 2013 (UTC)
No, Nikki, X=Y or X>Y. If you get smacked for what you did, (and I have already made my comments on that issue, I have nothing more to add there) justice demands that the punishment fit the crime and all "offenders" be appropriately approached. Smerus, Kleinzach (and possibly others) certainly contributed to the mess and you should not be carrying that alone. Scapegoating someone as the sole offender is not justice, nor appropriate, particularly when, as noted here, you and Gerda actually were working stuff out between you. I consider the others with the "lalalalalalanoinfoboxevereverever" attitude to be the far greater problem here. At most, you had a few bad days where you started stalking edits and lost your usual good judgement. They have a longstanding premeditated ownership problem. That's a much deeper concern. Montanabw (talk) 19:12, 9 September 2013 (UTC)
"your actions increasingly appear to be driven by some kind of vendetta". Driving Smerus (one of our best classical music editors) off Wikipedia is not enough. After all, Smerus and Kleinzach messed with core members of WP:QAI and must be punished. I have a strong suspicion they aren't the first to receive this kind of treatment. -- Folantin ( talk) 09:21, 8 September 2013 (UTC)
Folantin, you and I agreed to a truce on discussing one another's behavior and your QAI conspiracy theories. As we agreed, you struck some of the things you said, particularly about me, and I struck my concerns about you. So let's just keep that hatchet buried. Your stirring the pot was not calming down the situation. If you really want to crank this up again, though, be aware of the WP:BOOMERANG effect. Montanabw (talk) 19:12, 9 September 2013 (UTC)

I return to this after two days off, and again can't believe what I read above. I - a core QAI member - ask for Smerus, a colleague with whom would like to continue working and who accepted a comprise solution on Symphony No. 1 (Sibelius), to not be admonished/restricted. I had no problem with his arguing, minding only one term. Is anything not clear about this? -- Gerda Arendt ( talk) 12:22, 8 September 2013 (UTC)

I don't think Smerus should be sanctioned to any greater degree than you, Gerda. And I don't think you should be sanctioned at all. But if they are going to treat you like the villain, then the eye needs to be focused on all players equally. However, if left alone, you three would have worked things out between yourselves, but others were not going to allow the sacred ground of the classical music wikiproject local consensus to be altered and were more than willing to bully, intimidate, snark and threaten anyone who challenged the status quo. So really. Montanabw (talk) 19:12, 9 September 2013 (UTC)

Pigsonthewing and Joseph Priestley

I'd just like to highlight what Ruhrfisch wrote above: "Please also see Pigsonthewing adding an infobox to Joseph Priestley with the fairly misleading edit summary "template" ( diff). I reverted it, citing WP:BRD and the previous consensus not to include an infobox ( diff). I then opened a discussion on the talk page where I linked to 4 of the 6 archives where infoboxes are discussed (there is also clear consensus against a box from late 2011 on the current talk page) here and was told by Pigsonthewing "I note that you dismiss my addition of an infobox without making any arguments against it" (which he had not even labeled as an infobox on adding it to the article)."

This shows Andy Mabbett's persistence. I remember bringing up evidence of his warring on the very same very article in the Pigsonthewing2 Arb Case back in 2007 [144]. If it wasn't obvious already, this is why the previous Arb Cases are relevant to this one.

If Mabbett isn't sanctioned properly, we can expect more of the same. -- Folantin ( talk) 15:00, 8 September 2013 (UTC)

Dance

You read it on the Main page: ... that when rehearsing Dvořák's Eighth Symphony, conductor Rafael Kubelík said: "Gentlemen, in Bohemia the trumpets never call to battle – they always call to the dance!"?

  • I recommend a closer look at the above mentioned "six more infobox discussions were initiated on article talk pages by the parties involved here during these proceedings", six diffs provided. Yes, I started a few, not for battle, but to see if we can actually argue in decency, as a model for future discussions. I inserted an infobox for Götterdämmerung, for example, - it was reverted and discussed, - have a look what the parties did and if there is anything in it that requires restriction. (I confirm again that I will not add an infobox to another opera, it's enough.) The infobox on Peter Warlock was added by none of the parties. The following discussion reads to me as if the principal author was ready to accept a short infobox. The two discussions on Verdi and Das Liebesverbot were started as part of the arbcom case and only taken to the respective talk pages. Rigoletto was started before the case. Siegfried (opera) was a suggestion on the talk page, a very short eye-opening discussion which I actually enjoyed for literary skill displayed. Don't miss it.
  • I am by now bold enough to recommend a closer look at a diff that was at one point given as a reason to ban Andy. He moved an existing infobox from the bottom up to the top and uncollapsed it. He did that in an article written by me where I wanted an infobox. - Looking at his contributions in 2013, I don't see a reason to restrict him, - what do I miss? -- Gerda Arendt ( talk) 06:32, 9 September 2013 (UTC)
  • I recommend a look at the top of my talk: links to several articles, including the symphony mentioned above which has an infobox shaped after the 2007 Buckner model, and some of Andy's recent article work. Enjoy, -- Gerda Arendt ( talk) 06:32, 9 September 2013 (UTC)
Gerda, a couple of points. The constant reference to Main Page material (and recent article work) is becoming rather wearisome. There is really no point constantly emphasising that and using DYKs (or other Main Page content) as examples. Main Page content is good, but it doesn't have a special or hallowed place on Wikipedia. Things appear on the Main Page only briefly, and far more important is long-term stability and quality. Quoting a DYK hook in an attempt to recast a battle as a dance is distracting and annoying. If you want to say that you think this area should be less a battle and more an area for calm discussion, then just say that without dressing it up as a dance.

I am sure many of the discussions associated with infoboxes are fascinating, but at the end of the day are they really productive and useful? Can you see that some people think that the amount of time and effort that goes into them may outweigh the benefits? Why do people spend so much time on the details, when there is so much other (arguably more productive) work that can be done on Wikipedia? Some people like discussing things like infoboxes, but people have differing tolerance levels: some would like to get back to doing other things, while some seem quite happy to spend weeks and months (even years) discussing infoboxes over many articles (essentially specialising in infoboxes). Can you see how that can end up being be a problem? Imagine this amount of discussion over a category, an article title, an image, the balance of the lead section, the precise wording used at any point in the article itself, or even the quality of the sources used (or not used).

Those discussions do happen (and people do 'specialise' in category work and article title discussions - not always terribly productively in my opinion, but that is their choice), but like the discussions over infoboxes, they need to be focused and not overwhelm the other work that needs doing. My inclination when something is disputed is to recognise that fact and consciously attempt to minimise the impact discussions can have on others, plus (and this is critical) focusing on improving other aspects of the article before even considering returning to previous discussions. If things show no sign of improving after this case, it is extremely likely that those mentioned in the decision (if they continue to contribute to the overall deterioration) will face further sanctions later on, such as topic bans or even site bans. Those named in this decision absolutely need to step back and let others have their say in the post-case discussions. Please consider that. Carcharoth ( talk) 08:11, 9 September 2013 (UTC)

  • I can speak only for myself. I repeat that I don't add infoboxes to "contentious" Classical composers unless they are "my own". I repeat that for articles on operas and Classical music, I stepped back from adding infoboxes and starting discussions on talk pages, unless they are "my own", as this symphony. I confess that I would prefer to see more consistency, all symphonies treated similarly, or at least those by one composer, but will spend no time fighting for that. I hope that consistency may be an aspect in future thoughts on the topic. - I would have chosen a different word than "dance", but could not change a quotation ;) -- Gerda Arendt ( talk) 09:47, 9 September 2013 (UTC)
  • Gerda, first of all, please note that I'm speaking only in my personal capacity, but would you be willing to enter a gentlemen's agreement under which, for the moment, you accept to refrain from adding infoboxes to single articles, with the exception of those you start, until a better guideline regarding infoboxes is adopted? Salvio Let's talk about it! 11:59, 9 September 2013 (UTC)
  • I offered above my way to avoid conflict. Why would you think the project wins if I stop adding infoboxes in the estimated 95% of articles where an infobox is the normal thing to have? (Not that I would have time for it, just curious.) -- Gerda Arendt ( talk) 22:14, 9 September 2013 (UTC)

Time to close

Isn't this whole case now rather going around pointlessly in circles? The Arbcom has accepted and established, that which most of us already knew: infoboxes are not mandatory. Furthermore, the Arbcom has established, again what most of us already knew, that certain editors (one in particular) have been vehemently arguing and trying to impose infoboxes on pages against consensus and policy and in doing so, causing disruption. Arbitrators are now themselves becoming guilty of deviation and in danger of exceeding their remit.  Giano  09:14, 9 September 2013 (UTC)

They should probably dot their i's and cross their t's, though. Gerda Arendt restricted (2) and Smerus prohibited are now both marked in the implementation notes as "cannot pass", but each has 5 supports, 5 opposes, and no abstentions. User:Roger Davies's previous votes have been struck but he has not "re-voted" in either of them. Voceditenore ( talk) 11:30, 9 September 2013 (UTC)
Roger's votes were struck not because he changed his mind, but rather because he went inactive. Salvio Let's talk about it! 11:47, 9 September 2013 (UTC)
Ah. Thanks for that explanation. Best, Voceditenore ( talk) 11:57, 9 September 2013 (UTC)
(ec) I don't think it's time to close as long as the proposed "remedy" for Andy ("Pigsonthewing is indefinitely banned from adding, or discussing the addition or removal of, infoboxes.") would prohibit him from adding an infobox to "his own" articles, such as Francis John Williamson and Selly Manor. -- Gerda Arendt ( talk) 11:51, 9 September 2013 (UTC)
Well he should have thought of that before he caused all this trouble. If there was any sensible justice in the world, he would be be completely banned and therefore not writing anything at all. He should count himself lucky that he's not.  Giano  11:53, 9 September 2013 (UTC)
I happen to like his writing, this edit especially, -- Gerda Arendt ( talk) 12:01, 9 September 2013 (UTC)
( edit conflict)Gerda, as far as I'm concerned, Andy is getting off lightly, here; however, having caused enough disruption wrt infoboxes, it's best if he keeps as far away from the topic as humanly possible without exceptions. So, no, I would oppose authorising him add infoboxes to "his own" articles.

Also, as a side note, in the spirit of patti chiari, amicizia lunga, as they say in Italy, (which means "clear understanding breed long friendships", by which I mean that I'm not assuming bad faith of you or anyone else, but just want to make this clear to avoid unpleasant surprises for anybody), if Andy was to ask another editor to add an infobox to an article on his behalf, that may be construed as an attempt to game the restriction and may lead to sanctions. Salvio Let's talk about it! 12:08, 9 September 2013 (UTC)

Here you are, Gerda, encouraging people to go arownd and arownd in circles again. We are not discussing the quality of Andy Mabbitt's writing - that is not the issue. This case is about the hectoring and bullying that has surrounded the implementation of infoboxes against policy. That has been proven. Now it would help this case enormously if you and others would try and stick to the relevant facts of the case.  Giano  12:12, 9 September 2013 (UTC)
Giano, "it's the irrational hatred of a clique of editors" as noted below that IS the relevant facts of the case and what got us here. Not Gerda. She is the person who was hectored and bullied. Can't anyone understand that? Montanabw (talk) 19:36, 9 September 2013 (UTC)
You need to make very sure there is no leeway for Mabbett to game the sanctions. You also need to make sure you have the stamina to enforce them - please, Arbs, no offloading the responsibility for enforcement onto the shoulders of some poor admin who will be mobbed by Mabbett's fan club. As far as I'm concerned, Mabbett's already tried a breaching experiment with his addition of an infobox to Joseph Priestley, as noted in the section above. I predict more of the same, unless he's properly supervised. -- Folantin ( talk) 13:05, 9 September 2013 (UTC)
Folantin, there is no cabal, and they are not after anyone. Drop the stick, please. Montanabw (talk) 19:36, 9 September 2013 (UTC)
Sorry, I don't understand "implementation of infoboxes against policy" (there is no policy against them) and "mobbed by Mabbett's fan club". Everybody can check Andy's edits, no? Many will. -- Gerda Arendt ( talk) 13:38, 9 September 2013 (UTC)
Gerda, as you well know, it's not policy to enforce an infobox: Mabbett frequently wandered in off the street and dictatorially tried to impose them - that's against policy. While your loyalty to Mabbett is to be admired - you really need to accept that he was in the wrong behaving as he did.  Giano  18:18, 9 September 2013 (UTC)
I thought I had said more than enough but you addressed me personally. So, as gently as I can (imitating the ways of the sadly missed George Ponderevo) I ask as I asked consistently since the beginning of the case: when did Andy add an infobox to an article that was meant to be infobox-free and behave "dictatorially" (however you would reference that term)? You have experiences from a past that I don't share, but the last time I observed him adding an infobox, followed by a long discussion was Cosima Wagner, 25 December 2012 (Please note that the lady isn't even a classical music composer.). What I observed now (see below) is add, make one comment and walk away, see below. I trust that he can do it from now on, that's all. -- Gerda Arendt ( talk) 06:59, 10 September 2013 (UTC)
Not to preclude any answer Giano might provide, but I have to say my very first encounter of Andy here totally chimes with what others, including Giano, have said about his dictatorial behavior. On Talk: Peter Warlock Andy suddenly appeared, intervening in what appeared to be a reasonably civil if candid exchange between Smerus and another editor, who had just posted "I consider myself wrist-slapped. Sorry." Andy's very first comment was: "Don't. Smerus is bullshitting. "no infobox should be added without a formal justification" is utter bunkum." I should add that Andy had latched onto a phrase of Smerus's, which in context has a quite different flavor: "I considered tinkering with the added infobox to remove the irrelevant information included in it. However, on further consideration I believe that, as this article obtained FA status (the highest classification possible for a WP article), no infbox should be added without a formal justification and evdience that it improves the article." i.e. Smerus meant no more or less - it seems clear to me - than anyone wanting to add an infobox should present a written justification for doing so and demonstrate "that it improves the article". Furthermore, Smerus had indeed, as I'd seen from the edits on the article, attempted to improve the content of the infobox before deciding - quite rightly in my opinion - that the infobox was a poor introductory tool for this particular article.
Anyway, Andy proceeded to edit-war over the info box, twice reverting within 70 minutes to reinstate it without offering any justification, and only desisting when a *third* editor (neither Smerus or myself) intervened and removed the infobox. If anyone cares to check the talk page, they will see that - quite apart from my being offended by Andy's rude appearance and attitude - I actually went over the objections Smerus had raised against the box, pointing out that he had at least tried to make it work, whereas Andy by contrast offered no argument or attempt to demonstrate the efficacy of the box but was, as I said at that time, "imposing the infobox for no stated reason whatsoever". I wrote this based entirely on what I had seen him write on that talk page (I've just checked, and that was absolutely his first post there), and his edits on the article. Andy continued to refuse to answer any points either Smerus or I had raised about the article and the infobox, but simply brandished the straw man he had made - i.e. his selective quotation from Smerus.
I have since understood there was a past "history" between Andy and Smerus. Still, that does not excuse Andy's behavior on that (still quite recent) occasion. Alfietucker ( talk) 07:39, 10 September 2013 (UTC)
You describe your perception well, and everybody interested can follow the discussion. You might have mentioned that Andy had not added the box, - we were talking about "wandered in off the street and dictatorially tried to impose them". (I think I mentioned already somewhere that I don't mind bullshit here, bollocks there. Telling someone - possibly a user who never heard that an infobox can be a problem and who felt "wrist-slapped" by a revert: "don't" [feel wrist-slapped], - how do you describe that?) You might have added that the further discussion with the main author (Smerus had made only one edit before) reached acceptance for a shorter infobox. This - discussing the content (!) of the infobox - could have been achieved without a revert. The only reason why an infobox is not in the article seems to be that the author is waiting for " less volatile times". I wish him patience. -- Gerda Arendt ( talk) 08:24, 10 September 2013 (UTC)
I'm aware of what was being discussed. In the Peter Warlock instance Andy certainly "wandered in off the street and dictatorially tried to impose" an infobox: the fact he was not the original author is not the issue; what is relevant is that he twice reverted within 70 minutes to keep it there, which *was* an imposition (and disregarded BRD), and the fact he refused to offer any explanation to justify this makes his actions dictatorial. I'm afraid Giano's description of Andy's behaviour matches this case fairly exactly. Alfietucker ( talk) 08:43, 10 September 2013 (UTC)
I don't think it's a coincidence that Mabbett chose Joseph Priestley at this particular time.-- Folantin ( talk) 14:46, 9 September 2013 (UTC)
There is already talk of gaming the system (or not gaming the system) here]. My view is that Andy Mabbett's continued presence will be disruptive by its very existence. How will we know that infoboxes are not being added by his many 'students of Wikipedia' and what influence will he exert as Wikipedian in residence (the Wikipedian in Residence at Queen Street Textile Mill Museum, Burnley; also the Wikipedian in Residence at The New Art Gallery Walsall; Wikipedian in Residence at Staffordshire Archives and Heritage Service (winter 2012/2013) and Wikipedia Outreach Ambassador). If he's allowed to remain a 'Wikipedian', the whole thing is unpoliceable.  Giano  13:19, 9 September 2013 (UTC)
The difficulty of monitoring infoboxes added by 'students" would by just the same even if he was banned. Now I - in a way a student - restricted myself, will not infoboxes for opera and classical music other than "my own". But for a building such as Selly Manor: where's a problem with a 'student' adding an infobox? Then why not allow the author to add it himself? -- Gerda Arendt ( talk) 13:38, 9 September 2013 (UTC)
Gerda, you really are not getting it are you? The whole point of this case seems to have passed you by in some sort of fluffy cloud of cotton wool. I shall say no more and leave it to the Arbs to see that this case needs wrapping up tightly before we are all suffocated by any more thick fog.  Giano  13:43, 9 September 2013 (UTC)
Giano, you have just exemplified the locus of this dispute. It's not the infoboxes, it's the irrational hatred of a clique of editors who are so vehemently opposed to the great unwashed editing "their" articles that they feel it gives them the right to talk to other editors like something they just stepped in. This is an encyclopaedia built by collaboration, and no editor has the right to take the sort of tone your posts above take with Gerda. There is no need for it, and its only purpose is demean other editors, so kindly knock it off. I'm not going to sit here and defend Andy—he knows his conduct has been unacceptable and it's up to him to see the error of his ways—but nothing he or any of the pro-infobox crowd have done gives you license to attempt to patronise and demean Gerda or anybody else like that. I'm firmly of the belief that if both sides stopped stopped bickering like children and stopped trying to get one-up on each other, you might actually find some common ground. HJ Mitchell | Penny for your thoughts? 17:39, 9 September 2013 (UTC)
👍 Like You got it in one, HJ. That is EXACTLY what I have been trying to explain all along! Montanabw (talk) 19:36, 9 September 2013 (UTC)
  • This case would have been simply and quickly resolved if people were capable of (and advised)to sticking to relevant facts. Instead we have had millions of words going of at tangents. You say, User:HJ Mitchell, "Andy knows his conduct has been unacceptable" - well you seem to be the only person who has spotted that amid the huge smokescreen of waffle that's been created. So don't you come here preaching like some puritanical Sir Gallahad telling us what we all should have seen and how to behave because you appear to be alone in your observations.  Giano  20:08, 9 September 2013 (UTC)
  • I don't think HJ Mitchell is all that alone in how he believes people should be behaving, Giano. I've found your comments to be consistently derisive too. As for Andy, HJ is not alone there either. Several people, including arbitrators, have acknowledged Andy's own acknowledgment that his behavior needs improvement. equazcion (talk) 20:16, 9 Sep 2013 (UTC)
  • Drowning people invariably learn to swim a few strokes before they sink for the third time - and I believe it will be Andy's third time. I admre your faith and trust, but really its naivety is worrying.  Giano  20:21, 9 September 2013 (UTC)
  • I don't have any trust or faith. It's not myself who thinks Andy will get better. I don't know anything about him and have no experience with him. But you said HJ was alone in his observations, and I just wanted to correct you. equazcion (talk) 20:25, 9 Sep 2013 (UTC)
  • ".I don't know anything about him and have no experience with him" Then why on earth are you here? Sitting like a little old woman knitting at the foot of the guillotine.  Giano  20:28, 9 September 2013 (UTC)
  • I'm here because I wanted to refocus a little of this case on the larger underlying issue, and suggested a proposed decision recommending a community RfC, which was subsequently added and passed. I may not know anything about the involved parties prior to this case, but solving the greater issue interests me. Some of us do make appearances in the interest of something other than interpersonal drama. equazcion (talk) 20:33, 9 Sep 2013 (UTC)
"Andy knows his conduct has been unacceptable". His addition of an infobox to Joseph Priestley on 2 September would suggest otherwise, especially given the history of his prior involvement in that article. -- Folantin ( talk) 20:36, 9 September 2013 (UTC)
Andy's friends are currently bestowing him with the gifts of humility and remorse that his actions don't seem to portray. Throughout this has been a strong theme of the case - I wonder if the Arbs are clever enough to see through the fog and cotton wool. Time will tell.  Giano  20:42, 9 September 2013 (UTC)
So people who don't know Andy shouldn't be commenting here, and anyone who supports him must be his friend. I have to say, Giano, without being privy to this conflict, if I had to ascertain who might be most responsible for its escalation, you'd be at the top of my list, based on what I'm seeing on this page. It's a shame the case is nearly concluded without a decision regarding you, as I have a feeling your continued involvement in infobox issues will cause continued problems. equazcion (talk) 22:57, 9 Sep 2013 (UTC)
You can't base a judgement on this case only by what you see on this page, that's the point. Smeat75 ( talk) 00:59, 10 September 2013 (UTC)
As you say, Equazcion, you are not privy to this conflict. Were you informed on this subject, you would be aware that Mabbett and I have only come into contact when you has wandered off the street onto pages where I have been a significant editor (note: I do not say my pages) on one occasion I would go as far as to say he was provocatively trolling a page. I have frequently declined to comment on his edits to musical pages because, while I sympathise, I have not edited those pages. However, My advice to Mr Mabbett is if you don't want trouble don't go looking for it. Like most editors here, I woudl quite like a quiet life without being ordered and dictated to by misinformed editors who have already been banned twice (without any help from me) because of their behavior on this subject.  Giano  06:11, 10 September 2013 (UTC)
Well, this is the crux of the conflict, is it not? My understanding is that the way "significant" editors react when someone from "outside" comes along to make changes is central. Referring to the them as "coming in off the street" and "looking for trouble", etc, is the stance from the involved parties in opposition to Andy, rather than being some special circumstance that precludes your being referred to as involved. equazcion (talk) 06:22, 10 Sep 2013 (UTC)
I can see that this is very difficult for you to grasp. Let me try to explain it simply: Arriving on a page upon which one has never edited (but is often still in progress by a group of dedicated and knowledgeable editors) and then making major changes without at least minor consultation is at the least extreme bad manners, at worst disruptive. When the dedicated and knowledgeable editors unanimously reject Andy's changes, he edit wars and causes trouble and distress. Often he plonks his infobox on a fully formed page which has attained or is attaining GA or FA status (again without consultation) and then wanders off and expect others to maintain it. That this causes resentment and anger is hardly surprising. Your "crux" of this matter is that Mr Mabbett is the architect of his own misfortune and attempts by his supporters to try and shift the blame are misguided.  Giano  06:41, 10 September 2013 (UTC)
Allow me to make my stance easier to grasp as well: I'm more than aware of your stance and who you think is to blame. That's not in contention at the moment. Perhaps Andy has acted inappropriately, or perhaps not -- I wouldn't presume to know this without delving deeper into several page histories. Your own manner in dealing with it, if the comments on this page are any indication, tells me it is likely that he is far from the sole reason this conflict has escalated to an arbitration case; and I suspect the conflict will survive any measures implemented against him if you continue to act in the future the way you are here. equazcion (talk) 06:51, 10 Sep 2013 (UTC)
  • I rather think you will find, if you bother to research before further commenting, that compared to the long term trouble that Mr Mabbett has caused others, my involvement with him has been minimal. In fact, I have often felt guilty for not doing more to support the many beleaguered musical editors who have suffered from his behavior. However, my own personal view is that editors should not become involved in pages about which they know nothing. This is a public page, so it is right that all who have experience of the subject can bring their grievances here - providing they understand what they are talking about. It seems to me that you belong to a class, once known as the Peanut Gallery. I suggest that you read up before commenting further.  Giano  07:58, 10 September 2013 (UTC)
I'm commenting on your behavior on this page, Giano, which I'm equipped to do, having been involved here and read the entire thing. You're free to dismiss me using whichever personal criteria you deem acceptable, although I seem to not be alone in my assessment, among at least one person who does appear to meet your criteria. equazcion (talk) 08:06, 10 Sep 2013 (UTC)
You are actually wasting time and space by deliberately deviating and obscuring with hot air; so I shall cut off your oxygen and not engage further here with you.  Giano  08:10, 10 September 2013 (UTC)
I don't think this exchange has deviated from the point, and I don't have any interest in wasting time (I'm not sure what possible motivation I would have in doing so deliberately). If most of the people here have come in order to assess the conflict from a user behavior standpoint, I think this is a rather relevant discussion, even though it's not my own primary reason for being here. Your responses here have demonstrated that you handle disagreements by responding derisively, resorting to name calling and attempting to "score hits", as they say; quite the opposite of attempting to defuse the situation. I do hope this is a unique result of my somehow having inadvertently pushed your buttons (if so, I do apologize), and I similarly hope this isn't how you normally engage those with whom you have disagreements. If this is how you've been handling infobox conflicts, then I think something needs to change there if the matter is to progress better in the future. equazcion (talk) 08:27, 10 Sep 2013 (UTC)

@ Salvio and Hahc21, since Roger Davies is now listed as inactive, shouldn't all of his votes have been struck? I notice that his "oppose" at Pigsonthewing banned remains. Not that it makes any difference to the outcome, but there should be an accurate record of how the final vote was split. Voceditenore ( talk) 13:45, 9 September 2013 (UTC)

That was just an oversight, which I have just corrected. Thanks for pointing this out! Salvio Let's talk about it! 10:13, 10 September 2013 (UTC)

Request clarification re "Editors reminded" section

I would still like arbitrators to clarify, preferably in the decision itself, what exactly is meant when it says "All editors are reminded ....to avoid turning discussions about a single article's infobox into a discussion about infoboxes in general" which would seem to me to mean that any discussion of "metadata" or machine readability or wikidata etc should never be introduced into discussions about whether a specific article should have an infobox or not as that is exactly an issue "about infoboxes in general". Thanks Smeat75 ( talk) 02:14, 10 September 2013 (UTC)

This is similar to the point I made on 3 September: " . . . If centralized discussions of key aspects of “infoboxes in general” have never taken place, then that avoidance will be difficult, if not impossible, to achieve.". So I support Smeat75's call for clarification. Klein zach 03:32, 10 September 2013 (UTC)
The way I read it, the principle invites editors to discuss each case on its merits, i.e. why an infobox would be a good or a bad addition to the article in question. This may include references to metadata and machine readability.

In my opinion, this remedy was only meant to indicate that generalisations such as "infoboxes are always good, no article should go without one" and its opposite "infoboxes are the worst thing ever" should be avoided at all times. Salvio Let's talk about it! 10:22, 10 September 2013 (UTC)

"A discussion about infoboxes in general" is not quite the same thing as "a generalisation about infoboxes". Arguably generalizations are always bad . . . . but in reality the arguments have related to specific templates rather than individual articles, e.g. the use of Infobox musical artist for classical composers, so they haven't normally been about infoboxes in general, or about individual articles either. Klein zach 12:07, 10 September 2013 (UTC)
"infoboxes are always good" because they emit metadata, etc., is just what has been said in hundreds of these arguments which, if anything is going to change, should not be acceptable any more in discussions of specific articles, in my opinion. Smeat75 ( talk) 13:11, 10 September 2013 (UTC)

What this case is about: The right to say no (and have it stick)

Many of our basic rights can be expressed as a right to say no. An election allows voters to say no to the candidates or leaders they do not want. Free speech is the right to disagree, to say "no, that is not what I think". Many protections of a civil society involve the rights of minorities to say no to the majority (no, children cannot work in factories; or no, you cannot enslave others; or no, you cannot stop me from voting, etc.).

On Wikipedia, ALL of the Five Pillars can be seen in some way as rights to say no:

What Wikipedia is not (No to all things not encyclopedic);
Neutral point of view (No to bias);
Wikipedia is free content (No to payment for or restrictions on use and re-use)
Civility (No to offensive language, no to ignoring the positions and conclusions of others, and no to attacking others)
Ignore all rules (No to any rule that prevents you from improving or maintaining Wikipedia)

As far as infoboxes go, WP:INFOBOXUSE says in part "The use of infoboxes is neither required nor prohibited for any article. Whether to include an infobox, which infobox to include, and which parts of the infobox to use, is determined through discussion and consensus among the editors at each individual article." To me that says that editors have the right to say no (on occasion) to infoboxes. This applies to all sorts of articles, not just classical music. So Waterfalls in Ricketts Glen State Park and Horse Protection Act of 1970 and British military intervention in the Sierra Leone Civil War are all FAs and none of them have infoboxes, and that's OK.

I am not against infoboxes, per se (and most of the aticles I've nominated at FAC have a box of some sort). I am against any "one size fits all" solution, and I am in favor of editors having the right to say no to an infobox. I am also in favor of decisions being decided by consensus, and then allowed to stay that way. Let it stick, and don't bring it up over and over and over and over and over again ...

This is the last thing I plan to say about infoboxes for the next three months.1 I invite everyone to take a break, think things over, and hopefully let things calm down. Ruhrfisch ><>°° 02:33, 10 September 2013 (UTC)

1If someone adds an infobox to an article on my watchlist without one, I reserve the right to discuss it there, or to comment on a RfC on this topic.

  • Very reasonable and well expressed - I agree. Alfietucker ( talk) 06:56, 10 September 2013 (UTC)
  • This should form part of the Decision. I've yet to read a better expression of the moderate infobox-sceptic position. Klein zach 00:39, 11 September 2013 (UTC)

Include infoboxes in new articles which they create

"They may ... include infoboxes in new articles which they create." is a clause in the planned restriction for me, and I can live with that. This clause is still not in one of the restrictions for Andy. please think about it. Philosopher, with a background of law, noticed this ( see above, "My only thought was that since this is about conflict between users, a restriction where there was only one user would be irrelevant."), improved wordings were suggested by Mackensen, supported by SchroCat.

I support that Andy may add infoboxes to his own new articles.

  1. -- Gerda Arendt ( talk) 10:41, 10 September 2013 (UTC)
  2. -- I would agree. -- ColonelHenry ( talk) 13:16, 10 September 2013 (UTC)
  3. Support, Though I think my modification of Mackensen's proposal above is better still. He would not be able to revert or argue against any subsequent removal so there is no risk of extended argie-bargie. Johnbod ( talk) 14:19, 10 September 2013 (UTC)
    @Johnbod: I agree that your version is better, also Mackensen's proposals. This is more an idea than a specific wording. -- Gerda Arendt ( talk) 14:27, 10 September 2013 (UTC)
  4. I'm going to go out of my way and AGF here, with some additional criterion: articles which Andy has personally started (first edit) and the infobox may only be included in that first edit. —  Crisco 1492 ( talk) 16:01, 10 September 2013 (UTC)
  5. I'd support; also if I were to create an article and ask Andy to help me, I'd sure prefer that optionL there are dozens of wikiprojects where infoboxes are standard operating procedure and the local consensus is to encourage them; more than not, in fact. Is there any project other than the classical music ones that have such an anti-infobox position? (Wondering) Montanabw (talk) 17:02, 10 September 2013 (UTC)

I support Andy having nothing to do with infoboxes whatsoever anywhere.

  1. --  Giano  15:11, 10 September 2013 (UTC)
  2. What Giano said. I can already guess how this concession might be gamed. -- Folantin ( talk) 15:20, 10 September 2013 (UTC)
    I can't - how? Johnbod ( talk) 16:05, 10 September 2013 (UTC)
Well, I should be careful of WP:BEANS, but one way would be the creation of dozens of stubby one- or two-line articles in certain subject areas, just so those pages can have obligatory infoboxes. -- Folantin ( talk) 16:17, 10 September 2013 (UTC)
Which anyone not restricted can remove without comeback. I think this is pretty far-fetched, and would it be the end of the world? Johnbod ( talk) 16:28, 10 September 2013 (UTC)
I'm afraid that I agree with Folantin, John, as you say anyone could remove infoboxes that Mabbett inserted; his pages would become a playground for trolls and anons and cause even more trouble. Personally, I would keep a lot of spave between me and any page he created, but you know what Wikipedia can be like....  Giano  08:09, 11 September 2013 (UTC)
Comments by ColonelHenry

If Andy creates an article, he should be able to add whatever he wants by way of infoboxes, templates, widgets, whatever. Telling an editor "you can't do this" when other editors can violates the spirit of Wikipedia. Personally, even though I'm not a big fan of infoboxes, a good infobox is a benefit to an article. Where the infobox is lacking, I can understand the desire some editors in deciding against adding one. But it is nonsensical where there's a net improvement to article to avoid adding one. I wish the infobox policies on Wikipedia would change...especially in the classical music area. Infoboxes should be on a case by case basis (balancing the informativeness of infobox with the needs of the article), there shouldn't be any blanket edicts banning them by either a WikiProject or a well-organised clique of determined editors intransigently insisting one way or the other irregardless of the facts or rationale. Further, I don't see the point of irrational arbitration cases giving edicts of "thou shalt not add infoboxes." A dictum of "we're not going to provide infoboxes because the information's already in the article" doesn't address all users....while I like reading the articles, I have to acknowledge that 90% of readers give an article 30 seconds despite our best efforts and useless arguing. And penalizing Andy for improving an article is a ludicrous position just because someone is vehemently anti-infobox. Apparently, I wouldn't be surprised the same people who refuse editors to classical music articles the freedom to choose whether or not to infobox are probably listening to Shostakovich and know Stalin denounced him for exercising freedom in creating and almost silenced him over insistence on similar bullshit. -- ColonelHenry ( talk) 13:16, 10 September 2013 (UTC)

I'm confused; was Shostakovich for or against infoboxes? -- Michael Bednarek ( talk) 13:34, 10 September 2013 (UTC)
( edit conflict)Rather *against*, I'd say. Seriously, though, if we're going to evoke Stalin it could be argued with more pertinence that those who insist on infoboxes being inserted in an article - against the wishes of those editors who are familiar with the subject - are rather like Stalin insisting that every artist should work within the aesthetic of Socialist Realism. More to the point, isn't it usually argued (by Gerda, for instance) that infoboxes are *not* meant to be, and cannot be, a 30 second summary of an article? It's precisely your confusion on this matter which adds grist to the mill to those who are concerned that infoboxes, rather than enhancing, can short-circuit an article: i.e. you've just demonstrated the mindset of those readers who think all they need to crib up on the subject is to read the infobox, rather than the lead/lede which demonstrably - when well written - does that job much more efficiently. Alfietucker ( talk) 13:37, 10 September 2013 (UTC)
You called me: what do you think I argued? Summary not of the article, but key facts? Yes. Any time in seconds given? No. - I believe an infobox serves an article like a cover a book, but I don't insist, and I respect the wish of a main author, even if I don't understand it. - Yesterday I was pleasantly surprised seeing the main author of Peter Warlock experimenting with an operatic infobox, - if a new era begins with a small step, I can easily leave the scene ;) -- Gerda Arendt ( talk) 13:58, 10 September 2013 (UTC)
I was responding to the implication of "ColonelHenry's statement: "A dictum of "we're not going to provide infoboxes because the information's already in the article" doesn't address all users....while I like reading the articles, I have to acknowledge that 90% of readers give an article 30 seconds despite our best efforts and useless arguing." Sorry, I didn't mean to misrepresent your argument - I guess I should have written something like "infoboxes are *not* meant to be, and cannot be, a summary of an article ("30 seconds" or otherwise)". My point - about the evident danger of readers treating infoboxes as a "crib" for an article - still stands. Alfietucker ( talk) 14:11, 10 September 2013 (UTC)
(Aside: Actually, the Stalin page is a brilliant demonstration of the uselessness of biographical infoboxes. The box contains tons of trainspotterish information while completely failing to get to the essence of the man's "achievements" (Ukrainian famine or Great Purge, anyone?). I think I've already mentioned Adolf Eichmann as another example of the box's ability to miss the point in a crashingly offensive, anal retentive way). -- Folantin ( talk) 15:33, 10 September 2013 (UTC)
Nazi Germany and Adolf Hitler are further gems in this respect. Johnbod ( talk) 16:31, 10 September 2013 (UTC)
"Actually, the Stalin page is a brilliant demonstration of the uselessness of biographical infoboxes." - I think this is too general. If one box is bad, it doesn't demonstrate the uselessness of others. If one is bad because the wrong parameters were chosen and filled badly, it can be discussed and adjusted on article level. If the template doesn't provide the right parameters, that can be discussed and fixed on the template level. We improved infobox book by providing wikisource in other languages, not only English, for example, and working on the publishing (next thread there), -- Gerda Arendt ( talk) 16:50, 10 September 2013 (UTC)
Oh great, Stalin and the Nazis. We've now invoked Godwin's Law. Sheesh. I love those biography infoboxes in general, the one for Stalin is a bit long and overdone, but "trainspotterish" info is helpful and often what people ARE looking for in the "cover" of the article (nice analogy, Gerda, I like it). Let's NOT start in on this in other wikiprojects, I beg you! Montanabw (talk) 17:09, 10 September 2013 (UTC)
Montanabw - just to politely point out, in case it's escaped anyone's notice, that Stalin was first evoked by one of the *pro* infobox supporters: make of that what you will. Alfietucker ( talk) 12:51, 11 September 2013 (UTC)
As I keep saying: it really is about time this case was closed.  Giano  17:15, 10 September 2013 (UTC)
It really is time to knock this on the head. -- Folantin ( talk) 18:12, 10 September 2013 (UTC)
Hmmm, given that they are waiting for a 24 hour stable consensus (people keep changing their votes), we can't quite get there, but perhaps as far as the wall of text on THIS page, where we non-ArbCom members have been debating forever and I doubt any minds have changed much, perhaps we finally have said something we can all agree on for this page, at least? Montanabw (talk) 18:32, 10 September 2013 (UTC)

Case is closing

A brief note to let those posting here know that the case is now closing. Please read what I said earlier above. There may be some more discussion at the arbitration noticeboard once the case is closed, but other than that, please let things calm down and allow people to work out in their own time what to do next (if anything). In particular, if any editors sanctioned in this case decide to seek clarification from the committee (at WP:ARCA), please give them time and space to do so by themselves without extraneous commentary. Carcharoth ( talk) 23:44, 10 September 2013 (UTC)

You keep telling us it's closing, but it never seems to. Viewing the Arb's voting is as thrilling as sitting in the middle row at the opera, desperate to go to the loo, and watching Tosca repeatedly trampolining above the parapet. Get a move.  Giano  08:16, 11 September 2013 (UTC)
I'm assuming this is now closed, given the parties have been handed final decision notices. My view: some promising points, but it's too early to tell. The real test will be whether this is enforced properly and what a certain editor decides to do with yet another last chance he has been given. Also, there's the question of whether Smerus returns to editing at some point in the future (let's hope so). I think we should have a moratorium on the infobox issue of, say, three months (I believe something of the kind has been suggested elsewhere on this page). Even that will be too soon.-- Folantin ( talk) 08:42, 11 September 2013 (UTC)

Videos

Youtube | Vimeo | Bing

Websites

Google | Yahoo | Bing

Encyclopedia

Google | Yahoo | Bing

Facebook