Edge Rewrite
// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a44c725d380126ee

Jump to content

Wikipedia:Articles for deletion/Implementing the PAM–AfD merge

From Wikipedia, the free encyclopedia

Not done

[edit]
Tasks related to the PAM–AfD merge (implementation discussion)
Task namePrio-rityStatusDependent on...DescriptionPlanWhoDiscussions
Update {{afdm}}, {{afd}}, {{afdx}}, {{afdn}} parametersHigh In progress—
  •  Done Expand built-in merge instructions
  •  Done Expand merge parameters to allow multiple targets: see {{Article for deletion/dated/testcases}}
  •  Done Implement named alternatives to unnamed parameters
  •  Done Notify bot/script operators of necessary changes
  •  Done Update all docs!
  • Anything else to allow merge (to) templates to become wrappers (please!!!)
  •  Not done Test rigorously!
oklopfer
Turn PAM {{merge to}} template into wrapper of {{AfDM}} and redirect {{merge}} to itMedium In progressUpdate afd parametersTurn {{merge to}} and {{merge}} into wrappers of the {{AfDM}} template. Details are in the TfD consensus (merge w/ target ≈ merge to w/ 1 or target). Turn the various |talk= parameters into aliases of |afd=
  • Sandbox done for {{merge to/sandbox}}
  • Sandbox done: Turn all of them them into substable wrappers
oklopferAFD#{{Merge to}} wrapper rewrite
Rewrite PAM {{merge from}} and {{being merged from}} template Medium In progress —
  • {{being merged from}} should be swapped with {{afd-merge from}}, and the latter should become a redir to the former, since all future formal merge nominations will be held at AfD (perhaps the other way around is preferred, to keep in line with the other afd templates?)
  • Update the wording of {{merge from}} so it's similar to the AfD templates and specifically mentions AfD. Turn the various |talk= parameters into aliases of |afd=
Being merged backlog needs to be minded when making these changes; in-use templates may need param updates (can be done with AWB/JWB)
Merge {{Old merge}} into {{old XfD multi}} and {{Afd-merged-from}} into {{Merged from}} Low Not started — These are now mostly duplicates with mostly similar parameters. We should turn them into a wrapper for the main template now that merge nominations can only be made at AfD. Their codebase should be similar.
Rename {{Afd-merge to}}, {{Merged-from}}, and {{Merged-to}} to a more sensible naming scheme Low Not started Merge {{Afd-merged-from}} into {{Merged from}} We already have {{Being merged from}} and we should try to keep this normal naming scheme without the dashes. In order, rename to: FaviFake
Update wording of Module:Old XfD multi and module:Copied Low In progress — Module:Old XfD multi and module:Copiedcurrently default to saying "nominated for deletion" even though the articles are actually being nominated for merging (example)
  • Make them say "nominated at AfD" instead.
  • OR, change the wording of the template based on the nomination (merge, delete, etc) and make XFDcloser itself use |merge= properly (but that would still be incorrect for redirect or draftify nominations)
  • Also, for Module:Old XfD multi, change the "merging" link to point to "Wikipedia:Merging rather than the deletion policy.
Trialpears {{Old XfD multi}}#Change default wording following PAM–AFD merge
Deprecate redundant PAM templatesMedium In progress
(blocked)
  • Updates to afd-merge templates
  • Turn merge templates into wrapper
  • {{afd-merge to}} should be renamed (moved) to {{being merged to}}
  • Old versions of templates should be archived, in oklopfer's userspace
Note that w/ and w/o to currently function differently; backlog needs clearing before this can be done. Compare:

{{merge|A|B|target=C}} & {{being merged|A|B|target=C}} vs {{merge to|A|B|target=C}} & {{being merged to|A|B|target=C}} vs {{merge from|A|B|target=C}} & {{being merged from|A|B|target=C}} Note target only works on the first set, which also does not have a direction (unless target is specified → becomes more equivalent to to); see {{being merged/testcases}}

Update /doc pages of the various Merge templates, and merge the {{PAM templates}} navbox into {{AfD templates}} Low In progress Everything else, ideally Most /doc pages are out of date or too short Update them, maybe by transcluding parts of WP:MERGE like in {{being merged from/doc}} FaviFake
Clear {{Merge portions from}} backlogLow Not started—Cleanup the pages using the template so that it can be deprecatedUndecided{{Merge}}#AfD parameter
Consider creating {{afd-merged-to}}Low Not startedUpdate {{afd-merge to}} paramsConsider creating a partner template parallel to {{merged to}} and {{afd-merged-from}}. May be decided to stick with the current {{old XfD multi}}&{{merged to}} combination instead.Undecided TfD#Merge templates
Add extra steps to XFDcloser for merges Immensely high Slowly in
progress
Twinkle AfD merge option Update and remove leftover {{Merge from}} templates after closing an AfD as "merge" Novem Linguae
XFDcloser afd-merge paramsHigh In progressUpdates to afd-merge templatesUpdate XFDcloser to use the new afd-merge params
  •  Done Turn current usage of unnamed params into named ones
  •  Done Allow usage of newly expanded parameters
  •  Not done XFDcloser closing as "merge Source to multiple targets" or vice versa
oklopfer
Allow making a bundled merge nomination using Twinkle directly Medium Ready,
not started
— Currently, Twinkle can only nominate one thing at a time. For example, if one were to nominate more than one article for merging at a time, one would have to make the first nomination and then manually tag the other pages. Twinkle should do it automatically
Update wording of SDZeroBot talk page notices Medium Not started — Currently notifies editors about deletion even if nominated for merging. Make it use all 4 cases (see {{Afd notice/testcases}} User:SD0001 SDZeroBot#Necessary update following PAM merger

Done

[edit]
Tasks related to the PAM–AfD merge (implementation discussion)
Task namePrio-rityStatusDependent on...DescriptionPlanWhoDiscussions
Add Twinkle AfD merge option High Done AfD/Dated template Add merging as option to Twinkle AfD module Novem Linguae Twinkle#Updates to AfD backend
Update instructions at AFD1 and MERGE Medium Done — Update instructions (manual and Twinkle) and streamline AFD page, and clarify the instructions for bundling merge nominations FaviFake, ScrubbedFalcon
Clear out PAM backlogMedium Done—Clear out the PAM backlogs Category:Articles proposed for merging and Category:Articles with consensus to mergeContinue as usual, slowly closing all open discussion and performing merges with consensus. Move all new PAM discussions to AfD.The latter is being done by FaviFake
Clarify if merge noms can end as delete Medium Done ? Clarify if articles nominated for merging at AfD can be deleted as a result of that discussion. If no, then update instructions on participating in and closing discussions. Decided to add clarification to all of the versions of the AfD templates ScrubbedFalcon, Chaotic Enby AFD#Can merge discussions at AfD close as Delete?
Unnamed parameters backlog High Done — Clear out Category:AfD merge templates using unnamed parameters Use regex replace with AWB/JWB oklopfer AFD#Implementing the template updates
Where should MERGEREASON go? Very low Done — Should MERGEREASON be moved elsewhere? It shouldn't. Deletion policy#Adjusting ATD-M
Deprecate unnamed parameters on afd-merge to/from and afd-merged-from High Done Unnamed parameters backlog Deprecate the old usage of unnamed parameters on the afd-merge series templates to allow repurposing for multi-targeting/sourcing oklopfer
Remove {{Merge}} options from Page Curation Medium Done — Remove the historical {{Merge}} tags from the Curation Toolbar, just like Twinkle did
Update {{afd-merge to}} and {{afd-merge from}} params High Done Unnamed parameters backlog Update the parameters to match those of {{merge to}}+{{being merged to}} and of {{merge from}}+{{being merged from}} respectively Turn current usage of unnamed params into named ones, then import usage from the old templates oklopfer AFD#Planning the template updates
Update {{afd-merged-from}} params High Done Unnamed parameters backlog Update the parameters to match those of {{afd-merge from}} to avoid breakage when the bot auto-replaces the template post-merge Turn current usage of unnamed params into named ones, then import usage from the old templates oklopfer
Option to block redirects in {{pagelist}} High Done {{pagelist}} needs to have a |noredir= parameter to maintain the usage of {{noredir}} in the afd-merge templates while also allowing for multi-page listing Module:Pagelist/sandbox updated, awaiting template editor approval and merge oklopfer Template talk:Pagelist#Edit request 4 June 2026
Add XFDcloser SOFTMERGE option Low Done None! Add the option to close a discussion as soft merge rather than merge. You should be able to just tick the "soft" check box to do a soft merge closure. Novem Linguae XFDcloser#Extra step needed on merge closes
Deal with the draft merge backlog Low Done ? We have a huge backlog of pages in the Draft: and User: namespaces. These drafts and user drafts were covered by PAM and so they were tagged. Since MfD is only for deletion and PAM doesn't exist anymore, do we just remove the tags from all of them, even if they have a talk page discussion attached to them? We should probably add some tracking categories and figure out what to do with the pages tagged. After they've all been cleaned up in some way, the templates should probably show a big error message when placed in these namespaces? (or in all namespaces except articles and drafts?) FaviFake {{Merge}}#Include draft merge proposals in the merge backlog
Decide and implement the nomenclature for failed AfD merge discussions Very low Done Should a failed merge proposal be closed as keep or not merged? If the latter, XFDcloser will have to be updated to somehow support it. "keep" Deletion process#The opposite of “merge(d)” is “not merged”
PROMERGE instructions Low Done None Clarify the instructions at PROMERGE on edit summaries to make sure that the instructions are clear for both boldmergers and merges that result from a discussion and that all necessary links are included. Being discussed at WT:Merging FaviFake, ScrubbedFalcon Wikipedia talk:Merging#Promerge edit summary instructions
Decide what to do with the {{Consider merging}} templateLow DoneNoneCreate a consider merging template similar to {{Notability}}ScrubbedFalcon
Decide whether AfD can be closed as SOFTMERGEwithout being relisted if previously kept Very low Done None If a merge was actively considered in previous AfD discussion (for example as an alternative to deletion) a soft merge closure will not usually be appropriate. Deletion process#Does soft merge apply?
Merge the PAM and AfD-merge categories Medium Done—Now that the PAM backlogs are cleared, the distinction of Category:Articles with consensus to merge following AfD discussion will no longer be necessary.Update all templates that currently add pages to the "... following AfD discussion" categories to use the Category:Articles with consensus to merge, and delete the former AfD-merge categories now that they're empty. 2 done, 1 pending TPER.
Improve display of {{multiple}} {{merge from}} templates Low Mostly
done
— Is it possible for templates to display differently when inside {{multiple}}? example with merge from and example with merging from