Knowledge

:Knowledge Signpost/2009-03-30/Discussion report - Knowledge

Source 📝

516: 109: 99: 33: 119: 79: 477:), only the first proposal (the "Scrabble tile" logo) has been implemented at all. The English Wiktionary, along with some of the other language projects, has retained the original logo. Several users have expressed reservations about that logo, since it poses significant translation and standardization issues. The "Scrabble tile" logo has been adopted by a number of Wiktionary projects, including 129: 89: 317:, most AfDs on such articles are closed with a "keep" result, since they are about populated places. Many users have expressed reservations on the talk page that the proposal would cause many articles on places from small towns in rural England to large cities in Africa to be deleted, due to a lack of secondary sources. Consensus is currently against making this a guideline. 335:
account. Opponents to the proposal have stated that there is no way to determine if a username is actually random, or if it means something to the person who registered it. Supporters have said that disallowing random usernames would reduce confusion (resulting from dealing with two users named "klfasdj" and "klfsadj", for example) and vandalism from one-off accounts.
234:, the process' main proponent, "MRfD is a process that is concerned primarily with content, not subjects, and it seeks to preserve valuable content in a way that improves the quality and depth of Knowledge." MRfD aims to centralize merge discussions so that they can receive wider community input. Opponents have noted that 334:
has suggested that user names consisting of random strings of characters should be blocked on sight. The ensuing discussion centered around the question of how random a name must be to be blocked, the potential loss of good contributors, and the probability that a random account is a throwaway vandal
256:
led to the deprecation of date linking, but several editors later expressed concerns that it did not reflect wider community consensus. The current poll has several options, including whether to use autoformatting, whether months/days/years should be linked (and if so, if they should only be linked
402:
as they inherently reflect a particular point of view. Some users have expressed the viewpoint that the aforementioned words can be used as "straightforward descriptive terms" in certain cases, such as if an event has been characterized in the media as a "terrorist attack". Others have stated that
283:
should be able to be granted and revoked manually (by admins). The status would still be conferred automatically at 10 edits and 4 days, but admins would be given the capability to grant it early. This would decrease certain types of vandalism while allowing certain users who need autoconfirmed
586: 284:
status early to be given it. This would require making "autoconfirmed" an explicit usergroup in MediaWiki. Most users who have commented are in favor of allowing autoconfirmed status to be removed and reinstated, while maintaining the automatic granting that is currently in place.
82: 102: 195:
moved the page back to its original title later that day. The discussion is mostly concerned with whether "speedy" has connotations of "quickly" or "instantly" deleting an article with no application of common sense, and if "summary" brings up
368:. Most users commenting in the discussion have expressed the opinion that transclusion should still be disallowed due to increased server load and the possibility of vandalism, but there are differing opinions on allowing substitution. 312:
a guideline. The proposed guideline, as it stands, would govern the inclusion criteria for small villages and hamlets. According to current practices, articles about small villages and other settlements are allowed, and according to
122: 341: 92: 132: 533: 253: 433:
should be made a guideline. Little discussion has taken place at the latter RfC, but the former is focusing on how much weight a criticism section or article can be given without violating the guidelines on
297: 230:, discussions about whether to merge article content are generally pointed at the article's talk page, where it can take months (and, in extreme cases, years) to effect a merge. According to 352:
asked for confirmation that the policy of disallowing the use of templates in signatures should continue to exist. Transcluding a template in one's signature has been prohibited since
65: 601: 184: 208:"brings up an image of a posse in the old west, hanging a suspect without any evidence of guilt." Other words to be used in place of "speedy" are currently being discussed. 565: 575: 112: 570: 503: 494: 149: 356:, but substitution has been allowed (if generally discouraged, since substitution has historically been used to circumvent the 255-character limit on signatures in 540: 550: 545: 409: 555: 148:
The following is a brief overview of new discussions taking place on the English Knowledge. For older, yet possibly active, discussions please see our
630: 462: 527: 214: 331: 323: 164: 59: 383: 268: 683: 606: 374: 257:
on first occurrence), and if the Manual of Style should provide any guidance on the matter at all. It is scheduled to run for two weeks.
244: 466: 613: 461:
was conducted to create a new logo for the Wiktionary projects. While there was a good deal of support for four of the proposals (
309: 180: 21: 658: 176: 435: 653: 648: 458: 426: 643: 365: 223: 156: 227: 470: 353: 289: 155: 474: 252:
A poll was started on March 30 regarding linking dates and the use of autoformatting for logged-in users. A
638: 515: 449: 41: 32: 17: 288: 590: 482: 235: 478: 280: 238:
already exists and is underutilized, and that an additional process may not yield better results.
192: 442: 422: 222:
It has been proposed that a separate process should be created to discuss article mergers, at
187:
that had a rough consensus to rename the speedy deletion process. Some users objected to the
425:) and some have previously survived attempts to delete them. Another RfC has been opened at 664: 417:
Editors are seeking consensus on whether or not "Criticism of..." articles are appropriate
8: 430: 357: 597: 314: 142: 349: 261: 231: 201: 172: 197: 418: 305: 188: 677: 276: 191:
renaming and suggested that further discussion should take place, and
390:. Currently, the guideline strongly discourages the use of the words 361: 269:
Proposal to allow autoconfirmation to be manually granted and revoked
403:
there are other ways to word such events that are less inflammatory.
421:
for article content. Several of these articles exist (for example,
298:
RfC on making Knowledge:Notability (populated places) a guideline
386:
to state that there are some appropriate usages of the word
360:). The current wording of the guideline was introduced by 485:. Currently, no consensus exists on any of the proposals. 165:
Proposed move of Knowledge:Criteria for speedy deletion
215:
Proposed creation of Knowledge:Mergers for discussion
611:If your comment has not appeared here, you can try 60:Discussion Reports And Miscellaneous Articulations 675: 410:RfC on the appropriateness of criticism articles 450:Refreshing and standardizing Wiktionary's logo 382:An RfC has been started on whether to reword 140: 375:RfC on changing the wording of WP:TERRORIST 614: 342:RfC on allowing templates in signatures 181:Knowledge:Criteria for summary deletion 14: 676: 177:Knowledge:Criteria for speedy deletion 684:Knowledge Signpost archives 2009-03 27: 514: 31: 28: 695: 596:These comments are automatically 324:RfC on blocking random usernames 245:Date formatting and linking poll 224:Knowledge:Mergers for discussion 127: 117: 107: 97: 87: 77: 631:putting together the next issue 607:add the page to your watchlist 13: 1: 429:in an attempt to find out if 310:Notability (populated places) 582: 18:Knowledge:Knowledge Signpost 7: 10: 700: 236:Knowledge:Proposed merges 427:Knowledge talk:Criticism 384:Knowledge:Words to avoid 157:Centralized discussions 604:. To follow comments, 519: 423:Criticism of Microsoft 183:on March 27, citing a 36: 518: 507:"Discussion report" → 228:Articles for deletion 35: 600:from this article's 308:has proposed making 290:Requests for comment 281:autoconfirmed status 204:noted that the word 566:Features and admins 499:"Discussion report" 431:Knowledge:Criticism 358:Special:Preferences 279:has suggested that 254:poll in August 2008 185:previous discussion 591:Discuss this story 576:Arbitration report 520: 193:Ryan Postlethwaite 37: 615:purging the cache 571:Technology report 561:Discussion report 366:February 18, 2009 57:Discussion report 46:Discussion report 691: 667: 629:needs your help 618: 616: 610: 589: 538: 530: 523: 506: 498: 150:previous edition 145: 131: 130: 121: 120: 111: 110: 101: 100: 91: 90: 81: 80: 48: 699: 698: 694: 693: 692: 690: 689: 688: 674: 673: 672: 671: 670: 669: 668: 663: 661: 656: 651: 646: 641: 634: 623: 622: 620: 612: 605: 594: 593: 587:+ Add a comment 585: 581: 580: 579: 541:From the editor 531: 526: 524: 521: 510: 509: 504: 501: 496: 445: 443:Sister projects 400:freedom fighter 293: 264: 198:summary justice 160: 146: 139: 138: 137: 128: 118: 108: 98: 88: 78: 72: 69: 58: 51: 49: 45: 44: 42:← Current issue 38: 26: 25: 24: 12: 11: 5: 697: 687: 686: 662: 657: 652: 647: 642: 637: 636: 635: 625: 624: 621: 595: 592: 584: 583: 578: 573: 568: 563: 558: 553: 551:News and notes 548: 546:License update 543: 537: 525: 513: 512: 511: 502: 493: 492: 491: 489: 487: 486: 454: 453: 444: 441: 440: 439: 414: 413: 405: 404: 379: 378: 370: 369: 346: 345: 337: 336: 328: 327: 319: 318: 302: 301: 292: 287: 286: 285: 273: 272: 263: 260: 259: 258: 249: 248: 240: 239: 219: 218: 210: 209: 169: 168: 159: 154: 136: 135: 125: 115: 105: 95: 85: 74: 73: 70: 64: 63: 62: 61: 56: 55: 53: 50: 47: 40: 39: 30: 29: 15: 9: 6: 4: 3: 2: 696: 685: 682: 681: 679: 666: 660: 655: 650: 645: 640: 632: 628: 617: 608: 603: 599: 588: 577: 574: 572: 569: 567: 564: 562: 559: 557: 554: 552: 549: 547: 544: 542: 539: 535: 529: 528:30 March 2009 522:In this issue 517: 508: 500: 490: 484: 480: 476: 472: 468: 464: 460: 456: 455: 452: 451: 447: 446: 437: 432: 428: 424: 420: 416: 415: 412: 411: 407: 406: 401: 397: 393: 389: 385: 381: 380: 377: 376: 372: 371: 367: 363: 359: 355: 354:February 2005 351: 348: 347: 344: 343: 339: 338: 333: 330: 329: 326: 325: 321: 320: 316: 311: 307: 304: 303: 300: 299: 295: 294: 291: 282: 278: 275: 274: 271: 270: 266: 265: 255: 251: 250: 247: 246: 242: 241: 237: 233: 229: 225: 221: 220: 217: 216: 212: 211: 207: 203: 199: 194: 190: 186: 182: 178: 174: 171: 170: 167: 166: 162: 161: 158: 153: 151: 144: 134: 126: 124: 116: 114: 106: 104: 96: 94: 86: 84: 76: 75: 67: 54: 43: 34: 23: 19: 627:The Signpost 626: 560: 534:all comments 488: 448: 436:undue weight 408: 399: 395: 391: 387: 373: 340: 322: 315:Phil Bridger 296: 267: 243: 213: 205: 163: 147: 143:Hermione1980 52: 665:Suggestions 598:transcluded 556:In the news 457:In 2006, a 350:Allstarecho 232:NickPenguin 202:Fabrictramp 173:Happy-melon 71:Share this 66:Contribute 22:2009-03-30 659:Subscribe 602:talk page 396:terrorist 392:extremist 388:terrorist 332:Shawnhath 306:OrangeDog 262:Proposals 678:Category 654:Newsroom 649:Archives 497:Previous 277:Cenarium 113:LinkedIn 93:Facebook 20:‎ | 483:Italian 206:summary 103:Twitter 479:French 175:moved 123:Reddit 83:E-mail 644:About 419:forks 398:, or 226:. At 16:< 639:Home 505:Next 481:and 459:poll 362:xeno 189:bold 133:Digg 364:on 179:to 141:By 68:— 680:: 495:← 473:, 469:, 465:, 394:, 200:. 152:. 633:. 619:. 609:. 536:) 532:( 475:4 471:3 467:2 463:1 438:.

Index

Knowledge:Knowledge Signpost
2009-03-30
The Signpost
← Current issue
Contribute
E-mail
Facebook
Twitter
LinkedIn
Reddit
Digg
Hermione1980
previous edition
Centralized discussions
Proposed move of Knowledge:Criteria for speedy deletion
Happy-melon
Knowledge:Criteria for speedy deletion
Knowledge:Criteria for summary deletion
previous discussion
bold
Ryan Postlethwaite
summary justice
Fabrictramp
Proposed creation of Knowledge:Mergers for discussion
Knowledge:Mergers for discussion
Articles for deletion
NickPenguin
Knowledge:Proposed merges
Date formatting and linking poll
poll in August 2008

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