EditingPolicies

Differences between revisions 1 and 16 (spanning 15 versions)
⇤ ← Revision 1 as of 2006-08-20 09:59:55 →
Size: 523
Editor: 195
Comment:
← Revision 16 as of 2006-10-24 14:59:57 → ⇥
Size: 1901
Editor: ip72-209-68-178
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
If it is you, this week, who is about to send out the UbuntuWeeklyNewsletter, please pay attention to the following guidelines:  UbuntuWeeklyNewsletter, please pay attention to the following guidelines:
Line 3: Line 3:
 * Use the [UbuntuWeeklyNewsletter/IssueTemplate Ubuntu Weekly Newsletter Template] to start out.
 * Have the MarketingTeam proofread all that is written
 * Don't forget to credit anyone... and try not to credit people from previous issues who haven't contributed
 * When sending, send from your @ubuntu.com address, GPG sign the message, and don't forget line breaks (at 72 or 80 chars)		  * We use the [http://en.wikipedia.org/wiki/Gobby Gobby] in EdgyEft (0.4.1) to edit UWN, Gobby can be installed with ''sudo apt-get install gobby'' or the package ''gobby''. Once installed point it to ''72.209.68.178''port 6522 and password {{{ufl@ftw}}} the host has given permission to any UWN translation team to use the server as well.

 * If you are still using dapper use [http://pkern.debian.net/debian/pool/main/g/gobby/gobby_0.4.1-1_i386.deb this deb]

== 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)
 * Have the MarketingTeam proofread all that is written.

== Sending the email ==
After everybody has checked off, it must be sent to the ubuntu-news mailing list. The email is ubuntu-news@lists.ubuntu.com. The mail will be caught in the spam filter, so will need to find CoreyBurger and get him to pass it through the filter.

 * 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]
 * Update topic in #ubuntu-marketing

Creating a new development copy

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)

  • Have the MarketingTeam proofread all that is written.

Sending the email

After everybody has checked off, it must be sent to the ubuntu-news mailing list. The email is ubuntu-news@lists.ubuntu.com. The mail will be caught in the spam filter, so will need to find CoreyBurger and get him to pass it through the filter.

Post Release

  • Fix redirect at UbuntuWeeklyNewsletter/Current

  • Change UbuntuWeeklyNews to reflect new current

  • Update [:UbuntuWeeklyNewsletter/Archive:the Archive]

  • Update topic in #ubuntu-marketing