Steps to Creating the Ubuntu Weekly Newsletter


Create next issue wiki

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


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)


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


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


Review articles

Review articles added and remove duplicate, inaccurate or excess articles


Gather Summaries

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


Copy articles to the wiki

Proof read as you go along


Add statistics

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


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


Spell Check issue

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


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



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


In this Issue

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


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


Run publish script

Once the wiki is ready to be published run uwn/ (all scripts in, this will create several files in uwn/issues/### which you will use for the next several steps



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


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

Social Media admins will take care of this


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


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.


Change Current Issue Link on wiki

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


Change Current Issue number on wiki

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


Change /Current link on wiki

edit /Current to redirect to new current issue


Next Issue on wiki

edit the upcoming issue link


add current issue to archives on wiki

add issue just published to the archives


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.


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


Email LoCo-Contacts mailing list

UbuntuWeeklyNewsletter/EditingPolicies/HowToEdit (last edited 2020-02-07 02:20:46 by bashing-om)