- Air Canada Flight 018 Stowaway Incident (talk||history|logs|links|watch) (XfD|restore)
I was very surprised to see this article closed as a keep. This started out as a garden variety WP:NOTNEWS, and while sources were added to the article, I think the closer incorrectly ignored the delete !voters who commentated after the addition. The WP:GNG/WP:EVENTCRIT analysis by the closer comes off as a bit of a supervote considering nobody discussed WP:EVENTCRIT. I myself did not follow the AfD closely and did not realise it had been improved until I checked the close, but I would have reiterated my delete !vote. I'm asking that this either be relisted or re-closed as a no consensus, so it can be easily renominated in the future. (Also entirely ignored at the AfD were possible issues with WP:CRIME.) SportingFlyer T·C 10:41, 23 October 2019 (UTC)[reply]
- Endorse-ish - I probably would've closed as no consensus - there's a lot of asserting back and forth about NOTNEWS, though it's not straightforwardly applicable and they're largely just asserted opinion - more detail on the review of security procedures could push that argument; as it stands, it's extremely skimpy, but not wholly untenable, so it's hard for a closing admin to strongly favour either position as a closer. The tenor of the discussion also changed after the re-write, which means a straight headcount would be inappropriate. WilyD 12:21, 23 October 2019 (UTC)[reply]
- Endorse-ish. My habit, when there's been substantial work on the article late in the discussion, is relist to allow additional consideration of the changes. I agree that no consensus might have been a better close, but I can't get too excited about the difference between Keep and NC. I reject SportingFlyer's thesis that NC would make it easier to renominate in the future. That's invoking WP:RENOM, which while widely regarded as good advice, is just an essay. We don't overturn closes just to make them essay-compliant. I'm somewhat more concerned that the closing statement does sound like a supervote, and I'm also disappointed that Scott Burley didn't respond to this query on their talk page per WP:ADMINACCT. I wouldn't object to voiding the close and relisting this, but I can't argue that it's necessary. -- RoySmith (talk) 14:41, 23 October 2019 (UTC)[reply]
- @RoySmith: It's not just WP:RENOM I'm invoking here, to be honest - while WP:RENOM does imply this can be renominated more quickly (and, let's be fair, I'm typically skeptical if someone doesn't follow WP:RENOM in practice), any renomination of this article would have to explicitly deal with the fact it had been previously kept on similar grounds. If I see an article has been nominated for a second time and it was kept the first time, I will generally query as to what has changed which would cause the article to need to be deleted now. I don't think overturning this to no consensus (or relisting) is that big of an ask, either, as I don't think this could have been kept based on the discussion. SportingFlyer T·C 20:06, 23 October 2019 (UTC)[reply]
- Strong ugh- drip feeding sources to invalidate previous votes? Check. Insulting disdain expressed towards anyone !voting delete? Check. Supervote by a subsequently unresponsive admin? Check. This isn't going to get overturned, but it's also emblematic of everything that's wrong with AfD. Reyk YO! 16:47, 23 October 2019 (UTC)[reply]
- Overturn and Relist - There are two concerns. First, the close was definitely in the nature of a supervote. However, second, it appears that the Delete and the Keep were in response to two versions of the article. That calls for a Relist with the new version of the article. Robert McClenon (talk) 17:04, 23 October 2019 (UTC)[reply]
- If we complain about supervotes every time a closing admin explains what they're doing, all we get is an opaque set of unexplained decisions. Indeed, in cases like this, it's helpful for the closing admin to explain how they read the discussion, so we can see if there's some error in their read. Slagging them for trying to be helpful isn't helpful. WilyD 05:08, 24 October 2019 (UTC)[reply]
- Overturn and relist it doesn't sound like Lightburst's edits were that persuasive, given that two people who commented afterwards supported deletion and SportingFlyer wasn't convinced either. A relist would allow more of a focus on that version. Adding more sources doesn't necessarily address a NOTNEWS argument either, because the point of NOTNEWS is that something which gets a short burst of news coverage may not be encyclopedic. The comment by the closer that "The sources added to the article appear to satisfy both WP:GNG and WP:EVENTCRIT" suggests a WP:SUPERVOTE, because determining whether the sources meet notability guidelines is the responsibility of the participants, not the closer. Admins are expected to justify their actions when asked as well. Hut 8.5 20:54, 23 October 2019 (UTC)[reply]
- Endorse. Perfectly reasonable sensible close. The article was substantially improved during the course of the AfD, with supportive responses during the later half of the AfD. This calls for a close, not a relist. Give it time to settle. Follow the advice at WP:RENOM. --SmokeyJoe (talk) 00:37, 24 October 2019 (UTC)[reply]
- Weak endorse. Like some others, I would have closed it as NC, but I wouldn't go so far as to say the closing admin was supervoting because he mentioned EVENTCRIT. After all, participants had debated whether the event was of lasting significance and others cited international reporting, so although "EVENTCRIT" per se wasn't mentioned in the discussion, it was certainly being alluded to in regards to notability. JGHowes talk 02:27, 24 October 2019 (UTC)[reply]
- Endorse. Looks like a classic case of WP:HEYMANN to me. Nominator and early voters see completely unreferenced article, that seems trivial, fail to do due diligence, and say delete. Someone comes along, Significantly improves the article with a lot of GNG sources over an extended period of time (from three OTHER continents - what, could no one find one from Africa or South America :). A relist would surely lead to an unambiguous keep. Nfitz (talk) 15:38, 24 October 2019 (UTC)[reply]
- Overturn and relist I had been watching that article to see whether it would get relisted or closed as no consensus. I don't disagree with the improvement that has occurred but think, especially as one !vote for delete came after the improvement, the closing sysop cannot just say that it has become a keep consensus. An explanation is certainly necessary here and I am thankful Tone gave one, but I do not think that explanation sufficient for the consensus shown here. Best, Barkeep49 (talk) 02:55, 25 October 2019 (UTC)[reply]
- Overturn and relist – with the article having been changed significantly during the discussion, more time should be given to participants to review the new sources and see if it changes their !vote. It's true that when a closer says "sources [meet/don't meet] GNG", the closer is supervoting – commenting on the notability of the article subject, rather than on the discussion. "Consensus is the sources [meet/don't meet] GNG" is an entirely different statement, though, and I think a lot of closers write the former when they mean the latter. In any case, this discussion would have benefitted from more time to allow consensus to crystallize. – Levivich 04:52, 28 October 2019 (UTC)[reply]
- Comment Starting a DRV to get a keep overturned to no consensus is a complete waste of everybody's time. There's no rule saying a keep closure can't be renominated at a later date either, and consensus can change. Smartyllama (talk) 18:36, 28 October 2019 (UTC)[reply]
-
-
- @SmokeyJoe: No. I'm asking for either the discussion to be relisted so the late-arriving keep arguments can be addressed, or in the alternative the close changed to a no consensus to both reflect the discussion more accurately and make it easier to renominate for deletion in the future. SportingFlyer T·C 01:59, 29 October 2019 (UTC)[reply]
- Well Smartyllama wrote "renominated" and you replied as if "relisted" was a synonym. The AfD isn't complicated by "late-arriving keep arguments", but by stubstantive changes to the sourcing that probably render the PROD, AfD nomination and early !votes non-applicable. Better to let it settle for a short amount of time. Also, noting the nominator's reference to "news" and delete !voters reference to WP:NOTNEWS, letting the article sit until some times passes, enabling an observation of whether all sources belong to a brief burst of news, seems to be to be more sensible than rushing a 1 week old topic. The page is now approaching four weeks. I think a much clearer result will be obtained by waiting a few weeks and renominating. --SmokeyJoe (talk) 02:59, 29 October 2019 (UTC)[reply]
- I responded to Smartyllama since they seemed to assume my only request was overturning a keep to a no consensus. I'm fine with a result here which would allow a renomination in a few weeks. Also, it's likely I misunderstand your latter reasoning, but the event itself happened in 2010, so it should be relatively easy to determine WP:NOTNEWS. SportingFlyer T·C 01:58, 2 November 2019 (UTC)[reply]
|