Knowledge (XXG)

:Knowledge (XXG) Signpost/Newsroom/Coordination - Knowledge (XXG)

Source 📝

72: 40: 338:
All regular features are started by their assigned writers in the Newsroom by clicking the "Start Article" button. Following that, the piece is developed until the writer marks it "Ready for copyedit" on the main Newsroom page, after which a Copyeditor will copyedit the piece. An Editor will then
330:
project. All features are brought together in the main table, with links to the "Next Issue" pages, links to content guidance and resource pages and all relevant discussions. The general discussion of the Newsroom also takes place here, in order to have everything related to the next issue of the
374:
page. Section editors browse through the page for each edition and decide whether a suggestion will be included. Note: A suggestion does not need to have any written text, but can also just consist of a link to the relevant information. Suggestions will be developed by the relevant regular team
506:
While editor-in-chief is a volunteer role like any other, its centralized responsibilities mean that (unusually for wikis) it can become a serious bottleneck that may even endanger the continuation of the entire publication. There is thus an expectation that the editor(s)-in-chief should
450:: They seek new writers for irregular features and replacement writers for regular ones. They also ask users involved in discussions if they want to write an Op-Ed, leaders of WikiProjects if they want their project featured, and solicit other users on other matters. 547:
Editor(s)-in-chief who have stepped down from overall responsibility but who maintain a presence at the project are given this title. Editor(s) Emeritus do not have any formal responsibilities, but help out with the general process of producing the
444:: They check the content of upcoming articles to make sure they're not saying anything insane. If there are dedicated copyeditors, copyediting can be left to them; otherwise, the regular editors will have to take over that as well. 257: 485:. Ultimate responsibility for the project rests squarely on the shoulders of the editor(s)-in-chief, but though they coordinate the overall project (and are, usually, the lead editors of at least one of the 406:
and their responsibility is to provide content for publication. Their contributions can be regular or irregular, or even one-time user submissions. Sometimes, writers also maintain another position in the
184: 528:: After an extended period of unresponsiveness to Signpost-related questions and lack of any Signpost-related public activity, the rest of the Signpost team may look to appoint a new editor-in-chief. 434:
by regular and irregular writers and turning them into a publishable next issue. All members of the editorial board are editors, but the News and Features editors take most of the responsibility.
283: 250: 172: 789: 563:
publication is a complex and multi-step semi-automated procedure; preparing to publish and then actually publishing each issue are the primary responsibilities of the publication manager.
829: 371: 359: 352: 243: 165: 153: 148: 521:
to questions about information that's essential for others on the Signpost team to continue work on the Signpost and is only available to the EiC(s), within a reasonable timeframe
177: 740: 602: 571: 802:
is a non-editing role account, created to allow using the "Email this user" function in order to contact the Editor(s) in Chief. As of mid-2022, its email address was
293: 203: 193: 136: 857: 198: 117: 852: 847: 323: 129: 109: 48: 21: 842: 104: 885: 736: 379: 84: 355:, where team members will provide feedback and criticism. Once an editor has given their OK, the piece can be added to the main Newsroom page. 482: 391: 534:: Making sure that access to any official Signpost-branded accounts or services (e.g. the official Twitter account and Facebook page, cf. 411:. All writer content is subject to editorial oversight before publication, including those written by members of the editorial board. 462:: They approve each article for publication. Normally, News and Features editors do this for their own articles, but this can change. 837: 78: 71: 39: 17: 601:
Upon publication of a new Signpost issue, outreach managers announce it in various external channels (see also instructions at
492:
s regular columns), they cannot handle all tasks alone and depend on the assistance of the project's many other contributors.
27: 422:
are not full-time editors, but are rather responsible for correcting spelling, grammar, and other minor changes.
863: 716: 686: 231: 766: 732: 799: 816: 746:
This posting should (after approval by that list's moderators) automatically forward to the
91: 770: 670: 628: 456:: They ensure the regular writers fulfill their duties. This includes reminding yourself. 430:
Editors are responsible for taking the articles, drafts, and suggestions provided to the
879: 762: 693: 666: 620: 712: 751: 468:: They clean up the Newsroom, Submissions, and Suggestions pages after each issue. 221: 217: 803: 747: 701: 812: 419: 793: 705: 697: 662: 658: 632: 624: 477:
The editor(s)-in-chief has or have responsibility for executing the overall
603:
Knowledge (XXG):Wikipedia_Signpost/Newsroom/Resources#Manual_off-wiki_tasks
538:) remains shared so that it won't be lost in case of unexpected departures. 682: 514:
before going on a longer wikibreak, or when leaving the EiC post entirely
657:
As of December 2022, people with access to the Mastodon handle include
644: 613: 347:
Irregular features and those not written by regular members of the
808: 754:). In that case it might be worth posting to Wikimedia-l directly. 619:
As of June 2022, people with access to the Twitter handle include
583:
Outreach managers assist the editor(s)-in-chief with managing the
692:
As of November 2022, the people with access to the page are
70: 38: 28:
Knowledge (XXG):Knowledge (XXG) Signpost/Newsroom/Publishing
785: 711:
Separately, it may also be worth posting in the popular
815:(used experimentally in 2016/2017, credentials held by 651: 390:
For the current occupants of these positions, see the
378:
General feedback and ideas should be directed to the
502:
give(s) the final okay for publication of the issue.
358:First-time writers should first read through the 715:, which has to be done from a personal account ( 278:team works together to produce the publication. 574:after the final okay from the editor-in-chief. 750:list as well. However, this sometimes fails ( 251: 8: 685:automatically mirrors the Twitter feed (via 598:s official email and social media accounts. 343:Irregular features on the Submissions desk 258: 244: 66: 727:: Send an announcement from the official 566:For each issue, the publication manager: 402:Writers are those who actually write the 495:For each issue, the editor(s)-in-chief: 18:Knowledge (XXG):Knowledge (XXG) Signpost 757:As of 2022, people with access to the 69: 526:replacement after prolonged inactivity 499:Assume(s) normal editorial duties; and 792:to provide short URLs, maintained by 535: 370:Article tips may be submitted at the 7: 780:Other outreach-related credentials: 591:reader surveys, and maintaining the 587:tip lines, handling the occasional 351:team should first be posted to the 739:), using the pre-generated output 274:These guidelines describe how the 35: 886:Knowledge (XXG) Signpost newsroom 612:: Send one or more tweets from 318:Regular features in the Newsroom 643:: Send one or more posts from 339:mark it ready for publication. 713:"Knowledge (XXG) Weekly" group 1: 437:For each issue, the editors: 683:the Signpost's Facebook page 654:on Mastodon (without images) 335:visible at a single glance. 650:As of May 2023, tweets are 481:mission as outlined in our 902: 652:automatically cross-posted 524:Accept the possibility of 326:is the central hub of the 65: 386:Who makes things happen? 307:how we go about doing it 681:: As of November 2022, 532:Keep credentials shared 313:Where do things happen? 303:coordination guidelines 271:Who does what and where 761:Gmail account include 75: 43: 731:Gmail account to the 74: 42: 819:as of February 2022) 696:(as administrator), 483:statement of purpose 733:WikimediaAnnounce-l 556:Publication Manager 173:Content + resources 572:publication script 380:Signpost talk page 284:content guidelines 76: 44: 874: 873: 800:User:The Signpost 759:wikipediasignpost 729:wikipediasignpost 366:Tips and feedback 268: 267: 207: 188: 140: 26:(Redirected from 893: 866: 597: 579:Outreach Manager 491: 360:Quick Start page 353:Submissions desk 294:style guidelines 260: 253: 246: 215:Recent changes: 201: 182: 134: 94: 67: 63: 62: 58: 31: 901: 900: 896: 895: 894: 892: 891: 890: 876: 875: 870: 869: 868: 867: 862: 860: 855: 850: 845: 840: 833: 790:created in 2022 778: 687:an IFTTT applet 595: 581: 558: 545: 543:Editor Emeritus 489: 475: 473:Editor-in-Chief 428: 417: 400: 388: 368: 345: 320: 315: 299:how we write it 264: 114: 90: 61: 59: 55: 54: 51: 45: 33: 32: 25: 24: 12: 11: 5: 899: 897: 889: 888: 878: 877: 872: 871: 861: 856: 851: 846: 841: 836: 835: 834: 823: 822: 821: 820: 806: 797: 777: 776: 775: 774: 767:Chris troutman 755: 722: 721: 720: 709: 676: 675: 674: 655: 638: 637: 636: 580: 577: 576: 575: 570:initiates the 557: 554: 544: 541: 540: 539: 529: 522: 515: 504: 503: 500: 474: 471: 470: 469: 463: 457: 451: 445: 427: 424: 416: 413: 399: 396: 387: 384: 367: 364: 344: 341: 319: 316: 314: 311: 272: 269: 266: 265: 263: 262: 255: 248: 240: 237: 236: 235: 234: 228: 225: 224: 216: 214: 211: 210: 209: 208: 196: 191: 190: 189: 175: 170: 162: 159: 158: 157: 156: 151: 146: 141: 126: 123: 122: 121: 120: 113: 112: 107: 101: 100: 97: 96: 82: 60: 57: 52: 47: 46: 37: 36: 34: 15: 14: 13: 10: 9: 6: 4: 3: 2: 898: 887: 884: 883: 881: 865: 859: 854: 849: 844: 839: 831: 827: 818: 814: 810: 807: 804: 801: 798: 795: 791: 787: 786:signpost.news 783: 782: 781: 772: 768: 764: 760: 756: 753: 749: 745: 744: 742: 738: 734: 730: 726: 723: 718: 714: 710: 707: 703: 699: 695: 691: 690: 688: 684: 680: 677: 672: 668: 664: 660: 656: 653: 649: 648: 646: 642: 639: 634: 630: 626: 622: 618: 617: 615: 614:@wikisignpost 611: 608: 607: 606: 604: 599: 594: 590: 586: 578: 573: 569: 568: 567: 564: 562: 555: 553: 551: 542: 537: 536:documentation 533: 530: 527: 523: 520: 516: 513: 510: 509: 508: 501: 498: 497: 496: 493: 488: 484: 480: 472: 467: 464: 461: 458: 455: 452: 449: 446: 443: 440: 439: 438: 435: 433: 425: 423: 421: 414: 412: 410: 405: 397: 395: 393: 385: 383: 381: 376: 373: 365: 363: 361: 356: 354: 350: 342: 340: 336: 334: 329: 325: 317: 312: 310: 308: 304: 300: 296: 295: 290: 289:what we write 286: 285: 279: 277: 270: 261: 256: 254: 249: 247: 242: 241: 239: 238: 233: 230: 229: 227: 226: 223: 219: 213: 212: 205: 200: 197: 195: 192: 186: 181: 180: 179: 176: 174: 171: 169: 168: 164: 163: 161: 160: 155: 152: 150: 147: 145: 142: 138: 133: 132: 128: 127: 125: 124: 119: 116: 115: 111: 108: 106: 103: 102: 99: 98: 93: 89: 86: 81: 80: 73: 68: 64: 53:WP:POST/COORD 50: 41: 29: 23: 19: 825: 809:The Signpost 779: 758: 752:phab:T115300 728: 725:Mailing list 724: 678: 640: 609: 600: 592: 588: 584: 582: 565: 560: 559: 549: 546: 531: 525: 518: 511: 505: 494: 486: 478: 476: 465: 459: 453: 447: 441: 436: 431: 429: 418: 408: 403: 401: 389: 377: 369: 357: 348: 346: 337: 332: 327: 321: 306: 302: 301:, and these 298: 292: 288: 282: 280: 275: 273: 166: 144:Coordination 143: 130: 87: 79:The Signpost 77: 56:Coordination 864:Suggestions 817:Peteforsyth 788:domain was 748:Wikimedia-l 512:Give notice 420:Copyeditors 415:Copyeditors 372:Suggestions 232:Newsletters 154:Suggestions 149:Submissions 828:. You can 824:It's your 813:Medium.com 771:EpicPupper 671:EpicPupper 629:EpicPupper 519:responsive 392:About page 185:cheatsheet 178:Formatting 49:← Newsroom 858:Subscribe 199:Technical 118:Subscribe 880:Category 853:Newsroom 848:Archives 826:Signpost 763:The ed17 694:The ed17 679:Facebook 667:The ed17 641:Mastodon 621:The ed17 593:Signpost 589:Signpost 585:Signpost 561:Signpost 550:Signpost 487:Signpost 479:Signpost 432:Signpost 409:Signpost 404:Signpost 375:member. 349:Signpost 333:Signpost 328:Signpost 324:Newsroom 305:explain 297:explain 287:explain 276:Signpost 131:Newsroom 110:Archives 22:Newsroom 20:‎ | 830:help us 737:example 717:example 610:Twitter 460:Approve 448:Solicit 426:Editors 398:Writers 167:Writing 735:list ( 702:Evad37 466:Manage 454:Remind 291:, the 843:About 194:Style 105:About 16:< 838:Home 794:JPxG 784:The 769:and 741:here 706:JPxG 704:and 698:HaeB 669:and 663:JPxG 659:HaeB 633:JPxG 631:and 625:HaeB 442:Edit 322:The 281:The 222:talk 218:main 204:talk 137:talk 92:chat 85:talk 811:on 689:). 605:): 517:Be 882:: 765:, 743:. 719:). 700:, 665:, 661:, 647:. 627:, 623:, 616:. 552:. 394:. 382:. 362:. 309:. 220:· 832:. 805:. 796:. 773:. 708:. 673:. 645:@ 635:. 596:' 490:' 259:e 252:t 245:v 206:) 202:( 187:) 183:( 139:) 135:( 95:) 88:· 83:( 30:)

Index

Knowledge (XXG):Knowledge (XXG) Signpost
Newsroom
Knowledge (XXG):Knowledge (XXG) Signpost/Newsroom/Publishing
The Signpost
← Newsroom
The Signpost
The Signpost
talk
chat
About
Archives
Subscribe
Newsroom
talk
Coordination
Submissions
Suggestions
Writing
Content + resources
Formatting
cheatsheet
Style
Technical
talk
main
talk
Newsletters
v
t
e

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