'''Steps to Creating the Ubuntu Weekly Newsletter'''

||1 || Create next issue wiki || Create a new page for next issue and select  [[https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/IssueTemplate|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 [[https://docs.google.com/Doc?docid=0AdKZelXU8Y2LZGNrcHRkYmhfODlkODNxNnRnZA&hl=en|the Google Doc]] || Throughout the week, gather news articles for each section, see [[UbuntuWeeklyNewsletter/LinkSuggestions]] and [[https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/IssueTemplate?action=raw|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 [[http://validator.w3.org/checklink|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 [[UbuntuWeeklyNewsletter/StyleGuidelines|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 || [[NewsTeam/Contact|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 || [[https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Current?action=edit|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 Lo``Co-Contacts mailing list || loco-contacts@lists.ubuntu.com ||