Knowledge (XXG)

:AfD and mergers - Knowledge (XXG)

Source đź“ť

226:, you can ask the closing admin how to save material that might be used elsewhere, and the admin can advise on any further review steps that might be needed to justify that reuse. This is not an issue, however, if the merged content is not merely copied and pasted, but instead completely rewritten so that only uncopyrightable facts are transferred, not copyrightable expression. 24: 80: 205:
AfD participants should not circumvent consensus by merging or copying material to another article unilaterally, before the debate closes. Such action may cause contention, extra process steps, and additional admin work if undoing any copying is necessary.
170:, sometimes early. If there is substantial discussion of merging, the closing admin may make a recommendation in the closing rationale. Depending on its framing, this may be an evaluation of consensus or an independent opinion. 344: 106:
describes the merge process. This essay covers the intersection between these two processes: most commonly when a potentially mergeable article is nominated at AfD or when an AfD discussion closes with consensus to merge.
328: 115:
Since mergers can be implemented and reversed by ordinary editing, they are considered to be content issues, properly addressed on the articles' Talk pages. Outside input can be solicited by listing at
231: 384: 380: 369: 356: 332: 166:. Provided that its nomination is in order, an AfD with support for merging is usually allowed to run to completion. AfDs without consensus for merging may be closed 408: 211: 293: 297: 222:, offer a specific proposal, negotiate with the other participants, and wait for the discussion to be closed. Even if the debate ends with 39:
It contains the advice or opinions of one or more Knowledge (XXG) contributors. This page is not an encyclopedia article, nor is it one of
274: 90: 40: 214:
between articles that may require retaining some article history that would otherwise be deleted. If you see a debate leaning toward
99: 129: 86: 121: 300:. They believe that it is natural to consider all outcomes at once, which encourages compromise and middle ground solutions. 198: 157: 253:
Various changes have been proposed, generally falling into the broad categories of constraining or expanding AfD's scope.
153: 117: 242:
A number of users consider mergers to be a misuse of the AfD process. They may express their opposition by recommending
403: 309: 140:
Nominations lacking a rationale to delete – including those recommending merge – are generally speedy kept per
141: 125: 288:
Some users propose that merge and redirect nominations be allowed at AfD, with the expanded process renamed
182: 186: 44: 207: 54: 178: 103: 247: 32: 277:. Also, narrowing the nomination criteria would reduce the number of articles and burden on AfD. 185:}} on the appropriate pages, which tags the articles for merging via ordinary editing. The 397: 250:
at individual AfDs, or by participating in discussions regarding the process itself.
47:. Some essays represent widespread norms; others only represent minority viewpoints. 370:
WT:Articles for deletion/Archive 53#Renaming this process Articles for Discussion
261:
Some users advocate banning mergers from AfD and restricting allowed outcomes to
385:
WT:Articles for deletion/Archive 50#back to basics: a rename and that's all
132:. However, AfD discussions that are substantially merge-focused do occur. 381:
WT:Articles for deletion/Archive 49#Secondary proposal: AFDiscussion
102:(AfD) is the forum where article deletion is discussed and decided. 89:
attempts to describe actual practice and may conflict with written
79: 345:
WP:Articles for deletion/January 7th Riots, Oakland, California
74: 18: 329:
WP:Articles for deletion/Leroy Jethro Gibbs (2nd nomination)
280:
Mergers would be handled solely in their existing process.
62: 158:
WP:Guide to deletion § Recommendations and outcomes
357:WT:Articles for deletion/Archive 48#Mergers at AfD 273:(whether to keep or delete the page history) and 154:WP:Deletion process § Articles for deletion page 310:Knowledge (XXG):Merge what?#Voting merge at AfD 8: 269:. This better matches the original scope of 210:is often worthwhile but copying causes an 168:keep, discuss merge on article Talk page 41:Knowledge (XXG)'s policies or guidelines 321: 409:Knowledge (XXG) essays about deletion 100:Knowledge (XXG):Articles for deletion 7: 130:Knowledge (XXG):Requests for comment 193:Merging during deletion discussions 45:thoroughly vetted by the community 14: 230:This issue was mentioned in the 118:Knowledge (XXG):Proposed mergers 78: 22: 16:Essay on editing Knowledge (XXG) 173:When an admin closes an AfD as 1: 162:AfDs are regularly closed as 189:gadget supports these tags. 142:Knowledge (XXG):Speedy keep 425: 151: 52: 294:Categories for discussion 298:Redirects for discussion 292:to match the renames of 275:avoids instruction creep 232:Knowledge (XXG) Signpost 290:Articles for discussion 104:Knowledge (XXG):Merging 91:policies and guidelines 404:Knowledge (XXG) essays 238:Proposed modifications 228: 212:attribution dependency 203: 43:, as it has not been 124:including relevant 120:or through general 271:Votes for deletion 244:keep, then discuss 122:dispute resolution 199:Guide to deletion 97: 96: 73: 72: 416: 388: 378: 372: 366: 360: 354: 348: 342: 336: 326: 234:in August 2009. 111:Current practice 82: 75: 65: 26: 25: 19: 424: 423: 419: 418: 417: 415: 414: 413: 394: 393: 392: 391: 379: 375: 367: 363: 355: 351: 343: 339: 333:endorsed at DRV 327: 323: 318: 306: 286: 259: 240: 195: 177:, they place {{ 160: 150: 138: 136:AfD nominations 113: 69: 68: 61: 57: 49: 48: 23: 17: 12: 11: 5: 422: 420: 412: 411: 406: 396: 395: 390: 389: 373: 361: 349: 337: 320: 319: 317: 314: 313: 312: 305: 302: 285: 282: 258: 255: 239: 236: 194: 191: 149: 146: 137: 134: 112: 109: 95: 94: 83: 71: 70: 67: 66: 58: 53: 50: 38: 37: 29: 27: 15: 13: 10: 9: 6: 4: 3: 2: 421: 410: 407: 405: 402: 401: 399: 386: 382: 377: 374: 371: 365: 362: 358: 353: 350: 346: 341: 338: 334: 330: 325: 322: 315: 311: 308: 307: 303: 301: 299: 295: 291: 283: 281: 278: 276: 272: 268: 264: 256: 254: 251: 249: 245: 237: 235: 233: 227: 225: 221: 217: 213: 209: 202: 201:recommends: 200: 192: 190: 188: 184: 183:afd-mergefrom 180: 176: 171: 169: 165: 159: 155: 147: 145: 143: 135: 133: 131: 127: 123: 119: 110: 108: 105: 101: 92: 88: 84: 81: 77: 76: 64: 60: 59: 56: 51: 46: 42: 36: 34: 28: 21: 20: 376: 364: 352: 340: 324: 289: 287: 279: 270: 266: 262: 260: 252: 243: 241: 229: 223: 219: 218:rather than 215: 208:Preservation 204: 196: 174: 172: 167: 163: 161: 148:AfD outcomes 144:, clause 1. 139: 126:WikiProjects 114: 98: 30: 179:afd-mergeto 63:WP:AFDMERGE 31:This is an 398:Categories 368:Rejected, 316:References 246:or citing 152:See also: 257:Constrain 248:WP:BEFORE 187:XFDcloser 181:}} and {{ 304:See also 55:Shortcut 284:Expand 267:delete 224:Delete 216:Delete 156:, and 220:Merge 175:merge 164:merge 87:essay 85:This 33:essay 296:and 263:keep 197:The 128:and 265:or 400:: 383:, 331:, 387:. 359:. 347:. 335:. 93:. 35:.

Index

essay
Knowledge (XXG)'s policies or guidelines
thoroughly vetted by the community
Shortcut
WP:AFDMERGE

essay
policies and guidelines
Knowledge (XXG):Articles for deletion
Knowledge (XXG):Merging
Knowledge (XXG):Proposed mergers
dispute resolution
WikiProjects
Knowledge (XXG):Requests for comment
Knowledge (XXG):Speedy keep
WP:Deletion process § Articles for deletion page
WP:Guide to deletion § Recommendations and outcomes
afd-mergeto
afd-mergefrom
XFDcloser
Guide to deletion
Preservation
attribution dependency
Knowledge (XXG) Signpost
WP:BEFORE
avoids instruction creep
Categories for discussion
Redirects for discussion
Knowledge (XXG):Merge what?#Voting merge at AfD
WP:Articles for deletion/Leroy Jethro Gibbs (2nd nomination)

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

↑