195:
714:
In my eyes, this goes contradictory to what the
Signpost is, which is exactly not the rest of Knowledge (XXG). It’s in the name; the paper (magazine?) consists of signed publications, reviewed by copy-editors, okayed by an editorial board. Journalistic quality cannot be guaranteed if we throw this out of the window. The current system with submissions by irregular contributors and suggestions for an (apparently?) existing regular team of writers coexisting in the page space, both being used, seems to contribute to this confusion; but especially currently, when we have something of a team together for the next issue, the Signpost should keep its identity while going into the future.
706:) – but it’s just way too much, both for the current skeleton crew to handle and to introduce any newbie to. For example, I only found out after writing my article and asking myself several style-related questions that there is, in fact, an extremely long page on style – but that page actually deals with Wiki formatting instead of being an actual Manual of Style. There’s also the extremely confusing transclusions, about half a dozen spaces to actually discuss an article draft or the next issue itself, a table of editors and contributors where half the positions are still not filled… the list goes on.
732:
necessary part of its production, but the mass (mess?) of tables and transclusions that goes on must be significantly rationalised and everything given a proper workflow overview so that not only the editorial team's work is somewhat better organised (especially when done by a skeleton crew trying to cover all functions), but also easier for non editorial users to submit their articles. Having stood in on this issue as temporary E-in-C, seeing all the work to be done, it beats me how it used to be produced to a weekly deadline.
710:
to spell Wiki terms etc.), while keeping the current page as
Formatting. A review of the duties and roles of the Signpost would probably also make clearer what role new people could actually take on. In my eyes, this – keeping the Signpost rolling, and getting some more wheels on – should be the main concern right now. While thoughts of 2.0 are cool’n’all, I don’t think they help too much, and maybe are even dangerous, as long as we can’t even guarantee regular publication.
113:
694:
Knowledge (XXG) as a platform often moves a little faster – especially discussions dealing with topics that need to be resolved quickly. Other discussions, sometimes on extremely important and far-reaching topics, get far too big far too quickly for anyone to stay informed by themselves; but with a monthly publication, the
Signpost can fulfil its duty as informant for exactly these discussions only partially, dependent on when they come up and how long they last.
133:
499:
93:
123:
426:
36:
143:
103:
316:
153:
731:
is naturally, a clever literary device to remind us to sign our posts, and the name should never be changed. I concur that it should be very different from the rest of
Knowledge (XXG) mainspace; the 'pesky publication, editing or other things' are what set it apart and make it a newspaper. They are a
701:
The next issue is the direction of the
Signpost itself. The problem, I think, is what Kudpung described so eloquently in the comments of last issue’s Editorial; “Trying to find out what was wrong, I stumbled through its offices and felt as if I were wandering nostalgically through a disused factory,
871:
tasks for the current skeleton team to go about it. For one thing, it needs an interactive editable spreadsheet to track the publication work - somehting that
Knowledge (XXG) markup doesn't permit. Wikitables are a challenge at the best of times. Perhaps this is a hint for MediaWiki
713:
While on the topic, I’d also like to talk about ideas that have been thrown around last month about making the
Signpost more of a collection of normal articles, without any of the pesky publication, editing or other things; in other words, to make the Signpost more like the rest of Knowledge (XXG).
709:
I’d therefore like to do a full review of the
Signpost page space and make article writing, editing, discussion and publishing possible with as few clicks as possible without losing anything. I’d also like to include a full Manual of Style (No abbreviations in titles, capitalizations in titles, how
772:
needs to do is to get a watchlist notice up for a few days when there is a new issue. Now it will be monthly any possible opposition to this should be very muted, though I doubt there will be much anyway. There are other easy on-wiki places to announce a new issue too. I'm sure
Signpost's problem
697:
Therefore, I’d like to propose that
Discussion Reports should include rolling coverage of Discussions deemed noteworthy and big enough. This could be organized either by initial publication of a Signpost article, which gets expanded as the Discussion continues, or by a Signpost writer posting a
693:
Secondly: The Signpost is now a monthly publication. That’s a good thing; with publishing being the real bottleneck, it seems logical to make it only necessary once a month instead of once a week. The content isn’t going anywhere, which can hopefully be seen in this pretty rich issue. However,
459:
Radical look & feel overhaul: integrated video, modern look and feel, easy user interaction, easy social sharing (incl. hashtag feedback), you know, more 2018 and less 1995. Re-imagining the whole thing from the start, in other words. Ideally with input from new media experts with specific
392:
has a tiny social media footprint which we could probably leverage better. We need to put our heads together to think about responses to modern social media. Just a few ideas off the top of my head listed here. These would be tiny steps on the way to an overhaul listed below. Would somebody be
243:
submitted after the last issue. The rapid grant proposal is intended to demonstrate for a short time (three months) that a funded publication manager role could help keep the publication on time and basically keep the work on its feet until we get some of the other stuff sorted out. Bri listed
698:
thread in the relevant discussion itself, which can be updated and later included in the next issue. This rolling coverage could include polls, short Op-Eds in favour / against a proposal, or even a moderated discussion. There’s obviously also Social Media.
687:
There’s a few things I have to say after publishing my first article for the Signpost in this issue. First off, thanks to the other people who spent their free time writing, copyediting, content editing, publishing, or getting someone else to do any of the
452:"Dream big" ideas have been floating around but need a place to land. Here are some of the things that have been discussed, in a grab-bag fashion. Readers are invited to further discuss how to organize and implement (especially where funding is required).
225:" was robust, and as somewhat frequent contributors, made us think of solutions, both incremental and major. Here are our cards on the table. This is intended to document a few of the incremental changes made so far, and to keep the conversation going.
578:
573:
795:. They did it for me for the March issue, but they insist it should be the subject of an RfC. Aren't we just getting perhaps tired of RfCs just now? One way would be to get 5 - 10 people to head over
598:
568:
468:
How about a "feed" of content proposals automatically formatted? That and some programming changes on the editorial side including short-term snippets and longer-term serious reporting and roll-ups.
603:
523:
593:
563:
548:
533:
79:
634:
30:
Future directions for The Signpost: How to revive and evolve The Signpost? Big blue-sky proposals and small concrete proposals from the community and from two regular Signpost contributors.
538:
516:
355:
a lightweight process more like editing any article. Would we lose brand identity doing this? Would editorial control evaporate? More discussion is required before committing to this.
897:
247:
543:
510:
55:
44:
608:
553:
268:
announced he is willing to take over as publication manager starting with next month's issue, for which we are very grateful. This apparently renders the grant proposals moot.
588:
558:
218:
583:
334:
305:
240:
236:
949:
21:
244:
himself as the fundee because it was easier and quicker than finding an organization to sponsor it and finding another individual with the required skills.
702:
hearing in my mind's eye the bustle of activity and the noise of machinery of yesteryear“. The Signpost page space is well developed and written ((kudos to
925:
920:
915:
867:, but precisely what we don't have are people that have the time (or energy) to rethink it all. It would be too much on top of their other
96:
910:
180:
Bri is a 10+ year Knowledge (XXG) contributor and acted as interim publication manager for this month's and last month's issue of The Signpost.
194:
183:
Eddie891 has been contributing to Knowledge (XXG) for over one year. They have both been involved in reviving The Signpost since June 2017.
754:
did, when it was an active podcast. For anyone interested in pursuing this, it might be worth considering integrating the two approaches.
251:
351:
A longer discussion took place related to whether we should strip away the gloss that makes it hard to publish, and make contributing to
905:
498:
49:
35:
17:
845:
I 100% support simplifying the publication model. We've painted ourselves into a corner with this complicated publication set-up.
377:
Figure out why others (OZOO, Armbrust, EpochFail, Piotrus, Milowent, Kaldari) stopped writing and if they will come back.
405:
678:
931:
881:
854:
834:
816:
782:
763:
741:
723:
682:
773:
have been as much about lack of readers as lack of writers, & more readers will generate more writers.
759:
294:
Consider allowing the Arb report to become just scripted by arbitration clerks, almost like the summaries.
330:
472:
More bot curated content as has been suggested – traffic report has been specifically mentioned here.
750:
I'm very intrigued by the idea of creating a "Signpost Show." In many ways, it sounds similar to what
719:
363:
An energized community of contributors, readers, and newsroom volunteers are what really would keep
265:
751:
250:
is buried and user contributions are inordinately hard. To trial a solution, we have put together
106:
877:
850:
830:
812:
778:
755:
737:
630:
374:
Reach out, e.g., an automated notice once a 500(?) edit milestone is hit. Increase visibility.
126:
398:
136:
804:
796:
715:
310:
Email addresses for team members at a custom domain (or a "group" email-list address like
156:
672:
408:, but I could see a video outlet becoming more of an integrated entity or even driving
943:
799:
and get a quick consensus for it in spite of the snark that was delivered last time.
170:
301:
page names from Knowledge (XXG):Wikipedia_Signpost... to Knowledge (XXG):Signpost...
873:
864:
846:
826:
808:
800:
792:
774:
733:
214:
146:
464:
Overhaul the submissions pages to make it inviting and easy as pie to contribute.
254:
to make it easier for first-time contributors. We're still working out the kinks.
367:
going. Can we do some incremental things to reinvigorate, reward, and recognize?
703:
116:
656:
Speaking personally, I'd be glad to help with the arbitration report. Thanks,
666:
658:
425:
276:
Lots of ideas worth exploring came in from the community. Here are a few:
166:
430:
488:
Ad-hoc and self-organizing editorial board based on followership.
291:
Automate tedious parts (e.g., part of F.C., traffic report, etc.)
54:
235:
Publishing is hard and requires unusual technical skills; see
248:
Knowledge (XXG):Knowledge (XXG) Signpost/Newsroom/Submissions
497:
193:
34:
325:
And/or: At a minimum, set up an RSS feed that points to
822:
646:
639:
619:
335:
Knowledge (XXG) talk:Knowledge (XXG) Signpost/Mirroring
306:
Knowledge (XXG) talk:Knowledge (XXG) Signpost/Mirroring
416:
Why is our Twitter feed not visible in the pages of
644:If your comment has not appeared here, you can try
397:? We could start just by reading headlines for the
803:might also still be in favour of it, and probably
476:User-customizable editions, filters, periodicity.
8:
480:Upvote/downvote model for TOC presentation.
329:content in its existing home. Perhaps using
424:
201:Pitching-in on a participatory publication
950:Knowledge (XXG) Signpost archives 2018-04
18:Knowledge (XXG):Knowledge (XXG) Signpost
647:
623:
264:Just before publication of this issue,
252:WP:Knowledge (XXG) Signpost/Quick Start
70:
342:Enable Visual Editor for contributions
484:Multiple curators of multiple views
29:
7:
863:I think we're all agreed on that
768:One very basic thing that Signpost
460:knowledge of Web based platforms.
239:for a solution, or Bri's followup
237:Bluerasberry's 2017 grant proposal
56:
28:
872:devs to take a look at tables.
629:These comments are automatically
347:Simplifying the publication model
314:
151:
141:
131:
121:
111:
101:
91:
371:Participation badges/chicklets.
286:Autofill submission block (duh)
280:Different publication schedule
640:add the page to your watchlist
1:
385:Moving towards social media
966:
855:23:58, 30 April 2018 (UTC)
835:14:33, 27 April 2018 (UTC)
817:14:23, 27 April 2018 (UTC)
783:11:00, 27 April 2018 (UTC)
764:04:31, 27 April 2018 (UTC)
742:12:05, 26 April 2018 (UTC)
724:08:40, 26 April 2018 (UTC)
683:05:17, 26 April 2018 (UTC)
333:. (Relevant notes also at
331:mw:Extension:FeaturedFeeds
259:Publication manager update
219:"Death knell sounding for
315:
882:01:59, 1 May 2018 (UTC)
898:looking for new talent
637:. To follow comments,
502:
400:Spoken Knowledge (XXG)
380:Becoming a User group?
198:
71:Future directions for
39:
501:
197:
38:
633:from this article's
423:Where do replies to
217:'s op-ed last issue
624:Discuss this story
579:WikiProject report
574:Arbitration report
503:
393:willing to create
322:might be helpful)
231:Immediate problems
199:
45:← Back to Contents
40:
665:
648:purging the cache
599:Technology report
569:Discussion report
438:The Signpost Show
395:The Signpost Show
272:Incremental fixes
50:View Latest Issue
957:
934:
663:
651:
649:
643:
622:
604:Featured content
524:From the editors
521:
513:
506:
428:
401:
321:
319:
318:
317:
312:en-signpost-team
283:Navigation links
212:
173:
155:
154:
145:
144:
135:
134:
125:
124:
115:
114:
105:
104:
95:
94:
62:
60:
58:
965:
964:
960:
959:
958:
956:
955:
954:
940:
939:
938:
937:
936:
935:
930:
928:
923:
918:
913:
908:
901:
890:
889:
874:Kudpung กุดผึ้ง
809:Kudpung กุดผึ้ง
734:Kudpung กุดผึ้ง
653:
645:
638:
627:
626:
620:+ Add a comment
618:
614:
613:
612:
514:
509:
507:
504:
492:
491:
450:
399:
387:
361:
349:
313:
311:
274:
233:
227:
210:
203:
202:
191:
190:
175:
174:
164:
163:
162:
161:
152:
142:
132:
122:
112:
102:
92:
86:
83:
69:
65:
63:
53:
52:
47:
41:
31:
26:
25:
24:
12:
11:
5:
963:
961:
953:
952:
942:
941:
929:
924:
919:
914:
909:
904:
903:
902:
892:
891:
888:
887:
886:
885:
884:
858:
857:
842:
841:
840:
839:
838:
837:
791:I Tried that,
786:
785:
766:
747:
746:
745:
744:
711:
707:
699:
695:
690:
689:
685:
628:
625:
617:
616:
615:
611:
606:
601:
596:
594:Traffic report
591:
586:
581:
576:
571:
566:
564:Community view
561:
556:
551:
549:Special report
546:
541:
536:
534:News and notes
531:
526:
520:
508:
496:
495:
494:
493:
490:
489:
449:
442:
441:
440:
435:
421:
412:(more below).
386:
383:
382:
381:
378:
375:
372:
360:
357:
348:
345:
344:
343:
340:
339:
338:
308:
302:
295:
292:
289:
288:
287:
284:
273:
270:
266:Chris troutman
262:
261:
232:
229:
228:
206:Feedback from
204:
200:
192:
189:
186:
177:
176:
160:
159:
149:
139:
129:
119:
109:
99:
88:
87:
84:
78:
77:
76:
75:
67:
66:
64:
61:
48:
43:
42:
33:
32:
27:
15:
14:
13:
10:
9:
6:
4:
3:
2:
962:
951:
948:
947:
945:
933:
927:
922:
917:
912:
907:
899:
895:
883:
879:
875:
870:
866:
862:
861:
860:
859:
856:
852:
848:
844:
843:
836:
832:
828:
824:
820:
819:
818:
814:
810:
806:
802:
798:
794:
790:
789:
788:
787:
784:
780:
776:
771:
767:
765:
761:
757:
753:
749:
748:
743:
739:
735:
730:
727:
726:
725:
721:
717:
712:
708:
705:
700:
696:
692:
691:
686:
684:
680:
677:
674:
671:
668:
661:
660:
655:
654:
650:
641:
636:
632:
621:
610:
607:
605:
602:
600:
597:
595:
592:
590:
587:
585:
582:
580:
577:
575:
572:
570:
567:
565:
562:
560:
557:
555:
552:
550:
547:
545:
542:
540:
537:
535:
532:
530:
527:
525:
522:
518:
512:
511:26 April 2018
505:In this issue
500:
487:
483:
479:
475:
471:
467:
463:
458:
455:
454:
453:
447:
443:
439:
436:
433:
432:
427:
422:
419:
415:
414:
413:
411:
407:
403:
396:
391:
384:
379:
376:
373:
370:
369:
368:
366:
358:
356:
354:
346:
341:
336:
332:
328:
324:
323:
320:wikimedia.org
309:
307:
303:
300:
296:
293:
290:
285:
282:
281:
279:
278:
277:
271:
269:
267:
260:
257:
256:
255:
253:
249:
245:
242:
238:
230:
226:
224:
222:
216:
213:s readers on
209:
196:
187:
185:
184:
181:
172:
168:
158:
150:
148:
140:
138:
130:
128:
120:
118:
110:
108:
100:
98:
90:
89:
81:
74:
59:
57:26 April 2018
51:
46:
37:
23:
19:
894:The Signpost
893:
868:
769:
756:OhKayeSierra
728:
675:
669:
657:
539:In the media
528:
517:all comments
485:
481:
477:
473:
469:
465:
461:
456:
451:
445:
437:
429:
418:The Signpost
417:
410:The Signpost
409:
394:
390:The Signpost
389:
388:
365:The Signpost
364:
362:
353:The Signpost
352:
350:
326:
298:
275:
263:
258:
246:
234:
221:The Signpost
220:
208:The Signpost
207:
205:
188:We heard you
182:
179:
178:
97:PDF download
73:The Signpost
72:
932:Suggestions
631:transcluded
444:Dream big:
297:Change all
241:rapid grant
147:X (Twitter)
805:Zarasophos
716:Zarasophos
402:'s channel
85:Share this
80:Contribute
22:2018-04-26
926:Subscribe
823:done that
752:WP:WEEKLY
635:talk page
359:Community
304:Consider
944:Category
921:Newsroom
916:Archives
869:Signpost
729:Signpost
544:In focus
529:Signpost
446:Signpost
327:Signpost
299:Signpost
171:Eddie891
137:Facebook
127:LinkedIn
117:Mastodon
68:Signpost
20: |
865:Kaldari
847:Kaldari
827:Johnbod
801:Lourdes
793:Johnbod
775:Johnbod
609:Gallery
554:Opinion
431:Twitter
406:YouTube
215:Kudpung
770:really
704:Evad37
688:above.
589:Humour
157:Reddit
107:E-mail
911:About
807:too.
659:Kevin
559:Op-ed
16:<
906:Home
878:talk
851:talk
831:talk
821:Ok,
813:talk
797:here
779:talk
760:talk
738:talk
720:talk
667:L235
584:Blog
169:and
896:is
664:aka
448:2.0
434:go?
404:on
167:Bri
165:By
82:—
946::
880:)
853:)
833:)
825:.
815:)
781:)
762:)
740:)
722:)
681:)
337:.)
900:.
876:(
849:(
829:(
811:(
777:(
758:(
736:(
718:(
679:c
676:·
673:t
670:·
662:(
652:.
642:.
519:)
515:(
486:·
482:·
478:·
474:·
470:·
466:·
462:·
457:·
420:?
223:?
211:'
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
