Feature #10103

Assistant: Refine Windows scenario (sajolida's plate)

Added by sajolida 2015-08-27 07:14:06 . Updated 2015-10-27 03:15:09 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Installation
Target version:
Tails_1.6
Start date:
2015-02-03
Due date:
% Done:

100%

Feature Branch:
web/10103-windows
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Installation Assistant
Deliverable for:

Description

We have 40 things to change as a result from Feature #10047, so no, we’re not going to track each one in a separate Redmine ticket with broken parenthood. This is sajolida’s plate. The numbers correspond to the lines in /code/attachments/download/917/windows-testing-issues.fods.

  • 6. Rework “Due to” to sound less like an exception.
  • 15+16+17. Don’t talk about Tails Installer in “Install temporary Tails”. Rather explain more the specifics of the temporary Tails, maybe as a warning or info.
  • 18+19. Get rid of the tip about SD cards.
  • 21. Test security warning on different Windows versions and find a more generic formulation.
  • 23. Move the warning about data loss in intro.
  • 23. Change download button as simple link.
  • 24. Verify in UUI if there is an indication about formatting.
  • 25-26. Update UUI screenshot.
  • 25-26. Consider moving screenshot between step 6 and 7.
  • 28. Warn that installation takes a couple of minutes.
  • 29. Consider saying “warning” instead of "confirmation dialog in step 9.
  • 30. Forgive people who don’t plug the key before start UUI. “Show all drives…”
  • 33. Add a separate step for shutting down and switching context.
  • 33. Create a new image of the infography for shutting down and switching context.
  • 35. Add QR code.
  • 37. Rephrase “Write down the URL” to take into account email, chat, etc. “Send”.
  • 38. Mention other computer or tablet and not only smartphone.
  • 40. Clarify in step 3 that it doesn’t work most of the time; people are lucky if it works.
  • 41. Replace “usual operating system” by “Windows”.
  • 43. Clarify that Tails will never replace Windows.
  • 45. Move troubleshooting sections in collapsed.
  • 47. “On most computer” → “On most computers”.
  • 48. Rework the sequence in the intro “you need a key”, “boot menu”, “list”.
  • 49. Rephrase “Consult the manual of the computer to know how to enter the BIOS settings” to take into account that people don’t have a manual, they will search it online.
  • 50. Acknowledge after step 4 the fact that people might not be able to use Tails and that would imply the end of the instructions.
  • 51. People should take note of the state of these options to put them back if Windows doesn’t boot in Legacy mode.
  • 52. Split step 4 “Hold down” into two.
  • 54. Clarify instructions on how to add boot options (“type”).
  • 55. Rewrite “When removing this option”.
  • 57. Do as for temporary Tails: rework intro, move warning in intro, and rewrite step 1 to start with “Plug”.
  • 59. Warn that installation takes a couple of minutes.
  • 60. Consider mentioning that the progress bar usually get stuck at 95%.
  • 62. Improve first sentence of persistence to explain that each feature is optional.
  • 63. Split warning #2 into two:
    • 1. “Only enable the features you need”, and move it in step 4
    • 2. “You can always start without persistence enabled”, as a tip in step 7.
  • 64. Give tips about choosing a strong passphrase and link to https://firstlook.org/theintercept/2015/03/26/passphrases-can-memorize-attackers-cant-guess/

Subtasks

Feature #8841: Assistant: Integrate subscribing to the newsletter Resolved

0
Feature #10159: Assistant: Apply the new terminology around "USB stick" and "SD card" Resolved

0
Feature #10169: Assistant: Create a new image of the infography for shutting down and switching context Resolved

0

Related issues

Blocks Tails - Feature #9444: Assistant: Explain how to verify that the source USB is up-to-date Resolved 2015-05-21

History

#1 Updated by sajolida 2015-08-27 07:14:34

#2 Updated by sajolida 2015-09-03 08:27:59

  • blocks Feature #9444: Assistant: Explain how to verify that the source USB is up-to-date added

#3 Updated by sajolida 2015-09-03 09:33:38

  • Status changed from Confirmed to In Progress
  • Feature Branch set to web/10103-windows

Started the work in web/10103-windows.

#4 Updated by sajolida 2015-09-06 14:07:21

  • Assignee changed from sajolida to tchou
  • QA Check set to Ready for QA

I’m done with a first batch of commits. I think that I solved all the issues raised here. Please review. Hint: git log -p origin/master...origin/web/10103-windows blueprint/bootstrapping/assistant/windows.mdwn.

I tried to solved them in order to make your review easier.

I skipped:

  • 25-26. Update UUI screenshot, because I think I updated it already.
  • 43. Clarify that Tails will never replace Windows, because I think that’s not the place to clarify such an abstract notion.
  • 6. Rework “Due to” to sound less like an exception, because it have to be done in the overview but I’m a bit lost on the status of your last experiments and where it would be more suitable to work on this.
  • 33. Create a new image of the infography for shutting down and switching context, because that can’t be done in the same Git branch so I created Feature #10169 for that.

I’m marking this review as priority Elevated as it’s going to block me for the writing of all the other scenarios (huge work ahead).

#5 Updated by sajolida 2015-09-09 04:51:07

Added two commits on this to fix formatting.

#6 Updated by tchou 2015-09-17 23:20:51

  • Assignee changed from tchou to sajolida

I failed reviewed it with vanilla git, but found a way to see it here (it took me some time to understand that it was not on your repo, but on tails one) : https://git-tails.immerda.ch/tails/log/?h=web/10103-windows . With this interface, the oldest one is “Move warning about data loss in intro (Feature #10103, 23)”.

Everything seems ok except maybe in “Mention that progress bar freezes (Feature #10103, 60)” : mention that it’s freezing but going on after some time.

#7 Updated by sajolida 2015-09-18 09:33:39

  • Status changed from In Progress to Resolved

Applied in changeset commit:77d79c0c2b08e07843addc9a686087f50dafc25f.

#8 Updated by sajolida 2015-09-18 09:39:19

  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)

Thanks for the review, I merged it into master now!

> I failed reviewed it with vanilla git

What did you try and what failed? Did you try, as instructed in note-4:

git log -p origin/master...origin/web/10103-windows blueprint/bootstrapping/assistant/windows.mdwn

If so what happened?

> it tool me some time to understand that it was not on your repo, but on tails one

I don’t have “my repo”. I push directly on the main Tails repo on immerda.

> Everything seems ok exept maybe in “Mention that progress bar freezes (Feature #10103, 60)” : mention that it’s freezing but going on after some time.

I thought about that but too me in the current sentence the fact that this freeze is temporary is already expressed in “for some time” and “while synchronizing” which both imply that other things happen afterwards. Let’s see from tests if this is still no clear enough.