Wikipedia:Wikipedia Signpost/Newsroom: Difference between revisions
Ncmvocalist (talk | contribs) →Next issue: done |
→Next issue: ok, seems i'll have to do this.. |
||
Line 84: | Line 84: | ||
|Task2= In the news |
|Task2= In the news |
||
|Link2= Wikipedia:Wikipedia_Signpost/2010-09-06/In_the_news |
|Link2= Wikipedia:Wikipedia_Signpost/2010-09-06/In_the_news |
||
|Status2= |
|Status2= Done |
||
|Notes2=At the moment, this doesn't look very good. The Wikileaks story is largely redundant to [[Wikipedia:Wikipedia_Signpost/2010-08-30/In_the_news|last week's ITN]], which already had the subtitle "Wales on Wikileaks". I will try to rewrite it to make it more relevant, and also add a note about an Austrian survey. Other topics that would be good to cover: |
|Notes2=At the moment, this doesn't look very good. The Wikileaks story is largely redundant to [[Wikipedia:Wikipedia_Signpost/2010-08-30/In_the_news|last week's ITN]], which already had the subtitle "Wales on Wikileaks". I will try to rewrite it to make it more relevant, and also add a note about an Austrian survey. Other topics that would be good to cover: |
||
*[http://blog.google.org/2010/08/health-speaks-begins-pilots-in-arabic.html Google's "Health Speaks"], see also [http://hi.wikipedia.org/w/index.php?title=%E0%A4%8F%E0%A4%B8%E0%A5%8D%E0%A4%AA%E0%A4%BF%E0%A4%B0%E0%A4%BF%E0%A4%A8&diff=746489&oldid=655511] |
*[http://blog.google.org/2010/08/health-speaks-begins-pilots-in-arabic.html Google's "Health Speaks"], see also [http://hi.wikipedia.org/w/index.php?title=%E0%A4%8F%E0%A4%B8%E0%A5%8D%E0%A4%AA%E0%A4%BF%E0%A4%B0%E0%A4%BF%E0%A4%A8&diff=746489&oldid=655511] |
||
Line 153: | Line 153: | ||
|Task9= Dispatches |
|Task9= Dispatches |
||
|Link9= Wikipedia:Wikipedia_Signpost/2010-09-06/Dispatches |
|Link9= Wikipedia:Wikipedia_Signpost/2010-09-06/Dispatches |
||
|Status9= |
|Status9= In progress. |
||
|Notes9= Is it ready or isn't it? Can easily be put off again if not ready by Monday 03:00 UTC. Could there be just a ''little'' mention of featured content at the top, since that is the theme of "Dispatches"? [[User:Tony1|<font color="darkgreen">'''Tony'''</font >]] [[User talk:Tony1|<font color="darkgreen">(talk)</font >]] 01:26, 5 September 2010 (UTC) |
|Notes9= Is it ready or isn't it? Can easily be put off again if not ready by Monday 03:00 UTC. Could there be just a ''little'' mention of featured content at the top, since that is the theme of "Dispatches"? [[User:Tony1|<font color="darkgreen">'''Tony'''</font >]] [[User talk:Tony1|<font color="darkgreen">(talk)</font >]] 01:26, 5 September 2010 (UTC) |
||
:Yes, it is. Any other arguments that are being brought up are repititions of old ones at this point. There's nothing wrong with the article, it's well enough written, comprensive enough, not some big thing, and fits the scope. In other words, it's perfectly ready for publication. If it gets delayed ''again'', I swear... <span style="font-family:Verdana,Arial,Helvetica"><b><font color="#731A25">[[User:Resident Mario|Res]]</font></b><font color="#B31023">[[User_talk:Resident_Mario#top|Mar]]</font></span> 15:52, 5 September 2010 (UTC) |
:Yes, it is. Any other arguments that are being brought up are repititions of old ones at this point. There's nothing wrong with the article, it's well enough written, comprensive enough, not some big thing, and fits the scope. In other words, it's perfectly ready for publication. If it gets delayed ''again'', I swear... <span style="font-family:Verdana,Arial,Helvetica"><b><font color="#731A25">[[User:Resident Mario|Res]]</font></b><font color="#B31023">[[User_talk:Resident_Mario#top|Mar]]</font></span> 15:52, 5 September 2010 (UTC) |
||
::The split seems to have resolved some remaining concerns. Note: Most of the recent discussion took place on the story's talk page. Unfortunately, ResMar hasn't replied (despite being active) to my question on the talk page there, which represents my main concern at this point: To organize the series into topics, such that similar tools are in the same issue. I'll try to fix this issue myself now, and then publish. Regards, [[User:HaeB|HaeB]] ([[User talk:HaeB|talk]]) 20:11, 6 September 2010 (UTC) |
|||
|Task10= Book review |
|Task10= Book review |
||
|Link10= Wikipedia:Wikipedia_Signpost/2010-09-06/Book_review |
|Link10= Wikipedia:Wikipedia_Signpost/2010-09-06/Book_review |
Revision as of 20:11, 6 September 2010
Suggestions | Review desk | Opinion desk | Interviews desk |
Notices
- Everyone interested in Signpost matters is invited to join the IRC channel #wikisignpost.(webchat)
- I'm working on a "Quotation workshop" tutorial-like page for content writers generally. I will use some examples from The Signpost, which needs to manage quotations intensively. At this stage, could I quote here something I'll use on that page; it's a fragment from the "Ten rules for writing" by Elmore Leonard, American crime fiction writer, on which he was interviewed last year on ABC Radio National:
"Never use a verb other than 'said' to carry dialogue'. Not 'stated', not 'declared', not 'exclaimed' ".
PS, on exclamation points, you might be amused to hear his view: "I say you're allowed three per 100,000 words". :-) Tony (talk) 05:18, 23 August 2010 (UTC)
- I have created a template for use on Signpsot articles when they are undergoing a major edit. Please note the parameters:
{{Wikipedia:Wikipedia Signpost/Inuse|user=[[User:Example|Example]]}}
. Regards, Rock drum Ba-dumCrash (Driving well?) 13:28, 24 August 2010 (UTC)
- Fundraising campaign: grassrootsish approach; please report. ℳono 01:43, 3 September 2010 (UTC)
- Please explain :) ResMar 02:40, 3 September 2010 (UTC)
- Well, it's in now. ResMar 03:02, 4 September 2010 (UTC)
- Suggestion for more neatly formatting references to previous stories on The Signpost: instead of the clunky "participants were prevented from further discussing their case on the case pages (see Signpost coverage)", perhaps a standard form of "and participants were prevented from further discussing their case on the case pages (previous story)? There are also instances of "previous", whereas I think that is the natural default. It may be appropriate to mark a link to a story in the current edition as such ("see story in current Signpost"). Tony (talk) 01:34, 5 September 2010 (UTC)
- The traditional "see earlier Signpost coverage" way of doing it is better than the "see previous story" suggestion; I don't see the former as clunky at all. Ncmvocalist (talk) 09:45, 5 September 2010 (UTC)
- Sorry to be brutal, but HaeB, before you went to bed was the time to say "no" to everything that isn't finished. We have a copyedit sign now on WikiProject report ... that should go in next week's edition if it wasn't ready by the deadline. It is just unfair to allow the whole thing to be held up again by one or two late sections. Can we get into the rhythm of doing everything one or two days earlier, especially allocating the stories in ITN and NAN? I'd prefer to see a less voluminous Signpost, and I think the readers would, too. So why are we waiting, to pump up the size again? Tony (talk) 08:05, 6 September 2010 (UTC)
- Are you seriously suggesting that just to teach Mabeenot a lesson, I should run the first Signpost in ages without a WikiProject report? I think that realizing being the last regular section to finish should be enough, at least for now. To quote yourself from a few days ago: "No one minds if the publication comes out a few hours, or even 12 hours late, but not 24 hours late". And I'd like to remark that I was doing (and have to do) other things besides sleeping and Signpost, and need to process feedback that comes in late, too. Regards, HaeB (talk) 10:42, 6 September 2010 (UTC)
- No, and you're right, it was harsh. I guess I'm just deeply frustrated that the deadline can't be met. I'm sorry, Mabeenot. Tony (talk) 10:57, 6 September 2010 (UTC)
- Sorry to be brutal, but HaeB, before you went to bed was the time to say "no" to everything that isn't finished. We have a copyedit sign now on WikiProject report ... that should go in next week's edition if it wasn't ready by the deadline. It is just unfair to allow the whole thing to be held up again by one or two late sections. Can we get into the rhythm of doing everything one or two days earlier, especially allocating the stories in ITN and NAN? I'd prefer to see a less voluminous Signpost, and I think the readers would, too. So why are we waiting, to pump up the size again? Tony (talk) 08:05, 6 September 2010 (UTC)
- The traditional "see earlier Signpost coverage" way of doing it is better than the "see previous story" suggestion; I don't see the former as clunky at all. Ncmvocalist (talk) 09:45, 5 September 2010 (UTC)
- Suggestion for more neatly formatting references to previous stories on The Signpost: instead of the clunky "participants were prevented from further discussing their case on the case pages (see Signpost coverage)", perhaps a standard form of "and participants were prevented from further discussing their case on the case pages (previous story)? There are also instances of "previous", whereas I think that is the natural default. It may be appropriate to mark a link to a story in the current edition as such ("see story in current Signpost"). Tony (talk) 01:34, 5 September 2010 (UTC)
Tony's suggestion: Standard weekly schedule
- Tuesday–Thursday: start. Start all pages that are to be included in the next edition. NAN and INN stories/links listed below.
- Saturday–Sunday: mature versions. Aim to have reasonably mature drafts of all pages for comments by the Managing Editor, fellow journalists, and other interested users. Signpost editors recommend any structural changes, reductions in length, expansions in scope, necessary coordination between pages, postponement to subsequent issue. Copy-editors go through the drafts.
- Late Sunday – early Monday: trouble-shooting. Fresh stories added to INN and NAN by the "Next issue deadline" (only if sufficiently topical and important).
- Monday: last minute tweaks & copyedits; publication.
Next issueOnce all tasks are complete, the editor-in-chief (or nominated deputy) should complete the publication process. |
It's coming togethor. ResMar 15:40, 3 September 2010 (UTC)
|
At the moment, this doesn't look very good. The Wikileaks story is largely redundant to last week's ITN, which already had the subtitle "Wales on Wikileaks". I will try to rewrite it to make it more relevant, and also add a note about an Austrian survey. Other topics that would be good to cover:
I don't think the Windows 7 phone blog post is a very relevant news item. Regards, HaeB (talk) 01:58, 5 September 2010 (UTC)
3 News stories that might be of interest for "in the news" section, [4] [5] [6], I am not sure if they have been previously covered or if they are notable enough. Someone mind taking a look?--Theo10011 (talk) 04:43, 5 September 2010 (UTC)
|
When will this be completed? We want to publish much earlier than last week. Regards, HaeB (talk) 01:20, 6 September 2010 (UTC)
|
|
|
At last. Ncmvocalist (talk) 09:45, 5 September 2010 (UTC) I feel the same way. When our readership expands gradually with the new interwiki subscription facility, it will all seem undeniably worth it. I want a weekly readership of 3,000. Tony (talk) 12:49, 5 September 2010 (UTC) [9] [10][11] What is the ArbCom directive in question, and how is it a concern here? Please try to resolve this as quickly as possible. Regards, HaeB (talk) 14:41, 6 September 2010 (UTC)
|
|
Is it ready or isn't it? Can easily be put off again if not ready by Monday 03:00 UTC. Could there be just a little mention of featured content at the top, since that is the theme of "Dispatches"? Tony (talk) 01:26, 5 September 2010 (UTC)
|
Following last week's feedback, I have added more structure to enhance readability, as suggested by Ragesoss. Despite adding some things like section headings and an image caption, it is now slightly shorter (ca. 2330 instead of 2370 words) - for comparison: This (IMHO very good) review last year had around 2250 words, and the professional review of Shirky's book I cite (from the Boston Review) has almost 3300 words, but the Signpost review guidelines currently suggest "While there is no set length, between 600 and 1200 words is a rule of thumb." Ragesoss thought the level of detail in last week's version was appropriate, and I can offer some justification - the book review is enriched with some stuff that might otherwise be in ITN or N&N, about Shirky's presentation to Wikipedians last week (which was based on the book but introduced some new aspects), and Sue Gardner citing him in an interview this week. And I think it is a book that is highly relevant for Signpost readers; Shirky's ideas seem to be informing the strategic thinking at the Foundation to some extent, which was another reason for me to emphasize a Wikipedian/Wikimedian angle more than a normal Signpost review might already do. Still, I'd like to hear if there continue to be readability concerns about the new version. Last week, starting with John Broughton, several people suggested to split the review into two parts. Although I would like to avoid that for reasons of flow and coherence, it is conceivable to run what is now the "Motivating and cultivating collaboration" section one week later. One could perhaps frame that as the first part being more about the book itself and the author, and how it illuminates Wikipedia's role in society, and the second part being a summary of Shirky's presentation of numerous research results that shed light on why Wikipedia works. It will still a bit messy to separate it like this, though, and I would prefer to run it in one piece. Thoughts? Regards, HaeB (talk) 03:21, 5 September 2010 (UTC)
|
Regular responsibilities
Signpost journalists can claim responsibility for regular features, and continue writing their beat for as long as they wish. If you would like to be a regular writer for The Signpost, add your name to the appropriate task. If you'd be willing to cover a story that is usually covered by another editor, or are willing to cover it sporadically when the normal writer can't, add your name to the Backup list so you can be contacted when the need arises – the more the merrier. If a beat is not assigned to anyone and no draft for the next issue is listed above, anyone should feel free to write it that week.