This is an old revision of this page, as edited by 2400:6a80:81a4:2080:4c08:e64e:98a2:35b3 (talk) at 15:47, 23 November 2024 (11). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 15:47, 23 November 2024 by 2400:6a80:81a4:2080:4c08:e64e:98a2:35b3 (talk) (11)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)This is the talk page for discussing improvements to the Consensus page. |
|
Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24Auto-archiving period: 3 months |
The project page associated with this talk page is an official policy on Misplaced Pages. Policies have wide acceptance among editors and are considered a standard for all users to follow. Please review policy editing recommendations before making any substantive change to this page. Always remember to keep cool when editing, and don't panic. |
view · edit Frequently asked questions
Q: When was WP:CONEXCEPT, which says that editors at the English Misplaced Pages do not get to overrule the Wikimedia Foundation on issues like server load, software and legal issues, first added? A: It was added in January 2007 by User:Circeus, after a brief discussion on the talk page in the context of whether this page should be a policy rather than a guideline. It has been discussed and amended many times since then, e.g., here, here, and here. |
“ | Consensus is a partnership between interested parties working positively for a common goal. | ” |
— Jimmy Wales |
1
WP:NOCONSENSUS
Wondering if the old wording was more clear? We seem to have a new generation of editors that have a different interpretation of this policy. That caused us more edit wars than it solves. Nostalgic old man. > Moxy🍁 20:37, 5 August 2024 (UTC)
- It seems to me that closers must be more active in this, its no use just saying it's Nocon, go ahead and sort it out. OK, in some cases it can be very clear but often it won't be so clear, as in the case that has prompted this question here. Selfstudier (talk) 21:02, 5 August 2024 (UTC)
- I do agree with this point..... if someone's closing an RFC they should not tell people just to go ahead and have another RFC. If bold edits are contested and RCF are inconclusive...... those that edit wars in the contested content should be dealt with accordingly not rewarded with the content be included with experience editor having to deal with consequences.Moxy🍁 21:08, 5 August 2024 (UTC)
- I think in this case it is clear; an edit in place for just six weeks doesn't become the status quo.
- If it had been a few months, then things might be ambiguous, but that isn't the case here - six weeks is just too short. BilledMammal (talk) 21:31, 5 August 2024 (UTC)
- Part of the problem is that we seem to have forgotten how to reach compromises. Blueboar (talk) 21:46, 5 August 2024 (UTC)
- Misplaced Pages:Consensus#No consensus after discussion, aka NOCONSENSUS, does not belong in this policy. No consensus is not a strategy for achieving consensus. No consensus belongs in WP:Editing policy and WP:Closing discussions.
- - SmokeyJoe (talk) 22:45, 5 August 2024 (UTC)
- I like the idea of putting it in Misplaced Pages:Closing discussions. Also, I think the rather dubious bit about WP:STATUSQUO usually applying after the discussion is over should probably just get lost on during the trip to that page. WhatamIdoing (talk) 16:23, 6 August 2024 (UTC)
- That’s two of us, with a silent audience. SmokeyJoe (talk) 23:41, 6 August 2024 (UTC)
- Three of us, really, though how does one progress such a thing? Selfstudier (talk) 17:10, 9 August 2024 (UTC)
- Either we do it, and see if BRD will identify a Very Interested Person™, or we have an Official Discussion™ (RFC or otherwise). WhatamIdoing (talk) 00:01, 11 August 2024 (UTC)
- Any day now maybe. SmokeyJoe (talk) 01:00, 11 August 2024 (UTC)
- I'll get grief if I bold edit that, it's a policy page, so I guess an RFC.
- Here? (Editing policy is also a policy page).
- Question " Should Misplaced Pages:Consensus#No consensus after discussion be moved to Misplaced Pages:Closing discussions? (and/or Editing policy).
- with this convo as RFCbefore. Selfstudier (talk) 09:08, 11 August 2024 (UTC)
- I think a split/merge discussion is the usual format. I've started a separate sub-section at Misplaced Pages talk:Consensus#Moving NOCON to CLOSE. WhatamIdoing (talk) 23:34, 30 August 2024 (UTC)
- Any day now maybe. SmokeyJoe (talk) 01:00, 11 August 2024 (UTC)
- Either we do it, and see if BRD will identify a Very Interested Person™, or we have an Official Discussion™ (RFC or otherwise). WhatamIdoing (talk) 00:01, 11 August 2024 (UTC)
- Three of us, really, though how does one progress such a thing? Selfstudier (talk) 17:10, 9 August 2024 (UTC)
- Not entirely opposed to moving it, but I think some form of it needs to be retained in policy, and if not here then at WP:EP. Otherwise, the guidance may be viewed as a demotion of sorts at an informational page. --GoneIn60 (talk) 16:18, 11 August 2024 (UTC)
- That’s two of us, with a silent audience. SmokeyJoe (talk) 23:41, 6 August 2024 (UTC)
- I like the idea of putting it in Misplaced Pages:Closing discussions. Also, I think the rather dubious bit about WP:STATUSQUO usually applying after the discussion is over should probably just get lost on during the trip to that page. WhatamIdoing (talk) 16:23, 6 August 2024 (UTC)
- Quite happy for the details to be examined (impartially). If there's some volunteers. Selfstudier (talk) 22:21, 5 August 2024 (UTC)
- Part of the problem is that we seem to have forgotten how to reach compromises. Blueboar (talk) 21:46, 5 August 2024 (UTC)
The post close discussions/editing have not achieved any consensus either and I have opened an RFC to try and settle the matter. Selfstudier (talk) 09:51, 6 August 2024 (UTC)
- You have opened an RFC to try and settle the matter? Where? SmokeyJoe (talk) 11:09, 6 August 2024 (UTC)
- Years ago, Kim Bruning used to talk about the importance of "the wiki way" in identifying consensus, which is to say: If an edit sticks, it probably has some level of consensus. It might be a shaky, tenuous, temporary weakling of a consensus, but it's enough of a consensus that other editors don't feel obliged to instantly revert the edit. This may be difficult to achieve on hot-button issues (or if someone has outside influences, such as a paid editor or a volunteer for a political campaign), but that's the goal: to find something that the other 'side' won't revert. WhatamIdoing (talk) 16:28, 6 August 2024 (UTC)
- I miss Kim. He was very wise.
- What I read him as expressing is what is now called BRD and SILENCE. What I have deduced is that BRD is good for rapid development, and was more often appropriate in 2004 than 2024. Now, different to then, it is much better, expected, almost demanded, that there be a talk page record of consultation. Number of Watchers is no longer meaningful, and a quiet bold edit on a quiet page can be reverted as undiscussed even years later. SmokeyJoe (talk) 01:06, 11 August 2024 (UTC)
- Nothing should be reverted "as undiscussed." Editors should provide a substantive rationale. For more on this topic, see wp:DRNC. - Butwhatdoiknow (talk) 00:55, 12 August 2024 (UTC)
- Moxy, just for clarification, what exactly is this "
different interpretation
" you're referring to? Here's a version from 2017 that predates some of the recent tinkering. Is that the "old wording" you had in mind, and if so, what about this version seems more clear? Presentation, phrasing, or both?FWIW, this version was the last revision I paid attention to. I now see that some mini-subheadings have since been added along with a bullet covering FfDs. While well-intentioned, I think these unnecessarily crowd an already cluttered NOCON that's struggling to be concise. --GoneIn60 (talk) 03:58, 12 August 2024 (UTC)- more clear here. Moxy🍁 09:16, 12 August 2024 (UTC)
- Ah, well that's taking it way back! Is it more clear though? I suppose it depends on how the RfC is worded. The "proposed change" could be in reference to the bold edit added a year ago...or...it could be in reference to the recent effort to remove it. I suspect that's why additional verbiage was added later on. Unfortunately, as we've seen, it hasn't really gotten us any closer to solving the underlying issue of determining when a bold edit achieves some level of consensus without discussion. --GoneIn60 (talk) 10:11, 12 August 2024 (UTC)
- more clear here. Moxy🍁 09:16, 12 August 2024 (UTC)
Moving NOCON to CLOSE
As suggested above, let's move WP:NOCON over to WP:CLOSE, where it will have more immediate relevance. No changes to the wording/facts/etc. in the section are suggested – just a simple move of these words out of this page and over to the more closely related page. What do you think? WhatamIdoing (talk) 23:33, 30 August 2024 (UTC)
- Will you propose to move the last sentence of WP:ONUS to CLOSE as well? Butwhatdoiknow (talk) 15:30, 31 August 2024 (UTC)
- I haven't thought about it, but I think we should deal with one thing at a time. WhatamIdoing (talk) 17:04, 31 August 2024 (UTC)
- Sounds like a plan! Let's deal with the ONUS sentence first. - Butwhatdoiknow (talk) 18:36, 31 August 2024 (UTC)
- This question was already asked three weeks ago, so it's too late to do something else "first". WhatamIdoing (talk) 21:44, 31 August 2024 (UTC)
- Sounds like a plan! Let's deal with the ONUS sentence first. - Butwhatdoiknow (talk) 18:36, 31 August 2024 (UTC)
- NOCON and the last sentence of ONUS are yin and yang. You can't make this change without changing the balance between the two. I oppose moving only one into CLOSE. - Butwhatdoiknow (talk) 00:18, 1 September 2024 (UTC)
- That's interesting to know, but not very clear. Do you think it would ultimately be best for NOCON and ONUS both to get moved to the other page, or do you think it would be best for neither to move? WhatamIdoing (talk) 00:26, 1 September 2024 (UTC)
- Note: I am only talking about the last sentence in ONUS.
- I think it would be best for NOCON and ONUS to be reconciled and put in one place. CLOSE is probably the best, but it is not a policy or guideline. And that is the primary problem with putting only NOCON in CLOSE, it leaves ONUS as the only policy statement on the issue.
- On the other hand, good luck getting community consensus on reconciling NOCON and ONUS. - Butwhatdoiknow (talk) 15:27, 1 September 2024 (UTC)
- Neither NOCON nor ONUS belong in WP:Consensus.
- I think both belong primarily in WP:Editing policy. I have no issue with ONUS remaining described in WP:V, but NOCON should be no more than a pointer to WP:EP.
- With both nested in WP:EP, both can be mentioned in WP:CLOSE. Both are true regardless of whether there has been a formal discussion to be formally closed. SmokeyJoe (talk) 13:04, 2 September 2024 (UTC)
- That's interesting to know, but not very clear. Do you think it would ultimately be best for NOCON and ONUS both to get moved to the other page, or do you think it would be best for neither to move? WhatamIdoing (talk) 00:26, 1 September 2024 (UTC)
- I haven't thought about it, but I think we should deal with one thing at a time. WhatamIdoing (talk) 17:04, 31 August 2024 (UTC)
- Apart from the seeming logic of such a move, the thing that interests me most is whether it will result in closers paying more attention to it in their closes. Do you think? Selfstudier (talk) 16:29, 31 August 2024 (UTC)
- I have no idea if it will affect closer behavior, or if it might affect "closee" behavior (e.g., fewer close challenges, close challenges that are better explained, etc.). WhatamIdoing (talk) 17:10, 31 August 2024 (UTC)
- WP:CLOSE is not policy, so moving NOCON over there would just remove it from policy, which I do not think would be a good idea (when there's no consensus, there needs to be an answer, whatever it may be, to the question of what to do). I've thought before that it'd be good to have some sort of guideline on closing (like WP:DGFA but not just for deletion), but as long as WP:CLOSE is a mere "information page" I would oppose this. Extraordinary Writ (talk) 03:41, 1 September 2024 (UTC)
- @Extraordinary Writ, NOCON doesn't (and isn't supposed to) say anything that doesn't appear elsewhere.
- So, e.g., if the dispute is over BLPs, then you can currently say "Well, NOCON is a policy, and it says that WP:BLP says that contentious matter gets removed if there's no consensus", but you could just as easily say – and probably ought to be saying – "WP:BLP is a core content policy, and it says that contentious matter gets removed when editors don't agree that it's adequately sourced".
- You'd lose nothing any maybe even gain something by citing the policy that is most relevant. WhatamIdoing (talk) 05:51, 1 September 2024 (UTC)
- Extraordinary Writ, thanks for a good observation. I oppose making WP:NOCON a non-policy. Peter Gulutzan (talk) 13:40, 1 September 2024 (UTC)
- I wish that I'd never started NOCON.
- Okay, guys, let's try this again from the top. Here's the facts:
- BLP says we remove contentious matter unless editors agree that it's well-sourced. This encompasses both "we have a consensus that it's badly sourced" and "we don't have a consensus that it is well-sourced".
- BLP is a policy. A policy is not magic pixie dust, but BLP is definitely, absolutely, indisputably a policy. It's even one of our Misplaced Pages:Core content policies.
- Some years ago, I added a little copy/summary of the BLP rules to this page. This little copy did not create or change any rules.
- Now the question for @Extraordinary Writ and @Peter Gulutzan: If we removed NOCON, would you:
- Still be able to remove badly sourced contentious matter when editors can't form a consensus that it's well-sourced, because the BLP policy requires this action, or
- Have no idea what to do, because the BLP policy isn't enough all by itself, and you need to be able to cite two policies to get the badly sourced material removed?
- If you pick the latter, then please tell me what we would actually lose by "only" having the BLP policy as an official policy that requires this. WhatamIdoing (talk) 17:32, 1 September 2024 (UTC)
- Well, and not just in BLPs, the problem remains that the version in the article is presumed to have consensus, including that it belongs in the article for all the right reasons (sourcing/npov/nor/noncvio). So if there is no consensus, its presence in the article misrepresents a consensus that does not exist. -- Alanscottwalker (talk) 20:23, 1 September 2024 (UTC)
- I don't think that's true. The version in the article might be presumed to have consensus up until the consensus was disputed, but NOCON is about when that presumption has just been proven false. You literally cannot have a presumed consensus in the article when the discussion just ended as no consensus; it is an X-and-not-X situation. WhatamIdoing (talk) 06:37, 2 September 2024 (UTC)
- What you just said, is another way of saying what I said, if it's in the article it has consensus. Alanscottwalker (talk) 11:24, 2 September 2024 (UTC)
- Right, the issue is usually about how long it has been in the article in relation to it being contested. Selfstudier (talk) 12:18, 2 September 2024 (UTC)
- @Alanscottwalker, if it's
- in the article, and
- an RFC just closed saying that "there is no consensus about whether this should be in the article",
- then "if it's in the article it has consensus" is a false statement, right? WhatamIdoing (talk) 17:02, 2 September 2024 (UTC)
- Nope. Practice has it that it depends how recently the material was added and the NOCON means nocon for inclusion or exclusion and then if it was there for long enough, it has consensus pending any possible further discussion to resolve the nocon discussion one way or another. Of course this leads to altercations and I think closers ought to at least opine, if not decide, on such matters in their closes (and discussion openers should ask them to opine as well). Selfstudier (talk) 17:12, 2 September 2024 (UTC)
- I also think that it's helpful, for the minority of discussions that get formally summarized, for the closers to express an opinion on what to do next.
- I wonder if you have thought about the distinction between "There is no consensus either way, and that means we keep/remove/undo/whatever" (=what I've been saying for years) and "There is no consensus either way, and that means this version has consensus" (=what you appear to be saying here). WhatamIdoing (talk) 17:34, 2 September 2024 (UTC)
- I'm not saying that, I'm saying it depends, on when it was added and possibly some other things too (eg conlevel). As for your first version, that's what I want the closers to do, although they are more likely to opine than decide. What they tend to do now is say nothing and leave it to editors to figure it out. Selfstudier (talk) 18:26, 2 September 2024 (UTC)
- And this to me would be an inconsistency and an overall issue that requires guidance. Concur with Selfstudier.No consensus to keep is also no consensus to remove. If something is:
- Verifiable
- Has been in place a reasonable amount of time
- Within an article with a reasonable amount of traffic
- Was subject to discussion including a reasonable amount of participants
- Then a stalemate should result in retaining the disputed content...for now. Relegating this advice to an essay demotes it. -- GoneIn60 (talk) 18:54, 2 September 2024 (UTC)
- The statement that "No consensus to keep is also no consensus to remove" is not literally true. When you have a consensus to remove, you also have "no consensus to keep". I realize this sounds pedantic, but this kind of P&G content really needs to be as wikilawyer-resistant as we can make it.
- I really wish editors would quit fixating on the idea of additions and removals, when the real question may be something like "Shall we have ==This== section or ==That== section first?"
- @GoneIn60, the Misplaced Pages:Editing policy takes a default position of retaining information (though it cares about whether Misplaced Pages retains information, rather than whether any given article retains the information). Removing this particular sentence from this policy would not actually make it impossible for you to claim that A Policy™ Requires the outcome you prefer. WhatamIdoing (talk) 20:00, 2 September 2024 (UTC)
- Best thing is to get the principle right, get it done and then wikilawyer it. Trying to wikilawyer it first just results in nothing getting done. Selfstudier (talk) 20:11, 2 September 2024 (UTC)
- When a proposal to take action results in "no consensus", then logically the proposed action is not taken. What happens next depends. The conditions I listed count for something, and in applicable situations, they can be enough to tip the "no consensus" balanced scale in favor of retaining disputed content. It seems most that participate in these discussions agree with that sentiment. Where we seem to differ or want more clarification (or where the wikilawyering sets in) is in regard to reasonable amount; how is that determined?
- To your point: "When you have a consensus to remove, you also have
no consensus to keep
".I don't see it this way. When you have a consensus to take action one way, then you equally have a consensus against taking action the opposite way. So if you have a "consensus to remove", then you have a "consensus against keeping". You shouldn't phrase this as "no consensus to keep". I prefer to preserve "no consensus" for situations that represent outcomes of inaction, or stalemates. --GoneIn60 (talk) 04:27, 3 September 2024 (UTC)
- And this to me would be an inconsistency and an overall issue that requires guidance. Concur with Selfstudier.No consensus to keep is also no consensus to remove. If something is:
- I'm not saying that, I'm saying it depends, on when it was added and possibly some other things too (eg conlevel). As for your first version, that's what I want the closers to do, although they are more likely to opine than decide. What they tend to do now is say nothing and leave it to editors to figure it out. Selfstudier (talk) 18:26, 2 September 2024 (UTC)
- They are certainly contrary, and some may just will to see it as consensus version, nonetheless. -- Alanscottwalker (talk) 17:13, 2 September 2024 (UTC)
- When you have a decision that there is no consensus for a change, then that change does not have consensus. There may be no consensus about what to do instead, but there is no consensus.
- This is important for policies to get right, because the alternative is that we reward edit warring to keep m:The Wrong Version out of the article during a discussion (which would actually be a violation of the WP:QUO essay, which I recommend actually reading, because it's one of those WP:UPPERCASE shortcuts that gets cited for the opposite of what it actually says).
- What we want is:
- Alice changes something. (NB: Not necessarily adding anything. Maybe she just moved a sentence from one section to another.)
- Bob dislikes it and changes the article again. (NB: Not necessarily reverting Alice's edit. Maybe he rearranged a few more sentences, or added some explanatory text in an attempt to make Alice's change be less bad.)
- The discussion about what to do closes as "no consensus either way".
- The decisions about what to do next are not prejudiced in favor of Bob's version just because "It's in the article so it has consensus".
- What we don't want is:
- Alice changes something.
- Bob dislikes it but decides not to risk an edit war.
- The discussion about what to do closes as "no consensus either way".
- The decisions about what to do next are prejudiced in favor of Alice's version just because "It's in the article so it has consensus".
- If anything, we want to reward editors for using restraint. WhatamIdoing (talk) 17:28, 2 September 2024 (UTC)
- Which means, that where the discussion is in respect to core content policies (besides in some cases of BLP or CVIO), it results in the article remaining in internal doubt with respect to policy compliance, but external (or on-its-face) certitude with respect to policy compliance. Which is often important for article creation and improvement because we replicate articles in-form across the pedia, by editors going, that's done there, I'll replicate in kind or use it, here. And we believe it also matters to the quality, we provide readers to rely on. Alanscottwalker (talk) 14:39, 3 September 2024 (UTC)
- I don't know what you mean by the article remaining in internal doubt with respect to policy compliance, but external (or on-its-face) certitude with respect to policy compliance. Does this mean "No consensus means there actually is no consensus, but we'll pretend, for the sake of convenience, that there is a consensus for some version or another"? WhatamIdoing (talk) 03:22, 4 September 2024 (UTC)
- Which means, that where the discussion is in respect to core content policies (besides in some cases of BLP or CVIO), it results in the article remaining in internal doubt with respect to policy compliance, but external (or on-its-face) certitude with respect to policy compliance. Which is often important for article creation and improvement because we replicate articles in-form across the pedia, by editors going, that's done there, I'll replicate in kind or use it, here. And we believe it also matters to the quality, we provide readers to rely on. Alanscottwalker (talk) 14:39, 3 September 2024 (UTC)
- Nope. Practice has it that it depends how recently the material was added and the NOCON means nocon for inclusion or exclusion and then if it was there for long enough, it has consensus pending any possible further discussion to resolve the nocon discussion one way or another. Of course this leads to altercations and I think closers ought to at least opine, if not decide, on such matters in their closes (and discussion openers should ask them to opine as well). Selfstudier (talk) 17:12, 2 September 2024 (UTC)
- @Alanscottwalker, if it's
- Right, the issue is usually about how long it has been in the article in relation to it being contested. Selfstudier (talk) 12:18, 2 September 2024 (UTC)
- What you just said, is another way of saying what I said, if it's in the article it has consensus. Alanscottwalker (talk) 11:24, 2 September 2024 (UTC)
- I don't think that's true. The version in the article might be presumed to have consensus up until the consensus was disputed, but NOCON is about when that presumption has just been proven false. You literally cannot have a presumed consensus in the article when the discussion just ended as no consensus; it is an X-and-not-X situation. WhatamIdoing (talk) 06:37, 2 September 2024 (UTC)
- Is
When discussions of proposals to add, modify, or remove material in articles end without consensus, the common result is to retain the version of the article as it was prior to the proposal or bold edit
written down in policy anywhere else? That's the part I'm most concerned about (and the main reason why most people cite NOCON, I think). You're of course right that the BLP wording (and everything else) is just a summary of other policy, and I indeed don't really care about those parts of NOCON—although if we're going to state the general rule, we probably need to cross-reference the exceptions too. Extraordinary Writ (talk) 21:18, 1 September 2024 (UTC)- That's a statement of statistical fact. It is not a rule and doesn't tell you what to do in any given situation. "If BLP, remove it" is a policy requirement. "Yeah, looking at a bunch of these, I see this pattern" is not a policy requirement. WhatamIdoing (talk) 06:35, 2 September 2024 (UTC)
- I suppose you're right, and if anything my confusion only proves your point that something needs to change. I do think this page has to say something about no consensus (which is presumably why you wrote NOCON to begin with), so I would prefer a rewrite to a full-scale move, though obviously the wording is very difficult. (Prefacing each bullet point with "According to WP:EXAMPLE..." might help somewhat.) That said, although NOCON has somehow come to symbolize the objections to ONUS, getting rid of the symbol won't get rid of the conflict or the deep-seated objections: the central problem remains one undiscussed 2014 edit that there was never consensus for in the first place. Extraordinary Writ (talk) 09:09, 2 September 2024 (UTC)
- Or we could say that the problem is another edit, by a now-indeffed editor, which was not only discussed but actively objected to. The same editor repeatedly removed the statement about BLPs and insisted for years that "no consensus means no change". WhatamIdoing (talk) 17:17, 2 September 2024 (UTC)
- I suppose you're right, and if anything my confusion only proves your point that something needs to change. I do think this page has to say something about no consensus (which is presumably why you wrote NOCON to begin with), so I would prefer a rewrite to a full-scale move, though obviously the wording is very difficult. (Prefacing each bullet point with "According to WP:EXAMPLE..." might help somewhat.) That said, although NOCON has somehow come to symbolize the objections to ONUS, getting rid of the symbol won't get rid of the conflict or the deep-seated objections: the central problem remains one undiscussed 2014 edit that there was never consensus for in the first place. Extraordinary Writ (talk) 09:09, 2 September 2024 (UTC)
- That's a statement of statistical fact. It is not a rule and doesn't tell you what to do in any given situation. "If BLP, remove it" is a policy requirement. "Yeah, looking at a bunch of these, I see this pattern" is not a policy requirement. WhatamIdoing (talk) 06:35, 2 September 2024 (UTC)
- Well, and not just in BLPs, the problem remains that the version in the article is presumed to have consensus, including that it belongs in the article for all the right reasons (sourcing/npov/nor/noncvio). So if there is no consensus, its presence in the article misrepresents a consensus that does not exist. -- Alanscottwalker (talk) 20:23, 1 September 2024 (UTC)
Moving NOCON to Editing Policy
- No, my first belief, and my long term gut feel, and my latest reading, is that NOCON belongs in WP:Editing policy. Nest there, it can be better referred to from WP:CLOSE. - SmokeyJoe (talk) 13:06, 2 September 2024 (UTC)
There is a conflict between NOCON and the last sentence of ONUS. If you demote NOCON to an essay then you are picking sides in that conflict. Is that an intended or unintended consequence of your support for "move only NOCON"? - Butwhatdoiknow (talk) 15:05, 2 September 2024 (UTC)- It's not demoting NOCON to an essay if moved to Editing policy? Selfstudier (talk) 15:11, 2 September 2024 (UTC)
- Oh, OK, you struck it. Selfstudier (talk) 15:12, 2 September 2024 (UTC)
- It's not demoting NOCON to an essay if moved to Editing policy? Selfstudier (talk) 15:11, 2 September 2024 (UTC)
- And move the last sentence of ONUS there as well? - Butwhatdoiknow (talk) 15:11, 2 September 2024 (UTC)
- Moving that last sentence out of VNOT essentially removes ONUS from WP:V. That's a big change and something we may want to shelve for now. Obviously, it's a hot button topic with editors on both sides of the fence: WT:Verifiability/Archive 80#ONUS - a different idea.Policies occasionally provide some brief overlapping coverage, and this would be one such area where it can exist. If editors feel VNOT is not the right place for it, the proper approach might be to flesh out the changes at WP:EP following the NOCON move, bring the policy up to date following discussion, and then decide if ONUS needs revisited. We may find more consensus at that point to remove it from VNOT and/or rephrase accordingly, but now doesn't seem like the time. -- GoneIn60 (talk) 18:31, 2 September 2024 (UTC)
- That sounds like a plan. Selfstudier (talk) 18:40, 2 September 2024 (UTC)
- That plan would require editors to agree to move NOCON out of this page. WhatamIdoing (talk) 20:18, 2 September 2024 (UTC)
- Yep, fine by me and since it's to another policy page, less objectionable for some people, I would think. And we can still leave some sort of summary here pointing to there, that's doable as well, right? Selfstudier (talk) 21:37, 2 September 2024 (UTC)
- Consider me on board if some form of NOCON is staying in policy, just being relocated. Don't think I would support a move to an essay, however. I understand the principle behind NOCON already loosely exists in WP:EP from the comments above, but I think the reason for its existence is that it needs to be spelled out; editors need something to point to. -- GoneIn60 (talk) 22:28, 2 September 2024 (UTC)
- The main reason it exists is because I thought it would be convenient to have a handy summary of all the different rules about what to do when a discussion has a no-consensus result that are scattered about in various policies, guidelines, and procedural pages.
- Boy, was I wrong. WhatamIdoing (talk) 05:21, 3 September 2024 (UTC)
- You've weathered a lot of storms in these here parts! ;)It is handy, or at least it should be, since as you say it was meant to gather in one place several rules that are scattered about on various pages. Despite the number of editors here that may indicate otherwise (which in the grand scheme of things is still a small sampling of Misplaced Pages's overall user base), NOCON is needed in some form. You were onto something all those years ago. GoneIn60 (talk) 07:27, 3 September 2024 (UTC)
- I think the biggest mistake was not predicting the shift towards revering The Policies™ (may their words endure forever). If I had, the collection probably would have ended up on its own page. Compare, e.g., WP:MINREF, which is a handy list of all the times policy requires in inline citation, and yet is not on a policy page, and WP:NOTGOODSOURCE, which is a bulleted list summarizing the common characteristics of WP:Reliable sources, and yet is no less effective for not being on a guideline page. But this one, especially when people twist "this usually happens" into "The Policy™ Requires this", has been a mistake.
- I read decades ago that towards the end of the Roman empire, the tax laws would be written in gold ink on purple vellum, proclaimed with great ceremony, and then ignored by the people who were supposed to be paying the taxes. I would like Misplaced Pages to take the opposite approach to its policies: They are not statutes. They are not sacred. They are a handy summary of reality. And when they diverge from reality, we should fix them. WhatamIdoing (talk) 17:44, 3 September 2024 (UTC)
- You've weathered a lot of storms in these here parts! ;)It is handy, or at least it should be, since as you say it was meant to gather in one place several rules that are scattered about on various pages. Despite the number of editors here that may indicate otherwise (which in the grand scheme of things is still a small sampling of Misplaced Pages's overall user base), NOCON is needed in some form. You were onto something all those years ago. GoneIn60 (talk) 07:27, 3 September 2024 (UTC)
- That plan would require editors to agree to move NOCON out of this page. WhatamIdoing (talk) 20:18, 2 September 2024 (UTC)
- That sounds like a plan. Selfstudier (talk) 18:40, 2 September 2024 (UTC)
- Moving that last sentence out of VNOT essentially removes ONUS from WP:V. That's a big change and something we may want to shelve for now. Obviously, it's a hot button topic with editors on both sides of the fence: WT:Verifiability/Archive 80#ONUS - a different idea.Policies occasionally provide some brief overlapping coverage, and this would be one such area where it can exist. If editors feel VNOT is not the right place for it, the proper approach might be to flesh out the changes at WP:EP following the NOCON move, bring the policy up to date following discussion, and then decide if ONUS needs revisited. We may find more consensus at that point to remove it from VNOT and/or rephrase accordingly, but now doesn't seem like the time. -- GoneIn60 (talk) 18:31, 2 September 2024 (UTC)
- I support moving NOCON to EDITING POLICY (being sure to leave a link to NOCON in CONSENSUS). - Butwhatdoiknow (talk) 16:41, 3 September 2024 (UTC)
- I'm fine (support) with moving to EDITING POLICY. Alanscottwalker (talk) 19:57, 3 September 2024 (UTC)
- Support per discussion above.Selfstudier (talk) 08:50, 4 September 2024 (UTC)
111