Project

General

Profile

Feature #14477

Feature #14468: Add VeraCrypt support to Tails

User testing and community feedback for VeraCrypt support

Added by segfault 4 months ago. Updated 2 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
12/10/2017
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Communicate
Blueprint:
Starter:
Affected tool:

Description

This is "A.8 User testing & community feedback":

  • Doing in-person user testing. This will be suited to identify UX issues in our design.
  • Asking for feedback online through our blog and Twitter. This will help us identify bugs in our software implementation.
  • Analysis of WhisperBack reports, to identify both technical and usability issues.

Subtasks

Feature #14481: Release Beta for VeraCrypt support in TailsConfirmedsegfault

Feature #15037: Have plans to release our VeraCrypt work in TailsConfirmedanonym

Feature #15038: Clarify which version of the partition formatting dialog of Disks we should redesignConfirmedsegfault


Related issues

Blocked by Tails - Feature #14476: Write user documentation for VeraCrypt support in Tails Confirmed 10/08/2017
Blocks Tails - Feature #14480: Fix bugs and UX issues of VeraCrypt support Confirmed 08/28/2017

History

#1 Updated by segfault 4 months ago

  • Target version set to Tails_3.9

#2 Updated by sajolida 3 months ago

  • Target version changed from Tails_3.9 to Tails_3.8

We aiming at a beta on June 1 and a release on July 15. This needs to happen before the release. Hopefully early enough after the beta to have time to fix stuff. So I'm arking it for 3.7 instead (June 26).

#3 Updated by intrigeri 2 months ago

  • Blocked by Feature #14476: Write user documentation for VeraCrypt support in Tails added

#4 Updated by intrigeri 2 months ago

  • Description updated (diff)

I wonder how the "identify UX issues in our design" part should relate to upstreaming code: on the one hand we want to upstream stuff ASAP. OTOH it would be lame to upstream something and come back to it 2 months later saying "sorry, user testing proved that our design was bad, here's a new one". Perhaps the 2 tickets we have about upstreaming user-facing stuff should take this into account so we can tell upstream when submitting our initial PR that the design will be user tested and improved later if needed, which might give us the best of both worlds :)

#5 Updated by intrigeri 2 months ago

  • Blocks Feature #14480: Fix bugs and UX issues of VeraCrypt support added

#6 Updated by intrigeri 2 months ago

  • Blocked by Feature #14481: Release Beta for VeraCrypt support in Tails added

#7 Updated by intrigeri 2 months ago

  • Blocked by deleted (Feature #14481: Release Beta for VeraCrypt support in Tails)

#8 Updated by sajolida 2 months ago

Yeap. In addition to what you are proposing, note that we will have a first round of user testing when designing the interface during the UX sprint in November. There we will do paper testing to quickly iterate on our initial ideas. The objective by then is to have a "good design": a solid basis that works and won't change too much. After the beta and user testing of it we will improve the current design but not question it completely; otherwise we'd screwed up badly during the UX sprint in November.

So hopefully, the improvements coming out from the test of the beta version can be formulated as such to upstream ("improvements" and "bug fixes" and not "complete redesign of a bad design").

Also available in: Atom PDF