HowToEdit
|
Size: 6553
Comment: added howto steps
|
Size: 4805
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| ||1 || Create Template || Got to: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/IssueTemplate Replace the word Template with the number of the next edition of the newsletter you will be working on You will also need to make sure once it is created you go into the wiki and Add the issue number and the dates it will cover || || 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 || || 3 || Add Images to the wiki || add the newsletter image and the CCL 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 || Send out reminder emails || This are optional but helpful if you can get people from the lists to help you get the information to you || || 5 || LoCo Teams || This are optional but helpful if you can get people from the lists to help you get the information to you || || 6 || Reminder Blog Post || This are optional but helpful if you can get people from the lists to help you get the information to you || || 7 || Welcome || EIC adds this section highlights and SHORT summary of what the issue is about - Gets added right before you publish || || 8 || In this Issue || Gets added right before you publish bullet points of table of contents || || 9 || Bug Stats || http://launchpad.net/distros/ubuntu/+bugs || || 10 || Translation Stats Lucid || https://wiki.ubuntu.com/BugSquad || || 11 || Ubuntu Brainstorm Top 5 this week || https://translations.launchpad.net/ubuntu/lucid (or current release) || || 12 || LoCo News || Keep and eye on the Planet, the LoCo Directory, and other LoCo team Blogs you can add to your RSS Feeds, also the loco-contacts mailing list || || 13 || Launchpad News || http://blog.launchpad.net/ || || 14 || Ubuntu Forums News || Comes from the Forums but only used rarely || || 15 || The Planet || http://planet.ubuntu.com/ || || 16 || In The Press || Various Sources Things Ubuntu-specific are great, but general Linux goings-on are good to, to an extent.We don't need to replicate Digg & Slashdot, but certain things are of special interest. || || 17 || In The Blogosphere || Various Sources || || 18 || In Other News || Various Sources || || 19 || Monthly Team Reports || We have a script that pulls these || || 20 || Upcoming Meetings and Events || These come from The Fridge Calendar, and Classroom Calendar || || 21 || Updates and Security || We have a script that pulls these || || 22 || Credits || Make sure anyone who actively worked on the current issue is credited || || || After 1-22 are complete || || || 23 || Proof Issue you and 2 others || 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... || || 24 || Make sure all links are valid || Just click on them and make sure they open the page they are supposed to || || 25 || Spell Check issue || Use gedit or some other text editor you are familiar as you will need a txt version of the newsletter anyway || || 26 || Take out wiki commented out lines || items in the wiki that have the ## in from of. Remove the complete text not just the ## || || 27 || In a Text editor take out the `` marks || remove all the camelcase breaks `` - `` is used to make wikipage look like the rest of the text - EXAMPLE LoCo will always be a link if you do not make it look like Lo``Co in the wiki markup. || || 28 || Save a text version as uwnissuenumerin.txt (uwn195in.txt) || || || || Convert uwnissuenumerin.txt (uwn195in.txt) to uwnissuenumerout.txt (uwn195out.txt)|| we ahave a script for this as the out version is the one that gets posted to the Forums || || 29 || 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. || || 30 || 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 || || 31 || IRC -locoteams || "Notice is pasted in this Channel - The new edition of the Ubuntu Weekly Newsletter is now available here: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue195(change the Issue Number to reflect the current issue you are publishing)" || || 32 || IRC-news || "Notice is pasted in this Channel - The new edition of the Ubuntu Weekly Newsletter is now available here: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue195 (change the Issue Number to reflect the current issue you are publishing)" || || 33 || IRC-us || "Notice is pasted in this Channel - The new edition of the Ubuntu Weekly Newsletter is now available here: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue195 (change the Issue Number to reflect the current issue you are publishing)" || || 34 || IRC-marketing || "Notice is pasted in this Channel - The new edition of the Ubuntu Weekly Newsletter is now available here: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue195 (change the Issue Number to reflect the current issue you are publishing)" || || 35 || Post to the Forums || A Forum Moderator will do this/EIC is also a Forums Moderator || || 36 || Post to the Fridge || A Fridge Editor will do this/EIC is also a Fridge Editor || || 37 || Post to the planet || If your blog is syndicated to the planet. However you can also publish the newsletter to the planet by using the "planetubuntu" tag on the Fridge || || 38 || Dent/Tweet/FB (social-media) that the issue is ready || Everyone is encouraged to do this || || 39 || Email LoCo-Contacts mailing list || loco-contacts@lists.ubuntu.com || || 40 ||Email Translation Team Mailing list || ubuntu-translations-coordinators@lists.launchpad.net || || || After steps 23-37 are complete on https://wiki.ubuntu.com/UbuntuWeeklyNewsletter || || || 41 || Change Current Issue Link || edit the Current Issue Link to reflect the issue you just completed|| || 42 || Change Current Issue number || edit the Current Issue number to reflect the issue you just completed|| || 43 || Next Issue || edit the upcoming issue link || || 44 || add current issue to archives || add issue just published to the archives || |
||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 newspaper-icon41.jpg 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 || Post to Discourse || Use Fridge text to copy into a Cafe post for discourse.ubuntu.com || || 21 || Change Current Issue Link on wiki || edit the Current Issue Link to reflect the issue you just completed|| || 22 || Change Current Issue number on wiki || edit the Current Issue number to reflect the issue you just completed|| || 23 || Change /Current link on wiki || [[https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Current?action=edit|edit /Current]] to redirect to new current issue || || 24 || Next Issue on wiki || edit the upcoming issue link || || 25 || add current issue to archives on wiki || add issue just published to the archives || || 26 || 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. || || 27 || 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 || || 28 || Email Lo``Co-Contacts mailing list || loco-contacts@lists.ubuntu.com || |
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 newspaper-icon41.jpg 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 |
Post to Discourse |
Use Fridge text to copy into a Cafe post for discourse.ubuntu.com |
21 |
Change Current Issue Link on wiki |
edit the Current Issue Link to reflect the issue you just completed |
22 |
Change Current Issue number on wiki |
edit the Current Issue number to reflect the issue you just completed |
23 |
Change /Current link on wiki |
edit /Current to redirect to new current issue |
24 |
Next Issue on wiki |
edit the upcoming issue link |
25 |
add current issue to archives on wiki |
add issue just published to the archives |
26 |
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. |
27 |
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 |
28 |
Email LoCo-Contacts mailing list |
UbuntuWeeklyNewsletter/EditingPolicies/HowToEdit (last edited 2020-02-07 02:20:46 by bashing-om)