EditingPolicies

Differences between revisions 37 and 39 (spanning 2 versions)
Revision 37 as of 2010-09-28 13:08:44
Size: 5101
Editor: user80
Comment: updated list of tasks
Revision 39 as of 2012-02-25 06:53:07
Size: 752
Editor: lyz
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
||<tablestyle="width:25%;float:right;" style="font-size: 0.90em; width:30%; background:#f0f5fa; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;border: none;-moz-border-radius-bottomleft: 15px; -moz-border-radius-topleft: 15px;-moz-border-radius-topright: 15px;-moz-border-radius-bottomright: 15px;"><<TableOfContents>>|| == Publishing Editor Checklist ==
Line 3: Line 3:
== Ubuntu Weekly Newsletter Checklist == <<Include(UbuntuWeeklyNewsletter/EditingPolicies/HowToEdit)>>
Line 5: Line 5:
||<#f0f5fa>Steps||<#f0f5fa>How to start each week||
|| 1 || [[UbuntuWeeklyNewsletter/IssueTemplate|Create New In Progress Wiki Page]] ||
|| 2 || Clear out unused sections ||
|| 3 || Add Images to the wiki ||
|| 4 || Send out reminder emails ||
|| 5 || Lo``Co Teams ||
|| 6 || Reminder Blog Post ||
|| 7 || Welcome ||
|| 8 || In this Issue ||
|| 9 || Bug Stats ||
|| 10 || Translation Stats Lucid ||
|| 11 || Ubuntu Brainstorm Top 5 this week ||
|| 12 || Top 5 Stack Exchange Questions this week ||
|| 13 || Lo``Co News ||
|| 14 || Launchpad News ||
|| 15 || Ubuntu Forums News ||
|| 16 || The Planet ||
|| 17 || In The Press ||
|| 18 || In The Blogosphere ||
|| 19 || In Other News ||
|| 20 || Monthly Team Reports ||
|| 21 || Upcoming Meetings and Events ||
|| 22 || Updates and Security ||
|| 23 || Credits ||
||<#f0f5fa>||<#f0f5fa>After 1-23 are complete ||
|| 24 || Proof Issue you and 2 others ||
|| 25 || Double Check all links to make sure they are valid ||
|| 26 || Spell Check issue ||
|| 27 || Take out wiki commented out lines ||
|| 28 || In a Text editor take out the `` marks ||
|| 29 || Save a text version as uwnissuenumerin.txt (uwn195in.txt) ||
|| 30 || Send the the -news mailing list ||
|| 31 || Once it goes out on this list sent notice to news-team ML ||
|| 32 || IRC -locoteams ||
|| 33 || IRC-news ||
|| 34 || IRC-us ||
|| 35 || IRC-marketing ||
|| 36 || Post to the Forums ||
|| 37 || Post to the Fridge ||
|| 38 || Post to the planet ||
|| 39 || Dent/Tweet/FB other Social Media announcement ||
|| 40 || Email LoCo-Contacts mailing list ||
|| 41 || Email Translators Team ||
||<#f0f5fa>||<#f0f5fa>After steps 23-41 are complete ||
|| || on https://wiki.ubuntu.com/UbuntuWeeklyNewsletter ||
|| 42 || Change Current Issue Link ||
|| 43 || Change Current Issue number ||
|| 44 || Next Issue ** ||
|| 45 || add current issue to archives ||
|| 46 || See step 1 :-) ||
== Template for posting to The Fridge ==
Line 56: Line 7:
* To see the checklist spreadsheet click [[https://spreadsheets.google.com/ccc?key=0AtKZelXU8Y2LdFFxY0RhLVdaZU9xNk5zdTZIbFEyQVE&hl=en | here]] The template for posting to to the Fridge can be found [[https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/IssueTemplate | here]]
Line 58: Line 9:
** Please do not modify [[UbuntuWeeklyNewsletter/IssueTemplate |the template]] without consulting the [[AmberGraner]].

== HOWTO for Checklist ==

For the HOW``TO Guide for each Step click [[https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/EditingPolicies/HowToEdit | here]]

=== Template for posting to The Fridge ===

The template for posting to to the Fridge can be found [[https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/TemplateForPostingUWNOnTheFridge | here]]

== Schedule ==

Schedule for Upcoming UWN Issues can be found [[UbuntuWeeklyNewsletter/Schedule | here.]]

== Section Definitions and Suggestions ==

Guidelines for each section can be found [[https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/SectionGuidelines | here.]]
Use "More Actions: View Raw" to see details for each section.
Line 88: Line 23:
 * LoCo News - weekly encouragement to loco mailing list: https://lists.ubuntu.com/mailman/listinfo/loco-contacts)  * Lo``Co News - weekly encouragement to loco mailing list: https://lists.ubuntu.com/mailman/listinfo/loco-contacts)
Line 95: Line 30:

== Creating a new development copy ==

 * Create it as soon as possible, to allow possible editing by new people
 * Use the [[UbuntuWeeklyNewsletter/IssueTemplate|Ubuntu Weekly Newsletter Template]] to start out.

== During the Week ==

 * Add content, encourge new people to add their own content
 * Pay attention to the [[UbuntuWeeklyNewsletter/Ideas|Ideas]] page
 * Write concisely (that's one of the things people like about UWN)

== Pre-Release Checklist ==

 * have all sections completed
 * run a spellcheck
 * FIX any FIXME tags
 * check all images are in place and the links are valid
 * All editors attributed at the bottom (this usually changes each week)

== Sending the email ==

It must be sent to the ubuntu-news mailing list. The email is ubuntu-news@lists.ubuntu.com. The Ubuntu Weekly Newsletter is the only item that should be sent from this list. The Newsletter will caught in the spam filter and will need a list moderator to accept it.

 * When sending, send from your @ubuntu.com address, '''send ONLY in plain text'''.
 * Send to ubuntu-news@lists.ubuntu.com

== Post Release ==

 * Fix redirect at UbuntuWeeklyNewsletter/Current
 * Change UbuntuWeeklyNews to reflect new current
 * Update [[UbuntuWeeklyNewsletter/Archive|the Archive]]
 * Send an email to LoCo and Translators list
 * Open up a forum thread with the UWN.
 * Make sure it's posted in the Fridge

Publishing Editor Checklist

Steps to Creating the Ubuntu Weekly Newsletter

1

Create next issue wiki

Create a new page for next issue and select IssueTemplate as the page template

2

Clear out unused sections

Once you have the Template created and have added the issue number and dates make sure you take the sections you know you will not be using takes the clutter of the wiki out of your way (ie: we don't add Team Reports every week, they are monthly)

3

Add Images to the wiki

add the header.png and the CCL.png image to the wiki these can be found as attachments on previous issues. I downloaded them to my computer and just attach them each week

4

Gather news articles in the Google Doc

Throughout the week, gather news articles for each section, see UbuntuWeeklyNewsletter/LinkSuggestions and view raw text of IssueTemplate for resources for other sections

5

Review articles

Review articles added and remove duplicate, inaccurate or excess articles

6

Gather Summaries

Email summary writers (shared Google Doc has addresses and form email) and ask in #ubuntu-news for summary writers

7

Copy articles to the wiki

Proof read as you go along

8

Add statistics

Calculate bugs (see inline instructions), run scripts for askubuntu, loco, security and updates

9

Make sure all links are valid

Click on them and make sure they open the page they are supposed to or use a tool like W3C Link Checker

10

Spell Check issue

Use gedit or some other text editor you are familiar as you will need a txt version of the newsletter anyway

11

Email editors to proof issue

Email editors as soon as summaries are done! (shared Google Doc has addresses and form email) This should take at least 30 mins to critically proof. Make sure the people you ask to proof it will take their time and be critical with things like grammar, spelling, etc. and the Style Guidelines

12

Credits

Make sure anyone who actively worked on the current issue is credited, remind them to add their name to the Google Doc

13

In this Issue

Gets added right before you publish bullet points of selected table of contents

14

Take out wiki commented out lines and WIP

items in the wiki that have the ## in from of. Remove the complete text not just the ## and confirm there is no CamelCase, also remove the WORK IN PROGRESS section

15

Run publish script

Once the wiki is ready to be published run uwn/publish-uwn.pl (all scripts in https://code.launchpad.net/uwn), this will create several files in uwn/issues/### which you will use for the next several steps

16

IRC-news

Use microblog.txt text to announce to #ubuntu-news that the new issue is out

17

G+/Tweet/FB (social-media) that the issue is ready

Social Media admins will take care of this

18

Post to the Forums

A Forum Moderator will do this (several are in #ubuntu-news), posting must be done in source mode not WYSIWYG mode

19

Post to the Fridge

A Fridge Editor will do this (several are in #ubuntu-news). Make sure "Planet" category is selected so it appears on the Planet.

20

Change Current Issue Link on wiki

edit the Current Issue Link to reflect the issue you just completed

21

Change Current Issue number on wiki

edit the Current Issue number to reflect the issue you just completed

22

Change /Current link on wiki

edit /Current to redirect to new current issue

23

Next Issue on wiki

edit the upcoming issue link

24

add current issue to archives on wiki

add issue just published to the archives

25

Send the the -news mailing list

The *ONLY* mail that should every be sent to the ubuntu-news list is the newsletter. Nothing else should appear on this list. Confirm the mail didn't get stuck in the queue.

26

Send the notice to ubuntu-news-team ML

Once the Full Text Version of the Newsletter is sent to the ubuntu-news ML, then you send the NOTICE ONLY to the ubuntu-news-team list. This only gets sent after the full txt version is published to the ubuntu-news ML

27

Email LoCo-Contacts mailing list

loco-contacts@lists.ubuntu.com

Template for posting to The Fridge

The template for posting to to the Fridge can be found here

Use "More Actions: View Raw" to see details for each section.

Other

Core Articles

(cannot be dropped for a release)

  • General community news
  • Security announcements
  • Upcoming meetings and events

Secondary

(can be dropped to release on time)

Trivial

  • Bug stats