Knowledge talk:Deletion process/Archive 8

3503:

currently universal use of the "no consensus" option, and the feeling by supporters that "soft delete" would be more appropriate in most cases. But I believe "no consensus NPASR" should still be available per closer discretion - although I would like to see it used more rarely, and with a closer comment as to why they did not choose "soft delete". That's why I reordered the options but did not prescribe; I thought listing "soft delete" first implied it as the default, with the others listed as options, with closer discretion maintained. I do agree with your improvement to the first sentence. Hmmm, thinking further about it... how about adding an option "if the closer feels that the article should be kept or that consensus to delete has not been reached, they should post a !vote instead of closing"? Because if the feeling here is that these are unopposed PRODs, but the closer doesn't agree with deletion, they are in effect opposing the PROD - which reopens the discussion, and if no further comments are made, it allows the next closer to choose "no consensus".--

2360:, per the logic you have just expounded. In effect this was an uncontested PROD, and it had greater exposure for a longer time than a PROD. IMO it should be treated like a PROD, i.e., deleted but restorable on request. BTW I am wondering: in the dozen cases you found that were closed as Keep, how many were NAC closures? I will share my own recent experience as someone preparing for RfA: People who aspire to adminship want to do NAC closes at AfD to establish a record of competence at them. And some people just like to do NAC closes for whatever reason. This can result in a kind of competition to find and close the (really very few) AfD discussions that are eligible for NAC closure. Basically, there aren't enough "obvious keeps" to go around, for all the people who want to do NAC. I wonder if this creates a kind of incentive to close these no-quorum cases as "keep"? This is just speculation, I don't have any evidence that it's the case. -- 3802:

the nomination was valid in the first place) should have a standard result rather than left to the personal inclinations of whoever happens to be closing. A PROD is a very similar scenario not just in the sense of being about deletion but also because when a PROD expires, it's a very matter-of-fact scenario wherein the "closer" acts based on very few variables: is the PROD valid? If yes, then delete or remove it as would anyone else. There aren't enough variables for something like "removing PROD without prejudice to someone immediately re-adding it". The same is true here. The would-be closer can effectively take down the PROD notice upon expiration by weighing in at the AfD or close a standard way (a standard way for which we can hope this thread will generate a consensus). --—

3282:- on the occasions when leaving the article visible would cause actual harm to the encyclopedia, I imagine there is already a speedy deletion reason which can be invoked. Bringing an article to AfD indicates either that the proposer thinks discussion is necessary before it be deleted or a prod was rejected, in neither case is there implied support for deletion without discussion. In the case of an article which has been edited by several editors, there is presumably some implication that they think it should be retained, even if they are not watching it (I tend to avoid editing an article if I think it should be deleted, since my time will have been wasted). -- 3233:

to express a new kind of reasoning. Or maybe there's some feeling that the nomination is wrong, or there will be an unfair practical impact on some editor(s), or drama is likely, or the timing is not right. These are generally NOT just like PRODs, it is generally clear that there should be a discussion before deleting. These either need to be dealt with, by us facing the difficulties, or closed no consensus. No consensus effectively means either that keeping is the right thing, permanently, or keeping is right, at least for now. I appreciate MelanieN's summary that the consensus is not to change. --

3787:

people who have commented here (which is not clear), there are still some who disagree. This is not a vote. Our goal is consensus if possible, rather than majority rule being imposed over minority opposition. What I am trying to do - what I always try to achieve with these exercises in multiple draft versions - is to work toward a wording that pretty much everyone can accept. In this case I think a re-ordering of the existing options, and a re-emphasis on what is recommended, might well be acceptable to everyone. --

706:- Actually my removal was a bold removal, so if anyone re-instates the removed text, I won't pull it back out. The point is, it was put in boldy, now it's removed and being discussed, so if the concern is to follow policy and guideline, the proper steps would be, get consensus via this RFC, if the consensus is for the belief that admins can't just close out NACs as they had before, then the wording needs to stay out. If the consensus is that they can, the wording can be returned just as it was. 3904:

outcome is to abolish No Consensus and replace it with Soft Delete, then this thread is indeed futile - because that idea is not going to pass. On the other hand, I am hopeful that we COULD pass a proposal to make Soft Delete a more visible and even encouraged option - while leaving No Consensus as an option for those who prefer it. As for Keep vs. Speedy Keep in the (likely very rare) case of an invalid nomination which has somehow survived unchallenged for three weeks, I am open to either. --

1021:

CSD was less robust, and people in general were bad at selecting articles that actually deserved deletion. So non-admins were allowed to close obvious "keep" discussions in order to reduce admins' workload and get some "admin practice" (for prospective RfA candidates). Just because TPO does not explicitly mention this as an exception (assuming it even applies to closures) doesn't mean the intent isn't there that mistakes by non-admins acting in an admin-like capacity can be overturned. --

31: 2119:

article will be restored (same as pretending like the article was never nominated for AfD but was instead deleted under PROD). Formerly (like several years ago), admins were advised to close discussions with little participation as "no consensus," but it didn't make a whole lot of sense given that if they had nominated it under PROD, the article would have been deleted already. So the change in policy was made. --

3009:- I recently nominated an article that had no !votes and was closed as "No consensus", After reverting the close - the afd got 1 delete !vote and was subsequently deleted - I firmly believe with or without that !vote it would've been soft-deleted which brings me on to the next point - More often than not I see the "no votes" AFDs being closed as No Consensus when it's obvious half can and should be soft-deleted,- 2286:. Disclaimer: technically I've been plenty involved in the AfD process (including closing them in situations where this proposal would have applied to me). However, given I genuinely couldn't care less and the fact that the outcome of "no consensus" is fairly apparent below, it seems safe enough to make this call. If someone else feels more qualified to close instead, please, by all means. :P -- 3566:

scenarios by definition do not vary except in the validity/quality of the nomination? Wouldn't it just come down to closer preference (i.e. where we are now)? If I understand MelanieN's latter idea correctly, it would present soft delete as the default action while presenting a clear course of action if the closer feels it should be closed as no consensus. That makes the most sense to me. --—

3720:

all or almost all such cases are being closed as "no consensus", thus defaulting to keep, by both admins and non-admins. The discussion here is an attempt to change the culture, so that "soft delete" becomes more of an option - perhaps the norm - rather than the time-wasting need to renominate for deletion or the retention of articles that nobody thought it worthwhile to keep. --

3924:

nothing in its particulars to judge). Regarding what can/can't pass, I can't agree. The majority of support opinions above look to be supporting, at weakest, "it should be soft deleted at the admin's discretion" which is quite far from a basis on preference. Yes, yes, majority isn't everything, but I'd like to think that if some consensus can be reached about what is preferred

1891:

problem with a non-admin reopening, because it would also represent a problem had it been an admin reopening. The poster I questioned has made assertions that are plausible based on reading the guideline, but I'm wondering if the assertions are also founded in practice. Examples might include both NAC reopened by nonadmins, and NAC reopened by admins.

3762:

rationale goes unnoticed -- and is even relisted two or three times -- for so long such that the first person to act on it is the no quorum closer...but if it does happen, it would be a speedy keep. There is likewise nothing "speedy" about a CSD much of the time except insofar as it can be done without discussion when appropriate. Such is the case here.

3919:

no consensus is "an option for those who prefer it"? Flipping that, the closer's preference has more practical significance than the community's preference. Documented encouragement would mean it's the community's preference, but that's immediately negated by "no consensus an option for those who prefer it". Saying it comes down to the closer's

2633:. If no one comments in the deletion discussion, the closer usually assumes that there is no contest to the nominator's opinion. If the possible closing admin/non-admin has an opinion that differs from the nominator's while reviewing the discussion, then it should be voiced in the discussion instead of the discussion being closed. 4010:

and for a longer time - and in all that time nobody said they thought the article was worth saving. But if someone as experienced and respected as DGG disagrees, then it is simply not going to happen. Those of us who proposed this idea should instead focus on trying to make sure there are fewer discussions with no consensus. --

3488:

changed "If an AfD nomination has received no comments" to "If an AfD nomination has received no substantive opinions or analysis." I think that's closer to what we mean by "comments", which is otherwise much more broad and inclusive of administrative notes, off-topic comments, very general neutral questions, etc. —

3951:

re-reading the discussion, I think this is a classic example of how wikipedia process works: find a minor problem,and propose a complex solution. And in fact,as often the case for complicated fixes, it is counterproductive to the basic purpose of deletion policy: it puts borderline articles where

3923:

makes the decision arbitrary based on the individual who closes it. Whatever is stated about soft delete should preclude personal preference. The problem is, as I've said above, preference is all there is when multiple options are given and there's no role for judgment (i.e. a standard situation with

3761:

The phrase "speedy keep" is a little weird, yes, but still seems appropriate. If I nominate an article with the rationale "I don't like it" and nobody notices for three weeks, surely it still qualifies for Speedy Keep. This is the same situation. It should almost never happen that an invalid deletion

3719:

I am getting the feeling that people want "no consensus NPASR" to continue to be an option in this kind of situation, even if "soft delete as an uncontested prod" should be the recommended outcome. This situation (no quorum) seems to come up a couple of times a day. Recent research has suggested that

3465:

If an AfD nomination has received no substantive opinions or analysis from any editor besides the nominator, even after two or three relistings, the discussion may be closed at the closer's discretion and best judgment. If the closer determines the nominator's rationale to be valid, the nomination is

3380:

If an AfD nomination has received no comments from any editor besides the nominator, even after two or three relistings, the discussion may be closed at the closer's discretion and best judgment. If the nominator proposed deletion and their rationale is valid, the article can be considered equivalent

3232:

Arriving here late, I see the discussion below may have reached a conclusion (not to make a change). I agree with that. I observe that the cases where there are no votes--and/or where I don't vote--are ones which are difficult, where it would take substantial effort to figure out what's best and/or

3155:

Rule creep. This is not a common problem, and can easily be solved by renomination. A few frustrating non-deletions is not adequate case for introducing an entire new procedure. Soft close is sufficiently new that it would have to be incorporated into the procedures at many places, and I think at the

2936:

I agree that the Altai discussion was correctly closed as "No consensus." IMO that really wasn't a "no quorum" case, because multiple people participated in the discussion; it's just that none of them said "keep" or "delete". The proposal here would encourage a "soft delete" close in the type of case

3671:

As minimal modifications of this, (1)if the admin thinks it should not be deleted, it it ought to be keep, not SK. SK implies there is something wrong with the nomination, not just that the admin disagrees. (2) An argument agains the deletion , proposing am ere or the like, or something other

3454:

To me the draft above reorders the list without really implementing the proposed changes above. In other words, the same options are presented without clear preference. If the nomination is valid, it should be considered as an uncontested prod. If it's not a valid nomination to begin with, it should

1890:

It seems I should reiterate the framework of the discussion here to answer that question. The premise of this RfC is that non-admins reopening a discussion is problematic and that admins reopening a discussion is proper. I've objected that the problem in the initial example was not an example of a

1838:

The last thing we want is edit wars over NACs of deletion discussions. However, if an editor feels that the close was inappropriate then there should be a mechanism to air their concerns. The best way to do that is to ask an admin if they think it was a non-appropriate closure based on the concensus

1599:

Participation here is not really adequate to form a rock-solid consensus, but there does seem to be a general agreement that, as a rule, non-admins reversing each others' closes is not a good idea and it's usually better to seek input from an admin or take it to DRV. As with any rule, this will have

1082:

Thanks to all for chiming in and pointing out to this editor that their relative inexperience has led them to an interpretation of policy that conflicts with how it has been executed consistently for 7 or so years. As I wrote on ANI, I had the courage of my convictions that I was acting in line with

942:

Well, if TPO (which is a guideline, not a policy) forbids admins from acting according to NACD (which is also a guideline), one solution would be to simply forbid all NAC closures, and say that only admins can close discussions from now on. However, I don't think that would be a positive development

761:

This is longstanding practice. Admins are entrusted by the community, via the RfA process, to make this kind of decision. Nobody "vets" or approves of non-admin closers, they just jump in and do it as volunteers. Their help is appreciated, but ONLY if they are willing to defer to review and possible

677:

NACs should be rare. Want the power to close discussions? Submit an RFA. DRV is designed to allow the community to review (generally) admin decisions relating to deletion. Non-admins can't delete articles so the number of non-admin closures being brought to DRV should be pretty low and people take a

290:

Closing discussions in which you have offered an opinion or for a page in which you have a vested interest (i.e. a page that you have edited heavily) should be avoided. The sole exception is if you are closing your own withdrawn nomination as a speedy keep and all other viewpoints expressed were for

3918:

Here you're saying "abolish" and previously "outlaw", which is pretty loaded language. Nothing on Knowledge is "outlawed" because there's always the caveat to ignore all rules if necessary. Regardless, what is the practical result of making soft delete "a more visible and even encouraged option" if

3867:

Comment regarding "rule creep": I don't see this as a new rule, but rather a re-ordering of the options currently in the guideline here. Right now the guideline recommends: relisting; closing as No Consensus; "closing in favour of the nominator's stated proposal" whatever that means; or (fourth and

3801:

A no quorum situation simply lacks the variables involved with most decisions made by admins/closers all over Knowledge that call for such gray area: assessing consensus, evaluating arguments, interpreting policy, etc. Instead we have a standard scenario that (assuming we get out of the way whether

3786:

Version 3 omitted the No Consensus option entirely; Version 4 restores it. I am thinking in terms of the possible. If we propose to outlaw No Consensus and make Soft Delete the rule - that is probably beyond what is possible. We are looking for consensus, and even if that is the majority opinion of

3580:

Sorry, I kind of dropped the ball here. You are correct that I kind of changed my tune halfway through - I started out wanting to maintain the No Consensus option and ended up saying they should !vote. How about this for a more prescriptive set of guidelines? And we can ask people in the discussion

2833:

comment from the discussion above. I believe closer discretion should be retained, but the recommended closure should be "soft delete", since the result of the discussion is pretty much the same as an uncontested PROD. Also, if the consensus here is to recommend "soft delete", we need to figure out

2378:

Since you ask Melanie, two of the closers in my sample were admins and three not, but I didn't raise this intending to point fingers at particular people, rather to urge a rethink of the guidance that anyone closing these non-discussions is working to, whether admins or not. Congratulations, by the

2318:

section this is left to the closer's discretion. They can "keep" with no prejudice etc., soft-delete, or follow the nominator's proposal (usually this will be a normal delete), or indeed do something else. However, most of these cases are currently being closed with the article kept. (I found 12 in

2209:

exists, but is it used in practice? (I think it is not usually used, but am not sure. It was not applied in one recent RfD that I followed.) Surely it should be used, always, when the redirect is not deleted, right? Or at least when the RfD discussion is essentially a request for deletion of the

2148:

There's continued misunderstanding. It sounds like it will be something less than deleting, but it simply is deleting. There's no way anyone besides admins can see the former article in order to decide to ask for its restoration. An editor commenting in the RFC below, assumes, perhaps reasonably

1690:

You mean at an AfD? No. That's what deletion review is for. Discuss it on the closer's talk page, alert a friendly admin, or take it to the due process. Re-opening a closed discussion is disruptive. It leads to edit wars where people repeatedly open and close the discussion, and then newcomers

1049:

Admin's are !voted in by the community on the basis that they are able to judge what's good for Knowledge and what isn't. Allowing anyone to close an AfD (albeit as a non delete outcome) is certainly subject to admin oversight and reversion if appropriate. I've also closed the similar discussion on

925:

I appreciate your passion, however, pull back a bit, or at least re-read your responses, you're coming across harshly, and I don't think that's your intent. Let me point out that as of this second, Admins can reverse NAC closes on AFD's, however, that idea is being challenged at this time as it

4009:

I am abandoning my attempt to promote this idea, or to find a consensus wording for it. To me it seemed obvious that an AfD where no-one comments but the nominator is the equivalent of an unopposed PROD. In fact it seemed even more delete-worthy than an unopposed PROD, since it had more eyes on it

3715:

I actually do think "speedy keep" is a misnomer; the discussion has presumably been at AfD for two or three weeks and is ready to close, so a simple "keep" would be appropriate; there is nothing "speedy" about it. They should explain, in a comment or their edit summary, why they chose that option.

3356:

is a special kind of deletion often used after an articles for deletion discussion. If a deletion discussion sees very little discussion even after being relisted several times, the administrator can close the discussion as soft delete and delete the page. However, in this case, the article can be

2438:

OK, the closure notices don't say "the result was 'keep'", they say "the result was 'no consensus'" but the effect is the same: no action is taken and the article sticks around. People may well be discouraged from trying a second AfD after the first one failed, not due to any arguments to keep the

1941:

I've reverted non-admin closes and if the circumstances were repeated I'd do it again. (I'd have reverted a sysop if they'd made the same close: some decisions are so dumb that they need to be unilaterally reversed.) It would be suboptimal if this discussion came up with a rule against reverting

1020:

is an attempt at wikilawyering IMO. Non-admin closes have always been subject to review and unilateral overturn by an admin; they were first introduced around 2005 to reduce the admin backlog at AfD. I remember back then, hundreds upon hundreds of articles showed up at AfD since PROD didn't exist,

3691:

This wording works for me. Might change "If the closer feels that deletion is not the appropriate outcome" to "If the closer feels that the nominator's rationale is valid, but that deletion is not the appropriate outcome, they can...". Otherwise we could consider an invalid rationale as "whatever

588:

and RFC is being conducted to determine whether the guideline should be edited or not. If you're going to determine the consensus of this discussion you should close it (a spectacularly bad idea after less than 24 hours, especially given the subject matter) but editing things while they are being

379:

which states inter alia "Inappropriate early closures may either be reverted by an administrator ("Decisions are subject to review and may be reopened by any administrator", from Knowledge:Deletion process#Non-administrators closing discussions) or could result in a successful request to redo the

3903:

I do think we need to allow for the opinions of people who just don't like the idea of deleting in no quorum cases. And I don't think that makes this thread moot. This thread is about ENCOURAGING people to use Soft Delete, or even making them aware that the option exists. If your only acceptable

3502:

Thanks for your input. This is more prescriptive than what I thought was being proposed. (As I said, that's why it's important to get actual language into the proposal.) In effect this eliminates the "no consensus NPASR" outcome. It's true that this discussion was inspired by what appears to be

2789:

for soft-deleted articles get rejected. AfD closers need to be explicit about when they mean soft deletion by actually using the words "soft delete" as opposed to just "delete," and UNDEL patrollers should feel free to restore an AfD with zero participation (not one, or two, for those cases the

130:

Well as a user I would be unhappy about a bot delinking them of my page. It is OK if the bot does something useful, such as renaming, but I think it would be preferable to let a redlink remain so that the affected user can take care of the situation. Perhaps they want to use a different box or

3487:

I left out relist option because it's already presented as having been relisted "two or three times". I left out the NPASR option because that seems like what this proposal addresses directly. I left out the deletion option because, well, our premise is that there's no quorum for that. I also

2118:

If someone nominates an article for AfD and after several relists the discussion receives no discussion or very little discussion, the closing admin can close the debate as "soft delete" and delete the article. But afterwards, if anyone wants the article restored for any reason whatsoever, the

3565:

The scenario being discussed is one without the variables of a typical AfD, so it doesn't make sense to me why we would have multiple viable ways to close if consensus emerges on a default action. In other words, how would we articulate what kinds of scenarios would make sense as NPASR if the

2964:– Prods can be declined, whereas AfD nominations usually cannot, with the exception of withdrawn noms with no delete !votes. Prefer to leave discretion regarding closures as it presently exists, rather than forcing delete closures for AfD discussions that receive no input. For admin closures, 3883:

I don't think that "keep" makes sense at all for the last as it has implications for future nominations. Again, as my comment above, this means that a nomination as "I don't like it," if it makes it to a no quorum close, would be closed as "keep" rather than "speedy keep" as invalid. I don't

1675:

As a description of best practice, implying that users should seek admin review rather than simply reverting closes they dislike is fine. I oppose making any stronger statement in either direction, however, because these cases are always going to need to be judged on their individual merits.

762:

reversal of their closures by an admin. Admins have been given the "keys" to do this; non-admin closers have not. If someone reopens a NAC close, the person who closed it should view it as a learning experience, from which they can gain experience and learn more about evaluating consensus.

3851:

If the closer feels that the nominator's rationale is valid, but that deletion is not the appropriate outcome for whatever reason, they can cast a !vote with their opinion, and allow someone else to close the discussion (which now is no longer a no-quorum discussion and not eligible for

1239:

I don't know if the admins are claiming the right to literally revert closes, but if so, that is something that would be good to discuss. I suspect that they are rationalizing reverts as expedient, and wouldn't object if we expanded the WP:NACD reopening guideline to mention WP:TPO.

1162:

I think this was closed too quickly. The issue of WP:TPO has gotten mixed into the discussion without being properly aired. In this entire discussion, there is only one example of an NAC being reopened. Not saying that it should be reopened, but IMO this is far from conclusive.

943:

for the wiki. Better solution: if anyone other than Scorch and Kosh actually finds this "conflict" to be a problem, we could add "admins reverting NAC closures" to the permitted exceptions at TPO. Even better: consensus could agree that TPO refers to comments but not to actions. --

3976:

be challenging the PROD system, which achieves the same result (deletion if no-one including the closer objects) with less visibility. The laudable attempt to find a consensus wording seems to be complicating the issue and paradoxically taking us away from consensus. To repeat:

2456:

And I agree with that suggestion. It would be nice if a few more people would chime in here. Does the lack of participation mean nobody watchlists this page? And if nobody watchlists this page, what effect would it have to change the guideline even if it is decided to do it????

2327:

is placed and nobody objects, the article gets deleted: if an AfD is opened and nobody objects, the article is likely to be kept, even though the proposed deletion will then have had more exposure and usually been up for a longer time. Where's the logic in that? Proposal: that

3981:

Finally, "no consensus" shouldn't be the closer's verdict in AfDs with no participation; that term is more suitably applied where there was a debate which did not reach consensus. It should be either "no quorum: soft delete" or "no quorum: <keep NPASR/ keep / merge / etc:

1429:

My concern is more about deletion discussions (and AfD in particular), which is where I see most of this behavior. Part of the problem, I feel, is that people at AfD are often new(er) content creators and don't know the ins and outs of policy as well as RfC participants.

554:

the admins to remove inappropriate AFD closes if the close is shown to either be something only an admin can do (like a close to Delete) or the consensus can be shown to be wrong. This would put the onus on the NAC to document how a close was determined as well.

196: 4054:

Please can someone post a link to a "soft-deleted" article so we can see the difference between that and a "deleted" article? Although I occasionally click on deleted article redlinks to find the deletion discussion I have never until now seen the term "soft delete".

107:

Having just closed an MfD for several userboxes, I was wondering whether there's a way of getting a bot to delete their transclusions? I can't seem to find any instructions on this, and the boxes have a lot of transclusions - would take hours to sort it myself.

3700:

I think the SK scenario is when there's something wrong with the nomination (invalid) rather than the admin disagrees (which is the third scenario). Is there another wording you'd recommend other than "rationale to be invalid" that would make it clearer? --—

1658:

Yes, that is another issue, but I'm pretty sure I've seen uninvolved non-admins do it before too. It's hard for me to find examples, because I've participated in a lot of deletion discussions and read through even more without leaving a trace of involvement.

3065:

That's a good qualifier, and it's why we will still need closer discretion. If they feel the nomination is not well based in policy, they could and should close as "no consensus". If the nomination seems completely bogus they could even close it as "keep".

3672:

than deletion , is an opinion whether or not in bold. Some of the examples presented here ha such opinions. Any reasonable challenge is a reason for not considering the afd uncontested. (3)There needs to be a formal requirement for at least 2 relistings.

3267:

the closer's toolbox to be able to "soft delete" (which I presume is merely a courtesy blanking of the page) I don't mind that (especially in the case of a BLP), but it should definitely not be the automatic result of a no consensus / no quorum close. -

3093:

here that soft deletion at the admin's discretion and reversion on reasonable request is the appropriate way to go. I would also encourage closers to make a !vote themselves rather than closing a discussion that has no !votes other than the nomination.

1236:

Ahh, ok, but there is no consensus that WP:NACD takes precedence over WP:TPO. The issue of WP:TPO that was raised here was based on a misunderstanding that WP:TPO makes other editors' edits inviolate, and also, editors were using the word "revert"

4166:- make sure that you wait all the way until the script redirects to the discussion page before closing the tab and/or window - this will allow it to complete all steps of the task successfully. And if you did do that, well...then I've got no idea. 3370:

Here is what I think we are talking about with this proposal. An important point with this proposal is that soft deletion would NOT be forced or required. It would simply be made a more prominent suggestion in the options available to the closer.

1643:

The problem in the example, and I could give others, is that a participant is re-opening the discussion. This is not a problem of whether or not the editor is an admin, as an admin has been known to re-open an RfC whose close they didn't like.

3581:

above, do they want to keep the No Consensus NPASR option, or do they want such cases to be closed as soft delete as general practice? Here's a version of the guideline that does NOT offer No Consensus as an option. I guess this is Version 3. --

1990: 4146:

but for some reason it said error and didn't get on the page-seems to be a error there. (On another note yesterday a page I put up as a XFD didn't even get one for some reason until I redid it, and titles with ? don't seem to go through XFD)

3535:

Since the proposer said "recommend soft-delete unless the closer gives a reason to take another course," I don't think they are trying to remove NPASR as an option - it merely requires explanation as to why they deviated from the norm. --

2911:

is clearly deserving of disambiguation as it's a significant region and people in Asia. So, we should not let tiresome wikilawyering of this sort drive off contributors to the point that it damages the project. There are usually obvious

3835:

3608:

1735:

a discussion. WP:TPO does not say that the edits of other users are inviolate. The two key principles are (1) Don't change the meaning, and (2) We are here to build an encyclopedia. Reverting violates WP:TPO by changing the meaning.

286:

In cases where an administrator has deleted a page, including by speedy deletion, but forgot to close the discussion, anyone may close the discussion provided that the administrator's name and deletion summary are included in the closing

3311:

If a nomination has received no comments from any editor besides the nominator (or few in the case of AfDs), the discussion may be closed at the closer's discretion and best judgment. Common options include, but are not limited to:

255:

It's a little funny seeing another current RfC involving the same section of this guideline. If a NAC closes an AfD, can an admin revert the close if they disagree with the closer's interpretation of consensus and completely avoid

1448:

The premise here doesn't make sense to me. What evidence is there that the sentence is ignored? I don't see the relation between the sentence and the issue of involved editors (both admin and non-admin) re-opening RfC and AfD.

1217:

That there is a general consensus clearly emerging that this accepted process either does not conflict with the aforementioned guideline or takes precedence over it, both of which come up with the same answer to the RfC question.

276:

Deletion discussions must be decided in accordance with consensus and taking account of Knowledge policies and guidelines. If you are not familiar with deletion policy or the workings of deletion discussions, please avoid closing

1407:) has been maintaining it since 2013. It's not a long list, but there are cases when a non-admin close is contested and subsequently reviewed by an administrator; some have been endorsed and others reverted or the RfC reopened. 3928:, that it is implemented in a way that has real practical effects. Anyway, with this I'm feeling like I've posted more than my share to this thread so will sit in the timeout chair until others have had a chance to weigh in. — 2636:

In other news, I'm not sure why we're discussing this; I would believe that my belief is common sense, and has also been the way that it has been for ages. Seriously, this discussion, to me, seems like a solution looking for a

1981: 455:

does not have any strings attached, so in the current text any admin can undo any NAC for any reason. It may or may not be particularly appropriate, especially if the admin participated in the discussion, but it would still be

3888:

the idea of deleting in no quorum cases (making this thread moot). Other than that, it seems like it would have to be based on either the article or on the nomination, both of which are addressed by the other options here. —

3455:

be speedy kept. And, as always, it should be implied that if a would-be closer strongly disagrees with a deletion, he/she can decide not to be a closer and instead weigh in, thus removing soft delete as an option. What about:

766:, this principle has been confirmed to you by many people, both here and at the original ANI discussion. Your stubborn refusal to accept it makes me wonder if you should be forbidden from doing any more non-admin closes. -- 2495:, if you have the data could you provide links to the 12 AfDs you mentioned above, where an AfD with no Keep votes was closed with No consensus? Having some examples could make it easier to think about this issue. Thanks, 2069: 1578: 2081: 3561:

The RfC just asks "Per the above, when deletion discussions have no comments what should the administrator do? Soft delete, keep, or some other action?" I understood "per the above" to mean "per the issue raised

2907:. This seems to be a tedious technical wrangle about disambiguation and so it's not surprising that most editors would soon decide that they had something better to do than get tangled up in that. But the word 2034: 3634:

If the closer feels that deletion is not the appropriate outcome for whatever reason, they can cast a !vote with their opinion, and allow someone else to close the discussion (which now is no longer a no-quorum

2173: 1342:

which is, as far as I can see, often ignored: I usually see involved non-administrators who disagree with the close reverting (though, they're often right) and sometimes even edit-warring to keep it open.

360: 303:

an admin can reopen, logic tells me that the statement is paired with the 5 criteria directly above (also how it is laid out in the guideline). If it is meant to be a standalone statement, it contradicts

238: 820:

Huh? The guideline at TPO says that in general one should not edit or change the comments of others on a talk page. I am baffled what this has to do with the case. A closure is not a "comment", it is an

3884:

understand including the third option unless some kind of explanation is given for when it could be an option. The only reason I can see of including it as an option is for the sake of those who don't

2149:

but incorrectly, that "soft deletion" means just courtesy blanking the page. It is not just that, the page is entirely gone. It's not saved in a Drafts area or anywhere regular editors can see it. --

1068:

There is no system of governance that is problem free. However, imposing the view that any passing non-admin can perform a close that can only be challenged with DRV would not help to reduce problems.

3045:

If there is a deletion discussion and nobody objects and the reasoning is valid then it should be soft deleted at the admin's discretion. Such a deletion should be reversed upon a reasonable request.

1154: 3952:

they will not be found to be improved, instead of where they will be found to be improved; it is a direct contradiction to the basic rule that deletion is the last choice among possible solutions.

957:

I think that your third proposal shouldn't be decided here, but rather on the respected talk page. We still have a lot of time for this RfC, so let's wait for other users to come along and comment.

3297: 2025:

without a rationale.Whatever be the result Keep, no consensus or delete. Feel Procedurally and by policy if one non admin's closure is reopened by an admin another non admin should not close it.

2517: 2269: 2560: 2179: 2093: 1083:

both policy and general precedent, although one naturally doubts themselves slightly when an editor so belligerently insists that you're wrong. Your kind words and confirmation is appreciated.

550:

I agree that it goes against TPO, as both are guidelines, it creates a situation where two equal proceedures say "yes" and "no" to the same thing. My suggestion (suprisingly) would be to

4034:, that is, that it may be restored upon request. An admin is obviously free to not grant the request at their discretion. (As a volunteer project, no admin is ever "forced" to use the tools.)" 3675:

But in any case, I quite frankly this is rule creep. The situation is not the common. Theo obvious thing to do is to simply renominate a month later. That almost always gets enough attention.

3175:

delete (soft or otherwise). It creates opportunity for abuse. Should be more input than the nom and closer. If there is no participation, try again. Not such a bad worse case: try again. --

487:

So you are telling me an admin can arbitrarily revert an NAC closure based on their own agenda not listed in that policy (preceding that first statement) and against the purpose of DRV? Also,

2077: 2070: 2251: 2040:

I would tend to agree with you. Particularly if there is no rationale, it suggests the closer did not have the experience to realise that it needed a proper explanation to go with a close.

3111:

as default. Entirely agree with the logic that it should be treated as though it were an uncontested PROD. I disagree with the wording in the subsection below, but will address it there. —

3868:

presumably last) soft delete. I am mostly trying to change the priority or order of the listed options, so that "soft delete" is the first thing a closer thinks of rather than the last. --

2420:

I just noticed that you said those dozen examples were closed as "keep". Were they actually closed as "keep", or was it "No consensus, NPASR"? I don't see "keep" as one of the options at

1614: 1637: 2851:

soft deletion as the default option when there is no quorum, per MelanieN. There's nothing to stop a closer from specifying something like "on request, may be restored by any admin".

2228: 1935: 1994: 1909:

Sorry, but I don't have any examples. This is a guideline discussion about a "what if?" situation, i.e. what do we do at some future point in time when a particular event occurs.

3772:. Certainly those opposing want to retain NPASR, but I don't think that's what you meant. Maybe I'm misunderstanding your point or improperly reading into the opinions above. — 2539: 2257: 3474:

result means the article is deleted but can be restored for any reason by any administrator upon request. If your article was soft-deleted, you can request it be restored at

2049: 1929:

I think you can just ask an admin or go to DRV. I suppose a non-admin could revert a NAC but it would accomplish little, ultimately someone needs to make a binding decision.

2196: 1781:

is another. Non-admin closed as "keep" at a time when there were five !votes for "keep" and five (counting the nominator) for "delete". Reopened and relisted by an admin. --

1390: 3389:

result means the article is deleted but can be restored for any reason by any administrator on request. If your article was soft-deleted, you can request it be restored at

2545: 2214: 3768:- Those supporting above, other than King of Hearts, look to all be favoring soft delete by default, for the AfD to be treated as a prod, and/or to say, as Chillum, that 2565: 3877: 3448: 366:

Policy and practise are both clear that any admin can revert any NAC for any reason. The rest of your TLDR rant is simply making you look childish and petulant. Thanks.

2860: 1718: 179: 3361:.nd delete the page. However, in this case, the article can be restored for any reason on request. If your article was soft-deleted, you can request it be restored at 2671:

checked a dozen discussions where there was minimal participation and no "keep" !votes, but all 12 were closed as "no consensus" - which of course defaults to keep. --

2550: 1745: 851:

P.S. As for following vs. violating guidelines: the guideline for non-administrators is that they are only supposed to close cases where the result is pretty obvious.

2988:

True, AfD nominations cannot be declined, but a "keep" comment can be made, which takes the discussion out of the realm of "no quorum" that we are discussing here. --

2063: 3855:

At the closer's discretion the discussion can be closed as "no consensus NPSAR", but they may wish to add a comment explaining why they did not choose "soft delete".

3575: 2555: 2979: 2696:

Wow, it seems that we really do have a problem here, given that it seems common sense results may vary. In that case, I bid this discussion to carry on valiantly.

2570: 2522: 1041: 2925: 2528: 1293: 3190: 3120: 2997: 2810: 2139: 1700: 1307: 380:

process at Knowledge:Deletion review. " That's pretty clear that reverting admin can act on their own authority without needing a consensus at DRV behind them.

161: 140: 4156: 2950: 2824: 1790: 1768: 1653: 1276: 1172: 784:

I would need a ban (or how a ban would help the community) if I we are not debating my ability or my closure(s). I am debating the ability of admins to reverse

690: 601: 3937: 3913: 3898: 3811: 3796: 3781: 3729: 3660: 3590: 3556: 3530: 3512: 3497: 2534: 1915: 1900: 1881: 1863: 1668: 1514: 1500: 1486: 1472: 1458: 1249: 1227: 1208: 1186: 1109: 717: 566: 4133: 2165: 748: 3224: 3103: 2904: 2512: 1505:

In the sentence, "Decisions are subject to review and may be reopened by any administrator.", I see the word "administrator", but nothing about non-admins.

1077: 994: 976: 903: 872: 846: 815: 775: 3035: 2655: 1126: 1060: 668: 617: 527: 510: 482: 440: 370: 4117: 3291: 2843: 1998: 1983: 1778: 1092: 952: 937: 731: 265: 3840:

If the closer determines the nominator's rationale to be valid, the nomination may be considered equivalent to an unopposed PROD and can be closed with a

3710: 3686: 3249: 3210: 3051: 2895: 2768: 2743: 2711: 2680: 2588: 2504: 1959: 1439: 1417: 4064: 4019: 1756: 1685: 4024:

I like the concept, the problem is the implementation. I think rather than go about it this way, try to see if you could get support for the following:

3075: 2790:

deleting admin has discretion over soft vs. hard and when not explicitly specified it is assumed to be hard) even if soft deletion is not specified. --

2487: 2466: 2451: 2433: 2391: 2369: 1845: 1825: 1811: 1572: 1177:

And the issue of WP:TPO has also been deemed irrelevant by several uninvolved commenters. Besides, Scorch, who initiated the RfC, closed it themselves.

3274: 2883: 2408: 384: 3613:

If the closer determines the nominator's rationale to be valid, the nomination is considered equivalent to an unopposed PROD and can be closed with a

3167: 4177: 4042: 3302:

I find it is often helpful in a discussion like this to try to come up with the exact wording that is being proposed. Here is the section currently:

2344: 3963: 722:

I've restored it. Your removal was bold and in good faith, but premature. It should stay in the guidelines UNTIL consensus develops to remove it. --

124: 4000: 2938: 2756: 2471:

Good point: according to the Page information link this page has 237 watchers but we don't know how many are currently active. I've crossposted to

2294: 1267:

I've updated the WP:NAC essay to change the word "reverted" to "reopened" with the edit comment "revert is not normative practice as per WP:TPO".

1839:

shown. If the admin concurs, then he/she (i.e. the admin) can reopen it. If not, then the decision stands and we avoid a lot of potential drama.

1284:

The issue with the word "revert" is confounded on this talk page in that it is being used with multiple meanings, and in some cases ambiguously.

191: 2941:. And this proposal would not REQUIRE a soft deletion; closer discretion would be maintained and would obviously have been used in this case. -- 2752: 2751:

Well, for a sample I just scanned through a single day's log: January 30, 2015. There were two no-quorum discussions closed as "No consensus":

1354: 1335: 678:

pretty dim view of bad NACs there. If you're a non-admin and your decisions are being overturned at DRV then that's a big problem in my view.

2085: 2006: 1545: 1394: 1376: 4139: 2354: 2311: 1363:) Now, if my observations are true (and please, tell me if they are or not) - that most of the time, this rule is not known or ignored - 4143: 4030:

in an XfD, which had no commenters other than the nominator, may be considered a "soft delete", which means it is to be treated like a

2112: 1533: 796:. Admins shouldn't be exempted from a guideline. Third of all, it goes against the use of DRV and once again, the action violates TPO. 94: 86: 3014:

So personally I think No consensus type AFDs should be closed and soft-deleted by Admins only - If anyone had an issue we always have

2624: 272:

says nothing about an admin being allowed to do this and only states the following points for basis of an admin reverting a closure:

3218:

There's a few common cases where SOFTDELETE is counterindicated, it is often the right answer, but not uniformly so. Also per DGG. --

2615:

Per the above, when deletion discussions have no comments what should the administrator do? Soft delete, keep, or some other action?

421:; it is not enforceable nor does it reflect community consensus over the ability that "any admin can revert any NAC for any reason". 340:"Deletion Review may be used: 1. if someone believes the closer of a deletion discussion interpreted the consensus incorrectly;....." 81: 69: 64: 59: 1477:

Perhaps you are thinking of the Template used in closing the discussion, that says that the page should not be edited thereafter.

859:

five (counting the nominator) "delete" !votes when you closed it as "keep". That is a textbook example of a discussion that should

2834:

how to convey that consensus to current closers. Right now they all seem to be closing no-quorum discussions as "no consensus". --

4084: 1298:

Agree with that change. My opinion is that as long as the original close is mentioned either up top or at the bottom, it's fine.

2439:

article but for mere lack of interest. My suggestion is for the default action in such a case to be soft-delete rather than none

376: 2274: 3144: 1633: 1568: 1100:

The value of this oversight is quite clear, and the AfD that led to this discussion is a pretty clear example of that value.

792:

if I was asked, but I wasn't and it wasn't discussed with me before he re-opened. Second off all, it is a clear violation of

3550: 2804: 2472: 2306: