Changes between Version 23 and Version 24 of TorWeeklyNews


Ignore:
Timestamp:
Jul 2, 2013, 6:04:24 AM (5 years ago)
Author:
luttigdev
Comment:

added writing tips, fixed errors

Legend:

Unmodified
Added
Removed
Modified
  • TorWeeklyNews

    v23 v24  
    1 ''Tor Weekly News'' would be a regular bulletin that would cover what happened in the Tor community for the past week.
     1''Tor Weekly News'' would be a regular bulletin that covers what happens in the Tor community each week.
    22
    3 '''Goals:''' Make everyone aware of what's going on around Tor. Feel/fuel the collective energy. Spread the word about where help would be worthwhile.
     3'''Goals:''' Make everyone aware of what's going on around Tor. Feel and fuel the collective energy. Spread the word about where help would be worthwhile.
    44
    5 '''Project status:''' currently gathering volunteers, ideas and blockers.
     5'''Project status:''' currently gathering volunteers, ideas, and blockers.
    66
    77'''Next steps:''' Write a [wiki:TorWeeklyNews/2013/0 first issue].
     
    1414== Target audience ==
    1515
    16 Developers, enthusiasts, relay operators, power users.
     16 * Developers
     17 * Relay operators
     18 * Enthusiasts
     19 * Power users
    1720
    1821== Roles ==
    1922
    20 '''Editors:''' Final cut on what get sent. Responsible for publishing the newsletter. Three rotating volunteers would be good.
     23'''Editor:''' Final cut on what gets sent. Responsible for publishing the newsletter. Three rotating volunteers would be good.
    2124
    22 '''Language reviewers:''' Help improve the english. At least one by newsletter.
     25'''Language reviewer:''' Help improve the english. At least one per newsletter.
    2326
    24 '''Technical reviewers:''' Help imporove technical soundness. At least one by newsletter.
     27'''Technical reviewer:''' Help improve technical soundness. At least one per newsletter.
    2528
    26 '''Watcher:''' There are many areas that need to be monitored to cover everything. We should have a list of who is watching what, trying to get the best coverage and eventually backups so that people can get vacations.
     29'''Watcher:''' There are many areas that need to be monitored to cover everything. We should have a list of who is watching what, trying to get the best coverage of Tor-related news. We should eventually have backups so that people can get vacations.
    2730
    2831== Scope ==
     
    3033Example of what could be read in TWN:
    3134
    32  * Posts on blog.torproject.org.
    33  * Release announcements: Tor, TBB, Torbirdy, Tails, Whonix, tor-ramdisk, …
    34  * Call for testing.
     35 * Posts on blog.torproject.org
     36 * Release announcements: Tor, TBB, Torbirdy, Tails, Whonix, tor-ramdisk, etc.
     37 * Call for testing
     38 * On-going project discussions on #tor-talk or #tor-dev
     39 * Important code milestones
    3540 * Meaningful blog posts by the community
    3641 * Quotes
    37  * On-going project discussions on tor-talk or tor-dev
    38  * Important code milestones
    3942
    4043Out of scope: anything that does not comply with the trademark policy, projects
     
    4649'''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.
    4750
    48 '''Release:''' Publish the first issues on tor-talk, eventually move to a dedicated mailing-list (`tor-weekly@lists.torproject.org`?) and post on `blog.torproject.org`
     51'''Release:''' Publish the first issues on tor-talk, eventually move to a dedicated mailing-list (`tor-weekly@lists.torproject.org`?) and post on `blog.torproject.org`.
    4952
    5053'''Internal communication:''' An open mailing-list could be created to coordinate the work between volunteers.
     
    5255== Process ==
    5356
    54 A planning listing who is responsible each week should be filled on a wiki page.
     57A list of who is responsible for the newsletter each week should be filled out on a wiki page.
    5558
    5659People are free to send worthy news item to the internal mailing-list if they don't feel like writing a news item.
    5760
    58 The content is written along the week on the wiki page. Deadline for new items on Tuesday. The editor then sends a call for
     61The content is written along the week on the wiki page. Deadline for new items is on Tuesday. The editor then sends a call for
    5962review. The editor for the following week starts the next week wiki page.
    6063
     
    9497   [https://twitter.com/sjmurdoch @sjmurdoch],
    9598   [https://twitter.com/RogerDingledine @RogerDingledine]
    96  * IRC : `#tor`, `#tor-dev`, `#ooni`, `#tails`
     99 * IRC: `#tor`, `#tor-dev`, `#ooni`, `#tails`
    97100
    98101== Writing tips ==
    99102
    100103Use `https://bugs.torproject.org/9999` to reference bug 9999.
     104
     105Cite the online URL when referring to a specific Tor mailing list message.
     106
     107Cite emails, blogs, sites, etc. that are referenced in each news item.
     108
     109Don't use the first person ("I", "We").
    101110
    102111Only list the 4 next upcoming events.