[TWN team] Recent changes to the wiki pages
Lunar
lunar at torproject.org
Tue Feb 25 19:40:31 UTC 2014
===========================================================================
==== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2014/8 ====
===========================================================================
version 43
Author: lunar
Date: 2014-02-25T18:42:06+00:00
let's not sound sketchy to arma
--- version 42
+++ version 43
@@ -12,8 +12,7 @@
========================================================================
Welcome to the eighth issue of Tor Weekly News in 2014, the weekly
-newsletter that covers what is happening in the steambathing Tor
-community.
+newsletter that covers what is happening in the Tor community.
News from the 2014 Winter Developers’ Meeting in Reykjavík
----------------------------------------------------------
version 42
Author: arma
Date: 2014-02-25T18:39:08+00:00
--
--- version 41
+++ version 42
@@ -19,7 +19,7 @@
----------------------------------------------------------
Since 2010, core Tor Project’s contributors try to meet twice a year to
-enjoy the pleasure of each others company and move projects forward
+enjoy the pleasure of each other's company and move projects forward
through face-to-face discussions and hack time. This year, close to
forty people attended the “2014 winter dev. meeting” [1] that was held
in Reykjavík, Iceland.
version 41
Author: lunar
Date: 2014-02-25T18:09:03+00:00
FREEZE
--- version 40
+++ version 41
@@ -1,6 +1,8 @@
''34th issue of Tor Weekly News. Covering what's happening from February 18th, 2014 to February 25th, 2014. To be released on February 26th, 2014.''
'''Editor:''' Lunar
+
+'''Status:''' FROZEN! New items should go to [wiki:TorWeeklyNews/2014/9 next week's edition]. Expected publication time: 2014-02-26 12:00 UTC.
'''Subject:''' Tor Weekly News — February 26th, 2014
@@ -10,7 +12,8 @@
========================================================================
Welcome to the eighth issue of Tor Weekly News in 2014, the weekly
-newsletter that covers what is happening in the XXX Tor community.
+newsletter that covers what is happening in the steambathing Tor
+community.
News from the 2014 Winter Developers’ Meeting in Reykjavík
----------------------------------------------------------
@@ -18,46 +21,45 @@
Since 2010, core Tor Project’s contributors try to meet twice a year to
enjoy the pleasure of each others company and move projects forward
through face-to-face discussions and hack time. This year, close to
-forty people attended the “2014 winter dev. meeting” [XXX] that was held in
-Reykjavík, Iceland.
+forty people attended the “2014 winter dev. meeting” [1] that was held
+in Reykjavík, Iceland.
The team had over forty discussion topics ranging from organizational
matters to highly technical design decisions. For a couple of
highlights, many sessions have been focused on discussing and producing
-roadmaps: a mid-term vision for the Tor Browser [XXX], a step-by-step
-plan for the Tor Instant Messaging Bundle [XXX], detailed ideas for new
-bridge bundles [XXX], ways to solve the research problems around guard
-nodes [XXX], and how to plan little-t tor releases [XXX].
-
-The meeting also enabled cross-team communication: pluggable
-transports developers have been able to discuss integration in the Tor
-Browser [XXX] and the lifecycle of recommended transports [XXX];
-the Tor Browser and the support teams met to see how to improve
-communications on both sides [XXX]. One outcome is a plan to remix
-existing documentation to create the Tor Browser User Manual [XXX].
+roadmaps: a mid-term vision for the Tor Browser [2], a step-by-step plan
+for the Tor Instant Messaging Bundle [3], detailed ideas for new bridge
+bundles [4], ways to solve the research problems around guard nodes [5],
+and how to plan little-t tor releases [6].
+
+The meeting also enabled cross-team communication: pluggable transports
+developers have been able to discuss integration in the Tor Browser [7]
+and the lifecycle of recommended transports [8]; the Tor Browser and the
+support teams met to see how to improve communications on both
+sides [9]. One outcome is a plan to remix existing documentation to
+create the Tor Browser User Manual [10].
The two intense days of discussions have been followed by hands-on
-sessions which have seen their fair share of hacking and write
-ups [XXX].
+sessions which have seen their fair share of hacking and write ups [11].
Some of the minutes are still missing, but there is already plenty to
read already. Now that developers had to stop contemplating northern
-lights [XXX], some discussions [XXX] are already continuing on various
+lights [12], some discussions [13] are already continuing on various
project’s mailing lists. Stay tuned!
- [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting
- [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/TorBrowserPlan
- [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/RoadmapTIMB
- [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/BridgeBundles
- [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/GuardDesign
- [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/TorReleaseProcess
- [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/PTTBB
- [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/BridgeProtocolsAndTBB
- [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/SupportAndTorBrowserTeamsMeeting
- [XXX]: https://bugs.torproject.org/10974
- [XXX]: https://trac.torproject.org/projects/tor/timeline?from=Feb+21%2C+2014&daysback=2&authors=&ticket=on&ticket_details=on&changeset=on&update=Update
- [XXX]: https://en.wikipedia.org/wiki/Aurora_%28astronomy%29
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006288.html
+ [1]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting
+ [2]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/TorBrowserPlan
+ [3]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/RoadmapTIMB
+ [4]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/BridgeBundles
+ [5]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/GuardDesign
+ [6]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/TorReleaseProcess
+ [7]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/PTTBB
+ [8]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/BridgeProtocolsAndTBB
+ [9]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/SupportAndTorBrowserTeamsMeeting
+ [10]: https://bugs.torproject.org/10974
+ [11]: https://trac.torproject.org/projects/tor/timeline?from=Feb+21%2C+2014&daysback=2&authors=&ticket=on&ticket_details=on&changeset=on&update=Update
+ [12]: https://en.wikipedia.org/wiki/Aurora_%28astronomy%29
+ [13]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006288.html
Miscellaneous news
------------------
@@ -66,95 +68,95 @@
the rewrite of Tor Weather, to be held on the OFTC #tor-dev channel on
Wednesday 26th February at 18:00 UTC. “Topics include reporting progress
made since the last meeting two weeks ago, making plans for the next
-week, and possibly turning this project into a GSoC project” [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006299.html
+week, and possibly turning this project into a GSoC project” [14].
+
+ [14]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006299.html
Nick Mathewson announced the start of a weekly Tor developer’s meeting,
to be held on the OFTC #tor-dev channel, “for working on the program
‘tor’. (This won’t cover all the other programs developed under the Tor
-umbrella.)” [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006282.html
+umbrella.)” [15].
+
+ [15]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006282.html
The Tails developers will be holding their next contributors’ meeting on
the OFTC #tails-dev channel at 9pm UTC on March 5th; “everyone
-interested in contributing to Tails is welcome.” [XXX].
-
- [XXX]: https://mailman.boum.org/pipermail/tails-dev/2014-February/004934.html
-
-Andrew Lewman submitted his monthly status report for January [XXX], and
+interested in contributing to Tails is welcome.” [16].
+
+ [16]: https://mailman.boum.org/pipermail/tails-dev/2014-February/004934.html
+
+Andrew Lewman submitted his monthly status report for January [17], and
also wrote up a report of his involvement in the recent Boston
-CryptoParty [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-February/000462.html
- [XXX]: https://lists.torproject.org/pipermail/tor-reports/2014-February/000463.html
-
-Alexander Dietrich published [XXX] a multi-instance init script for Tor
+CryptoParty [18].
+
+ [17]: https://lists.torproject.org/pipermail/tor-reports/2014-February/000462.html
+ [18]: https://lists.torproject.org/pipermail/tor-reports/2014-February/000463.html
+
+Alexander Dietrich published [19] a multi-instance init script for Tor
(“basically the current official init script and torservers.net’s
“instances” mechanism frankensteined together”, in Alexander’s words) in
-response to a recent discussion on tor-relays [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003942.html
- [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003913.html
+response to a recent discussion on tor-relays [20].
+
+ [19]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003942.html
+ [20]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003913.html
Responding to a message from someone interested in writing a DNS-based
pluggable transport, George Kadianakis suggested several ways in which
-the existing obfsproxy code could be reworked to accommodate this [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006250.html
+the existing obfsproxy code could be reworked to accommodate this [21].
+
+ [21]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006250.html
George also recommended that operators of obfs3 or ScrambleSuit bridges
install the python-gmpy package on their relays, as it can significantly
-increase the speed of some cryptographic operations [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003951.html
+increase the speed of some cryptographic operations [22].
+
+ [22]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003951.html
Jens Kubieziel wrote up the results of an attempt to determine whether
the recent transition between the TAP and NTor handshake protocols is
-connected to some users’ reports of hidden service unavailability [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006260.html
+connected to some users’ reports of hidden service unavailability [23].
+
+ [23]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006260.html
Max Jakob Maass published the preliminary results of a test in which the
RIPE Atlas measurement API was used to retrieve the SSL certificate of
torproject.org from as many countries as possible in order to detect
attempted attacks or censorship, and wondered whether it might be worth
-running such a test on a regular basis [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-February/032173.html
+running such a test on a regular basis [24].
+
+ [24]: https://lists.torproject.org/pipermail/tor-talk/2014-February/032173.html
With regard to a coming redesign of the “Volunteers” section on the Tor
Project’s website, Moritz Bartl wrote up a list of proposed volunteer
categories that was the fruit of a brainstorming session at the Tor
developers’ meeting, and asked for suggestions of “obvious” missing
sections, as well as “acceptably-licensed” graphics that could serve as
-icons for each category [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-February/032176.html
-
-Nathan Freitas wrote [XXX] from the Tor developers’ meeting with a
+icons for each category [25].
+
+ [25]: https://lists.torproject.org/pipermail/tor-talk/2014-February/032176.html
+
+Nathan Freitas wrote [26] from the Tor developers’ meeting with a
request for help in compiling “user stories” on the Tor wiki: that is,
stories of the form “a <type of Tor user> wants to <some feature of a
Tor app> in order to <some reason related to security, privacy,
-etc>” [XXX]. If you have any to add, please write them up on the
+etc>” [27]. If you have any to add, please write them up on the
dedicated wiki page!
- [XXX]: https://lists.torproject.org/pipermail/tor-talk/2014-February/032174.html
- [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/UserStories
+ [26]: https://lists.torproject.org/pipermail/tor-talk/2014-February/032174.html
+ [27]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/UserStories
Yawning Angel sent out a draft of a proposal to “extend the SOCKS5
protocol when communicating with pluggable transports to allow passing
more per-bridge meta-data to the transport and returning more meaningful
-connection failure response codes back to Tor” [XXX].
-
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006300.html
+connection failure response codes back to Tor” [28].
+
+ [28]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006300.html
Josh Ayers wrote to the Tor-ramdisk list suggesting possible ways to
ensure that sufficient entropy is available to the kernel by the time
-tor-ramdisk generates its long-term keys [XXX].
-
- [XXX]: http://opensource.dyc.edu/pipermail/tor-ramdisk/2014-February/000119.html
+tor-ramdisk generates its long-term keys [29].
+
+ [29]: http://opensource.dyc.edu/pipermail/tor-ramdisk/2014-February/000119.html
Tor help desk roundup
---------------------
@@ -166,9 +168,9 @@
connects automatically to a URL will not route its traffic through Tor
if the file is opened with an external application. An open bug ticket
for improving this warning message has more information about the
-issue [XXX].
-
- [XXX]: https://bugs.torproject.org/7439
+issue [30].
+
+ [30]: https://bugs.torproject.org/7439
Upcoming events
---------------
@@ -195,15 +197,15 @@
| http://libreplanet.org/2014/
-This issue of Tor Weekly News has been assembled by Lunar, harmony,
-and Matt Pagan.
+This issue of Tor Weekly News has been assembled by Lunar, harmony, and
+Matt Pagan.
Want to continue reading TWN? Please help us create this newsletter.
We still need more volunteers to watch the Tor community and report
-important news. Please see the project page [XXX], write down your
-name and subscribe to the team mailing list [XXX] if you want to
+important news. Please see the project page [31], write down your
+name and subscribe to the team mailing list [32] if you want to
get involved!
- [XXX]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
- [XXX]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
-}}}+ [31]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
+ [32]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
+}}}
version 40
Author: boklm
Date: 2014-02-25T17:43:31+00:00
Island -> Iceland
--- version 39
+++ version 40
@@ -19,7 +19,7 @@
enjoy the pleasure of each others company and move projects forward
through face-to-face discussions and hack time. This year, close to
forty people attended the “2014 winter dev. meeting” [XXX] that was held in
-Reykjavík, Island.
+Reykjavík, Iceland.
The team had over forty discussion topics ranging from organizational
matters to highly technical design decisions. For a couple of
version 39
Author: lunar
Date: 2014-02-25T17:41:02+00:00
both Roger and Nick Hopper will be at Financial Crypto
--- version 38
+++ version 39
@@ -180,7 +180,7 @@
| Boston, Massachusetts, USA
| https://surveillance.hackpad.com/BostonCambridge-Countersurveillance-DiscoTech-lpF9SgcyhR2
|
-Mar 3-7 | Roger @ Financial Cryptography and Data Security 2014
+Mar 3-7 | Tor @ Financial Cryptography and Data Security 2014
| Barbados
| http://fc14.ifca.ai/
|
version 38
Author: lunar
Date: 2014-02-25T17:29:55+00:00
not covered for two weeks, let's drop it
--- version 37
+++ version 38
@@ -206,8 +206,4 @@
[XXX]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
[XXX]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
-}}}
-
-Possible items:
-
- * announcement of new TBB releases https://lists.torproject.org/pipermail/tor-talk/2014-February/032116.html (hope we'll have an answer from the TBB team, otherwise it's pointless to mention it — lunar)
+}}}
version 37
Author: lunar
Date: 2014-02-25T17:28:58+00:00
typography
--- version 36
+++ version 37
@@ -15,7 +15,7 @@
News from the 2014 Winter Developers’ Meeting in Reykjavík
----------------------------------------------------------
-Since 2010, core Tor Project's contributors try to meet twice a year to
+Since 2010, core Tor Project’s contributors try to meet twice a year to
enjoy the pleasure of each others company and move projects forward
through face-to-face discussions and hack time. This year, close to
forty people attended the “2014 winter dev. meeting” [XXX] that was held in
@@ -24,16 +24,16 @@
The team had over forty discussion topics ranging from organizational
matters to highly technical design decisions. For a couple of
highlights, many sessions have been focused on discussing and producing
-roadmaps: a mid-term vision for the Tor Browser [XXX], a step-by-step
+roadmaps: a mid-term vision for the Tor Browser [XXX], a step-by-step
plan for the Tor Instant Messaging Bundle [XXX], detailed ideas for new
-bridge bundles [XXX], ways to solve the research problems around guard
-nodes [XXX], and how to plan little-t tor releases [XXX].
+bridge bundles [XXX], ways to solve the research problems around guard
+nodes [XXX], and how to plan little-t tor releases [XXX].
The meeting also enabled cross-team communication: pluggable
transports developers have been able to discuss integration in the Tor
-Browser [XXX] and the lifecycle of recommended transports [XXX];
+Browser [XXX] and the lifecycle of recommended transports [XXX];
the Tor Browser and the support teams met to see how to improve
-communications on both sides [XXX]. One outcome is a plan to remix
+communications on both sides [XXX]. One outcome is a plan to remix
existing documentation to create the Tor Browser User Manual [XXX].
The two intense days of discussions have been followed by hands-on
@@ -42,8 +42,8 @@
Some of the minutes are still missing, but there is already plenty to
read already. Now that developers had to stop contemplating northern
-lights [XXX], some discussions [XXX] are already continuing on various
-project's mailing lists. Stay tuned!
+lights [XXX], some discussions [XXX] are already continuing on various
+project’s mailing lists. Stay tuned!
[XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting
[XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/TorBrowserPlan
@@ -66,20 +66,20 @@
the rewrite of Tor Weather, to be held on the OFTC #tor-dev channel on
Wednesday 26th February at 18:00 UTC. “Topics include reporting progress
made since the last meeting two weeks ago, making plans for the next
-week, and possibly turning this project into a GSoC project” [XXX].
+week, and possibly turning this project into a GSoC project” [XXX].
[XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006299.html
Nick Mathewson announced the start of a weekly Tor developer’s meeting,
to be held on the OFTC #tor-dev channel, “for working on the program
-“tor”. (This won’t cover all the other programs developed under the Tor
+‘tor’. (This won’t cover all the other programs developed under the Tor
umbrella.)” [XXX].
[XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006282.html
The Tails developers will be holding their next contributors’ meeting on
the OFTC #tails-dev channel at 9pm UTC on March 5th; “everyone
-interested in contributing to Tails is welcome.” [XXX].
+interested in contributing to Tails is welcome.” [XXX].
[XXX]: https://mailman.boum.org/pipermail/tails-dev/2014-February/004934.html
@@ -102,11 +102,12 @@
pluggable transport, George Kadianakis suggested several ways in which
the existing obfsproxy code could be reworked to accommodate this [XXX].
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006250.html
+
George also recommended that operators of obfs3 or ScrambleSuit bridges
install the python-gmpy package on their relays, as it can significantly
increase the speed of some cryptographic operations [XXX].
- [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006250.html
[XXX]: https://lists.torproject.org/pipermail/tor-relays/2014-February/003951.html
Jens Kubieziel wrote up the results of an attempt to determine whether
@@ -199,8 +200,8 @@
Want to continue reading TWN? Please help us create this newsletter.
We still need more volunteers to watch the Tor community and report
-important news. Please see the project page [XXX], write down your
-name and subscribe to the team mailing list [XXX] if you want to
+important news. Please see the project page [XXX], write down your
+name and subscribe to the team mailing list [XXX] if you want to
get involved!
[XXX]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
version 36
Author: lunar
Date: 2014-02-25T17:26:27+00:00
update events
--- version 35
+++ version 36
@@ -175,11 +175,23 @@
Feb 26 18:00 | Tor Weather development meeting
| #tor-dev, oftc.net
|
-Mar 04 20:00 | Weekly tor development meeting
+Mar 1 10:00 | Andrew @ Boston/Cambridge Countersurveillance DiscoTech
+ | Boston, Massachusetts, USA
+ | https://surveillance.hackpad.com/BostonCambridge-Countersurveillance-DiscoTech-lpF9SgcyhR2
+ |
+Mar 3-7 | Roger @ Financial Cryptography and Data Security 2014
+ | Barbados
+ | http://fc14.ifca.ai/
+ |
+Mar 4 20:00 | Weekly tor development meeting
| #tor-dev, oftc.net
|
-Mar 05 21-00 | Tails contributors’ meeting
+Mar 5 21:00 | Tails contributors’ meeting
| #tails-dev, oftc.net
+ |
+Mar 22-23 | Tor @ LibrePlanet 2014
+ | Cambridge, Massachusetts, USA
+ | http://libreplanet.org/2014/
This issue of Tor Weekly News has been assembled by Lunar, harmony,
version 35
Author: lunar
Date: 2014-02-25T17:15:25+00:00
write up about the dev. meeting
--- version 34
+++ version 35
@@ -15,7 +15,49 @@
News from the 2014 Winter Developers’ Meeting in Reykjavík
----------------------------------------------------------
-???
+Since 2010, core Tor Project's contributors try to meet twice a year to
+enjoy the pleasure of each others company and move projects forward
+through face-to-face discussions and hack time. This year, close to
+forty people attended the “2014 winter dev. meeting” [XXX] that was held in
+Reykjavík, Island.
+
+The team had over forty discussion topics ranging from organizational
+matters to highly technical design decisions. For a couple of
+highlights, many sessions have been focused on discussing and producing
+roadmaps: a mid-term vision for the Tor Browser [XXX], a step-by-step
+plan for the Tor Instant Messaging Bundle [XXX], detailed ideas for new
+bridge bundles [XXX], ways to solve the research problems around guard
+nodes [XXX], and how to plan little-t tor releases [XXX].
+
+The meeting also enabled cross-team communication: pluggable
+transports developers have been able to discuss integration in the Tor
+Browser [XXX] and the lifecycle of recommended transports [XXX];
+the Tor Browser and the support teams met to see how to improve
+communications on both sides [XXX]. One outcome is a plan to remix
+existing documentation to create the Tor Browser User Manual [XXX].
+
+The two intense days of discussions have been followed by hands-on
+sessions which have seen their fair share of hacking and write
+ups [XXX].
+
+Some of the minutes are still missing, but there is already plenty to
+read already. Now that developers had to stop contemplating northern
+lights [XXX], some discussions [XXX] are already continuing on various
+project's mailing lists. Stay tuned!
+
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/TorBrowserPlan
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/RoadmapTIMB
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/BridgeBundles
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/GuardDesign
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/TorReleaseProcess
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/PTTBB
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/BridgeProtocolsAndTBB
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/SupportAndTorBrowserTeamsMeeting
+ [XXX]: https://bugs.torproject.org/10974
+ [XXX]: https://trac.torproject.org/projects/tor/timeline?from=Feb+21%2C+2014&daysback=2&authors=&ticket=on&ticket_details=on&changeset=on&update=Update
+ [XXX]: https://en.wikipedia.org/wiki/Aurora_%28astronomy%29
+ [XXX]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006288.html
Miscellaneous news
------------------
@@ -125,7 +167,7 @@
for improving this warning message has more information about the
issue [XXX].
-[XXX]: https://bugs.torproject.org/7439
+ [XXX]: https://bugs.torproject.org/7439
Upcoming events
---------------
@@ -156,5 +198,3 @@
Possible items:
* announcement of new TBB releases https://lists.torproject.org/pipermail/tor-talk/2014-February/032116.html (hope we'll have an answer from the TBB team, otherwise it's pointless to mention it — lunar)
- * the main feature should be a wrap-up of the dev. meeting; I'm trying to sort the minutes as much as I can before writing a summary (Lunar)
- * Guard node security: ways forward (if this doesn't make it into the dev meeting summary) https://lists.torproject.org/pipermail/tor-dev/2014-February/006288.html
===========================================================================
==== https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews/2014/9 ====
===========================================================================
version 3
Author: lunar
Date: 2014-02-25T18:53:50+00:00
add item
--- version 2
+++ version 3
@@ -85,4 +85,5 @@
Possible items:
- * Mozilla dev. reaching out: New API for TorBrowser add-on https://lists.torproject.org/pipermail/tor-talk/2014-February/032204.html+ * Mozilla dev. reaching out: New API for TorBrowser add-on https://lists.torproject.org/pipermail/tor-talk/2014-February/032204.html
+ * Why Johnny Can't Blow the Whistle https://lists.torproject.org/pipermail/tor-talk/2014-February/032205.html
version 2
Author: lunar
Date: 2014-02-25T17:37:29+00:00
add item
--- version 1
+++ version 2
@@ -81,4 +81,8 @@
[XXX]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
[XXX]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
-}}}+}}}
+
+Possible items:
+
+ * Mozilla dev. reaching out: New API for TorBrowser add-on https://lists.torproject.org/pipermail/tor-talk/2014-February/032204.html
version 1
Author: lunar
Date: 2014-02-25T17:36:39+00:00
import template
---
+++ version 1
@@ -0,0 +1,84 @@
+''35th issue of Tor Weekly News. Covering what's happening from February 25th, 2014 to March 4th, 2014. To be released on March 5th, 2014.''
+
+'''Editor:'''
+
+'''Subject:''' Tor Weekly News — March 5th, 2014
+
+{{{
+========================================================================
+Tor Weekly News March 5th, 2014
+========================================================================
+
+Welcome to the nineth issue of Tor Weekly News in 2014, the weekly
+newsletter that covers what is happening in the XXX Tor community.
+
+New Release of XXX
+------------------
+
+XXX: cite specific release date, numbers, and developers responsible
+
+XXX: details about release
+
+ [XXX]:
+
+Monthly status reports for XXX month 2014
+-----------------------------------------
+
+The wave of regular monthly reports from Tor project members for the
+month of XXX has begun. XXX released his report first [XXX], followed
+by reports from name 2 [XXX], name 3 [XXX], and name 4 [XXX].
+
+ [XXX]:
+ [XXX]:
+ [XXX]:
+ [XXX]:
+
+Miscellaneous news
+------------------
+
+Item 1 with cited source [XXX].
+
+Item 2 with cited source [XXX].
+
+Item 3 with cited source [XXX].
+
+ [XXX]:
+ [XXX]:
+ [XXX]:
+
+Tor help desk roundup
+---------------------
+
+Summary of some questions sent to the Tor help desk.
+
+Vulnerabilities
+---------------
+
+XXX: Reported vulnerabilities [XXX].
+
+ [XXX]: vulnerability report source
+
+Upcoming events
+---------------
+
+Jul XX-XX | Event XXX brief description
+ | Event City, Event Country
+ | Event website URL
+ |
+Jul XX-XX | Event XXX brief description
+ | Event City, Event Country
+ | Event website URL
+
+
+This issue of Tor Weekly News has been assembled by XXX, XXX, and
+XXX.
+
+Want to continue reading TWN? Please help us create this newsletter.
+We still need more volunteers to watch the Tor community and report
+important news. Please see the project page [XXX], write down your
+name and subscribe to the team mailing list [XXX] if you want to
+get involved!
+
+ [XXX]: https://trac.torproject.org/projects/tor/wiki/TorWeeklyNews
+ [XXX]: https://lists.torproject.org/cgi-bin/mailman/listinfo/news-team
+}}}
--
Your friendly TWN monitoring script
In case of malfunction, please reach out for lunar at torproject.org
or for the worst cases, tell weasel at torproject.org to kill me.
More information about the news-team
mailing list