Jump to content

Wikipedia:Village pump (policy): Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
m Reverted edit by 149.126.14.70 (talk) to last version by Black Kite
 
Line 1: Line 1:
<noinclude>{{Redirect|WP:VPP|proposals|Wikipedia:Village pump (proposals)}}
<noinclude>{{Short description|Page for discussing policies and guidelines}}{{Redirect|WP:VPP|proposals|Wikipedia:Village pump (proposals)}}{{pp-move-indef|small=yes}}
{{village pump page header|Policy|alpha=yes|The '''policy''' section of the village pump is used to discuss proposed policies and guidelines and changes to existing [[WP:Policies and guidelines|policies and guidelines]].<br>If you want to propose something new that is ''not'' a policy or guideline, use the ''[[WP:VPR|proposals]]'' section.<br> If you have a question about how to apply an existing policy or guideline, try one of the many [[Wikipedia:Noticeboards]].<br>This is '''not the place to resolve disputes''' over how a policy should be implemented. Please see [[Wikipedia:Dispute resolution]] for how to proceed in such cases.
{{village pump page header|Policy|alpha=yes|The '''policy''' section of the [[Wikipedia:Village pump|village pump]] is used to discuss already-proposed policies and guidelines and to discuss changes to existing [[WP:Policies and guidelines|policies and guidelines]]. Change discussions often start on other pages and then move or get mentioned here for more visibility and broader participation.
* If you want to propose something ''new'' that is ''not'' a policy or guideline, use [[Wikipedia:Village pump (proposals)|Village pump (proposals)]]. For drafting with a more focused group, you can also start on the talk page for a WikiProject, Manual of Style, or other relevant project page.
Please see '''[[WP:PEREN|this FAQ page]]''' for a list of frequently rejected or ignored proposals.
* If you have a question about how to apply an existing policy or guideline, try one of the many [[Wikipedia:Noticeboards]].
* If you want to ask what the policy is on something, try the [[Wikipedia:Help desk|Help desk]] or the [[Wikipedia:Teahouse|Teahouse]].
* This is '''not the place to resolve disputes''' over how a policy should be implemented. Please see [[Wikipedia:Dispute resolution]] for how to proceed in such cases.
* If you want to propose a new or amended speedy deletion criterion, use [[Wikipedia talk:Criteria for speedy deletion]].
Please see '''[[WP:Perennial proposals|this FAQ page]]''' for a list of frequently rejected or ignored proposals. Discussions are automatically archived after remaining inactive for two weeks.
|WP:VPP|WP:VPPOL}}__NEWSECTIONLINK__
|WP:VPP|WP:VPPOL}}__NEWSECTIONLINK__
{{centralized discussion|compact=yes}}
{{cent}}
__TOC__
__TOC__<div id="below_toc"></div>
<span id="below_toc"/>
[[Category:Wikipedia village pump]]
[[Category:Wikipedia village pump]]
[[Category:Non-talk pages that are automatically signed]]
[[Category:Non-talk pages that are automatically signed]]
[[Category:Pages automatically checked for accidental language links]]
[[Category:Pages automatically checked for incorrect links]]
</noinclude>
{{User:MiszaBot/config
{{User:MiszaBot/config
|archiveheader = {{Wikipedia:Village pump/Archive header}}
|archiveheader = {{Wikipedia:Village pump/Archive header}}
|maxarchivesize = 400K
|maxarchivesize = 400K
|counter = 128
|counter = 197
|algo = old(7d)
|algo = old(10d)
|archive = Wikipedia:Village pump (policy)/Archive %(counter)d
|archive = Wikipedia:Village pump (policy)/Archive %(counter)d
}}</noinclude>
}}
{{-}}


== Date redirects to portals? ==
== Wikipedia:Disambiguation and inherently ambiguous titles ==
{{archive top|result=Due to formatting errors, this RfC has failed. Please see a new RfC at [https://en.wikipedia.org/wiki/Wikipedia_talk:Disambiguation#Request_for_Comment:_Disambiguation_and_inherently_ambiguous_titles Wikipedia talk:Disambiguation], which is intended to resolve the question posed below. [[User:RGloucester|<span style="font-family:Monotype Corsiva;font-size:12pt;color:#000000">RGloucester </span>]] — [[User talk:RGloucester|☎]] 17:52, 12 July 2016 (UTC)}}
What guidance should [[WP:Disambiguation]] give for article titles that do not result in a conflict between two or more articles, but which are not inherently unambiguous to a general audience?


{{-r|16 August 2006}} points to the current events portal as a result of [[Wikipedia:Redirects_for_discussion/Log/2024_October_4#16_August_2006|this discussion]]. However, date redirects will continue to come up at RfD, some some wider community discussion and input is helpful on '''whether or not the current events portal is an appropriate target for mainspace redirects'''. See also: [[Wikipedia:Redirects_for_discussion/Log/2024_October_14#26,_November,_2006|this ongoing discussion]] for some context.
'''Background:
*[https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Disambiguation&diff=665798731&oldid=663463105 This content] regarding titles that inherently lack precision was added to [[WP:DAB]] on June 6, 2015, by {{u|SMcCandlish}}, consisting of a paragraph under "Is there a Primary Topic?", an example under "Deciding to disambiguate", and a summary sentence in the lead paragraph: "Disambiguation may also be applied to a title that inherently lacks precision and would be likely to confuse readers if it is not clarified, even it does not presently result in a titling conflict between two or more articles." SMcCandlish posted a rationale of this addition to [[Wikipedia_talk:Disambiguation/Archive_43#Disambiguating_WP:PRECISION_failures|the talk page]], which received no replies.
*On July 16, 2015, {{u|Red Slash}} [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Disambiguation&diff=671784557&oldid=671612130 removed] the main paragraph, with the comment "How does this have anything at all to do with disambiguation?". A [[Wikipedia_talk:Disambiguation/Archive_43#WP:PRECISIONDAB|talk page discussion]] between Red Slash and {{u|Francis Schonken}} discussed this removal.
*On July 28, 2015, Red Slash [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Disambiguation&diff=673503177&oldid=673300432 removed] the example under "Deciding to disambiguate". On August 6, this example was restored by SMcCandlish and again removed by Red Slash, then, on August 7, restored by SMCandlish, removed by Francis Schonken, again restored by SMcCandlish, and again removed by Francis Schonken. An [[Wikipedia_talk:Disambiguation/Archive_44#Natural_and_clarifying_disambiguation|RFC]] on the content from that time doesn't appear to have been officially closed, but by my count has three editors in support of the principle of "disambiguation for clarification" and three opposed.
*In February 2016, the lead sentence (the only remaining portion of the content originally added June 6) was removed by {{u|Born2cycle}}, restored by by SMcCandlish, removed by {{u|BD2412}}, restored by {{u|Dicklyon}}, removed by {{u|Calidum}}, restored by {{u|Tony1}}, removed by Calidum, restored by Tony1, removed by Calidum, and restored by {{u|Bagumba}} who locked the page for edit warring. A [[Wikipedia_talk:Disambiguation/Archive_45#Unsupported_change_reverted|talk page]] discussion did not result in any clear consensus.
*On March 23, the lead sentence was removed by {{u|Dohn joe}}, restored by {{u|In ictu oculi}}, removed by Dohn joe, and restored by SMcCandlish. A further [[Wikipedia_talk:Disambiguation#Restored_content_on_precision_cut_from_lead|talk page discussion]] ensued.
*With respect to the participants on both sides, the discussion of the proposed guideline so far has generated more heat than light. I'm hoping a straightforward and (pardon the pun) unambiguous RFC can resolve the issue somewhat permanently and put an end to the disruptions to [[WP:D]]. Two of the talk page discussions have proposed taking this to RFC, but don't seem to have been able to reach agreement even on what an RFC should look like. As I have not, to my recollection, participated in the dispute, I have done my best to frame it neutrally and been so bold as to just go ahead and post it here. Please let me know if I have missed anything salient in the above summary.--[[User:Trystan|Trystan]] ([[User talk:Trystan|talk]]) 02:34, 25 March 2016 (UTC)


Related questions to consider: are portals "part of the encyclopedia"? Thanks, [[User talk:Cremastra|<span style="font-family:'Futura';">''Cremastra''</span>]] ([[User:Cremastra|u]] — [[Special:Contribs/Cremastra|c]]) 00:55, 30 October 2024 (UTC)
===Responses (disambiguation)===
*The second question is easy: Yes, portals are part of the encyclopaedia. As to the first question, portals are reader-facing content and so I see no reason why they wouldn't be appropriate targets for mainspace redirects, given that uncontroversially target mainspace redirects to reader-facing templates and categories when they are the best target. Whether the port is the best target for a given date will depend on the specific date but in general the portal should always be an option to consider. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 01:32, 30 October 2024 (UTC)
*:I agree with this. The portal is definitely not always the best option and it has its limitations, but, as I wrote at [[WP:RDATE]] it should be considered and assessed along with mainspace articles. [[User talk:Cremastra|<span style="font-family:'Futura';">''Cremastra''</span>]] ([[User:Cremastra|u]] — [[Special:Contribs/Cremastra|c]]) 01:44, 30 October 2024 (UTC)
:<small>Pinging: {{u|Utopes}}, who I've discussed this with.</small>
:{{block indent|em=1.6|1=<small>Notified: [[WT:RFD]], [[WT:PORT]], [[WT:CURRENTEVENTS]], [[WT:WPRED]]. [[User talk:Cremastra|<span style="font-family:'Futura';">''Cremastra''</span>]] ([[User:Cremastra|u]] — [[Special:Contribs/Cremastra|c]]) 01:43, 30 October 2024 (UTC)</small>}}<!-- Template:Notified -->
:If a namespace doesn't have the same standards as mainspace, then the reader shouldn't be redirected there while possibly not realizing they are now outside of mainspace. Yes, there is more content at [[Portal:Current events/August 2006]] than at [[2006#August]], but the reader is now facing a decades-old page with no quality control, where links to Breitbart are misleadingly labeled as (AP). [[User:Chaotic Enby|<span style="color:#8a7500">Chaotic <span style="color:#9e5cb1">Enby</span></span>]] ([[User talk:Chaotic Enby|talk]] · [[Special:Contributions/Chaotic Enby|contribs]]) 00:50, 6 November 2024 (UTC)
::Portal does have the same standards as mainspace. That a portal is not up to those standards is no different to an article being in bad shape - fix it. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 00:54, 6 November 2024 (UTC)
:::So I can use the speedy A-criteria for portal pages? [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 17:40, 7 November 2024 (UTC)
::::No, because they are not articles. Two things can be held to the same standard without being the same thing. Criterion P1 previously allowed that (indirectly) but it was [[Wikipedia talk:Criteria for speedy deletion/Archive 85#RfC: Should P1 and P2 be repealed as CSDs?|repealed in 2023]] due to lack of use. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 19:42, 7 November 2024 (UTC)
:::::Then they aren't held to the same standards... More in general, no, they ''obviously'' aren't held to the same standards, e.g. a portal page doesn't have to be a notable topic but may be purely decorative or (as is the case with the date pages) be a list of mainly non-notable things, failing [[WP:NOTNEWS]] and [[WP:LISTN]]. That ''some'' standards are the same (BLP, copyvio, ...) can also be said for e.g. user talk pages, and we don't redirect to these pages either. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 20:24, 7 November 2024 (UTC)
::::::We don't redirect to user talk pages because they aren't reader-facing, so that's irrelevant. We don't hold reader-facing templates and categories to article content policies (because they aren't articles) but we do redirect to them. Don't conflate quality standards with inclusion policies, they are not the same thing. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 21:15, 7 November 2024 (UTC)
::::::::I wasn´t aware that the standards we were talking about were solely quality standards, whatever these may be, and not content standards, sourcing standards, ... I´m sadly not amazed that you consider these irrelevant when deciding what to present to our readers. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 21:37, 7 November 2024 (UTC)
::::In theory, I think portals should be held to the same CSD criteria as articles. But of course the A criteria actually only apply to articles. [[User talk:Cremastra|''Cremastra'']] ([[User:Cremastra|u]] — [[Special:Contribs/Cremastra|c]]) 22:08, 7 November 2024 (UTC)
* There's a lot of random junk in portalspace, but '''yes''', it is part of the encyclopedia. Just like categories and templates, portals are reader-facing content. <span style=white-space:nowrap;>[[User:CFA|<span style="background-color:#e0f7fa;padding:2px 5px;border-radius:5px;font-family:Arial black"><span style=color:#00c>C</span> <span style=color:red>F</span> <span style=color:#5ac18e>A</span></span>]] <span style="background-color:#e6e6fa;padding:2px 5px;border-radius:5px;font-family:Arial black">[[User talk:CFA|💬]]</span></span>
* I didn't really have super strong opinions on portals until seeing this one link to Breitbart, twice, in a misleading way. This is not okay. I agree with Fram that clearly Portals are not being held up to the same standards as regular articles and it might be a bad idea to redirect readers to them. [[User:Toadspike|<span style="color:#21a81e;font-variant: small-caps;font-weight:bold;">'''Toadspike'''</span>]] [[User talk:Toadspike|<span style="color:#21a81e;font-variant: small-caps;font-weight:bold;">[Talk]</span>]] 23:00, 7 November 2024 (UTC)
* I saw this on CENT, and I am confused by the question. [[Portal:Current events/2006 August 16]] is very different from something like [[Portal:Belgium]], and it doesn't make sense to pretend they are the same to establish policy. And what does "part of the encyclopedia" even mean? "Interpreting a confusing phrase" is a terrible way to decide redirect targets. {{br}} For the specific question of "Should dates redirect to the Current Events portal rather than to a page like [[August 2006]] ... I don't know. I don't see a compelling reason why they can't, nor a compelling reason why they should. [[User:Walsh90210|Walsh90210]] ([[User talk:Walsh90210|talk]]) 15:45, 8 November 2024 (UTC)
*:Hey, that's a nice Portal! Thank you for restoring my faith in portals. Clicking on "Random Portal" took me to [[Portal:Trees]], which is also pretty nice. My opinion is now that yes, portals can be good, but it seems to me that we currently have no Ps and Gs to apply to their content or measure their quality, no consensus about how to direct readers to them, and a very checkered and controversial history of deletion. I really dunno what to do about them. [[User:Toadspike|<span style="color:#21a81e;font-variant: small-caps;font-weight:bold;">'''Toadspike'''</span>]] [[User talk:Toadspike|<span style="color:#21a81e;font-variant: small-caps;font-weight:bold;">[Talk]</span>]] 16:49, 8 November 2024 (UTC)
*::Of course that's a nice portal, look who created it :-D [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 17:51, 8 November 2024 (UTC)
*'''No''', we should not redirect dates to the current events portal subpages. It's a [[WP:R#DELETE|cross-namespace redirect]] that takes readers from somewhere they expect to be (an encyclopedia article on the topic "16 August 2006") to somewhere they don't expect to be (a navigational aid(?) that highlights some things that happened that day). I'm not 100% sure what the current events portal subpages are for, but they're not meant to stand in as pseudo-articles in places we lack real articles. [[User:Ajpolino|Ajpolino]] ([[User talk:Ajpolino|talk]]) 22:04, 8 November 2024 (UTC)
*:Cross-namespace redirects in and of themselves are not a problem. They only cause issues when they take someone expecting reader-facing content to "backroom" content (e.g. project space). Both article and portals are reader-facing content, so this is not an issue. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 22:17, 8 November 2024 (UTC)
*::Is there another case where we link a reader from an article to a non-article without clearly denoting it? E.g. I have no problem with the {{tl|Portal}} template folks often use in the See also section. [[User:Ajpolino|Ajpolino]] ([[User talk:Ajpolino|talk]]) 01:12, 9 November 2024 (UTC)
*:::There are lots of redirects to templates and categories. Many navigation templates link to other navigation templates. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 08:12, 9 November 2024 (UTC)
*::::Any examples of these lots of mainspace pages which are redirects to templates? 08:42, 9 November 2024 (UTC) [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 08:42, 9 November 2024 (UTC)
*:::::[[List of elections in Texas]], [[List of Kentucky county seats]], [[Cite web]]. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 00:13, 10 November 2024 (UTC)
*::::::Thanks. Okay, Citeweb is a bad example, not something readers look for but something editors look for. The other 2 are among the 6 existing reader facing redirects to templates (from [[:Category:Redirects to template namespace]], the only ones which are from mainspace and not editor-related like the cite templates). Not quite the "lots" you seemed to be suggesting throughout this discussion, but extremely rare outliers which should probably all be RfD'ed. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 11:42, 10 November 2024 (UTC)
*::::::Now only 2 remaining, converted the other 4 in articles or other redirects. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 11:52, 10 November 2024 (UTC)
*'''Yes''', the current events portals are valid redirect targets for dates and preferred in this case of the best article redirect for a specific date being the month section of an article on an entire year. I agree with Fram that portals are not held to the same standards as articles, but I disagree with Ajpolino's stance that a cross-namespace redirect is so disruptive that they are prohibited in all cases, given that [[WP:Portal]] says "portals are meant primarily for readers." [[User:ViridianPenguin|<span style="color:#40826D">ViridianPenguin&nbsp;🐧</span>]]&nbsp;(&nbsp;[[User talk:ViridianPenguin|💬]]&nbsp;) 23:46, 8 November 2024 (UTC)
*Commenting strictly on the "are portals part of the encyclopedia" question, '''yes''' it is. Unfortunately there was one extremely loud, disruptive voice who kept making portals less useful and suffocating any discussions that ''would'' make it more beneficial to readers. Plenty of willing portal contributors, including myself, left this space and readers are still reaping the seeds of what that disruptive user planted even after they have been ArbCom banned over a year ago. So it may given some people an illusion that portals aren't doing much towards the encyclopedic goal, because the current status is handicapped by its history. I'm reserving my views on the redirect part of the discussion. [[User:OhanaUnited|<b style="color: #0000FF;">OhanaUnited</b>]][[User talk:OhanaUnited|<b style="color: green;"><sup>Talk page</sup></b>]] 07:29, 9 November 2024 (UTC)
*'''Not''', portals are not held to the standards of articles, and if something for whatever reason shouldn't be or can't be an enwiki article, this shouldn't be circumvented by having it in portalspace. Either these date pages are acceptable, and then they should be in mainspace. Or they are not what we want as articles, and then we shouldn't present them to our readers anyway. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 11:42, 10 November 2024 (UTC)
*:These current events pages differ from articles in many respects, but the referencing standards are similar. Whether they happen to be prefixed by "Portal:" or not is not reflective of their quality. '''[[User:J947|<span style="color: #1009bf;">J</span>]][[User talk:J947|<span style="color: #137412;">947</span>]]''' ‡ <sup>[[Special:Contribs/J947|edits]]</sup> 23:18, 11 November 2024 (UTC)
*'''Yes''', because the purpose of [[Portal:Current events/2022 August 21]] is to provide encyclopaedic information on [[21 August 2022]] and this purpose has been by-and-large successful. '''[[User:J947|<span style="color: #1009bf;">J</span>]][[User talk:J947|<span style="color: #137412;">947</span>]]''' ‡ <sup>[[Special:Contribs/J947|edits]]</sup> 23:18, 11 November 2024 (UTC)
*The current events portal example listed seems encyclopedic enough, in that apart from some formatting differences it might as well be a list article, but I've seen other portals that have editor-facing content that is more dubiously appropriate for mainspace. Consider, for example, {{section link|Portal:Schools#Wikiprojects}} (capitalization {{sic}}) and {{section link|Portal:Schools#Things you can do}}, and the similar modules at many other portals. <span style="border:3px outset;border-radius:8pt 0;padding:1px 5px;background:linear-gradient(6rad,#86c,#2b9)">[[User:Sdkb|<span style="color:#FFF;text-decoration:inherit;font:1em Lucida Sans">Sdkb</span>]]</span> <sup>[[User talk:Sdkb|'''talk''']]</sup> 18:27, 13 November 2024 (UTC)
*'''Yes''' per J947, especially given that the current event portals function like an encyclopedic list for the given date. --[[User:Tavix| <span style="color:#000080; font-family:georgia">'''T'''avix</span>]] <sup>([[User talk:Tavix|<span style="color:#000080; font-family:georgia">talk</span>]])</sup> 16:46, 14 November 2024 (UTC)
*'''Yes''', speaking as a recognized ''portalista'', portals have not yet been excised from the pedia. In this case, User:J947 makes the essential point. I'm not convinced that even incomplete, out-of-date portals are any less encyclopedic than the 2 million or so Wikipedia articles nobody bothered to edit last year. [[User:BusterD|BusterD]] ([[User talk:BusterD|talk]]) 14:53, 19 November 2024 (UTC)
*Portals are not part of the encylopedia as we understand encyclopedias: sources of information. They serve as navigation within an encylopedia. We would not see a Portal as the final delivery of information, any more than we would see a contents page, index, blurb, or advert as the final information page. These are all ancillary. People mostly land on a Wikipedia article page without a Portal. I have used Wikipedia for nearly twenty years without ever needing a Portal to direct me to where I want to go, and I would assume this is true for the majority of people. Redirects are designed as a signpost, and we frown upon a signpost simply pointing to another signpost. People would generally only arrive at a Portal if directed there from a link that should more helpfully point to the appropriate article. The Belgium Portal is mentioned above as a good Portal. If we go to the Belgium article and scroll down, there is a link to the Belgium Portal. But the Portal mainly provides us with a digest of the Belgium article, including a link back to the Belgium article, which itself contains more links to Belgium related articles than the Belgium Portal. Huh? Seriously? Why are we taking readers away from a sublime source, rich with information and links, to an inferior source? There is nothing on the Belgium Portal that is not available on the Belgium article page - including links to news. But there is much on the Belgian article page that is not on the Belgium Portal page. My suggestion is that ALL links to portals such as the Belgium Portal should instead go to the main article page. Why are we redirecting people to a redirect page when we can send them to the main article on the topic? Portals are a waste of our time and resources, and are a misdirect for readers. [[User:SilkTork|SilkTork]] ([[User talk:SilkTork|talk]]) 22:33, 23 November 2024 (UTC)
*:@[[User:SilkTork|SilkTork]] Are you also specifically opposed to redirecting to the current events portal, which is more "encyclopedic" than "navigational"? [[User talk:Cremastra|''Cremastra'']] ‹ [[User:Cremastra|u]] — [[Special:Contribs/Cremastra|c]] › 22:44, 23 November 2024 (UTC)
*::I'm not exactly comfortable with [[2006#August]] as a target as that itself is a signpost, but I see little value in us having two such signposts - that simply duplicates and confuses things. Either we have [[2006#August]] or we have [[Portal:Current events/2006 August 16]], and I'd much prefer we simply get rid of Portals, so I would obviously opt for [[2006#August]]. [[User:SilkTork|SilkTork]] ([[User talk:SilkTork|talk]]) 23:02, 23 November 2024 (UTC)
*:::The CE portal has more information for the reader, so I prefer it (see my arguments at [[WP:RDATE]].) [[User talk:Cremastra|''Cremastra'']] ‹ [[User:Cremastra|u]] — [[Special:Contribs/Cremastra|c]] › 23:12, 23 November 2024 (UTC)
*:@[[User:SilkTork|SilkTork]] Your argument breaks down as soon as you realise that disambiguation pages and set indexes exist and that redirects to those pages are extremely common and uncontroversial. We also redirect people to outlines, broad concept articles and overviews. What is the "main article page" for a date? In all but a few exceptional cases there isn't a single article but multiple, and so just as if they had searched [[Mercury]], [[Bitter ash]] or [[Stuffed flatbread]] we present them with a menu of content that is relevant to their search term and let them choose what it is they want to read about. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 22:46, 23 November 2024 (UTC)
*::See my answer above. I don't see the point in duplicating signposts. We have [[Belgium]], so we don't need [[Portal:Belgium]]; and we have [[2006#August]] so we don't need [[Portal:Current events/2006 August 16]]. Signposts are not part of the encyclopedia, but they are navigational aids which lead us to further information. However, we have built into every article multiple signposts to further information. We don't need to have duplicate signposts outside of mainspace to which people are directed away from mainspace to consult. It is a waste of our time and resources, and a misdirection for readers. Internal links are an elegant way of signposting to further information. Navigational templates are a little clunky, but are useful. Portals take readers away from the encyclopedia, and are a pointless timesink for both editors and readers. [[User:SilkTork|SilkTork]] ([[User talk:SilkTork|talk]]) 23:02, 23 November 2024 (UTC)
*:::Portals are just as much part of the encyclopaedia as set indexes and navigational templates. [[Portal:Belgium]] and [[Belgium]] fulfil very different roles in the encyclopaedia, neither is a duplicate of the other. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 23:10, 23 November 2024 (UTC)


== Issues with antiquated guideline for [[WP:NBAND]] that essentially cause run of the mill non-notable items to be kept ==
*'''Comment''': Parenthetical notes in an article title (unless the parenthetical notes are part of the article title) should only be used to distinguish between multiple articles with the same title. I can't think of a time when I would add a parenthetical dab to a title of an article when it didn't belong, merely to clarify something. Perhaps if some examples of contentious article titles were posted, we could see the nature of the dispute here. --[[User:Jayron32|<span style="color:#009">Jayron</span>]][[User talk:Jayron32|<b style="color:#090">''32''</b>]] 03:11, 25 March 2016 (UTC)
::This isn't a pertinent concern, since the disambiguation in question is always or at least virtually always done with [[WP:NATURALDIS|natural]], [[WP:COMMADIS|comma]], or [[WP:DESCRIPTDIS|descriptive disambiguation]] (can anyone think of any exception?). For about two years, adherents to [[WP:PARENDIS|parenthetic disambiguation]] pushed for this at naturally ambiguous animal breed article titles as a [[WP:LOCALCONSENSUS]] gambit, and consistently failed to gain consensus for that (see [[WP:BREEDDAB]] for partial list of RMs and outcomes). <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 16:53, 17 May 2016 (UTC)
*'''No guidance.''' This kind of guidance is a can of worms - loads of unintended consequences. We should not "pre-disambiguate" an article because "it sounds too generic" or "that doesn't sound like it is an X" or "that sounds too similar to X". If there is an existing encyclopedic topic that shares a name with another topic, there is potential ambiguity, and we refer to WP:DAB's guidance. If there's only one topic, then WP:DAB does not come into the equation. The examples given to illustrate the contested guidance show that. "Flemish giant" - with no context - sounds like it might be a tall person from Antwerp. While this may be true, tall people from Flanders is not an encyclopedic topic. So instead, [[Flemish giant]] redirects to [[Flemish Giant rabbit]] - a domestic rabbit breed.<p>But that's the point - "Flemish giant" ''redirects'' to "Flemish Giant rabbit". Why? Because there is no other encyclopedic topic to disambiguate from. Conversely, [[Algerian Arab]] is a dab page, while [[Algerian Arab sheep]] is an article about sheep. So in this case, "sheep" serves to disambiguate, while "rabbit" does not. If you prefer "Flemish Giant rabbit" for [[WP:CONSISTENCY]] purpose or something else, that's fine, but it's not actually disambiguating anything.<p>So - there is actually nothing unusual here. Regular WP:DAB questions should be asked of any title. Those questions should not include "Doesn't that kind of sound like something else?" [[User:Dohn joe|Dohn joe]] ([[User talk:Dohn joe|talk]]) 03:45, 25 March 2016 (UTC)


Specifically, [[WP:NBAND]] #5 and #6, which read:
::"If you prefer 'Flemish Giant rabbit' for WP:CONSISTENCY purpose or something else, that's fine, but it's not actually disambiguating anything." OK, by your narrow definition, this is not actually disambiguating anything, in that there is no confusion what article you want if you say [[Flemish giant]]. Note, however, that by a broader definition, quite often that extra word that is "not necessary" does a lot of good in terms of improving precision and reducing ambiguity. Did you look at the railway station example I added? The point is that that minimalist titling that some espouse leaves things looking imprecise, and we have many examples of consensus naming conventions that don't interpret precision and ambiguity in this narrow B2C way. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 03:52, 25 March 2016 (UTC)
:::Projects are allowed to develop naming conventions. They usually are ''exceptions'' to the precision/ambiguity criterion of [[WP:AT]] - see [[WP:USPLACE]], [[WP:Naming conventions (UK Parliament constituencies)]], etc., referenced at [[WP:PRECISION]]. So, yes, consistency, or naturalness or some other consideration can override precision. But it should remain an exception that doesn't swallow the rule. [[User:Dohn joe|Dohn joe]] ([[User talk:Dohn joe|talk]]) 04:03, 25 March 2016 (UTC)
::::I'm pretty sure projects don't change, supercede, or make exceptions to policy and guidelines. And [[WP:PRECISION]] isn't overridden by having the article title "unambiguously define the topical scope of the article". People seem to ignore that provision, and treat precision as a negative when they could use a shorter title without a collision. That's the B2C algorithm, and it's nonsense. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 05:03, 25 March 2016 (UTC)
::::I'd never seen [[Wikipedia:Naming conventions (UK Parliament constituencies)]] until today. I can't believe it exists. [[User:Curly Turkey|Curly&nbsp;Turkey]]&nbsp;<span style="color:red">🍁</span>&nbsp;[[User talk:Curly Turkey|''¡gobble!'']] 05:09, 25 March 2016 (UTC)
:::::Your singular personal belief is not required to make things exists. The world, and the things in it, exist outside of your consciousness. --[[User:Jayron32|<span style="color:#009">Jayron</span>]][[User talk:Jayron32|<b style="color:#090">''32''</b>]] 05:18, 25 March 2016 (UTC)
:::::: And the world outside the [[Wikipedia:Naming conventions (UK Parliament constituencies)]] basement has moved strongly against this pointless "disambiguation"—WProjects like WP:CANADA and WP:INDIA dropped this silliness years ago. So, what were you saying about "singular personal beliefs"? [[User:Curly Turkey|Curly&nbsp;Turkey]]&nbsp;<span style="color:red">🍁</span>&nbsp;[[User talk:Curly Turkey|''¡gobble!'']] 05:25, 25 March 2016 (UTC)
:::::::And yet, it still exists. Notice how you had a feeling or an emotion (you thought it "silly") and nothing changed. The world works like that: reality continues to keep being real despite you having feelings about it. It's odd you haven't learned that. --[[User:Jayron32|<span style="color:#009">Jayron</span>]][[User talk:Jayron32|<b style="color:#090">''32''</b>]] 16:17, 25 March 2016 (UTC)
:::::::: You don't appear to have a point. [[User:Curly Turkey|Curly&nbsp;Turkey]]&nbsp;<span style="color:red">🍁</span>&nbsp;[[User talk:Curly Turkey|''¡gobble!'']] 21:18, 25 March 2016 (UTC)
::What Dohn joe is missing is that [[Algerian Arab]] was disambiguated to [[Algerian Arab sheep]] on the basis of it simply being naturally ambiguous. It only became a disambiguation page {{em|later}}. His 'So in this case, "sheep" serves to disambiguate, while "rabbit" does not' point is completely invalid. He doesn't appear to understand what "ambiguous" and "disambiguate" means. Neither do many of the other correspondents here. Fortunately, RM respondents often do. That's why [[Argentine Criollo]], [[Welsh Black]], [[British White]], [[Florida White]], and many other such names were disambiguated to more [[WP:PRECISE]] titles, despite no other article directly vying with them for the shorter ones. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 04:03, 26 March 2016 (UTC)
*'''No guidance'''. [[WP:DAB]] was created to address a very specific situation – what to do when two or more articles share the same name. Everything else is covered by [[WP:AT]] and its spin-offs. For example, I'd consider [[Flemish Giant]] to be an inappropriate title (or at least less appropriate than [[Flemish Giant rabbit]]) because it fails WP:AT's "precision" criterion ("The title unambiguously identifies the article's subject..."). No extra guidance needs to be added to allow for titles like [[Flemish Giant rabbit]], and any such guidance would be outside the scope of [[WP:DAB]]. [[User:DoctorKubla|DoctorKubla]] ([[User talk:DoctorKubla|talk]]) 09:39, 25 March 2016 (UTC)
*'''Retain the guidance – and this RfC is non-neutral and grossly misleading''' due to major errors of omission: No policy rationale presented for removal, only false claims that consensus wasn't established. The material describes actual practice at [[WP:RM]] for 15 years, and actual requirements of various naming conventions (e.g. [[WP:USPLACE]]). Attempts to delete it are based on lack of basic understanding of the word "disambiguation" (it means "to resolve ambiguity"), patently false claims that previous discussion did not happen and that consensus wasn't established, and a minority, extremist view that [[WP:CONCISE]] trumps all other [[WP:CRITERIA|article naming criteria]] in every case, no matter what, despite the clear wording of the [[WP:AT]] policy. The RfC falsely paints a picture of a slow editwar. Actual review of the history shows two back-to-back consensus discussions, two different attempts to by parties that the RfC falsely paints as opponents to integrate the material ''into [[WP:AT]] policy itself'', normal [[WP:BRD]] process and revision, 8 months of acceptance, the two drive-by attempts at deletion predicated on false claims and unawareness of previous discussion, which were reverted by multiple parties. See [[#Discussion (disambiguation)]] for details. This RfC, whatever its intent, would reverse much longer-standing portions of multiple stable naming conventions like USPLACE and [[WP:USSTATION]], just for starters, yet none of the affected pages were notified. Three quarters of a year of stability is plenty evidence of consensus, especially after three consensus discussions refined the material to its present state. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 16:04, 25 March 2016 (UTC)</p>
*'''Recognize that disambiguation is more than one thing'''. Keep the guidance, as it deters those who try to use the omission (of recognition of this common practice of making titles non minimally short in order to make them more precise and less ambiguous) to drive toward a precision-is-bad minimality. [[Special:Contributions/2620:0:1000:110A:71BE:75D9:749D:32C9|2620:0:1000:110A:71BE:75D9:749D:32C9]] ([[User talk:2620:0:1000:110A:71BE:75D9:749D:32C9|talk]]) 19:42, 25 March 2016 (UTC)
::That IP is me. Sorry for forgetting to log in, and expressing myself so poorly. The point is that disambiguation of this "unnecessary" sort ''is used'', widely, in wikipedia, and is even encouraged in various naming guidelines and conventions, for the purpose of supporting the [[WP:CRITERIA]] or precision and recognizability. Those who argue against this use of disambiguation seem to want to take a very narrow view of what ambiguty is, and put zero value on precision. This approach is epitomized by the decade-long campaign of B2C for "title stability", described by him at [[User:Born2cycle#A_goal:_naming_stability_at_Wikipedia]], where he espouses moving toward a system of unambiguous rules, essentially removing from editors the discretion to make titles more precise or less ambiguous than the shortest possible title that does not have a name conflict. To support this approach he has spent years rewording the recognizability, precision, naturalness, and consistency criteria to essentially minimize their value, leaving concisenss as the main criterion. I find this approach abhorrent. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 16:44, 26 March 2016 (UTC)
:::There is ambiguity, and there is ambiguity that is relevant to [[WP:DISAMBIGUATION]]. They are not the same. Don't conflate them. The only ambiguity that has ever been relevant to [[WP:DISAMBIGUATION]] is when two are more titles on WP share the exact same [[WP:COMMONNAME]]. --[[User:Born2cycle|В²C]] [[User_talk:Born2cycle#top|☎]] 21:33, 27 March 2016 (UTC)
::::See dictionary material I helpfully provided for you. What you just posted doesn't even parse. Disambiguation is removal of ambiguity. All ambiguity is relevant to disambiguation, and all disambiguation is relevant to ambiguity. ''Disambiguation'' doesn't magically refer to "only the ambiguity I want it to mean". You don't get to make up your own version of the language on the fly. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 21:00, 1 April 2016 (UTC)
*'''No guidance''' from disambiguation should be created for article titles generally. If someone is looking for information about the Flemish Goose, which is very large and sometimes referred to as the Flemish Giant, then it is good to have the search box suggesting "Flemish Giant rabbit" as the only possibility before the person clicks and starts reading and is disappointed. Ditto for the Flemish Giant cross-stitch pattern. A recent example of a too-short page title that I came across was [[Hybrid name]], which I moved to [[Hybrid name (botany)]] because on the talk page are such comments as "Why is this article written entirely from the point of view of plants, as if hybrid animals don't exist? We need to redress the balance." and the page itself had a tag "The examples and perspective in this article may not include all significant viewpoints. Please improve the article or discuss the issue. (May 2010)". The situation has clearly confused a few readers because although hybrid animals such as [[Liger]]s do exist, there is no special way of naming them, whereas for plants there is a detailed set of rules for creating scientific names. [[User:Sminthopsis84|Sminthopsis84]] ([[User talk:Sminthopsis84|talk]]) 20:58, 25 March 2016 (UTC)
*'''Retain guidance as it stands''' - This isn't even a properly presented RfC. What is the problem with the current guidelines and why does it need to be re-evaluated per [[WP:PG]]? All I'm seeing here is [[WP:JUSTDONTLIKEIT]] or something for the DRN (which would be rejected). --[[User:Iryna Harpy|Iryna Harpy]] ([[User talk:Iryna Harpy|talk]]) 21:53, 25 March 2016 (UTC)
*'''No guidance.''' I feel that this sort of guidance should be integrated into [[WP:AT]] itself, if ever. I've been here on Wikipedia for a long time and I've always understood the [[WP:DAB]] guideline to only apply whenever two or more articles have ambiguous titles, and not merely because a non-ambiguous title ''sounds'' ambiguous. So such additional guidance that touches singularly on precision should be placed into [[WP:AT]], where a more holistic look at the 5 criteria of good article titles should lead to better titles. Otherwise, the guidance placed on [[WP:DAB]] will seek to emphasize precision over the other criteria. —[[User:Seav|seav]] ([[User talk:Seav|talk]]) 03:26, 26 March 2016 (UTC)
*'''Injection of some facts and reliable sources''', since at least half the respondents here don't seem to understand what "disambiguate" means. It is not a made-up Wikipedian neologism, for "resolve a title conflict between two articles" (resolving such conflicts is simply the most {{em|common}} use of disambiguation on WP; it has never, in the entire history of the project, been the only one).
*# Definition of ''disambiguate'' at Dictionary.com (''Random House Dictionary'' [US] and ''Collins English Dictionary'' [UK]): ''RH'': "to remove the ambiguity from; make unambiguous: ''In order to disambiguate the sentence 'She lectured on the famous passenger ship,' you'll have to write either 'lectured on board' or 'lectured about.'''"; ''Collins'': "to make (an ambiguous expression) unambiguous".[http://www.dictionary.com/browse/disambiguate?s=t]<br />Definition of ''ambiguous'': ''RH'': "1. open to or having several possible meanings or interpretations; equivocal: ''an ambiguous answer''; 2. ''Linguistics.'' (of an expression) exhibiting constructional homonymity; having two or more structural descriptions; 3. of doubtful or uncertain nature; difficult to comprehend, distinguish, or classify: ''a rock of ambiguous character''; 4. lacking clearness or definiteness; obscure; indistinct: ''an ambiguous shape; an ambiguous future.''" ''Collins'': "1. lacking clearness or definiteness; obscure; indistinct; 2. difficult to understand or classify; obscure."[http://www.dictionary.com/browse/ambiguous]
*# Definition of ''disambiguate'' at OxfordDictionaries.com [UK & US]: "Remove uncertainty of meaning from (an ambiguous sentence, phrase, or other linguistic unit): ''<nowiki />'word senses can be disambiguated by examining the context'<nowiki />''&thinsp;".[https://www.oxforddictionaries.com/definition/english/disambiguate?q=disambiguation#disambiguate__8][https://www.oxforddictionaries.com/definition/american_english/disambiguate]<br />Definition of ''ambiguous'': "(Of language) open to more than one interpretation; having a double meaning: ''<nowiki />'the question is rather ambiguous'<nowiki />'', ''<nowiki />'ambiguous phrases'<nowiki />''&thinsp;".[https://www.oxforddictionaries.com/definition/american_english/ambiguous#ambiguous__2][https://www.oxforddictionaries.com/definition/english/ambiguous]; "Not clear or decided".[https://www.oxforddictionaries.com/definition/english/ambiguous]. Note that the definition some people want to apply here as if it were the only one does not appear to be a language-related one: "Unclear or inexact because a choice between alternatives has not been made: ''<nowiki />'this whole society is morally ambiguous'<nowiki />'', ''<nowiki />'the election result was ambiguous'<nowiki />''&thinsp;".[https://www.oxforddictionaries.com/definition/american_english/ambiguous#ambiguous__2]
*# Definition of ''disambiguate'' at Dictionary.Cambridge.org [UK & US]: "{{sc1|specialized}} to show the ​differences between two or more ​meanings ​clearly: ''Good ​dictionary ​definitions disambiguate between ​similar ​meanings.''"[https://dictionary.cambridge.org/us/dictionary/english/disambiguate]<br />Definition of ''ambiguous'': "having or ​expressing more than one ​possible ​meaning, sometimes ​intentionally: ''The movie's ending is ambiguous.'' ... ''His ​reply to my ​question was ​somewhat ambiguous.'' ''The ​wording of the ​agreement is ambiguous.'' ''The ​government has been ambiguous on this ​issue.''"[https://dictionary.cambridge.org/us/dictionary/english/ambiguous] "having more than one possible ​meaning, and therefore likely to cause confusion: ''Many ​companies are ​appealing against the ​ruling, because the ​wording is ambiguous.''"[https://dictionary.cambridge.org/us/dictionary/english/ambiguous]{{rp|in "Business" tab}}
*# Definition of ''disambiguate'' at Merriam-Webster.com/dictionary [US]: "to establish a single semantic or grammatical interpretation for".[http://www.merriam-webster.com/dictionary/disambiguation]<br />Definition of ''ambiguous'': "able to be understood in more than one way : having more than one possible meaning; not expressed or understood clearly; doubtful or uncertain especially from obscurity or indistinctness: ''eyes of an ambiguous color''; capable of being understood in two or more possible senses or ways: ''an ambiguous smile''; ''an ambiguous term''; ''a deliberately ambiguous reply''.[http://www.merriam-webster.com/dictionary/ambiguous] "Not expressed or understood clearly".[http://www.learnersdictionary.com/definition/ambiguous]{{rp|Learner's Dictionary subsite}}
:Shall we continue? <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 04:51, 26 March 2016 (UTC)
::I think we all know what "disambiguation" means in the real world – however, I think it's one of those words, like "notability", that has acquired a very specific meaning in the world of Wikipedia. In the four years I've been here, I've only ever seen the word used in relation to article-title conflicts. [[WP:DAB]], since [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Disambiguation&oldid=45734 its inception], has only ever been about article-title conflicts, and it's the broadening of the scope of this guideline that I object to. [[User:DoctorKubla|DoctorKubla]] ([[User talk:DoctorKubla|talk]]) 18:57, 26 March 2016 (UTC)
:::[[WP:REALWORLD]]. The nature of the discussion has made it very, very clear that "we" did not all know what ''disambiguation'' means at all. But let's back up and just look at [[WP:POLICY]]: {{tq|"Wikipedia policy and guideline pages describe its principles and best-agreed practices. Policies explain and describe standards that all users should normally follow, while guidelines are meant to outline best practices for following those standards in specific contexts. Policies and guidelines should always be applied using reason and common sense. ... Guidelines are sets of best practices that are supported by consensus. Editors should attempt to follow guidelines, though they are best treated with common sense, and occasional exceptions may apply."}} There are entire naming convention guidelines that depend on this kind of precision disambiguation, and it is regularly performed at [[WP:RM]]; the "occasional exceptions [that] may apply" are so common they've often become codified as guidelines themselves! Ergo it has consensus, and it should be documented properly. {{em|It does not matter}} that the current draft of the [[WP:Disambiguation]] page only addresses title-collision disambiguation. It is {{em|not}} the only kind of disambiguation we do, and it never has been. We can wikilawyer for another year about what that draft says, and it will never change the facts about what Wikipedia actually {{em|does}}. There is no conflict of any kind between the wording you want to remove and actual WP practice, but there would be in removing it. By contrast, changing the [[WP:Notability]] guideline to use a broader definition of the word ''notable'' would instantly and radically conflict with actual WP practice. ''Notability'' here is a precise [[term of art]] with a particular definition laid out in detail at the top of that guideline; it's a criterion that causes results (e.g. article deletion). ''Disambiguation'' is simply a procedure, an action taken as a result of the application of other [[WP:CRITERIA|criteria]], including [[WP:PRECISION|precision]] and [[WP:RECOGNIZABILITY|recognizability]], after balancing their interaction with others, like [[WP:CONCISE|conciseness]]. It's an apples and oranges comparison, except in that [[WP:Notability]] presently directly reflects WP consensus and best practices, and [[WP:Disambiguation]] did not until this was fixed 8 months ago; before then, and without the sentence you want to remove for no clearly articulated reason, the page reflects only some of standard WP disambiguation operating procedures, and pretends the others don't exist. All because people don't know what the damned word means. You're trying to disprove my point that some people are mistakenly treating "disambiguation" as some kind of special Wikipedianism, by trying to show that it's some kind of special Wikipedianism. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 22:35, 26 March 2016 (UTC)
::::Just because some people sometimes justify title choices based on real world ''disambiguation'' does not mean [[WP:DISAMBIGUATION]] is, should be, or ever was about real world ''disambiguation''. Whether real world ''disambiguation'' should continue to be tolerated as a factor to consider in title selection is within the domain of [[WP:AT]], not [[WP:D]]. --[[User:Born2cycle|В²C]] [[User_talk:Born2cycle#top|☎]] 21:33, 27 March 2016 (UTC)
:::::Since you're just repeating yourself, I will as well: {{tq|See dictionary material I helpfully provided for you. What you just posted doesn't even parse. Disambiguation is removal of ambiguity. All ambiguity is relevant to disambiguation, and all disambiguation is relevant to ambiguity. ''Disambiguation'' doesn't magically refer to "only the ambiguity I want it to mean". You don't get to make up your own version of the language on the fly.}} <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 21:30, 1 April 2016 (UTC)
::::::[[WP:DISAMBIGUATION]] deals with how to resolve ambiguities among two or more titles of actual WP articles. When no actual ambiguities exist between actual WP article titles, then there is no need for [[WP:DISAMBIGUATION]]. Period. #NotThatDifficult. --[[User:Born2cycle|В²C]] [[User_talk:Born2cycle#top|☎]] 20:15, 7 April 2016 (UTC)
* '''No guidance'''. [[WP:DISAMBIGUATION]] has always been, and should always remain, limited to situations where two or more actual articles on WP share the same [[WP:COMMONNAME]]. --[[User:Born2cycle|В²C]] [[User_talk:Born2cycle#top|☎]] 21:33, 27 March 2016 (UTC)
* '''Delete''' per [[WP:IAR]] and [[WP:CREEP]]. It generally doesn't matter what the exact title of an article is and arguing about such titles is disruptive. [[user:Andrew Davidson|Andrew D.]] ([[user talk:Andrew Davidson|talk]]) 18:25, 30 March 2016 (UTC)
*'''No guidance'''. Disambiguation was intended only to be used where multiple articles shared the same name. Preemptive disambiguation is unnecessary disambiguation and shouldn't be promoted. '''<span style="border: 1px blue solid;background:Cyan">[[User:Calidum|<font color="#4863A0">Calidum</font>]]&nbsp;[[User talk:Calidum|<font color="#A18648">¤</font>]]</span>''' 02:14, 31 March 2016 (UTC)
::Whose intention are you referring to? What about all the cases where it is used to reduce ambiguity and improve precision? Are you saying just define those as something different, not disambiguation? Or you're saying those are bad and we need to stop making titles more precise than the shortest possible title? [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 02:17, 31 March 2016 (UTC)
:::{{U|Dicklyon}}, I can't speak for {{U|Calidum}}, but conflating the WP and general meanings of "ambiguous" and "disambiguation" is not helpful, so I'll be precise about which one I mean. The point is that the merits of whether ''general ambiguity'' is a factor to consider when there is no actual ''WP ambiguity'' with another title is not a matter of [[WP:DISAMBIGUATION]], but something for [[WP:AT]] to address. Perhaps it can be justified by [[WP:PRECISION]], as you say. But unless there is an actual url conflict to resolve between two or more article titles, it's not a [[WP:DISAMBIGUATION]] situation, period. That's the point here, and therefore the wording in question has no place on [[WP:DISAMBIGUATION]]. --[[User:Born2cycle|В²C]] [[User_talk:Born2cycle#top|☎]] 00:42, 1 April 2016 (UTC)
::::I hear what you're saying. But in the past you and others have pointed to this page to justify making titles less precise and more ambiguous. So having this page acknowledge that removing ambiguity has roles other than preventing article name collisions seems like a good thing that should stay. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 02:30, 1 April 2016 (UTC)
:::::{{ping|Dicklyon}} Just asking for my own education – could you point me to an example of a discussion in which [[WP:DAB]] was cited as a justification for making an article title less precise? [[User:DoctorKubla|DoctorKubla]] ([[User talk:DoctorKubla|talk]]) 09:48, 1 April 2016 (UTC)
::::::Here's one that opened just today: [[Talk:...Re_(film)#Requested_move_01_April_2016]]. It doesn't explicitly cite [[WP:DAB]] but relies on the theory that only name collisions matter and that ambiguity is otherwise fine. As you can see, editors other than Dohn joe are pretty much unanimous against this interpretation; maybe some of the other "no guidance" voices here will join him? [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 17:02, 1 April 2016 (UTC)
::::::Another open case, not explicitly citing [[WP:DAB]], is [[Talk:Ron_Walsh_(footballer)#Requested_move_13_March_2016]]; many primarytopic grabs are of this form; treat the disambiguating information as negative and argue that name collision can be avoided in other ways, so we must move to the more ambiguous title. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 17:23, 1 April 2016 (UTC)
:::::::And here's a classic example from way back in 2008, with multiple editors on each side of the question: [[Talk:Bronson_Avenue_(Ottawa)#Requested_move]]; illustrating that editors often want to reduce ambiguity (disambiguate) even when there are not title collisions, and other editors point here and argue that's not OK per disambiguation guidelines. This one went on at great length and closed as "no consensus", meaning that the attempt to make the titles less precise and more ambiguous by citing "Unnecessary disambiguation" failed in that multiple-RM case. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 01:18, 2 April 2016 (UTC)


5.) Has released two or more albums on a major record label or on one of the more important indie labels (i.e., an independent label with a history of more than a few years, and with a roster of performers, many of whom are independently notable).
*'''Stop circumventing policy''': '''Keep''' what became somewhat stable and take this up through the proper venue for making changes to policies and guidelines, that only in part includes this discussion. ''A problem I have is that there are errors in thinking and procedure''.
**'''Note to closing admin''': We have long established procedural policy covered under [[Wikipedia:Policies_and_guidelines#Proposals|Proposals]] and [[Wikipedia:Policies_and_guidelines#Good practice for proposals|Good practice for proposals]] for making changes to policies and guidelines.
:Exemptions like boldly making changes that ''could'' be accepted by a broad community consensus, seems to only make confusion and possible perennial discussions on what should be more stable far more often than not. Changing policies and/or guidelines should not be done by edit warring, the apparent practice of BRD, or these "local" only discussions to definitively solve such local editing solutions concerning policies and guidelines. A continued practice of by-passing a procedural policy (protection for any long accepted broad community consensus) does not make it proper, makes a laughing stock of our policies and guidelines, and allows said policies and guidelines to be changed on a whim.
:I am in support of '''retaining what is on the page''' because we can not right an error by a wrong procedure any more than we should attempt to edit war to create policy. I think this should be closed as consensus to move forward and follow procedure (to be brought up on the talk page), or an admin could move the discussion to the talk page so it can be listed everywhere relevant. The end result would mean leaving things as they are and settling it the right way. This would also reassert that policy should be followed. I would think, from this point, that only Wikilawyers would oppose following policy. [[User:Otr500|Otr500]] ([[User talk:Otr500|talk]]) 06:31, 31 March 2016 (UTC)
::{{U|Otr500}}, I, for one, cannot understand what you're saying, specifically what reasoning justifies "retaining what is on the page". What is on the page is the result of edit warring; the point of this discussion is to decide in a more thoughtful process whether it should be retained or not. This discussion has been publicized at the talk page; previous discussions there did not lead to consensus, so someone thought maybe we could have a more productive discussion here. Again, I don't understand what exactly you're saying, much less why. Please clarify. --[[User:Born2cycle|В²C]] [[User_talk:Born2cycle#top|☎]] 00:34, 1 April 2016 (UTC)
<!-- BEGIN Otr500's long, multi-paragraph post with differing indentation levels, ending with:
[[User:Otr500|Otr500]] ([[User talk:Otr500|talk]]) 10:22, 1 April 2016 (UTC) -->
:@ B2C: Read the procedural policy. Because ''you can't here me'' (I don't understand "exactly" what you are saying) does not mean that others can't. I thought listing in two places, in bold, would be pretty clear as I didn't use any big words. '''Keep''' seemed pretty clear and '''retaining what is on the page''' equally understandable so I will assume (and hope) a miscommunication would be in the reasoning.<!-- This is all part of Otr500's long, multi-paragraph post, ending with:
[[User:Otr500|Otr500]] ([[User talk:Otr500|talk]]) 10:22, 1 April 2016 (UTC) -->
**''"If consensus for broad community support has not developed after a reasonable time period, the proposal is considered failed. If consensus is neutral or unclear on the issue and unlikely to improve, the proposal has likewise failed."''. A discussion to a conclusion, that might involve an admin, would normally stop edit warring. Editors that find themselves in such a position, especially seasoned editors here to build a good encyclopedia, should self include [[Wikipedia:Edit_warring#Other_revert_rules]] to include ''1RR (one-revert rule) or 0RR (zero-revert rule)'' and not use reverts to include team reverts to push a POV. I could expect this on articles but policies and guidelines should enjoy more prudence.
:"Stop" means exactly what it states and I can provide a definition if that is unclear. Any "edit warring" began at a point and I saw nobody argue with what {{Ping|SMcCandlish}} stated that there were 8 months of stability. Maybe you missed that or didn't understand, and IF I missed something specifically please point it out instead of not understanding everything. I am stating: '''There should be no edit warring on policy changes or attempted changes.''' Clear on that? If not you might consider reading the procedural policy again.
:To argue that disambiguation has only one meaning does not make it true and that it should stand alone is not policy. Policies should not conflict nor should guidelines conflict with policy. IF [[WP:AT]] needs to mention disambiguation and point to a guideline, to make better article titles, then what in the world is the problem with that. What we have is editors that sometimes have a POV and sometimes promote it the tenth degree and Wikipedia enhancement be damned.
:Support for the below mentioned [[Flemish Giant]] over [[Flemish Giant rabbit]] has proven in many article discussions to be against consensus. To support [[Flemish Giant (rabbit)]] has also be shown to largely be against consensus preferring natural over parenthetical disambiguation. To try to ride a dead horse that disambiguation means only one thing just does not make it fact.
:There is no need to change [[Belgian Hare]] but [[Blanc de Bouscat]] would be vague to the average reader. It has become practice (like it or not) to clarify titles like this by adding the breed and without the parenthetical disambiguation. Brackets around a word is not the only determining factor of disambiguation. Die-hard Britannica fans do not like this but Wikipedia does not have to be a sister site. Discussions have shown consensus has moved away from Britannica style parenthetical disambiguation, preferring to add the breed as part of the title, and to naturally ''disambiguate'' to prevent ambiguity and have [[WP:AT#Consistency within articles|consistency within articles]], when we are [[WP:AT#Deciding on an article title|deciding on an article title]]. Maybe we should examine the little active but relevant essay [[Wikipedia:Consistency in article titles]]? This does not mean that such practice of using parenthetical disambiguation is bad, or against policy, but used as an exception.
<!-- This is all part of Otr500's long, multi-paragraph post, ending with:
[[User:Otr500|Otr500]] ([[User talk:Otr500|talk]]) 10:22, 1 April 2016 (UTC) -->
:Sometimes accepted practice (by consensus) already shows the direction of community consensus, without trying to confuse the issue. Adding clarity so that new articles can follow accepted practice without large debates is not a bad thing. This prevents (as mentioned in above discussions) titles like [[Beveren (rabbit)]] (unassessed article with no talk page activity at this time), [[British Lop]] (stub class that is not a rabbit but a pig), [[English Lop]] (that is a rabbit and not a pig), [[French Lop]] (that is a rabbit), from [[Lop Nur]], that is not a rabbit or sheep but a lake, and so articles like [[Welsh Mountain sheep]] are more clear (less vague) and differentiate (take away ambiguity that is still to disambiguate) a mountain from sheep.
:Real world versus Wikipedia world: It doesn't matter because we are not talking animated or other world characters versus real world people. We are talking clarity versus unclear, precise versus concise, parenthetical disambiguation verses natural ''disambiguation''. Leaning towards concise verses leaning towards precision. This should not be a battle. We use balance to name articles, as well as source and community consensus, and sometimes ''leaning'' one way or the other is not a bad thing, actually justifiable, and adding article consistency among titles helps and carries broad community consensus. Disambiguation, in the form of adding a word for clarity, does not mean we are promoting precision over concise. It means we are adding some precision so that the precise title name is more clear and less vague, and follows other like article naming. It does not matter how much we wikiLawyer this it is still disambiguation but I am sure we must because that is what lawyers have to do right?
:Mr. B2C stated he can not understand what I am saying, and I hope not because of any personal inabilities. This discussion should be on the relevant talk page. The procedural policy, and I will type slow for clarity, states "''Authors can request early-stage feedback at Wikipedia's village pump for idea incubation and from any relevant WikiProjects''. Amendments to a proposal can be discussed on its talk page."'''. "'''start an RfC for your policy or guideline proposal ''in a new section on the talk page'', and include the "rfc|policy" tag...". ''"The "proposed" template should be placed at the top of the proposed page; this tag will get the proposal properly categorized"''. These are ways to prevent edit warring and discussions from taking place, all over the place, as well as to ensure broad community consensus is followed, and so that changes made to policy by consensus is transparent, being on the relevant talk page. Listing a discussion here, as well as other relevant places, would be to point to a discussion on that talk page not have continued splintered discussions in many places.
:Or; we can just make this a perennial discussion to be brought up over and over again. A lot of times this does not deter community practices as reflected by broad community consensus, no matter how much we discuss a supposed issue. Here is some fantastic reading: [[Wikipedia:Edit_warring#What to do if you see edit-warring behavior|'''What to do if you see edit-warring behavior''']] and [[Wikipedia:Edit_warring#How experienced editors avoid becoming involved in edit wars|'''How experienced editors avoid becoming involved in edit wars''']]. That is why I stated that a discussion here is not a definitive solution but to gather consensus (not battle) that should be continued on the talk page to effect broad community consensus continuation or change. [[User:Otr500|Otr500]] ([[User talk:Otr500|talk]]) 10:22, 1 April 2016 (UTC)
<!-- END Otr500's long, multi-paragraph post -->
::To compress and get to what I think the gist is of Otr500's multi-paragraph, multi-indent-level post above, and cut through a lot of the other chatter here: Eight months ago, WP:DAB was updated to describe actual practice, which is what guidelines are form as a matter of [[WP:POLICY]]. There were multiple BRD discussions about the then-long wording. The language was refined, and a short version (the sentence at issue here) was retained. Two thirds of a year later, two editors (B2C and Dohn joe) attempted to delete it on the patently false basis that it had not been discussed. Not only are their facts wrong, they cannot even formulate a cogent reason why it should be removed, just [[hand-wave]] a lot, in ways that have confused a few other people into supporting removal of it from its present location, though plenty of others support its retention. Notably, many of those who don't want to keep it where it is right now think it should be moved into [[WP:AT]] policy instead. This was also discussed 8 months ago at [[WT:AT]] and the decision was to not merge it into AT policy. This is now stable guideline language. A proper closure analysis of this confused and confusing pseudo-RfC should conclude with no consensus to remove the material (since the arguments for keeping it are valid and those for removing it are not, ergo the original consensus to include the material has not changed), and no consensus to merge it into AT policy, because that idea has already been rejected, and no new rationale for why this should rise to {{em|policy}} level has been provided, so again consensus has not changed. There are thousands of things in various guidelines that are {{em|relevant}} to various policies but which remain in guidelines and are not merged into policies, because they are not policy material, but guideline material. This is not mystically different somehow. In absence of any showing that the material {{em|does not}} actually describe long-established [[WP:RM]] and disambiguation practice, which it clearly does, the sentence {{strong|remains in the guideline}}. Suggesting that it can be removed when it was arrived at through multiple consensus discussions, now that a new discussion to possibly move it into policy fails to come to consensus for that idea, would be patent [[WP:GAMING]]. One could just as easily propose that, say, [[WP:Citing sources]] should be merged into [[WP:V]] policy, and then when that proposal failed to gain consensus, delete the guideline on citing sources! WP does not work that way. Nothing works that way. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 21:30, 1 April 2016 (UTC)
* [[WP:Disambiguation]] overreaches with respect to minimalist disambiguation, at the expense of the reader, at the expense of naming criteria "recognizability", "precision" and "consistency". If inclusion of a parenthetical term helps, it should be used, subject to balancing recognizability, naturalness, precision, concision, and consistency, and other good things even if not documented. Parentheses should be ''avoided'', but inclusion does not make [[WP:Disambiguation]] a trump card. --[[User:SmokeyJoe|SmokeyJoe]] ([[User talk:SmokeyJoe|talk]]) 01:05, 1 April 2016 (UTC)
** Aye. I most cases where this comes up, we use [[WP:NATURALDIS|natural disambiguation]] simply because such a phrase exists in the reliable sources already, and the policy tells use to favor natural over parenthetic disambiguation when possible. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 21:30, 1 April 2016 (UTC)
*'''Retain guidance''' – A title like "[[Flemish Giant]]" benefits no one. Most importantly, it does not benefit the reader, because it does not clearly define the subject. Shorter titles are not always better. [[WP:AT]] does not suggest this, but certain editors continue to the push this notion to the detriment of our readers. It is important that the disambiguation policy does not result in an automatic removal of bits of titles that do not serve to disambiguate from other Wikipedia articles, but ''do'' serve to clearly define the topic of the article in line with [[WP:AT]], as Mr Lyon suggested above. The guidance as it stands allows for this to be made clear. [[User:RGloucester|<span style="font-family:Monotype Corsiva;font-size:12pt;color:#000000">RGloucester </span>]] — [[User talk:RGloucester|☎]] 02:45, 1 April 2016 (UTC)
*'''Retain the guidance'''. There has been a reluctance among some of the players to see disambiguation in terms of our readers. B2C's long campaign for a narrow algorithm-like solution was an utter disaster. [[User:Tony1|<font color="darkgreen">'''Tony'''</font >]] [[User talk:Tony1|<font color="darkgreen">(talk) </font >]] 13:42, 1 April 2016 (UTC)
** Just for those unaware of it, three times (at least) Born2cycle has agitated for concision-above-all-other-concerns changes to article titles policy and RM procedures, citing personal essays of his on the topic as if they were guidelines. In all three cases [[WP:MFD]] userspaced them as anti-policy nonsense [https://en.wikipedia.org/wiki/Wikipedia:Miscellany_for_deletion/Wikipedia:Concision_razor], [https://en.wikipedia.org/wiki/Wikipedia:Miscellany_for_deletion/Wikipedia:Yogurt_Rule], [https://en.wikipedia.org/wiki/Wikipedia:Miscellany_for_deletion/Wikipedia:Unnecessary_disambiguation]. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 21:30, 1 April 2016 (UTC)


6.) Is an ensemble that contains two or more independently notable musicians, or is a musician who has been a reasonably prominent member of two or more independently notable ensembles. This should be adapted appropriately for musical genre; for example, having performed two lead roles at major opera houses. Note that this criterion needs to be interpreted with caution, as there have been instances where this criterion was cited in a circular manner to create a self-fulfilling notability loop (e.g., musicians who were "notable" only for having been in two bands, of which one or both were "notable" only because those musicians had been in them.)
*'''Data point''' Life is too precious to read all the above, but I once was in an argument over ''Memorial Hall (Harvard University)''. This other editor said it should be simply ''Memorial Hall'' since, at that moment, no other Memorial Hall had an article -- and apparently guidelines supported that knuckleheaded approach. Anything that remedies that would be welcome. '''[[User:EEng#s|<font color="red">E</font>]][[User talk:EEng#s|<font color="blue">Eng</font>]]''' 19:53, 2 April 2016 (UTC)
::This reminds me of [[National Pension Scheme]]. (Surprise! It's specifically about India.) [[User:Huwmanbeing|╠╣uw]]&nbsp;<span style="font-size:smaller"><nowiki>[</nowiki>[[User talk:Huwmanbeing|talk]]<nowiki>]</nowiki></span> 10:22, 12 April 2016 (UTC)
:::Per [[WP:NATURAL]] policy, the proper titles would use natural disambiguation as first choice. But in both cases ("Harvard Memorial Hall", "Indian National Pension Scheme"), it results in a new ambiguity (which I needn't spell out here). The obvious solution is [[WP:COMMADIS]]: "Memorial Hall, Harvard" (adding "University" seems superfluous, per [[WP:CONCISE]]), and "National Pension Scheme, India", or [[WP:DESCRIPTDIS]] in the latter case, "National Pension Scheme of India". Both "Memorial Hall, Harvard" and "National Pension Scheme of India" actually border on alternative NATURALDIS, and are attested in sources. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 17:04, 17 May 2016 (UTC)
*'''Retain the guidance''' since the lengthy discussion above and below has convinced me that this is useful guidance to editors in encouraging a better and less frustrating experience for our readers. [[User:BushelCandle|BushelCandle]] ([[User talk:BushelCandle|talk]]) 06:59, 3 April 2016 (UTC)
*'''No guidance''' as I agree wholeheartedly with DoctorKubla. --[[User:Tavix| <span style="color:#000080; font-family:georgia">'''T'''avix</span>]] <sup>([[User talk:Tavix|<span style="color:#000080; font-family:georgia">talk</span>]])</sup> 12:24, 5 April 2016 (UTC)


These appear to have been put together by a very small number of editors over a decade ago and hasn't seen much change since then and I feel it's much more lenient than just about anything else. This SNG defines a "label" that has been around for over "a few years" that has a roster of performers as "important". So, any group of people who have released two albums through ANY verifiable label that has exited for more than a few year can end up being kept and this isn't exactly in line with GNG. I believe a discussion needs to be held in order to bring it to GNG expectations of now.
*'''Retain the guidance'''. I am also irked by the [[Memorial Hall (Harvard University)]] example provided by EEng and similar ones – articles about obscure things with common-sounding (i.e. [[:wikt:ambiguous]]) names ''do'' benefit from some extra [[WP:PRECISION]]. Doing otherwise easily confuses the readers (as the context is often not enough to quickly conclude what the topic is, and matches displayed in the search box do not provide any hint about the topic) and editors (quite easy mislinking) alike. Of course, case-by-case examination is always welcome, but we do not apply [[WP:CONCISE]] at all costs. [[User:No such user|No such user]] ([[User talk:No such user|talk]]) 15:35, 6 April 2016 (UTC)
**I, for one, do not call for applying [[WP:CONCISE]] ''at all costs''. To the contrary. I call for applying it primarily as a "tie breaker". When considering all other [[WP:CRITERIA]] there is no clear answer, then go with the more concise one. It is that simple. But the main point her is that all this is [[WP:AT]] consideration; it has nothing to do with [[WP:DISAMBIGUATION]]. --[[User:Born2cycle|В²C]] [[User_talk:Born2cycle#top|☎]] 20:07, 7 April 2016 (UTC)


[[User:Graywalls|Graywalls]] ([[User talk:Graywalls|talk]]) 06:17, 30 October 2024 (UTC)
*'''Retain the guidance.''' It's reasonable to note that some titles may be ambiguous or likely to confuse a reader even if they don't exactly match any other titles, and I'm fine with having at least a modicum of text into the guideline to explain this. I understand that some prefer the term "disambiguation" to be defined more narrowly as just the mechanical process of distinguishing between otherwise identical Wikipedia titles, but I don't think that's particularly useful. There can be (and often is) a difference between what's merely technically ambiguous and what's actually ambiguous, and the latter can be a valid consideration when determining the best title for our readers. [[User:Huwmanbeing|╠╣uw]]&nbsp;<span style="font-size:smaller"><nowiki>[</nowiki>[[User talk:Huwmanbeing|talk]]<nowiki>]</nowiki></span> 19:01, 11 April 2016 (UTC)
:Especially given how broadly the various criteria have been "interpreted" in deletion discussions, the best way to go about it is just to deprecate the whole thing. Rely on the GNG for band notability, and if that results in a heap of articles on ephemeral outfits, garage bands and local acts vanishing, huzzah. [[User talk:Ravenswing|'''<span style="background:#2B22AA;color:#E285FF"> '' Ravenswing '' </span>''' ]] 09:07, 30 October 2024 (UTC)
:The SNG isn't workable in the age of digital distribution. It's very easy to create "an independent label with a history of more than a few years". If someone wants to suggest a way to reform the SNG, I am open to solutions. But deprecation is a simple alternative if we can't. The GNG is always a good standard because it guarantees we have quality sources to write an article. [[User:Shooterwalker|Shooterwalker]] ([[User talk:Shooterwalker|talk]]) 14:22, 30 October 2024 (UTC)
:I was active in AfD discussions when NBAND was pretty new, and it was useful for dealing with a flood of articles about garage bands and such, but I think our standards in general have tightened up since then, and I agree it is time to review it. There is the possibility, however, that revising NBAND may require as much discussion as revising NSPORT did. [[User talk:Donald Albury|Donald Albury]] 17:49, 30 October 2024 (UTC)
::This sounds reasonable. I guess we need some concrete re-write suggestions to base an rfc on. [[User:Gråbergs Gråa Sång|Gråbergs Gråa Sång]] ([[User talk:Gråbergs Gråa Sång|talk]]) 18:17, 30 October 2024 (UTC)
:It sounds like you're assuming that NBAND is meant to be a substitute for the [[Wikipedia:General notability guideline]]. That's true for some [[WP:Subject-specific notability guidelines]] but not for all of them.
:I guess the underlying question is: Is there actual harm in having a permastub about a band that proves to be borderline in GNG terms? Consider this:
:{{tqb|"'''Alice and Bob''' are a musical duo in the [[science fiction]] genre.{{dummy ref}} They released their first album, ''[[Foo]]'', in 2019 and their second, [[Bar (album)|''Bar'']], in 2020. Both albums were released by [[Record Label]].{{dummy ref|2}} They are primarily known for singing during a [[Minor key|minor]] event.{{dummyref|3}}"}}
:I'm asking this because I think that the nature of sources has changed, particularly for pop culture, since NBAND and the GNG were written. We now have subjects that get "attention from the world at large", but which aren't the Right™ kind of sources and, while these Wrong™ sources definitely provide "attention", some of that attention might not provide biographical information (which means we're looking at a short article).
:For example, instead of getting attention in the arts section of a daily newspaper, they're getting attention from [[Anthony Fantano]] on YouTube. He's an important music critic,[https://www.nytimes.com/2020/09/30/arts/music/anthony-fantano-the-needle-drop.html] but I suspect that our knee-jerk reaction is "Pffft, just some YouTuber, totally unreliable". Consequently, we might rate a band that we theoretically intend to include ("attention from the world at large") as not meeting the GNG (because the whole field relies on the Wrong™ style of sources). [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 19:02, 30 October 2024 (UTC)
:Keep in mind that like most other notability guidelines, it is a presumed assumption that a topic is notable if it meets these criteria. If you do an exhaustive Before and demonstrate there is no significant coverage beyond the sourcing to satisfy there criteria, the article should still be deleted. None of the SNGs are geared towards preventing this type of challenge.<span id="Masem:1730316637166:WikipediaFTTCLNVillage_pump_(policy)" class="FTTCmt"> —&nbsp;[[User:Masem|M<span style="font-variant: small-caps">asem</span>]] ([[User Talk:Masem|t]]) 19:30, 30 October 2024 (UTC)</span>
::If we had to yield to presumptive notability about some random band because it released two albums with Backyard Trampoline Recordings established few years ago and had to do exhaustive search to disprove notability, we're getting setup for a situation where removal is 10x more challenging than article creation. So.. I see a great value in scrapping NBAND 5, and 6. [[User:Graywalls|Graywalls]] ([[User talk:Graywalls|talk]]) 00:47, 31 October 2024 (UTC)
:Welcome to [[WP:SNG]]s. As Masem said, they're supposed to be a rough idea of gauging notability before exhaustively searching for sources. But pretty much all of them have ended up being used as means to keep articles about trivial or run-of-the-mill subjects. [[User:Thebiguglyalien|<span style="color:#324717">The</span><span style="color:#45631f">big</span><span style="color:#547826">ugly</span><span style="color:#68942f">alien</span>]] ([[User talk:Thebiguglyalien|<span style="color:sienna">talk</span>]]) 19:37, 30 October 2024 (UTC)


Graywalls listed two criteria but the main discussion seems to be about the 1st (#5). I agree with Graywalls on that. With the evolution of the industry, the label criteria is no longer a useful indicator as it once was and IMO #5 should be removed or modified. Sincerely, <b style="color: #0000cc;">''North8000''</b> ([[User talk:North8000#top|talk]]) 19:13, 30 October 2024 (UTC)
*'''Change names''' The simplest thing to do would be to change the names. <small><span class="autosigned">—&nbsp;Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Shinyapple|Shinyapple]] ([[User talk:Shinyapple|talk]] • [[Special:Contributions/Shinyapple|contribs]]) 01:22, 30 April 2016 (UTC)</span></small><!-- Template:Unsigned --> <!--Autosigned by SineBot-->
:I agree, both those criteria should be scrapped. [[User:JoelleJay|JoelleJay]] ([[User talk:JoelleJay|talk]]) 22:21, 30 October 2024 (UTC)
:I've noticed that as well. I think #6 has some value still, while #5 is like saying an author who has published two or more books by a major publishing house is presumed notable. Way too low a bar without requiring some level of reception of those albums/books. ([[WP:NAUTHOR]] doesn't have that 2-book criteria, of course, just seems like parallel benchmarks.) [[User:Schazjmd|<span style="color:#066293;">'''Schazjmd'''</span>]]&nbsp;[[User talk:Schazjmd|<span style="color:#738276;">''(talk)''</span>]] 13:25, 31 October 2024 (UTC)
:: On the other hand, in this case, I suspect that an artist that "has released two or more albums on a major record label or on one of the more important indie labels" will in 99% of cases have enough coverage to clear the GNG bar. I'd like to see an example of one that doesn't. [[User_talk:Black Kite|Black Kite (talk)]] 13:29, 31 October 2024 (UTC)
:::The definition of important as said in #5 is "history of more than a few years, and with a roster of performers, many of whom are independently notable". This would mean that a garage band is notable, because they've released two CD-R albums on Rotten Peach Recordings which has been around for 3 1/2 years, has a roster of performers and some of whom have a Wikipedia page on them. Often time "notable" is determined by the presence of a stand alone Wikipedia page. When you look at the page, many band member pages are hopelessly non-notable, but removal takes an AfD. So a simple deletion can become a time consuming multi-step AfD. [[User:Graywalls|Graywalls]] ([[User talk:Graywalls|talk]]) 19:18, 31 October 2024 (UTC)
::: Here's a current AfD I am participating in where NBAND#5 was invoked to justify a keep. [[Wikipedia:Articles_for_deletion/Sons_of_Azrael_(3rd_nomination)]] [[User:Graywalls|Graywalls]] ([[User talk:Graywalls|talk]]) 19:24, 31 October 2024 (UTC)
:::: Not opining on that band's notability, but Metal Blade is a famous independent label that has existed for 42 years, has released material by ''very'' high-profile bands, and is distributed by Sony - it's not some one-person imprint operating out of their garage. [[User_talk:Black Kite|Black Kite (talk)]] 11:28, 1 November 2024 (UTC)
:::::I concur regarding that particular example.{{pb
}} Metal Blade is a big label, and not surprisingly notability was quickly demonstrated in the deletion discussion through citing reliable source coverage. And that's how #5 should work - artist is on a significant label, which suggests coverage exists. And then coverage is found.--[[User:3family6|<b style="color:navy">3family6</b>]] ([[User talk:3family6|<u style="color:black">Talk to me</u>]] &#124; [[Special:Contributions/3family6|<small style="color:purple">See what I have done</small>]]) 12:08, 16 November 2024 (UTC)
:::It's complicated - on the one hand, [https://www.cjr.org/analysis/music-journalism-access.php music publications are increasingly prioritizing their coverage toward Taylor Swift-level celebrities], so I am almost certain there are artists on major labels that might be examples -- major as in the Big 3. This is especially so for genres like country that publications don't cover as much - there are some big names on the roster of [https://www.warnermusicnashville.com/artist Warner Music Nashville] and also some not-so-big names.
:::The elephant in the room here is that entertainment journalism is in crisis mode right now, publications are operating on skeleton crews, and the range of coverage has narrowed dramatically. I encourage everyone taking part in this discussion to read the article I linked, there are a lot of assumptions being made about the way things work that aren't true. [[User:Gnomingstuff|Gnomingstuff]] ([[User talk:Gnomingstuff|talk]]) 20:30, 19 November 2024 (UTC)
*One suggestion I would add is to make these two criteria apply only to bands before a specific year, that year being where physical releases still dominated over digital sales. I don't know the exact year but I am thinking it's like around 2000 to 2010. There may still be older groups during the time of physical releases that don't yet have articles that would fall into one of these criteria. [[User:Masem|M<span style="font-variant: small-caps">asem</span>]] ([[User Talk:Masem|t]]) 20:02, 31 October 2024 (UTC)
*As someone who's had [[WP:DSMUSIC]] watchlisted for most of their editing history, and who tends towards deletion at that, I actually don't see much of a problem with these criterions. It certainly seems true that the majority of musicians who are signed to a label or a member of multiple bands with two other musicians who meet [[WP:GNG]] themselves meet GNG. I do think it is sometimes justified to accept less-than-GNG sourcing in articles where a SNG is met (see [[Wikipedia:Articles for deletion/John LeCompt]] for this as it applies to c6 specifically) and more importantly, NMUSIC contains language that allows deleting articles even where it is technically met (see [[Wikipedia:Articles for deletion/Rouzbeh Rafie]] for an extended argument about that. [[User talk:Mach61|Mach61]] 23:29, 31 October 2024 (UTC)
*I've understood these criterion to be supplementing GNG, that is, that if a band or individual artist meets one or more of these criterion, they *likely* are notable. However, in the past when I was a younger and less experienced editor, I think I did understand these as being additions or alternatives to GNG. So I think that should be clarified. This has come up on the deletion discussion for [[Jayson Sherlock]]. He is a member or former member of several very notable bands, and for that reason I presumed that he would easily have independent coverage about him specifically. However, to my surprise, there's only one interview of him in a reliable source that would provide notability (there's some interviews on personal blogs or minor sites that wouldn't be RS except for him making statements about himself). But at least one editor has used the above criterion to argue that the article should be kept.--[[User:3family6|<b style="color:navy">3family6</b>]] ([[User talk:3family6|<u style="color:black">Talk to me</u>]] &#124; [[Special:Contributions/3family6|<small style="color:purple">See what I have done</small>]]) 12:20, 1 November 2024 (UTC)
*:Just as an aside, interviews do not contribute to GNG unless they include secondary independent SIGCOV (such as a substantial background introduction by the interviewer). [[User:JoelleJay|JoelleJay]] ([[User talk:JoelleJay|talk]]) 15:39, 1 November 2024 (UTC)
::*Agreed. That's important to note. I was presuming such, and also why I wouldn't rely on a singular interview as the sole source for establish GNG.--[[User:3family6|<b style="color:navy">3family6</b>]] ([[User talk:3family6|<u style="color:black">Talk to me</u>]] &#124; [[Special:Contributions/3family6|<small style="color:purple">See what I have done</small>]]) 16:30, 1 November 2024 (UTC)
::That's how I see most SNGs (and the outliers ought to follow their lead). At the very least, we can clarify that NBAND is meant as an indicator for the GNG, and not a substitute. [[User:Shooterwalker|Shooterwalker]] ([[User talk:Shooterwalker|talk]]) 02:04, 2 November 2024 (UTC)
* As someone who thought the old NSPORTS was wildly overinclusive and needed cleanup... these NBAND guidelines don't seem that bad? If two plainly notable musicians were discovered to have done some obscure team-up in the 1970s, that does indeed seem to be a notable topic and useful to have linked somewhere, even if there isn't tons of info on this collaboration. It's worth mentioning because minor subtopics are often merged to the overarching topic (e.g. songs to the album), but there may not be a clear merge location for this if both parties were equal contributors, and a short separate article is an acceptable compromise. Similarly, the complaint about #5 seems to be about just how "indie" the hypothetical label is, but this seems like a solvable problem. If a band fails GNG, that implies that either their two albums really were from a very obscure indie outfit and thus also fail NBAND, or else that we have some sort of non-English sources issue where we may consider keeping on [[WP:CSB]] grounds (i.e. that sources probably ''do'' exist to pass GNG, but they're difficult to find, and we can trust they exist because this was a major and notable label releasing the band's work). About the only suggestion I can offer is that the comment in 6 about avoiding circular notability could probably be phrased in the sense of GNG, i.e. that the two notable musicians need to both meet GNG and then this will create a new, safe NBAND notability for their collaboration. [[User:SnowFire|SnowFire]] ([[User talk:SnowFire|talk]]) 17:36, 4 November 2024 (UTC)
*:The reverse situation, such as is currently being discussed at [[Wikipedia:Articles for deletion/Jayson Sherlock]], is one where you have someone who was/is in multiple notable bands, but doesn't have independent coverage about them as an individual person. -- [[User:3family6|<b style="color:navy">3family6</b>]] ([[User talk:3family6|<u style="color:black">Talk to me</u>]] &#124; [[Special:Contributions/3family6|<small style="color:purple">See what I have done</small>]]) 22:30, 7 November 2024 (UTC)
*Agreed with deprecation; "Rely on the GNG for band notability" is the correct answer. And is the correct answer for many other things about which we have SNGs that attempt to be alternatives to GNG. Perhaps the only justifiable one is [[WP:NACADEMIC]], because special considerations apply in that sphere (academics and other journal-publishing researchers are generally unknown the public and the public-facing media coverage like newspapers but may have major impacts in particular fields and on the world; what determines their influence level is primilar the frequency of citation of their work by other academics). No such special considerations apply with regard to bands or most other categories. We have some SNGs that are helpful because they are written to comply with GNG, to explain predictively what is most likely or unlikely to pass a GNG test at ANI, rather than trying to be an end-run around GNG. If we actually needed an SNG for bands and musicians, then the current SNG for them could be replaced by something like that. However, we don't actually need an SNG for bands and musicians.<!--
--><p>PS: The ideas in the current NBAND SNG are daft. Lots of musical acts have multiple albums (i.e. tracks released at the same time under a grouping title) and lots of indie labels (which may just be some dude in his bedroom) exist with multiple acts, some of them nominally notable [because of NBAND's issues, making this a vicious cycle!], but that doesn't actually make every band on that notional label (nor the label itself) enclopedia-worthy. Some of these are farcically obscure acts [not a denigration – I'm probably buying their stuff]. This is not 1977; you do not need a vinyl pressing plant to be a music label. You just need to figure out how to fill in a web form at Bandcamp and Spotify, and have enough of a clue about how the present music industry works (often just within a narrow subculture) that you can convince some acts (probably your friends in the same scene) that you can help them if they agree to be on your roster. PPS: A side issue is that "albums" isn't a good metric anyway, since several genres are not album-driven at all, and the entire notion of albums is being increasingly questioned in the era of on-demand music. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''']] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] 😼 </span> 21:59, 15 November 2024 (UTC)</p>


*'''Retain guidance''' What useful purpose is served by inherently ambiguous titles, even when this is the sole article? [[User:Pincrete|Pincrete]] ([[User talk:Pincrete|talk]]) 21:37, 6 May 2016 (UTC)
I'd be happy to see #5 and #6 completely eliminated. What does it take to make that happen? What's the next step? [[User:Graywalls|Graywalls]] ([[User talk:Graywalls|talk]]) 02:08, 16 November 2024 (UTC)
*'''Retain Guidance''' Why would we remove relevant information that helps users avoid pointless move discussions. I have seen time and again pointless move requests to ambiguous titles that fail precision. <span style="font-family:monospace;background:lightgrey;border:solid 1px;border-radius:5px;"> '''''[[User:Insertcleverphrasehere|Insert]][[Special:Contributions/Insertcleverphrasehere|CleverPhrase]][[User talk:Insertcleverphrasehere|Here]]''''' </span> 03:23, 15 May 2016 (UTC)
::And numerous RMs have closed with the opposite result. '''<span style="border: 1px blue solid;background:Cyan">[[User:Calidum|<font color="#4863A0">Calidum</font>]]&nbsp;[[User talk:Calidum|<font color="#A18648">¤</font>]]</span>''' 03:48, 16 May 2016 (UTC)
:::Not in the case of naturally ambiguous titles. They get resolved one way or another, and this way is much more common that the deleters here understand or admit. (Often a notably different alternative name is available, but when one is not, all that is left is some form of disambiguation). <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 17:08, 17 May 2016 (UTC)
*'''Retain guidance''' (and apply with common sense). There are situations where reduction of ambiguity is desirable even though there may be only one article with the title. This doesn't mean every potential ambiguity must be "pre-disambiguated", but we should not prohibit this. [[User:Bkonrad|older]] ≠ [[User talk:Bkonrad|wiser]] 17:11, 17 May 2016 (UTC)
*'''No guidance'''; at least, not on connection with disambiguation. If there should be guidance of this sort at [[WP:AT]], that is a different discussion. [[User:BD2412|<font style="background:gold">'''''bd2412'''''</font>]] [[User talk:BD2412|'''T''']] 17:23, 17 May 2016 (UTC)
**One that was already had about a year ago, and consensus did not agree to import this wording from the guideline. Deletionists don't get to nuke stable guideline wording they don't like by re-proposing failed merges to policy, then pretending that's an argument against retaining it where it was originally. Could kill any guideline on sight with that tactic. Guidelines are guidelines for a reason, because they are not policy material. A simple observation of fact, that WP disambiguates for more that one reason (though one reason is certainly the most common) is not a policy matter, but a guideline matter. It does not tell us to do or not do anything, it describes actual practice. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 18:15, 17 May 2016 (UTC)
*'''No guidance''': As a user of Wikipedia, even years before I joined, it was clear that the bizarre term "disambiguate" on Wikipedia meant to figure out the title of the article you were looking for when multiple articles have similar titles. I thought it was some term a bunch of geeks made up, proud of their $10 word a bit like the [[International Obfuscated C Code Contest]]. (When I first learned C and heard the term "obfuscated", I was confused, and apparently, that was intentional.) I always assumed there was a better more common sense way to describe how to find the correct title than "disambiguation", but now we just accept it. I read a lot, and I have, never, ever seen the word "disambiguate" used anywhere else, although "obfuscate" sometimes. Good writing should avoid unnecessary $10 words [http://www.cjr.org/language_corner/salubrity_and_salutations.php]. To find more than one use for this $10 word on Wikipedia is a mistake. The word "disambiguate" needs to be "disambiguated"! --[[User:David Tornheim|David Tornheim]] ([[User talk:David Tornheim|talk]]) 12:21, 4 June 2016 (UTC)
*'''No guidance''': this is [[WP:AT]] matter, not [[WP:D]] matter. A general "non-disambiguating disambiguator" guidance is not a good idea: it didn't get accepted at WP:AT (see ample prior discussion), not a good idea to insert some WP:AT-conflicting guidance into the WP:D guideline. Note that specific naming conventions contain guidance against using "non-disambiguating disambiguators" in certain cases (e.g. [[Wikipedia:Naming conventions (books)#Precision]]): not a good idea to add some conflicting guidance elsewhere (in other words: this is [[WP:RULECRUFT]], ready to open up endless discussions again). For me [[WP:CRITERIA]] suffises, combined with what can be found in naming conventions for specific cases (e.g. [[Wikipedia:Naming conventions (music)#Articles in series]] implying that some article titles in specific series will contain extensions in a uniform format on top of what is necessary for disambiguation alone). The WP:D insertion under discussion here tries to shift the balance among the five WP:AT criteria: it tries to give the "precision" criterion some sort of over-all advantage over the "conciseness" criterion, contrary to the balance between these criteria in the policy. When such shift of balance would be needed (which I doubt), that should be hashed out at WT:AT and not at a guideline that is not even directly about article titling, and thus tries to get an upper hand over a policy. --[[User:Francis Schonken|Francis Schonken]] ([[User talk:Francis Schonken|talk]]) 06:17, 19 June 2016 (UTC)
**For clarity: afaics this RfC was not properly notified to [[WT:AT]], not even after unarchiving, despite that it has been suggested multiple times that this is in fact WP:AT matter. So far so good, but then below it is advocated that no "WP:AT/WP:MOS regular (...) should close" this RfC. So please make up your mind: either notify WT:AT and WT:MOS that this RfC is going on, so that said regulars are invited to express their opinion in this RfC, or retract objections that said regulars couldn't close this as uninvolved. --[[User:Francis Schonken|Francis Schonken]] ([[User talk:Francis Schonken|talk]]) 05:16, 19 June 2016 (UTC)


:If you believe this would amount to a major change to the guideline, then you should probably be making a formal [[WP:PROPOSAL]]. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 04:52, 16 November 2024 (UTC)
===Discussion (disambiguation)===
::{{u|WhatamIdoing}}, would clarifying that SNG don't override GNG requirements be a major change?--[[User:3family6|<b style="color:navy">3family6</b>]] ([[User talk:3family6|<u style="color:black">Talk to me</u>]] &#124; [[Special:Contributions/3family6|<small style="color:purple">See what I have done</small>]]) 11:57, 16 November 2024 (UTC)
*''' More detailed background:''' Attempts to delete part of the guideline, which was established through standard consensus-building discussion and revision many months ago, are predicated on two obvious fallacies: 1) That "disambiguate" is a made-up Wikipedian neologism for "prevent article title collisions". Check any dictionary; it's a plain-English word meaning "to resolve ambiguity"; doing so to prevent title collisions is simply the most common reason we disambiguate and has never been the only one. 2) That [[WP:CONCISE]] is akin to a law, and that the most concise possible name must always be chosen no matter what. Actually read [[WP:AT]] policy – all of the [[WP:CRITERIA]] are considered, and balanced against each other; the overriding concern is not following any "rule" [[WP:BUREAUCRACY|bureaucratically]], but ensuring clarity for readers. The [[WP:CRITERIA|naming criteria]] {{tq|"should be seen as goals, not as rules. For most topics, there is a simple and obvious title that meets these goals satisfactorily. If so, use it as a straightforward choice. However, in some cases the choice is not so obvious. It may be necessary to favor one or more of these goals over the others."}}<p>The previous debates about this guidance are misrepresented in the the summary in the RfC, which incorrectly paints it as a slow editwar instead of removal, discussion, refinement, acceptance, then much latter isolated attempts to delete it without a rationale. In the original discussions 8 months ago [[Wikipedia_talk:Disambiguation/Archive_43#Disambiguating_WP:PRECISION_failures|here]] and [[Wikipedia_talk:Disambiguation/Archive_43#WP:PRECISIONDAB|here]], Red Slash tried to move it into policy itself at [[WP:AT]] (rejected), objections were raised about iit original length (it was shortened), and about particular examples it use (removed); the principal objector was Francis Schonken, on the basis of having made a proposal to rewrite AT in ways that would have integrated this and made various other changes (which did not achieve consensus at AT). After revision, the short version of this material was accepted in [[WP:Disambiguation]] without incident since that second discussion. This is standard [[WP:BRD]] operating procedure, and this revision and resolution process is how consensus is established. By August, the principal objector, Schonken, was removing attempts to reinserted expanded wording and examples [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia%3ADisambiguation&type=revision&diff=674979475&oldid=674978595] but retaining the agreed short version from prior discussions [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Disambiguation&oldid=674979475#top], which had already been accepted for two months. It remained uncontroverted for 6 more months, clearly long enough for consensus to be established, especially in a much-watchlisted guideline we use every single day.</p><p>It was drive-by deleted in Feb. by Born2Cycle, with a bogus claim that discussion didn't happen and consensus was not been established [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia%3ADisambiguation&type=revision&diff=703455441&oldid=701307091]. This is is part of his years-long, tendentious campaign to promote [[WP:CONCISE]] as some kind of "super-criterion" that trumps all other concerns – which [[WP:MFD]] has rejected three times in a row: [[Wikipedia:Miscellany_for_deletion/Wikipedia:Yogurt_Rule|1]], [[Wikipedia:Miscellany_for_deletion/Wikipedia:Concision_razor|2]], [[Wikipedia:Miscellany_for_deletion/Wikipedia:Unnecessary_disambiguation|3]]. The recent attempt by Dohn joe to delete material was predicated on his unawareness of the February discussion (which is mischaracterizing as being against inclusion when it was not) [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia_talk%3ADisambiguation&type=revision&diff=711734004&oldid=711708819], his misunderstanding of previous discussions (see [[WT:Disambiguation#Restored content on precision cut from lead]], which covers much of what I've outline here in more detail), and more false claims that consensus was not established.<p><p>After 8 months of stability, ''the burden is on would-be deleters to demonstrate what the supposed problem is, and provide actual evidence that WP-wide consensus that such precision-and-recognizability disambiguations are permissible when necessary has somehow disappeared all of a sudden''. This RfC, and two editors' PoV against this part of WP:DAB, would undo very long-standing naming conventions that call for this kind of precision-and-recognizability disambiguation, like [[WP:USPLACE]] and [[WP:USSTATION]], and fly in the face of years of [[WP:COMMONSENSE|common sense]] decisions at RM, like the disambiguation of [[Algerian Arab]] (now a disambiguation page) to [[Algerian Arab sheep]], and [[British White]] to [[British White cattle]]. Per [[WP:POLICY]], the purpose of guidelines is to record actual community best practice, not try to force someone's made up idea about how things should be, like changing the meaning of English words, or preventing RM from doing what RM routinely does. Retaining this does the former, and removing it does the latter, both to pretend the word "disambiguation" doesn't mean what it means, and as to elevate concision above every other criterion, against the clear wording of policy. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 16:04, 25 March 2016 (UTC)</p>
:::Yes. And if you want to try that, you should find and read the many previous discussions about that. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 19:27, 16 November 2024 (UTC)
*'''Comments''' (since there seems to be confusion): Wait! You mean [[WP:JUSTDONTLIKEIT|I just don't like it]] doesn't mean we can change things just because? How about used in conjunction with and while [[Wikipedia:What "Ignore all rules" means|ignoring all rules]].
:::See [[WP:NPLACE]], which presumes populated legally recognized places are notable. So, all it takes is prove the legal recognition and presence of people and it's assumed to be notable, unless refuted.
:We have many policies and guidelines and a single one can not be used in disregard of others. I was under the impression we can not ignore all rules, if it is against consensus, even if we don't like it, unless we can [[Wikipedia:Silence and consensus|sneak it in under the radar]]. FYI -- we should not really (according to policy) attempt to make or change policy by using [[WP:BRD]] unless we "ignore" the policy on [[Wikipedia:Policies_and_guidelines#Proposals|Proposals]] and [[Wikipedia:Policies_and_guidelines#Good practice for proposals|Good practice for proposals]]. The first states: ''"Proposals for new guidelines and policies require discussion and a '''high level of consensus from the entire community''' for promotion to guideline or policy."''. The second: ''"If '''consensus for broad community support''' has not developed after a reasonable time period, the proposal is considered failed. If consensus is neutral or unclear on the issue and unlikely to improve, the proposal has likewise failed."''.
:::A legally recognized city is presumed, but not guaranteed notable. If it doesn't meet GNG, then the presumed notability can be refuted. It does essentially "override" GNG though a short cut, but is subject to removal by presenting failure to meet GNG.
:Further, the [[Wikipedia:List of policies#Procedural|procedural]] [[Wikipedia:List of policies##Policies and guidelines|policy]] explains the process in detail that is located in the second part. A request for comments here is only one part of that process and not a determining factor for an outcome. Some confusion at [[Wikipedia:How to contribute to Wikipedia guidance#Policy discussions]] seems to be at odds with policy and may contribute to errors. Policy (Good practice for proposals) states the process for any proposed changes to policy:
:::Such presumption is not present for most things. For example, simply quoting a local paper about a gas station opening up and operating demonstrates existence of that gas station, but there's no presumed notability for businesses.
:1)- The first step is to write the best initial proposal that you can.
:::NBAND 5 and 6 qualifies bands and albums into Wikipedia far easier than they should and they stand as a burden to article deletion due to presumed notability under tenuously defined importance, such as having released two albums through an important indie label Four Legged Octopus, which is "important" because the MailBox Etc based label has been around for five years and has a roster. [[User:Graywalls|Graywalls]] ([[User talk:Graywalls|talk]]) 16:55, 18 November 2024 (UTC)
:2)- Authors can request early-stage feedback at [[Wikipedia:Village pump (idea lab)|Wikipedia's village pump for idea incubation]] and from any relevant WikiProjects.
*Not speaking to this issue directly, but the trend in subject specific guidelines, IMHO, has been to ''reduce the influence'' of SNGs relative to GNG, not override. When we started these projects 20 years ago, almost every article was low hanging fruit, almost bound to be found notable eventually. As an example, Military History Wikiproject adopted and modified [[WP:SOLDIER]], a set of specific and non-subjective criteria which if met gave an indication of presumption of reliable sources being found somewhere eventually. This was intended to screen out a lot of "dead veteran I know" articles, not become the floor for inclusion. When it [https://en.wikipedia.org/enwiki/w/index.php?oldid=1008759107#rfc finally came up for discussion] it was made clear SOLDIER was just a project thing and wasn't itself an approved SNG. It was quickly decommissioned, but SOLDIER criteria was for many years a frequently mentioned keep argument at AfD. As another example, [[WP:SPORTSPERSON]] is another project related shorthand (but consensus-approved SNG), which made it more difficult to create and keep articles about athletes without at least ''one source with significant coverage'', which still seems a low bar indeed. IMHO the original intent of such SNGs was to screen article candidates, but as the pedia grew, we started using SNGs to keep them. Adjusting SNGs to meet the modern usage era seems the practical and accepted path. The medical SNGs are still used as exclusionary, and for the best reasons. [[User:BusterD|BusterD]] ([[User talk:BusterD|talk]]) 15:21, 19 November 2024 (UTC)
:3)- Once it is thought that the initial proposal is well-written, and the issues sufficiently discussed among early participants to create a proposal that has a solid chance of success with the broader community, '''start an RfC for your policy or guideline proposal in a new section on the talk page''', and include the {rfc tag along with a brief, time-stamped explanation of the proposal.
*:{{tq|IMHO the original intent of such SNGs was to screen article candidates, but as the pedia grew, we started using SNGs to keep them.}} As someone who joined 10 years in, this seems to have been the trend.--[[User:3family6|<b style="color:navy">3family6</b>]] ([[User talk:3family6|<u style="color:black">Talk to me</u>]] &#124; [[Special:Contributions/3family6|<small style="color:purple">See what I have done</small>]]) 18:20, 19 November 2024 (UTC)
:4)- A RfC should typically be announced at this [[Wikipedia:Village pump (policy)|policy page]] (and/or the [[Wikipedia:Village pump (proposals)|proposals page]], and other potentially interested groups (WikiProjects).
*:Yes, in my opinion SNGs should be ''exclusionary'' criteria, necessary but not sufficient for notability. [[User:JoelleJay|JoelleJay]] ([[User talk:JoelleJay|talk]]) 23:02, 20 November 2024 (UTC)
:There appears to be some confusion at [[Wikipedia:Centralized discussion]] concerning sequence or location but policy seems clear.
*::Agreed, and this makes a lot more sense to me. I haven’t paid much attention to SNGs till recent years, so it has been my impression that they are applied as supplemental options towards keeps and creates. The only one that I even think of as exclusionary is [[WP:NEVENT]], although that’s got its own difficulties inherent.
: '''[[Wikipedia:Disambiguation|DAB]]''': Does cover the topic question above as well as [[WP:AT]]. Although there are editors that seem to prefer parenthetical disambiguation, or unnecessary use of such on article titles (Britannica style), this has not been established by any broad consensus but more just the opposite according to policy natural disambiguation is preferred and parenthetical disambiguation as a last choice. The etymology of "disambiguation" would be "not unclear" which would be "not clarified". An article title should be precise enough to ''unambiguously define the topical scope of the article, but no more precise than that.''. Recognizable, natural, and concise goes along with this. DAB states: ''"Disambiguation is also sometimes employed if the name is too ambiguous, despite not conflicting with another article (yet),"''. Consistency also goes along with these and gives more than one reason why we have [[Flemish Giant rabbit]], [[Continental Giant rabbit]], [[French Lop]], [[Lop rabbit]], [[Angora rabbit]], and so forth. Certainly using the more common name according to references. Common sense is also thrown in there somewhere.
*::Ideally I’d like to see every AfD “SNG-therefore-keep” voter back their rationale up by saying that they endorse the SNG by its likelihood toward [[WP:NEXIST|sources existing]]. <span style="font-family:Avenir, sans-serif">—&nbsp;<span style="border-radius:5px;padding:.1em .4em;background:#faeded">[[User:HTGS|HTGS]]</span>&nbsp;([[User talk:HTGS|talk]])</span> 22:34, 21 November 2024 (UTC)
:'''Conclusion''': We should not attempt to change or change policies or guidelines on a whim or by any local consensus. The process is made somewhat complicated to prevent easy changes. DAB and AT do a fine job. I think if editors disagree then they should probably follow the above procedures. [[User:Otr500|Otr500]] ([[User talk:Otr500|talk]]) 12:39, 26 March 2016 (UTC)
::The portion of [[WP:DAB]] that you quote was [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia%3ADisambiguation&type=revision&diff=711749118&oldid=711606693 added a couple of days ago]. A clear consensus in support of this recent addition would neatly resolve the difficulty of having an orphaned sentence in the lead that isn't explained in the body of the guideline.--[[User:Trystan|Trystan]] ([[User talk:Trystan|talk]]) 18:50, 27 March 2016 (UTC)
:::It's also based on material present in the original, longer version. The [[WP:GAME]] here is to keep whittling away at the material in hopes that it can be made to seem out-of-place in its context. If context is restored, it's obviously belongs where it is. This was true 8 months ago, when the context material was originally reduced, on the basis (Francis Schonken's objection) that the example article titles were "unstable". This wasn't actually true then, and 8 months have proven conclusively that it's not true now, so the original rationale to decontextualizing the sentence has evaporated. Better yet, later editors like Dick Lyon have pointed out that entire NC guidelines, like USPLACE and USSTATION, rely on the exact same principle and have for years, so the examples Schonken didn't like almost a year ago were could have been replaced at any time anyway. A challenge against this provision now is a challenge against multiple naming conventions that have been stable for years. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 21:59, 1 April 2016 (UTC)


== Blind 1RR/3RR ==
===Request for closure===
This RfC was archived by the bot before having been closed. I would suggest that an administrator close it. [[User:RGloucester|<span style="font-family:Monotype Corsiva;font-size:12pt;color:#000000">RGloucester </span>]] — [[User talk:RGloucester|☎]] 18:28, 23 April 2016 (UTC)
*Shall this long expired RfC ever be closed, or shall it languish here for eternity? [[User:RGloucester|<span style="font-family:Monotype Corsiva;font-size:12pt;color:#000000">RGloucester </span>]] — [[User talk:RGloucester|☎]] 00:23, 12 May 2016 (UTC)
**All the above effort should have been put into something that actually matters. [[Special:Contributions/217.44.215.253|217.44.215.253]] ([[User talk:217.44.215.253|talk]]) 11:57, 16 May 2016 (UTC)
***It matters plenty, since dispute keeps erupting about this, on policy and guideline talk pages, and in RMs, and elsewhere. The real time drain is the recurrent disputation, not the attempt to resolve it with an RfC. In the end, this can only reasonably close one way, or be consensus-reviewed without a close (not all RfCs must have formal closure and consensus determination by common sense doesn't require it) in one way: to retain the guidance. Let's review:
****It's been stable for a year+; the original objections to it were mooted by later tweaks (i.e., objections ceased, and the changes the original objectors insisted on were accepted, resulting in a consensus).
****We've since learned it agrees with multiple long-term naming conventions that weren't even considered when it was written and which were not taken into account by any objections, then or now.
****It codifies actual practice that has been ongoing the entire time WP has existed.
****In just a few topics we’ve bothered looking at, the last two years or so produced somewhere between dozens and a hundred RMs that did exactly what the wording suggested, before and after the wording, and with and without naming conventions behind them. The community gets it, even if some editors do not or will not.
****The wording was clarified and improved further in response to issues raised by the RfC (though there has been back-and-forth reverting about this [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Disambiguation&diff=prev&oldid=716398607], [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Disambiguation&diff=next&oldid=716398607], [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Disambiguation&diff=next&oldid=716413865], followed by excessive rewriting (without discussion or consensus) that has tried to eliminate every trace of the wording at issue, in mid-RfC, as shown in this [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia%3ADisambiguation&type=revision&diff=719529736&oldid=711749118 multi-edit diff]; this has been very partially reverted [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Disambiguation&diff=next&oldid=719529736] to preserve some hint of the material, pending RfC closure.
**** Nothing at all negative has happened on the basis of this wording despite this RfC languishing unclosed (it has not been over-applied to do stupid things, nor was it applied this way before the RfC, and cases which actually need this sort of disambiguation of naturally ambiguous names have been proceeding as if nothing happened. Or they had been. Now confusion and dispute {{em|has}} arisen in the wake of attempts to delete the material during the RfC; e.g. [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia_talk%3AArticle_titles&type=revision&diff=720739705&oldid=720738458 this other RfC] has quite a number of editors in favor of such disambiguation in certain kinds of song-title cases, while others suddenly don't seem to think it is possible/permissible, obviously because of [[FUD]] surrounding the WP:DAB wording. <small>[Not all support/oppose at that RfC relates to this matter, however; some of it is about [[WP:CONSISTENCY]] vs. [[WP:CONCISE]], etc. But at least half a dozen participants are making arguments clearly rooted in the wording at WP:DAB that some are trying to delete, consensus and process notwithstanding.]</small>
**** The numbers are in favor of retention, though not by landslide, to the extent that is seen as meaningful.
**** The RfC itself is misleadingly and non-neutrally worded (in favor of deletion); the contravenes [[WP:RFC]] and requires a closer to account for the bias (or to close the RfC as invalid on its face).
****Supporters have provided source, policy, and RM precedent backing, while deleters have not. Various opposers to inclusion in the guideline have actually wanted to move it into AT policy (going all the way back to its original inclusion in WP:DAB), but this proposal was already rejected at WT:AT. Re-proposing failed ideas when nothing has changed is a waste of time. And one does not get to delete guideline material by proposing an implausible move-and-merge to policy that is sure to be rejected, then claim that this somehow has something to do with whether it can be deleted from the guideline. By that rationale any guideline could be nuked by proposing a such a doomed move and claiming that the material suddenly had no consensus of any kind.
**** [[WP:NOT#BUREAUCRACY]], [[WP:EDITING]] and [[WP:CONSENSUS]] are policy (it does not require some local-consensus's permission to codify actual practice in guidelines; this is what guidelines are for, and no one owns them).
**** Finally, the arguments presented here are far stronger for retention than for removal. The latter are primarily predicated on [[WP:IDONTLIKEIT]], factual errors about RM outcomes, confusion about what ''disambiguation'' means, and an insistence, with no basis, that the [[WP:DAB]] page cannot possibly be about anything but article title collisions even if the word itself has broader meaning.
:::In short, there really is no case for removal. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 16:42, 17 May 2016 (UTC) <small>[updated 18:19, 17 May 2016 (UTC)]</small>
*So, my first request for closure was more than a month ago...doesn't that seem a bit beyond the pale? Would someone close this thing out, ''please''? [[User:RGloucester|<span style="font-family:Monotype Corsiva;font-size:12pt;color:#000000">RGloucester </span>]] — [[User talk:RGloucester|☎]] 17:52, 26 May 20(UTC)


Blind enforcement of 1RR/3RR does not serve the project. The question should not be whether one violated the rule, but whether they violated the rule in a way that does not benefit the article. If there is no objection to the violation, we can reasonably assume that they are benefiting the article, or at least causing no harm. The decision should be left in the hands of other editors. Could this be used as a weapon? Would there be editors who claim harm where none exists? Certainly, but that's preferable to what we have now.
:RGloucheser, there is nothing ''to'' "close". The thread was never actually marked as an RFC, even though people started to !vote as if it was. Just stop responding, and the thread will be moved into the archives like any other old discussion. [[User:Blueboar|Blueboar]] ([[User talk:Blueboar|talk]]) 18:06, 26 May 2016 (UTC)
::Yes, it [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Village_pump_(policy)&oldid=712937380#Wikipedia:Disambiguation_and_inherently_ambiguous_titles was an RfC]. The RfC tag is automatically removed after 30 days (i.e. ages ago), when RfCs expire and are meant to be closed. Closure is required, or else there is no resolution to the question asked by the RfC. [[User:RGloucester|<span style="font-family:Monotype Corsiva;font-size:12pt;color:#000000">RGloucester </span>]] — [[User talk:RGloucester|☎]] 18:13, 26 May 2016 (UTC)
:::Sorry... my mistake. If you are willing to go with a non-admin, I would be willing to formally close. [[User:Blueboar|Blueboar]] ([[User talk:Blueboar|talk]]) 19:00, 26 May 2016 (UTC)
::::The "automatic" removal - actually a bot edit - is {{diff|Wikipedia:Village pump (policy)|prev|716828350|here}}, and within seconds it was {{diff|Wikipedia:Requests for comment/Wikipedia style and naming|prev|716828360|removed}} from the RfC listings. There is a request for closure at [[WP:AN/RFC#Wikipedia:Village pump (policy).23Wikipedia:Disambiguation and inherently ambiguous titles]], filed over a month ago. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 19:05, 26 May 2016 (UTC)
:::::I don't think any [[WP:AT]]/[[WP:MOS]] regular like Blueboar should close it. Anyone who regularly works on these policypages is apt to have very strong opinions about how they "should" be, when there is nothing to analyze here but the consensus process, disconnected from what the topic is: Wording was introduced; it was discussed; it was modified by those objecting to it; they stopped objecting after modification, resulting in a consensus; it remained stable all year; someone who did not participate in any of these discussions attempted to delete the agreed-upon, stable text without new discussion or even being aware of previous discussion; multiple editors reverted that; that deletion idea has been discussed, and arguments for and against removing or retaining the wording in some form have been aired; which are stronger, from a [[WP:POLICY]], [[WP:PROCESS]], and [[WP:COMMONSENSE]], especially given that the main alternative proposal is "move it into [[WP:AT]]", a proposal that was already rejected in the first discussion? The answer is pretty clear, so even if we don't get a formal closure, consensus to keep the wording has not actually changed. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 17:52, 29 May 2016 (UTC)


The problem, no doubt familiar to editors reading this, is that there are often not enough "good" editors around to protect an article from "bad" editors (malicious or merely inexperienced) while staying within 1RR/3RR. There is no restriction on the number of BOLD edits by a given editor, or on the number of editors performing BOLD edits. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#888;">&#9742;</span>]] 00:09, 10 November 2024 (UTC)
Just FYI, it's not at all unusual for a discussion like this to languish without a formal closing statement for months. I suspect that having nearly all RFCs bulk-listed at [[WP:ANRFC]] by one editor causes the limited volunteer attention to be spent where it's not truly needed, at the expense of longer and more complex discussions.
:1RR in contentious areas should be fully maintained, with no exceptions. Otherwise, edit wars will quickly develop. [[User:GoodDay|GoodDay]] ([[User talk:GoodDay|talk]]) 00:11, 10 November 2024 (UTC)


:If someone is repeatedly reverting reverts, then there is objection to the violation by definition. That's what edit warring is. If someone is making the same BOLD edit that needs to be reverted multiple times, then they are also edit warring. There are already exceptions with these rules for patent nonsense or obvious vandalism. If there's routine disruption, then it only makes the problem worse to revert over and over instead of taking it to [[WP:RFPP]]. If you feel the need to make more than one or two reverts in a content dispute, then it's time to either consider other options or step away from the article. [[User:Thebiguglyalien|<span style="color:#324717">The</span><span style="color:#45631f">big</span><span style="color:#547826">ugly</span><span style="color:#68942f">alien</span>]] ([[User talk:Thebiguglyalien|<span style="color:sienna">talk</span>]]) 01:31, 10 November 2024 (UTC)
Looking at who's been active recently at ANRFC, if you want an admin to close this, then you probably need to hope that [[User:Bencherlite]], [[User:Xaosflux]], [[User:Coffee]], [[User:BD2412]] or [[User:EdJohnston]] will have time and interest in reading and summarizing 10,000+ words on this subject.
::It's not about edit warring or re-reverts; the problem exists without a single re-revert. Editor A does ten BOLD edits, five of which are detrimental to the article because they are too inexperienced (this stuff takes years to master, so that's far from uncommon). Editors B, C, D, and E contribute an additional twenty detrimental edits (along with any number of good ones, that number being irrelevant for our purposes here). Meanwhile, competent editors F, G, and H are limited to a total of nine reverts, leaving 21 detrimental edits in the article. I say F, G, and H should be allowed to revert until someone claims they are doing harm. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#888;">&#9742;</span>]] 02:04, 10 November 2024 (UTC)
:::Where are you seeing thirty detrimental edits to an article in every day? Why isn't this article protected? Why aren't editors F, G, and H starting a discussion? Why are they reverting Editor A's edits individually instead of rolling them back? Why is it so urgent that these edits need to be reverted right this moment? Even on the off chance that they encounter such an article that exists, F, G, and H would not need to engage in tag-team reverting (which is still edit warring) if they knew what they were doing. [[User:Thebiguglyalien|<span style="color:#324717">The</span><span style="color:#45631f">big</span><span style="color:#547826">ugly</span><span style="color:#68942f">alien</span>]] ([[User talk:Thebiguglyalien|<span style="color:sienna">talk</span>]]) 02:07, 10 November 2024 (UTC)
::::You are welcome to reduce the numbers as you please; the problem exists regardless. The article ''is'' protected, even with ECP, and there is no shortage of registered editors who have 30 days and 500 edits and still have years to go before they are editing with any reasonable level of competence. Some ''never'' reach that point. {{tq|Why aren't editors F, G, and H starting a discussion?}} Seriously? {{tq| Why are they reverting Editor A's edits individually instead of rolling them back?}} Because (1) they may not have the rollback right, and the rollback right should not be required to function as an editor, (2) they would be rolling back five good edits, and (3) it's impossible if Editor A's edits are interleaved with those of any other editor(s). {{tq|Why is it so urgent that these edits need to be reverted right this moment?}} Because (particularly in large and very active articles) the bad edits can easily be missed if not caught immediately. Then they stay in the article for some unknown amount of time until noticed by a competent editor and corrected with a BOLD edit. Could be months or even years. Is that good for the article? &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#888;">&#9742;</span>]] 02:27, 10 November 2024 (UTC)
:::::<small>{{tq|they may not have the rollback right|q=yes}}: Not the main point of this thread, but [[Wikipedia:Twinkle]] has its verison of rollback, available for any registered user.—[[User:Bagumba|Bagumba]] ([[User talk:Bagumba|talk]]) 04:57, 10 November 2024 (UTC)</small>
:::::Could you give an example or two where this has caused a problem? And I note that you have answered the two most important questions inadequately: if an article is subject to edit-warring it should be ''fully'' protected, and you dismissed "Why aren't editors F, G, and H starting a discussion?" with "Seriously?". Yes, of course it's a serious question. Starting a discussion is the best way of defusing an edit war. [[User:Phil Bridger|Phil Bridger]] ([[User talk:Phil Bridger|talk]]) 09:20, 10 November 2024 (UTC)
::::::"Seriously?", while counter to the [[WP:DR]] policy, might be an honest response. I often get page protection or block requests, where my first response is often "where's the discussion?" —[[User:Bagumba|Bagumba]] ([[User talk:Bagumba|talk]]) 10:02, 10 November 2024 (UTC)
:::::::Unless {{u|Mandruss}} is extremely lazy, for which I have no evidence, I don't see how that response can be honest. It only takes a few seconds to start a discussion, no longer than it took to start this one, and the person who starts it wins some extra points. [[User:Phil Bridger|Phil Bridger]] ([[User talk:Phil Bridger|talk]]) 17:08, 10 November 2024 (UTC)
::::::::{{tq|extremely lazy, for which I have no evidence}} Thank you! I have my share of faults and shortcomings, but I don't think extreme laziness is one of them. So there should be new discussions for each of the bad edits (separately for the sake of efficiency and organization), and the bad edits should remain in the article until enough editors have the time, interest, and attention span to form consensuses against them while attending to other important matters. This, at [[Talk:Donald Trump|an ATP where we're struggling to keep the ToC at a manageable size even without such discussions]]. I don't know what articles you're editing, but I want to work there. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#888;">&#9742;</span>]] 03:51, 11 November 2024 (UTC)
:::::::::Did you seriously just point to [[Donald Trump]] as your example and then say you don't know what articles aren't like that [[User:Thebiguglyalien|<span style="color:#324717">The</span><span style="color:#45631f">big</span><span style="color:#547826">ugly</span><span style="color:#68942f">alien</span>]] ([[User talk:Thebiguglyalien|<span style="color:sienna">talk</span>]]) 04:01, 11 November 2024 (UTC)
::::::::::I gather the [[Donald Trump]] article is a rare anomaly where bad content is something we have to live with because the current rules are incapable of preventing it. After all, it's just one article. I would oppose that reasoning. I'd say article quality is ''at least'' as important there as anywhere else. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#888;">&#9742;</span>]] 04:33, 11 November 2024 (UTC)
:::::::::{{tq|So there should be new discussions for each of the bad edits ...|q=yes}}: Yes, or what is an alternative? Your suggestion to favor "good" edits over "bad" is problematic when everyone says their's are the "good" ones. Polarizing topics can be difficult for patrolling admins to [[WP:AGF]] determine "good" v. "bad" edits if they are not subject matter experts.—[[User:Bagumba|Bagumba]] ([[User talk:Bagumba|talk]]) 05:43, 11 November 2024 (UTC)
:::Remember that consecutive edits by a single editor are treated as a single revert for [[WP:3RR]] purposes. So, in your case, editor H can go back and revert the various bad edits and, even if they mechanically break it out into multiple edits, they still have done one revert... Until someone goes back and re-reverts. [[User:Simonm223|Simonm223]] ([[User talk:Simonm223|talk]]) 19:58, 20 November 2024 (UTC)
:If "do not repeat edits without consensus" were the rule (rather than "do not revert"), it would take care of this problem. [[User:Levivich|Levivich]] ([[User talk:Levivich|talk]]) 03:42, 10 November 2024 (UTC)
::Who said anything about repeated edits? Am I missing something? I'm tired at the moment, so that's a possibility. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#888;">&#9742;</span>]] 04:04, 10 November 2024 (UTC)
:::What do you mean, who said? ''I'' said something about repeated edits :-) If the rule were "do not repeat edits without consensus" 1x or 3x in 24 hours, instead of "do not revert" 1x or 3x in 24 hours (which leads to the whole "what exactly counts as a revert?" issue), the problem you are describing would not happen. The 'bad' editor can make 10 bad edits, and the 'good' editor can revert all 10 edits without violating do-not-repeat-3RR, and the 'bad' editor would be able to repeat 3 of those 10 edits without crossing do-not-repeat-3RR, and the 'good' editor can revert all 3 of those without crossing do-not-repeat-3RR, ''et voila'': equilibrium. The problem is we focus on "revert" instead of "repeat." To tamp down on edit warring, we should prohibit people from ''repeating'' their edits, not from "reverting" (whatever that means, exactly) edits. [[User:Levivich|Levivich]] ([[User talk:Levivich|talk]]) 04:50, 10 November 2024 (UTC)
::::Well I'll have to come back after a sleep and try to comprehend that. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#888;">&#9742;</span>]] 04:56, 10 November 2024 (UTC)
:{{tq|Blind enforcement of 1RR/3RR does not serve the project|q=yes}}: Are you referring to page protection or blocks? On contentious topics or any subject? —[[User:Bagumba|Bagumba]] ([[User talk:Bagumba|talk]]) 05:11, 10 November 2024 (UTC)


== What determines "global consensus"? ==
Also, there's no "rule" against requesting closure for any discussion. ANRFC is "Administrators' noticeboard/Requests for closure", not "Administrators' noticeboard/Requests for comment". It's not an RFC-specific thing. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 19:06, 17 June 2016 (UTC)
:Yep. Lots of non-RfCs get listed and acted upon there. "Requests for comment" is only one subsection of "Requests for closure" (though often the only populated one, and people tend to list RfC-like not-quite-RfCs there; it's up to ANRFC admins if they want to reorganize it, and apparently they [[WP:DGAF]] per [[WP:BURO]]. :-) <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 04:49, 30 June 2016 (UTC)


This [[Wikipedia:Arbitration/Requests/Case/Infoboxes#Levels of consensus|ArbCom resolution]] established that "Where there is a global consensus to edit in a certain way, it should be respected and cannot be overruled by a local consensus."
* I was going to close this, but I just don't think it's closable as is. By my read, some editors used the "bolded" text to refer to different "sides"/pespectives. If I sift through, ignoring the bolded text, and, just reading everything for content, I think this pretty much ends up "no consensus". The one thing that I think had consensus was that [[WP:AT]] is policy and regardless of whether DAB should be merged to it or in what state DAB should be in, it should exist as secondary to [[WP:AT]]. But that's just my read of the discussion. As I said, the confusion over what the RFC intent was, and what the RFC was trying to do, in my opinion just makes this a bit of an unfortunate trainwreck. So, while I suppose someone could add a top n bottom template to this, I don't think it's closable (which may be why no one else has either), so please don't consider this a close, but merely my read of things. I hope this helps. - <b>[[User:Jc37|jc37]]</b> 05:35, 9 July 2016 (UTC)


I would like to ask what is the standard for defining that there is global consensus. If the [[Wikipedia:Popular_pages|top 100 articles]] in a certain category all are written in a certain way, is this considered sufficient for global consensus?
{{od}}'''I'm setting this up as a proper RfC''' which will focus on a single question, will be located in the correct place, will point to the permalink of this discussion, and will hopefully be closable. Will be done presently. [[User:Herostratus|Herostratus]] ([[User talk:Herostratus|talk]]) 14:53, 12 July 2016 (UTC)
{{Archive bottom}}


If a 100 articles are not enough, what is the threshold? Is it proportional to the number articles in that category?
== RfC: Clarification of BIO1E ==


Should then this warrant that all articles in that category be written in that way (unless very clearly harmful to the specific article)?
{{atop|result=I'm not sure this requires formal closure, but it's been mass-listed at [[WP:AN/RFC]] and I'm trying to clear the backlog. There doesn't seem to be consensus to adopt any particular option among those initially proposed, and various additional suggestions have been made that are not part of any of these options. Probably, if this is to proceed, a new RfC with more clearcut !voting and taking account of various additional suggestions made may need to take place. <small>[[Wikipedia:Deletion process#Non-administrators closing discussions|(non-admin closure)]]</small> [[User:Dionysodorus|Dionysodorus]] ([[User talk:Dionysodorus|talk]]) 22:41, 8 July 2016 (UTC)}}
In the second paragraph at [[WP:BIO1E]], the assassination that led to the start of World War I is given as an example (and the only example) of a "highly significant" event. To me, this suggests that the appropriate bar is whether the event is covered in, or can reasonably expected to be covered in, history books. Others prefer a lower bar, especially for more recent events, that requires only extensive RS coverage and a subjective assessment of the event's impact—an assessment which often takes a short-term view. They would include events that very likely <u>will not</u> be covered in history books. Should the guideline be modified to clarify this point? If so, how? &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#AAA;">&#9742;</span>]] 19:07, 2 June 2016 (UTC)


[[User:Milo8505|Milo8505]] <sub>[[User_talk:Milo8505|(talk)]]</sub> 10:41, 17 November 2024 (UTC)
No response after one week at [[Wikipedia talk:Notability (people)]].


:[[WP:CONLEVEL]] was already a policy, independent of that resolution. It was just being cited as a principle used in deciding that case. —[[User:Bagumba|Bagumba]] ([[User talk:Bagumba|talk]]) 16:03, 17 November 2024 (UTC)
The sentence in question first gives the example of the assassination of Archduke Franz Ferdinand as an example. This was an event with very high historical impact and is widely covered in history books. The sentence then refers to "the large coverage of the event in [[WP:RS|reliable sources]]". This would include many events that receive extensive <u>news</u> coverage but have far less historical impact, if any. This is contradictory, creating more confusion than clarity.
:I believe that "global consensus" refers to [[WP:P&G|policies and guidelines]] in particular, and to generally accepted practices across the whole of the English Wikipedia. A consensus that applies to just 100 articles out of the almost 7 million article in the English Wikipedia is a local consensus. [[User talk:Donald Albury|Donald Albury]] 16:14, 17 November 2024 (UTC)
:[[User:Milo8505|Milo8505]], you asked this question in a way that can't be answered. Consensus does not depend on categories, and Wikipedia does not deal in abstract quantities but in concrete articles. Is this about whether to have an infobox on [[Gustav Mahler]]? If so then please say so, to provide some context to your question. [[User:Phil Bridger|Phil Bridger]] ([[User talk:Phil Bridger|talk]]) 17:34, 17 November 2024 (UTC)
::@[[User:Phil Bridger|Phil Bridger]] Yes, it is about that topic. I believe that there is sufficient global consensus about the inclusion of infoboxes on biographies. I am well aware that the official policy is "no policy defined", but I see a clear trend, by looking at the most read articles, that all biographies - of musicians and non musicians alike - have an infobox, except a select few classical music composers.
::I do not currently have the whole information regarding exactly how many of all biographies have an infobox, and that is why I was asking what is usually considered consensus.
::However, given that I'm very aware that a hundred articles out of seven million is not precisely consensus, I will attempt, when I have the time, to go through every single biography to determine an exact percentage.
::[[User:Milo8505|Milo8505]] <sub>[[User_talk:Milo8505|(talk)]]</sub> 18:56, 17 November 2024 (UTC)
:::If you want to spend your time doing that then I can't stop you, but I warn you that you will be wasting your time. That is not how consensus is measured. [[User:Phil Bridger|Phil Bridger]] ([[User talk:Phil Bridger|talk]]) 19:10, 17 November 2024 (UTC)
::::Obviously I will not count by hand, I have some idea of how to use an automated tool to do that.
::::But then, ''how'' is consensus measured?
::::I'm under the impression that there is a group of very determined and very vocal editors that fiercely oppose infoboxes on classical composers' articles (which leads to most of them having discussions about infoboxes, citing each other as examples of articles without infobox), separate from the majority of biographies, which have an infobox.
::::I see no better way of proving (or maybe disproving) my point than this, because my earlier points of infoboxes being a great thing for [[Gustav Mahler]]'s article, and the fact that numerous non-classical musicians have infoboxes, and lengthy ones at that, seem to have fallen on deaf ears.
::::[[User:Milo8505|Milo8505]] <sub>[[User_talk:Milo8505|(talk)]]</sub> 20:01, 17 November 2024 (UTC)
::::And I would like to state, for the record, that I'm not doing this out of spite, or out of a personal interest (I'm actually ''losing'' my time by arguing about this), but because I truly, wholeheartedly believe that an infobox on each and every biography, and in general, on every article where there could be one (this excludes abstract topics such as [[existencialism]]) would make Wikipedia a truly better place.
::::[[User:Milo8505|Milo8505]] <sub>[[User_talk:Milo8505|(talk)]]</sub> 20:43, 17 November 2024 (UTC)
:::::I would have to search the archives, but we actually held an RFC (one of the ways in which we determine GLOBAL consensus) that was focused on whether to mandate infoboxes on articles about composers… which determined that there were valid reasons not to require them (I suppose you could say that global consensus was to defer to local consensus on this specific issue). Remember [[WP:Other Stuff Exists]] is not an accepted argument here at WP. And that “standard practice” often has exceptions. [[User:Blueboar|Blueboar]] ([[User talk:Blueboar|talk]]) 22:06, 17 November 2024 (UTC)
::::::I understand, but that is ''not'' my sole argument. I have provided other arguments in favor, which you can read at [[Talk:Gustav_Mahler|the aforementioned talk page]] which basically boil down to:
::::::<sub>in my opinion,</sub>
::::::#Infoboxes make standardized information more easily accessible, and
::::::#They do not harm the rest of the article, as they do not displace the lead paragraph.
::::::However, in the linked talk page, I see that opponents of infoboxes rely somewhat on the loosely established precedent/consensus that composers shouldn't have infoboxes.
::::::That is why I wanted to bring forth a new argument, using the, as I see it, very established consensus for infoboxes in biographies, and what I want to know here is whether this consensus can be proven to exist (or what is it required for this consensus to exist). [[User:Milo8505|Milo8505]] <sub>[[User_talk:Milo8505|(talk)]]</sub> 07:30, 18 November 2024 (UTC)
:::::This whole thing about "global" and "local" consensus seems to confuse everyone, and consequently folks make up whatever seems plausible to them. Let me give you a potted history and the usual claims, and perhaps that will help you understand the principle.
:::::'Way back in the day, infoboxes didn't exist. AIUI the first widely used infobox template was {{tl|taxobox}} in 2004, and the general concept appeared soon after. However, [https://en.wikipedia.org/enwiki/w/index.php?title=Template:Infobox&oldid=178933718 through the end of 2007, Template:Infobox] didn't look like what we're used to. Originally, an 'infobox template' was literally a [[Help:Table|wikitext table]] that you could copy and fill in however you wanted.<ref><small>Being able to do this in wikitext was was considered an improvement, because originally, you had to code tables in raw HTML.</small></ref>
:::::While infoboxes were being developed, the editors at [[Wikipedia:WikiProject Composers]] decided that infoboxes were [[Wikipedia:Disinfoboxes|a bad idea]] specifically for articles about [[classical composers]], so after a series of disputes and [[Wikipedia talk:WikiProject Composers/Infobox debates|discussions]], in April 2007 they wrote a note that said, basically, "BTW, the sitewide rules don't apply to the articles we [[WP:OWN]]."<ref><small>This was not as unreasonable back then as it sounds now. WikiProjects were a significant source of subject-specific advice back then, and the rule-making systems were quite informal. [[WP:PROPOSAL]] didn't exist until late 2008. Before then, most guidelines and even policies acquired their labels merely because someone decided to slap the tag on it, and if nobody objected, then that was the consensus for what to call it.</small></ref>
:::::The conflict between this group and the rest of the community eventually resulted in the 2010 [[Wikipedia talk:WikiProject Composers/Infoboxes RfC]]. The result of this years-long dispute is memorialized in the example given in what is now the [[Wikipedia:Consensus#Levels of consensus]] section of the policy: "Consensus among a limited group of editors, at one place and time, cannot override community consensus on a wider scale. For instance, unless they can convince the broader community that such action is right, participants in a [[Wikipedia:WikiProject|WikiProject]] cannot decide that some generally accepted [[Wikipedia:POLICY|policy or guideline]] does not apply to articles within its scope."
:::::Or, to be rather more pointy-headed about it: WikiProject Composers doesn't get to decide that "their" articles are exempt from [[MOS:INFOBOXUSE]].
:::::What was then a statement about the "Purpose of consensus" or, before then, one of several "Exceptions" to forming a consensus on a talk page has since been renamed ==Levels of consensus==. Also, ArbCom (and consequently part of the community) has started talking about "global" consensus. I think that has confused people about the point.
:::::"Levels" of consensus could mean the strength of the consensus ("This is just a weak consensus, so..."). It could mean something about the process used ("My CENT-listed RFC trumps your Village pump post"). It could mean whether the consensus applies to the whole site ("We formed a consensus at [[Talk:Article]] about the first sentence of [[Article]], so now I need to make 500 other articles match this one"). And it could tell us something about how likely it is that the decision matches the overall view of the community.
:::::It's supposed to be that last one. We don't want a handful of people getting together on some page and saying "Let's reject this rule. This article ''needs'' to be censored. Copyvio restrictions are inconvenient. Bold-face text helps people see the important points. And we know this POV is correct, so it should dominate." We want quite the opposite: "The community says that this is usually the best thing, so let's do this."
:::::AFAICT, the overall view of The Community™ is that we think that there should not be any Official™ Rule saying that any subset of articles should have an infobox. We're probably doing this mostly for social reasons, rather than article reasons. For example, every single article about a US President, or atomic elements, or any number of other subjects, has an infobox – but we refuse to write any rule saying they ''should'', or even that they ''usually should'', even though we know the popularity is ever-increasing. For example, at the moment, [[Georgina Sutton]] is the only biography linked on the [[Main Page]] that doesn't have an infobox.
:::::I suspect that the closest we will come to such a rule during the next few years is a note about how popular they are. It should be possible to see how many articles (overall, or in particular subsets) already use infoboxes, and to add that information to [[MOS:INFOBOXUSE]]. For now, we could add a statement that "most" articles have an infobox.
:::::
<references />
:::::[[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 22:27, 17 November 2024 (UTC)
::::::Thank you very much for your detailed response.
::::::From what you have said, given that WikiProject composers have to follow [[MOS:INFOBOXUSE]], there should be a discussion on each and every composer's talk page to determine whether an infobox is warranted.
::::::I see this as a bit of a, difficult and fruitless endeavor, as the arguments presented, for either case, are always the same, and they all usually result in stalemates (like the one about [[Gustav Mahler|Mahler]]).
::::::What I propose is to change the policy, to, at least, recommend infoboxes on certain categories, given that, as you said, they are very popular. Or at the very least, as you suggest, acknowledge the fact that they are very popular.
::::::When I have time to gather more data on the use of infoboxes, I will propose a new RfC to try to commit this change to the policy.
::::::I am very well aware that my chances of success are slim, but, I'll do what I can do.
::::::[[User:Milo8505|Milo8505]] <sub>[[User_talk:Milo8505|(talk)]]</sub> 08:00, 18 November 2024 (UTC)
:::::::Well, if "they all usually result in stalemates", then that represents a change, because the last complaint I saw about this subject said that the RFCs on whether to add an infobox almost always resulted in an infobox being added. Perhaps it varies by subject, however.
:::::::Acknowledging that they're popular shouldn't require a proposal for a change. It should only require getting some decent numbers. Check the archives of [[WP:RAQ]]; they probably can't query it directly, but if there's been a request, you'll see what could be done. It might also be possible to create a hidden category for "All articles with infoboxes", automagically transcluded, to get a count on the number of infoboxes. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 06:45, 20 November 2024 (UTC)
::::::::First of all, thank you again very much for your continued interest.
::::::::The discussions around infoboxes (not RfCs, discussions on talk pages) as far as I have seen usually go something like:
::::::::- I propose adding an infobox
::::::::+ We have talked a lot about that and there are good reasons<sup>tm</sup> for which it should not be added
::::::::- But I also have good reasons<sup>tm</sup> for which it should be added.
::::::::(no comments for 4 years, then it begins again).
::::::::I thought a bit about counting links, and I realized maybe getting this data is easier than I thought, see:
::::::::For counting the number of transclusions to a given page, [https://linkcount.toolforge.org/ this tool] is very useful, and says that there are around 3.2 million infoboxes ''in total'', and 460 thousand infoboxes about people. (on the (Article) namespace).
::::::::Looking in the Talk namespace, there are around two million links to [[Template:Wikiproject Biography]].
::::::::This seems to suggest that only around a quarter of all biographies have an infobox? Maybe I was wrong all along in my observation that infoboxes are very popular.
::::::::I am however not too sure that the two million links to [[Template:Wikiproject Biography]] on the Talk namespace actually corresponds to two million unique biographies.
::::::::Maybe another way of getting this data would be better, I'll have to look at it on some other occasion that I have more time.
::::::::[[User:Milo8505|Milo8505]] <sub>[[User_talk:Milo8505|(talk)]]</sub> 11:28, 20 November 2024 (UTC)
:::::::::I looked at the first 10 articles in [[:Category:Core biography articles]], and 100% had infoboxes. However, those ten articles used seven different infoboxes:
:::::::::* [[Template:Infobox person]] (is this the one you looked at?)
:::::::::* [[Template:Infobox royalty]]
:::::::::* [[Template:Infobox writer]]
:::::::::* [[Template:Infobox saint]]
:::::::::* [[Template:Infobox scientist]]
:::::::::* [[Template:Infobox philosopher]]
:::::::::* [[Template:Infobox writer]]
:::::::::[[:Category:People and person infobox templates]] lists dozens. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 23:22, 21 November 2024 (UTC)
::::::::::Yes! Yes!
::::::::::That's my point. Most{{cn}} good biographies have an infobox - except those of classical composers.
::::::::::I will look at the category you mentioned and try to count from there.
::::::::::Thank you very much! [[User:Milo8505|Milo8505]] <sub>[[User_talk:Milo8505|(talk)]]</sub> 16:46, 22 November 2024 (UTC)
:::::::::::The problem is, there still exist editors who strongly dislike infoboxes on most biographies -- me for one. When one writes every word of an article and then someone, who has not otherwise contributed, comes and adds an infobox it can be ... annoying. The basic use tends to highlight bits of trivial information (birth & death dates/places, nationality, spouse, children) that are not usually key to the person's notability. Even more contentious can be trying to define what a person's key contributions are, in a half-sentence. For some this is easy, and an infobox might be a good way of presenting the data, for others (including many classical composers) not so much. It can be hard enough to write a lead that presents this in a balanced fashion in a paragraph or three.
:::::::::::Are all good biographies written by groups? I'm not sure; probably the best are, but there are many many biographies of minor figures where 99.9% of the text was contributed by a single author, some of which are fairly well developed. [[User:Espresso Addict|Espresso Addict]] <small>([[User talk:Espresso Addict|talk]])</small> 05:05, 28 November 2024 (UTC)
::::::::::::I'm thankful for your contributions, but I'm sorry that you don't [[WP:OWN]] any article, and you can't dismiss someone else improving the article you wrote because ''you'' wrote it and ''you'' don't personally agree with the contributions made.
::::::::::::That said, it may be difficult to summarize why someone is important in a phrase, but it's not impossible, and, IMO actually something that should be done, as it makes the article easier (and faster) to scan. [[User:Milo8505|Milo8505]] <sub>[[User_talk:Milo8505|(talk)]]</sub> 09:39, 28 November 2024 (UTC)
:::::::::::::What I am obviously failing to convey is that some editors write articles, far fewer than those who contribute in other ways, and some of those dislike the "improving" addition of an infobox by another editor who makes no other edits, improving or otherwise. [[User:Espresso Addict|Espresso Addict]] <small>([[User talk:Espresso Addict|talk]])</small> 10:40, 28 November 2024 (UTC)
::::::::::::::Why is that relevant? Nobody owns an article, regardless of in which why they contribute to Wikipedia. Just because some editors dislike something does not give them a veto over things that the majority of other editors believe does improve the article. Obviously an infobox with incorrect information is not an improvement but that doesn't mean an infobox with correct information is not an improvement. In exactly the same way as a paragraph with incorrect information about an aspect of the article subject is a bad addition, this does not mean that a paragraph with ''correct'' information about that same aspect is bad. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 11:55, 28 November 2024 (UTC)
:::::::::::::::It seems to me a great deal more like reference format and English variant. It could easily be argued that we should have standardised on US spelling and picked a mode of referencing, but we never did because it would alienate too much of the workforce. [[User:Espresso Addict|Espresso Addict]] <small>([[User talk:Espresso Addict|talk]])</small> 12:55, 28 November 2024 (UTC)
::::::::::::::::It's not even close to being like ENGVAR or reference formatting. Those are stylistic decisions where there are multiple equally valid choices that don't impact content. Infoboxes are a content decision where one choice directly benefits the readership and one choice placates the dislikes of a minority of editors. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 16:40, 28 November 2024 (UTC)
:::::::::::::::::Load up the Good Faith, {{u|Thryduulf}} :D another phrasing, less pejorative or sweeping, might be {{blue|Infoboxes are a content decision where either choice directly affects the readers' preconceptions of the topic}}. '''''[[User talk:Serial Number 54129|<span style="color: #ee6f53;">Tight faded male arse. Decadence and anarchy. A certain style.</span>]] [[Special:Contributions/Serial_Number_54129|<span style="color:#6c4a43;">Smile.</span>]]''''' 16:47, 28 November 2024 (UTC)
::::::::::::::::::It may or may not be less pejorative or sweeping, but it is also less accurate. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 18:24, 28 November 2024 (UTC)
:::::::::::Case in point [[Jacqueline Stieger]], where the box I've just removed (1) highlighted her place of birth Wimbledon and nationality British, which -- for someone with two Swiss parents, who was brought up in Yorkshire, did some of her notable work in France/Switzerland with her Swiss husband and then settled back in Yorkshire with her Swiss stepchildren -- is undue; and (2) copied "artist and sculptor" from the beginning of the capsule, while not paying heed to the fact her notable works predominantly fall into two groups, big architectural sculptures mainly in metal, and jewellery/art medals. [[User:Espresso Addict|Espresso Addict]] <small>([[User talk:Espresso Addict|talk]])</small> 05:52, 28 November 2024 (UTC)
::::::::::::X thing is bad, because once, some time ago, I saw an instance of X and it was bad, really really bad, as a matter of fact. [[User:Milo8505|Milo8505]] <sub>[[User_talk:Milo8505|(talk)]]</sub> 09:42, 28 November 2024 (UTC)
:::::::::::::Well sure, but I just looked down my list of created bios by date till I found the first to which someone had added an infobox. I didn't drag out my historical collection of badly added infoboxes including those that had been cut-and-pasted wholesale from another article without changing any of the data, and those that introduced errors in the dates. [[User:Espresso Addict|Espresso Addict]] <small>([[User talk:Espresso Addict|talk]])</small> 10:40, 28 November 2024 (UTC)


== Should WP:CRYSTAL be clarified? ==
{{larger|'''Options:'''}}


The article [[2028 United States presidential election]] was proposed for deletion several times ([[WP:Articles_for_deletion/2028_United_States_presidential_election_(3rd_nomination)|last one]]). Editors repeatedly cited [[WP:CRYSTAL]], which reads
*{{larger|'''1'''}} - Clarify the guideline. Remove the Princip example, replacing that entire sentence with: "The event should have received large coverage in [[WP:RS|reliable sources]] that devote significant attention to the individual's role."
<nowiki>If preparation for the event is not already in progress, speculation about it must be well documented. Examples of appropriate topics include the [[{{#expr: {{CURRENTYEAR}} + 4 + ({{CURRENTYEAR}} * -1)mod4 }} United States presidential election|{{#expr: {{CURRENTYEAR}} + 4 + ({{CURRENTYEAR}} * -1)mod4 }} U.S. presidential election]] and [[{{#expr: {{CURRENTYEAR}} + (2*4) - ({{CURRENTYEAR}}mod4)}} Summer Olympics]]. By comparison, the [[{{#expr: {{CURRENTYEAR}} + (5*4) + ({{CURRENTYEAR}} * -1)mod4 }} United States presidential election|{{#expr: {{CURRENTYEAR}} + (5*4) + ({{CURRENTYEAR}} * -1)mod4 }} U.S. presidential election]] and [[{{#expr: {{CURRENTYEAR}} + (6*4) - ({{CURRENTYEAR}}mod4)}} Summer Olympics]] are not appropriate article topics if nothing can be said about them that is verifiable and not original research.</nowiki>
*{{larger|'''2'''}} - Clarify the guideline. Add language following the Princip sentence: "Historical significance sufficient for inclusion of the event in history books is not required; extensive coverage in reliable news sources may be enough."
According to this, the 2028 election and 2032 Olympics automatically became valid articles on January 1, 2024, although it is not really clear ''why'' that exact date matters. Should this be clarified, and if so, how? <span style="font-family:cursive">[[User:Ypn^2|<span style="color:green">''ypn''</span>]][[User talk:ypn^2|<span style="color:blue;font-size:90%;vertical-align:12%">^</span><span style="color:purple;vertical-align:45%;font-size:75%">2</span>]]</span> 19:44, 18 November 2024 (UTC)
*{{larger|'''3'''}} - Clarify the guideline. Add language following the Princip sentence: "Generally, the bar should be historical significance sufficient for inclusion of the event in history books, either demonstrated or reasonably anticipated."
*{{larger|'''4'''}} - No change to the guideline. Simply affirm that: "Generally, the bar is historical significance sufficient for inclusion in history books, either demonstrated or reasonably anticipated." This RfC will then be used to show community consensus, supplementing BIO1E.
*{{larger|'''5'''}} - Do nothing, the status quo is adequate.
*{{larger|[other]}} - Roll your own. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#AAA;">&#9742;</span>]] 19:07, 2 June 2016 (UTC)


:The relevant question IMO is why do we need an article on the 2028 or 2032 presidential elections? Any "significant coverage" is just speculation at this point. Until candidates declare, I don't see how articles on either is useful to readers. [[User:Voorts|voorts]] ([[User talk:Voorts|talk]]/[[Special:Contributions/Voorts|contributions]]) 19:53, 18 November 2024 (UTC)
===RfC survey: BIO1E===
::Encyclopaedic coverage of predictions and speculation about and preparations for the 2028 presidential election that appear in reliable sources is possible and (in at least some cases) due. Similarly things like whether (and if so what) changes to electoral collage allocations will happen, etc should also be easily found by someone searching. Whether that should be on its own article yet or as part of a broader article will depend entirely on the volume of encyclopaedic material there is. Similarly for the Olympics. As soon as we have coverage about the next and next+1 US presidential elections and Olympic games there should be blue links from the titles those articles will reside at when they have articles (e.g. [[2036 Summer Olympics]] was kept at AfD (although moved to [[Bids for the 2036 Summer Olympics]]) in November 2022 due to there being significant sourcing about the preparations). I don't think the dates in [[WP:CRYSTAL]] should be taken as "there must be an article" but as loose guidelines along the lines of "significantly before this time sufficient information to justify a standalone article is unlikely; it is unlikely there will not be sufficient information for a standalone article significantly after this time." i.e. those dates are the approximate midpoint in the range when sufficient information for a standlone article existing changes from very unlikely to very likely. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 20:36, 18 November 2024 (UTC)
*'''3 or 4''' as proposer. I feel that (1) the guidance is inadequate as written, and that (2) the criterion should be historical significance, not simply RS coverage of any kind. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#AAA;">&#9742;</span>]] 19:07, 2 June 2016 (UTC)
*I support option '''2'''. Something that occurred reasonably recently, no matter how notable the event was, is unlikely to turn up in any history book. If an event has been covered extensively by reliable sources, then I don't see why it matters that it hasn't been covered in history books. '''[[User:Omni Flames|<span style="color:#68829E; font-family:Segoe UI; text-shadow:2px 2px 2px #C4DFE6">Omni Flames</span>]] ([[User_talk:Omni Flames|<span style="color:#A2C523;">talk</span>]])''' 05:04, 19 June 2016 (UTC)
*I lean towards '''4'''. As it currently stands we see plenty of articles being created with dubious historical significance (e.g. this person came in second in the 2005 American Idol, has never been heard from since; or had a minor role in a soap opera, which nevertheless did something consequential to the plot and got coverage for it, but then had no other significant coverage or played any notable roles). This needs to be corrected and made clearer. What we need to define is a way to establish ''"demonstrated or reasonably anticipated"'' - how would you ascertain if an event will be historical and covered in reliable long-term sources, such as books? "History books" should not be taken in the literal sense - I believe this refers to any long-term coverage in the relevant media for that particular subject. Best, <small>[[User:FoCuSandLeArN|FoCuS]]</small> [[Special:Contributions/FoCuSandLeArN|<span style="color: green">contribs</span>]]; [[User_talk:FoCuSandLeArN|<span style="color: dark blue">talk to me!</span>]] 16:42, 26 June 2016 (UTC)
* '''Simply add a non-history-book example, which effectuates the idea of Option 2 without having to change the guidance wording.'''. Extensive RS coverage, regardless of the publication medium, is sufficient. The idea we can predict what will be in future history books is [[WP:CRYSTAL]]. Focusing on "history books" in particular is "medium/genre fetishization" and should be avoided, per the avoidance of it at [[WP:V]] and [[WP:RS]] themselves and at [[WP:NOT#PAPER]]. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 04:46, 30 June 2016 (UTC)
*'''3 or 4''' Current practice in news reporting tends to be like sharks in a feeding frenzy so lots of RS material may be generated for events of little or no long term significance. It is OK, in my opinion, to give the term "history books" a broad interpratation in that the term can refer to "popular" writings rather than being restricted to rigorous academic works. [[User:Jbhunley|<span style="font-family:Monotype Corsiva;font-size:14pt;color:#886600">J</span><span style="font-family:Lucida Calligraphy;font-size:10pt;color:#886600">bh</span>]][[User_talk:Jbhunley|<span style="color: #00888F"><sup>Talk</sup></span>]] 18:22, 7 July 2016 (UTC)


== [[Wikipedia talk:Article titles#Request for comment on the relationship between WP:CRITERIA and WP:TITLEFORMAT]] ==
===RfC discussion: BIO1E===
*What you seem to be asking for is some kind of "super notability", based on what a particular subset of reliable sources have written about (or upon our own subjective opinion of what a particular subset of reliable sources might be writing about at some undetermined point in the future), rather than what we know reliable sources generally have written about. I don't see the merit, nor have I seen any indication that it is established practice so as to justify changing the guideline's description of what practice is. I think you're just reading too much into an example that was probably included for its obviousness rather than it setting the bar that all others must pass. We also already have [[WP:NOTNEWS]], which I think is on point with your concern. '''[[User:Postdlf|postdlf]]''' (''[[User talk:Postdlf|talk]]'') 19:51, 2 June 2016 (UTC)
:The guideline confuses me as written. Unless I'm unusually, almost singularly stupid, which is not outside the realm of possibility, it will confuse others as well. My primary goal here is to eliminate avoidable confusion and the resulting wasted time in discussions. Thus I would ask you to !vote '''1''', '''2''', or '''1 or 2'''. If you can't see fit to do that, I included '''5''' just for you. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#AAA;">&#9742;</span>]] 19:58, 2 June 2016 (UTC)
*Endorse Postdlf's points that this example is chosen for its sheer obviousness, also about 'NOTNEWS'. Real problem is the difficulty in establishing what IS going to be long-term significant. Would a better clarifier be the purely practical one that until the volume of available material requires a seperate article, default should be to not create one? Trouble is too many editors see a seperate article as an endorsement of the individual's significance, rather than the most efficient way to present information IM''(H?)''O. [[User:Pincrete|Pincrete]] ([[User talk:Pincrete|talk]]) 14:58, 3 June 2016 (UTC)
*I think there's a bit of a [[WP:NOTCRYSTAL]] issue if we start predicting what will be in history books and how it will be covered. Who knows what society will consider important in 100 years? I'd rather keep the example in there, but have an additional sentence to the effect of: "The event should have received extensive and enduring coverage in [[WP:RS|reliable sources]] that devote significant attention to the individual's role." In other words, it can't be minor coverage (obviously) and it can't be brief coverage (two days in the limelight and then complete silence is ''exactly'' what [[WP:BLP1E]] is meant to keep out of the encyclopedia). ~ <b>[[User:BU Rob13|Rob]]</b><sup>[[User talk:BU Rob13|Talk]]</sup> 14:44, 7 June 2016 (UTC)
**That sounds remarkably like option '''5'''. For some reason no one wants to !vote in this RfC, so I'm prepared to let this archive for lack of participation and just continue to live with the ongoing consequences of this lack of clarity.<br />The ability to step outside oneself and put oneself in others' shoes is very rare in such decision making. "It's clear to me, with my years of experience, so there is no need for further clarification." Ok then. Wikipedia continues to be designed by the experienced, for the experienced, and the less experienced can just struggle on—or not. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#AAA;">&#9742;</span>]] 02:37, 8 June 2016 (UTC)
***No, I'm more-or-less voting for both an example and clarification away from the use of "future inclusion in history books", which is not currently an option. The wording of 2 prevents me from supporting it. The clarification there is worded in such a way that it still enshrines "future inclusion in history books" as the gold standard (with occasional exceptions for extraordinary sourcing). ~ <b>[[User:BU Rob13|Rob]]</b><sup>[[User talk:BU Rob13|Talk]]</sup> 04:39, 15 June 2016 (UTC)
** Mandruss, I congratulate you on receiving thoughtful comments, rather than simplistic votes, in response to your Request for Comments. Most people starting an RFC would consider themselves lucky. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 19:54, 17 June 2016 (UTC)
**:{{ping|WhatamIdoing}} The same comments can't be part of a !vote? Ok, I wasn't aware of that, and it hasn't been my experience. And I wasn't aware it was a binary choice, anyway. But thanks all, for the thoughtfulness, and I always consider myself lucky just to be allowed to work at a wonderful place like Wikipedia! &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#AAA;">&#9742;</span>]] 01:08, 19 June 2016 (UTC)
*I do not find the guideline confusing and do not think I found it confusing when I first read it. I concede that others may find it confusing and so I '''support''' the addition of the clarifying sentence suggested by {{U|BU Rob13|Rob}}. I certainly do not think that we should be in the business of predicting how much coverage unpublished hypothetical future history books may or may not devote to a topic. [[User:Cullen328|<b style="color:#070">Cullen</b><sup style="color:#707">328</sup>]] [[User talk:Cullen328|<span style="color:#00F">''Let's discuss it''</span>]] 04:41, 17 June 2016 (UTC)
* I think this is a difficult area for less experienced editors, especially when they are interested and excited about writing about a recent event. IMO the biggest focus should be on "enduring" coverage, with a specification that editors should have a reasonable expectation of coverage extending significantly beyond the first anniversary of the end of the event. (For example, almost every murder or kidnapping will get a namecheck in a local newspaper on the one-year anniversary, and that's not enough.) This is not so much "future inclusion in history books" as "future inclusion in any reliable sources", which has some CRYSTAL challenges, but it is far easier to predict one year than one century, the 'deadline' has already passed for many events, and it's easy to clean up next year if we guess wrong. <br> Also, expanding the requirement to require coverage in non-local sources would probably help. It's easy to find year-long coverage in local newspapers of (for example) individual children with cancer or the mayor's arrest for drunk driving, but that's not really notability. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 19:54, 17 June 2016 (UTC)
{{Archive bottom}}


Please see subject RfC. [[User:Cinderella157|Cinderella157]] ([[User talk:Cinderella157|talk]]) 22:19, 18 November 2024 (UTC)
== [[WP:DATERANGE]] ambiguity and stylistic concerns ==
{{rfc|policy|rfcid=FB10353}}
I recently initiated [[Wikipedia_talk:Manual_of_Style/Dates_and_numbers#WP:DATERANGE_again|a discussion]] regarding [[WP:DATERANGE]], the MoS guideline that specifies use of two-digit abbreviated years in end-ranges (i.e. 1995–99 instead of 1995–1999) for years from the 11th century onward only. Objections have been raised regarding this guideline before, and now again, with many agreeing with my reasoning for reverting to the old format, but it never proceeds any further. Here are several reasons why the current guideline should be abandoned and reverted:


==We need to fix the admin recall process==
* Date ranges under the current format can easily be confused for something else entirely, especially for ranges ending in years '01–'12. For example, "2010–12" can easily be interpreted as December 2010 instead of a date range of 2010–2012.
* It looks very unprofessional IMHO. Saving a measly two digits is not worth giving the appearance of using unnecessary shortcuts/slang in a respectable encyclopedia.
* It doesn't read naturally for years in the 21st century spanning the 2000s decade to 2010 or later. This is mainly because years from 2000–2009 are usually pronounced "two thousand and", while years from 2010—present are usually said as "twenty". So a range such as 2000–16 being read as "two thousand to sixteen" sounds ridiculous. This is especially problematic for anyone having Wikipedia read aloud by a text-to-speech program.
* Implementation is inconsistent, since it is only applicable to years 1000 AD+ and to none of the years in the BC era (why not?), leading to more confusion and unnecessary stylistic asymmetry.


Right now only "recall" votes count, and those opposing recall don't count for anything, nor do any points made in the discussion. So 25 quick group-think / mob thumbs-down votes and even be best admmin can get booted. And the best (= the most active) are the ones most likely to get booted. An admin that does near zero will get zero votes to recall. And with a single regular RFA currently the only way back in (which we've seen, very few want to go through) "booted" is "booted". The fix would be to have a discussion period pror to voting, with both "recall" and "don't recall" choices. And then say that the recall has occurred (thus requiring rfa) if over 50% or 60% of those voting said "recall".
I am looking to canvass the wider community to see if there is support to revert to the older style, which <s>preferred</s> permitted the entire 4-digit year for end-ranges. Please indicate whether you support the current MoS guideline or the previous one. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 00:43, 18 June 2016 (UTC)


Sincerely, <b style="color: #0000cc;">''North8000''</b> ([[User talk:North8000#top|talk]]) 20:40, 19 November 2024 (UTC)
:'''Question:''' You say {{tq|the old format}}, but I've just been looking through the history to find when the format changed, and got tired around [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Manual_of_Style/Dates_and_numbers&oldid=161512925 October 1, 2007]‎ when it was ''still'' stating a XXXX&ndash;XX format as it does today. How long ago was the change from XXXX&ndash;XXXX, and why did it change? <code style="background:#DFF;white-space:pre">[[User:Fred Gandt|Fred Gandt]] · [[User talk:Fred Gandt|talk]] · [[Special:Contributions/Fred Gandt|contribs]]</code> 01:41, 18 June 2016 (UTC)
::In 2007, it also said {{tq|"The full closing year is acceptable, but abbreviating it to a single digit (1881–6) or three digits (1881–886) is not"}}, and this no longer seems to be accepted, except for birth and death dates. It once also specified that date ranges from the first millenium used all the digits (886–889, not 886–89). [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 05:52, 18 June 2016 (UTC)
::As of February 10, 2012, our own manual of style is cited in [http://english.stackexchange.com/questions/57606/how-to-write-date-range-succinctly-and-unambiguously-in-american-written-english this stackexchange question] as a "guide" to how to format date ranges - so that's helpful. <code style="background:#DFF;white-space:pre">[[User:Fred Gandt|Fred Gandt]] · [[User talk:Fred Gandt|talk]] · [[Special:Contributions/Fred Gandt|contribs]]</code> 07:25, 18 June 2016 (UTC)
::Sorry for the confusion, but what I had meant by the "old" style was the ''permissing'' of the full closing year (4 digits), which is now removed from the guide. This removal is what has resulted in the change of 4-digit end-years to 2-digits across thousands of articles over the years, and for any 4-digit closing years in new articles/edits to be changed by someone with a comment citing the MoS. I'd prefer the abbreviated form be discouraged altogether, but as long as the 4-digit form is once again ''permitted'' as equally legitimate, that would be sufficient. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 14:56, 18 June 2016 (UTC)
:::Ah, cool. Cheers. <code style="background:#DFF;white-space:pre">[[User:Fred Gandt|Fred Gandt]] · [[User talk:Fred Gandt|talk]] · [[Special:Contributions/Fred Gandt|contribs]]</code> 03:00, 19 June 2016 (UTC)
:::{{Reply to|Crumpled Fire}} The "permissing of"??
: {{Reply to|Crumpled Fire}} I suggest this be converted to a "formal" [[WP:RfC]], so that whatever its results are carry more "weight"... --[[User:IJBall|IJBall]] <small>([[Special:Contributions/IJBall|contribs]] • [[User talk:IJBall|talk]])</small> 19:46, 27 June 2016 (UTC)
:: Good idea. <s>[[Wikipedia_talk:Manual_of_Style/Dates_and_numbers#Four-digit_end_year_re-introduction_to_WP:DATERANGE_w.2F_high_level_of_support_at_Village_Pump|I've done so here]],</s> you and others watching this discussion are welcome to join. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 08:29, 29 June 2016 (UTC)
::: Per [[WP:MULTI]] and common simplicity and ease, I suggest the RfC should be held right here. <code style="background:#DFF;white-space:pre">[[User:Fred Gandt|Fred Gandt]] · [[User talk:Fred Gandt|talk]] · [[Special:Contributions/Fred Gandt|contribs]]</code> 12:17, 29 June 2016 (UTC)
:::: Done. Moved to below. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 13:13, 29 June 2016 (UTC)
::::: If you don't mind, I've refactored the RfC tag to the top, or it will lead to an accidental fork of the "!voting" (a term some object to) into two redundant sections, as people click links to the RfC and end up below it. I almost did this myself until realizing that the comments were in a section above the RfC tag. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 03:54, 30 June 2016 (UTC)</span></small>
:::::: Not a problem, I was considering doing something similar myself, thanks for the help. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 05:05, 30 June 2016 (UTC)


:@[[User:North8000|North8000]] Please see [[Wikipedia:Administrator recall/Reworkshop]], where editors are already discussing potential changes. [[User:Samwalton9|'''S'''am '''W'''alton]] ([[User talk:Samwalton9|talk]]) 20:43, 19 November 2024 (UTC)
===Comments on DATERANGE RfC===
::Thanks. I looked for something like that but I guess I didn't look hard enough. I hope others look harder than me. :-) <b style="color: #0000cc;">''North8000''</b> ([[User talk:North8000#top|talk]]) 21:58, 19 November 2024 (UTC)
{{anchor|!Votes}}
:I don't think you understand how recall works. An admin is only desysopped after the RRFA, not after the 25 signatures, unless they choose to resign on their own. You're asking to hold a vote on whether or not a vote should be held. ~~ [[User:Jessintime|Jessintime]] ([[User talk:Jessintime|talk]]) 20:55, 19 November 2024 (UTC)
* '''Revert''' to previous style (''permit and prefer 4-digit years''), per points above. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 00:43, 18 June 2016 (UTC)
::Yes, I understood that and that is integrated into my comment above. Unless they go through and succeed at an RFA they are gone. <b style="color: #0000cc;">''North8000''</b> ([[User talk:North8000#top|talk]]) 21:54, 19 November 2024 (UTC)
* I'm in favor of ''permitting'' the "full closing year", without requiring it. "In 2006–07, the sports person did something" is appropriate to the subject, even though I prefer "2006–2007" (or even "from 2006 to 2007", spelled out with actual words) for other contexts. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 05:52, 18 June 2016 (UTC)
:I've never heard of a petition that lets people sign because they ''don't'' support it. And I'll add that between the two recall petitions that were enacted to this point, both were preceded by many, ''many'' attempts to get the admin to correct course over the years despite egregious misconduct. [[User:Thebiguglyalien|<span style="color:#324717">The</span><span style="color:#45631f">big</span><span style="color:#547826">ugly</span><span style="color:#68942f">alien</span>]] ([[User talk:Thebiguglyalien|<span style="color:sienna">talk</span>]]) 21:03, 19 November 2024 (UTC)
*:FYI, in case you were unaware, this policy isn't just referring to adjacent years, it's any years within an entire century. In otherwords, "1957–98" is preferred over "1957–1998", which is IMO ridiculous. If it were just "1957–58", as in the common practice used for school years/fiscal years/etc., I'd have no concerns. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 14:50, 18 June 2016 (UTC)
::I'm not talking about any particular cases. Sincerely, <b style="color: #0000cc;">''North8000''</b> ([[User talk:North8000#top|talk]]) 21:56, 19 November 2024 (UTC)
* '''Permit 4-digit years'''. I can think of ''no'' reason to have 2-digit year ranges at all, much less have them preferred. WP isn't paper, so what are we saving by removing some digits? I'm not aware of any increase in understanding by the reader for 2-digit years in ranges, and per above, several possible misunderstandings. I'm saying "permit" rather than "require" only to avoid the same rash of MOS-fanatic changes that caused this dumb situation. --[[User:A D Monroe III|A D Monroe III]] ([[User talk:A D Monroe III|talk]]) 15:14, 18 June 2016 (UTC)
:::So, the premise of your argument is pure conjecture? Regards, [[User:Goldsztajn|Goldsztajn]] ([[User talk:Goldsztajn|talk]]) 22:05, 19 November 2024 (UTC)
* '''Permit 4-digit years'''—forcing two-digit ranges is silly micromanagement, and I can see no profit from enforcing it. [[User:Curly Turkey|Curly&nbsp;Turkey]]&nbsp;<span style="color:red">🍁</span>&nbsp;[[User talk:Curly Turkey|''¡gobble!'']] 22:23, 18 June 2016 (UTC)
::::???? It was from an analysis of it's current structure. <b style="color: #0000cc;">''North8000''</b> ([[User talk:North8000#top|talk]]) 14:10, 20 November 2024 (UTC)
* '''Prefer or require 4-digit years''': I think MOS:DATERANGE permits 4-digit years: {{tq|"the range's end year is {{highlight|usually}} abbreviated to two digits"}}. Two-digit years are an anachronism from before the printing press, in the computer age a two digit year cutoff is a kind of database problem. I was taught to not be ambiguous by using {{code|9999}} for four-digit years (and {{code|999}} for three-digit years, etc.). –[[User:BoBoMisiu|BoBoMisiu]] ([[User talk:BoBoMisiu|talk]]) 00:59, 19 June 2016 (UTC)
:::::But you've just refused to engage in a discussion with how the structure has actually worked in practice; hence, conjecture. Regards, [[User:Goldsztajn|Goldsztajn]] ([[User talk:Goldsztajn|talk]]) 00:19, 21 November 2024 (UTC)
* '''Require ''full'' syntax:''' I was considering this from the standpoint of ''standards'', with the weight being on simple continuity ''i.e.'' One rule to rule them all. With this in mind I considered a range like "1874 to 1984" which would currently read as "1874&ndash;984" if we apply the same logic to the formatting as "1874 to 1884" being written as "1874&ndash;84". This is nonsensical, so we need several formatting rules to cover ''different'' ranges, which leads to confusion and argument. A ''one rule'' solution is to '''always''' use the full syntax ''e.g.'' "1874&ndash;1984", "1874&ndash;1884", "874&ndash;984", "874&ndash;1984" ''etc.''. There can, under this simple single rule, be no confusion or ambiguity. <code style="background:#DFF;white-space:pre">[[User:Fred Gandt|Fred Gandt]] · [[User talk:Fred Gandt|talk]] · [[Special:Contributions/Fred Gandt|contribs]]</code> 03:00, 19 June 2016 (UTC)
:The process at the moment does have a certain level of redundancy, with the recall and reconfirmation RFA being separate things. The reconfirmation RFA is even a standard RFA, as it has different criteria for success.
*'''Previous style''' (full four digit year required) - We should not be using a potentially ambiguous two digit shorthand.- [[user: MrX|Mr]][[user talk:MrX|X]] 03:27, 19 June 2016 (UTC)
:I'm not sure if anything should be done yet, as it's still very early in its adoption. However if the situation occurs that a petition is successful but the reconfirmation RFA SNOWs, it could indicate that adjustments needs to be made so that community time isn't wasted. That speculative at the moment though. -- <small>LCU</small> '''[[User:ActivelyDisinterested|A<small>ctively</small>D<small>isinterested</small>]]''' <small>''«[[User talk:ActivelyDisinterested|@]]» °[[Special:Contributions/ActivelyDisinterested|∆t]]°''</small> 23:53, 19 November 2024 (UTC)
*'''Permit both styles, prefer four digit''' – I wouldn't want to prohibit "1957–58" for school years or sports seasons. It would be nice to come up with a set of simple rules but there are so many exceptions and edge cases I think we need to leave it partly up to editor discretion. [[User:Kendall-K1|Kendall-K1]] ([[User talk:Kendall-K1|talk]]) 12:40, 19 June 2016 (UTC)
:The recall petition threshold is not the recall discussion - it is just a check to prevent the most frivolous recall discussions from being held. — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] <sup>[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]</sup> 00:56, 20 November 2024 (UTC)
* '''Require all digits''' to avoid confusion and ambiguity; saving two characters (especially in a digital context) is unnecessary. [[User:Jc86035|Jc86035]] ([[User talk:Jc86035|talk]]&nbsp;• [[Special:Contributions/Jc86035|contribs]]) <small>Use <span class="nowrap">&#123;&#123;[[Template:Reply to|re]]&#124;Jc86035&#125;&#125;</span> to reply to me</small> 13:12, 19 June 2016 (UTC)
* '''Leave guideline as it is'''. This reflects normal English-language usage. [[User:Jc3s5h|Jc3s5h]] ([[User talk:Jc3s5h|talk]]) 13:23, 19 June 2016 (UTC)
::{{+1}} [[User:Goldsztajn|Goldsztajn]] ([[User talk:Goldsztajn|talk]]) 06:54, 20 November 2024 (UTC)
:The optics of this look alltogether terrible from my observation. I don't edit much, but I like reading a lot. Every criticism of the recall process i've seen so far just looks like old established admins thinking they might be next and having anxiety about that.
*:No it doesn't. Two-digit abbreviations for end-ranges consisting of a period of decades or longer (i.e. 1909–98) are virtually non-existent. The only use of this abbreviated format that I've ever seen commonly is for ''immediately adjacent years'', as in fiscal or school years (i.e. 2008–09), as noted above. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 13:40, 19 June 2016 (UTC)
:The problem of something like this is that the optics are terrible. If anyone who doesn't know you reads that, the conclusion they will draw will likely not be "this recall process is terrible" and more likely go along the lines of "wow this is a lot of admins who don't have the community's trust anymore and want to dodge accountability".
* '''Require all digits:''' A consistent style for ''all'' dates is far more compatible with automated tools, screen readers for the visually impaired, search engines, etc. --[[User:Guy Macon|Guy Macon]] ([[User talk:Guy Macon|talk]]) 16:44, 19 June 2016 (UTC)
:By being so vocally against any form of community led accountability, you're strenghtening the case for easy recalls and low thresholds, not weakening it.
* '''Permit''' 4-digit years, prefer this as default, but leave 4 vs 2 editorial decisions to a case by case scenario. — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] <sup>[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]</sup> 16:48, 19 June 2016 (UTC)
:Specifically regarding Fastily, I'll make no comment on whether or not he deserves to still be an admin or not, I don't know him well enough for that and haven't reviewed enough of his contributions, but the arguments of "ANI agreed that no sanctions were appropriate" sound a lot like "our police department has investigated itself and found nothing was wrong". You have to see how this comes across, it's eroding trust in Admins on the whole project right now. [[User:Magischzwei|Magisch]] <sup>[[User talk:Magischzwei|talk to me]]</sup> 09:24, 20 November 2024 (UTC)
* '''Permit both styles, prefer four digit''' per the rapidly accumulating SNOW above. Specifying always four digits is tempting, but two digits is extremely common for consecutive years and other edge cases. [[User:Alsee|Alsee]] ([[User talk:Alsee|talk]]) 10:03, 20 June 2016 (UTC)
::Specifically, if RFA is so toxic that nobody wants to do it, that needs to be reformed. But the recent amount of vitriol towards a process that only kickstarts having to prove that you retain community trust has me convinced that there should be automatic mandatory RRFAs for every admin every 2 years or so.
* '''Require all digits except for school years or sports seasons and the like''' [[User:Peter coxhead|Peter coxhead]] ([[User talk:Peter coxhead|talk]]) 11:29, 20 June 2016 (UTC)
::If, as of today, you don't believe the community would entrust you with admin tools, why do you think you should still have them? The criteria for losing them should not be "has clearly abused them", it should be "wouldn't be trusted with them if asked today". [[User:Magischzwei|Magisch]] <sup>[[User talk:Magischzwei|talk to me]]</sup> 09:33, 20 November 2024 (UTC)
*'''Prefer full years''' – I've had to correct my own edits to the two digit style more than once, and each time I always wondered why I was having to do that. Even if the two digit style is acceptable, the four digit style is more universal. I can't think of any reason in the context of Wikipedia to prefer the two digit style. Expressing a preference is what the MoS does, by the way. There is no matter of "requirement" in it. Editorial consensus on a talk page should still be able to determine specific instances where the two digit style might have usefulness. [[User:RGloucester|<span style="font-family:Monotype Corsiva;font-size:12pt;color:#000000">RGloucester </span>]] — [[User talk:RGloucester|☎]] 16:41, 20 June 2016 (UTC)
:::As an admin actively working to improve the recall process, my goal is to make it as fair as possible to all parties. That means it should not be possible to subject an admin to the process frivolously while equally making it possible to recall administrators who have lost the trust of the community, and it needs to be as non-toxic as possible, because even administrators who are actively abusing their tools are people and ''nobody'' deserves 1-2 months of abuse. It's also incorrect to describe ANI as a police department investigating itself - everybody engaging in good faith is welcome to comment there, regardless of whether they are an admin or not. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 11:15, 20 November 2024 (UTC)
* '''Comment''' – In this decision, either leave the current default '''2010–12''' or ''require'' the 4-year '''2010–2012''' format. But whatever you do, ''don't'' leave it as a "dealer's choice". IOW, either leave the current, or go to the full 4 year, but don't leave both formats as "acceptable". This should be a binary choice: either choose the current, or choose the former. Leaving as a "dealer's choice" will lead to chaos and edit warring... (On my end, I've gotten very used to the current format, but the "all-4 year" format would probably be "cleaner" across the whole project...) --[[User:IJBall|IJBall]] <small>([[Special:Contributions/IJBall|contribs]] • [[User talk:IJBall|talk]])</small> 16:45, 20 June 2016 (UTC)
::::@[[User:Thryduulf|Thryduulf]] It's the Administrator's Noticeboard, naturally the vast majority of participants will be either admins or people who are involved in the same work.
** From below, either '''A)''' ''or'' '''B)''', but absolutely, positively ''not'' D), which is just a recipe with dateranges for the kind of minor edit warring over date formats, etc. on RETAIN vs. TIES grounds we have now but probably on a larger scale. --[[User:IJBall|IJBall]] <small>([[Special:Contributions/IJBall|contribs]] • [[User talk:IJBall|talk]])</small> 07:25, 2 July 2016 (UTC)
::::I don't think asking an admin to confirm they still retain the trust of the community (the whole basis of giving out admin tools to begin with) is ever really frivolous. The current process allows that at most once a year. If an admin had to stand for RFA every year, that might be a bit too much long term, but really, if any admin thinks they would not pass RRFA today, why should they retain their tools.
*** Agreed about D. It's invalid because [[MOS:RETAIN]] doesn't actually apply to this. That whole "here's how I personally think the closers should do their analysis" section with the A, B, C, etc. things, should just be hatted as unwittingly disruptive. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 11:35, 6 July 2016 (UTC)
::::Also, the sheer optics of it being mostly (from what i've seen) established admins calling this process toxic are terrible. Anyone who doesn't know anything about this process will see this as some kind of thin blue line mentality in the admin corps - and might conclude that it is time to desysop the majority of old admins to dissolve the clique.
*'''Require four-digit years''' per Fred Gandt, IJBall, Guy Macon above. For simplicity, clarity, lack of ambiguity, and for tools that automatically extract meaning from wp. Regards, [[User:James Allison|James]] (<sup>[[User talk:James Allison|talk]]</sup>/<sub>[[Special:Contributions/James Allison|contribs]]</sub>) 17:31, 20 June 2016 (UTC)
::::I wouldn't be surprised if we see a bunch of recall petitions for the most vocal critics of this process. [[User:Magischzwei|Magisch]] <sup>[[User talk:Magischzwei|talk to me]]</sup> 11:27, 20 November 2024 (UTC)
* '''Permit both styles'''... I wouldn't mind requiring "4-digit" for prose, but when it comes to usage in tables, I usually much prefer "1998–99" because it makes the column nice and narrow and there's not all the repeating of 19s or 20s down the column. But then, there are times when "4-digit" is the better choice in tables as well. —[[User:Musdan77|Musdan77]] ([[User talk:Musdan77|talk]]) 17:39, 20 June 2016 (UTC)
:::::I have no horse in this race, except that I regret not seeing the RFA earlier so I could have voted Support, sorry about that.
*'''Permit both styles, preference to two-digit except where ambiguous''' per nom. Examples: 1965–68; 2010–2011. &#128406;[[User:ATS|<span style="font-family:times;font-size:110%;color:#083884;text-shadow:1px 1px 1px">ATS</span>]]&nbsp;<b>/</b>&nbsp;[[User talk:ATS|<span style="font-family:times;color:#373;text-shadow:1px 1px 1px">Talk</span>]] 00:29, 21 June 2016 (UTC)
* '''Require all digits, except for school years, sports seasons, and potentially tables if not ambiguous''' and the like, for the good rationales given. [[User:FeatherPluma|FeatherPluma]] ([[User talk:FeatherPluma|talk]]) 01:00, 21 June 2016 (UTC)
:::::But if your argument is optics, then having a bunch of recall petitions for the people who most vocally expressed a valid opinion on an evolving policy is ''absolutely awful'' optics. At best. [[User:Gnomingstuff|Gnomingstuff]] ([[User talk:Gnomingstuff|talk]]) 01:33, 22 November 2024 (UTC)
::I took the stats from the first RRfA to test this theory:
*'''Permit both styles, preference for two-digit except where ambiguous''' I find 2 digit simpler to read, and people employ 'translations' when verbalising the written form, sometimes using the longest, sometimes the shortest form. [[User:Pincrete|Pincrete]] ([[User talk:Pincrete|talk]]) 11:07, 21 June 2016 (UTC)
*'''Question''' How does a screen reader read 2000-12 compared to 2000-2012? [[User:Only in death|Only in death does duty end]] ([[User talk:Only in death|talk]]) 11:45, 21 June 2016 (UTC)
**Just to clarify, depending on the answer to the question, my vote will be either ****-**** only or 'both allowed'. As an accessibility issue, if screen readers have issues (which I have seen on other websites, but personally have not experienced on wikipedia) with the ****-** format, generally it should be discouraged. If there is no issue, I dont see any reason it shouldnt. [[User:Only in death|Only in death does duty end]] ([[User talk:Only in death|talk]]) 13:03, 21 June 2016 (UTC)
** Paging [[User:Graham87]]... <br> On a related note, I understand that the hyphen (or en dash) between the years is silently dropped. It's possible that spelling it out the connection in words, as in "2000 to 2012" or "between 2000 and 2012", would be best for users of [[screen reader]]s. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 03:35, 26 June 2016 (UTC)
***By default, [[JAWS (screen reader)|JAWS]] reads 2000–2012 as "2000 dash 2012" and 2000–12 as "2000 dash 12". [[NonVisual Desktop Access]] omits the hyphen when it is present, but when an en dash is there, it reads "2000 en dash 2012" and "2000 en dash 12", respectively. I don't think we should let screen readers determine the guidance here; both forms are exceedingly common, and using "to" and "between" would just not work in many places. '''[[User:Graham87|Graham]]'''<font color="green">[[User talk:Graham87|87]]</font> 06:59, 26 June 2016 (UTC)
****Just to clarify: It would say 'two thousand (en)dash two thousand twelve' versus 'two thousand (en)dash twelve'? I understand punctuation is a mess, I am more familiar with braile readers ;) but to me I think the former would be preferable to the latter. [[User:Only in death|Only in death does duty end]] ([[User talk:Only in death|talk]]) 08:48, 29 June 2016 (UTC)
** According to [http://www.deque.com/blog/dont-screen-readers-read-whats-screen-part-1-punctuation-typographic-symbols/ this blog] who tested 3 screen readers - punctuation is a mess (scroll down to the table of dashes). Of note, not all screen readers will behave the same. — [[User:Xaosflux|<span style="color:#FF9933; font-weight:bold; font-family:monotype;">xaosflux</span>]] <sup>[[User talk:Xaosflux|<span style="color:#009933;">Talk</span>]]</sup> 03:50, 26 June 2016 (UTC)
*'''Comment:''' per Only in death's concern (above); I think it worth considering that if the abbreviated form is ''allowed'', it should '''only''' be so when wrapped in {{tag|abbr}} tags to assist human and machine comprehension. <code style="background:#DFF;white-space:pre">[[User:Fred Gandt|Fred Gandt]] · [[User talk:Fred Gandt|talk]] · [[Special:Contributions/Fred Gandt|contribs]]</code> 12:15, 21 June 2016 (UTC)
*'''Define full ending year as the default house style''', with local exceptions based on discussion of real need (this last part is implicit in the word "guideline" and does not need to be stated). As with any guideline, it would not be useful to say both are permissible and leave it to personal preference; that would be a guideline largely devoid of guidance, and would enable more time-wasting conflict than it prevented. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#AAA;">&#9742;</span>]] 03:52, 26 June 2016 (UTC)
* '''Require all digits''' because saving 2 digits is not a huge benefit, having multiple permissible styles gives an unprofessional look, yyyy-yy seems to be more of a US thing that is less commonly used by other countries, yyyy-yy can be confused with yyyy-mm dates, avoids editors toggling between the two formats and one universal rule is so much easier than multiple rules trying to pin down exactly when 2 digits are/aren't allowed. <span style="border:1px solid blue;border-radius:4px;color:blue;box-shadow: 3px 3px 4px grey;">[[User:Stepho-wrs|'''&nbsp;Stepho&nbsp;''']]&nbsp;<span style="font-size:xx-small; vertical-align:top">[[User Talk:Stepho-wrs|talk]]&nbsp;</span></span> 01:01, 30 June 2016 (UTC)
*'''Permit both styles.''' Retrograde step to insist on all eight digits in ''all'' situations, removing the flexibility we currently have. Even in infoboxes and tables? Nuts. [[User:Tony1|<font color="darkgreen">'''Tony'''</font >]] [[User talk:Tony1|<font color="darkgreen">(talk) </font >]] 01:43, 30 June 2016 (UTC)
:: Although I find the two digit style unnecessary, aesthetically ugly, potentially ambiguous, and arbitrary (Why not abbreviate to 1 or 3 digits? Why not for years before 1000? Why omit the grammatically correct apostrophe preceding the two digits?), I would be willing to support a guideline identical to that currently found at [[MOS:DATEVAR]], which allows the abbreviation of month names "''only when brevity is helpful (refs, tables, infoboxes, etc.)''". Which is not to say that two digits should always be used in tables and infoboxes, but rather only when a cluttering amount of (three or more) date ranges are present. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 02:18, 30 June 2016 (UTC)
:::You ask, "Why not abbreviate to 1 or 3 digits?" Do you really not understand why, or is that just rhetoric? The reason is an application of the principle that writing conventions follow speaking conventions. English speakers say and understand year ranges as follows: "1980 to 86"; "1980 to 94"; "2001 to 10" ("two thousand one to ten" ''or'' "twenty oh one to ten"); "2005 to 12"; and "2008 to 20." An English speaker would not say "1980 to 6"; "1991 to 4"; or "2011 to 7". Neither would an English speaker say "1980 to 986"; "1980 to 994"; nor "2010 to 012".—[[User talk:Finell|Finell]] 04:00, 5 July 2016 (UTC)
::::Rhetorical. My point being that it's still arbitrary, especially since the proper grammatical form is to place an apostrophe to denote the omission (i.e. 1995–’99), which is also omitted in our style. That the two-digit form has (limited) common usage doesn't mean our MOS should recommend it; I find it to be bordering on slang. Plus, in common usage, it's usually only implemented for years that immediately follow, i.e. 2008–09, not for something like 1901–87, which is silly and used virtually nowhere else but here. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 10:35, 6 July 2016 (UTC)
::::: ''the proper grammatical form is to place an apostrophe to denote the omission''—no, that is very much not an issue of grammar. [[User:Curly Turkey|Curly&nbsp;Turkey]]&nbsp;<span style="color:red">🍁</span>&nbsp;[[User talk:Curly Turkey|''¡gobble!'']] 10:38, 6 July 2016 (UTC)
::::::<small>Agreed. It's a stylistic choice based on parallelism to word contraction like "isn't" and {{"'}}tis", and it has long fallen out of favor in both actual use and in style guides when it comes to date ranges (probably from ISO's influence). Some still recommend it when an abbreviated year (or longer period) is used by itself ("back in '06", "I grew up in the '80s"), which is a style we don't use here except in quotations. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 11:35, 6 July 2016 (UTC)</small>
*'''Require full "2001–2012" syntax''', which will avoid inevitablly confusing or ambiguous constructions. This matches our treatment of page numbering ("pp. 2001–2012", except possibly in some citation styles imported from off-WP that forbid it, but this seems so rare it need not be accounted for, and I've never once had someone revert me correcting to the longer, clearer format). It also comports with our treatment of other similar ranges of numbers ("sources reported between 2,001 and 2,012 fatalities", not "sources reported 2,001–12 fatalities", which to many will imply some kind of subtraction operation).<p>'''Permit an exception for tables, if and only if all of the following apply''': a) horizontal space in the table is genuinely at a premium, b) line-breaking with "<code>2001–&lt;br /&gt;2012</code>" would be disruptive to the table layout or sortability, c) the shortened date is wrapped in {{tag|abbr}} (or the {{tlx|abbr}} template for it), {{em|and}} (not "or") d) the table also includes some shorthand dates like "1996–00" and "2012–15" that cannot be mistaken for {{var|yyyy}}–{{var|mm}} dates (i.e., do not end in "-01" through "-12"). A large table broken up into several smaller ones with the same columns, in the same article, would be considered a single table for this purpose.</p><p>'''No [[Special pleading|special exemption]] for sports or any other particular topic''', whether they use dash- or slash-delimited formatting by convention. Wikiprojects do not get to [[WP:POVFORK|PoV-fork]] their own little [[WP:LOCALCONSENSUS|local micro-consensus]] against site-wide norms, as a matter of policy. [[WP:ENG|WP is an encyclopedia]]; it is [[WP:NOT#NEWS|not sports journalism]] or mimicry of it. WP permits some specialized stylization when it does not conflict with general-audience expectations and comprehensibility needs, but [[WP:SSF|rejects it when it does]]. And '''no special pleading for "I got here first" editors'''. We already have way, way too much [[WP:OWN]]/[[WP:VESTED]]-violating "get off my article!" behavior, over micromanagement of formatting nit-picks. This has to be [[WP:MERCILESS|put to an end]], not expanded even further.<br /><span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 03:48, 30 June 2016 (UTC)</p>
* '''Prefer the unambiguous all-digits form''', with use of 2-digit shortening where space is at a premium and the meaning is obvious from context. For years not aligned with calendar years, such as 2008-09, that's a different matter, and 2-digit shortening in preferred in such cases, I think. [[User:Dicklyon|Dicklyon]] ([[User talk:Dicklyon|talk]]) 06:54, 30 June 2016 (UTC)
*'''No uniform rule''' There is not a compelling case for any one choice. As such, we should let authors decide, and proceed on the basis of [[MOS:RETAIN]]. If projects can agree on local consensus for the type of material they cover, that is fine too, but if it results in disputes, [[MOS:RETAIN]] should resolve it. [[User:Monty845|<span style="color:Green;">Monty</span>]][[User talk:Monty845|<small><sub><span style="color:#A3BFBF;">845</span></sub></small>]] 01:23, 1 July 2016 (UTC)
**MOS:RETAIN cannot actually apply to this, because both styles are not equally appropriate – one of them leads to inevitable ambiguities and confusion. RETAIN only applies when the choice between two+ options is completely arbitrary and makes no practical difference. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 11:35, 6 July 2016 (UTC)
*'''Require all digits, with limited exceptions''', these being for a "year" that spans two calendar years, e.g. an academic year or a sporting year. [[User:Peter coxhead|Peter coxhead]] ([[User talk:Peter coxhead|talk]]) 10:13, 2 July 2016 (UTC)
*'''Permit both styles, prefer four digits''' per most of the arguments above. Four digits is less ambiguous and we don't need to worry about space because [[WP:NOTPAPER]]. [[User:Kaldari|Kaldari]] ([[User talk:Kaldari|talk]]) 15:43, 2 July 2016 (UTC)
* Either '''require full years''' or '''allow both'''. I agree that some ranges are ambiguous in their meaning. Stylistic inconsistency is also another problem. When we have a range that goes from 1990 to 2000 (1990–2000) next to a range that goes from 2001 to 2016 (2001–16), it looks a bit weird. [[User:NinjaRobotPirate|NinjaRobotPirate]] ([[User talk:NinjaRobotPirate|talk]]) 17:13, 2 July 2016 (UTC)
*'''Prefer four digits, permit two digits for two-year spans.''' The two-digit format is fine for a school year or TV season, where the meaning is unambiguous; otherwise four digits. [[User:BlackcurrantTea|BlackcurrantTea]] ([[User talk:BlackcurrantTea|talk]]) 17:33, 2 July 2016 (UTC)
*'''Permit both styles'''. This doesn't need to be micro-managed. Leave it to editorial discretion. --[[User:Trovatore|Trovatore]] ([[User talk:Trovatore|talk]]) 17:57, 2 July 2016 (UTC)
*'''Require all digits''' &ndash; The only way this could be more confusing than it is now is if some ranges had two digits and some had four. [[User:KSFT|<font color="22DD77"><b>KSF</b></font>]][[User talk:KSFT|<font color="2277DD"><b>T</b></font>]][[Special:Contributions/KSFT|<sup><font color="33DD44"><b>C</b></font></sup>]] 18:57, 2 July 2016 (UTC)
*'''Require full years with a few exceptions''' having all the digits reduces the chance of confusion, increases accessibility, and avoids unnecessary abreviations that just don't look formal. However, the two digit format should still be available for labelling types of years that don't quite match up (sports seasons, chool years, Catholic liturgical year etc.) and in tables and infoboxes where space actually matters. [[user:Happysquirrel|Happy Squirrel]] ([[user talk:Happysquirrel|talk]]) 21:56, 2 July 2016 (UTC)
*'''Permit both styles''' as this should be considered on a case-by-case basis per the good points made above. [[user:Andrew Davidson|Andrew D.]] ([[user talk:Andrew Davidson|talk]]) 10:29, 3 July 2016 (UTC)
*'''Decline to Decide this RFC''' or '''Retain current guideline, but omit exception for special subject matter.''' Crumpled Fire states, "Objections have been raised regarding this guideline before" and that "many" (but ''not'' a consensus) agreed with his or her position, but obliquely acknowledges that these objections never achieved consensus ("but it never proceeds any further"). The issue was decided by consensus at [[WP:MOSNUM]] in January 2014; even then, the topic heading was preceded by "Redux". Crumpled Fire reopened the discussion in early June on the [[WP:MOSNUM]] talk page, but got no traction there, so Crumpled Fire brings it here to a different forum. Stability in a style manual is desirable for its own sake. Changing the guideline would require a massive project of revising articles that complied with the existing guideline. If a genuine problem existed, that would justify changing the guideline, but no one has identified a genuine problem. Personal preference for a different style does not, in my opinion, warrant a change to the MOS. Also, does Village Pump want to become the Court of Appeals for the innumerable MOS disputes? I propose that the Village Pump decline to decide this RFC and leave it to the MOS discussion to resolve. Regarding the guideline itself, I would change the current guideline insofar as it makes exceptions based on subject matter (e.g., sports). The MOS guides Wikipedia articles. Wikipedia should not abandon its house style guide because sports (or other publications) follow a different style guide.—[[User talk:Finell|Finell]] 00:36, 4 July 2016 (UTC)
*'''Permit 4-digit years''' As noted by Curly Turkey, this is silly micromanagement; MOS needs to be in the business of enforcing general provisions such as WP:ENGVAR, WP:CITEVAR, and WP:ERA, not dictating details to article writers. One of those general provisions (already in there) needs to be that we follow naming conventions in article collections; it doesn't really matter whether we have articles on the National Basketball Association seasons for 2010-2011 and 2011-2012 or 2010-11 and 2011-12, but we need to be careful not to have articles on the seasons for 2010-2011 and 2011-12. And coming here is a great way to cut through the dictatorship of the few MOS trolls: we need to break their dominance. [[User:Nyttend|Nyttend]] ([[User talk:Nyttend|talk]]) 01:57, 6 July 2016 (UTC)
*'''Permit 4-digit years'''. I would prefer to say require four digits, but the MoS should advise not require. [[User:SlimVirgin|SarahSV]] <small><sup>[[User_talk:SlimVirgin|(talk)]]</sup></small> 04:22, 6 July 2016 (UTC)
*'''Prefer two year, permit both''' - My concern is the literal thousands date ranges used on television pages which are fairly uniform with two years. This includes season section headers. Which reflex could handle it, it would be a large undertaking if for years is required. I prefer two years for season headers personally. There's no ambiguity the ranges imho. If allow both, treat like ERA as mentioned others. Also allow project mos to state a preference per consensus at that project. [[User:EvergreenFir|'''<span style="color:#8b00ff;">Eve</span><span style="color:#6528c2;">rgr</span><span style="color:#3f5184;">een</span><span style="color:#197947;">Fir</span>''']] [[User talk:EvergreenFir|(talk)]] <small>Please &#123;&#123;[[Template:re|re]]&#125;&#125;</small> 04:32, 6 July 2016 (UTC)
*'''Prefer or require 4-digit years'''. To have the MOS or drive-by editors enforce a specific two-digit form is just ludicrous. Four digits are clear, immediately understandable, and completely unambiguous. The wiki servers are not going to freeze because of two extra characters. If two digits work better in some instances or in some articles, perhaps allow that as well if agreed to by consensus. But don't dictate two-digits -- that's just silly; it's like dictating a serial comma (or no serial comma). [[User:Softlavender|Softlavender]] ([[User talk:Softlavender|talk]]) 05:01, 6 July 2016 (UTC)
*'''Retain existing format''' - Requiring the first two digits for ranges in the same century is requiring unnecessary redundancy. I'm not convinced by the argument that "2000-10" is ambiguous and could be read as October 2010, as this is not a format that is acceptable for anything other than year ranges. Most importantly, tables and infoboxes often require abbreviated formats and the existing format caters for this requirement while yyyy-yyyy does not. --[[User:AussieLegend|'''<span style="color:#008751;">Aussie</span><span style="color:#fcd116;">Legend</span>''']] ([[User talk:AussieLegend#top|<big>✉</big>]]) 09:00, 6 July 2016 (UTC)
::The format "2000-10" may not be acceptable to represent "YYYY-MM" ''according to current MOS'' (i.e., a wikipedia standard) but it is certainly valid by the [[ISO 8601]] standard that blesses and defines many date formats. [[User:DMacks|DMacks]] ([[User talk:DMacks|talk]]) 09:13, 6 July 2016 (UTC)
:::And? [[WP:ISNOT]] the ISO. We have a different audience; much of ISO 8601 is intended for machine parsing, not human prose. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 11:22, 6 July 2016 (UTC)
*'''Permit 4-year but do not require''' – for many of the same reasons noted above. There may be situations in which the use of two digits is well understood and appropriate, so requiring four digits in all instances is unnecessary (not to mention tedious instruction creep that would require a lot of changes to exising articles that already use the two-digit format). --[[User:GoneIn60|GoneIn60]] ([[User talk:GoneIn60|talk]]) 11:48, 6 July 2016 (UTC)
*'''Prefer 4-digit years but allow 2-digit years''' in certain cases like consecutive years, within the same decade, etc. if the context is clear. ---- [[User:Patar knight|Patar knight]] - <sup>[[User talk:Patar knight|chat]]</sup>/<sub>[[Special:Contributions/Patar knight|contributions]]</sub> 18:07, 7 July 2016 (UTC)
*'''Retain existing format''' – Wikipedia is a professional, formal encyclopaedia and requires a high standard of writing and formatting. This is the very reason that guidelines such as this exist. Allowing both options would just be messy and inconsistent, and will lead to confusion for readers who get used to seeing the XXXX-XXXX format and then come across the XXXX-XX format. We need to be consistent with this, it's just common sense. Likewise, there is no reason for Wikipedia to suddenly ignore basic writing and referencing conventions by changing to the XXXX-XXXX format. What I'm saying is, not only is writing out both years in full every time completely redundant and counter-intuitive for everyday, casual writers, it is also amateurish and unbecoming of an encyclopaedia given that XXXX-XX is {{em|the}} academic and professional format found in at least the most common style guides. And if people confuse '2010-12' with 'December 2010', especially in what is presumably well-written prose that provides context, then that is their fault. No respectable encyclopaedia would present a date like that, just as one wouldn't present a year range like you want to. By the way, why isn't this discussion taking place at [[WP:MOSNUM]]? - [[User:Adamstom.97|adamstom97]] ([[User talk:Adamstom.97|talk]]) 22:08, 7 July 2016 (UTC)
*'''Prefer 4-digit years, permit 2-digit where space is an issue'''. This is a guideline that is widely ignored anyway; best update it to general practice. At the very least require 4-digit years in most tables, where the 2-digit ones play havoc with both aesthetic and sorting. [[User:Frickeg|Frickeg]] ([[User talk:Frickeg|talk]]) 04:58, 9 July 2016 (UTC)
*'''Permit 4-digit years''' - I've never agreed with the 2 digit thing and IMHO 4 digits look much better, Plus as the years continue the 2 digit thing will only get more confusing, 4 is IMHO better. –[[User:Davey2010|<span style="color: blue;">'''Davey'''</span><span style="color: orange;">'''2010'''</span>]]<sup>[[User talk:Davey2010|<span style="color: navy;">'''Talk'''</span>]]</sup> 14:27, 11 July 2016 (UTC)


{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
===Extended discussion of DATERANGE RfC===
|+ 1st RRfA votes
A short discussion was [[Wikipedia_talk:Manual_of_Style/Dates_and_numbers#WP:DATERANGE_again|initially had at the MoS/Dates and numbers talk page]] (the latest of many which went nowhere) regarding the re-introduction of the four-digit endrange year in [[WP:DATERANGE]]. When some support was garnered but discussion again stalled, it was then [[Wikipedia:Village_pump_(policy)#WP:DATERANGE_ambiguity_and_stylistic_concerns|expanded to a discussion and !vote here at the Village Pump]], garnering a high level of agree !votes to return to the original style of allowing—or even preferring—four-digit end years (''i.e. 2000–2016'') instead of the current two-digit end years (''i.e. 2000–16'') for ranges that occur post-11th century and within the same century.
!
! Support
! Oppose
! ''Total''
|-
! Administrators
| 48
| 29
| ''77''
|-
! Non-admins
| 71
| 116
| ''187''
|-
! ''Total''
|'' 119''
| ''145''
| '''''264'''''
|}
::Administrators made up 29% of the voters. If being an admin doesn't influence anyone's vote, then we can expect admins to make up roughly 29% of the supporters and 29% of the opposers. But this didn't happen. In the final results, administrators made up 40% of the supporters and 20% of the opposers. We can also look at the individual odds of supporting/opposing depending on user rights. It ended at 45% support, so you'd expect admins to have a 45% chance of supporting and a 55% chance of opposing. But this also didn't happen. If you choose any admin at random, they had a 62% chance of supporting and a 38% chance of opposing (ignoring neutrals). Non-admins were the opposite: they had a 38% chance of supporting and a 62% chance of opposing.


::So our next question should be why it was so much more likely for an admin to support the RRfA relative to a non-admin. The obvious answer is of course as you said: admins have a perverse incentive to support here, especially if they're not-so-great admins who know they probably don't have the trust of the community anymore. Also suggested during the RRfA is the comradery that comes from working alongside a fellow admin for so long. I'd be interested in seeing how account age affects likelihood of supporting, but that's not something that can be counted up in a few minutes like admin status. [[User:Thebiguglyalien|<span style="color:#324717">The</span><span style="color:#45631f">big</span><span style="color:#547826">ugly</span><span style="color:#68942f">alien</span>]] ([[User talk:Thebiguglyalien|<span style="color:sienna">talk</span>]]) 17:48, 20 November 2024 (UTC)
In addition to the points made and support garnered at the Village Pump, it's becoming clear to me that the general editing public (and likely the general public itself) finds the 2000–16 format disagreeable, as I've already had to revert '''three instances''' ([https://en.wikipedia.org/enwiki/w/index.php?title=Anton_Yelchin&diff=prev&oldid=727482362],[https://en.wikipedia.org/enwiki/w/index.php?title=Anton_Yelchin&diff=prev&oldid=726247993],[https://en.wikipedia.org/enwiki/w/index.php?title=Anton_Yelchin&diff=prev&oldid=726090890]) within the last few days of someone changing "2000–16" to "2000–2016" in the infobox for [[Anton Yelchin]] (a high-traffic article due to the subject's recent death). As suggested by a user at the Village Pump discussion, I am opening an RfC to hopefully determine once and for all whether the community at large agrees it's time to re-introduce four-digit end years in ranges. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 13:12, 29 June 2016 (UTC)
:::I believe it may be centered on the idea that we all make mistakes, and many of us like to think we'd be given a chance to grow and learn from said mistake, instead of being forced through the RfA process again. But I recognize I may be being overly optimistic on that, and that others may not have the same thoughts on the matter that I do. Many admins I've spoken to would simply choose to give up their tools as opposed to go through an RfA again, something I've also considered despite my relatively smooth RfA. I'm also not sure Graham is the best representation of that. I voted support, recognizing that Graham87 has made mistakes, but also recognizing the significant contributions they've made and their pledge to do better. Bluntly, I did so expecting the vote to fail, and wanting to show some moral support and appreciation for their work. There's certainly a psychological aspect involved in it, but I don't think that, generally speaking, those of us who voted support or have issues with the current process are doing so out of self preservation.
:::There's a lot of numbers that could be analyzed, such as the history of those admins who vote at RfA (whether they often vote support or don't vote at all), but it's hard to draw meaningful conclusions from this small of a dataset. [[User:Hey man im josh|Hey man im josh]] ([[User talk:Hey man im josh|talk]]) 19:14, 20 November 2024 (UTC)
::::On paper, I get that. The thing is, I don't know whether you saw [https://en.wikipedia.org/wiki/Wikipedia:Requests_for_adminship/Graham87_2#c-Levivich-20241117223500-Oppose Levivich's comment] or [https://en.wikipedia.org/wiki/Wikipedia:Requests_for_adminship/Graham87_2#c-Bradv-20241120021000-Oppose bradv's comment], but you'd be hard-pressed to find a less appropriate time to test the "chance to grow" theory than the absolutely deplorable behavior that we saw from Graham for many years with far too many chances to improve. If it were down to me, this should have been a block in 2023 rather than a desysop in 2024. [[User:Thebiguglyalien|<span style="color:#324717">The</span><span style="color:#45631f">big</span><span style="color:#547826">ugly</span><span style="color:#68942f">alien</span>]] ([[User talk:Thebiguglyalien|<span style="color:sienna">talk</span>]]) 19:32, 20 November 2024 (UTC)
:::I'm late to the discussion, but I think it's also worth pointing that only 7 of the 25 users who signed Graham87's petition and 2 of the 25 on Fastily's were admins. ~~ [[User:Jessintime|Jessintime]] ([[User talk:Jessintime|talk]]) 13:16, 23 November 2024 (UTC)
:: I would add that there is a potential wrinkle in this analysis. I'm an extended-confirmed user here (and thus would likely be counted as a non-admin), but I am a sysop on Commons so I would have my own perspective on the matter. [[User:Abzeronow|Abzeronow]] ([[User talk:Abzeronow|talk]]) 21:06, 22 November 2024 (UTC)


:Well, I'm not an admin and I started this thread. I'm all for having an admin recall process by the community in place. I'm also also for a process for course correction by the community in areas where and admin has drifted off course but where the problem is fixable. Administrative Action Review has the potential to become this but that has been stymied by various things. Sincerely, <b style="color: #0000cc;">''North8000''</b> ([[User talk:North8000#top|talk]]) 14:24, 20 November 2024 (UTC)
While if one were writing an informal blog or a company memo, one might not care what date format was used, and not really care all that much if a few people had some difficulty with it, on Wikipedia the fact that alternative styles can be attested to exist [[WP:NOT#PAPER|does {{em|not}} mean]] that every imaginable paper-medium style must be permitted, willy-nilly; we have a mission and responsibility to be as accessible to and clearly informative for as many readers as possible. Most of [[WP:MOS]] and its subpages consist of [[best practices]] selected from a range of possible practices, and selected (especially in favor of clarity over ambiguity, even at the cost of a tiny bit of brevity) by consensus on the basis of experience with what does and does not work well on WP, what leads to continual strife when no firm rule is provided, what [[WP:COMMONSENSE]] suggests, and what the preponderance of external style guides recommend. On all four counts, we are pointed toward using the full "2001–2012", not shorthand "2001–12", format. The shorthand style is primarily used in journalism, where saving space is often taken to matter more than clarity, and inside academic citation formats in particular fields, especially those also geared toward maximum compression, for reduced journal printing cost and for expert convenience, at the expense of "lay" readability (e.g. "Jacksom PM, Garcia AG. ''AmJPsych''", versus the "Jackson, P. M.; Garcia, A. G. ''American Journal of Psychology''" we expect here). <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 03:48, 30 June 2016 (UTC)
::I think, fundamentally, the problem is that admins have a direct and concrete conflict of interest in this discussion. Of course an admin would be naturally opposed to more mechanisms that might make them lose their permissions, especially since desysops are very rare at the moment.
:<small>[[User:SMcCandlish|SMcCandlish]], expanding "Jackson" to "Jacksom" is not a form of compression :-) [[User:Nyttend|Nyttend]] ([[User talk:Nyttend|talk]]) 02:00, 6 July 2016 (UTC)</small>
::I also don't really agree that the current recall process is all that toxic. You could get rid of the discussion section, as the recall is only a petition, not a consensus discussion, but that's about it. [[User:Magischzwei|Magisch]] <sup>[[User talk:Magischzwei|talk to me]]</sup> 18:33, 20 November 2024 (UTC)
::<small>{{ping|Nyttend}} Danm it, I cam't blane mobile auto-correct for that ome. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span></small>
:::{{tq|Of course an admin would be naturally opposed to more mechanisms that might make them lose their permissions}} – I wholeheartedly disagree with this assertion. There's a number of us that fully support a recall process, including quite a few people who have historically been open to recalls. This is an over simplification of the motives of a large group of experienced editors, many of which have legitimate and reasonable concerns about the process in its current form. [[User:Hey man im josh|Hey man im josh]] ([[User talk:Hey man im josh|talk]]) 19:15, 20 November 2024 (UTC)
::::Substantially all criticism i've seen so far of the process have boiled down to "RFA is abusive and it's unreasonable to make people go through that again". And yet, instead of attempting to change that, the only suggestions seem to be to support older admin's rights to have their permissions continue being grandfathered in. [[User:Magischzwei|Magisch]] <sup>[[User talk:Magischzwei|talk to me]]</sup> 19:27, 20 November 2024 (UTC)
:::::I'm sorry that that's all you've taken away from the vast amounts of criticism given by people. Perhaps consider focusing on whether the process, in its current state, makes sense instead of focusing on older admins. I'm a relatively new admin and I don't support the current iteration of the process. [[User:Hey man im josh|Hey man im josh]] ([[User talk:Hey man im josh|talk]]) 19:30, 20 November 2024 (UTC)
::::::I think it's eminently sensible to have adminship not be a lifetime appointment, both by the fact that norms change even when people dont, and that I see people in every RFA expressing reluctance over granting lifetime tools. I also think that assuming RFA isn't a big deal regular reconfirmations make sense. IFF RFA is a big deal, then the focus should be on fixing that.
::::::It seems to me that existing admins being immune to having to suffer RFA again has created a lack of pressure to actually make it into a functional, nontoxic process.
::::::Take my opinion for what it's worth though. I'm not an admin nor do I foresee myself ever having aspirations to become one. [[User:Magischzwei|Magisch]] <sup>[[User talk:Magischzwei|talk to me]]</sup> 19:43, 20 November 2024 (UTC)
:::::Attempting to improve RFA is a ''very'' hard problem that people have been working on since before you joined Wikipedia, and are still working on it. I would also say that {{tpq|it is unreasonable to make people go through that again}} is a mischaracterisation of the views expressed, which are {{tpq|it is unreasonable to make people go through that again unnecessarily}}, which is significantly different. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 19:31, 20 November 2024 (UTC)
::::::I just found out about this discussion, and it looks to me like the same or similar things are being discussed in way too many different places. Anyway, I'm someone who has stated repeatedly and strongly in multiple places that I think the recall process is a disaster, and is beyond repair. And, contra some statements above, here are some other facts about me. I'm not an admin. I opposed Graham's re-RfA. And I played a central role in [[WP:CDARFC]]. --[[User:Tryptofish|Tryptofish]] ([[User talk:Tryptofish|talk]]) 20:12, 20 November 2024 (UTC)
:I would be against it for a different reason: if we allow both supports and opposes, then the recall petition becomes a mini-RfA with the same amount of pressure as the RRfA itself (especially since, given the identical threshold, the recall's result would be indicative of the RRfA's subsequent result). Since anyone can start the recall petition, it functionally means that ''anyone'' can force an admin to re-RfA, which is clearly worse.<br>On the other hand, having a set number of supports needed provides for a "thresholding" of who can open a RRfA, while not necessarily being as stressful. If anything, I would say the recall should become more petition-like (and thus less stressful for the recalled admin), rather than more RfA-like. [[User:Chaotic Enby|<span style="color:#8a7500">Chaotic <span style="color:#9e5cb1">Enby</span></span>]] ([[User talk:Chaotic Enby|talk]] · [[Special:Contributions/Chaotic Enby|contribs]]) 20:01, 20 November 2024 (UTC)


:The ones most likely to be booted are bad admins who are abusive toward the editor community and who negatively represent themselves as admins. Both of the recalls thus far were just exact examples of that and worked perfectly as designed and needed. The process worked exactly as desired and removed bad admins who deserved to be desysopped. Though I do think the discussion section of the petitions should be more regulated. Discussion should be about the admin's actions and conduct and nothing else. Any extraneous commentary should be removed. [[User:Silver seren|<span style="color: dimgrey;">Silver</span>]][[User talk:Silver seren|<span style="color: blue;">seren</span>]]<sup>[[Special:Contributions/Silver seren|C]]</sup> 00:23, 21 November 2024 (UTC)
For transparency, recording that I'm notifying [[WP:TV]] of this rfc as it will impact most pages within the project's scope. [[User:EvergreenFir|'''<span style="color:#8b00ff;">Eve</span><span style="color:#6528c2;">rgr</span><span style="color:#3f5184;">een</span><span style="color:#197947;">Fir</span>''']] [[User talk:EvergreenFir|(talk)]] <small>Please &#123;&#123;[[Template:re|re]]&#125;&#125;</small> 04:36, 6 July 2016 (UTC)
::When I first started editing Wikipedia almost 20 years ago, I was struck by what, to me at least, appeared to be widespread incivility. Among a number of things which have changed for the better IMHO is an all round expectation that everyone's standards of behaviour should rise (and they have). The admin role breeds a certain "culture" (for lack of a better term) akin to a conservationist, the role is to "protect" Wikipedia from "harm" and I can certainly see why being an admin could be a deeply frustrating experience. However, what has happened, I think, in the attrition of the admin corps, and the turnover in the non-admin corps, is that the generalised culture of "regular" non-admin editors has moved further forward towards less acceptance of a culture prevalent 10-15 years ago. I think also the rise in editors from non-English speaking backgrounds and from the Global South has caused complexities for those with limited experience outside the anglosphere. The statistics above on the vote for G87's RRFA show an interesting split between admins and non-admins, and within admins. Non-admins were almost overwhelmingly (close to 2/3) of the view that G87 had been given an almost exceptionaly long period to improve, had not, and no longer held their trust. 5/8s of admins, appeared (and comments here also seem to confirm this) split between solidarity for one of their own and displeasure with the recall process. 3/8s admins were in alignment with the majority of non-admins. FWIW, I'm not trying to point to some grand schism; A 38/62 admin split on these numbers is not that profound - if just 9 admins had changed their vote from support to oppose it would have been a 50/50 split. To reiterate, I'm not suggesting that there is a great gap between admins and non-admins, but there does appear to be some gap when it comes to generalised views around the expected behaviour of admins. Regards, [[User:Goldsztajn|Goldsztajn]] ([[User talk:Goldsztajn|talk]]) 01:01, 21 November 2024 (UTC)
:::Maybe the divide is not between admins and non-admins but between newer and longer-serving editors (who are more likely to be admins)? [[User:Hawkeye7|<span style="color:#800082">Hawkeye7</span>]] [[User_talk:Hawkeye7|<span style="font-size:80%">(discuss)</span>]] 01:20, 21 November 2024 (UTC)
::::I don't disagree, and in effect I was sort of saying the same thing in terms of the attrition of the admin corps and turnover in non-admin corps. FWIW, I do think there are some generalised feelings about admins among non-admins; for example, admins are less likely to face sanction than non-admins. How true that actually is I'm not sure and the point would be that a group of people already tested in commnuity trust (ie RFA) are less likely to breach that trust. However, comments in the G87 RRFA and the strength of the vote suggest there are (wrongly or rightly) widely felt perceptions of disparity. Regards, [[User:Goldsztajn|Goldsztajn]] ([[User talk:Goldsztajn|talk]]) 01:53, 21 November 2024 (UTC)
::::I'm currently compiling the data to get some statistics about voters in Graham's re-RFA. I'm a bit less than halfway through so it might be a couple of days before I can present any results. However among the first 113 support voters the maximum account age (on the day the re-RFA started) was 7919 days (21 years), the minimum was 212 days and the average was 4785 days (13 years). I have no data yet for neutral or oppose voters so cannot say how that compares. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 02:03, 21 November 2024 (UTC)
:::::Do you have a handy list of all voters for RFA? It should be simple enough to use a [[WP:QUARRY]] to find out all details about the voters if someone finds an easy enough scrape of who each user is [[User:Soni|Soni]] ([[User talk:Soni|talk]]) 05:51, 21 November 2024 (UTC)
::::::@[[User:Soni|Soni]]: [https://apersonbot.toolforge.org/vote-history/?page=Wikipedia%3ARequests%20for%20adminship%2FGraham87%202]. [[User:Levivich|Levivich]] ([[User talk:Levivich|talk]]) 07:09, 21 November 2024 (UTC)
:::::::Here's the Quarry query editcount/registration date for [https://quarry.wmcloud.org/query/88070 Supports], [https://quarry.wmcloud.org/query/88072 Neutrals], [https://quarry.wmcloud.org/query/88073 Opposes].
:::::::I think about 6 editors were missed by the tool you linked, but it should not change overall patterns much so we can just use this as is. [[User:Soni|Soni]] ([[User talk:Soni|talk]]) 07:24, 21 November 2024 (UTC)
::::::::Prepare to not be surprised. Supporters/Opposers:
::::::::*Median registration date 2008/2014 <-- Behold, Wikipedia's generational shift
::::::::*Average registration date: 2011/2014
::::::::*Median edit count: 40,293/17,363
::::::::*Average edit count: 76,125/43,683
::::::::Thanks for doing the quarry. Teamwork makes the dream work! [[User:Levivich|Levivich]] ([[User talk:Levivich|talk]]) 05:17, 22 November 2024 (UTC)
:::::At a quick glance, it seemed like editors with more edits were more likely to support while editors with fewer edits (with one exception) were more likely to oppose. - [[User:Enos733|Enos733]] ([[User talk:Enos733|talk]]) 07:54, 21 November 2024 (UTC)
::::::Given a single admin action may involve multiple edits, it's not so surprising the supporters' list possibly reflects a group with higher edit counts. Personally, I'd be more inclined to draw conclusions from length of registration rather than edit count. Regards, [[User:Goldsztajn|Goldsztajn]] ([[User talk:Goldsztajn|talk]]) 09:11, 21 November 2024 (UTC)
:::::::my very, very rapid count - supports 35/117 (30%) less than 10 years old, opposes 67/141 (48%) less than 10 years old. In absolute numbers, 10+ year accounts were 82 supports, 74 opposes - actually quite even. What was crucial was younger accounts. It does confirm my sense of gaps between "older" and "younger" generations in regard to perceptions of tolerable admin behaviour. Regards, [[User:Goldsztajn|Goldsztajn]] ([[User talk:Goldsztajn|talk]]) 09:50, 21 November 2024 (UTC)


We have had two recalls as of now. The people signing the recall were by and large not trolls, vandals, people blocked by that admin, ... but regular editors in good standing and without a grudge. One of these recalls has been supported by the RRFA afterwards, and the other admin decided not to go for a RRFA. There is ''zero'' evidence that the process is flawed or leads to results not wanted by the community at large. While minor issues need working out (things like "should it be closed immediately the moment it reaches 25 votes or not"), the basic principles and method have so far not produced any reason to fundamentally "fix" the issue. That the process highlights a gap between parts of the community (see e.g. the Graham RRFA) doesn't mean that the process needs fixing. The process only would need fundamental fixing if we would get successful recalls which would then be overwhelmingly reversed at RRFA, showing that the recall was frivolous, malicious, way too easy... Not now though. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 09:24, 22 November 2024 (UTC)
====Possible outcomes?====
: I agree with Fram. There is not any evidence that the recall process is reaching outcomes that are not supported by the Community (I voted Oppose on the Graham RRFA; I don't know how I would have voted on a Fastily RRFA). Small fixes to the process if supported would not be indicative of the process itself being fundamentally flawed. [[User:Abzeronow|Abzeronow]] ([[User talk:Abzeronow|talk]]) 21:15, 22 November 2024 (UTC)
<small>''Keep in mind that this policy applies to years 1000–present only, and only to ranges that stay within the same century.''</small>
:I agree that it just needs fixes.<b style="color: #0000cc;">''North8000''</b> ([[User talk:North8000#top|talk]]) 15:24, 23 November 2024 (UTC)
*A) Status quo (prefer 2-digit, no explicit allowance of 4-digit)
*B) Only allow 4-digit end-range years
*C) Only allow 2-digit end-range years
*D) Equally allow both, using whichever is established/the first editor used, and discuss prior to change (similar to CE/AD policy)
*E) Prefer one, but allow the other in certain circumstances (specify details in your comment)


I believe that desysoppings for cause should only happen when there is objective evidence of misconduct. My main concern about the recall process is that it may be wielded against administrators who are willing to take actions that are controversial, yet necessary. Examples of actions that have got administrators hounded include (1) closing contentious and politically charged AFD discussions; (2) blocking an "[[WP:UNBLOCKABLE]]" editor who is being disruptive or making personal attacks; (3) stepping up to protect a politically charged article to stop an edit war. None of these actions are administrator misconduct, but in a heated dispute the side that has an admin rule in their disfavor may quickly resort to punishing said administrator by starting a recall petition, and in a dispute involving many editors, getting to 25 may be easy. Even if that petition fails, it is so unpleasant that it may have a chilling effect on admin involvement even when needed. [[User:Sjakkalle|Sjakkalle]] [[User talk:Sjakkalle|<small>(Check!)</small>]] 21:14, 23 November 2024 (UTC)
As the proposer, the outcome I support is '''B''', as I see no benefit to reducing 4-digit years to 2 digits arbitrarily in any case, ranges or otherwise, as argued previously. — '''[[User talk:Crumpled Fire|<font face="Lucida Fax"><font color="#2695A9">Crumpled Fire</font></font>]]'''<small> • ''[[Special:Contributions/Crumpled Fire|contribs]]'' •</small> 14:26, 29 June 2016 (UTC)
: In which case, a RRFA might be overwhelmingly in favor of the administrator and thus vindicate the administrator. I would definitely vote in support of an administrator if those any of those three were the impetus behind a recall. I also trust our editors, and so far, the recall process has worked as intended. [[User:Abzeronow|Abzeronow]] ([[User talk:Abzeronow|talk]]) 21:50, 23 November 2024 (UTC)
:This isn't helpful, and should be hatted. Anyone can add another proposed option at any time; you can't constrain people to what you see as the possible outcomes, and it's not your job to steer the closer's analysis. Also, MoS is a guideline not policy.<p>'''D has fatal problems''', per [[WP:OWN]], [[WP:MERCILESS]], and [[WP:VESTED]]; while we do have some article-wide, anti-[[WP:POINT]] "don't fiddle with stuff just to fiddle with it" provisions like [[MOS:DATEVAR]], [[MOS:ENGVAR]], and [[WP:CITEVAR]], they do not permit micro-management of something like this, i.e. exactly which formatting of a date, {{em|within}} the variations of a particular DATEVAR, is used in a particular table or whatever. Furthermore, [[MOS:RETAIN]] does not and cannot apply here, only when the choice between options is arbitrary and makes no real difference; one of these styles (the "2001-09" one) leads to inevitable ambiguities and confusion, so it fails this test automatically. <small>(Also, it's not really similar to CE/AD, which is not "use whichever one you like best, and thereafter no one can change it without an RfC"; there are contextual rationales to use one vs. the other (e.g. an article on geology vs. an article on biblical historicity.)</small></p><p>I think you should {{tl|collapse}} this subsection, let discussion continue freely, and let the closer decide what outcomes have been proposed and which if any has consensus. Or an admin should {{tl|hat}} it. While I know it wasn't intended that way, it's disruptive to the RfC process. People are starting to insert objections to your enumerated "possibilities" into their original comments, etc. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 11:44, 6 July 2016 (UTC)</p>
:ArbCom have to face re-election. Does that have a chilling effect on the arbitrators? [[User:Hawkeye7|<span style="color:#800082">Hawkeye7</span>]] [[User_talk:Hawkeye7|<span style="font-size:80%">(discuss)</span>]] 21:48, 23 November 2024 (UTC)
:: That's a facile argument. Arbitrators are well aware that they are standing for a fixed term period. [[User_talk:Black Kite|Black Kite (talk)]] 21:50, 23 November 2024 (UTC)
::It's driving me up the wall that people keep saying that the process has worked as intended. Come back and tell me that, after you can link to an RRfA for Fastily that resulted in whatever result you define as working as intended. --[[User:Tryptofish|Tryptofish]] ([[User talk:Tryptofish|talk]]) 22:01, 23 November 2024 (UTC)
:::Choosing not to do an RRfA was their own choice, particularly if Fastily thought it wouldn't be successful. It was also their choice to make no attempt whatsoever to defend the reams of evidence presented against them in the recall petition of their negative actions toward the editing community. So, yes, Fastily as well was an example of the process working as intended. [[User:Silver seren|<span style="color: dimgrey;">Silver</span>]][[User talk:Silver seren|<span style="color: blue;">seren</span>]]<sup>[[Special:Contributions/Silver seren|C]]</sup> 22:08, 23 November 2024 (UTC)
:::: Or perhaps they just thought "well, I've put XX years into this and a load of random people with rationales ranging from reasonable to utterly non-existent have told me I'm not fit to do it, so f*** you". If that's the case, I don't blame them. [[User_talk:Black Kite|Black Kite (talk)]] 22:13, 23 November 2024 (UTC)
:::::Maybe, maybe not. Probably not though right? Seems kind of silly. [[User:PackMecEng|PackMecEng]] ([[User talk:PackMecEng|talk]]) 22:17, 23 November 2024 (UTC)
:::::: I suspect that might be my reaction, to be honest. [[User_talk:Black Kite|Black Kite (talk)]] 22:24, 23 November 2024 (UTC)
:::::::He was going to lose if he didn't apologize, and he didn't want to apologize. That simple. As others have said, that was his choice to make, and I respect it. [[User:Levivich|Levivich]] ([[User talk:Levivich|talk]]) 22:28, 23 November 2024 (UTC)
::::::::Except that he ''did'' apologize, although there were differing views of whether that apology was enough. This oversimplification is what's wrong with the way discussions happen in this process. --[[User:Tryptofish|Tryptofish]] ([[User talk:Tryptofish|talk]]) 22:34, 23 November 2024 (UTC)
:::::::::He woulda had to apologize more, then, including for the stuff that came out during the petition, and any other stuff that may have come out during the RRfA. He woulda had to answer questions about it, make promises, etc., basically go through what Graham went through, and realize that even that (answering questions, making promises) might not be enough (as it wasn't for Graham). It's not at all irrational for someone to choose not go through that. Being an admin isn't worth all that to some (e.g., to me), especially if you might not get it despite your best efforts. [[User:Levivich|Levivich]] ([[User talk:Levivich|talk]]) 22:44, 23 November 2024 (UTC)
::::::::::"Someone decided that it just isn't worth it" does not equal "the process worked". --[[User:Tryptofish|Tryptofish]] ([[User talk:Tryptofish|talk]]) 22:47, 23 November 2024 (UTC)
:::::::::::No, those two things are not the same. If you want to know why I think the process worked, it's because it stopped disruption, did it faster than Arbcom, and I think with less drama (though admittedly the third one is purely subjective and speculative). [[User:Levivich|Levivich]] ([[User talk:Levivich|talk]]) 22:56, 23 November 2024 (UTC)
::::::::::::Um, thanks for sharing? --[[User:Tryptofish|Tryptofish]] ([[User talk:Tryptofish|talk]]) 23:06, 23 November 2024 (UTC)
::::On the petition page, I conducted a careful analysis of the evidence. Nobody refuted what I said there. --[[User:Tryptofish|Tryptofish]] ([[User talk:Tryptofish|talk]]) 22:15, 23 November 2024 (UTC)
:::::Linking might help though. It doesn't seem to be on [[Wikipedia talk:Administrator recall/Graham87]], [[Wikipedia talk:Administrator recall/Fastily]], or on [[Wikipedia talk:Administrator recall]], so it's a bit hard to know what "the petition page" is. Do you mean your 00:39, 13 November 2024 (UTC) reply to A smart kitten? The one that ended with "Does this rise to the level of requiring, for me, a desysop? I'm leaning towards no." And others leaned towards "yes", it's not as if people couldn't draw different conclusions from your post or could disagree with things you said without actually replying directly to you. You didn't contradict the evidence, you personally didn't find it severe or convincing enough, that's all. That doesn't show that the process needs fixing though, just because enough people disagreed with your opinion and the result wasn't put to the test. [[User:Fram|Fram]] ([[User talk:Fram|talk]]) 09:28, 25 November 2024 (UTC)
::::::Fram, the context of what I said was clearer before there were all those intervening edits, but yes, you correctly identified the post I meant as the one that ended with the words that you quoted. Here's the diff: [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia%3AAdministrator_recall%2FFastily&diff=1257054614&oldid=1257048515]. From where I'm sitting, your analysis here of how people reacted to what I posted is, well, not convincing enough. There was ''a lot'' of discussion about the evidence that I analyzed, back and forth. When the editor (A smart kitten) who originally posted the evidence came back with the additional information that I requested, the discussion was still very active. I provided a very detailed examination, point-by-point, of each individual claim made in that evidence. Yes, it was based upon my opinions, but I drew specific conclusions, and justified those conclusions. And nobody came back and said that they thought anything in my analysis was incorrect, nor did anyone who signed on the basis of that evidence before my comment come back and reaffirm their signature, rejecting my analysis. If you think somebody actually did, you can provide a diff of it, but I can assure you that you won't find one. And that wasn't because the petition discussion had come to a close, because it continued for several more days after I posted that. After a whole lot of back-and-forth about that particular evidence, nobody said that they found errors in anything that I said. But a couple more editors ''did'' sign the petition after that, with brief comments saying, in some cases, that they decided to sign after reading that particular evidence.
::::::So the question, in the light of your comment to me, becomes whether those later signers did so because they carefully read all of the discussion, including my critique, and decided to sign, implicitly having decided that my critique was unconvincing – or whether they signed after only a superficial read and had never really engaged with my critique. I cannot ''prove'' that it was the latter, and you cannot ''prove'' that it was the former. But given that their signatures came only with brief comments, and nobody found reason to actually mention that they had rejected my critique, I'm pretty skeptical of the former. And ''that's'' a problem. The petition process does not, of course, ''require'' that anyone had to say explicitly that they disagreed with me, either, but that's a shortcoming of the discussion process. A desysop via ArbCom makes room for careful examination of the facts. The petition did not. This is a half-assed way of driving someone off Wikipedia. And I'm arguing for a more deliberative process. --[[User:Tryptofish|Tryptofish]] ([[User talk:Tryptofish|talk]]) 18:55, 25 November 2024 (UTC)
*I have to say I don’t get the recall process either. I support admin accountability but just having an arbitrary number of “support” votes, no “oppose” votes, and I guess a time limit instead of consensus forming seems… extremely weird and out of step with how virtually everything else is done on Enwiki. [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 10:56, 24 November 2024 (UTC)
*:The intended point of the recall petition is not to find consensus or to determine whether the admin has lost the trust of the community, has abused the tools or anything like that. The intended point of the petition is only to prove that a re-RFA is not frivolous. The Re-RFA is where consensus is formed from support and oppose, analysis of evidence, etc. Think of it in judicial terms, the petition is at the pre-trial stage and simply aims to answer the question "are there 25 people who think there is a case to answer?" if the answer is no, then it ends there. If the answer is yes, then you can please innocent or guilty. If you plead guilty you take the sentence (desysopping) and move on. If you plead innocent there is a trial and the jury finds you either innocent or guilty by majority verdict. This is an imperfect analogy of course, but it hopefully helps explain the concept.
*:It didn't work like that in either of the two that we've had, but that's a fault with the implementation not with the concept. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 12:57, 24 November 2024 (UTC)
*::The problem is, the concept itself makes no sense. Nearly everything on Wikipedia is decided one of three ways: [[consensus democracy]] that must be approved/vetoed by an admin (most non-trivial issues); [[WP:BOLD]] editing, informal discussion, or admin fiat (trivial issues); or arbitration (extreme fringe cases). This resembles none of those. It’s like arbitration, only everyone can be an arb, and instead of voting yay or nay to take the case you collect signatures to see if there’s general support for a case? [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 13:11, 24 November 2024 (UTC)
*:::The request stage of arbitration is the closest analogy, but it is indeed a process not used anywhere else on Wikipedia. That doesn't mean it doesn't make sense. It's sole purpose is intended to be a check against frivolous requests so that an admin doesn't have to go through re-RFA just because they pissed off a single editor once by making an objectively correct decision. The actual decision is intended to made by consensus democracy at the Re-RFA. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 13:33, 24 November 2024 (UTC)
*::::I think a limited vote based on a formula like “after 7 days a minimum of 2/3rds of people must support for re-RFA” would be less opaque than trying to start a Wiki-[[Minyan]]? [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 09:26, 25 November 2024 (UTC)
*:::::That sounds like skipping the petition, and going right to the RRFA, or running two successive RRFA's. I have not been involved in any of this but it is not really hard to understand why there is the two-step process of: 1) calling the question, and 2) deciding the issue. [[User:Alanscottwalker|Alanscottwalker]] ([[User talk:Alanscottwalker|talk]]) 11:52, 25 November 2024 (UTC)
*::::::Honestly I think it should just go straight to RRFA, and if there’s enough opposition fast enough it can just be [[WP:SNOW]] closed. We don’t, for example, ask for 25 signatures to start and AfD discussion in order to weed out frivolous nominations— it’s patently obvious when a nomination is garbage in most cases. RRFA is clearly a last resort, and no established, good faith user is likely to abuse this kind of process so egregiously we need a two-step failsafe. [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 12:03, 25 November 2024 (UTC)
*:::::::In other words any user should be able to start a binding RRFA on any admin at any time? No, no thank you... &ndash;&#8239;[[User:Joe Roe|Joe]]&nbsp;<small>([[User talk:Joe Roe|talk]])</small> 12:16, 25 November 2024 (UTC)
*::::::::Not ''any time'', there should be a policy that steps ''must'' already been taken and failed, ideally multiple times, similar to ArbCom. And not ''any user'', since the starter should probably be autoconfirmed at the absolute minimum, and probably be required to be in goof standing, have X edits, been on WP X years, and been active during the last year. If it was unambiguously required that an RRFA follow these rules or be rejected (with filing an improper case being a sanctionable offense) I don’t think anyone would realistically start a frivolous case. [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 12:33, 25 November 2024 (UTC)
*:::::::Well, we also don't require a !vote to create an article but we do for an admin. I also don't think it is likely that 'any experienced user' has experience in making an RRFA -- [[User:Alanscottwalker|Alanscottwalker]] ([[User talk:Alanscottwalker|talk]]) 12:34, 25 November 2024 (UTC)
*::::::::An admin is essentially just voted into office; they should be voted out of office in an identical way. There’s no need for some kind of novel additional process on top of that. That’s all I’m saying. [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 12:55, 25 November 2024 (UTC)
:I think the basic complaint here is that the 25-vote threshold is too easy to meet, and therefore it is unfair to require an affirmative consensus for the admin to retain the tools. I think the 25-vote threshold is fine for weeding out frivolous nominations, but correspondingly I think we should make it harder to remove adminship, i.e. make 50-60% the discretionary range for ''removing'' adminship. This would make it in line with most of our other processes, where a slight supermajority is required to make changes, and no consensus defaults to the status quo. Whereas under the current recall system, 25 votes with no opportunity to object are enough to make removal of adminship the status quo, which seems a bit harsh. -- [[User:King of Hearts|<b style="color:red">King of ♥</b>]][[User talk:King of Hearts|<b style="color:red"> ♦</b>]][[Special:Contributions/King of Hearts|<b style="color:black"> ♣</b>]][[Special:EmailUser/King of Hearts|<b style="color:black"> ♠</b>]] 19:53, 25 November 2024 (UTC)
::I think the 25-vote threshold, because it’s so easy to meet, is essentially pointless because it will only weed out extreme outlier cases that I don’t believe will ever happen enough to be a serious concern. We should ''just'' have a supermajority vote requirement, and if we ''must'' have a petition it should be a lot higher than 25. [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 16:06, 27 November 2024 (UTC)
:::We don't have evidence the 25-vote threshold is easy to meet. Of the two recalls, one only hit 25 due to a bad block ''during'' the petition period. [[User:Chipmunkdavis|CMD]] ([[User talk:Chipmunkdavis|talk]]) 16:14, 27 November 2024 (UTC)
::::One more reason I don’t like this: it’s extremely important, but we’re using it to prototype this weird system not used anywhere else on Enwiki and possibly Wikimedia (if you have examples of off-wiki precedent please share them). [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 16:18, 27 November 2024 (UTC)
:::::Have to try new things at some point. But CMD is right, from all the evidence we do have, it looks about right. Where as there is zero evidence that a higher number is required or helpful. [[User:PackMecEng|PackMecEng]] ([[User talk:PackMecEng|talk]]) 17:09, 27 November 2024 (UTC)
::::::It's usually called [[Approval voting]] when it's used, though that might not be precisely the right name. It's used all over the Wikimedia movement. At least until recently, both grant requests and the (technical) community wishlist used petition-like voting processes that encouraged support and disregarded opposition votes. That is, if there were 25 people supporting something and you showed up to say "* '''Oppose''' because WMF Legal will have a heart attack if you do this", then the request might be rejected because of the information you provided, and your comment might change the minds of potential/future supporters, but it would never be counted as a vote of 25 to 1. It's still counted as a list of 25 supporters. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 18:53, 27 November 2024 (UTC)
:::::::The original Phase I Proposal was directly written as adapting dewiki's recall policies into enwiki. I believe the Italian wikipedia also has a threshold to RRFA style process. And I think spanish too? I might be getting some projects confused. But it's directly used in recall in other projects - That's how it was recommended here (and then adapted after). [[User:Soni|Soni]] ([[User talk:Soni|talk]]) 18:58, 27 November 2024 (UTC)
:::::Arbitration election commissioners are chosen by collecting solely supporting statements. Once upon a time, the arbitration election RFCs also consisted of proposals that commenters approved, without any option to oppose. [[User:Isaacl|isaacl]] ([[User talk:Isaacl|talk]]) 19:50, 27 November 2024 (UTC)


== the REGIME test ==
== Drafts in draftspace versus WikiProject subpages ==
{{Archive top|status=Closed|result=I am [[WP:BOLD|boldly]] closing this discussion as the proposal [[WP:SNOWBALL|has no chance of passing]] as demonstrated by the responses already provided. [[User:ElKevbo|ElKevbo]] ([[User talk:ElKevbo|talk]]) 14:55, 24 November 2024 (UTC) }}


* That any news outlet or source that refers to a government as a "''regime''" be considered not reliable for facts ''about that regime'', except for attributed statements.
There's been a series of moves and requested moves about various drafts inside WikiProject open at the moment. I was moving a bunch by hand to draftspace but this was opposed and so we had these discussions:
* That a list be kept and updated, similar to [[WP:RS/Perennial sources]]
* [[Wikipedia talk:WikiProject Outlines/Drafts/Outline of ancient history]] - RM request rejecting a move from Outlines WikiProject to draftspace.
[[User:Skullers|Skullers]] ([[User talk:Skullers|talk]]) 04:03, 20 November 2024 (UTC)
* [[Wikipedia talk:WikiProject Dacia/Drafts/Angustia]] - proposal to move a series from within [[Wikipedia:WikiProject Dacia]] to draftspace.
* [[Wikipedia talk:WikiProject Swami Vivekananda/Drafts/List of educational institutions named after Swami Vivekananda]] - proposal to move from [[Wikipedia:WikiProject Swami Vivekananda]] draft to draftspace.
* [[Draft talk:Outline of William Shakespeare]] - return from draftspace back to Outlines.
* [[Draft talk:Outline of cardiology]] - return from draftspace back to Outlines.
* [[Draft talk:Outline of Jesus]] - return from draftspace back to Outlines.
* [[Draft talk:Outline of golf]] - return from draftspace back to Outlines.
* [[Draft talk:Outline of Star Trek]] - return from draftspace back to Outlines.


:Why do we want to only use sources that haven't noticed that a regime is a regime? -- [[User:NatGertler|Nat Gertler]] ([[User talk:NatGertler|talk]]) 04:09, 20 November 2024 (UTC)
I can't finding any particular policy for when these should (if they should) be moved from their locations as subpages within WikiProjects or in draftspace but I'd like to put a notice here so that we can have some more outside views for the following discussions, even if it is reversing all the pages moves or keeping them where they are. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 07:09, 27 June 2016 (UTC)
:This would, for example, rule out using a significant proportion of reliable sources covering contemporary North Korea, Afghanistan, Cuba and Iran as well as countless historical governments (e.g. Saddam Hussein's Iraq, Franco's Spain, Gaddafi's Libya, etc). This is clearly hasn't been fully thought through. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 04:17, 20 November 2024 (UTC)
* WikiProjects '''own nothing'''. If they are interested in those pages they can add a banner tag to the talk page, just as any other project can do. --[[User:Izno|Izno]] ([[User talk:Izno|talk]]) 11:21, 27 June 2016 (UTC)
::Well, it might have been thought through if the idea is to exclude sources critical of said regimes, eg [https://www.bbc.com/news/articles/cvg0qz157yyo Activist takes own life in protest at Iranian regime] (BBC). Regards, [[User:Goldsztajn|Goldsztajn]] ([[User talk:Goldsztajn|talk]]) 06:57, 20 November 2024 (UTC)
** {{u|Izno}} Based on [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia_talk:WikiProject_Outlines/Drafts/Outline_of_ancient_history&diff=726461182&oldid=726455877 this revert] including other project is not considered acceptable. Either way, there's a lot of discussions and inconsistency about them so I don't know if an RFC is needed or we just go hap-hazardly. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 21:03, 27 June 2016 (UTC)
:::That would be a gratuitous failure of NPOV. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 11:04, 20 November 2024 (UTC)
* Concur with Izno, as a matter of policy at [[WP:OWN]], [[WP:BURO]], and [[WP:LOCALCONSENSUS]]. Also, SmokeyJoe's revert, diffed above, was inappropriate, since he is not the official spokesperson of all those wikiprojects, and the purpose of wikiproject banner templates on talk pages is to identify scope; it's a tagging mechanism for maintenance-side categorization, not a stamp of project turf-warring. "Live" content categories like [[:Category:Ancient history]] should not be put on article drafts, but it is {{em|eminently}} sensible to wikiproject-categorize drafts, because it helps direct topically-relevant editorial attention to improving them and getting them out of draft state. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 06:05, 30 June 2016 (UTC)
::::In heated agreement. Regards, [[User:Goldsztajn|Goldsztajn]] ([[User talk:Goldsztajn|talk]]) 01:57, 21 November 2024 (UTC)
*It should not be assumed that any article-focused WikiProject has any interest in being associated with any non-article outline. Outlines have a navigation purpose, but as articles the<u>y</u> <s>ir</s> are frequently redundant and/or attractors of original research. This is why they shouldn't be carelessly moved to draftspace, if moved, some more care is needed. The proper place for this discussion is at [[Wikipedia_talk:WikiProject_Outlines]]. --[[User:SmokeyJoe|SmokeyJoe]] ([[User talk:SmokeyJoe|talk]]) 06:29, 30 June 2016 (UTC)
::What do you mean by "''but as articles their [they?] are frequently redundant and/or attractors of original research.''"? <b>[[User:DexDor|DexDor]]</b><sup> [[User talk:DexDor|(talk)]]</sup> 15:20, 30 June 2016 (UTC)
:Bad idea. A biased source does not mean unreliable. See [[WP:BIASED]]. However, it is indeed good indicator that a in-text attribution may be needed. [[User:Ca|Ca]] <i><sup style="display:inline-flex;rotate:7deg;">[[User talk:Ca|talk to me!]]</sup></i> 15:00, 20 November 2024 (UTC)
::I think this does get at ''something'' which is a problem in Wikipedia. It just doesn't quite hit the mark. And that is that there is a core assumption in Wikipedia's handling of news media sources that they are largely independent and that a deviation from editorial independence represents a deviation from best practices. However this often leads to Wikipedia simply assuming the biases of the New York Times and other major media outlets. But there has been an accumulation of multitudinous issues - one of the most recent being accounts of Jeff Bezos influencing the Washington Post to withhold an endorsement of Kamala Harris - that demonstrate that the ''idea'' of editorial independence is frankly quaint.
:::[[User:DexDor|DexDor]], I mean, thinking of the many old AfD battles on outlines, that "Outline of X" pages were frequently noted to be duplication of "List of X" (not to be confused with notable lists), where both exist to list a large number of related topics. This problem seemed to be worse at the bottom of the outline hierarchy. Separately, some people who seem unfamiliar with [[WP:Outlines]] would add explanatory prose excessively, and when combined with the partial knowledge that Outlines are not supposed to contain references, the excessive prose violates [[WP:NOR]]. Or it forks article ledes, without attribution. --[[User:SmokeyJoe|SmokeyJoe]] ([[User talk:SmokeyJoe|talk]]) 01:25, 1 July 2016 (UTC)
::<br>
::::That isn't clarifying - e.g. what do you mean by "''notable lists''"? <b>[[User:DexDor|DexDor]]</b><sup> [[User talk:DexDor|(talk)]]</sup> 06:08, 1 July 2016 (UTC)
::This, of course, then creates problems with adjudicating those sources that have previously been demonstrated to be non-independent (see for example [[WP:XINHUA]]) as the rationale on Wikipedia for treating Xinhua differently from, let's say, the BBC or Al Jazeera for that matter largely depends upon the assumption of independence of those outlets that are not aligned with enemy states of the US/UK hegemony.
::::: A notable list is a list that meets the guideline section [[WP:LISTN]], the narrow case of "list topic is considered notable is if it has been discussed as a group or set by independent reliable sources", as opposed to the lower bar of [[Wikipedia:Stand-alone_lists#Appropriate_topics_for_lists]]. --[[User:SmokeyJoe|SmokeyJoe]] ([[User talk:SmokeyJoe|talk]]) 07:31, 1 July 2016 (UTC)
::<br>
*'''Move to draftspace''' - mainly for consistency with how the rest of wp works. For example, if someone creates a (draft) article List_of_bars_in_Fooland then that's probably of interest to 3 wikiprojects (Lists, Bars and Fooland) and should be tagged for those 3 wikiprojects on its talk page, but none of those 3 wikiprojects "owns" that page so it should not be a subpage of a particular wikiproject. Another way to look at this: The [[Wikipedia:Project namespace|Wikipedia (Project) namespace]] should be for information or discussion about Wikipedia (MOS, XFDs, Signpost...); not content. <b>[[User:DexDor|DexDor]]</b><sup> [[User talk:DexDor|(talk)]]</sup> 15:20, 30 June 2016 (UTC)
::My personal opinion is that the use of news sources on an encyclopedia should be far more limited than it presently is as, in my case, it's not that I trust Xinhua (I don't) but that I don't trust ''any'' media outlet to produce material appropriate for a neutral encyclopedia. I don't think a "regime" test is going to improve the quality of pages that over-rely on news media. But I would suggest that it's another indication that Wikipedia needs to be far more critical of what news sources we depend on and in what contexts. [[User:Simonm223|Simonm223]] ([[User talk:Simonm223|talk]]) 19:54, 20 November 2024 (UTC)
*'''Generally Oppose''' putting Outline drafts into draftspace. They are not proper drafts, mostly being templated creations; they are not proper articles, and all of them probably belong in Portal Space if not a new dedicated name space. Structurally, they should all be subpages of [[Portal:Contents/Outlines]], but I think they are not because the wikilinks were bothersomely long.
:::No, editorial independence is ''not'' the reason for a source being considered reliable or not. Many sources are biased, or influenced by specific governments/interest groups, and are still considered reliable for topics other than the groups influencing them (in which case, by definition, they would not be an [[Wikipedia:Independent sources|independent source]]). A history of disinformation (actually making up stuff, not just reporting it in a biased way) pushes the source towards being considered unreliable.{{pb}}[[WP:XINHUA]], which you link, demonstrates this clearly, stating {{tq|There is consensus that Xinhua is generally reliable for factual reporting except in areas where the government of China may have a reason to use it for propaganda or disinformation.}} In the same way, we shouldn't rely on the ''Washington Post'' for topics related to Jeff Bezos. [[User:Chaotic Enby|<span style="color:#8a7500">Chaotic <span style="color:#9e5cb1">Enby</span></span>]] ([[User talk:Chaotic Enby|talk]] · [[Special:Contributions/Chaotic Enby|contribs]]) 20:07, 20 November 2024 (UTC)
* The above list of linked discussions should be set aside per [[Wikipedia:Administrators'_noticeboard/Archive277#Ban_time.3F]]. Definitely not be considered precedent setting. The central place for productive discussion is at [[Wikipedia_talk:WikiProject_Outlines]]. Ricky has, in my opinion, got ahead of consensus in doing some things; not a shooting offense but he has irritated some with different styles. The IP is his personal IP hopping troll who started the linked discussions, which were poor both due to being fragmented/unadvertised and poorly initiated. --[[User:SmokeyJoe|SmokeyJoe]] ([[User talk:SmokeyJoe|talk]]) 01:25, 1 July 2016 (UTC)
::::The example I gave wasn't one of a story about Jeff Bezos or a topic related to Jeff Bezos unless one contends (which, I will grant there's a case to be made) that anything to do with a US election is ultimately about the interests of the Billionaire class. But, you see, that's my point. Pretty much any media outlet will distort truth, spread disinformation or, at the most basic, bury stories that aren't to the interests of their handlers. And I do want to stress that ''the stories that are not covered is a key method through which media occludes truth.'' The only real question is whether the handler is a politbureau or a rich guy. I don't think one of those is better than the other. [[User:Simonm223|Simonm223]] ([[User talk:Simonm223|talk]]) 20:12, 20 November 2024 (UTC)
::Why do you think outlines belong in Portal namespace? [[WP:PORTAL|Portals]] (e.g. [[Portal:Fish]]) are nothing like outlines (e.g. [[Outline of fish]]). Anyway, what namespace (article/portal/outline) non-draft outlines are in is largely/completely irrelevant to the question of what namespace (wikipedia/draft) draft outlines should be in. <b>[[User:DexDor|DexDor]]</b><sup> [[User talk:DexDor|(talk)]]</sup> 06:08, 1 July 2016 (UTC)
:::::The fact that a news media is influenced to not publish a story makes it biased, but not unreliable. Having a point of view when reporting (or choosing not to report) stories is what every media does, and is different from outright making up disinformation. And that is the difference between bias and unreliability. It's not about who the handler is, [[Rupert Murdoch|rich guys]] can also own unreliable news sources. [[User:Chaotic Enby|<span style="color:#8a7500">Chaotic <span style="color:#9e5cb1">Enby</span></span>]] ([[User talk:Chaotic Enby|talk]] · [[Special:Contributions/Chaotic Enby|contribs]]) 20:16, 20 November 2024 (UTC)
:::1. Because the top level of outlines lies under Contents in Portal space, not under [[Portal:Contents/Outlines]].
::::::I mean we certainly agree about that rich guy. I just think Wikipedia is too fast to treat news sources as reliable out of convenience rather than any real confidence in the quality of information. [[User:Simonm223|Simonm223]] ([[User talk:Simonm223|talk]]) 20:20, 20 November 2024 (UTC)
:::2. Because outlines do not contain unique content. They should contain minimal prose, if any.
:::::::I agree with [[User:Simonm223|Simonm223]]. I just can't understand why an encyclopedia should be largely based on news sources rather than peer-reviewed academic articles or books. For a start most of them are primary sources, by any definition other than Wikipedia's. This is dumbing-down at its worst. [[User:Phil Bridger|Phil Bridger]] ([[User talk:Phil Bridger|talk]]) 21:09, 20 November 2024 (UTC)
::: Portal:Fish are nothing like outlines is correct, Portal:Fish is not under [[Portal:Contents/Outlines]]
::: DraftSpace should be restricted to mainspace drafts. Draft proposals do not go in draftspace. Neither do draft templates, categories or userpages. --[[User:SmokeyJoe|SmokeyJoe]] ([[User talk:SmokeyJoe|talk]]) 07:56, 1 July 2016 (UTC)
::::::::Exactly, yes. [[User:Simonm223|Simonm223]] ([[User talk:Simonm223|talk]]) 22:42, 20 November 2024 (UTC)
:::::::I agree, out article on [[Donald Trump]] and [[Joe Biden]] for example would do better citing academic sources than news outlets. [[User:Ca|Ca]] <i><sup style="display:inline-flex;rotate:7deg;">[[User talk:Ca|talk to me!]]</sup></i> 02:21, 21 November 2024 (UTC)
:::: That's like saying root articles should be subpages at [[Portal:Contents/Overviews]]. Or that lists belong in portal space as subpages of [[Portal:Contents/Lists]]. Portal:Contents is a set of top-level lists (all but one being a list of lists), not a container for encyclopedia articles (of which lists are a type). Yes, lists are articles. And outlines are lists. As [[WP:STAND|stand-alone lists]], outlines are mainspace articles, and so having drafts of outlines in draft space is valid. [[User talk:The Transhumanist|<i>The&nbsp;Transhumanist</i>]] 20:48, 9 July 2016 (UTC)
:See [https://www.merriam-webster.com/dictionary/regime the definition (specifically 2(c) and 2(d))]. Regime is a synonym for "administration" or "government" (when used to describe, as example, the Biden administration or the Tory government). It makes zero sense whatsoever to block sources who use a synonym for administration just because one person feels it has negative connotations. Wikipedia is not the place to practice redefining words or limiting their use based on their worst definitions or connotations. -bɜ:ʳkənhɪmez &#124; [[User:berchanhimez|me]] &#124; [[User talk:berchanhimez|talk to me!]] 05:03, 21 November 2024 (UTC)
* '''Drafts belong in draft space''' &ndash; That's the dedicated space for them now. Move 'em. [[User talk:The Transhumanist|<i>The&nbsp;Transhumanist</i>]] 20:48, 9 July 2016 (UTC)
::Prescriptivism is dead. See examples. There is zero percent usage in modern times that isn't derogatory; literally no one says unironically "our regime", "the regimes of our allies", or "regimes we'd like to do business with". [[User:Skullers|Skullers]] ([[User talk:Skullers|talk]]) 08:29, 21 November 2024 (UTC)
:::I agree in as much as "government" would always be a better term in any use case I can think of.
:::However, your polemics here have been consistently superficial and unhelpful. It seems almost self-parody to aphorize "prescriptivism is dead" amid seeking to categorically deprecate sources based on the sole criterion of whether they use a particular word, citing what you feel is the only correct definition of said word in practice. <span style="border-radius:2px;padding:3px;background:#1E816F">[[User:Remsense|<span style="color:#fff">'''Remsense'''</span>]]<span style="color:#fff">&nbsp;‥&nbsp;</span>[[User talk:Remsense|<span lang="zh" style="color:#fff">'''论'''</span>]]</span> 09:03, 21 November 2024 (UTC)
::::The attraction of the word "regime" to headline writers is often that it is simply shorter than "government" or "administration", rather than anything to do with its connotations. [[User:Phil Bridger|Phil Bridger]] ([[User talk:Phil Bridger|talk]]) 09:48, 21 November 2024 (UTC)
:::::Exactly my point. -bɜ:ʳkənhɪmez &#124; [[User:berchanhimez|me]] &#124; [[User talk:berchanhimez|talk to me!]] 23:24, 21 November 2024 (UTC)
:What is the rationale for this proposal? Is there a specific source or incident that prompted it? [[User:Gnomingstuff|Gnomingstuff]] ([[User talk:Gnomingstuff|talk]]) 01:09, 22 November 2024 (UTC)
:While I understand the rationale for this proposal, IMO it goes way too far. I would agree that it's important to keep in mind when a source is using biased language and consider using in-text attribution in these cases, but certainly it's not worth a blanket ban.
:Furthermore, it's often the case that when the news media uses negative language about a topic, that's because that negative language is the consensus. For instance, nobody would really question the phrase "the Nazi regime" or even probably "the genocidal Nazi regime" from a reliable source, and for good reason. When everyone agrees on a [[WP:LABEL|contentious label]] that implies that in that specific case the label is not, in fact, contentious. [[User:LokiTheLiar|Loki]] ([[User talk:LokiTheLiar|talk]]) 01:21, 22 November 2024 (UTC)
*This proposal is rather absurd. You can’t declare a source unreliable based on ''a word'', especially one that’s frequently used as a harmless rhetorical flourish. What should we ban next? Sources that use swearing? Sources that use subjective adjectives like “best” or “amazing”? [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 13:16, 24 November 2024 (UTC)


:I say we should also ban all sources that use the word "slam". Equally as absurd, but more likely to actually hit unreliable sources. '''[[User:Lee Vilenski|<span style="color:green">Lee Vilenski</span>]] <sup>([[User talk:Lee Vilenski|talk]] • [[Special:Contribs/Lee Vilenski|contribs]])</sup>''' 13:58, 24 November 2024 (UTC)
[[Portal:Contents/Outlines]]
::Presumably excluding sports uses? We definitely need sources that report on grand slams. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 14:40, 24 November 2024 (UTC)
* '''Update''': Of the ones above, they have all been resolved (other than the initial Outlines pages not being moved, they are either in draft or not moved from draftspace). However, [[Wikipedia talk:WikiProject Dacia/Drafts/Angustia]] has been relisted and could use more commentators and [[Wikipedia talk:WikiProject Alabama/W. H. Taylor]] I just started. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 21:25, 1 July 2016 (UTC)


{{Archive bottom}}
== Use of USPS stamp images ==

A inquiry to the US Postal Service “Integration and Planing Rights and Permissions” division on 9/8/15, case ID 124603003, reported that no prior approval is necessary for use of stamp images in "newspapers, news magazines, news journals and other media,” which I take to mean online encyclopedias, as the inquiry specifically referred to use of USPS stamp images on Wikipedia. However users "must credit the USPS and noting its rights, such as “United States Postal Service. All rights reserved.” and “all aforementioned uses must consist of the unaltered, original image...” — that can be obtained by a download free from the Smithsonian Institute’s [http://arago.si.edu Arago:people, postage and the post] website, as well as USPS sites featuring the most current issues.

Why should Wikipedia policy continue to bar most USPS stamp images, when it is just a matter of reporting image information in historical context of cultural significance in a Wikipedia article and their use is permitted by the USPS? There need be no fear of Wikipedia becoming a stamp album, any more than there is need to fear WP becoming an art gallery, or a video game promotion by representing images of art or box covers. The key is writing informative encyclopedic narrative directly associated with each image. [[User:TheVirginiaHistorian|TheVirginiaHistorian]] ([[User talk:TheVirginiaHistorian|talk]]) 15:09, 27 June 2016 (UTC)

:The USPS statement clearly does not release the stamp images under an acceptable free license (specifically that it does not allow alteration, which is a requirement we need to call images free). As such, stamps (since a specific year when the USPS was no longer a direct government agency) are copyrighted works and treated as non-free, and since WP's mission is to minimize the use of non-free, we restrict the use of such stamp images unless they meet NFCC. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 15:13, 27 June 2016 (UTC)
::That's not clear. How can the images of copyrighted video game boxes and album covers be allowed on Wikipedia and not stamps as a part of informative encyclopedic narrative? [[User:TheVirginiaHistorian|TheVirginiaHistorian]] ([[User talk:TheVirginiaHistorian|talk]]) 16:02, 27 June 2016 (UTC)
:::Cover art for a ''notable'' published work (one that has its own standalone article) is considered to be an acceptable use of non-free images to illustrate how that work is marketed and branded (even if that is not discussed at all in the article). If there was a stamp or stamp set that was notable on its own (eg meeting the [[WP:GNG]] for a standalone article, the same allowance would clearly be made. However, individual stamp or series of stamps are rarely notable on their own, and generally are covered on the topic that the stamp is illustrating to say that the topic was commemorated on a stamp or stamp series. And in that case, one rarely needs to see the image of the stamp to understand that context. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 16:37, 27 June 2016 (UTC)
:[[User:TheVirginiaHistorian|TheVirginiaHistorian]], I think it depends upon where you want to use an image of the stamp. For example, I see that they have stamps with pictures of [[spoonbill]] birds and [[banana split]]s, and it's unlikely that those stamps would be appropriate for those articles. However, they also have one of the renowned teacher [[Jaime Escalante]], and it would probably be appropriate to include the stamp alongside a well-sourced paragraph that explains that the USPS printed a stamp in honor of him. The File: page would need to be here (not at Commons) and it would need a {{tls|Stamp rationale}} template, but that is probably an acceptable use. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 18:55, 27 June 2016 (UTC)
::Actually, no, that would not be an acceptable use ''if'' there already existed an image of Escalante, particularly a free one. If we already know what the person looks like from other media, just using the image of the stamp to show another image and to say that a stamp was made to commemorate him would fail [[WP:NFCC#1]] (if a free image was available) and [[WP:NFCC#3a]] (if a photograph existed otherwise). There would need to be more discussion on the specific image used on the stamp sourced in the text to made it an allowable use. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 19:04, 27 June 2016 (UTC)
:::I was assuming that the "well-sourced paragraph that explains that the USPS printed a stamp" would actually talk about the stamp, and that the image of said stamp existed to illustrate the paragraph about the stamp, rather than the article's subject as a whole. ;-) An unrelated snapshot of the person doesn't really tell you anything about the stamp's appearance, so NFCC complaints on grounds of "we have a different picture of this person" would not prohibit us from using a copy of the stamp to show what the ''stamp'' (NB: not ''the person'') looks like. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 05:53, 30 June 2016 (UTC)

I see the notable test. Most stamps with historical interest are initiated with joint resolutions of Congress, a majority of both House and Senate. Anti-stamp editors have previously objected that the dust jacket of a book on the New York Times best selling list, or a national marketing campaign for a video game make the respective visual representations “notable”. Surely relative to the larger context of U.S. history, a Joint Resolution of Congress commemorating a person, event or place is even more notable in comparison.

The Template:Stamp rationale is, “used for purposes of illustration in an educational article about the entity represented by the image”. It is not replaceable image, because "a free use alternative won’t exist.” Further, “there is no possible commercial disadvantage to the copyright holder.” The WP:Stamp rationale was used for the images at [[Puerto Rico on stamps]] which now is populated with placeholders since their arbitrarily removal. They were at Commons, why must they be exclusively at Wikipedia? I thought the Foundation policy was to migrate images to Commons. This seems to be a narrow parochial argument against the larger interests of the Foundation for free online access to information.

It is notable that Puerto Ricans and other U.S. citizens from U.S. territories were once excluded from U.S. commemorative stamp notice, while now politicians, poets, actors and baseball notables are commemorated as Americans, rather than an anonymous peon. WP has a project to overcome WP structural bias. Is that the proper venue for that article? Or is opposition just a general bias against stamps in Wikipedia at all, as one editor complained. It seems that the anti-stamp view is not consensus policy, as there is a [[Template:Stamp rationale]]. [[User:TheVirginiaHistorian|TheVirginiaHistorian]] ([[User talk:TheVirginiaHistorian|talk]]) 06:39, 28 June 2016 (UTC)

:No, the act of Congress doesn't make the stamp image notable, but instead lends to the notability of the person or the topic that the act commemorates.
:Also, keep in mind that the Foundation wants to encourage a encyclopedia with minimal use of non-free images, those images that cannot be reused and modified by any reuser, so that the work can be distributed freely around the world. Stamps, under the language you quoted, do not fall into that, so their use should be minimized. In an article about the general culture of Puerto Rico on stamps, it would be impossible to illustrate every stamp that has been issued to commemorate that, free or non-free, and where non-free is concerns, on such lists, only one or two representative examples would be appropriate for visual identification. It's not a bias against stamps, since stamps can be used selectively for illustration, just mass representation of stamps without any discussion of the stamp's image importance. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 14:05, 28 June 2016 (UTC)

That a republic commemorates its outstanding citizens is a remarkable event in history, the expression of it in a stamp happens to be visual rather than verbal. The visual expression should be seen as equivalent to the verbal. The Foundation encourages the use of stamps by providing a Template:Stamp rationale. It does not want free images of persons, places or events modified on Wikipedia so that the personage is unrecognizable. The stamp image is stipulated as non-free in the policy approved [[Template:Stamp rationale]] for each image.

The contrast between the free-use Spanish commemoration of 1492 Columbus in 1892 and the proposed non-free use U.S. commemoration of Columbus in 1992 is instructive to the reader, but denied by Masem's misconstruing of NFCC#1, there is no image of the U.S. stamp available except that of the U.S. stamp, although is is allowed in lower resolution in NFCC#3b. In NFCC#3a, where "Multiple items are not used when one item can convey equivalent significant information" — does not apply as the visual contrast between the Spanish and U.S. stamps is not apparent without the U.S. image. There is no multiple image gallery of the same U.S. stamp in the article.

At [[Puerto Rico on stamps]] the history of U.S. postage for Puerto Rico is comprehensive, to meet the standards of a Featured Article classification by WP policy. Masem’s characterization of it being “impossible to illustrate” is simply a unreasonable denial of the work completed. Each stamp is discussed in relation to its importance as representative of Puerto Rico in compliance with NFCC#8. The charge that there is no discussion on image importance is unthinking obstruction of the intent of the Foundation. [[User:TheVirginiaHistorian|TheVirginiaHistorian]] ([[User talk:TheVirginiaHistorian|talk]]) 17:21, 28 June 2016 (UTC)

:The Foundation did not supply Template:Stamp Rationale. That was a template created on en.wiki that does have some allowed uses but does not mean every stamp image is allowed. It simply helps to make assigning a rationale for a stamp easier by filling in some of the required NFCC information that are common to stamps. The rational and other NFCC aspects must still be valid.
:Most of the items listed at [[Puerto Rico on stamps]] do not require one to see the stamp to understand the topic. You have plenty of sources to note that various people and places in PR were commemorated by putting them on stamps, and that's as far as the sources go, they do not describe anything of significance of the visual nature of the stamp. As such, one does not need to see the stamp to understand why the person or place was commemorated, nor to understand that a stamp was made for them. That said, we are reasonable in allowing one or two visual examples of non-free in such lists, recognizing many readers are visual readers, so one or two stamp images would be fine under NFCC. But not all those presently marked as "no image available". --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 17:35, 28 June 2016 (UTC)

Every stamp image which is supplied with a Template:Stamp rationale meets the NFCC requirements for usage by #1 and #3a, it cautions the user to the limits of the non-free image, it must be credited to USPS and “All rights reserved”, even as the entire image is used. All elements of NFCC are met at [[Puerto Rico on stamps]] for those with the place holder, “No image yet”, including #8, each stamp is "discussed in relation to its importance" as representative of U.S. stamps of Puerto Rico.

Your interest in the descriptions of the visual nature of each stamp and its production at [[Puerto Rico on stamps]] is a technical philately one, which does not directly bear on the subject matter of the article, an article that addresses the history, politics and culture of Puerto Rico as a U.S. territory on stamps. But if that is your particular interest, of course it can be admitted as your contribution to the article to expand its coverage of the topic.

The idea that “There are U.S. stamps about Puerto Rico.” would comprehensively cover the topic of reader interest without visual images of the stamps is reductio ad absurdum. At George Washington, readers want to know more than “George Washington was a Virginian” albeit in an absurd sense, that is all a reader needs to know. An article on a visual medium requires visual representations, so long as article length guidelines are not violated. [[User:TheVirginiaHistorian|TheVirginiaHistorian]] ([[User talk:TheVirginiaHistorian|talk]]) 10:19, 29 June 2016 (UTC)
*"Every stamp image which is supplied with a Template:Stamp rationale meets the NFCC requirements for usage by #1 and #3a," Er, unless I am reading you wrong, you are stating that merely using the template meets the criteria for #1 and #3a - thats incorrect, you have to demonstrate use of the media meets the criteria, then the template can be used as an aide. [[User:Only in death|Only in death does duty end]] ([[User talk:Only in death|talk]]) 10:41, 29 June 2016 (UTC)
* The template only helps towards meeting NFCC#10; #1 and #3 have to be satisified by the actual use and rational entered into the template. The subject matter is how PR has been commemorated on stamps, not the visual aspects of those stamps, so images are secondary and not necessary to understanding the topic. That is not to say no image can be used, one or two representative examples are fair, but without any further discussion of the visual aspects of the stamps (beyond a simple description), particularly with commemorated subjects that already have free images, more images are against the Foundation's goal of minimizing non-free use and our NFCC policy that supports that. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 13:59, 29 June 2016 (UTC)

This discussion badly needs involvement from some US copyright experts. Just because the USPS claims rights doesn't mean it actually has them. There's a general principle that materials produced at taxpayer expenses by agencies and other bodies of the US federal, state, county, and local governments is public domain, and caselaw has even extended this to work produced for them by contractors. It's difficult to see why the US Postal Service would be some magical exception. That said, this is not a question I've pursued in any detail (i.e. with Westlaw and LexisNexis access and other shepardizing resources) since the 1990s, so something could have changed. Most of the intellectual property attorneys I know, who have looked into the overall question, are convinced that WMF is being excessively paranoid about copyright in general, and not permitting the community to avail itself of most of its fair use rights, to the detriment of projects like Wikipedia (they theory being that WMF is trying to avoid litigation it could win hands-down but which would still generate legal expenses; some of us would rather WMF fought those fights and did fundraising efforts and outreach to ACLU, EFF, etc. to back them up). <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 04:16, 30 June 2016 (UTC)

:It's rather simple, actually. Up to 1978, the USPS ''was'' considered a branch of the federal gov't and stamps issued by them were in the PD by the US-PDGov. However, after 1978, the USPS while still an agency of the gov't specifically had copyright laws apply that works produced by the USPS were now eligible for copyright; see [[United_States_Postal_Service#Stamp_copyright_and_reproduction]].
:And no, it's not an issue about copyright, it's about being a ''free'' content work. We know we are more restrictive than fair use but that's because we are trying to create a free content encyclopedia. Very little has to deal with how things are classified as copyright or not. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 04:29, 30 June 2016 (UTC)

::{{Ping|User:SMcCandlish}} Some of what you say is acknowledged by the NFCC gatekeepers, so that images of out-of-copyright art framed with a USPS border and postage value has been allowed in articles such as battles pictured at [[Commemoration of the American Civil War on postage stamps]]. The general usage of the postage places it in the public domain, but I argue additionally that the non-free use Template:Stamp rationale covers us in that it stipulates the USPS copyright, we acknowledge their "All rights reserved", and inquiry to the US Postal Service “Integration and Planing Rights and Permissions” division on 9/8/15, case ID 124603003 concerning use of USPS images on Wikipedia, reported that no prior approval is necessary for use of stamp images for educational, news and "other media". [[User:TheVirginiaHistorian|TheVirginiaHistorian]] ([[User talk:TheVirginiaHistorian|talk]]) 04:42, 30 June 2016 (UTC)
:::My point really is that, from years of doing fair-use legal work (as a policy analyst, not an attorney, but in an office full of intellectual-property specialist attorneys), it appears to me extremely dubious that any copyright claims made by the USPS are valid, and that if challenged they would be invalidated at every court level from District through SCotUS, because all the statutory and case law regarding the American governments' attempts to evade or eliminate fair use to control its own materials has ruled on the public interest's side. Unless, as I said, something recently changed radically. If it has, then an attorney steeped in that caselaw should be advising us (and [[WP:OFFICE]]) on these matters. If this has not transpired but there's a danger of it, then a) WMF should not be restraining our exercise of fair use out just out of some nebulous "what if" concerns, and b) should be working with other public interest groups like ensure that taxpayer-funded materials remain public domain. It would be an unmitigated disaster if something like [[crown copyright]] arose in the US (and other more open, public-domain jurisdictions that follow the US lead), all because various parties not only failed to speak up, but treated a non-law as if it were a law, and thereby established a ''de facto'' anti-fair-use "industry standard" that the courts or legislative bodies decided to enforce (which has definitely happened before – ever heard of [[sample clearances]]?). <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 05:51, 30 June 2016 (UTC)
::::See the point I made above: the copyrightability of USPS stamps from 1978 is in the federal code, specifically written in by the Copyright office in response to the [[Postal Reorganization Act]] that reflects that the service become essentially an independent agency from the federal government [http://www.copyright.gov/history/law/clrev_94-1476.pdf]. And again, we are purposely stronger that US fair use not because of any legal issues, but because the goal is to make a free content encyclopedia. Meeting goal assures that we're always within fair use, by happenstance, but no law is requiring us to be more restrictive, it is the Foundation's mission that makes us so. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 06:00, 30 June 2016 (UTC)
:::::The mission: I buy that; I just think it's a mistake. It's a technical matter, and nothing more: All it requires is some kind of wrapper around or metadata tagging of non-FC material, then any re-users of WP material in bulk, who demand or need truly free content only, can exclude that material as they import and repurpose it. They already have to do that with things like the WP logo anyway. WP's mission as an encyclopedia, and now the most-used information source in the world, is far more important than Stallmanesque ''libre'' position-taking by the foundation.<p>The USPS legal matter: I understand that it's a statutory issue. The point I was trying to make, poorly I guess, is that one of the primary functions of the federal courts, from a civil liberties standpoint, is striking down bad statutes. I spent about a decade helping ensure they did so, and it is mostly action by principled nonprofits that kicks those balls through the goal. The right case would nuke that statute as an invalid attempt to evade public domain by using a quasi-privitization shell game (not very different from attempts that the courts have already invalidated). <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 12:03, 6 July 2016 (UTC)</p>
::::::While it is very easy to dismiss that those that can't use non-free can just apply wrappers to get non-free-less content, it still stresses on us editors to make sure we do not rest too heavily on non-free being a presumed allowance, thus creating content that ''requires'' the non-free to a point where without the non-free it no longer becomes useful. We should be seeing this as a intellectual challenge to figure out how to write on topics without resorting to non-free as to meet the Foundation's mission. And of course, the less non-free we use, the more we keep our noses clean in any fair use issues. As to the USPS, I do note that the action that the Copyright office set included two other agencies that were transferred from being internal to external, similarly allowing them to claim copyright. And that it was no required that take copyright, only that it existed as an option (which the USPS clearly took). --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 16:03, 6 July 2016 (UTC)
::{{Ping|User:Only in death}} The use of a stamp for a stamp related article such as [[Puerto Rico on stamps]] when it is one of the U.S. stamps on Puerto Rico, demonstrates the use of the media (stamps) is required in the [[Template:Stamp rationale]], “protected by copyright, therefore a free use alternative won’t exist”. That is, making the article into a literary discourse of the fine arts uniquely associated for each stamp image is not a requirement for an article on the stamps of Puerto Rico which addresses its American history, politics, economy and culture on stamps. But images of each of those stamps is a requirement to be comprehensive so as to meet the interests of a general reader.

::{{Ping|User:Masem}}The use of postages stamps “to illustrate the stamp in question (as opposed to things appearing in the stamp’s design)…qualifies as fair use under United States copyright law.” The visual aspects are not required to be addressed — those are explicitly excluded. Even when they are, the stamp images are removed capriciously. In the article [[Puerto Rico on stamps]], the image of the [http://arago.si.edu/record_244819_img_1.html Julia de Burgos stamp] notes that it "features the poet with blue water flowing behind her, evoking one of her best known poems, “Río Grande de Loíza,” a sensuous ode to the Puerto Rican river where she was raised.” — Yet that image was also removed.

::{{ping|User:WhatamIdoing}} All copyrighted images are removed, even though they meet the ten NFCC requirements and satisfy the Template:Stamp rationale. One or two are not allowed due to editors blanket removal when they misconstrue the NFCC criteria. An article on stamps can use stamp images. To simply assert it is “impossible” to comprehensively discuss Puerto Rico on stamps to meet the interest of a general reader ignores the editorial contribution. [[User:TheVirginiaHistorian|TheVirginiaHistorian]] ([[User talk:TheVirginiaHistorian|talk]]) 04:42, 30 June 2016 (UTC)

:::Remember that the Wikimedia Foundation and en.wiki's are ''purposely more restrictive than US fair use law'' to encourage the avoidance of non-free and the use of free content in its place, so it doesn't matter what fair use would allow, and we do not simply allow for images of things for causal illustration; there must be a reasonable purpose beyond decoration. I know you and I have discussed the de Burgos stamp before since I remember that the language about the imagery would justify it. It is true that it looks like an editor removed all the non-free without question and as they were not readded the files were deleted as orphans, but it is reasonable to readd ''only'' the de Burgos stamp image, just that you can't justify all of the others under NFC allowances. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 05:50, 30 June 2016 (UTC)
::::The community should resist and undo this WMF angle to the extent that it can, because it's ultimately inimical to [[WP:ENC]]. One of the principal criticisms of WP as a usable work is the dearth of images. A less frequent but more serious one is our reliance on natural history images and the like from 1800s publications, many of which are grossly inaccurate. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 05:54, 30 June 2016 (UTC)
:::::As long as they are footing the bill for the services, we're bound by their goals. You're welcome to freely fork en.wiki and make the it more amendable to fair use, but as long as we're in the WMF's sandbox, we have to abid by their rules. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 06:01, 30 June 2016 (UTC)

::::::This last Masem post may be the key to his misunderstanding the article, [[Puerto Rico on stamps]] and others like it. The purpose of the article is to convey the information about U.S. postage concerning Puerto Rico’s history, politics, economy and culture in its American identity since 1898. That requires showing images both free-use and non-free use, before and after 1978, in order to satisfy the interest of the general reader, which is a Foundation goal. Images for the visual medium such as stamps is as important as referencing multiple speeches for in a politician's biography. It is not sufficient to say, "Lincoln made several important speeches," the speeches demonstrated as important to the subject should be illustrated individually with direct quotes from each. Visual media should be illustrated with each important stamp image related to the subject.

::::::Masem said, {{Gi|We do not simply allow for images of things for causal illustration}}. No, NFCC is misconstrued if each stamp image is imagined to be “casual" in these articles, when the accompanying text demonstrates the importance of each one to the subject matter of the article in accordance with NFCC#8. There is no Foundation goal to restrict the subjects of the encyclopedia to only subjects with free images, as non-free images for video games and music albums abound, without the notability conveyed by the Congressional joint resolution for each stamp and the public domain usage of hundreds of thousands of issues for each stamp prior to its illustration here with a WMF sanctioned [[Template:Stamp rationale]]. [[User:TheVirginiaHistorian|TheVirginiaHistorian]] ([[User talk:TheVirginiaHistorian|talk]]) 12:28, 30 June 2016 (UTC)
:::::::First the WMF has had nothing to do with the Stamp rationale template. It is a template made by editors on en.wiki and that's it, and even then I'm not sure if that was made with consensus or not. Nothing more. Just because it exists does not validate any stance by the WMF or that it was authorized by the WMF.
:::::::Second, the article you are presenting is not talking about the importance of the stamps ''themselves'', simply the importance of PR and various people and topics from it that were deemed important enough to be put on stamps. No part of that requires any imagery whatsoever to understand that PR has been memorialized on various stamps - sources are used to validate that these stamps were commemorated. Only in a few isolated cases has there been any specific discussion from the sources of ''what imagery went on the stamp itself'', and those seem only to be one or two lines of prose, nothing in any great detail. It shows that the stamps themselves are not important, only that PR-related people and topics were deemed important enough to be put on stamps. (If you ''don't'' have a source to say that the stamp was issued to commemorate that person/topic and are using the image as proof, that's original research and unacceptable, but I don't think that's the situation here in this case).
:::::::Of course, we do encourage the use of images to illustrate articles, but now we have to consider that WMF wants to minimize the use of non-free and our NFC policy abides by this goal. This does not restrict free images, since that's explicitly meeting the WMF goal. But non-free images must be used with extremely caution in this case since one does not visually need to see the stamp to understand that a stamp was made to commemorate that person. This is basically the case outlined in [[WP:NFC#UUI #9]] (keeping in mind these are not all-encompassing rules but examples of how NFC applies) {{green|A magazine or book cover, to illustrate the article on the person whose photograph is on the cover. However, if the cover itself is the subject of sourced discussion in the article, it may be appropriate if placed inline next to the commentary.}} You ''do not'' have any significant sourced discussion of the stamps themselves (beyond the fact that they were printed) for these stamps outside of de Burgos' which describes why the imagery for the stamp was selected. So that's only one clear non-free allowance. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 12:49, 30 June 2016 (UTC)

*'''Comment''': It's all about fair-use rationale. USPS stamps since 1978 are copyrighted, and therefore cannot be used on Wikipedia except possibly in the infobox of an article about that specific stamp (same as the fair-use rationale for album covers, video covers, and book covers, <u>only on the article strictly about the item -- in this case stamp -- in question</u>). You can't use a copyrighted stamp on an article about the subjct the stamp depicts -- only on an article about ''the stamp itself''. See [[Wikipedia:WikiProject_Philately#Stamp_images]] and [https://commons.wikimedia.org/wiki/Commons:Stamps/Public_domain#United_States]. [[User:Softlavender|Softlavender]] ([[User talk:Softlavender|talk]]) 13:17, 30 June 2016 (UTC)

::Its all about using the Template:Stamp rationale as specified in your link [[Wikipedia:WikiProject_Philately#Stamp_images]]. Further, USPS gave Wikipedia permission to use USPS images without prior permission as "other media" by the Integration and Planning Rights and Permissions case ID 124603003 of 9/8/15. In addition, we have WP:NFC#UUI#9, {{Gi|However, if the cover itself is the subject of sourced discussion in the article, it may be appropriate if placed inline next to the commentary.}} Each stamp itself is the subject of sourced discussion in the article, so WP:NFC#UUI#9 makes it appropriate to use the image of each stamp if placed inline next to the commentary. Again some misunderstanding: the stamp images do not merely illustrate the article topic, they are the article topic.

::{{Ping|Softlavender}} For example, the subject of the article [[Puerto Rico on stamps]] is not about Columbus discovering America, it is about Puerto Rico on U.S. stamps, which encompasses the U.S. 1992 commemoration stamp of Columbus discovering America. WP:NFC#UUI#9 justifies use of the stamp image if placed inline next to the commentary, because the stamp itself is the subject of sourced discussion in the article.

::{{Ping|Masem}} The Columbus commemorative is about Columbus’ landing at Puerto Rico. That is not original research as you have supposed, it is as sourced to the Smithsonian Institute’s Arago website, which sources the USPS. Generally, WP allows single source attribution from reliable secondary sources, without the need for multiple citations of their sourcing. The sourced discussion on the stamps generally encompasses the commentary provided by USPS, which is a reliable source for information about its stamps in general circulation, as is the Smithsonian Institute's Arago website. [[User:TheVirginiaHistorian|TheVirginiaHistorian]] ([[User talk:TheVirginiaHistorian|talk]]) 08:09, 1 July 2016 (UTC)
:::For images to be called "free", we require that ''everyone'' has the right to use and modify the image. While the USPS may have granted Wikipedia this right, it clearly does not extend to reusers, so these images are still non-free.
:::Your article is not about the stamps, but about the people and places that are represented on the stamps. An article about a stamp itself, specifically would be something like [[Inverted Jenny]]. It's subtle but important difference that is critical to understand why you must limit the use of non-free on that article. You have no commentary about the stamps that is not otherwise about the person or place on the stamp; in contrast, the Inverted Jenny has only the briefest info about the plane on it and the bulk on the stamp's history and legacy, something not at all present in the PR stamp article. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 12:33, 1 July 2016 (UTC)

The Template:Stamp rationale stipulates that the images in use are non-free, and it addresses the legal technicalities required of Wikipedia to use them in articles. Narratives including a stamp with sourced discussion in the article can use the image with the Template:Stamp rationale according to [[WP:NFC#UUI #9]], "Images that are themselves subject of commentary." I have stipulated that the article is not about each stamp itself, but the article is about the U.S. stamps of Puerto Rico from 1898 to present as addressed in sourced article narrative, which includes those stamps issued after USPS began printing them in 1978.

The Inverted Jenny stamp article is one of the stand alone “notable postage stamps” which are notable for their errors. Other than appealing with readers in a narrow interest in technical lithography errors in postage stamp mass production, they are described with the same information as that found at [[Puerto Rico on stamps]], but with the additional technical information related to pane size, number issued, reproduction process, inks and adhesive.

I have explained my rationale for omitting these technical philately details for an article devoted to the U.S. stamps about Puerto Rico, but a philatelist is welcome to add the information. That the article is not a technical article on lithographic errors does not take away from its historical interest to the general reader. It is an article which is “not about the stamps” in the sense that it is not about the stamp production errors. But the general reader has a broader interest including the historical context of the people, places and events which are nationally commemorated. For example, the Smithsonian Institute's web page on stamps is [http://arago.si.edu Arago: people, postage and the post] which mostly includes stamps without errors. The notability for the majority of stamps featured there comes from the joint resolution of Congress commissioning them and the national usage of hundreds of thousands issued for public use. [[User:TheVirginiaHistorian|TheVirginiaHistorian]] ([[User talk:TheVirginiaHistorian|talk]]) 12:41, 2 July 2016 (UTC)
===Summary for USPS images===
* The USPS endorsed the use of the Template:Stamp rationale in that its use in a WP article of “other media” stipulates in the template the USPS copyright and “all rights reserved” criteria, see USPS “integration and Planning, Rights and Permissions” division case ID 124603003 of 9/8/15 responding to an editor request for use of its stamp images in WP stamp articles.

* The proposition that a stamp article substitute stamp images, which have no free-use equivalent, with free-use images other than stamps, does not meet the test of writing to a general reader interest in the historical context of stamps such as [[Puerto Rico on stamps]]. The Template:Stamp rationale filled out for each stamp image meets the requirements of NFCC#1 which allows non-free stamp content to be used when there is no stamp substitute. The proposition that the completed Template does not meet the requirements it is written to meet, because there are requirements to meet in the Template -- is circular reasoning.

* The proposition that the article on [[Puerto Rico]] with a stamp image or two for illustration satisfies the visual interest of the general reader for knowledge about the U.S. stamps of Puerto Rico from 1898 to present dismisses the visual interest of stamps. That interest is not truncated at 1978 with the creation of the USPS. Each stamps' notability springs from the Congressional Joint Resolution commissioning them, and their general use in the public domain in the hundreds of thousands. The general reader has an interest in stamp articles by subject. The Australian post office estimates there are 22 million stamp collectors worldwide [http://www.apfelbauminc.com/blog/how-many-people-collect-stamps], Linn’s stamp magazine estimates over 5 million collectors in the U.S. alone with a particular subject interest.[http://stamps.org/A-Hobby-for-Everyone APS] Topical stamp articles have a greater notability and general reader interest than narrowly marketed video games featured at Wikipedia, each illustrated with a non-free image box cover, for instance.

* Each stamp at [[Puerto Rico on stamps]] that is accompanied with sourced commentary can be appropriately illustrated with a non-free use image according to [[WP:NFC#UUI#9]]. Topical articles on stamps with sourced commentary describing each stamp and their significance meet [[WP:NFCCP|NFCC#10]]. The proposition that they are unsourced with a citation to the Smithsonian Institute’s Arago webpage is specious; the Smithsonian Institute is a reliable source, the USPS stamp commemorating Columbus in 1992 is about Columbus landing at Puerto Rico, for instance, as sourced. [[User:TheVirginiaHistorian|TheVirginiaHistorian]] ([[User talk:TheVirginiaHistorian|talk]]) 09:45, 4 July 2016 (UTC)

== Notability guidelines and policy for eSports ==

I am wondering if it might be a good idea for the community to consider a notability guideline for [[eSports]], in light of the increasing number of articles being created about teams and competitors. Unlike most sports, there is no guideline under [[Wikipedia:Notability (sports)|Notability (sports)]], so at the moment only general biography rules seem to apply. A nomination - that so far is a keep - at [[Wikipedia:Articles for deletion/Rekkles]] has suggested that we need a "serious evaluation of all esports articles" and certainly it does seem like a field that is growing and so we should at least have guidance on. Thoughts? [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 22:41, 30 June 2016 (UTC)
:Speaking from the stance of the [[WP:VG|video games project]], compared to athletic sports, the amount of coverage esports gets is still very low and weak. Whereas athletes that achieve some level of professional play will likely get coverage due to the volume of sources that cover traditional sports, this simply doesn't exist yet for eSports, so the best advice is to stay with the general notability guidelines. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 22:52, 30 June 2016 (UTC)
::I agree that eSports is still minor in the mainstream, but it doesn't change that the number of articles being created for players and teams is increasing. By our very nature, we're more likely to attract content on the sport. We have specific guidelines for rodeo and curling, and a lot more editing comes into the eSports topics - so it may still be a good idea to create a guideline to be added to the sports topic. Just at a glance through the categories, it is very contentious as to how a lot of it would do at AFD or whether individual players are relevant. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 23:02, 30 June 2016 (UTC)
:[https://en.wikipedia.org/enwiki/w/index.php?title=User_talk:Drmies&diff=727428682&oldid=727362337 I brought up the issue with the drastically low-quality of eSports articles] to [[User:Drmies|Drmies]] a couple days ago. ESports as a whole is appropriate to keep on Wikipedia, but we at this point have hundreds of low-quality articles, with many featuring dubious notability, that largely are relying on Daily Dot and Liquipedia referencing- the second being a serious no-no, for as referencing is concerned. We must find an effective way to comb through these articles are either fix them or toss them, as the whole topic is running counter to Wikipedia standards. Furthermore, we have a number of categories and navboxes featured on these pages that contribute next to nothing, other than adding to the enormous pile of vague categories. I'd say with the number of eSports player articles, one could click at random on them and almost certainly find what I'm saying to be true ''verbatim''. [[User:DarthBotto|D<small>ARTH</small>B<small>OTTO</small>]]<sub>&nbsp;[[User talk:DarthBotto|talk]]•[[Special:Contributions/DarthBotto|cont]]</sub> 22:56, 30 June 2016 (UTC)
:As with any other SNG, one should be tailored to reflect the point where we can presume a subject has achieved the necessary coverage in reliable sources to produce an article. I guess the first step is to consider what sources ''are'' reliable, given eSports really doesn't appear in mass market media all that much. What absolutely should not happen is to just say "appeared in random event x or is popular on reddit" = notable. [[User:Resolute|Reso]][[User Talk:Resolute|lute]] 23:01, 30 June 2016 (UTC)
I've taken the liberty of picking out some articles, almost at random, to demonstrate the issues with the content:
:1. [[Lustboy]] - Won a professional championship as a "support player" in a team and is now a "strategic analyst" in a national league. All sources from Daily Dot. Does winning the championship justify inclusion, or is a support player not important enough? Is a strategic analyst a notable role? Without an expertise of eSports and a guideline it is very difficult to know.
:2. [[FORG1VEN]] - A player for a League of Legends team that is "off of the starting roster due to lack of motivation". This almost reads like cruft, but there's a reference pointing to ESPN too.
:3. [[Origen (eSports)]] - A team that finished "3rd-4th" in a League of Legends world championship. What criteria should a team have is a question we haven't really asked - in some sports you need to be winning things and is eSports important enough to include everyone?
:4. [[League of Legends Master Series]] - A professional competition with a large prize fund, but no real reliable sources. How much coverage does an eSports competition need to be notable, or is being professional enough?
This is just a few examples I've plucked out for a feel of the current content, but there's plenty that are a lot more contentious, and only a few that are clear cut keeps (typically those notable for more than competing in the competitions, so those without a following and press coverage). [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 23:14, 30 June 2016 (UTC)
* There was a long and oft-caustic debate several years back with "eSports" advocates trying to get a set of guidelines written into [[WP:NSPORTS]]. Editors from the various sports WikiProjects were all but unanimously opposed, with the consensus being that they are not actually "sports" -- the wishes of their fans notwithstanding -- but games, that they could always get an independent set of guidelines created, and failing that could rely on the GNG.<p>That being said, any set of proposed guidelines for presumptive notability ought to come with ironclad, demonstrated evidence that someone who meets those guidelines will likely meet the GNG. Given my own experiences with AfDs involving "eSports" figures, the overwhelming number of sources proffered as "reliable" tend to be their inhouse blog- and fansites, and I'm concerned that guidelines will reflect "We think this is important" or "ZOMG I love this game so much anyone who's good at it must be a figure of legendary repute!" more than any extant standard of notability. [[User talk:Ravenswing|'''<span style="background:#7F00FF;color:#00FFFF"> '' Ravenswing '' </span>''']] 00:09, 1 July 2016 (UTC)
**That particular discussion can be found [[Wikipedia_talk:Notability_(sports)/Archive_10#Statement_to_exclude_Esports_from_this_guideline|here]], for reference.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 01:16, 1 July 2016 (UTC)
** Whether or not eSports are a form of "sports" is a side issue: at that time, the regular followers of [[Wikipedia:Notability (sports)|sports notability guideline]] did not feel particularly suited to develop rules of thumb for notability of participants in eSports. But as long as the guidelines are reviewed by the general community of editors, they can be formed and maintained by any suitable group, such as the video games WikiProject. [[User:Isaacl|isaacl]] ([[User talk:Isaacl|talk]]) 01:18, 1 July 2016 (UTC)
*One of the "regular" guidelines for sports notability is "participated in Olympics" or such events. I don't see how we have such a thing here--the events are much less selective, and there are no national committees (the plethora of flagporn on all those articles notwithstanding). I agree that articles on Daily Dot don't amount to notability: it's a niche publication, explicitly. The Rekkles article has better sources, but (and I raised this at the AfD) whether those sources provide the extensive coverage required by the GNG is a matter of discussion, and I am of the opinion that they don't. What's happened with these articles, these hundreds of little biographies and dozens of big, fat, directory-style articles on the teams, is that notability is ''presumed''. BTW, MMA, which is also a kind of a sport, I suppose, was able to draw up guidelines, and the MMA articles have not been brought up in any forum that I know of recently, so it can certainly be done. [[User:Drmies|Drmies]] ([[User talk:Drmies|talk]]) 00:37, 1 July 2016 (UTC)
*I've just been making articles for things that get coverage in, among other sources, ''[[The Daily Dot]]'', ''[[TheScore eSports]]'', and ''[[ESPN]]'', and from there those articles should meet [[WP:GNG]]. From what I've seen, because the landscape of esports is constantly changes, achievement based notability requirements like those in [[WP:NSPORTS]] may not work very well. More specifically, making requirements like "players are notable if they have won the ''[[League of Legends World Championship]]''" may not work because while the winners of the most recent tournament are notable, because ''League of Legends'' was much smaller in 2011 not every player on the 2011 championship team seem to be notable. --[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 00:19, 1 July 2016 (UTC)
**I don't see how getting written up in Daily Dot or on theScore adds up to notability via the GNG. Do any of these publications ''matter''? Are they reliable, but also, do they have ''weight''? Are they considered to be independent of their subject matter? ESPN isn't, for instance; they depend on the sports they present in all kinds of ways. The landscape of eSports may be changing, but so is that of death metal and Barbie collecting, and neither of ''those'' get every participant written up without some kind of standards. For death metal, for instance, [[WP:NALBUM]], [[WP:NSONG]], [[WP:NBAND]] still apply. So, if it's a sport, sport guidelines should apply, for instance. [[User:Drmies|Drmies]] ([[User talk:Drmies|talk]]) 00:41, 1 July 2016 (UTC)
***Those publications appear to meet requirements to be [[WP:RS|reliable sources]], and can thus help an article pass [[WP:GNG]]. Beyond this whether or not the websites or the topics they cover have any lasting significance to humanity is up to opinion.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 01:10, 1 July 2016 (UTC)
****Well, ''informed'' opinion. And "appear"--yeah, I don't know. Can you prove that they have reliable editorial boards? Do they publish writing by recognized experts and journalists? Are they truly independent of the topics they cover? I don't know who argues that ESPN is truly independent, for instance; I'd love to see that evidence. [[User:Drmies|Drmies]] ([[User talk:Drmies|talk]]) 03:10, 1 July 2016 (UTC)
*****According to [http://www.dailydot.com/about/ its website] the ''[[Daily Dot]]'' was nominated for a Digday Publishing Award, has also received acclaim from other news agencies and has a large writing and editing team.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 03:40, 1 July 2016 (UTC)
*****I don't think there is a dispute regarding ESPN being a third-party source, and I think its analysis can be fairly called independent. However its sports coverage, just like most mass media sports journalism, has an entertainment role, and so not everything reported can be considered to be indicative of meeting Wikipedia's standards for inclusion. [[User:Isaacl|isaacl]] ([[User talk:Isaacl|talk]]) 03:45, 1 July 2016 (UTC)
******There was a discussion about TheScore eSports [[Talk:League_of_Legends_Pro_League|here]].--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 03:55, 1 July 2016 (UTC)
'''So, moving forward:''' Where do we go from here? Would a formal RFC be an idea here? What are we thinking in terms of guidelines? My thoughts at the moment are that there's three directions we could go in:
:1. eSports articles needing independent coverage outside of specialist websites, so only players with significant coverage not exclusive to niche websites covering the sport and related topics;
:2. A general rule that certain achievements are a sign of notability (as with, for example, junior gymnastics) - like winning a professional competition of a certain standard solo or as a main part of a team. (Or this could supplement point one.)
:3. A decision that the status quo is reasonable, and that all participants in professional competitions are eligible for inclusion.
Obviously we'd need to discuss these, but the general hunch I'm getting - from participants so far here at least - is a concern at the amount of references to The Daily Dot and The Score, and I would agree that their suitability in defining notability is questionable. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 22:20, 1 July 2016 (UTC)
*There are more reliable sources than just The Daily Dot and TheScore, and there are also many foreign languages sources that I listed at [[User:Prisencolin/esportsnews]]--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 23:42, 1 July 2016 (UTC)
**I think the problem is that so many of these sources are specific to eSports, so they may be reliable ''within'' the eSports community, but they don't necessarily prove the notability of eSports articles on Wikipedia. An earlier contributor made an allusion to death metal, in that there's many death metal blogs and websites, but that doesn't automatically make the bands that they cover notable. Some of this sources, certainly, have names attached that make me think they could be useful, like Yahoo! and ESPN.
::The key point I would make is this: With most sports, they have their niche websites and blogs, but then they receive coverage on more general websites too. So for Formula One, there's websites like F1 Fanatic and James Allen on F1, but there's also the BBC and national newspapers and so on. It's the same for football, cricket, baseball, and countless others. The question for me is, where is this wider significant coverage beyond websites like [[Blog of Legends]] and [[The Score eSports]]? I do not dispute their reliability for facts and figures, but I do dispute it for proving that these articles are notable.
::This is exactly what we need to explore, else we'll end up with articles for every eSports player and team that these specific websites cover. I personally don't feel that coverage on these should be enough, and that only major competition winners and those with substantial wider coverage should be included, but an RFC or similar process should decide these guidelines.
::Your input is massively valuable by the way as you clearly know the topic well. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 23:51, 1 July 2016 (UTC)
:::I understand your concern, but just wanted to point out that neither Blog of Legends nor TheScore eSports specialize in eSports coverage; Blog of Legends is owned by FanSided, which covers general sports and entertainment, and is in turn owned by [[Time Inc.]], the holdings company of [[Time magazine]], among other publications. TheScore publishes a general sports score app and news webste, and a fantasy sports game.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 00:14, 2 July 2016 (UTC)
::Going back to the question, the reasoning for having the subject-specific notability guidelines (SNG) like NSPORTS is to spell out conditions where if a topic has met some milestone, there will likely be sufficient sourcing that already exists or will come to exist to have that topic meet the GNG eventually. For example, a Nobel prize award winner routinely gets several articles after the award is named that detail their life and contributions, if this has not already been documented, so an SNG saying that Nobel prize winners are presumed notable works. In sports, a broad line is drawn for those that have in professional games, as to get to the professional level they likely have had to performed exceptionally at lower leagues (college or minors or equivalent), and the volume of coverage of those sports in reliable sources is still high such that these players will be documented there, if not from their current career. These SNG don't need to be 100% accurate in the source availability, since we're only making a presumption of notability, but they need to be the rule with only few exceptions.

::The problem then with eSports is that we don't have enough time or sourcing to go on to assure that if an eSports player makes it to a certain level that they are going to have sources sufficient for GNG in the future. It's probably far too early given how new eSports is relative to other sports to be able to make a fair assessment of what "rules" work to make an SNG case out of. Hence that the GNG is a safe backup, and that then leads to the discussion of what are reliable sources for eSports, which is a fair but separate question. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 00:08, 2 July 2016 (UTC)

:::GNG is a safe bet. I would say a good start for examining what is reliable is to see what pages utilize Liquipedia, which is a '''completely''' unreliable source. I fear two things from this discussion. The first is that we will simply find ourselves losing interest or going in circles, as I proposed an evaluation of esports about a year ago and it accomplished nothing, as nobody even began to comb through the articles with proper scrutiny. My second fear is that we'll try to reach a resolution for esports standards that will be inadequate, in comparison with general Wikipedia policies.

:::I believe the million dollar question is, how do we ensure that every esport article is reviewed for being up to par? There are hundreds that are probably eligible for deletion as of now, so it's a monumental task to bring the project up to snuff. [[User:DarthBotto|D<small>ARTH</small>B<small>OTTO</small>]]<sub>&nbsp;[[User talk:DarthBotto|talk]]•[[Special:Contributions/DarthBotto|cont]]</sub> 00:44, 2 July 2016 (UTC)

:::This is a good argument [[User:Masem|Masem]], however I would have one point to make regarding it: The fact that eSports is so new and in its relative infancy only supports the notion that blanket inclusion of professional players and teams is probably not appropriate at this time. I do not feel we can allow wide inclusion simply because of the work involved with checking sources. Some basic guidelines, even if they aren't quite as inflexible as something like [[WP:NFOOTY]], would be a great help in deletion decisions. One other thing, too: I personally feel a good half of the eSports players on Wikipedia could reasonably go to AFD and be expected to fail. Such a flood may not be helpful, and we've encountered issues with that sort of thing regarding schools and Pokémon among other topics in the past. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 13:46, 2 July 2016 (UTC)
:::: {{talkquote|i=y| I believe the million dollar question is, how do we ensure that every esport article is reviewed for being up to par?}} This part isn't hard. The vast majority of new (and old) eSports articles are by Prisencolin, so if we make it clear that new (and old) eSports articles need to be sourced to vetted reliable sources, with no unreferenced content in biographies of living people, then the fight is already over. Hopefully this would mean Prisencolin going back to correct previous articles before the rest of Wikipedia was as firm about the sources being used. <span style="background:#F0F0FF; padding:3px 9px 4px">[[User talk:Czar|<span style='font:bold small-caps 1.2em Avenir;color:#B048B5'>czar</span>]]</span> 18:42, 3 July 2016 (UTC)

* I don't have time to wade through the proposals above but I wanted to add that this has been discussed at [[WT:VG]] for some time. Instead of following Prisencolin's list of sources, I would encourage you to look at [[Wikipedia talk:WikiProject Video games/Sources/Archive 14#eSports revisited]] and the related/linked threads, where the sources had at least a modicum of vetting. I don't think we need an automatic bar set for eSports players—I think a surprising amount of them meet the GNG, mainly surprising because few expected so much coverage so fast. An automatic bar would undoubtably lead to even worse articles, like the lowest ranks of any of the athletic notability guidelines, as player articles will/will not be created for the major teams regardless of their actual coverage. So I'd scrap that idea to focus on the GNG. I think there is a question of whether a player is notable if their only coverage is in the Daily Dot. If Daily Dot is presumed reliable, and I believe it is, the only case for ''not'' having such an article would be that Daily Dot-exclusive coverage (with no other outside coverage) is not [[WP:SIGCOV|significant coverage]] for the GNG. Feel free to make that argument if it's convincing, otherwise the most obvious way forward is to check whether each article is significant in [[WP:VG/RS]]-vetted sources. Also I'm interested in these "hundreds" of deletion-worthy eSports articles—care to share examples? Because I've been following their creation and while their quality is low (prose copied from another cc-by-sa encyclopedias) and their sourcing needs cleanup, the majority of them do pass the GNG, at least sufficiently so that they would live through AfD noms. I am, however, glad that this content area is finally getting some attention outside the project. Please ping me if I can be useful. [[File:Eye close font awesome.svg|14px|link=user:czar/watching|I am no longer watching this page—ping if you'd like a response]]&nbsp;<span style="background:#F0F0FF; padding:3px 9px 4px">[[User talk:Czar|<span style='font:bold small-caps 1.2em Avenir;color:#B048B5'>czar</span>]]</span> 18:21, 3 July 2016 (UTC)
::{{ping|Czar}} I would support a requirement for coverage outside of The Daily Dot and eSports sources, with the usual requirements (substantial, significant) for that. That would remove any competition requirements while those are in their infancy, but mean they need to be notable beyond niche eSports circles. I think this might be worth drafting into some sort of remedy to maybe add to [[Wikipedia:Notability (sports)]]. As an aside, if the same user is creating a lot of the articles, we're kind of going off their judgement, and as the area grows - and from past experience - that doesn't end well. Certainly [[User:Prisencolin|Prisencolin]] is the most vocal in AFD debates about eSports. As for there not being many that are debatable, the debate at [[Wikipedia:Articles for deletion/FREAKAZOiD]] being so contentious is a sign that there's a few to look into, and my list at the beginning of this debate has more samples. FREAKAZOiD is one of the better sourced and even he's got delete proposals, so the area could easily fall victim to a particularly proactive AFD lister if some guidance isn't put in a place. A list of reliable sources on the WikiProject probably isn't enough, so I'd go with the outside coverage requirements for now. Sorry for the long reply. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 22:53, 3 July 2016 (UTC)
=== eSports proposal ===
* '''Proposal'''. Ok, per [[User:Czar|Czar]] and other comments, here's a starter - I'm not suggesting it's added exactly like this - for an addition to [[Wikipedia:Notability (sports)]]. Thoughts?

::eSports:
:::1. eSports subjects (competitors, teams and competitions) that have received substantial coverage via significant reliable sources beyond the eSports community and media are considered to be notable;
:::2. eSports subjects that have only received substantial coverage via The Daily Dot, The Score eSports and similar sites are not considered to be notable;
:::3. Competing in a professional competition is not considered to qualify a subject for inclusion on its own.

:This definitely still needs work but it's an idea for starters. Pinging: {{ping|DarthBotto}}, {{ping|Prisencolin}}, {{ping|Drmies}}, {{ping|Ravenswing}}. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 23:02, 3 July 2016 (UTC)
::Haven't made up my mind yet about these, but I do object to the guideline's inclusion into [[WP:NSPORT]] without broader consensus, since a lot of people just don't consider video games a sport.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 23:07, 3 July 2016 (UTC)
:::Ok, shall we discuss the guidelines and then worry about where to put them later? They're not going to be added overnight, but at least we're finally trying to gauge a consensus on them. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 23:09, 3 July 2016 (UTC)
* I'd simplify as "[[WP:SIGCOV|Significant coverage]] for separate articles on eSports players/gamers requires coverage outside of dedicated [[WP:VG/RS|eSports sources]] (e.g., ''The Daily Dot'', ''Red Bull'')." That seems to be the heart of the discussion above, at least. A discussion at [[WT:VG]] could lead to its inclusion in the [[Wikipedia:WikiProject Video games/Article guidelines|video games WikiProject guidelines]] and you could RfC all the way to another notability guideline if you want. I don't think it needs more clauses than that (I don't think we need a site-wide verdict on whether eSports are sports—sounds like a waste of time). <span style="background:#F0F0FF; padding:3px 9px 4px">[[User talk:Czar|<span style='font:bold small-caps 1.2em Avenir;color:#B048B5'>czar</span>]]</span> 23:20, 3 July 2016 (UTC)
:: I think this wording would have the effect of not including teams, which are just as potentially troublesome, because by stating "separate articles" it might suggest they can be covered in a team article. Players, teams ''and'' competitions should ideally be covered and all should require coverage outside of the decidated eSports sources. The other problem is that this might make The Daily Dot - we seem to have a degree consensus that this is a problematic site - seem legitimate as it isn't purely for eSports. I think it's important to give examples. The list also conforms to the existing notability formats and, with the greatest will in the world, restricting this to a WikiProject guideline might make it less likely to be effectively referenced in notability debates. I'd like to see it in one of the proper guidelines. I think [[WP:NESPORTS]] or siimlar would be a good abbreviation. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 23:27, 3 July 2016 (UTC)
:: ''But'', perhaps, to avoid this becoming essay length might we look to develop a consensus on these generally being a criteria rather than the technicalities just yet? If we can agree on the points broadly we can look into drafting and where they'd be put later on. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 23:29, 3 July 2016 (UTC)
::: Examples are fine—added above. Another angle to consider: I suggested starting with a local guideline as a band-aid for now, but the wound is really the larger point about niche topics and notability. This is really a discussion about what constitutes [[WP:SIGCOV|significant coverage]] for the [[WP:GNG|general notability guideline]] and whether several sources from a vetted but niche source together constitute notability. This is like a local/regional paper publishing several articles on a local business, or several low-grade indie film magazines with editorial staff publishing on an indie film, or several mobile-only games websites publishing on indie mobile games—what kind of line is being drawn about the types of noteworthy coverage considered in deciding whether a topic is independently notable for its own article, if we are discussing drawing a line at not including articles that have only been covered in The Daily Dot? <span style="background:#F0F0FF; padding:3px 9px 4px">[[User talk:Czar|<span style='font:bold small-caps 1.2em Avenir;color:#B048B5'>czar</span>]]</span> 23:41, 3 July 2016 (UTC)
:::: I think we'd be saying any sort of coverage that would meet the usual sort of biography guidelines, we don't have to be too over-specific there, the rest of notability is well-established. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 23:46, 3 July 2016 (UTC)
* Separately, I think we all would welcome outside opinions on whether The Daily Dot, TheScore, PVP Live, etc. have [[Wikipedia:Verifiability#Reliable sources|reputations for reliability]] in the first place. There are a variety of venues for such a discussion: here, [[WP:RSN]], [[WT:VG]], [[WT:VG/RS]]... <span style="background:#F0F0FF; padding:3px 9px 4px">[[User talk:Czar|<span style='font:bold small-caps 1.2em Avenir;color:#B048B5'>czar</span>]]</span> 23:22, 3 July 2016 (UTC)
:: In my view every single one would come under point two in my list, requiring coverage via reliable sources outside of the eSports community and media. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 23:30, 3 July 2016 (UTC)
::: But if an eSports-specific source isn't reliable in the first place then the conversation would be over before it begins <span style="background:#F0F0FF; padding:3px 9px 4px">[[User talk:Czar|<span style='font:bold small-caps 1.2em Avenir;color:#B048B5'>czar</span>]]</span> 23:41, 3 July 2016 (UTC)
:::: Of course, however it can also be reliable but not enough. Yahoo! has an eSports section, for example; We'd say Yahoo! is reliable generally, but if their coverage is confined to their eSports section and niche coverage of competition outcomes there, that wouldn't necessarily be enough. Also, making these sorts of notability criteria makes it less likely we'll be constantly debating the reliability of sources and relevance of them as well. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 23:46, 3 July 2016 (UTC)
* I would staunchly oppose the inclusion of any such guideline into NSPORTS. My view from the 2011 RfC hasn't changed, and I'll be happy to quote myself: "Playing video games /= "sport," no matter how much their partisans hunger to be considered Real Athletes ... This recent flurry is by no means the first attempt to claim that video gamers are "athletes" and should be covered by WP:ATHLETE. It won't be the last." Prescient of me.<p>That being said, I don't think this proposal does video gamers any favors. It doesn't set up ''any'' level of presumptive notability beyond the GNG, and its only stipulations are restrictive. Surely there must be some championships, some level of dollar earnings at which participants can reasonably clear the GNG. [[User talk:Ravenswing|'''<span style="background:#7F00FF;color:#00FFFF"> '' Ravenswing '' </span>''']] 04:54, 4 July 2016 (UTC)
::I think the last part of your point is a lot of the problem - you're raising championships and dollar earnings, but we really have no precedent or prior discussion, so it's difficult for it to be referenced or used as any sort of criteria. My view is that eSports is in its infancy to such an extent that winning a competition alone should not be enough, but the biggest winners are likely to satisfy the criteria by other means. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 12:09, 4 July 2016 (UTC)
::: Fair enough, [[User:KaisaL|KaisaL]]; I agree that there hasn't been. But it seems that most of the editors involved in this discussion aren't video game experts, and people are commenting here less out eagerness to set forth new and accurate criteria than out of grim determination to clear up ongoing messes at AfD. This isn't the way to go about it. Criteria should be developed by people out of the video games WikiProject, they should be well tested to gauge whether those who meet the criteria are likely to meet the GNG, and all that legwork should be done '''prior''' to a formal proposal being raised here or anywhere else. Failing partisans doing that work, I'm entirely comfortable with continuing to rely on the GNG. [[User talk:Ravenswing|'''<span style="background:#7F00FF;color:#00FFFF"> '' Ravenswing '' </span>''']] 13:34, 5 July 2016 (UTC)
:::: I absolutely agree that the input of experts on eSports and video games is important. However, and having seen this happen in the past, purely having the debate between those especially invested in a field without outside input can lead to a natural bias. I suppose you're right that, if this subject were being discussed actively between those parties now with a specific view to establishing guidelines and recording a consensus, there would be no need for input generally at this stage. I have purely taken on a role here intending to kick start the debate, an advocate for the discussion in a way; This discussion is almost certain to fizzle out for the archives, and my most recently nominated articles for AFD are receiving a response that is going to make it difficult to gauge a consensus on the wider issue from those too. As such, I just hope that the WikiProject and the "video game experts" you refer to actually have this debate before the topic grows much further. I hope this makes sense. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 14:30, 5 July 2016 (UTC)
* I honestly believe that GNG does the job already. I mean, I wouldn't be opposed to having this included, so you can count my input as '''Neutral, but conditional'''; I insist that there's a tighter leash on this topic, unlike all the previous attempts to fix this particular WikiProject, where people claim they have consensus, but nothing's changed. Implementing these rules may save a number of articles from being deleted, but if it's decided that it's not in favor of the project, I will insist that GNG is followed to the letter. [[User:DarthBotto|D<small>ARTH</small>B<small>OTTO</small>]]<sub>&nbsp;[[User talk:DarthBotto|talk]]•[[Special:Contributions/DarthBotto|cont]]</sub> 08:27, 4 July 2016 (UTC)
* '''Comment''' [[Wikipedia:Articles for deletion/FREAKAZOiD|This debate]], closed a few hours ago, is an interesting case to reference here. It went to a delete, but a brief discussion of the reliability of sources about eSports occurred; Prisencolin listed a number, and The Daily Dot particularly was disputed by the other user. The AFD went to a close, and this was an eSports topic with an above average amount of external coverage. It could be quite easy to nominate a lot more on similar grounds.
:The two key problems I see with just using [[WP:GNG]] is that the reliability of the sources that most of our eSports content references is disputed, and will continue to be in debates, and secondly that we have passed no community judgement on this coverage of eSports as a whole. Is an article on a sub-section of Yahoo! dedicated to eSports about the outcome of an event or somebody changing a team, for example, enough to give them notability here? Someone will say yes because it's Yahoo!, and others will say no because it's an area dedicated to the subject. For me, at this time, it's akin to saying that [[The Non-League Paper]] is enough to qualify a footballer. However what is unfortunate and may doom this debate, sadly, is that we seem to be more caught up on whether eSports is a sport and not on the actual criteria. The only other solution may be to simply start sending articles to AFD, and see what precedent forms. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 12:19, 4 July 2016 (UTC)
::If anybody wants to know, I talked to the deleting admin, and he's allowed fFREAKZOiD to go to [[WP:DRV]].--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 00:08, 6 July 2016 (UTC)
*I'm opposed to currently including any notability guidelines specific to esports at this time, allowing the GNG to do its job, only because the topic is in its infacy and it is impossible to determine if any of these will, the near-majority of the time, lead to GNG-type coverage. Maybe after a few more years we'll be able to make a better assessment, but now is too early. Note that GNG does allow RSes that are not necessarily universally accepted as RSes for any topic and allows subject-specific ones as long as elements like editorial control and fact-checking stand, so while The Daily Dot, for example, I would avoid for some topics, does seem appropriate for the context of eSports. It should be kept in mind that GNG requires significant coverage, and BLP1E still stands, so if all we can do is talk about one win a player has, that's not sufficient for GNG. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 13:00, 4 July 2016 (UTC)
::The use of The Daily Dot is certainly contentious, as it the use of many of the sites most regularly referenced. I am inclined to test the AFD waters further because [[Wikipedia:Articles for deletion/FREAKAZOiD]] going to a close - that was an article with references - suggests to me that we have huge swathes of non-notable eSports content. I had thought a better solution might be to establish some guidelines, but if that isn't going to be the case, I don't think it's fair to just let the content stand unchallenged due to a perception that a topic is in its "infancy" (which is anything only serves to promote the notion that individual players and teams shouldn't have articles unless they're somehow notable for major events with reach beyond the eSports niche). [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 14:00, 4 July 2016 (UTC)
:::I have nominated four eSports articles for AFD: [[Happy (video gamer)]], [[Lustboy]], [[FORG1VEN]] and [[Allu (gamer)]]. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 14:22, 4 July 2016 (UTC)
::That was a bad close of Freakazoid: 3 deletes, 1 redirect, 2 keeps and a 'neutral'. Given two of the delete arguments were 'this isnt notable outside of egaming' - not a valid argument if it satisfies GNG, and 'doesnt satisfy GNG and per 1e' - when the numerous sources listed indicated both it wasnt a 1e (admittedly they were most notable for a particular event) and that it had general coverage for the area. You have at most, 'no consensus' to delete there given the weight of arguments on both sides. [[User:Only in death|Only in death does duty end]] ([[User talk:Only in death|talk]]) 14:38, 4 July 2016 (UTC)
:::Though I would argue that the Freakazoid afd is a bad example to base the discussion of notability of esports players around given that the only real aspect was the player's role in a bullying incident at an esports competition and less about their skill/player achievements, so the weight of BLP1E readily applies here (justifying the AFD as delete for that purpose). --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 14:46, 4 July 2016 (UTC)
::::For BLP1E to be valid (and also the reason its not used that often sadly) it has to be the *only* reason for which they are notable. In this case primarily it was because of that incident, however since sources were presented which were unrelated to said event, it cant be said their only claim is because of that. BLP1E is very difficult to use to get stuff deleted precisely because keep voters will generally find some other coverage unrelated to the event, or will claim the event had wider implications etc. I have lost count of the number of times its blatantly ignored over the flimsiest of excuses. Dont get me wrong though, I dont think its a huge issue if the article stays or goes, however the delete closer listed no reasoning and failed to address the arguments either way (generally required in a close-run delete/keep). [[User:Only in death|Only in death does duty end]] ([[User talk:Only in death|talk]]) 15:18, 4 July 2016 (UTC)
:::::I suspect if you have issue with the close it would be best to take it up with the closer, [[User:Kelapstick|Kelapstick]]. My reference to it was simply to point out how even articles with a bit more to them than niche eSports community coverage are disputed under the criteria we have for GNG and BLP1E, and the way that general criteria are being used only serves to strengthen my view (in my opinion, of course) that we need some more specific guidelines. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 19:19, 4 July 2016 (UTC)

The notion that esports related sources should be disqualified from esports related articles is just nonsense. There are plenty of topical publications for whom their topicality doesn't, and shouldn't, disqualify them from reference. There may be particular problems with particular sources, but a blanket disqualification is obtuse at best. So long as they are [[WP:INDEPENDENT]] sources, and the only interest they have is publishing content that people want to read (like everyone else), whether they concentrate on a particular area of interest is irrelevant.

Compare disqualifying Billboard, Vibe, or The Rolling Stone from music related articles. ESPN has been discussed, and I think it would be absurd to suggest that coverage by ESPN didn't lend itself to the notability of an athlete. So why should it lend itself less so to that of a player? Even more so to WSJ, USA Today, and the like that other's involved in the conversation have been referenced in.

Remove the mostly if not entirely arbitrary ban on a swath of relevant sources and the proposal says nothing. Oppose on the grounds of capriciousness and inanity. [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 01:21, 5 July 2016 (UTC)

If it can fill up stadiums, make it's participants millionaires, make mainstream publications like ESPN take it seriously and with it's rising popularity among adolescents that it's only a matter of time before this discussion is obsolete but i strongly think [[X Games]] gold winners in e-sports should get the nod. I also think it's worrying that people with admitted ignorance, dismissive attitudes and belief of shock at the existence of the subject get to decide what it and is not notable in a field. Specialist websites are also used in most other cases too like Rolling Stone etc, as a fan of Death Metal sources like [[Metal Hammer]] are normally used, we can't expect the [[New York Times]] to report on everything can we? [[User:GuzzyG|GuzzyG]] ([[User talk:GuzzyG|talk]]) 01:49, 5 July 2016 (UTC)
:Notability is not based on popularity, though popularity ''can'' potentially lead to notable coverage. The ''field'' of eSports is clearly notable, but right now, for players, its hard to tell. As a relevant example, reality television is huge and here to stay, with similar prizes to be won and even larger audiences at times, but we don't cover every player or winner unless there is notability beyond their appearance on the show (eg someone like [[Susan Boyle]] or [[Rob Mariano]]). --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 01:56, 5 July 2016 (UTC)
:: I'd support reality television winners, I made this comment a while ago on this subject and i think it suits it well. "I've noticed there's a alot of subconscious thinking on this encyclopedia that's associated with things that are seen negative in society like reality television, e-sports, porn, beauty pageants, criminals, mass murderers, internet personalities (memes/youtuber), heavier more extreme music (black metal, deathcore etc) and graffiti/street art, you're probably thinking "these are not important/shouldn't be notable/i just don't get it" but that's the point, there' just some notable things in these subjects that's not going to be reported in the mainstream media and where we should start looking in specialist media or we lose our viewers to sub wikis which i think is a waste. (notice there's specific guidelines that block these types of things?) It's a bold prediction but there should honestly be a relook at the qualifying criteria to online entertainment (youtube) and electronic sports as i can only imagine as this current generation gets of old age and is common to this type of thing that it will be the norm. I know some might want to resist that but it's a fact. Yes playing games and being notable at it may be odd to us but i'm sure dunking a ball in a hoop would be odd to some too." i don't think every player should get a article mind you but when it comes to winners of their equivalent of a world championship i do. [[User:GuzzyG|GuzzyG]] ([[User talk:GuzzyG|talk]]) 02:11, 5 July 2016 (UTC)
:::It's not about the topic being "negative". In fact, the success of [[WP:PORN|the WikiProject Pornography]] to find a way to create encyclopedic bios for an industry that is looked down upon society is a counterpoint. What we have to recognize is that we are limited by what is covered in RS, and many traditional RSes shy away from these topics. There are bound to be more "new media" sources that will come in the future that will meet our RS definitions then, but they aren't there now, and there's no reason to make special cases in terms of subject specific notability guidelines, only to review RSes to show how the GNG can be met. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 02:17, 5 July 2016 (UTC)
::: I'd consider [[The Daily Dot]] and [[ESPN]] a reliable source, would you not agree? I'd also consider winning a medal in a competition like the [[X Games]] being notable. I just think that the mission of this site should be to cover notable things in every field, if you win a [[League of Legends World Championship|world championship]] in a field you get an article if you get nominated for the top [[AVN Award for Female Performer of the Year|award]] in your field you should qualify. I'm not a fan of sending people to a different place to get information that is source able (The Daily Dot). That's a general site issue though so with these current guidlines i can see that these e-sports players might not pass GNG, i just think that specialist media should be included and encouraged. Then again i have a Excel sheet of over 50, 000 people that should qualify but are bogged down by some ridiculous guideline so it could just be me. [[User:GuzzyG|GuzzyG]] ([[User talk:GuzzyG|talk]]) 02:38, 5 July 2016 (UTC)
*My two cents I've mentioned at [[WP:VG]] in the past as well - I think the [[WP:GNG]] is sufficient at this point, I think the problem more lies in who is writing and maintaining these eSports articles. Much of the core, experienced editors at WikiProject Video Games just aren't all that interested in it (myself included). As such, many of the articles are being created and maintained by relatively inexperienced editors, or ones with extremely lenient interpretations of the GNG, RS, and significant coverage. I think that if/when more people just get more involved, we'll naturally be able to start weeding out some of the garbage out there. [[User:Sergecross73|<span style="color:green">Sergecross73</span>]] [[User talk:Sergecross73|<span style="color:teal">msg me</span>]] 12:34, 5 July 2016 (UTC)

===Arbitrary section break===
<small>Apologies for length.</small>

{{ping|Masem}}, it seems, at least to me, that the actual special case is not allowing these sources to weight in on notability, but trying to establish an arbitrary guideline disqualifying them for no apparent reason. I'm only commenting on the [[League of Legends]] players, because I don't really follow CS:GO or Starcraft, but looking at the three recent AfDs for league players that partially started this thread:

* [[Rekkles]]: 13 sources including USA Today and WSJ already in the article. News searches (WP:BEFORE plz) find further mention in Yahoo and ESPN. You can add the team's [https://www.fnatic.com/players/LoL/Rekkles/ official site] to the list as a primary. This is in addition to what appears to be probably thousands of hits for outlets that cover esports in particular in multiple languages.

* [[FORG1VEN]]: Currently poorly sourced, that's a given, but does include coverage by ESPN. Searches find [https://esports.yahoo.com/origen-picks-up-forg1ven-hybrid-181638764.html Yahoo]. Official ruling by [http://2015.na.lolesports.com/articles/competitive-ruling-konstantinos-%E2%80%98forg1ven%E2%80%99-tzortziou Riot], which in this case is not simply a game developer, but the officiating organization, so is the esports equivalent of a ruling by FIFA or the NFL. There is substantial corresponding esports coverage pre and post ruling, as well as a good deal of esports coverage regarding his exception from Greek military service.

* [[Lustboy]], currently a stub. Searches find [http://espn.go.com/esports/story/_/id/15612467/longzhu-switches-seven-man-roster-flame-frozen-benched ESPN] coverage of him as a coach, and a half dozen other ESPN articles. Looks like he got passing mention in [http://www.forbes.com/sites/johngaudiosi/2012/08/04/korean-pro-gamer-bok-reapered-han-gyu-explains-why-league-of-legends-is-dominating-asia/#41b36b081701 Forbes]. I see a dedicated spotlight bio by [http://2015.na.lolesports.com/articles/you-cant-see-him-rise-lustboy Riot]. And again, all of this is in addition to scores or more of esports outlet coverage.

So, at least for these three individuals, there seems to be no shortage of sources. If we do need a policy beyond [[WP:GNG]] these article are patently bad examples of why. Beyond this, there's been, as far a I can tell, no substantive argument as to why esports outlets should be a special case other than ones that seem to boil down to ''"I don't particularly care for it," "I'm not familiar,"'' or ''"I'd really just prefer to get rid of a lot of these articles on people I don't personally recognize."'' [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 13:18, 5 July 2016 (UTC)
:Your comments are kind of what I'm getting at in my comment above. Your examples show an extremely lax interpretation of our notability standards. For example, general consensus is to avoid Forbes "Contributor" written articles, because they're not of the same caliber of actual ''Forbes'' staff writers - they're semi-professional bloggers with a history for making mistakes or controversial claims. WP:VG consensus is generally not to use them. Your example of the ESPN source for "Lustboy" is pretty weak too - sure ESPN is a reliable source, but is that really significant coverage for Lustboy himself? Its a very short article, with very little about it in regards to Lustboy (most is about the team, not Lustboy). I think you're setting the bar a bit too low, as are the article creators, and that's why they keep getting sent to AFD... [[User:Sergecross73|<span style="color:green">Sergecross73</span>]] [[User talk:Sergecross73|<span style="color:teal">msg me</span>]] 13:54, 5 July 2016 (UTC)
::The particular forbes contributor writer is John Gaudiosi and according to his self written biography: "I've been covering the video game space for 20 years for outlets like ''[[The Washington Post]]'', ''[[Reuters]]'', ''[[CNET]]'', ''[[AOL]]'', ''[[Wired Magazine]]'', ''[[Yahoo!]]'', ''[[Entertainment Weekly]]'', ''[[NBC]]'', ''[[Variety magazine|Variety]]'', ''[[Maxim]]'', ''[[EGM]]'', and ''[[ESPN]]''. I serve as EIC of GamerHub.tv and co-founder of GamerHub Content Network, a video game and technology video syndication network that works with Tribune and DBG to syndicate game videos and editorial around the world. I also cover games for outlets like The Hollywood Reporter, IGN, Geek Monthly, CNN, DigitalTrends and PrimaGames."--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 00:27, 6 July 2016 (UTC)

:Keep in mind that notability is more than just being named in a source -we are looking for significant coverage across multiple sources. Most eSports players are listed as winners, but that's not significant coverage, instead we're looking for more to write about beyond the player's record. (Rekkles' mentions in the USA Today article are just about the minimum that we're looking for). If this is typical of the current type of coverage of players, then there's no way we can asset a subject-specific notability guideline since there's no assurance the GNG can be met on a regular basis by winners. But the GNG itself remains just fine for notability, as long as issues with sourcing and reliable sources (as Sergecross alludes to) are met. --[[User:Masem|M<font size="-3">ASEM</font>]] ([[User Talk:Masem|t]]) 14:06, 5 July 2016 (UTC)

:Timothyjosephwood, I'm going to have to salt your argument about the people here being ignorant to the topic, so they are not in a position to lend input, as I myself was in the upper management of several prominent esports organizations between 2008 to 2014, and I was the person who brought this issue up with Drmies in the first place. ESPN is terrific and reliable source, but most of the articles in question use it as a source to describe teams and not the players themselves and even then, its presence is light. On top of that, the articles up for deletion are being dared to present the content and reliable sources that will bring them up to par, but they've thus far failed to do so. Even upon independently researching the players, there was next to no content about game-changing transitions that unreliable sources could present. I mean, is there anything encyclopedic about [[FORG1VEN]], aside from his business with H2k-Gaming and facing a ban? [[User:DarthBotto|D<small>ARTH</small>B<small>OTTO</small>]]<sub>&nbsp;[[User talk:DarthBotto|talk]]•[[Special:Contributions/DarthBotto|cont]]</sub> 23:09, 5 July 2016 (UTC)
::There's been a real failure on both sides to define exactly what "encyclopedic value" even is. In any case, broader ideas of what does and does not belong on Wikipedia are probably discussion for another time. Consensus is that many athletes and competitors of other types of games belong on Wikipedia, so therefore why can't video game player, provided they have enough coverage in sources.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 00:30, 6 July 2016 (UTC)
::: Not a single person has argued that articles on video game players don't belong on Wikipedia. Not a single person has argued that video game players inherently lack encyclopedic value. [[User talk:Ravenswing|'''<span style="background:#7F00FF;color:#00FFFF"> '' Ravenswing '' </span>''']] 03:48, 6 July 2016 (UTC)
::::DarthBotto has been continuously questioning whether certain types of content are encyclopedic, like here. That's what I'm alluding to.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 22:45, 6 July 2016 (UTC)
:::::DarthBotto has said that eSports is an appropriate topic for Wikipedia, so I agree with Ravenswing: there's no attempt to argue that even with appropriate significant, independent, non-routine, non-promotional secondary coverage in reliable sources, this topic should not be covered. [[User:Isaacl|isaacl]] ([[User talk:Isaacl|talk]]) 05:33, 7 July 2016 (UTC)
::::::I have been wondering about somekind of "inherent encyclopedic value" concept for quite some time as well, be it for webcomics or [[Overwatch porn]], so I simply decided that if something is described in words by a reliable source, it is likely to be considered interesting and worth including. The same should go for esports-related topics. The biggest issue in my eyes is that there only seems to be a small set of reliable source frequently discussing the topic. That makes it unclear whether every single thing that The Daily Dot writes is worth repeating on Wikipedia. If the same information is provided by multiple reliable sources, its inherent value is much clearer. The field of said sources is irrelevant, as long as the actual staff is different. ~[[User:Maplestrip|<span style="color:#005080">Mable</span>]] ([[User talk:Maplestrip|<span style="color:#700090">chat</span>]]) 08:48, 7 July 2016 (UTC)

=== Some thoughts on the latest developments at AFD ===
The ongoing AFD debates on a number of players have had some quite back-and-forth discussions about eSports sources, the importance (or lack thereof) of competing in or even winning professional competitions, and whether passing mentions in articles about teams confer notability. There's also been some less savoury stuff about whether those that aren't experts on the topic have a right to an opinion (which is less up for discussion - they very much do per the way Wikipedia works). I am finding that the community is, indeed, torn on a number of questions:
:* What constitutes a reliable source for eSports coverage?
:* How important is competing in a professional team competition?
:* Should professional eSports competitions carry the same weight as other sports (classification disputed) in considerations of notability?
:* Does coverage of a team that mentions a player briefly confer their notability as an individual?
:* How important is generic coverage (firings, hirings, competing, results) in establishing notability on Wikipedia?
:* Is one or two passing mentions via well-established mainstream sources enough to justify an article?
:* What constitutes significant coverage within an acceptable source?
I'm not asking for answers to these questions - consider them hypothetical - but they do give us a feel of the clear split. Furthermore, that split isn't a case of experts versus outsiders, but is happening between contributors to the video gaming WikiProject. The current AFDs are all going to wind up contentious and I think we'll end up with a couple of them going to a no consensus.
Some of this is a sign of differing interpretations of [[WP:GNG]], [[WP:BLP1E]], [[WP:RS]] and other general Wikipedia guidance. But some of it is a clear sign that a fuller discussion does need to take place about eSports topics - particularly those on individuals - else I wouldn't be surprised to see many more of the articles we have going through the AFD process, and that doesn't seem productive (even if it is appropriate when doubts exist on any topic). [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 16:19, 6 July 2016 (UTC)

* For my part, it seems strange to me that some of these elements are in dispute at all (although I do agree they are points of contention in the recent AfDs). I certainly do agree that "eSports" are prominent enough to have notability standards, but those standards ''do not yet exist,'' so no argument along the lines of "People who've participated in X competition should be notable!" or "People who've coached X team should be notable!" can be sustained. The GNG is unambiguous that fleeting mentions, however prominent the sources, ''do not count towards notability.'' WP:ROUTINE is unambiguous about generic coverage not counting towards notability. [[User talk:Ravenswing|'''<span style="background:#7F00FF;color:#00FFFF"> '' Ravenswing '' </span>''']] 17:03, 6 July 2016 (UTC)
* Although there are dissenters, a number of your questions have a current consensus view in the general English Wikipedia community:
** Coverage of a team does not meet Wikipedia's standards of inclusion for the individual team members.
** Routine coverage such as you listed does not meet Wikipedia's standards of inclusion.
** Passing mentions do not consist of significant coverage and do not meet Wikipedia's standards of inclusion.
* Regarding participation in competitions, although there are various subject-specific guidelines that list these as rules of thumb that suggest an individual meets Wikipedia's standards for inclusion, they do not set a new bar for inclusion. Wikipedia does not use achievements as a standard for inclusion: significant, independent, non-routine, non-promotional [[WP:SECONDARY|secondary coverage]] from [[WP:RS|reliable sources]] is required. The rules of thumb are just indicative that appropriate coverage can be found, given enough time to locate them. [[User:Isaacl|isaacl]] ([[User talk:Isaacl|talk]]) 18:29, 6 July 2016 (UTC)
**[[WP:NSPORT]], which seems most applicable, does appear to set some variety of "new bar" for the particular areas it covers. Per the guidance, subject must either meet [[WP:GNG]] or the criteria of NSPORT. Even if it is officially just a rule of thumb, it is often used as a hard standard in practice. [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 19:30, 6 July 2016 (UTC)
***The first sentence, second paragraph, and third paragraph of the sports notability guidelines page provide details on the relationship with the general notability guideline, as well as the associated [[Wikipedia:Notability (sports)/FAQ|frequently asked questions page]], which explicitly states that the guidelines do not create new criteria for inclusion in Wikipedia. This has been agreed upon by consensus since the inception of these guidelines and periodically since. If closers of articles for deletion discussion are ignoring this consensus, it's unfortunate. [[User:Isaacl|isaacl]] ([[User talk:Isaacl|talk]]) 22:46, 6 July 2016 (UTC)
*** It doesn't, really, and that's a misconception editors active on sports WikiProjects have to correct at AfD all too often. The whole purpose of NSPORTS criteria is to set forth achievements by which a player is highly likely to meet the GNG. A bunch of us consistently vote to delete at AfD if a player technically meets a criterion if after diligent search we can't find any coverage in reliable sources. [[User talk:Ravenswing|'''<span style="background:#7F00FF;color:#00FFFF"> '' Ravenswing '' </span>''']] 03:54, 7 July 2016 (UTC)
*The article [[Karrigan]] was just [[WP:A7]] speedily deleted by {{ping|Nyttend}} after it had been in mainspace for over a month. Perhaps he wants to share his thoughts here?--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 21:22, 6 July 2016 (UTC)
:*This article merely said that he was the "in-game leader" for an e-sports group, mentioned a couple of other groups of which he'd been a member, and noted an immigration hiccup that he'd encountered. It didn't demonstrate any evidence of real-life importance. Of course, A7 shouldn't be used on someone who's demonstrably notable, but it provided no secondary source coverage. This is distinctly not the kind of article that should be retained: barring solid coverage in solid secondary sources, professional video game players should be treated like anyone else. [[WP:ATHLETE]] provides for keeping professional sportsmen because they routinely get coverage in secondary sources, and it would be unhelpful to have notability-based deletion discussions for individuals who are almost certain to pass WP:GNG and unhelpful to have the occasional hole for that rare individual who doesn't otherwise pass GNG. Professional video game playing is new enough that there's no parallel to secondary sources such as [[:Category:Baseball books]], [[:Category:Boxing books]], [[:Category:Association football books]], [[:Category:Olympic Games books]], etc. Perhaps those sources will start to appear in coming years, but in the absence of extensive sport-wide reference works and other comprehensive publications, presuming these folks to be notable (or even A7-exempt) purely because of their video game accomplishments is fundamentally incompatible with [[WP:BALL]]. [[User:Nyttend|Nyttend]] ([[User talk:Nyttend|talk]]) 03:03, 7 July 2016 (UTC)
::::The comment, ''A7 shouldn't be used on someone who's demonstrably notable, but it provided no secondary source coverage'' demonstrates a lack of understanding of A7. A7 says, ''The criterion does not apply to any article that makes any credible claim of significance or importance even if the claim is not supported by a reliable source or does not qualify on Wikipedia's notability guidelines''. That's a very low bar. If you're speedy deleting an article based on the lack of secondary sources, that's well outside what A7 allows. -- [[User:RoySmith|RoySmith]] [[User Talk:RoySmith|(talk)]] 13:22, 8 July 2016 (UTC)
:**I'm not sure the proper procedure to do this but I would like to request the article back with an AfD if needed. The subject is one of the top ''Counter-Strike'' players in the world, and just look up "Karrigan" on the web and you'll find many secondary sources about him. Oh and there is coverage of him outside of just the teams, [http://www.sport1.de/esports/counter-strike-go/2015/12/counter-strike-global-offensive-karrigan-und-sein-jahr-bei-tsm this article] found on ''[[Sport1 (Germany)|Sport1]]'', for instance.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 03:32, 7 July 2016 (UTC)
:***[[User:Prisencolin|Prisencolin]], you may open up a review at [[Wikipedia:Deletion review]]. [[User:DarthBotto|D<small>ARTH</small>B<small>OTTO</small>]]<sub>&nbsp;[[User talk:DarthBotto|talk]]•[[Special:Contributions/DarthBotto|cont]]</sub> 07:27, 7 July 2016 (UTC)
:****I was hoping to work something out with {{ping|Nyttend}} first.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 22:09, 7 July 2016 (UTC)
:*****So I've decided to submit a DRV (another one...), in case I forget it about it later or am unable to. For the record, for the record though, there are some books about esports, including ''Game Boys'' by Michael Kane, ''Raising the Stakes'' by [[TL Taylor]], and OpTic Gaming: the Making of Esports Champions by H3CZ, [[NaDeSHot]], [[Scump]] et al.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 23:27, 7 July 2016 (UTC)
:******Of course, you have every right to do this and I do agree that with this subject, it's necessary to be sure that everything was done correctly. In the meantime, I'd encourage you to lay off the creation of new articles until we have a developed consensus with assertive conclusions. In the time since this very discussion began, you've created nineteen new articles, which unfortunately comes across as an act of defiance. Mind you, I'm a big supporter of esports, but I also want to see the topic held to the same standards as everything else on Wikipedia. I don't believe just adding to the pile is going to help this discussion at all. [[User:DarthBotto|D<small>ARTH</small>B<small>OTTO</small>]]<sub>&nbsp;[[User talk:DarthBotto|talk]]•[[Special:Contributions/DarthBotto|cont]]</sub> 22:51, 9 July 2016 (UTC)
:*******Alright I suppose I'll stop for now as a good faith gesture, even though I've been holding myself to a timetable to create the articles that are notable.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 23:03, 9 July 2016 (UTC)
====Proposal 2====
This proposal is broadly modeled after [[WP:NSPORT]]. Whether you consider this a sport in some broad philosophical sense isn't important, the continuity is in the competitive aspect as it defines notability, as well as the established history of using this type of guideline to determine notability in a range of competitions. Whether a guideline in this area is incorporated into the actual text of NSPORT is equally unimportant.

* An attempt is made to define esports, and is largely done in an effort to remain as analogous to athletic sports as possible. The goal is to exclude as many newcomers or fads as possible, while providing a criteria where areas generally recognized as legitimate (namely Starcraft, League of Legends, and CS:GO) will easily qualify.

* Emphasis is given to the exclusivity of high level competition. An appropriate level of competition should rightfully exclude the vast majority of players, which is what lends notability. This policy anchors this to national level tournaments or higher, in lieu of attempting to specify particular tournaments for each game, and this may not be possible in a policy that would have any longevity. My understanding is that most large tournaments take place on the multi-national/regional level, and so this is a standard that will set a bar easily met by established competitions, and yet easily exclude amateur and semi-professional play.

* Further emphasis is given to continuity of participation. This is a departure from NSPORT, as single event participation in a sufficiently high level event (however unlikely without an extensive history), qualifies individuals in many NSPORT guidelines. This is done to further restrict the potential field and weed out minor players.

I have attempted to be broad enough to apply across games, and specific enough that there will be clear instances where individuals will objectively qualify and not qualify. Improvement can almost certainly be made, but hopefully this is a substantial starting place grounded in similar accepted policy. [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 19:24, 6 July 2016 (UTC)

{{talkquote|'''Individuals participating in electronic sports/professional video game playing are presumed notable if the following criteria are satisfied:'''

1. The game being played qualifies as an esport or is otherwise included in high-level, professional competition. Consider the presence of the following:
* Significant barriers-to-entry: Participation requires an extended successful amateur play, extended successful semi-professional play, corporate sponsorship, unusually exceptional ability, or similar requirements which prevent the vast majority of players from participating on a competitive level.
* Status as a spectator event: high-level competitive play consistently draws a substantial audience of viewers as a form of entertainment, especially as events which are broadcast live. Competitions are regularly held in venues designed to accommodate a live viewing audience.
* Codified governing rules, formulated, maintained and enforced by an officiating body
* Regular national, regional and global tournaments including an escalation of the barrier-to-entry which ensures that even significant portions of those who play the game professionally are not admitted to the highest levels of competition.
* Regular media coverage of events and players
* Large consistent base of amateur players. Qualifying games should typically be stable among the most played games globally.

2. The individual has participated substantially on a professional level. Consider the presence of the following:
* The individual consistently participated and was successful in major competitions on the national, regional or global level.
**Participation in competitions taking place at lower than a national level may only be considered if it garners coverage comparable to that typically given to a competition taking place at the national level or higher.
**Participation solely in competitions below the national level, even extensively or highly successfully, will most likely not qualify the individual under this critera, barring extenuating circumstances.
**Individuals with single or very few instances of participation or achievement should typically not be considered notable unless there is reason to expect their continued high-level participation, such as admittance to an established franchise with an extended contract
**Individuals with a history of participation in global-level competition will typically meet this standard, regardless of whether they have won at this level.
**First place finishes do not automatically qualify an individual. Neither do successive lesser place finishes disqualify. Rather, career performance should be considered as a whole to establish the degree of overall success.
* The individual consistently earned substantial income from sources related to their competitively played game.
* The individual has achieved other milestones related to their competitive play including:
** Being admitted to a high-profile franchise
** Receiving honors related to their participation
** Was involved in other achievements of a historic value
}}
* '''Oppose''' I'm sorry, but not at all. I admire your passion for eSports and certainly you have been a strong voice in the ongoing AFD debates about this, but it is not football, baseball, hockey or a sport of that ilk. Being successful in "major competitions on the national, regional or global level" is an unthinkable level of inclusion for an area with such limited mainstream coverage, and especially when those major competitions are still broadly so niche and receive only specialist coverage the vast majority of the time. Simple "participation substantially on a professional level" is even more so. As for defining a criteria by "being admitted to a high-profile franchise" and "substantial income from sources", those would be dubious even for a genuinely top-level sport. The only thing I could possibly support in terms of competition level for such a niche field (as it is right now) would be to allow winners of the most significant global competitions to have an article, as we (for example) have for gymnastics. But then those winners are often ''teams'', so the individuals should really be merged to those team articles if their only notability were that competition play. I really just think this is a criteria better suited to an eSports Wikia than Wikipedia. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 21:09, 6 July 2016 (UTC)
::Honestly, besides a rewrite of the main League article last year, I haven't contributed to this area at all prior to this. What about settling on world level competition? This seems to be ubiquitous in NSPORT. I didn't even know badminton had a world championship until today. Is that a minimum that could potentially be agreed upon?
::As to the franchise and income clauses, those are meant mainly to be exclusionary...as in...if you don't do this full time we're not even going to have the discussion. They both can be removed. I have no objection to that.
::I realize you may be against the topic generally. Like it or not there seems to be hundreds of these articles. I actually started to list them and stopped straight away. I'm not sure that the argument they are inherently less notable than badminton or curling really stands muster. So I'm trying to find some kind of middle ground that can be agreed upon. [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 21:35, 6 July 2016 (UTC)
::: Well there's multiple parts: we have the leagues, the seasons, the teams and then the players. For some "major" sports, the players are generally notable based on a small number of games played. For college football, the league, teams and season articles are but not players. For others, it's more of a mix. There's a middle ground on all of them. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 21:49, 6 July 2016 (UTC)
::::Well do in fact have articles for some current D1 college football players, just not all of them obviously.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 22:00, 6 July 2016 (UTC)
::: There may be hundreds of articles, and a large number of them may be of dubious notability. There's four at AFD right now and not one of them is proving to be a clear-cut keep. Badminton and curling are Olympic sports so I would say they're absolutely more notable than eSports at this time. My personal opinion is that a maximum for meeting the notability criteria by way of competition is winning a major individual competition; I wouldn't even say being part of a team that wins a major competition, that should qualify the team and not the player. I would personally say that any guidelines should be focused instead on what constitutes significant coverage for this field, which is what my initial proposals attempted to address. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 21:54, 6 July 2016 (UTC)
::::What of players who play for multiple notable teams? The teams are just franchises, or in Asia and increasingly the US, just glorified extended corporate sponsorships. It's rare cases where any team goes a season without significant roster changes. [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 22:12, 6 July 2016 (UTC)
:::::No current esports team is really a [[franchise]] of (this was a typo) a larger organization, so the particular word should probably be replaced with just "team".--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 22:35, 6 July 2016 (UTC)
::::::[[Samsung Galaxy]] Blue/White, [[SK Telecom]] T1, [[Jin Air]] Green Wings, [[SBENU]] Sonicboom, ROX Tiger (Guongzhou Huaduo Network Technology, LLC). In the US, [[Team SoloMid|TSM]] and [[Counter Logic Gaming|CLG]] are multi-game esports organizations. None of these are a group of five guys who like playing together and when they decide to stop the team ends. They are franchises proper. [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 23:25, 6 July 2016 (UTC)
:::::::There was a typo, I mean "franchise OF a larger organization" not "franchise OR a larger organization". And by larger organization I'm talking about a league or association like the [[NFL]]--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 22:05, 7 July 2016 (UTC)
:::::Well, for bands for example, the members almost never have their own articles unless they've received substantial coverage or achieved significant success separately. But I don't feel that simply playing for two teams is enough in this sport either, it's just not important enough yet. And, I've not really delved into teams but I'm sure there's issues with some of those too. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 22:42, 6 July 2016 (UTC)
:::::I'm not going to be online much for the next few days (I'm sure you'll be delighted by this!) but I think I've made plenty of quite clear arguments by now anyway. I feel consensus on this whole issue is going to be very hard to come by and so we might indeed be debating [[WP:GNG]] for years to come at AFD. [[User:KaisaL|KaisaL]] ([[User talk:KaisaL|talk]]) 22:42, 6 July 2016 (UTC)
*'''Strong Freaking Oppose:''' That's an impossibly vague set of criteria. What's "substantial income?" What's a "high-profile franchise?" How broadly do you define "honors?" Do consider that over the years, the various SNGs across Wikipedia started out just as loosey-goosey, and keep on being tightened and tightened, as editors hellbent on saving their creations claim that a collegiate "Academic Rookie of the Week" award constitutes a "preeminent honor," or that having had a speaking line in two Oscar-winning movies constitutes a "significant body of work." [[User talk:Ravenswing|'''<span style="background:#7F00FF;color:#00FFFF"> '' Ravenswing '' </span>''']] 04:02, 7 July 2016 (UTC)
::Starting out with something "loosey goosey" and then tightening was kindof the point. And I would appreciate quite more strong opposes so long as they include specific parts people take issue with. Eliminating the honors is perfectly fine. It is vague and there isn't an obvious way to fix that. The goal of the income portion was to categorically eliminate everyone who may play in local tournaments but don't do is as an actual job. What do you think about language saying that players should have played full time? The focus being on categorical elimination of those who don't, not categorical inclusion of those who do. [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 10:17, 7 July 2016 (UTC)
::Consider changing to: "Full-time players: While not all full time players will be notable, those who play competitively on less than a full-time basis will generally not meet notability under this guideline. This includes students who play competitively as part of a scholarship." [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 12:05, 7 July 2016 (UTC)
::: Here's the issue with that: a recent discussion took umbrage with the NHOCKEY guideline, feeling that a couple of leagues (of which she happened to be a partisan) were undervalued, and that they should be considered top-tier leagues. Our retort was, as all NSPORTS guidelines exist as guides as to what athletes can reliably pass the GNG, that she had to do more than assert that some of the players in those leagues were notable. For those leagues to be in the top tier, it would have to be demonstrated that ''each and every player in league history'' who had played so much as a single minute could meet the GNG, and it was provably not remotely the case.<p>If, therefore, you assert (for the sake of argument) that players on eSports teams in a competitive league should be presumptively notable, it needs to be the case that ''every'' player on ''every'' team in that league can meet the GNG. Demonstrate proof of that, and I'm perfectly willing to support such a criterion. [[User talk:Ravenswing|'''<span style="background:#7F00FF;color:#00FFFF"> '' Ravenswing '' </span>''']] 22:56, 8 July 2016 (UTC)
*'''Oppose''' "Esports" are a modern enough phenomenon that there is no need for a SNG "presumed notability" either the subject is notable per GNG or not and there in not a significant body of indivduals whose RS are hard to find because they are old, offline etc. <p>This should be read by the closer, as a flat opposition to ''any'' SNG for "Esports" because SNGs, particularly in sports, are abused to include articles on subjects who do not have nor will ever have coverage which meets GNG. [[User:Jbhunley|<span style="font-family:Monotype Corsiva;font-size:14pt;color:#886600">J</span><span style="font-family:Lucida Calligraphy;font-size:10pt;color:#886600">bh</span>]][[User_talk:Jbhunley|<span style="color: #00888F"><sup>Talk</sup></span>]] 18:12, 7 July 2016 (UTC)
*'''Abstain''', this set of guidelines is just too vague to be accepted, as other users have pointed out. It also seems to just uphold the status quo by reiterating [[Wikipedia:Notability_(people)#Any_biography]] over and over again in different ways. Another concern I have is that there isn't a real definition what "national level tournaments" are, because eSports aren't organized along national borders, unlike [[List of association football competitions|football competitions]]. The closest analogue we have, and what you're probably alluding to are the regionals ''[[League of Legends]]'' leagues, like the [[EU LCS|LCS]], [[League of Legends Champions Korea|LCK]] etc. I'm not opposed to these guidelines per se, but they just way to vague to become an official guideline.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 22:21, 7 July 2016 (UTC)
::As I said originally, I just wanted to provide a more substantial starting off point for discussion about what might be agreed upon. It's vague by design. But there seems a general feeling of "I don't want anything at all" or people that have been unresponsive to attempts at trying to formulate their criticism into actual changes. So it seems this will probably go nowhere on any front. [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 23:25, 7 July 2016 (UTC)
:::My thought is that if it's this vague, we might as well not have it at all. Either that or we could just have a notice where that just reaffirms the fact that eSports articles need to meet [[WP:GNG]]. There's no need define which games are eSports; we can just list out high profile games like ''LoL'', ''Dota'', ''SC'' etc. and any new emerging titles can be added later. --[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 23:34, 7 July 2016 (UTC)
*'''Mostly oppose'''. I would prefer something structured like [[WP:NHOCKEY]] and [[WP:NHOCKEY/LA]], where we would have a tiered list of esports based on community consensus (e.g. LOL, CS:GO, DOTA II, SC2 etc. as top tier, smaller titles like WOT as a lower tiers) and assess notability for players and teams striclty based on results at top events. For example, community consensus on League may be that a player on a team that reaches the knockout bracket of the League worlds is presumed notable if mentioned in sources covering the event/team result and players on a team that reaches the finals of one of the regional LCS championships is presumed notable if mentioned in sources. For CS:GO, this could be making the finals at a CS:GO Major, for SC2, making the finals of WCS, or winning GSL or Proleague, etc. Of course if a subject could also meet GNG without meeting these standards. ---- [[User:Patar knight|Patar knight]] - <sup>[[User talk:Patar knight|chat]]</sup>/<sub>[[Special:Contributions/Patar knight|contributions]]</sub> 03:58, 8 July 2016 (UTC)
[[User:Prisencolin|Prisencolin]], [[User:Patar knight|Patar knight]], Maybe there's a different take away lesson here. Maybe what needs to happen is an esports WikiProject, and after there is a substantial involved community knowledgeable about the subject, we should revisit issues like these. [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 11:23, 8 July 2016 (UTC)
:I've taken the liberty of creating a place holder page [https://en.wikipedia.org/wiki/Wikipedia:WikiProject_eSports here]. I'm gonna poke around and see if I can find someone more versed in setting all this up. [[User:Timothyjosephwood|<span style="color:#a56d3f;font-family:Impact;">Timothy</span><span style="color:#6f3800;font-family:Impact;">Joseph</span><span style="color:#422501;font-family:Impact;">Wood</span>]] 12:12, 8 July 2016 (UTC)
::I'm wholly in support of this, but pretty sure you need permission before creating a wikiproject page, so I would move this into userspace for now if I were you.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 20:45, 8 July 2016 (UTC)
:::Actually, I read the rules again and found no such guideline. There is a suggestion though that these pages be kept in userspace until enough editors come aboard.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 20:48, 8 July 2016 (UTC)
*'''Oppose'''. Before adding any SNG criteria, we first should ensure that it really does mean that in a vast majority of cases, subjects covered by it would in fact meet the GNG. SNGs are not "alternate criteria" to the GNG, but instead are meant to highlight cases where sufficient coverage would exist in almost all cases. If that's not in fact true here, such an SNG would be deceptive and unhelpful. Let's figure out that before proposing anything. [[User:Seraphimblade|Seraphimblade]] <small><sup>[[User talk:Seraphimblade|Talk to me]]</sup></small> 15:07, 8 July 2016 (UTC)

===Proposal 3===
I've noticed that the articles that meet these criteria seem to always have significant coverage in sources. Note that the dates are arbitrary cutoffs that nonetheless seem to reflect the existence of sourcing. Also note that this list assumes the current eSports afds will pass, otherwise it may have to become more restrictive:


{{talkquote|autocollapse="yes"|'''Individuals participating in electronic sports/professional video game playing are presumed notable if the following criteria are satisfied:'''

{{hidden begin|}}
====Teams<ref>refers organization pages, not sure about standalone articles about an individual squad like [[Fnatic (Dota 2)]]</ref>====
* ''[[League of Legends]]'':
** All auto qualifier league teams ([[EU/NA LCS]], [[LoL LPL|LPL]], [[LoL LCK|LCK]], [[LoL LMS|LMS]]) as of the 2016 season
** Wildcard region teams who participate in the World Championship after 2013

* ''[[Dota 2]]''
** Top four team at [[The International (Dota 2)|The International]]
** Teams invited to TI

* ''[[Counter-Strike]]''
** Legends seed teams at a CS:GO Major

====Players====
* ''[[League of Legends]]'':
** Players who have played in the LCS for more than four splits
** [[League of Legends World Championship]] MVPs
** LCS MVPs or Rookies MVPs

* ''[[Counter-Strike (series)]]''
** Players who win a ''CS:GO'' Major

* ''[[Dota 2]]''
** Winning The International

* ''[[Smash Bros.]]''
** Winners of [[EVO]], [[Genesis (tournament)|GENESIS]], or [[Apex tournament|Apex]] from 2012-2015

* ''[[Street Fighter]]''
** Top eight at [[Capcom Cup]] or [[EVO]] 2013-present

* ''[[StarCraft: Brood War]]''
** Winners of the [[Ongamenet Starleague]] or [[MBCGame StarCraft League]]<ref>this is a logical one, but it seems that six winners of the OSL currently don't have pages</ref>

* ''[[StarCraft II]]''
** Win WCS or GSL

====Competitions====
*''[[League of Legends]]''
** All [[List_of_League_of_Legends_leagues_and_tournaments#Tier_1|Tier 1 Professional]] leagues
** [[League of Legends Championship Series splits]] except Spring 2013<ref>the paper trail of secondary sources seems to run out after Summer 2013, the [[NA LCS Summer 2013]] was only added because it was discussed in ''[[Playboy]]''</ref>
**Autoqualifier leagues split articles (i.e. [[2016 League of Legends Champions Korea]]) after 2015

*''[[Dota 2]]''
**Dota 2 Majors + TI
**ESL One

*''[[Counter-Strike]]''
**CS:GO Majors
**$250,000+ prize pool tournaments

*''[[Hearthstone]]''
**World Championship

*''[[Call of Duty]]''
**[[Call of Duty Championship]]
**[[Call of Duty World League]]

*[[Fighting games]]
** [[EVO]]

*[[StarCraft: Brood War]]

}}
{{hidden end}}
====Notes====
{{reflist}}

====Discussion====
* I agree with what {{ping|Seraphimblade|p=}} just said: {{talkquote|i=y|Before adding any SNG criteria, we first should ensure that it really does mean that in a vast majority of cases, subjects covered by it would in fact meet the GNG. SNGs are not "alternate criteria" to the GNG, but instead are meant to highlight cases where sufficient coverage would exist in almost all cases. If that's not in fact true here, such an SNG would be deceptive and unhelpful. Let's figure out that before proposing anything.}} This is what you would need to show before this could even be considered. <span style="background:#F0F0FF; padding:3px 9px 4px">[[User talk:Czar|<span style='font:bold small-caps 1.2em Avenir;color:#B048B5'>czar</span>]]</span> 06:33, 12 July 2016 (UTC)
*Without any explanation, these all look rather...arbitrary. This is all far less clear or clean-cut than, for example, how in the music world, there's the argument that "[[WP:NSONGS|if a song charted, its likely to have received the significant coverage to meet the GNG]]. I'd ask how you determined some of these criteria (Why top 4/8/X and not other numbers? Why is $1 million a cutoff point?) but I also agree with Czar/Seraphimblade's notion above, and it may be better to address that first (and my question would probably take a lot of research/explanation, and may well be rendered moot by SB's concern.) [[User:Sergecross73|<span style="color:green">Sergecross73</span>]] [[User talk:Sergecross73|<span style="color:teal">msg me</span>]] 16:04, 12 July 2016 (UTC)
**The cutoffs are indeed arbitrary, but it's just what I've noticed tends to correlate best with articles that would probably meet GNG.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 03:24, 13 July 2016 (UTC)
**I created a list of all the ''[[League of Legends]]'' players who would meet the criterion for playing four or more LCS splits. which can be found [[User:Prisencolin/4lcssplits|here]] (sorry for lack of formatting). Look some of them up if you want to doublecheck.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 03:28, 13 July 2016 (UTC)
**I might lower the CS:GO tournament prize pool limit, but it just seems like the media has discussed $1,000,000 as a cutoff and it's more than the amount offered by [[ELeague]], which is larger than the prize pool offered by CS:GO Majors.--[[User:Prisencolin|Prisencolin]] ([[User talk:Prisencolin|talk]]) 03:31, 13 July 2016 (UTC)

=== Manchester City sign first esports player ===
[http://www.bbc.co.uk/news/technology-36734518 Here, for information purposes.] [[User:Only in death|Only in death does duty end]] ([[User talk:Only in death|talk]]) 11:25, 7 July 2016 (UTC)

== Should we remove Commons templates if the same link has been set up in Wikidata? ==

There don't seem to be specific guidelines about whether it is recommended to treat links to Commons the same way that other-language links are treated (and another editor has called me out for what I was doing). [[Wikipedia:Wikidata#Migration_of_interlanguage_links]] states that "In general, it is best to remove interwiki links in Wikipedia articles once they are associated with Wikidata." However, as the page name indicates, that recommendation is about interlanguage links only.
There are already a lot of Wikidata entries that connect EN Wikipedia to Commons. Question is, is that yet the new, proven method? Is it recommended to make those Wikidata entries and remove the templates that link to Commons when they exactly reproduce a link that is in Wikidata? [[User:Sminthopsis84|Sminthopsis84]] ([[User talk:Sminthopsis84|talk]]) 13:13, 3 July 2016 (UTC)
:I would say not to remove links to Commons categories or galleries as there is not always a 1:1 link between an article subject and those pages on Commons, and a box highlighting the presence of additional media about a subject with a direct link is a conceptually (to me at least) different thing to an indirect link via a page full of dry facts and metadata about the subject where the link to Commons is neither prominent nor consistently located (and I say this as a Wikidatan). Unless and until the Commons templates can be and are generated from Wikidata (with a many-many relationship) then imo there is still a need for the local manually added templates. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 21:50, 3 July 2016 (UTC)
::Thank you, I'm convinced. [[User:Sminthopsis84|Sminthopsis84]] ([[User talk:Sminthopsis84|talk]]) 13:24, 5 July 2016 (UTC)
:::What's more, a {{tl|commonscat}} or a {{tl|commonscat-inline}} placed in its normal spot is much more prominently located than a sidebar link; editors and other frequent readers are conditioned to expect a Commons box at bottom right, and its absence tends to indicate that there isn't a relevant Commons page, so treating a link to Commons like a link to Wikidata would be confusing. Moreover, Commons boxes/inline links should be treated like boxes/inline links for other projects; I doubt that we'll be sending Wikinews reports, Wikispecies documentation, etc. to the sidebar. [[User:Nyttend|Nyttend]] ([[User talk:Nyttend|talk]]) 13:43, 6 July 2016 (UTC)

== Notification of RFC for Korean MOS in regard to romanization ==

Should we use McCune-Reischauer or Revised for topics relating to pre-1945 Korea? Those inclined, [[Wikipedia talk:Manual of Style#RFC: Which romanization system should be used for pre-division Korean topics?|please contribute here]]. [[User:Hijiri88|Hijiri 88]] (<small>[[User talk:Hijiri88|聖]][[Special:Contributions/Hijiri88|やや]]</small>) 06:19, 6 July 2016 (UTC)

== Requesting comments on requested move: [[ESports]] ==

{{FYI|Pointer to discussion elsewhere.}}
The present name of the article (on a general topic, professional video-gaming competition) coincides with a commercial trademark (in that market sector).

Over the last year, there have been 6 or so requested moves and other renaming discussions at what is presently [[Talk:ESports]], most of them poorly attended, with mostly [[WP:ILIKEIT]] votes, mis-citations of policy where any was mentioned at all, and closure reasoning problems (while only one was an admin close), resulting in the name flipping around all over the place.

I've opened a multi-option, RfC-style requested move at:<br />
{{in5}}'''[[Talk:ESports#Broadly-announced and policy-grounded rename discussion]]'''<br />

It presents four potential names, all with some rationale outlines provided.

Input is sought from the community to help arrive at a long-term stable name for this article, based on actual policy and guideline wording, and on treatment in {{em|[[WP:RS|reliable]]}} and {{em|[[WP:INDY|independent]]}} sources (i.e. not blogs or "eSports" marketing). <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — [[User:SMcCandlish|'''SMcCandlish''' ☺]] [[User talk:SMcCandlish|☏]] [[Special:Contributions/SMcCandlish|¢]] ≽<sup>ʌ</sup>ⱷ҅<sub>ᴥ</sub>ⱷ<sup>ʌ</sup>≼ </span> 15:38, 6 July 2016 (UTC)

== Removal of "cannot edit own talk page" and "email disabled" from block settings ==
{{atop|Overwhelming consensus against implementing this proposal --[[User:NeilN|<b style="color:navy">Neil<span style="color:red">N</span></b>]] <sup>[[User talk:NeilN|<i style="color:blue">talk to me</i>]]</sup> 00:03, 13 July 2016 (UTC)}}
I don't feel that administrators should have the technical ability to remove a blocked user's ability to edit their talk page or email other users. If a user is blocked from editing, I believe that they should be allowed to file as many appeals as desired. If a user is blocked and thinks that the block doesn't relate to what they have done (the punishment doesn't fit the crime), they could [[WP:EVADE|evade the block]], be scared and afraid to communicate with administrators upon return, or, at the worst, [[WP:NLT|sue Wikipedia or Wikimedia]] because they feel as if they were deceived by "the free encyclopedia that anyone can edit". I've seen it happen on other websites not operated by WMF, and I don't want it to become a problem on Wikipedia.


==Discussion at [[:Wikipedia talk:Criteria for speedy deletion#RfC: Enacting T5 (unused template subpages)|Wikipedia talk:Criteria for speedy deletion §&nbsp;RfC: Enacting T5 (unused template subpages)]]==
I would be willing to make a couple of exceptions to this proposal:
[[File:Symbol watching blue lashes high contrast.svg|25px|link=|alt=]]&nbsp;You are invited to join the discussion at [[:Wikipedia talk:Criteria for speedy deletion#RfC: Enacting T5 (unused template subpages)|Wikipedia talk:Criteria for speedy deletion §&nbsp;RfC: Enacting T5 (unused template subpages)]]. <b>[[User:HouseBlaster|House]][[Special:Contributions/HouseBlaster|<span style="color:#7D066B;">Blaster</span>]]</b>&nbsp;([[User talk:HouseBlaster|talk]]&nbsp;•&nbsp;he/they) 03:01, 25 November 2024 (UTC)<!-- [[Template:Please see]] -->


== Information on cross-wiki article creation ==
*If a user has filed 5 appeals that have all been declined, talk page access can be removed for a ''short period of time'' (not the entire length of the block, unless it's only 24 hours)


The [[Harald Winter]] article was created by [[User:X3ntar|X3ntar]] as a port from the German Wikipedia article (found here: {{interlanguage link|Harald Winter|de}}). The English article consists primarily of poor English translation and promotional content, and when I was looking through the history of the article, all I saw originally were red-linked accounts created a short while before their edits to the article, leading me to begin researching to source a [[WP:SPI]] case. After almost an hour of looking into this, I don't think this is canvassing, meatpuppetry, or anything like that. More likely it's a case of German editors wanting to update the English version of the article. However, I couldn't find any policies or essays that gave advice on how to handle cross-wiki contributions or page creations. Is there a common consensus reached prior? [[User:Sirocco745|Sirocco745]] ([[User talk:Sirocco745|talk]]) 04:59, 25 November 2024 (UTC)
*If a user has been sending spam or otherwise inappropriate emails, a change could be made to [[Special:Block|the blocking form]] that would enable the option of "Prevent this user from sending email to X user(s) while blocked", which a field to enter one or more usernames.


:This doesn't happen very often, so I don't think there are any advice pages. In general, it would be a lovely thing if people who created an article in one language could then do a semi-decent translation into another language.
[[WP:SOCK|Sockpuppetry]] is becoming a large problem on Wikipedia, and in my opinion, a lot of the time, a user's evasion is triggered by the subtraction of their ability to appeal, and they want revenge or just want to be able to edit again. If we allow users to appeal freely, noted the exceptions above, I think block evasion frequency numbers will go way down. [[Special:Contributions/73.114.22.215|73.114.22.215]] ([[User talk:73.114.22.215|talk]]) 13:17, 7 July 2016 (UTC)
:I'm aware of two multi-editor cases of that. The first is that when a WMF staffer mentioned writing her first article (in English), a handful of staffers who are not native English speakers (but who are experienced Wikipedians) translated that into their native language as a way of encouraging her to keep editing as a volunteer. This probably happened about a decade ago, and it was very sweet.
:Things are fine as is, our policies defend us against any such ridiculous lawsuits. If there are legal issues you can always contact the foundation through regular mail. These blocks aren't given to just anyone, they are deserved, and I've never seen anyone get one that wasn't. [[User:CFCF|<span style="color:#014225;font-family: Copperplate Gothic Bold;text-shadow:0px -1px 0px #014225;">Carl Fredrik</span>]]<span style="font-size: .90em;">[[User talk:CFCF| 💌]] [[Special:EmailUser/CFCF|📧]]</span> 13:25, 7 July 2016 (UTC)
:The other was a sustained self-promotion effort by a handful of artists, including hoax photos. See [[d:Q131244]] for what's left of their efforts. We [[Wikipedia:Articles for deletion/IMMAGINE&POESIA|deleted the English article]]. The reason this sticks in my mind is that they repeatedly faked photos – see [[c:Commons:Deletion requests/File:Ferlinghetti meets Immagine&Poesia representatives.jpg]] for one example – of various people and the poet [[Lawrence Ferlinghetti]]. Every few months, one of the same two photos of Ferlinghetti in a public place would appear, with a different person photoshopped into the scene next to him, and it would get added to an article with a caption saying something like "Ferlinghetti met with so-and-so" (a different name each time). The result is that [https://en.wikipedia.org/enwiki/w/index.php?search=%22Immagine+%26+Poesia%22&title=Special%3ASearch&profile=advanced&fulltext=1&ns0=1&searchToken=9dlry6r97lnb1yodkuttowsju every remaining mention of that group] seems suspicious to me. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 02:09, 27 November 2024 (UTC)
::{{ping|CFCF}} I'm not just talking about the legal issues - that's only one concern. All of my other reasons also have purpose. Also, I strongly disagree with the statement that blocks are "deserved". Given Wikipedia's slogan, a lot of users won't think that they even exist, and then get angry when one is implemented against them. [[Special:Contributions/73.114.22.215|73.114.22.215]] ([[User talk:73.114.22.215|talk]]) 13:30, 7 July 2016 (UTC)
::Okay, thanks for responding. I'm going to think about what can be done to assist editors in future scenarios and draft some thoughts for an essay in my sandbox later. I don't believe that creating a policy proposal is worth it right now, since as you've observed, cross-wiki article copy-pasting isn't a major concern due to its relative uncommonness. I'm considering writing up an essay on the subject instead, maybe also creating a template later on to go at the top of an article that says something along the lines of "This article was cross-posted from the "XYZ Wikipedia" and is currently undergoing translation, discussion, and improvement." [[User:Sirocco745|Sirocco745]] ([[User talk:Sirocco745|talk]]) 02:56, 27 November 2024 (UTC)
* First off, c'mon: not one blocked user in ten ''doesn't'' think that he's been blocked for No Good Reason (save, of course, that the admins are Out To Get Him). We have a limited number of admins, and admin time shouldn't be sucked up with endless specious appeal after specious appeal. Beyond, that ... seriously? If someone genuinely takes it in his head to sue the Foundation because he's enraged a private website has the right to enforce codes of conduct as the agreed-upon prerequisite for participation, and he finds an attorney addle-pated enough to take such a specious case (a key element in US tort law being the requirement to ''prove damages'') ... well, I'd like to be a fly on the wall when the judge reads the complaint.<p>In any event, my longstanding opinion is that every touchy editor washing his hands of Wikipedia out of rage when he discovers that the rules apply to him too is a material gain for the encyclopedia. [[User talk:Ravenswing|'''<span style="background:#7F00FF;color:#00FFFF"> '' Ravenswing '' </span>''']] 15:39, 7 July 2016 (UTC)
*Such a lawsuit would be laughed out of court. If that were a real legal concern, the WMF would intervene, and certainly would not have developed those features. Editors with email and talk page access disabled can still appeal via [[WP:UTRS|UTRS]], so there's always an avenue open. Unfortunately, we do have blocked editors who use unblock requests and email as a way to make abusive unblock requests, to abuse other editors, or just to waste people's time declining silly appeals that stand no chance of success. At some point, it comes time to say "Enough" there. Talk page and email access is not revoked by default when an editor is blocked, that happens only when it's misused or abused. [[User:Seraphimblade|Seraphimblade]] <small><sup>[[User talk:Seraphimblade|Talk to me]]</sup></small> 16:39, 7 July 2016 (UTC)
::{{ec}} Well said {{u|Ravenswing}} and {{u|Seraphimblade}}. Talk page access is not removed on a whim. It comes after continual disruption. This thread should probably be "snow" closed because the policy is not going to be changed. [[User:MarnetteD|MarnetteD]]&#124;[[User talk:MarnetteD|Talk]] 16:45, 7 July 2016 (UTC)
:I think this would be a very cumbersome slogan: ''Wikipedia, the encyclopedia anyone can edit if they are prepared to abide by its standards of conduct.'' I can't sue McDonald's because my Big Mac didn't look like the picture. &#8213;[[User:Mandruss|<span style="color:#775C57;">'''''Mandruss'''''</span>]]&nbsp;[[User talk:Mandruss|<span style="color:#AAA;">&#9742;</span>]] 17:40, 7 July 2016 (UTC)
*I would prefer if Admins where a bit more reluctant to revoke talk page access, as it does remove the best and most transparent way to appeal the block and have someone else look at the Admin's actions. That said, the vast majority of talk page access removals are very well justified, and it is an important tool to keep available to admins. We would should try to leave the question up to another admin if it was originally our own block in all but the most unambiguous cases, but there are plenty of those too. [[User:Monty845|<span style="color:Green;">Monty</span>]][[User talk:Monty845|<small><sub><span style="color:#A3BFBF;">845</span></sub></small>]] 22:34, 7 July 2016 (UTC)


== Topics on Jehova's Witnesses - article spamming issues ==
*There are (unfortunately) some admins who seem to like talk page and email access removal too much. Some of these admins have revoked talk page access after one appeal that is not violating either [[WP:CIVIL]] or [[WP:NICETRY]] (these actions have been [[Special:Log/block|clearly logged]]). Revoking email access isn't as much of a concern, although technically blocks are only supossed to prevent users from ''editing'' Wikipedia. Emails aren't actual edits, so prehaps they shouldn't even be part of blocking. [[Special:Contributions/73.114.33.224|73.114.33.224]] ([[User talk:73.114.33.224|talk]]) 19:33, 11 July 2016 (UTC)


Polish Wikipedia is experiencing and uptick in Jehova's Witnesses topics article spamming, surrepticious edits pushing JW terminology etc. One of current problems is the spamming of separate articles for every "convention", which is an annual (I think) event with a theme and about 100k visitors. We are discussing their notability right now, and I was wondering whether English Wikipedia already discussed and cleaned this, which would be helpful? If you remember any topic discussing notability or monitoring of Jehova's Witnesses related topics, and possibly deleted articles. (I'm not sure if there is any sensible search method of deleted articles archive/log? Can I use any wildcards in [[Special:Log/delete]]? It doesn't seem to work.) [[User:Tupungato|Tupungato]] ([[User talk:Tupungato|talk]]) 12:04, 25 November 2024 (UTC)
*'''Oppose''' removal of these sanctions. They are not employed lightly, and I've never seen them applied in error or without enormous good cause. Perhaps if the IPs on this thread (both of whom have never edited before and are from the same place in Massachusetts) could tell us who they really are, that would shed some light here. [[User:Softlavender|Softlavender]] ([[User talk:Softlavender|talk]]) 20:34, 11 July 2016 (UTC)


:@[[User:Tupungato|Tupungato]], we used to have a list of conventions, but it was deleted 16 years ago at [[Wikipedia:Articles for deletion/List of Jehovah's Witnesses conventions]]. I'm not sure we would make the same decision today. Information about some conventions is in [[History of Jehovah's Witnesses]]. [[User:WhatamIdoing|WhatamIdoing]] ([[User talk:WhatamIdoing|talk]]) 02:22, 27 November 2024 (UTC)
*'''Oppose''' - if these block abilities would expose the Foundation to legal issues, they would have either not put them into the software, or given us admins '''explicit''' restrictions on using them. Most sockpuppetry is done by users who are here to abuse Wikipedia, not trying to bypass a bad block for good edits. And we don't punish - blocks are preventative, not punitive. [[User:Od Mishehu|עוד&nbsp;מישהו]] [[User talk:Od Mishehu|Od&nbsp;Mishehu]]


== Titles of articles about false theories or accusations ==
*'''Oppose''' I agree with Softlavender that these are not used lightly. Having received attack emails in the past the revocation prevents harassment which is a good thing. [[User:MarnetteD|MarnetteD]]&#124;[[User talk:MarnetteD|Talk]] 21:37, 11 July 2016 (UTC)


This seems to be a little bit inconsistent. Some have "conspiracy theory" in the title, clearly stating they are false (I don't think there's any possible way any even remotely possible theory or accusation would have the words "conspiracy theory" in it). Some go even further outright stating "myth" (not unwarranted if it is clearly false).
*'''Oppose''' - I've seen ''many, many'' instances of talk page editing privilege abuse by [[WP:LTA|LTA]]'s, openly disruptive [[WP:SOCK|sock puppets]], and IPs that '''clearly''' and '''grossly''' violate Wikipedia's policies after the user has been [[WP:BLOCK|blocked]]. These options are disabled by default when a block is imposed, and are enabled via a modification of block settings and based off an admin's judgment call and for reasons that prevent further disruption and abuse when it occurs. Removing the technical ability for an administrator to revoke these privileges from blocked users would result in disruption and abuse that couldn't be easily controlled; it would add unnecessary "red tape" to something that really shouldn't be. If the guidelines on the use of these settings to revoke talk page or email access need clarification, then they should be clarified. Removing the ability for administrators to use the options ''at all'' seems crazy to me. If an administrator cannot do it, then who could? Who would? What, are we going to create an AIV2 page to report talk page and email abuse to... whoever it is that is allowed to do it now? I think you see where I'm going with this... :-) [[User:Oshwah|<b><span style="color:#C00000">~Oshwah~</span></b>]]<sup><small><b>[[User_talk:Oshwah|<span style="color:blue">(talk)</span>]] [[Special:Contributions/Oshwah|<span style="color:green">(contribs)</span>]]</b></small></sup> 23:56, 12 July 2016 (UTC)
{{abot}}


* [[LGBT chemicals conspiracy theory]]
==Requesting Policy on 'Star Databases'==
* [[LGBTQ grooming conspiracy theory]]
It is possible for people to 'name' any star by making a payment to one of a plethora of databases. Whether these databases serve a valuable social function or they are completely scurrilous is irrelevant - these names have no wider validity and the star may already have an historic name. I found an example on the entry for [[Messier 29]] stating one of the stars had been named with a silly name on one of these databases. I fear this could become a trend - perhaps fed by the fact that it can be used to promote the database used by including the name or even a link. I can imagine the databases encouraging people to add their star to Wikipedia.
* [[Moon landing conspiracy theories]]
A clear policy statement would help give people the confidence to rapidly delete such entries wherever they crop up. [[User:Stub Mandrel|Stub Mandrel]] ([[User talk:Stub Mandrel|talk]]) 16:32, 7 July 2016 (UTC)
* [[International Jewish conspiracy]]
:I don't think we need a specific policy. We already have policies about [[WP:WEIGHT|undue weight]], [[WP:SPAM|spamming]], and [[WP:ELNO|inappropriate external links]]. Putting names from a "name your own" database would normally be inappropriate undue weight, unless such a name has received significant coverage in reliable sources for some reason. I suspect for the vast majority of them, that is not the case. [[User:Seraphimblade|Seraphimblade]] <small><sup>[[User talk:Seraphimblade|Talk to me]]</sup></small> 16:42, 7 July 2016 (UTC)
* [[999 phone charging myth]]
* [[John F. Kennedy assassination conspiracy theories]]


However: These do not, despite the article clearly stating the theory or accusation is incorrect:


* [[Fan death]]
== Moderator proposal ==
* [[Allegations of genocide in Donbas]] (Note: [[Allegations of genocide of Ukrainians in the Russo-Ukrainian War]] has the same title format, despite one referring to actual actions, and one that serves only as a [[casus belli]] with no basis at all in actual true events)
*[[Wikipedia:Moderators/Proposal]]
* [[Vaccines and autism]] (Note: the fraudulent study that begun this conspiracy is titled [[Lancet MMR autism fraud|''Lancet'' MMR autism fraud]], not using the word "study" or something not indicating it was a fraud in the title, which it used to, I don't know when it was changed)
A [[Wikipedia:Moderators/Proposal|Request for Comment on a proposal]] to create a new [[:Special:ListGroupRights|user group]] with an abbreviated set of [[Wikipedia:Administrators|administrator]] user-rights, as an option for editors to request instead of requesting the entire '''sysop''' user-right package. I welcome everyone's thoughts on this. - <b>[[User:Jc37|jc37]]</b> 21:13, 8 July 2016 (UTC)
* [[Abortion–breast cancer hypothesis]]
* [[Turbo cancer]]


Is there some kind of policy regarding whether to include "conspiracy theory", "myth", etc in article titles about false theories or accusations? &lt;/[[User:MarkiPoli|MarkiPoli]]&gt; &lt;[[User_talk:MarkiPoli|talk]] /&gt;&lt;[[Special:Contributions/MarkiPoli|cont]] /&gt; 12:37, 25 November 2024 (UTC)
== [[Wikipedia:Proposed draftspace deletion]] ==
:Generally, all articles should be titled neutrally and in line with their common name, where they have one. If the significant majority of reliable sources do not describe something as a conspiracy theory or myth (even if they are false) then our article titles should not. In most cases where "myth" and "conspiracy" appear in the article titles they are descriptive as there is no single common name for the topic(s) covered. Consistency is part of the [[Wikipedia:Article titles|article titles policy]] but it is only one criterion and generally not regarded as the most important. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 12:50, 25 November 2024 (UTC)
{{rfc|policy|prop|rfcid=B0659FB}}
:I see two situations here: one where the article title wouldn’t work without the addition of “conspiracy theory” (i.e “International Jewish” is a non sequitur fragment); and one where the title ''would'' work (“999 phone charging” makes sense on its own). We don’t need to state something is a myth in the title if the article explains it’s a myth; there’s enough RFK Jr. types whining at [[Talk:Turbo cancer]] to prove that much. [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 13:10, 25 November 2024 (UTC)
Following the closure at [[Wikipedia:Village_pump_(policy)/Archive_128#RfC:_Proposed_draftspace_deletion]], and no review, I've created [[Wikipedia:Proposed draftspace deletion]] as a proposed process. Given that there is consensus that the policy should be adopted, I'd like to see if we could move it to a policy at this point. Some people express some concerns about the time limits listed so I'll add that. Please vote in the subheaders about (a) the length of inactivity; (b) the length of review; and finally (c) whether to adopt as policy. I figured I'd see where we are before starting on the templates and categories. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 01:56, 12 July 2016 (UTC)
:Agree with Thryduulf. We should use titles that are considered the common name for the topic and that fall with the article title policy, and then after that any necessarily disambiguation steps to differentiate from other topics. And as long as the lede sentence or lede itself (as in the case of Vaccines and autism) is clear what is legitimate science or fact and what is a conspiracy theory, pseudoscience, or disproven, then its not as important for the title to reflect that as well. [[User:Masem|M<span style="font-variant: small-caps">asem</span>]] ([[User Talk:Masem|t]]) 13:31, 25 November 2024 (UTC)
::Indeed there are some editors on the sceptic side who seem to feel that it is necessary to explicitly and stridently describe something as pseudoscientific at every possible opportunity. We don't need to bash our readers over the head with it, indeed doing so can be contrary to NPOV (e.g. when reliable sources disagree and/or take a more nuanced approach). [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 14:39, 25 November 2024 (UTC)
:::I think that what leads to adding "conspiracy theory", "myth", etc. generally boils down to whether the topic is one that perennially annoys the regular page watchers at [[WP:FRINGE/N]]. So, for instance, [[Fan Death]] isn't caused "the Fan Death Myth" largely because there's not a large proportion of editors rushing to the Fan Death article to say "this is a real serious problem guys". [[User:Simonm223|Simonm223]] ([[User talk:Simonm223|talk]]) 14:48, 25 November 2024 (UTC)
::::I think that’s a genuine problem that we should probably address— some anti-fringe editors are among the most aggressive contributors I’ve encountered, probably because too many “skeptics” are also culture warriors who need to [[Wikipedia:GREATWRONGS|right great wrongs]] by doing everything short of calling something “stupid” and its adherents “idiots”, which of course actually ''damages'' our credibility. [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 15:09, 25 November 2024 (UTC)
:::::I'm all for preventing the spread of quack medicine and Ufology silliness on the encyclopedia but, generally, the fringe noticeboard is poorly equipped to address assessments of what research is fringe outside of medicine, history and archaeology. I think some of these anomalous titling conventions kind of point toward that specificity of scope. [[User:Simonm223|Simonm223]] ([[User talk:Simonm223|talk]]) 15:57, 25 November 2024 (UTC)
::::::FRINGE should really only apply to topics where objective research have thoroughly debunked the notion, and not to areas where questions remain open or where debunking may never be possible at which point Undue becomes the answer. For example, whike most science rejects the COVID lab theory, it's still near difficult to devisicely conclude that the lab theory is not posdible, so we should avoid calling it fringe but clearly note the weight of experts that have dismissed it.<span id="Masem:1732553641319:WikipediaFTTCLNVillage_pump_(policy)" class="FTTCmt"> —&nbsp;[[User:Masem|M<span style="font-variant: small-caps">asem</span>]] ([[User Talk:Masem|t]]) 16:54, 25 November 2024 (UTC)</span>
:::::::Hmm, there is a difference between "theories that are scientific, plausible and supported only an extreme minority of sources but have not been/are unlikely to be conclusively disproven", "theories that are scientific, were previously mainstream but no longer are, but are still supported by an extreme minority of sources as they have not been conclusively disproven". "theories that are scientific but implausible to the extent that mainstream sources do not feel the need to conclusively disprove them.", "theories which are scientific and have been conclusively disproven, but still have some supporters", "theories which are pseudoscientific" and "theories which are neither scientific nor pseudoscientific". I've seen FRINGE used to describe all of these cases, which is unhelpful. [[User:Thryduulf|Thryduulf]] ([[User talk:Thryduulf|talk]]) 17:08, 25 November 2024 (UTC)
:I think part of the issue is: there is a Kennedy assassination, but this article is about the conspiracy theories; there is grooming but this article is about about a conspiracy theory; there is phone charging but this article is about a myth; there are international Jewish organizations but this article is not about that, etc. So, the article title is limited to (and limits) the scope of the article. And other times, 'myth' or 'conspiracy theor[ies]' is in a common name for the subject. Also note, you really can't tell why an article is called 'this' instead of 'that', unless it has actually been discussed. Article title decisions are made in a decentralized manner, and may never be revisited. [[User:Alanscottwalker|Alanscottwalker]] ([[User talk:Alanscottwalker|talk]]) 12:46, 26 November 2024 (UTC)
::Alan raises a good point… when there actually are theories that postulate a conspiracy, then it is not POV to call them “conspiracy theories”. That is a neutral descriptive title, not a pejorative one. [[User:Blueboar|Blueboar]] ([[User talk:Blueboar|talk]]) 13:32, 26 November 2024 (UTC)
:::I am not sure if that's true, that those that subscribe to a theory that is based on conspiracy would necessary call it a conspiracy theory themselves. Eg those that claim there is a [[deep state]] aren't usually calling that a conspiracy theory, but a theory about conspiracies, if that makes sense. [[User:Masem|M<span style="font-variant: small-caps">asem</span>]] ([[User Talk:Masem|t]]) 15:46, 26 November 2024 (UTC)
::::And according to that article "deep state" is a pejorative. Regardless, just because you have [[Illuminati]] does not mean you can't have [[New World Order conspiracy theory]]. The ''Illuminati'' of Bavaria, can well be a different matter than the ''Illuminati'' of the 1960s novel.[https://www.bbc.com/future/article/20170809-the-accidental-invention-of-the-illuminati-conspiracy] [[User:Alanscottwalker|Alanscottwalker]] ([[User talk:Alanscottwalker|talk]]) 16:31, 26 November 2024 (UTC)
*I would like to add that, while I would ''like'' standardized article titles and would ''also like'' if some anti-FRINGE editors dropped the “angry atheist” stereotype, I think this is an exceedingly trivial issue that does not ''need'' to be “solved”. [[User:Dronebogus|Dronebogus]] ([[User talk:Dronebogus|talk]]) 16:03, 27 November 2024 (UTC)


== New users required to cite sources when creating an article ==
*My understanding is that the consensus is that there is no deadlines for pages both in the main namespace as well as the draft namespace; see [[https://en.wikipedia.org/wiki/Wikipedia_talk:Drafts#RfC:_is_there_a_deadline_for_a_draft.3F]] This proposal is thus against the consensus (and cannot be implemented). <strike>Please try to find new toys to play with.</strike> -- [[User:TakuyaMurata|Taku]] ([[User talk:TakuyaMurata|talk]]) 11:49, 12 July 2016 (UTC)
*:The result of the "Proposed draftspace deletion" RfC means that a PROD-like process can be initiated to remove unwanted drafts without requiring a full Miscellany for Discussion, thus speeding up maintenance. However, since (per consensus) non-AfC Drafts are not subject to deadlines, the Prod should state an explicit reason for their removal - being stale would be not enough. [[User:Diego Moya|Diego]] ([[User talk:Diego Moya|talk]]) 12:16, 12 July 2016 (UTC)
*::Thank you for the clarification. I'm fine with streamlining the process. -- [[User:TakuyaMurata|Taku]] ([[User talk:TakuyaMurata|talk]]) 12:29, 12 July 2016 (UTC)
*:::{{u|TakuyaMurata}}, they don't seem really unrelated, it looks more like an attempt to overrule the previous consensus regarding the lack of deadlines by placing a streamlined process with more reviews and checks. Well, that doesn't work for me. I'm OK with having the streamlined process for maintenance, but not with having it triggered just by stalled time. PRODs are an acceptable way to remove ''bad'' content, but an explicit reason why the content is bad must be provided, and "nobody touched it recently" is not a valid one. [[User:Diego Moya|Diego]] ([[User talk:Diego Moya|talk]]) 12:39, 12 July 2016 (UTC)
*:::: It's not. [[Wikipedia:User_pages/RfC_for_stale_drafts_policy_restructuring]] was more detailed in that drafts should not be kept indefinitely. If you think there should be an additional requirement that the person explicitly states that they support deletion on [[WP:NOTHOST]] grounds, that seems duplicative to me but fine. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 17:09, 12 July 2016 (UTC)
*::::: Don't you mean [https://en.wikipedia.org/enwiki/w/index.php?oldid=721038836 the RfC] that was used for including in [[WP:STALEDRAFT]] the text "In a RfC held in March 2016, the community held the view that drafts have no expiration date and thus, cannot and should not be deleted on the grounds of their age alone."? Removing drafts in order to "not keeping them indefinitely" is only in cases where "notability is unlikely to be achieved", which is a reason different to "having been unedited for a time", which is my point. [[User:Diego Moya|Diego]] ([[User talk:Diego Moya|talk]]) 17:22, 12 July 2016 (UTC)
*::::::Oh, and the closing statement of the RfC that you linked includes this gem: "Unless a userspace draft is unacceptable for Wikipedia for GNG-unrelated reasons (copyright violations, self-promotion, and so on), it does not have an expiration date and does not have to comply with WP:GNG. No-hope drafts should not stick around indefinitely, but drafts with some potential should be allowed to stay." To me, this seems fairly incompatible with wanting to delete a draft by PRODing it for being stale without providing a further reason. [[User:Diego Moya|Diego]] ([[User talk:Diego Moya|talk]]) 17:30, 12 July 2016 (UTC)
*::::::: I'll agree with you on that. The page has been changed to allow for a separate rationale. It's basically an alternative to MFD limited to a subset of draftspace pages with very specific criteria. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 19:26, 12 July 2016 (UTC)


[[:Meta:Community_Wishlist_Survey_2023/New_contributors/Reference_requirement_for_new_article_creation|This wishlist item]] proposes a hard edit filter which would change citation policy for new users. We've repeatedly discussed requiring sources, and the consensus has been not to require them; per current policy, articles must be on notable topics and statements must be citable, but neither need be cited.
=== Length of inactivity of draft ===
The current proposal is that the draft must be inactive for at least six months. Any draft submitted to AFC would be subject to G13 deletion under this criteria. A rough estimate says that we are talking about [[User:MusikBot/StaleDrafts/Report|approximately 4400 pages]] just for a rough number. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 01:56, 12 July 2016 (UTC)


I know changes that affect new editors typically don't ignite as much interest as those that affect established editors, but they are in some ways ''more'' important; anything that affects our retention rate will eventually substantially affect the number of active editors, and the nature of their editing.
==== Support six month inactivity requirement ====
* '''Support''' as proposer. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 01:56, 12 July 2016 (UTC)
* Thinking "support", but with some expansion that requires six months inactivity not just by the original author, but also by any other editors who opt-in as supporting the draft. This could be taken to include all substantial editors, but that might get complicated due format-fixers, and copy-vio removers, etc, and I think it need be bot-process-able. NB. This would only apply to a small fraction of abandoned drafts. --[[User:SmokeyJoe|SmokeyJoe]] ([[User talk:SmokeyJoe|talk]]) 02:10, 13 July 2016 (UTC)


More broadly, it might be good to set limits on policy changes done through a wishlist survey on another wiki; big changes need broader discussion. [[User:HLHJ|HLHJ]] ([[User talk:HLHJ|talk]]) 01:05, 27 November 2024 (UTC)
==== Oppose six month inactivity requirement ====
If you oppose, please state what you suggest instead (one year, two years, longer). -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 01:56, 12 July 2016 (UTC)
:I strongly oppose implementing this on en-wiki. This is not the sort of change that the broader community should be allowed to dictate to local communities. [[User:Voorts|voorts]] ([[User talk:Voorts|talk]]/[[Special:Contributions/Voorts|contributions]]) 01:22, 27 November 2024 (UTC)
:It's just a wish. Anyone can male one. We don't know whether it will ever be implemented (community wishlists don't exactly have a good track record), never mind turned on on enwiki. &ndash;&#8239;[[User:Joe Roe (mobile)|Joe]]&nbsp;<small>([[User talk:Joe Roe (mobile)|talk]])</small> 05:52, 27 November 2024 (UTC)
*'''Oppose''': there is no deadline for draft content if it doesn't contradict any content policy. The people supporting removal based on timelines have never provided a good reason why such deletion would be an improvement to the project over proposed alternatives like tagging and/or blanking stale drafts. [[User:Diego Moya|Diego]] ([[User talk:Diego Moya|talk]]) 12:34, 12 July 2016 (UTC)
:As Joe says, a wishlist item is a long way from becoming something that works. We don’t have need for limits on changes; it is very rare for any changes to be pushed on en.wiki. Those that are are large-scale changes that affect all wikis (think Vector2022 or the upcoming IP masking), and the community here is usually very aware of these ahead of time. If wishlist items turn into tools the wiki can use, they tend to require local activation, as different projects have different needs. (En.wiki for example already has [[WP:NPP]], which will see any new pages, which may include pages that aren’t meant to have sources, like disambiguation pages.) [[User:Chipmunkdavis|CMD]] ([[User talk:Chipmunkdavis|talk]]) 08:17, 27 November 2024 (UTC)
** The RFC was closed with support for this proposal. No one disputed the closure from what I can tell. Do we have to repeatedly obtain a consensus in support with the same people just opposing it repeatedly or will you respect the [[WP:CONSENSUS]] that you ignoring the reasons provided as "not good" is not productive? I also reverted your [https://en.wikipedia.org/enwiki/w/index.php?title=Wikipedia:Proposed_draftspace_deletion&diff=prev&oldid=729496480 requirement to have an additional concern parameter] as there was no consensus for ''another'' requirement beyond what was proposed before. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 16:07, 12 July 2016 (UTC)
::The WMF Community wishlists in the past have actually had some impressive successes, particularly in 2018 for NPP's [[WP:Page Curation|Page Curation]] extension improvements. It is not all that rare for any changes to be pushed on en.wiki; two slightly earlier community driven major policies largely contributed - at the time - to reducing the flow of sewage in the new page feed: the 2016 [[Wikipedia:New pages patrol/Reviewers|NPP user right]], and after a 7 year battle with the WMF, the 2018 [[Wikipedia:Autoconfirmed article creation trial/Request for comment on permanent implementation|ACPERM]]. However, the number of new registrations has since grown again by users whose first intention above all else is to create a new article by hook or crook with little or no regard for notability, relevance, UPE, and spam policies. NPP has lost many of its prolific, skilled patrollers and coordinators either through burn-out and/or the constant whining either from users whose inappropriate articles have been consigned to the queues for the various trash cans or draft space, or have been driven away for good by other (non NPP) back office regulars' complaints, for the sake of complaining, over a couple of misplaced CSDs or AfDs out of thousands.
*::The RFC was closed with support to implement a lightweight process to solve the problems of 1a) being difficult to find pages in draftspace, 1b) archiving pages that don't help in writing an encyclopedia, 1c) having a backlog and MfD and 1d) hosting harmful . There were nothing in that RfC supporting the deletion of drafts that contain content that should be [[WP:PRESERVE]]d (in fact the very closing rationale acknowledges at 2a) that pages that are not harmful do not need to be removed).
*::There's consensus that you *can* establish a procedure for cleanup that removes the "not good" drafts, but you don't have consensus for overruling the previous long-standing position that useful drafts should be kept unless there's a reason to remove them; certainly not from the result of that RfC.
*::As has been pointed out numerous times, there are remedies for 1a) and 1c) that don't require deleting the good drafts - such as classifying the reviewed drafts and blanking unusable but non-harmful content instead of deleting it. Putting those remedies in place as part of this policy would be a net positive. [[User:Diego Moya|Diego]] ([[User talk:Diego Moya|talk]]) 16:34, 12 July 2016 (UTC)
*::: There's a proposal for sorting at [[Wikipedia_talk:Drafts#General_discussion]]. However, I don't really understand whether the end goal for the "no potential"/"non-starter" drafts or whatever they are is if the proposal is to mass list those at MFD or something in waves. I don't know why a 100 nomination of say two-year-old non-starter drafts is a better system than just proposing them for deletion as we see them. My other disapproval is that I don't believe that we should like there ''is'' an inherent draft sorting system here. There isn't one. It's only by project in mainspace and/or by AFC by choice. That's why I can live with doing it with [[Wikipedia:WikiProject Abandoned Drafts]] but all that sorting theory just seems to be debates about how things ''could'' be sorted with no progress coming. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 19:24, 12 July 2016 (UTC)
* '''Oppose six months, support one year'''. Six months is too short (e.g. I'm thinking of some actor BLPs – esp. child actor BLPs – I work on where you want to wait a year to see what develops in the actor's career). A year sounds about right. --[[User:IJBall|IJBall]] <small>([[Special:Contributions/IJBall|contribs]] • [[User talk:IJBall|talk]])</small> 20:56, 12 July 2016 (UTC)


::The [[Wikipedia_talk:New_pages_patrol/Reviewers#NPP_backlog|NPP backlog sawtooth profile]] looks menacing - it should be a regular low-value straight line. It is well known common knowledge that NPP is hopelessly overburdened and can no longer sensibly cope with even the minimum suggested criteria for patrolling new pages. The best way to ensure that the WMF's flagship project - the one that draws all the donations - becomes an untrustworthy resource full of useless and corrupt articles, is to sit back and do nothing and let WP become a mire of misinformation and spam. Wikipedia has already become the buck of media satire with "If you believe Wikipedia, you'll believe anything". The quest is therefore for ''any'' measures that will tighten up the article quality '''at the source''' of creation.
=== Length of review ===
The current proposal is that the draft must be sitting in the category for at least 30 days (one month can vary). In contrast, the current MFD method has a one week review process. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 01:56, 12 July 2016 (UTC)


::Although they are aware of them, as usual the WMF Growth Team has played down and resisted addressing these issues in favour of pursuing other, and expensive initiatives of their own design which in the NPP realm remain ineffective. It's the responsibility of the WMF to ensure new users are aware of the rules at the '''point of registration'''.
==== Support one month review ====
* '''Support''' as proposer. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 01:56, 12 July 2016 (UTC)
* '''Support''' a lightweight process as long as "being stale" is never considered a reason on itself for deleting a draft, and a different reason is required such as [[WP:NOTHOST]] or [[WP:BLP]]. Per [[WP:PRESERVE]], those drafts containing verifiable facts and reliable sources that could be reused at any article in main space should never be deleted through this process. [[User:Diego Moya|Diego]] ([[User talk:Diego Moya|talk]]) 12:22, 12 July 2016 (UTC)
** <s>[[WP:NOTHOST]] would apply to most every page, would it not? Does it actually need to be stated in each proposed deletion? It seems unnecessary. I'd support additional language such as "no plausible chance of any use" or something more but we have never managed to get any solid criteria on when a draft is appropriate to be kept versus deleting it. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 16:10, 12 July 2016 (UTC)</s>
*:: [[WP:NOTHOST]] only applies to pages which do not contain useful content, so hardly "most every page"; every former article that has been moved from mainspace as a result of an AfD decision, or draft page containing references to reliable sources (i.e. content useful for writing the encyclopedia) would not fall under [[WP:NOTHOST]].
*::{{green|we have never managed to get any solid criteria on when a draft is appropriate to be kept versus deleting it}} That is the reason why a process that can remove ''any stalled draft, without even providing a reason for that removal and without reaching a consensus from multiple editors'' is madness and should not happen as is. [[User:Diego Moya|Diego]] ([[User talk:Diego Moya|talk]]) 16:40, 12 July 2016 (UTC)
*::: I struck it. You have a good point. I restored the parameter as well to the template as well as the policy language. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 19:15, 12 July 2016 (UTC)


::The NPP team has handed solutions to the WMF on a plate, which at the same time will not only reduce the tide of rubbish, but most importantly, encourage the good faith new users to offer articles that have a fair chance of being published. All this project needs is to be written up in MediaWiki source code, but of course short of a mutiny by the community, the WMF will not entertain any ideas that they did not think of themselves and can collect the accolades for.
==== Oppose one month review ====
::The '' "anyone can edit" '' principle is not a get out of jail free card; it should be quoted in its full context: 'Anyone can edit as long as they play by the rules'. For once and for all, just make those basic rules clear for bona fide new registrants, and help them comply. [[User:Kudpung|Kudpung กุดผึ้ง]] ([[User talk:Kudpung|talk]]) 03:53, 28 November 2024 (UTC)
If you oppose, please state what you suggest instead (one week, two weeks, two months, six months, longer). -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 01:56, 12 July 2016 (UTC)
*'''Oppose''' Rule creep. And no "suggestion" that a "suggestion" is required as it makes no sense. Points to those who parse that correctly. [[User:Collect|Collect]] ([[User talk:Collect|talk]]) 13:01, 12 July 2016 (UTC)
* Oppose. No reason has been provided for any deletions at all. G13 should be banned as well. [[User:Wikijuniorwarrior|Wikijuniorwarrior]] ([[User talk:Wikijuniorwarrior|talk]]) 20:04, 12 July 2016 (UTC)


== Propose to create page of block discussion in noticeboards ==
=== Adoption as a policy ===
Just want to check if there's support for adoption as is. Doubtful but a first shot. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 01:56, 12 July 2016 (UTC)


Hello users, I propose having a page within noticeboards in the "general" section called "Block discussion" with a list of active discussions (which could be a review request, an unblock request or a discussion on whether to block the user) (to separate from administrators ' noticeboard, to clarify further, and that within the DB there are 5 topics, 1. Evidence (evidence that the user can provide as a reason for blocking, will be ignored in the review request), 2. Defense (defense of the blocked or accused against blocking or defending its review), 3. Comments (comments from anyone who is registered and at least 10 edits whether they agree, disagree or neutrality with blocking, a filter or unblocking), 4. Administrators' evaluation (where administrators agree or disagree with blocking, unblocking or filtering, this means that the conclusion depends on the administrators' assessment), 5. Conclusion (Conclusion of the discussion if the blocking, filtering or unblocking was approved).
==== Support adoption ====
* '''Support''' -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 01:56, 12 July 2016 (UTC)


NOTE: And there must be verification in the discussion to prevent someone from manipulating BD through sockpuppetry. [[User:JPPEDRA2|<span style="color:blue;font-family:Times New Roman;font-size:12pt">JPPEDRA2</span>]] <sup>[[User talk:JPPEDRA2|<span style="color:blue;font-family:Comic Sans;">why not?</span>]]</sup> 18:54, 27 November 2024 (UTC)
==== Oppose adoption ====
*'''Oppose''' And demur on the current non-admin close of a proposal which had significant substantial and reasoned opposition in any case. I suggest the proposer note this and ask for a ''formal closure'' by an admin with ''at least 2000 total edits'' to close it. [[User:Collect|Collect]] ([[User talk:Collect|talk]]) 13:06, 12 July 2016 (UTC)
** {{u|Collect}} Then I suggest you take it to [[WP:AN]]. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 16:08, 12 July 2016 (UTC)
*** {{reply|Collect}} There is a close challenge discussion at [[WP:AN]] if you wish to make that point there. Note that opposing because it's an non-admin is against policy. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 20:28, 12 July 2016 (UTC)


:This means I'm proposing to separate "Wikipedia:Block Discussion" from "Wikipedia:Administrators' noticeboard" to be clearer [[User:JPPEDRA2|<span style="color:blue;font-family:Times New Roman;font-size:12pt">JPPEDRA2</span>]] <sup>[[User talk:JPPEDRA2|<span style="color:blue;font-family:Comic Sans;">why not?</span>]]</sup> 18:57, 27 November 2024 (UTC)
=== Other comments ===
:I understand the desire to split things off of AN/ANI, but this split poses several problems in practice. Quite frequently the proposal for a CBAN only arises after discussion has been ongoing for some time, and while it could be split off at that point it creates an extra bureaucratic step for questionable benefit. The other issue is that neither CBAN impositions nor their appeals are all that common, and separate noticeboards only tend to work well for things that have a fairly high frequency threshold. Arguably, if we had to do it over again AN wouldn't be the catchall, but at this point changing that is more trouble than its worth.
:Granted, CBAN and appeal procedures could be tightened up separately without splitting anything off, but there's a longstanding preference for unstructured and somewhat messy discussions, and I don't see that changing anytime soon. [[Special:Contributions/184.152.68.190|184.152.68.190]] ([[User talk:184.152.68.190|talk]]) 17:03, 28 November 2024 (UTC)
::@[[Special:Contributions/184.152.68.190|184.152.68.190]] Ok, i'm understand, so can i'm cancel this proposal because that will be more complex? [[User:JPPEDRA2|<span style="color:blue;font-family:Times New Roman;font-size:12pt">JPPEDRA2</span>]] <sup>[[User talk:JPPEDRA2|<span style="color:blue;font-family:Comic Sans;">why not?</span>]]</sup> 17:57, 28 November 2024 (UTC)
:::{{re|JPPEDRA2}} Yes, you can just close it as withdrawn, if you so chose. But don't let me discourage you if you want to leave this open for input from others; every so often [[WP:PEREN|perrenial proposals]] do get implemented, including rather recently, though its usually better to get input at [[WP:VPI]] first.
:::As a side note unregistered users cannot <small>yet</small> [[WP:PINGIP|be pinged]], though apparently that is coming sometime in the not to distant future. [[Special:Contributions/184.152.68.190|184.152.68.190]] ([[User talk:184.152.68.190|talk]]) 18:52, 28 November 2024 (UTC)
::::Ok, so I won't cancel now, I will let others discuss it, if it is rejected, put it in those VPI or perrenial proposals that you mentioned, thanks non-registrered user. [[User:JPPEDRA2|<span style="color:blue;font-family:Times New Roman;font-size:12pt">JPPEDRA2</span>]] <sup>[[User talk:JPPEDRA2|<span style="color:blue;font-family:Comic Sans;">why not?</span>]]</sup> 19:20, 28 November 2024 (UTC)


== Global welcoming policy ==
*I agree that a completely inactive Draft should be removed from Draftspace if a reasonable time has passed with no edits... But before we delete the draft, we should notify relevant editors (such as the draft creator) and give them the opportunity to request userfication. [[User:Blueboar|Blueboar]] ([[User talk:Blueboar|talk]]) 03:28, 12 July 2016 (UTC)
** {{reply|Blueboar}} That's already a part of [[Wikipedia:Proposed_draftspace_deletion#Nominating|Nominating #4]]. I haven't created it yet but [[Template:Proposed draft deletion notify]] will probably be worded even easier than [[Template:Proposed deletion notify]]. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 08:01, 12 July 2016 (UTC)
::::It mentions notification... But does not say anything about the possibility of userfication. That should be in there somewhere. [[User:Blueboar|Blueboar]] ([[User talk:Blueboar|talk]]) 11:42, 12 July 2016 (UTC)
::::: I'll add that as a proposal. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 17:09, 12 July 2016 (UTC)
:::::: {{u|Blueboar}} Feel free to revise the proposal if you think more is needed. The actual templates will probably need more work as well. I'm not particularly confident this as is will succeed but let's see. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 19:19, 12 July 2016 (UTC)
*I wholeheartedly oppose the notion that being inactive is a reason to remove a draft in Draftspace. The whole reason of having such space to begin with is to allow the possibility that any editor may find usable content that could be reused in the future, but it does not conform to the main space strict criteria (yet); if we delete such content, we might as well get rid of the Draft space entirely. [[User:Diego Moya|Diego]] ([[User talk:Diego Moya|talk]]) 12:25, 12 July 2016 (UTC)
** It's not "being inactive", it really should be "not edited and not likely to go anywhere." Old drafts that are useful are currently reviewed and extended via AFC. Old drafts that are ready currently get moved to mainspace. As such, it's basically an extended MFD for older drafts in a particular space with the rationale being provided there in the notice and just a single veto needed rather than a formal discussion. -- [[User:Ricky81682|Ricky81682]] ([[User talk:Ricky81682|talk]]) 19:19, 12 July 2016 (UTC)


There is a proposed global policy at [[:meta:Requests for comment/Welcoming policy]]: "A wiki is only allowed to post welcome messages to users if their account was originally created at the wiki, or the user has at least one non-imported edit there." Comments belong there and not here. [[User:PrimeHunter|PrimeHunter]] ([[User talk:PrimeHunter|talk]]) 21:48, 27 November 2024 (UTC)
=== Move to [[Wikipedia_talk:Proposed_draftspace_deletion]] ===
I think this discussion should be moved to [[Wikipedia_talk:Proposed_draftspace_deletion]]. Link from here, transclude it to here, whatever, by all means, but proposal development discussion belongs on the proposal's talk page. --[[User:SmokeyJoe|SmokeyJoe]] ([[User talk:SmokeyJoe|talk]]) 01:54, 13 July 2016 (UTC)
: Plus it'll be easier to remove this lunacy when that page is finally defeated and deleted. [[User:Wikijuniorwarrior|Wikijuniorwarrior]] ([[User talk:Wikijuniorwarrior|talk]]) 03:59, 13 July 2016 (UTC)

Latest revision as of 20:15, 28 November 2024

 Policy Technical Proposals Idea lab WMF Miscellaneous 
The policy section of the village pump is used to discuss already-proposed policies and guidelines and to discuss changes to existing policies and guidelines. Change discussions often start on other pages and then move or get mentioned here for more visibility and broader participation.
  • If you want to propose something new that is not a policy or guideline, use Village pump (proposals). For drafting with a more focused group, you can also start on the talk page for a WikiProject, Manual of Style, or other relevant project page.
  • If you have a question about how to apply an existing policy or guideline, try one of the many Wikipedia:Noticeboards.
  • If you want to ask what the policy is on something, try the Help desk or the Teahouse.
  • This is not the place to resolve disputes over how a policy should be implemented. Please see Wikipedia:Dispute resolution for how to proceed in such cases.
  • If you want to propose a new or amended speedy deletion criterion, use Wikipedia talk:Criteria for speedy deletion.

Please see this FAQ page for a list of frequently rejected or ignored proposals. Discussions are automatically archived after remaining inactive for two weeks.


Date redirects to portals?

[edit]

16 August 2006 points to the current events portal as a result of this discussion. However, date redirects will continue to come up at RfD, some some wider community discussion and input is helpful on whether or not the current events portal is an appropriate target for mainspace redirects. See also: this ongoing discussion for some context.

Related questions to consider: are portals "part of the encyclopedia"? Thanks, Cremastra (uc) 00:55, 30 October 2024 (UTC)[reply]

  • The second question is easy: Yes, portals are part of the encyclopaedia. As to the first question, portals are reader-facing content and so I see no reason why they wouldn't be appropriate targets for mainspace redirects, given that uncontroversially target mainspace redirects to reader-facing templates and categories when they are the best target. Whether the port is the best target for a given date will depend on the specific date but in general the portal should always be an option to consider. Thryduulf (talk) 01:32, 30 October 2024 (UTC)[reply]
    I agree with this. The portal is definitely not always the best option and it has its limitations, but, as I wrote at WP:RDATE it should be considered and assessed along with mainspace articles. Cremastra (uc) 01:44, 30 October 2024 (UTC)[reply]
Pinging: Utopes, who I've discussed this with.
If a namespace doesn't have the same standards as mainspace, then the reader shouldn't be redirected there while possibly not realizing they are now outside of mainspace. Yes, there is more content at Portal:Current events/August 2006 than at 2006#August, but the reader is now facing a decades-old page with no quality control, where links to Breitbart are misleadingly labeled as (AP). Chaotic Enby (talk · contribs) 00:50, 6 November 2024 (UTC)[reply]
Portal does have the same standards as mainspace. That a portal is not up to those standards is no different to an article being in bad shape - fix it. Thryduulf (talk) 00:54, 6 November 2024 (UTC)[reply]
So I can use the speedy A-criteria for portal pages? Fram (talk) 17:40, 7 November 2024 (UTC)[reply]
No, because they are not articles. Two things can be held to the same standard without being the same thing. Criterion P1 previously allowed that (indirectly) but it was repealed in 2023 due to lack of use. Thryduulf (talk) 19:42, 7 November 2024 (UTC)[reply]
Then they aren't held to the same standards... More in general, no, they obviously aren't held to the same standards, e.g. a portal page doesn't have to be a notable topic but may be purely decorative or (as is the case with the date pages) be a list of mainly non-notable things, failing WP:NOTNEWS and WP:LISTN. That some standards are the same (BLP, copyvio, ...) can also be said for e.g. user talk pages, and we don't redirect to these pages either. Fram (talk) 20:24, 7 November 2024 (UTC)[reply]
We don't redirect to user talk pages because they aren't reader-facing, so that's irrelevant. We don't hold reader-facing templates and categories to article content policies (because they aren't articles) but we do redirect to them. Don't conflate quality standards with inclusion policies, they are not the same thing. Thryduulf (talk) 21:15, 7 November 2024 (UTC)[reply]
I wasn´t aware that the standards we were talking about were solely quality standards, whatever these may be, and not content standards, sourcing standards, ... I´m sadly not amazed that you consider these irrelevant when deciding what to present to our readers. Fram (talk) 21:37, 7 November 2024 (UTC)[reply]
In theory, I think portals should be held to the same CSD criteria as articles. But of course the A criteria actually only apply to articles. Cremastra (uc) 22:08, 7 November 2024 (UTC)[reply]
  • There's a lot of random junk in portalspace, but yes, it is part of the encyclopedia. Just like categories and templates, portals are reader-facing content. C F A 💬
  • I didn't really have super strong opinions on portals until seeing this one link to Breitbart, twice, in a misleading way. This is not okay. I agree with Fram that clearly Portals are not being held up to the same standards as regular articles and it might be a bad idea to redirect readers to them. Toadspike [Talk] 23:00, 7 November 2024 (UTC)[reply]
  • I saw this on CENT, and I am confused by the question. Portal:Current events/2006 August 16 is very different from something like Portal:Belgium, and it doesn't make sense to pretend they are the same to establish policy. And what does "part of the encyclopedia" even mean? "Interpreting a confusing phrase" is a terrible way to decide redirect targets.
    For the specific question of "Should dates redirect to the Current Events portal rather than to a page like August 2006 ... I don't know. I don't see a compelling reason why they can't, nor a compelling reason why they should. Walsh90210 (talk) 15:45, 8 November 2024 (UTC)[reply]
    Hey, that's a nice Portal! Thank you for restoring my faith in portals. Clicking on "Random Portal" took me to Portal:Trees, which is also pretty nice. My opinion is now that yes, portals can be good, but it seems to me that we currently have no Ps and Gs to apply to their content or measure their quality, no consensus about how to direct readers to them, and a very checkered and controversial history of deletion. I really dunno what to do about them. Toadspike [Talk] 16:49, 8 November 2024 (UTC)[reply]
    Of course that's a nice portal, look who created it :-D Fram (talk) 17:51, 8 November 2024 (UTC)[reply]
  • No, we should not redirect dates to the current events portal subpages. It's a cross-namespace redirect that takes readers from somewhere they expect to be (an encyclopedia article on the topic "16 August 2006") to somewhere they don't expect to be (a navigational aid(?) that highlights some things that happened that day). I'm not 100% sure what the current events portal subpages are for, but they're not meant to stand in as pseudo-articles in places we lack real articles. Ajpolino (talk) 22:04, 8 November 2024 (UTC)[reply]
    Cross-namespace redirects in and of themselves are not a problem. They only cause issues when they take someone expecting reader-facing content to "backroom" content (e.g. project space). Both article and portals are reader-facing content, so this is not an issue. Thryduulf (talk) 22:17, 8 November 2024 (UTC)[reply]
    Is there another case where we link a reader from an article to a non-article without clearly denoting it? E.g. I have no problem with the {{Portal}} template folks often use in the See also section. Ajpolino (talk) 01:12, 9 November 2024 (UTC)[reply]
    There are lots of redirects to templates and categories. Many navigation templates link to other navigation templates. Thryduulf (talk) 08:12, 9 November 2024 (UTC)[reply]
    Any examples of these lots of mainspace pages which are redirects to templates? 08:42, 9 November 2024 (UTC) Fram (talk) 08:42, 9 November 2024 (UTC)[reply]
    List of elections in Texas, List of Kentucky county seats, Cite web. Thryduulf (talk) 00:13, 10 November 2024 (UTC)[reply]
    Thanks. Okay, Citeweb is a bad example, not something readers look for but something editors look for. The other 2 are among the 6 existing reader facing redirects to templates (from Category:Redirects to template namespace, the only ones which are from mainspace and not editor-related like the cite templates). Not quite the "lots" you seemed to be suggesting throughout this discussion, but extremely rare outliers which should probably all be RfD'ed. Fram (talk) 11:42, 10 November 2024 (UTC)[reply]
    Now only 2 remaining, converted the other 4 in articles or other redirects. Fram (talk) 11:52, 10 November 2024 (UTC)[reply]
  • Yes, the current events portals are valid redirect targets for dates and preferred in this case of the best article redirect for a specific date being the month section of an article on an entire year. I agree with Fram that portals are not held to the same standards as articles, but I disagree with Ajpolino's stance that a cross-namespace redirect is so disruptive that they are prohibited in all cases, given that WP:Portal says "portals are meant primarily for readers." ViridianPenguin 🐧 ( 💬 ) 23:46, 8 November 2024 (UTC)[reply]
  • Commenting strictly on the "are portals part of the encyclopedia" question, yes it is. Unfortunately there was one extremely loud, disruptive voice who kept making portals less useful and suffocating any discussions that would make it more beneficial to readers. Plenty of willing portal contributors, including myself, left this space and readers are still reaping the seeds of what that disruptive user planted even after they have been ArbCom banned over a year ago. So it may given some people an illusion that portals aren't doing much towards the encyclopedic goal, because the current status is handicapped by its history. I'm reserving my views on the redirect part of the discussion. OhanaUnitedTalk page 07:29, 9 November 2024 (UTC)[reply]
  • Not, portals are not held to the standards of articles, and if something for whatever reason shouldn't be or can't be an enwiki article, this shouldn't be circumvented by having it in portalspace. Either these date pages are acceptable, and then they should be in mainspace. Or they are not what we want as articles, and then we shouldn't present them to our readers anyway. Fram (talk) 11:42, 10 November 2024 (UTC)[reply]
    These current events pages differ from articles in many respects, but the referencing standards are similar. Whether they happen to be prefixed by "Portal:" or not is not reflective of their quality. J947edits 23:18, 11 November 2024 (UTC)[reply]
  • Yes, because the purpose of Portal:Current events/2022 August 21 is to provide encyclopaedic information on 21 August 2022 and this purpose has been by-and-large successful. J947edits 23:18, 11 November 2024 (UTC)[reply]
  • The current events portal example listed seems encyclopedic enough, in that apart from some formatting differences it might as well be a list article, but I've seen other portals that have editor-facing content that is more dubiously appropriate for mainspace. Consider, for example, Portal:Schools § Wikiprojects (capitalization [sic]) and Portal:Schools § Things you can do, and the similar modules at many other portals. Sdkbtalk 18:27, 13 November 2024 (UTC)[reply]
  • Yes per J947, especially given that the current event portals function like an encyclopedic list for the given date. -- Tavix (talk) 16:46, 14 November 2024 (UTC)[reply]
  • Yes, speaking as a recognized portalista, portals have not yet been excised from the pedia. In this case, User:J947 makes the essential point. I'm not convinced that even incomplete, out-of-date portals are any less encyclopedic than the 2 million or so Wikipedia articles nobody bothered to edit last year. BusterD (talk) 14:53, 19 November 2024 (UTC)[reply]
  • Portals are not part of the encylopedia as we understand encyclopedias: sources of information. They serve as navigation within an encylopedia. We would not see a Portal as the final delivery of information, any more than we would see a contents page, index, blurb, or advert as the final information page. These are all ancillary. People mostly land on a Wikipedia article page without a Portal. I have used Wikipedia for nearly twenty years without ever needing a Portal to direct me to where I want to go, and I would assume this is true for the majority of people. Redirects are designed as a signpost, and we frown upon a signpost simply pointing to another signpost. People would generally only arrive at a Portal if directed there from a link that should more helpfully point to the appropriate article. The Belgium Portal is mentioned above as a good Portal. If we go to the Belgium article and scroll down, there is a link to the Belgium Portal. But the Portal mainly provides us with a digest of the Belgium article, including a link back to the Belgium article, which itself contains more links to Belgium related articles than the Belgium Portal. Huh? Seriously? Why are we taking readers away from a sublime source, rich with information and links, to an inferior source? There is nothing on the Belgium Portal that is not available on the Belgium article page - including links to news. But there is much on the Belgian article page that is not on the Belgium Portal page. My suggestion is that ALL links to portals such as the Belgium Portal should instead go to the main article page. Why are we redirecting people to a redirect page when we can send them to the main article on the topic? Portals are a waste of our time and resources, and are a misdirect for readers. SilkTork (talk) 22:33, 23 November 2024 (UTC)[reply]
    @SilkTork Are you also specifically opposed to redirecting to the current events portal, which is more "encyclopedic" than "navigational"? Cremastra ‹ uc › 22:44, 23 November 2024 (UTC)[reply]
    I'm not exactly comfortable with 2006#August as a target as that itself is a signpost, but I see little value in us having two such signposts - that simply duplicates and confuses things. Either we have 2006#August or we have Portal:Current events/2006 August 16, and I'd much prefer we simply get rid of Portals, so I would obviously opt for 2006#August. SilkTork (talk) 23:02, 23 November 2024 (UTC)[reply]
    The CE portal has more information for the reader, so I prefer it (see my arguments at WP:RDATE.) Cremastra ‹ uc › 23:12, 23 November 2024 (UTC)[reply]
    @SilkTork Your argument breaks down as soon as you realise that disambiguation pages and set indexes exist and that redirects to those pages are extremely common and uncontroversial. We also redirect people to outlines, broad concept articles and overviews. What is the "main article page" for a date? In all but a few exceptional cases there isn't a single article but multiple, and so just as if they had searched Mercury, Bitter ash or Stuffed flatbread we present them with a menu of content that is relevant to their search term and let them choose what it is they want to read about. Thryduulf (talk) 22:46, 23 November 2024 (UTC)[reply]
    See my answer above. I don't see the point in duplicating signposts. We have Belgium, so we don't need Portal:Belgium; and we have 2006#August so we don't need Portal:Current events/2006 August 16. Signposts are not part of the encyclopedia, but they are navigational aids which lead us to further information. However, we have built into every article multiple signposts to further information. We don't need to have duplicate signposts outside of mainspace to which people are directed away from mainspace to consult. It is a waste of our time and resources, and a misdirection for readers. Internal links are an elegant way of signposting to further information. Navigational templates are a little clunky, but are useful. Portals take readers away from the encyclopedia, and are a pointless timesink for both editors and readers. SilkTork (talk) 23:02, 23 November 2024 (UTC)[reply]
    Portals are just as much part of the encyclopaedia as set indexes and navigational templates. Portal:Belgium and Belgium fulfil very different roles in the encyclopaedia, neither is a duplicate of the other. Thryduulf (talk) 23:10, 23 November 2024 (UTC)[reply]

Issues with antiquated guideline for WP:NBAND that essentially cause run of the mill non-notable items to be kept

[edit]

Specifically, WP:NBAND #5 and #6, which read:

5.) Has released two or more albums on a major record label or on one of the more important indie labels (i.e., an independent label with a history of more than a few years, and with a roster of performers, many of whom are independently notable).
6.) Is an ensemble that contains two or more independently notable musicians, or is a musician who has been a reasonably prominent member of two or more independently notable ensembles. This should be adapted appropriately for musical genre; for example, having performed two lead roles at major opera houses. Note that this criterion needs to be interpreted with caution, as there have been instances where this criterion was cited in a circular manner to create a self-fulfilling notability loop (e.g., musicians who were "notable" only for having been in two bands, of which one or both were "notable" only because those musicians had been in them.)

These appear to have been put together by a very small number of editors over a decade ago and hasn't seen much change since then and I feel it's much more lenient than just about anything else. This SNG defines a "label" that has been around for over "a few years" that has a roster of performers as "important". So, any group of people who have released two albums through ANY verifiable label that has exited for more than a few year can end up being kept and this isn't exactly in line with GNG. I believe a discussion needs to be held in order to bring it to GNG expectations of now.

Graywalls (talk) 06:17, 30 October 2024 (UTC)[reply]

Especially given how broadly the various criteria have been "interpreted" in deletion discussions, the best way to go about it is just to deprecate the whole thing. Rely on the GNG for band notability, and if that results in a heap of articles on ephemeral outfits, garage bands and local acts vanishing, huzzah. Ravenswing 09:07, 30 October 2024 (UTC)[reply]
The SNG isn't workable in the age of digital distribution. It's very easy to create "an independent label with a history of more than a few years". If someone wants to suggest a way to reform the SNG, I am open to solutions. But deprecation is a simple alternative if we can't. The GNG is always a good standard because it guarantees we have quality sources to write an article. Shooterwalker (talk) 14:22, 30 October 2024 (UTC)[reply]
I was active in AfD discussions when NBAND was pretty new, and it was useful for dealing with a flood of articles about garage bands and such, but I think our standards in general have tightened up since then, and I agree it is time to review it. There is the possibility, however, that revising NBAND may require as much discussion as revising NSPORT did. Donald Albury 17:49, 30 October 2024 (UTC)[reply]
This sounds reasonable. I guess we need some concrete re-write suggestions to base an rfc on. Gråbergs Gråa Sång (talk) 18:17, 30 October 2024 (UTC)[reply]
It sounds like you're assuming that NBAND is meant to be a substitute for the Wikipedia:General notability guideline. That's true for some WP:Subject-specific notability guidelines but not for all of them.
I guess the underlying question is: Is there actual harm in having a permastub about a band that proves to be borderline in GNG terms? Consider this:

"Alice and Bob are a musical duo in the science fiction genre.[1] They released their first album, Foo, in 2019 and their second, Bar, in 2020. Both albums were released by Record Label.[2] They are primarily known for singing during a minor event.[3]"

I'm asking this because I think that the nature of sources has changed, particularly for pop culture, since NBAND and the GNG were written. We now have subjects that get "attention from the world at large", but which aren't the Right™ kind of sources and, while these Wrong™ sources definitely provide "attention", some of that attention might not provide biographical information (which means we're looking at a short article).
For example, instead of getting attention in the arts section of a daily newspaper, they're getting attention from Anthony Fantano on YouTube. He's an important music critic,[1] but I suspect that our knee-jerk reaction is "Pffft, just some YouTuber, totally unreliable". Consequently, we might rate a band that we theoretically intend to include ("attention from the world at large") as not meeting the GNG (because the whole field relies on the Wrong™ style of sources). WhatamIdoing (talk) 19:02, 30 October 2024 (UTC)[reply]
Keep in mind that like most other notability guidelines, it is a presumed assumption that a topic is notable if it meets these criteria. If you do an exhaustive Before and demonstrate there is no significant coverage beyond the sourcing to satisfy there criteria, the article should still be deleted. None of the SNGs are geared towards preventing this type of challenge. — Masem (t) 19:30, 30 October 2024 (UTC)[reply]
If we had to yield to presumptive notability about some random band because it released two albums with Backyard Trampoline Recordings established few years ago and had to do exhaustive search to disprove notability, we're getting setup for a situation where removal is 10x more challenging than article creation. So.. I see a great value in scrapping NBAND 5, and 6. Graywalls (talk) 00:47, 31 October 2024 (UTC)[reply]
Welcome to WP:SNGs. As Masem said, they're supposed to be a rough idea of gauging notability before exhaustively searching for sources. But pretty much all of them have ended up being used as means to keep articles about trivial or run-of-the-mill subjects. Thebiguglyalien (talk) 19:37, 30 October 2024 (UTC)[reply]

Graywalls listed two criteria but the main discussion seems to be about the 1st (#5). I agree with Graywalls on that. With the evolution of the industry, the label criteria is no longer a useful indicator as it once was and IMO #5 should be removed or modified. Sincerely, North8000 (talk) 19:13, 30 October 2024 (UTC)[reply]

I agree, both those criteria should be scrapped. JoelleJay (talk) 22:21, 30 October 2024 (UTC)[reply]
I've noticed that as well. I think #6 has some value still, while #5 is like saying an author who has published two or more books by a major publishing house is presumed notable. Way too low a bar without requiring some level of reception of those albums/books. (WP:NAUTHOR doesn't have that 2-book criteria, of course, just seems like parallel benchmarks.) Schazjmd (talk) 13:25, 31 October 2024 (UTC)[reply]
On the other hand, in this case, I suspect that an artist that "has released two or more albums on a major record label or on one of the more important indie labels" will in 99% of cases have enough coverage to clear the GNG bar. I'd like to see an example of one that doesn't. Black Kite (talk) 13:29, 31 October 2024 (UTC)[reply]
The definition of important as said in #5 is "history of more than a few years, and with a roster of performers, many of whom are independently notable". This would mean that a garage band is notable, because they've released two CD-R albums on Rotten Peach Recordings which has been around for 3 1/2 years, has a roster of performers and some of whom have a Wikipedia page on them. Often time "notable" is determined by the presence of a stand alone Wikipedia page. When you look at the page, many band member pages are hopelessly non-notable, but removal takes an AfD. So a simple deletion can become a time consuming multi-step AfD. Graywalls (talk) 19:18, 31 October 2024 (UTC)[reply]
Here's a current AfD I am participating in where NBAND#5 was invoked to justify a keep. Wikipedia:Articles_for_deletion/Sons_of_Azrael_(3rd_nomination) Graywalls (talk) 19:24, 31 October 2024 (UTC)[reply]
Not opining on that band's notability, but Metal Blade is a famous independent label that has existed for 42 years, has released material by very high-profile bands, and is distributed by Sony - it's not some one-person imprint operating out of their garage. Black Kite (talk) 11:28, 1 November 2024 (UTC)[reply]
I concur regarding that particular example.
Metal Blade is a big label, and not surprisingly notability was quickly demonstrated in the deletion discussion through citing reliable source coverage. And that's how #5 should work - artist is on a significant label, which suggests coverage exists. And then coverage is found.--3family6 (Talk to me | See what I have done) 12:08, 16 November 2024 (UTC)[reply]
It's complicated - on the one hand, music publications are increasingly prioritizing their coverage toward Taylor Swift-level celebrities, so I am almost certain there are artists on major labels that might be examples -- major as in the Big 3. This is especially so for genres like country that publications don't cover as much - there are some big names on the roster of Warner Music Nashville and also some not-so-big names.
The elephant in the room here is that entertainment journalism is in crisis mode right now, publications are operating on skeleton crews, and the range of coverage has narrowed dramatically. I encourage everyone taking part in this discussion to read the article I linked, there are a lot of assumptions being made about the way things work that aren't true. Gnomingstuff (talk) 20:30, 19 November 2024 (UTC)[reply]
  • One suggestion I would add is to make these two criteria apply only to bands before a specific year, that year being where physical releases still dominated over digital sales. I don't know the exact year but I am thinking it's like around 2000 to 2010. There may still be older groups during the time of physical releases that don't yet have articles that would fall into one of these criteria. Masem (t) 20:02, 31 October 2024 (UTC)[reply]
  • As someone who's had WP:DSMUSIC watchlisted for most of their editing history, and who tends towards deletion at that, I actually don't see much of a problem with these criterions. It certainly seems true that the majority of musicians who are signed to a label or a member of multiple bands with two other musicians who meet WP:GNG themselves meet GNG. I do think it is sometimes justified to accept less-than-GNG sourcing in articles where a SNG is met (see Wikipedia:Articles for deletion/John LeCompt for this as it applies to c6 specifically) and more importantly, NMUSIC contains language that allows deleting articles even where it is technically met (see Wikipedia:Articles for deletion/Rouzbeh Rafie for an extended argument about that. Mach61 23:29, 31 October 2024 (UTC)[reply]
  • I've understood these criterion to be supplementing GNG, that is, that if a band or individual artist meets one or more of these criterion, they *likely* are notable. However, in the past when I was a younger and less experienced editor, I think I did understand these as being additions or alternatives to GNG. So I think that should be clarified. This has come up on the deletion discussion for Jayson Sherlock. He is a member or former member of several very notable bands, and for that reason I presumed that he would easily have independent coverage about him specifically. However, to my surprise, there's only one interview of him in a reliable source that would provide notability (there's some interviews on personal blogs or minor sites that wouldn't be RS except for him making statements about himself). But at least one editor has used the above criterion to argue that the article should be kept.--3family6 (Talk to me | See what I have done) 12:20, 1 November 2024 (UTC)[reply]
    Just as an aside, interviews do not contribute to GNG unless they include secondary independent SIGCOV (such as a substantial background introduction by the interviewer). JoelleJay (talk) 15:39, 1 November 2024 (UTC)[reply]
That's how I see most SNGs (and the outliers ought to follow their lead). At the very least, we can clarify that NBAND is meant as an indicator for the GNG, and not a substitute. Shooterwalker (talk) 02:04, 2 November 2024 (UTC)[reply]
  • As someone who thought the old NSPORTS was wildly overinclusive and needed cleanup... these NBAND guidelines don't seem that bad? If two plainly notable musicians were discovered to have done some obscure team-up in the 1970s, that does indeed seem to be a notable topic and useful to have linked somewhere, even if there isn't tons of info on this collaboration. It's worth mentioning because minor subtopics are often merged to the overarching topic (e.g. songs to the album), but there may not be a clear merge location for this if both parties were equal contributors, and a short separate article is an acceptable compromise. Similarly, the complaint about #5 seems to be about just how "indie" the hypothetical label is, but this seems like a solvable problem. If a band fails GNG, that implies that either their two albums really were from a very obscure indie outfit and thus also fail NBAND, or else that we have some sort of non-English sources issue where we may consider keeping on WP:CSB grounds (i.e. that sources probably do exist to pass GNG, but they're difficult to find, and we can trust they exist because this was a major and notable label releasing the band's work). About the only suggestion I can offer is that the comment in 6 about avoiding circular notability could probably be phrased in the sense of GNG, i.e. that the two notable musicians need to both meet GNG and then this will create a new, safe NBAND notability for their collaboration. SnowFire (talk) 17:36, 4 November 2024 (UTC)[reply]
    The reverse situation, such as is currently being discussed at Wikipedia:Articles for deletion/Jayson Sherlock, is one where you have someone who was/is in multiple notable bands, but doesn't have independent coverage about them as an individual person. -- 3family6 (Talk to me | See what I have done) 22:30, 7 November 2024 (UTC)[reply]
  • Agreed with deprecation; "Rely on the GNG for band notability" is the correct answer. And is the correct answer for many other things about which we have SNGs that attempt to be alternatives to GNG. Perhaps the only justifiable one is WP:NACADEMIC, because special considerations apply in that sphere (academics and other journal-publishing researchers are generally unknown the public and the public-facing media coverage like newspapers but may have major impacts in particular fields and on the world; what determines their influence level is primilar the frequency of citation of their work by other academics). No such special considerations apply with regard to bands or most other categories. We have some SNGs that are helpful because they are written to comply with GNG, to explain predictively what is most likely or unlikely to pass a GNG test at ANI, rather than trying to be an end-run around GNG. If we actually needed an SNG for bands and musicians, then the current SNG for them could be replaced by something like that. However, we don't actually need an SNG for bands and musicians.

    PS: The ideas in the current NBAND SNG are daft. Lots of musical acts have multiple albums (i.e. tracks released at the same time under a grouping title) and lots of indie labels (which may just be some dude in his bedroom) exist with multiple acts, some of them nominally notable [because of NBAND's issues, making this a vicious cycle!], but that doesn't actually make every band on that notional label (nor the label itself) enclopedia-worthy. Some of these are farcically obscure acts [not a denigration – I'm probably buying their stuff]. This is not 1977; you do not need a vinyl pressing plant to be a music label. You just need to figure out how to fill in a web form at Bandcamp and Spotify, and have enough of a clue about how the present music industry works (often just within a narrow subculture) that you can convince some acts (probably your friends in the same scene) that you can help them if they agree to be on your roster. PPS: A side issue is that "albums" isn't a good metric anyway, since several genres are not album-driven at all, and the entire notion of albums is being increasingly questioned in the era of on-demand music.  — SMcCandlish ¢ 😼  21:59, 15 November 2024 (UTC)[reply]

I'd be happy to see #5 and #6 completely eliminated. What does it take to make that happen? What's the next step? Graywalls (talk) 02:08, 16 November 2024 (UTC)[reply]

If you believe this would amount to a major change to the guideline, then you should probably be making a formal WP:PROPOSAL. WhatamIdoing (talk) 04:52, 16 November 2024 (UTC)[reply]
WhatamIdoing, would clarifying that SNG don't override GNG requirements be a major change?--3family6 (Talk to me | See what I have done) 11:57, 16 November 2024 (UTC)[reply]
Yes. And if you want to try that, you should find and read the many previous discussions about that. WhatamIdoing (talk) 19:27, 16 November 2024 (UTC)[reply]
See WP:NPLACE, which presumes populated legally recognized places are notable. So, all it takes is prove the legal recognition and presence of people and it's assumed to be notable, unless refuted.
A legally recognized city is presumed, but not guaranteed notable. If it doesn't meet GNG, then the presumed notability can be refuted. It does essentially "override" GNG though a short cut, but is subject to removal by presenting failure to meet GNG.
Such presumption is not present for most things. For example, simply quoting a local paper about a gas station opening up and operating demonstrates existence of that gas station, but there's no presumed notability for businesses.
NBAND 5 and 6 qualifies bands and albums into Wikipedia far easier than they should and they stand as a burden to article deletion due to presumed notability under tenuously defined importance, such as having released two albums through an important indie label Four Legged Octopus, which is "important" because the MailBox Etc based label has been around for five years and has a roster. Graywalls (talk) 16:55, 18 November 2024 (UTC)[reply]
  • Not speaking to this issue directly, but the trend in subject specific guidelines, IMHO, has been to reduce the influence of SNGs relative to GNG, not override. When we started these projects 20 years ago, almost every article was low hanging fruit, almost bound to be found notable eventually. As an example, Military History Wikiproject adopted and modified WP:SOLDIER, a set of specific and non-subjective criteria which if met gave an indication of presumption of reliable sources being found somewhere eventually. This was intended to screen out a lot of "dead veteran I know" articles, not become the floor for inclusion. When it finally came up for discussion it was made clear SOLDIER was just a project thing and wasn't itself an approved SNG. It was quickly decommissioned, but SOLDIER criteria was for many years a frequently mentioned keep argument at AfD. As another example, WP:SPORTSPERSON is another project related shorthand (but consensus-approved SNG), which made it more difficult to create and keep articles about athletes without at least one source with significant coverage, which still seems a low bar indeed. IMHO the original intent of such SNGs was to screen article candidates, but as the pedia grew, we started using SNGs to keep them. Adjusting SNGs to meet the modern usage era seems the practical and accepted path. The medical SNGs are still used as exclusionary, and for the best reasons. BusterD (talk) 15:21, 19 November 2024 (UTC)[reply]
    IMHO the original intent of such SNGs was to screen article candidates, but as the pedia grew, we started using SNGs to keep them. As someone who joined 10 years in, this seems to have been the trend.--3family6 (Talk to me | See what I have done) 18:20, 19 November 2024 (UTC)[reply]
    Yes, in my opinion SNGs should be exclusionary criteria, necessary but not sufficient for notability. JoelleJay (talk) 23:02, 20 November 2024 (UTC)[reply]
    Agreed, and this makes a lot more sense to me. I haven’t paid much attention to SNGs till recent years, so it has been my impression that they are applied as supplemental options towards keeps and creates. The only one that I even think of as exclusionary is WP:NEVENT, although that’s got its own difficulties inherent.
    Ideally I’d like to see every AfD “SNG-therefore-keep” voter back their rationale up by saying that they endorse the SNG by its likelihood toward sources existing. — HTGS (talk) 22:34, 21 November 2024 (UTC)[reply]

Blind 1RR/3RR

[edit]

Blind enforcement of 1RR/3RR does not serve the project. The question should not be whether one violated the rule, but whether they violated the rule in a way that does not benefit the article. If there is no objection to the violation, we can reasonably assume that they are benefiting the article, or at least causing no harm. The decision should be left in the hands of other editors. Could this be used as a weapon? Would there be editors who claim harm where none exists? Certainly, but that's preferable to what we have now.

The problem, no doubt familiar to editors reading this, is that there are often not enough "good" editors around to protect an article from "bad" editors (malicious or merely inexperienced) while staying within 1RR/3RR. There is no restriction on the number of BOLD edits by a given editor, or on the number of editors performing BOLD edits. ―Mandruss  00:09, 10 November 2024 (UTC)[reply]

1RR in contentious areas should be fully maintained, with no exceptions. Otherwise, edit wars will quickly develop. GoodDay (talk) 00:11, 10 November 2024 (UTC)[reply]
If someone is repeatedly reverting reverts, then there is objection to the violation by definition. That's what edit warring is. If someone is making the same BOLD edit that needs to be reverted multiple times, then they are also edit warring. There are already exceptions with these rules for patent nonsense or obvious vandalism. If there's routine disruption, then it only makes the problem worse to revert over and over instead of taking it to WP:RFPP. If you feel the need to make more than one or two reverts in a content dispute, then it's time to either consider other options or step away from the article. Thebiguglyalien (talk) 01:31, 10 November 2024 (UTC)[reply]
It's not about edit warring or re-reverts; the problem exists without a single re-revert. Editor A does ten BOLD edits, five of which are detrimental to the article because they are too inexperienced (this stuff takes years to master, so that's far from uncommon). Editors B, C, D, and E contribute an additional twenty detrimental edits (along with any number of good ones, that number being irrelevant for our purposes here). Meanwhile, competent editors F, G, and H are limited to a total of nine reverts, leaving 21 detrimental edits in the article. I say F, G, and H should be allowed to revert until someone claims they are doing harm. ―Mandruss  02:04, 10 November 2024 (UTC)[reply]
Where are you seeing thirty detrimental edits to an article in every day? Why isn't this article protected? Why aren't editors F, G, and H starting a discussion? Why are they reverting Editor A's edits individually instead of rolling them back? Why is it so urgent that these edits need to be reverted right this moment? Even on the off chance that they encounter such an article that exists, F, G, and H would not need to engage in tag-team reverting (which is still edit warring) if they knew what they were doing. Thebiguglyalien (talk) 02:07, 10 November 2024 (UTC)[reply]
You are welcome to reduce the numbers as you please; the problem exists regardless. The article is protected, even with ECP, and there is no shortage of registered editors who have 30 days and 500 edits and still have years to go before they are editing with any reasonable level of competence. Some never reach that point. Why aren't editors F, G, and H starting a discussion? Seriously? Why are they reverting Editor A's edits individually instead of rolling them back? Because (1) they may not have the rollback right, and the rollback right should not be required to function as an editor, (2) they would be rolling back five good edits, and (3) it's impossible if Editor A's edits are interleaved with those of any other editor(s). Why is it so urgent that these edits need to be reverted right this moment? Because (particularly in large and very active articles) the bad edits can easily be missed if not caught immediately. Then they stay in the article for some unknown amount of time until noticed by a competent editor and corrected with a BOLD edit. Could be months or even years. Is that good for the article? ―Mandruss  02:27, 10 November 2024 (UTC)[reply]
they may not have the rollback right: Not the main point of this thread, but Wikipedia:Twinkle has its verison of rollback, available for any registered user.—Bagumba (talk) 04:57, 10 November 2024 (UTC)[reply]
Could you give an example or two where this has caused a problem? And I note that you have answered the two most important questions inadequately: if an article is subject to edit-warring it should be fully protected, and you dismissed "Why aren't editors F, G, and H starting a discussion?" with "Seriously?". Yes, of course it's a serious question. Starting a discussion is the best way of defusing an edit war. Phil Bridger (talk) 09:20, 10 November 2024 (UTC)[reply]
"Seriously?", while counter to the WP:DR policy, might be an honest response. I often get page protection or block requests, where my first response is often "where's the discussion?" —Bagumba (talk) 10:02, 10 November 2024 (UTC)[reply]
Unless Mandruss is extremely lazy, for which I have no evidence, I don't see how that response can be honest. It only takes a few seconds to start a discussion, no longer than it took to start this one, and the person who starts it wins some extra points. Phil Bridger (talk) 17:08, 10 November 2024 (UTC)[reply]
extremely lazy, for which I have no evidence Thank you! I have my share of faults and shortcomings, but I don't think extreme laziness is one of them. So there should be new discussions for each of the bad edits (separately for the sake of efficiency and organization), and the bad edits should remain in the article until enough editors have the time, interest, and attention span to form consensuses against them while attending to other important matters. This, at an ATP where we're struggling to keep the ToC at a manageable size even without such discussions. I don't know what articles you're editing, but I want to work there. ―Mandruss  03:51, 11 November 2024 (UTC)[reply]
Did you seriously just point to Donald Trump as your example and then say you don't know what articles aren't like that Thebiguglyalien (talk) 04:01, 11 November 2024 (UTC)[reply]
I gather the Donald Trump article is a rare anomaly where bad content is something we have to live with because the current rules are incapable of preventing it. After all, it's just one article. I would oppose that reasoning. I'd say article quality is at least as important there as anywhere else. ―Mandruss  04:33, 11 November 2024 (UTC)[reply]
So there should be new discussions for each of the bad edits ...: Yes, or what is an alternative? Your suggestion to favor "good" edits over "bad" is problematic when everyone says their's are the "good" ones. Polarizing topics can be difficult for patrolling admins to WP:AGF determine "good" v. "bad" edits if they are not subject matter experts.—Bagumba (talk) 05:43, 11 November 2024 (UTC)[reply]
Remember that consecutive edits by a single editor are treated as a single revert for WP:3RR purposes. So, in your case, editor H can go back and revert the various bad edits and, even if they mechanically break it out into multiple edits, they still have done one revert... Until someone goes back and re-reverts. Simonm223 (talk) 19:58, 20 November 2024 (UTC)[reply]
If "do not repeat edits without consensus" were the rule (rather than "do not revert"), it would take care of this problem. Levivich (talk) 03:42, 10 November 2024 (UTC)[reply]
Who said anything about repeated edits? Am I missing something? I'm tired at the moment, so that's a possibility. ―Mandruss  04:04, 10 November 2024 (UTC)[reply]
What do you mean, who said? I said something about repeated edits :-) If the rule were "do not repeat edits without consensus" 1x or 3x in 24 hours, instead of "do not revert" 1x or 3x in 24 hours (which leads to the whole "what exactly counts as a revert?" issue), the problem you are describing would not happen. The 'bad' editor can make 10 bad edits, and the 'good' editor can revert all 10 edits without violating do-not-repeat-3RR, and the 'bad' editor would be able to repeat 3 of those 10 edits without crossing do-not-repeat-3RR, and the 'good' editor can revert all 3 of those without crossing do-not-repeat-3RR, et voila: equilibrium. The problem is we focus on "revert" instead of "repeat." To tamp down on edit warring, we should prohibit people from repeating their edits, not from "reverting" (whatever that means, exactly) edits. Levivich (talk) 04:50, 10 November 2024 (UTC)[reply]
Well I'll have to come back after a sleep and try to comprehend that. ―Mandruss  04:56, 10 November 2024 (UTC)[reply]
Blind enforcement of 1RR/3RR does not serve the project: Are you referring to page protection or blocks? On contentious topics or any subject? —Bagumba (talk) 05:11, 10 November 2024 (UTC)[reply]

What determines "global consensus"?

[edit]

This ArbCom resolution established that "Where there is a global consensus to edit in a certain way, it should be respected and cannot be overruled by a local consensus."

I would like to ask what is the standard for defining that there is global consensus. If the top 100 articles in a certain category all are written in a certain way, is this considered sufficient for global consensus?

If a 100 articles are not enough, what is the threshold? Is it proportional to the number articles in that category?

Should then this warrant that all articles in that category be written in that way (unless very clearly harmful to the specific article)?

Milo8505 (talk) 10:41, 17 November 2024 (UTC)[reply]

WP:CONLEVEL was already a policy, independent of that resolution. It was just being cited as a principle used in deciding that case. —Bagumba (talk) 16:03, 17 November 2024 (UTC)[reply]
I believe that "global consensus" refers to policies and guidelines in particular, and to generally accepted practices across the whole of the English Wikipedia. A consensus that applies to just 100 articles out of the almost 7 million article in the English Wikipedia is a local consensus. Donald Albury 16:14, 17 November 2024 (UTC)[reply]
Milo8505, you asked this question in a way that can't be answered. Consensus does not depend on categories, and Wikipedia does not deal in abstract quantities but in concrete articles. Is this about whether to have an infobox on Gustav Mahler? If so then please say so, to provide some context to your question. Phil Bridger (talk) 17:34, 17 November 2024 (UTC)[reply]
@Phil Bridger Yes, it is about that topic. I believe that there is sufficient global consensus about the inclusion of infoboxes on biographies. I am well aware that the official policy is "no policy defined", but I see a clear trend, by looking at the most read articles, that all biographies - of musicians and non musicians alike - have an infobox, except a select few classical music composers.
I do not currently have the whole information regarding exactly how many of all biographies have an infobox, and that is why I was asking what is usually considered consensus.
However, given that I'm very aware that a hundred articles out of seven million is not precisely consensus, I will attempt, when I have the time, to go through every single biography to determine an exact percentage.
Milo8505 (talk) 18:56, 17 November 2024 (UTC)[reply]
If you want to spend your time doing that then I can't stop you, but I warn you that you will be wasting your time. That is not how consensus is measured. Phil Bridger (talk) 19:10, 17 November 2024 (UTC)[reply]
Obviously I will not count by hand, I have some idea of how to use an automated tool to do that.
But then, how is consensus measured?
I'm under the impression that there is a group of very determined and very vocal editors that fiercely oppose infoboxes on classical composers' articles (which leads to most of them having discussions about infoboxes, citing each other as examples of articles without infobox), separate from the majority of biographies, which have an infobox.
I see no better way of proving (or maybe disproving) my point than this, because my earlier points of infoboxes being a great thing for Gustav Mahler's article, and the fact that numerous non-classical musicians have infoboxes, and lengthy ones at that, seem to have fallen on deaf ears.
Milo8505 (talk) 20:01, 17 November 2024 (UTC)[reply]
And I would like to state, for the record, that I'm not doing this out of spite, or out of a personal interest (I'm actually losing my time by arguing about this), but because I truly, wholeheartedly believe that an infobox on each and every biography, and in general, on every article where there could be one (this excludes abstract topics such as existencialism) would make Wikipedia a truly better place.
Milo8505 (talk) 20:43, 17 November 2024 (UTC)[reply]
I would have to search the archives, but we actually held an RFC (one of the ways in which we determine GLOBAL consensus) that was focused on whether to mandate infoboxes on articles about composers… which determined that there were valid reasons not to require them (I suppose you could say that global consensus was to defer to local consensus on this specific issue). Remember WP:Other Stuff Exists is not an accepted argument here at WP. And that “standard practice” often has exceptions. Blueboar (talk) 22:06, 17 November 2024 (UTC)[reply]
I understand, but that is not my sole argument. I have provided other arguments in favor, which you can read at the aforementioned talk page which basically boil down to:
in my opinion,
  1. Infoboxes make standardized information more easily accessible, and
  2. They do not harm the rest of the article, as they do not displace the lead paragraph.
However, in the linked talk page, I see that opponents of infoboxes rely somewhat on the loosely established precedent/consensus that composers shouldn't have infoboxes.
That is why I wanted to bring forth a new argument, using the, as I see it, very established consensus for infoboxes in biographies, and what I want to know here is whether this consensus can be proven to exist (or what is it required for this consensus to exist). Milo8505 (talk) 07:30, 18 November 2024 (UTC)[reply]
This whole thing about "global" and "local" consensus seems to confuse everyone, and consequently folks make up whatever seems plausible to them. Let me give you a potted history and the usual claims, and perhaps that will help you understand the principle.
'Way back in the day, infoboxes didn't exist. AIUI the first widely used infobox template was {{taxobox}} in 2004, and the general concept appeared soon after. However, through the end of 2007, Template:Infobox didn't look like what we're used to. Originally, an 'infobox template' was literally a wikitext table that you could copy and fill in however you wanted.[1]
While infoboxes were being developed, the editors at Wikipedia:WikiProject Composers decided that infoboxes were a bad idea specifically for articles about classical composers, so after a series of disputes and discussions, in April 2007 they wrote a note that said, basically, "BTW, the sitewide rules don't apply to the articles we WP:OWN."[2]
The conflict between this group and the rest of the community eventually resulted in the 2010 Wikipedia talk:WikiProject Composers/Infoboxes RfC. The result of this years-long dispute is memorialized in the example given in what is now the Wikipedia:Consensus#Levels of consensus section of the policy: "Consensus among a limited group of editors, at one place and time, cannot override community consensus on a wider scale. For instance, unless they can convince the broader community that such action is right, participants in a WikiProject cannot decide that some generally accepted policy or guideline does not apply to articles within its scope."
Or, to be rather more pointy-headed about it: WikiProject Composers doesn't get to decide that "their" articles are exempt from MOS:INFOBOXUSE.
What was then a statement about the "Purpose of consensus" or, before then, one of several "Exceptions" to forming a consensus on a talk page has since been renamed ==Levels of consensus==. Also, ArbCom (and consequently part of the community) has started talking about "global" consensus. I think that has confused people about the point.
"Levels" of consensus could mean the strength of the consensus ("This is just a weak consensus, so..."). It could mean something about the process used ("My CENT-listed RFC trumps your Village pump post"). It could mean whether the consensus applies to the whole site ("We formed a consensus at Talk:Article about the first sentence of Article, so now I need to make 500 other articles match this one"). And it could tell us something about how likely it is that the decision matches the overall view of the community.
It's supposed to be that last one. We don't want a handful of people getting together on some page and saying "Let's reject this rule. This article needs to be censored. Copyvio restrictions are inconvenient. Bold-face text helps people see the important points. And we know this POV is correct, so it should dominate." We want quite the opposite: "The community says that this is usually the best thing, so let's do this."
AFAICT, the overall view of The Community™ is that we think that there should not be any Official™ Rule saying that any subset of articles should have an infobox. We're probably doing this mostly for social reasons, rather than article reasons. For example, every single article about a US President, or atomic elements, or any number of other subjects, has an infobox – but we refuse to write any rule saying they should, or even that they usually should, even though we know the popularity is ever-increasing. For example, at the moment, Georgina Sutton is the only biography linked on the Main Page that doesn't have an infobox.
I suspect that the closest we will come to such a rule during the next few years is a note about how popular they are. It should be possible to see how many articles (overall, or in particular subsets) already use infoboxes, and to add that information to MOS:INFOBOXUSE. For now, we could add a statement that "most" articles have an infobox.
  1. ^ Being able to do this in wikitext was was considered an improvement, because originally, you had to code tables in raw HTML.
  2. ^ This was not as unreasonable back then as it sounds now. WikiProjects were a significant source of subject-specific advice back then, and the rule-making systems were quite informal. WP:PROPOSAL didn't exist until late 2008. Before then, most guidelines and even policies acquired their labels merely because someone decided to slap the tag on it, and if nobody objected, then that was the consensus for what to call it.
WhatamIdoing (talk) 22:27, 17 November 2024 (UTC)[reply]
Thank you very much for your detailed response.
From what you have said, given that WikiProject composers have to follow MOS:INFOBOXUSE, there should be a discussion on each and every composer's talk page to determine whether an infobox is warranted.
I see this as a bit of a, difficult and fruitless endeavor, as the arguments presented, for either case, are always the same, and they all usually result in stalemates (like the one about Mahler).
What I propose is to change the policy, to, at least, recommend infoboxes on certain categories, given that, as you said, they are very popular. Or at the very least, as you suggest, acknowledge the fact that they are very popular.
When I have time to gather more data on the use of infoboxes, I will propose a new RfC to try to commit this change to the policy.
I am very well aware that my chances of success are slim, but, I'll do what I can do.
Milo8505 (talk) 08:00, 18 November 2024 (UTC)[reply]
Well, if "they all usually result in stalemates", then that represents a change, because the last complaint I saw about this subject said that the RFCs on whether to add an infobox almost always resulted in an infobox being added. Perhaps it varies by subject, however.
Acknowledging that they're popular shouldn't require a proposal for a change. It should only require getting some decent numbers. Check the archives of WP:RAQ; they probably can't query it directly, but if there's been a request, you'll see what could be done. It might also be possible to create a hidden category for "All articles with infoboxes", automagically transcluded, to get a count on the number of infoboxes. WhatamIdoing (talk) 06:45, 20 November 2024 (UTC)[reply]
First of all, thank you again very much for your continued interest.
The discussions around infoboxes (not RfCs, discussions on talk pages) as far as I have seen usually go something like:
- I propose adding an infobox
+ We have talked a lot about that and there are good reasonstm for which it should not be added
- But I also have good reasonstm for which it should be added.
(no comments for 4 years, then it begins again).
I thought a bit about counting links, and I realized maybe getting this data is easier than I thought, see:
For counting the number of transclusions to a given page, this tool is very useful, and says that there are around 3.2 million infoboxes in total, and 460 thousand infoboxes about people. (on the (Article) namespace).
Looking in the Talk namespace, there are around two million links to Template:Wikiproject Biography.
This seems to suggest that only around a quarter of all biographies have an infobox? Maybe I was wrong all along in my observation that infoboxes are very popular.
I am however not too sure that the two million links to Template:Wikiproject Biography on the Talk namespace actually corresponds to two million unique biographies.
Maybe another way of getting this data would be better, I'll have to look at it on some other occasion that I have more time.
Milo8505 (talk) 11:28, 20 November 2024 (UTC)[reply]
I looked at the first 10 articles in Category:Core biography articles, and 100% had infoboxes. However, those ten articles used seven different infoboxes:
Category:People and person infobox templates lists dozens. WhatamIdoing (talk) 23:22, 21 November 2024 (UTC)[reply]
Yes! Yes!
That's my point. Most[citation needed] good biographies have an infobox - except those of classical composers.
I will look at the category you mentioned and try to count from there.
Thank you very much! Milo8505 (talk) 16:46, 22 November 2024 (UTC)[reply]
The problem is, there still exist editors who strongly dislike infoboxes on most biographies -- me for one. When one writes every word of an article and then someone, who has not otherwise contributed, comes and adds an infobox it can be ... annoying. The basic use tends to highlight bits of trivial information (birth & death dates/places, nationality, spouse, children) that are not usually key to the person's notability. Even more contentious can be trying to define what a person's key contributions are, in a half-sentence. For some this is easy, and an infobox might be a good way of presenting the data, for others (including many classical composers) not so much. It can be hard enough to write a lead that presents this in a balanced fashion in a paragraph or three.
Are all good biographies written by groups? I'm not sure; probably the best are, but there are many many biographies of minor figures where 99.9% of the text was contributed by a single author, some of which are fairly well developed. Espresso Addict (talk) 05:05, 28 November 2024 (UTC)[reply]
I'm thankful for your contributions, but I'm sorry that you don't WP:OWN any article, and you can't dismiss someone else improving the article you wrote because you wrote it and you don't personally agree with the contributions made.
That said, it may be difficult to summarize why someone is important in a phrase, but it's not impossible, and, IMO actually something that should be done, as it makes the article easier (and faster) to scan. Milo8505 (talk) 09:39, 28 November 2024 (UTC)[reply]
What I am obviously failing to convey is that some editors write articles, far fewer than those who contribute in other ways, and some of those dislike the "improving" addition of an infobox by another editor who makes no other edits, improving or otherwise. Espresso Addict (talk) 10:40, 28 November 2024 (UTC)[reply]
Why is that relevant? Nobody owns an article, regardless of in which why they contribute to Wikipedia. Just because some editors dislike something does not give them a veto over things that the majority of other editors believe does improve the article. Obviously an infobox with incorrect information is not an improvement but that doesn't mean an infobox with correct information is not an improvement. In exactly the same way as a paragraph with incorrect information about an aspect of the article subject is a bad addition, this does not mean that a paragraph with correct information about that same aspect is bad. Thryduulf (talk) 11:55, 28 November 2024 (UTC)[reply]
It seems to me a great deal more like reference format and English variant. It could easily be argued that we should have standardised on US spelling and picked a mode of referencing, but we never did because it would alienate too much of the workforce. Espresso Addict (talk) 12:55, 28 November 2024 (UTC)[reply]
It's not even close to being like ENGVAR or reference formatting. Those are stylistic decisions where there are multiple equally valid choices that don't impact content. Infoboxes are a content decision where one choice directly benefits the readership and one choice placates the dislikes of a minority of editors. Thryduulf (talk) 16:40, 28 November 2024 (UTC)[reply]
Load up the Good Faith, Thryduulf :D another phrasing, less pejorative or sweeping, might be Infoboxes are a content decision where either choice directly affects the readers' preconceptions of the topic. Tight faded male arse. Decadence and anarchy. A certain style. Smile. 16:47, 28 November 2024 (UTC)[reply]
It may or may not be less pejorative or sweeping, but it is also less accurate. Thryduulf (talk) 18:24, 28 November 2024 (UTC)[reply]
Case in point Jacqueline Stieger, where the box I've just removed (1) highlighted her place of birth Wimbledon and nationality British, which -- for someone with two Swiss parents, who was brought up in Yorkshire, did some of her notable work in France/Switzerland with her Swiss husband and then settled back in Yorkshire with her Swiss stepchildren -- is undue; and (2) copied "artist and sculptor" from the beginning of the capsule, while not paying heed to the fact her notable works predominantly fall into two groups, big architectural sculptures mainly in metal, and jewellery/art medals. Espresso Addict (talk) 05:52, 28 November 2024 (UTC)[reply]
X thing is bad, because once, some time ago, I saw an instance of X and it was bad, really really bad, as a matter of fact. Milo8505 (talk) 09:42, 28 November 2024 (UTC)[reply]
Well sure, but I just looked down my list of created bios by date till I found the first to which someone had added an infobox. I didn't drag out my historical collection of badly added infoboxes including those that had been cut-and-pasted wholesale from another article without changing any of the data, and those that introduced errors in the dates. Espresso Addict (talk) 10:40, 28 November 2024 (UTC)[reply]

Should WP:CRYSTAL be clarified?

[edit]

The article 2028 United States presidential election was proposed for deletion several times (last one). Editors repeatedly cited WP:CRYSTAL, which reads

If preparation for the event is not already in progress, speculation about it must be well documented. Examples of appropriate topics include the [[{{#expr: {{CURRENTYEAR}} + 4 + ({{CURRENTYEAR}} * -1)mod4 }} United States presidential election|{{#expr: {{CURRENTYEAR}} + 4 + ({{CURRENTYEAR}} * -1)mod4 }} U.S. presidential election]] and [[{{#expr: {{CURRENTYEAR}} + (2*4) - ({{CURRENTYEAR}}mod4)}} Summer Olympics]]. By comparison, the [[{{#expr: {{CURRENTYEAR}} + (5*4) + ({{CURRENTYEAR}} * -1)mod4 }} United States presidential election|{{#expr: {{CURRENTYEAR}} + (5*4) + ({{CURRENTYEAR}} * -1)mod4 }} U.S. presidential election]] and [[{{#expr: {{CURRENTYEAR}} + (6*4) - ({{CURRENTYEAR}}mod4)}} Summer Olympics]] are not appropriate article topics if nothing can be said about them that is verifiable and not original research.

According to this, the 2028 election and 2032 Olympics automatically became valid articles on January 1, 2024, although it is not really clear why that exact date matters. Should this be clarified, and if so, how? ypn^2 19:44, 18 November 2024 (UTC)[reply]

The relevant question IMO is why do we need an article on the 2028 or 2032 presidential elections? Any "significant coverage" is just speculation at this point. Until candidates declare, I don't see how articles on either is useful to readers. voorts (talk/contributions) 19:53, 18 November 2024 (UTC)[reply]
Encyclopaedic coverage of predictions and speculation about and preparations for the 2028 presidential election that appear in reliable sources is possible and (in at least some cases) due. Similarly things like whether (and if so what) changes to electoral collage allocations will happen, etc should also be easily found by someone searching. Whether that should be on its own article yet or as part of a broader article will depend entirely on the volume of encyclopaedic material there is. Similarly for the Olympics. As soon as we have coverage about the next and next+1 US presidential elections and Olympic games there should be blue links from the titles those articles will reside at when they have articles (e.g. 2036 Summer Olympics was kept at AfD (although moved to Bids for the 2036 Summer Olympics) in November 2022 due to there being significant sourcing about the preparations). I don't think the dates in WP:CRYSTAL should be taken as "there must be an article" but as loose guidelines along the lines of "significantly before this time sufficient information to justify a standalone article is unlikely; it is unlikely there will not be sufficient information for a standalone article significantly after this time." i.e. those dates are the approximate midpoint in the range when sufficient information for a standlone article existing changes from very unlikely to very likely. Thryduulf (talk) 20:36, 18 November 2024 (UTC)[reply]

Please see subject RfC. Cinderella157 (talk) 22:19, 18 November 2024 (UTC)[reply]

We need to fix the admin recall process

[edit]

Right now only "recall" votes count, and those opposing recall don't count for anything, nor do any points made in the discussion. So 25 quick group-think / mob thumbs-down votes and even be best admmin can get booted. And the best (= the most active) are the ones most likely to get booted. An admin that does near zero will get zero votes to recall. And with a single regular RFA currently the only way back in (which we've seen, very few want to go through) "booted" is "booted". The fix would be to have a discussion period pror to voting, with both "recall" and "don't recall" choices. And then say that the recall has occurred (thus requiring rfa) if over 50% or 60% of those voting said "recall".

Sincerely, North8000 (talk) 20:40, 19 November 2024 (UTC)[reply]

@North8000 Please see Wikipedia:Administrator recall/Reworkshop, where editors are already discussing potential changes. Sam Walton (talk) 20:43, 19 November 2024 (UTC)[reply]
Thanks. I looked for something like that but I guess I didn't look hard enough. I hope others look harder than me. :-) North8000 (talk) 21:58, 19 November 2024 (UTC)[reply]
I don't think you understand how recall works. An admin is only desysopped after the RRFA, not after the 25 signatures, unless they choose to resign on their own. You're asking to hold a vote on whether or not a vote should be held. ~~ Jessintime (talk) 20:55, 19 November 2024 (UTC)[reply]
Yes, I understood that and that is integrated into my comment above. Unless they go through and succeed at an RFA they are gone. North8000 (talk) 21:54, 19 November 2024 (UTC)[reply]
I've never heard of a petition that lets people sign because they don't support it. And I'll add that between the two recall petitions that were enacted to this point, both were preceded by many, many attempts to get the admin to correct course over the years despite egregious misconduct. Thebiguglyalien (talk) 21:03, 19 November 2024 (UTC)[reply]
I'm not talking about any particular cases. Sincerely, North8000 (talk) 21:56, 19 November 2024 (UTC)[reply]
So, the premise of your argument is pure conjecture? Regards, Goldsztajn (talk) 22:05, 19 November 2024 (UTC)[reply]
???? It was from an analysis of it's current structure. North8000 (talk) 14:10, 20 November 2024 (UTC)[reply]
But you've just refused to engage in a discussion with how the structure has actually worked in practice; hence, conjecture. Regards, Goldsztajn (talk) 00:19, 21 November 2024 (UTC)[reply]
The process at the moment does have a certain level of redundancy, with the recall and reconfirmation RFA being separate things. The reconfirmation RFA is even a standard RFA, as it has different criteria for success.
I'm not sure if anything should be done yet, as it's still very early in its adoption. However if the situation occurs that a petition is successful but the reconfirmation RFA SNOWs, it could indicate that adjustments needs to be made so that community time isn't wasted. That speculative at the moment though. -- LCU ActivelyDisinterested «@» °∆t° 23:53, 19 November 2024 (UTC)[reply]
The recall petition threshold is not the recall discussion - it is just a check to prevent the most frivolous recall discussions from being held. — xaosflux Talk 00:56, 20 November 2024 (UTC)[reply]
+1 Goldsztajn (talk) 06:54, 20 November 2024 (UTC)[reply]
The optics of this look alltogether terrible from my observation. I don't edit much, but I like reading a lot. Every criticism of the recall process i've seen so far just looks like old established admins thinking they might be next and having anxiety about that.
The problem of something like this is that the optics are terrible. If anyone who doesn't know you reads that, the conclusion they will draw will likely not be "this recall process is terrible" and more likely go along the lines of "wow this is a lot of admins who don't have the community's trust anymore and want to dodge accountability".
By being so vocally against any form of community led accountability, you're strenghtening the case for easy recalls and low thresholds, not weakening it.
Specifically regarding Fastily, I'll make no comment on whether or not he deserves to still be an admin or not, I don't know him well enough for that and haven't reviewed enough of his contributions, but the arguments of "ANI agreed that no sanctions were appropriate" sound a lot like "our police department has investigated itself and found nothing was wrong". You have to see how this comes across, it's eroding trust in Admins on the whole project right now. Magisch talk to me 09:24, 20 November 2024 (UTC)[reply]
Specifically, if RFA is so toxic that nobody wants to do it, that needs to be reformed. But the recent amount of vitriol towards a process that only kickstarts having to prove that you retain community trust has me convinced that there should be automatic mandatory RRFAs for every admin every 2 years or so.
If, as of today, you don't believe the community would entrust you with admin tools, why do you think you should still have them? The criteria for losing them should not be "has clearly abused them", it should be "wouldn't be trusted with them if asked today". Magisch talk to me 09:33, 20 November 2024 (UTC)[reply]
As an admin actively working to improve the recall process, my goal is to make it as fair as possible to all parties. That means it should not be possible to subject an admin to the process frivolously while equally making it possible to recall administrators who have lost the trust of the community, and it needs to be as non-toxic as possible, because even administrators who are actively abusing their tools are people and nobody deserves 1-2 months of abuse. It's also incorrect to describe ANI as a police department investigating itself - everybody engaging in good faith is welcome to comment there, regardless of whether they are an admin or not. Thryduulf (talk) 11:15, 20 November 2024 (UTC)[reply]
@Thryduulf It's the Administrator's Noticeboard, naturally the vast majority of participants will be either admins or people who are involved in the same work.
I don't think asking an admin to confirm they still retain the trust of the community (the whole basis of giving out admin tools to begin with) is ever really frivolous. The current process allows that at most once a year. If an admin had to stand for RFA every year, that might be a bit too much long term, but really, if any admin thinks they would not pass RRFA today, why should they retain their tools.
Also, the sheer optics of it being mostly (from what i've seen) established admins calling this process toxic are terrible. Anyone who doesn't know anything about this process will see this as some kind of thin blue line mentality in the admin corps - and might conclude that it is time to desysop the majority of old admins to dissolve the clique.
I wouldn't be surprised if we see a bunch of recall petitions for the most vocal critics of this process. Magisch talk to me 11:27, 20 November 2024 (UTC)[reply]
I have no horse in this race, except that I regret not seeing the RFA earlier so I could have voted Support, sorry about that.
But if your argument is optics, then having a bunch of recall petitions for the people who most vocally expressed a valid opinion on an evolving policy is absolutely awful optics. At best. Gnomingstuff (talk) 01:33, 22 November 2024 (UTC)[reply]
I took the stats from the first RRfA to test this theory:
1st RRfA votes
Support Oppose Total
Administrators 48 29 77
Non-admins 71 116 187
Total 119 145 264
Administrators made up 29% of the voters. If being an admin doesn't influence anyone's vote, then we can expect admins to make up roughly 29% of the supporters and 29% of the opposers. But this didn't happen. In the final results, administrators made up 40% of the supporters and 20% of the opposers. We can also look at the individual odds of supporting/opposing depending on user rights. It ended at 45% support, so you'd expect admins to have a 45% chance of supporting and a 55% chance of opposing. But this also didn't happen. If you choose any admin at random, they had a 62% chance of supporting and a 38% chance of opposing (ignoring neutrals). Non-admins were the opposite: they had a 38% chance of supporting and a 62% chance of opposing.
So our next question should be why it was so much more likely for an admin to support the RRfA relative to a non-admin. The obvious answer is of course as you said: admins have a perverse incentive to support here, especially if they're not-so-great admins who know they probably don't have the trust of the community anymore. Also suggested during the RRfA is the comradery that comes from working alongside a fellow admin for so long. I'd be interested in seeing how account age affects likelihood of supporting, but that's not something that can be counted up in a few minutes like admin status. Thebiguglyalien (talk) 17:48, 20 November 2024 (UTC)[reply]
I believe it may be centered on the idea that we all make mistakes, and many of us like to think we'd be given a chance to grow and learn from said mistake, instead of being forced through the RfA process again. But I recognize I may be being overly optimistic on that, and that others may not have the same thoughts on the matter that I do. Many admins I've spoken to would simply choose to give up their tools as opposed to go through an RfA again, something I've also considered despite my relatively smooth RfA. I'm also not sure Graham is the best representation of that. I voted support, recognizing that Graham87 has made mistakes, but also recognizing the significant contributions they've made and their pledge to do better. Bluntly, I did so expecting the vote to fail, and wanting to show some moral support and appreciation for their work. There's certainly a psychological aspect involved in it, but I don't think that, generally speaking, those of us who voted support or have issues with the current process are doing so out of self preservation.
There's a lot of numbers that could be analyzed, such as the history of those admins who vote at RfA (whether they often vote support or don't vote at all), but it's hard to draw meaningful conclusions from this small of a dataset. Hey man im josh (talk) 19:14, 20 November 2024 (UTC)[reply]
On paper, I get that. The thing is, I don't know whether you saw Levivich's comment or bradv's comment, but you'd be hard-pressed to find a less appropriate time to test the "chance to grow" theory than the absolutely deplorable behavior that we saw from Graham for many years with far too many chances to improve. If it were down to me, this should have been a block in 2023 rather than a desysop in 2024. Thebiguglyalien (talk) 19:32, 20 November 2024 (UTC)[reply]
I'm late to the discussion, but I think it's also worth pointing that only 7 of the 25 users who signed Graham87's petition and 2 of the 25 on Fastily's were admins. ~~ Jessintime (talk) 13:16, 23 November 2024 (UTC)[reply]
I would add that there is a potential wrinkle in this analysis. I'm an extended-confirmed user here (and thus would likely be counted as a non-admin), but I am a sysop on Commons so I would have my own perspective on the matter. Abzeronow (talk) 21:06, 22 November 2024 (UTC)[reply]
Well, I'm not an admin and I started this thread. I'm all for having an admin recall process by the community in place. I'm also also for a process for course correction by the community in areas where and admin has drifted off course but where the problem is fixable. Administrative Action Review has the potential to become this but that has been stymied by various things. Sincerely, North8000 (talk) 14:24, 20 November 2024 (UTC)[reply]
I think, fundamentally, the problem is that admins have a direct and concrete conflict of interest in this discussion. Of course an admin would be naturally opposed to more mechanisms that might make them lose their permissions, especially since desysops are very rare at the moment.
I also don't really agree that the current recall process is all that toxic. You could get rid of the discussion section, as the recall is only a petition, not a consensus discussion, but that's about it. Magisch talk to me 18:33, 20 November 2024 (UTC)[reply]
Of course an admin would be naturally opposed to more mechanisms that might make them lose their permissions – I wholeheartedly disagree with this assertion. There's a number of us that fully support a recall process, including quite a few people who have historically been open to recalls. This is an over simplification of the motives of a large group of experienced editors, many of which have legitimate and reasonable concerns about the process in its current form. Hey man im josh (talk) 19:15, 20 November 2024 (UTC)[reply]
Substantially all criticism i've seen so far of the process have boiled down to "RFA is abusive and it's unreasonable to make people go through that again". And yet, instead of attempting to change that, the only suggestions seem to be to support older admin's rights to have their permissions continue being grandfathered in. Magisch talk to me 19:27, 20 November 2024 (UTC)[reply]
I'm sorry that that's all you've taken away from the vast amounts of criticism given by people. Perhaps consider focusing on whether the process, in its current state, makes sense instead of focusing on older admins. I'm a relatively new admin and I don't support the current iteration of the process. Hey man im josh (talk) 19:30, 20 November 2024 (UTC)[reply]
I think it's eminently sensible to have adminship not be a lifetime appointment, both by the fact that norms change even when people dont, and that I see people in every RFA expressing reluctance over granting lifetime tools. I also think that assuming RFA isn't a big deal regular reconfirmations make sense. IFF RFA is a big deal, then the focus should be on fixing that.
It seems to me that existing admins being immune to having to suffer RFA again has created a lack of pressure to actually make it into a functional, nontoxic process.
Take my opinion for what it's worth though. I'm not an admin nor do I foresee myself ever having aspirations to become one. Magisch talk to me 19:43, 20 November 2024 (UTC)[reply]
Attempting to improve RFA is a very hard problem that people have been working on since before you joined Wikipedia, and are still working on it. I would also say that it is unreasonable to make people go through that again is a mischaracterisation of the views expressed, which are it is unreasonable to make people go through that again unnecessarily, which is significantly different. Thryduulf (talk) 19:31, 20 November 2024 (UTC)[reply]
I just found out about this discussion, and it looks to me like the same or similar things are being discussed in way too many different places. Anyway, I'm someone who has stated repeatedly and strongly in multiple places that I think the recall process is a disaster, and is beyond repair. And, contra some statements above, here are some other facts about me. I'm not an admin. I opposed Graham's re-RfA. And I played a central role in WP:CDARFC. --Tryptofish (talk) 20:12, 20 November 2024 (UTC)[reply]
I would be against it for a different reason: if we allow both supports and opposes, then the recall petition becomes a mini-RfA with the same amount of pressure as the RRfA itself (especially since, given the identical threshold, the recall's result would be indicative of the RRfA's subsequent result). Since anyone can start the recall petition, it functionally means that anyone can force an admin to re-RfA, which is clearly worse.
On the other hand, having a set number of supports needed provides for a "thresholding" of who can open a RRfA, while not necessarily being as stressful. If anything, I would say the recall should become more petition-like (and thus less stressful for the recalled admin), rather than more RfA-like. Chaotic Enby (talk · contribs) 20:01, 20 November 2024 (UTC)[reply]
The ones most likely to be booted are bad admins who are abusive toward the editor community and who negatively represent themselves as admins. Both of the recalls thus far were just exact examples of that and worked perfectly as designed and needed. The process worked exactly as desired and removed bad admins who deserved to be desysopped. Though I do think the discussion section of the petitions should be more regulated. Discussion should be about the admin's actions and conduct and nothing else. Any extraneous commentary should be removed. SilverserenC 00:23, 21 November 2024 (UTC)[reply]
When I first started editing Wikipedia almost 20 years ago, I was struck by what, to me at least, appeared to be widespread incivility. Among a number of things which have changed for the better IMHO is an all round expectation that everyone's standards of behaviour should rise (and they have). The admin role breeds a certain "culture" (for lack of a better term) akin to a conservationist, the role is to "protect" Wikipedia from "harm" and I can certainly see why being an admin could be a deeply frustrating experience. However, what has happened, I think, in the attrition of the admin corps, and the turnover in the non-admin corps, is that the generalised culture of "regular" non-admin editors has moved further forward towards less acceptance of a culture prevalent 10-15 years ago. I think also the rise in editors from non-English speaking backgrounds and from the Global South has caused complexities for those with limited experience outside the anglosphere. The statistics above on the vote for G87's RRFA show an interesting split between admins and non-admins, and within admins. Non-admins were almost overwhelmingly (close to 2/3) of the view that G87 had been given an almost exceptionaly long period to improve, had not, and no longer held their trust. 5/8s of admins, appeared (and comments here also seem to confirm this) split between solidarity for one of their own and displeasure with the recall process. 3/8s admins were in alignment with the majority of non-admins. FWIW, I'm not trying to point to some grand schism; A 38/62 admin split on these numbers is not that profound - if just 9 admins had changed their vote from support to oppose it would have been a 50/50 split. To reiterate, I'm not suggesting that there is a great gap between admins and non-admins, but there does appear to be some gap when it comes to generalised views around the expected behaviour of admins. Regards, Goldsztajn (talk) 01:01, 21 November 2024 (UTC)[reply]
Maybe the divide is not between admins and non-admins but between newer and longer-serving editors (who are more likely to be admins)? Hawkeye7 (discuss) 01:20, 21 November 2024 (UTC)[reply]
I don't disagree, and in effect I was sort of saying the same thing in terms of the attrition of the admin corps and turnover in non-admin corps. FWIW, I do think there are some generalised feelings about admins among non-admins; for example, admins are less likely to face sanction than non-admins. How true that actually is I'm not sure and the point would be that a group of people already tested in commnuity trust (ie RFA) are less likely to breach that trust. However, comments in the G87 RRFA and the strength of the vote suggest there are (wrongly or rightly) widely felt perceptions of disparity. Regards, Goldsztajn (talk) 01:53, 21 November 2024 (UTC)[reply]
I'm currently compiling the data to get some statistics about voters in Graham's re-RFA. I'm a bit less than halfway through so it might be a couple of days before I can present any results. However among the first 113 support voters the maximum account age (on the day the re-RFA started) was 7919 days (21 years), the minimum was 212 days and the average was 4785 days (13 years). I have no data yet for neutral or oppose voters so cannot say how that compares. Thryduulf (talk) 02:03, 21 November 2024 (UTC)[reply]
Do you have a handy list of all voters for RFA? It should be simple enough to use a WP:QUARRY to find out all details about the voters if someone finds an easy enough scrape of who each user is Soni (talk) 05:51, 21 November 2024 (UTC)[reply]
@Soni: [2]. Levivich (talk) 07:09, 21 November 2024 (UTC)[reply]
Here's the Quarry query editcount/registration date for Supports, Neutrals, Opposes.
I think about 6 editors were missed by the tool you linked, but it should not change overall patterns much so we can just use this as is. Soni (talk) 07:24, 21 November 2024 (UTC)[reply]
Prepare to not be surprised. Supporters/Opposers:
  • Median registration date 2008/2014 <-- Behold, Wikipedia's generational shift
  • Average registration date: 2011/2014
  • Median edit count: 40,293/17,363
  • Average edit count: 76,125/43,683
Thanks for doing the quarry. Teamwork makes the dream work! Levivich (talk) 05:17, 22 November 2024 (UTC)[reply]
At a quick glance, it seemed like editors with more edits were more likely to support while editors with fewer edits (with one exception) were more likely to oppose. - Enos733 (talk) 07:54, 21 November 2024 (UTC)[reply]
Given a single admin action may involve multiple edits, it's not so surprising the supporters' list possibly reflects a group with higher edit counts. Personally, I'd be more inclined to draw conclusions from length of registration rather than edit count. Regards, Goldsztajn (talk) 09:11, 21 November 2024 (UTC)[reply]
my very, very rapid count - supports 35/117 (30%) less than 10 years old, opposes 67/141 (48%) less than 10 years old. In absolute numbers, 10+ year accounts were 82 supports, 74 opposes - actually quite even. What was crucial was younger accounts. It does confirm my sense of gaps between "older" and "younger" generations in regard to perceptions of tolerable admin behaviour. Regards, Goldsztajn (talk) 09:50, 21 November 2024 (UTC)[reply]

We have had two recalls as of now. The people signing the recall were by and large not trolls, vandals, people blocked by that admin, ... but regular editors in good standing and without a grudge. One of these recalls has been supported by the RRFA afterwards, and the other admin decided not to go for a RRFA. There is zero evidence that the process is flawed or leads to results not wanted by the community at large. While minor issues need working out (things like "should it be closed immediately the moment it reaches 25 votes or not"), the basic principles and method have so far not produced any reason to fundamentally "fix" the issue. That the process highlights a gap between parts of the community (see e.g. the Graham RRFA) doesn't mean that the process needs fixing. The process only would need fundamental fixing if we would get successful recalls which would then be overwhelmingly reversed at RRFA, showing that the recall was frivolous, malicious, way too easy... Not now though. Fram (talk) 09:24, 22 November 2024 (UTC)[reply]

I agree with Fram. There is not any evidence that the recall process is reaching outcomes that are not supported by the Community (I voted Oppose on the Graham RRFA; I don't know how I would have voted on a Fastily RRFA). Small fixes to the process if supported would not be indicative of the process itself being fundamentally flawed. Abzeronow (talk) 21:15, 22 November 2024 (UTC)[reply]
I agree that it just needs fixes.North8000 (talk) 15:24, 23 November 2024 (UTC)[reply]

I believe that desysoppings for cause should only happen when there is objective evidence of misconduct. My main concern about the recall process is that it may be wielded against administrators who are willing to take actions that are controversial, yet necessary. Examples of actions that have got administrators hounded include (1) closing contentious and politically charged AFD discussions; (2) blocking an "WP:UNBLOCKABLE" editor who is being disruptive or making personal attacks; (3) stepping up to protect a politically charged article to stop an edit war. None of these actions are administrator misconduct, but in a heated dispute the side that has an admin rule in their disfavor may quickly resort to punishing said administrator by starting a recall petition, and in a dispute involving many editors, getting to 25 may be easy. Even if that petition fails, it is so unpleasant that it may have a chilling effect on admin involvement even when needed. Sjakkalle (Check!) 21:14, 23 November 2024 (UTC)[reply]

In which case, a RRFA might be overwhelmingly in favor of the administrator and thus vindicate the administrator. I would definitely vote in support of an administrator if those any of those three were the impetus behind a recall. I also trust our editors, and so far, the recall process has worked as intended. Abzeronow (talk) 21:50, 23 November 2024 (UTC)[reply]
ArbCom have to face re-election. Does that have a chilling effect on the arbitrators? Hawkeye7 (discuss) 21:48, 23 November 2024 (UTC)[reply]
That's a facile argument. Arbitrators are well aware that they are standing for a fixed term period. Black Kite (talk) 21:50, 23 November 2024 (UTC)[reply]
It's driving me up the wall that people keep saying that the process has worked as intended. Come back and tell me that, after you can link to an RRfA for Fastily that resulted in whatever result you define as working as intended. --Tryptofish (talk) 22:01, 23 November 2024 (UTC)[reply]
Choosing not to do an RRfA was their own choice, particularly if Fastily thought it wouldn't be successful. It was also their choice to make no attempt whatsoever to defend the reams of evidence presented against them in the recall petition of their negative actions toward the editing community. So, yes, Fastily as well was an example of the process working as intended. SilverserenC 22:08, 23 November 2024 (UTC)[reply]
Or perhaps they just thought "well, I've put XX years into this and a load of random people with rationales ranging from reasonable to utterly non-existent have told me I'm not fit to do it, so f*** you". If that's the case, I don't blame them. Black Kite (talk) 22:13, 23 November 2024 (UTC)[reply]
Maybe, maybe not. Probably not though right? Seems kind of silly. PackMecEng (talk) 22:17, 23 November 2024 (UTC)[reply]
I suspect that might be my reaction, to be honest. Black Kite (talk) 22:24, 23 November 2024 (UTC)[reply]
He was going to lose if he didn't apologize, and he didn't want to apologize. That simple. As others have said, that was his choice to make, and I respect it. Levivich (talk) 22:28, 23 November 2024 (UTC)[reply]
Except that he did apologize, although there were differing views of whether that apology was enough. This oversimplification is what's wrong with the way discussions happen in this process. --Tryptofish (talk) 22:34, 23 November 2024 (UTC)[reply]
He woulda had to apologize more, then, including for the stuff that came out during the petition, and any other stuff that may have come out during the RRfA. He woulda had to answer questions about it, make promises, etc., basically go through what Graham went through, and realize that even that (answering questions, making promises) might not be enough (as it wasn't for Graham). It's not at all irrational for someone to choose not go through that. Being an admin isn't worth all that to some (e.g., to me), especially if you might not get it despite your best efforts. Levivich (talk) 22:44, 23 November 2024 (UTC)[reply]
"Someone decided that it just isn't worth it" does not equal "the process worked". --Tryptofish (talk) 22:47, 23 November 2024 (UTC)[reply]
No, those two things are not the same. If you want to know why I think the process worked, it's because it stopped disruption, did it faster than Arbcom, and I think with less drama (though admittedly the third one is purely subjective and speculative). Levivich (talk) 22:56, 23 November 2024 (UTC)[reply]
Um, thanks for sharing? --Tryptofish (talk) 23:06, 23 November 2024 (UTC)[reply]
On the petition page, I conducted a careful analysis of the evidence. Nobody refuted what I said there. --Tryptofish (talk) 22:15, 23 November 2024 (UTC)[reply]
Linking might help though. It doesn't seem to be on Wikipedia talk:Administrator recall/Graham87, Wikipedia talk:Administrator recall/Fastily, or on Wikipedia talk:Administrator recall, so it's a bit hard to know what "the petition page" is. Do you mean your 00:39, 13 November 2024 (UTC) reply to A smart kitten? The one that ended with "Does this rise to the level of requiring, for me, a desysop? I'm leaning towards no." And others leaned towards "yes", it's not as if people couldn't draw different conclusions from your post or could disagree with things you said without actually replying directly to you. You didn't contradict the evidence, you personally didn't find it severe or convincing enough, that's all. That doesn't show that the process needs fixing though, just because enough people disagreed with your opinion and the result wasn't put to the test. Fram (talk) 09:28, 25 November 2024 (UTC)[reply]
Fram, the context of what I said was clearer before there were all those intervening edits, but yes, you correctly identified the post I meant as the one that ended with the words that you quoted. Here's the diff: [3]. From where I'm sitting, your analysis here of how people reacted to what I posted is, well, not convincing enough. There was a lot of discussion about the evidence that I analyzed, back and forth. When the editor (A smart kitten) who originally posted the evidence came back with the additional information that I requested, the discussion was still very active. I provided a very detailed examination, point-by-point, of each individual claim made in that evidence. Yes, it was based upon my opinions, but I drew specific conclusions, and justified those conclusions. And nobody came back and said that they thought anything in my analysis was incorrect, nor did anyone who signed on the basis of that evidence before my comment come back and reaffirm their signature, rejecting my analysis. If you think somebody actually did, you can provide a diff of it, but I can assure you that you won't find one. And that wasn't because the petition discussion had come to a close, because it continued for several more days after I posted that. After a whole lot of back-and-forth about that particular evidence, nobody said that they found errors in anything that I said. But a couple more editors did sign the petition after that, with brief comments saying, in some cases, that they decided to sign after reading that particular evidence.
So the question, in the light of your comment to me, becomes whether those later signers did so because they carefully read all of the discussion, including my critique, and decided to sign, implicitly having decided that my critique was unconvincing – or whether they signed after only a superficial read and had never really engaged with my critique. I cannot prove that it was the latter, and you cannot prove that it was the former. But given that their signatures came only with brief comments, and nobody found reason to actually mention that they had rejected my critique, I'm pretty skeptical of the former. And that's a problem. The petition process does not, of course, require that anyone had to say explicitly that they disagreed with me, either, but that's a shortcoming of the discussion process. A desysop via ArbCom makes room for careful examination of the facts. The petition did not. This is a half-assed way of driving someone off Wikipedia. And I'm arguing for a more deliberative process. --Tryptofish (talk) 18:55, 25 November 2024 (UTC)[reply]
  • I have to say I don’t get the recall process either. I support admin accountability but just having an arbitrary number of “support” votes, no “oppose” votes, and I guess a time limit instead of consensus forming seems… extremely weird and out of step with how virtually everything else is done on Enwiki. Dronebogus (talk) 10:56, 24 November 2024 (UTC)[reply]
    The intended point of the recall petition is not to find consensus or to determine whether the admin has lost the trust of the community, has abused the tools or anything like that. The intended point of the petition is only to prove that a re-RFA is not frivolous. The Re-RFA is where consensus is formed from support and oppose, analysis of evidence, etc. Think of it in judicial terms, the petition is at the pre-trial stage and simply aims to answer the question "are there 25 people who think there is a case to answer?" if the answer is no, then it ends there. If the answer is yes, then you can please innocent or guilty. If you plead guilty you take the sentence (desysopping) and move on. If you plead innocent there is a trial and the jury finds you either innocent or guilty by majority verdict. This is an imperfect analogy of course, but it hopefully helps explain the concept.
    It didn't work like that in either of the two that we've had, but that's a fault with the implementation not with the concept. Thryduulf (talk) 12:57, 24 November 2024 (UTC)[reply]
    The problem is, the concept itself makes no sense. Nearly everything on Wikipedia is decided one of three ways: consensus democracy that must be approved/vetoed by an admin (most non-trivial issues); WP:BOLD editing, informal discussion, or admin fiat (trivial issues); or arbitration (extreme fringe cases). This resembles none of those. It’s like arbitration, only everyone can be an arb, and instead of voting yay or nay to take the case you collect signatures to see if there’s general support for a case? Dronebogus (talk) 13:11, 24 November 2024 (UTC)[reply]
    The request stage of arbitration is the closest analogy, but it is indeed a process not used anywhere else on Wikipedia. That doesn't mean it doesn't make sense. It's sole purpose is intended to be a check against frivolous requests so that an admin doesn't have to go through re-RFA just because they pissed off a single editor once by making an objectively correct decision. The actual decision is intended to made by consensus democracy at the Re-RFA. Thryduulf (talk) 13:33, 24 November 2024 (UTC)[reply]
    I think a limited vote based on a formula like “after 7 days a minimum of 2/3rds of people must support for re-RFA” would be less opaque than trying to start a Wiki-Minyan? Dronebogus (talk) 09:26, 25 November 2024 (UTC)[reply]
    That sounds like skipping the petition, and going right to the RRFA, or running two successive RRFA's. I have not been involved in any of this but it is not really hard to understand why there is the two-step process of: 1) calling the question, and 2) deciding the issue. Alanscottwalker (talk) 11:52, 25 November 2024 (UTC)[reply]
    Honestly I think it should just go straight to RRFA, and if there’s enough opposition fast enough it can just be WP:SNOW closed. We don’t, for example, ask for 25 signatures to start and AfD discussion in order to weed out frivolous nominations— it’s patently obvious when a nomination is garbage in most cases. RRFA is clearly a last resort, and no established, good faith user is likely to abuse this kind of process so egregiously we need a two-step failsafe. Dronebogus (talk) 12:03, 25 November 2024 (UTC)[reply]
    In other words any user should be able to start a binding RRFA on any admin at any time? No, no thank you... – Joe (talk) 12:16, 25 November 2024 (UTC)[reply]
    Not any time, there should be a policy that steps must already been taken and failed, ideally multiple times, similar to ArbCom. And not any user, since the starter should probably be autoconfirmed at the absolute minimum, and probably be required to be in goof standing, have X edits, been on WP X years, and been active during the last year. If it was unambiguously required that an RRFA follow these rules or be rejected (with filing an improper case being a sanctionable offense) I don’t think anyone would realistically start a frivolous case. Dronebogus (talk) 12:33, 25 November 2024 (UTC)[reply]
    Well, we also don't require a !vote to create an article but we do for an admin. I also don't think it is likely that 'any experienced user' has experience in making an RRFA -- Alanscottwalker (talk) 12:34, 25 November 2024 (UTC)[reply]
    An admin is essentially just voted into office; they should be voted out of office in an identical way. There’s no need for some kind of novel additional process on top of that. That’s all I’m saying. Dronebogus (talk) 12:55, 25 November 2024 (UTC)[reply]
I think the basic complaint here is that the 25-vote threshold is too easy to meet, and therefore it is unfair to require an affirmative consensus for the admin to retain the tools. I think the 25-vote threshold is fine for weeding out frivolous nominations, but correspondingly I think we should make it harder to remove adminship, i.e. make 50-60% the discretionary range for removing adminship. This would make it in line with most of our other processes, where a slight supermajority is required to make changes, and no consensus defaults to the status quo. Whereas under the current recall system, 25 votes with no opportunity to object are enough to make removal of adminship the status quo, which seems a bit harsh. -- King of ♥ 19:53, 25 November 2024 (UTC)[reply]
I think the 25-vote threshold, because it’s so easy to meet, is essentially pointless because it will only weed out extreme outlier cases that I don’t believe will ever happen enough to be a serious concern. We should just have a supermajority vote requirement, and if we must have a petition it should be a lot higher than 25. Dronebogus (talk) 16:06, 27 November 2024 (UTC)[reply]
We don't have evidence the 25-vote threshold is easy to meet. Of the two recalls, one only hit 25 due to a bad block during the petition period. CMD (talk) 16:14, 27 November 2024 (UTC)[reply]
One more reason I don’t like this: it’s extremely important, but we’re using it to prototype this weird system not used anywhere else on Enwiki and possibly Wikimedia (if you have examples of off-wiki precedent please share them). Dronebogus (talk) 16:18, 27 November 2024 (UTC)[reply]
Have to try new things at some point. But CMD is right, from all the evidence we do have, it looks about right. Where as there is zero evidence that a higher number is required or helpful. PackMecEng (talk) 17:09, 27 November 2024 (UTC)[reply]
It's usually called Approval voting when it's used, though that might not be precisely the right name. It's used all over the Wikimedia movement. At least until recently, both grant requests and the (technical) community wishlist used petition-like voting processes that encouraged support and disregarded opposition votes. That is, if there were 25 people supporting something and you showed up to say "* Oppose because WMF Legal will have a heart attack if you do this", then the request might be rejected because of the information you provided, and your comment might change the minds of potential/future supporters, but it would never be counted as a vote of 25 to 1. It's still counted as a list of 25 supporters. WhatamIdoing (talk) 18:53, 27 November 2024 (UTC)[reply]
The original Phase I Proposal was directly written as adapting dewiki's recall policies into enwiki. I believe the Italian wikipedia also has a threshold to RRFA style process. And I think spanish too? I might be getting some projects confused. But it's directly used in recall in other projects - That's how it was recommended here (and then adapted after). Soni (talk) 18:58, 27 November 2024 (UTC)[reply]
Arbitration election commissioners are chosen by collecting solely supporting statements. Once upon a time, the arbitration election RFCs also consisted of proposals that commenters approved, without any option to oppose. isaacl (talk) 19:50, 27 November 2024 (UTC)[reply]

the REGIME test

[edit]

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.


  • That any news outlet or source that refers to a government as a "regime" be considered not reliable for facts about that regime, except for attributed statements.
  • That a list be kept and updated, similar to WP:RS/Perennial sources

Skullers (talk) 04:03, 20 November 2024 (UTC)[reply]

Why do we want to only use sources that haven't noticed that a regime is a regime? -- Nat Gertler (talk) 04:09, 20 November 2024 (UTC)[reply]
This would, for example, rule out using a significant proportion of reliable sources covering contemporary North Korea, Afghanistan, Cuba and Iran as well as countless historical governments (e.g. Saddam Hussein's Iraq, Franco's Spain, Gaddafi's Libya, etc). This is clearly hasn't been fully thought through. Thryduulf (talk) 04:17, 20 November 2024 (UTC)[reply]
Well, it might have been thought through if the idea is to exclude sources critical of said regimes, eg Activist takes own life in protest at Iranian regime (BBC). Regards, Goldsztajn (talk) 06:57, 20 November 2024 (UTC)[reply]
That would be a gratuitous failure of NPOV. Thryduulf (talk) 11:04, 20 November 2024 (UTC)[reply]
In heated agreement. Regards, Goldsztajn (talk) 01:57, 21 November 2024 (UTC)[reply]
Bad idea. A biased source does not mean unreliable. See WP:BIASED. However, it is indeed good indicator that a in-text attribution may be needed. Ca talk to me! 15:00, 20 November 2024 (UTC)[reply]
I think this does get at something which is a problem in Wikipedia. It just doesn't quite hit the mark. And that is that there is a core assumption in Wikipedia's handling of news media sources that they are largely independent and that a deviation from editorial independence represents a deviation from best practices. However this often leads to Wikipedia simply assuming the biases of the New York Times and other major media outlets. But there has been an accumulation of multitudinous issues - one of the most recent being accounts of Jeff Bezos influencing the Washington Post to withhold an endorsement of Kamala Harris - that demonstrate that the idea of editorial independence is frankly quaint.

This, of course, then creates problems with adjudicating those sources that have previously been demonstrated to be non-independent (see for example WP:XINHUA) as the rationale on Wikipedia for treating Xinhua differently from, let's say, the BBC or Al Jazeera for that matter largely depends upon the assumption of independence of those outlets that are not aligned with enemy states of the US/UK hegemony.

My personal opinion is that the use of news sources on an encyclopedia should be far more limited than it presently is as, in my case, it's not that I trust Xinhua (I don't) but that I don't trust any media outlet to produce material appropriate for a neutral encyclopedia. I don't think a "regime" test is going to improve the quality of pages that over-rely on news media. But I would suggest that it's another indication that Wikipedia needs to be far more critical of what news sources we depend on and in what contexts. Simonm223 (talk) 19:54, 20 November 2024 (UTC)[reply]
No, editorial independence is not the reason for a source being considered reliable or not. Many sources are biased, or influenced by specific governments/interest groups, and are still considered reliable for topics other than the groups influencing them (in which case, by definition, they would not be an independent source). A history of disinformation (actually making up stuff, not just reporting it in a biased way) pushes the source towards being considered unreliable.
WP:XINHUA, which you link, demonstrates this clearly, stating There is consensus that Xinhua is generally reliable for factual reporting except in areas where the government of China may have a reason to use it for propaganda or disinformation. In the same way, we shouldn't rely on the Washington Post for topics related to Jeff Bezos. Chaotic Enby (talk · contribs) 20:07, 20 November 2024 (UTC)[reply]
The example I gave wasn't one of a story about Jeff Bezos or a topic related to Jeff Bezos unless one contends (which, I will grant there's a case to be made) that anything to do with a US election is ultimately about the interests of the Billionaire class. But, you see, that's my point. Pretty much any media outlet will distort truth, spread disinformation or, at the most basic, bury stories that aren't to the interests of their handlers. And I do want to stress that the stories that are not covered is a key method through which media occludes truth. The only real question is whether the handler is a politbureau or a rich guy. I don't think one of those is better than the other. Simonm223 (talk) 20:12, 20 November 2024 (UTC)[reply]
The fact that a news media is influenced to not publish a story makes it biased, but not unreliable. Having a point of view when reporting (or choosing not to report) stories is what every media does, and is different from outright making up disinformation. And that is the difference between bias and unreliability. It's not about who the handler is, rich guys can also own unreliable news sources. Chaotic Enby (talk · contribs) 20:16, 20 November 2024 (UTC)[reply]
I mean we certainly agree about that rich guy. I just think Wikipedia is too fast to treat news sources as reliable out of convenience rather than any real confidence in the quality of information. Simonm223 (talk) 20:20, 20 November 2024 (UTC)[reply]
I agree with Simonm223. I just can't understand why an encyclopedia should be largely based on news sources rather than peer-reviewed academic articles or books. For a start most of them are primary sources, by any definition other than Wikipedia's. This is dumbing-down at its worst. Phil Bridger (talk) 21:09, 20 November 2024 (UTC)[reply]
Exactly, yes. Simonm223 (talk) 22:42, 20 November 2024 (UTC)[reply]
I agree, out article on Donald Trump and Joe Biden for example would do better citing academic sources than news outlets. Ca talk to me! 02:21, 21 November 2024 (UTC)[reply]
See the definition (specifically 2(c) and 2(d)). Regime is a synonym for "administration" or "government" (when used to describe, as example, the Biden administration or the Tory government). It makes zero sense whatsoever to block sources who use a synonym for administration just because one person feels it has negative connotations. Wikipedia is not the place to practice redefining words or limiting their use based on their worst definitions or connotations. -bɜ:ʳkənhɪmez | me | talk to me! 05:03, 21 November 2024 (UTC)[reply]
Prescriptivism is dead. See examples. There is zero percent usage in modern times that isn't derogatory; literally no one says unironically "our regime", "the regimes of our allies", or "regimes we'd like to do business with". Skullers (talk) 08:29, 21 November 2024 (UTC)[reply]
I agree in as much as "government" would always be a better term in any use case I can think of.
However, your polemics here have been consistently superficial and unhelpful. It seems almost self-parody to aphorize "prescriptivism is dead" amid seeking to categorically deprecate sources based on the sole criterion of whether they use a particular word, citing what you feel is the only correct definition of said word in practice. Remsense ‥  09:03, 21 November 2024 (UTC)[reply]
The attraction of the word "regime" to headline writers is often that it is simply shorter than "government" or "administration", rather than anything to do with its connotations. Phil Bridger (talk) 09:48, 21 November 2024 (UTC)[reply]
Exactly my point. -bɜ:ʳkənhɪmez | me | talk to me! 23:24, 21 November 2024 (UTC)[reply]
What is the rationale for this proposal? Is there a specific source or incident that prompted it? Gnomingstuff (talk) 01:09, 22 November 2024 (UTC)[reply]
While I understand the rationale for this proposal, IMO it goes way too far. I would agree that it's important to keep in mind when a source is using biased language and consider using in-text attribution in these cases, but certainly it's not worth a blanket ban.
Furthermore, it's often the case that when the news media uses negative language about a topic, that's because that negative language is the consensus. For instance, nobody would really question the phrase "the Nazi regime" or even probably "the genocidal Nazi regime" from a reliable source, and for good reason. When everyone agrees on a contentious label that implies that in that specific case the label is not, in fact, contentious. Loki (talk) 01:21, 22 November 2024 (UTC)[reply]
  • This proposal is rather absurd. You can’t declare a source unreliable based on a word, especially one that’s frequently used as a harmless rhetorical flourish. What should we ban next? Sources that use swearing? Sources that use subjective adjectives like “best” or “amazing”? Dronebogus (talk) 13:16, 24 November 2024 (UTC)[reply]
I say we should also ban all sources that use the word "slam". Equally as absurd, but more likely to actually hit unreliable sources. Lee Vilenski (talkcontribs) 13:58, 24 November 2024 (UTC)[reply]
Presumably excluding sports uses? We definitely need sources that report on grand slams. Thryduulf (talk) 14:40, 24 November 2024 (UTC)[reply]
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.

 You are invited to join the discussion at Wikipedia talk:Criteria for speedy deletion § RfC: Enacting T5 (unused template subpages). HouseBlaster (talk • he/they) 03:01, 25 November 2024 (UTC)[reply]

Information on cross-wiki article creation

[edit]

The Harald Winter article was created by X3ntar as a port from the German Wikipedia article (found here: Harald Winter). The English article consists primarily of poor English translation and promotional content, and when I was looking through the history of the article, all I saw originally were red-linked accounts created a short while before their edits to the article, leading me to begin researching to source a WP:SPI case. After almost an hour of looking into this, I don't think this is canvassing, meatpuppetry, or anything like that. More likely it's a case of German editors wanting to update the English version of the article. However, I couldn't find any policies or essays that gave advice on how to handle cross-wiki contributions or page creations. Is there a common consensus reached prior? Sirocco745 (talk) 04:59, 25 November 2024 (UTC)[reply]

This doesn't happen very often, so I don't think there are any advice pages. In general, it would be a lovely thing if people who created an article in one language could then do a semi-decent translation into another language.
I'm aware of two multi-editor cases of that. The first is that when a WMF staffer mentioned writing her first article (in English), a handful of staffers who are not native English speakers (but who are experienced Wikipedians) translated that into their native language as a way of encouraging her to keep editing as a volunteer. This probably happened about a decade ago, and it was very sweet.
The other was a sustained self-promotion effort by a handful of artists, including hoax photos. See d:Q131244 for what's left of their efforts. We deleted the English article. The reason this sticks in my mind is that they repeatedly faked photos – see c:Commons:Deletion requests/File:Ferlinghetti meets Immagine&Poesia representatives.jpg for one example – of various people and the poet Lawrence Ferlinghetti. Every few months, one of the same two photos of Ferlinghetti in a public place would appear, with a different person photoshopped into the scene next to him, and it would get added to an article with a caption saying something like "Ferlinghetti met with so-and-so" (a different name each time). The result is that every remaining mention of that group seems suspicious to me. WhatamIdoing (talk) 02:09, 27 November 2024 (UTC)[reply]
Okay, thanks for responding. I'm going to think about what can be done to assist editors in future scenarios and draft some thoughts for an essay in my sandbox later. I don't believe that creating a policy proposal is worth it right now, since as you've observed, cross-wiki article copy-pasting isn't a major concern due to its relative uncommonness. I'm considering writing up an essay on the subject instead, maybe also creating a template later on to go at the top of an article that says something along the lines of "This article was cross-posted from the "XYZ Wikipedia" and is currently undergoing translation, discussion, and improvement." Sirocco745 (talk) 02:56, 27 November 2024 (UTC)[reply]

Topics on Jehova's Witnesses - article spamming issues

[edit]

Polish Wikipedia is experiencing and uptick in Jehova's Witnesses topics article spamming, surrepticious edits pushing JW terminology etc. One of current problems is the spamming of separate articles for every "convention", which is an annual (I think) event with a theme and about 100k visitors. We are discussing their notability right now, and I was wondering whether English Wikipedia already discussed and cleaned this, which would be helpful? If you remember any topic discussing notability or monitoring of Jehova's Witnesses related topics, and possibly deleted articles. (I'm not sure if there is any sensible search method of deleted articles archive/log? Can I use any wildcards in Special:Log/delete? It doesn't seem to work.) Tupungato (talk) 12:04, 25 November 2024 (UTC)[reply]

@Tupungato, we used to have a list of conventions, but it was deleted 16 years ago at Wikipedia:Articles for deletion/List of Jehovah's Witnesses conventions. I'm not sure we would make the same decision today. Information about some conventions is in History of Jehovah's Witnesses. WhatamIdoing (talk) 02:22, 27 November 2024 (UTC)[reply]

Titles of articles about false theories or accusations

[edit]

This seems to be a little bit inconsistent. Some have "conspiracy theory" in the title, clearly stating they are false (I don't think there's any possible way any even remotely possible theory or accusation would have the words "conspiracy theory" in it). Some go even further outright stating "myth" (not unwarranted if it is clearly false).

However: These do not, despite the article clearly stating the theory or accusation is incorrect:

Is there some kind of policy regarding whether to include "conspiracy theory", "myth", etc in article titles about false theories or accusations? </MarkiPoli> <talk /><cont /> 12:37, 25 November 2024 (UTC)[reply]

Generally, all articles should be titled neutrally and in line with their common name, where they have one. If the significant majority of reliable sources do not describe something as a conspiracy theory or myth (even if they are false) then our article titles should not. In most cases where "myth" and "conspiracy" appear in the article titles they are descriptive as there is no single common name for the topic(s) covered. Consistency is part of the article titles policy but it is only one criterion and generally not regarded as the most important. Thryduulf (talk) 12:50, 25 November 2024 (UTC)[reply]
I see two situations here: one where the article title wouldn’t work without the addition of “conspiracy theory” (i.e “International Jewish” is a non sequitur fragment); and one where the title would work (“999 phone charging” makes sense on its own). We don’t need to state something is a myth in the title if the article explains it’s a myth; there’s enough RFK Jr. types whining at Talk:Turbo cancer to prove that much. Dronebogus (talk) 13:10, 25 November 2024 (UTC)[reply]
Agree with Thryduulf. We should use titles that are considered the common name for the topic and that fall with the article title policy, and then after that any necessarily disambiguation steps to differentiate from other topics. And as long as the lede sentence or lede itself (as in the case of Vaccines and autism) is clear what is legitimate science or fact and what is a conspiracy theory, pseudoscience, or disproven, then its not as important for the title to reflect that as well. Masem (t) 13:31, 25 November 2024 (UTC)[reply]
Indeed there are some editors on the sceptic side who seem to feel that it is necessary to explicitly and stridently describe something as pseudoscientific at every possible opportunity. We don't need to bash our readers over the head with it, indeed doing so can be contrary to NPOV (e.g. when reliable sources disagree and/or take a more nuanced approach). Thryduulf (talk) 14:39, 25 November 2024 (UTC)[reply]
I think that what leads to adding "conspiracy theory", "myth", etc. generally boils down to whether the topic is one that perennially annoys the regular page watchers at WP:FRINGE/N. So, for instance, Fan Death isn't caused "the Fan Death Myth" largely because there's not a large proportion of editors rushing to the Fan Death article to say "this is a real serious problem guys". Simonm223 (talk) 14:48, 25 November 2024 (UTC)[reply]
I think that’s a genuine problem that we should probably address— some anti-fringe editors are among the most aggressive contributors I’ve encountered, probably because too many “skeptics” are also culture warriors who need to right great wrongs by doing everything short of calling something “stupid” and its adherents “idiots”, which of course actually damages our credibility. Dronebogus (talk) 15:09, 25 November 2024 (UTC)[reply]
I'm all for preventing the spread of quack medicine and Ufology silliness on the encyclopedia but, generally, the fringe noticeboard is poorly equipped to address assessments of what research is fringe outside of medicine, history and archaeology. I think some of these anomalous titling conventions kind of point toward that specificity of scope. Simonm223 (talk) 15:57, 25 November 2024 (UTC)[reply]
FRINGE should really only apply to topics where objective research have thoroughly debunked the notion, and not to areas where questions remain open or where debunking may never be possible at which point Undue becomes the answer. For example, whike most science rejects the COVID lab theory, it's still near difficult to devisicely conclude that the lab theory is not posdible, so we should avoid calling it fringe but clearly note the weight of experts that have dismissed it. — Masem (t) 16:54, 25 November 2024 (UTC)[reply]
Hmm, there is a difference between "theories that are scientific, plausible and supported only an extreme minority of sources but have not been/are unlikely to be conclusively disproven", "theories that are scientific, were previously mainstream but no longer are, but are still supported by an extreme minority of sources as they have not been conclusively disproven". "theories that are scientific but implausible to the extent that mainstream sources do not feel the need to conclusively disprove them.", "theories which are scientific and have been conclusively disproven, but still have some supporters", "theories which are pseudoscientific" and "theories which are neither scientific nor pseudoscientific". I've seen FRINGE used to describe all of these cases, which is unhelpful. Thryduulf (talk) 17:08, 25 November 2024 (UTC)[reply]
I think part of the issue is: there is a Kennedy assassination, but this article is about the conspiracy theories; there is grooming but this article is about about a conspiracy theory; there is phone charging but this article is about a myth; there are international Jewish organizations but this article is not about that, etc. So, the article title is limited to (and limits) the scope of the article. And other times, 'myth' or 'conspiracy theor[ies]' is in a common name for the subject. Also note, you really can't tell why an article is called 'this' instead of 'that', unless it has actually been discussed. Article title decisions are made in a decentralized manner, and may never be revisited. Alanscottwalker (talk) 12:46, 26 November 2024 (UTC)[reply]
Alan raises a good point… when there actually are theories that postulate a conspiracy, then it is not POV to call them “conspiracy theories”. That is a neutral descriptive title, not a pejorative one. Blueboar (talk) 13:32, 26 November 2024 (UTC)[reply]
I am not sure if that's true, that those that subscribe to a theory that is based on conspiracy would necessary call it a conspiracy theory themselves. Eg those that claim there is a deep state aren't usually calling that a conspiracy theory, but a theory about conspiracies, if that makes sense. Masem (t) 15:46, 26 November 2024 (UTC)[reply]
And according to that article "deep state" is a pejorative. Regardless, just because you have Illuminati does not mean you can't have New World Order conspiracy theory. The Illuminati of Bavaria, can well be a different matter than the Illuminati of the 1960s novel.[4] Alanscottwalker (talk) 16:31, 26 November 2024 (UTC)[reply]
  • I would like to add that, while I would like standardized article titles and would also like if some anti-FRINGE editors dropped the “angry atheist” stereotype, I think this is an exceedingly trivial issue that does not need to be “solved”. Dronebogus (talk) 16:03, 27 November 2024 (UTC)[reply]

New users required to cite sources when creating an article

[edit]

This wishlist item proposes a hard edit filter which would change citation policy for new users. We've repeatedly discussed requiring sources, and the consensus has been not to require them; per current policy, articles must be on notable topics and statements must be citable, but neither need be cited.

I know changes that affect new editors typically don't ignite as much interest as those that affect established editors, but they are in some ways more important; anything that affects our retention rate will eventually substantially affect the number of active editors, and the nature of their editing.

More broadly, it might be good to set limits on policy changes done through a wishlist survey on another wiki; big changes need broader discussion. HLHJ (talk) 01:05, 27 November 2024 (UTC)[reply]

I strongly oppose implementing this on en-wiki. This is not the sort of change that the broader community should be allowed to dictate to local communities. voorts (talk/contributions) 01:22, 27 November 2024 (UTC)[reply]
It's just a wish. Anyone can male one. We don't know whether it will ever be implemented (community wishlists don't exactly have a good track record), never mind turned on on enwiki. – Joe (talk) 05:52, 27 November 2024 (UTC)[reply]
As Joe says, a wishlist item is a long way from becoming something that works. We don’t have need for limits on changes; it is very rare for any changes to be pushed on en.wiki. Those that are are large-scale changes that affect all wikis (think Vector2022 or the upcoming IP masking), and the community here is usually very aware of these ahead of time. If wishlist items turn into tools the wiki can use, they tend to require local activation, as different projects have different needs. (En.wiki for example already has WP:NPP, which will see any new pages, which may include pages that aren’t meant to have sources, like disambiguation pages.) CMD (talk) 08:17, 27 November 2024 (UTC)[reply]
The WMF Community wishlists in the past have actually had some impressive successes, particularly in 2018 for NPP's Page Curation extension improvements. It is not all that rare for any changes to be pushed on en.wiki; two slightly earlier community driven major policies largely contributed - at the time - to reducing the flow of sewage in the new page feed: the 2016 NPP user right, and after a 7 year battle with the WMF, the 2018 ACPERM. However, the number of new registrations has since grown again by users whose first intention above all else is to create a new article by hook or crook with little or no regard for notability, relevance, UPE, and spam policies. NPP has lost many of its prolific, skilled patrollers and coordinators either through burn-out and/or the constant whining either from users whose inappropriate articles have been consigned to the queues for the various trash cans or draft space, or have been driven away for good by other (non NPP) back office regulars' complaints, for the sake of complaining, over a couple of misplaced CSDs or AfDs out of thousands.
The NPP backlog sawtooth profile looks menacing - it should be a regular low-value straight line. It is well known common knowledge that NPP is hopelessly overburdened and can no longer sensibly cope with even the minimum suggested criteria for patrolling new pages. The best way to ensure that the WMF's flagship project - the one that draws all the donations - becomes an untrustworthy resource full of useless and corrupt articles, is to sit back and do nothing and let WP become a mire of misinformation and spam. Wikipedia has already become the buck of media satire with "If you believe Wikipedia, you'll believe anything". The quest is therefore for any measures that will tighten up the article quality at the source of creation.
Although they are aware of them, as usual the WMF Growth Team has played down and resisted addressing these issues in favour of pursuing other, and expensive initiatives of their own design which in the NPP realm remain ineffective. It's the responsibility of the WMF to ensure new users are aware of the rules at the point of registration.
The NPP team has handed solutions to the WMF on a plate, which at the same time will not only reduce the tide of rubbish, but most importantly, encourage the good faith new users to offer articles that have a fair chance of being published. All this project needs is to be written up in MediaWiki source code, but of course short of a mutiny by the community, the WMF will not entertain any ideas that they did not think of themselves and can collect the accolades for.
The "anyone can edit" principle is not a get out of jail free card; it should be quoted in its full context: 'Anyone can edit as long as they play by the rules'. For once and for all, just make those basic rules clear for bona fide new registrants, and help them comply. Kudpung กุดผึ้ง (talk) 03:53, 28 November 2024 (UTC)[reply]

Propose to create page of block discussion in noticeboards

[edit]

Hello users, I propose having a page within noticeboards in the "general" section called "Block discussion" with a list of active discussions (which could be a review request, an unblock request or a discussion on whether to block the user) (to separate from administrators ' noticeboard, to clarify further, and that within the DB there are 5 topics, 1. Evidence (evidence that the user can provide as a reason for blocking, will be ignored in the review request), 2. Defense (defense of the blocked or accused against blocking or defending its review), 3. Comments (comments from anyone who is registered and at least 10 edits whether they agree, disagree or neutrality with blocking, a filter or unblocking), 4. Administrators' evaluation (where administrators agree or disagree with blocking, unblocking or filtering, this means that the conclusion depends on the administrators' assessment), 5. Conclusion (Conclusion of the discussion if the blocking, filtering or unblocking was approved).

NOTE: And there must be verification in the discussion to prevent someone from manipulating BD through sockpuppetry. JPPEDRA2 why not? 18:54, 27 November 2024 (UTC)[reply]

This means I'm proposing to separate "Wikipedia:Block Discussion" from "Wikipedia:Administrators' noticeboard" to be clearer JPPEDRA2 why not? 18:57, 27 November 2024 (UTC)[reply]
I understand the desire to split things off of AN/ANI, but this split poses several problems in practice. Quite frequently the proposal for a CBAN only arises after discussion has been ongoing for some time, and while it could be split off at that point it creates an extra bureaucratic step for questionable benefit. The other issue is that neither CBAN impositions nor their appeals are all that common, and separate noticeboards only tend to work well for things that have a fairly high frequency threshold. Arguably, if we had to do it over again AN wouldn't be the catchall, but at this point changing that is more trouble than its worth.
Granted, CBAN and appeal procedures could be tightened up separately without splitting anything off, but there's a longstanding preference for unstructured and somewhat messy discussions, and I don't see that changing anytime soon. 184.152.68.190 (talk) 17:03, 28 November 2024 (UTC)[reply]
@184.152.68.190 Ok, i'm understand, so can i'm cancel this proposal because that will be more complex? JPPEDRA2 why not? 17:57, 28 November 2024 (UTC)[reply]
@JPPEDRA2: Yes, you can just close it as withdrawn, if you so chose. But don't let me discourage you if you want to leave this open for input from others; every so often perrenial proposals do get implemented, including rather recently, though its usually better to get input at WP:VPI first.
As a side note unregistered users cannot yet be pinged, though apparently that is coming sometime in the not to distant future. 184.152.68.190 (talk) 18:52, 28 November 2024 (UTC)[reply]
Ok, so I won't cancel now, I will let others discuss it, if it is rejected, put it in those VPI or perrenial proposals that you mentioned, thanks non-registrered user. JPPEDRA2 why not? 19:20, 28 November 2024 (UTC)[reply]

Global welcoming policy

[edit]

There is a proposed global policy at meta:Requests for comment/Welcoming policy: "A wiki is only allowed to post welcome messages to users if their account was originally created at the wiki, or the user has at least one non-imported edit there." Comments belong there and not here. PrimeHunter (talk) 21:48, 27 November 2024 (UTC)[reply]