Jump to content

Wikipedia:Categories for discussion

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by William Allen Simpson (talk | contribs) at 00:17, 20 June 2006 (+June 20). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Purge the cache to refresh this page

See How to use this page for the official rules of this page, guidelines for Speedy Deletion and Speedy Renaming, and how to do cleanup. See Wikipedia:Naming conventions (categories) for the policies guiding many renaming decisions.

Deletion of a category may mean that the articles and images in it are directly put in its parent category, or that another subdivision of the parent category is made. If they are already members of more suitable categories, it may also mean that they become a member of one category fewer.


How to use CfD

Nomination procedure

Twinkle

You may use Twinkle to facilitate CfD nominations. To install Twinkle, go to Special:Preferences#mw-prefsection-gadgets and check "Twinkle" in the "Browsing" section. Use the now-installed "XfD" (Start a deletion discussion) tab while viewing the page you want to nominate.

Twinkle only allows you to nominate a single category or stub template. For bundled nominations including multiple categories, see § MassCFD.

MassCFD

You can use the script User:Qwerfjkl/scripts/massXFD to automatically make mass nominations.

Manual nominations

I
Preliminary steps.

Before nominating a category:

In the following special cases:

For further information, see Wikipedia:Categorization and Wikipedia:Manual of Style.

II
Edit the category.

Add one of the following templates at the beginning of the category page (not the talk page) of every category to be discussed. For nominations involving large numbers of categories, help adding these templates can be requested here.

Otherwise, if nominating a single category:
  • For deleting, use {{subst:Cfd}}
  • For merging, use {{subst:Cfm|Other category}}
    • For merging to two categories, use {{subst:Cfm-double|Other category 1|Other category 2}}
  • For renaming, use {{subst:Cfr|Proposed name}}
  • For splitting, use {{subst:Cfs|Proposed name 1|Proposed name 2}}
  • For converting the category into a list, use {{subst:Cfl|Proposed name}}
  • For other options (containerization, etc.), use {{subst:Cfd|type=nature of proposed discussion}} (see Template:Cfd/doc#Optional parameter)
If nominating a group of related categories, use a bundled nomination:
  • For deleting, use {{subst:Cfd|CfD section name}}
  • For merging, use {{subst:Cfm|Other category|CfD section name}}
    • For merging to two categories, use {{subst:Cfm-double|Other category 1|Other category 2|CfD section name}}
  • For renaming, use {{subst:Cfr|Proposed name|CfD section name}}
  • For splitting, use {{subst:Cfs|Proposed name 1|Proposed name 2|CfD section name}}
  • For converting the category into a list, {{subst:Cfl|Proposed name|CfD section name}}
  • For other options (containerization, etc.), use {{subst:Cfd|type=nature of proposed discussion|CfD section name}} (see Template:Cfd/doc#Optional parameter)
  • Include "CfD", "CfM", "CfR", "CfS" or "CfL" in the edit summary, and do not mark the edit as minor. Preview before saving.
  • To add the template for previous nomination days, use the "full" version of the template by appending "full" to the template name, i.e. {{cfd full}}, {{cfm full}}, {{cfr full}}, {{cfs full}} and {{cfl full}}. Use the |day=, |month= and |year= parameters to make the banner link to the correct CfD page.
  • Consider adding {{subst:cfd notice|Category name|2024 September 16|CfD section name}} ~~~~ to the talk page of the category's creator.
  • For details about these templates, see each template's documentation.
III
Create the CFD section.

Click THIS LINK to edit the section of CfD for today's entries.

Follow the instructions (visible in edit mode) to copy and paste one of the templates below. When inserting category names into these template's parameters, except the text= parameter, omit the Category: prefix and do not use wikilinks, as the template takes care of this.

If nominating a single category:
  • For deleting, use {{subst:Cfd2|Obsolete category|text=Your reason(s) for the proposed deletion. ~~~~}}
  • For merging, use {{subst:Cfm2|Origin category|Destination category|text=Your reason(s) for the proposed merge. ~~~~}}
    • For merging to two categories, use {{subst:Cfm2|Origin category|Destination category 1|target2=Destination category 2|text=Your reason(s) for the proposed merge. ~~~~}}
  • For renaming, use {{subst:Cfr2|Current category|Proposed name|text=Your reason(s) for the proposed rename. ~~~~}}
  • For splitting, use {{subst:Cfs2|Current category|Proposed category 1|Proposed category 2|text=Your reason(s) for the proposed split. ~~~~}}
  • For converting the category into a list, use {{subst:Cfc2|Current category|Proposed article|text=Your reason(s) for the proposed conversion. ~~~~}}
  • For other options (containerization, etc.), use {{subst:Cfd2|Current category|type=other type|text=Your reason(s) for the proposed conversion. ~~~~}}
For a bundled nomination, use one of the standard templates to build the "Cfd section name" for the first nominated category. After saving that, the second and subsequent nominations must be inserted manually, as follows:
==== Cfd section name ====
* 1st category
* 2nd category [Make clear whether you propose deletion, merging or renaming]
* Your reason for nominating the categories, and signature.
  • If a bundled nomination is too long, consider using {{hidden}} to hide some of the nominated categories.
  • In your reason, use links if mentioning articles or categories. To link to a category, use the colon trick by adding a colon (:) to the beginning of the link, e.g. [[:Category:Foo]].
  • Preview before saving to check that your nomination is formatted correctly, and remember to include your signature at the end of the nomination.

Stub types

I
Preliminary steps.

In general, a stub type consists of a stub template and a dedicated stub category. Before nominating a stub type for deletion, merging or renaming:

  • Read and understand guidance for creating stub types and stub type naming conventions.
  • Review the list of existing stub types—be advised, this list may not be comprehensive.
  • If you wish to:
    • Create a new stub type—follow the procedure for proposing new stub types.
    • Delete, merge or rename a stub category only, without deleting or renaming the associated stub template—follow the instructions above this section.
    • Delete or rename a stub template—continue to section II.
II
Edit the template.

Add one of the following tags at the beginning of the template to be discussed.

  • For deletion, use {{subst:Sfd-t|Section name}}
  • For renaming, use {{subst:Sfr-t|Proposed name|Section name}}
  • Please include "SFD" or "SFR" in the edit summary, and don't mark the edit as minor. Preview before saving.
  • Consider notifying the template's creator on their talk page. To find the contributor, check the page history of the stub template.
III
Create the CFD section.

Click THIS LINK to edit the section of CfD for today's entries.

Follow the instructions (visible in edit mode) and paste the following text (remember to update the default parameters):

  • For deletion, use {{subst:sfd-t2|TemplateName|text=Your reason(s) for the proposed deletion. ~~~~}}
  • For renaming, use {{subst:sfr-t2|TemplateOldName|TemplateNewName|text=Your reason(s) for the proposed deletion. ~~~~}}
  • In your rationale, mention how many articles currently use the template to help other editors. When linking to a category in your rationale, always add a colon (:) to the beginning of the link, like [[:Category:Foo]]. This makes a category link that can be seen on the page, and avoids putting this page into the category you are nominating.
  • Preview before saving to check that your nomination is formatted correctly, and remember to include your signature at the end of the nomination.

Notifying interested projects and editors

In addition to the steps listed above, you may choose to invite participation by editors who are likely to be informed about a nominated category. All such efforts must comply with Wikipedia's guideline against biased canvassing. In addition, to help make your messages about the CfD discussion clear, avoid Wikipedia-specific abbreviations, link to relevant policies or guidelines, and link to the discussion itself.

Notifying related WikiProjects

WikiProjects consist of groups of editors who are interested in a particular subject. If a nominated category is within the scope of one or more WikiProjects, consider adding a brief, neutral note on their talk page(s) about the nomination. You may use {{subst:cfd notice|Category name|2024 September 16|CfD section name}} ~~~~ or write a personalized message.

Tagging the nominated category's talk page with a relevant WikiProject's banner will include the category in that WikiProject's Article Alerts if they subscribe to the system. For instance, tagging a nominated category with {{WikiProject Physics}} will add the discussion to Wikipedia:WikiProject Physics/Article alerts.

Notifying substantial contributors to the category

While not required, it is generally considered courteous to notify the good-faith creator and main contributors of the category that you are nominating for discussion. To find the creator and main contributors, check the category's page history or talk page. You may use {{Cfd notice}} to inform the category's creator and all other editors.

Notifying other interested editors

It may be helpful to invite other subject-matter experts by posting a message on the talk page of the most closely related article, such as Protein family for Category:Protein families. You may use {{Cfdnotice}} for this.

Closing procedure

After seven days, someone will close the discussion according to the consensus that formed or, if needed, relist it to allow more discussion. Editors closing discussions must follow the administrator instructions and, except in the case of a "keep" or "no consensus" outcome, implement the result or log it at the Working page to ensure it is implemented.

Redirecting categories

In general, an unpopulated category should be deleted (see speedy deletion criterion C1) because it is not useful for navigation and sorting. In limited circumstances, and because categories cannot be redirected using "hard" redirects (i.e. #REDIRECT[[''target'']]), we use a form of "soft redirect" to solve the issue. You can create a category redirect by adding {{Category redirect|target}} to the category page. Bots patrol these categories and move articles into the "redirect" targets.

In particular, category redirects are used at the former category name when we convert hyphens into en dashes (e.g. Category:Canada-Russia relationsCategory:Canada–Russia relations). It is also helpful to set up category redirects from titles with plain letters (i.e. characters on a standard keyboard) where the category names include diacritics.

A list of redirected categories is available at Category:Wikipedia soft redirected categories.

Redirecting categories

It is our general policy to delete categories that do not have articles in them. Unlike articles, categories are mostly for internal use only. If they don't have any articles, they shouldn't have any links from any articles or any other categories, because they are not useful for navigation and classification.

However, some categories frequently have articles assigned to them accidentally, or are otherwise re-created over and over again. In these cases, we use a form of "soft" redirection.

Categories cannot be redirected using "hard" redirects (#REDIRECT [[target]]) due to limitations in the MediaWiki software. Instead, just use Template:Categoryredirect. The NekoDaemon (talk · contribs) bot hourly automatically patrols these categories and moves articles out of them and into the redirect targets.

You can see a list of redirected categories in Category:Wikipedia category redirects.

Special notes

Some categories may be listed in Category:Categories for deletion but accidentally not be listed here.

See also meta-discussion going on at Wikipedia talk:Categories for deletion phrases regarding the content of the {{cfd}} template, and about advisory/non-advisory phrases to be used on this "Categories for deletion" page.

Anonymous users may nominate and comment on proceedings, just as in AfD. Votes from anonymous or new users may be discounted if they lack edit history. See Wikipedia:Suffrage and WP:SOCK for details.

Categories relating to stub articles should not be nominated here, but should be taken to Wikipedia:Stub types for deletion.

When nominating a category, it's helpful to add a notice on the talk page of the most-closely related article. Doing so would not only extend an additional courtesy, but possibly also bring in editors who know more about the subject at hand. You can use {{cfd-article}} for this.

Speedy renaming and merging

Speedy renaming or speedy merging of categories may be requested only if they meet a speedy criterion, for example WP:C2D (consistency with main article's name) or WP:C2C (consistency with established category tree names). Please see instructions below.

  1. Determine which speedy criterion applies
  2. Tag category page with {{subst:cfr-speedy|New name}} or {{subst:cfm-speedy|Merge target}}
  3. List request along with speedy criteria reason under "Current requests" below on this page

Please note that a speedy request must state which of the narrowly defined criteria strictly applies. Hence, any other non-speedy criteria, even "common sense" or "obvious", may be suitable points, but only at a full discussion at WP:Categories for discussion.

Request may take 48 hours to process after listing if there are no objections. This delay allows other users to review the request to ensure that it meets the speedy criteria for speedy renaming or merging, and to raise objections to the proposed change.

Categories that qualify for speedy deletion (per Wikipedia:Criteria for speedy deletion, e.g., "patent nonsense", "recreation") can be tagged with the regular speedy tags, such as {{db|reason}} with no required delay. Empty categories can be deleted if they remain empty 7 days after tagging with {{db-empty}}. Renaming under C2E may also be processed instantly (at the discretion of an administrator) as it is a variation on G7.

To oppose a speedy request you must record your objection within 48 hours of the nomination. Do this by inserting immediately under the nomination:

  • Oppose, (the reasons for your objection). ~~~~

You will not be able to do this by editing the page WP:Categories for discussion. Instead, you should edit the section WP:Categories for discussion#Add requests for speedy renaming and merging here or the page WP:Categories for discussion/Speedy#Add requests for speedy renaming and merging here (WP:CFDS). Be aware that in the course of any discussion, the nomination and its discussion may get moved further down the page purely for organizational convenience – you may need to search WP:CFDS to find the new location. Participate in any ongoing discussion, but unless you withdraw your opposition, a knowledgeable person may eventually bring forward the nomination and discussion to become a regular CFD discussion. At that stage you may add further comments, but your initial opposition will still be considered. However, if after seven days there has been no support for the request, and no response from the nominator, the request may be dropped from further consideration as a speedy.

Contested speedy requests become stale, and can be untagged and delisted after 7 days of inactivity. Optionally, if the discussion may be useful for future reference, it may be copied to the category talk page, with a section heading and {{moved discussion from|[[WP:CFDS]]|2=~~~~}}. If the nominator wants to revive the process, this may be requested at WP:Categories for discussion (CfD) in accordance with its instructions.

If you belatedly notice and want to oppose a speedy move that has already been processed, contact one of the admins who process the Speedy page. If your objection seems valid, they may reverse the move, or start a full CFD discussion.

Speedy criteria

The category-specific criteria for speedy renaming, or merging are strictly limited to:

C2A: Typographic and spelling fixes

  • Correction of spelling errors and capitalization fixes. Differences between British and American spelling (e.g. Harbours → Harbors) are not considered errors; however if the convention of the relevant category tree is to use one form over the other then a rename may be appropriate under C2C. If both spellings exist as otherwise-identical category names, they should be merged.
  • Appropriate conversion of hyphens into en dashes or vice versa (e.g. Category:Canada-Russia relations → Category:Canada–Russia relations).
  • Correction of obvious grammatical errors, such as a missing conjunction (e.g. Individual frogs toads → Individual frogs and toads). This includes pluralizing a noun in the name of a set category, but not when disagreement might reasonably be anticipated as to whether the category is a topic or set category.

C2B: Consistency with established Wikipedia naming conventions and practices

C2C: Consistency with established category tree names

Bringing a category into line with established naming conventions for that category tree, or into line with the various "x by y", "x of y", or "x in y" categorization conventions specified at Wikipedia:Category names

  • This should be used only where there is no room for doubt that the category in question is being used for the standard purpose instead of being a potential subcategory.
  • This criterion should be applied only when there is no ambiguity or doubt over the existence of a category naming convention. Such a convention must be well defined and must be overwhelmingly used within the tree. If this is not the case then the category in question must be brought forward to a full Cfd nomination.
  • This criterion will not apply in cases where the category tree observes distinctions in local usage (e.g. Category:Transportation in the United States and Category:Transport in the United Kingdom).

C2D: Consistency with main article's name

  • Renaming a topic category to match its eponymous page (e.g. Category:The Beatles and The Beatles).
  • This applies only if the related page's current name (and by extension, the proposed name for the category) is:
    • unambiguous (so it generally does not apply to proposals to remove a disambiguator from the category name, even when the main article is the primary topic of its name, i.e. it does not contain a disambiguator); and
    • uncontroversial, either because of longstanding stability at that particular name, or because the page was just moved (i) after a page move discussion resulted in explicit consensus to rename, or (ii) unilaterally to reflect an official renaming which is verified by one or more citations (provided in the nomination). C2D does not apply if the result would be contrary to guidelines at WP:CATNAME, or there is any ongoing discussion about the name of the page or category, or there has been a recent discussion concerning any of the pages that resulted in a no consensus result, or it is controversial in some other way.
  • This criterion may also be used to rename a set category in the same circumstances, where the set is defined by a renamed topic; e.g. players for a sports team, or places in a district.
  • Before nominating a category to be renamed per WP:C2D, consider whether it makes more sense to move the article instead of the category.

C2E: Author request

  • This criterion applies only if the author of a category requests or agrees to renaming within six months of creating the category.
  • The criterion does not apply if other editors have populated or changed the category since it was created. "Other editors" includes bots that populated the category, but excludes an editor working with the author on the renaming.

C2F: One eponymous page

  • This criterion applies if the category contains only an eponymous article, list, template or media file, provided that the category has not otherwise been emptied shortly before the nomination. The default outcome is an upmerge to the parent categories, where applicable. Nominations should use {{subst:cfm-speedy}} (speedy merger) linking to a suitable parent category, or to another appropriate category (e.g. one that is currently on the article).

Admin instructions

When handling the listings:

  1. Make sure that the listing meets one of the above criteria.
  2. With the exception of C2E, make sure that it was both listed and tagged at least 48 hours previously.
  3. Make sure that there is no opposition to the listing; if there is a discussion, check if the opposing user(s) ended up withdrawing their opposition.

If the listing meets these criteria, simply have the category renamed or merged – follow the instructions at Wikipedia:Categories for discussion/Administrator instructions, in the section "If the decision is to Rename, Merge, or Delete"; to list it for the bots, use the Speedy moves section.

Applying speedy criteria in full discussions

  • A nomination to merge or rename, brought forward as a full CfD, may be speedily closed if the closing administrator is satisfied that:
    • The nomination clearly falls within the scope of one of the criteria listed here, and
    • No objections have been made within 48 hours of the initial nomination.
  • If both these conditions are satisfied, the closure will be regarded as having been a result of a speedy nomination. If any objections have been raised then the CfD nomination will remain in place for the usual 7-day discussion period, to be decided in accordance with expressed consensus.

Add requests for speedy renaming and merging here

If the category and desired change do not match one of the criteria mentioned in C2, do not list it here. Instead, list it in the main CFD section.

If you are in any doubt as to whether it qualifies, do not list it here.

Use the following format on a new line at the beginning of the list:

* [[:Category:old name]] to [[:Category:new name]] – Reason ~~~~

If the current name should be redirected rather than deleted, use:

* REDIRECT [[:Category:old name]] to [[:Category:new name]] – Reason ~~~~

To note that human action is required, e.g. updating a template that populates the category, use:

* NO BOTS [[:Category:old name]] to [[:Category:new name]] – Reason ~~~~

Remember to tag the category page with: {{subst:cfr-speedy|New name}}

A request may be completed if it is more than 48 hours old; that is, if the time stamp shown is earlier than 00:32, 14 September 2024 (UTC). Currently, there are 2,088 open requests (refresh).

Current requests

Please add new requests at the top of the list, preferably with a link to the parent category (in case of C2C) or relevant article (in case of C2D).

I guess you responded after I stopped checking regularly for a response, so thank you for the note on my talk page. DGG is deceased, so it's obviously not an option to seek his input. I'm opposed to using obscure corners of project space to bypass discussion on items which should be discussed. Some editors in those project spaces appear only interested in pursuing (a purely superficial notion of) consistency, often without regard for whether there was any consistency involved WRT consensus enroute to that point. Hence, my earlier mention of venue-shopping. I have no strong opinion on capitalization variants other than they're often time wasters that stand in the way of moving the project forward. RadioKAOS / Talk to me, Billy / Transmissions 04:52, 2 September 2024 (UTC)[reply]

That doesn't answer the question @RadioKAOS, we need to know whether you're opposing just the national monuments nominations, or also the national forest nominations. Hey man im josh (talk) 13:10, 4 September 2024 (UTC)[reply]
I left them a message after the above reply on their talk page and I've left them another one now. We still need clarity on whether the objection is just to the national monuments renamings, or the other renamings as well, including the national forests. Hey man im josh (talk) 15:48, 10 September 2024 (UTC)[reply]
This is a ridiculous failure of communication... They've been pinged for clarity four times and had three messages left on their talk page about this. Personally I think it's reasonable to proceed with all but the national monuments nominations since there's been a lot of effort made to seek out clarity on this and they're not providing it. I don't think it's unreasonable to believe they're talking about the monuments categories solely, but I'm obviously a bit biased as the nominator. Any thoughts @Ymblanter? Hey man im josh (talk) 17:37, 12 September 2024 (UTC)[reply]
@Hey man im josh, I full support this move but I'd say move this to full Cfd, just to be safe. At this point, it is safe to say this person is deliberatly ignoring you. If they have an objection, they can raise it there. If not, then they had numerous oppertunities to do so. Omnis Scientia (talk) 21:15, 13 September 2024 (UTC)[reply]

Opposed requests

@HouseBlaster: Yes. Instead of doing a speedy move, can you do a move discussion, and post the rationale there? Perhaps WP:CONSUB. @Dekimasu:, would you like to interpret your original close? Did that cover this too? User_talk:Dekimasu#LGBT_->_LGBTQ_move Bluerasberry (talk) 22:50, 10 September 2024 (UTC)[reply]
Multiple people have already supported the move of sub articles (whether it be in Talk:LGBTQ community#Requested move 27 August 2024 RM and (myself including) have started moving various articles that are uncontroversial as many have for a long term already explained the Q in addition to the LGBT. The relevant policy that covers the category now following suit is WP:C2D.
Do you want a collective category move discussion for all categories as a sort of “sampling”? In any case I don’t think there will be any good policy based reason to oppose, other than the personal WP:JDL at this point and we should stop rehashing the same arguments over and over. As for you pinging the closer of the original RM, asking for interpretation, he already did that in his close he noted: This move may require changes to the article text to conform to the new title, and may imply that templates, categories, etc. should also be moved; please consider contributing to this sort of cleanup. - so yes, it implied that categories will likely (using the word may) follow suit in line with our existing consistency policies (CONSUB for artices, C2D for categories) for main and sub-topic relationships. Raladic (talk) 23:06, 10 September 2024 (UTC)[reply]
Raladic (cc: Ymblanter), a common position I see in the move review discussion was that the RM result should strictly only apply to the article, while further renaming of the very numerous associated pages should be subject to further discussion I'd throw in another oppose for all these LGBT/LGBTQ speedies. --Paul_012 (talk) 06:41, 13 September 2024 (UTC)[reply]
@Paul 012 - This blanket opposition to "all LGBT moves" is not in line with policy.
The 2 latest requests I made above:
LGBTQ writers, LGBTQ events
were carefully submitted in line with their respective eponymous List of LGBTQ writers and List of LGBTQ events articles titles.
A blanket statement of saying we need to now run all of these category moves, whether they were bulk, or whether they actually were very deliberate and definitely uncontroversial through the bureaucracy of full category move reviews with an WP:SNOW outcome, then that just grinds us to a halt for no reason. Raladic (talk) 16:49, 13 September 2024 (UTC)[reply]
Those two list articles were only recently moved by you, and not as a result of the RM discussion, which they were not named as part of. C2D does not apply here. --Paul_012 (talk) 17:08, 13 September 2024 (UTC)[reply]
C2D is not preempted just because I was the one that moved them, if those BOLD moves were still uncontroversial (which is the case there, as those pages I moved have LGBTQ events and LGBTQ writers explicitly).
C2D does allow a cat move even if the article it is based on was or (ii) unilaterally to reflect an official renaming which is verified by one or more citations
While my rename was bold, it still is well in line with our article policies, both on CONSUB, but also more specifically for those articles as I just outlined as I checked the content.
Arguably, I didn't provide a citation for the catmove itself as the unilateral part requests (as I missed that part), so on procedural grounds I can see someone could request one and place it on hold, which I'll be happy to provide.
But I dispute that C2D doesn't apply outright on this careful and deliberately selected move. Raladic (talk) 21:05, 13 September 2024 (UTC)[reply]
There is no reason to move quickly with a mass rename of tens of thousands of articles. I am asking for days, not unreasonable delays. I am not re-arguing this as I never got to participate in the move discussion anyway. This started as a move discussion attended by 20 people for one article, and now it is 100,000 moves of links and prose. I do not object to the moves if consensus is there but I want someone, perhaps the closing admin, to take responsibility for the decision that the one-article move discussion was sufficient for these massive changes. At Wikipedia:Move_review/Log/2024_September the closing admin said, I did not write here or elsewhere that the result should be used to "radiate everything outwards" without discussion.. The original move discussion was sufficiently attended for what it was - the move of a single article - but I am arguing that it was not sufficiently attended for mass changes of Wikipedia and what could very well be a change big enough to make the news and be the subject of anthropology studies. I am ready to stand down but I am trying hard to find a venue to have a voice in this. At the move discussion I feel like the subject was whether that one article's move was legitimate, and I agree it was, but I still want to be heard about the next cohort of several thousand moves when they are considered collectively. Bluerasberry (talk) 21:12, 13 September 2024 (UTC)[reply]
And that's why, just as I also expressed in the MR and some other editors as well, I posted after the initial RM, the notification on The WikiProject to ensure that the community agreed that in line with our long standing understanding of active members of the project and various sub articles (which I have participated in), that after we found consensus for the main article, likely this would also allow the movement of sub articles. Also as I already noted, this wasn't just the understanding of this single RM that ultimately triggered the move, but the follow up to last years RM, which already pointed everything in that direction and many active editors in the Wikiproject and the space were aware of it and anticipated it, so it didn't come as a surprise to any of us. Prior to the final move to LGBTQ, many sub-articles were repeatedly changed back to "LGBT", even though those pages were always explicitly about LGBTQ, but that was always shot down with the inverse argument of "we want consistency, so we'll keep it LGBT under CONSUB. So those inverse arguments can't have it both ways, now that we do have the main article moved to LGBTQ.
Now I have not moved tens of thousands of pages, nor am I advocating for it in a rush. I first posted the notice to the Wikiproject after the RM and waited, to ensure my feeling on this wasn't wrong, and you expressed opposition, which was discussed there, as well as in the MR, but beyond that, most active editors of the project appear to have had the same thoughts as me as they've followed it closely over the years. Following the SNOW outcome of the MR and not seeing any clear good policy based reasoning for further opposition of moving some sub-articles, I have now started with some individual, very deliberate uncontroversial moves of articles that have already discussed LGBTQ in the article bodies for a long time, including the sourcing to support it (basically using the litmus test of "if someone did decide that they disagreed with my BOLD move, would it be very likely that policy based my move would be supported by a subsequent formal RM for that sub-article (basically following our policies of WP:BEFOREMOVING).
Also independent of my own feeling and the notice, some other editors also appear to feel that it has become appropriate and have started moving a handful of articles. Separate to the few articles I have moved myself over the past few days, none of which have had any opposition from people, in fact, quite the opposite as I've gotten a few "thanks" for them, showing explicit support. So now I'm simply following up and nominating those categories to follow those articles that I believe are uncontroversial, based on the topics they cover. I think the move of many articles (and categories and the likes) will take many months, might even be a year or longer, since we want to be deliberate about it and even just the few articles I have moved, have required a lot of post cleanup, such as link corrections in templates, default sorts and updating article leads and prose as appropriate. But I don't think that it is unreasonable to get started with it in line with those topics that arguably are covering LGBTQ topics and doing so slowly as I have started. An article at a time. Raladic (talk) 21:32, 13 September 2024 (UTC)[reply]
@Raladic: Okay, everything seems cool then. Some articles are moved, and that's fine, and more people know, and that is good too. There was a move discussion last year - that's nice, let's build from that. Now that we have the attention of 100+ people and we know that the discussion is about moving all of this per CONSUB, can we move this to full category discussion? I support pinging everyone who has ever shown interest, to confirm we have consensus for this. Bluerasberry (talk) 21:50, 13 September 2024 (UTC)[reply]
I don't think we so need a collective discussion that says "should every single article be moved" as that question does not have a simple "yes/no" answer, the answer inevitably is "it depends on the context".
Instead, I think the right path forward, and that which I have taken so far is to raise awareness where we can, and go one by one on specific articles, whether it be with WP:BOLD moves with my own abilities as an editor to interpret that article X can likely uncontroversially be moved and stands a reasonable chance based on the data. Or for cases where there may be more contention, that someone will open an RM for that particular article and then it will be moved.
Even from a technical standpoint, we can't bulk move articles because of all the post-cleanup that has to be done manually, so I think doing these moves and trusting editors judgement of whether to be bold (and be subject to a retroactive RM if someone does find contention in a move) or do an RM is the right move, individually, per article. Raladic (talk) 22:05, 13 September 2024 (UTC)[reply]
Note that the now full Wikipedia:Categories for discussion/Log/2024 September 11#LGBT nominations which were opposed at CFDS category discussion for those categories that @HouseBlaster nominated is underway and it also looks like a SNOW case and a very experienced editors has questioned why the speedy move requests were opposed procedurally to begin with.
So I think I'd take that one full CfD as the litmus test for these category moves and hope that after it, we can proceed with the others as CfDS, such as my above ones that were very deliberate. Raladic (talk) 22:19, 13 September 2024 (UTC)[reply]
As it stands now, I will not be willing to move everything anything via CFDS. We always have extremely vocal people coming a week after everything has been moved demanding that the categories get moved back because they oppose the move but were not around during the 48h nomination period. And processing these categories is a lot of my time. I believe my (limited) time is best spent on something else than on moving thousands of categories back and forth.--Ymblanter (talk) 06:54, 14 September 2024 (UTC)[reply]
Hear hear, @Ymblanter. It's about time to move on, I think. We're currently having the same discussion in multiple places and it's becoming a huge time sink.

You state yourself, @Bluerasberry, that at least part of your objection is based on being heard rather than policy. In a single post yesterday, you said:

  • "I never got to participate in the move discussion"
  • "I want someone, perhaps the closing admin, to take responsibility for the decision"
  • "I am trying hard to find a venue to have a voice in this"
  • "I still want to be heard"

Your words strongly suggest, at least to me, that this is actually about feeling unheard and your sense of unfairness that this discussion was resolved without you. And I get that—it sucks when you get left out, or you miss out on something, or it seems no one agrees with you. But I do think you have been listened to—multiple times—and your viewpoint has been taken onboard.

I don't intend my comments as a personal attack, so I apologise if I seem blunt, but your remaining objections no longer seem to be based on valid WP policy. Your policy-based arguments, on the other hand, have all been addressed and discussed in turn, and you've slowly retreated from those arguments. Most people didn't agree with your interpretation of those policies or believe other policies are more relevant, and it seems unlikely anyone is going to change their minds here.

So, in the end, your remaining argument largely seems to boil down to WP:DONTLIKEIT, and holding the process hostage based on this (again, IMO) risks becoming disruptive. I suspect others are getting tired of the same debate, too.

@Raladic's suggestion of addressing each page on a case-by-case basis (following WP:CONSUB where there isn't a specific reason to use another initialism) seems to me to be a very pragmatic one. In fact, it gives people the option to discuss such changes on each individual page, which allows even more people to potentially engage in the discussion—which is exactly what you want, anyway. It doesn't rely on people having to engage with a process within a limited timeframe, either.

It would be great if we could draw a line under this now. I hope we can. Lewisguile (talk) 11:20, 14 September 2024 (UTC)[reply]
I think this is what is happening: "Because of the move discussion at Talk:LGBTQ#Requested_move_14_August_2024, we have now established consensus to move all all instances of LGBT to LGBTQ. This includes categories, wikilinks, and instances of the term in prose, and may be a change of the term in 100,000+ instances. Here we apply that consensus to categories."
@Lewisguile: is this an accurate statement of your reasoning? I am still surprised about the speed and impact of all of this, and want confirmation of what is happening. Is there another consensus statement in support of the move somewhere, or is this the one? Bluerasberry (talk) 20:35, 14 September 2024 (UTC)[reply]
No, I wouldn't say that's quite right. It seems to me that, with the consensus to change LGBT-->LGBTQ, there is a case for moving many, but perhaps not all, pages using the former initialism to the latter, and that this can be done via WP:BOLD as per WP:CONSUB. And I believe that, in most cases, this change will be non-controversial based on policy and changing common usage.

But there will, obviously, be pages that need to stay as LGBT, or some other, related initialism—not least because of proper names of organisations. In those cases, it will mostly be obvious from context (an org called, f'rex, LGBT Organisation would need to retain its name in the relevant article). Where it is debatable, discussion and the requested moves process can help us reach consensus in those specific cases. We therefore don't need a drawn out process to make a blanket decision, because a blanket decision isn't required.

Links currently pointed to LGBT will also redirect to LGBTQ anyway, so there doesn't need to be a sudden effort to change everything. Most of this will happen in time as people edit and tweak individual articles, and/or when any moves occur. That removes the worry that 100,000s of changes will need to be made immediately. Lewisguile (talk) 12:00, 15 September 2024 (UTC)[reply]

On hold pending other discussion

Moved to full discussion

Ready for deletion

Check Category:Empty categories awaiting deletion for out of process deletions. In some cases, these will need to be nominated for discussion and the editor who emptied the category informed that they should follow the WP:CFD process.

Once the renaming has been completed, copy and paste the listing to the Ready for deletion section of Wikipedia:Categories for discussion/Working/Manual.

Discussions

June 20


and

Streams to Rivers

Companies of the United States by state


June 19

Billboard number one categories

Category:Portal:Foo

Billy Meier Categories



June 18

Singles by genre to Songs by genre

Singles by artist nationality to Songs by nationality

More Singles by artist to Songs by artist

and



June 17

Category:Cover songs and subcategories


Cars and stuff

Environmental organizations by country

Roman Catholics by nationality

The Legend of Zelda

models, phase II


June 16

Joke Wikipedian categories

Jntg4 does not have sock puppets. They are brothers.

Number-one categories

RPG Maker categories


June 15

Fabartus user categories


June 14

Victorian era categories for countries other than the United Kingdom



June 13


Cleanup overhead

If process guidelines are met, move categories to the appropriate section here to prepare to delete.

Before deleting a category, please ensure that it is empty.

Please help keep this page clean! Listings that have already been dealt with need to be removed quickly.

List is located at Wikipedia:Categories for discussion/Awaiting closure – updated by AnomieBOT.
See also Wikipedia:Categories for discussion/Old unclosed discussions.

Discussions awaiting closure


Closing procedure


Bot

JJMC89 bot III (talk · contribs · logs) processes the requests on this page. It currently checks for new work at 19 and 49 minutes past the hour.

Process
  • The working page must have full (sysop) edit protection.
  • The bot can only recategorize when a page is categorized using category syntax ([[Category:Foo]]).
  1. The bot iterates over each section of the page using the section header to determine the mode.
  2. Within a section the bot iterates over each line if wikitext.
    • Each line consists of three parts: prefix, wikilinks/templates, and suffix. Everything else is ignored.
      • All wikilinks on the line
        • They must be to a CfD page or a category. The bot will not process the rest of the section if any other wikilink is found.
        • If a CfD link does not contain a section, the bot will attempt figure it out based on the linked CfD page.
      • {{c}}, {{cl}}, and {{lc}} can be used to link categories. All other templates are ignored.
      • The prefix is the plain text at the beginning of the line.
        • The prefix on a line with a CfD link applies to all lines until the next CfD link.
        • If the prefix contains "NO BOT" (case sensitive), the bot will not queue it. (These should be placed on WP:CFD/W/M instead.)
      • The suffix is the plain text at the end of the line.
        • The suffix on a line with a CfD link applies to all lines until the next CfD link unless that line has a suffix.
  3. If a CfD link was found and there is at least one category link is on the line, the bot will queue the request.
  4. After queueing the entire page, the bot will remove any conflicting requests and requests involving disambiguation categories from the queue and then check and process the remaining requests.

Bot work

If the category needs to be split among multiple destination categories, requires template editing, or requires editing the documentation subpage of templates, or any other special circumstances that require manual review, list it at Wikipedia:Categories for discussion/Working/Manual rather than here.

If a category has over 5,000 members to be updated by bot, list it at Wikipedia:Categories for discussion/Working/Large.

Speedy moves

Wikipedia:Categories for discussion/Speedy


Move

Bot information
  • The bot moves the category to a target category without leaving a redirect and removes the {{cfx full}} template.
  • If the prefix contains "REDIRECT" (case sensitive), then the bot will leave a redirect.
  • Checks:
    • The current category cannot be the move target.
    • There must be one move target on the line.
    • If the current category is a redirect, then the target must exist.
    • The target must not be a redirect.
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 August 26
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 5
Wikipedia:Categories for discussion/Log/2024 September 6
Wikipedia:Categories for discussion/Log/2024 September 7
Wikipedia:Categories for discussion/Log/2024 September 7

Merge then delete

Bot information
  • The bot merges the category to one or more target categories and deletes the empty category.
  • If the prefix contains "REDIRECT" (case sensitive) and there is a single merge target, then the bot will redirect the category to the target using {{category redirect}} instead of deleting it and add {{old CfD}} to the talk page.
  • Checks:
    • The current category cannot be a merge target.
    • There must be one or more merge targets on the line.
    • All merge targets must exist and not be a redirect.
Wikipedia:Categories for discussion/Log/2024 September 7
Wikipedia:Categories for discussion/Log/2024 September 7
Wikipedia:Categories for discussion/Log/2024 September 7
Wikipedia:Categories for discussion/Log/2024 September 6
Wikipedia:Categories for discussion/Log/2024 September 6
Wikipedia:Categories for discussion/Log/2024 September 5
Wikipedia:Categories for discussion/Log/2024 September 6
Wikipedia:Categories for discussion/Log/2024 September 6
Wikipedia:Categories for discussion/Log/2024 September 5
Wikipedia:Categories for discussion/Log/2024 September 5
Wikipedia:Categories for discussion/Log/2024 September 5
Wikipedia:Categories for discussion/Log/2024 September 5
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 1
Wikipedia:Categories for discussion/Log/2024 August 31
Wikipedia:Categories for discussion/Log/2024 August 27
Wikipedia:Categories for discussion/Log/2024 August 29
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 1
Wikipedia:Categories for discussion/Log/2024 September 1
Wikipedia:Categories for discussion/Log/2024 September 1
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 5
Wikipedia:Categories for discussion/Log/2024 September 5
Wikipedia:Categories for discussion/Log/2024 September 7


Empty then delete

Bot information
  • The bot removes the category from all pages and deletes the empty category.
  • Checks:
    • There must be one category on the line.
Wikipedia:Categories for discussion/Log/2024 September 5
Wikipedia:Categories for discussion/Log/2024 September 1
Wikipedia:Categories for discussion/Log/2024 September 1
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 1
Wikipedia:Categories for discussion/Log/2024 August 31
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 3
Wikipedia:Categories for discussion/Log/2024 September 2
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 4
Wikipedia:Categories for discussion/Log/2024 September 5
Wikipedia:Categories for discussion/Log/2024 September 7

Retain

Bot information
  • The bot removes the {{cfx full}} template and adds {{old CfD}} to the talk page.
  • If the suffix does not contain the discussion action and result for {{old CfD}}, the bot will attempt figure them out based on the linked CfD page.
  • On the working page, the action/result must be one of the following.
    • no consensus (for|to) action
    • not action
    • keep (The action is assumed to be delete.)
  • Checks:
    • There must be one category on the line.
    • There must be an action and result (on the line or bot detected).
  • None currently


Old by month categories with entries

This section lists old maintenance categories that should be empty but are not. This can result from reversions of pages, incomplete nominations, bot errors, backlogs or pending manual work.