Wikipedia:Administrators' noticeboard

From Wikipedia!

Wikipedia:Administrators' noticeboard/Header

Wikipedia:Administrators' noticeboard/Requests for closure

Pages recently put under extended-confirmed protection[edit]

Thousands of Portals[edit]

The purpose of this posting is to discuss portals, hundreds of portals. There is already discussion at Village pump (Proposals) (see WP:Village pump (proposals)#Hiatus on mass creation of Portals) to stop the creation of large numbers of portals by User:The Transhumanist, and the consensus is going strongly in favor of a hiatus, and there have been no new portals created since 22 February, but there has been no agreement to stop the creation of portals. The discussion at VPR appears to have slowed down, with a very clear consensus for some sort of hiatus, although it is not clear whether everyone agrees that the consensus is to stop the semi-automated creation of portals, or to stop the semi-automated creation of portals by TTH, or to stop all creation of portals by TTH (since there seems to be disagreement on what is semi-automated creation). Some editors have suggested that these portals are the equivalent of redirects by Neelix that warrant mass destruction. Anyway, proposals at VPR are just that, proposals. I am bringing the discussion here.

Perhaps I don’t understand, but User:The Transhumanist appears to be saying that we need to use portals as an experiment in navigation and in innovation. I am not sure that I understand whether, by experiment, they mean testing, a new initiative, or what, but I am not sure that I understand what is being innovated, or why it requires hundreds or thousands of portals. Robert McClenon (talk) 02:51, 1 March 2019 (UTC)Reply[reply]

Note that the mass hiatus wasn't on me per se, but applicable in general. It applies to everyone. It's so that nobody mass creates portals for the time being. That includes me.    — The Transhumanist   05:53, 1 March 2019 (UTC)Reply[reply]

An Example and Some Comments[edit]

File:English language portal error.png

One of the portals that has been proposed by User:Legacypac for deletion is Portal:English language. A look at it, with its error messages, is sadly informative. It was one of Wikipedia's earliest portals, preceding the involvement of the current portal team of TTH and a few other editors. However, the current portal team has made breaking changes to Portal:English language, apparently in order to attempt to improve the maintenance of portals. They apparently don't know how to keep our existing portals working, so what business do they have creating thousands of additional portals? We are told that the new portals are maintenance-free or nearly maintenance-free, but have the new portals been created at the cost of breaking existing portals? Robert McClenon (talk) 03:39, 2 March 2019 (UTC)Reply[reply]

Also, TTH says, above, that there is a hiatus that applies to everyone so that nobody mass creates portals for the time being. What is meant by mass creation, as opposed to individual creation? Are they agreeing not to create any portals for the time being? How long a time? Will they defer the creation of any new portals until (and unless) there is a consensus arrived at the criteria for the creation and maintenance of new portals? Robert McClenon (talk) 03:39, 2 March 2019 (UTC)Reply[reply]

Also, if any editor wishes to propose mass deletion of portals, similar to Neely redirects, that can be Proposal 3 (or 4). Robert McClenon (talk) 03:39, 2 March 2019 (UTC)Reply[reply]

Further investigation found 2 of the 8 portals linked off the top of the Mainpage had similar Red Script Errors where content should be. User:Moxy has now reverted these to pre-automation status. A lot of effort goes into keeping content linked from the Mainpage error free, yet this little Portal Project group replaced featured article quality portals with automated junk. Legacypac (talk) 03:46, 2 March 2019 (UTC)Reply[reply]
See WP:AADD#Surmountable problems. "Something broke but could be fixed" isn't a deletion rationale. Much less a deletion rationale for different pages; that's the guilt by association fallacy. Note also the ad hominem fallacy in there too, making it about specific people and getting back at them and suggesting they're too incompetent to create a new page, etc., instead of the argument focusing on content and our systems of presenting and navigating it. Tsk tsk.  — SMcCandlish ¢ 😼  17:11, 14 March 2019 (UTC)Reply[reply]

Proposal 1: Interim Topic-Ban on New Portals[edit]

The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.

I propose a topic-ban on the creation of portals by User:The Transhumanist for three months, to provide time for the development of new guidelines on portals, to provide time to dispose of some of the portals at MFD, and to provide time to consider whether it is necessary to mass-destroy portals. Robert McClenon (talk) 02:51, 1 March 2019 (UTC)Reply[reply]

  • Support as proposer. Robert McClenon (talk) 03:02, 1 March 2019 (UTC)Reply[reply]
  • Support the true number of portal creations by this user appears to be around 3500 portals since July 2018 (claims this here [1]). There were less than 1700 portals prior. On their talk they said it takes them 3 mins. 3 minutes is not enough time to properly consider content or what should be included. After we get a few automated portals deleted at MFD and the VP discussion reaches some closure I feel strongly we need to delete all the automated portals as a really bad idea. The template that automates these is up for deletion at Wikipedia:Templates_for_discussion/Log/2019_February_28#Template:Basic_portal_start_page Further, even though TTH disputes semi-automated creation here he says he uses "semi-automated methods of construction" and is using a "alpha-version script in development that speeds the process further" [2] Legacypac (talk) 03:12, 1 March 2019 (UTC)Reply[reply]
  • Comment. I need to investigate this issue a little further, but I was quite concerned about this before I even saw the thread, because I discovered Portal:Ursula K. Le Guin a few months ago. I've written a considerable portion of the content about Le Guin on Wikipedia, and even I think it's too narrow a topic for a portal; and when I raised this on the talk page, Transhumanist didn't respond, though they've been active. Transhumanist has been around for a while, so if they're willing to voluntarily stop creating portals while guidelines are worked out, I don't see a need for a formal restriction. Vanamonde (Talk) 03:21, 1 March 2019 (UTC)Reply[reply]
  • Response from The Transhumanist – The proposer of the hiatus, User:UnitedStatesian, acknowledged that my efforts have been in good faith. Note also that no rules have been broken (to my knowledge) – I carefully went over the existing mass creation rule and portal scope rule before starting. I have been a participant in the hiatus of mass creation discussion, and have voluntarily ceased portal creation since Feb 21, so as not to aggravate the other participants of that discussion. (What purpose would that serve?) I wish the matter to be resolved as much as anyone else. Since scope is actively being discussed over at the portals guideline talk page, it makes little sense to create pages that might be removed shortly thereafter based on new creation criteria. I plan on participating in the discussions, perhaps continue working on (existing) portals, and I have no plans to defy the mass creation hiatus. Nor do I plan on pushing the envelope any further. The VPR community has expressed a consensus that mass creation be halted. Robert McClenon is seeking to go beyond community consensus specifically to stop me from creating any portals at all, which is not what the community decided. If editors in general are allowed to create portals, just not mass create them, as the response to UnitedStatesian's proposal has indicated, why should I be singled out here? A topic-ban would be unjustified given the circumstances, and would be punitive in nature. In such a case, I would like to know what I was being punished for. Sincerely,    — The Transhumanist   06:20, 1 March 2019 (UTC)Reply[reply]
  • @The Transhumanist: I do not share @UnitedStatesian's assumption of good faith. The evidence which I have seen points far too strongly in the other direction for me to sustain that assumption.
Please see for example MFD: Portal:University of Fort Hare. I find it impossible to believe that a remotely competent editor acting in good faith could have created that portal-to-nowhere. If there is some good faith explanation which i overlooked, then I will enjoy hearing it ... but for now, that page looks like just one of many of examples of TTH intentionally creating utterly useless portsalspam in flagrant disregard of any version of the much-hacked portal guidelines, let alone the clear community consensus for selectivity in portal creation as expressed at WP:ENDPORTALS.
As others have noted, this is not TTH's first rampage of disruption. If there really was good faith this time, then TTH needs to urgently some serious explaining of their actions, because they do not look like the good faith conduct of a competent editor. --BrownHairedGirl (talk) • (contribs) 02:07, 16 March 2019 (UTC)Reply[reply]
  • Support, given Transhumanist's utter refusal to listen to the input at the Proposals thread during the last days, or anywhere else for that matter. Would go further and support a full, indefinite topic ban or even site ban. Every time I've encountered The Transhumanist over the years, it was invariably over some pattern of mindless mechanistic mass creation of contentless pages, which he then kept pushing aggressively and single-mindedly into everybody's face. Fut.Perf. 07:18, 1 March 2019 (UTC)Reply[reply]

And now we need to clean this mess up. It took me far too long to find and bundle thirty pages for deletion at Wikipedia:Miscellany for deletion/Districts of India Portals compared to the 3 minutes a piece he took to create them, but better to head this off before he starts into the other 690 odd Indian districts. Legacypac (talk) 07:33, 1 March 2019 (UTC)Reply[reply]

  • Quoted Comment on scale of this issue "Since July 1st (after WP:ENDPORTALS was over), over 4500 portals, excluding redirects, have been created (quarry:query/33793); the Transhumanist created more than 3500 (quarry:query/33795); of those, at least 561 were created with a summary along the lines of Started portal, in tab batch save, after batch was inspected: image slideshow minimum 2 pics, no empty sections. No visible formatting or Lua errors upon save, but there may be intermittent errors; report such bugs at WT:WPPORTD so that they can be fixed. Thank you. (quarry:query/33794). Just a note --DannyS712 (talk) 04:42, 27 February 2019 (UTC)" (end quote) |This off a base of just under 1800 Portals existing in July 2018. Legacypac (talk) 07:49, 1 March 2019 (UTC)Reply[reply]
  • Support. Given the history with TTH—who has been pulling this same kind of "create an unwanted megaproject, force it through without discussion, and expect the rest of us to waste our time maintaining it" stunt for well over a decade (anyone remember The Award Center? Wikipedia:WikiProject Outlines? The Admin School?) and always tries the same "well, it wasn't explicitly banned so I assumed it was what you wanted" defense when called out on it, I'd strongly support a full and permanent topic ban and wouldn't be opposed to a site ban; anyone who's been here for as long as TTH and still can't see the issue with Portal:Yogurts, Portal:Rutland or Portal:A Flock of Seagulls is someone who's either being intentionally disruptive or is wilfully refusing to abide by Wikipedia's norms. ‑ Iridescent 08:26, 1 March 2019 (UTC)Reply[reply]
  • Support temporary topic ban as a first step. We can look at a site ban if he ignores the topic ban. PhilKnight (talk) 08:32, 1 March 2019 (UTC)Reply[reply]
  • Support A topic ban is necessary while the issue is discussed and mass deletion considered. Adding thousands of inadequate and unmaintainable pages is not helpful. Johnuniq (talk) 09:39, 1 March 2019 (UTC)Reply[reply]
  • Support A generally-accepted principle of Wikipedia editing is that people who add content, and especially established editors, help to maintain it. Even assuming the best about Transhumanist here, I can't see how they can possibly do this with all these obscure portals. A ban on creating more of them has to be the first step. Nick-D (talk) 10:07, 1 March 2019 (UTC)Reply[reply]
  • Reluctantly Support We need time to curate and prune the low-quality portals, otherwise someone will panic and start deleting portals outright. 1:1 (topic to portal) parity is a nice goal, but it isn't readily achievable without the content to fill those portals.--Auric talk 11:33, 1 March 2019 (UTC)Reply[reply]
  • Support: TTH's approach seems rather cavalier at the moment. A change, as they say, is as good as a test. ——SerialNumber54129 11:58, 1 March 2019 (UTC)Reply[reply]
  • Oppose/Wait Let's see if he complies with the eventual results of the discussion at VPP. If he voluntarily agrees to stop, based on community input, then sanctions are not necessary. This seems like overkill right now. First, let the community guidelines pass, THEN let him violate those before we rush to ban. --Jayron32 12:13, 1 March 2019 (UTC)Reply[reply]
  • Massive Oppose - why the rush to ban? - the idea that giving a TBAN is the only appropriate means is bonkers - there are ongoing discussions. Currently you are trying to TBAN someone who hasn't broken policy. Let's get the agreements in, see if they stop and only then make any action Nosebagbear (talk) 12:18, 1 March 2019 (UTC)Reply[reply]
  • Comment: Isn't this all very similar to the mass creation of "Outline of" articles by The Transhumanist that met with the same kind of opposition (and tanked an RFA) 10 years ago? If so, then I'd say a topic ban might be in order.--Atlan (talk) 13:37, 1 March 2019 (UTC)Reply[reply]
  • Support this or a complete topic ban from portals or if this continues simply a complete ban. His latest reply here shows such a complete WP:IDHT attitude, with utterly founded claims about the need to have thousands of portals to be able to find and fix issues (even though many of the now reported issues appear in portals from months ago already), and on the other hand that they have now trouble finding and fixing flaws: "With Legacypac and others actively nominating the new portals for deletion at MfD, our opportunities for improving them and discovering and fixing design flaws are diminishing quickly.", even though perhaps 2 or 3% of the new portals have been nominated, and more than enough similar problematic ones remain to work on (e.g. the inclusion of a DYK which links to red herring on the Portal:Forage fish...). Statements like "Legacypac's approach is to recommend deletion of the new type of portal due to design flaws such as this. " shows a thorough lack of understanding of why these MfDs are made and why so many people support them. The designs flaws are just a small part of the reason for deletion, the lack of interest in, maintenance of, and contents for many of these portals are much more important. Fram (talk) 14:11, 1 March 2019 (UTC)Reply[reply]
    • The MfDs are potentially a prelude to an RfC, which may accelerate the process of deletion. With that in mind, the potential shrinkage is worrisome. I'm so tired, I forgot to mention it above.    — The Transhumanist   14:42, 1 March 2019 (UTC)Reply[reply]
The MfDs, which impact a tiny portion of these creations but a decent sample of various types of topics, are very useful for finding out what the community finds acceptable or desirable. The MfDs are consensus building (something you forgot/ignored). Soon we will be able to craft acceptance and deletion criteria based on the MfD results. That's how notability and other guidelines get developed, precedent. Legacypac (talk) 15:23, 1 March 2019 (UTC)Reply[reply]
  • Unnecessary Yes, they need to stop, but they have already agreed to do so (see above: [I] have voluntarily ceased portal creation since Feb 21, so as not to aggravate the other participants of that discussion), and they are unlikely to kneecap themselves by continuing under the massive scrutiny now present. Let's be civil and spare them the block log entry. Current discussion should drive the portal thing towards some practical steps that will likely include the deletion of most of the offending portals, and some agreed-on guideline that prevents mass creation from occurring again. Let's focus on that. --Elmidae (talk · contribs) 14:44, 1 March 2019 (UTC)Reply[reply]
  • Support – The unilateral creation of thousands of portals must stop. This has been driven largely by one editor, who has made the creation and preservation of portals his or her singular objective. We've seen since the portals RfC that this user will stop at nothing to continue the march of portals...regardless of community concerns, and regardless of Wikipedia policies and guidelines. Removing him or her from the portal topic area is the only way to prevent further disruption. RGloucester 15:09, 1 March 2019 (UTC)Reply[reply]
  • Support - as a first step. Beyond My Ken (talk) 18:42, 1 March 2019 (UTC)Reply[reply]
  • Unnecessary per Elmidae. Enterprisey (talk!) 19:31, 1 March 2019 (UTC)Reply[reply]
  • Unnecessary at this time as the editor has already agreed to stop and discussions are ongoing. Jonathunder (talk) 22:45, 1 March 2019 (UTC)Reply[reply]
  • Support Although TTH seerms to be acting in good faith they just don't know when to stop, so the community has to do it for them. Miniapolis 23:50, 1 March 2019 (UTC)Reply[reply]
  • Reluctant support TT was one of the first users that was ever nice to me, many years ago, so I'd really rather not, but this is way out of line. Personally tripling the number of portals, a WP feature that almost nobody uses, and with apparenrly very little consideration to what subjects actualy merit a portal is grossly iresponsible. I get that they were upset at the proposed removal of portals, but this is a ridiculous overreaction that benefits nobody, and if they can't see that then a formal restriction is necessary. Beeblebrox (talk) 18:20, 2 March 2019 (UTC)Reply[reply]
  • Support per User:Fram, and I assume it would also cover conversions of "old-style" Portals to the problematic one-page versions, as well as adding portal links to any article in the mainspace, and all other Portal-related editing. WP:IDHT is spot on: in all of these Portal-related discussions, TTH has again shown what is to me a shocking failure of self-examination: no "Gee, this is another case where a broad swath of the community seems to have a major issue with my behavior, and thus should cause me to step back and assess whether there is 1) anything that, in retrospect, I should I have done differently, and 2) anything I can do now to a) try to mitigate the damage and/or b) regain the communitity's good favor." TTH's factual statement that "I have not created any new Portals since Feb. 21" is meaningless as a commitment to future behavior. UnitedStatesian (talk) 03:24, 3 March 2019 (UTC)Reply[reply]
  • Unnecessary As mentioned above, moving to preemptively TBAN an editor who has already agreed to stop while discussion is underway serves no purpose here. If they choose to ignore the community consensus, then we can discuss further preventative measures, but doing so now is premature. As an aside, most of those red errors that are being reported are simple fixes, so anyone who finds one can post a note on WT:WPPORT for one of our editors to fix, or simply add |broken=yes to the {{Portal maintenance status}} template at the top of the page. — AfroThundr (u · t · c) 06:11, 3 March 2019 (UTC)Reply[reply]
  • Support. Portals have not been working for for 13 years. A pause of 3 months is more than reasonable. --SmokeyJoe (talk) 04:47, 4 March 2019 (UTC)Reply[reply]
  • Mass portal creation should be consider foul of Wikipedia:MEATBOT. Before continuing, I suggest seeking approval at an RfC, followed by the standard Bot approval process. --SmokeyJoe (talk) 04:59, 4 March 2019 (UTC)Reply[reply]
  • Support This is a long-term problem with TTH. It used to be "Outline" pages, & maybe still is. He is always polite & cheery, but completely ignores all criticism and pushes on with his agenda, as his rather scary newsletters show. Johnbod (talk) 15:50, 7 March 2019 (UTC)Reply[reply]
  • Support. Sensible proposal. Agree with UnitedStatesian that this should also cover conversions of old-style portals. feminist (talk) 05:04, 8 March 2019 (UTC)Reply[reply]
  • Oppose TTH has agreed to stop for now, he doesn't need a formal ban when he's already doing it voluntarily. SemiHypercube 17:01, 8 March 2019 (UTC)Reply[reply]
  • Oppose Per Elmidae, the user has agreed to stop and has not formally violated policies. We don't need more portals and this behavior needs to stop, but it seems that this has already been achieved for now while discussion is ongoing. — MarkH21 (talk) 08:12, 12 March 2019 (UTC)Reply[reply]
  • Oppose - Uneccessary, as The Transhumanist has already ceased such activities (i.e. I have ... voluntarily ceased portal creation since Feb 21 ... I have no plans to defy the mass creation hiatus [that has already been established].). — Godsy (TALKCONT) 00:04, 13 March 2019 (UTC)Reply[reply]
  • Oppose. This is circular reasoning. "I don't think we should have these portals, and others disagree, so I want to punish/shame my principal opponent in hopes of winning." This is several forms of red herring fallacy all at once (including argumentum ad baculum, appeal to spite, poisoning the well, and traitorous critic). If consensus firmly decides we don't want these portals, and then if an editor were to defy that decision and create a bunch more portals of exactly the sort we decided were unwanted, only then would a topic-ban of any kind be warranted.  — SMcCandlish ¢ 😼  16:54, 14 March 2019 (UTC)Reply[reply]
  • Strong support this and any other restraint on TTH, up to and including perma-siteban. After stumbling on some micro-portals and MFDing them, I spent a lot of time in September last year discussing these issue ubsuccessfully with the Portals project (see e.g. WT:WikiProject_Portals/Archive 7#Portal_Wish_List, WT:WikiProject_Portals/Archive 7#BrownHairedGirl's_agenda, more at WT:WikiProject Portals/Archive 8)
It was absolutely clear throughout those discussions that TTH had no regard to the balance of opinion in last years RFC, and repeatedly personalised all reasoned criticism of his conduct as "bias", "personal attack" or "bullying"
There were a few other voices in those discussions who urged restraint, such as @Bermicourt, but TTH took no notice of any of it. So all that's happening now was flagged well in advance, and TTH paid no heed until a community outcry. TTH is now pledging restraint, but made similar promises back in September which were ignored when when the heat was off. --BrownHairedGirl (talk) • (contribs) 07:16, 15 March 2019 (UTC)Reply[reply]
  • Strong oppose. Respectfully to supporters, this idea of a TB that targets a single editor for something that several of us have been involved with comes off as witch-hunty and scapegoaty. I know that's not what it is; however, that is how it seems – at least to me. Paine Ellsworth, ed.  put'r there  09:30, 15 March 2019 (UTC)Reply[reply]
    • That's a really weird oppose, @Paine Ellsworth. If you know it's not actually witch-hunty and scapegoaty, what's the problem? --BrownHairedGirl (talk) • (contribs) 09:48, 15 March 2019 (UTC)Reply[reply]
      • uhm, I "know" because I really do want to AGF; the problem is that I can't stand by and watch forty lashes given to someone when I helped tie him to the whipping post, so to speak. Hold us all responsible if you want, but don't single just one of us out for something several of us helped do. Hope that's a bit clearer. Thank you for asking, because I do sometimes have difficulty expressing myself adequately with the written word. Paine Ellsworth, ed.  put'r there  10:15, 15 March 2019 (UTC)Reply[reply]
        • @Paine Ellsworth: thanks for the reply. Can you explain more about what you mean by helped tie him to the whipping post, so to speak?
I am puzzled by it, because while I was aware that a few others WP:WPPORT supported auto-portals, I was not specifically aware that anyone had encouraged @The Transhumanist's mass-creation sprees of micro-portals and nano-portals.
For example, did you or others support the this creation of over 40 portals per hour?
Did you or others support or encourage the creation of Portal:University of Fort Hare (I have now nominated it at MFD: Portal:University of Fort Hare), which was literally a portal to nowhere?
I ask this, because it seems to me that there is in fact massive gap between the culpability of a) those WP:WPPORT members who supported creating far more more portals than the community supports; and b) TTH, who repeatedly rapid-created created portals which unavoidably meet WP:P2.
That's why I think it's fair to single out TTH. But if I have misunderstood the gap in responsibility, please correct me. --BrownHairedGirl (talk) • (contribs) 01:25, 16 March 2019 (UTC)Reply[reply]
Responsibility begins with the discussion that saved the portals. It gave the impression that not only was portalspace worth saving, it was worth improving. Then there were those of us who joined the portals project to help when we can, and we did. Perhaps the nom should be held responsible for comparing TTH's actions with the Neelix redirect fiasco? Incomparable, because Neelix created all those filthy dirty redirects all alone, with no help from any members of WikiProject Redirect. TTH had help creating all those filthy dirty portals, though, and with spreading their application. This is outrageously overkill. TTH has ceased making portals all on their own. The nom knows this and yet still had to suggest a topic ban. Why? In my own crummy way of expressing myself with words: pffft! Paine Ellsworth, ed.  put'r there  12:57, 16 March 2019 (UTC)Reply[reply]
  • Oppose per Elmidae, SMcCandlish and Jonathunder. The user has already voluntarily ceased creating new portals since February 21. There's no need for "the beatings to continue until morale improves". North America1000 01:39, 16 March 2019 (UTC)Reply[reply]
Northamerican1000 should also be banned from creating more portals. Creating automated navbox portals that overlap existing portal topics is not cool. Legacypac (talk) 01:46, 16 March 2019 (UTC)Reply[reply]
You need to stop scolding everybody who has ever created a portal. I have breached no policies. North America1000 02:18, 16 March 2019 (UTC)Reply[reply]
Au contraire: North, you need to desist from defending this flood of portalspam. Consensus is now clear that it has gone way too far, and a year ago at WP:ENDPORTALS was very clear that a significant minority of editors supported deleting all portals, while many more supported a purge., Instead you and some others went a spree in the opposite direction. That was at best reckless; at worst, it was wilful disregard of consensus WP:CONSENSUS. And WP:CONSENSUS is core policy, so don't push your luck. The guideline WP:DE is also relevant. --BrownHairedGirl (talk) • (contribs) 02:27, 16 March 2019 (UTC)Reply[reply]
The handful of portals I have created is certainly not a spree. Tired of this typecasting and WP:ASPERSIONS against any and all portal content creators. Does nothing to improve the encyclopedia. My !vote is regarding the matter at hand regarding TTH; that's it. North America1000 02:32, 16 March 2019 (UTC)Reply[reply]
Tired of you defending the indefensible, and then claiming victimhood when challenged. Portals are not content, they are a navigational device ... and defending a spammer does nothing to improve the encyclopedia. --BrownHairedGirl (talk) • (contribs) 02:46, 16 March 2019 (UTC)Reply[reply]
  • Oppose TTH stopped created portals when asked and has not resumed since. A topic ban is not needed to stop disruption and imposing one about three weeks after they stopped would be punitive in the extreme. I am though deeply troubled by the personal attacks from some very experienced editors above. Thryduulf (talk) 11:52, 16 March 2019 (UTC)Reply[reply]
  • Oppose as unnecessary, two weeks after it was proposed. As I understand it, there were multiple editors involved in this effort, so I don't see why we'd TBAN just one. AFAIK the editor at issue has so far kept their promise to stop making portals for the last two weeks. There's no need for a tban right now, as evidenced by the fact that we've had two weeks of discussion on this topic without a tban in place. Nuke the content, not the editor. Of course, that's based on the voluntary self-ban continuing to be observed. If that were to change, so would my !vote. (non administrator observation) Levivich 17:11, 16 March 2019 (UTC)Reply[reply]

Lack of good faith from User:The Transhumanist[edit]

I posted above[3] to dissent from @UnitedStatesian's assertion that Template:Lu has been acting in good faith.

I have just encountered a further small example, from today, of TTH's bad faith. In this case, TTH added[4] the nostubs=no parameter to Portal:University of Fort Hare, contrary to the general consensus that stubs should not be included in a portal's article lists. I see no evidence that TTH sought a consensus to do so ... and the change was was sneaky, because the edit summary add parameter did not disclose the nature of the change.

Since that portal is being discussed at Portal:University of Fort Hare|MFD: Portal:University of Fort Hare, the change should have been disclosed there.

That edit was of course only a small thing, and it has no practical effect because the sum total of non-biographical articles about University of Fort Hare is 1 (the head article). But at this stage, if TTH was acting with any good faith at all, the appropriate way to demonstrate it would have been to support prompt deletion of this portal-to-nowhere, rather than trying to expand its scope into stubs.

I have just checked the last 3 weeks of TTH's contribs, and have found precisely zero instances where TTH has supported the deletion of even the most ridiculously tiny-scope portal which they have created, let alone any instance where they assisted the cleanup by identifying and CSD/MFDing inappropriate creations.

I could understand that at this stage TTH might feel dejected by the deprecation of their portalspamming, and prefer to walk away from the topic ... but that explanation for inaction is undermined by a sneaky attempt to rescue a useless portal by adding stubs to its topic list. This breaches the spirit, if not the letter, of the self-restraint which TTH had promised. --BrownHairedGirl (talk) • (contribs) 22:15, 16 March 2019 (UTC)Reply[reply]

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Proposal 2 - Indefinite ban on page creation[edit]

The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.

Helpful comments above lead me to these numerous Drafts by User:The Transhumanist (ranging from 1 to 12 years old) => Wikipedia:WikiProject_Outlines#Outline_starts:. This is an obsession with mass creation of content no one wants. He has been creating hundreds of useless pages for years and at least 3500 useless automated Portals in the last few months. He has used up his allotment of lifetime page creations on Wikipedia and has a maintenance job to do now on his creations. He should also be working on removal of these useless pages. Therefore I propose a TBAN on page creations in all namespaces, and a TBAN on moves of pages into Mainspace or Portalspace (to prevent the moving of presetup but now empty existing drafts into mainspace), with the following exceptions: Starting an XfD (so he can assist in cleaning yup his mess) and talkpages of other users (for vandal warning etc so he can maintain quality on his creations) and talkpages in general of any existing page. TBAN may be appealed to AN which would want to approve a specific plan for the types of pages he wants to create.

  • Support as proposer Legacypac (talk) 10:44, 1 March 2019 (UTC)Reply[reply]
  • Oppose in current form - a TBAN on page creations in all namespaces is too drastic, give how many other namespaces that cuts off. I can understand prohibition on mainspace, portalspace, wikipedia space, or even userspace. But TTH not being able to start talk pages? To upload files? To start community books? That's unnecessary. --DannyS712 (talk) 10:57, 1 March 2019 (UTC)Reply[reply]
    I explicitly exempted talkpages of users but modified so all talkpages could be allowed. If he wants to create 500 books he should get permission. If there is a desire to create articles, he could ask for a relaxation, going through AfC for example, but with a preapproved plan. Legacypac (talk) 11:06, 1 March 2019 (UTC)Reply[reply]
  • Oppose This seems overbroad, locking down the English Wikipedia over one user. --Auric talk 11:20, 1 March 2019 (UTC)Reply[reply]
    Umm, this user has a long history of mass page creations. When people object he says no one told him he could not do it. A restriction would not prevent him from creating pages, it would just require him to get the plan preapproved. I don't know what crazy idea he might try next, so block everything except what he gets the community to agree to first. Legacypac (talk) 11:26, 1 March 2019 (UTC)Reply[reply]
    The problem isn’t page creation, it’s MASS page creation (usually using automated tools). Essentially, TTH routinely sacrifices quality for the sake of volume. It is the focus on volume that needs addressing. Blueboar (talk) 12:20, 1 March 2019 (UTC)Reply[reply]
    Yes MASS creation. We don't know what he will MASS create next, so let him propose what he wants to create BEFORE he creates it. If his idea is reasonable, great, but if not we save a ton of work and drama. Legacypac (talk) 12:24, 1 March 2019 (UTC)Reply[reply]
    So why does the original proposal not ban him from mass creation? --Izno (talk) 13:07, 1 March 2019 (UTC)Reply[reply]
    Because 3500 pages [5] is not Mass Creation according to his post near the top of the VPP thread: "Please clarify what you mean by "mass creation"; the figure provided above is less than 10 new pages per day per editor, which has never been considered mass creation by any WP standard. Also, please clarify what you mean by "semi-automated", since all software programs, including Wikipedia's internal text editor, may be considered semi-automated. Thank you. — The Transhumanist 19:25, 26 February 2019 (UTC)"[6] Legacypac (talk) 13:16, 1 March 2019 (UTC)Reply[reply]
  • Oppose - the problem is limited to the Portal: namespace; there is no evidence provided that there is a problem in any other namespace (I disagree with the foregone conclusion presented about outlines). This is overreaching by a wide margin. Ivanvector (Talk/Edits) 13:33, 1 March 2019 (UTC)Reply[reply]
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Proposal 3: Relax tagging and notification requirements for Grouped Portal MfDs[edit]

Withdrawn in favor of Proposal 4
The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.

Creating group MfDs for portals is almost as hard as creating one of these portals. If you use twinkle it creates a bunch of redundent discussion pages and floods the creator's talkpage with templates. TheTranshuminist is insisting every page in a group nomination be tagged for deletion [7]. He is technically correct, but this generates a lot of extra work for no real benefit. Notifying the creator with the first nom in the group should be sufficient. It is not like there are tons of editors with a vested interest in an a given district of India portal. I expect there will be a few more group nominations so addressing this will speed this up. Legacypac (talk) 18:06, 2 March 2019 (UTC)Reply[reply]

Well, there is no notification requirement that I'm aware of , so I think you can consider that relaxed. Tagging however, is usually considered a hard-and-fast requirement. It isn't exactly fair to discuss deleting a page while not giving any indication to users watching that page. Beeblebrox (talk) 18:13, 2 March 2019 (UTC)Reply[reply]
But in this particular case, there is no realistic expectation that there are any page watchers to begin with, other than the single individual who created them all. Fut.Perf. 18:19, 2 March 2019 (UTC)Reply[reply]
Perhaps any change to the requirements should wait until until it has been agreed which topics merit a portal. There is no urgent need to carry out a mass deletion before deciding what to keep. Certes (talk) 18:22, 2 March 2019 (UTC)Reply[reply]
Grouped MfDs create precedent and help us create policy based on the result. For example if 20+ District of India portals are deleted at MfD a precident against creation of 690 more such portals has been established. Similarly an effort to create portals on all the counties in the US or regional districts in Canada would be easier to shut down.
Given how we found two recently automated now broken portals linked off the Mainpage, is the creator even watching them?
The Neelix situation creates precedent for this relaxation. We went even further there and dispensed with discussion. Legacypac (talk) 18:28, 2 March 2019 (UTC)Reply[reply]
Thanks for the clarification. Grouping portals which are clearly going to stand or fall together, such as districts of India, makes sense. Certes (talk) 18:38, 2 March 2019 (UTC)Reply[reply]

Oppose. Tagging is a requirement, notification is not. And I just completed tagging on all of the Districts of India that are in the bundled nom. Assuming the current crop of MfD's close as delete, the solution is to propose a temporary speedy deletion criterion X3. UnitedStatesian (talk) 00:47, 3 March 2019 (UTC)Reply[reply]

Those portals aren't representative, they're fringe cases. The set of new portals include a wide range of scope, for example, and many had additional work done on them.    — The Transhumanist   01:45, 3 March 2019 (UTC)Reply[reply]
What do you mean by "fringe cases" and "representative"? They seem very representative to me. UnitedStatesian (talk) 03:58, 3 March 2019 (UTC)Reply[reply]

Oppose – Any readers of a page that's up for deletion has a right to know that the page may go bye bye, and that's why the deletion policy requires notice. There's no need to create a separate MfD page for each page being nominated for deletion. Posting a notice on each page that leads directly to the same discussion is easy.    — The Transhumanist   01:45, 3 March 2019 (UTC)Reply[reply]

  • Oppose - As User:UnitedStatesian says, we need X3. Robert McClenon (talk) 04:11, 3 March 2019 (UTC)Reply[reply]
  • The is no need to relax anything. Mass tagging and mass notification is no great issue. If the consensus is that they should all be deleted, Feds them all through mfd in one list. Ask The Transhumanist to tag and notify. I trust that he will cooperate. Stop the panic. —SmokeyJoe (talk) 11:27, 4 March 2019 (UTC)Reply[reply]
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Concerning further proposals[edit]

The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.

The proper venue for proposals is Wikipedia:Village pump (proposals).    — The Transhumanist   01:49, 3 March 2019 (UTC)Reply[reply]

AN is a perfectly good place for many kinds of proposal. With over 300,000 edits and many years here you should know better. Legacypac (talk) 03:51, 3 March 2019 (UTC)Reply[reply]
AN is not the proper place for a proposal on regulating content (referring to portals loosely as content). The way forward does not require administrative action, TTH will respect consensus. —SmokeyJoe (talk) 12:18, 4 March 2019 (UTC)Reply[reply]
@SmokeyJoe, I admire your AGF, but I think it is wildly misplaced.
This whole drama arose because after a far-from-unanimous RFC consensus not to actually delete the whole portal namespace, TTH chose to invert the meaning of that consensus to "create thousands of crappy new semi-automated microportals at a rate of up 40 per hour" ... and then go batshit raging at anyone who MFed some of the junk or pointed out that the consensus was not actually for a pressure hose of portalspam.
I don't know whether TTH has comprehension issues or just disdains the consensus, but I don't see any other explanation for the last year of TTH antics ... and either way, I see zero reason to expect that TTH will respect consensus. --BrownHairedGirl (talk) • (contribs) 10:50, 15 March 2019 (UTC)Reply[reply]
I’ve known TTH for a long time, although I have never worked with him. He always seemed perfectly reasonable, and really interested in a very worthwhile thing, navigation aids. There’s no problem there. I haven’t followed portal discussions closely, but I have never seen TTH rude or obstinate or disdainful. There must have been a misapprehension. I encouraged him to make auto-portals, and he did, and now he is trouble for it. I think the answer is at WT:Bots. AN should not be for making and implementing portal-specific proposals, the proposals should be directed at TTH. Follow the Bot process for any auto-portal creation. Do not create any new portals without an approved bot. That sort of thing. —SmokeyJoe (talk) 12:03, 15 March 2019 (UTC)Reply[reply]
Wrong venue In the nutshell at the top in read mode, and again in bold and red in the edit window, the words scream This noticeboard is for issues affecting administrators generally – announcements, notifications, information, and other matters of general administrator interest.. What we have here is a big idea involving the work of everyone. At most there should be a pointer diff here at AN. NewsAndEventsGuy (talk) 12:02, 6 March 2019 (UTC)Reply[reply]

As I see it the reason this ended up here is because the initial proposal was for a topic ban, which is AN material. The other related proposals were put here for convenience. At any rate it’s not grounds for a procedural close. — pythoncoder  (talk | contribs) 01:26, 11 March 2019 (UTC)Reply[reply]

  • This is absolutely the wrong venue, since this is not an "issue affecting administrators generally", it's a proposal (actually a pile of confused and confusing proposals – "I'm not getting my way in version A, so try version B. Nope? Okay, how about C? No? Then here's proposal D ...") that would affect the entire project, and is essentially a content-presentation and navigation matter, not an administrator matter of any kind. This is basically a variant of forum shopping, where instead of moving to a different venue, the idea is dressed up in a new outfit and put before the same venue over and over. The wrong venue. (And is actually regular forum-shopping, too, since we just had a big RfC about this last year.) WP:VPPOL is the place for something like this, especially since one of the various competing proposals includes making changes to WP:CSD policy, something we very, very rarely touch and only after considerable site-wide debate and a clear community consensus that it's required and will not have unintended negative consequences (ever noticed that the sequence of lettered and numbered CSD criteria has gaps in it? The community has revoked several CSD criteria as going too far). CSD is pretty much our most dangerous policy.  — SMcCandlish ¢ 😼  16:59, 14 March 2019 (UTC)Reply[reply]
Yeah, if I were the one starting this, I would’ve put it on one of the village pumps. At any rate it’s on T:CD now so it will be seen by those who frequent the village pumps (though it won’t show up on watchlists). Also, only two out of the nine deprecated CSDs were repealed for “going too far”. 6/9 were removed because they were redundant and they were folded into other CSDs. This leaves CSD X1, the prototype for the CSD X3 proposal, which was repealed at the conclusion of the Neelix redirect cleanup. — pythoncoder  (talk | contribs) 19:24, 15 March 2019 (UTC)Reply[reply]
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Proposal 4: Provide for CSD criterion X3[edit]

The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.

Template:Admin comment This proposal is being advertised at WP:VPP and WP:CD, and it has been requested that it stay open for at least 30 days. ~Swarm~ {talk} 05:14, 17 March 2019 (UTC)Reply[reply]

I am entering and numbering this proposal in order to get it into the record, but am requesting that action on it be deferred until the current round of MFDs are decided.

As per User:UnitedStatesian, Create Criteria for Speedy Deletion criterion X3, for portals created by User:The Transhumanist between April 2018 and March 2019. Tagging the portals for speedy deletion will provide the notice to users of the portals, if there are any users of the portals. I recommend that instructions to administrators include a request to wait 24 hours before deleting a portal. This is a compromise between the usual 1 to 4 hours for speedy deletion and 7 days for XFD. The availability of Twinkle for one-click tagging will make it easy to tag the pages, while notifying the users (if there are any). Robert McClenon (talk) 04:21, 3 March 2019 (UTC)Reply[reply]

This proposal should be posted in a wider venue, such as WP:VPR or WP:MFD. Many of those portals have been in place for months, making WP:AN too narrow a venue for them. CSD notices wouldn't be placed until after the discussion is over, and therefore would not serve to notify the users of those portals of the discussion. A notice to the discussion of this proposal, since it is a deletion discussion, should be placed on each of the portals, to allow their readers to participate in the discussion. The current round of MfDs are not a random sampling of the portals that were created, and therefore are not necessarily representative of the set. The portals themselves vary in many ways, including scope, the amount of time they've been accessed by readers, quality, number of features, picture support, volume of content, amount of work that went into them, number of editors who worked on them, length, readership, etc.    — The Transhumanist   07:09, 3 March 2019 (UTC)Reply[reply]
How would you suggest to get a representative sample? Legacypac (talk) 07:20, 3 March 2019 (UTC)Reply[reply]
Thank you for asking. That would be difficult now, since there are already a bunch of portals nominated for MfD. If those were included, then the sample would already be skewed. I expect a truly random sample would reveal that some portals are worth keeping and others are not. A more important question would be "How would we find the portals worth keeping? Which is very similar to the question "what should the creation criteria for portals be?", the very thing they are discussing at the portal guidelines page right now. Many of these portals may qualify under the guideline that is finally arrived upon there. For example, they are discussing scope. There are portals of subjects that fall within Vital articles Level 2, 3, 4, and 5, and there are many portals of subjects of similar scope to the subjects at those levels. And many of the portals had extra work put into them, and who knows how many had contributions by other editors besides me. Another factor is, that the quality of the navigation templates the portals are powered by differs, and some of the portals are powered by other source types, such as lists. Some have hand-crafted lists, as there are multiple slideshow templates available, one of which accepts specific article names as parameters. Another way to do that is provide a manual list in the subtopics section and power the slideshow from that. Some of the portals are of a different design than the standard base template. Some are very well focused, contextually, while others are not. For example, some of the portals have multiple excerpt slideshows to provide additional context.    — The Transhumanist   07:46, 3 March 2019 (UTC)Reply[reply]
  • Support in principle. Looking at the existing MFD discussions, TTH seems determined to drag and wikilawyer as much as possible to try to derail the discussions, even for blatantly and indefensibly inappropriate microportals like those discussed at Wikipedia:Miscellany for deletion/Portals for Portland, Oregon neighborhoods; it's not a good use of anyone's time to go through the same timesink 5000+ times. (The cynic in me says that a speedy criterion wouldn't work as while the creators wouldn't be able to decline the templates themselves, TTH and Dreamy Jazz would probably just follow the tagger around removing the speedy templates from each other's creations.) In practice, it would probably be more efficient to do what we did with Neelix and have a streamlined MFD nomination process, in which "created by TTH" is considered sufficient grounds for deletion at MFD and they default to delete unless someone can make a strong argument for keep. MFD is less gameable and also gives a space for people to defend them in those rare cases where they're actually worth keeping. (Every time I look, I find that the flood of inane and pointless TTH portals has spread further than I thought; shipping containers portal, anyone?) ‑ Iridescent 08:26, 3 March 2019 (UTC)Reply[reply]
    Dreamy Jazz seems unlikely do that, having already decided during this debate to stop donating their time to Wikipedia. Certes (talk) 18:06, 3 March 2019 (UTC)Reply[reply]
  • Comment – Another option would be to move these to draft space. The templates and lua modules could be modified so that the portals render right in that namespace (I wish I would have thought of this before). Being in draft space would give time to fix their various problems (keeping in mind that micro-scope is not fixable), and identify the ones worth keeping. I would agree not to move any of them personally, and would propose/request such moves after the new creation criteria guidelines for portals are settled upon. I would also be willing to tag those that did not meet those guidelines with CSD (as creator), saving Legacypac the trouble of nominating them at MfD (he mentioned somewhere that he thought I should help clean up this "mess"). Another benefit of this strategy is that if any of them sit in draft space too long without further development, they automatically become subject to deletion per the draft space guidelines, and those that reach that age without any edits can be deleted en masse without time-consuming effort-wasting MfD discussions. This course of action would of course need the participation of some lua programmers to add the necessary functionality to the modules, which would be a good upgrade for those, to allow for portal drafts to be created in the future.    — The Transhumanist   09:15, 3 March 2019 (UTC)Reply[reply]
P.S. @Iridescent and Legacypac: (pinging)    — The Transhumanist   09:28, 3 March 2019 (UTC)Reply[reply]
  • Absolutely not. The problem is that hundreds of portals on obscure topics makes an unmaintainable mess. Passing it to another namespace does not solve the problem which is that the portals are not helpful and are not maintainable. Automated creation of outlines/portals/anything must stop. Johnuniq (talk) 09:36, 3 March 2019 (UTC)Reply[reply]
  • No. I tried moving one broken portal to Draft as a test and it broke even more stuff. Not worth the effort to modify everything for draft space and then let the same little group of editors release them willy nilly back into portal space. Since this group ignored their own Wikipedia:Portal/Guidelines "portals should be about broad subject areas, which are likely to attract large numbers of interested readers and portal maintainers." why should anyone trust them to follow stricter guidelines? Legacypac (talk) 09:57, 3 March 2019 (UTC)Reply[reply]
  • Definitely not. What possible benefit would there be to cluttering up another namespace with ≈5000 pages that will never serve any useful purpose? If you want to goof around with wikicode, nobody's stopping you installing your own copy of Mediawiki; we're not your personal test site. ‑ Iridescent 15:38, 3 March 2019 (UTC)Reply[reply]
  • As a general rule, Portal pages should not be draftified. In fact, we should not usually move anything not designed to be an article to draft space. Draft portals should be in portal space, just like draft books should be in book space and draft templates in template space (pages with subpages are a pain to move, and many namespaces have special features that suggest keeping drafts in the same space if possible). If a portal is not ready for viewing by the general public, tag it with a relevant maintenance template and make sure it is not linked to from mainspace or from other portal pages.
  • In the case at hand, TT's mass created portals do not seem like they will all be soon made ready for wider consumption, so deleting them seems the better option. —Kusma (t·c) 20:15, 3 March 2019 (UTC)Reply[reply]
  • How is this the "only way" to be "sure"? What about actually viewing the portals themselves, as opposed to mass deleting them all sight unseen? North America1000 03:08, 26 March 2019 (UTC)Reply[reply]
  • Could you provide any evidence that all of the portals are "broken"? Many of them that I have viewed and used are fully functional, and not broken at all. North America1000 03:09, 26 March 2019 (UTC)Reply[reply]
  • Support, too many, too quickly, not enough thought went into their creation. Nuke these, revert other portals that were better before TTH "restarted" them. Automation should help with portal maintenance, not replace portal maintenance or move the maintenance burden to navboxes or other places. —Kusma (t·c) 14:57, 3 March 2019 (UTC)Reply[reply]
  • Support, sensible and fair way to deal with these. Johnbod (talk) 16:53, 3 March 2019 (UTC)Reply[reply]
  • Support: MFD could never handle the overwhelming amount of unnecessary and unsustainable portals, considering the magnitude of TTH's portal creation entering the thousands. –eggofreasontalk 20:12, 3 March 2019 (UTC)Reply[reply]
  • Support nuking. Beyond My Ken (talk) 20:30, 3 March 2019 (UTC)Reply[reply]
  • Transcluded to Wikipedia talk:Criteria for speedy deletion. {{3x|p}}ery (talk) 20:31, 3 March 2019 (UTC)Reply[reply]
  • Support mass creation of portals on these topics isn't appropriate without wider discussion, and the automated/semi-automated method used to create them doesn't produce high quality output. Portal:Sierra County, California, for example, is about a county with a population of 3,240, and consists of the lead of the main article, a few random contextless images grabbed from that article (mostly maps or logos) and portal boilerplate. Cleaning these up will require a temporary speedy deletion criterion, I don't think MfD could handle the load. Hut 8.5 22:25, 3 March 2019 (UTC)Reply[reply]
  • Support as proposer. I had already suggested deferring, but am satisfied that it is going ahead to mass-delete. I will add that, after a consensus is reached on whether and how to use portals, any that were deleted and are needed are available at Requests for Undeletion. Robert McClenon (talk) 01:01, 4 March 2019 (UTC)Reply[reply]
  • This mass page creation went against WP:MEATBOT and at least the spirit of WP:MASSCREATION if not the letter. An appropriate remedy for automated script and semi-automated creation is speedy deletion. Did you know they were driving for 10,000 portals at a rapid pace? It's here [8] Legacypac (talk) 04:44, 4 March 2019 (UTC)Reply[reply]
  • Oppose any and all notions of creating new CSD criteria at any drama board. Discussions here are too rushed, too emotive, too reactionary. Use WT:CSD. Consider using a WT:CSD subpage RfC. Do not attempt to mandate the detail of policy from a drama board. --SmokeyJoe (talk) 04:52, 4 March 2019 (UTC) Transclusion is not good enough. The discussion needs to be searchable from WT:CSD, and the specifics of any and all new criteria need to address the Criteria for a new CSD criterion. --SmokeyJoe (talk) 04:55, 4 March 2019 (UTC)Reply[reply]
Many editors at the Village Pump discussion, the Tban discussion above, and at MfDs also supported this. We do not need to fragment this discussion further. Legacypac (talk) 05:12, 4 March 2019 (UTC)Reply[reply]
Proposal 1 will make this Proposal 4 moot. This Proposal 4 is not a proper CSD implementation. --SmokeyJoe (talk) 05:41, 4 March 2019 (UTC)Reply[reply]
Proposal 1 is about stopping TTH from creating new portals. Proposal 4 is about deleting those he created in the last couple of months. How is P1 going to make P4 moot? —Kusma (t·c) 10:19, 4 March 2019 (UTC)Reply[reply]
List them all in an MfD, if they must all be deleted. A CSD that enables self appointed decision makes for which should go and which might be ok, is inferior to MfD. MfD can handle a list of pages. —SmokeyJoe (talk) 11:24, 4 March 2019 (UTC)Reply[reply]
If you want them all at MfD stop objecting to the listing of specific Portals at MfD. Legacypac (talk) 01:34, 11 March 2019 (UTC)Reply[reply]
No. Some of the Portals I would support for deletion, and others definitely no. This makes the proposal for a CSD invalid. It fails the CSD new criterion criteria. The proposal is neither Objective or Uncontestable. It would pick up a lot of portals that should not be deleted. --SmokeyJoe (talk) 01:44, 11 March 2019 (UTC)Reply[reply]
  • Support. No care at all went into these portals, they are mindless creations with loads of errors and little actual benefit for our readers. I would also support the restoration of all pre-existing portals to the pre-transhumanist version, the new "single page" version may require less maintenance, but is way too often clearly inferior (see e.g. this, which is more like vandalism than actual improvement, and has been reversed since). Fram (talk) 10:31, 4 March 2019 (UTC)Reply[reply]
  • Comment. Anyone restoring old multi-subpage portals should bear in mind that they will require maintenance. If there is no-one willing to maintain them, they, too are likely to be MfDed. No old-style portal with a willing and active maintainer has been converted as far as I know, so I suggest that anyone restoring them should be willing to maintain them. · · · Peter Southwood (talk): 16:47, 4 March 2019 (UTC)Reply[reply]
    • No. Converting an unmaintained but well-designed portal into an unmaintained semi-automated worse portal is not the way forward. Any claims that the new portals are maintained or don't need maintaining is false, as the many problematic new portals demonstrate. Fram (talk) 17:00, 4 March 2019 (UTC)Reply[reply]
    • Portal:Germany was converted (more than once) although it has maintainers. To make sure your portal isn't "improved", you need to put a specific template on the page, which isn't very obvious. There are old-style multi page portals that require only minimal maintenance, and where the conversion removed specific features. All those should be reverted, also to protect the subpages from overzealous deleters (the worst is deleting the /box-footer subpages; this breaks all old revisions by removing a necessary closing div). —Kusma (t·c) 17:21, 4 March 2019 (UTC)Reply[reply]
  • Oppose A mass-deletion of the new generation portals. Listing them at MfD will be sufficient for any that do not meet the criteria laid out in the portal guidelines (which are still under discussion). It makes little sense to remove the whole batch because some of them are problematic. They would need to be properly triaged to ensure the good ones are not caught in the process. I would of course, help with said triage. We're not trying to create more work for the community, just preserve good content. — AfroThundr (u · t · c) 23:47, 4 March 2019 (UTC)Reply[reply]
  • Comment - You created more work for the community by creating thousands of portals, some of which do not work, and with no intention to maintain them. I see no evidence that this effort created good content that needs to be preserved. Robert McClenon (talk) 04:17, 5 March 2019 (UTC)Reply[reply]
There is no new content in the automated portals, it's all poorly repackaged bits of existing content. Legacypac (talk) 04:40, 5 March 2019 (UTC)Reply[reply]
All portals, old or new, good or bad, manual or automated, repackage existing content. That's their job. New content belongs in articles. Certes (talk) 11:20, 5 March 2019 (UTC)Reply[reply]
  • Strong oppose per wumbolo below: criterion P2 already covers a number of these, the rest should be discussed. I still stand by my original comment which follows this addition. Wugapodes [thɑk] [ˈkan.ˌʧɹɪbz] 22:37, 13 March 2019 (UTC) Original comment: Weak oppose on principle. CSD is a necessary evil, and I don't think we should be hasty to add another criterion that skips our usual consensus process. I'm fine with nuking these portals and not opposed to deleting them, any diamonds in the rough will prove their worth by being created again, but I would prefer one big MfD with the rationale "created by The Transhumanist" which allows proper determination of consensus and gives those who want to spend their time triaging a chance to do so. Wugapodes [thɑk] [ˈkan.ˌʧɹɪbz] 08:03, 5 March 2019 (UTC)Reply[reply]
Building multipage MfDs like Wikipedia:Miscellany for deletion/Portals for Portland, Oregon neighborhoods is time consuming and tedious. A temporary CSD is rhe way to go. Consensus against this mess of new portals has already been established at VP, AN and in the test MfDs. Legacypac (talk) 17:20, 5 March 2019 (UTC)Reply[reply]
  • Support due to the massive amount of time it would take to put the ~4500 portals through MfD. MfD has been swamped with portal deletion requests from some time ago, and I can't see all this stuff removed via MfD in the foreseeable future (as someone said earlier, there is still a lot of Outlines left over from one of TTH's previous projects, so who knows how long it would take for MfD to delete all of this). This CSD X3 would streamline the process, and it would probably only take a few days to a week. It would help, as also mentioned earlier, to extend the criterion to the other users involved in the mass creation of these portals. Rlin8 (··📧) 03:31, 6 March 2019 (UTC)Reply[reply]
    • MfD has never had an issue to nominations of list of pages. 4500 separate MfD nominations would be absurd, but a list would be OK. If each is new, and has a single author, notifications of the author will be trivial. A CSD proposal shortcuts a discussion of the merits of the new portals, and pre-supposes deletion to be necessary, contrary to deletion policy. --SmokeyJoe (talk) 04:01, 6 March 2019 (UTC)Reply[reply]
TTH demands we place notification on every portal. We can skip notifying him, but building even 20 page MfD's is very time consuming. How do you propose to discuss 4500 or even 100 assorted portals at a time? These took 3 min to make - but far more than 3 min to list, tag, discuss and vote, then delete - when you add up all the time required from various editors and Admins. The test MfDs are sufficent and the very strong opposition to this automated portal project justifies this temporary CSD. Legacypac (talk) 04:16, 6 March 2019 (UTC)Reply[reply]
"TTH demands we place notification on every portal"? Legacypac, I have missed that post by him. If he did that, it needs to be repudiated. If these are new pages, and he is the only author, it is sufficient to notify him once. If all 4500 are essentially variations on the same thing, as long as the full set is defined, and browsable, we can discuss them all together at MfD. --SmokeyJoe (talk) 05:34, 6 March 2019 (UTC)Reply[reply]
User:SmokeyJoe during the Portland Oregon neighborhood MFD I specifically said I was not tagging all the related portals but he insisted I tag here [9] I could not get support in the section above to relax the MfD tagging because others wanted this CSD. During the Delete Portals RFC TTH went all out insisting every portal including the community portal be tagged for deletion - then he did it himself. That brought in all kinds of casual infrequent editors who were mostly against deleting the community portal. (Even though that was Pretty much pulled out of consideration for deletion before the tagging project). That massive tagging derailed the deletion RFC. By making cleanup as hard as possible TTH is making a lot of people want to nuke everything. Legacypac (talk) 06:11, 6 March 2019 (UTC)Reply[reply]
Legacypac's analysis is erroneous and misleading. The WP:ENDPORTALS RFC was a deletion discussion, and posting a notice on each page up for deletion is required by deletion policy. Note that the Community Portal was only mentioned twice. A portal that was the basis for about 50 oppose votes was the Current Events portal. Neither the Community Portal nor the Current Events portal were exempted in the proposal at any time. If you didn't count those, that left the count at about 150 in support of eliminating portals to about 250 against.    — The Transhumanist   07:25, 6 March 2019 (UTC)Reply[reply]
@SmokeyJoe: (edit conflict) See the top of this section for the referred to statement, which is not exactly as he quoted. A notice posted at the top of the portals slated by this proposal would be appropriate. Legacypac has been posting notice for his multi-page nominations using the {{mfd}} template, which auto-generates a link to an mfd page of the same title as the page the template is posted on. Rather than following the template's instructions for multiple pages, he's been creating an MfD page for each, and redirecting them to the combined mfd. Then a bot automatically notifies the creator of each page (me), swamping my user talk page with redundant notifications. Thus, Legacypac believes he'll have to create thousands of mfd redirect pages, and that I somehow want 3500+ notifications on my talk page.    — The Transhumanist   07:10, 6 March 2019 (UTC)Reply[reply]
You want us to manually tag pages for deletion that you used an automated script to create? You flooded Wikipedia with useless pages in violation of WP:MEATBOT but you are worried about having to clean up your talkpage notices? Just create an archiving system for your talkpage like we did for User:Neelix's talkpage. If you don't want notices you could start tagging pages that fail your own guidelines with "delete by author request" instead of commenting on how we will do the cleanup. Legacypac (talk) 08:37, 6 March 2019 (UTC)Reply[reply]
TTH, if you don't want so many deletion notices on your talk page, then remember in future not to create thousands of spam pages. Please help with the cleanup, rather than complaining about it.
@Legacypac: good work MFDing the spam, but it does seem that you are using a somewhat inefficient approach to tagging. Have you tried asking at WP:BOTREQ for help? In the right hands, tools such as AWB make fast work of XfD tagging. --BrownHairedGirl (talk) • (contribs) 12:21, 15 March 2019 (UTC)Reply[reply]
  • Support whatever course of action that will result in every portal created in this manner being deleted with the minimal of time and effort required. TTH has set up his automated tool, created a massive mess, and left it unattended for others to sort out. It should take less time to clean up this mess than it did to make it, not more. Nuke the lot and if there is anything of value lost then TTH can manually request pages to be restored one at a time at DRV. Fish+Karate 11:19, 6 March 2019 (UTC)Reply[reply]
  • Support per Fish and karate. RGloucester 14:20, 6 March 2019 (UTC)Reply[reply]
  • Strong oppose as written. I could support something that explicitly excluded portals which are in use and/or are being developed, but the current proposal to indiscriminately delete everything, including active portals, unless the admin chooses to notify any editors and the ones notified happen to be online in a narrow time frame is significantly overly broad. Thryduulf (talk) 01:54, 7 March 2019 (UTC)Reply[reply]
  • Support Not that portals are that bad, but I don't think we need portals on smaller subjects. (Portal:Spaghetti when we already have Portal:Pasta? Portal:Nick Jr., anyone?) Some might be worth keeping, but a lot are unneeded and unmaintainable. At least it's not a Neelix case. SemiHypercube 16:57, 8 March 2019 (UTC)Reply[reply]
    • Template:Replyto "Some might be worth keeping" is actually an argument against this proposal. Thryduulf (talk) 12:08, 11 March 2019 (UTC)Reply[reply]
      • @Thryduulf: Kind of, but that might be a reason not to just mass delete all at once. In the Neelix case there were some redirects that were actually useful, so a separate CSD criterion was used to keep some redirects at the admins' discretion, so this might be a similar case (before you say that contradicts my "it's not a Neelix case" statement, I meant that in terms of what the redirects were about) SemiHypercube 12:23, 11 March 2019 (UTC)Reply[reply]
      • It violates points 1 and 2 of the requirements for CSD criteria: objectivity and unconestability. Unless all the portals covered should be speedily deleted then none of them should be. If you only want to delete some of them then you should be opposing this criterion (just like you should have opposed the subjective Neelix criterion). Thryduulf (talk) 12:34, 11 March 2019 (UTC)Reply[reply]

*Support Only realistic way to deal with these. Johnbod (talk) 01:57, 11 March 2019 (UTC) Duplicate !vote struck. GoldenRing (talk) 10:16, 4 April 2019 (UTC)Reply[reply]

  • Request the posting of a notice at the top of each of the pages being nominated here for mass deletion, as required by the Deletion Policy. This proposal is currently a gross violation of the deletion policy because it is a discussion to delete 3500+ pages, that have been created over the span of a year, that are presently being viewed hundreds of thousands of times per month (projected to millions of times over the coming year) by readers of Wikipedia. The proposal for mass deletion has been made without the required notice being posted at the top of the pages to be deleted. This is being decided by a handful of editors unbeknownst to the wider community, namely, the readership of the portals to be deleted. It may be that those reading such notices would decide that the portals should be deleted, but the point here is that you are denying them the opportunity to participate in the deletion discussion as required by the deletion policy.    — The Transhumanist   21:12, 11 March 2019 (UTC)Reply[reply]
Request you stop wasting people's fucking time. Only in death does duty end (talk) 21:41, 11 March 2019 (UTC)Reply[reply]
  • He switched back to Outlines Special:Contributions/The_Transhumanist which are another unpopular plague for Wikipedia. The assertion that hundreds of thousands of readers a month are looking at his 3500 portals is fanciful at best and not supported by readership stats. Legacypac (talk) 21:58, 11 March 2019 (UTC)Reply[reply]
Support opposing anything TTH says from now on. Per OiD. ——SerialNumber54129 13:30, 12 March 2019 (UTC)Reply[reply]
Strong oppose taking ad hominem arguments into consideration. Thryduulf (talk) 13:49, 12 March 2019 (UTC)Reply[reply]
Oppose WP:BLUDGEONING. ——SerialNumber54129 15:48, 18 March 2019 (UTC)Reply[reply]
  • @Legacypac, technically he's probably telling the truth. Even obvious drivel like Portal:Coconuts averages around five views per day, thanks to webcrawlers and people who have the articles watchlisted and are wondering "what's this mystery link that's just been spammed onto the article I wrote?"; multiply that by 3500 and you have 500,000 pageviews per month right there. ‑ Iridescent 22:52, 11 March 2019 (UTC)Reply[reply]
  • Comment Neelix created about 50,000 redirects, which were reviewed by the community. The number of portals is an order of magnitude smaller. If X3 is to be introduced, it should involve a similar review process. We should certainly delete portals which have too narrow a scope or are of poor quality and cannot be improved. However, systematic deletion of all portals which qualify for consideration, purely on an ad hominem argument, would be as wrong as semi-automatic creation. Certes (talk) 10:51, 12 March 2019 (UTC)Reply[reply]
Absolutely not. Look at the rate these were created [10] sometimes several dozen an hour, and sometimes an average of 12 seconds each. If so little thought went into creation, why make deletion so difficult? The Neelix cleanup took far too long (I was a big part of it) and we deleted the vast majority of those redirects anyway the extra hard way. As far as I could see the editors who insisted we review everything did none of the reviewing. Also, these were created in violation of WP:MEATBOT which is a blockable or at least sanctionable offense Legacypac (talk) 11:04, 12 March 2019 (UTC)Reply[reply]
Two wrongs do not make a right - it is much more important that we get the cleanup right than it happens quickly. Whether or not TTH is blocked or otherwise sanctioned is completely irrelevant. While many (maybe even most) of the created portals should be deleted not all of them should be, and this needs human review: see requirement 2 for new CSD criteria at the top of WT:CSD. Thryduulf (talk) 12:07, 12 March 2019 (UTC)Reply[reply]
@Thryduulf, Certes, SmokeyJoe, and Legacypac: Concerning the rate, Legacypac's observation is not accurate. What the edits he is citing do not show, is the method by which the pages were created: they were created in batches, in tabs. Before saving, all the pages/tabs were inspected. For the pages that did not pass muster, such as those that displayed errors (this did not catch all errors, because lua errors can be intermittent or turn up later due to an edit in source material being transcluded), the tabs for those were closed. In a batch of 50, 20 or 30 might survive the cull (though batch sizes varied). Some tabs got additional edits in addition to inspection, to fix errors or remove the sections the errors were in, or further development. After all the tabs in a batch were inspected and the bad ones culled, the remaining ones were saved. That's why the edits' time stamps are so close together. If you look more closely, you'll see the time gap is between the batches rather than the individual page saves. Therefore, WP:MEATBOT was not violated.    — The Transhumanist   18:55, 12 March 2019 (UTC)Reply[reply]
He claims [11] he created 500 portals in 500 to 1000 minutes. and is using a script Wikipedia:Miscellany_for_deletion#User:The_Transhumanist/QuickPortal.js If this is not MEATBOT we should refind MEATBOT as meaningless. Legacypac (talk) 19:07, 12 March 2019 (UTC)Reply[reply]
A minute or two per portal of the new design sounds about right. Note that the script doesn't save pages. It puts them into preview mode, so that the editor can review them and work on them further before clicking on save.    — The Transhumanist   19:39, 12 March 2019 (UTC)Reply[reply]
Template:Replyto As I said above, the method of creation is irrelevant to this proposal, as is what (if any) sanction is appropriate. Likewise discussions of WP:MEATBOT don't affect this at all. What matters is only that these pages exist but some of them should not, this proposal needs to be rejected or modified such that it deletes only those that need deleting without also deleting those that do not. Thryduulf (talk) 20:42, 12 March 2019 (UTC)Reply[reply]
  • Procedural note I have advertised this discussion at WP:VPP and would encourage others to add links where they think interested editors might see. I think this should remain open for 30 days, as it is quite a significant policy change. GoldenRing (talk) 09:24, 13 March 2019 (UTC)Reply[reply]
  • Support now that the MfDs (here, here, here, here, here, here, here, here, here, here and here) are closing with strong consensus around delete, it is clear this is the fastest path to improving the encyclopedia (which is what we are here for, remember?) Any argument that 3,500 more portals have to go through MfD is strictly throwing sand in the gears. It is going to be enough manual labor pulling the links to the deleted portals from all the templates and pages they have been added to. UnitedStatesian (talk) 15:15, 13 March 2019 (UTC)Reply[reply]
    • That shows that a speedy deletion criterion is possibly warranted for some, but several comments on those discussions - including your own at Wikipedia:Miscellany for deletion/Portal:Spaghetti - indicate that this proposed criterion is too broad. Thryduulf (talk) 15:33, 13 March 2019 (UTC)Reply[reply]
      • You misunderstand my comment at that MfD: I strongly support that portal's deletion and all the others that would be covered by this proposed criterion. UnitedStatesian (talk) 15:37, 13 March 2019 (UTC)Reply[reply]
        • You supported the deletion of Portal:Spaghetti because the topic was covered by Portal:Pasta, even though Portal:Pasta would be deleted under this criterion? That's rather disingenuous at best and very significantly and unnecessary disruptive at worst. Portal:Pasta is an example of a portal that should not be deleted without discussion. Thryduulf (talk) 16:00, 13 March 2019 (UTC)Reply[reply]
  • Strong oppose and keep all. WP:P2 covers unnecessary portals, and there is no rationale presented other than WP:IDLI to delete a large proportion of all of them, which were all kept after a RfC in 2018. The next time content policies are created at AN by the cabal of admins, I am retiring from Wikipedia. wumbolo ^^^ 16:40, 13 March 2019 (UTC)Reply[reply]
    @Wumbolo: Well, if it came to that, take it to WP:RFARB first. Given the past history of WP:FAITACCOMPLI and WP:LOCALCONSENSUS extremism (i.e., WP:FALSECONSENSUS) cases, I have little doubt that ArbCom would agree to take a case about a gaggle of anti-portal people WP:GAMING the consensus-formation process by inventing sweeping policy changes out of their butts in a venue few content editors pay attention to and which is clearly out-of-scope for such a decision, even if it somehow had sufficiently broad input (e.g., via WP:CENT). I'm skeptical any alleged consensus is going to come out of this discussion, anyway.  — SMcCandlish ¢ 😼  17:33, 14 March 2019 (UTC)Reply[reply]
  • Support This is a repeat of the Neelix situation. ―Susmuffin Talk 00:01, 14 March 2019 (UTC)Reply[reply]
    • Template:Replyto The situation has similarities, but the proposed criterion is not comparable. Criterion X1 applied only to redirects created by Neelix that the reviewing administrator reasonably believed would be snow deleted if discussed at RfD (i.e. they had to evaluate each redirect), this criterion would apply to every portal created by TTH in the timeframe without any other conditions and without the need for anyone to even look at anything other than the date of creation. Thryduulf (talk) 00:13, 14 March 2019 (UTC)Reply[reply]
      • Honestly, there are far too many portals to be deleted through the usual channels. However, an quick evaluation would be reasonable, provided we keep the portal system itself. ―Susmuffin Talk 00:24, 14 March 2019 (UTC)Reply[reply]
Unlike Neelix who created some reasonable redirects along the way, these autogenerated portals are of uniformly low quality. The community has looked at representive samples across a variety of subject areas at MFD and the community has already deleted 143 of the 143 portals nominated at closed MfDs. The yet to be closed MfDs are headed to increasing that number. No one has suggested any alternative deletion criteria for X3. Legacypac (talk) 00:45, 14 March 2019 (UTC)Reply[reply]
That nobody has suggested an alternative is irrelevant - it's not up to those who oppose this proposal to fix it, and those who support it are by-and-large ignoring the objections. The MfDs have been selected as a representative sample of those that, after review, are not worth keeping and have been reviewed by MfD participants. This does not demonstrate that deletion without review is appropriate - indeed quite the opposite. Remember there is no deadline, it is significantly more important that we get it right than we do things quickly. Thryduulf (talk) 09:59, 14 March 2019 (UTC)Reply[reply]
Not particularly similar to the redirect situation that occurred; portals are vastly different in nature and composition from simple redirects. North America1000 03:16, 26 March 2019 (UTC)Reply[reply]
  • Oppose as unwarranted and dangerous (and circular reasoning). First, we do not modify CSD without a strong community (not admins' star chamber) consensus that an entire class of material is not just categorically unwanted but so unwanted that it should be deleted on sight without any further consideration. It's our most dangerous policy, and a change like this to it should be an RfC matter at WP:VPPOL. In theory, it could be at WT:CSD, except there is not yet any establishment of a consensus against these portals, and VPPOL is where that would get hashed out, since it's a project-wide question of content presentation and navigation (and maintenance, and whether tools can permissibly substitute for some manual maintenance, and ...). The cart is ahead of the horse here; we can't have a speedy deletion criterion without already having a deletion criterion to begin with. I strongly agree with SmokeyJoe: "Oppose any and all notions of creating new CSD criteria at any drama board. Discussions here are too rushed, too emotive, too reactionary."  — SMcCandlish ¢ 😼  17:05, 14 March 2019 (UTC)Reply[reply]
  • OpposeWP:P2 covers problematic portals just fine. A concerning issue here is that some users herein appear to simply not like portals in general, and so there are several arguments above for mass deletion as per this "I don't like it" rationale. Mass deletion should be a last step, not a first step, and portals should be considered on a case-by-case basis. North America1000 22:22, 14 March 2019 (UTC)Reply[reply]
You created some with the same tools. One or two of your creations are now at MfD which is why you are now engaging against this solution. We will consider each of your creations at MfD. Legacypac (talk) 02:34, 15 March 2019 (UTC)Reply[reply]
My !vote here is based upon my view of the matter at hand, and as such, it stands. Period. Regarding my portal creations, so what? You come across as having a penchant for scolding content creators on Wikipedia if you don't like the medium that is used. Please consider refraining from doing so, as it is unnecessary, and patronizing. North America1000 01:12, 16 March 2019 (UTC)Reply[reply]
  • @Northamerica1000: I agree - for example, I actually welcome the creation of Portal:Economics because I think econ should be established as distinct from business as in Portal:Business and economics. Qzekrom 💬 theythem 02:20, 18 March 2019 (UTC)Reply[reply]
  • Oppose - this CSD seems have to no more objective criteria than "shoot unless someone defends it". For this to be justified, they'd have to explain how no-one reacting within 24 hours was sufficient reasoning. As far as the initial proposal included, it didn't contain any acceptable objective criteria for something warranting deletion on quality grounds. Far worse, it didn't contain suitable justification (whether popularity/quality) for these portals to impose such a major hindrance to Wikipedia as to warrant a process with as few eyes (per consideration) as CSD. The nominator might have had more luck with a PortalPROD mechanism. Nosebagbear (talk) 23:09, 14 March 2019 (UTC)Reply[reply]
This CSD exactly meets each criteria for CSD's at the WP:CSD page. It is clear. It is easy to decide if the page meets the CSD. We ran 145 of these portals through MfD already and none survived. Numerous editors suggested this CSD in the Village Pump discussion. These mass created portals universally have the same flaws. Therefore this oppose rational is flawed. Legacypac (talk) 02:34, 15 March 2019 (UTC)Reply[reply]
  • Support: will allow to quickly manage the auto-created portals of zero utility. --K.e.coffman (talk) 02:23, 15 March 2019 (UTC)Reply[reply]
  • Support enthusiastically. Taking all these portals through MFD would be a massive drain on community resources. TTH created these portals at sustained speeds of up to 40 per hour, so even the time taken to apply a CSD tag and assess it 24 hours later will require more editorial time than TTH took to create them. --BrownHairedGirl (talk) • (contribs) 07:23, 15 March 2019 (UTC)Reply[reply]
  • Strong oppose - There are good quality portals that will be excluded, few maybe, but deserve to remain. For example Portal: Cities, Portal: Architecture Portal:Sculpture.Guilherme Burn (talk) 11:40, 15 March 2019 (UTC)Reply[reply]
    • @Guilherme Burn, maybe those are worth keeping. Or maybe not. But even if they are good, they are not worth the price of the community committing huge amounts of time to individually debating every one of the thousands of useless portals which members of the portal project have spewed out over the last year (often as drive by creations, and which project members have then piled into MFDs to keep.
If the Portals Project had exercised discretion so far, then we would be in a very different place. But it's utterly outraegous to ask the community to devote more time to assessing this spam than the Portal Project put into creating them. --BrownHairedGirl (talk) • (contribs) 12:10, 15 March 2019 (UTC)Reply[reply]
Could these portals be marked to be spared?Guilherme Burn (talk) 13:03, 15 March 2019 (UTC)Reply[reply]
Template:Replyto not according to the proposal as written. The only chance of saving is if an admin chooses to notify and wait 24 hours and somebody objects within those 24 hours and someone spots that CSD has been declined previously if it gets renominated. Thryduulf (talk) 14:01, 15 March 2019 (UTC)Reply[reply]
@Guilherme Burn: Portal:Cities is totally moribund and unread, and has never had a single participant. Portal:Architecture dates from 2005 and wasn't created by TTH or this tag-team, so wouldn't be deleted regardless (although I imagine the enormous wall of pointless links which TTH's bot dumped onto the page a couple of months ago would be reverted). ‑ Iridescent 14:08, 15 March 2019 (UTC)Reply[reply]
Template:ReplytoOne portal that does not meet Mfd criteria is enough for me to keep my opinion. Portal:Cities Although poor visualized is an important and good quality portal and the Portal:Sculpture (erroneously I quoted another portal) as well.Guilherme Burn (talk) 13:20, 20 March 2019 (UTC)Reply[reply]
@Guilherme Burn: please can you clarify that statement that One portal that does not meet Mfd criteria is enough for me to keep.
Are you saying that you are willing to personally scrutinise a few thousand drive-by Portals at MfD in order to find the one which should be kept? Or do you want others to do that work?
TTH as made it very clear that these portals took on average between one and two minutes each to create ([12] Have you tried creating 500 portals? It is rather repetitious/tedious/time-consuming (from 500 to 1000 minutes)). So many multiples of that-one-to-two minutes per portal do you think it is fair to ask the community to spend scrutinisng them? And how much of that time are you prepared to give? --BrownHairedGirl (talk) • (contribs) 14:12, 20 March 2019 (UTC)Reply[reply]
So many multiples of that-one-to-two minutes per portal do you think it is fair to ask the community to spend scrutinisng them?Yes. The community also failed to set criteria for creating portals. What is the difference of Portal: Lady Gaga to Portal: ABBA? For me both should be excluded. If the community not had problems to create a portal for a unique singer, why now have problems with someone who has decided to create portals for lot of singers? And to be honest I do not think so much work like that, Mfd can be executed in blocks excluding several portals at the same time.Guilherme Burn (talk) 17:11, 20 March 2019 (UTC)Reply[reply]
  • Oppose per SmokeyJoe et al. Completely unnecessary to override already existing procedure. Paine Ellsworth, ed.  put'r there  17:12, 15 March 2019 (UTC)Reply[reply]
    • @Paine Ellsworth: the administrative work of trawling through several thousand drive-by-created micro-portals is huge. Cleaning up this flood of portalspam through MFD requires a huge amount of editorial time, vastly more than was involved in creating the spam.
If you think that existing procedure is fine, why aren't you devoting large hunks of your time to doing the cleanup by the laborious procedure you defend? --BrownHairedGirl (talk) • (contribs) 02:33, 16 March 2019 (UTC)Reply[reply]
  • Because...? I don't know, I guess I think this whole thing is rather more of a knee-jerk reaction than a brainy, measured response. Sure I've done my share of big, teejus jobs for the project and plan to continue (on my terms). I have a lot of respect for editors like yourself and TTH who've been lifting this project out of the primal soup of its beginnings even longer than I have (I went over ten in January, or was it Feb? whatever) and I'm tired of seeing good, solid editors get reamed for their work and retire, just leave or get banned. Don't think it can't happen to you, because as good as you are, neither you nor the rest of us are immune to the gang-up-on-em mentality that turns justice into vengeance 'round here. Think you should also know if you don't already that I'm about 95 farts Wikignome and 5 parts other, and it takes a lot less for us to think we're being badgered and handled. I voted correctly for me and my perceptions, and I don't expect either of us will change this unwise world one iota if you vote you and yours! WTF ever happened to forgiveness? REspectfully, Paine Ellsworth, ed.  put'r there  13:28, 16 March 2019 (UTC)Reply[reply]
But it seems to me that the unintended effect of what you are both saying is something like "I am not making any effort to assist the cleanup of this mass portalspam, but I will take the effort to oppose measures which reduce the huge burden on those who are actually doing that necessary cleanup work".
As I say, I do not believe that is what either of you intend. But all I see from either of you is opposition to any restraint on the portalspammer, and opposition to anything which would assist the cleanup. I respect the fine principles from which you two start, but I urge you to consider the effects on the community both of not easing the cleanup burden and of continuing to describe the likes of TTH in positive terms. Look for example at my post in a thread above about the #Lack_of_good_faith_from_User:The_Transhumanist, and at Iridiscent's observation above that of TTH's previous history of spamming useless pages.
As to lifting this project out of the primal soup of its beginnings ... that's an extraordinary way to describe TTH's spamming of hundreds, if not thousands, of useless, unfinished micro-portals. Face-sad.svg --BrownHairedGirl (talk) • (contribs) 22:53, 16 March 2019 (UTC)Reply[reply]
I am not making any effort to assist with mass deletions, beyond !voting to delete the clearer cases. We already have enough enthusiasts working in that department. Until recently, I had been adjusting individual portals and enhancing the modules behind them to improve quality, but I slowed down when it became obvious that my contributions in that area will be deleted. Certes (talk) 00:19, 17 March 2019 (UTC)Reply[reply]
So that's as I feared, @Certes: members of that WikiProject are leaving it to others to clean up the mess created by the WikiProject and its members.
That only reinforces my impression of a collectively irresponsible project, which doesn't restrain or even actively discourage portalspam, doesn't try to identify it, and doesn't assist in its cleanup.
That's a marked contrast with well-run projects. --BrownHairedGirl (talk) • (contribs) 02:06, 17 March 2019 (UTC)Reply[reply]
Template:To not a surprising perspective, possibly a hasty generalization, however that's not your worst move. Your worst move is to consider "mass deletions" of what you deem "portalspam" as Template:Du than the "mass creations" of portals. Who's really to say? As an editor mentions below, "...these portals are doing no harm so great that they can be deleted without due process." So maybe you're wrong about those mass deletions that portray some portals as WMDs instead of the harmless windows into Wikipedia that they were meant to be? No matter, at present you are part of the strong throng. If you're right, you're right. But what if you and the strong throng are wrong? May things continue to go well with you! Paine Ellsworth, ed.  put'r there  07:01, 17 March 2019 (UTC)Reply[reply]
  • Support and also apply it to those created by Northamerica1000, who has made such useless portals as Portal:Strawberries and Portal:Waffles. Reywas92Talk 08:26, 16 March 2019 (UTC)Reply[reply]
  • Support per F&K (whatever course of action that will result in every portal created in this manner being deleted with the minimal of time and effort required) and SN (nuke from orbit). I'll be honest I don't know enough to know whether it should be a X3 or a P2 or a single MfD list with 4,500 entries... but it should not need to involve manually tagging pages that were created by a bot or otherwise spending any real time figuring out which should be kept and which should not be kept. Delete them all. If editors feel like this portal or that portal should be kept, let them make the case for undeletion afterwards which can be examined on a case-by-case basis. (If that process is followed, it goes without saying that the portal creator should be banned from making any such undeletion requests.) Levivich 17:25, 16 March 2019 (UTC)Reply[reply]
    How are we supposed to work out what is worth undeleting, short of downloading all portals in advance lest they be deleted? Certes (talk)
    If an editor is not aware of a portal existing, then that editor shouldn't be asking for it to be kept. If there are particular portals that editors know they want saved, then they should have an opportunity to request that it be saved. But there should be no one-by-one examination of thousands and thousands of portals created by one user using semi-automatic methods. Levivich 19:39, 16 March 2019 (UTC)Reply[reply]
    Kill them all and let God sort them out is very much not the way Wikipedia works and is very much not the way it should work. Why should the review be restricted to administrators (as your proposal would require)? Why is it preferable to significantly harm the encyclopaedia by deleting good portals than to do the job properly and delete only those that actually need deleting (which are doing significantly less harm by existing than deleting good ones would cause)? Thryduulf (talk) 18:06, 16 March 2019 (UTC)Reply[reply]
    So let me create several thousand pages semi-automatically, and then I'll put it to you to go through them one by one and tell me which should be deleted and why? I don't think that's how it should work. It should work in reverse. The default should be delete them all, with some process for allowing people to request that particular portals not be deleted. BTW, when I say "all portals" I mean all portals covered by this proposal, not all portals that exist on Wikipedia. Levivich 19:39, 16 March 2019 (UTC)Reply[reply]
    If an editor created several thousand pages semi-automatically, the correct sequence of events is to analyse a representative sample to determine whether consensus is that they are (a) all good, (b) mostly good, (c) all bad, (d) mostly bad, or (e) a mixture. If (a) then no action is necessary, if (b) then individual deletion nominations are the correct response. If (c) then a CSD criterion to remove all of them is appropriate, if (d) or (e) then a CSD affectingly only the bad ones should be explored. In this the situation is somewhere between (d) and (e) depending on your point of view, but this proposal is treating them as (c). As I've said several times, I'm not opposed to a criterion proposed (in the right place) that caught only the bad ones and allowed for objections - that is not this proposal. This situation is frequently compared to Neelix, but the proposal is very different - this one: All pages created between Time A and Time B, unless anyone objects to the optional tagging within 24 hours. Neelix: All pages created between Time A and Time B that would be snow deleted if nominated at RfD, retargetting would not lead to a useful redirect and no other editor has materially edited the redirect. Do you now understand the fundamental difference? Also remember that pages can be tagged by bot. Thryduulf (talk) 20:56, 16 March 2019 (UTC)Reply[reply]
    Yes. We also need to clarify one important detail of the proposal: would an editor be required to look at the portal before applying CSD, or is there an assumption that everything created by this editor in that time period is automatically rubbish and does not deserve assessment? Certes (talk) 22:29, 16 March 2019 (UTC)Reply[reply]
    If a human being didn't spend a lot of time making a page, then human beings should not spend much time deciding whether to keep it. I put it to you again: suppose tomorrow I create 5,000 new pages and ask you to go through them and decide which to keep and which to delete. That would be insane; this is a website of volunteers; my doing such a thing would be disruptive. It would make work for others. Nobody reading this thinks it would be a good idea for me to do such a thing. Yet this is what is essentially being asked of us. Insofar as I have a !vote, I !vote no. Delete them all. They are all bad. Any that are good can be recreated as easily as they were created in the first place. Letting people flag keepers in one way or another is a perfectly reasonable way to prevent the baby from being thrown out with the bathwater. But yes, my starting point is that all of them should be deleted because none of them should have been made in the first place, and they do not have content value. Some portals are the product of careful creation and extensive work, but not 5,000 or however-many automatically created by one editor. The quantum portal idea is a much better idea, anyway. Levivich 02:38, 17 March 2019 (UTC)Reply[reply]
    I've alreadyanswered this immediately above, but as you apparently don't like the answer I'll respond again. If you create 5000 new pages in good faith (which TTH did), then the correct response is for others to go through and look at a representative sample, then gain a consensus about whether they are all bad, mostly bad, a mixture, mostly good or all good. This has been done with TTH's portals and while you may think they are all bad that is not the consensus view, especially as others have taken over some and either have improved them or are working on improving them. This means that it is important that only the bad ones are deleted meaning any proposal (such as this one) to delete all of them is overbroad and needs to be opposed. Thryduulf (talk) 10:03, 17 March 2019 (UTC)Reply[reply]
    This statement by Thryduulf is incorrect on many levels. Who has taken over and improved any of his creations? Where is the concensus view that they are not all bad when so far zero of his creations have been kept at MfDs. Where is the proof any of this was in good faith when he admits several sections down that no one (including him) has followed WP:POG Legacypac (talk) 10:38, 17 March 2019 (UTC)Reply[reply]
    Are you even reading the comments made by those who disagree with you because I'm not seeing evidence of it, especially when it comes to the MfDs (to reiterate, a reviewed selection of the worst pages being deleted by consensus but not unanimously in all cases does not provide evidence of the need for deletion of all of them without possibility of review). Thryduulf (talk) 16:36, 17 March 2019 (UTC)Reply[reply]
    Thryduulf, so I spend less than 1 minute per page creating 5,000 pages; you and others spend–what, an hour, cumulatively, at least?–per page to analyze it, discuss it, vote it, close it, and delete it. I spend 5,000 minutes; the community spends 5,000 hours. With all due respect I am flabbergasted to hear such a high-ranked Wikipedian express the view that this is OK or preferred. Even with your representative sample approach, say it's 100 portals that are looked at, that's still 100 hours of labor forced upon volunteers. In my opinion, no one should be allowed to make 5,000 pages without going through something like a BAG process to seek community approval. There was once a time, years ago, when it made sense to, for example, automatically create a stub for every known city and town in the world. I believe that time has long since passed; there are not 5,000 pages that can be created automatically that we need to have that we do not already have (IMO). And as for consensus, if they're not being kept at MfD, the consensus is clear. Those portals that people maintain manually are the same ones that can be flagged as exceptions to a mass-deletion. So I feel like we're on the same page about consensus, but I'm saying the consensus to keep a particular portal can be effectuated by allowing people to flag them as exceptions to mass deletion, whereas you seem to be suggesting: let's get together and spend an hour per portal to decide if it should be kept, even though nobody spent anywhere near that time creating it in the first place. If that's where we are, we'll have to agree to disagree, because I fundamentally don't believe these portals are worth a one-by-one analysis, and I believe the representative sample approach you advocate has been done and has led to the conclusion that these are worth mass deleting with exceptions. I guess that's for a closer to make the ultimate decision about, but for my part, from uninvolved editors, I'm seeing a lot more support than oppose for mass deletion. Levivich 14:42, 17 March 2019 (UTC)Reply[reply]
    Template:Replyto If you're just going to ignore all the explanations I give in response to you (twice) and all the explanations elsewhere from me and others about why a reviewed selection of the worst being deleted (and not unanimously in all cases) is not evidence of the need for all of them to be deleted without possibility of review by others then it is clear we will never agree. Fortunately, per WP:VOLUNTEER, nobody is being forced to do anything they don't want to do - including you - and it's really disappointing that someone as experienced as you feels the need to prevent that work being done by others just because you don't want to. Perhaps between now and the time this is closed those in support of this overbroad proposal will actually choose to address the points in opposition but unless they do the only possible outcomes are no consensus or consensus against. Thryduulf (talk) 16:36, 17 March 2019 (UTC)Reply[reply]
    Thryduulf, I heard you say: pick a representative sample and decide if they're all bad, some bad, etc. As I understand it, a representative sample has been sent to MfD with consensus to delete almost all of them, if not all of them (I'm not sure if lists I've seen are complete). Then you say that just because the sample is all-delete doesn't mean the whole category is all-delete. I infer you think the sample is not well-chosen? By TTH's admission there are like 4,500–5,000 portals, and a tiny tiny percentage of those are being manually maintained–like less than 5%. Are we on the same page about the facts so far? If so, where do you see consensus other than "delete 95% of these things"? Why can't we tag the 100 that are manually maintained and delete the remaining 4,500? I am reading what you're writing, but I am not understanding it. Levivich 16:44, 17 March 2019 (UTC)Reply[reply]
  • Support: these portals are easy to create semi-automatedly and contain no information not found in articles so we're not losing any information from Wikipedia, which sets this apart from most other CSD criteria. An alternative proposal I would support is to expand the remit of P2 to apply to any portals with fewer than one-hundred pages under their scope (or alternatively, fewer than one-hundred notable topics if there is evidence that the portal creators and users are planning to create such topics as articles). If a topic doesn't have 100 pages on it at the bare minimum, there's absolutely no reason to focus a portal around it. Even for portals covering tens of thousands of articles, reader interest is very, very low and the current semi-automated busywork is not serving the readers. Bilorv (he/him) (talk) 19:05, 16 March 2019 (UTC)Reply[reply]
    • Template:Replyto a proposal for expansion of speedy deletion criterion P2 is being discussed currently at [[Wikipedia talk:Criteria for speedy deletion}} (which is where proposals related to speedy deletion criteria should be held, not AN), so I will refrain from explaining here why I oppose your suggestion to avoid splitting the discussion. Thryduulf (talk)
  • Support with exceptions. I support the speedy deletion of all portals auto-created in recent months as it seems excessive and unnecessary. However, those few portals which are manually maintained in good faith should be kept. Down the line we need to take another look at a notability threshold to keep a lid on portalmania. Bermicourt (talk) 22:37, 16 March 2019 (UTC)Reply[reply]
    • If you believe there should be exceptions for portals maintained in good faith (and I agree there should be), then you should be opposing this proposal in favour of an alternative one that allows for that. Thryduulf (talk) 22:59, 16 March 2019 (UTC)Reply[reply]
    X3 only covers the mass created automated portals started by TTH so already excludes the type of portal User:Bermicourt wants to exclude. Thryduulf is muddying the facts. Legacypac (talk) 23:08, 16 March 2019 (UTC)Reply[reply]
  • Oppose because a) on procedural grounds this shouldn't be discussed at the AN "closed shop" and b) because these portals are doing no harm so great that they can be deleted without due process. It is not TTH's fault that the guidelines for portal creation are permissive. Triptothecottage (talk) 02:56, 17 March 2019 (UTC)Reply[reply]
  • Comment: I have already voted here but I just wanted to provide an example of how much thought was going into the creation of these portals. Portal:Aquatic ecosystem was created by TTH on Aug 15 2018 and in classified as "Complete" despite having 4 selected images. An identical portal was created at Portal:Aquatic ecosystems by TTH on Nov 24 and is classified as "Substantial" (the portalspace equivalent of B-class). One wonders, which portal is of better quality, how was this determined, and how was this oversight not caught? — pythoncoder  (talk | contribs) 13:33, 17 March 2019 (UTC)Reply[reply]
  • Oppose: Criteria are supposed to be uncontestable - almost all pages could be deleted under this criterion, according to consensus. Looking at the most recent 50 portals created by TTH, I see a lot of frivolous ones, but I also see Portal:Pumpkins, Portal:Woodpeckers, Portal:International trade, and Portal:World economy, all of which represent subjects with well-populated categories. And I could add at least as many that are debatable. If TTH, now under a topic ban, were to create more portals, they could be speedy deleted under WP:G4. But the pages considered here were created before the ban, so they should stand or fall on their own merits. RockMagnetist(talk) 06:05, 18 March 2019 (UTC)Reply[reply]
    • Template:Replyto I think you mean WP:CSD#G5 (Creations by banned or blocked users) rather than WP:CSD#G4 (Recreation of a page that was deleted per a deletion discussion). Thryduulf (talk) 14:49, 18 March 2019 (UTC)Reply[reply]
      • WP:CSD#G5 cannot be used here. The locus of G5 revolves around obliterating the edits of LTA's and sockpupeters and for ban-evasion in a generalized scope. << FR (mobileUndo) 15:12, 18 March 2019 (UTC)Reply[reply]
        • G5 can be used to delete pages created in violation of a topic ban, if deletion is the best course of action. I would never use G5 on a page that was a borderline violation, but that's not relevant here (I can't think of any page creation that would be anything other than clear-cut one way or the other). It's all theoretical though as TTH hasn't created any pages in violation of his ban and I think it unlikely they will. Thryduulf (talk) 15:37, 18 March 2019 (UTC)Reply[reply]
        • @FR30799386 and Thryduulf: My point in mentioning G4 (oops - G5!) was that it is a more appropriate standard for deleting pages based on who created them. The current proposal is too broad. RockMagnetist(talk) 16:09, 18 March 2019 (UTC)Reply[reply]
  • Oppose I have gone over many of the portals. It seems that there are a mix of topics which are mainstream and some which should not have been created. This isn't a white or a black issue, the wheat must be carefully separated from the chaff. << FR (mobileUndo) 12:04, 18 March 2019 (UTC) !vote from sockpuppet struck. GoldenRing (talk) 10:17, 4 April 2019 (UTC)Reply[reply]
  • FR, is there some issue with deleting them without prejudice to re-creating existing ones? These were basically made by a bot in what amounts to a single spasm, so deleting them all could be seen as a BRD reversion. The next step would be to let uninvolved editors recreate any worth keeping. Yes, that might take a while. There is no deadline and if some potentially useful portals have gone uncreated up til now, it's fine if they stay absent a little longer. (talk) 04:07, 19 March 2019 (UTC)Reply[reply]
  • Oppose - the proposal assumes that none of the portals should have been created, and that is an incorrect assumption. Certainly the are some that perhaps should not exist, but equally there are some that definitely should, and some that need a bit of discussion to determine consensus. Speedy deletion is not the way to resolve this. WaggersTALK 16:45, 18 March 2019 (UTC)Reply[reply]
    • No, the proposal assumes (correctly) that 95% should never have been created, and that the tiny amount of time spent on those few that might be worth keeping doesn't justify the hours needed to discuss them all at MfD. The ones that get speedy deleted and would be an acceptable portal anyway can easily be recreated if someone really wants them. No effort has gone into creating these portals (usually not even the effort of checking if the result was errorfree, never mind informative or not a duplicate of existing portals), so demanding a week-long discussion for all of them because sometimes the mindless effort created an acceptable result is putting the cart before the horse. Fram (talk) 08:28, 19 March 2019 (UTC)Reply[reply]
    Throwing out the baby with the bathwater is not a sensible solution. Also, given WP:PAPER, could you explain why the existence of these portals is such a problem? This is nothing more than a massive exercise in punishing a user for the crime of trying to improve the encyclopaedia and getting a bit overenthusiastic. It's horrible to see and I honestly thought the Wikipedia community was better than this. WaggersTALK 11:42, 2 April 2019 (UTC)Reply[reply]
    The existence of these portals is a problem because they add extra clutter to already link-intensive articles (the lower part of our articles has become more and more overcrowded over the years, with authority links, navboxes, links to sister projects, ...) and removing links with no or very little value makes the articles better and avoids sending readers to utterly useless pages created in a completely mindless manner without oversight or care. Deleting pages which are useless is not "punishing a user", that is a WP:OWN approach you show there which should not be taken into consideration when debating whether to keep or delete pages. Punishing the user would be blocking or banning them. Fram (talk) 12:10, 2 April 2019 (UTC)Reply[reply]
    And that is happening (or has happened) too, so my point very much stands. Describing an editor's good faith hard work as "useless" isn't exactly conducive to a civil discussion either. Certainly some of the portals created are worthy of deletion, others are worthy of being kept. I could support a new PROD criterion, but CSD is not the right tool for this job. WaggersTALK 12:51, 3 April 2019 (UTC)Reply[reply]
  • Oppose—CSD is for stuff where there's zero grey area. At best, this should be a specialized PROD. Gaelan 💬✏️ 14:42, 20 March 2019 (UTC)Reply[reply]

Arbitrary break (CSD criterion X3)[edit]

  • Oppose Although the vast majority may not be needed: that does not mean they should just be deleted (without oversight or consensus). The arguments for this critera seem to be centered around: 'so little work was put into them, therefore we shouldn't need to put in any work to fix it'. Why not just let them sit there then? Is there a deadline? Seeing as portals themselves are an auxiliary aide to our main focus (of writing articles) this seems unnecessary. I'm surprised that this is (at least) the second time that a Private Bill has been proposed for the cSd, I guess times have changed a bit. It seems uncollegial to respond to opposers by saying: "then you better help out with all the MfD's'. I agree with the points made by SMcCandlish and RockMagnetist among others. Crazynas t 23:54, 20 March 2019 (UTC)Reply[reply]
    • "Why not just let them sit there then"? Have you actually looked at the pure drivel many of these portals are? Most of these portals are not an "auxiliary aid", they are random shit, bot generated without bot permission but without actual human oversight. Sending any reader to such total shit is a disgrace. The below image is how one of these portals looks right now, after it has existed for 7 months and after this discussion highlighting many problems has run for a month. Time spent discussing these (time spent looking at these) is time wasted. Any portal which people think is necessary after all can be recreated (in a much better fashion) afterwards, the speedy deletion of these doesn't restrict this. But keeping the shit an editor mass produced because their may be some less shitty pages included is doing a disservice to the people who actually wander to these portals and can only stare in dsbelief at what we show them. "'Calamba, officially the ', (Tagalog: Lungsod ng Calamba), or known simply as Calamba City is a class of the Philippines in the province of , . According to the ?, it has a population of people. " Fram (talk) 09:16, 21 March 2019 (UTC)Reply[reply]
have you looked at all the shit that sits in the mainspace (some of it for years)? There are like 182,000 unreferenced articles live right now, but this is the hill we're choosing to die on? Crazynas t 21:57, 21 March 2019 (UTC)Reply[reply]


Typical example of the kind of portals spammed across enwiki. Not just the five errors, but also the actual "text" of the lead article...
Typical example of the kind of portals spammed across enwiki. Not just the five errors, but also the actual "text" of the lead article...


Thank you for identifying a problem with a small number of Philippines portals where the lead contains {{PH wikidata}}, a technique designed for use in infoboxes. I'll pass your helpful comments on to the relevant WikiProject. Certes (talk) 11:02, 21 March 2019 (UTC)Reply[reply]
No, please pass my comment on to all people supporting these portals, but not bothering to actually look at what they propose or defend. Creating and supporting pages with such blatant problems is basically the same as vandalism. There are e.g. also quite a few portals which confront their readers with the below "selected article" (as the default selected article, not even when scrolling deeper). Or with the same image two or three times. Or... The list of problems with these portals is near endless (selected categories only consisting of one redlink? Sure...). The fact that adding a category can cause a page to look completely different and generate different errors (like in the example above) should be a major indicator that this system, used on thousands of pages, is not as foolproof and low in maintenance as is being claimed. Fram (talk) 11:36, 21 March 2019 (UTC)Reply[reply]


Read more... and weep
Read more... and weep


Thank you for your continued help in identifying portal issues. I have found and fixed three pages which had repeated "Read more" links. If you could be kind enough to reveal which portal you have depicted as "PortalShit2.png", we may also be able to fix that case and any similar ones. Certes (talk) 12:20, 21 March 2019 (UTC)Reply[reply]
There are two very simple solutions: either support X3, and all these portals are instantly fixed. Or actually take a look at all these low maintenance, automatic portals of the future, find the many issues, and fix them. Which still won't solve the problem that many of them are utterly pointless, mindless creations of course. I've noted more than enough problems with these portals to wholeheartedly support speedy deletion, since spending any time "corecting" a portal like the Calamba one is a waste of time (as it should be deleted anyway, speedy or not). Fram (talk) 12:42, 21 March 2019 (UTC)Reply[reply]
Template:Replyto You are clearly not understanding the opposition to this proposal. It is not about supporting the inclusion of poor content, it is about opposing a speedy deletion criterion that fails the criteria for new and expanded criteria and would delete content that should not be deleted in addition to content that should. Thryduulf (talk) 13:41, 21 March 2019 (UTC)Reply[reply]
No, I often have trouyble understanding burocratic opposition which creates tons of extra work for very little actual benefit. Furthermore, I'm not convinced that this actually fails the four criteria: it is objective and nonredundant (I guess we all agree on these two?), it is frequent (in the sense that having 3K portals at MfD is quite a heavy load, it's not just one or two pages), so we are left with "Uncontestable", which doesn't mean that as soon ass someone opposes it, it becomes contested, but that "almost all pages that could be deleted using the rule, should be deleted, according to consensus.". Looking at this discussion and the MfDs, I believe this to be true. Opposing this new CSD rule "because it is contested" is circular reasoning, as you are then basically saying "it is contested because it is contested", which is obviously not a valid argument. Having a significant number of portals which fall under the X3 but should not be deleted (which doesn't equal "should never exist", only "should not exist in the current form or any older form in the page history") would be a good argument, but I haven't seen any indication of such. Fram (talk) 13:57, 21 March 2019 (UTC)Reply[reply]
Template:Ec Frequent is not an issue (it wouldn't be as a permanent criteria, but as a temporary one it's fine), non-redundant is not an issue for most (although a few might be caught by P2 that's not a significant proportion so not a probelm). This proposal (unlike the ones being discussed at WT:CSD) is objective as written (created by a single user within a defined time period). Uncontestable however very much is, the requirement is "It must be the case that almost all pages that could be deleted using the rule, should be deleted, according to consensus. CSD criteria should cover only situations where there is a strong precedent for deletion. Remember that a rule may be used in a way you don't expect, unless you word it carefully." It is very clear from this discussion and others around these portals that not all of them should be deleted - several have received strong objections to deletion at MfD, some are argued to be kept and others merged. "it is contested because it is contested" is exactly the point of this requirement - nobody argues in good faith against deleting copyright violations, patent nonsense, recreations, or specific types of articles that don't assert importance. There is consensus that were these to be discussed they would be unanimously deleted every time. There is no such consensus about these portals. Some, perhaps most, should be deleted but not all of them. Thryduulf (talk) 15:47, 21 March 2019 (UTC)Reply[reply]
I am pleased to report that a recent module change should eliminate the problem where articles too short to be worth featuring occasionally appear as "Read more... Read more...". This should fix the mystery portal depicted above next time it is purged. Certes (talk) 11:26, 22 March 2019 (UTC)Reply[reply]
User:Thryduulf your opposition to X3 is baffling. You oppose it basically because some topics where Portals were mass created using automated tools against policy may warrant portals. But none of these pages have any original content to preserve. They are mindless spam poorly repackaging existing content. Kind of a poor Wikipedia mirror effort. MFDing these has proven they are unwelcome - yet you want to force us to spend a week debating pages that the creator spent seconds to create without even checking for compliance against their own criteria or for major errors? If these deletions were actually controversial (the only one of the 4 CSD criteria you say is not followed) we would expect a significant number of the MfDs to close Keep. We might expect the creator to defend and explain, but instead the creator freely admits he ignored WP:POG. Seriously makes me doubt your competence and judgement. Admins should show better judgement then this. Legacypac (talk) 17:12, 21 March 2019 (UTC)Reply[reply]
Template:Replyto Assuming you mean X3, then I have explained every single one of my reasons several times and you have either not listened or not understood on every single one of those occasions so I Will not waste even more of my time explaining them again. Thryduulf (talk) 17:16, 21 March 2019 (UTC)Reply[reply]
Second Legacypac. Additionally, part of what I meant by "some might be worth keeping" is that they can be deleted, but if any were actually worthy they could be recreated, perhaps with more care and effort than this. SemiHypercube 17:19, 21 March 2019 (UTC)Reply[reply]
  • It seems like a lot of what is objected to can be covered by a judicious use of P2, G1, and A3 (via P1) but there's probably something I'm missing. @Fram:, I'm not here to support bad content, but bad policy (and precedent) can be far more harmful to the project than 'repackaged nonsense' existing for a bit longer than some people want it to. This would have the side effect of saving the portals worth saving. Crazynas t 22:07, 21 March 2019 (UTC)Reply[reply]
  • Oppose let's discuss deletion based on content and merit of individual portals. No need to throw the baby out with the bath water, this is not how we do things here. You're proposing deletion of many very good portals here. ɱ (talk) 15:41, 21 March 2019 (UTC)Reply[reply]
Please identify 35 out of the 3500 (1%) that are "very good portals" so we can run them through MFD to test your statement. Also there is no baby - there is no original content at all. No work done by humans is lost with X3 deletions because they were created using an automated script that was used without BAG approval to repackage existing content. Therefore WP:PRESERVE is not an issue. If someone started creating thousands of articles called "Foo lite" that just copied Foo mindlessly we would CSD them without debate. These are just in another mainspace but they are really Foo lite. Legacypac (talk) 17:12, 21 March 2019 (UTC)Reply[reply]
Except that's not comparable at all. The point of portals (which the community has repeatedly endorsed) is to duplicate article content and provide links to related content - which is exactly what these portals are doing. They might be doing it poorly in many cases, but that's qualitatively different to one article duplicating another. Thryduulf (talk) 18:10, 21 March 2019 (UTC)Reply[reply]
Wouldn't it be faster to delete them all and then recreate the ones that need recreating, rather than go through them one by one to see which to keep? Because the number of "keeps" is like 5% or 10% and not 50%? (It would have to be 50% to be equal time between the two approaches.) If you're not convinced that it's 5-10% keep and not 50% keep, what sort of representative sampling process can we engage in to test the theory? Levivich 19:13, 21 March 2019 (UTC)Reply[reply]
Yes it would be faster, but there is no deadline so it is very significantly more important to get it right than it is to do it quickly. Deleting something that doesn't need deleting is one of the most harmful things that an administrator can do - and speedily deleting it is an order of magnitude more so. As only administrators can see pages once they have been deleted, and doing so is much harder, deleting it first makes the job of finding the good portals very significantly harder. Thryduulf (talk) 21:30, 21 March 2019 (UTC)Reply[reply]
Timing matters because this issue is being discussed in several forums at once. If the first debate to close decides to delete, the portals may be gone by the time another discussion reaches a consensus to keep them. Certes (talk) 21:48, 21 March 2019 (UTC)Reply[reply]
  • CommentI listed The Transhumanist's portal creations, latest first, and examined the top entry on each page, i.e. every 100th portal.
Assessment of a sample of TTH's recent creations
  1. Portal:Polar exploration – decent appearance; no obvious errors. 50 excerpts with more links at the bottom. Four other images, plus plenty more in the 50 leads. Manual input: refining the search criteria for Did You Know and In the News (DYK+ITN).
  2. Portal:Nick Jr. – Lua error: No images found. (To be fair, there may have been images before a recently requested module change to suppress images without captions.) 13 excerpts. No manual input: the wikitext matches that generated by {{bpsp6}}.
  3. Portal:Alternative metal – decent appearance; no obvious errors but a narrow scope. 11 excerpts; one other image. Manual input: refining DYK+ITN.
  4. Portal:Modulation – decent but minimal portal with no obvious errors. 30 excerpts; four other images. Several manual improvements.
  5. Portal:Spanish Civil War – potentially good portal but with a couple of display errors which look fixable. 30 excerpts; 20 other images. Manual input: routine maintenance, probably of a routine technical nature rather than creative.
  6. Portal:Carl Jung – decent appearance; no obvious errors. 40+ excerpts; six other images. Routine maintenance.
  7. Portal:Reba McEntire – decent appearance; no obvious errors but a narrow scope. 40+ other excerpts; six images. Routine maintenance.
  8. Portal:Romantic music – decent appearance; no obvious errors. 40+ excerpts; two other images. Routine maintenance.
  9. Portal:Anton Chekhov – decent appearance; no obvious errors. 36 excerpts; 17 other images. Routine maintenance.
  10. Portal:Media manipulation – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; no image section. Routine maintenance.
  11. Portal:Desalination – decent appearance; no obvious errors but a narrow scope. 15 excerpts; six other images. Manual input: refining DYK+ITN.
  12. Portal:Abuse – This portal has display errors which make it hard to evaluate properly. It's had plenty of manual input, possibly in attempts to fix it.
  13. Portal:Emmy Awards – decent appearance; one minor display error which looks fixable.(fixed) 50 excerpts; two other images. Routine maintenance.
  14. Portal:Shanghai cuisine – decent appearance; no obvious errors but a narrow scope. 19 excerpts; four other images. Routine maintenance.
  15. Portal:Saab Automobile – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; 14 other images. Routine maintenance.
  16. Portal:High-speed rail – decent appearance; one minor display error which looks fixable.(fixed) 40+ excerpts; 30+ other images. Routine maintenance.
  17. Portal:Tetris – decent appearance; no obvious errors but a narrow scope. 30+ excerpts; two other images. Routine maintenance.
  18. Portal:Azores – decent appearance; no obvious errors but a narrow scope. 20 excerpts; 18 other images. Some manual improvements.
  19. Portal:Musical instruments – decent appearance; no obvious errors. 40+ excerpts; 13 other images. Routine maintenance.
  20. Portal:Hidalgo (state) – decent appearance; no obvious errors but a narrow scope. 11 excerpts; 16 other images. Routine maintenance.
  21. Portal:Sporting Kansas City – decent appearance; one minor display error which looks fixable;(fixed) narrow scope. 11 excerpts; 7 other images. Routine maintenance.
  22. Portal:Piciformes – decent appearance; no obvious errors but a narrow scope. 9 excerpts; one other image. Routine maintenance.
  23. Portal:Birds-of-paradise – decent appearance; no obvious errors. 50 excerpts; five other images. Some manual improvements. Currently at MfD with the rationale that woodpeckers are not a family.
  24. Portal:Coffee production – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; 11 other images. Routine maintenance.
  25. Portal:Albanian diaspora – decent appearance; no obvious errors but a narrow scope. 30+ excerpts; three other images. Routine maintenance.
  26. Portal:University of Nebraska–Lincoln – decent appearance; no obvious errors but a narrow scope. 18 excerpts; eight other images. Routine maintenance. Currently at MfD with the rationale that Portal:University of Arkansas at Pine Bluff contains only two articles.
  27. Portal:University of Gothenburg – decent appearance; no obvious errors but a narrow scope. 10 excerpts; two other images. Routine maintenance.
  28. Portal:Transformers – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; two other images (everything else is non-free). Some manual improvements.
  29. Portal:Boston Celtics – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; 16 other images. Routine maintenance.
  30. Portal:Newbury Park, California – decent appearance; no obvious errors but a narrow scope. 16 excerpts; 34 other images. Routine maintenance.
  31. Portal:Vanessa Williams – decent appearance; no obvious errors but a narrow scope. 30+ excerpts; two other images. Routine maintenance.
  32. Portal:Bette Midler – decent appearance; no obvious errors but a narrow scope. 40 excerpts; seven other images. Routine maintenance.
  33. Portal:Ozzy Osbourne – generally decent appearance but several minor display errors;(fixed) narrow scope. 50 excerpts; 17 other images. Routine maintenance.
  34. Portal:Carnegie Mellon University – decent appearance; no obvious errors but a narrow scope. 15 excerpts; 28 other images. Routine maintenance.
  35. Portal:Milwaukee – decent appearance; no obvious errors. 15 excerpts; 47 other images. Some manual improvements. Too few excerpts but potentially good.
  36. Portal:Billings, Montana – decent appearance; no obvious errors but a narrow scope. Four excerpts; 27 other images. Some manual improvements.
  37. Portal:Empire of Japan – decent appearance; no obvious errors but a narrow scope. 40+ excerpts; 20 other images but with a couple of repeats. Routine maintenance.
  38. Portal:Cheese – decent appearance; no obvious errors. Nine excerpts; 50+ other images. Extensive manual improvements. Too few excerpts but potentially good.
It appears that most of the portals have a narrow scope and should go but a significant minority are either already of a good enough standard to keep or show sufficient potential to merit further attention. This impression is based not on cherry-picking but on a random sample. Certes (talk) 21:42, 21 March 2019 (UTC)Reply[reply]
Thank you for this, this is a very good illustration of why this proposal is too broad - it will delete portals that clearly should not be deleted, and others that may or may not need to be deleted (e.g. I've !voted to merge several of the portals about universities). Thryduulf (talk) 21:58, 21 March 2019 (UTC)Reply[reply]
  • Query Why don't we have a CSD for pages created by unauthorized scripts or bots? WP:BAG exists for a reason right? (And this seems to be a good example of it). Crazynas t 21:50, 21 March 2019 (UTC)Reply[reply]
@Thryduulf: You're missing my point. Just like we have a policy that banned users are to be reverted in all cases not because they might not make good edits (to game the system or not) but because they are a disruption to the community; so we should have a policy that pages created (or edited I suppose) by unauthorized bots are inherently not welcome, because of the potential for disruption regardless of their merit (by disruption I'm talking about this AN thread as much as the pages themselves). This is the whole reason we have a group dedicated to overseeing and helping with bots right? Crazynas t 22:12, 21 March 2019 (UTC)Reply[reply]
No bots were involved. The pages were created using a template. One of your last page creations was a user talk page, where you welcomed a new editor using Twinkle. You did a very professional job, by applying a template which introduces the new editor with the sort of carefully considered and neatly arranged prose that we don't have time to write every time a new contributor appears. Using a template is not a valid rationale for mass deletions. Certes (talk) 22:22, 21 March 2019 (UTC)Reply[reply]
Curious, what template did you use? I guess the difference I see is the twinkle is highly curated and subject to extensive review (as are the templates it calls). If all these pages were manually created, then what happened in the example of (what to me looks pretty much like G1) that Fram posted above? Why didn't the human that pressed the button take responsibility for that (so to speak) pile of rubbish? To clarify, Bot here covers scripts, AWB (which is 'manual'), java implementations etc. In short: "Bot policy covers the operation of all bots and automated scripts used to provide automation of Wikipedia edits, whether completely automated, higher speed, or simply assisting human editors in their own work." The policy explicitly references mass page creation as being under the purview of BAG here. Crazynas t 22:39, 21 March 2019 (UTC)Reply[reply]
I haven't used any of these templates myself but recent portals have been created by variants on {{Basic portal start page}}. The numbered versions such as {{bpsp6}} cater for portal-specific conditions such as there being no DYKs to feature. Certes (talk) 23:07, 21 March 2019 (UTC)Reply[reply]
Template:Replyto I was simply answering your question about why we do not speedy delete every page created by an unauthorised bot, etc - simply because not every page created by such means should be deleted. You are also mistaken about banned users - they may be reverted but they are not required to be. Certes analysis shows that some of the portals created by the script have been improved since, sometimes significantly. Thryduulf (talk) 22:46, 21 March 2019 (UTC)Reply[reply]
@Thryduulf: Sure, and this is tangential to the proposal here (which I'm still opposing, if you noticed). In any case the thought I'm having wouldn't be applied ex post facto but it would make it explicitly clear that mass creation of pages by automated or semi-automated means without prior approval is disruptive. Crazynas t 23:02, 21 March 2019 (UTC)Reply[reply]
  • Comment. The problem with many of these recently created template-based portals is that it is difficult or impossible to improve them. I've edited portals for over a decade but cannot work out how to change the portal code to include or exclude a particular article or image. (For articles I believe one has to change the template or mark the article as stub to exclude it; for images I believe it just harvests those from the main topic article.) Thus they are not drafts that could be further improved, they are static uneditable entities for which the only solution is to start from scratch. There is no thought to be preserved that is not equally present in the list of articles in the template/images in the root article. Espresso Addict (talk) 02:12, 22 March 2019 (UTC)Reply[reply]
  • The key issue is that traditionally, portals are viewed as entry points to broad topic areas. However a page generated by the helper templates that draw content from an underlying navigation box is more akin to a second screen experience: it provides an X-ray view into the navigation box. It's not clear this is the experience the community wants to provide for readers visiting something labelled a portal. isaacl (talk) 20:47, 24 March 2019 (UTC)Reply[reply]
  • the automated scripts are so easy to fool. Even if everything looks perfect when the portal is set up, as soon as someone adds an new link to a nav box (that may make sense in the nav box but not for the portal), adds an image to a page, or creates a DYK completely unrelated to the topic which includes the five letters "horse" within someone's name behind a pipe, you get random inappropriate stuff in an automated portal. The editor adjusting the nav box, adding a picture without a caption per WP:CAPTIONOBVIOUS or creating the DYK has no idea the portal is being busted. There is no edit to the portal to review so watch listing the portal does not help. You have to manually review the portal display regularly. That is before looking at lua errors. Autogenerated content is a bad idea. Forcing other editors to review your auto generated crap is wrong. Ignoring the guidelines because they are "outdated" and leaving 4500 pages that need to be checked and discussed against the guidelines by other editors is wrong. The only reasonable solution is to nuke these from orbit. Then if someone willing to follow the guidelines and use intellgently designed and applied tools want to recreate some titles, that is fine. Legacypac (talk) 21:23, 24 March 2019 (UTC)Reply[reply]
    • Everything you say before "The only reasonable solution..." may be true but is irrelevant to this proposal as written. "Nuking them from orbit" is not the only reasonable solution, as fixing the issues so that the portals don't break is also reasonable. As is not deleting the ones that have been fixed so that the errors you talk about don't occur. Thryduulf (talk) 00:46, 25 March 2019 (UTC)Reply[reply]
      Template:Tq2 Someone spent less than 50 seconds creating the page; requiring editors to spend more time than that to delete it has an extortionate effect, even though there's a good faith intent. If we don't nuke from orbit, then those who want these automatically-created portals deleted will be forced to spend far, far more than 50 seconds per portal discussing them one by one (or ten by ten, or one hundred by one hundred, it'll still be a lot of time). 50 seconds "taken up by manual activities" is how we end up with a Portal:Sexual fetishism that includes Pedophilia as one of the selected articles–probably not the best selection–but that's been there for five months now. Levivich 03:04, 25 March 2019 (UTC)Reply[reply]
      • Two wrongs do not make a right and there is no deadline. The only reason for deleting them all you seem to have is that you don't like that these portals were created so quickly, and that some of them are bad. That's fine, you are entitled to your opinion and some of them are bad. However that does not equate to a reason to delete all of them without checking whether they are good or bad. If you have problems with specific portals then they should be fixed and/or nominated for deletion, as I see you have done in this case, but just because X is bad doesn't mean that the entire set of pages of which is a part should be speedily deleted. Thryduulf (talk) 09:35, 25 March 2019 (UTC)Reply[reply]
        • "There is no deadline" is a complete non-argument. There is no deadline to have these portals either. Knowingly advocating for keeping problematic portals around until someone not only notices it but also decides to MfD it is exposing readers to shitty, thoughtless reproductions of content for no actual benefit (the benefits" of these portals are addressed dequately by the navigation templates they are based on) and with the risk of showing them all kinds of errors which gives a very poor impression. Luckily very few people get actually exposed to these pages, but this also means that the very hypothetical damage deleting some of these pages would do is extremely minimal. Fram (talk) 10:09, 25 March 2019 (UTC)Reply[reply]
          • There was indeed no deadline for their creation, now they have been created that is irrelevant. If we follow your logic though we should delete every article and then just recreate the ones that admins vet as meeting an undefined standard. Yes, deleting more slowly does increase the risk that some readers will see errors, but thtat's exactly what happens in every other namespace without a problem. Thryduulf (talk) 16:35, 27 March 2019 (UTC)Reply[reply]
            • No, that's not my logic. Your use of "no deadline" when it suits you, and the dismissal when it doesn't, is quite clear though. Deleting articles is losing content, deleting these auto-portals is losing nothing. Furthermore, we have in the past speedy deleted large groups of articles by one or two creators once it became clear that too many contained errors. This has been done with thousands of articles by Dr. Blofeld, with thousands by Jaguar, and with thousands by Sander v. Ginkel (the last ones moved to draft and then deleted afterwards). Once we know that with one group of creations by one editor, there are many problems, we had no qualms in the past to speedy delete them. That didn't mean that they can't be recreated, or that admins will first vet them, no idea where you get those ideas. Please don't make a caricature of what I support here, and please don't make absolute statements which don't match reality. Fram (talk) 17:41, 27 March 2019 (UTC)Reply[reply]
  • Oppose 1) Let's not create precedents where we hand single admins editorial control, admins may well be great editors (some better than others), but let's keep editorial control as much as possible only with all editors. 2) The formulation of this supposed CSD criteria seems to be a WP:PUNISH against a single user. (As an aside, different perspective: there are perhaps millions of pages in article space that are "poor", so portal space is bound to have them, too - just work through it -- and if we come-up with new forward looking policies and guidelines for all portals (or mass creations) consistent as possible with the 5 P, all the better). Alanscottwalker (talk) 17:42, 25 March 2019 (UTC)Reply[reply]
  • Support - per Fish & Karate. Ealdgyth - Talk 16:08, 27 March 2019 (UTC)Reply[reply]
  • Oppose. I feel there are much better ways of handling the situation, including but not limited to: expanding P2, Portal PROD, and even MFD. This is too broad of a sword that doesn't even cut in the right places since it's only limited to one user in a given time frame. -- Tavix (talk) 16:15, 27 March 2019 (UTC)Reply[reply]
  • Thought I had voted here but I guess I hadn’t. Regardless, my thinking on this has changed because of Certes’ in-depth analysis of TTH’s portal creations. Anyway: Oppose. The mass creation of portals is something that should be dealt with preferably quickly, but this proposal as written is not the right way to do it. Sure, there are a lot of crappy portals that could be deleted fairly uncontroversially, but there are also a lot of good portals as well as edge cases that deserve more community discussion on whether they should be deleted, or at least a longer waiting period so users may object. — pythoncoder  (talk | contribs) 12:40, 29 March 2019 (UTC)Reply[reply]
  • Oppose for now. I still hope that the proposal might become limited to portals looked at and determined to be poor by some objective criteria, which I could support, but that hasn't yet happened. Speedy ad hominem deletion regardless of subsequent tuning, current quality or even potential for future improvement is likely to throw too many babies out with the bathwater. Certes (talk) 12:46, 29 March 2019 (UTC) Duplicate !vote stricken. GoldenRing (talk) 10:14, 4 April 2019 (UTC)Reply[reply]
  • Regretfully support: as an editor I dislike the idea of creations made by certain users being deleted en masse but, quite frankly, MfD cannot cope with the influx at the moment. Hell, I've got a decent laptop and MfD is getting so big scrolling down causes a bit of lag. SITH (talk) 20:57, 30 March 2019 (UTC)Reply[reply]
  • Strong support of something to this effect, per WP:MASSCREATION and WP:TNT (i.e., the babies thrown out with the bathwater can be recovered later). However, opponents raise good points of localizing control to a few members, and while I do argue that portals are not content, they are a navigational tool, so community control of them can be a bit "stricter" than mainspace articles, perhaps something like PROD would be better. Regardless of how this pans out, for future portals going forward I proposed Portals for Creation at RfC, and created a mockup here if anyone wants a look. — Preceding unsigned comment added by John M Wolfson (talkcontribs)
    Why is requiring administrators to comb through deleted portals to find those that should not have been deleted in order to restore them, having inconvenienced those people who use the portals in the mean time, in any way better for the project than deleting only those that need to be deleted? Thryduulf (talk) 07:34, 4 April 2019 (UTC)Reply[reply]
  • Support. Worthless pages which take 12 seconds to create shouldn't take more than 50000 times that for multiple users to delete. If a subject WikiProject or person interested in the portal's subject is willing to "adopt" that portal, or even assert that the portal is not useless, a more nuanced consideration may apply. And, I should point out, some of the individual deletions are incomplete, as user-facing pages (mostly categories and navigation templates, but some actual article pages) still point to the deleted portals. — Arthur Rubin (talk) 10:25, 4 April 2019 (UTC)Reply[reply]
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Proposal 5: Shut down or reform WikiProject Portals[edit]

I know, me proposing shutting down a WikiProject I'm in? What am I thinking?

Well, I mainly joined to make sure things would go smoothly after that RfC to delete all portals - clearly it has not. As thus, I think a solution (among the others) would be to shut down the WikiProject responsible for many of the bad portal creations. Right now it appears all its doing is creating new portals, not maintaining or improving them - which is what a WikiProject is supposed to do.

However, a less extreme solution would be to reform the project to actually maintain and improve the portals it creates, and creates portals sparingly. I'm fairly certain a task force making sure portals meet standards would be beneficial to the issue, and also making it clear that not everything needs a portal.

I'm going for the latter option to reform - however, I'm going to leave the shutdown option up in the air in case people find good reason for it to be considered.

Addendum 13:48, 15 March 2019 (UTC) - Since I forgot to clarify (Template:Selftrout) here's two examples of reforms I could see being useful:

  • A quality scale for portals, like we use for articles - this could help with knowing which portals are good and which ones need improvement
  • Dividing the Project into task forces to make sure necessary tasks for the maintenance of portals are completed, as right now they clearly are not
  • Sub-reform for this would be to make a task force that deletes bad portals that don't meet quality standards and are not needed

Hopefully this can help clarify this proposal somewhat - if none of these can be done reasonably (which I doubt they can't) the shutdown option should be considered.

Kirbanzo (userpage - talk - contribs) 23:01, 14 March 2019 (UTC)Reply[reply]

Survey on sub-proposal to shut down WikiProject Portals[edit]

The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.

  • Neutral as per above. Kirbanzo (userpage - talk - contribs) 23:01, 14 March 2019 (UTC)Reply[reply]
  • Strong oppose firstly this is the wrong forum, secondly there is nothing in the nomination that explains why this is needed, or how it will result in an improvement to the encyclopaedia. Thryduulf (talk) 01:04, 15 March 2019 (UTC)Reply[reply]
  • Oppose. Abyssal (talk) 01:35, 15 March 2019 (UTC)Reply[reply]
  • Support: might as well. --K.e.coffman (talk) 02:23, 15 March 2019 (UTC)Reply[reply]
  • Oppose. There is consensus to keep the portal system but it has many faults, so a focus for improving it seems sensible. Certes (talk) 14:36, 15 March 2019 (UTC)Reply[reply]
  • Strong oppose. Not necessary and not the best way to fix Wikipedia’s portals. — pythoncoder  (talk | contribs) 19:49, 15 March 2019 (UTC)Reply[reply]
  • Oppose – Would amount to throwing the baby out with the bathwater. North America1000 01:19, 16 March 2019 (UTC)Reply[reply]
  • Oppose For the same reasons. — AfroThundr (u · t · c) 19:48, 16 March 2019 (UTC)Reply[reply]
  • Oppose For the same reasons. Bermicourt (talk) 22:37, 16 March 2019 (UTC)Reply[reply]
  • Support Incompetent project that doesn't want to deal with the crud their members create. CoolSkittle (talk) 18:07, 17 March 2019 (UTC)Reply[reply]
  • Oppose as ad hominem vindictiveness. The only rationale for deleting such a project would be a proper community-wide decision to eliminate all portals. This is not the venue for that; WP:VPPOL is. And this is not the venue for deletion of a wikiproject; WP:MFD is. WP:Process is important, most especially in deletion discussions and related matters, because damned near zero people are going to look for such discussions in an admins' "house organ" page like this. Hardly any non-admins watchlist this page or pay any attention at all to what is said here. It is not intended to be a venue for community-wide concerns in the first place, and even with belated addition to WP:CENT, discussing such matters here is a special kind of forum shopping, namely an attempt to appeal to a small cadre of specialist editors whose concerns about maintenance (and cop-like role of "going after" people for alleged behavioral flaws, often with little oversight, especially compared to WP:ANI process) will colour everything they do and say about the matter.  — SMcCandlish ¢ 😼  20:58, 17 March 2019 (UTC)Reply[reply]
Widely misleading arguments. This is a widely advertised and widely participated discussion. It came from a VPR discussion, linked from the very beginning. There are far more non-Admins than Admins involved here. Try to stick to facts. Legacypac (talk) 23:23, 17 March 2019 (UTC)Reply[reply]
  • Support [non-admin comment :] opposed to portals, they harvest legitimate contributions yet the creators expect them to be automatically protected as legitimate contributions and outside of normal guidance on creation. There are cadres of users who think this is what wikipedia is about, or at least it is a way of making a big splash without knowing anything but how to tweak code (and then wikilawyer when challenged). cygnis insignis 06:10, 18 March 2019 (UTC)Reply[reply]
  • Oppose Punishing a whole community for the actions of one person is not reasonable. WaggersTALK 16:49, 18 March 2019 (UTC)Reply[reply]
  • Oppose per above. It's getting cold out... SemiHypercube 16:52, 18 March 2019 (UTC)Reply[reply]
  • Oppose In the grand scheme of things I'd like to see portals deprecated, but doing so is not where the community is at right now. If there is consensus to keep portals, having a wikiproject to maintain them seems like a good idea. I also feel cold... Wugapodes [thɑk] [ˈkan.ˌʧɹɪbz] 06:47, 19 March 2019 (UTC)Reply[reply]
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Survey on sub-proposal to reform WikiProject Portals[edit]

  • Support as proposer and per above. Kirbanzo (userpage - talk - contribs) 23:01, 14 March 2019 (UTC)Reply[reply]
  • Oppose as the proposal is in the wrong forum and contains no details of what reform is being suggested, let alone how these reforms would solve the issues identified. Thryduulf (talk) 01:05, 15 March 2019 (UTC)Reply[reply]
  • This is related to the discussion as the WikiProject is headed by the user being discussed here. Kirbanzo (userpage - talk - contribs) 13:48, 15 March 2019 (UTC)Reply[reply]
    • Wikprojects are a collection of editors, not just one person. There is no evidence presented that there is any admin action required regarding the WikiProject as a whole collectively (not that I can immediately think of what that action could look like if it were), and there isn't even consensus that admin action regarding the single editor is required. Thryduulf (talk) 13:57, 15 March 2019 (UTC)Reply[reply]
  • Fair point, but considering the discussion below it should still be considered. Kirbanzo (userpage - talk - contribs) 14:00, 15 March 2019 (UTC)Reply[reply]
  • Support. I’ve been doing some reform work of this type by creating a page to clean up some of the damage done to the older portals. WikiProject Portals has an assessment page but I’m not sure how much it gets used. — pythoncoder  (talk | contribs) 19:49, 15 March 2019 (UTC)Reply[reply]
    • It took quite a lot of discussion to form a consensus for those assessment criteria. Any portals would need to be evaluated against them to ensure they meet at least minimal quality standards (not including the other criteria in the portal guidelines). It will take a while to go through all of the portals and rate them on the quality scale, and that is one of our backlog tasks. — AfroThundr (u · t · c) 19:48, 16 March 2019 (UTC)Reply[reply]
  • Support in theory. It makes more sense than the above "I disagree with you so I will try to just erase you" bullshit. However, it's not at all clear that the wikiproject, as such, needs any "reform"; rather, some specific decisions and actions taken by its participants have turned out to be controversial, and the community will discuss that (hopefully in a more sensible venue like WP:VPPOL), and the wikiprojects should abide by the result of that process. We don't have any indication this would not happen, so there isn't actually a "reform" to perform, nor is there yet any consensus of what form that should take anyway. Some people here seem to be under the impression that WP is going to come out against portals; others that it'll be against automated portals; others that it'll be against portals on minor topics (and sub-sub-sub-topics) that people aren't likely to seek a portal for; others that nothing is actual broken; others that .... There isn't a single direction of "reform" being proposed.  — SMcCandlish ¢ 😼  21:03, 17 March 2019 (UTC)Reply[reply]
  • Oppose The way to reform a project is to get involved with it. We've already had multiple discussions about how the project should be structured and how it should operate on the project pages themselves, and further suggestions there are always welcome. But proposing "reform" without specifying what particular changes are being suggested isn't exactly helpful. WaggersTALK 16:53, 18 March 2019 (UTC)Reply[reply]
Exactly right, Waggers, exactly right. You've hit the nail on the head. ~Swarm~ {talk} 18:22, 20 March 2019 (UTC)Reply[reply]
But is you see little need for portals why get involved? Legacypac (talk) 23:18, 21 March 2019 (UTC)Reply[reply]
Nominating hundreds of portals for deletion is getting involved. If you see little need for them then fine, live and let live, they're not doing you any harm. The community has decided to keep portals, so either you respect that consensus and ignore them, or you respect that consensus and get involved with resolving whatever problem you have with them. WaggersTALK 12:58, 3 April 2019 (UTC)Reply[reply]
  • Qualified support. The current project is far from perfect but it's hard to give unqualified support without a statement of specific reforms. We don't want thousands more portals, but last year's RfC shows that it would be equally inappropriate to "reform" into WikiProject Nuke All Portals From Orbit. I removed my name from the project's roster when portal creation grew rapidly. Since then I have done some maintenance but I see little point in improving pages that other editors are working so hard to delete. I could rejoin a project that combined improved existing portals with the right blend of identifying poor, narrow portals for deletion and creating portals in small numbers where clear gaps exist. Certes (talk) 13:32, 29 March 2019 (UTC)Reply[reply]

Discussion on proposal to reform WikiProject Portals[edit]

  • Query @Kirbanzo: - do you have any early thoughts about what some good reforms would be to shift the primary focus of the project towards maintenance/improvement over creation? Nosebagbear (talk) 23:11, 14 March 2019 (UTC)Reply[reply]
  • Transcluded to Wikipedia talk:WikiProject Portals. {{3x|p}}ery (talk) 23:36, 14 March 2019 (UTC)Reply[reply]
  • No, do not transclude important discussions from AN to the relevant talkpage. Hold the discussion on the relevant talk page. Transclude to here is there is good reason, which there is not. Holding hte discussion here means watchlisting it doesn't work, and it wont be archived in the right place. Shutting down a WikiProject is not in scope for WP:AN. --SmokeyJoe (talk) 02:20, 15 March 2019 (UTC)Reply[reply]
  • The Portals Wikiproject members can't even come up with a proper new guideline for what topics get a portal even when faced with a village pump imposed moratorium. The discussion is all over the place with no focus. Heck they did not even follow their old guideline about picking subjects broud enough to gain reader and editor interest. The only thing they appear to agree on is MORE MORE MORE and using WP:VITAL as a to do list. Their newsletter said they are pushing to 10,000 portals (off a base of 1500 old line portals). Now the number of portals will shrink until and unless they get new guidelines passed by an RFC. Legacypac (talk) 09:57, 15 March 2019 (UTC)Reply[reply]
  • That old guideline wasn't generally followed, ever. That's because portals (except those on the main page) get about 1 to 3 percent of the amount of traffic that their corresponding root articles get. In other words, "not a lot". That's because almost all their traffic comes via WP internal links. Almost nobody googles "Portal". So, for the vast majority of topics, large numbers of readers and editors will never be forthcoming, and never were. Out of the 1500 portals, about 100 had maintainers (maintained by around 60 editors), and maybe 20% of them regularly edited the portals they maintained.
The WikiProject, and the community, need feedback in the form of hard numbers, in order to get a sense of what will even get used. How hard would it be to make a chart listing all the portals in one column, and their page views for the past month in the second column, and then sort the chart by the second column? That might provide some insight.    — The Transhumanist   11:05, 15 March 2019 (UTC)Reply[reply]
  • Sigh. :TTH, you had this data already. You know that portal pageviews are miniscule. At the RFC on deleting the portal namespace, stats were posted on pageviews, and not even all the portals linked from the front page had decent viewing rates.
Yet despite knowing all that, you personally created thousands of new portals, despite having all the evidence in front of you that they are useless.
And when I presented the evidence to you again, and asked you to desist, you were furious. Instead of assessing the issues, you posted multi-screenfull unfocused ramblings replete with shouts of "bias", "personal attack" etc.
The problem is not any shortage of information. The problem is that as @Legacypac notes above, the discussions in the WikiProject have no focus, no regard for available evidence, and no respect for community consensus.
Legacypac and usually disagree, but in this case we see exactly the same problem: a WikiProject which has a long and sustained track record of being utterly incapable of acting responsibly wrt the page within its purview.
This is not solely TTH's doing. TTH bears by far the highest responsibility because TTH has been both the most prolific creator and the most angry objector to calls for restraint, but several other regulars at WikiProject Portals have been equally unfocused and equally bonkers. For example:
So the community simply cannot rely on this group to set and uphold resposnsible guidelines. --BrownHairedGirl (talk) • (contribs) 11:53, 15 March 2019 (UTC)Reply[reply]
@BrownHairedGirl: I make the proposal 5. And it was a proposal. I Support a reform in WikiProject Portals. My idea is the existence of approximately 1000(level 3) single page portals layout, directly linked in tree model with the main page. The role of the wikiproject should be to organize this tree and develop tools to transform all portals into single-page layout portals.Guilherme Burn (talk) 12:11, 15 March 2019 (UTC)Reply[reply]
@Guilherme Burn, no technical diversions. My point is not about how the portals operate; it's about their scope. And 20 pages is insanely narrow. A 20-page portal is just an bloated navbox. --BrownHairedGirl (talk) • (contribs) 12:36, 15 March 2019 (UTC)Reply[reply]
@BrownHairedGirl: I'm trying to figure out how you've come to the conclusion that WPPORT completely ignores evidence and consensus. The project discussions I've participated in have been rational and reasonable, and far from unfocused. Also, please try not to conflate individual editors' behavior with the project as a whole. I've seen no evidence that the WikiProject has acted irresponsibly regarding the Portal system. If you're referring to the several thousand new portals created by TTH, you should keep in mind that WikiProjects don't have any actual authority to dictate who can and can't create something (even if we were opposed to creating new portals). That's what guidelines are for.
We've been working to develop updated criteria for the Portal guidelines since November (rebooted from even earlier discussions in April) - which you already know, since you've participated as well. We're still working on the guidelines so that we have better, more concrete criteria to judge new and existing portals against (and which would make MfD easier for those that fail). Once we've developed consensus on these, they can be applied to the namespace to fix the portals that can be fixed, and remove the ones that can't (new or old). (Side note: Anyone with input or ideas is welcome to participate at WT:PORTG.)
Actions in the Portal namespace itself (for most of us, it seems) has mostly been technical fixes and tweaks to our tools. Also, your not agreeing with particular proposals does not make those proposing them irresponsible or incompetent. Talk pages are a place to discuss new ideas so that we can find the benefits and drawbacks of each. If we constantly had to worry about being labeled as irresponsible or incompetent for suggesting something, we'd never have any new ideas or get anything done. I've made plenty of suggestions that didn't pan out later, as I'm sure you have, and everyone else here. That's how we learn what works and what doesn't and build a better encyclopedia. In the end, that's what we're all here for right? — AfroThundr (u · t · c) 19:48, 16 March 2019 (UTC)Reply[reply]
@AfroThundr3007730: that's not at all how it looks from outside.
  1. Last year, the project began developing automated portals, whose advocates claimed need little or no curation. No attempt was made to hold an RFC to determine whether the community found these automated portals to be a worthwhile addition. (I think I see an emerging consensus that they are not useful, or maybe useful only in some curcumstances)
  2. Following the WP:ENDPORTALS RFC which decided not to actually delete the whole portal namespace, the project decided to massively expand the number of portals, despite the clear evidence at RFC that many editors wanted fewer portals. At no point did the project initiate an RFC to establish whether there was a community consensus for the project's enthusiasm to bizarrely interpret "don't TNT the lot" as "create thousands more".
  3. You are right that a WikiProject has no powers of restraint on an individual editor. However, the project does have an ability to watch what is done, and to act a venue to monitor inappropriate creations, and to initiate cleanup as needed. I see no sign at all that the project has done any of that ... and on the contrary, when outsiders have challenged TTH's sprees of portalspam, other project members have rallied to TTH's defence.
  4. Even now, as a cleanup is underway, I see next to no assistance from project members. V few even comment in the MFDs. For example, take the most extreme case so far: MFD Portal:University of Fort Hare, an utterly absurd creation for which there exists precisely zero relevant selected articles ... yet none of the project regulars is visible.
    In my view, a WikiProject which shows zero interest in removing inappropriate pages within its scope is dysfunctionally irresponsible.
  5. The project's efforts to develop guidelines have been exceptionally poor. The discussions have been rambling and unfocused, with a persistent failure to distinguish between factors such as technical ability to create, availability of editors to maintain and monitor, actual usage data, etc.
  6. Above all, none of the proposals has been put to an RFC to gauge community consensus, so the guideline discussion have effectively been the work of a small group of editors who are united by a common desire to massively increase the number of automated portals.
  7. The result of this failure has been a walled garden of thousands of micro-portals, sustained only by the enthusiasm of the portal project ... and the absolutely inevitable massive shitstorm at the village pump.
What this needs now is a structured RFC, which brings together some or all of the proposals made at the project, adds proposals from outside the project, and seeks a community consensus. --BrownHairedGirl (talk) • (contribs) 20:18, 16 March 2019 (UTC)Reply[reply]

Proposal 6: Proposed Deletion for portals[edit]

The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.

Proposal: Create a proposed deletion criterion for portals created on April 8, 2018 or later by any user. Per normal PROD rules, the page would be deleted after 7 days, but a user who objects to the deletion may remove the prod template. However, unlike regular PROD, the creator would not be allowed to remove the template (though they would of course be allowed to contest it on the talk page). — pythoncoder  (talk | contribs) 21:58, 22 March 2019 (UTC)Reply[reply]

  • Support as proposer. I proposed this to resolve issues raised by various opposers. This would provide a longer waiting period before deletion, reduce the chances that the recently created portals that comply with the portal guidelines, and not restrict it to a single user, because there were other users who created problematic portals. Possible reasons for removing a prod template include the portal meeting the portal guidelines or being under active development. — pythoncoder  (talk | contribs) 21:58, 22 March 2019 (UTC)Reply[reply]
  • Comment. I'm leaning support, having been mulling over proposing something like this myself but, I'm not certain this proposal is quite right yet. I don't think there should be a list of acceptable reasons to deprod, rather a non-exhaustive list of examples to reduce the chance of wikilawyering about it (and there will be situations we don't think of and probably some we do that we shouldn't list per WP:BEANS). Any restriction on creators deprodding needs to come with exceptions for reverting obvious vandalism and where prod is not permitted (e.g. doesn't meet the criteria, previously kept in a discussion, etc) - it may be better to say creators should not rather than must not. I also think it important that prodded portals show up in article alerts before this goes live (I no idea if this would require any changes to bot code or not, and if it does how significant it might be). Thryduulf (talk) 22:21, 22 March 2019 (UTC)Reply[reply]
    The deprod "criteria" are suggestions and not part of the proposal. — pythoncoder  (talk | contribs) 01:56, 23 March 2019 (UTC)Reply[reply]
    I wasn't certain either way, so thanks for clarifying. I do think though that jumping straight in to an RfC without workshopping the proposal first was a poor choice though - there is a good idea but it needs refining before I am comfortable supporting it. Thryduulf (talk) 03:11, 23 March 2019 (UTC)Reply[reply]
  • Prod isn't going to do anything except delay MFD for a week so long as there's multiple users who think all portals, however narrow, should be kept. And there are. —Cryptic 23:35, 22 March 2019 (UTC)Reply[reply]
    • Do multiple users think that? I certainly don't; I just oppose the view that all should be deleted. Certes (talk) 23:43, 22 March 2019 (UTC)Reply[reply]
    • Template:Replyto How does a link to a deletion log support the assertion that there are multiple users who think all portals should be kept? I'm one of the most (perhaps even the most) vocal advocates against the proposed speedy deletion criterion, yet I do not hold that view. I've repeatedly explained that I simply think that only some of the portals should be deleted, and that it is more important to get it right than to do it quickly - there is no deadline. Thryduulf (talk) 00:09, 23 March 2019 (UTC)Reply[reply]
  • Oppose. This would be a pseudo-CSD failing WP:NEWCSD. Better to list or reference all new templated portals in a big MfD. —SmokeyJoe (talk) 00:18, 23 March 2019 (UTC)Reply[reply]
  • Comment some users think all portals, no matter how narrow or inappropriate the topic, need to be debated at MfD. SmokeyJoe wants a 3500 portal MfD yet NorthAmerica1000 is complaining about a 6 fruit portals being bundled. A lot of unreasonable positions here. Legacypac (talk) 01:00, 23 March 2019 (UTC)Reply[reply]
  • Comment What's to stop the group behind the auto-portals removing every PROD? CoolSkittle (talk) 01:24, 23 March 2019 (UTC)Reply[reply]
    • I would imagine exactly the same thing that stops (groups of) editors systematically removing prods from any given set of articles - doing so is disruptive editing - just as systematically tagging any large set of articles without considering them is (see also WP:FAITACCOMPLI and WP:SK points 2 and 3). Thryduulf (talk) 03:16, 23 March 2019 (UTC)Reply[reply]
  • Comment check out some of the comments here Wikipedia:Miscellany for deletion/Portal:Alhambra, California where all portals prior to the reboot survived a deletion discussion as acceptable and any similar ones are therefore acceptable. No one followed the guidelines because they don't matter anymore. Amazing stuff. Legacypac (talk) 01:57, 23 March 2019 (UTC)Reply[reply]
  • Transcluded to Wikipedia talk:Proposed deletion. {{3x|p}}ery (talk) 02:34, 23 March 2019 (UTC)Reply[reply]
  • Template:SbbOppose CSD is better, this just sounds like MfD with extra steps. SemiHypercube 11:19, 28 March 2019 (UTC)Reply[reply]
  • Oppose I can think of at least three editors who would make it their duty in life to automatically remove a PROD with the rationale, "Controversial; take to MfD". Which makes this a waste of everyone's time. ——SerialNumber54129 11:25, 28 March 2019 (UTC)Reply[reply]
  • Oppose Being created recently is not a rationale for deletion, let alone semi-speedy deletion. Certes (talk) 13:35, 29 March 2019 (UTC)Reply[reply]
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Proposal 7: Toss it to the WikiProjects[edit]

I suggested at the Arbcom case that this be imposed by motion as an interim measure, but I'll put it as a proposal here to allow people to support or oppose it.
Proposal: All editors intending to create a portal must consult with the relevant WikiProject for that topic as to whether they feel a portal would be useful. All existing portals should be raised at the talk pages of the relevant WikiProjects and deleted if there is no consensus at any one of those projects that the portal should be kept. If the topic has no relevant WikiProject, it should be deleted. ‑ Iridescent 10:42, 29 March 2019 (UTC)Reply[reply]

  • Support as proposer. This would have the advantages of avoiding bulk speedy deletions, avoiding personalising disputes or naming-and-shaming individuals on either the pro or anti side, avoiding flooding MFD, putting the decision on each portal in the hands of those who actually know about that topic and can make an informed call as to whether the portal would be potentially useful (if a topic is so obscure that it doesn't have a relevant project, then it's reasonable to assume that it's unlikely there are sufficient people with an interest in the topic to maintain or use a portal), and providing an opportunity to neutrally assess whether the older portals are still deemed to be serving a useful purpose. The process could probably be largely automated; a bot could presumably scrape the WikiProjects listed on the talk page of the parent article for each portal, and post a "Do you find this portal useful?" question to the talk pages of those projects, and after a reasonable time (presumably 30 days) we could then go through at leisure and see which portals are considered worth keeping. It might annoy some projects, as e.g. WT:WikiProject Food or WT:WikiProject United States will be flooded with 50 different discussions, but unless we're going to speedy delete or speedy keep every portal there will be a flooding effect somewhere, and at least this way it spreads the flood to a manageable level across multiple pages, rather than dumping 4000 pages into WP:MFD or CAT:EX. ‑ Iridescent 10:42, 29 March 2019 (UTC)Reply[reply]
  • Support as the compromise candidate. It's not guaranteed to annoy no-one or be loved by all, but it's better than, as we seem to be enjoying atm, a process that annoys more and is loved even less... ——SerialNumber54129 10:56, 29 March 2019 (UTC)Reply[reply]
    • It won't be liked by anyone, as it concentrates the decision-making in the hands of small cliques of people, but at least it (1) spreads the load regarding where the discussions take place, (2) notifies people interested in the topics who may not be aware of the existence of the portals, and (3) means the fate of Portal:London transport is decided by people who have an interest in either London or Transport and hopefully have a better idea than the rest of us of what would be useful to readers. ‑ Iridescent 11:05, 29 March 2019 (UTC)Reply[reply]
  • Template:Ec Support with minor tweaks: To avoid flooding WikiProjects there should be a limit on the number of concurrent discussions on each project (somewhere in the 5-10 region would be my first suggestion) and the 30-day deadline should not be absolute - e.g. if discussion is ongoing at that point there is no rush to close it, equally if consensus is abundantly apparent (by the standards of WP:SNOW) before that there is no reason to delay taking any necessary action or inaction. Discussions should also be framed neutrally (i.e. don't describe it as "spam", "worthless", "essential" or anything like that.) Also, to avoid edit warring, arguments, etc there should be no extended discussion of which projects are asked - if any editor in good faith believes that a project is worth asking then they are worth asking. Finally there should be a list kept somewhere (probably at the portals project) of which projects have been asked about which portals so the same project doesn't get asked about repeatedly. Thryduulf (talk) 11:15, 29 March 2019 (UTC)Reply[reply]
    On the neutral point, it might be worth agreeing a standard wording that can be added with a template that also provides links to basic information about portals so people don't have to keep repeating themselves. Thryduulf (talk) 11:18, 29 March 2019 (UTC)Reply[reply]
  • Strong Oppose - See the bullet points below for my various rationales.
  • Wikiprojects are perenially understaffed and underwatched, with some having no participation for months or even years at a time on their talk pages. Some are marked as semi-active or inactive. Making it a requirement to consult with projects with such problems would amount to muzzling portal creations for many topics, because nobody may actually come along to discuss a portal proposal.
  • This proposal would further denigrate Wikipedia in the wrong direction, with an increasing nanny state type of governance regarding content, where permissions have to first be made to create pages. This would result in even more chilling effects than already exist in various areas of the encyclopedia at this time.
  • The proposal goes entirely against the grain of WP:5, point #5, concerning being WP:BOLD. Wikipedia having no firm rules is one of the fundamental principles of the encyclopedia. The proposal also goes against the grain of WP:NOTBUREAUCRACY in several ways.
  • Regarding the notion that if a topic has no project, the portal would then be procedurally deleted: some topics may not have a direct Wikiproject, but may have a related one. For example, there is no direct project for the topic of air conditioning, but a related project would be WikiProject Engineering.
Furthermore, many of the discussions listed at WikiProject Council/Proposals receive very little input, sitting in limbo. If a Wikiproject cannot be created without first consulting a forum that receives little input, and therefore a portal could not be created without a project backing it, all without a means for a project to get off the ground in the first place, it would amount to a vicious circle of automatically denying portal creation for some topics based upon the already largely broken system at the WP Council.
  • Would older portals also be automatically, procedurally deleted if no project exists, or would this only apply to the newer ones, with a grandfather clause existent for the older portals? Either way, automatic deletion in this manner goes against several core principles of Wikipedia, and would serve to unnecessarily stifle the creation of functional, useful content.
  • Regarding having discussions for all existing portals raised on talk pages of relevant Wikiprojects: this is very unlikely to even be viable. Who would ultimately be responsible to perform creating and then watching all of these discussions? Would said posited discussions be a subjective straw poll, or based upon actual objective discussion about a portal's content and how it relates to a topic? Importantly, this would significantly and negatively shift Wikipedia from being a volunteer project to one that requires specific actions, in this case, mandatory discussions for all content in the portal namespace. This would set a very poor precedent for the encyclopedia.
  • Regarding the notion of procedurally deleting portals if no consensus exists in a talk page discussion: at AfD, MfD, and other areas of deletion on Wikipedia, a no consensus result typically results in retention of a page or pages, rather than deletion.
  • There's more, but I will leave my post at that for now.
North America1000 12:16, 29 March 2019 (UTC)Reply[reply]
  • Oppose I appreciate this proposal as one made in good faith using reasoned language. We should certainly invite WikiProjects to have more involvement in portals, including their creation and deletion. However, Northamerica1000 makes enough convincing arguments that I don't need to add any. Certes (talk) 13:40, 29 March 2019 (UTC)Reply[reply]
  • Unfortunately reasonable, but WikiProjects do not own topics within their scope. (See also WP:CONLEVEL.) --Izno (talk) 13:48, 29 March 2019 (UTC)Reply[reply]
  • An essentially similar proposal is under discussion at the portal guidelines talk page. The issue is not one of ownership; it's integrating support for portals with the same interested editors who maintain the navigation boxes and articles for the topic area. Particularly if the helper templates are used, editors need to take portals into account when modifying any associated navigation boxes and articles. But in general, portals can only be successful in the long term if they are supported in the same way as the rest of the related content. Accordingly, decisions on their creation and maintenance should be made by those editors, either under the aegis of associated WikiProjects, or through other methods of identifying editors active in the area. isaacl (talk) 15:11, 30 March 2019 (UTC)Reply[reply]
  • If a portal is of high quality, it does not really matter whether there is a WikiProject about a related topic or not. Usually there will be a WikiProject (we have projects covering almost everything), but probably not a very active one. I do agree with the inviting subject experts to portal discussions, though. —Kusma (t·c) 15:25, 30 March 2019 (UTC)Reply[reply]
  • Support - I have tossed this out at the Village Pump. See . Robert McClenon (talk) 21:28, 30 March 2019 (UTC)Reply[reply]
  • Comment - I will argue that NorthAmerica1000's argument about understaffed WikiProjects is a valid consideration that will serve as a check on the creation of rogue portals. (We are not discussing rogue WikiProjects here.) Robert McClenon (talk) 21:28, 30 March 2019 (UTC)Reply[reply]