Do an informal usability study on the "get bridges" process

See this mailing list post from May 2019. We would like to:

1. Give a user a device with a censored Tor Browser / Tor Browser Android
2. Ask the user to figure out how to connect to Tor
3. Observe what issues the user runs into

We may be able to do another iteration of this experiment at the OTF summit in Taipei.

Trac:
Parent Ticket: #31279 (closed)

added anti-censorship-roadmap-2020 component::circumvention parent::31279 points::2 priority::medium s30-o22a1 severity::normal sponsor::30-must status::new type::task usability ux labels

Trac:
Keywords: s30-o21a1 deleted, s30-o21a2 added

Actually, this fits better into O 2.2, A1.

Trac:
Keywords: s30-o21a2 deleted, s30-o22a1 added
Parent: #31274 (moved) to #31279 (closed)

Trac:
Keywords: N/A deleted, s30-o21a2 added

Trac:
Cc: cohosh, phw to cohosh, phw, ggus

Adding an idea to IFF 2020 or other event:

We could have a router simulating levels of censorship to torproject.org, blocking default bridges and others ways to connect to Tor. And connected to the router, we would have a computer with a regular browser, so people could try and learn how to bypass levels of censorship to download and use Tor. For each level we would give a Tor swag.

Trac:
Keywords: N/A deleted, anti-censorship-roadmap-2020Q1 added

Given that we are not going to have face-to-face events in the short future, we are planning all this user research remotely.

I've started to work on this at the ux research repo:

https://gitlab.torproject.org/torproject/ux/research/issues/4

No more Q1 for 2020.

Trac:
Keywords: anti-censorship-roadmap-2020Q1 deleted, anti-censorship-roadmap-2020 added

Removing label because this ticket isn't part of two activities.

Trac:
Keywords: s30-o21a2 deleted, N/A added

cohosh cc'ing myself on sponsor 30 work

changed time estimate to 16h

mentioned in issue #31279 (closed)

moved to tpo/anti-censorship/trac#31870 (closed)