Bug #6843

Write design documentation for Tor bridges support

Added by intrigeri 2014-03-04 23:57:12 . Updated 2014-04-26 08:28:16 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_1.0
Start date:
2014-03-04
Due date:
% Done:

100%

Feature Branch:
doc/bridge-mode-design
Type of work:
End-user documentation
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

This documentation shall include “how to import a new Tor Launcher”, at least until we migrate this to a Git submodule (if we ever do).

Subtasks

History

#1 Updated by intrigeri 2014-03-06 16:38:43

#2 Updated by intrigeri 2014-03-14 16:19:17

  • Description updated

#3 Updated by anonym 2014-04-15 04:17:27

  • Status changed from Confirmed to In Progress
  • Assignee changed from anonym to intrigeri
  • QA Check set to Ready for QA
  • Feature Branch set to doc/bridge-mode-design

A simple design document has been pushed to the doc/bridge-mode-design branch.

#4 Updated by intrigeri 2014-04-15 10:17:59

  • Assignee changed from intrigeri to anonym
  • % Done changed from 0 to 50
  • QA Check changed from Ready for QA to Dev Needed

Apparently it was already merged into master. Anyway, here are my comments:

  • I see no mention of where our Tor Launcher repo is
  • I see no mention of where the ugly Tor Launcher bundled copy lives in our main repo

Otherwise, looks fine!

#5 Updated by anonym 2014-04-25 14:49:51

  • Assignee changed from anonym to intrigeri
  • QA Check changed from Dev Needed to Ready for QA

Fixed in the doc/bridge-mode-design branch.

#6 Updated by intrigeri 2014-04-26 08:28:16

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

Merged into master, added a few improvements on top (73a1b37, 497a4ee, 771b7bc) that you’ll want to have a look at, pushed. Thanks!