Wikipedia:Requests for comment/When there is no consensus either way

Add links
Source: Wikipedia, the free encyclopedia.

When editors are unable to form a consensus either way about including or excluding a particular fact in a Wikipedia article, should they default to including or excluding that fact? (This question is not about living persons.) WhatamIdoing (talk) 02:40, 6 January 2024 (UTC)[reply]

The story

(TL;DR)  The only problem with the material is that editors can't agree on whether they want it in this article.
Some say the lack of agreement means it should be kept, and others say the lack of agreement means it should be removed.

Imagine that an editor recently created a new article. The subject is obviously notable, and all of the information in the article is correctly cited to an appropriate reliable source. All editors agree that all of the information in the article is accurate, verifiable, and neutrally phrased.

However, editors currently disagree about whether one particular fact in the new article should be in this article at all. There is no dispute over the wording of the sentence that presents this fact; the dispute is specifically and completely about inclusion or exclusion of the fact at all. (The exact nature of the potentially unwanted information is unimportant, except for the fact that the disputed material has nothing to do with any living person, so Wikipedia:Biographies of living persons does not apply.)

As normal editing and discussions on the talk pages were unable to resolve the question, an RFC was held on the article's talk page, which produced a large number of thoughtful and policy-based comments from a large number of editors. However, at the end, the two sides were equally balanced. At the end of this discussion:

After considering both the equal strength of the arguments and the equal numbers, the closing admin felt there was no option except to declare a true case of "no consensus" in the closing summary.

Obviously, if editors had formed a consensus to include this fact, then they would include it, and if they had formed a consensus to exclude it, then they would exclude it. But since they were unable to form a consensus, they are uncertain what to do. These editors are now asking you: When there is no consensus to include information, shouldn't it be removed, because policy A says to remove it? But when there is no consensus to remove information, shouldn't it be retained, because policy B says to retain it?

The Fine Print:

The problem

(TL;DR)  Some policies and guidelines don't agree about what editors should do in this edge case.
To resolve the conflict between the policies, we need editors to tell us what they believe, in principle, the best approach would be.

Usually, when article content is disputed, it's easy for editors to reach an agreement ("consensus") about what to do. In rare instances, even after extensive discussion, editors are unable to make a decision. Several policies and guidelines provide advice about the default actions in such cases. For example, contested ==External links== are

removed, and an Wikipedia:Articles for deletion
discussion ending in no consensus results in the article being kept.

We have attempted to create a central list of what to do in cases of no consensus. However, in the course of doing this, we have inadvertently created a conflict between two policies. One policy says content without consensus is usually kept, and the other says content without consensus should be removed. According to our

policy on conflicting written rules
, we need to figure out what the best practice is and make all of the relevant advice pages match the right thing to do. If we are able to reach a consensus about what the best practice is, then we will later be able to make specific proposals about which page(s) to change and what those changes should be.

(NB: We don't need you to tell us what the policies currently say, because we already know what they say, and – since they conflict with each other – at least one of them is currently wrong. Just tell us what you believe the best practice is.)

How to respond

(TL;DR)  Don't tell us what this or that policy says; we've already read them. Instead, tell us what you personally believe is the best thing for editors to do when they can't reach consensus.

Please add your viewpoint in the #Responses section.

  • In this discussion, it's more important to think about common sense, practicalities, and Wikipedia's values than about which line of policy or guideline you'd quote in such an RFC. The goal for this discussion is to figure out what editors believe the best practice is, in principle, when there is no consensus about whether to include or exclude non-BLP-related material in a particular article.
  • The policy
    evolving consensus
    ." This RFC is trying to figure out what the current community consensus is. Once we know what the current community consensus is, we will be prepared to accurately document the community's best practice in the written rules.
  • If you decide to cite a policy, guideline, essay, or other page that matches your view, please read it first, to make sure your memory of the page matches its current contents. (Previous discussions have seen editors linking pages that don't actually say what they thought it said.)
  • The key and immutable point is that there is no consensus. Responses that reject this premise (e.g., "I need to know what the arguments were, because one side always has better arguments, so the admin was wrong to say the reasons each side gave were exactly equal in strength" or "The side with the stronger argument should get what they want") will not help us answer the real question.

Discussion

Do you have questions? Do you have ideas? Do you want to share some thoughts with other editors while you contemplate possible #Responses? Post them here. RFCs operate under the normal rules for discussions. If you have meta-comments about the RFC (e.g., Why is it happening on this page? Can I notify page X? Why didn't you give me specific examples?), then please post those on the talk page.

I'm having trouble making up my mind. I think that it's best for Wikipedia to include more information. If people are looking for encyclopedic information (broadly defined), I'd like them to be able to find it here. However, I worry about certain kinds of claims, such as health claims ("One study showed that Wonderpam™ kills cancer cells in a petri dish") or geopolitical disputes ("Blue Country says that Orange Country smells bad"). Usually, I think it would be okay. If the material is obviously bad, we'll form a consensus against it. However, every now and again, we make really odd decisions. Of course, those decisions tend not to last very long, so perhaps it doesn't matter that much if disputed content is included until a consensus is formed against it.

OTOH, the approach we take to

WP:BLPs
is to remove contentious material until there is a consensus to include it, and why shouldn't we take a similar level of care for other subjects?

WP:QUO is a fine approach during a dispute, to the extent that it discourages edit warring, but it's bad to extend it beyond that point. I've been catching up on my watchlist after years of neglect, and it has been discouraging to find articles editing 25 times over 25 months, without even a single sentence being added or removed. WhatamIdoing (talk) 19:48, 9 January 2024 (UTC)[reply
]

REMOVE. I'm going to equate "contentious" with "damaging". If the information is "damaging," meaning that it would harm a person, place, thing -- it should be removed. Wikipedia is one of the largest databases in the world, we have a duty to do no damage. Lives and livelihoods are affected by our decisions. We are not a news source so contentious information can be learned about via news sources. It is not our role to be that news source. SO, unless the "damaging" information is combined with a criminal conviction -- IT STAYS OUT. Slacker13 (talk) 31 January 2024


It's been my general impression that this is what a maintenance phase looks like. We get oodles of smol gnomings as editors flit around fixing whatever is in their maintenance tasklist, and every once in awhile an article will undergo a complete rewrite over the course of weeks, without much action taking place in the space between.
My sample may be biased, and my memory might be faulty, but on my watchlist I very rarely see an edit that adds one or a few sentences of sourced information to an established article. Creation and repair seem to be the major spheres of mainspace editorial activity, with expansion and updating barely visible in the distance. Folly Mox (talk) 02:01, 10 January 2024 (UTC)[reply]
It's been like that for years, and has been getting worse. Many if not most of our current editors hardly ever add text. Some can't be bothered to find references, some are unconfident of their abilities to write sentences in English, and so on. Plus most are now on mobiles, where I certainly wouldn't want to do long edits. We should stop encouraging people to write new articles, & instead promote improving existing ones. Not sure what this has to do with your issue here, though. Johnbod (talk) 03:49, 10 January 2024 (UTC)[reply]
A lot of articles aren't changing anyway, so why would we ever want a bias towards the old version? The old version is happening too often anyway. If someone is attempting to (in their opinion) improve an article, maybe we should encourage that. Instead of excluding by default or including by default, maybe we should try the newest approach by default, or the least experienced editor by default. Really: If I can't, despite all of my wiki-friends, despite knowing the core policies so well, despite having written a non-trivial fraction of their contents, despite (as all my wiki-friends will agree ;-)) almost always being right, manage to scare up a consensus for my view, maybe the newbie deserves to "win". WhatamIdoing (talk) 05:25, 10 January 2024 (UTC)[reply]
Honestly, I kind of like that idea: bias towards change in order to counter natural ossification. Feels unimplementable in practice though. Assuming we're still in the hypothetical here where there's a true no consensus on strength of argument or numbers, do we count up the total active editing days of both sides and award the lower total the victory? Does the newest editor present in the discussion grant an automatic win like a golden snitch? Folly Mox (talk) 13:46, 10 January 2024 (UTC)[reply]
I was thinking just then about a dispute as being a 1:1 thing, with the other voices not exactly being participants in it, but you're right that some big disputes have a group-vs-group dynamic. The newest editor rule would tempt people to engage in socking, but there are probably ways around that (e.g., the newest editor as of the day before the dispute started, the most recently extended-confirmed editor, the side with the most voters who have between one and five years' experience, etc).
We could also have a rotating golden snitch tiebreaker: A dispute can apply for a tiebreaker decision, and a randomly selected admin is stuck with making the decision. WhatamIdoing (talk) 19:29, 10 January 2024 (UTC)[reply]
If the old text has been there a long time, there is a
MOS:RETAIN-style argument that if it was all that wrong someone would have changed it. Rfc's on most pages only attract a tiny fraction of our editors, often those most invested with a particular POV. The long-term wisdom of the crowds will often produce a better answer. Johnbod (talk) 17:25, 10 January 2024 (UTC)[reply
]
There's equally a Wikipedia:List of hoaxes on Wikipedia#Extant for 10+ years argument that we can't rely on people to have already fixed it. WhatamIdoing (talk) 19:32, 10 January 2024 (UTC)[reply]
I'm reading this and thinking, when did I propose that we should completely reverse one of the defaults from retaining the status quo to be to adopt the new. I then read my text below and see that when I summarised our
Editing policy
it looked like I was proposing that. I wasn't really. I was saying that policy says we should try to work with and improve the new, but it also says that if you can't then you can excise it. It doesn't say what we should do if we disagree on whether the text can be fixed enough to be retained. But it does say that we do encourage change and for editors to try to incorporate change. What I was really saying is I think we should drop the "default to the old", because that doesn't encourage change, and I wasn't proposing replacing that with "default to the new". I can see problems with that default too. It is swinging too much the other way. I thought we should be more neutral about whether changes were better than what we had, on a project that does indeed encourage change.
MOS:RETAIN is absolutely nothing to do with "if it was all that wrong, someone would have changed it". It is about preventing regional English variety disputes. Because we always get random folk coming along and noticing that an article has spelled something "wrong" and "fixing" it. It is entirely a dispute-prevention and dispute-settling policy. Per WP:UPPERCASE
, the words MOS:RETAIN sound like we have a MOS guideline that values keeping longstanding text. We don't.
I disagree with the idea that generally speaking text on Wikipedia demonstrates its goodness through age. Also the logic that says we should default to keeping the old because if the old was wrong, someone would have changed it, is, em, fundamentally flawed. You've got a rule that makes it hard to change, and thus a tendency to keep the crap. Most of our readers don't have the knowledge or inclination to fix the faults on Wikipedia. I can tell that because when I look at some random article, I can see absolute nonsense text added by some student class three years ago, on the assumption that "the wisdom of the crowd" would fix all their mistakes. Or I can read a barely literate lead that hasn't changed much for years despite being so painful to read you want to have a lie down after. Wikipedia is very much a work in progress and we absolutely shouldn't have a policy that discourages progress.
On the other axis, of inclusion vs exclusion, there are just too many areas I think where there are clear arguments in favour of defaulting to exclude (certainly BLP but also biomedical and science). There may be some areas where editors think it really isn't an important enough topic to care, but I think mostly when editors get passionate about Wikipedia not misleading or misinforming our readers, then they tend towards exclusion. Exclusion is also a good default because long term, if something does become important or accepted, then we can always include it later. Whereas, as we have seen, once material is in Wikipedia, it can be hard to get it out, with people giving entirely non-policy based reasons like that it has been there a long time so must be ok. -- Colin°Talk 10:51, 11 January 2024 (UTC)[reply]
You can certainly find a lot of "absolute nonsense text added by some student class three years ago", though it rarely sustains being completely wrong over any length of text, but then no-one is likely to mind in the least if you remove it. That is not what we are talking about here. Johnbod (talk) 18:47, 15 January 2024 (UTC)[reply]
Johnbod, I know we are only discussing contested text here. But the claim was that somehow our existing text is obviously better (and thus should be defaulted to) than any text (or absence) that some new contributor had offered simply because it has been here a long time. I think there are no end of examples of why that is not only wrong but also wrongheaded on a project that is based on "What we have here is not good enough, please help us improve it" model. If editors were more likely to make the text worse than make it better, we'd just lock all the pages and sit back and enjoy reading what people wrote in the past. -- Colin°Talk 08:55, 16 January 2024 (UTC)[reply]
I don't see anybody claiming anything like that. Johnbod (talk) 17:18, 16 January 2024 (UTC)[reply]
Maybe not here, but we do see that belief in practice. Some editors revert copyediting because the new version is "only" equally good as the old version. Many editors incorrectly believe that
WP:STATUSQUO is a policy requirement and that it requires them to prefer the old version over the new version if there's a dispute. WhatamIdoing (talk) 17:42, 16 January 2024 (UTC)[reply
]
Ok, but "not an improvement" is a valid reason to revert. Where there is an actual change some editors are just mistrustful of new/different material, especially if not referenced (or worse, not changing the old ref immediately after). Johnbod (talk) 18:52, 16 January 2024 (UTC)[reply]
Is it really a valid reason to revert? If that's being used as a polite euphemism for "makes the article worse", then it's a valid reason, but if you believe that the change literally makes no difference to the overall article quality, I don't think you should be reverting it. Why would you waste your time making no difference to the article's quality? WhatamIdoing (talk) 19:45, 16 January 2024 (UTC)[reply]
Johnbod, you wrote "If the old text has been there a long time, there is a MOS:RETAIN-style argument that if it was all that wrong someone would have changed it." Surely that is explicitly favouring old text merely for being old, on the assumption that many eyes have reviewed it and found it acceptable. But it assumes that otherwise, if someone found it unacceptable, that they would overcome the inertia required to actually edit it to something better (for example, they may need to go look up sources, which they may find they don't have access to, learn how to cite them, and so on), or remove it, and then manage to get their edit retained rather than reverted by someone assuming the old text was fine because it is old.
Many editors may be considering situations where they supported existing text because they wrote it or are imagining situations where they have come into conflict with someone removing or changing text they wrote. Maybe they aren't so strongly remembering the text they improved and didn't get any conflict over because whoever wrote that is not here or because it was obviously better. I wonder if there is a bias in our recollection that assumes other people are making bad edits, rather than realising that to everyone else, we are the other people.
Don't you see a conflict between editors favouring existing text and our fundamentals which are that we want editors to change what's here because we hope you can make it better. Anyone coming to Wikipedia, in good faith, to make an edit, is doing so because they believe they are making it better. So surely that should be the default? I mean for articles that aren't protected in some way and editors who are established, our edits are automatically "live" and "retained". It isn't like we need to prove they are better to someone before they show up, or that they are removed after a few days unless anyone confirms it. And reverting is officially discouraged by editing policy in favour of trying to accommodate the change. -- Colin°Talk 08:28, 17 January 2024 (UTC)[reply]
All these are factors, certainly, and there is such a conflict, but we know that quite a large proportion of (the minority of) edits that change texts aren't actually improvements. I don't see any workable "default" approach, either way. Each edit has to be looked at. We are still off-topic here. Johnbod (talk) 19:43, 17 January 2024 (UTC)[reply]
Size of English Wikipedia (1000 vol)
Speaking of subject-by-subject, this image splits Wikipedia's subject areas into these categories:
  • Biology/health/medicine,
  • Business,
  • Science,
  • Geography,
  • History,
  • Biography (living + dead),
  • Society, and
  • Culture/arts
I wonder whether editors would choose an include/exclude default differently for the different categories. Presumably for overlapping categories (e.g., BLP + pop culture), the more restrictive rule would apply. WhatamIdoing (talk) 16:46, 11 January 2024 (UTC)[reply]

While this specific RfC question has merit, I think a related question that actually comes up more frequently might be a more important thing to discuss: what to do when there is consensus for change, but no consensus on which. This happened at RFA Reform 2021, Article Creation at Scale, maybe Emoji Redirects?, and probably other mega-RFCs that I've forgotten. People agree the current approach isn't working, but every specific proposal for change fails, and we're left with the broken status quo. It would be nice if we had some sort of escape valve from those, like a mandate to implement the change that saw the least opposition, taking into account somehow when each proposal was made during the lifespan of the overarching RfC. Folly Mox (talk) 13:54, 10 January 2024 (UTC)[reply]

Oh, I thought we were talking about article content. Behind the scenes proposals are different, but ideas can change - compare the current Wikipedia:Village_pump_(proposals)#Increase_default_thumbnail_size_from_220px_to_250px with the last attempt, a mere decade ago. Johnbod (talk) 17:25, 10 January 2024 (UTC)[reply]

Responses

It's impossible to answer this because important information is missing. I need to know...

This is the place to say "I can't answer this, because you didn't say __________" (e.g., whether there were more admins on one side, whether the material in this new article is considered 'long-standing', what the article's subject area is, whether the material could realistically be moved to a different article, or whatever else is on your mind).

Feel free to ping WhatamIdoing (who wrote the hypothetical story above) in your comment, if you think she could supply the information you need.

  • Your comment here...

We have enough information. In principle, when there is truly no consensus, I believe we should err on the side of...

Most responses to this will probably be either exclusion or inclusion, though you should not feel constrained by those options. Please consider explaining your view with:

  • an example from articles you edit (e.g., "In articles about geography, editors might reasonably disagree about whether to mention _____, and in such cases I believe..."),
  • a common-sense or practical explanation (e.g., "In my experience with Wikipedia:Contentious topics, what helps settle difficult disputes is...") , or
  • a values-based explanation about what you think is best for Wikipedia's editing community and/or Wikipedia's readers ("In line with my favorite of our shared Wikipedia:Principles, namely...").

Remember, we're looking for editors' own opinions about what, in principle, is the normally right thing to do, when editors really can't form a consensus.

I think the former, the default to what we had before you came along, is bad for the project. It is based on an "old hands" mindset that has crept in that thinks all us old hands have created something wonderful and all these new editors are just making it worse. I think that is fundamentally against the principles upon which Wikipedia was founded and preserved at
WP:5P3: any contributions can and may be mercilessly edited and our default should be to try to incorporate and improve those edits. Our Wikipedia:Editing policy says "Even the best articles
should not be considered complete, as each new editor can offer new insights on how to enhance and improve the content in it at any time."
Wrt the latter, that content has to justify itself and get consensus to be added or kept if challenged, I think on balance that is better than the opposite, that we make it really really hard to remove or keep out the shit. Not all additions are useful, educational or encyclopaedic information. Some of it is bad data. Some of it misleading. Some of it just doesn't belong on this project. Nearly of our policies are about keeping the bad out. There's a reason for that. Our heart wants to keep adding but our heads know we have to keep a check on it. So, when there's a dispute, and editors can't agree, we should go with keeping it out. -- Colin°Talk 22:17, 8 January 2024 (UTC)[reply]
We have a bunch of policies for that. Escalating to involve more people via an RFC or noticeboards, for instance. IMHO the absolute worst situation caused by these attempts at "default outcome" policies is when people fail to escalate in that manner. More generally, though, while having long-running disputes that continuously fail to reach consensus is bad, I would argue that a "false consensus" created by policies that dictate a particular outcome and leave people who prefer that outcome with no reason to engage is even worse. Some problems are genuinely difficult and complex and unsettled even in the real world, and therefore are things we have to discuss a lot and revisit regularly. It's bad when policies waste editor time and effort, sure, but if something reaches the point of massive RFCs and still plainly has no consensus, that probably means it's complex and difficult and is deserving of a lot of effort to get it right. A "just say screw it and go with X" policy isn't helpful in those situations. Ultimately, when there's no consensus, what is probably needed is a compromise, rather than one side or the other trying to clobber the other with "we win automatically" policies. --Aquillion (talk) 21:31, 15 January 2024 (UTC)[reply]
Yes, we have lots of methods for dispute resolution, but what are editors supposed to do in the meantime, when none of those efforts produce a consensus? Right now, we are telling editors two contradictory defaults. I would like to have either one default or none (none being what @Amakuru seems to lean towards), but we need to stop having two contradictory ones.
Some intractable problems really aren't amenable to consensus. You can't name an article both Gdansk and Danzig, to give one of the oldest examples of this problem. You can't put a particular image both halfway in and halfway out of an article. You can't name someone's spouse and also not mention the spouse's name. Some of these are complex and difficult disputes, but many of them are really quite minor, too. WhatamIdoing (talk) 00:40, 16 January 2024 (UTC)[reply]
  • I don't think we have a default outcome in these situations. For one thing, there's a lot of other factors to consider and it's rare for something to be a complete void in that regard (eg. the level of consensus the material had formerly; how dangerous it is per policies like
    WP:STONEWALLing and encourages people in protracted disputes who prefer total omission but who probably have a wording they would otherwise accept to resist that sort of compromise. --Aquillion (talk) 21:31, 15 January 2024 (UTC)[reply
    ]
  • In general, assuming all the conditions described in the hypothetical example apply, and no compromise is possible (I know you already mentioned that no amount of rewriting would resolve the issue—but depending on context, other compromises may yet exist), I would lean towards "whatever the stable version prior to the discussion was". (
    the No Consensus section of the Consensus Policy can be trusted to be reflective of actual practice, this is already the common result post-no consensus outcomes.) When both sides hold equally strong, valid positions that do not run counter to existing policies, other considerations than the merits of the arguments need to be weighed to come to a decision. While it's situational and exceptions do exist, typically stability and not wasting volunteer time are among the next-strongest considerations. (As also evidenced by how many parts of en.wiki have this codified into The Way Things Are Done. ENGVAR, keeping pre-existing date order, not messing around with MOS style variations or reference style, COSMETICBOT, and so on.) I do however think the Consensus Policy has it right: describe what's typically done, but don't prescribe a hard default. AddWittyNameHere 03:32, 16 January 2024 (UTC)[reply
    ]
  • Reject this RFC Editing and discussion is the way forward in all situations. So two editors disagree there is
    WP:3O, still no resolution then have a RFC. For what this will solve it will create a thousand times more problems. This maybe stated as For one specific edge case, but that's not how any result will be used. For all it's good intentions it will be used by those wishing to include "alternative knowledge" as a way to retain the content, and create endless timesinks to remove it. These and more was expressed in my comments before this RFC. -- LCU ActivelyDisinterested «@» °∆t° 21:11, 16 January 2024 (UTC)[reply
    ]
    When two editors reach no consensus, there is WP:3O.
    When the RFC reaches no consensus (or perhaps multiple discussions and RFCs), there is... what else?
    You can't leave the fact halfway in and halfway out while editors prepare for RFC #6. What happens in the meantime, while one group is demanding that you remove the fact per Policy A and the other group is demanding that you include the fact per Policy B – and both groups are right about what their preferred policies say? WhatamIdoing (talk) 22:16, 16 January 2024 (UTC)[reply]
    As I said previously this is asking a question about an extreme edge case when any result won't be used in an edge case. It's all well and good asking hypothetical questions, but the actual impacts are what matter. -- LCU ActivelyDisinterested «@» °∆t° 22:52, 16 January 2024 (UTC)[reply]
    If we can figure out what happens in this edge case, we can figure out how to resolve the existing conflict in policy, which has caused "actual impacts". WhatamIdoing (talk) 01:50, 17 January 2024 (UTC)[reply]
    No we can't because as I said in the discussion coming into this your are asking the wrong question. You are asking a question about what to do at the end of consensus building, but the discussion it stems from is about the start of consensus building. The two situations are not the same. The discussion this stems from is what to do before any discussion, third opinion, or RFC has happened. So any outcome from this isn't applicable to that discussion, because you carefully crafted your question to the point it no longer applies. -- LCU ActivelyDisinterested «@» °∆t° 19:42, 25 January 2024 (UTC)[reply]
    I don't think I understand the distinction you're drawing here. One of the policies is explicitly about what ecitors should do when, "at the end of consensus building", there is no consensus. Why would me asking about what to do "at the end of consensus building" efforts not be relevant for figuring out what to do about a policy statement that only addresses actions taken at the end of the discussion(s)? WhatamIdoing (talk) 03:51, 26 January 2024 (UTC)[reply]
    The answer to the specific question you asked is that the situation before the disagreement should stand. If the content was pre-existing then it should be retained, if the content is being added it should be excluded (if after a well attended RFC the community can't even agree if the content is verifiable, I doubt it should be in the article). If, as is often the case in such situations, the fail to find consensus reflects a wider disagreement amongst sources then both sides should be included in the article. But again the answer is pointless to the discussion it stems from. -- LCU ActivelyDisinterested «@» °∆t° 19:47, 25 January 2024 (UTC)[reply]
    So you would make
    WP:ONUS altogether, since it indicates removal. WhatamIdoing (talk) 03:52, 26 January 2024 (UTC)[reply
    ]
    What would you recommend when there really isn't any status-quo option (e.g., an article that is only a few weeks old, and the contested material has been edit-warred over so steadily that neither side can claim to be 'winning')? WhatamIdoing (talk) 03:54, 26 January 2024 (UTC)[reply]
    No, absolutely and completely not. You can't just ignore my previous comment and come up with something I specifically didn't say. The question of QUO vs ONUS is one of how consent building starts, you RFC is specifically about what to do if at the end of that process there is still no consensus. Nothing coming from this effects the previous discussion at all. Again as I said in the discussion before this RFC and just above (and you ignored then, and have ignored again), you have crafted a question that has nothing not do with the discussion it comes from and so it will have no impact on that discussion. -- LCU ActivelyDisinterested «@» °∆t° 19:00, 26 January 2024 (UTC)[reply]
    AFAICT "If the content was pre-existing then it should be retained" is 100% incompatible with ONUS. Do you have a different understanding of what ONUS means for whether we retain pre-existing material for which "those seeking to include disputed content" have "The responsibility for achieving consensus for inclusion" and have failed to achieve that consensus? WhatamIdoing (talk) 19:04, 26 January 2024 (UTC)[reply]
    If you want to have an RFC about ONUS vs QUO, then have an RFC about ONUS vs QUO not some aside that you made up. If that issue isn't addressed then there is nothing to discuss because this is just an aside that doesn't address the issue.
    And no I don't agree with you assessment, in fact that disagreement is the basis of the discussion this comes from. The fact it isn't resolved by your RFC question just shows thr issues with your RFC question. -- LCU ActivelyDisinterested «@» °∆t° 19:10, 26 January 2024 (UTC)[reply]
    Tell me how to reconcile these two. How exactly do I retain the long-standing content after failing to achieve consensus to include it? If you don't think it's possible for me to understand, then imagine that you're trying to convince someone like @Bon courage instead of me. WhatamIdoing (talk) 19:42, 26 January 2024 (UTC)[reply]
    O this again! I remember this issue and IMO it's true WAID has identified an issue, and that the community has failed to (or doesn't want to grapple with) it. I've seen some interesting incidences recently of pointy uses of
    WP:ONUS where an editor removes something obviously well-sourced, claims no-consensus, and then relies on the tiresomeness of going through process of establishing consensus to get their way. Bon courage (talk) 20:11, 26 January 2024 (UTC)[reply
    ]
    But that is my point. There are editors behaving disruptively by requiring other editors to get consensus for an edit, but this question is about what to do after consensus isn't achieved. It's the wrong question.
    Editors shouldn't have to get permission to edit, it's against BOLD and the spirit of Wikipedia. The issue isn't ONUS, it's distuptive behaviour. In the same way that QUO isn't the problem with editors
    WP:STONEWALLING. This won't solve the behavioural issue it will just make legitimate situations where ONUS applies a massive timesink for the community.
    There is an issue, but this is the wrong question and wrong RFC to fix it. It has been specifically designed to highlight only one small facet of a larger problem. -- LCU ActivelyDisinterested «@» °∆t° 22:20, 26 January 2024 (UTC)[reply
    ]
    “Editors shouldn’t have to get permission to edit”… true. But… remember that removing information that some other editor has added is just as much “an edit” as adding information was. Neither edit requires permission. However, if there is a dispute over these two edits, then discussion and consensus determines which will prevail. What WAID is asking is: What if there is no consensus? Blueboar (talk) 22:52, 26 January 2024 (UTC)[reply]
    Then if there is going to be an RFC about ONUS vs QUO, let's have an RFC about ONUS Vs QUO. Not an RFC designed to highlight one part of the disagreement, that goes to great lengths to mention neither. Things should be done in the light not in shadow. -- LCU ActivelyDisinterested «@» °∆t° 14:42, 27 January 2024 (UTC)[reply]
    Not exactly.
    WP:QUO
    doesn't apply after the discussion's over (go read it...). This problem touches small pieces of multiple policies, and which ones might benefit from changes depend on what editors believe is the best practices.
    For example, if editors decided to take a hard-line exclude-everything-unless-agreed approach, then we should be reconsidering the second sentence in
    WP:DUE
    to point out that when there is a dispute about whether a POV is "a minority" or "a tiny minority", the default is to exclude.
    And, of course, if the best practice is inclusion, then it might be a different set of policies and a different set of changes altogether. For example, ONUS would get a re-write to clarify that it's only a procedural point about who has to start the discussion and has no bearing on what happens if the discussion fails to produce a consensus. WhatamIdoing (talk) 19:12, 27 January 2024 (UTC)[reply]
    And as I said, and as your comment has mentioned, the disagreement is about the starting point of consensus - when editors misuse a policy to force a long-winded consensus building discussion. But this RFC question is very specifically as about what should be done if that consensus building discussion fails. -- LCU ActivelyDisinterested «@» °∆t° 14:47, 27 January 2024 (UTC)[reply]
    It sounds like you see ONUS as meaning "the person who wants to include the material has to start a discussion", and saying nothing about what happens if that discussion does not produce a result (either way). WhatamIdoing (talk) 18:39, 27 January 2024 (UTC)[reply]
    I'm saying and have always said, that this RFC doesn't cover the discussion properly. -- LCU ActivelyDisinterested «@» °∆t° 18:21, 11 February 2024 (UTC)[reply]
  • Inclusion. In this rare and very specific situation the goal of providing information should prevail. - Butwhatdoiknow (talk) 21:51, 16 January 2024 (UTC)[reply]
  • We should consider what is most useful to our readers. More information is probably better. Other ways to go might be third opinion, widen the RFC to a more central board, put up with a slow revert war, and possibly block the perpetrators from the article in question. Graeme Bartlett (talk) 05:02, 19 January 2024 (UTC)[reply]
    I'm curious that a few editors have suggested more information is probably better. But in the scenario posted, an equal number of editors have apparently argued equally persuasively (or unpersuasive) that the article would be better without the information. For example, they consider it misleading, or in the wrong place or insufficient weight to be appropriate to mention. Not all "information" is better. For example, "information" that Keir Starmer "failed to prosecute Jimmy Savile", as claimed by the then prime minister Boris Johnson, lead to death threats and a persistent false belief that Starmer actually defended Savile, that polls show impacts whether people might vote Labour. While that "information" is easily dismissable because we do (fortunately) have reliable sources arguing it is a misleading half truth, there are far more examples where, for example, politically motivated press run with stories that are misleading, and more neutral sources simply don't mention the nonsense. We end up in this position where it is left to editors to work out whether on balance the information is encyclopaedic and neutral, and often if both sides are equally represented, we have a stalemate. I don't think it is safe to assume, if editors argue about inclusion, that inclusion is the wisest default for our readers. -- Colin°Talk 09:10, 19 January 2024 (UTC)[reply]
    "Where is the knowledge we have lost in information?" Information can be antithetical to knowledge, which is what Wikipedia aspires to contain. Bon courage (talk) 18:29, 11 February 2024 (UTC)[reply]
    Knowledge comes from information. IMO it’s *not* antithetical to knowledge. --Dustfreeworld (talk) 12:16, 13 February 2024 (UTC)[reply]
    Which is why I said "can be". Putting forward a carefully chosen selection of "facts" is a classic misinformation tactic, and anti-knowledge. Bon courage (talk) 12:20, 13 February 2024 (UTC)[reply]
    No information, no knowledge.
    I never said that we don’t need to guard against misinformation.
    I don’t think everything we include needs to be “fact”. But, we need to state clearly when it’s not a fact. --Dustfreeworld (talk) 12:30, 13 February 2024 (UTC)[reply]
    A discussion of the difference between information and knowledge would IMO be fascinating. Perhaps we could have it over on my User_talk: page instead? WhatamIdoing (talk) 17:19, 13 February 2024 (UTC)[reply]
  • There is no black-white solution; it depends on specific scenarios. Further, Wikipedia has existing policies and procedures for resolving disagreements. Path2space (talk) 19:33, 20 January 2024 (UTC)[reply]
    @Path2space, we currently have one policy that says to remove the content unless there is consensus to keep it, and another that says to keep the content unless there is a consensus to remove it. Which policy do you think editors should be following? WhatamIdoing (talk) 05:28, 21 January 2024 (UTC)[reply]
I'd bother to disagree but will follow your instruction above: "Don't tell us what this or that policy says ...". Peter Gulutzan (talk) 18:25, 21 January 2024 (UTC)[reply]
WAID, you haven't expressed the conflict here as accurately as you did elsewhere. I'm not sure keep/remove are the right words to use in the policy examples.
One policy is exclude unless there is consensus to include, it doesn't matter if the disputed text is a new addition or longstanding text that is only now being disputed. But the other policy is to restore to the previously existing text unless there is consensus to change it, it doesn't matter if the change is addition, removal or modification. -- Colin°Talk 09:44, 25 January 2024 (UTC)[reply]
Which, under the specific circumstance of "long-standing material" with no consensus, means that wikilawyers and other editors cite policy #1 (as if it were the only one that exists) when we want to remove it, and policy #2 (equally as if it were the only one that exists or matters) when we personally want to keep the material in question. Unless you know the policies as well as the top 1% (or top 0.1%), you have very little chance of discovering that you're being manipulated by the editor who claims that "the policy" requires things to go my way. There is a conflict; we need to know what editors believe the best practice is before we can figure out how to remove the conflict. WhatamIdoing (talk) 15:29, 25 January 2024 (UTC)[reply]
I don't disagree with that, just your choice of "keep/remove" to describe both policies. We have a policy ONUS that allows text to be "removed" if there isn't consensus to include it, but that same policy might also be invoked if someone had merely suggested the addition on a talk page (so there's nothing to remove), or when it had already been removed prior to discussion. That policy can be used to argue against putting it back or adding in the first place. The other policy, NOCON, could similarly be cited to "remove" recently added text, or "keep" recently removed text. Both policies can be used to "remove". And both policies can, with such ambiguous terms, be used to "keep", where "keep" might mean "keep the existing text that you removed" or "keep it how it was before you added your text".
Best to keep the language clear and unrelated to what edits are needed to bring it about. One policy is on the include/exclude axis wrt disputed text, and another is on the new/old axis wrt disputed text. What edits are required to achieve these results is a separate matter. -- Colin°Talk 08:42, 26 January 2024 (UTC)[reply]
  • There is a “third option” that lies between inclusion and exclusion… which is “temporarily retain the disputed material… BUT… tag it with an appropriate tag so readers know it under discussion.” Perhaps we need to explore this option a bit more. Blueboar (talk) 13:29, 25 January 2024 (UTC)[reply]
    I don't think that "option" is really in the spirit of WAID's question unless your "temporarily" is until the heat death of the universe. There is already
    WP:STATUSQUO
    , which is an essay that advises a slightly different approach, which is to go back to what existed before the dispute, whether that means restoring text that got removed or removing text that got added or un-rewording text. Maybe that's what you meant anyway. The point here is we tagged the dispute, we discussed it, and we still haven't found consensus. Then what?
    If you think that behavioural advice, for what to do during a debate, is worth reconsidering, then probably the first step is to discuss on the essay talk page. But that advice isn't in conflict with any of our no-consensus P&G. -- Colin°Talk 15:18, 25 January 2024 (UTC)[reply]
    The other difficulties I foresee with adopting that as the solution are:
    • We have
      Wikipedia:No disclaimers in articles
      , and "an appropriate tag so readers know" would count as a type of disclaimer.
    • All of those tags operate under the principle that when the discussion stops, the tag can be removed, and we can't realistically expect editors to endlessly discuss the same thing over and over and over for months/years/decades/the rest of their lives.
    WhatamIdoing (talk) 15:37, 25 January 2024 (UTC)[reply]
  • Another solution: Instruct closers to NOT close with a simple “No Consensus” but with either: “No Consensus - Keep pending further discussion” or “No Consensus - Omit pending further discussion”.
In other words, the closer has to make a decision … but one that acknowledges the lack of consensus and the need for further discussion… a decision that can intentionally be easily overturned if/when consensus actually forms.
It doesn’t really matter Which decision the closer makes. Some closers will usually lean towards “keep” and others will usually lean towards “omit”… but that’s Ok. It is understood that such closures are temporary in nature - telling the disputing editors what to do pending an actual consensus (eventually) forming. Blueboar (talk) 15:45, 27 January 2024 (UTC)[reply]
I like this solution, and it might be particularly helpful for the fairly common situation in which there isn't a a true consensus, but the discussion leans a little to one side. WhatamIdoing (talk) 19:15, 27 January 2024 (UTC)[reply]

My knee-jerk reaction, and how the way this is wrong, shows that the question is ill posed

So here's my knee-jerk reaction. You keep the fact, because it's easier to do. If more evidence arrives or consensus changes you can effortlessly carry on keeping it, or with minimal effort delete it. However had you deleted it, you may never be aware that it has now become inclusion worthy.

Unfortunately this is now knowledge that can be added to the premise of the question. In other words: what if, given that this is taken into account, we are in a perfect tie? The same reasoning applies to any other valid answer that provides a reason to keep or delete. Hence no answer can ever affect the totality of the question "What if there's a tie, when we have accounted for everything?"

A mathematical sidenote: We are in theory talking about a point on a line (or if you prefer an n-1 dimensional boundary in an n-dimensional space) so the probability of being on this point is zero, rendering the question moot in another aspect.

All the best: Rich Farmbrough 19:06, 19 March 2024 (UTC).[reply]

Summing up

Andrevan, Colin, Johnbod, ActivelyDisinterested, Blueboar, Folly Mox, SMcCandlish, Aquillion, L3X1, Dustfreeworld, Slacker13, Bon courage, Peter Gulutzan, Path2space, Graeme Bartlett, Butwhatdoiknow, AddWittyNameHere, Amakuru, Scribolt:

Hello, all (and anyone else watching this page).

Thank you for your comments above. I wonder if you'd be willing to help with a sort of collective summing-up. I realize that I'm proposing a bit of an unusual process, but my main goal is to find out what you all think, rather than to make a specific decision or to "win" a dispute, and I think that hearing a little more from you will help. Also, you're all pretty smart and experienced editors. I don't think that we need someone else to tell us what we said ourselves (yet, anyway). ;-)

Along those lines, if you're willing to give me a few more minutes of your time, please consider one request and a couple of questions:

  1. Request: Is there a comment from someone else that you thought was helpful, interesting, or insightful? For example, you might choose a comment that helped you better understand a view opposite your own, or that helped you solidify your own view, or that you keep thinking about.
  2. Question: In this discussion about disputes ending in no consensus, do you feel like there is support for the idea of a "status quo" default after discussions have ended?
  3. Question: In this discussion about disputes ending in no consensus, do you feel like there is support for removing all/nearly all disputed information until there is a consensus to include it?
  4. Question: In this discussion about disputes ending in no consensus, do you feel like there is support for keeping all/nearly all (non-BLP) disputed information until there is a consensus to exclude it?

Thank you all for your help. I really do appreciate it. WhatamIdoing (talk) 06:33, 11 February 2024 (UTC)[reply]

Here are my answers:
  1. I keep thinking about this comment from Blueboar, about asking editors who writing closing summaries to specify what action should be taken (e.g., "No consensus, which means ______ in this case").
  2. I was surprised by how unimportant
    WP:NOCON
    approach).
  3. I feel like there was some support for removing sourced information that some editors don't want (the
    WP:ONUS
    approach).
  4. I feel like there was some, but not as much, support for keeping sourced information that some editors don't want. I don't know what that could mean for the Wikipedia:Editing policy, or for Wikipedia:Be bold or (kinda sorta) for our way of talking about Wikipedia and its goals in general.
What do you think? WhatamIdoing (talk) 06:45, 11 February 2024 (UTC)[reply]
I think I've come to to think a key aspect of all this is what "no consensus" means. If it means truly, really no consensus after there's been well-publicised/attended community consideration then I'd be happier formalising some kind of consequence for that. But if it just means one or two editors rocking up at an article and making a fuss then I see anything in this area as a potentially problematic gateway to wikilawyering. The current NOCON/ONUS ambiguity has remained unchallenged I think because in practice it works quite well in a kind of 'European rules' rather than 'American rules' way. The power is granted via ONUS to remove anything without consensus, but NOCON can be invoked with a shrug if people will wear it. Bon courage (talk) 06:57, 11 February 2024 (UTC)[reply]
This seems well reasoned. -- LCU ActivelyDisinterested «@» °∆t° 14:45, 11 February 2024 (UTC)[reply]
Regarding your comment about
WP:QUO, that recommended procedure only applies before it becomes clear that there is no consensus. - Butwhatdoiknow (talk) 17:40, 11 February 2024 (UTC)[reply
]
QUO is frequently (mis-)invoked as prescribing an outcome that applies after discussions have ended. The pattern that Colin identified (about the risk that a clear rule for a True™ No Consensus being invoked at the start of a discussion to "win" now, without allowing space for a full discussion) is plausible to me precisely because so many editors have claimed that our rules around reverting to the status quo ante bellum apply far more broadly than one might find from reading the WP:QUO section itself. Think, too, about how editors perceive
WP:BRD
, especially if they've never read it ("BRD says you have to start the discussion"; "You're required to follow BRD"; "BRD says I can revert you but you can't revert me"...).
I expected more editors to explore whether QUO would work as a better post-dispute rule than inclusion vs exclusion. WhatamIdoing (talk) 20:33, 11 February 2024 (UTC)[reply]
  • My take away is that we have no consensus on what to do when there is “no consensus”.
    And that may be a good thing. I understand the desire to have a “default” that will resolve disputes expeditiously, but sometimes disputes simply need more time to be resolved. Intentionally NOT having a “default” encourages conversation and compromise. It gives us flexibility to explore options beyond “the rules”. Blueboar (talk) 16:50, 11 February 2024 (UTC)[reply]
  • I agree that a formal consequence would be helpful when there is truly, really no consensus. (I disagree with the statement "The current NOCON/ONUS ambiguity has remained unchallenged" and with the theory that it remains in place because it works (as opposed to because there are editors on either side that are not interested in compromise).)
    I have not done an analysis of the support in this discussion for what that consequence should be. (Personally, I'd go with "keep.") - Butwhatdoiknow (talk) 17:57, 11 February 2024 (UTC)[reply]
  • I had difficulty in forming a comment on the original question because I don't agree with the premise that there should be a single way to handle the situation. I think the nature of the disputed information plays a role in what the community thinks should be done, and even the state of the article. For example, in a biography, the degree of relevance to be included might be disputed. If the info could have a significant effect for the person, then I think there would be a tendency to keep the info out until there was a consensus for inclusion. If the info was a piece of personal trivia that had been in the article a long time, then there might be a tendency to keep the info. However if there were already plenty of other trivia that help round out a more complete view of the subject, then editors might impose a higher burden and pull the info until consensus was reached. I understand why a single approach might be desirable, but I don't think a rigid approach matches what the community wants in practice. isaacl (talk) 18:57, 11 February 2024 (UTC)[reply]
    @
    WP:ONUS to exist, or at least for it to say that the default is to exclude content until a consensus is formed; it could instead say that when there is a dispute over whether to include material that is both verifiable and cited, then that decision is made according to other policies (primarily WP:EP, WP:CONS, WP:BLP, WP:NPOV, and WP:NOT). WhatamIdoing (talk) 20:42, 11 February 2024 (UTC)[reply
    ]
    If you mean the proposal for the discussion evaluator to indicate what should be done with the content in question, I'm not sure what I think of it yet. If you mean that we have no consensus on what to do when there is no consensus, as I alluded to, I don't really like the framing of the question. I think that ideally the interested participants would agree upon a compromise interim approach that would best serve the interests of readers. However I acknowledge that can be difficult, as it's hard enough to keep participants focused and engaged in a lengthy dispute, and prolonging it by having to discuss an interim approach is non-ideal in other ways. isaacl (talk) 22:54, 11 February 2024 (UTC)[reply]
    I see that my comment above is not entirely clear. I meant only that you two seem to agree that a one-size-fits-all response may not be the best approach. I didn't mean to imply that you agreed on anything more than that. WhatamIdoing (talk) 03:26, 12 February 2024 (UTC)[reply]
  • I keep seeing
    WP:ONUS
     in this discussion. I believe it might have been misinterpreted. Per WP:ONUS,

    While information must be verifiable for inclusion in an article, not all verifiable information must be included.

    Consensus may determine that certain information does not improve an article.

    Such information should be omitted or presented instead in a different article.

    The reseponsibility for achieving consensus for inclusion is on those seeking to include disputed content.

    I don’t think ONUS means “exclude when no concensus”
    It actually means exclude the information (or presented instead in a different article) only when these conditions are met:
    • Consensus determine that certain information does not improve an article.
    • AND, no further consensus for inclusion of that information can be achieved (those seeking to include disputed content are responsible for achieving this consensus).
  • The prerequisite for exclusion is “Consensus determine that certain information does not improve an article.”
    In short, our default for no consensus is include, which aligns with our goals and EP. Likely an unnecessary Rfc for no consensus, but a needed Rfc for policy clarification. --Dustfreeworld (talk) 21:05, 11 February 2024 (UTC); 23:41, 11 February 2024 (UTC)[reply]
    • The statement that "The responsibility for achieving consensus for inclusion is on those seeking to include disputed content" has commonly been interpreted as "Until you have achieved that consensus, you don't get to include it". WhatamIdoing (talk) 21:57, 11 February 2024 (UTC)[reply]
    Common ≠ Correct --Dustfreeworld (talk) 22:10, 11 February 2024 (UTC)[reply]
    Yup, I would agree that 90% of the angst over “no consensus” is due to this one single sentence. I find it a useful tool when rewriting and cleaning trivial fluff from articles… but it does get misused. It should be used like a scalpel… and too often it is used as a hammer (and as they say: “to a hammer, everything looks like a nail”). Blueboar (talk) 22:22, 11 February 2024 (UTC)[reply]
    Common errors are still errors, but when the question is what the Wikipedia community's actual policy is, then what editors do or accept is more important than what the words on a page say. When consensus (with a lowercase c) is the main rule of a wiki, then if editors commonly agree that a policy sentence means ____, then that's what it actually does mean. The goal (as explained in WP:PG and WP:NOTLAW) is for the written policies to reflect the practiced policies. If the community accepts that this sentence means I get to remove everything until you provide written evidence of consensus to include it, then at some level, that's what that sentence actually means, even if it doesn't look like it. (If you'd like to see how editors use that sentence in practice, then this set of search results may be helpful. Expect to see a lot of editors saying some variation on "The WP:ONUS is on you to get consensus".)
    My goal, as someone who likes to work on policy, is to make the wording of the written policies reflect the community's actual practices and what they intend for the policies to say. I do this because I want new folks to have a fair chance and because I want to avoid preventable disputes. The purpose of this RFC is to help me more clearly understand what the community believes these policies ought to say, so that I've got a better chance at making them clearly reflect the community's goals (and not, e.g., my own). WhatamIdoing (talk) 22:49, 11 February 2024 (UTC)[reply]
    IMO it’s not “community accepts that”, *if* one believes it’s “community accepts that”, they should believe “community misinterprets that”, or “community misled (by each other for a long time) that” instead. (BTW, I think the shortcut “WP:ONUS”, with the use of the word “onus”, is a source of misinterpretation as well.)
    That said, I’m glad that we have this Rfc, so that we have a chance to have things clarified and corrected. :-) --Dustfreeworld (talk) 23:18, 11 February 2024 (UTC); 03:43, 12 February 2024 (UTC)[reply]
    I think the ultimate issue is that there are conflicts between different desired behaviour, and we can't define hard lines when one should be followed versus another. Generally, for editors to be most productive, it's helpful for someone making a change to take responsibility for ensuring that the change is in alignment with Wikipedia guidance, including having consensus support as needed. But there's also an acknowledgement that it's impractical to require every change to undergo a consensus discussion prior to being made, so there's a weak assumption that long-standing text has had some degree of practical review from users reading the article. Which approach to follow is situation-dependent and requires subjective judgement, and in the real world, getting along with others to figure out how to move forward. isaacl (talk) 23:32, 11 February 2024 (UTC)[reply]

To answer this whole thread from the top:

  1. WhatamIdoing's observation, though it came later, is spot-on: when the question is what the Wikipedia community's actual policy is, then what editors do or accept is more important than what the words on a page say. When consensus (with a lowercase c) is the main rule of a wiki, then if editors commonly agree that a policy sentence means ____, then that's what it actually does mean.
  2. Defaulting to the status quo ante is what is done with everything when no consenus results. No consensus to delete a page? It is kept. No consensus to move an article? It is not moved. Etc. See this internal search for how often this is employed. It's also a good proof of WhatamIdoing's assessment above: we have no page that lays out SQA as a procedural rule (there seems to be nothing by a brief mention of the idea at
    WP:NOCON, again without using the SQA term), yet it remains deeply embedded in all WP process. In short, consensus exists on how WP operates, regardless whether the consensus on a particular point has been written down as a rule somewhere. SQA is generally interpreted as status quo ante bellum, that is, the state of things before the dispute erupted. So, if someone made a change that led to a dispute, the SQAB is the state of the material before that change. There are cases in which the SQA or SQAB get explicitly discussed and consensus cannot agree that version was desirable either; we have a specific rule to default to what was done by the "first major contributor" AKA what was done in the "first non-stub version" (or first relevant one that included material to which the recent dispute could pertain); this rule can be found in most of the WP:VARS
    provisions, but it is a last resort, not a default.
  3. Removing disputed information until there is a consensus to include it is the general practice.
    WP:IAR
    only applies when ignoring a rule will objectively, certainly improve the encyclopedia.
  4. "do you feel like there is support for keeping all/nearly all (non-BLP) disputed information until there is a consensus to exclude it" – Definitely not, given all the above. To keep something, it would need to be firmly supported in a
    WP:NOTINDISCRIMINATE
    and other policies also have to be satisifed.

To move on to the

gaming the system: IMO it’s not “community accepts that”, it’s “community misinterprets that”, or “community misled (by each other for a long time) that”. (BTW, I think the shortcut “WP:ONUS”, with the use of the word “onus”, is a source of misinterpretation as well. This is a bad-faith assumption about the entire community, that it is collectively stupid and doesn't know what it's doing, and is so confused that it is misled by itself (i.e. is completely dysfunctional); combined with the extreme hubris of deciding that this one person knows the "right" answer and is in a position to deliver it to the community and show them the error of their collective ways. There is no chance of any kind that such an actual misinterpretation of ONUS is going to grow any legs.  — SMcCandlish ☏ ¢ 😼  01:15, 12 February 2024 (UTC)[reply
]
@User:SMcCandlish, I would say your
our editing policy on community’s consensus, and these pages on shortcut usage: [3][4][5]. Thanks and regards, --Dustfreeworld (talk) 03:13, 12 February 2024 (UTC)[reply
]
You must be kidding. You have dragged out what could have been a simple RfC question into a very long-winded discussion of hypotheticals and theory, all the while expounding your "novel" hypotheses about WP policy and how it operates, and castigating the entire community while you're at it. You cannot possibly be surprised to meet with detailed whys and wherefores, as well as pushback against your policy misinterpretations. Attempts to lecture long-term editors, on what the community is all about and what its policies actually mean, don't amount to much coming from short-term and low-activity-level quarters. Any time anyone says "TL;DR" in response to being refuted, it means they cannot mount a rebuttal, and amounts to a concession. If you can't understand the difference between me quoting and citing the contents of specific policies in detail, as specifically applicable here, versus some rando just bandying about shortcuts to material they haven't read and don't understand, then it's no particular wonder that your input into this discussion has been along
FUD lines instead of elucidating anything. Finally, if you treat any disagreement with and criticism of your input as "WP:PA" (what was that you were hypocritically saying about shortcuts again?), then you are not going to do well here; this project is characterized by frequent editorial disagreements. Go actually read Wikipedia:No personal attacks; nothing in this discussion qualifies (from me or anyone else). No one is victimizing you here.  — SMcCandlish ☏ ¢ 😼  07:11, 12 February 2024 (UTC)[reply
]
@User:SMcCandlish; in your post you are using words like: kidding, castigating, pushback against, refuted, rebuttal, disagreement, criticism, victimizing ... If all you want is
winning, Ok, you win. :-) Be well. Sincerely,--Dustfreeworld (talk) 11:45, 12 February 2024 (UTC)[reply
]
What I observe, at the coal face, is that
WP:ONUS is commonly invoked when a persistent editor wants to add bad content to an article, often with a bit of edit-warring. They'll be told "The ONUS is on you to achieve consensus for your desired change". I have, a few times, seen it abused in the opposite direction: i.e. an editor will remove some good content from an article and try to force a lot of process to establish 'consensus' before it can go back. Bon courage (talk) 03:48, 12 February 2024 (UTC)[reply
]
This gets back to your comment above that the real rules are whatever editors will put up with. If we think that _____ is best for the article, then nobody (except me) is going to get picky about what words are used to explain the right thing to do. WhatamIdoing (talk) 04:44, 12 February 2024 (UTC)[reply]
That may actually often be the case, though ONUS is probably not what to base it on (whether one wants to be "prickly" about it or not). Ultimately, what goes into an article is going to be a matter of general consensus, informed by policies & guidelines, by sources, by analysis of the reliability of the sources, and generally by common sense. Even most of NOT and many other policies are wide open to a lot of editorial discretion. This often leads to A) suppression or including of details that someone else would rather include or suppress, respectively, especially if there's a
WP:DR processes, most of opening an RfC (few people seem to have the patience for other DR mechanisms most of the time). In short, the answer generally comes down to fixing the "only two of us care and can't agree" problem by getting more editors to care and give their input.  — SMcCandlish ☏ ¢ 😼  07:11, 12 February 2024 (UTC)[reply
]
Dustfreeworld, the assumption that others cite policies and guidelines correctly does not, as you have seen, hold up very well under scrutiny. Editors mostly learn the rules through a kind of
WP:MDPI was interpreted as a total ban rather than as advice to conduct case-by-case review). One consequence of this is that our written rules diverge from the practices that our editors believe to be the correct ones. WhatamIdoing (talk) 04:41, 12 February 2024 (UTC)[reply
]
About this: This is a bad-faith assumption about the entire community, that it is collectively stupid and doesn't know what it's doing, and is so confused that it is misled by itself (i.e. is completely dysfunctional)...
@SMcCandlish, isn't that ...kind of reality, though? For example:
  • The median editor in 2023 has made a total of five edits (not five edits during 2023; five edits ever, including at least one during 2023). IMO if half the community has only made five edits ever, that means that much more (possibly much, much, much more) than half the community doesn't know what it's doing.
  • We don't really teach people how to edit. We give them
    lies to children
    instead of accurate explanations. We push for compliance instead of full understanding. Isn't the logical outcome of that system that the editors are misled by other editors?
WhatamIdoing (talk) 04:54, 12 February 2024 (UTC)[reply]
Well, no one reads and understands policy other than the editors who actually build this place. "Editors" who have made a total of 5 edits in their entire lives don't really matter, either to understanding of policy or to the current reality and future of the project. WP is weird in that it allows inactive accounts to linger forever (for attribution reasons), but it has practial downsides. "The community" really consists of the active editors participating in discussions and building the content; not the zillion accounts that see nearly no activity. Their very inaction makes their voices not heard.

The answer to the problem of some

WP:TEAHOUSE, and so on. This is one of the most complex projects in human history, so it's not surprising that it has a learning curve. But it's not unique in this. Try getting started on GitHub, or becoming a respected community member at StackExchange or any of its sub-units. Various complex systems for human collaboration have steep learning curves, the steeper the more complex the system is. There doesn't seem to be a magic-bullet solution for this. In a "former life" in NGO work, I noticed this also with offline volunteer coordination; it's actually quite difficult and time-consuming to train up a volunteer, anywhere, to do anything.  — SMcCandlish ☏ ¢ 😼  07:11, 12 February 2024 (UTC)[reply
]

It's not necessarily a case of some WP:Randy in Boise "editor" throwing around false policy claims while trying to push a PoV. It's often a case of an editor who genuinely doesn't understand (see, e.g., all the editors who believe BRD is mandatory) or who is trying to get the right outcome with the minimum of effort (so "I know it's an interesting idea, but that kind of source is not really what we want to see for this particular type of claim, and anyway, it would only belong in this sub-article anyway" becomes "You have WP:DAMAGED the WP:ARTICLE and if you do this again, I will have you WP:BLOCKED for WP:VIOLATING all the WP:UPPERCASE, which must WP:NOT happen.")
If you want to define The Community™ more narrowly (already achieved extended confirmed + recently averaging at least one edit per day), then there are about 9,000 of us. Even among that smaller group, a lot of people don't carefully read the policies and guidelines. WP:V, for example, is watched by 130 recent editors. That's plenty to catch vandalism, but it's also less than 2% of The Community™ (if there are 9,000 of us), so even if 100% of the watchers saw a change to that policy, it still means that 98% of The Community™ would not. (This is doubtless why it seems to take about two years before changes to the written policies get noticed by any significant fraction of The Community™.) WhatamIdoing (talk) 07:31, 12 February 2024 (UTC)[reply]
I think we've got a bit distracted in a meta discussion about community behaviour vs what appears to have been written in P&G. Dustfreeworld I think you misinterpreted a perfectly clear policy statement. While SMcCandlish wasn't particularly kind about telling you this, and WhatamIdoing got distracted with your "Common ≠ Correct", that policy is clear. I think you either didn't read the final sentence carefully enough or you are so keen for policy to be otherwise that you thought it said differently. The middle sentence "Consensus may determine that certain information does not improve an article" doesn't indicate a default in the absence of consensus, that's the job of the last sentence. And a default of "include" doesn't actually align with our goals. Editing an encyclopaedia involves decided what to include, how and how much to include, or to exclude, or to include somewhere else, or to include something else instead. All of those are entirely pursuing our goals. If inclusion was clearly "the goal" nobody would be arguing and failing to reach consensus. Nearly all our policies are about excluding stuff. -- Colin°Talk 09:45, 13 February 2024 (UTC)[reply]
IMO it would be great if we can stay focus on discussing policies and how to improve the project, instead of making guesses / assumptions / judgements against other good-faith users. I don’t believe you are one of those, Colin.
The middle sentence "Consensus may determine that certain information does not improve an article" is the context and prerequisite of the last sentence. And a default of "include" *does* actually align with our goals. As to what our goals are, we’d better listen to our founders:
  • Jimmy Wales
    • Imagine a world in which every single person on the planet is given free access to the sum of all human knowledge. That's what we're doing.
  • Larry Sanger
    • Our goal with Wikipedia is to create a free encyclopedia--indeed, the largest encyclopedia in history, both in terms of breadth and in terms of depth. We also want Wikipedia to become a reliable (probably, peer-approved) resource.
  • https://en.wikipedia.org/wiki/Wikipedia:Free_encyclopedia
    • The Wikimedia community aims to be the vanguard of a knowledge revolution that will transform the world ... Through this work, every single person on the planet will have easy low cost access to free knowledge to empower them to do whatever it is that they want to do ... it always puts forward its best effort to ensure that free knowledge really is free.
Of course we need to have balance on what to include or exclude, but I don’t think “nearly all of our policies are about excluding stuff”. It’s more like a personal assumption/opinion. Our goal is to have “the sum of all human knowledge”, but *not* “excluding stuff”. --Dustfreeworld (talk) 11:46, 13 February 2024 (UTC)[reply]
There's a common misconception that the "sum of knowledge" means "loads of information", It doesn't; knowledge is a particular kind of thing beyond mere information, and the sum of it is a reduction of that. Bon courage (talk) 12:11, 13 February 2024 (UTC)[reply]
Knowledge comes from information. Please see my reply to you above. Thanks. --Dustfreeworld (talk) 12:21, 13 February 2024 (UTC)[reply]
Yes, and Wikipedia aims for the "sum of knowledge", not "all the info". Bon courage (talk) 12:25, 13 February 2024 (UTC)[reply]
I never said we should include “all the info”. We should exclude the info if “Consensus determine that certain information does not improve an article.” --Dustfreeworld (talk) 12:33, 13 February 2024 (UTC)[reply]
If the consensus that “the info doesn’t improve an article” can’t be established, it’s very likely that the info *will* improve the article. If no other policies (e.g. BLP MEDRS) warrant it’s exclusion (which should have been discussed already in the consensus discussion), the info should be included. --Dustfreeworld (talk) 12:39, 13 February 2024 (UTC); 15:30, 13 February 2024 (UTC)[reply]
For example, if the info violates BLP WP:MEDRS, obviously it won’t improve the article. Clear consensus can be established easily and have the info excluded. --Dustfreeworld (talk) 12:54, 13 February 2024 (UTC); 15:30, 13 February 2024 (UTC)[reply]
Forgive me if I misunderstand, but you seemed to arguing that "a default of include" aligned with the "sum of knowledge" notion. It doesn't. Bon courage (talk) 12:39, 13 February 2024 (UTC)[reply]
It does. --Dustfreeworld (talk) 12:55, 13 February 2024 (UTC)[reply]
That is not logical. Bon courage (talk) 13:01, 13 February 2024 (UTC)[reply]
May I ask why do you think it’s not logical? Can you elaborate more? (Perhaps our definitions of "a default of include" and "sum of knowledge" are not the same?) --Dustfreeworld (talk) 13:52, 13 February 2024 (UTC)[reply]
Because the "sum of knowledge" goal can only be attained by modifying Wikipedia in ways which make it closer to being the "sum of knowledge". Including material may, or or may not, do that; so, whatever the default for inclusion/exclusion is, that default's setting would be orthogonal to the "sum of knowledge" goal. In some cases inclusion of material may be counter to the goal. Bon courage (talk) 14:01, 13 February 2024 (UTC)[reply]
“In some cases inclusion of material may be counter to the goal”. For examples? --Dustfreeworld (talk) 14:23, 13 February 2024 (UTC)[reply]
IMO the cases that “inclusion of material may be counter to the goal” are already handled by other exclusion policies (not
WP:VNOT). Inclusion of material that does not counter to the goal will make Wikipedia closer to being the “sum of knowledge”. --Dustfreeworld (talk) 14:24, 13 February 2024 (UTC)[reply
]
We see it all the time every day: for example people adding primary source medical material or adding irrelevant details. Last year I removed ~ 1,200 medical citations and associated content from Wikipedia, and I can assure you that activity took it closer to being a sum of knowledge (rather than a miscellany of factoids). Bon courage (talk) 14:28, 13 February 2024 (UTC)[reply]
Already handled by
WP:MEDRS. --Dustfreeworld (talk) 14:59, 13 February 2024 (UTC)[reply
]
I suppose by “a default of include” we are talking about the default when no consensus, under the scenario stated in the problem section on the top of this page?
“Usually, when article content is disputed, it's easy for editors to reach an agreement ("consensus") about what to do. In rare instances, even after extensive discussion, editors are unable to make a decision. Several policies and guidelines provide advice about the default actions in such cases. For example, contested ==External links== are removed, and an Wikipedia:Articles for deletion discussion ending in no consensus results in the article being kept.” --Dustfreeworld (talk) 15:04, 13 February 2024 (UTC)[reply]
And cases that violates MEDRS, etc. aren’t under that scenario (those violating info should have been excluded already before reaching that scenario). --Dustfreeworld (talk) 15:08, 13 February 2024 (UTC)[reply]
Well... In practice, it's a bit more complicated than that. For example, you can get pretty evenly divided views on whether to make a factual statement like "Makeup is sometimes used to cover up acne". In that particular case, we had a group of editors whom, for convenience, I will call "men" saying that unless the zillion-dollar cosmetics industry was proven in medical journals to cure acne, it didn't deserve to be mentioned. (I may or may not have told one of them to go ask his wife what she thought about his exclusionary POV.) We had another group of editors who thought that Concealer was not only a notable subject, but also a perfectly reasonable thing to mention in the article on Acne.
We've had similar fights over the years about whether to mention various
cough syrup
).
But: The purpose of this section isn't to re-litigate the subject or re-state one's own views. What I'd appreciate is having each of you tell me what you think were the common views up at the top of the page. I'm not asking whether you agree with those views, but it's helpful to know what the common views were. This is particularly important when we can identify a common theme – less like "the majority voted this way" and more like "editors on both sides think this principle is important". WhatamIdoing (talk) 16:59, 13 February 2024 (UTC)[reply]
Dustfreeworld, please drop the stick. The very fact that we have arguments all the time on Wikipedia about whether to include something, or where it should go, or how much of it to say shows that editors feel the answers to those questions are not obviously "yes", "anywhere you like" and "as much as possible". If it was as simple as you propose to know which solution aligns with our mission, WAID would never have needed to ask this RFC. Everyone else in this discussion agreed that the conflicting policies were (a) "default to removal" and (b) "default to whatever was there before". Nobody mentioned the mythical (c) "default to include" policy because there isn't one. You are welcome to advocate for it but please stop arguing with everyone else that we are all wrong and really (c) exists and is in fact the obvious solution and the only one that aligns with all our goals. -- Colin°Talk 17:35, 13 February 2024 (UTC)[reply]
“Everyone else in this discussion agreed that ...” your assumption again ... it seems to me that one of the editors who had participated in this discussion is now blocked (for unknown reason). Perhaps we can ping them here to ask whether they agreed or not?
BTW, you may have misunderstood my comments. I suggest you reread.
--Dustfreeworld (talk) 17:49, 13 February 2024 (UTC)[reply]
Who's blocked? Bon courage (talk) 17:56, 13 February 2024 (UTC)[reply]
Andrevan. WhatamIdoing (talk) 17:59, 13 February 2024 (UTC)[reply]
Oh. Arbcom blocked. Murky. Bon courage (talk) 18:05, 13 February 2024 (UTC)[reply]
By "everyone else in this discussion" I mean the one you started by saying you'd like to inform us we are all interpreting
WP:ONUS wrongly and that the holy words of Jimbo made it clear how wrong we all were. -- Colin°Talk 18:03, 13 February 2024 (UTC)[reply
]
I don’t know who’s that “everyone” you mean. You have your own (changing) definition. I’ve never used the word “wrong”. It’s *your* interpretation of my opinion. You are free to have your own interpretation (in your thought), but again, please don’t make assumptions / accusations here and please AGF. Thanks. --Dustfreeworld (talk) 18:16, 13 February 2024 (UTC)[reply]
Your opening words were "I keep seeing WP:ONUS in this discussion. I believe it might have been misinterpreted" which is a statement that at least some of those citing WP:ONUS are misinterpreting it. And then "I don’t think ONUS means “exclude when no concensus”" which is you misinterpreting ONUS. I really am not interested in a meta argument about whether or not I have changed my definition of everyone or who might no longer be assuming good faith. Good evening. -- Colin°Talk 18:51, 13 February 2024 (UTC)[reply]
@WhatamIdoing, seems like a
WP:WEIGHT issue ... --Dustfreeworld (talk) 17:50, 13 February 2024 (UTC)[reply
]
Probably. Especially for articles in the
WP:MEDRS range, we do have a tendency to claim "bad sources" when we mean "doesn't feel important enough to me". WhatamIdoing (talk) 21:47, 17 February 2024 (UTC)[reply
]
I'm finding SMcCandlish's points 2 and 3 to be contradictory for exactly the reasons WAID started this. And I'm not persuaded by the long list of UPPERCASE policies as proof that it is straightforward to remove disputed content merely by citing a shortcut. For example,
WP:INDISCRIMINATE are cited as though those policies settled arguments, rather than themselves being the basis of the argument that failed to reach a consensus (is this text DUE or does this text fail INDISCRIMINATE). I do think nearly all our policies are geared towards judging what should be removed, possibly because editor instinct is to add and this needs countered. Like the heart wants but the head knows better. -- Colin°Talk 09:53, 13 February 2024 (UTC)[reply
]

Bon courage may be right that these contradictory polices work in practice and people may tend to pick the most appropriate one. I do think we could live happily without

WP:ONUS to exclude a recent addition, it might not actually be "the common result" (which is clumsy English imo, like a non-native speaker wrote it). I also wonder if there is a difference between "the proposal" and "the bold edit" in that the former is a timid approach that sets oneself up for failure on no-consensus whereas the latter achieves its aim often without disagreement. One could propose something and get exactly one negative "meh" response and be stuck with no change, whereas if one was bold then the "meh" response might not encourage any reversion. -- Colin°Talk 10:31, 13 February 2024 (UTC)[reply
]

If two sides are exactly evenly matched taking policies into account, there would be no reason to favor one or the other. A pro-inclusion/exclusion interpretation of "no consensus" just means the side aligned with this change would have more "merit" over their opposition to begin with. Vacosea (talk) 23:50, 11 March 2024 (UTC)[reply]
IMO this is not the right venue to discuss article’s content. As to “potential conflict of interest”, I believe people will know more about what you mean by that if they take a closer look at your contribution history. --Dustfreeworld (talk) 01:23, 12 March 2024 (UTC)[reply]
And other participants in this discussion have really wanted some particular text omitted from an article during this discussion. Some of us have even wanted both – to omit something from one article and retain something from another. That's okay. Sometimes it takes one of those disputes to remind you what this kind of question means in practice. WhatamIdoing (talk) 01:31, 12 March 2024 (UTC)[reply]
The difference is I'm neutral and not pushing for inclusion (or exclusion) here. A fundamental change like this would make Wikipedia as a whole more inclusionist or more deletionist by policy. Is this something that 20 editors can decide? Vacosea (talk) 06:15, 12 March 2024 (UTC)[reply]
@Vacosea, I wonder if you could tell us what you think the current policy about disputed content is (as seen in actual practice). I have been wondering whether the answer depends on the kinds of articles you tend to edit (e.g., exclude disputed sentences in altmed and American politics articles, but include disputed sentences in films and books). WhatamIdoing (talk) 17:24, 13 March 2024 (UTC)[reply]
It's not often that both sides are exactly evenly matched. From what I have seen, no consensus usually reduces activities related to debate without prejudicing future discussion, like a temporary ceasefire but without the enforcement potential of a policy. Vacosea (talk) 18:21, 13 March 2024 (UTC)[reply]
Well, it's very rare for both sides to be exactly evenly matched, but it's not unusual for a discussion to close as no consensus. I have found that if I don't specify that the sides are exactly evenly matched, then editors try to weasel out of the finding of no consensus. (There must be a winner.) But if there is truly no consensus to include or exclude, say, a particular photo in an article, then what do you think editors should do? You can't justify keeping it in, because there's no consensus to include it, but you can't justify taking it out, because there's no consensus to remove it. Now what? WhatamIdoing (talk) 18:54, 13 March 2024 (UTC)[reply]
What now?… now we continue to discuss the issues people have with the photo, with a goal of actually forming a consensus… we explore compromise options beyond just a simple binary keep/remove choice. For example, is there a better photo that would be more acceptable? Would the photo be more acceptable if the caption were changed? Etc. Blueboar (talk) 12:58, 14 March 2024 (UTC)[reply]
I don't think that's a reasonable approach and possibly why we've ended up with the "revert to status quo before dispute" option, which is neither inclusionary nor exclusionary. Reasonable people will have already explored the options you give and sometimes we really can't come to an agreement but continuing to argue is in nobody's interests or the best use of our time. See Agree to disagree.
The recent Wikipedia:Requests for comment/Names of deceased trans people was closed as no consensus. Even the person opening the RFC hoped it would "hopefully settle this and end the seemingly endless discussions", in other words, community patience was being tested already. The closing admin took "no consensus" to imply "no change to policy". That doesn't mean some involved in this aren't considering alternatives to propose at some point. But it does mean the community needs a break from this, perhaps for everyone to approach it again with fresh eyes months later. So the question is what to do now? For articles, it isn't always include/exclude. Someone might just be proposing a reordering of sections. -- Colin°Talk 13:52, 14 March 2024 (UTC)[reply]
More immediately, what shall we do right now, while we explore compromise options? When the options are binary (either this particular photo is 100% in the article, or it is 100% out; either ==Causes== comes 100% before ==Symptoms== or it 100% doesn't), the article must be in one of those states during any future discussions. So which state is it supposed to be in, when editors really, truly, absolutely cannot agree on which state it's supposed to be in? WhatamIdoing (talk) 16:52, 14 March 2024 (UTC)[reply]
Maybe we should have some examples of where this has happened, as a way of helping editors understand the problem. -- LCU ActivelyDisinterested «@» °∆t° 12:43, 14 March 2024 (UTC)[reply]
In the end this seems to boil down to whether we should add a more inclusionist policy or a more deletionist policy. I am neutral at the moment. Vacosea (talk) 14:12, 14 March 2024 (UTC)[reply]
I don't think that's what WAID is saying at all. Some questions are not "should we add this" or "should we remove that". And even for those that are, some include/exclude questions might often be answered with "if it was there before, we keep it, if it wasn't there before, we remove it" which isn't an inclusionist or exclusionist position but more of a "resistant to change" position. WAID has often asked whether some areas of the project might suit one approach more than another. I think there are four options
  1. Tend to inclusion
  2. Tend to exclusion
  3. Tend towards adopting change
  4. Tend towards resisting change
And there are areas where any of these occur. Our BLP policy tends to exclusion. Deletion discussions tend to inclusion. As the project has matured, our approach especially with regard to P&G and featured content has been to resist change. But that's not really what a wiki is about, and
WP:MEDRS). -- Colin°Talk 14:33, 14 March 2024 (UTC)[reply
]
That breakdown makes more sense. It's still not easy to decide but is something to think about. Vacosea (talk) 15:20, 14 March 2024 (UTC)[reply]
The point of this discussion is to decide that, and if you have any advice, I'd be happy to hear it.
The underlying problem is that all four of these options are declared by one page or another to be The One True™ Option, and they are mutually incompatible. We have editors showing up at discussions saying "My page says #2" (when they want to exclude content) and "My page says #4" (when they want to keep long-standing/long-neglected content), and so forth.
In principle, such contradictory claims should not be possible, because the policies and guidelines should not be contradicting each other. But we can't fix the contradictions until we decide which approach we want to prioritize in the no-consensus-whatsoever state. So – what to do?
Another proposal above sidesteps this by suggesting that no consensus must be declared by an uninvolved editor, who must then pick from the four options (generally, at any point, one of the first two plus one of the second two will be true). WhatamIdoing (talk) 16:58, 14 March 2024 (UTC)[reply]
And what rationale is this uninvolved editor supposed to give for picking 1..4? Who's to say they don't just pick whichever outcome they prefer and then claim it was supported by option #n. Plus why do we need to go find an uninvolved third party every time a few people on the internet can't agree? I wonder if the desire expressed above that we simply must keep arguing stems from our Twitter mentality that somebody must be right and somebody else must be wrong, and horribly hatefully wrong too. Some decisions are just hard and some decisions aren't that important. -- Colin°Talk 19:36, 14 March 2024 (UTC)[reply]
For me, the “keep talking” option stems from my NOT liking the “someone must win” mentality. I want to encourage editors to look for compromises and think outside the box… beyond just binary “keep/remove” options. Is there a different way to phrase the contested material that the naysayers would accept? Might it work better if placed in a different article? I want editors to explore options beyond just “X or Not X”. Sometimes you need everyone to be in a mental state of exhaustion before they are ready to explore compromise. Blueboar (talk) 19:48, 14 March 2024 (UTC)[reply]
Colin, as we said above, that proposal would amount to declaring that the closer has to
WP:SUPERVOTE
.
Blueboar, you remind me of Wikipedia:WikiSpeak#consensus: "One of the three states that can be reached at the end of a discussion after all parties have become thoroughly fed up with it; the alternatives are no consensus or for pity's sake, I wish I'd never gotten involved in this."
The outcome that I really want to avoid is no consensus followed by one editor declaring that means removal is required per the Wikipedia:Verifiability policy and the other editor declaring that means inclusion is required per the Wikipedia:Consensus policy. Conflicting policies mean that we all end up in "for pity's sake, I wish I'd never gotten involved in this." WhatamIdoing (talk) 23:21, 14 March 2024 (UTC)[reply]
Problem is… we DO have conflicting policies. And whenever we try to resolve that conflict, we end up with (you guessed it)… “No consensus”. The BEST a closer can do in such a situation is acknowledge that the policy conflict exists in his closing comments, and impose a TEMPORARY resolution along the lines of WP:WRONGVERSION… noting that his closure is to be immediately overturned should a clearer consensus form in the future. Blueboar (talk) 00:32, 15 March 2024 (UTC)[reply]
We also have a written policy, AFAICT with consensus behind it, that says written policies shouldn't conflict with each other.
(All decisions are temporary, because we have
WP:No binding decisions.) WhatamIdoing (talk) 01:46, 15 March 2024 (UTC)[reply
]
  • One other consideration that was hinted at above… are we talking about “no consensus” re disputes over article content, or “no consensus” re disputes over policy/guideline provisions? I think there is a difference.
For article content, we actually want to encourage editors to edit… we EXPECT change (whether that change entails adding OR removing content) … especially when new information becomes available and different sources are examined. So… unless there is a demonstrated consensus against the change I would “default” to allowing it. With the understanding that someone else can change it yet further.
For policy/guideline pages, on the other hand, we EXPECT stability. Frequently changing “the rules” is disruptive to editing. So… I would default to being reluctant to accept any change to policy/guideline pages without a demonstrated consensus in favor of the change. Blueboar (talk) 17:07, 14 March 2024 (UTC)[reply]
I was going to stay out this time around. There is a tension in the rules (policy, guideline, whatever) that permits an argument (OK, discussion) on either side of almost anything and in the end, it comes down to consensus. If at any point, there is none, then discussion needs to continue until there is. Selfstudier (talk) 17:16, 14 March 2024 (UTC)[reply]
Endless discussion doesn't always result in a consensus, and sometimes further discussion is destructive to the community. Ask yourself: Why does
WP:ARBDSRFC
authorize admins to impose a year-long moratorium on RFCs about a given topic, if endless discussion were always a functional approach on disputed topics?
Blueboar, I love your commitment to compromise and creative thinking, but sometimes there really is a binary choice: either a fact is in this article, or it's not. Either this section comes first, or it doesn't. Either this exact photo is in the article, or it's not. Sometimes a compromise works (e.g., the nude photo is no longer in the lead of Pregnancy) but sometimes it doesn't.
And even if a compromise is theoretically possible the article must be in one state or another right now. Unless no-consensus results in deleting articles entirely until a consensus agrees, "let's just keep talking" doesn't tell us what to do before that magical day appears and consensus is achieved. WhatamIdoing (talk) 21:46, 14 March 2024 (UTC)[reply]
If there is truly only a binary choice, then I would adapt the concept of WP:WRONGVERSION. I would close the immediate discussion, noting the lack of consensus and the need for everyone to take a break… and if necessary I would flip a coin to determine which binary state the article should be in UNTIL further discussion achieves a consensus. Blueboar (talk) 22:06, 14 March 2024 (UTC)[reply]
I think sometimes a coin flip could be appropriate, such as which section comes first. I'm not sure coin flipping on the result of no-consensus is a good way to conclude a policy debate. We have the stability expectation for P&G because the project is mature. I don't think that's a fundamental, more of a mindset of the aging users who hang around P&G pages these days. A younger project would be (and was) more experimental.
Wrt the "compromises and think outside the box" as WAID says, there are a lot of decisions that are fairly simplistic and editors debating in good faith should have already considered those options and presumably didn't find them. And sometimes people are split on things and no amount of arguing is going to fix that because they are split in the real world too. Some arguments are just people bringing political and cultural wars onto Wikipedia and so conflict and arguing are inherently not what the project is about and should be discouraged (i.e. very much not: 'keep arguing until you get a consensus, even though nobody else in the world has reached agreement, on whether one should say "gender critical feminists" or "TERFs", and once you do, we can inform the United Nations and all nations will be glad to follow our wisdom on this matter'). -- Colin°Talk 09:02, 15 March 2024 (UTC)[reply]
Yup… some debates may take years reach resolution/consensus (and a few will likely never be fully resolved) … and when that happens, the best we can do is acknowledge the lack of consensus, and say “Ok… here is a temporary solution. The intent is to impose a pause on the immediate arguing, and not to be a final, precedent setting determination.” Blueboar (talk) 13:03, 15 March 2024 (UTC)[reply]
To add to how you distinguished between article content and policy, how drastic the change being debated is another factor, as well as what type of article it is as mentioned by WAID. For what it's worth, the options are no change, change (include), and change(exclude). For that to be implied by "no consensus", I still think it would be too blunt as a policy. Maybe it can mean a pause in related editing instead. Vacosea (talk) 06:59, 19 March 2024 (UTC)[reply]
I don't think the only change options are include or exclude. For example, where to stick something, whether that's the order of sections, or in this policy or in that guideline, or which images come first and which last, are all just change full stop. Wrt Blueboar's "temporary", WAID keeps reminding us that even conclusive consensus decisions are temporary. Consensus can change that it might change just as quickly as this temporary no-consensus situation changes to has-consensus. So all ideas of permanence are an illusion. A wiki is permanently in flux. And I do think that's important for this project, as some people do go around citing the opinions of a handful of people who really weren't quite debating what that person claims they were, as though the admin's closing remarks were written in stone. I agree many discussions need a break or pause in arguing, even if that argument didn't reach consensus. -- Colin°Talk 08:22, 19 March 2024 (UTC)[reply]
Using Vacosea's model, the options would be:
  • no change
  • include
  • exclude
  • rearrange (or otherwise make a change that doesn't include or exclude the material)
I don't think there are any other options, and in between "no consensus" and "we finally reached consensus", the article's going to have to be in one of those four states.
Under certain circumstances, we could call those four options:
  • WP:NOCON
  • WP:EP
  • WP:ONUS
  • WP:BOLD
The question here is – which one? Or if we won't pick which one for all articles, how are editors supposed to decide which one to follow and which ones to "violate" in each instance? WhatamIdoing (talk) 21:13, 21 March 2024 (UTC)[reply]
The page top says "Don't tell us what this or that policy says" but as we head towards bottom you're telling us what the policy says. I hope you will start a new discussion with "tell us what this or that policy says" if that's what you really want discussed. Peter Gulutzan (talk) 21:27, 21 March 2024 (UTC)[reply]
Do you really think it would help to have editors voting "Remove per ONUS" and "Keep per NOCON"? We need to find out what the policies and guidelines should say, not what they currently and contradictorily say. WhatamIdoing (talk) 01:50, 22 March 2024 (UTC)[reply]
Thing is, there is a good chance that the discussion has already noted what NOCON and ONUS say. The closer could acknowledge this but close with something like: “While ONUS and NOCON conflict, in this case I feel NOCON should prevail because blah blah reasons.”
And yes, that means that in some other dispute the closer might determine that ONUS should prevail. That’s OK. The key is that the close allows the editors to move forward at that specific article, and the closer gives a rational for the close.
The closer could also close with: “Omit for now (per onus), HOWEVER if blah blah conditions are met it should be returned”… This would again settle the immediate dispute, while giving guidance and direction to those who favor the material.
In short: when there is No Consensus, closers need to be less wikilegalistic and a bit more creative in their closing. Blueboar (talk) 11:48, 22 March 2024 (UTC)[reply]
No closer has even a smidgen of a right to "acknowledge" that there is a conflict in policies, since the request from the start was to not discuss that. In fact there should be no closer, this was just a free-wheeling conversation with a hypothetical. Peter Gulutzan (talk) 13:24, 22 March 2024 (UTC)[reply]
  • (outdent) - Peter, I was not talking about how the RFC here was to be closed… the question we are discussing is how other RFCs (focused on inclusion/exclusion) should be closed. The conflict between the policies is an important factor in those. Blueboar (talk) 14:57, 22 March 2024 (UTC)[reply]
Blueboar: okay, sorry, I mistook your reference to "the closer" as "the closer of this", and objected based on my mistookness. I don't believe there is an RfC here as I don't see it in Wikipedia:Requests for Comment/All, but formal closes are okay on non-RfCs and I was worried that somebody think this discussion merited one. If that's not the case, fine. Peter Gulutzan (talk) 15:41, 22 March 2024 (UTC)[reply]
The RFC listing expired in February, and the bot removed the entry from the central lists at that point. If you think the tag should be re-added to re-advertise it, please feel free to put a new tag (without an id number) at the top of the page and update the date in the first signature to be less than 30 days old (otherwise, the bot will just remove the rfc template again, on its next run). WhatamIdoing (talk) 17:30, 22 March 2024 (UTC)[reply]
So it was de facto closed on February 5, eh? I'm happy with that result. Peter Gulutzan (talk) 18:18, 22 March 2024 (UTC)[reply]
Some terms we use:
Ending an RfC
Removing the link to the discussion from the central RfC lists. This is accomplished by removing the {{rfc}} tag from the talk page; a bot takes care of the rest. The bot will also remove the tag, if you wait long enough.
The end of a discussion
This means people have stopped discussing the question. When a discussion has naturally ended, you should consider ending the RfC.
Closing the discussion
Someone lists conclusions (if any) and discourages further discussion. Some editors make a distinction between "closing" a discussion (discouraging further discussion, usually with the {{closed rfc top}} tag pair) and "summarizing" a discussion (naming outcomes). Neither "closing" nor "summarizing" are required.
Using the words as defined in this box (copied from
WP:RFC), this RFC "ended" on February 5th, but it has neither been "closed" nor "summarized" yet, and "the discussion" is ongoing (obviously, since we're still posting). WhatamIdoing (talk) 19:20, 22 March 2024 (UTC)[reply
]
Conceded. The main objection remains, though. I'd said earlier: No closer has even a smidgen of a right to "acknowledge" that there is a conflict in policies, since the request from the start was to not discuss that. In fact there should be no closer, this was just a free-wheeling conversation with a hypothetical. Now I have to accept there can be a formal close, but the rest still applies. Peter Gulutzan (talk) 00:38, 23 March 2024 (UTC)[reply]
The conflict between the policies is part of the story. See the part of the story that says These editors are now asking you: When there is no consensus to include information, shouldn't it be removed, because policy A says to remove it? But when there is no consensus to remove information, shouldn't it be retained, because policy B says to retain it?
The closer of this RFC therefore has every right to acknowledge that the whole question is derived from this conflict (if they want to). WhatamIdoing (talk) 18:06, 23 March 2024 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Requests_for_comment/When_there_is_no_consensus_either_way&oldid=1215194483"