Changes between Version 26 and Version 27 of TorWeeklyNews


Ignore:
Timestamp:
Jul 2, 2013, 6:14:33 PM (5 years ago)
Author:
luttigdev
Comment:

writing tips to maintain consistency between editions

Legend:

Unmodified
Added
Removed
Modified
  • TorWeeklyNews

    v26 v27  
    99Inspired by Debian Weekly News ([http://lists.debian.org/debian-news/2006/msg00011.html 2006-03-21 edition as an example]).
    1010
    11 Ideally, the newsletter should be sent on Wednesday so it can appear in the ''development'' section of Linux Weekly News (released every Thursday).
    12 See [https://lwn.net/Articles/554075/ 2012-06-12 as an example].
     11Ideally, the newsletter should be sent on Wednesday so it can appear in the ''development'' section of Linux Weekly News (released every Thursday). See [https://lwn.net/Articles/554075/ 2012-06-12 as an example].
    1312
    1413== Target audience ==
    15 
    1614 * Developers
    1715 * Relay operators
     
    2018
    2119== Roles ==
    22 
    2320'''Editor:''' Final cut on what gets sent. Responsible for publishing the newsletter. Three rotating volunteers would be good.
    2421
     
    3027
    3128== Scope ==
    32 
    3329Example of what could be read in TWN:
    3430
     
    4137 * Quotes
    4238
    43 Out of scope: anything that does not comply with the trademark policy, projects
    44 that do not use Tor (except those supported by the Tor project itself, like
    45 OONI or MAT).
     39Out of scope: anything that does not comply with the trademark policy, projects that do not use Tor (except those supported by the Tor project itself, like OONI or MAT).
    4640
    4741== Tools ==
    48 
    4942'''Creation:''' Each edition is assembled on a wiki page. A pad could also work, but wiki pages tend to work more reliabily over Tor. A wiki with an email notification system would be best so people can subscribe if they want to help with this week edition.
    5043
     
    5447
    5548== Process ==
    56 
    5749A list of who is responsible for the newsletter each week should be filled out on a wiki page.
    5850
    5951People are free to send worthy news item to the internal mailing-list if they don't feel like writing a news item.
    6052
    61 The content is written along the week on the wiki page. Deadline for new items is on Tuesday. The editor then sends a call for
    62 review. The editor for the following week starts the next week wiki page.
     53The content is written along the week on the wiki page. Deadline for new items is on Tuesday. The editor then sends a call for review. The editor for the following week starts the next week wiki page.
    6354
    6455Reviews are done on Wednesday.
     
    6960
    7061== Areas to watch ==
    71 
    7262The following list is probably not complete:
    7363
     
    8272 * [https://mailman.boum.org/listinfo/tails-dev tails-dev mailing-list]
    8373 * [https://mailman.boum.org/listinfo/tails-l10n tails-l10n mailing-list]
    84  * Twitter accounts:
    85    [https://twitter.com/torproject @torproject],
    86    [https://twitter.com/OpenObservatory @OpenObservatory],
    87    [https://twitter.com/Tails_live @Tails_live],
    88    [https://twitter.com/erinn_tor @erinn_tor],
    89    [https://twitter.com/flamsmark @flamsmark],
    90    [https://twitter.com/hellais @hellais],
    91    [https://twitter.com/ioerror @ioerror],
    92    [https://twitter.com/isislovecruft @isislovecruft],
    93    [https://twitter.com/loesing @loesing],
    94    [https://twitter.com/nickm_tor @nickm_tor],
    95    [https://twitter.com/puellavulnerata @puellavulnerata],
    96    [https://twitter.com/runasand @runasand],
    97    [https://twitter.com/sjmurdoch @sjmurdoch],
    98    [https://twitter.com/RogerDingledine @RogerDingledine]
     74 * Twitter accounts: [https://twitter.com/torproject @torproject], [https://twitter.com/OpenObservatory @OpenObservatory], [https://twitter.com/Tails_live @Tails_live], [https://twitter.com/erinn_tor @erinn_tor], [https://twitter.com/flamsmark @flamsmark], [https://twitter.com/hellais @hellais], [https://twitter.com/ioerror @ioerror], [https://twitter.com/isislovecruft @isislovecruft], [https://twitter.com/loesing @loesing], [https://twitter.com/nickm_tor @nickm_tor], [https://twitter.com/puellavulnerata @puellavulnerata], [https://twitter.com/runasand @runasand], [https://twitter.com/sjmurdoch @sjmurdoch], [https://twitter.com/RogerDingledine @RogerDingledine]
    9975 * IRC: `#tor`, `#tor-dev`, `#ooni`, `#tails`
    10076
    10177== Writing tips ==
    102 
    10378Use `https://bugs.torproject.org/9999` to reference bug 9999.
    10479
    105 Cite the online URL when referring to a specific Tor mailing list message.
     80Cite the URL when referring to a specific Tor mailing list message.
    10681
    10782Cite emails, blogs, sites, etc. that are referenced in each news item.
     
    10984Don't use the first person ("I", "We").
    11085
     86Write dates as ''Month date, year''. Example: July 3rd, 2013.
     87
     88Keep news item titles concise.
     89
    11190Only list the 4 next upcoming events.
    11291
    11392== Volunteers ==
    114 
    115  * Lunar (editor, watcher)
     93 * Lunar (editor, watcher)
    11694 * moskvax (language and technical reviewer, watcher)
    11795 * dope457 (watcher)
     
    11997 * luttigdev (language reviewer)
    12098
    121 ''Please add yourself!
     99''Please add yourself! ''