Modified DRV instructions

i have modified the DRV instructions, here.

DRV is suitable if recreation prevented by de-SALTing denied; re-creation explicitly prohibited; or AfC decline/reject is disputed.

Otherwise, if the AfD is old, and you have overcome the reasons for deletion, then just re-create, and see if anyone else nominates it at AfD. --SmokeyJoe (talk) 22:58, 19 November 2020 (UTC)

I thought SmokeyJoe's language was pretty good, but I also agree about having a wide interpretation of "significant new information" and potentially drawing a line between "uncontroversial" re-creation (BOLD) and "controversial" re-creation (DRV). The instructions that are there now should be changed/updated, and I'm hopeful agreeable language can be workshopped, or if not at least on an RFC A/B proposal or something like that. Lev¡vich 08:05, 21 November 2020 (UTC)
  • My problem with SmokeyJoe's language is that it limited DRV, and we want DRV to be as welcoming as possible! I don't really see this as a problem that needs to be solved, as it comes up relatively rarely, and when it does people tend to "get permission" to recreate the article, which is technically welcoming. The problem we're trying to solve here is to make clearer the fact you don't need to use DRV if the AfD you're challenging is old, you rewrite the article, and you now think the article now passes WP:N, as opposed to limiting the scope of DRV. SportingFlyer T·C 08:45, 21 November 2020 (UTC)
  • I think we disagree. People SHOULD NOT use DRV if they have not already tried REFUND for a REFUND, or tried RFUP for de-SALTing (and noting the highlighted instruction they’ll find there), and really should be discouraged from coming straight to DRV with new sources after a years old AfD. DRV SHOULD NOT be saccharine sweet, like the old AfC “decline” messages were in giving a plain letter reading that told them to do unproductive time wasting things. Sure, if someone comes to DRV ill-advised but in good faith DRV admins don’t speedy close, we participants give feedback, but this is not an efficient process compared to the recommended path, with is typically REFUND and add new sources to the draft. The problem we are trying to solve here is to limit well meaning Wikipedians like RMcC giving poor advice based on the poor DRV instructions. DRV is a review process, it for for catching errors, in judgement or process, and for providing running community based education where there have been errors. DRV should NOT be routinely used for notability assessments. —SmokeyJoe (talk) 09:54, 21 November 2020 (UTC)
  • I'm not sure we do, I think we're just approaching the problem from a very different angle. DRV isn't saccharine sweet now and works as intended in the vast majority of cases. I am not trying to expand the scope of DRV, but as an appeal of last resort, we do not want to make it harder for someone to use DRV by limiting the instructions. Users will be mistaken sometimes, that's fine, but that's exactly what DRV is there for. I really don't think this is that big of a problem, I don't think the instructions are that unclear, although I think they can be improved slightly to make clear you can work around an old AfD by producing a new article. The proposed instructions limited "significant new information" to three very specific instances, which I do disagree with quite firmly. SportingFlyer T·C 16:38, 21 November 2020 (UTC)
It should be used for 2 purposes: to determine if it's good enough to pass G4 (the alternative being to trust a single admin's judgement), and to deal with a SALTed page. 109.186.211.111 (talk) 16:26, 21 November 2020 (UTC)
WP:RFUP should be used for desalting, which includes asking the salting admin first, if they are active. DRV should be reserved for a refused de-salting request, and should not be the port of first call. This is not to say that such requests should be speedily rebuffed, but that Wikipedians should be able to easily understand the instructions when advising newcomers on the best course of action. —SmokeyJoe (talk) 20:23, 21 November 2020 (UTC)
  • They couldn't necessarily have easily gotten a refund. WP:REFUND states: This means that content deleted after discussion—at articles for deletion, categories for discussion, or miscellany for deletion among other deletion processes—may in some cases be provided to you, but such controversial page deletions will not be overturned through this process. Copyright violations and attack pages will not be provided at all. While boldly recreating's (almost?) always an option, DRV's purview should allow for discussion about whether REFUND is appropriate. We disagree on that. SportingFlyer T·C 22:23, 3 March 2021 (UTC)
  • No one ever said anyone should "necessarily have easily gotten a refund".
    What the instructions should say, is try asking for a REFUND first. Alternatively, one can ask the deleting admin, or indeed any admin. There are two very big advantages to this: (1) you may get the page undeleted immediately and painlessly; (2) if refused, you should get a reason, and then you have a focused point for discussion at DRV.
    Something should be said also, both here and at REFUND, about whether to request REFUND direct to mainspace, to userspace, or to draftspace. There is too much implication that REFUND requests are to undelete back to mainspace, when WP:Userfication or undeletion to draftspace should probably be the default for an AfD-deleted page.
  • There is no intention from me to restrict DRV's purview to discuss anything. The intention is to inform and advise people of the easier and more efficient alternative path. --SmokeyJoe (talk) 23:19, 3 March 2021 (UTC)
  • The way things currently work though is that you can't REFUND a page to mainspace which was deleted at AfD "controversially," which I interpret as "deleted after discussion/not soft-deleted." For instance, there's no way the United Airlines Flight 1175 page should be restored to mainspace at REFUND, but DRV could conclude that's possible. My only immediate suggestion would be this change, but I'm still not sure about it: if significant new information has come to light since a deletion that would justify recreating restoring the deleted page; SportingFlyer T·C 23:40, 3 March 2021 (UTC)
  • Where restoration in mainspace is obvious, it should be done without a week or more at DRV. Where it is not obvious, it is a very good idea to have a live draft. --SmokeyJoe (talk) 03:00, 4 March 2021 (UTC)
  • Yes. But this is a principle. An editor will quickly find out when asking for a REFUND. Do you oppose putting in information and encouragement for editors to use REFUND or to ask the deleting admin, and encouragement to ensure there is a draft before going to DRV arguing “new sources”? —SmokeyJoe (talk) 21:36, 4 March 2021 (UTC)
  • I think we need to workshop some outcomes here, because I do generally oppose that. Why? REFUND doesn't work if a deletion was controversial, even if it's old. Admins come and go. And we shouldn't require people to create drafts when they bring new sources, if they're requesting a restore. I for one don't really mind when someone comes to DRV with the odd "can I recreate this page?" since the workload isn't that great anyways. I propose finding examples of DRVs that you'd like to discourage in the future and then figuring out how we change policies across the project to fix those. SportingFlyer T·C 22:59, 4 March 2021 (UTC)
  • Workshop before edit? OK.
    REFUND doesn't work if a deletion was controversial, even if it's old. That assumes "REFUND to mainspace". I am thinking to specifically suggest "REFUND to userpace or draftspace".
    The admins at REFUND I have noted to be experienced and sensible. However, the header documentation at REFUND looks like it has grown without review for a long time, it needs simplification to achieve readability even more than DRV/Purpose. --SmokeyJoe (talk) 23:07, 4 March 2021 (UTC)
  • Friday Night Funkin? Who says it’s out of scope. No, not trying to discourage these, but there was an easier option of asking the deleting admin to undelete now that it is no longer TOOSOON. If someone really wants to come to DRV then fine, but I want the instructions to inform of easier options for simple cases. —SmokeyJoe (talk) 13:07, 5 March 2021 (UTC)

Wrong deletion of Page Sandeep Singh Rissam

The page sandeep singh rissam has been wrongly deleted. Even when the page had enough of references and moreover the hindi language newspapers mentioning him were not considered. Why ? A notable person means a someone doing a work which is notable. Also it was wrongly mentioned in the discussion that the references have his name as passing name whereas most of the reference of news given had him as main person. The profile of sandeep Singh Rissam can also be checked by googling his name. Sunny50888 (talk) 11:34, 16 March 2021 (UTC)

This is the deletion review talk page; please follow the instructions on the project page and post your review there. OhNoitsJamie Talk 13:59, 16 March 2021 (UTC)

Involvement of closer in DRV

See: Wikipedia:Deletion_review/Log/2021_March_16#Mavis_Amankwah. Courtesy ping @WilyD: as initiator of discussion.

Hi all, at the above linked discussion, I offered an endorsement for my own close, while providing a couple of procedural notes in reference to statements by the nominator. You can see my comment there.

In response to this, WilyD stated that "XfDs need to be closed by an admin who can at least act as a disinterested party", and when I questioned how I was not disinterested, this was clarified with "an admin closing a discussion as a disinterested party acting on community consensus wouldn't come to DRV to argue for a particular outcome".

My personal view was that the closer of a discussion could contribute willingly to any deletion review, given it is an assessment of the process rather than the article content itself. However, I will concede that I am frequently wrong about current process, and may be wrong about this also. Either way, I would appreciate some clarity from the DRV community about to what extent, if any, the closer of the discussion can be involved and advocate for their close to be endorsed (a lot, some, or not at all).

Cheers
Daniel (talk) 01:18, 19 March 2021 (UTC)