Bug #12148

install/mac/clone has confusing "grab the new USB stick" (that other cloning methods haven't)

Added by intrigeri 2017-01-15 18:08:20 . Updated 2018-02-19 15:38:17 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Installation
Target version:
Start date:
2017-01-15
Due date:
% Done:

0%

Feature Branch:
doc/12148-remove-grab-on-mac-clone
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Installation Assistant
Deliverable for:

Description

On https://tails.boum.org/install/mac/clone/index.en.html, after starting the other Tails, at the end of step 2/6, one is told to “grab the new USB stick on which you want to install Tails”. But at this point, the new USB stick is useless. It’ll be needed only in step 4/6. I’ve seen one new user wonder what they were supposed to do with that new USB stick after grabbing it.

OTOH, the (very similar) https://tails.boum.org/install/clone/index.en.html method (used on Mac and Linux) hasn’t this piece of weird instructions, and feels nicer.

Maybe it’s a bug to display these instructions in the Mac version?

Subtasks

Related issues

Blocks Tails - Feature #14758: Core work 2017Q4 → 2018Q1: Technical writing Resolved 2017-09-17

History

#1 Updated by sajolida 2017-04-07 15:24:19

#2 Updated by sajolida 2017-07-05 19:01:35

  • blocked by deleted (Feature #12432: Technical writing core work 2017Q2)

#3 Updated by sajolida 2017-07-05 19:01:46

#4 Updated by sajolida 2017-10-02 17:55:12

  • blocked by deleted (Feature #13423: Core work 2017Q3: Technical writing)

#5 Updated by sajolida 2017-10-02 17:55:56

  • blocks Feature #14758: Core work 2017Q4 → 2018Q1: Technical writing added

#6 Updated by cbrownstein 2018-01-05 23:19:36

  • Assignee changed from sajolida to cbrownstein

#7 Updated by sajolida 2018-02-16 19:56:32

  • QA Check set to Ready for QA
  • Feature Branch set to doc/12148-remove-grab-on-mac-clone

Cody: I took this one over from you. I hope you don’t mind. I thought that it might be a bit tricky for you still since it involves some of this weird conditional CSS display. Hopefully, reviewing the diff will teach you cool stuff for the future :)

#8 Updated by sajolida 2018-02-16 21:13:17

  • Status changed from Confirmed to In Progress

Applied in changeset commit:ecae8f78ca97ea0c1f0efbb97dd3e1a98550472d.

#9 Updated by cbrownstein 2018-02-17 01:45:59

  • Status changed from In Progress to Confirmed
  • Assignee changed from cbrownstein to sajolida
  • QA Check changed from Ready for QA to Pass

@sajolida I don’t mind. It looks good.

N.B. I’m familiar with the conditional CSS (“scenario-dependent bits”). :-)

#10 Updated by cbrownstein 2018-02-17 01:46:21

  • Status changed from Confirmed to In Progress

#11 Updated by sajolida 2018-02-19 15:38:17

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Pass)

Merged!