Wikipedia:Village pump (policy)/Archive 187

• Village pump
  • Policy
  • Technical
  • Proposals (persistent)
  • Idea lab
  • WMF
  • Miscellaneous

Village pump (policy) archive  

This page contains discussions that have been archived from Village pump (policy). Please do not edit the contents of this page. If you wish to revive any of these discussions, either start a new thread or use the talk page associated with that topic.

---

< Older discussions · Archives: A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, AA, AB, AC, AD, AE, AF, AG, AH, AI, AJ, AK, AL, AM, AN, AO, AP, AQ, AR, AS, AT, AU, AV, AW, AX, AY, AZ, BA, BB, BC, BD, BE, BF, BG, BH, BI, BJ, BK, BL, BM, BN, BO · 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198

Requirement for non-primary sourcing in NGEO

The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion. A summary of the conclusions reached follows.

Withdrawn, per discussion with FOARP etc. It may be worth having a discussion on the secondary idea of a location not being notable if the only coverage of the feature is mention in a census table as suggested by SMcCandlish, but that idea would need considerable work shopping before it can be proposed anywhere. BilledMammal (talk) 04:54, 8 October 2023 (UTC)

---

Should WP:NGEO be clarified to state that all articles within its scope must include at least one non-primary source? 16:58, 5 October 2023 (UTC)

Survey (Non-primary sourcing in NGEO)

• Support per WP:OR, which says Do not base an entire article on primary sources, and be cautious about basing large passages on them and Secondary or tertiary sources are needed to establish the topic's notability, as well as WP:WHYN which compliments this by saying We require the existence of at least one secondary source so that the article can comply with Wikipedia:No original research's requirement that all articles be based on secondary sources.

While this clarification is redundant as we already have a core policy that clearly requires this, I think it is useful to provide as it is not uncommon in this topic area for editors to forget that such a requirement exists; we see many articles on geographical locations sourced solely to the census, for example. I also believe the requirement itself is a good idea; if all we have is raw data on a topic then we are not able to put it in context with explanations referenced to independent sources, as required by WP:INDISCRIMINATE, and we are not able to provide the interpretation and context that is required for an article to provide encyclopedic coverage of a topic. Further, the sole use of primary sources often causes issues; such sources often require a degree of interpretation to comprehend and this has resulted in the creation of articles that claim, for example, a petrol station is a village. We can minimize such mistakes by reminding editors that they need also need to use secondary sources in their article creations. BilledMammal (talk) 16:58, 5 October 2023 (UTC)

• Oppose per NEXIST, we don't actually have to be currently using a source for it to count towards notability. That being said anyone asserting that the topic is notable on NEXIST grounds actually needs to be able to present the sources... The only real caveat I would carve out would be for topic where their primary language of coverage is likely other than English (a Kyrgyz parliamentarian for example), in that cases coverage can be presumed to exist if nobody present has the language skills to confirm one way or another whether it does or doesn't. Horse Eye's Back (talk) 17:05, 5 October 2023 (UTC)

  While we don't need to be using the source for it to count towards notability we do need to be using at least one secondary source to comply with WP:OR; I think it would be helpful to provide a reminder of that - particularly since even when articles covered by NGEO are challenged editors forget this requirement. BilledMammal (talk) 17:11, 5 October 2023 (UTC)

  Ehh, I think its more a user behavior issue if someone is creating articles without reliable secondary sources. My understanding is that the vast vast majority of articles which are largely unsourced were created more than a decade ago, not recently. Horse Eye's Back (talk) 17:14, 5 October 2023 (UTC)

  Unfortunately, it's still quite common today; for example, I recently came across someone creating hundreds of articles on hromada's sourced solely to the same primary source, and someone else creating hundreds of articles on Indian villages sourced to the same four censuses; even a quick scroll through recent page creations turned up this article, which is sourced solely to GNIS and the Iranian Census. Given that it is such a common misconception I feel it is more appropriate to characterize it as a communication issue rather than a behavioral issue. BilledMammal (talk) 17:23, 5 October 2023 (UTC)

• Oppose As North8000 frequently says, Wikipedia is a fuzzy ecosystem and we ought to be clear and deliberate in how or why we change WP:N. I, for one, believe two things - first that stub articles are appropriate and useful to our project. Some information is better than none. Second, I believe that we should not treat primary sources as black and white. Yes, relying on primary sources is problematic, since primary sources frequently make the thing they are associated with/from look good and more important. However, there are primary sources that are purely factual and should be trusted. Who are the members of a legislature? Who are members of a football squad? Who holds a named professorship? Which businesses are listed on NASDAQ? I am more concerned with improving this project and using common sense than design one-size-fits-all rules that may have unintended consequesnces that make this project less usueful to readers. -— Preceding unsigned comment added by Enos733 (talk • contribs) 17:12, 5 October 2023 (UTC)
• Oppose per WP:NEXIST. Notability is independent of the sources actually used in an article. (Edit: there's also an interesting point made by Thryduulf just below. There may be a forum shopping issue to dig into.) Ed ^{[talk] [OMT]} 17:13, 5 October 2023 (UTC)

  WP:NEXIST is about whether the sourcing is currently on Wikipedia. It is not a pass on it not existing at all.FOARP (talk) 18:13, 5 October 2023 (UTC)

  @FOARP: I might re-read the proposal again. :-) This proposal has nothing to say about sources existing, but would add a new requirement that one be on Wikipedia to count towards notability. Ed ^{[talk] [OMT]} 18:39, 5 October 2023 (UTC)

• Oppose per all Enos733, The ed17 and Horse Eye's Black. I really don't want to assume bad faith here, but this feels remarkably like trying again to make it easier to delete content that some people do not like when the Wikipedia:Village pump (proposals)#Changes to GEOLAND RFC is not going the way they hoped. The existence of a large number of stub articles on geographic places is not a problem that needs solving. Thryduulf (talk) 17:24, 5 October 2023 (UTC)

  The requirement already exists; articles based solely on primary sources can already be deleted, both in this topic area and any other. The difference that this will hopefully make is to reduce the number of articles created in violation of the requirement, by reminding editors who are using NGEO to help determine whether a topic warrants an article that they need to include a secondary source. BilledMammal (talk) 17:47, 5 October 2023 (UTC)

  Although I am aware that you believe The requirement already exists, I have not yet seen any evidence that the community supports this view. This is the question I have asked in the discussion section above, and it has not yet been answered. Newimpartial (talk) 17:59, 5 October 2023 (UTC)

  There is no reasonable way to interpret the sections of WP:OR and WP:N that I quoted other than that the requirement exists; if you believe the community no longer supports that requirement then the correct way to address it is an RfC proposing modifications to WP:OR and WP:N. BilledMammal (talk) 18:05, 5 October 2023 (UTC)

  Guidelines are not hard and fast rules, by design. WP:N is not absolute. Your interpretation of it is not inherently correct, nor the sole interpretation. oknazevad (talk) 15:35, 7 October 2023 (UTC)

• Oppose per above votes.--Ymblanter (talk) 17:33, 5 October 2023 (UTC)
• Support - per WP:WHYN, WP:NOR. Secondary, independent sourcing is required for all articles. No area of Wikipedia is exempt from this requirement as it is needed to maintain WP:NPOV and avoid inaccuracy and hoaxes. WP:NEXIST is an argument as to when it needs to be established, not if it needs to be established - and it needs to be established no later than a primary facile case of it lacking is put forward.FOARP (talk) 18:07, 5 October 2023 (UTC)
• Oppose the overall proposal, per the most of above commenters; it has confused the sourcing used to establish notability with the sourcing used to satisfy WP:V. But I support this secondary idea: "While we don't need to be using the source for it to count towards notability we do need to be using at least one secondary source to comply with WP:OR; I think it would be helpful to provide a reminder of that". A problem with using old census data and the like as the only sources for the existence of something is that micro-local jurisdictions are created and absorbed all the time, sometimes within just a couple of years, and they are not encyclopedic material (WP:NOT#DICTIONARY including a geographic one, WP:NOT#DATABASE, etc.). At best, they should redirect to whatever they merged into or are a subset of, just as we redirect non-notable school titles to notable school districts. But if there isn't even any sourcing available to establish that the little locality presently or recently existed and some basic details about it, other than a mention in a census, then there isn't any basis on which to write anything encyclopedic in the first place, even as a sentence inside another aritcle. I'll repeat part of NGEO: "Even the smallest geographical features usually may be found in numerous reliable sources: you can easily see creeks in maps, sand banks in navigation guides, hamlets in census tables, etc. There may be hundreds of them. They do provide reliable information about the subject. However this guideline specifically excludes them from consideration when establishing notability, because these aggregate sources tell us nothing about why a particular object is distinguished. Still, they do contribute to the satisfaction of the requirement of verifiability." Note in particular hamlets in census tables which is mostly what this is about. NGEO also says: "A feature cannot be notable, under either WP:GNG or any SNG, if the only significant coverage of the feature is in maps, though rare exceptions may apply." The actual rationale for that perhaps overly specific line-item also applies to "if the only coverage of the feature is mention in a census table"; it's just that the RfC that arrived at that exact wording was only considering maps at the time.  — SMcCandlish ☏ ¢ 😼  18:17, 5 October 2023 (UTC)
• Oppose and I agree with a lot of SMcCandlish has said. Also I'd maybe some clarity on NEXIST might help, notability isn't depend on the references in the article, but those references do need to exist and be proven to exist at AfD. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 19:46, 5 October 2023 (UTC)
• Support. Per policy, articles must be based on non-primary sources. This is an independent criterion from establishment of notability. While I acknowledge the concerns of @Horse Eye's Back and @SMcCandlish that presumptions of IRS SIGCOV can be asserted with SNGs and rebuttably protected by NEXIST, the articles themselves must still comply with NOR policy--which means that the content of the article must be based on non-primary sources. In theory, one could achieve this without actually citing the secondary source, as long as the majority of the info is verifiable to a secondary source. However, in practice the NGEO criteria have become totally divorced from any empirical demonstration of predictive power. Even the "evidence" that every subject in some subclass really does meet GNG is often simply a collection of passing mentions in primary news, appearances in primary government docs, and clearly indirect coverage that just bypasses NOTINHERITED. Inclusion of secondary sources, which should be a very easy ask -- and indeed is expected in every other topic area -- is apparently too onerous and time-consuming for geo mass creators in particular. Editors who create each article with individual attention should not have any more of a problem finding secondary sourcing than they would for any other topic from the same region or time period. So the only editors who would be affected by enforcing the secondary basis requirement would be those concerned with rapidly creating boilerplate stubs for every item in a geographical database--and if doing this is so vital to the encyclopedia that we can indefinitely waive all standards for this topic, then it would make a lot more sense to give the task to a bot and free the human editors to work on things that do need human effort. JoelleJay (talk) 19:48, 5 October 2023 (UTC)
• Oppose. This is yet another one of BilledMammal's backdoor deletion proposals. Can we ban such proposals already? LilianaUwU ^{(talk / contributions)} 20:26, 5 October 2023 (UTC)

  If you think BilledMammal is being disruptive, the noticeboards are thataway. Der Wohltemperierte Fuchs ^talk 20:36, 5 October 2023 (UTC)

• Oppose while it is best to have secondary sources it is not quite as easy to locate them as is being suggested above. I once came across a stub about an Iraq town with a population of 46,000 and I couldn't find any secondary sources at all and there wasn't much in primary sources either. In these situations a local editor with access to offline sources would be essential. Beyond adding templates I don't think deletion is appropriate in these circumstances if the details are verified in reliable primary sources, imv Atlantic306 (talk) 20:46, 5 October 2023 (UTC)
• Oppose. An article on a geographical place is going to include the history of that place, if suitable sources exist for that history. I happen to be aware that there are books written by historians that do not contain the level of veneration of secondary sources, and the level of condemnation of primary sources, that appears in our policy. Examples that I have come across include, in particular, "Historical Interpretation" by J J Bagley, "The King's Parliament of England" by G O Sayles, and the introduction to Selincourt's translation of books 21 to 30 of Livy titled "The War with Hannibal" by Betty Radice. In view of what these authors say about primary and secondary sources, I am unable to support the proposed addition to this guideline. If Wikipedia's policies and guidelines are going to animadvert on primary sources of history, I think the starting point should be to find out what historians actually say about those sources. I will not at this time support the addition of any further such animadversions not based on statements made in the verifiable published works of historians. James500 (talk) 22:11, 5 October 2023 (UTC)
• Oppose per the NEXIST argument above; contradictions in Wikipedia policy exist—deal with them instead of digging a deeper hole, per WP:POLCON (which I see was mentioned in the pre-RfC discussion, and then just discarded). I feel like the proposer should also be aware, if they have any hope of passing more proposals, that WP:BLUDGEON can also apply to starting discussions, and not just participating in them. ~~ AirshipJungleman29 (talk) 22:34, 5 October 2023 (UTC)
• Oppose. There is no clear definition of secondary that we agree on; I've come to realise that the definition differs widely between fields. This level of hostility towards articles that cover topics that verifiably exist, are covered in reliable sources and are generally considered the purview of an encyclopedia is getting really wearying. Espresso Addict (talk) 22:39, 5 October 2023 (UTC)
• Oppose This seems to be a solution to a problem that's already been solved. I understand there were a ton of articles started about cities and/or named places based off of one GNIS or census entry. That created a mess and stirred up some hostile feelings that unfortunately resulted in us losing some good editors. However, that is over and done and dealt with. I can understand a desire to want something in policy to avoid a repeat of history, but let's not impose hard line mandates that could have any number of unintended consequences. Remember what made Wikipedia great was freedom to edit, not endless and ever expanding restrictions.Dave (talk) 00:42, 6 October 2023 (UTC)
• Oppose We have long said that WP performs the function of a gazetteer. Until a separate sister project is established by the WMF to do this, it makes sense that we actually include all formally-recognized placed as to serve this purpose. That means we need sourcing to affirm they exist, but not the same type of sourcing expected for notability (non-primary sourcing). Obviously, if that can be added, great, but it should not be a requirement as long as we consider the gazetter function as part of our purpose. (Also, this is the only area that we do have such allowance, so its not likely to spread to other topic areas). --Masem (t) 13:38, 6 October 2023 (UTC)
• Oppose per the already mentioned points and and NEXIST. Masterhatch (talk) 14:43, 6 October 2023 (UTC)
• Oppose. Adding more confusion between notability and sourcing type, and more wiki-dogma in place of reasoned evaluation, is not a step in the right direction. The proposal treats "primary" as if it is always an attribute of a source, taken completely out of context. This is incorrect. A source can be primary for some claims and secondary for others. —David Eppstein (talk) 07:23, 7 October 2023 (UTC)
• Oppose. I think everyone would agree that this is the direction individual articles should be moving in over time. However, the notability guideline has always been focused on the subject itself, rather than the article. —siroχo 09:46, 7 October 2023 (UTC)
• Oppose. Notability is an inherent property of the subject of an article and entirely separate from the current state of said article. That is a fundamental principal that this proposal would toss out. If someone sees an article that they think is insufficiently sourced, WP:SOFIXIT still applies, as does WP:BEFORE. oknazevad (talk) 15:51, 7 October 2023 (UTC)
• Oppose What novel ideas, syntheses, analyses, evaluations and/or conclusions are present in a geography stub? XOR'easter (talk) 00:27, 8 October 2023 (UTC)

Discussion (Non-primary sourcing in NGEO)

See here for the pre-RFC discussion. BilledMammal (talk) 16:58, 5 October 2023 (UTC)

• There have been so many proposals relating to notability and deletion recently, I'm losing track... BeanieFan11 (talk) 21:29, 5 October 2023 (UTC)

  Almost all started by or strongly and prolifically endorsed by the same few editors. I would support a moratorium on any new noticeboard-level proposals relating to notability and/or deletion until after all the currently open RFCs and similar discussions about such matters are closed. Thryduulf (talk) 22:26, 5 October 2023 (UTC)

Seconded. Espresso Addict (talk) 22:33, 5 October 2023 (UTC)

• Agreed. One at a time? ~~ AirshipJungleman29 (talk) 22:45, 5 October 2023 (UTC)

Support moratorium. The sheer number of proposals, the speed with which they are being proposed, and the sheer number of comments in those discussions by the same few editors, is making it impossible for other editors to get anything useful done elsewhere on the project. James500 (talk) 23:02, 5 October 2023 (UTC)

Agreed. couldn't have said it better myself.Dave (talk) 00:46, 6 October 2023 (UTC)

And I note there is now yet another one on extending BLP-type prods to all unreferenced articles, taking place on proposals. It is genuinely hard to keep up with all this and actually do any real work here. Espresso Addict (talk) 00:20, 7 October 2023 (UTC)

Feel free to share a link. –Novem Linguae (talk) 00:25, 7 October 2023 (UTC)

@Novem Linguae Wikipedia:Village pump (proposals)#Request for comment: Unreferenced PROD. I'm about to start a formal proposal for a moratorium. Thryduulf (talk) 00:30, 7 October 2023 (UTC)

@Espresso Addict, Airshipjungleman29, James500, Moabdave, and Novem Linguae: and anyone else interested, the formal proposal for a moratorium is at: Wikipedia:Village pump (proposals)#Temporary moratorium on new proposals regarding deletion, notability and related matters Thryduulf (talk) 01:16, 7 October 2023 (UTC)

@AirshipJungleman29: fixing the ping. Thryduulf (talk) 01:17, 7 October 2023 (UTC)

• I think it worth noting here that this discussion was supposed to take place after the other RFC closed - indeed it was agreed on the NGEO page that it would not take place until the other RFC had at least closed. It was then that NewImpartial decided to open their RFC to pre-empt this one and BM open this one. To be honest I would not have opened this RFC now - tit-for-tat is never a good idea.

There's a lot of talk about "the same few editors" above, I haven't counted the number of editors who repeat this particular statement but it does also appear to fall into the definition of "a few". Frankly, there is an increasingly acrimonious discussion between editors who focus is on cleaning articles up and removing inaccurate content, and those whose focus is on generating or defending articles created rapidly and in large numbers based on primary sourcing - you might feel that characterisation is unfair, but it is the effect of the present discussion.

@SMcCandlish - your argument about WP:NEXIST is interesting. Is there a proposal, giving proper weight to WP:NEXIST, that you could support? For example, a requirement that secondary sourcing should at least exist for the article-subject? FOARP (talk) 08:41, 6 October 2023 (UTC)

Note that Newimpartial's discussion is not an RFC. Your characterisation of the editors is definitely unfair, but this is the wrong place for discussion of that. Thryduulf (talk) 08:51, 6 October 2023 (UTC)

Forgive me: NewImpartial's question about how to implement policy on the page that says right at the top "this is not the place to resolve disputes over how a policy should be implemented". 08:58, 6 October 2023 (UTC) FOARP (talk) 09:00, 6 October 2023 (UTC)

I didn't have specific wording in mind, and in the P&G sphere I tend to focus on the style matters, so I may not be the best to craft such wording. The exact interplay between various statements in the sourcing and notability policies isn't an area of expertise for me. But I think someone for whom it is could gin up a propposal pretty easily, using what I said above and perhaps your summary "secondary sourcing should at least exist for the article subject". But something like that should surely be proposed after the current furor[e] has died down a bit. There's a clear lack of appetite above for another proposal relating to any of this until after all the concurrent ones are closed. Kind of a WP:TALKFORK problem (even if not strictly WP:MULTI; it's not literally "the same" discussion in multiple places, but a failure to centralize related propositions and consider them together or at least in series).  — SMcCandlish ☏ ¢ 😼  09:00, 6 October 2023 (UTC)

Agreed that we have had at least one too many discussions on this topic of late. The mass-creation RFC mandated by ARBCOM after the whole Lugnuts farago was supposed to be a centralised discussion of all this, but it simply fell apart without a conclusion.

I would support workshopping the WP:NEXIST proposal over at NGEO and proposing something based on that back here towards the end of the year/start of the next as a Christmas present for everyone. BM is correct to highlight that we're acting as if secondary sourcing can be abandoned entirely in the NGEO area, but it's also worth saying that WP:NEXIST needs to be given some play since so many articles have been created under the apparent assumption that it basically doesn't matter. I don't believe the doom-laden predictions about mass deletion myself, but clearly enough people do that something needs to be done to assuage their concerns.

@Newimpartial/@BilledMammal - are you guys OK with mutually withdrawing the proposals and going back to the drawing board on this? We could play this out to the end but I don't think it's going well. FOARP (talk) 10:04, 6 October 2023 (UTC)

Well, I haven't made any proposals, and I also haven't asked a question about how to inplement policy, which was your second attempt to characterize my question and was a second fail.

What I did, was to ask what the status quo is. We have two or three editors who believe it is a certain thing (NOR offers a deletion option unrelated to SYNTH) and we have other editors who don't see it that way. If the status quo really amounts to "the community is divided on this" I would think it helpful to see that documented before anyone draws up a proposal to change the status quo.

Basically, I would like to see what the community - not the five or so most invested editors - think the status quo is before an attempt is made to change it. I am not especially attached to the wording I used in my section above, but I do think that step ought logically to precede any proposals either to implement or to change the status quo. Newimpartial (talk) 13:20, 6 October 2023 (UTC)

OK NewImpartial, replace "proposal" with "whatever that is" if that fits for you. BM is OK with withdrawing, are you? FOARP (talk) 14:54, 6 October 2023 (UTC)

I don't see a reason to "withdraw" the question I asked above, since it still seems pertinent and it doesn’t involve any change to the status quo. If editors have better ideas about how to assess what the status quo actually is, or if there is a SNOW sense that the status quo is "editors can't agree what the status quo is", or some other, better approach has been identified than asking the question I asked above, those would be reasons to shut down the above discussion. So far, I haven't really seen anything that falls in any of those buckets, and I also don't see how leaving the above section open could make anything "worse". Perhaps I am simply lacking imagination at the moment. Newimpartial (talk) 15:49, 6 October 2023 (UTC)

FWIW, I think that 'the status quo really amounts to "the community is divided on this"' is pretty well demonstrated by the nature of these discussions. Whether it should be divided or not (based on existing policy and what it all says) is a different matter, but I learned a long time ago not to assert that dispute or uncertainty didn't really exist (in the face of demonstrable actual dispute/uncertainty) on the basis that it shouldn't exist because of policy's clarity. Got myself a reasonably long-term move-ban for taking that kind of stance, back in the day.  — SMcCandlish ☏ ¢ 😼  17:00, 7 October 2023 (UTC)

No objection from me; I quite like what SMcCandlish is suggesting. BilledMammal (talk) 14:45, 6 October 2023 (UTC)

Notifications (Non-primary sourcing in NGEO)

@Actualcpscm, BilledMammal, Bkonrad, Davidstewartharvey, FOARP, Firefangledfeathers, Harper J. Cole, Horse Eye's Back, James500, JoelleJay, Mangoe, Masterhatch, Newimpartial, North8000, and The ed17: Notify editors involved in the pre-RFC discussion. BilledMammal (talk) 16:58, 5 October 2023 (UTC)

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

Clear consensus by use ignoring discussions

Is it fair to assume that consensus by use occurs, where no matter how many discussions take place, users who are unaware/not party to the discussions or unaware/not party of Wikiproject style guides and discussions carry on doing the actions which are being discussed a certain way no matter what occurs in those discussions or internally within a wikiproject.

TL;DR is it consensus by use where users (a large number) simply pay no attention to or have no knowledge of discussions on a specific subject? PicturePerfect666 (talk) 16:45, 15 September 2023 (UTC)

I'm not sure I understand your question. Sometimes, a local consensus can emerge from a talk page which is not necessarily indicative of a broad, community-wide consensus. Is that the point you're making? Pecopteris (talk) 17:56, 15 September 2023 (UTC)

It shouldn't, per WP:LOCALCONSENSUS, but it sometimes does. Addressing that behavioral issue is difficult. BilledMammal (talk) 17:59, 15 September 2023 (UTC)

Yeah I mean when a Wikiproject decides something, but users such as casual and new users, simply pay no attention either through ignorance or preference. I mean i feel in some cases Wikiprojects can make all the consensus they want but trying to get others to pay attention to those discussions can be impossible.

I mean a prime example is the accessibility rules, I know the rules sty not to have headers embedded tables, to aid screen readers, but that is roundly ignored by users, who may not even know the rule exists. PicturePerfect666 (talk) 20:35, 15 September 2023 (UTC)

There is also this discussion where a wikiproject has withdrawn support for doing something one-way nad is endorsing doing something another way, but editors outside of the wikiproject are roundly ignoring hat the wikiproject is saying by continuing to do things the way the wikiproject no longer wants things done. PicturePerfect666 (talk) 20:50, 15 September 2023 (UTC)

That's a slightly different situation; per WP:LOCALCONSENSUS editors outside the WikiProject have no obligation to follow the WikiProject's consensus; if the WikiProject wants the broader community to follow it then it needs to get consensus in the broader community. BilledMammal (talk) 20:58, 15 September 2023 (UTC)

Thanks, I am fairly new here and trying to get to know how things work.

Can the members of the wikiproject try and say 'do it our way because we have discussed it'? PicturePerfect666 (talk) 21:51, 15 September 2023 (UTC)

No. I often revert changes to number articles where a drive-by vandal thinks it's amusing to replace the topic by 42, 69 or 420. Despite the frequency of such updates, I don't see an unwritten consensus to change all numbers in Wikipedia to 42.

Where written guidance varies from common good practice, we should update it. This does happen. For example, those of us who work on disambiguation follow detailed and carefully crafted guidelines. We recently discovered a clause in an unrelated policy page contradicting our practices. The policy was duly amended to reflect reality by removing the clause. Certes (talk) 09:55, 16 September 2023 (UTC)

Not sure I get your first paragraph

How is something, as shown in the football topic be resolved? (Redacted) PicturePerfect666 (talk) 15:38, 16 September 2023 (UTC)

My slightly ridiculous first paragraph was to illustrate that, just because people do something, doesn't mean we should mandate or even allow it (though we may mandate or allow it for other reasons). The football issue clearly needs a discussion about which format is better, or indeed if both formats are acceptable. I don't know the topic well enough to say anything helpful on that matter. Certes (talk) 14:46, 16 September 2023 (UTC)

No. Wikipedia gets used for referencing in articlea all the time, that doesn't mean it should be used or that it's reliable for sourcing. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 16:21, 16 September 2023 (UTC)

I do not understand your comment above please expand. PicturePerfect666 (talk) 18:12, 16 September 2023 (UTC)

PicturePerfect666, please read WP:CIRCULAR. Cullen328 (talk) 18:29, 16 September 2023 (UTC)

Ok but how does that apply here? PicturePerfect666 (talk) 18:32, 16 September 2023 (UTC)

WP:CIRCULAR explains why Wikipedia shouldn't cite Wikipedia as a reliable source. Despite that policy, editors do cite Wikipedia, making it an example of something that is done but prohibited. In my opinion, we shouldn't ignore that policy simply because some others ignore it. See also WP:OTHERSTUFF. Certes (talk) 19:47, 16 September 2023 (UTC)

CIRCULAR doesn't seem to be relevant to the OP's question, though. The question is about "discussions" (which are not policies) and "Wikiproject style guides" (which are also not policies). WhatamIdoing (talk) 23:59, 23 September 2023 (UTC)

Examples to illustrate a point don't need to be directly related to all the points discussed. My original statement made no mention of WP:CIRCULAR, but the point still stands. CIRCULAR has consensus through discussion or silence, and ignoring that consensus because IDLT is wrong. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 19:05, 9 October 2023 (UTC)

No. Consensus should be (and regularly is) ignored by the closers of discussions, where the majority of opinions are on one side of the argument but do not represent policy or provide strong enough arguments. The points made in WP:LOCALCONSENSUS is a typical example of this. Black Kite (talk) 18:21, 16 September 2023 (UTC)

• Policy is supposed to be descriptive (based on “what is actually done”) as opposed to proscriptive (based on “what we would like done”). However, there are rare occasions where we don’t achieve this. When that occurs, one could argue that policy does not follow community consensus.

The solution is to discuss the issue and suggest changes to the policy that better reflect “what is done” (ie community consensus) - with good examples of how and why the community consensus isn’t properly reflected by the current policy. Blueboar (talk) 16:49, 17 September 2023 (UTC)

It's weird that anyone would jump to LOCALCONSENSUS to say that "Wikiproject style guides and discussions" should be followed. I know that Wikipedia:Nobody reads the directions, but seriously: two of the three sentences in LOCALCON say that WikiProjects don't get to decide these things. LOCALCON (which I wrote) exists because a WikiProject tried to ban infoboxes from "their" articles. Nobody has to follow the advice put forward by a WikiProject, just like nobody has to follow the advice put forward by any other individual or self-selected group of editors.

What editors actually do in individual articles is Wikipedia:Consensus#Through editing. WhatamIdoing (talk) 23:58, 23 September 2023 (UTC)

Relationship between Notability guidelines and WP:NOR

NOR/WP:N Question

As a matter of current practice and status quo, has WP:NOR established a requirement that all articles must have at least one secondary source or face deletion? Or would the general application of this principle represent a change to the status quo? Newimpartial (talk) 15:53, 5 October 2023 (UTC)

NOR/WP:N Context

• WP:GEOLAND reflects a long-standing consensus that Wikipedia incorporates features of a gazetteer (in the language of WP:5P); it creates a presumption of notability for places where WP:V, independent sourcing has been presented showing official recognition;
• in both AfDs of stub articles and proposals to change GEOLAND (e.g., here) a substantial current of community sentiment has been expressed in support of this understanding of the status quo;
• recently, certain editors have decided that the sentence about Notability in NOR and a reference to it in the "Why we have these requirements" section of WP:N mean that no topic can be Notable (and therefore presumed to merit an article) without at least one secondary source (see this discussion).

To be clear, my own position is that articles should have secondary sources (which reflects the language used in the WP:GNG) and, of course, I recognize that policies take preference over guidelines via WP:CONLEVEL. However, I have always read WP:NOR as essentially concerned with the validity of article content (especially the exclusion of SYNTH), rather than being intended providing grounds for the deletion (or mass deletion) of articles where synth concerns are absent. So I would very much like to know where the VP community situates itself on this matter. Newimpartial (talk) 15:53, 5 October 2023 (UTC)

NOR/WP:N Discussion

Please add threaded discussion here.Newimpartial (talk) 15:56, 5 October 2023 (UTC)

• Without at least one independent source, how do we know whether the article is not a hoax? Blueboar (talk) 16:47, 5 October 2023 (UTC)

  To answer your question, Independent and reliable sourcing is, indeed, required to meet WP:N and GEOLAND. But what I am asking about is secondary (or tertiary) sourcing, which is not strictly required in the relevant sections of WP:N but is set down as a universal requirement in NOR. Newimpartial (talk) 16:56, 5 October 2023 (UTC)

• (edit conflict) It is disappointing that you chose to open this despite knowing that an RfC was being drafted to ask a related question, and without consulting with the other editors involved in drafting that RfC despite otherwise taking part in the discussion; I've now gone ahead and opened that RfC, would you be willing to close this to allow that to proceed and then if there are outstanding questions open it then?

  As feedback on the question itself, I think it would have been better to make the context more neutral, and at the very least include the lines from WP:OR that you believe should be interpreted as only applying to the content of articles, rather than to the question of an articles existence. It also doesn't seem to be a productive question; it won't resolve the conflict between the clear wording at WP:OR and the creation of articles based solely on primary sources like censuses. BilledMammal (talk) 16:58, 5 October 2023 (UTC)

  To answer your question, BilledMammal: no; I think it would be best to leave this discussion open in parallel, since it asks a different question (namely, what is the status quo).

  Also, in your comment to me earlier today you stated that you planned to run your RfC "next week" - I am curious why you have now rushed to do so today. Surely there was time to discuss what the status quo is, for a couple days at least, before launching into a major change?

  Finally, in response to why I believe the WP:OR policy page is concerned with the content of articles, I would quote the first sentence of the page, Wikipedia articles must not contain original research, which I have always understood to represent both the purpose and the scope of that policy page. But I didn't offer that kind of proof-text in support of my own views precisely in an attempt to present my question - and as best I could, the relevant context - in a neutral manner. Newimpartial (talk) 17:24, 5 October 2023 (UTC)

  This seems like a reasonable explanation for your actions. I don't know why but it seems FOARP is assuming bad faith and ignoring it, below. (I've no idea what any of your editing is about.)

  To answer your question: I think it's not cool, but editors routinely ignore WP:PAG when it comes to policing new pages. I created a new page a couple weeks ago and it was deleted within what felt like seconds, even though it was about a large US company that had recently changed its name (hence the new article) but was already obviously notable because the page showed had several subsidiaries with their own articles. A bit less absurd than deleting Alphabet Inc. right when it was new. I guess the folks who do new page patrol are generally trigger-happy/terse/aggro, because the bulk of what they see is non-notable self-promotional trash, and that's just the way it is. You could 'win' the RFC in favor of a bit more clearly mandated restraint on deletions being written into policy and I bet the status quo wouldn't change.

  Dealing with the gunshots left a bad taste in my mouth. I found a way to put the content on an existing page and don't even care to look back to see if the page is still alive. RudolfoMD (talk) 08:43, 10 October 2023 (UTC)

• Yes, secondary independent sourcing is needed/leaning Bad RFC

I have to agree with the others above this attempt to “spike” BM’s RFC was distinctly on the cheesy side as a move. I’ve also go to ask if WP:BEFORERFC was followed. Finally the question is not neutrally formatted.

But addressing the question directly: yes, we need independent secondary sourcing in all of our articles as a basic way of avoiding original research and maintaining a neutral point of view, as well as avoiding hoaxes and inaccuracy. We can discuss when that needs to be established, but it needs to be there eventually. At the very least no later than a primary-facile case that it doesn’t exist has been put forward (eg by pointing out that the article sourcing includes no independent, secondary sourcing and that none appears to exist elsewhere). FOARP (talk) 18:01, 5 October 2023 (UTC)

• Yes and no - it depends on the nature of the source and what it is being used to verify. Some primary, non-independent sources are sufficient to fully verify that the subject of an article exists and is not a hoax, others are not. For example we do not need a source independent of an organisation to verify that Person X is an employee of that organisation; a book verifies it's own existence, author, date and place of publication, etc. A researcher's statement that they have discovered a room temperature superconductor verifies that they have claimed that, but an independent source is required to verify that the claim is correct. It is important to note that questions of verifiability are completely independent of questions of notability, and both are separate to and independent of questions of neutrality and balance. The three must not be confused or conflated. Thryduulf (talk) 18:43, 5 October 2023 (UTC)
• I wonder if this is the right question. As there is disagreement of what the current status quo is, a better question might be what the future consensus should be. The current question appears to try and retroactively apply a consensus. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 19:32, 5 October 2023 (UTC)

• Bad RFC, the question is ridiculously ambiguous (are we supposed to answer that yes the status quo as described at WP:OR and at WP:N is indeed that all articles not only must have secondary sourcing but also must be based upon it, and that it is further needed to establish notability; or that yes, the expectations at AfC, NPP, and AfD broadly enforce this requirement; or that yes a topic for which no secondary sourcing can be found should be deleted?).

JoelleJay (talk) 20:01, 5 October 2023 (UTC)

• Comment - as the creator of the section, I did not at all intend this filing as an RfC. I am asking editors for their views to assess the current community status quo about one main point - does NOR currently establish a requirement for secondary sourcing that can be used, e.g., as a grounds for mass article deletion, or would that represent a change in policy? But I am also hoping for input on more general questions, like: is WP:NOR supposed to bear on deletion discussions only if synth is an issue, or more generally? Does all of NOR on article notability trump everything in WP:N, because the former is a policy and the latter a guideline, or do questions of scope also come into it?

I was really hoping for fruitful threaded discussion rather than sterile !votes, but as the old men have said, you can't always get what you want. Newimpartial (talk) 20:14, 5 October 2023 (UTC)

• Comment. I think one problem that has been muddying the waters of this general debate is that different groups mean entirely different things by "secondary" and there's also considerable debate about what exactly "independent" means. Espresso Addict (talk) 22:51, 5 October 2023 (UTC)

  I think that in general, "secondary", "independent" and "significant" are not nearly as clear-cut as a lot of us act a lot of the time. XOR'easter (talk) 00:32, 8 October 2023 (UTC)

Supplying surnames for siblings

[NOTE: I have edited my own text here, for better clarity, based on the discussion below.]

Hello. I would appreciate other editors' thoughts as to whether it's good practice to include, rather than omitting, surnames, when an important reference is made to a sibling of someone already mentioned, even when the surnames are the same. My perspective is that, as with spouses, sharing a surname should not be presumed just because two individuals are siblings, given all the reasons that this might not be the case, even though it's true more often than not. Beyond this, it seems just basic encyclopedic decency to identify someone by their full name at first mention. (The exception would be if the reference to the sibling were a trivial mention in passing.)

If you have a moment, please look at the reversion of my edit here:

http://en.wiki.x.io/w/index.php?title=Fanny_%28band%29&diff=1179379930&oldid=1179333240

and the discussion between the two parties concerned in the reversion here:

http://en.wiki.x.io/wiki/User_talk:Binksternet#Surnames

Thank you. Jcejhay (talk) 22:01, 9 October 2023 (UTC)

I think where related folks share a surname, it's more readable if that surname is not repeated. It is understood by the common reader of English, and the addition can make things stiff and awkward. (Bob Bobbington was raised with his older brothers Freddie Bobbington and Stan Bobbington, and younger sisters Barbara Bobbington (now Barbara Bobbington-Hemsworth) and Flossie Bobbington.) And if these people are not separately notable, the surname isn't even particularly important. -- Nat Gertler (talk) 03:27, 10 October 2023 (UTC)

@NatGertler I agree, for the sort of example you're giving. That's what I'd call a "passing mention." But if you look at the instance that brought up the difference of opinion, you'll see that it's about a rock band, where the text is telling us who the band members were. The band members might not all be notable enough individually to have their own articles, but within the context of the band's article they are important figures. Jcejhay (talk) 12:00, 10 October 2023 (UTC)

I've now revised my original text to make it clearer. Jcejhay (talk) 12:36, 10 October 2023 (UTC)

Yes, siblings may not share a surname. However, such sharing is so common that it is always assumed to be the case unless specified otherwise. You are arguing against the standard practice throughout the entire English speaking world. Passing reference or important figure doesn't matter.--User:Khajidha (talk) (contributions) 17:49, 10 October 2023 (UTC)

@Khajidha, may I ask you this: Would you make the same argument regarding the surname of the wife of a previously mentioned husband? Jcejhay (talk) 18:36, 10 October 2023 (UTC)

Yes. And for the surname of a husband if the wife was mentioned first. It's REALLY simple: family members with the same surname don't need to have that surname repeated. --User:Khajidha (talk) (contributions) 01:10, 11 October 2023 (UTC)

If it bothers you so much, try rearranging things so that they aren't listed one right after the other. In that case, referring to one in relation to the other becomes the clunkier formation. --User:Khajidha (talk) (contributions) 01:16, 11 October 2023 (UTC)

I think the proposed text should be rewritten to put them on an equal footing. Limiting the description of the second person to "her sister, bassist Jean" casts her in a subordinate role. My preference would be to follow the model of 30 Seconds to Mars: "brothers Jared Leto (lead vocals, guitar, bass, keyboards) and Shannon Leto (drums, percussion)". Alternatively, if there is an insistence on not repeating the surname, "sisters June (guitar) and Jean (bass) Millington".--Trystan (talk) 19:09, 10 October 2023 (UTC)

@Trystan Yes, well put: "casts her in a subordinate role." That ties in with my second point above, about what I called the "basic encyclopedic decency" of giving someone's full name (unless it's an incidental mention). Jcejhay (talk) 20:03, 10 October 2023 (UTC)

Incidentally, if June is mentioned first because she was more a driving force behind Fanny than Jean was (I don't know offhand whether or not that's the case), that doesn't seem to come across in the article. However, June was the older sister; and if rock and roll logic says that guitar is more important than bass, then perhaps these factors could explain why June is mentioned first. But I also see that in the lineup section farther down, Jean is listed first, then June, then the other two (even though both those musicians' surnames would precede "Millington" alphabetically—so it doesn't seem to be simply that Jean comes alphabetically before June). Jcejhay (talk) 20:12, 10 October 2023 (UTC)

I agree with @Trystan. "The group was founded by guitarist June Millington and her sister, bassist Jean" suggests that Jean was less important to the founding. Why not "The group was founded by Jean and June Millington"? It might help to not cram quite so much information (founding, names, instruments, relationship) into the one sentence. WhatamIdoing (talk) 02:15, 11 October 2023 (UTC)

The applicable guidelines are at MOS:SAMESURNAME. It is also helpful to review WP:WAW. —Kusma (talk) 20:10, 10 October 2023 (UTC)

Hmm...unless I'm missing something, MOS:SAMESURNAME seems to cover everything except the type of scenario we're talking about. Jcejhay (talk) 20:14, 10 October 2023 (UTC)

Sorry, then I don't understand the problem: is this about siblings where you don't know people's surnames? —Kusma (talk) 20:52, 10 October 2023 (UTC)

@Kusma Did you follow the links in my original post? That should illustrate what's at issue. Thanks. Jcejhay (talk) 21:01, 10 October 2023 (UTC)

That part seems covered by the Reagan examples. —Kusma (talk) 21:05, 10 October 2023 (UTC)

No, I don't think so. Jcejhay (talk) 21:14, 10 October 2023 (UTC)

I think the Grimm example is arguably the more relevant. However, I don't think that example implies that formulation is either mandatory or advisable when introducing individuals. The more on-point advice is in WP:WAW, to not define women by their relationships (e.g., don't reduce the person on introduction to "her sister, bassist Jean"). Compare the lead of AC/DC, which doesn't mention they are brothers until the next paragraph. Or The Carpenters, that at least puts the siblings on equal footing, rather than introducing one as an adjunct of the other.--Trystan (talk) 23:29, 10 October 2023 (UTC)

Based on some of the suggestions here, I have revised the Fanny article along the lines of "sisters June and Jean Millington." I kept June first because she's the older sister. (She's also the one whose notability level has resulted in her having her own wikilinkable article.) Jcejhay (talk) 11:39, 11 October 2023 (UTC)

Should Wikipedia offer article protection as a compromise between deletion on request and causing needless distress?

There seems to me to be a wide chasm between Wikipedia having the good sense to delete the biographies of relatively unknown people who request it, and forcing them to just live with the fact Wikipedia has an article on them because they aren't deemed sufficiently non-public to be afforded this courtesy.

There appears to be a large class of people out there who are not unknown in the sense Google will return a lot of mundane biographical material as a result of a search on their name, but who are otherwise by any other definition, private individuals who are not seeking fame or fortune.

People whose presence in the digital space is merely a by product of their career. People who are not on Wikipedia for any other reason than they exist and have achieved certain things in their career. Noteworthy but not exceptional or controversial things. In context, relatively mundane things. Things that only get written about in specialist sources to do with their specific field.

It is quite understandable that a large proportion of these people, while being comfortable with having an internet presence in the form of accurate, reliable and relevant Google results, would be distresssed at the prospect of the top result on their name one day being a Wikipedia biography. A result that is by design, potentially inaccurate, unreliable and often featuring irrelevant trivia of an often deeply personal nature.

Since there seems to be a good case to make that Wikipedia would suffer if these people are arbitrarily removed simply because they request it, given that would for example make cataloging the top echelon memberships of professional bodies permanently incomplete, a sensible compromise would appear to be to keep these biographies, but fully protect them.

This would ensure changes are only accepted if they are indeed accurate and relevant. Since by definition these people are relatively unknown, this would hardly be a burden, with their biographies unlikely to see more than a handful of non-trivial edits over their careers, and perhaps none once they retire. And rather obviously, biographies of such people need to be quite comprehensive before they are even published here.

Without this compromise solution, Wikipedia seems doomed to have to continually make an unenviable choice between knowingly causing distress or knowingly damaging its integrity as an almanac. A resource where by design, achieving a certain milestone in one's career comes with it an automatic presumption you are worthy of a Wikipedia biography. Edson Makatar (talk) 07:26, 9 October 2023 (UTC)

This is covered by our Wikipedia:Biographies of living persons policy. Long term full protection is not a viable solution; all these articles would quickly become outdated and actually inaccurate instead of the potentially inaccurate that you wish to prevent. —Kusma (talk) 07:37, 9 October 2023 (UTC)

There are also possibly unreasonable degrees to which living persons would seek such protection. I can envision someone who has no real privacy concerns, or no real objection to having an article on Wikipedia, nonetheless wanting to control the content of their Wikipedia article in ways we don't permit to try and use this as a mechanism to that end. BD2412 T 01:50, 10 October 2023 (UTC)

Full protection greatly impedes factual errors being corrected, or edits to bring biographies into closer compliance with relevant policies. It would lock such articles into a semi-permanent state of being potentially inaccurate, unreliable and often featuring irrelevant trivia of an often deeply personal nature. It would greatly increase the workload on administrators who would be called on to make content decisions about areas where they may lack expertise or an interest in re-writing specific content. And the number of active administrators is declining. It is the responsibility of all active editors, not just administrators, to maintain and improve BLPs. If input is desired about specific BLPs, then Wikipedia:Biographies of living persons/Noticeboard is the place to go. Cullen328 (talk) 02:31, 10 October 2023 (UTC)

I'm a WP:VRT agent. Every time I see a request from an article subject (person or company) to protect a page, it's always, without fail, a request to protect the page so that only the article subject or associates may edit it. This is neither desriable nor even technically possible. For the borderline cases, I propose the article for deletion. Otherwise, I advise the person, if they don't like what the article says, to suggest improvements on the talk page. Sometimes they do, sometimes they don't, or they send me a letter and I suggest improvements on their behalf, which are evaluated by others and either rejected or implemented.

That's how things work now. Someone distressed about having a Wikipedia article about them, which is not deletable due to notability, can contact VRT and get the response I described, or they can engage on the talk page to suggest improvements and corrections. I see no need to offer a "compromise" protection. If anything, the article should be semi-protected to prevent the COI editors from making unilateral substantive changes to it. ~Anachronist (talk) 02:51, 10 October 2023 (UTC)

The source of the distress this compromise seeks to abate, is the knowledge a biography exists, it is not being looked after, and anyone can make poor quality or even damaging changes to it. It says a lot that your only perceived beneficial use of protection is to protect Wikipedia from a subject. Perhaps that answers the question as to why some never even bother to engage with Wikipedia to even ask for a change. It must be difficult for a subject who has already seen Wikipedia apparently accept an edit that saw Google instantly transmit deeply personal and totally irrelevant information to the world, to then assume there is anyone here who is going to remove it on their behalf, never mind doing it quickly and without questioning the subject's motives. It was after all inserted right under the noses of all these editors who are supposedly keeping an eye on these biographies. But in reality probably don't exist and never did, because it stretches credulity to think there is anyone here who really cares about the biographies of these little known people given their biographies are rather famously only being added to Wikipedia at a very slow rate even though they are theoretically notable enough to be on Wikipedia and have been for decades. Edson Makatar (talk) 11:22, 10 October 2023 (UTC)

It was of course assumed that at the time it was locked, the biography had been checked for errors and stripped of irrelevant material. I do not think Administrators here are incompetent or over-worked, given some are confident enough in their own abilities they charge consulting fees. The workload here would be limited since these are little known people whose biographies would not realistically be receiving valid updates very often. The workload is surely higher when the biographies of such people are left open, since the vast majority of edits then will either be vandalism or otherwise inappropriate, or worse, as some claim, attempts by the subject to abuse Wikipedia for their own ends. Obviously the workload is negligible if there is nobody bothering to review and correct those edits made in the open model, and it seems rather obvious that it is this historical weakness of Wikipedia that causes these kinds of subjects distress. The sheer and ever present knowledge nobody here is looking after your biography (and the ever present assumption that you as the subject are a threat to Wikipedia). Too many amateurs and vandals, not enough experienced editors. Edson Makatar (talk) 11:09, 10 October 2023 (UTC)

Apart from the small issue that open editing is the very point of Wikipedia: Leaving editing open means that tens of thousands of Wikipedia editors can spot and fix issues. "Admin only" reduces the number to the low hundreds. We would not be able to deal with the additional workload you are proposing, which would likely turn into a several years long backlog. —Kusma (talk) 11:19, 10 October 2023 (UTC)

You won't know it is impossible until you try it. The sheer irony of your comment is that the existing systems of protection were brought in precisely because it is a complete myth that tens of thousands of good people stand ready to spot and correct poor or even bad edits. After all, how many of the 3,000+ American Academy of Sciences biographies Wikipedia currently has are even on your radar? My guess is precisely zero. I could go and select one at random right now, insert something true but deeply personal and entirely irrelevant, and I would bet good money that the time it takes for anyone to notice it could be measured by days or even months, not hours or minutes. It could stay there forever. And as seen above, if the subject dares to open their mouth, much less remove it themselves, they will not be treated with kindness or respect. That is the reality of the open editing model for the people whose distress is clearly real and currently unmitigated, precisely because there is not a vast army of diligent overwatchers here anymore, if there ever even was. The subject's only recourse currently is to ask that Wikipedia delete their biographiy, but it appears this does not happen very often because wanting Wikipedia to have a comprehensive almanac of Academy members is a powerful force. I happen to agree with the goal, I just don't see why all those biographies need to be left vulnerable, when the vast majority will not be in receipt of worthwhile edits very often. We are probably talking months if not years between worthwhile encyclopedic changes. Any higher, and clearly the person is not the kind of subject I had in mind for this proposal. Edson Makatar (talk) 11:42, 10 October 2023 (UTC)

If you don't think that Wikipedia has volunteers looking at new edits, I suggest you spend some time at WP:recent changes competing to be the first to revert a vandalism. About the only area of the project where we are seriously struggling and on a longterm decline is in getting new administrators, Only eight so far this year. Now is really not the time to try and put extra tasks onto our dwindling admin cadre. However if you were willing to accept a lesser level of protection, there have been discussions about increased protection for BLPs in the past. So you could read Wikipedia:Requests_for_comment/Pending_Changes_expansion_RfC#B:_PC1_protection_for_recognized,_vital,_and_BLP_articles especially the oppose arguments, and try to formulate a proposal that meats at least some of the concerns that the opposers had. Then launch a new RFC. ϢereSpielChequers 15:21, 11 October 2023 (UTC)

Just because something can be abused (although in this case I see little benefit to the subject in the proposed form of abuse) doesn't mean it shouldn't be implemented. By that logic, Wikipedia should never have been created in the first place. Edson Makatar (talk) 10:54, 10 October 2023 (UTC)

Why would the biography of a little known person quickly become outdated if open editing is disabled? By definition, for these sorts of people, there will be very little change in what Wikipedia can say about them over time. Edson Makatar (talk) 10:51, 10 October 2023 (UTC)

That excludes anybody who writes or publishes, for example academics. —Kusma (talk) 11:10, 10 October 2023 (UTC)

It really doesn't. There is a long tail of little known authors and academics with biographies here whose latest book and paper can be safely ignored by Wikipedia, the encyclopedia (whose role is after all to summarize and analyse, rather than merely document). They are ironically the very people who probably try to abuse Wikipedia by using it as some kind of free CV service, updating their bibliographies whether the works were significant or not, and so end up inadvertently being subjected to the very protection that is not afforded to those for whom having a presence on Wikipedia is a source of great distress. Edson Makatar (talk) 12:01, 10 October 2023 (UTC)

Accepting for the sake of argument that protecting BLP articles on request would be workable, do you have any evidence that there exist any BLP subjects who would prefer to see their articles fully protected but otherwise subject to normal wikipedia processes? Is there any evidence that there are any BLP subjects who would actually be helped by this proposal? Caeciliusinhorto-public (talk) 15:05, 10 October 2023 (UTC)

I have no such evidence. Do you have any reason to believe a subject wouldn't be happy with this as a compromise solution? If, as seems to happen a lot, they request deletion because they are a low profile individual, but many people here tell them to go jump in a lake because they are notable in a mundane sense and their presence here completes a notional set of people with X achievement in Y field. Edson Makatar (talk) 18:19, 10 October 2023 (UTC)

I'm completely failing to understand what they are complaining about in the first place.--User:Khajidha (talk) (contributions) 18:30, 10 October 2023 (UTC)

All the time! Where information is inaccurate I will fix it quick smart. The problem is that most complaints are not about the accuracy of the information presented. The most common complaint is that the image in the article is unflattering and that they would prefer a high-quality, professional, publicity image. I tell them to upload an image that meets our requirements. However, I also get requests to remove reliably sourced information that they find embarrassing for one reason or another. For example, athletes found reports on how much money they received in grants embarrassing because it showed that some members of the team got far more than others. I have learned to treat these requests carefully, as sporting bodies will come down on the athletes like a ton of bricks if they find out about attempts to remove such information. Hawkeye7 (discuss) 18:47, 10 October 2023 (UTC)

CN tagging fiction for citations for basic plot points in the fiction

FYI

 – Pointer to relevant discussion elsewhere.

Please see Wikipedia:Reliable sources/Noticeboard#CN tagging fiction for citations for basic plot points in the fiction. Most of the responses to far have basically been off-topic, trying to address whether media references/popular culture material is best included in the article in question, rather than the posed question of whether an inline citation is required that a work contains the plot point that it contains.  — SMcCandlish ☏ ¢ 😼  13:24, 9 October 2023 (UTC)

The section heading is misleading. The question is whether mentions in "In popular culture" sections require citations, and the answer is "yes", even for statements that would not require citations as part of the plot section of an article about a work of fiction. —Kusma (talk) 13:36, 9 October 2023 (UTC)

More strongly, for "in popular culture" sections, I would generally require citations to independent publications, not merely citations to the fiction itself. That way we have some sourced evidence that this plot point is actually of significance to the fiction in question, not just a throwaway mention. —David Eppstein (talk) 18:47, 10 October 2023 (UTC)

• The reason why most of the responses were “off topic” is because the initial challenge/question was focused on the wrong policy. The underlying problem with the article wasn’t really that the material was unverifiable… the problem was that it was TRIVIA (a common problem when it comes to “in popular culture” sections). Remember that Verifiability does not guarantee inclusion. Material can be deemed irrelevant, trivial, or undue to mention, even if it is verifiable. Blueboar (talk) 13:39, 10 October 2023 (UTC)
• If this is about sourcing for "in popular culture"-style items, then WP:IPCV would seem to sufficiently cover the matter, including a footnote to the RFC that established not only that sourcing is generally required, but that it generally should be secondary sourcing. DonIago (talk) 16:25, 13 October 2023 (UTC)

Specify animal/plant care guides in WP:NOTGUIDE

I edit a lot of articles for various animals and by far the most common issue I come across is care guides for pets, either uncited or citing a pet store/hobbyist page. There’s undoubtedly hundreds more I haven’t found, and a lot of these stay up for years. Recommending specific enclosure sizes, humidity, diet, etc. These are often outdated or dangerous, and they are always subjective as all husbandry is. While I’m sure it wouldn’t completely fix the issue (considering these guides always lacking reliable sources anyways), I feel it might help if animal/plant care guides were explicitly mentioned in WP:NOTGUIDE. PoetaCorvi (talk) 07:30, 27 September 2023 (UTC)

@PoetaCorvi, if you have a suggestion how to add this to the first point of WP:NOTGUIDE, please mention it at WT:NOT. —Kusma (talk) 09:35, 27 September 2023 (UTC)

I doubt that it would make any difference at all, because Wikipedia:Nobody reads the directions. WhatamIdoing (talk) 21:29, 13 October 2023 (UTC)

Is it time to revisit "opt out" and BLPs?

In preparing to comment on the suggestion several threads up by Edson Makatar regarding protection of BLPs, I came across this failed proposal from 2013 which suggested that BLPs, other than those for elected officials, could be deleted at the request of the subject. That seems overly harsh and inconsistent with WP:NOTCENSORED. However, is there any feeling that the proposal might be workable if it offered a much more modest accommodation? Specifically, I had in mind providing that BLPs in these circumstances could have the NO INDEX tag applied to them (instead of being deleted)? I'd also add a carve-out to BLPs listed in Wikipedia:Popular pages (in addition to those for elected officeholders).
This should ameliorate NOTCENSORED concerns as no content is actually being removed. And, truthfully, my interest in this has less to do with the privacy of persons as it does with improving the style of BLPs. Offering "opt out" would provide a mild disincentive to WP:LEAD section manipulation and promote a more collegial editing atmosphere by significantly lowering the stakes. Chetsford (talk) 01:16, 14 October 2023 (UTC)

There is already a provision for admins to delete BLPs of barely notable individuals when closing a deletion discussion. I genuinely can't follow from your post what you are suggesting beyond noindexing BLPs on request but I would not support that. The direction of travel for a long time has been that BLPs must be properly sourced and the only real change I would make would be some kind of UNDUE protection so that BLPs don't become hit jobs simply because the only sourcing we have is something bad about the person. Spartaz ^Humbug! 06:20, 14 October 2023 (UTC)

"I genuinely can't follow from your post what you are suggesting beyond noindexing BLPs on request" Good news! You actually are following what I'm suggesting as that's it: noindexing BLPs on request.

"the only real change I would make would be some kind of UNDUE protection" I think we already have that, but I'd be interested in hearing more. In any case, I think my proposal is more about article quality and overall project experience than anything else. In closing RfCs I've noted that a not insignificant number of these requests originate out of disagreements with the first few sentences of the lead of a BLP. I don't believe this is coincidence. Rather, some editors occasionally try to "float" the most tawdry aspects of a BLP's life to the top of an article so it will appear in search engine snippets. These disputes generally lead to inferior articles and a sometimes toxic editing environment. Providing for optional noindexing of some BLPs that, while they meet our notability standards may not be persons of urgent public concern, would mitigate that to some extent by removing the incentive without limiting content accessibility. Chetsford (talk) 21:06, 14 October 2023 (UTC)

Correct me if I'm wrong, but if a NOINDEX tag is added to an article after search engines have already indexed it, doesn't that fail to have the effect of search engines removing the page from their search results? I thought once it's indexed, it's indexed. ~Anachronist (talk) 22:08, 14 October 2023 (UTC)

It depends on the exact search engine, but most respect the tag even when the content is previously indexed AFAIK. ― novov (t c) 01:24, 15 October 2023 (UTC)

At least with the larger ones (i.e. Google, Bing), that's my understanding, too. Chetsford (talk) 03:06, 15 October 2023 (UTC)

Policies about how we interact with search engines

There's a discussion at WP:VPM#Obsolete policy proposals appearing in Google answers about how we should interact with search engines. Noting it here since it has policy implications. RoySmith (talk) 14:56, 15 October 2023 (UTC)

Discussion regarding video depicting extremely violent murders could benefit from additional community input

A discussion is underway at Talk:2023_Israel–Hamas war#Extremely violent execution video in the body section regarding a video that depicts militants shooting people and beating/chopping them to death in the street. Although I believe the issues governing inclusion/removal here are already settled under existing policy and community consensus, I nevertheless think the issue of this particular media is of substantially large enough concern and implication to warrant broad community consideration, and the sooner the better. SnowRise ^{let's rap} 03:27, 16 October 2023 (UTC)

Seeking feedback re: endorsement guideline

This comment serves as notice of a discussion that editors of this page may be interested in: Wikipedia talk:WikiProject Elections and Referendums#Interpretation of endorsement guideline re: EMILY's List/Laphonza Butler? 67.170.42.135 (talk) 01:18, 17 October 2023 (UTC)

Deprecate the minor edit system

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.

---

Partially as a result of editors who were !voting on the earlier proposal to redefine what counts as a minor edit: Should the minor edit system, an option through which edits can be marked as minor for small technical or grammatical changes, be deprecated?

• Option 1: Yes, completely.
• Option 2: Yes, except for experienced editors or admins.
• Option 3: Yes, except for bots strictly performing technical tasks or cleanup.
• Option 4: No.

My choice: Option 1. It is hard to see any benefit from this system, as it's far too easy to abuse minor edits by marking major ones as minor, and there's no penalty for not marking actual minor edits as minor. With the definition and criteria of minor edits being as vague as they are, it seems to me that the best practice would be to remove it, and if need be, potentially replace it with something else. _{Duly signed,} ⛵ WaltClipper -(talk) 17:38, 27 September 2023 (UTC)

Option 1 I don't see what having minor edits adds. People don't use them consistently, and some use them to try to hide what they've done. I don't think you can safely exclude minor edits if you're following an article. I realize we've had minor edits since the year of the Flood and it's hard to change something of such long standing. But I'd get rid of them.--Wehwalt (talk) 17:50, 27 September 2023 (UTC)

Discussion

• I spent a few minutes thinking about what utility I get out of the minor edits system, IMO the biggest one is that its effectively an "I'm a vandal who is editing in bad faith" button. Seeing a major edit marked minor is the #1 thing that makes my spidey sense tingle. Horse Eye's Back (talk) 17:56, 27 September 2023 (UTC)

  I suppose one could then argue that the "minor edit" checkbox is a honey-trap for vandals (a 1,000-byte edit marked as minor is a sure sign you've found one) which makes it easier for admins to block them, but I would also think that reducing the attack vector for vandals looking to cause trouble would be a much better idea. Removing the minor edit box is one fewer temptation to cause havoc. _{Duly signed,} ⛵ WaltClipper -(talk) 18:08, 27 September 2023 (UTC)

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

• What the actual fuck. People in the prior RfC were complaining that any !votes asking to deprecate minor edits shouldn't be counted or need to go in a separate RfC. Then when that RfC gets created, it gets insta-closed procedurally by a non-admin saying that discussion needs to be concluded. If you want me to remove the "RfC:" from the topic, actually tell me that instead of this maneuver which to me reeks of WP:NOTBURO. _{Duly signed,} ⛵ WaltClipper -(talk) 18:48, 27 September 2023 (UTC)

  People are already discussing the subject of this pseudo-RfC in the discussion above; it is counterproductive to have two concurrent, duplicate discussions. If after that other discussion has been closed, and editors wish to continue pushing for minor edits to be deprecated, then a discussion should be held planning an RfC, due to the enormous scope of a potential change (which could affect millions of editors). This would need to be advertised extensively and hosted on a more suitable location, such as VPT or a subpage. InfiniteNexus (talk) 18:59, 27 September 2023 (UTC)

  Sure looks like bureaucracy but what is the next step? The discussion above should be closed so that an RFC can be set in motion (I don't see that a simple question RFC needs to be planned).Selfstudier (talk) 19:09, 27 September 2023 (UTC)

  Yeah, I'm too lazy to do all this, but what someone should do is:

  1. Close the "proposal" discussion above, which doesn't have an RFC tag btw, and where consensus is bloody clear (it's "scrap the whole system")

  2. Revert the procedural close of this section

  3. Add an RFC template

  4. List it at WP:CENT

  I encourage InfiniteNexus or anyone else to do this. Levivich (talk) 19:12, 27 September 2023 (UTC)

  I have requested a formal close of the previous discussion at WP:CR. But like I said, additional planning is necessary for an RfC of this scale. For starters, I think the question should just be a clear-cut yes-or-no (or support/oppose). Secondly, VPP is not the best place to host this RfC; I would think VPT or VPR are better options, or perhaps it should be hosted on its own subpage like I suggested above. And finally, this needs to be advertised beyond at CENT — to reiterate, this change could affect literal millions of editors. InfiniteNexus (talk) 19:25, 27 September 2023 (UTC)

  Due to the implications of the proposal, I think there’s also a case that could be made for any RfC to have an invitation placed somewhere like MediaWiki:Sitenotice in addition to anywhere/everywhere else. Best, ^user:A smart kitten_meow 19:27, 27 September 2023 (UTC)

  We need a consensus to open a request for comment to form a consensus on something now? Congratulations, InfiniteNexus, you've invented a whole new layer of wikibureaucracy. – Joe (talk) 18:33, 28 September 2023 (UTC)

  I've never heard of needing consensus to start an RFC. It makes me wonder if you need to build consensus to seek consensus to start an RfC. Possibly, it may be required to get consensus to try to get consensus to seek consensus to start an RfC. It only gets worse from there. I think the close in that regard is open to question.Wehwalt (talk) 19:42, 28 September 2023 (UTC)

  As I have said elsewhere, this isn't your typical RfC; it's a change that could potentially affect millions of editors. At least some planning of how and where to present the RfC is necessary, not a hasty pseudo-RfC that is initiated while a discussion on the same subject is still ongoing. InfiniteNexus (talk) 00:25, 29 September 2023 (UTC)

• While this RfC is not open, how about workshopping the options? I think that keeping minor edits is fine if the feature to hide them is removed. I can live with keeping minor edits if the "hide minor edits" feature is made opt-in and renamed "hide edits marked as minor". The options to restrict use of minor edits are acceptable to me only if anyone who complains about any other editor's use of the minor edit feature earns an automatic block. —Kusma (talk) 19:46, 27 September 2023 (UTC)

  A more bureaucratic option would be a system of "minor edit reviewers" in the same way we have NPP but that seems hard to do. Horse Eye's Back (talk) 19:54, 27 September 2023 (UTC)

  There's a major gap between new pages and minor edits. I don't think we need much more than RC patrol to monitor minor edits, and creating new groups to monitor them feels excessive. How many problems are actually caused by misused minor edits that can't be covered by filtering to just minor edits in Special:RecentChanges (because yes, you can do that)? Skarmory (talk • contribs) 21:33, 27 September 2023 (UTC)

  I haven't seen any research on whether or not the misuse of minor edits actually causes more problems than it solves. As I've said above effective misuse of the tool is rare as misuse is more likely to paint a big fat target than dissuade scrutiny. Horse Eye's Back (talk) 17:44, 28 September 2023 (UTC)

• This close does seem needlessly bureaucratic, but I haven't looked in all that far, so I could be wrong. As a non-admin, I do resent your implication that non-admins are less competent, at, say, closing RfCs. Edward-Woodrow • talk 20:34, 28 September 2023 (UTC)

  That was not my implication. It was the confluence of factors altogether that I find to be generally insulting. I have no objection with a non-admin closing an RfC, particularly if it's a clear-cut outcome and you're just moving the wheels for the betterment of Wikipedia. But to outright deny a discussion from taking place truly takes some nerve, and I would hope that would come from a position of authority, if it comes at all. And that closer better have a CLUE and know their PAG inside and out. _{Duly signed,} ⛵ WaltClipper -(talk) 23:01, 28 September 2023 (UTC)

  The purpose of the close was not to "deny" a discussion from taking place; it was to temporarily slam the brakes on it because an RfC was premature. Now, how about we move onto actually discussing how to format the RfC? InfiniteNexus (talk) 00:25, 29 September 2023 (UTC)

  What's wrong with the format of this RfC? Levivich (talk) 02:42, 29 September 2023 (UTC)

  I have already answered this question several times throughout this thread, but I'll summarize here. For starters, let's talk about where it's being held: Village pump (policy). Minor edits have nothing to do with policy! I would think an RfC should be held at WP:VPT (technical) or WP:VPR (proposals), or if the discussion potentially becomes too massive, it may be prudent to create a standalone page like Wikipedia:Requests for comment/Deprecation of minor edits. Secondly, having four options (while not exactly unheard of) increases the likelihood of it ending with no consensus. Thirdly, the RfC itself is improperly formatted, missing an {{RfC}} tag and having a blatantly non-neutral question which bizarrely includes the initiator's !vote (see WP:RFCBRIEF). InfiniteNexus (talk) 02:50, 29 September 2023 (UTC)

  As to the location, it seems obvious that VPP is the most visible place for making Big Changes such as this. If it were anywhere else, it should get a pointer from VPP, but better to just have it at VPP than have the pointer IMO. Yeah it can be moved to a subpage if need be, and yeah it should have an RfC tag and be listed at cent.

  Do you have a suggestion for an alternative RfC question? "Should minor edits be deprecated?" seems like the obvious one to me. Levivich (talk) 03:00, 29 September 2023 (UTC)

  VPP is not the right place; this topic has nothing to do with PAGs. But of course, we have to make sure this RfC is visible/advertised as widely as possibly, and that means posting at the other village pumps, CENT, watchlist or site notices, tech news, large WikiProjects, etc. InfiniteNexus (talk) 03:04, 29 September 2023 (UTC)

  It seems to me the only way forward is to have an RfC on where to have the RfC. – Joe (talk) 06:44, 29 September 2023 (UTC)

  The word "kafkaesque" appears on over two thousand Wikipedia pages. Levivich (talk) 06:55, 29 September 2023 (UTC)

  VPT generally dislikes hosting RFCs.

  But let me put in a suggestion that if you expect this to attract a lot of comments, please start it on its own sub-page. This page is already 600,000 bytes long. The sheer size of the page makes it impossible for some people to participate in the discussions. WhatamIdoing (talk) 03:41, 2 October 2023 (UTC)

  In re-reading this, I want to make the following comments:

  • If minor edits have nothing to do with policy, why then was this discussion allowed to continue unabated?
  • Your second point is untrue. Any closer worth their salt will understand that options A, B, and C fall under the "remove" category while D falls under "don't remove". If there are an assortmed mix of answers in "remove" that still outweigh the "don't remove" option, it will be obvious that the consensus is for deletion and at a minimum, they would start from that baseline.
  • Several RfCs on this page don't have the RfC tag. I was planning to add it and put it on CENT once it was clear there was some interest in holding it.
  • Seriously? The question was neutral. The same page you quoted does not prevent the RfC proposer from voting. In fact it says: If you have lots to say on the issue, give and sign a brief statement in the initial description and publish the page, then edit the page again and place additional comments below your first statement and timestamp. Although I didn't sign it twice, I did put my !vote below the initial statement and made it clear it was my opinion.

  I said on your Talk Page, I wouldn't contest the close, but at this point I am about to go ahead and re-open the RfC and reformat it to your liking. I'm highly disappointed at the manner in which you interpreted my actions. _{Duly signed,} ⛵ WaltClipper -(talk) 14:13, 29 September 2023 (UTC)

  Multi option was the way to go, given the outcome of the prior RfC in this (and the bot point raised above). Yes/no was tried in the prior RfC. Levivich (talk) 14:34, 29 September 2023 (UTC)

  Please see WP:TALKFORK: Discussions should not be forked to multiple talk pages, noticeboards, or other venues, but centralized in a single place. Opening duplicate discussions wastes editorial time, scatters editorial input, and can even lead to conflicting outcomes. [...] In most cases, an open discussion is preferably kept at the place where it first began, with split-off discussions closed and retargetted to the oldest open discussion. and wait until the previous discussion (to which editors are still adding new comments) is closed. We are in no rush, unless you are in a hurry to abolish minor edits for some reason. And I am perplexed that you continue to insist on holding an RfC not about policy on a page about policy. InfiniteNexus (talk) 16:25, 29 September 2023 (UTC)

  This discussion no longer serves any further purpose. It is clear that our positions are entrenched and irreconcilable. _{Duly signed,} ⛵ WaltClipper -(talk) 17:13, 29 September 2023 (UTC)

• I'd like to ask which policy requires an RfC to have consensus to start it, which policy says that an RfC can't start while related discussions are vaguely ongoing, and why InfiniteNexus couldn't simply add an RfC tag? In other words, please justify your close with reference to policy. ~~ AirshipJungleman29 (talk) 01:56, 29 September 2023 (UTC)

  (edit conflict) Not everything editors do have to be expressly permitted by PAGs. An RfC of this scale should not be started unilaterally without giving any thought to how and where to present it. Also, WP:TALKFORK states: Opening duplicate discussions wastes editorial time, scatters editorial input, and can even lead to conflicting outcomes. InfiniteNexus (talk) 02:43, 29 September 2023 (UTC)

  Ah, an IAR close. Thanks for clearing that up. ~~ AirshipJungleman29 (talk) 16:38, 29 September 2023 (UTC)

RfC workshop

(edit conflict) So while several editors above believe it is better worth their time deliberating whether my close was appropriate, let's be more constructive and start brainstorming how a take-two RfC should be formatted. As I have written above, I think the RfC question should just be a straightforward "should minor edits be deprecated" with either "yes" or "no" options, maybe a third option if somone can come up with a alternative/compromise to deprecation. But we shouldn't go anywhere beyond three, or else that would just become too complex. InfiniteNexus (talk) 03:00, 29 September 2023 (UTC)

I don't have an opinion on the question, but as a neutral RfC covering all possibilities I would suggest:

Should the minor edit system, an option through which edits can be marked as minor for small technical or grammatical changes, be deprecated?

• Option 1: Yes, completely.
• Option 2: Yes, except for experienced editors or admins.
• Option 3: Yes, except for bots strictly performing technical tasks or cleanup.
• Option 4: No.

BilledMammal (talk) 03:05, 29 September 2023 (UTC)

I think we should also include Partially as a result of editors who were !voting on the earlier proposal to redefine what counts as a minor edit (which means nothing without context) and a random !vote at the end. InfiniteNexus (talk) 03:08, 29 September 2023 (UTC)

Sarcasm aside, those four options do not accurately represent what editors in the previous (and still ongoing) discussion believe are our best options. Bots were barely even mentioned. InfiniteNexus (talk) 03:12, 29 September 2023 (UTC)

The point of an RfC is to request COMMENT so that if people have a different option in mind, they can suggest it and it can then be added to the RfC options. _{Duly signed,} ⛵ WaltClipper -(talk) 11:13, 29 September 2023 (UTC)

We'd be more likely to get comments if we didn't provide a numbered list of options.

Even re-writing it into prose would encourage comments. Contrast the numbered list with "Some editors want to get rid of it, and others would like to keep it as-is, but there have also been suggestions that it should be hidden from most new editors, while remaining available to admins or other experienced editors, or that it should only be used by bots (e.g., when approved as part of the Wikipedia:Bots/Requests for approval process for tasks that might flood watchlists but are unlikely to interest editors)." WhatamIdoing (talk) 03:54, 2 October 2023 (UTC)

We could also do something simpler, like keep the minor edit system, but allow any editor to mark any edit as minor. That would allow people who like it to use it but remove the arguing. —Kusma (talk) 06:05, 29 September 2023 (UTC)

Isn't all the arguing happening because other editors use it? Or did you mean that I could mark your edits as being minor? (The Database administrators might object to that.) WhatamIdoing (talk) 03:35, 2 October 2023 (UTC)

I had a quick glance over the previous discussion a few days ago, and I feel there's some support for considering the flag semantically equivalent to a part of the edit summary. I think not hiding minor edits by default would be more consistent with that, though I'm not sure it's actually worth breaking that out into a 4b or something. Also, extending what Kusma brought up a little, I wonder if it would be worthwhile giving people doing RCP a way to easily tag edits with s indicator of what it did similar to the canned edit summaries that see occasional use. Alpha3031 (t • c) 07:46, 30 September 2023 (UTC)

And I just discovered that there was already an RfC two years ago. InfiniteNexus (talk) 03:45, 29 September 2023 (UTC)

There are all those editors above saying "Throw whole system away" or equivalent so maybe that's the only question that needs an answer from the community at large, should it or shouldn't it be thrown away (suitably phrased).Selfstudier (talk) 11:18, 29 September 2023 (UTC)

That's the question asked in the RfC from two years ago, which closed with a suggestion to poll restricting minor edits to autoconfirmed users (hence option 2). The discussion above also raised the issue of bots (hence option 3). I think given the prior discussions, the four options make sense. Levivich (talk) 14:08, 29 September 2023 (UTC)

Well, if you're brainstorming ideas, here's one: Rename "minor edit" to "typo fix". - jc37 10:09, 30 September 2023 (UTC)

Renaming it won’t change anything. The abusers and vandals would still attempt to “hide” substantial edits by marking them as “typo fix” edits. And the rest of us would continue to have to pay extra attention to any edit so marked, for precisely that reason. Blueboar (talk) 14:55, 1 October 2023 (UTC)

Is it really impossible for the system to identify minor-marked edits that are plainly bad faith? If they could be de-marked as minor automatically, or a filter created to list them for special attention, the rest of us could get on with marking edits as minor and not flooding watchlists with our obsessive need to italicise periodical titles, or whatever. Espresso Addict (talk) 21:22, 1 October 2023 (UTC)

You could probably detect changes within a particular size range with reasonable accuracy, e.g., changing something in more than one paragraph, or changes that affect more than X characters. You could do something fancier in the visual editor than in the old wikitext editors, but I think something could be detected in most cases.

@Matma Rex probably knows what would be realistic. WhatamIdoing (talk) 03:38, 2 October 2023 (UTC)

Well, one realistic thing we already do is measuring the size of the change (the green and red numbers in page history), but that doesn't always identify change as minor (or as good-faith). I think the canonical example of this problem is a change that just changes a date – it's a one-character change, but it's not minor, and it could be bad-faith. Matma Rex talk 14:09, 2 October 2023 (UTC)

Matma Rex Indeed! But is there really no way of automatically detecting that? There are very few reasons for changing numbers or dates with a minor edit designation (perhaps clearly typo'd years?). Espresso Addict (talk) 00:45, 3 October 2023 (UTC)

I could see updating an as-of date when nothing has changed as being minor in at least some situations, such as where it is guaranteed that the change would see references to back that up but lack of change will not. The first examples that comes to mind are major disasters, updating an article from saying a 2004 event was the largest/most deadly/most costly/most destructive/etc "as of 2018" to "as of 2023" when no significant events of the type have occurred in the place in the intervening years is minor. Thryduulf (talk) 10:47, 4 October 2023 (UTC)

So then a contentious WP:ENVAR change could be potentially marked as a "typo fix"? There's really no such thing as a "minor edit" unless you're restricting yourself to changes that solely change the source without affecting the article at all. ~ F4U (talk • they/it) 08:37, 9 October 2023 (UTC)

Something like Special:Diff/1178878685 is a minor edit that is not a typo but does affect the article. Thryduulf (talk) 11:14, 9 October 2023 (UTC)

Next steps

The previous RfC has been closed by an uninvolved administrator. The closing statement precisely illustrates why it was right for WaltCip's botched RfC to be procedurally closed: By my reading I do see consensus to create a formal RfC about minor edits. Such a process would need to be well-planned, centrally located, and well-advertised. So, what next? InfiniteNexus (talk) 16:53, 10 October 2023 (UTC)

The next step is to carefully plan an RFC. As I see it the very first question to ask is:

Should the option of marking edits as minor be:

1. Retained as is
2. Retained, but modified in some way (e.g. limiting who can use it, changing definitions of what counts as a minor edit, etc)
3. Deprecated - existing edits marked minor will remain so marked but the option to do so will be removed.
4. Removed completely - the minor edit flag will no longer be displayed for any edit in the history of Wikipedia, this may or may not be reversible.

If the consensus is for option 1 then there is no point spending time on anything else. If the consensus is for options 3 or 4 then the process for deprecating should be initiated (what that process is and how long it will take, and whether we get a choice between options 3 and 4, should be established before the RFC). Only if consensus is for option 2 is it worth time working out how to modify it, so that should form a second RFC.

In terms of modifications there are at least two independent strands

• Who can mark an edit as minor (e.g. anyone, autoconfirmed editors, extended confirmed editors, administrators, people with some right (new or existing), etc).
  • Which options are technically possible to implement, what the process for implementation is and how long it will take need to be established before the RFC.
• What edits count as minor.
  • One option would be to collate a small list of mutually compatible options and asking people to pick which they think should be marked as minor.
  • I would suggest not allowing new options to be added during the RFC to stand a chance at consensus.
  • Ideally there should be some clear statement about what the current definition is (regardless of what people think of it)

Any other ideas should be collated and formed into independent strands, so that the second RFC has only a small number of questions (in the unlikely event I've thought of everything that would be two questions). Thryduulf (talk) 18:34, 10 October 2023 (UTC)

As someone who supported throwing the whole system out and still supports doing so, is there anyone who actually wants the fourth option of the minor edit flag will no longer be displayed for any edit in the history of Wikipedia? Keeping the tag there will be necessary, for example, for past discussions over specific edits being labeled as minor to make sense. I feel like the better selection of options would be:

1. Minor edits retained as is.

2. Retained but limited to certain users.

3. Retained with some other change.

4. Depreciated. Edits will continue to be marked as minor, but the option to do so will be removed. ~ F4U (talk • they/it) 02:01, 11 October 2023 (UTC)

I don't like the Retained but limited to certain users option. What "certain users" are we talking about, and what is the purpose of making minor edits a pseudo-right? Other than that, I agree with the three choices. InfiniteNexus (talk) 04:02, 11 October 2023 (UTC)

No change, change, deprecate. Levivich (talk) 04:25, 11 October 2023 (UTC)

@Freedom4U I don't know whether anyone would want that (afaik the question has never been asked), but it might be what deprecation means - it will depend how developers implement deprecation. Offering those four options wouldn't be very useful I don't think because 2 and 3 are not necessarily mutually exclusive and you'll get people arguing about the vagueness. @Levivich's concision of my list is a better first step I think (although the options should be more verbose than that, but less verbose than my offering).

@InfiniteNexus those questions should be workshopped before a second RFC (if the consensus is for change rather than no change or deprecation). The purpose of pseudo-right would be to grant it to those people who can be trusted to use it appropriately. It was just a suggestion for a change that might be possible and something that should be discussed in the workshopping for RFC 2. Similarly @Kusma's suggestion below is an option that should be presented in RFC2 if RFC1 decides change is desired. Thryduulf (talk) 10:40, 11 October 2023 (UTC)

I note that the "nominornewtalk" user right depends on an edit being marked as minor to suppress the normal talk page edit notification. Removing the ability for archiving bots to mark edits as minor would likely be annoying to people. Anomie⚔ 11:43, 11 October 2023 (UTC)

We could have the minor edit right only available to bots (even if that looks a bit redundant with the bot flag). —Kusma (talk) 14:51, 11 October 2023 (UTC)

The entire harm that can be done by the minor edit flag goes away if we remove the "hide minor edits" option from the watchlist. If that is done, then minor edits are just a decorative edit summary. It is also a smaller software change than removing the ability to mark edits as minor. I would like to see such an option in the RfC. —Kusma (talk) 05:46, 11 October 2023 (UTC)

That might be a suitable compromise. We can easily write some JavaScript to hide the minor edits after this useful feature is removed. Certes (talk) 10:44, 11 October 2023 (UTC)

At a quick glance it looks like it would actually be a larger software change. Removing the ability to mark edits as minor should be able to be accomplished by simply removing the "minoredit" user right from appropriate groups. That's a configuration change, no code change necessary. But when I look at the watchlist code, I don't see any option to remove the "hide minor edits" option there. Anomie⚔ 11:37, 11 October 2023 (UTC)

@Anomie, thanks. How hard would it be to change the default of that option? —Kusma (talk) 14:49, 11 October 2023 (UTC)

You mean how hard would it be to change the rights of the groups here on enwiki? Not hard. Once we have consensus someone would file a task along the lines of phab:T344150, then someone would make an update similar to this (affecting this subarray).

Or do you mean changing the default of the "Hide minor edits from recent changes" and/or "Hide minor edits from the watchlist" preferences for new users? The defaults for both are already off. Anomie⚔ 16:55, 11 October 2023 (UTC)

• Just a driveby comment from someone who uses minor edits a lot (both checking edit histories and marking my own edits), I would be surprised if the broader community were in favour of totally removing either the ability to mark as minor, or the useful-with-caveats ability to filter them out, but I personally might well support some sort of a middle option to limit ability to mark as minor to some group, especially if the right could be reversed if abused, and could see that reaching consensus. Espresso Addict (talk) 22:39, 13 October 2023 (UTC)

  If you browse the recent discussion about this, you'll find that a substantial amount of the participating editors do want it totally removed, myself included; this is even noted in the closing statement. And I would also not support restricting it to a curated subset of users, but I'm happy to let the proposed RfC play out on that one. Orange Suede Sofa (talk) 01:12, 14 October 2023 (UTC)

I read the original discussion. I'm trying (obviously not so successfully) to call attention to the fact that the majority of content editors on Wikipedia rarely if ever read Village Pump, they just get on with editing, often using minor edits contentedly. Any proposed RfC would, imo, be well advised to include more nuanced compromise options than "status quo" vs "nuke 'em from orbit". Espresso Addict (talk) 00:09, 15 October 2023 (UTC)

Which is why I suggest a first RFC should have three options "keep as is", "keep but change in some way", and "deprecate". @Orange Suede Sofa it has also pointed out by multiple people that not everybody who wants to keep minor edits saw the first discussion as relevant to their views so they did not contribute. Thryduulf (talk) 09:20, 15 October 2023 (UTC)

I'm also someone who focusses more on building content than hanging around the discussion pages. (With exceptions.) I'll use the "minor edit" flag not only to indicate fixing minor things like typos or dropped words, but if I make an edit & don't care if it gets reverted. Any RFC that has only the options "keep" or "nuke 'em from orbit" will get an automatic keep vote from me. -- llywrch (talk) 20:43, 19 October 2023 (UTC)

Use of present tense for old TV series

I understand that creative works such as books or musical compositions live in the eternal present, but, to me, e.g. "The Partridge Family is an American musical sitcom starring Shirley Jones and featuring David Cassidy" (see article The Partridge Family) sounds completely wrong, or misleading, as if the sitcom is still being produced. If other people agree, and there is some written policy about this, the perhaps the policy could be revised. 2A00:23C8:7B09:FA01:8D1A:F39B:AA2D:F393 (talk) 23:01, 2 October 2023 (UTC)

The applicable guidance is MOS:TENSE: By default, write articles in the present tense, including those covering works of fiction (see Wikipedia:Writing better articles § Tense in fiction) and products or works that have been discontinued. Generally, use past tense only for past events, and for subjects that are dead or no longer meaningfully exist. Use past tense for articles about periodicals no longer produced, with common-sense exceptions. Probably the best place to begin a discussion on it would be Wikipedia talk:Manual of Style. Schazjmd (talk) 23:17, 2 October 2023 (UTC)

I can watch The Partridge Family on Roku right now if I wanted too. I am watching episodes of The Mary Tyler Moore Show with my wife, for laughs. Both shows are roughly 50 years old, and both are still being watched. Cullen328 (talk) 23:54, 2 October 2023 (UTC)

Not to mention, Romeo and Juliet is a tragedy written by William Shakespeare RoySmith (talk) 00:26, 3 October 2023 (UTC)

From my perspective, each individual episode "is" but the series "was". But I also disagree with the idea of plot summaries being given in present tense. Fiction isn't written that way (or at least only a vanishingly small percentage is) and our recounting of the events of fiction puts us even further removed from the events of the work. User:Khajidha (talk) (contributions) 13:37, 5 October 2023 (UTC)

Which is good. Our material should never be confused with fictional content, and we have MOS:WAF guideline to help prevent erosion of the barrier between in-universe and out-of-universe writing.  — SMcCandlish ☏ ¢ 😼  20:03, 8 October 2023 (UTC)

In this case, the lead could easily be edited to make it clearer that the series is old; I have attempted another version. Espresso Addict (talk) 00:38, 3 October 2023 (UTC)

We write, generally "X is a television series that ran from YYYY to YYYY", establishing the past/present duality quickly. Masem (t) 18:04, 10 October 2023 (UTC)

It makes sense to me to use the present tense for works that still exist. The Odyssey also is one of two major ancient Greek epic poems attributed to Homer, for example. To say that either was a television show, or was an epic poem, would sound like they'd been destroyed or transformed into something else, to me. – Joe (talk) 13:46, 5 October 2023 (UTC)

Yes, there are a lot of lost works (including a substantial amount of Hollywood's earliest output), for which past tense would be appropriate.  — SMcCandlish ☏ ¢ 😼  20:07, 8 October 2023 (UTC)

I must admit to finding present tense for old TV shows to be odd, but I suspect that is because I grew up in an era where TV shows were much more tightly coupled to their broadcast date. Once that date passed, it felt very much like the show was a past event rather than an extant product. There are 1940s and 1950s shows that were never recorded, and no longer exist. I think it still makes more sense to think of these as events that were more than products that are. But for everything else, there’s a long term trend towards TV-as-product rather than TV-as-event. From reruns to home media to streaming, TV shows have become progressively more accessible on-demand. Today, there are streaming-native TV shows which have a release date rather than a broadcast date, and we expect them to endure indefinitely as cultural artifacts and objects of study, exactly analogous to how we think of books. Thus TV shows have become almost entirely productlike, with indefinite existence, and almost entirely un-eventlike. As a result of this trend, I think we are seeing a shift in language from past tense to present tense when it comes to TV shows, and although I still find it weird to hear “The Flintstones is…”, I think that weirdness may pass with my generation. Barnards.tar.gz (talk) 06:26, 14 October 2023 (UTC)

I think eternal present tense for fiction works perfectly, and that includes serialised TV shows, which are becoming more and more like feature films in recent years anyway. I find it less clear that present tense is appropriate for 1970s American game shows other than The Price Is Right. —Kusma (talk) 08:18, 16 October 2023 (UTC)

Use of eternal present tense should be restricted to fansites like Memory Alpha. Television shows logically have three phases of life - before, during and after their original broadcast run. All coverage therefore neatly fals into one of thee three phases, buzz, reception and legacy. It follows therefore that a live encyclopedia should show the presence of mind to signpost to the reader what stage of life the show they are reading about is in. X is a planned, X is a, X was a. Edson Makatar (talk) 18:28, 10 October 2023 (UTC)

How is a television series different from other media which also have original runs, such as movies that have theatrical releases or books that have printing runs? Orange Suede Sofa (talk) 05:12, 13 October 2023 (UTC)

I would say the difference is, when there's an ongoing series, it's a continuing entity that is yet to be completed. A movie can be shown a bunch of times, but it's "in the can"; it isn't going to change certain meddlesome directors notwithstanding. An ongoing series is a living entity; what happens to it next season is not yet determined.

But that's an after-the-fact rationalization. The real reason is that this is how people speak of these art forms in real life. Casablanca is, but I Love Lucy was. That really is the tense that is overwhelmingly used in English, and when Wikipedia goes against this convention, it's jarring. --Trovatore (talk) 05:39, 13 October 2023 (UTC)

Is there any reliable data regarding this is how people speak of these art forms in real life? I know I'm just one person, but I say things like "hey, you should watch Blake's 7, it's an old BBC series..." where it's is in the present tense. I recognize that I'm just one person though, so I'd prefer to rely on broader data over individual assertions. Orange Suede Sofa (talk) 05:49, 13 October 2023 (UTC)

Hmm. I might use the present tense in that context, too. I still find it jarring in an introductory sentence defining the term. Fair point on finding data; I don't really know how to do that, and a naive corpus search is not going to be very indicative because of this context issue. For myself, I can only report my reaction to the Wikipedia convention on these, which it seems a number of others share. --Trovatore (talk) 06:05, 13 October 2023 (UTC)

The convention in literary analysis is to analyze the work of art in the present tense, outside of the events in the real world. The work continues to have its various properties, regardless of when it was published. When discussing a work in context of real world events, of course, the corresponding tense is used (Casablanca was a solid if unspectacular success in its initial run). I think there may be some implicit context in some situations when discussing TV shows, where the speaker is implicitly referring to its original broadcast release. Similar situations can arise with the any work, of course, including movies. isaacl (talk) 16:14, 13 October 2023 (UTC)

But TV series as wholes are not works of art; the individual episodes are. The series were continuing events at the time they happened, and if they've stopped, then those events are in the past. --Trovatore (talk) 16:18, 13 October 2023 (UTC)

Wikipedia as a whole is a creation by people, even if it's composed of individual articles. The broadcast airings of a show were events. As I mentioned, I agree some people may be implicitly referring to the (broadcast) release in some contexts: ...Casablanca was an A-list film .... isaacl (talk) 16:23, 13 October 2023 (UTC)

I see the series as recurring events, comparable to say the Tournament of Roses or the Main Street Electrical Parade (I'm trying to think of one that has stopped; I thought the Electrical Parade had, but it seems it's been revived). I think everyone would agree that, if those stopped definitively, we'd use the past tense for them? We should use the past tense for I Love Lucy for the same reason. Lucy was never a unified creation; it was a recurring event. --Trovatore (talk) 18:11, 13 October 2023 (UTC)

In a world where broadcasts are transitory and can never be seen again, perhaps. But in a world where works are published in an on-demand form, including physical media, shows aren't just one-time events. In addition, a work can both be transmitted as an event, and discussed in the past regarding that event, and also exist as a creative work to be analyzed, employing traditional conventions. isaacl (talk) 21:16, 13 October 2023 (UTC)

Again, this argument is an abstract linguistic/philosophical analysis, which is probably how the current WP convention originated. It's unnatural and jarring for native speakers, and that's the real problem, all the metaphysics aside. --Trovatore (talk) 21:23, 13 October 2023 (UTC)

I appreciate you find it jarring, however I do not personally feel all native speakers find it so. Context applies equally well to Casablanca as other forms of entertainment, and there are some cases where "Casablanca was" is more appropriate than "Casablanca is", and vice versa. isaacl (talk) 05:24, 14 October 2023 (UTC)

"All" native speakers? No, surely not. That's a pretty low bar. It's jarring enough to enough native speakers that it should be changed. --Trovatore (talk) 19:01, 14 October 2023 (UTC)

Isn't there a certain conflation here between the creative work itself and the event of its publication? Charles Dickens published Bleak House in a serial form between March 1852 and September 1853; during its publication, it was a recurring event. It is quite proper to say that the recurring event of the publication of Bleak House was, and that it will never happen again; but it doesn't make sense to me that for this reason we should say that Bleak House, the work of art, was; rather, we should say that it is, because it continues to exist.

To put it another way, if we had an article titled "Serial publication of Bleak House", it would be quite proper to say that "Bleak House was published serially from March 1852 to September 1853." In the same way, if the Rose Parade had stopped last year, it would have been proper to say "The Tournament of Roses Parade was an annual parade" etc. etc., because the Tournament of Roses Parade would have been a series of events that had ceased happening. We do not have an article about the Tournament of Roses Parade as a unified artistic whole, but if such an article could reasonably exist then it would seem perfectly reasonable to me to use the wording "The Tournament of Roses Parade is an artistic work" etc. etc.

Now to I Love Lucy. If we had an article titled "Initial broadcast run of I Love Lucy", then it would make perfect sense to me to use the phrasing "I Love Lucy was first broadcast from October 15, 1951, to May 6, 1957" etc. However, we don't have such an article; we only have a single article whose task is to combine information about I Love Lucy as an artistic work, and information about I Love Lucy as an event (i.e., its publication history) into a cohesive whole. From that perspective, I think the lead sentence of the article is quite workable: "I Love Lucy is an American television sitcom that originally aired [past tense!] on CBS from October 15, 1951, to May 6, 1957"; that is, I Love Lucy, the creative work, continues to exist and therefore is; but I Love Lucy, the set of television performances broadcast from 1951 to 1957, was a series of events that has ended.

This seems to be lifted almost wholesale from the theatrical convention: the specific run of a play at a theater was a series of events, but the play itself is an artistic work that continues to exist even if nobody is performing it. Shells-shells (talk) 20:33, 16 October 2023 (UTC)

There is no unified artistic work called I Love Lucy. But again, that's not the real issue. --Trovatore (talk) 20:39, 16 October 2023 (UTC)

What about TV series that are revived, such as Murphy Brown or Will & Grace? DonIago (talk) 05:23, 13 October 2023 (UTC)

When they are revived, there are two choices: Make a separate article for the reboot (which would be in present tense), or restore it to present tense because it is currently going on. --Trovatore (talk) 18:15, 13 October 2023 (UTC)

Buildings have planning, construction, and completion phases, but we tend to refer to them in present tense while they exist. It's also worth noting that some television shows gain their highest popularity, and establish their long-term impact, after their initial broadcast run. CMD (talk) 05:38, 13 October 2023 (UTC)

The same in the context of the Corporate world. We don't say Commodore is a manufacturer of computers. I believe for TV programmes that have finished it should be was, to show that it is no longer made. Davidstewartharvey (talk) 06:44, 14 October 2023 (UTC)

TV programs are the outputs, not the companies. The comparison would be Commodore 64, "The Commodore 64, also known as the C64, is an 8-bit home computer..." CMD (talk) 03:44, 16 October 2023 (UTC)

As previously put above by an other editor, the series is not the output, the actual individual episode of the series/season is. So the series/season is a "was" while the episode "is". Davidstewartharvey (talk) 05:18, 16 October 2023 (UTC)

I fundamentally disagree with that argument. The series is indeed a creative work. It also is plainly incorrect in terms of the reality of television series production. A TV series is a long form work. Episodes are chapters. That's why series titles are in italics, after all. oknazevad (talk) 05:27, 16 October 2023 (UTC)

Agree 100%. Episodes seem comparable to installments of a serial novel. Espresso Addict (talk) 07:57, 16 October 2023 (UTC)

It seems to me that the sort of series that would naturally be thought of as a "creative work" as a whole is a very recent development, maybe starting around the era of Babylon 5. Anyone who wants to tell me that B5 is not "recent" can go straight to Z'ha'dum. The classic TV sitcoms were not like that at all. They were much more "once a week we'll entertain you". --Trovatore (talk) 19:40, 16 October 2023 (UTC)

Without objecting too much to the premise, the idea that an (episodic) series might clearly constitute a creative work dates at least to Twin Peaks. And mini-series before that, but I understand that you are only interested in episodic television in this context. Newimpartial (talk) 19:45, 16 October 2023 (UTC)

Yes, correct. The present tense strikes me as natural for Roots. --Trovatore (talk) 19:47, 16 October 2023 (UTC)

Not familiar with much old American television but the British BBC sf series Blake's 7 (1978–81) definitely had long-running elements, especially in its later seasons. Espresso Addict (talk) 21:55, 16 October 2023 (UTC)

There was a long discussion and a long RfC about MOS:WAS in 2020; see here and here. There was no consensus to change the tense recommendation for defunct TV shows. I agree with those that argue for "was" but it was a surprisingly contentious RfC and I'm not sure I'd recommend opening that can of worms again. Mike Christie (talk - contribs - library) 21:30, 13 October 2023 (UTC)

I think it would be very confusing to have one rule for most fiction (novels, films) and another for television. Much old television is still available via DVDs or the like. Blake's 7, to take a case that someone mentioned above, is still available and still watched and discussed. I'm a native (British) English speaker, and do not find something of the form "Blake's 7 is a BBC television series that was first broadcast between 1978 and 1981" at all jarring. Espresso Addict (talk) 00:25, 15 October 2023 (UTC)

Even for some things that are not available, it would be weird to say "Marco Polo was the fourth serial of Doctor Who" but "The Edge of Destruction is the third serial of Doctor Who". That no copies are known to exist doesn't stop the serial from being at that place in the chronology, and should copies surface this won't change. —Kusma (talk) 08:22, 16 October 2023 (UTC)

As another example, at the video games project, we keep to present tense except for games that were cancelled prior to publication l. So even for defunct online games, or games that ran on defunct hardware, we still use present tense for these as there are ways to make the games work today even if it takes effort. Masem (t) 19:58, 16 October 2023 (UTC)

I don't have a problem with that for video games. I have a problem with text like Tonight Starring Jack Paar (in later seasons The Jack Paar Tonight Show) is an American talk show.... Seriously, who talks like that? You can argue all you want about the availability of episodes (I haven't checked whether they are available and don't really care) but it just doesn't come across as natural English. --Trovatore (talk) 20:28, 16 October 2023 (UTC)

There may be something to be said for the idea that a since-ended talk show, news program, or other such current-events-dependent series is more akin to a defunct periodical, which we do use past tense for, but for a scripted series the present tense is just as appropriate as it is for a film, book, play, album, etc. The series is a complete work that was produced in the past, but still exists in a viewable form. oknazevad (talk) 17:14, 24 October 2023 (UTC)

No, these old series are not complete works. They don't have narrative unity, they don't have a story arc; there's nothing that holds them together. They're just bunches of episodes. But again, that's a retrospective justification; the real point is that people use the past tense to talk about them in real life, and the present tense sounds unnatural. --Trovatore (talk) 19:53, 24 October 2023 (UTC)

IP, the original airing dates of the show-in-question, are within the page's lead. There's no way, a reader would think the TV series is being currently produced. GoodDay (talk) 19:50, 16 October 2023 (UTC)

This discussion has given me a new sympathy for "It depends on what the meaning of the word ‘is’ is.". Schazjmd (talk) 20:43, 16 October 2023 (UTC)

Wikipedia:Article Size and consensus

Originally posted at WP:VPIL because I got my noticeboards mixed up:

Recent discussions at a good article reassessment and Wikipedia talk:Article size, among others, have led me to ask whether WP:AS, and more specifically WP:SIZERULE still has community consensus to be a guideline. Objections raised include that: it includes false assumptions about Wikipedia readers; that the ideas behind it are based on out-of-date products and technologies; that it includes "rules of thumbs", etc.

I have come here to gain opinions on how to phrase a sort of "reconfirmation RfC" on the guideline as a whole. I think it would be beneficial to have clear consensus on whether the guideline should retain its status, and if so should WP:SIZERULE be a part of it. ~~ AirshipJungleman29 (talk) 15:01, 26 October 2023 (UTC)

@AirshipJungleman29, I think this is an interesting question, but I'm not sure you've put enough "handles" on it to help people get a grip on your question. So here's one:

• One of the characteristics of an encyclopedia article is its concise writing style (e.g., omit needless words) and brevity (e.g., an encyclopedia article should be shorter than a book). Should Wikipedia make any recommendations about the ideal maximum length of a Wikipedia article (NB: not lists, categories, or similar pages)?
  • If so, should Wikipedia make those recommendations based on:
    1. Word count (e.g., as measured by the Wikipedia:Prosesize gadget)
    2. Number of sentences or paragraphs
    3. How many minutes it takes to read the article
    4. Byte size (shown in page history)
    5. How long it takes to load the page (more pictures = slower)
    6. Rendered page size (more formatting = bigger/worse for people on old devices)
    7. Something else?

My answers would be Yes and 1 + 3. Bonus points if we define this in terms of the tomat (unit) (after The Old Man and the Sea. One tomat = 26,000 words). I suggest that one centitomat is a long stub, one decitomat is a nicely developed article, and one quarter tomat is getting a little long. (ScottishFinnishRadish, I'm particularly curious whether these numbers feel about right to you.)

What would you suggest? WhatamIdoing (talk) 00:01, 29 October 2023 (UTC)

It brings me no end of joy to see tomats catching on, but quick clarification, the unit name always contains the s and should be phrased so it always sounds plural. Also, according to the New York Times, it's about 27,000 words.[1] It is an excellent measure though, because it communicates the conceptual amount of reading in a way that many people are familiar with, rather than just word count.

Your scale seems pretty reasonable. If an article is running a quarter the size of a small novel it's definitely pushing out of encyclopedia article into a longer research work. ScottishFinnishRadish (talk) 00:26, 29 October 2023 (UTC)

The above comments are reasonable in general but there are plenty of exceptions where brevity would obfuscate the topic and remove important information. Some articles could be replaced with a couple of sentences that an expert in the field would understand but which would be a waste of time for anyone else. Johnuniq (talk) 00:29, 29 October 2023 (UTC)

There will always be exceptions, but in a lot of circumstances it would make more sense to fork the article and leave a summary. ScottishFinnishRadish (talk) 00:35, 29 October 2023 (UTC)

• Brevity is not a characteristic of an encyclopaedia article. The Encyclopaedia Britannica article on the United States runs to over 300 pages - easily comparable to a small book. It's hard to overemphasise how wrong-headed that preconception is. And Wikipedia is not paper. Hawkeye7 (discuss) 00:55, 29 October 2023 (UTC)
  • #3 is also based on an equally invalid and assumption; only about 5% of readers read the article from top to bottom; about a third read the lead only; and the rest jump about the article, looking for certain specific information. (See Research:Which parts of an article do readers read?) Hawkeye7 (discuss) 00:55, 29 October 2023 (UTC)

Wikipedia talk:Deletion policy#WP:RFCBEFORE discussion about proposed addition to Wikipedia:Deletion policy#Alternatives to deletion

Please see Wikipedia talk:Deletion policy#WP:RFCBEFORE discussion about proposed addition to Wikipedia:Deletion policy#Alternatives to deletion. Cunard (talk) 23:10, 29 October 2023 (UTC)

500/30 editing restrictions

In order to edit content related to the Arab-Israeli conflict, an editor must have made 500 edits and have an account that is over 30 days old. Does this restriction take into account edits made by a user to Wikipedia in other languages? The issue does not appear to be mentioned at Wikipedia:Contentious topics/Arab–Israeli conflict Burrobert (talk) 15:54, 28 October 2023 (UTC)

Only edits on the English Wikipedia count towards the total. ScottishFinnishRadish (talk) 15:55, 28 October 2023 (UTC)

Right-ho. Thanks. Burrobert (talk) 15:57, 28 October 2023 (UTC)

The page says repeatedly "extended confirmed". This is an automatic user right given to anyone with 500/30 on English Wikipedia. Animal lover |666| 09:42, 29 October 2023 (UTC)

That's actually an important point IMO. I think with the user right existing, any reference to 500/30 should generally be taken as meaning you need to have the EC user right. Mostly this is a distinction without a difference since it's automatic but the right can be revoked if it's felt the editor was WP:gaming to gain it, as just happened here Wikipedia:Administrators' noticeboard/IncidentArchive1141#EC permissions gaming. Editors who've lost the user right should be taken to not meet the requirements no matter that they may technically have 500 edits and been registered for 30 days. Of course this shouldn't be taken too far. If you know an account is a legitimate alternative account for someone with ECP EC, don't complain that the specific account doesn't have EC status. Yes they can request it at Wikipedia:Requests for permissions/Extended confirmed and in some cases it is technically necessary and can reduce confusion but it's also unhelpful to complain if you already know. (BTW in about a week it will be 30 days since the 2023 Israel–Hamas war begun so I assume we're going to get a bunch of relatively new accounts now having EC entering into the area.) Nil Einne (talk) 14:33, 29 October 2023 (UTC) 15:04, 29 October 2023 (UTC)

Yes, it's EC that's important. I don't care whether someone has over 500 edits. I do care whether they deserve the trust that we typically give by default at that 500-edit milestone but can be given early or revoked for cause. Certes (talk) 15:02, 29 October 2023 (UTC)

Arbpia is still a thing but WP:ARBECR applies to the topic area. Selfstudier (talk) 15:05, 29 October 2023 (UTC)

I understand your point but I think another issue is that rules and guidance vary from one Wikipedia to another. But I think if the editor is experienced in another Wikipedia, the 500 rule could be lowered a bit. Regards, Thinker78 (talk) 01:41, 30 October 2023 (UTC)

EC access requirements vs arbcom remedies vs when any of these are technically/administratively enforced has always been a sloppy mess. Arbcom has attempted to clean this up a few times, but as pointed above there seems to still be lingering artifacts / inconsistencies. In general any "500/30" specific rules are safe to ignore when ECP protection is actually in place; and administrators may also discretionally grant ECP to anyone they want. In practice, early ECP grants are rarely done - especially if the reason is that someone wants to dive right in to contentious topics, they are a minefield and anyone not at least moderately used to editing on the English Wikipedia is likely to run in to issues contributing to such topics. — xaosflux ^Talk 15:55, 30 October 2023 (UTC)

NB an update was processed at Wikipedia:Contentious topics/Arab–Israeli conflict - clarifying that group membership not static numbers is the gating factor for that remedy now. — xaosflux ^Talk 17:37, 30 October 2023 (UTC)

Yeah, the actual remedy in effect is at WP:ARBECR which doesn't mention 500 edits/30 days at all. Galobtter (talk) 17:46, 30 October 2023 (UTC)

Proposed change MOS:TERRORIST

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.

---

The problem

Decided to post this here instead of the NPOV noticeboard or MOS talk page as predicted this could generate quite lively discussion, as it historically has [2][3][4], but the 2023 Israel-Hamas war has again placed the spotlight on MOS:TERRORIST. The present policy rightfully encourages caution, but seemingly allows for the term's use in Wikivoice if consensus is reached in the sources. Nevertheless, the discussions on various Talk pages relating to the violence in Israel and Gaza plainly demonstrate the inherent problems of using the term in Wikivoice.

Although Terrorism scholars recognise a distinct phenomena to which the term applies, the problem for an encyclopedia is that its actual lay usage is extremely value-laden (except, of course, when referencing or quoting third party usage) and vague. Our own article on Terrorism offers such a broad definition that it escapes all utility. Scholarship is increasingly recognising the inherent definitional problems, or questioning the label's usefulness.[5]

I anticipate some of the counter arguments (based on those I've come across in the various discussions). Firstly, that terrorism is not a biased or value-laden label. I think the contentious discussions around the label disproves this point. Secondly, that it improves articles to include the term. And third that to not use the label gives such-named groups/individuals plausible deniability about the nature of their act(s). But, if the third is true, the first cannot be.

Working proposal

The Provisional Irish Republican Army article offers, in my opinion, persuasive precedent for how we should use the term. It discusses who designated it, and the fact news orgs routinely referred to the PIRA as "terrorist", all the while maintaining a neutral point of view by avoiding using the label in the narrative voice. As such, I propose a change to our MOS:TERRORIST. Of course, I welcome suggestions, but as a working start I propose the wording be amended to read:

Value-laden labels – such as calling an organization a cult, an individual a racist, sexist, or a sexual practice a perversion – may express contentious opinion and are best avoided unless widely used by reliable sources to describe the subject, in which case use in-text attribution. Avoid myth in its informal sense, and establish the scholarly context for any formal use of the term.

[...]

For the terms terrorist, terrorism, or freedom fighter: per the policy Wikipedia:Neutral point of view, these words should only be used in quotations or referencing third party use of the term.

If adopted, I realise this does mean slight edits to the wikivoice for an extensive number of articles, most notably the September 11 attacks, but these articles don't lose anything by replacing the word. In any case, the term is applied inconsistently across articles: used for the Jaffa Road bus bombings but not the 2016 Jerusalem bus bombing despite cited sources using the term. Yr Enw (talk) 19:01, 17 October 2023 (UTC)

For reference, the present material says: Value-laden labels – such as calling an organization a cult, an individual a racist, sexist, terrorist, or freedom fighter, or a sexual practice a perversion – may express contentious opinion and are best avoided unless widely used by reliable sources to describe the subject, in which case use in-text attribution. Avoid myth in its informal sense, and establish the scholarly context for any formal use of the term. It does not thereafter discuss terrorism further. So, this is a proposal to add the For the terms terrorist, terrorism, or freedom fighter: per the policy Wikipedia:Neutral point of view, these words should only be used in quotations or referencing third-party use of the term. language as a new sentence, and to remove terrorist, or freedom fighter from the opening sentence.  — SMcCandlish ☏ ¢ 😼  08:25, 18 October 2023 (UTC)

Hello, I think this is an important topic. Regarding Hamas, it is designated a terrorist organization by the European Union, the US, Canada, Australia, the UK Japan, Israel and Paraguay. In context of English Wikipedia, it is apparent that most English speaking nations have designated the organization as terrorist.

I think it is important to differentiate between militias and terrorists. This is important also for the inverse reason, so that the term militia does not come to encompass such a huge sway of organizations, thus weakening the word militia itself. Indeed I find it odd that units that served in the American Revolution are considered militia, and organizations such as Palestinian Islamic Jihad or Hamas are also considered militia.

Thus, I argue in respect to the Neutral Point of View issue, that just like Al Qaeda and ISIS can be argued to be freedom fighters or militia for some people. They are still recognized as a terrorist organization in English Wikipedia due to its intent to harm civilians as well as the scope of its actions. Thus there comes a point in which one must assume that the Neutral Point of view is that they are terrorist. Especially in light of the stance of English speaking nations towards it. To be neutral at times demands us to be objective and see the facts for what they are.

And one more thing for now, an encyclopedia such as Wikipedia can trust in rapport to the fact that it is trusted to reflect information and the values of its readership. If Wikipedia would decide to stop calling organizations such as Al Qaeda or ISIS or Hamas for this matter, terrorist; I fear Wikipedia would have lost itself in its readership.

In summary, I argue that we must designate and refer to Hamas as a terrorist organization. Homerethegreat (talk) 19:50, 27 October 2023 (UTC)

Discussion2

• Comment: Still thinking on this, but I my initial sense is that it's an oversimplification. The 9/11 attacks qualify as terrorism under every known definition of the term, but that probably is not true of every single thing that various sources apply terroris[m|t] to. I think what we need to be concerned with is whether the preponderance of the sources, the vast majority of them, agree in using the term. "I can find it in some source somewhere" doesn't equate to a WP:DUE viewpoint, but the idea above seems to encourage injection of "quotations or third-party uses of the term" without much consideration for that. As a side matter, I want to be very clear that BBC News is under rather concerted attack in [Western] public opinion for avoiding labeling Hamas's, well, terrorist actions as terrorism, and dancing along a thin and to many very inappropriate both-sidesism line. (The short version is that the fact that Israel probably has some things to answer for in regards to its treament of Palestine and residents thereof doesn't make Hamas massacring a music festival and going on a rampage of child-decaptiation any less a bunch of terrorism. Terrorism is a collection of techniques of pursuing political violence, and doing it in the name of "freedom fighting" doesn't make it magically become non-terrorism.) If WP joins BBC is beating around the bush on this, we're going to be inundated with both on-site disruption and off-site criticism in published sources. That's not a reason to do one thing versus the other, but it is something to consider and, potentially, to be prepared for. Anyway, I will agree that our lessons in how to write about the Provisional IRA are probably going to be of value in dealing with this situation in the Middle East.
  PS: There is a somewhat related RfC (of sorts) open at Wikipedia talk:Manual of Style/Words to watch#RfC Proposed Addition to "Contentious labels" section. Making much sense of it will require reading the thread immediately above it.
   — SMcCandlish ☏ ¢ 😼  08:41, 18 October 2023 (UTC)

  Thanks for the feedback. I don't disagree with the caution of the current policy, I think it needs to be tightened and certainly wouldn't advocate injection of quotations or third-party uses of the term without agreement in the sources. My thinking is that the policy needs to explicitly eliminate use of the terms in Wikivoice, but equally not to allow backchanneling a smattering sources that then falls foul of WP:DUE. This isn't, as I hope I had made clear above, to say I (or WP) think(s) there's no such thing as terrorism, just that the label is too loaded to be used neutrally and too contentious to be used consistently. Yr Enw (talk) 09:17, 18 October 2023 (UTC)

  I tend to agree with this, recently both of the UK and US governments placed pressure on the press to follow government policy such that if the government declared an org as terrorist then the press should follow and then presumably we would follow the press.

  Selfstudier (talk) 10:37, 18 October 2023 (UTC)

I think if we do that, we then compromise on impartiality. Yr Enw (talk) 10:45, 18 October 2023 (UTC)

On the contrary, to NOT follow the sources would be inserting our own partiality on the situation. Blueboar (talk) 11:21, 18 October 2023 (UTC)

I emphasise again I have no problem quoting and referencing such sources. My problem is explicitly with using the terms in Wikivoice, as is done in the Jaffa Road bus bombings article. Yr Enw (talk) 11:31, 18 October 2023 (UTC)

• Quoting the proposed addition: these words should only be used in quotations or referencing third party use of the term - That's what in-text attribution is; it is, or should be, already covered by MOS:TERRORIST. DFlhb (talk) 18:18, 18 October 2023 (UTC)

  Yeah, the application of that particular sentence is the crux of the issue really. I have no issue with the formulation of MOS:TERRORIST except that recent edit disputes have demonstrated that can seemingly be interpreted to allow use of the terms in Wikivoice as per Wikipedia:Citing_sources#In-text_attribution. Therein lies the problem from my perspective. Perhaps I should be clearer about that and the proposed wording be adjusted to specifically and explicitly address this. Yr Enw (talk) 18:37, 18 October 2023 (UTC)

  I'd point those people to WP:NPOV, which says: Biased statements of opinion can be presented only with in-text attribution. NPOV says we're supposed to attribute "John Doe is the best baseball player", so how could we not attribute "John Doe is a terrorist"? But MOS:LABEL being ignored is a problem, and, as you say, any fix should address that directly - DFlhb (talk) 19:30, 18 October 2023 (UTC)

  I guess that example goes to my point though, to say “John Doe is the best baseball player” in wikivoice would be absurd. It would likely read something like “John Doe is recognised as the best baseball player”. Likewise, “X is/was widely recognised as a terrorist organisation/attack”. Yr Enw (talk) 20:05, 18 October 2023 (UTC)

• I don't think there's any issue with the way MOS:LABEL treats the word "terrorist" specifically. If we were to make any change to it, it'd be for (slightly) liberalizing the wording. In practice, we do use MOS:LABELs in Wikivoice if the sourcing is so overwhelming the label can no longer be said to be contentious, and I think we should formalize that. Loki (talk) 19:34, 18 October 2023 (UTC)

  It seems we're both on the same page when it comes to recognising that, in practice, MOS:LABEL when read in combination with WP:INTEXT allows for use in Wikivoice, albeit we have opposite opinions on how to address that. Like I said to @DFlhb above, I think this is the crux of the issue. Yr Enw (talk) 06:50, 20 October 2023 (UTC)

  Yr Enw, we've got a handle on giving credit where it's due based on the sources we've got. But there's still a head-scratcher about those lists and categories with some pretty hot-button labels in their names. It seems like Wikipedia is slapping those labels on things without attribution in wiki voice. Infinity Knight (talk) 08:54, 20 October 2023 (UTC)

  That appears a slightly separate point to the one I was trying to make, but I agree with you the lists and categories is something that needs to be addressed by an revisal of the MOS too. Yr Enw (talk) 09:36, 20 October 2023 (UTC)

• How about we add a rule that when someone's part of a group known as a 'terrorist' organization, we make sure to mention that? It could go like, 'John Smith, a member of Brave Hearts, which countries Harmonia and Technoville call a terrorist organization.' And when we first bring up Brave Hearts on a page, we do the same thing. Just keeping things clear for the reader, no bias intended. What do you think about this idea? Infinity Knight (talk) 14:41, 19 October 2023 (UTC)

  If that reflects with due weight how the subject is discussed in reliable sources, sure, but not as a hard and fast rule. With figures like Nelson Mandela, it would give undue emphasis to primarily describe him by referencing the fact that some governments at some points in time labelled him as a terrorist.--Trystan (talk) 16:16, 19 October 2023 (UTC)

  I totally get what's going on with the whole Mandela case, but I'm kind of unsure about how to go about evaluating sources. Lately, it looks like sources are tossing around the word "terrorism" in quotes only, like it's open to interpretation. This isn't just happening on Wikipedia; even the big names like the BBC are doing it. For instance, the Prime Minister and the Royals are calling it an 'act of terror,' but it's being reported as an 'attack.' So, how do we figure out which sources are trustworthy? Doesn't it put the editors in a tricky spot, having to decide what qualifies as atrocities and what doesn't? Infinity Knight (talk) 20:35, 19 October 2023 (UTC)

  So, how do we figure out which sources are trustworthy? the usual way.

  Doesn't it put the editors in a tricky spot, having to decide what qualifies as atrocities and what doesn't? Plus ça change, consensus and all that. Selfstudier (talk) 20:39, 19 October 2023 (UTC)

  In my opinion, it appears that then OR and POV would have a significant influence.

  It's possible to envision small editorial teams forming local agreements in specific topics where unconventional viewpoints dominate. Infinity Knight (talk) 22:58, 19 October 2023 (UTC)

• Comment Totally, in the world of terrorism studies, they've been going back and forth on what the heck "terrorism" even means. It's like trying to separate real terrorism from other political violence - a real brain teaser. The whole terrorism lingo and how we think about it have been under the microscope of scholars, always changing.
  But hey, check this out, some new scholars are diving into the topic of "International Terrorism" after those wild Hamas attacks on Israel. They're not holding back on using the word "Terrorism" in their titles. They're also pointing fingers at some "international terrorist actors" and naming names. Infinity Knight (talk) 08:02, 20 October 2023 (UTC)
• I think this is bad idea. The suggested change says: ...these words should only be used in quotations or referencing third party use of the term. This contradicts the first and most important part, i.e. "...unless widely used by reliable sources to describe the subject.... It the term was widely used by multiple sources with regard to something, it should not be placed in quotations. For example, we can not write that person X was a "racist" ("...") if multiple RS have described him as a racist. Same applies to other terms. My very best wishes (talk) 23:59, 21 October 2023 (UTC)

  I see what you're saying, but as I had also said to an earlier comment: any such comment would likely read something like, “X is/was widely recognised as a terrorist organisation/attack”, and likewise "X is/was widely recognised as racist." I don't think the label loses power if framed that way. Yr Enw (talk) 14:57, 22 October 2023 (UTC)

  But is that sort of distancing really appropriate in all cases? Sometimes we should state things plainly. I think we can safely say that the founders of white supremacy organizations "are" racist, and not merely that they "were recognized as" or "called" racist. WhatamIdoing (talk) 00:22, 24 October 2023 (UTC)

  I see what you're saying, but in the case of "terrorist/m" it's so charged that I think there is no way to 'state things plainly' without getting into murky territory with regards to neutrality, assuming "terrorism/t" is a universally agreed definition, which it isn't. I don't personally think it loses impact caveating in as such, it is - after all - people who apply these words to things. Yr Enw (talk) 06:31, 24 October 2023 (UTC)

  I'm not entirely sure why there isn't a rule disallowing 'wiki voice'; all the information provided could be attributed since Wikipedia primarily rephrases its sources. Wouldn't this approach make Wikipedia more neutral and precise? Infinity Knight (talk) 06:57, 24 October 2023 (UTC)

  I completely agree. I'm unsure if I have just been obscure in my explainations, bc it seems a lot of editors are against exactly this. Yr Enw (talk) 06:59, 24 October 2023 (UTC)

  @Infinity Knight, we don't attribute every statement to a source because that would be non-neutral. Consider:

  • "According to Democratic Party, Joe Biden is the current US President" – and according to Donald Trump, he's not.
  • "According to the American Medical Association, HIV causes AIDS" – and according to Kary Mullis, it doesn't.
  • "According to algebra textbooks, algebra is a type of mathematics" – and according to some students, it's a particularly fiendish type of torture.

  We use wikivoice when a mainstream POV clearly exists (Barack Obama is US citizen, Al Capone was a gangster, Benedict Arnold was a traitor) and we are reporting that mainstream POV. To do otherwise is to imply that these are not widely agreed upon facts. WhatamIdoing (talk) 23:22, 28 October 2023 (UTC)

  Hello @WhatamIdoing: Wikipedia basically condenses and rephrases what it finds in its sources, and it can attribute the content to those sources. That'd be both impartial and precise. Some other contributors pointed out that the need to censor what sources actually state can introduce bias into Wikipedia. The word 'terrorist' can function as both a label and, at times, as a factual description. The guideline seems to overlook the latter. Now, how can we attribute the term 'terrorist' in the Hindustan Times content within the existing framework without introducing bias? Infinity Knight (talk) 03:40, 29 October 2023 (UTC)

  Is that source the only one that uses that label? If not, why do you want to attribute the label on this source alone? WhatamIdoing (talk) 04:33, 29 October 2023 (UTC)

  "Label"? Could it be a factual description? What's the right way to use the word "terrorist" when rewording the Hindustan Times source? Any ideas from other sources? Infinity Knight (talk) 05:41, 29 October 2023 (UTC)

  @Infinity Knight, the HT piece that you linked is WP:PRIMARYNEWS. Why would you be using that source at all? I don't think we need to worry about "rewording" that source because I think we should be citing secondary sources. WhatamIdoing (talk) 19:50, 29 October 2023 (UTC)

  "[It is not] always easy to distinguish primary from secondary sources. A newspaper article is a primary source if it reports events, but a secondary source if it analyses and comments on those events".

  HT goes through Israeli sources, and it's pretty obvious that the audio of the call is connected to the IDF. So, I have some reservations about labeling this source as primary. Infinity Knight (talk) 07:03, 30 October 2023 (UTC)

  @WhatamIdoing I agree with this point (that attributing some statements can lead to neutrality issues), except that I don’t think it should apply to any use of the terms “terrorism/t” because they are specifically called out for challenge in many academic sources. So the notion it’s “calling a spade a spade” just isn’t correct Yr Enw (talk) 07:46, 29 October 2023 (UTC)

  When most of the sources are using the term terrorist, and there is no significant disagreement, then we should feel free to use that term, too.

  The challenge in academic sources is about defining the edges. There is no significant disagreement about the core. Consider the debates in astronomy about what constitutes a planet: There have been debates about whether Pluto is a planet, but there is no disagreement about whether Earth is a planet. We don't say "Oh, there is disagreement about the cutoff point – okay, we give up; nothing can be called a planet in wikivoice!" The same logic applies here: There have been debates about whether certain groups are true terrorist organizations, vs (e.g.,) criminal gangs or political groups with unorthodox publicity methods. The fact that some are dispute doesn't, and shouldn't, stop us from labeling the undisputed other individual groups as terrorists. WhatamIdoing (talk) 16:23, 29 October 2023 (UTC)

  The academic debate isn’t simply about the “edge”. That might be a legal struggle by governments, but discussions in academia im talking about are about the very notion of “terrorism” as a term full stop. To use the planet example, academics aren’t talking simply asking “does x and y constitute a planet”, but rather to the core of “what even is a planet?” And “does the concept of planets in and of themselves help us understand?” And of course many are now saying “no” - See Stampinzky [6] for example.

  nb - ofc im not actually talking about planets, nobody doubt the utility of that term, just transplanting the example Yr Enw (talk) 17:37, 29 October 2023 (UTC)

  Funny coincidence that you'd link to Stampinzky. The rest of the book is also an excellent read. DFlhb (talk) 19:23, 29 October 2023 (UTC)

  I've read Stampnitzky. She doesn't argue against using the term. Instead, she argues that the people trying to come up with a single, universal, apolitical, amoral definition don't understand what the term means. She argues that this word means that the speaker has identified an "enemy" (someone who's the "them" in the us-versus-them thinking) who is using overt violence for political purposes in illegitimate or out-of-place contexts (e.g., shooting random people in a nice part of town is "out of place"; shooting people in a combat zone is expected).

  For example:

  • Drug cartel murdering someone who stole from them: "Enemy", but not "unexpected" or "political", therefore not terrorists.
  • 9/11 hijackers: "Enemy", "out-of-place violence", and "political", therefore terrorists.

  Her main point is to say that if you call someone a terrorist, you are saying that the action is overtly violent, that it is perpetrated in an atypical or abnormal context, and that it is primarily public and political in nature. This is not an argument against using the term. WhatamIdoing (talk) 20:27, 29 October 2023 (UTC)

  My apologies. The structure of my message was unintentionally misleading. Stampinzky is an example of scholars asking the question as to whether it’s possible to define it. For scholars more explicitly saying no, perhaps see [7]. I’m not sure what she offers can really be said to be a definition, although yes I suppose it’s “this is how people seem to define it”, which is a definition of a definition, albeit it’s so extremely broad that, even if we agree she accepts that definition, isn’t the very notion of “(il)legitimate” highly subjective that it escapes all utility? Yr Enw (talk) 07:24, 30 October 2023 (UTC)

  My argument being: analysis like hers underscores, to me, the need for extra caution with slapping unattributed labels around Yr Enw (talk) 07:26, 30 October 2023 (UTC)

  There is an elephant in the room. On a linguistic level, I'm not sure how the UK Prime Minister and the Royals can freely use the term "terrorism" when it lacks a clear definition. How can they expect the British people to fully understand what they're saying?

  When we look at current scholarly research, experts and international law scholars provide detailed explanations. The labeling of celebrities by world governments is a subject of extensive discussion, but scholars, when analyzing the available sources, tend to use the term in a factual, unattributed manner. They talk about what they define as "the world of international terrorism" and the interaction of major terrorist groups in that realm. So, it doesn't appear that there's a consensus among scholars that the term is so poorly defined that we should eliminate it from our vocabulary.

  This perspective should be taken into account in the guidelines. In some cases, the term could be used as a "LABEL," as seen with Mandela, while in other cases, it could be employed for factual description, as is the case with Bin Laden, for instance. Infinity Knight (talk) 07:38, 30 October 2023 (UTC)

  “(il)legitimate” highly subjective that it escapes all utility might be WP:FRINGE. Just a quick look at scholarly sources shows that the term is used without attribution in factual contexts, for instance in research about social interactions within certain celebrity groups, see "Identity, International Terrorism and Negotiating Peace: Hamas and Ethics-Based Considerations from Critical Restorative Justice" as a random instance. This isn't just a theoretical matter, see QFT; it's a practical one. Real governments invest significant resources in legislation and funding for counter-terrorism activities. For everyday people, this term has utility, and leaders use the term to communicate with their audiences. Regarding the guidelines, stating that the term is exclusively a label can be misleading and should be clarified. I share the concern about the potential for bias due to label misuse, and we already provide a warning about this. However, it has been argued that the current approach can also introduce bias in some cases. So, we need to strike a balanced approach. Any suggestions? Infinity Knight (talk) 14:51, 30 October 2023 (UTC)

  I’m not entirely sure there is a way to strike balance between the two perspectives. We either don’t use it (as I suggest) or we do (and potentially invite this debate each and every time). But perhaps someone else has an idea Yr Enw (talk) 15:26, 30 October 2023 (UTC)

References

Restating the problem & formal RfC

The above discussion appears to me to have ironed out the crux of the issue:

1. MOS:TERRORIST restricts the terms to "in-text attribution"
2. According to WP:INTEXT, "in-text attribution" includes use in Wikivoice can be used when there’s consensus in RSs.
3. For me, the problem is solely about using the terms in Wikivoice (ie. not quotations or referencing third party use).
4. Because the definition of these terms are highly contested, RSs cannot be said to use or define the terms consistently.
5. Therefore, I believe use of the terms "terrorist/terrorism/terror attack" in Wikivoice should be explicitly eliminated.

As such, perhaps a useful way of proceeding is to open a formal RfC below, to gauge whether there is appetite for any such change at all. Please note, this poll is not about any particular policy wording. It is solely about whether there should be any change to MOS:TERRORIST.

This poll has now closed.

 Not done There is clearly no consensus for change. I remain of the views expressed, most specifically that this will continue to lead to Talk page punch-ups until a clear interpretation of the guidelines is reached/adopted/enforced. Am keeping the discussion open, however, in case of further constructive comments. Yr Enw (talk) 10:06, 29 October 2023 (UTC)

MOS:TERRORIST is a link to a section that covers many things... Not just terrorism. Is there a reason for using this particular link and not the actual name or the more general links? Horse Eye's Back (talk) 19:22, 22 October 2023 (UTC)

Yes I appreciate that, I was only using it as a shorthand because my focus is on “terrorism”, as opposed to the other contentious labels Yr Enw (talk) 19:41, 22 October 2023 (UTC)

And, for what it’s worth, even if we were to eliminate wikivoice use of any of those terms (I say, once again, I’m not talking about referring to third party use of the term) I don’t feel it loses impact. Saying, “X is widely regarded as racist” for example. Yr Enw (talk) 19:48, 22 October 2023 (UTC)

Hello there, I think it would be a grave mistake to restrict the use of the term terrorist/terror attack/terrorism. Several points

Point 1) In respect to the Neutral Point of View issue, that just like Al Qaeda and ISIS can be argued to be freedom fighters or militia for some people. They are still recognized as a terrorist organization in English Wikipedia due to its intent to harm civilians as well as the scope of its actions. Thus there comes a point in which one must assume that the Neutral Point of view is that they are terrorist. Especially in light of the stance of English speaking nations towards it. To be neutral at times demands us to be objective and see the facts for what they are.

Point 2) An encyclopedia such as Wikipedia must be able to decide on such issues according to a set of parameters. For example, if the US, UK, Australia and Canada accept an organization as terrorist then it ought to be considered as such since they make up more than 75% of the Native English speaking world. (The rule should be if countries representing more than 75% of native English speakers consider an organization terrorist than it should be done so)

Point 3) What you are proposing would make the 9/11 attack not a terrorist attack but an "attack by militia"; it would make the Charlie Hebdo attacks, militia attacks; everything will be militia attacks! This would really be simply absurd.

Point 4) Potential for disastrous effect. Wikipedia has power, all who control information have power. By removing the terrorist label, we run into the dangerous ground of potential legitimization of groups. Wikipedia is read by millions, we have a responsibility to ensure that some organizations are labeled as terrorists and are not legitimized in some manner by us.

Homerethegreat (talk) 20:02, 27 October 2023 (UTC)

Hi there, thanks for your comments and for adding to the discussion. To just tackle the points you raise:

1. "They are still recognized as a terrorist organization in English Wikipedia due to its intent to harm civilians as well as the scope of its actions. Thus there comes a point in which one must assume that the Neutral Point of view is that they are terrorist. Especially in light of the stance of English speaking nations towards it. To be neutral at times demands us to be objective and see the facts for what they are." The problem is that this seem to fly in the face of WP:NOOBJECTIVITY. The NPOV policy "says nothing about objectivity." The point being, we are not - as WP editors - the arbiters of what does or doesn't constitute terrorism. We report what reliable sources say, aiming to reflect the general consensus in media and scholarship as best as possible. So, to me, that means attributing use of the term (ie. "X says Y is terrorism") but generally not interpreting acts as terrorism in the narrative (Wikivoice). This isn't to say we don't think it's terrorism.
2. "An encyclopedia such as Wikipedia must be able to decide on such issues according to a set of parameters." Agree, but the parameters of verifiability are not simply "what governments say". They are far from neutral actors when it comes to applying this specific set of terms, as well.
3. Disagree. I have said elsewhere, and evidently need to say again, the issue is only when in text attribution is avoided in favour of Wikivoice.
4. See above numbered point. I'm not advocating removing it.

Further to the point about objectivity, while this really gets into the domain of the Problem of universals, it should nevertheless be pointed out that even eminent terrorist scholar Bruce Hoffman, who spent an entire book trying to pin down a definition of terrorism, still had to acknowledge at the start of the book that - in reality - the term is never used neutrally and becomes inevitably subjective.[8]

If the issue is one of losing impact by not using the term (or that "terrorism" should be used bc it's a strong label), I just disagree. I don't believe there's any such loss by simply sticking some citations at the end of a sentence. But that's just me. Yr Enw (talk) 07:15, 28 October 2023 (UTC)

Survey (MOS contentious labels)

I'm not convinced that there is actually a problem that needs solving here. When the majority of reliable sources say X is/was a terrorist (organisation) it would be an NPOV violation not to include that description in our article. If the sources are using it with inconsistent meaning we should say that - iff we can do so without engaging in original research. Thryduulf (talk) 15:03, 22 October 2023 (UTC)

We probably wouldn't be able to do that without engaging in OR. But, like I said above, the problem I find arises solely with use in Wikivoice, not with the mentioning of it. I am not saying we shouldn't include that description in our article, just that we need to be cautious how frame that description (and, in my opinion, not use Wikivoice). Yr Enw (talk) 15:07, 22 October 2023 (UTC)

The BBC approach :) Selfstudier (talk) 15:10, 22 October 2023 (UTC)

The BBC and other entities who are unwilling to call terrorism terrorism are taking intense criticism and in some cases seeing loss of contributions, or so I've read. The optics of this proposal may not be ideal. Wehwalt (talk) 17:41, 22 October 2023 (UTC)

Yeah I can appreciate if that turns out to be the case. The irony is that whole thing really underscores how un-neutral a term it is! Yr Enw (talk) 17:43, 22 October 2023 (UTC)

Or maybe it represents how little tolerance most people have for a media outlet trying to protect the feelings of people who are willing to kill children for political reasons by making sure that they don't use the "T-word" to describe the murderers. Reminds me of https://www.gocomics.com/doonesbury/1982/08/26 in reverse. WhatamIdoing (talk) 00:28, 24 October 2023 (UTC)

Your comment underscores exactly how value-laden the term is, though, because you assume that by not using it you're 'protecting the feelings of people who are willing to kill children for political reasons'. That exemplifies the biases that have been imbued within it. That act is so clearly wrong and immoral without needing to get bogged down in labels. And hey, I am not even saying don't use it, I'm saying don't use it in wikivoice. Yr Enw (talk) 06:39, 24 October 2023 (UTC)

If "the act is so clearly wrong and immoral" – if, in short, there is no significant doubt about it being an accurate description, and when this is a typical categorization made by reliable sources – then we should call a spade a spade, and a terrorist a terrorist.

Here's how this conversation appears to me:

• You: We shouldn't call people names, even when they murder children for political purposes.
• Other editors: Um, you know that the general public, which includes our readers, is strongly criticizing the few other websites who've taken that self-censorship approach?
• You: Yeah, our readers hate it when we accurately describe terrorists as being terrorists. We just shouldn't call people names, even when it's totally obvious that they really are terrorists.

I understand that you dislike name calling, but I find your argument non-existent and your assertion unconvincing. WhatamIdoing (talk) 23:06, 28 October 2023 (UTC)

That is a total mischaracterisation of the arguments I have advanced. I have said from the start that there is substantial scholarly literature attesting to the problems inherent in this specific term. That is the motivation behind seeking a more restrictive policy in its usage. If my actual arguments simply go unaddressed, I don’t think we are going to get any further here. Yr Enw (talk) 07:42, 29 October 2023 (UTC)

Notice how we're not calling it a terrorist attack in wikivoice, because the sourcing doesn't support it? By definition, it's not totally obvious. Nor do we call Hamas, Al-Qaeda, or the Taliban "terrorists" in wikivoice. May I remind you that WP:BLP applies to groups, even those we don't like, and also applies in this namespace? DFlhb (talk) 09:25, 29 October 2023 (UTC)

Unfortunately, it seems many editors equate "not using in Wikivoice" to "saying/believing it doesn't exist". But the latter isn't relevant to the question of style, it belongs in the domain of the Problem of universals. Yr Enw (talk) 09:34, 29 October 2023 (UTC)

The issue is that Wikipedia editors are instructed to replace the word "terrorist" with "militant" which has slightly different meaning, thus introducing bias. In the Wikipedia world, we usually roll with the idea that a word's just a "label," but hey, that's not always the case. No one even talks about it when we're using the term to describe actual facts, and we don't even think about that possibility. The way we talk totally shapes how we see things, you know? Infinity Knight (talk) 10:14, 29 October 2023 (UTC)

Instructed? Sources use militant all the time, as well as fighter, gunman, etc depending. Here's an AP report of today, here the killer is a "settler" and we have "Hamas militants infiltrated Israel on Oct 7". Nothing there about Hamas attack being by "terrorists" or the October 7 events being "terrorism". Bias? Same goes for 7000+ dead, mostly civilians, half women and children, in Gaza, that's not "terrorism" either, it's "self defense". Selfstudier (talk) 10:31, 29 October 2023 (UTC)

See Yr Enw suggestion above: "militant" is a much less problematic term (eg. "A Hamas militant boasted to his mother of 'quote whatever he says', widely denounced as a terrorist (citation x, y, z)") I'm cool with going along with the sources and using the term they're throwing out, like "militant" if that's their lingo, or "terrorist" if that's what they're saying. Infinity Knight (talk) 10:51, 29 October 2023 (UTC)

That's my position as well, the trouble starts when MOS TERRORISM is cited as a reason not to, then it requires in depth source analysis every time to see what's what. Selfstudier (talk) 11:20, 29 October 2023 (UTC)

The term 'terrorism' is the elephant in the room: an obvious, significant, and often uncomfortable issue or topic that people are aware of but choose to ignore or avoid discussing. Infinity Knight (talk) 11:36, 29 October 2023 (UTC)

The AP Stylebook approach, too, for the record. DFlhb (talk) 20:26, 22 October 2023 (UTC)

And the Agence France-Presse approach too. I've noticed Le Monde has largely adopted this too, though silently. It's rather remarkable that we would be less cautious than our news sources, to say nothing of academic sources. We're supposed to be more formal and clinical than them; it would be an anomaly for the roles to be reversed.

• News is highly selective in which acts of political violence are presented as terrorism, according to this paper.
• These words have always been tricky; the subject of controversy. “One person’s terrorist is another person’s freedom fighter.” “Today’s terrorist is tomorrow’s statesperson.” These recurring phrases have become clichés in journalistic and political commentaries. They mean that using these terms is never neutral. (emphasis mine) from the UNESCO handbook for journalists
• Ariel Merari, professor at the International Institute for Counter-Terrorism, Tel Aviv University, from the above handbook: “Terrorism has become merely another derogatory word, rather than a descriptor of a specific type of activity. Usually, people use the term as a disapproving label for a whole variety of phenomena which they do not like, without bothering to define precisely what constitutes terroristic behavior.”

There is far, far more from that handbook, and from other papers, all the way from Becker's original labelling theory paper, up to today. DFlhb (talk) 09:10, 29 October 2023 (UTC)

The section is about contentious labels in general, not just the label terrorist. Is the objection to the entire idea of contentious labels or just this specific label? Horse Eye's Back (talk) 17:48, 22 October 2023 (UTC)

I believe this specific label requires singling out for particular treatment. Yr Enw (talk) 18:17, 22 October 2023 (UTC)

Then this isn't a discussion about MOS:TERRORIST is it? You've just used that link to make a point. Horse Eye's Back (talk) 19:23, 22 October 2023 (UTC)

I’m not sure I understand your comment? The MOS has a specific caveat about pseudoscience, for example, that’s what I envisioned when I said singling out, given how contested the term is (more so than “racism”, for eg) Yr Enw (talk) 19:38, 22 October 2023 (UTC)

So you're challenging the inclusion of terrorist but not freedom fighter, denialist, etc? Horse Eye's Back (talk) 20:05, 22 October 2023 (UTC)

I would support eliminating wikivoice for them all, but I’m singling terrorism out for specific mention because, as I have said in the “discussion” (and the “problem”) section, there is a specific recognition in the scholarship about how loaded and contentiously defined the term is. Yr Enw (talk) 20:17, 22 October 2023 (UTC)

• Oppose- I'm with Thryduulf here. When the overwhelming majority of RS say X, we can and should say X. --GRuban (talk) 18:49, 22 October 2023 (UTC)
• Oppose per GRuban and Thryduulf. If and only if the majority of sources say X, we must as well. Andre🚐 19:18, 22 October 2023 (UTC)
• Oppose per the above. Also feel that it's not the time to have such a discussion, even were it warranted.--Wehwalt (talk) 19:59, 22 October 2023 (UTC)
• Contrary to the OP, nothing in the manual of style is policy, thank goodness. Our articles have to mean what the sources mean, but we don't have to use the words the sources use. Whether to use the word "terrorism" is in fact a matter for editorial judgment, although our judgments should be based on what the most reliable sources say.—S Marshall T/C 08:14, 25 October 2023 (UTC)

  Thanks for the comment, that's quite informative and makes sense. This really does seem to come down to editorial subjectivity, which - in my opinion - is a neutrality problem when it comes to this set of terms because we are making a judgement as to what we think the sources mean. Yr Enw (talk) 08:16, 25 October 2023 (UTC)

  We have to know what the sources mean. Someone who doesn't know what the sources mean shouldn't be editing the article, under any circumstances, ever.—S Marshall T/C 14:45, 25 October 2023 (UTC)

  When making a statement like "X was a terrorist attack" without directly attributing the use of the term (which is the only thing I have an issue with here), are we not inevitably making an editorial judgement? Maybe I'm misunderstanding what you're saying. Yr Enw (talk) 14:55, 25 October 2023 (UTC)

  Yea, it is an editorial judgement, that's the point, I think. Selfstudier (talk) 14:57, 25 October 2023 (UTC)

  Doesn't this inevitably lead us to a potential punch-up between pro and anti "using the term" every time "terrorist" is put in any article? Yr Enw (talk) 15:02, 25 October 2023 (UTC)

  Ahem, civilized discussion, yep:) Selfstudier (talk) 15:08, 25 October 2023 (UTC)

  That's what underpins my desire for an explicit position, but I can understand why we may not get one. It's just frustrating to see this has seemingly been a point of disagreement for 20+ years on Wiki. Yr Enw (talk) 15:10, 25 October 2023 (UTC)

  There are loads of iffy labels, and that "terrorist" is contained in a short list named specifically, it's not doing us any favors in my book. It just gets folks all riled up 'cause of their different takes on things. So, I'm on board with setting some clear rules, or else this chaos just keeps rolling on. Infinity Knight (talk) 18:29, 25 October 2023 (UTC)

• There is no consensus in reliable sources about what the definition of terrorism is. Therefore, I see it as something that is almost never acceptable to use in wiki voice. I also don't think it conveys any information to the reader besides just describing in plain English what a "terrorist" attack consisted of or what a "terrorist" organization is up to, which we should already have in the article. (t · c) buidhe 03:33, 26 October 2023 (UTC)

  As the BBC reporter expressed it, while dealing with a comparable issue of "word choice," there are moments when certain freedom fighters engage in deeply troubling actions that indeed merit the label "an act of terror". Infinity Knight (talk) 04:42, 26 October 2023 (UTC)

  The problem still arises as to what measure determines when an action crosses into "an act of terror", on which there is seemingly little (if any) agreement. Yr Enw (talk) 05:14, 26 October 2023 (UTC)

  In most cases, it's important to focus on what really went down, rather than the political statements that were made. There are scholars and international law experts that break it down for us.Infinity Knight (talk) 05:21, 26 October 2023 (UTC)

  I agree. Contentious labels only bog us down Yr Enw (talk) 16:19, 26 October 2023 (UTC)

  "Contentious labels" is a guideline. I mean, the whole deal about giving credit when sources don't see eye to eye is already baked into those core policies about being neutral, reliable, and verifiable. In a sense, this guideline simply serves as an explanation of how to implement those fundamental policies. I think "Contentious labels" works fine and plays a key role, explains why not to use a pejorative term used by opponents to portray something or someone negatively. But tossing in political terms as examples in "Contentious labels" just gets editors all riled up about politics instead of making Wikipedia better. Infinity Knight (talk) 17:52, 26 October 2023 (UTC)

  Supporting @Infinity Knight.

  Generally speaking, I suspect it will continue to be the source of lively discussions (or civilised discussions as per @Selfstudier) as it was in the past ~two decades unless there will be a practical resolution agreed by the community.

  As I see it there is an internal conflict in MOS:LABEL concerning the classification of organisations/individuals. It starts with Value-laden labels – such as calling an organisation a cult, an individual a racist, sexist, terrorist, or freedom fighter, or a sexual practice a perversion – may express contentious opinion and are best avoided unless widely used by reliable sources to describe the subject, in which case use in-text attribution. I argue that it might be misleading to include terms like "racist" and "sexist" alongside "terrorist" because these terms differ in terms of formal categorisation. For instance, there are well-established lists - albeit with some variations - for defining terrorist organisations/individuals in different countries or unions, such as the UK, US, Australia, and the EU, just to name a few focusing on those that are especially relevant to the English speaking world. These lists have clear and practical criteria, like "initiation of investigations or prosecution for a terrorist act or an attempt to carry out or facilitate such an act."[9] However, there are no equivalent lists for categorising individuals or organisations as racist or sexist of course. Moreover, in the Value-laden labels reference in MOS:TERRORIST the example of 'terrorist' is taken from a source dated to 1944 - quite historic for our current discussion I'd say.

  Wikipedia serves as a platform for people to access common knowledge in a digestible format. Therefore, it's essential not to shy away from defining certain groups or individuals as they are according to major official listings, i.e terror organisations. Sunshine SRA (talk) 21:54, 27 October 2023 (UTC)

  Just a couple of (gentle) counterpoints to some of the points you raise at the end:

  • I don't know what 1944 source you're referring to, I don't appear to be able to see that. But, even if that's the case, there are plenty of contemporary sources attesting to the problems baked into the label.[10][11][12]
  • On your last point, "Wikipedia serves as a platform for people to access common knowledge in a digestible format. Therefore, it's essential not to shy away from defining certain groups or individuals as they are according to major official listings, i.e terror organisations". On the first part, I agree. WP is a platform for common knowledge in a digestible format. On the second, if we think avoiding or attributing the term is "shying away" then doesn't that betray an inevitable bias attached to the term?

  I can't seem to find a better way to articulate the points I've been raising in this discussion, except to say that the problem arises, to me, solely with regard to unattributed use of the label.

  Yr Enw (talk) 06:51, 28 October 2023 (UTC)

Support use of term Terrorist - There are actions that must be referred to what they are. 9/11 is a terrorist attack. If you give "both sides" an equal voice then it would be in essence legitimizing the action since it would be referring to Al Qaeda potentially as Freedom Fighters considered terrorist etc.

Sometimes there is no choice but to use the strong term - terrorist. According to international experts, world leaders and ordinary people the Hamas attack on Israel on the 7th of October targeted civilians, over 1000 civilians were killed, 229 civilians were kidnapped. Of the 1000 civilians killed, many were mutilated, burned, raped... It's the truth, can we really deny that it was a terrorist attack?

This debate may determine the course of Wikipedia. Please think through this. Homerethegreat (talk) 20:11, 27 October 2023 (UTC)

To be honest, I doubt there will be a resolution. And certainly unlikely in favour of my arguments. It's a very old debate that crops up every so often (see the links attached to my OP). I don't know how else to express the points I've been trying to make, but it seems they are still being misunderstood and misinterpreted. I'm not, for example, saying we can/should deny the 7th Oct attacks were terrorist. Yr Enw (talk) 07:22, 28 October 2023 (UTC)

I'm not convinced that these big RfCs with tons of folks jumping in are really doing much good for Wikipedia or its content quality, you know? There are better ways to put all that energy to work for the common greater good. The guideline's current wording doesn't acknowledge that "terrorism" isn't always meant to slam something or someone. Just look at who we should credit for using the term "terrorist" in that Hindustan Times piece, for instance? Infinity Knight (talk) 07:49, 28 October 2023 (UTC)

You might be right. The motivation behind sticking an RfC here was bc of the obviously wide ranging implications of any such changes for thousands of articles. But perhaps it’s better served by individual talk page discussions, after all Yr Enw (talk) 07:52, 28 October 2023 (UTC)

Sure, I get what you're saying. I wasn't aware of that before, the individual reported as the current Hamas military leader, as reported by FT, is the same person responsible for the 1996 incident described as "terrorism" in Wikipedia's voice, you previously referred to. When rephrasing, how should we attribute the term "terrorist" for the individual mentioned in the Hindustan Times article? Infinity Knight (talk) 10:05, 28 October 2023 (UTC)

Depends in what context we're saying it, I think. If we're describing him within a narrative of the incident itself, "militant" is a much less problematic term (eg. "A Hamas militant boasted to his mother of 'quote whatever he says', widely denounced as a terrorist (citation x, y, z)"). But then we could say X, Y, and Z denounced him as a terrorist (if it fits the article) and the actual incident can be attributed as terrorism according to X, Y, Z. Yr Enw (talk) 13:17, 28 October 2023 (UTC)

Widely described by whom? Infinity Knight (talk) 13:23, 28 October 2023 (UTC)

Whatever citations follow it in the sentence? Yr Enw (talk) 13:27, 28 October 2023 (UTC)

My bad, it's not quite clear what you're getting at here. Are you thinking of using "described by Hindustan Times"? Or maybe "Kyiv Post" or something else? We've already heard from a bunch of angles why this could introduce some bias, even though I get that the intention is to keep things fair and square. The concern is valid, sometimes people use "terrorism" to diss something or someone and make them look bad. But there are situations when it's just straight-up facts. Infinity Knight (talk) 13:39, 28 October 2023 (UTC)

Oh, my apologies. Yes, I would either say: "described by (whoever)" or just more passively say "described as" with citations at the end. Because it's implied "described as" means by the sources cited at the end of this sentence Yr Enw (talk) 13:48, 28 October 2023 (UTC)

Someone pointed out that such wording might come off as biased, even though the original intentions are well-meaning, and thus it could harm Wikipedia's credibility. Infinity Knight (talk) 14:07, 28 October 2023 (UTC)

If that's true, though, there is no way to avoid bias I don't think Yr Enw (talk) 14:21, 28 October 2023 (UTC)

Agreeing to ditch wiki voice altogether was one idea we could get behind. But I'm not convinced there's nothing we can do about it. Infinity Knight (talk) 14:27, 28 October 2023 (UTC)

That is the position but it is not set up as a policy, so can be overridden case by case. In other words, the usual WP thing of getouts, letouts and constructive ambiguity. Selfstudier (talk) 14:38, 28 October 2023 (UTC)

There also appears to be no consensus to establish "ditching Wikivoice" as a policy, either Yr Enw (talk) 14:44, 28 October 2023 (UTC)

I doubt it would be possible to ditch it completely but a tightening up might be doable. Selfstudier (talk) 15:08, 28 October 2023 (UTC)

Do you think it would be a better discussion on Wikipedia talk:Manual of Style/Words to watch? Is it a matter for the ArbCom?? I genuinely have no idea how we'd achieve it. But, like we discussed above, it seems this is going to be a persistent issue until there is something done. Yr Enw (talk) 15:12, 28 October 2023 (UTC)

Could start at MOS and see if could get some agreement. It's content question, I guess, it doesn't seem to be a V question, nor OR, leaves NPOV. When is it/Is it neutral to use the word "terrorist/terrorism/terror" in Wikivoice? Could be a question worth asking at the NPOV noticeboard, idk. Tricky. Selfstudier (talk) 15:24, 28 October 2023 (UTC)

@Yr Enw: Thanks for digging into this topic. I don't really have a strong take on what the next steps should be, but I'm on board with the idea that this is a recurring problem, and it's in everyone's best interest to figure it out. Infinity Knight (talk) 15:49, 28 October 2023 (UTC)

@Selfstudier @Infinity Knight Thanks both. This survey closes tomorrow anyway, with the very likely outcome of no consensus, so something to mull over after that. Yr Enw (talk) 15:57, 28 October 2023 (UTC)

Take care, and give me a heads up if you're doing some serious thinking. Infinity Knight (talk) 16:27, 28 October 2023 (UTC)

Sure thing. I think after the numerous attempts at explaining what I was trying to say here, collaborative drafting of any RfC/noticeboard comment/etc would be beneficial. Yr Enw (talk) 16:40, 28 October 2023 (UTC)

Also good would be RS using the phrase "widely described" or similar. Selfstudier (talk) 14:13, 28 October 2023 (UTC)

If it followed the Loughinisland massacre, for instance, it would be "member of Hamas". Yr Enw (talk) 13:30, 28 October 2023 (UTC)

• "Terrorism" is a word that has potential legal meaning - many police forces are given more powers to investigate when an event is considered terrorism. As such, we should not be using the term in the short-term in Wikivoice (w/o attribution) just because a majority of press sources use it. If it is declared terrorism by the appropriate authorities, that's fine. In the long-term well after the event has occurred, then the metric of using significant uses in normal reliable sources as to use it without attribution is then fine. --Masem (t) 13:24, 28 October 2023 (UTC)

  I'm not a lawyer, but according to WP:COMMONNAME, we want our content to be easy to understand for regular folks. "Terrorism" is a common English word, and we all know what it means. In general, Masem, your argument seems to keep ignoring the fact that terrorism does exist, and it's not always about people using "terrorism" to trash something or someone. There are cases where it's just stating the plain facts. And so far, I haven't come across any guidance on how to handle such situations. Infinity Knight (talk) 13:56, 28 October 2023 (UTC)

  The problem is, I don't agree that "we all know what it means" because it is not applied consistently and academic scholarship (which form part of our RSs) don't agree on any single definition. By very nature of being a contentious, value-laden term (as MOS:LABEL calls it), it doesn't have a definition that we all know and agree upon. Wikipedia isn't about determining whether or not "terrorism exists" but about reporting what people say (with citations, of course0. Yr Enw (talk) 14:00, 28 October 2023 (UTC)

  It's a legit legal puzzle. Hindustan Times appears to understand the word meaning, and so do the UK Prime Minister and the Royals. The list goes on. The deal is, "Terrorism" can sometimes be just a label, but it ain't always the case. The guideline ought to make that super clear. Infinity Knight (talk) 14:13, 28 October 2023 (UTC)

  The BBC is occasionally able to capture the meaning of the term "terrorism" when reporting on the bombing at the Ariana Grande concert in Manchester, for instance. Infinity Knight (talk) 04:09, 29 October 2023 (UTC)

• Oppose this proposal. If the preponderance of independent reliable sources use a term like "terrorist", then WP needs to use it also, or we're simply engaging in a PoV and OR dance to avoid going along with sources, for reasons particular to individual editors' sensibilities, and that's just not what this project is for. If there is some kind of discrepancy between definitions of "terrorism" as used by these sources (and they result in any sort of meaningful categorization difference with regard to the case at hand) then that can be explored in the article body. But this seems unlikely anyway. If pretty much all the sources are agreeing to use the term "terrorism" then whether they intend a meaning nuance that differs from someone else's exact definition really isn't material. It would only be relevant when a bunch of sources use "terrorism" and bunch do not and call it "freedom fighting" or something else. If an editor here is convinced that somehow the term "terrorism" shouldn't apply to a particular case, against the consensus of the reporting of the whole world, then they can go somewhere else and write a blog post about it. This isn't ContraryOpinionPedia or BothSidesismPedia or NeverUseATermThatSomeoneSomewhereMightNotLikePedia.  — SMcCandlish ☏ ¢ 😼  09:46, 29 October 2023 (UTC)

  I see your point, though how do we practice this in light of MOS:TERRORIST ? In-text citations all the time? If that's the case, there's no problem in my mind. Yr Enw (talk) 10:08, 29 October 2023 (UTC)

  So, there were like, tons of debates on climate change and the whole scientific consensus thing. "going against the worldwide reporting consensus," how do we figure that out? With that, I wouldn't be against adding something like that to the guidelines, just thinking out loud here. Infinity Knight (talk) 10:29, 29 October 2023 (UTC)

  going against the scientific consensus is a factual claim (and a correct one, which we should include per WP:PROFRINGE); not a label. That's what WP:INTEXT tells us to use in wikivoice, and we indeed should say it in wikivoice. DFlhb (talk) 11:44, 29 October 2023 (UTC)

  Thanks for simplifying it. How can we implement WP:PROFRINGE, WP:INTEXT, and MOS:TERRORIST when we're rephrasing Hindustan Times? Can you provide a neutral rewording that avoids introducing any bias? This is purely a thought exercise. Infinity Knight (talk) 12:03, 29 October 2023 (UTC)

  The same outlet uses the term "militant" elsewhere, while CBS News calls him a "Hamas fighter", and only uses the word "Terror" in its headline. Substituting "terrorist" for "fighter" or "militant" is one option, since the "terrorist" label isn't universal in sources. I think sources that discussed the labelling issue agree that "militant"/"fighter" are unbiased replacements for "terrorist". The Times of Israel presents it as: Foreign Minister Eli Cohen plays a recording of what he says is a Hamas terrorist bragging to his parents that he “is proud that he has the blood of 10 [Jews] that he murdered.” That would be another option, "BBC-style"; conveniently attribute the label as part of attributing the accuracy of the recording. Bear in mind a recording is only a "factual claim" if it's been independently verified, though that's a separate issue, and I've seen no reason to doubt this recording. DFlhb (talk) 12:28, 29 October 2023 (UTC)

  The BBC sometimes employs the term "terrorism" without providing attribution, such as in their coverage of the Ariana Grande concert bombing in Manchester, for instance. And here is another Hindustan Time article, where they appear to be referring to Hamas's attack as a "terror attack". I suppose the person in question made a phone call home during that attack. What would be the correct way to attribute the use of the word "terrorist" concerning the individual making the call home or should we just ignore the sources that use it? Infinity Knight (talk) 14:41, 29 October 2023 (UTC)

  Attribution of the word terrorist about that individual is exactly what my comment addresses. DFlhb (talk) 15:19, 29 October 2023 (UTC)

  You seem to have grasped what I was trying to get at in my post more than most others. May I ask, incidentally, do you have any suggestions on how we might advance this? Is it worth a post in the MOS talk? or NPOV noticeboard? Yr Enw (talk) 15:32, 29 October 2023 (UTC)

  It's advanced by making bold edits, and seeking consensus on talk pages if need be. DFlhb (talk) 17:28, 29 October 2023 (UTC)

  Can’t help but feel that’s just going to lead to endless debates with conflicting interpretations of the existent guidelines, of the kind that led me here in the first place Yr Enw (talk) 17:39, 29 October 2023 (UTC)

Discussion (MOS contentious labels)

According to WP:INTEXT, "in-text attribution" includes use in Wikivoice. I do not understand this statement. WP:INTEXT describes in-text attribution as "the attribution inside a sentence of material to its source". It then goes on to give several examples where not to use in-text attribution, because it would be non-neutral or otherwise misleading, but that doesn't alter the fact that in-text attribution involves explicitly attributing the wording, which is the opposite of wikivoice.--Trystan (talk) 10:51, 23 October 2023 (UTC)

I had potentially misunderstood those examples as saying wikivoice can still count as ITC. So, if that’s not the case, okay. What I’m saying though is that with the word terrorist/terrorism there is an inherent neutrality problem when in text attribution is avoided in favour of wikivoice. Yr Enw (talk) 11:03, 23 October 2023 (UTC)

I read MOS:TERRORIST as saying avoid or attribute (even if widely sourced) and I am fine with that. Selfstudier (talk) 11:22, 23 October 2023 (UTC)

So am I, but it doesn’t appear to always be attributed in practice. For example in Jaffa Road bus bombings and, ofc, the September 11 attacks. Yr Enw (talk) 11:30, 23 October 2023 (UTC)

Can you give examples of how the lead sentences of those two articles might read were your proposal adopted? Wehwalt (talk) 11:43, 23 October 2023 (UTC)

Something like “X was widely recognised/condemned as a terrorist attack”, following an article like 1996 Manchester bombing, but for September 11 in the lead (for WP:DUE) given the prominent association of the attacks with that term. Yr Enw (talk) 13:40, 23 October 2023 (UTC)

The "widely recognised" language doesn't provide in-text attribution. In-text attribution sounds like "was called a terrorist organization by Alice, Bob, Chris, David, Eve, Frank, and many others". WhatamIdoing (talk) 00:31, 24 October 2023 (UTC)

I was envisioning the "widely recognised" sentence to have a bunch of citations at the end. Yr Enw (talk) 06:32, 24 October 2023 (UTC)

Or an alternative demonstration of widely recognized. Selfstudier (talk) 10:56, 24 October 2023 (UTC)

In my experience, "was called <names>.^{[1][2][3][4][5][6]}" is at risk for getting a {{by whom?}} tag. WhatamIdoing (talk) 22:59, 28 October 2023 (UTC)

I would be inclined to allow Wikivoice if the perpetrator is as well included in the UN consolidated list (AQ, IS being the most notable). Selfstudier (talk) 11:43, 23 October 2023 (UTC)

• When we're using the strongest labels -- "evil", "terrorist", "terrorism", "act of terror", "extremist", "fundamentalist", and other words at that level -- I'd prefer it if the in-text attribution came before the label. So we'd get The British government called this an act of terrorism, and not An act of terrorism, in the British government's view.—S Marshall T/C 23:33, 26 October 2023 (UTC)

  1. In-text attribution cannot be applicable to article names and list articles such as List of terrorist incidents in London. Hence, it is imperative that the Wikipedia community reaches a consensus on a precise definition of 'Terrorism'.
  2. Moreover, it would be absurd to label the events of terrorist attacks such as 9/11 as a 'Militant attack' —a euphemistic term that grossly understates the gravity of the tragedy. The notion that this incident was not a terrorist attack is a fringe view and does not align with the mainstream understanding and historical narrative surrounding the events of that day. September 11 attacks uses the wording 'Islamist suicide terrorist attacks', Britannica describes this as 'the deadliest terrorist attacks on American soil in U.S. history' and there are few people who would contest this characterization.
  3. The above arguments apply to 'acts of terror' and 'terrorist organizations'. I'm not talking about moral judgements such as "evil" which are non-encyclopedic and should be kept outside of the scope of this discussion, in my view.

  Marokwitz (talk) 19:23, 27 October 2023 (UTC)

  Terrorism can sometimes be thrown around as a sort of diss by folks trying to paint something or someone in a bad light. But there are times when it's just plain facts. Take this person reported by Hindustan Times, for example. Hindustan Times didn't hold back on the title. So, just rattling off the names of countries where governments have spotted these global celebs and put them on a list, well, that's a little one-sided, since that list doesn't even include countries like India or Ukraine, to kick things off. Infinity Knight (talk) 21:49, 27 October 2023 (UTC)

• As the old saying goes, "One man's terrorist is another man's freedom fighter." "Terrorism" is a label often applied by the strong to the weak, the strong having the assumption that the use of violence on their behalf is justifiable, legitimate self defense and that violence opposing the strong is "terrorism." Plus, too often the use or non-use of the word "terrorism" is political. I may be wrong on this, but I don't think that U.S. government called the IRA a "terrorist organization." Why not? Our politicians didn't want to lose the support of voters of Irish origin in the U.S. Likewise, I doubt that we in the U.S. are going to call actions by Israel or Israeli citizens against the Palestinians "terrorism" although some acts of violence against Palestinians in the past and probably more in the future may deserve that designation.

  Also, we are horrified when a gunman shoots civilians in, for example, a grocery store, citing as a reason its help to enemies. But we are less horrified when an airplane drops a bomb on a grocery store and kills civilians citing as a reason its help to enemies. That's just collateral damage or military necessity.

  All that is by way of saying that a definition of terrorism is impossible. However, I don't oppose the use of the word "terrorism" or "terrorist" provided that it is cited as the view of a reliable, non-partisan source. Certainly the recent Hamas attacks on Israeli civilians qualify as terrorism. We should also, however, ensure that the motives and political aims of the "terrorists" are explained. We shouldn't let the strong dictate what we say about the weak. Smallchief (talk) 12:47, 29 October 2023 (UTC)

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

About page reviewing

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.

---

Should Page Reviewer rights be merged with Extended Confirmed rights so that Extended Confirmed editors can review drafts and recently created articles. Even if the Extended Confirmed editor doesn't apply for Page Reviewer rights? CosXZ (talk) 20:16, 30 October 2023 (UTC)

My perspective is that this definitely should not happen. WP:NPR is a sensitive right that demands more compared to other rights such as pending changes reviewers. Allowing all extended confirmed editors to review would lead to more abuse by bad-faith editors/socks/disruptive editors, lower the quality of CSD taggings/draftications/AfDs, and cause more clearly deficient articles being marked as reviewed. VickKiang (talk) 20:47, 30 October 2023 (UTC)

I believe that that is a very bad idea. NPR currently operates on a set of minimum requirements that are higher than the EC requirements, and even then it is not a guarantee. Also, EC is easily gamed. They should definitely not be merged. QuicoleJR (talk) 21:47, 30 October 2023 (UTC)

Note that I notified WT:NPR and WT:PERM on this, with the following: Notifying that a discussion on whether to merge NPR rights with extended confirmed is currently being discussed at VPP. This would fall under WP:APPNOTE which permits the talk page or noticeboard of one or more WikiProjects or other Wikipedia collaborations which may have interest in the topic under discussion. VickKiang (talk) 01:24, 31 October 2023 (UTC)

As someone recently given temporary approval to participate in new page patrol, I move against this motion. This is not a pleasant side of Wikipedia for anyone not fluent in WP:ACRONYMS. No one who does not explicitly request it should be exposed to this kind of technical bickering. (This with all due respect to everyone for all of their unpaid time and attention to Wikipedia—and also acknowledging that my own participation contributes to the problem.) Patrick J. Welsh (talk) 01:47, 31 October 2023 (UTC)

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

RfC on reducing the privileges afforded to the WMF under WP:CONEXCEPT

The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion. A summary of the conclusions reached follows.

Withdrawn, clear consensus against this proposal, although future editors interested in this topic may want to note that there was more support for an option to overturn CONEXECPT actions and a future proposal in that line (eg, The WMF has legal control over, and liability for, Wikipedia. Decisions, rulings, and acts of the WMF Board and its duly appointed designees presume consensus, but may be overturned by community consensus so long as said decisions, rulings, and acts are not required to comply with the WMF's obligations.) may be more successful. BilledMammal (talk) 08:31, 2 November 2023 (UTC)

---

WP:CONEXCEPT currently reads:

Certain policies and decisions made by the Wikimedia Foundation (WMF), its officers, and the Arbitration Committee of Wikipedia are outside the purview of editor consensus. This does not constitute an exhaustive list as much as a reminder that the decisions taken under this project apply only to the workings of the self-governing community of English Wikipedia.

• The WMF has legal control over, and liability for, Wikipedia. Decisions, rulings, and acts of the WMF Board and its duly appointed designees take precedence over, and preempt, consensus. A consensus among editors that any such decision, ruling, or act violates Wikimedia Foundation policies may be communicated to the WMF in writing.
• Office actions are not permitted to be reversed by editors except by prior explicit office permission.
• The English Wikipedia Arbitration Committee may issue binding decisions, within its scope and responsibilities, that override consensus. The committee has a noticeboard, Wikipedia:Arbitration/Requests/Clarification and Amendment, for requests that such decisions be amended, and may amend such decisions at any time.
• Some matters that may seem subject to the consensus of the community at the English-language Wikipedia (en.wiki.x.io) are in a separate domain. In particular, the community of MediaWiki software developers, including both paid Wikimedia Foundation staff and volunteers, and the sister wikis, are largely separate entities. These independent, co-equal communities operate however they deem necessary or appropriate, such as adding, removing, or changing software features (see meta:Limits to configuration changes), or accepting or rejecting some contributions, even if their actions are not endorsed by editors here.

Should it be changed to:

Certain policies and decisions made by the Wikimedia Foundation (WMF), its officers, and the Arbitration Committee of Wikipedia are outside the purview of editor consensus. This does not constitute an exhaustive list as much as a reminder that the decisions taken under this project apply only to the workings of the self-governing community of English Wikipedia.

• The WMF has legal control over, and liability for, Wikipedia. Decisions, rulings, and acts of the WMF Board and its duly appointed designees that are needed to comply with legal obligations take precedence over, and preempt, consensus.
• Office actions are not permitted to be reversed by editors except by prior explicit office permission.
• The English Wikipedia Arbitration Committee may issue binding decisions, within its scope and responsibilities, that override consensus. The committee has a noticeboard, Wikipedia:Arbitration/Requests/Clarification and Amendment, for requests that such decisions be amended, and may amend such decisions at any time.
• Some matters that may seem subject to the consensus of the community at the English-language Wikipedia (en.wiki.x.io) are in a separate domain. In particular, the community of MediaWiki software developers, including both paid Wikimedia Foundation staff and volunteers, and the sister wikis, are largely separate entities. These independent, co-equal communities operate however they deem necessary or appropriate, such as adding, removing, or changing software features (see meta:Limits to configuration changes), or accepting or rejecting some contributions, even if their actions are not endorsed by editors here.

The section that is proposed to be changed is highlighted in bold. 01:01, 3 October 2023 (UTC)

Related discussions

There are three related discussions that editors involved in this may be interested in; they are listed here.

Survey (CONEXCEPT RFC)

• Support, primarily to make the paragraph consistent with our broader values of collaboration, transparency, and consensus, as well as act as a safeguard against WMF overreach. If the WMF needs to overrule us then they should be able to - but absent any such need they should instead work with us to try to implement a change that they believe is necessary, and they should accept the communities consensus if their change is rejected.
  I also hope that this will serve to improve the long-term relationship between the WMF and the English Wikipedia, by shifting us away from a situation where we are functionally their subordinate and towards a situation where we are their partner. BilledMammal (talk) 01:01, 3 October 2023 (UTC)
• Doesn't really go far enough. It should be changed to read that WMF may only overrule the community when it is literally legally required to do so. This isn't a significant change, and it should be one. Seraphimblade ^{Talk to me} 01:27, 3 October 2023 (UTC)
• Oppose for the time being, as an example of pursuing something just for "the principle of it" without any information about the actual practical implications.
  Putting aside the quandary of proposing changes to a rule that basically prevents us from changing the rule, what actual problems would this solve? What are the ways the WMF has trumped local consensus in the past which were allowed under the current wording, but would be disallowed under the proposed wording? Especially curious for examples where existing mechanisms failed to achieve a good result. Also, what work are the words "legal" and "obligations" doing here? Legal matters that are not obligatory aren't covered, presumably? So best practices and precautions for following the law don't qualify? Global bans dealing with sensitive personal information, for example, would be subject to an ad hoc !vote with a bunch of volunteers? I'd be curious about what other things would be excluded here. — Rhododendrites ^talk \\ 01:31, 3 October 2023 (UTC)
  • +1. — Frostly (talk) 02:03, 3 October 2023 (UTC)

  WP:FRAMBAN is the most obvious and recent example, I suppose. The Trust & Safety department of the WMF placed several sanctions as office actions, which under this policy the enwiki community couldn't challenge directly (one admin tried and was desysopped for it). The only way we broke the stalemate was by complaining loudly and by the ArbCom of the time going over T&S' heads with a letter to the WMF Board, asking them to give it permission to review the case, which they did. The overall result was an enormous amount of wasted volunteer time and aggrevation over what, in the end, was a transparently bad call by T&S. I'm not sure where I stand on this proposal yet, but I can certainly see how restricting office actions to legal matters would have stopped, or at least made it easier for the community to object to, WMF attempts to intervene in user conduct issues, like FRAMBAN. – Joe (talk) 05:20, 3 October 2023 (UTC)

• Oppose as factually incorrect. I might not like it, but the board can overrule the community – for legal reasons or otherwise. If the board decides to shut enwiki down tomorrow, it doesn't matter why they made that decision. Enwiki would be shut down tomorrow, and that will not change if this proposal passes. Policies are descriptive, not prescriptive, and we cannot change reality by attempting to live in a fantasy land. HouseBlaster^talk 01:59, 3 October 2023 (UTC)

  The difference it will make is in how they overrule us. Currently, they can overrule us, point to this policy, and per our own policies we have to do what they say - the effort the WMF has to put into overruling us is minimal, and thus the cost of doing so is minimal. However, absent this policy they will need to take direct action to implement the change, and that will be a drain on their resoheaurces.

  You're right that they can still do so, but their ability and willingness to do so will be degraded, and I consider that a very positive step. BilledMammal (talk) 02:26, 3 October 2023 (UTC)

  The WMF doesn't like overriding community consensus for fun. Heck, in the post FRAMGATE world, they actively seek consensus where possible. They redesigned banners last year, and were unable to meet their fundraising goal. They opened an RfC before rolling out Vector 2022 (and yes, this counts; enwiki admins closed the two RfCs and determined consensus just like any other RfC; it is only different if we want to ban the foundation from making suggestions). They are already very unwilling to override consensus; all of the stuff at WP:FRAM happened under the current wording. The current policy was sufficient to get the foundation to go from "no appeals, no exceptions" to "ArbCom gets to decide the future of this ban". In sum, they already are already unwilling to override consensus and we already can push back when we feel they have stepped out of line. Actions don't need to be against policy to be "wrong" or open to criticism. HouseBlaster^talk 03:57, 3 October 2023 (UTC)

  To be pedantic, the WMF can force enwiki onto a non-WMF platform tomorrow. Alternative backers will fight for the tens of millions that come through that Donate link in the sidebar. Some candidates may even offer us better terms than the WMF. Certes (talk) 14:38, 3 October 2023 (UTC)

  I would also say that this proposal is a matter that should be discussed at the level of WMF, because it intends to regulate actions of WMF, not of enwiki editors. Janhrach (talk) 16:24, 13 October 2023 (UTC)

• I agree with Rhododendrites. I doubt this will have the intended effect, or really any effect at all. — Wug·a·po·des 02:45, 3 October 2023 (UTC)
• Support. Policies are decided by consensus. It makes no sense to have a consensus that consensus can be overruled. If the WMF wants to throw its weight around, then that's their decision. But we do not benefit in any way from actively encouraging it. I agree with Seraphimblade that the language could be stronger still, but I'm supporting as this wording is better than the status quo. Thebiguglyalien (talk) 03:18, 3 October 2023 (UTC)
• Support. Since my return I've been a bit shocked (perhaps naively so) at the veiled and not-so-veiled hostility between en and the Foundation.
  It would be a disruptive, existential crisis for a large group of en editors to fork and leave Wikimedia. But as someone who has a bit of of benefit of distance, reading over the past many years of controversy it's pretty clear that's the rough direction the relationship is going in.
  The benefit of such a change is that it draws a very clear line on the part of the en community, when the Foundation appears unable to do so. This doesn't have a direct effect on Foundation actions. But it makes it clear what actions the en community considers valid, and I hope such clarity can help lower the temperature, where ambiguity has raised it. I'm open to alternatives, but the idea here is a good one. —siroχo 03:31, 3 October 2023 (UTC)
• Oppose as it removes the ability for the enwiki community to formally protest decisions of the foundation that violate their own policies (Putting aside the quandary of proposing changes to a rule that basically prevents us from changing the rule). Also history suggests that the premise that the effort the WMF has to put into overruling us is minimal is very wrong in any circumstances the community actually cares about. Barkeep49 (talk) 03:37, 3 October 2023 (UTC)

  I agree with what Joe Roe said below, but I'll add that I can't see any situation under the proposed version of CONEXCEPT that the WMF could make such a decision - any such decision would go beyond what is needed to comply with legal obligations - and thus instead of needing to formally protest we just say "no, go get a consensus". BilledMammal (talk) 07:20, 3 October 2023 (UTC)

• Weak oppose, though spiritually I can see where this is coming from. Mostly I subscribe to the Rhodendentries argument on lack of effect, and to use the words of Cullen328 from the paid editing admin disclosure RFC, it's "a solution in search of a problem". With the WMF, it's usually better to WP:Drop the stick when it comes to office actions. I expected of them to uphold the present social contract between editors and the WMF, and so far I think they've done a good job at upholding their end. InvadingInvader (userpage, talk) 03:47, 3 October 2023 (UTC)
• Support as a shift in the balance of power toward clearly-defined roles and against nebulous subservience. This may well do nothing, as suggested above, but I don't see how it could harm anything. * Pppery * _{it has begun...} 04:26, 3 October 2023 (UTC)

  Removing a formal process for us to protest out of process CONEXEMPT actions does strike me as harmful. Best, Barkeep49 (talk) 04:32, 3 October 2023 (UTC)

  Do we need a formal process? I would've thought it was a given that we can inform the WMF about anything we like "in writing" (how else?), prior permission or not. – Joe (talk) 06:01, 3 October 2023 (UTC)

  Oh, I see, there's two separate issues here. I concur there's no reason to remove "A consensus among editors that any such decision, ruling, or act violates Wikimedia Foundation policies may be communicated to the WMF in writing", although it does seem kind of redundant. I still prefer the wording of the first sentence proposed in this RfC to the existing one, though. * Pppery * _{it has begun...} 20:14, 3 October 2023 (UTC)

• Oppose. Limiting things to where there is a legal obligation may cause problems with things that are legal good practice but not obligations and also enforcement of aspects of the terms of use and codes of conduct that they may not be legally obligated to do. I'm also seeing a complete lack of any evidence of any actual problems caused by the current wording. Thryduulf (talk) 08:17, 3 October 2023 (UTC)
• Oppose, largely per HouseBlaster and Barkeep. Changing the wording of this policy does not really change anything. It's a statement of fact that the WMF can override policies or consensuses on en.wp if it wishes. Changing the wording will not restrict the WMF's ability to do so. Even if it did, introducing the 'on legal grounds' wording doesn't really help much - legal grounds are themselves complicated, debatable and subject to interpretation - the en.wp community does not really have the level of expertise needed to interpret and debate them. Further, the WMF in practice is pretty keen to engage in dialogue these days and follow community consensus even on things like the fundraising banners (which it wouldn't have done at any previous point in the history of Wikipedia). The Land (talk) 09:12, 3 October 2023 (UTC)
• Neutral. It doesn't change the reality which is that the WMF can shut enwiki down in the morning if it wanted to. Stifle (talk) 10:17, 3 October 2023 (UTC)
• Oppose As it stands the WMF knows that they can override us, but if we disagree with them it will probably be a bit disaster. If we change this, the only different seems to be we've told the WMF you cannot override except in specific circumstances; but we know they still can and if we disagree it will be a bit of a disaster. I'm concerned that with this change rather than us considering, did the WMF have a reason to override us sufficient for us to just accept it; it will become a case of the WMF overrode us and it technically didn't fit the narrow parameters we defined so fuck them no matter that actually they probably did right thing. (I mean I feel there's already something like that but I don't see a reason to make it worse.) Nil Einne (talk) 11:33, 3 October 2023 (UTC)
• Support. I agree with Thebigugly alien. The WMF should have no need to interfere in community affairs outside of legal problems; the community regulates itself by consensus. The proposed change makes this position clear. Edward-Woodrow • talk 12:17, 3 October 2023 (UTC)
• Moot per HouseBlaster. The current reading of the text reflects reality. Changing it would just make the policy of WP:CONEXCEPT substantively incorrect, and I don't see how it helps anyone to tell ourselves to alter policy and scream from the heavens that WMF cannot or should not trump the common wisdom of Wikipedia as much as it can already do, and indeed has done. _{Duly signed,} ⛵ WaltClipper -(talk) 12:41, 3 October 2023 (UTC)
• Support per Thebiguglyalien and others. Gradually, over many years, the WMF has expanded dramatically in size and broadened its remit beyond all recognition. Whatever the technical merits of Vector 2022, its appearance and imposition out of nowhere is a perfect example of the WMF's disdain for readers and editors alike. It's time to issue a gentle reminder of why we're here. Certes (talk) 15:19, 3 October 2023 (UTC)
• Support restricting CONEXCEPT to "legal obligations" instead of the current rule, which can be paraphrased as "whenever the WMF feels it's best." Yes, the web host -- whoever it may be -- will always have legal obligations that the web host must and will follow, even if the user community doesn't agree. That should be the extent of CONEXCEPT. Beyond legal obligations, community consensus should rule. I also support removing the other sentence about lodging a complaint, because it implies that's the only thing the community can do. That sentence doesn't create any formal process, we already have a formal process (RFC), and there is much more the community can do (and has done, eg FRAMGATE, last year's fundraising RfC), than just lodge a complaint. Levivich (talk) 17:11, 3 October 2023 (UTC)

  Some oppose voters are pointing out that the web host can do whatever they want, regardless of what rules the user community comes up with. Yeah, that's true. But WP:CONEXCEPT is not a real-life rule, it's a Wikipedia rule (part of the core, foundational policy of this website, WP:CONSENSUS). The purpose of the document isn't to restrict the web host, it's to document what consensus is. Or, in other words, in my view, this proposal is not about what the WMF can do, it's about what the rest of us agree to. So, yeah, the web host can do whatever they want, up to and including pulling the plug and shutting down the whole website. But I support this proposal because I don't agree to the web host being able to overrule consensus, except when due to legal obligations. Levivich (talk) 23:08, 3 October 2023 (UTC)

• Oppose and Moot - There are and will always be issues that are not quite legal obligations that the Wikimedia Foundation should be the one to make decisions on, even if it conflict with individual project's wishes. There are decisions that are good for the Wikimedia movement as a whole that may be disliked by individual project, where it is undesirable for projects to have differing responses. And moot because such a change to the policy would itself falls under the existing policy exemption. -- KTC (talk) 17:43, 3 October 2023 (UTC)
• Support. The rule of the the server obviously gives the WMF the ability to override this if they want to, but our policies should reflect the community's desires and should communicate where we stand to the WMF, which would be better with the altered wording. In the past the WMF has stepped in it because they assumed that the existing CONEXCEPT language reflects the uncontroversial consensus of the community, which it absolutely does not; making it clear that the community's desires are that the WMF only override it in cases of legal necessity (and that carelessly overriding community consensus or failing to seek consensus at all for vital changes may result in a drastic blowback) would be preferable, even if the practical reality is of course that whoever controls the physical servers can do what they please. For the people who say that they don't see the problem, just look at the problems caused by WMF actions in the past; the WMF has trusted the previous CONEXCEPT language, which was a mistake because it is wrong - it doesn't reflect community consensus, and it is, in practice, subject to community consensus. And this addresses the other objection people have made above - the text absolutely is incorrect in putting itself above consensus; the very fact that we are having this discussion proves that. As a practical matter the WMF can obviously override any of our consensuses but we have the ability to define what those consensuses are and to make it clear where the lines are that will cause blowback if crossed carelessly; the fact that we have failed to make that clear in the past has benefited neither us nor the WMF. --Aquillion (talk) 18:11, 3 October 2023 (UTC)
• Out of scope - As WMF has control over all of Wikipedia, if you are displeased with Wikimedia Foundation actions, the only option you have is the right to fork. WMF will always have control over Wikipedia servers and always will have the ability to make decisions for the entire site, regardless of consensus. Changing this bit of text will not change this fact. Website owners have the right to determine policies for their website. Wikipedia is no exception. The best solution would be to have a WMF-appointed community liaison announce changes ahead of time so that community members can give feedback before they are implemented. That used to be Jimbo, but now Jimbo is quite distanced from Wikipedia in the hierarchy, only being one of several Board of Trustee members. Aasim - Herrscher of Wikis ❄️ 20:29, 3 October 2023 (UTC)

• Oppose Creating a Wikipedia account does not and should not give you any rights. CONEXCEPT is necessary for software changes. Hawkeye7 (discuss) 20:44, 3 October 2023 (UTC)

  CONEXCEPT will still apply for software changes; the fourth dot point, which deals with that, remains unchanged. BilledMammal (talk) 04:46, 4 October 2023 (UTC)

• Weak oppose I would support changing the first sentence from
  The WMF has legal control over, and liability for, Wikipedia. Decisions, rulings, and acts of the WMF Board and its duly appointed designees take precedence over, and preempt, consensus.
  to
  The WMF has legal control over, and liability for, Wikipedia. Decisions, rulings, and acts of the WMF Board and its duly appointed designees that are needed to comply with legal it's obligations take precedence over, and preempt, consensus.
  -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 22:05, 3 October 2023 (UTC)
• Oppose per Rhododendrites Gamaliel (talk) 23:05, 3 October 2023 (UTC)
• Oppose per Opposers. But especially Rhododendrites and the slant of the proposal that only legal "obligations" can overrule community consensus. This is "legalistic" in the bad way (as in, not actually legal, just faux-legal). There are lots of things where, strictly speaking, there isn't a law against doing something, but doing it anyway would be really stupid and could invite legal peril later. As an example, in most contracts, you aren't "obligated" to fulfill your end of the bargain - you can just break it (efficient breach). Does this mean an angry community mob can just be allowed to break unpopular contracts, even if there is a 1 zillion dollar penalty for doing so? Same with privacy concerns - often there's very vague obligations where any one step isn't clearly breaking the law, until some angry government official looking to make a name for themselves takes the collection of decisions and uses it to make a case. SnowFire (talk) 23:11, 3 October 2023 (UTC)
• Oppose, agreeing with sentiments that this is a solution in search of a problem. Post-FRAM, the foundation will have (what it thinks is) a very good reason to override community consensus if and when it does, demonstrated by the much-appreciated effort by the WMF in fundraising and the Vector RFC (and the time spent on that)(per Houseblaster). In addition, I suspect that T&S learned a lot from fram, and they take the time to regularly meet with arbcom now (I don't think fram is a problem that needs fixing now). Also per sentiments like Thryduulf. —Danre98^{(talk^contribs)} 03:42, 4 October 2023 (UTC)
• Oppose, for now. There hasn't been another "Fram incident" since, well, the Fram incident, so I would like to at least cautiously hope that lessons were appropriately learned from that. So, let's see if those stay learned. If it turns out they didn't, well, we can always consider stronger medicine at that point (and I'll be the first one supporting it if that day comes), but right now I don't see it being needed. Seraphimblade ^{Talk to me} 04:59, 4 October 2023 (UTC)
• Something, but not this I think the current wording goes a bit far, in that it says anything WMF does preempts consensus. But the proposed change goes too far in the other direction. IMO the reality is somewhere in between: the WMF has the power to try all sorts of stuff, but that doesn't mean we shouldn't push back if consensus says they've overstepped. Anomie⚔ 07:09, 4 October 2023 (UTC)

  Would you be suggesting something along the lines of the WMF can preempt consensus, so long as there isn't a consensus against their position? (Ie, a "no consensus" result for something the WMF supports will default in favor of their position, rather than in favor of the status quo)? Combined with ActivelyDisinterested's suggestion I wonder if something like this (subject to copy editing) would be more palatable:

  The WMF has legal control over, and liability for, Wikipedia. Decisions, rulings, and acts of the WMF Board and its duly appointed designees presume consensus, but may be overturned by community consensus so long as said decisions, rulings, and acts are not required to comply with the WMF's obligations.

  I think it is too late to switch to for this RFC, but it may be worth considering in a future one? BilledMammal (talk) 07:18, 4 October 2023 (UTC)

• Oppose per Risker, below. --In actu (Guerillero) ^{Parlez Moi} 11:18, 4 October 2023 (UTC)
• Oppose, principally per Rhododendrites and SnowFire. Restricting the WMF's putative remit to "legal obligations" creates the risk that currently uncontroversial WMF actions, if based on things that are best practice but not strict legal requirements (e.g. pertaining to individuals' privacy), could be turned into major points of contention and cause further friction between the WMF and the enwp community. I also don't find myself convinced that the proposed change in language would substantively change the WMF's ability or willingness to take any given action. ModernDayTrilobite (talk • contribs) 15:44, 4 October 2023 (UTC)
• Oppose I am concerned that the expression "legal obligations" is being used far too lightly. Particularly for large organisations it may be unclear what is a legal obligation until the courts have decided. How a business should behave will be a policy matter possibly (in the US) up to the Supreme Court. And as for jurisdictions outside the US, such jurisdictions can decide Wikipedia is breaking their laws. It will be a matter of policy whether to continue, so risking fines, sanctions on local editors and internet blocking. WMF, and not volunteer editors, need to bear the weight of all this uncertainty. Thincat (talk) 16:03, 4 October 2023 (UTC)
• Snow Oppose. While appropriately located in a policy page, the language in question here is less a reflection of community consensus and more just information relating legal and pragmatic realities that are simply not within the purview of the community to significantly change. We are volunteers with this project; the WMF have a fiduciary role, and they are not just entitled (by both internal and extrinsic factors defining this project's governance) to override volunteer decisions, where they have cause to believe it is in the best interests of project and to prevent certain kinds of harm to it or third parties--they are in fact legally and ethically obligated to do so.
  As Aasim quite aptly states above, anyone who has issues with that largely immutable state of affairs can feel free to stop volunteering their time here and attempt to create a similar project where they can position themselves in a fiduciary role, with all of the accordant responsibilities and authority, but with regard to this project, there are some things that volunteers, no matter how numerous or how dissatisfied, are simply not empowered to change. Therefore the proposal would accomplish nothing except to change the information contained in that section to be less accurate as to the division of authority and responsibilities between the community and the WMF and potentially foster unacceptable disruption.
  The reality is, much as we understandably value the wisdom-of-the-masses/consensus decision making model that defines our editorial and community standards, when it comes to certain activities, the WMF fiduciaries and the staff they designate for T&S and other functions are the final authority, and certain office actions are not permitted to be undone by volunteers--even our most highly positioned. If you are a volunteer on this project, you just have to accept that. SnowRise ^{let's rap} 17:38, 4 October 2023 (UTC)
• Oppose, the amendment is hopelessly vague on its face, as it is apparently assumes, random, 'nobody knows your a . . ., on the internet, will parse what "legal obligations" are -- no: real, known experts go through lengthy qualifications and long evolving trials to find that out for real and legal issues are constantly evolving. Also, in a system such as this, which is vulnerable to mobocracy, checks and balances are particularly crucial. Alanscottwalker (talk) 15:37, 5 October 2023 (UTC)
• Oppose. On consideration I believe there are numerous areas where the Foundation is required to take actions that don't fall within a strict definition of "legal obligation". Espresso Addict (talk) 23:03, 5 October 2023 (UTC)
• Oppose. The fact of the matter is that the WMF can pretty much do whatever it pleases, and while this community can complain about and protest against the WMF's actions in the most vehement of terms (and indeed, we have, we do, and we will), we have no authority to force the WMF to do anything. The text of CONEXCEPT should accurately reflect that dynamic. Mz7 (talk) 03:27, 7 October 2023 (UTC)
• Oppose. Per Rhododendrites, Houseblaster, and most of the other oppose comments above. Mike Christie (talk - contribs - library) 11:19, 7 October 2023 (UTC)
• Oppose, the WMF has the power to overrule the community outside of this narrow restriction. It is used sparingly, but used nonetheless, for example with WP:FRAMBAN and with WP:VECTOR2022, so presumably the WMF wants to keep it around. The proposed change unilaterally enacted by the community would be a symbolic gesture, but its practical impact and enforceability is unclear. I do not view the symbolic gesture as worth the potential for creating more conflict with the WMF. (And since legal issues are under discussion, the WMF would probably appreciate a broad remit if only for potential legal contingencies, and I don't think that is something we would want them to lack.) CMD (talk) 12:27, 7 October 2023 (UTC)
• Support the role of the WMF should be as limited as legally possible. This is a project made by the community, and the community should be in charge --Ita140188 (talk) 14:10, 9 October 2023 (UTC)
• Oppose per Rhododendrites and SnowFire.Pharaoh of the Wizards (talk) 22:24, 9 October 2023 (UTC)
• Oppose per SnowRise "and most of the other oppose comments above." The WMF's position as owner does give them certain rights that includes "final authority". We are not in some battle with the WMF. The editing world of wikipedia has secured a certain collective autonomy. This seems to be a world where each needs the other to advance the goal of a free encyclopedia so there is no reason to poke the bear. The WMF seems to have goals and obligations to ensuring the various projects exists in perpetuity. -- Otr500 (talk) 15:50, 14 October 2023 (UTC)
• Support One point many of those opposing this change overlook is the qualifying language immediately before this list of exceptions where consensus can be overruled by the Foundation: "This does not constitute an exhaustive list". So if the purview of this exception is reduced, it does not necessarily mean that the Foundation cannot overrule in some area not listed here.
  So what value do these listed exceptions have? IMHO, this does not apply to the Foundation whatever. What these exceptions apply to is what areas the en.wikipedia community may be asked to support some action. As pointed above, some or all of us volunteers could decide in response to some action of the Foundation to fork; this is an extreme act, & should not lightly be done, but if the Foundation attempts to overrule a consensus outside of these 4 areas, we reserve the right to fork over that act.
  I wish these exceptions could limit the powers of the Foundation. One oversight when the Foundation became an actual institution was an binding agreement about exactly what the Foundation would be empowered to do, with everything else being reserved to the various project communities. Had that been done, we could have avoided the Foundation arrogating the rights & duties of we volunteers. But it wasn't, & now we have the situation where the Foundation is free to act capriciously & irresponsibly towards the volunteer communities. For example, turn off the ability to edit articles or any pages & turn all of the projects in a Knowledge Machine. -- llywrch (talk) 06:50, 23 October 2023 (UTC)
• Oppose; regardless, this is out of scope. Wikimedia has full control of enwiki, regardless of what we say/want. Sure, it sounds nice, but it functionally does nothing. In these post-FRAMGATE times, WMF has, multiple times, sought out consensus, and while I am not necessarily a fan of their methods in many cases, they have complied with policy, and that is as much as we can reasonably expect. Forcing WMF to leave us alone by changing the rules to make it harder for them to interact with us is a terrifyingly hostile way to go about things, methinks, one that will only add to the WMF-enwiki tension. Cessaune [talk] 16:12, 25 October 2023 (UTC)
• Oppose. Seems like a (symbolic) solution in search of a problem. If this is about WP:FRAMBAN, I would say WP:DROPTHESTICK. Sometimes the WMF's decisions are clueless, but they do own the servers whether we like it or not. Luckily they don't blatantly overrule the community very often (unlike Reddit). Nosferattus (talk) 05:47, 28 October 2023 (UTC)

Discussion (CONEXCEPT RFC)

• Does the English Wikipedia even have the power to tell the Foundation (which somewhat owns all of the resources for this project save for the people) what it can and can't do? (I mean, everyone could fork, or everyone could make noise and complain to try to goad the WMF to change its course (reminiscent of how Framgate played out), but short of those two options this strikes me as a bit reminiscent of the ending of You're Not Elected, Charlie Brown: Linus meets with the principal to force him to implement the platform policies Linus had been elected upon, only to leave the room five minutes later and respond to "Well, did you tell him?" with a sheepish "...actually, he told me." 2600:1012:B164:9F55:5845:635D:767C:169B (talk) 02:40, 3 October 2023 (UTC)
• I'm intuitively leaning towards a strong support here, but I'd like more information. I can't think of a legitimate reason for the WMF to overrule en.wiki consensus, other than legal reasons. Can anyone provide an example of a situation where it's legitimate and important, for non-legal reasons, for the WMF to be able to overrule consensus? Pecopteris (talk) 03:58, 3 October 2023 (UTC)

  Safety of individuals/groups, site security, ability to operate the website(s); each of them has been in play in dozens of scenarios where the WMF hasn't done what (some) people on English Wikipedia wanted. Risker (talk) 04:58, 3 October 2023 (UTC)

  First would fall under legal, if I have understood correctly what scenarios you are referring to, second and third are technical matters and would fall under Some matters that may seem subject to the consensus of the community at the English-language Wikipedia (en.wiki.x.io) are in a separate domain. BilledMammal (talk) 06:35, 3 October 2023 (UTC)

  No, the first does *not* fall under "legal". And the second and third are both exactly the type of issues that have repeatedly caused invocation of CONEXEPT, to the dismay of the English Wikipedia community. They *are* the real-world examples under which this rule has created tensions between the community and the WMF. It would be helpful if you spent more time learning the history of these policies, and the actual reasons behind them, as it would result in better proposals. Risker (talk) 17:55, 3 October 2023 (UTC)

  The WMF's Trust & Safety team is part of its Legal department, is it not? If so, that would suggest that, yes, trust & safety would fall under "legal."

  Anyway, hard to see why/how the safety of individuals/groups, site security, or ability to operate the website(s), would require overruling consensus. Levivich (talk) 18:31, 3 October 2023 (UTC)

  Trust and safety currently is part of legal. But that hasn't always been the case. If that's the way people are interpreting legal that's pretty reassuring compared to the way I did

  I thought the revised wording would only cover things like following laws (eg DMCA) or following a court order. This would omit a variety of actions currently taken to protect editors, such as from authoritarian regimes (where the action might actually be illegal) but is following through on the safety part trust and safety. Barkeep49 (talk) 17:33, 4 October 2023 (UTC)

  Maybe "legal obligation" isn't the best phrasing. But the proposal is about overruling consensus. The WMF doesn't need to overrule consensus in order to protect editors from authoritarian regimes, or to protect editors' privacy, and so forth. Those are all things that consensus exists for. I'm having a hard time imagining a scenario where the WMF would need to act contrary to consensus for some reason other than fulfilling a legal obligation.

  So, for example, if the community decided to allow copywritten images to be uploaded, copyright law be damned, the WMF might step in and say no to that, and I would agree the WMF (as web host) should be allowed to make that decision. But if the WMF oversights something to protect editors' privacy, or globally locks someone they've determined is a bad actor, none of that involves overruling consensus; to the contrary, those are examples of the WMF following consensus. If the WMF enforces the TOU, that's not overruling consensus, that's following consensus, because the TOU (arguably) has consensus.

  To use a real-world analogy, pretty much all modern democracies have a "nobody is above the law" principle enshrined in their laws. There is an exception to this, which is the declaring of martial law, allowing the government to exercise extraordinary police powers in times of emergency -- powers that would otherwise be illegal. But it has to be a real emergency. So I see CONEXCEPT as analogous to that. As written, CONEXCEPT places the WMF "above the law" of consensus. I'd like to see it limited to something akin to "in times of emergency." Maybe "legal obligations" aren't the best words for conveying that. But I'm rather surprised that editors aren't, at least in principle, agreeing that the WMF is not "above the law" of consensus, but should only overrule consensus in emergency cases. Levivich (talk) 17:51, 4 October 2023 (UTC)

  Modern democracies don't use consensus decision making because it scales upwards poorly. On English Wikipedia, almost all major changes are stalemated by its consensus-based decision-making traditions. Organizations generally don't use consensus decision making by its entire membership both due to the scale problem, and because it's more effective to delegate decisions to a smaller group of people, with the membership setting direction. English Wikipedia has additional issues to overcome: truly getting the views of a representative sample of the community, which includes readers as well as editors, is very difficult. For a healthy collaboration, the community needs to engage throughout the objective-setting process to guide the organization on the path it desires. isaacl (talk) 22:22, 5 October 2023 (UTC)

  Actually it's about decisions that cannot be subject to consensus. Sometimes that means overruling consensus. More often it means that consensus can't overrule it. The actions I'm aware of, but NDA'ed from specifically documenting, around editor safety would fall into this second category. Best, Barkeep49 (talk) 08:11, 9 October 2023 (UTC)

  I'd say the job of executing the terms of service is mostly operational. Terms of Service are legally binding (both ways). A user could sue the foundation for NOT upholding them and that definitely would then involve the legal department. The judge would throw you into mediation faster than you can introduce yourself to said judge, but still. A department called 'Legal' doesn't just do things that are 'a legal obligation' of the foundation. For instance enforcing the trademarks is done by the legal department, but not a legal obligation of the foundation. It is an obligation if you want to keep your exclusive rights, but there isn't anything requiring the foundation to perpetually keep a trademark for Wikipedia. If the board tells the Legal department to let go of these trademarks, they can be let go. Executing that is a legal obligation of the employees designated to execute this (by their bosses), under the terms of the job contract and function of the employee.

  "Legally obliged" is probably a pretty narrow scope of the foundation's activities; very broadly stay within your legal purpose as an org, organise the required votes, do proper bookkeeping, fulfil contracts you agreed to and respond to and take action on legal demands with basis in law and you are pretty much done. If you've ever been part of a mostly dormant org or association, you will know that there is very little that is actually required to simply exist. —TheDJ (talk • contribs) 15:25, 4 October 2023 (UTC)

  Risker, I'd be interested to know more about what you see as your second two examples. I don't recall the community ever having reached a consensus that Wikipedia should be insecure or inoperable, the WMF overruling that, and anyone being upset about that, and that's quite the astonishing claim. Seraphimblade ^{Talk to me} 00:25, 6 October 2023 (UTC)

  Hi Seraphimblade. There was a point in time where there was a strong push to make 2FA available to anyone, which got promptly shut down. I don't recall that there was a consensus level, because things moved very quickly to illustrate why it is a bad idea. It is a security issue, it is also a user accessibility issue, and it is mostly an issue that the software was never designed for global use, and it is currently maintained only by volunteers. It was originally designed with the intention of only being used by the small number of developers who had full access to MediaWiki core software, and was subsequently expanded to WMF staff. Many years later, it was made optionally available to all administrators, and is now required for stewards and interface admins. The kicker is that there is no proper support for users who encounter difficulty with the extension. In the earlier days, everyone who had it personally knew someone who could vouch for them in order to get their 2FA reset. Today, not even all admins on all projects can say that. Instead of having a big long discussion or RFC about something like this, it's much more effective to simply say "not gonna happen" right off the bat. (As an aside, I've been reliably informed that this extension is high on the priority list for review and potential redevelopment, which could change this situation.) There are other examples I've seen over the years, all of which were stopped early.

  The most recent widely known and discussed example is the graph extension, with a very significant number of users on multiple projects expressing dismay about its removal. This was also a definite security issue, and was clearly labeled as such; as such, it's a global CONEXEPT situation. Risker (talk) 01:24, 6 October 2023 (UTC)

  As a fresh example, please see Challenging Disinformation in the Wikimedia Ecosystem. This includes a bundle of WMF initiatives including:

  1. Disinformation Response Taskforces focussed on prominent elections or geopolitical events
  2. WikiCred, a project aimed at training media professionals how to use Wikipedia
  3. Knowledge Integrity Risk Observatory

  As these seem to be concerned with content and are based outside individual projects such as this, they seem to have potential to generate conflict when establishing consensus for contentious topics.

  Andrew🐉(talk) 14:31, 3 October 2023 (UTC)

• I wish there was a decent solution to the ongoing problem of conflict between the WMF and the Wikipedia community. I think there's some cultural incompatibility -- the WMF is a traditional hierarchical voluntary sector organisation, while the Wikipedia community's an opinionated anarchy; the WMF's made up of voluntary sector people, who care and want to make a difference to the world, while the Wikipedia community's made up of exhausted people whose patience is constantly tested by playing whack-a-mole with vandals and marketers. We think differently because we live in different worlds. I think this is a conflict that'll come to a head again in future. But I can't see the point in us passing a resolution that the WMF should voluntarily give us its power. They won't do that. If this looks like passing they'll treat it as a PR problem and send someone to give us warm words and start a discussion about how to begin to plan a consultation.—S Marshall T/C 09:07, 3 October 2023 (UTC)

I think you're overestimating how much the WMF would care or react. To me, this change is useful in that it would convey the preferences of the Wikipedia community and would draw more clear-cut lines to establish that if the WMF goes past them they're going it alone, without community support and with the potential for blowback; but I'm under no illusions that the WMF will take this as any more than a suggestion or a community request. I just think it's worth having something like that, because previously the WMF has acted with the assumption that it can do whatever it wants without community protest and that clearly hasn't worked for either party. --Aquillion (talk) 18:20, 3 October 2023 (UTC)

I suspect that this change is useful is more a matter of personal opinion rather than, at least at this stage, a matter of community consensus. It seems unlikely that WMF has an assumption that it can do whatever it wants without community protest but I dare say we could note that protest is probable under some circumstances. If some editors are profoundly dissatisfied with English Wikipedia top-level governance they could fork it like Wikipedia en español did to Enciclopedia Libre Universal en Español. That would demonstrate where community consensus lies better than an RFC. Thincat (talk) 15:40, 4 October 2023 (UTC)

I've found it a bit curious that the WMF is not run as some sort of cooperative. Is this feasible and worthwhile? Shells-shells (talk) 00:05, 6 October 2023 (UTC)

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

Should the precautionary principle be policy?

In my opinion, Wikipedia:Precautionary principle should be policy. On Commons, the PCP has been long standing policy. There is little reason it shouldn't be policy here as well. It would help guide a lot of discussions at WP:FFD for one. — MATRIX! (a good person!)^{[Citation not needed at all; thank you very much!]} 10:45, 27 October 2023 (UTC)

WP:NFCC already says:

it is the duty of users seeking to include or retain content to provide a valid rationale; those seeking to remove or delete it are not required to show that one cannot be created.

And WP:C says:

Images, photographs, video and sound files, like written works, are subject to copyright. Someone holds the copyright unless the work has explicitly been placed in the public domain. Images, video and sound files on the internet need to be licensed directly from the copyright holder or someone able to license on their behalf.

In other words, it already is policy, albeit using slightly different wording. WaggersTALK 12:42, 27 October 2023 (UTC)

@Waggers: It is a bit indirect though. It doesn't directly reject any arguments unlike WP:Precautionary principle. — MATRIX! (a good person!)^{[Citation not needed at all; thank you very much!]} 13:20, 27 October 2023 (UTC)

But none of those are valid arguments under our existing policies. They wouldn't hold any water in a deletion discussion. Perhaps they should be added to WP:AADD but I don't see a need for any policy changes. WaggersTALK 14:06, 27 October 2023 (UTC)

Some of this comes down to a philosophical idea. If you are operating from a generally American context, then you might think of the policies as our equivalent of the Constitution of the United States – all rights enumerated, etc., in a single Yankee Doodle handy dandy location. But if you are operating from a context more in line with the British constitution, then you might see them as less about the written statute, and more about the general principles. The principles hold, regardless of whether there's a single official document that declares the principle to be important. We hold these truths to be self-evident, and also to be so fundamental that we don't need to slap an official stamp of approval on every single different way that we've expressed them. We have no capital-P policy that says editors should Wikipedia:Write encyclopedia articles; this does not mean that we do not value encyclopedia articles or that we are writing news stories instead. In other words, the main idea expressed in Wikipedia:Precautionary principle is already a policy, with a lowercase 'p'. The tag at the top is not the important part. WhatamIdoing (talk) 23:34, 28 October 2023 (UTC)

It is practically redacted as a short essay. There are already policies in Wikipedia that covers this. Regards, Thinker78 (talk) 20:20, 29 October 2023 (UTC)

I don't think this is a good idea. The copyright restrictions we abide here are already much stricter than virtually any site on the Web; I do not think it's necessary, or desirable, or benefits the project, to sit around coming up with new hypothetical ways in which we could make the rules even stricter and make illustrating the encyclopedia more difficult. jp×g🗯️ 21:41, 29 October 2023 (UTC)

• The proposition is mistaken in saying that "Someone holds the copyright unless the work has explicitly been placed in the public domain". It's wrong because copyrights are not perpetual and so expire. This has already happened for numerous historical documents and images and it will happen to everything in due course. There are also many orphan works for which it is impractical or impossible to identify the copyright holder. We should be pragmatic and proportionate rather than draconian and difficult. See also Avoid copyright paranoia. Andrew🐉(talk) 22:21, 3 November 2023 (UTC)

Article subject potentially directing the content of article

I have just been made aware that a press release has been put out by the Women's Rights Party that is written by the founder of the party Jill Ovens complaining about how the Wikipeida article on the party and her is written. Complaining about its content with the content then being replaced or removed in line with the complaints in the press release. Can I please get some help and advice on how best to approach this potentially contentious subject. The article talk page is also full of parroting of the press release complaints and legal threats being thrown around like 'defamatory' for including the complained about content.

• Press release by Womens Rights Party
• Jill Ovens
• Women's Rights Party
• Talk:Women's Rights Party
• Edit contributions for single IP address making favourable changes to Jill Ovens Page

PicturePerfect666 (talk) 19:07, 31 October 2023 (UTC)

I'm as ignorant about sexual issues as one can be, but I hesitate to call anybody a name, any name, including transphobic, unless I have a reliable source (and maybe two or three sources) explicitly calling them that name. Instead, why not quote the following description of the Women's Rights Party and Jill Ovens from your Mathew Scott reference: "The [Women's Rights] party platform is mostly based around upholding binary views of sex and gender, preventing trans women from accessing female spaces and resisting language that portrays gender and sex as a continuum." If that quote about the platform of the Women's Rights Party and Jill Ovens is sustained by reliable sources, the quote is far more explanatory than is the word "transphobic."

Regarding the criticism of Wikipedia, I take it as a compliment to the importance of Wikipedia. Smallchief (talk) 20:05, 31 October 2023 (UTC)

+ North8000 (talk) 20:09, 31 October 2023 (UTC)

Agree DFlhb (talk) 20:45, 31 October 2023 (UTC)

Agree. FOARP (talk) 17:07, 7 November 2023 (UTC)

My two cents is that, with regard to the content, Smallchief is right. If sources don't use the word transphobic, even if the stances fit your own definition of transphobic, you can't use the specific word (and FTR I agree that the party is transphobic personally, I just can't find a source that says so).

With regard to the off-wiki campaigning that may or may not be going on, you may consider WP:RPP and failing that, escalating to AN/I if the behaviour reaches disruptive/edit war levels. For now, I'll slap a COI template on the TPs of the IP, WP:LEGAL for the guy who shouted defamation, and maybe a template on top of the article talk page as well. Fermiboson (talk) 20:32, 31 October 2023 (UTC)

To the end claimed parties described as racist and fascist aren't typically expressly called that in sources yet Wikipedia calls them what they are. The statements are dogwhistles of transphobia 101 and should be recognised as such. The whole platform is transphobic...dedicated to the removal of trans rights and uses the language of that. No rasict is going to say they want specific things out loud they go at in couched language and inflame with common tropes of 'protecting children' and allusions to a threat to society from a certain group. This is not a place for not being honest about these parties. rthe party also being founded in support of a woman who wants to eliminate trans people also adds significant weight to it being transphobic. Just more explanation here.

This information is all contained in this 'manifesto' PicturePerfect666 (talk) 20:42, 31 October 2023 (UTC)

Again, for the record there is no need to direct the virtrol towards me because I agree wih you. However, parties described as racist and fascist definitely have a source behind them - and if they don't, rest assured the RfCs will come at you like hell. WP:SYNTH is pretty clear on this. We can, however, definitely say "upholding a gender binary, preventing transgender women from accessing safe spaces..." etc, which is just the WP:V way of saying transphobic. Fermiboson (talk) 20:48, 31 October 2023 (UTC)

What vitriol are you talking about? There is none in anything written. It is a description of the party and its positions. Not sure what you are on about with claims of 'no need to direct the virtrol towards me because I agree wih[sic] you.' PicturePerfect666 (talk) 20:52, 31 October 2023 (UTC)

Oh, also be careful about WP:1RR. No point in getting sanctioned for fighting dirty. Fermiboson (talk) 20:50, 31 October 2023 (UTC)

I share your frustration, but it is not for us to decode the dog whistles ourselves. Look for Reliable Sources that do the decoding for us. If we don't have an RS saying "transphobic" then the word should be removed until we do. Don't worry. Anybody with an ounce of sense can see that it is transphobic from the rest of the article's content whether we use the word or not.

As regards the Press Release: Just ignore it. Lots of people don't like what is written about them on Wikipedia. So long as what we say is true, and proportionate to their notability, then that is not something they get a veto over.

As regards legal threats, WP:NLT applies. People who make legal threats and don't withdraw them when the policy is drawn to their attention get blocked. DanielRigal (talk) 20:56, 31 October 2023 (UTC)

Do we use the word "transphobic" to describe something that's transphobic? Of course we do. (Disclaimer: I saw this discussion off-wiki.) LilianaUwU ^{(talk / contributions)} 20:48, 31 October 2023 (UTC)

I agree 100% call things what they are. Wikipedia is not a place for using wording to avoid saying the obvious. That is not synthesis. Starting a party in support of a parroting a transphobe (who has saluting Nazis at an event in Melbourne show up), who wants to eliminate trans people is also not synthesis to say the obvious. PicturePerfect666 (talk) 20:58, 31 October 2023 (UTC)

Dare I say the sky is blue? LilianaUwU ^{(talk / contributions)} 21:00, 31 October 2023 (UTC)

Considering the contentiousness of the topic, there must have been a past RfC on a similar descriptor of TERFs as transphobic hidden in some talk page. Fermiboson (talk) 21:02, 31 October 2023 (UTC)

Do we use the word "transphobic" to describe something that's transphobic? Per MOS:LABEL, transphobic is included with similar labels that are best avoided unless widely used in reliable sources, and then only using in-text attribution.--Trystan (talk) 23:02, 31 October 2023 (UTC)

Here is a source that uses the word transphobic to describe the activist that the party was apparently founded around (which, btw, is sourced to substack which is WP:BLOG un-RS, so that's another thing to fix). I couldn't find a source that refers to the party itself. Fermiboson (talk) 20:58, 31 October 2023 (UTC)

• There is a discussion on the article's talk page, though it was just started quite recently. Input would be appreciated there. I'm going to remind everyone commenting that WP:BLP applies everywhere on Wikipedia, so if you're going to start calling people names on here it will be noted in your block log. Ivanvector (^Talk/_Edits) 21:05, 31 October 2023 (UTC)

  Hold on. There is a point I think we've all missed here in the heat of the moment - is the subject even notable? Newsroom source is in list form so is kind of borderline passing mention. The party receives virtually no support in polls and no votes, and everything else is either self-published or a primary source. Fermiboson (talk) 21:10, 31 October 2023 (UTC)

  Google search of "women's rights party" with quotations gives the party's website and several unrelated foreign or historical organisations, but no RS coverage. Fermiboson (talk) 21:12, 31 October 2023 (UTC)

  Then I think in that point a deletion discussion is needed. PicturePerfect666 (talk) 21:12, 31 October 2023 (UTC)

  Yeah, I'm going to go ahead and start one. Fermiboson (talk) 21:15, 31 October 2023 (UTC)

  I think the party and the person should be nominated together neither appear to have general notability. PicturePerfect666 (talk) 21:16, 31 October 2023 (UTC)

  The person is a more borderline case, since she appears to be a former MP and the NZ Herald counts towards GNG. Fermiboson (talk) 21:20, 31 October 2023 (UTC)

  If she was an MP, then it's not even borderline -- she meets WP:NPOL. -- Nat Gertler (talk) 22:15, 31 October 2023 (UTC)

  As far as I can see stood a few times and never got elected…perennial/nuisance candidate at best. PicturePerfect666 (talk) 00:34, 1 November 2023 (UTC)

  I can't figure out what the NZ parliamentary source on her is supposed to be. Did she just speak in parliament or something? Fermiboson (talk) 00:42, 1 November 2023 (UTC)

  She responded to a public consultation because she was desperately trying to keep lgbt+ conversion therapy AKA torture and pseudoscience legal in NZ PicturePerfect666 (talk) 00:49, 1 November 2023 (UTC)

   Courtesy link: Wikipedia:Articles for deletion/Jill Ovens. Folly Mox (talk) 03:16, 2 November 2023 (UTC)

RfC on the "Airlines and destinations" tables in airport articles

The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion. A summary of the conclusions reached follows.

After reviewing the !votes and discussion, it is clear that there is consensus that airlines and destination tables may only be included in articles when independent, reliable, secondary sources demonstrate they meet WP:DUE. There is not a consensus for wholesale removal of such tables, but tables without independent, reliable, secondary sourcing, and where such sourcing cannot be found, should not be in the articles.

This is one of the rare cases with an RFC where, numerically, the responses are close, but arguments strongly grounded in established policy make a consensus clear. Wikipedia:Closing discussions says The closer is not to be a judge of the issue, but rather of the argument. In this discussion we have many !voters responding with strong policy-based rationales, and many responding with personal opinion. Additionally reading more than just the bolded yes or no, there is a common thread found in responses supporting and opposing the tables, as well as non-bolded and other !votes. That thread is articles should include such tables when including a table would be due... all the usual guidelines relating to weight and reliable referencing (I'm thinking specifically of WP:BURDEN and WP:ONUS) should still be considered... tables are fine if they are based in secondary sources... WP:V, WP:RS and WP:NPOV can cover relevant concerns... If it is unmaintained / not well sourced - it should be either repaired or deleted just like every other wikipedia article. This common thread, as well as the strength of arguments leads me to read consensus against the plurality of bolded !votes.

Addressing the arguments, the strongest and by far most common argument put forth by those opposed to the tables is WP:NOTALLSORTSOFSTUFF. WP:NOT is policy, and the strength of the arguments citing it are recognized by those supporting inclusion of the tables. There were also no strong arguments against the interpretation of WP:NOT, other than disagreement that it should apply. Merely stating that something is encyclopedic without elaborating how it does not fall foul of existing policy is not a strong counter-argument. A counter-argument saying that WP:V is a counter to WP:NOT, for instance, is weakened by the text of both policies, with WP:V linking specifically to WP:NOT and saying While information must be verifiable for inclusion in an article, not all verifiable information must be included. Another argument for excluding the tables was the editorial overhead of maintaining them, but this was significantly less widely cited and lacks the solid policy basis of WP:NOT arguments.

Many of those supporting provided weak arguments, with several essentially rooted in WP:ILIKEIT. Merely asserting that the information is useful or helpful doesn't demonstrate that it is encyclopedic. There were also several with reasoning that did not address and were strongly rebutted by the policy based arguments of those opposed to inclusion. There were also arguments that the tables provide an idea of how well served or active an airport is, but those arguments were weakened by pointing out that the context could be provided in prose. ScottishFinnishRadish (talk) 20:14, 18 November 2023 (UTC)

---

Should airport articles include tables that display all the airlines that serve the airport and the cities they fly to? Sunnya343 (talk) 16:05, 30 September 2023 (UTC)

I wanted to clarify that the central question is whether airport articles should mention every single flight that the airport offers (no matter the way that the information is presented). I said "tables" specifically because that's the format currently used by all of the articles. Sunnya343 (talk) 23:39, 30 September 2023 (UTC)

Virtually all airport articles contain tables showing all the cities that passenger airlines fly to. Some articles also have tables for cargo destinations. Here are a few examples: Tehran-Mehrabad, London-Heathrow, New York, Jakarta. In 2017, we had two RfCs at WikiProject Airports on this topic: one that determined we should keep the tables, and one on how to reference them. However, I am concerned the results of those RfCs may be cases of WP:CONLEVEL. I think it would be useful to hear more opinions from the wider Wikipedia community. Sunnya343 (talk) 16:07, 30 September 2023 (UTC)

Notices placed at WikiProject Airports, WikiProject Aviation, and the talk pages of editors who participated in the two RfCs above and the following discussions on lists of airline destinations: 2018 RfC and 2023 AfD.

• No. An article should certainly discuss an airport's current operations, but the listing of every single flight that is running as of today's date is inappropriate for this encyclopedia. Airlines frequently make changes to their schedules, and Wikipedia is not meant to be a news service that documents all of these changes. I also consider the lists indiscriminate; in the overall history of an airport, there is no reason why today's particular list of destinations is more noteworthy than the one from last month or two months ago. Few to no independent sources exist for most of the routes, demonstrating that they are not significant enough to merit inclusion in an article. The references that do exist generally are just covering the recent inauguration or upcoming termination of the flight - one of those frequent changes to airline schedules. Sunnya343 (talk) 15:00, 7 October 2023 (UTC)

  (I wanted to present a more clear argument above based on policies. The following is my original comment, where I describe the impractical nature of attempting to maintain and reference up-to-date lists of destinations.) I'd say there are three general categories of sources for the tables:

  1. Secondary Independent sources - Only exist for a small fraction of routes.
  2. Booking engines or flight schedules on airline websites - These require you to input the origin, destination, and a random date to see if the airline flies between the two cities. For routes listed as seasonal, I suppose you'd have to search for flights on random dates in different months.
  3. Flight-tracking websites - FlightRadar24 will show you a map of routes from an airport (example). You have to click on each destination to see which airlines fly to it.
  I have not encountered another type of Wikipedia article that includes sources like #2 and #3 above - databases that you have to navigate to verify each destination. I don't know if they are considered acceptable references.

  When an airline announces a new destination, editors will add it to the list with a reference. However, once the new flight begins, that reference is often removed (probably to avoid citation clutter). Still, what this means is that timetable references in the right-most column (see the New York-JFK article) are taking precedence over what may have been secondary third-party sources supporting individual destinations. I've also noticed that the timetable sources usually have access-dates going back several years, even though editors continue to update the lists. So there is a discrepancy. Maybe I'm nitpicking, but theoretically, every time you make a change to the list, you should go through the timetable and verify every other destination, and then change the access-date...

  Ultimately, I believe the fact that there are no secondary independent sources for most of these destinations demonstrates that listing all of them isn't encyclopedic. Primary Non-independent sources are certainly allowed, but I don't think it's OK for large portions of an article to rely on them exclusively. It may be appropriate to replace the tables with a few paragraphs that summarize the airport's operations, supported primarily by secondary third-party sources. Below is a rough draft for the Indianapolis airport article.

Idea
As of September 2023, the Indianapolis airport is served by ten passenger airlines. Allegiant Air maintains a base at the airport. International air service includes routes to Cancun and Toronto. Indianapolis is also a hub for the cargo carrier FedEx Express. In 2022, the airport handled 8.7 million passengers and 1.3 million tons of cargo. References

Sunnya343 (talk) 16:19, 30 September 2023 (UTC)

I agree in general but in my experience almost all routes will have secondary sources especially international ones. For example I bet I can find coverage for every single route out of Taoyuan International Airport. Horse Eye's Back (talk) 16:22, 30 September 2023 (UTC)

I've personally found those tables to be useful and feel it would be a waste to have them deleted. Wehwalt (talk) 16:36, 30 September 2023 (UTC)

Is that what I'm agreeing with? My understanding is that Sunnya343 is opposed to the whole RfC in general hence why they voted "oppose" instead of yes or no. Horse Eye's Back (talk) 17:17, 30 September 2023 (UTC)

I'm simply making my point without !voting. If you like I will outdent. Wehwalt (talk) 17:20, 30 September 2023 (UTC)

My apologies, I thought it was a direct response to me. Re-reading @Sunnya343:'s post their meaning does actually appear ambiguous and I'd like some clarification on that, so this was helpful for me regardless of whether it was intended. Horse Eye's Back (talk) 17:32, 30 September 2023 (UTC)

Sorry for the confusion, I'll change it to "No" (as in no, I don't think the tables should be included). Sunnya343 (talk) 17:37, 30 September 2023 (UTC)

Thank you, I did misunderstand a bit what you were saying but I still don't think we're actually that far apart position wise... 45% and 55% are close despite one being a yes and one being a no. Horse Eye's Back (talk) 17:42, 30 September 2023 (UTC)

@Horse Eye's Back: Even if you were able to find independent sources for each of the routes, the table would look like it does below, for each airline. I would argue that the bigger question is, do we need to mention every single destination.

Airlines	Destinations
China Airlines	Amsterdam, Auckland, Bangkok–Suvarnabhumi, Beijing–Capital, Brisbane, Busan, Cebu, Chengdu–Tianfu, Chiang Mai, Da Nang, Denpasar, Frankfurt, Fukuoka, Guangzhou, Hanoi, Hiroshima, Ho Chi Minh City, Hong Kong, Jakarta–Soekarno-Hatta, Kagoshima, Koror, Kuala Lumpur–International

Sunnya343 (talk) 01:23, 1 October 2023 (UTC)

@Sunnya343, the sources you list in your example are almost all WP:PRIMARYNEWS sources. Did you mean that you wanted Wikipedia:Independent sources? Wikipedia:Secondary does not mean independent. I'd also add that Wikipedia:Secondary does not mean good. Wikipedia requires 100% use of reliable sources, not 100% use of secondary ones or 100% use of independent ones. WhatamIdoing (talk) 22:54, 30 September 2023 (UTC)

Oh, I didn't realize those were primary sources. I would say then that the "Airlines and destinations" section should be based mainly on reliable independent sources. Sunnya343 (talk) 23:25, 30 September 2023 (UTC)

In my (US-focused) experience, every single time an airline adds a new destination (or a new airline), it's reported in the newspaper(s) for the airport's area. I therefore expect that it would be possible to provide a citation to an independent source for every destination (at least for a US airport). But – is it actually better? I'm not sure about that. WhatamIdoing (talk) 01:55, 1 October 2023 (UTC)

I agree with you about certain destinations, such as a new flight to a foreign city. But if we take the Indianapolis airport as an example, you'd be hard-pressed to find third-party sources for the more mundane domestic routes, e.g. American Airlines' flights to Charlotte and Phoenix. I think you have a point about newspaper articles and other independent sources perhaps not being better than non-independent sources in this context, where we only seek to reference the cities an airline flies to. What I'm arguing is that the lack of independent sources for many of the destinations is an indication that it is not notable to mention each and every one in an article. Sunnya343 (talk) 02:53, 1 October 2023 (UTC)

You will often find coverage of mundane domestic routes (even legacy ones), especially around mundane incidents. Here is Indianapolis to Charlotte[13] for example. I would also note that all of these routes were non-mundane once and almost certainly received coverage in the local paper when they launched even if that was in the 70s and it will be harder to find. Horse Eye's Back (talk) 14:38, 1 October 2023 (UTC)

If you can find reliable secondary coverage for each what would be the policy grounded basis for not including some of them? Horse Eye's Back (talk) 14:32, 1 October 2023 (UTC)

(Responding to your two comments above) You have a point. But I would say, compare your source on the Indianapolis-Charlotte route to this one that describes the airport's first transatlantic flight. Your source is not focused on the Charlotte route itself. I think this excerpt from the essay WP:TMI would apply: Advocates of adding a lot of details may argue that all of these details are reliably sourced. Even though the details may be reliably sourced, one must not lose sight of the need for balance. I'd also argue that per WP:NOTNEWS, we do not need to cover the launch of every single flight from an airport. Sunnya343 (talk) 15:19, 1 October 2023 (UTC)

Which of the four points of NOTNEWS would that be per? Horse Eye's Back (talk) 15:22, 1 October 2023 (UTC)

I'm referring to #2, in particular: While news coverage can be useful source material for encyclopedic topics, most newsworthy events do not qualify for inclusion and Wikipedia is not written in news style. You'll notice for example that in this table, the launch, resumption, and termination of various routes is mentioned. Sunnya343 (talk) 15:47, 1 October 2023 (UTC)

That part of 2 is about inclusion of articles on Wikipedia, that is WP:NOTABILITY not about what to include in articles. The only part of 2 which is not about notability is "Also, while including information on recent developments is sometimes appropriate, breaking news should not be emphasized or otherwise treated differently from other information." which does not support your argument that it be treated differently. Horse Eye's Back (talk) 15:51, 1 October 2023 (UTC)

I see your point. What I will say is that I'm focusing on the general notion of what sort of information belongs in the encyclopedia. The paragraph at the beginning of the section (WP:NOTEVERYTHING), especially the sentence A Wikipedia article should not be a complete exposition of all possible details, but a summary of accepted knowledge regarding its subject, addresses both the creation of articles on different subjects and the content of those articles. Do you really believe we ought to mention that Delta Air Lines is resuming flights from Indianapolis to Salt Lake City, or that Korean Air is ending service from Seoul to Tashkent? Sunnya343 (talk) 17:34, 1 October 2023 (UTC)

I struck the words above based on this excerpt from WP:N: [These guidelines on notability] do not limit the content of an article or list... For Wikipedia's policies regarding content, see Neutral point of view, Verifiability, No original research, What Wikipedia is not,... Sunnya343 (talk) 23:01, 2 October 2023 (UTC)

• Yes, airport articles should include such tables when including a table would be due (closed airports don't need to have an empty table for example). A table should not preclude prose coverage of routes nor should prose coverage of routes preclude a table, there is room for both and both are often due. Horse Eye's Back (talk) 17:39, 30 September 2023 (UTC)
• No comment there should not be WP:CREEP on this fairly minor point of discussion; as HEB noted above, prose coverage does not preclude tables and vice versa. Of course, all the usual guidelines relating to weight and reliable referencing (I'm thinking specifically of WP:BURDEN and WP:ONUS) should still be considered, but there is no need to prescribe a "yes" or "no" answer to this question. ~~ AirshipJungleman29 (talk) 17:48, 30 September 2023 (UTC)
• The tables are fine if they are based in secondary sources rather than original research using booking systems and the like. --Guerillero ^{Parlez Moi} 18:27, 30 September 2023 (UTC)
• No, but I'm willing to be convinced otherwise. My feeling is that this is both a) sometimes impractical, b) hard to source reliably, and c) verging on a WP:NOTGUIDE violation, which is the main reason for my opposition. Edward-Woodrow • talk 19:03, 30 September 2023 (UTC)
• Partial A list of airlines that routinely serve the airport makes sense, but the list of cities probably does not since this is a function of the airline, not the airport, and can change regularly. That said, outside of table, one can describe in prose the general profile of cities that it serves - I can see this for small regional airports to say what cities that they link to. But this should be by the airport in general, and not because Airline X goes to one place and Airline Y goes to another. --Masem (t) 19:45, 30 September 2023 (UTC)

  Let me add another notch against city listings. We're supposed to be writing content as an encyclopedia that will stand the test of time, not what is just currently the situation. A list of airlines that an airport serves will not routinely change, and if there are major departures, that will likely be a discussion in prose. But for the most part, the cities that each airline services changes year-to-year if not more frequent, so it is not very useful information in the long-term. The only arguments that are being given to keep those cities are from a WP:NOT#GUIDE standpoint. Masem (t) 03:45, 1 October 2023 (UTC)

• No, per WP:INDISCRIMINATE, WP:NOTTRAVEL, and WP:OR. First, these lists relying almost without exception on WP:OR; entries are typically unsourced, and when they are sourced the reference is usually something like this. Second, they are indiscriminate and are are not put in context with explanations referenced to independent sources as required by WP:INDISCRIMINATE; they are just lists of where an individual can travel to and on which carrier. This brings us to WP:NOTTRAVEL; these lists are travel guides, telling people how to get from a to b, and not content that belongs on an encyclopedia.

This isn't to say that we can't include information on the airlines and destinations at an airport; to provide information that is actually beneficial to our reader and complies with our policies we can use the section to discuss how the number of airlines operating from an airport changed over time, as well as the number of destinations. For example, using prose we could show how Heathrow went from a small airfield to a global hub, including covering the impact of events like the pandemic, all of which is encyclopedic content and none of which can be done with tables. BilledMammal (talk) 20:05, 30 September 2023 (UTC)

• Yes - this is one of the key aspects of airports, namely what connections to other airports they have. If the info is only embedded in prose, the risk of outdated creep increases. --Soman (talk) 20:35, 30 September 2023 (UTC)

  @Espresso Addict, Kusma, Soman, and Reywas92: (Replying to you all at once because I feel your arguments are similar) The same could be said of airlines - that we should have a list of the cities they currently serve because it's a key aspect of them. But there is consensus not to mantain lists of airline destinations on Wikipedia. I don't see how we can disapprove of full lists of airline destinations, and at the same time allow complete lists of each airline's destinations from an airport. Sunnya343 (talk) 22:38, 1 October 2023 (UTC)

  It seems to work and not cause any problems. Airline destination lists were also separate articles. It is perfectly acceptable to have rules that allow content in one form but not in a different one. —Kusma (talk) 05:19, 2 October 2023 (UTC)

• Generally yes per Horse Eye Black and Soman. Obviously everything must be verifiable, and in some cases it will be better covered on a separate article to the main airport article. In some cases there should be a history of notable carriers and destinations as the goal is an encyclopaedic coverage of the airport and its history rather than a contemporary travel guide. However the current services are an encyclopaedic aspect of the airport. Thryduulf (talk) 21:04, 30 September 2023 (UTC)

  @Thryduulf: When you say "in some cases it will be better covered on a separate article to the main airport article", where else do you believe the information should go?

  One could also argue that the current destinations of an airline are encyclopedic; however, the consensus of this RfC (reaffirmed by this AfD) was that Wikipedia should not have complete lists of airline destinations. I agree with Beeblebrox when they say, There is an important distinction between information and knowledge. Wikipedia strives to provide knowledge, and is explicitly not a directory or catalog, which is just information. Sunnya343 (talk) 14:51, 1 October 2023 (UTC)

  where else do you believe the information should go? it depends how information about the airport is covered, and how much information there is. For example a major airport that has a long history and lots of detail may need spin-off articles per WP:SUMMARY and the list of destinations may be better in (or indeed as) one of them, in other cases it may be better to have an "Air travel in X" article covering multiple airports. Basically, being overly prescriptive could cause problems.

  Whether airlines do or should have complete destination lists is not relevant to coverage of airports. I'm sorry I didn't comment in that RFC, but as should have been easily predictable based on other contemporary discussions the consensus is being over-applied to excise encyclopaedic related content. Thryduulf (talk) 15:16, 1 October 2023 (UTC)

• No per WP:NOTGUIDE and WP:NOTDB. These are things that change all the time. There are websites which do an admirable job of tracking all this stuff. Our job is to be an encyclopedia, not a airline database. RoySmith (talk) 21:17, 30 September 2023 (UTC)
• I feel these tables semi-duplicate list of airline destinations, something long described as WP:NOT. Also if no other sources are describing this information, beyond primary sources, then are they WP:DUE. If they are going to be included they need to be properly referenced with something better than a ticket system that needs to work through to see if the route is currently nrunning or not. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 21:28, 30 September 2023 (UTC)
• Yes, generally this is relevant and encyclopedic information, and it should be included if you can source it (including to the airport's own website, which is reliable despite not being independent). I arrived at this general conclusion by thinking about how important it is to understanding the subject of the article (i.e., the airport). If you want to understand the airport in context, you need to know some basic, objective/universal facts. These include: Is there scheduled passenger service at all? How many passengers use this airport? How many airports does it connect to? Are those connected airports nearby, or does it have long-distance/international flights? There is a big difference between "one daily flight to the next city" and "direct flights from ten countries", and providing the lists makes it easy to see whatever level of granularity the reader is interested in (e.g., how many destinations, how many countries, whether they're all short flights, etc.). Similarly, you can't understand an airport unless you understand whether one airline holds a monopoly there. On the other hand, does it need to be presented in the exact form of a table? Meh, I don't think that matters. A table is a perfectly fine form for this, if there are more than about three airlines or destinations to be presented, but a bulleted list is also fine, and if the list is very small, then plain old prose text is good, too. WhatamIdoing (talk) 22:40, 30 September 2023 (UTC)

  Is there scheduled passenger service at all? How many passengers use this airport? How many airports does it connect to? Are those connected airports nearby, or does it have long-distance/international flights? These questions are all better answered with prose; take Heathrow Airport#Airlines and destinations for an example. It doesn't answer the question "How many passengers use this airport", and while theory it could provide answer to the questions of "How many airports does it connect to" and "Are those connected airports nearby, or does it have long-distance/international flights", in practice it does not - we can't expect our readers to count the airports listed, and nor can we expect them to carefully analyze which airports the flights go to to assess what types of flights that leave the airport. It does answer the question "Is there scheduled passenger service at all", but it would be hard to include information on the airlines and destinations serviced by the airport without doing so.

  What would be better for the reader is to say something like In 2022, 35,000,000 people used the airport, with flights to 200 airports in 90 countries. On the average day 120 flights departed; 40% of the flights were shorthaul, 20% were medium haul, 30% were long haul, and 10% were ultra-long haul. British airways accounted for 60% of all flights. - and that's just what I threw together in 30 seconds. An editor working to improve the article could provide far more benefit to the reader than that. BilledMammal (talk) 00:34, 1 October 2023 (UTC)

  I would expect some of these questions to be answered elsewhere in the article, e.g., in Heathrow Airport#Air traffic and statistics, which begins with a description of its passenger traffic. (Note that you have quoted from a list of "some basic, objective/universal facts" that IMO readers need to know to understand the subject, and not from a list of things that I think belongs specifically in a list of destinations served.)

  Statements like "40% of the flights were shorthaul" and "British airways accounted for 60% of all flights" are good, but not necessarily what the reader wants to know, especially if the flight pattern is weird ("40% are shorthaul, and none of them go to the neighboring region that the governor is touting in his plan for promoting business in your state"). I think that a both/and approach would be better than an either/or approach. WhatamIdoing (talk) 01:48, 1 October 2023 (UTC)

• Yes. The tables give a clear view of many encyclopedic aspects of airports, in particular their connectivity, that would be unacceptably vague if relegated to a prose "description." While some of the data may be sourced from databases, it is definitely verifiable, and no one seems to be suggesting that it cannot be kept accurate. CapitalSasha ~ talk 22:46, 30 September 2023 (UTC)

  @CapitalSasha: Here's an example of (what I consider to be) the difficulties of using databases as references. This is an excerpt from the table in the Los Angeles airport article:

  Airlines	Destinations	Refs
  Delta Air Lines	Atlanta, Auckland (begins October 28, 2023), Austin, Boston, Cancún, Cincinnati, Dallas/Fort Worth, Dallas–Love

  When the flight to Auckland begins, should I remove the reference attached to it, since the timetable is already cited in the "References" column? But on what grounds can I remove a valid reference? If I leave it there, then I don't see what's stopping an editor from adding references to all the other destinations:

Airlines	Destinations	Refs
Delta Air Lines	Atlanta, Auckland, Austin, Boston, Cancún, Cincinnati, Dallas/Fort Worth, Dallas–Love

An example of the above can be seen in the Flydubai row of the Dubai airport table.

Sources

Sunnya343 (talk) 22:27, 1 October 2023 (UTC)

@Sunnya343: What's the problem with just using the timetable when the Auckland flight starts? CapitalSasha ~ talk 22:50, 1 October 2023 (UTC)

I suppose it would be OK. But pretty much all articles on Wikipedia include information that is supported by more than one reference. I can't think of any other place in this encyclopedia where you can remove one of two references - and in this case, what would the justification be, to make the table look better? Sunnya343 (talk) 23:11, 1 October 2023 (UTC)

It seems to me that if a reference is really redundant or out of date then there is no issue with removing it.... CapitalSasha ~ talk 23:22, 1 October 2023 (UTC)

I agree with you. But by removing those references, we are prioritizing the timetables over third-party sources. It's true that the timetables are only being used to support basic facts, but articles are supposed to be based on independent sources. And as WhatamIdoing pointed out, both the timetables and the newspaper articles describing new routes are all primary sources, and I don't believe we should be including such large amounts of information supported only by primary sources.

Another issue is that the timetable reference above has an access-date of April 7, 2018. But we just included a destination that began after that date. So I guess I have to check all the other destinations in the timetable, make sure Delta still flies to them, and change the access-date. Who is really going to do this, and is this how a Wikipedia article should be? This might seem like a minor critique, but I believe it helps shows the problem with having these tables and trying to keep them up-to-date. Sunnya343 (talk) 00:32, 2 October 2023 (UTC)

To be clear, a newspaper article describing a new route is not a primary source. For example, this recent local news piece about new international routes is a secondary source. Primary sources may be the airport's press release and the airline's press release. But there's nothing wrong with using the non-independent sources - while an article as a whole needs secondary sources for notability and some interpretations, to suggest they can't be used for this type of section is simply false. If anything, these could be more accurate than a secondary source because it's straight from the horse's mouth. We sometimes avoid WP:PRIMARY sources because they may require WP writers' original research to interpret or summarize, but none of what's cautioned about there is happening for this, or even a timetable. Things change and may not always be perfectly up-to-date, but so what? This is a wiki, and there are a lot of interested users who actually seem to be doing a pretty good job on these to stay current, there aren't daily changes on most pages. Everything is still perfectly verifiable, even if the accessdate in the reference is old. Reywas92^Talk 01:38, 2 October 2023 (UTC)

@Reywas92, I think you will want to read WP:PRIMARYNEWS and WP:LINKSINACHAIN. A newspaper article that repeats someone else's information, without adding its own analysis, means the newspaper article is still a primary source. As the article Secondary source puts it, "Secondary sources involve generalization, analysis, interpretation, or evaluation of the original information." It's not enough to merely be the second link in a chain.

Having said that, I agree with you that this kind of basic information isn't really what we need either a secondary or an independent source for. WhatamIdoing (talk) 02:23, 2 October 2023 (UTC)

• Sort of. I don't see why it's needful to have a complete list, but to me, it seems appropriate and encyclopaedic to provide some indication of which areas an airport serves.—S Marshall T/C 23:05, 30 September 2023 (UTC)
• Yes, this information is encyclopedic and as WhatamIdoing writes very important to understanding the nature of the airport. Sourcing to the airport website is sufficiently reliable. Agree that the list need not be exhaustive and need not necessarily be tabulated. Espresso Addict (talk) 23:29, 30 September 2023 (UTC)
• No the fact that these are not easily found and sourced to independent or secondary sources demonstrates that as a general rule they are run afoul of DIRECTORY and NOTGUIDE. Der Wohltemperierte Fuchs ^talk 02:08, 1 October 2023 (UTC)

  @David Fuchs: is that a fact? It doesn't appear to be true so it doesn't seem like it could possibly be factual. The vast majority of these are easily sourced to secondary independent sources, on what basis do you draw your unique conclusion? Horse Eye's Back (talk) 14:44, 1 October 2023 (UTC)

• Allow destination lists. They are central to what airports do, and generally well maintained and up to date. Old Britannicas feature this type of information about seaports, so there is some precedent for calling it "encyclopedic". We also don't have to delete information only because it is useful to have. —Kusma (talk) 02:12, 1 October 2023 (UTC)
• Allow, again This is getting tiresome, already recently at Wikipedia:Village_pump_(policy)/Archive_167#RfC:_Ariport_destination_tables and Wikipedia_talk:WikiProject_Airports/Archive_19#RFC_on_Maps_and_Airline_&_Destination_Tables. That an airport is a gateway to numerous destinations –and which airports – is obviously highly relevant to the airport, and it is perfectly acceptable and informative to include this content in the articles. It is risible to say this is indiscriminate or original research to include information that is easily verified in airline timetables and other sites. I have yet to see an example of users fighting over someone making up routes because there are in fact ways to look this up. These are not travel guides because they are not instructions, unencyclopedic details, or a guide at all! — Preceding unsigned comment added by Reywas92 (talk • contribs) 03:27, 1 October 2023 (UTC)

  Just because data is easily available doesn't mean it isn't indiscriminate - although based on the sparsity of sources at Heathrow Airport#Airlines and destinations I'm not convinced it is easily accessible.

  That an airport is a gateway to numerous destinations –and which airports – is obviously highly relevant to the airport, and it is perfectly acceptable and informative to include this content in the articles. Why are the specific airports that Heathrow is a gateway to highly relevant? As an experiment, I tried to find sources that discuss that the connection between Zakynthos International Airport and Heathrow Airport; Google news returns nothing, and while Google books returns a few dozen sources that mention both none of them even mention a connection between the two. Similarly, Google scholar returns five sources, but again there is no mention of a connection.

  If reliable sources don't consider this relevant, why should we?

  Based on this, I also support this proposal on the grounds of WP:BALASP; we are giving undue weight to an aspect of the topic that reliable sources give no weight to. BilledMammal (talk) 03:49, 1 October 2023 (UTC)

  While there's not always in-depth coverage of individual routes – though the introduction or cancelletion of routes are often covered in travel media (and it's disingenuous to search academic article) – that's downright false to say sources "give no weight to" an airport's destinations. Some for Heathrow include [14][15][16][17][18][19][20][21][22]. That's just risible to say no one cares about the entire point of an airport – getting to specific other places. How can this possibly be indiscriminate? Simple inclusion standard: Can you fly from one airport to another? There's no unrelated overlapping criteria, subjectivity, or excessive number of items for this objective, narrowly defined, and finite concept. Reywas92^Talk 23:57, 1 October 2023 (UTC)

  Websites like flightsfrom.com, directline-flights.co.uk, and the blog London Air Travel are not the type of source we should be using on Wikipedia. Sunnya343 (talk) 00:33, 5 October 2023 (UTC)

  it's disingenuous to search academic article Why? In any case, I searched academic articles, news articles, and books.

  While there's not always in-depth coverage of individual routes ... that's downright false to say sources "give no weight to" an airport's destinations You've constructed a bit of a strawman here; you argued that the specific airports that an airport is a "gateway" to are highly relevant. I demonstrated that they weren't, by providing an example of a pairing - picked at random - that sources give no weight to. I'm not sure how you can claim that my comment is "downright false".

  How can this possibly be indiscriminate? Indiscriminate; done without careful judgement. Including every route, regardless of whether sources consider that route relevant or irrelevant, is done without careful judgement. BilledMammal (talk) 23:04, 11 October 2023 (UTC)

  When I go to the airport, there's a big board with all the flights and destinations – that's what the purpose of the place is and what people are often interested in when they come to these articles. Is going after London_King's_Cross_railway_station#Services and Union_Station_(Los_Angeles)#Services next? I don't think Google Scholar talks much about Amtrak's Texas Eagle... Is the real complaint just that air routes aren't as permanent as train tracks so some change more frequently? Reywas92^Talk 00:30, 2 October 2023 (UTC)

  that's what the purpose of the place is and what people are often interested in when they come to these articles. And I still don't understand why we would want to have a manually updated, single-point-in-time snapshot, of what services are offered (contrary to WP:NOTDIRECTORY, which says Listings to be avoided include .... services), rather than an encyclopedic long-term summary. BilledMammal (talk) 23:14, 11 October 2023 (UTC)

• Yes. This is not indiscriminate info, as there's a very specific inclusion criteria. And being primary sourced is not disqualifying. Primary sources are perfectly acceptable for establishing matters of uncontroversial fact. oknazevad (talk) 14:53, 1 October 2023 (UTC)

  I agree with you that the tables are discriminate - they list all the destinations currently operating. But airport articles are not supposed to be directories that note each and every destination, no matter how trivial. Sunnya343 (talk) 02:16, 3 October 2023 (UTC)

  Your comment is begging the question and presumptive. This RFC is specifically to ask and answer whether or not such material is appropriate for articles. If the consensus is yes, then the guideline should be modified to note that consensus. Assuming existing guidelines automatically represent current and broader consensus is a perennial issue. Consensus can change, and arguing that the new consensus doesn't comply with older guidelines is without merit as an argument. oknazevad (talk) 23:29, 3 October 2023 (UTC)

  How else am I supposed to justify my point of view that the lists are not appropriate for Wikipedia articles, if I am not allowed to cite existing Wikipedia policies? Is this not what you yourself are doing when you make references to WP:INDISCRIMINATE and WP:PRIMARY? WP:PG says, Wikipedia's policy and guideline pages describe its principles and agreed-upon best practices. I am trying to make an argument based on those principles and best practices. If you have a concern with a policy itself, you should start a separate discussion (example). Sunnya343 (talk) 02:27, 4 October 2023 (UTC)

  Since the discussion is about the scope and content of the guideline itself, saying what the guideline contains doesn't actually contribute to the discussion of what it should be. Saying you think the guideline is fine as is and why does. oknazevad (talk) 22:41, 8 October 2023 (UTC)

  On second thought, I concur with JoelleJay and others that the information is indiscriminate. The tables list all destinations as of [insert today's date], and this information changes frequently. In the entire history of an airport, what makes today's list of destinations so notable, and not the one two months ago?

  Say that two months ago, an airport lost its only international flight. Because the emphasis is on maintaining up-to-date lists, an editor decides to simply delete the foreign destination. Sure, you can still mention the flight in the "History" section of the article, but you've nevertheless removed it from the table because you believe today's particular list of destinations is more noteworthy. FOARP said the following in an AfD on the lists of airline destinations, but I believe it applies to these tables as well: Since [the lists] can only be true on a particular, randomly-selected day, they are ephemeral and impossible to maintain given the way airline schedules change constantly, but if you did try to do keep them up to date, what you would have would essentially be an airline news-service, and Wikipedia is not news. Sunnya343 (talk) 02:34, 4 October 2023 (UTC)

• No, per @BilledMammal, @RoySmith, and @David Fuchs. I cannot see how these lists/tables of the airlines/destinations serviced by an airport provide so much utility and encyclopedic value as to override our policies on indiscriminate info, NOTDB, BALANCE, NOTNEWS, and OR. Items on these lists may be ephemeral and quickly out of date, and if their only sourcing is non-independent or primary then having such detailed tables for them arguably violates the Do not base an entire article on primary sources, and be cautious about basing large passages on them. policy in PRIMARY. Of course any routes that have enough coverage to be part of a BALANCED article can be discussed, but creating exhaustive lists or tables simply for completion's sake, or for needless consistency between articles, regardless of how well the entries are sourced, should not be normalized. JoelleJay (talk) 18:50, 1 October 2023 (UTC)
• Sort of We should provided enough details on destinations to allow readers to have a good understanding of the airports reach. For smaller regional airports this will likely be the complete list, whereas for large international airports perhaps condensing it into countries served would be more useful. As an aside, another thing to consider is to remove what destinations a particular airline serves, this starts intruding into making a product guide and introduces duplication if multiple airlines serve a single destination. Jumpytoo Talk 19:34, 1 October 2023 (UTC)
• Yes, the tables should stay – from a user standpoint, I've found them very helpful. At very least, if the tables are removed from Wikipedia, they should be moved elsewhere (Wikivoyage perhaps?) Codeofdusk (talk) 21:51, 1 October 2023 (UTC)

• @Codeofdusk: yes, Wikivoyage is the wiki for readers and users desiring for travel information, not encyclopedic information. See my vote+comment below. JWilz12345 (Talk|Contrib's.) 02:48, 8 October 2023 (UTC)

• Yes—There's nothing wrong with the prior RfC on this matter. Airports, like other transportation destinations, are primarily useful for their specific connections to specific places.--Carwil (talk) 16:43, 2 October 2023 (UTC)
• With my reader hat on, definitely yes - these are surprisingly useful. With my editor hat on, there is an obvious "...assuming they can be sourced", but this should not be difficult in most cases. Andrew Gray (talk) 17:10, 2 October 2023 (UTC)

  @Andrew Gray: What do you mean by these are surprisingly useful to readers?

  I agree that many destinations can be sourced with timetables and similar references (although I noted my concerns about this above in my response to CapitalSasha), but I believe Wikipedia is not supposed to be a directory of all destinations from an airport, nor is it meant to be a news site that seeks to maintain a current list of all destinations and makes note of the launch, resumption, and discontinuation of individual flights. Sunnya343 (talk) 02:11, 3 October 2023 (UTC)

  @Sunnya343 The use is I think in simply having that readable list of "where can you fly to from ---" without needing to go through individual airport websites. A reader can use it for various things, be that figuring out travel planning (I want to avoid a local domestic flight, does that place have any direct flights from Europe? Are they only seasonal?) or more general background reading (what places actually let commercial airlines fly to Pyongyang? Is some pair of cities very heavily served from that airport? Are the international flights only to one or two countries and what does that imply? Which airline clearly dominates the market here?). I think I've read it for some version of all of these over the years. Anecdotal I know, but hopefully informative.

  A lot of this can indeed be covered in text but it'd be awkward to try and pre-emptively address all those questions (as @WhatamIdoing I think noted above).

  In terms of suitability, I think I take an expansive approach to things like NOTDIRECTORY: the fact that we've been happily doing it for untold years means that we seem to implicitly consider that within the remit of permitted things, in much the same way we consider it eg appropriate to have a comprehensive list of film credits for an actor even when it's "policeman #3". You can certainly interpret the guidelines in such a way as to rule those both out, and I don't think you're wrong to read them that way, but ideally I feel our interpretation of them should be informed (and in many cases led) by what community practice is. Andrew Gray (talk) 12:41, 3 October 2023 (UTC)

  No one should be using Wikipedia articles on airports to plan their travel. We are explicitly not a travel guide, our information can be decades out of date or plainly wrong, and numerous sites like Google Flights are freely available to use for most airlines. JoelleJay (talk) 18:38, 3 October 2023 (UTC)

  To clarify, when I say "travel planning" I'm meaning something that might be better described as reading with the intention of eventually travelling, the sort of initial familiarisation reading people do well in advance of booking travel, rather than the detailed Google Flights type planning that involves "right, if we take Air France then there would be a connection in Frankfurt". I wouldn't expect anyone to use it for that. Andrew Gray (talk) 18:54, 3 October 2023 (UTC)

  But...what would readers actually be getting out of this content? Why would anyone be looking up which particular airports service airlines that go to particular other airports at any point in their planning? It would be way more effort to try to reconstruct flight paths based on a rarely-updated table of destinations on the wiki pages of individual airports than to just...go to Google Flights and plug in e.g. Pyongyang as the origin, set the destination as "anywhere", and select "nonstop only", which will yield all the locations that will send planes directly to Pyongyang in the next six months. Apparently roundtrip goes as low as $161 from Tokyo... JoelleJay (talk) 19:37, 3 October 2023 (UTC)

  You can disbelieve me if you want, but I'm pretty sure that I personally did that a few weeks ago (can't remember what prompted it, probably read something about someone travelling to NK and was curious; never underestimate idle curiosity...)

  I knew Wikipedia would have that table, and it was likely to be reasonably up-to-date (not updated this month, fine, but probably correct to a year or so) - YMMV, of course, but I wouldn't have gone to a flight search site because, well, I wouldn't want to wade through ads and a clunky interface to find the answer and then spend extra time figuring out if it was actually answering the question I'd meant to ask.

  On that note, GF would give you the wrong answer: it doesn't think Pyongyang Airport exists, so the flights it quotes are from the wrong side of the DMZ. Andrew Gray (talk) 20:22, 3 October 2023 (UTC)

  Ok, I guess in the extremely unusual situation where an airport has very restricted commercial accessibility it might be easier to use something other than a standard flight planner, but I would not have expected to find this info on Wikipedia and definitely would not expect it to be updated... I would just google which airlines/airports serve NK and go to their websites. JoelleJay (talk) 23:24, 3 October 2023 (UTC)

• No - they are poorly maintained and often out of date. There is no way any reader is going to rely on Wikipedia for accurate and up to date information in this area. Isaidnoway (talk) 23:26, 2 October 2023 (UTC)
• No. Poorly-sourced and badly-maintained lists like these are worse than useless, in contexts where people might be misguidedly attempting to use Wikipedia to plan travel. Wikipedia should not be trying to substitute itself for better sources of information, even disregarding the obvious WP:NOT issues. AndyTheGrump (talk) 02:19, 3 October 2023 (UTC)

  Do you have an example of one of these tables that is incorrect? CapitalSasha ~ talk 02:07, 4 October 2023 (UTC)

  Based on the airline destination list issue the problems are typically:

  - WP:CRYSTAL pronouncements about planned services that may not happen.

  - Long-out-of-date data.

  - Broken links.

  - Unreliable/non-independent sourcing.

  - Original research based on comparing the routes displayed as available on different days. FOARP (talk) 11:50, 4 October 2023 (UTC)

• No, not in this form. A general overview of an airport's airlines and connections over its history would be relevant. But a continuously updated point-in-time snapshot of every current airline and every current connections feels more like the function of a travel guide than an encyclopedia article taking a long-term, historical view.--Trystan (talk) 00:15, 4 October 2023 (UTC)
• Yes. WP:V, WP:RS and WP:NPOV can cover relevant concerns. Making a blanket rule banning such information is unnecessary WP:CREEP. —siroχo 00:45, 4 October 2023 (UTC)
• Not in this form - an overview of the major destinations served by a airport, sourced to an independent source seems fine. There we are talking about essentially transport infrastructure. Compiling exhaustive lists of all destinations served from airline websites, almost always including WP:CRYSTAL-style information about planned routes that may not happen, and which anyway change quickly, is creating a service-directory and promotional content, both barred by WP:NOT. Moreover it is essentially discussing the airlines, not the airport. FOARP (talk) 04:57, 4 October 2023 (UTC)

  Reliable sources like [23][24][25] do not violate CRYSTAL. There's no speculation, these are legitimate announced plans with approvals that rarely get reversed. Addressing the fact that they can change – and not that regularly – is the beauty of a wiki. Reywas92^Talk 04:34, 5 October 2023 (UTC)

  These are: (1 and 2) airline websites that are obviously not independent of the subject and (3) essentially a news-ticker blog. Flight plans change week-to-week, as a perusal of e.g., the BA website news section shows. FOARP (talk) 08:46, 6 October 2023 (UTC)

• yes such tables should be allowed or to a limited extent encouraged. Particularly for smaller airports, the information is useful and maintainable. However for major international hubs, it probably will not be complete or up-to-date. So major airports could have a reduced summary of long running or major routes. Graeme Bartlett (talk) 12:23, 4 October 2023 (UTC)
• No/ disallow per NOT. These ubiquitous lists exemplify everything we do not stand for: NOTNEWS, INDISCRIMINATE and NOTDIR. Also RECENT, for as the nom noted, this excludes previous versions on no other grounds than to be up to date. Whereas an encyclopedia should take a long-term, historical perspective where necessary. Plenty of policies back their exclusion. This would not preclude keeping information of genuinely encyclopedic interest (to be assessed on a talk page-by-talk page basis, perhaps). Serial 15:19, 7 October 2023 (UTC)
• No in this current form (airline+destination tables) in all airport articles. That is the job of Wikivoyage. Both Wikipedia and Wikivoyage provide meaningful information, but Wikipedia is geared towards encyclopedic information, not information exclusive for travellers or readers planning to travel. WP:NOTGUIDE. Migrate all tables to Wikivoyage. JWilz12345 (Talk|Contrib's.) 02:37, 8 October 2023 (UTC)
• Yes. Frostly (talk) 02:44, 8 October 2023 (UTC)
• Yes. At a glance, looking at how large the destination table gives us an idea how well served the airport is. And I would recommend listing this suggestion under WP:PERENNIAL because it is proposed at least once a year for last 3 years with no traction each time. I wouldn't oppose if this data is imported and made available in Wikidata before removing it from Wikipedia. But until then, it should stay. OhanaUnited^{Talk page} 05:02, 12 October 2023 (UTC)

  Your accurate characterization of this information as data underscores a larger point. Allow me to pose a rhetorical question. What if we made a tool that imported all the data from airline flight schedules into airport articles, and we configured it to update the lists regularly? That way we would always have up-to-date information... However, articles are not supposed to be repositories of raw data. Sunnya343 (talk) 02:38, 13 October 2023 (UTC)

  But we're proposing to delete the data first before it even has a chance to be exported to Wikidata. This is like telling someone that Commons can be used to upload photos but deletes the local copy first. OhanaUnited^{Talk page} 14:19, 17 October 2023 (UTC)

• No for all of the different reasons cited by others already that Wikipedia is NOT. And a maintenance nightmare.— Preceding unsigned comment added by SandyGeorgia (talk • contribs) 18:34, 8 October 2023 (UTC)
• Yes The routes for an airport are sensible content and, per WP:CREEP, what we don't need are petty rules to micro-manage the form of presentation. Andrew🐉(talk) 19:05, 8 October 2023 (UTC)
• No. The RfC is about current airlines which currently "serve" the airport. This is constantly changing and, per WP:NOTNEWS, WP:NOTDIRECTORY, etc. etc. this information is not appropriate to an encyclopedia. I am sure that some "yes" voters find it useful, but that is not the point; useful stuff does exist elsewhere on the Internet, but that is no reason to maintain a live copy here. The previous RfC, earlier this year, showed a clear consensus, and just because one editor missed that discussion is no reason to revisit it so soon. This RfC borders on WP:DISRUPTION. Of course, illustrative remarks on major and historic destinations, backed in depth by multiple independent WP:RS are quite a different matter, but are not the subject of this RfC. — Cheers, Steelpillow (Talk) 19:51, 8 October 2023 (UTC)

  Do you oppose listing the current (ever changing) squad in an article about a professional sports team? —Kusma (talk) 09:26, 9 October 2023 (UTC)

  Nearly every pro sports team has a per year/season article where the roster for that year is given. That type of resolution works for sports since these are typically always noted. But I can't ever see support for a case like "2023 in Chicago O'Hara Activity" which would be the equivalent here. Masem (t) 17:54, 10 October 2023 (UTC)

  That query is just a red herring: sports teams are not airports, and the points of interest are not comparable, per Masem. Specifically, if you want to cite/verify the lineup of Pro Team X back in 1953 there is likely plenty of RS, but if you want to do so for Airport Y you will be lucky to find anything at all. So we get WP:NOTABILITY, WP:UNDUE, etc. weighing in too. Just because there are fans here on Wikipedia does not mean that there is a verifiable fan base out there in WP:RS land. — Cheers, Steelpillow (Talk) 08:58, 13 October 2023 (UTC)

  @Steelpillow: Did you mean to link to this RfC from August 2023? That one was on the lists of airline destinations (example), whereas the present discussion is about the lists in airport articles (example). If you apply what you said to the latter type of list, I actually agree with you, but that's besides the point. I started this RfC here at the Village Pump because I felt the previous discussion at WikiProject Airports was a case of local consensus. Sunnya343 (talk) 02:18, 13 October 2023 (UTC)

  Apologies, I did get my RfC's mixed up. Thank you for spotting it. But both support the case that these kinds of list are inappropriate to this encyclopedia. — Cheers, Steelpillow (Talk) 08:58, 13 October 2023 (UTC)

• No Lists of destinations by airline are very volatile, and do not belong ion an encyclopedia. I have largely given up on reviewing changes to airport articles because of the constant churning to destinations, which can be difficult to verify. - Donald Albury 19:57, 8 October 2023 (UTC)
• No. NODIRECTORY, NOTDATABASE, NOTINDISCRIMINATE, basically, and it all changes too frequently. The very fact that many of our readers might think that the information is reliable and current, instead of incomplete and months out-of-date anyway, is itself problematic. This is not the kind of informational purpose that an encyclopedia serves, and there are oodles and oodles of travel-related sites that already fill this niche (never mind that WMF even seems to be running one itself at Wikitravel.org already).  — SMcCandlish ☏ ¢ 😼  20:01, 8 October 2023 (UTC)

  I would be happy to use one of the "oodles and oodles of travel-related sites" for my travel planning instead of Wikipedia, but I am not aware of any place that tells me in an easily accessible way what the direct connections from any given airport are. @SMcCandlish, if there are so many, I am sure it will be easy for you to point me to one. —Kusma (talk) 09:25, 9 October 2023 (UTC)

  [26][27], etc. And even if some informational niche gap could be identified does not mean that WP should fill it anyway; this is the main reason we have WP:NOT policy in the first place.  — SMcCandlish ☏ ¢ 😼  13:01, 9 October 2023 (UTC)

  These are all terrible (ad-ridden and full of stuff like sales links that do not help answer my question). And the point of WP:NOT is not actually "this is useful, so we must kill it". —Kusma (talk) 14:23, 9 October 2023 (UTC)

  I agree with SMcCandlish, but I will say, why don't you just consult one of Flightradar24's route maps for that purpose, like this one? Come to think of it, the lists in airport articles are basically attempts to duplicate the entire content of those Flightradar24 maps, which are more up-to-date anyway. Sunnya343 (talk) 01:05, 10 October 2023 (UTC)

  Why would you even need to know the list of direct connections from given airports? Do you plan your trips by looking up what places some airport has non-stop service to and then choosing one of them? Why not use google flights instead...? Also the flysfo.com link with a list of all the SFO destinations has zero ads... JoelleJay (talk) 01:45, 10 October 2023 (UTC)

  Why not use google flights instead...? Because not every airline is on Google Flights. And that's just in the US. We haven't gotten to developing countries. Are you confident in telling me what airlines and flights fly out of Mogadishu Airport with links to the announcements? OhanaUnited^{Talk page} 16:11, 12 October 2023 (UTC)

  As a contributor to an encyclopedia article, I'm not interested in mentioning every airline and flight out of the Mogadishu airport as of October 2023. I won't rehash my arguments in my !vote above, but one reason is that the body of reliable, independent sources does not cover that information in depth. On the other hand, I might note that Mogadishu has direct flights to the Middle East,[28] or that Turkish Airlines was the first major airline to begin flying to the city since the onset of the Somali Civil War 20 years prior.[29][30][31] Sunnya343 (talk) 03:20, 14 October 2023 (UTC)

• No. We settled this already. Nothing has changed, and WikiProject RfCs are a joke. --James (^talk/_contribs) 20:41, 8 October 2023 (UTC)

  That was a different question, about lists on airline articles. The question regarding airport articles has not been asked. Thryduulf (talk) 15:45, 12 October 2023 (UTC)

  In my opinion, the same logic applies here. --James (^talk/_contribs) 18:20, 13 October 2023 (UTC)

• No – WP:NOTDATABASE, WP:NOTTRAVEL, these lists are often quite volatile and difficult to properly maintain, and the fact that Wikivoyage exists. I did sample some major US airports and did not see lists of destinations on those articles, but there is no reason they cannot be created and maintained there with a cross-wiki link in the enWiki article. I presume the purpose of Wikivoyage is to serve as the very travel guide enWiki is not supposed to be. If there are particularly interesting things about an airport, such as the aforementioned fact that KIND only has CYYZ and MMUN as international destinations, then those can be mentioned in prose. — Jkudlick ⚓ (talk) 22:08, 8 October 2023 (UTC)
• No. A few very notable mentions are ok, but not a complete list. A lot of these lists aren't verifiable and the extend of what is considered a destination often involves adding references from booking sites, which becomes promotional. We have WikiVoyage for this purpose. Ajf773 (talk) 08:55, 9 October 2023 (UTC)

  With these and related articles where such lists mushroom up, perhaps we could do with a WP:NOTWIKIVOYAGE meme. — Cheers, Steelpillow (Talk) 12:02, 9 October 2023 (UTC)

• No. An encyclopedia summarizes. It has no business providing a comprehensive account of all the destinations served by an airport. It doesn't serve researchers, since it lacks any context or analysis, it is just raw information. It doesn't serve general readers, unless they are extremely bored. It doesn't serve historians, since it is only a snapshot of current arrangements (that it will invariably be out of date is already covered by the Wikipedia disclaimer). Edson Makatar (talk) 13:15, 9 October 2023 (UTC)
• Yes, obviously – The list of reachable destinations is naturally part of key information that a reader expects from airport articles. Even if Wikipedia is not a travel guide, it certainly is a go-to place to understand the local geography and potential connections in places you are not familiar with... or for that matter even for places you ARE familiar with. Wikipedia has a distinct advantage over travel-booking engines, in that the information is clearly and predictably laid out for a quick glance by human eyes instead of being buried in cookie acceptance requests, promotional offerings and ungodly "connections" through creative routes that only a database engine can imagine inflicting on a naive traveller. Yes, Wikipedia, please tell me whether I can fly direct from Phnom Penh to Yangon instead of spending 27 hours on a bus ride through the jungle. I'll figure out in a minute how to buy my tickets elsewhere, as you conveniently list which airlines may be able to serve me. Per WP:Readers first, Remember that the main purpose of Wikipedia is to provide useful articles for readers! — JFG ^talk 13:46, 9 October 2023 (UTC)

  Yes, Wikipedia, please tell me whether I can fly direct from Phnom Penh to Yangon instead of spending 27 hours on a bus ride through the jungle. Per WP:NOTGUIDE, this is not our purpose. If someone wants to determine this they can go to Wikivoyage, or to any one of the dozens of websites that, upon being told you want to fly from Phnom Penh to Yangon, will provide you a complete and up to date list of flights and booking options. BilledMammal (talk) 13:51, 9 October 2023 (UTC)

  Our purpose (at least mine) does not include ideological adherence to a pure vision of WP:NOTGUIDE, though. (Otherwise we would have long since deleted classic violations like the lists of United States network television schedules). That something is useful is not a reason to delete it (weird that this needs to be said). —Kusma (talk) 14:31, 9 October 2023 (UTC)

  The issue of television schedules has been debated before (5+ years I believe), which is why the wording for that in NOT is clarified as such. Its why these are generally allowed as talking about a given year's television season as to compare the blocks of prime time programming between the major networks as these trends are themselves notable. But not the specific week-to-week scheduling or things like daytime programming. There's a clear refinement there. The same can be done for airports - there are broad ways to discuss airlines and main routes but that do not rely on trying to keep up with day-to-day operations. Masem (t) 23:20, 11 October 2023 (UTC)

  You can just visit the RGN website's flight schedule and see that Myanmar Airways International provides service to PNH Mondays and Sundays...which you can confirm at the MAI site. JoelleJay (talk) 02:02, 10 October 2023 (UTC)

  Being useful is not a sole reason to keep info. It would be extremely useful if we could supply medical advice to our readers, but even if we kept that strictly to MEDRS sourcing, that's still a huge minefield that we avoid it all together. Our first purpose is an encyclopedia, and NOT is what sets the bounds for what that should not cover. Masem (t) 18:02, 10 October 2023 (UTC)

• Yes Keep them available for readers to enjoy. I have been trying to keep them up to date and accurate for the airports in the Oceania region for 15 years. They can be maintained with the right sources and they have been allowed on Wikipedia almost since the beginning. A lot of people will miss them when they are removed but won't know why as they are not too involved with the Wikipedia policy. So will never know why they will be no longer on Airport pages CHCBOY (talk) 14:48, 9 October 2023 (UTC)
• Yes informative, encyclopedic. The Rambling Man (Keep wearing the mask...) 16:40, 9 October 2023 (UTC)
• Yes Easy to source, from someone who started out working those tables, encyclopedic and should be kept. 47.227.95.73 (talk) 19:39, 9 October 2023 (UTC)
• No Wikipedia is not a travel guide, WP:NOTGUIDE. — Preceding unsigned comment added by Ratnahastin (talk • contribs) 01:19, 10 October 2023 (UTC)
• Yes, a rare case I disagree with SMcC. I love this discussion, as it combines many fine things about Wikipedia: meticulous attention to certain details; a desire to capture parallel details about every entry in a category; a desire to be concisely useful and maintainable as a public resource. The whole purpose of an airport is to host airlines taking people and things to other cities, so it is a significant detail. Destination tables are moderately long, need occasional but not continuous updating, and are maintained by a community of passionate enthusiasts — I see no reason not to include them. (This does not strike me as what NOTDIR or NOTGUIDE were created to avoid.) For the sake of making the freshness of information clear, it might help to have a standard template that includes a "last updated" footnote at the bottom of such tables with a link to a canonical source for anything without its own ref. – SJ + 01:38, 10 October 2023 (UTC)
• Yes, because non-stop destinations are useful information about an airport – what places does it directly connect to? Breaking it down by airline is even more helpful to determine WHO flies a specific route, instead of just saying there's a non-stop connection to X destination by some air carrier. Additionally, airport websites are not always the most frequently updated with their destination offerings, nor do they always differentiate between seasonal and year-round service. Panthercoffee72 (talk) 20:07, 11 October 2023 (UTC)
• Yes for me case-by-case makes the most encyclopedic sense; in general I would expect commercial airports with a handful of destinations would be the most suitable -- it really matters to understanding such a topic what three, or six, or nine places you can get to (indeed, it is perhaps the most informative thing to really understand the operation at all). Alanscottwalker (talk) 15:20, 12 October 2023 (UTC)
• Comment. There appear to be many Yes !votes here which really mean No. The OP has made it clear that "the central question is whether airport articles should mention every single flight that the airport offers". Many of those "Yes" votes are qualified as, for example, "every route" or "case by case", so what they really mean is "No, not every single flight indiscriminately". — Cheers, Steelpillow (Talk) 16:04, 14 October 2023 (UTC)

  An outcome of "no" will be interpreted as a justification for indiscriminately removing entire lists, which is not what any of those qualified "yes" !votes want (nor at least some of those with bolded "no" comments). Thryduulf (talk) 18:43, 14 October 2023 (UTC)

  My impression is that the people who !voted "no" (and many of those who made a qualified "yes" !vote) do not seek to simply remove a list and leave it at that, but to provide instead a description of the airport's operations that is in line with Wikipedia policies. Sunnya343 (talk) 03:14, 15 October 2023 (UTC)

  Some who voted "no" and some who voted "yes" do think a prose replacement and/or a prose supplement to a partial list will be appropriate, but lists (comprehensive and otherwise) will be removed without replacement using this RFC as a justification if the outcome is "no", even though that is not the desire of most. Thryduulf (talk) 09:16, 15 October 2023 (UTC)

  Mass excision of lists without a sincere effort to replace them would not be productive, but disruptive, and such behavior should be dealt with accordingly. Sunnya343 (talk) 14:13, 15 October 2023 (UTC)

  Except such mass removals are almost always the result of an RFC with a closure that something doesn't belong. And any attempt to push back against such mass removals results in not only the removed simply pointing to the RFC as justification with no nuance, but offer results in the person saying correctly that mass removal is a bad idea having to defend themself at ANI. Thryduulf is right. The strict binary of wording of the RFC would absolutely result in a mass removal with no sense of subtly whatsoever. oknazevad (talk) 14:32, 15 October 2023 (UTC)

  Agreed, this is why I raised issues with the phasing of the question all the way at the beginning. I'm not sure I could blame the removal on disruptive users I think the blame falls squarely on the wording of the RfC. @Sunnya343: this means that if such mass excision happens it will be on your head alone. You can not, as you do here, simply pass the buck to other editors and claim that its them who is disruptive for your mistake. Horse Eye's Back (talk) 14:44, 15 October 2023 (UTC)

  "It will be on your head alone"? What nonsense. It would be on the head of everybody who helped build the consensus - which usually means most of us - and especially on the wording of the closure. And many of us would not be sorry to see a clean slate and a fresh start on the well-sourced ones. — Cheers, Steelpillow (Talk) 15:19, 15 October 2023 (UTC)

  How am I supposed to incorporate every possible nuance into the RfC statement and still comply with WP:RFCBRIEF? The nuances arise over the course of the discussion and should be incorporated into the closing summary, as Steelpillow noted. Sunnya343 (talk) 23:08, 15 October 2023 (UTC)

  A question closer to "what should lists of destinations in airport articles include?" with a list of options, including (but not necessarily limited to) "nothing" (i.e. remove the lists), "an up-to-date list of all destinations", and "a representative sample of destinations" would allow for much greater nuance and much less scope for overzealous content removal. That you needed to clarify the question so soon after asking it is not evidence of a well-workshopped proposal. Thryduulf (talk) 00:33, 16 October 2023 (UTC)

I must add that I am astounded and bewildered by the personal attack on me for the hypothetical actions of other editors following the hypothetical outcome of an active RfC. Sunnya343 (talk) 22:58, 17 October 2023 (UTC)

• Close poorly phrased RFC and start over. It isn't clear from the wording whether we're discussing requiring these tables or banning them. I don't think anyone's going to !vote for saying the tables "should" always appear; that's not the same as putting in a rule against them. --Trovatore (talk) 18:56, 14 October 2023 (UTC)

  How is the wording different from this RfC, which editors did not have difficulty understanding: Should Wikipedia have and maintain complete lists of airline destinations? In the same vein as the latter discussion, the present RfC is asking whether the complete lists of airlines and destinations in airport articles belong in Wikipedia. The paragraph that begins with Virtually all airport articles should make this clear. Sunnya343 (talk) 02:34, 15 October 2023 (UTC)

  Appears to be substantially different from "Should airport articles include tables that display all the airlines that serve the airport and the cities they fly to?" the key difference being "all the airlines" which the first question doesn't ask at all. Horse Eye's Back (talk) 14:48, 15 October 2023 (UTC)

  The first question asks whether Wikipedia should have complete lists of airline destinations (example). My question asks if airport articles should have complete lists of airlines and destinations - i.e. "all the airlines that serve the airport and the cities they fly to". Sunnya343 (talk) 23:11, 15 October 2023 (UTC)

  @Sunnya343: The problem is with the interpretation of the word "should", where a yes answer could be taken as meaning that these lists should always appear, and no could be taken as meaning that they should never appear. That's a bad question and basically invalidates the whole RfC. You need to close it and start over, asking a question more focused on what you mean. If you think that maybe we should ban the lists, you should ask if we should ban the lists. If you think they should always appear, you should ask whether they should always appear. --Trovatore (talk) 16:04, 17 October 2023 (UTC)

  There are, at a basic level, multiple options for how lists/tables of destinations could be handled.

  1. Never allowed.
  2. Exceptionally allowed. Exceptions would require discussion at an individual article level, with a presumption against inclusion
  3. Discouraged. Most articles should not have a list/table, but there are some airports where it is justified.
  4. Neutral. Neither required nor prohibited, with no general presumption for or against inclusion.
  5. Encouraged. Most articles should have such a list/table, but sometimes it makes sense not have one.
  6. Almost always required. Exceptions are possible and would require discussion on each article, with a presumption in favour of inclusion.
  7. Required. Every article about an airport with scheduled flights should have list and/or table of the airlines and destinations.

  It should also be made clear that there are multiple types of list/table, none of which are mutually exclusive (even on a single article) and the consensus regarding each might be different:

  1. Complete, listing every airline and destination.
  2. Comprehensive, including most but not necessarily all.
  3. Representative, a sample giving an overview of the types of airlines and destinations and their relative proportions
  4. Most significant only.

  Finally, each of those four types could be for the rolling now, for a specific moment in time or covering a period of time (e.g. a single year through to a decade or so, possibly more). An article may have more than one (e.g. a complete list for now and a representative list for each prior era of operations).

  This discussion reduces all this to a single question and assumes that everybody is talking about the same thing. Thryduulf (talk) 16:54, 17 October 2023 (UTC)

  The other RfC statement also includes the word should, yet editors raised no concerns about its meaning. The outcome of that RfC was clear enough for three subsequent discussions to reaffirm it (1, 2, 3). I have contacted the people who started those discussions to seek their input.

  The question is quite straightforward. Either you believe Wikipedia should maintain the current, complete lists of airlines and destinations found in all airport articles, or you do not. If you !vote "Yes", you provide your reasoning. If you !vote "No", you are free to explain what sort of information should be provided instead, as many editors have done. Sunnya343 (talk) 23:03, 17 October 2023 (UTC)

• Needs further clarification. It should not be required, but does not prohibit mentions either. Senorangel (talk) 02:20, 15 October 2023 (UTC)

• No hopelessly outdated in most articles WP:NOTGUIDE.Moxy- 23:39, 15 October 2023 (UTC)
• Yes. I don't buy the WP:NOTGUIDE argument one bit. It's encyclopedic info relating to which airlines serve the airport (along with other airports that can be reached directly from that airport, which can often be found in RS). That is essential info relating to an airport's operation - much like we would not have a road article that fails to list what towns the road serves, or a railway station article that doesn't mention what railway lines actually stop there. What would bring this into NOTGUIDE territory are timetables, flight numbers, gate numbers, etc. Epicgenius (talk) 13:10, 17 October 2023 (UTC)

  Roads and train tracks are essentially permanent and thus once down, they won't change. The airlines that serve an airport, and moreso the list of cities they serve, are extremely flexible since planes are not required to travel fixed paths. Masem (t) 02:05, 19 October 2023 (UTC)

  Good point; it could be harder to maintain articles like that. I still think airline/destination lists can be included if supported by RS; though I don't think their usage should be banned (or conversely, mandated), as the destinations served by an airport are still valuable pieces of information relating to the airport's very operations. If an airport only has flights to one or two other airports, for example, it would not serve the WP:READER well to not mention that. – Epicgenius (talk) 02:12, 19 October 2023 (UTC)

  To add, the equivalent of airports/airlines to roads would be bus and train routes, which are subject to daily changes. And which we don't include. Masem (t) 02:18, 19 October 2023 (UTC)

  @Epicgenius: I agree 100% with your sentiment regarding an airport with few flights. For example, it would be silly to insist that you may not explicitly mention the three flights available at the Kalamazoo airport. I'm sure you will find a good number of RS that discuss them in detail, given their significance to a small airport like Kalamazoo's. The Newark airport is a different story. But even then, there are some noteworthy routes that we should describe in the article, such as the nonstop flight to Singapore, which is the longest in the world.[32][33]

  Is that what you thought when you read the RfC question and clarification - that if you !vote "No", it means you believe that explicitly mentioning any current destinations should be forbidden? (Not asking sarcastically.) Because that's not what I meant. I didn't think it was necessary to include that nuance since this RfC on a similar topic did not either, and editors seemed to understand. Sunnya343 (talk) 14:58, 21 October 2023 (UTC)

  Thanks for the response @Sunnya343. I will admit that I interpreted the question "Should airport articles include tables that display all the airlines that serve the airport and the cities they fly to?" as having two choices—yes, we should allow them to be included, and no, we should not allow them to be included. My position is that the tables could be included if sources support them, but that the tables shouldn't be mandatory (which I supposed would be the subject of a later discussion). Epicgenius (talk) 15:20, 21 October 2023 (UTC)

• Yes - It's an integral part of the importance of an airport. It includes information that goes into airport size, airline market share, and more. Since the dawn of Wikipedia we've had these tables and I'm not sure why some people keep going after them. ✈ mike_gigs ^talk_contribs 14:59, 17 October 2023 (UTC)
• No - We're not a directory and this comes off as way too promotional. It's like listing the menus of restaurants, or listing all the different model bulbs made by General Electric. It comes off as not only unencyclopedic but as an advertisement for these facilities. There's a fine line between giving a basic summary highlighting what a business does and promoting what they do. This seems to cross it by a mile. Zaereth (talk) 03:32, 18 October 2023 (UTC)
• Yes. The destinations that an airport serves are just as relevant as the destinations that a road or railway serves. It is true that these airport destinations change more easily than roads or railways, and so needs more frequent updating, but the content is usually easily verifiable through airport websites and airline timetables. Sjakkalle (Check!) 06:42, 18 October 2023 (UTC)

  As an aviation enthusiast who used to edit these lists frequently, I have found that the easiest way to verify their contents is to check Flightradar24. The website is convenient in that it compiles data from different airline timetables and other sources. If we take the Chongqing airport table as an example, it's easy to type "CKG-CAN" (the airport codes for Chongqing and Guangzhou) in the search box and click on Flight AQ 1200 to confirm that 9 Air flies between those cities. You can do the same for the rest of the destinations in the table. There was a time when I would pull up one of Flightradar24's route maps for an airport, write down all of the airlines and destinations, and add that information to articles in the Spanish Wikipedia that previously lacked such lists. Eventually I paused to reflect. What is the point of meticulously copying all of this information from one website to another, especially given how often it changes?

  Railway services are major pieces of infrastructure that receive extensive coverage in the body of published sources. For instance, the services at Cleveland Lakefront Station are notable enough to have their own Wikipedia articles. If one of these ended, it would be a major event that we would describe in the station's article. On the other hand, when Lufthansa ends its Frankfurt–Erbil service or British Airways stops flying from Doha to London-Gatwick, we will simply delete the destination from the table; that information will be removed from the article forever. In other words, we're not meaningfully building or expanding the article, but continually hitting the "refresh" button on the list of destinations. Providing information that is transient and at this level of granularity is a job better suited to a constantly updated database like Flightradar24, than to an encyclopedia article. Sunnya343 (talk) 22:32, 19 October 2023 (UTC)

• Yes: WP:V and WP:CREEP are each valid counters to the WP:INDISCRIMINATE claims, and simply because some articles lack the proper sourcing does not mean that it doesn't exist. Let'srun (talk) 18:03, 18 October 2023 (UTC)
• Yes Certainly they may need better sourcing, but that can come in the course of article improvement, and it's useful to have.--Wehwalt (talk) 18:08, 18 October 2023 (UTC)
• Yes Without expounding further....as many excellent reasons cited above. But the same expectations and content rules should be applied as consistently as the rest of Wikipedia (well sourced, cited, maintained etc...) (If it is unmaintained / not well sourced - it should be either repaired or deleted just like every other wikipedia article. DigitalExpat (talk) 06:03, 19 October 2023 (UTC)

  Vote to close this RFC - upon rereading, there's been excellent valid points raised about the flawed nature of the question in this RG and it is unlikely to be able to drive to a productive conclusion. Some very experienced wiki editors have given good points here and they have largely been ignored or taken as an argument. I would suggest a more productive RFC would be on the Aviation Wiki talk pages on perhaps 'how best to source flight information' (eg OAG and Cirium as proof of routes instead of FR24 that just says a plane flew from A to B within the last 30days). To contradict my vote above, upon reread of this long (and growing) RFC, it is a flawed question and unanswerable as evidenced by the above. (PS - if we source superior resources like Cirium based data,it would tell us that EWR-SIN is not the "longest flight", but is the 2nd longest.) Cheers! DigitalExpat (talk) 02:42, 20 October 2023 (UTC)

• Qualified yes For major airports like Heathrow, or Chicago IMHO it's not necessary: one can assume that there are many flights to & from many places involving those airports. However, when it comes to less trafficked airports, where there might be only one or two carriers that service it, it becomes important not only to potential travelers, but as an indicator of how busy that airport is. Further, the airports I have in mind are those in second or third-tier cities in Africa or Asia -- only as an afterthought I realized this could apply to the US & Western Europe. (IIRC, all cities in Oregon except Portland have at most one carrier serving their airport, which is the case for most states in the US.) As for the issue of maintainability, we have that same issue with countless articles, & the only solution is for more eyes & editors. If we start accepting that as an unqualified reason to omit information, we might as well go on a deletion spree thru the rest of Wikipedia. -- llywrch (talk) 21:04, 19 October 2023 (UTC)
• No, not at all, per SMcCandlish and Moxy. The fact that readers trust us for this, is a problem in itself, when these very long tables are poorly maintained. Disallowed by several sections of WP:NOT (heck, even WP:NOTPRICE: "products and services" / "availability information"). Information cannot be defining (or encyclopedic) if it changes frequently, and we shouldn't be maintaining carbon copies of info findable on other websites (like the airport's site, or flightradar24). Destinations are determined by airlines, not airports, so this would make less sense than lists of airline destinations, which there is already consensus against. DFlhb (talk) 18:14, 4 November 2023 (UTC)
• Include in some way, either in the article or as a soft redirect to WikiVoyage. I think that ultimately it's more useful to keep them despite the strong NOTDIRECTORY argument as it would better assist readers (per the essay Wikipedia:Readers first), but if they have to go, consider soft redirecting our readers to WikiVoyage as a middle ground. InvadingInvader (userpage, talk) 18:58, 13 November 2023 (UTC)
• Support. I think the most compelling argument for me was given by Kusma: this is traditionally within the scope of an encyclopedia. Streamline8988 (talk) 06:48, 18 November 2023 (UTC)

Discussion (airlines and destinations)

• I have a problem with the framing of this question, "Should airport articles include tables that display all the airlines that serve the airport and the cities they fly to?" is so vague that we all appear to be voting on different proposals. @Sunnya343: can you clarify whether by "all the airlines that serve the airport and the cities they fly to" you mean all which we can reliably source or is it a rhetorical question? Horse Eye's Back (talk) 20:47, 30 September 2023 (UTC)

  I'm asking whether airport articles should mention every single flight that the airport offers, which is what it appears the articles are trying to do. I specifically mentioned "tables" because that is the format used by all the articles, but the central question is what I said in the previous sentence. Sunnya343 (talk) 23:35, 30 September 2023 (UTC)

  If they're going to mention some of them, and a complete list is possible, then why shouldn't we have a complete list? What's the advantage to having a partial list? WhatamIdoing (talk) 01:50, 1 October 2023 (UTC)

  In my rough draft for the Indianapolis airport article (which is just an idea, I'm not saying this is exactly how it should be), I do explicitly mention Toronto and Cancun, but that's because those are the airport's only two international destinations. If the airport had 10 or 15 international destinations, I personally wouldn't list all of them. So I'd say it comes down to the judgment of the editor(s), just like in other articles, where you have to decide whether or not to include certain details. I think WP:NOTEVERYTHING would apply. Sunnya343 (talk) 02:36, 1 October 2023 (UTC)

  Does it come down to judgement or does it come down to what the sources cover? Horse Eye's Back (talk) 14:41, 1 October 2023 (UTC)

  I still believe it comes down to judgment, and that WP:TMI is relevant here. Sunnya343 (talk) 17:35, 1 October 2023 (UTC) Actually, I think it's more nuanced. Please see the paragraph I wrote on October 7 after !voting "No". Sunnya343 (talk) 03:13, 8 October 2023 (UTC)

  TMI is a WP:ESSAY, WP:NPOV is a WP:POLICY. Horse Eye's Back (talk) 17:46, 1 October 2023 (UTC)

  You're right. I guess we'll have to agree to disagree about the need to mention every flight then. Sunnya343 (talk) 18:37, 1 October 2023 (UTC)

  You're disagreeing with a straw man, that is not my position and never has been. Horse Eye's Back (talk) 20:13, 1 October 2023 (UTC)

  Then what exactly is your position? I thought you were saying that because third-party sources can be found for every destination, we should include them all. Sunnya343 (talk) 22:14, 1 October 2023 (UTC)

  Nowhere did I say that and I'm not really sure where you would get that I did from. I said that "airport articles should include such tables when including a table would be due (closed airports don't need to have an empty table for example). A table should not preclude prose coverage of routes nor should prose coverage of routes preclude a table, there is room for both and both are often due." Horse Eye's Back (talk) 01:16, 2 October 2023 (UTC)

• Theoretically these tables might be able to be maintained to adequate sourcing levels, but this will not ever happen in practice. It's thousands of airports with shifting schedules and much fewer editors. The route and destination tables of most airport articles I watch are maintained by unsourced and often unexplained edits which add or remove routes and airlines. Obviously no-one checks these, and no-one has time to check them all, and even if someone did check them at some point it's entirely possible the situation might have changed. That is not to say the edits are not in good faith, much seem likely to be accurate, but it can be hard to know. Sometimes sources are added, which will note route opening, but these routes are as subject to change and removal as the unsourced ones. Many seem to find the tables useful, so I'm hesitant to oppose. I find the tables occasionally informative if indiscriminate. However, I read them with the knowledge that they are a mixture of incomplete, out of date, and possibly unsubstantiated information. I do not know if we should assume the same from our readers. CMD (talk) 02:45, 1 October 2023 (UTC)
• I am pretty sure there was a major deletion discussion and reversion a few years back, on exactly this topic. Would it be relevant to this question? Jo-Jo Eumerus (talk) 15:36, 1 October 2023 (UTC)

  You might be thinking of this RfC on the lists of airline destinations. Sunnya343 (talk) 17:37, 1 October 2023 (UTC)

  Yeah, that was really weird. We got a consensus to delete destination lists, then I got yelled for actually doing it. I still firmly belive that per WP:NOTDIRECTORY we shouldn't be hosting these schedules at all. Beeblebrox (talk) 20:51, 2 October 2023 (UTC)

• I would suggest that rather than attempting the impossible task of maintaining a complete and current list of airlines and destinations, we provide a snapshot of the typical operations of a given airport with respect to this information. That way, nothing needs to be updated, so long as we can accurately say that a particular set of this information from a particular date is exemplary for that airport. BD2412 T 18:18, 8 October 2023 (UTC)

  But what encyclopedic purpose would that serve?  — SMcCandlish ☏ ¢ 😼  19:57, 8 October 2023 (UTC)

  The purpose would be to illustrate the typical activity of a given airport at a given time. This is not much different from showing a picture of a tiger in the Tiger article. No single picture will be illustrative of every possible instance of a tiger, but the snapshot is still informative. BD2412 T 02:45, 10 October 2023 (UTC)

  "a snapshot" and "at a given time" immediately runs against the fact we are an encyclopedia, that we are supposed to be looking reasonably long-term/enduring factors, and not what happens day to day. We can add and update that long-term coverage as it happens, but we should be far away from trying to keep WP up to date with information that is changing in the short term, as would be the case of an airport's destination list. Masem (t) 02:49, 10 October 2023 (UTC)

  As I said, it is the same as having a photograph of a tiger. Or, for that matter, a photograph of the airport itself, since airports tend to undergo steady renovations, extensions, and so forth. BD2412 T 01:18, 12 October 2023 (UTC)

  The matter of determining whether the list from a particular date is exemplary for the airport sounds arbitrary to me. Additionally, people will see an outdated list in the article and inevitably attempt to make corrections, and you will have to find a way to justify reverting all of their edits. Sunnya343 (talk) 01:07, 13 October 2023 (UTC)

  If someone updates then they will either be correct to a new as-of date or they will be incorrect. If they are incorrect then either revert them as incorrect (as is frequently done across the encyclopaedia today) or correct them (as is frequently done across the encyclopaedia today), if the updates are correct leave them. If reverted then the project is no different to how it was before, no gain no loss. If the article is now more up-to-date then the project has benefited. Thryduulf (talk) 02:25, 13 October 2023 (UTC)

  My comment above addresses BD2412's proposal, which, as I understand it, is to have a complete list of destinations from a particular date that is considered exemplary for the airport. Therefore, nothing [would need] to be updated (that is, until editors somehow decide the list is no longer exemplary). Let's say the list of destinations from July 2023 is deemed exemplary. If a person makes a single change today, the list will no longer be a snapshot from July 2023. You can either revert that edit or update the entire list every time someone modifies it, which would defeat the purpose of BD2412's strategy. In conclusion, this proposal would be difficult to carry out. Sunnya343 (talk) 02:44, 14 October 2023 (UTC)

  Look, it's a tautology. A list that is exemplary for its time will always be exemplary for its time. For example, a list (or a prose description) that demonstrates the height of activity of a particular airport in the 1970s will always demonstrate the height of activity of that particular airport in the 1970s. BD2412 T 02:55, 14 October 2023 (UTC)

  I think I understand what you were saying now. Nevertheless, two questions remain: a) How often would you "refresh" the entire list, and b) How would you respond to editors who just think the list is outdated and (in good faith) proceed to make individual corrections (e.g. today British Airways ended service to Zakynthos, tomorrow Ryanair starts flying to Warsaw) - i.e. the status quo.

  In any case, a complete list of destinations at a single point in time is far beyond what's necessary to communicate the scale of an airport's activity. See the paragraph I wrote in the HAL Airport article that starts with On the civilian front for, in my opinion, an example of how to convey that information without providing an exhaustive list of destinations. Sunnya343 (talk) 23:34, 14 October 2023 (UTC)

  Except a tiger doesn't change its stripes every quarter. Honestly, the comparison to a tiger is rather bizarre and suggests that there isn't a common understanding of what this discussion is about. Orange Suede Sofa (talk) 06:07, 14 October 2023 (UTC)

  @Orange Suede Sofa: no, that is not what I am saying at all. I am not saying that a given airport is like a specific tiger on a specific day. I am saying that there are thousands of tigers in the world, and we choose one picture of one tiger to represent all of the topic, Tiger, although there will be many tigers that do not look like the one selected. BD2412 T 03:33, 15 October 2023 (UTC)

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

Subsequent closure review request:

• Wikipedia:Administrators' noticeboard#Closure review request for the RfC on the "Airlines and destinations" tables in airport articles

--A. B. ^{(talk • contribs • global count)} 04:56, 21 January 2024 (UTC)