Non-admin closure with no reason stated other than "the result was keep." Attempted to discuss but was told to come to DRV. Relisting admin requested a source analysis which was then done and discussed between editors. Would feel more comfortable with an admin closure as the debate is about interpretation of WP:NMUSICIAN, with keep votes claiming an award is sufficient for notability. CNMall41 (talk) 21:13, 6 November 2024 (UTC)[reply]
Endorse. Not a WP:BADNAC. The AfD nominator expressed disagreement with many keep !votes, so there was some contention, but that's about it. The close is inherently non-controversial because the discussion could not have been closed any other way, obviously. An explanatory closer statement is not required, and that should not be a reason to overturn a non-admin closure.—Alalch E.23:37, 6 November 2024 (UTC)[reply]
Endorse overwhelming consensus to keep and overwhelming rejection of CNMall41’s source analysis, despite CNMall41’s attempts to WP:BLUDGEON the process. This seems like a fine NAC and there is no requirement for an in-depth closing statement. FrankAnchor04:29, 7 November 2024 (UTC)[reply]
I don't remember ever seeing an explicit "weak keep." I've certainly seen keeps where the closer has noted that it was just enough to be a keep, but that's different from a "weak keep." SportingFlyerT·C01:55, 10 November 2024 (UTC)[reply]
Endorse. Deletion review handles cases where a closer has failed to follow deletion process. It is not for cases where the deletion process was followed correctly but you do not like the decision that was arrived at. Stifle (talk) 10:55, 7 November 2024 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Rob Yundt – Restored to draft where it can be improved and mainspaced as soon as desired. Needed updates with time having passed negates any potential for G4. 11 year old AfD is not in force forever and we don't need seven days of bureaucracy. StarMississippi02:22, 7 November 2024 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Circumstances have changed. Yundt entered politics and is now a state senator-elect (see here and here), which is normally a clear enough basis for notability. A proactive approach of restoring the deleted article and allowing it to be worked on before he takes office is preferable to the standard practice of letting deleted revisions stay deleted and recreating a vastly inferior new article at some random point in the future. RadioKAOS / Talk to me, Billy / Transmissions 15:00, 6 November 2024 (UTC)[reply]
Restore to draft I don't think we need to have a deletion review of years-old discussions when circumstances change and the article is not salted. --Enos733 (talk) 16:08, 6 November 2024 (UTC)[reply]
@RadioKAOS: I don't think draftification is a bad thing at all here - it would just restore the old article, which would be 11 years out of date, to draft instead of mainspace. No one is going to oppose moving it to mainspace, this isn't "send to AfC." So we'd draftify the last version, you could update it to say he's a state senator and move it over. There's also nothing preventing you from just straight recreating it. SportingFlyerT·C17:47, 6 November 2024 (UTC)[reply]
Agreed. At minimum, all that is needed is for an editor to change the lede to "senator-elect" and restore it to mainspace. I don't think we need to overthink this (but the underlying reason for deletion was correct). I also note that WP:REFUND may have been used instead. - Enos733 (talk) 22:35, 6 November 2024 (UTC)[reply]
Speedy restore to draft per above, to allow any interested editor the time to add more recent sourcing so it is acceptable to be moved into article space (with or without the AFC process). I think this is a largely uncontroversial WP:REFUND request that does not need a full seven days' discussion time. FrankAnchor16:35, 6 November 2024 (UTC)[reply]
Restore Draft, but this doesn't require DRV. In DRV Purpose, point 10 says:
Deletion review should not be used… to ask for permission to write a new version of a page which was deleted, unless it has been protected against creation. In general you don't need anyone's permission to recreate a deleted page, and if your new version does not qualify for deletion then it will not be deleted.
The nominator claims this is a fork, but as was explained and unchallenged on the talk page, it is a subarticle. The nom does not seem to have noticed that explanation or the discussion at all. There may be a valid argument that some content should be merged somewhere, but probably from the parent article to this subarticle. Given rather minimal participation, I'd suggest this is at the very least relisted; if I was pinged (I was the one who commented and restored this before; I wasn't) I'd have voted to keep, and the result would likely be no consensus or a relist. Piotr Konieczny aka Prokonsul Piotrus| reply here02:36, 6 November 2024 (UTC)[reply]
Well, we didn't have any participants arguing to Keep this article which is one reason why I didn't relist this discussion. It's possible that relisting could have resulted in a different outcome but based on the participation in this discussion after a week, opinion didn't seem to be divided enough to warrant a relisting. LizRead!Talk!02:54, 6 November 2024 (UTC)[reply]
Endorse-ish if the argument had been deletion, there would have likely been enough consensus to do so. Three participants with a nomination suggesting redirection, one delete, and one merge/redirect is not a sufficiently anemic participation that we can assume consensus is invalid. But that brings us back to the question of how long and what sort of editing it would take to un-redirect an AfD-mandated redirect. What's the process for doing that other than DRV? I don't know that we have one. Jclemens (talk) 06:26, 6 November 2024 (UTC)[reply]
Endorse as the natural outcome in that AfD. Yes, zh-wiki, with their different guidelines and conventions, has a separate article on this. Is that a reason to fork it here? Relisting seems like a waste of time, but if that's what is needed to convey a sense of broader consensus, so be it. Owen×☎09:46, 6 November 2024 (UTC)[reply]
Weak endorse Neutral there is consensus to not keep the article. With a split opinion between delete and a WP:ATD, the latter is usually the preferred option. However, I consider relisting to be a valid option as well based on the DRV nom statement and somewhat limited participation in the AFD.FrankAnchor14:28, 6 November 2024 (UTC)[reply]
Removing my weak endorsement. Generally when the DRV is significantly longer than the AFD, it is likely that is more that can be discussed at the AFD. I do believe the close was correct but a relist can be useful in this case. FrankAnchor18:57, 13 November 2024 (UTC)[reply]
Endorse. Editors agreed around "Most of the content here duplicates". It is possible to restore the article so that the content does not duplicate.—Alalch E.15:17, 6 November 2024 (UTC)[reply]
Endorse as a valid reading of consensus. It should of course be noted that redirection is not deletion and should there be sufficient content to support an independent article it can be spun out upon reaching consensus at the talk page or by application of WP:BB. Stifle (talk) 10:56, 7 November 2024 (UTC)[reply]
