Project

General

Profile

Feature #9005

Improve Tails Installer UX: phase 1

Added by intrigeri over 2 years ago. Updated 7 days ago.

Status:
In Progress
Priority:
Elevated
Assignee:
Category:
Installation
Target version:
Start date:
02/04/2015
Due date:
% Done:

32%

QA Check:
Info Needed
Feature Branch:
Type of work:
Code

1.png View (31.4 KB) kurono, 05/18/2016 04:07 PM


Subtasks

Feature #8865: Implement "Install from ISO" in Tails InstallerDuplicate

Feature #8861: Be able to launch Tails Installer from the command lineIn Progresskurono

Feature #8860: Tails Installer should autodetect if Tails is installed on the destination deviceResolved

Feature #8859: Get rid of the splash screen of Tails InstallerResolved

Feature #11501: Confirmation dialog of Tails Installer should use verbs for button instead of Yes/NoConfirmedkurono

Feature #13301: Update doc to new Tails Installer without splash screen (in Tails)Resolved

Feature #14677: Update doc to new Tails Installer without splash screen (in Debian)Confirmedsajolida

Feature #14720: Fix self.opts.partition vs. self.force_reinstall semanticsConfirmedanonym

Feature #14721: Tails Installer's on_radio_changed method is much less generic than its name suggestsConfirmedanonym

Bug #14722: Tails Installer's is_ISO_selected method is not a predicateConfirmedanonym

Feature #14723: Improve name of Tails Installer's device_with_persistenceConfirmedanonym

Bug #14724: Make Tails Installer's isohybrid detection code robustConfirmedanonym

Bug #14755: Tails Installer treats drives differently depending on when they are pluggedConfirmedanonym

Bug #14810: Tails Installer allows buggy "Reinstall (delete all data)" on too small USB sticksConfirmedanonym

History

#1 Updated by kurono about 2 years ago

  • Assignee set to sajolida
  • Target version set to Hardening_M1
  • QA Check set to Info Needed
  • Easy set to No

As agree, I will work on this.

To begin with, it is not clear to me if we:

1. Feature #8859: Get rid of the splash screen of Tails Installer.
2. Feature #9006: Simplify the Tails Installer splash screen.

Both requests are contradictory.
As an user I would prefer the first.

Second:
  • Feature #8860: Tails Installer should autodetect if Tails is installed

If I undestand correctly, it is a duplicated of:

#2 Updated by sajolida about 2 years ago

  • Target version changed from Hardening_M1 to 2016

#3 Updated by intrigeri about 2 years ago

kurono wrote:

To begin with, it is not clear to me if we:

1. Feature #8859: Get rid of the splash screen of Tails Installer.
2. Feature #9006: Simplify the Tails Installer splash screen.

Both requests are contradictory.

That's indeed confusing in Redmine, but https://tails.boum.org/blueprint/bootstrapping/installer/#bonus_for_2015 clarifies what this is about :)

#4 Updated by kurono almost 2 years ago

  • Assignee changed from sajolida to kurono

#5 Updated by kurono almost 2 years ago

  • QA Check deleted (Info Needed)

#6 Updated by kurono over 1 year ago

  • Target version changed from 2016 to Tails_2.5
  • QA Check set to Ready for QA
  • Feature Branch set to kurono/feature/9005-Improve-tails-installer

#7 Updated by kurono over 1 year ago

Ok, I guess that there are still several details to fix, but its time to get feedback specially from the UX people.
All the changes have been added to https://git-tails.immerda.ch/kurono/liveusb-creator/log/?h=feature/9005-Improve-tails-installer.
I will attach a screen shot of the current tails-installer GUI.

#8 Updated by sajolida over 1 year ago

  • Assignee changed from kurono to sajolida

I'll do that!

#9 Updated by sajolida over 1 year ago

  • Assignee changed from sajolida to kurono
  • QA Check changed from Ready for QA to Dev Needed

So, after leaving some time for people to answer on my last proposal in https://mailman.boum.org/pipermail/tails-ux/2016-June/003246.html, I think you could implement something like:

https://mailman.boum.org/pipermail/tails-ux/attachments/20160629/62e60034/attachment-0003.png

Maybe:

  • Use a more visible help button, see #10990. Maybe try the one I uploaded there right now.
  • Rephrasing
    • "Clone current Tails" → "Clone the current Tails"
    • "Use downloaded Tails ISO image" → "Use a downloaded Tails ISO image"
    • "Target Device" → "Target USB stick"
    • "Erase & Reinstall" → "Reinstall (delete all data)"
  • I'm not sure whether "Installation Instructions" should be OS dependent and point to https://tails.boum.org/install/debian/usb/#install-tails in Debian; or point to a special page starting directing on this step (with one version for PC and another on for Mac once we get there). What do you think?

#10 Updated by intrigeri about 1 year ago

  • Target version changed from Tails_2.5 to Tails_2.6

#11 Updated by anonym about 1 year ago

  • Target version changed from Tails_2.6 to Tails_2.7

#12 Updated by BitingBird about 1 year ago

  • Status changed from Confirmed to In Progress
  • Target version changed from Tails_2.7 to Tails_2.9.1

Assigning to next major release

#13 Updated by kurono 11 months ago

  • Assignee changed from kurono to sajolida
  • QA Check changed from Dev Needed to Ready for QA

sajolida wrote:

So, after leaving some time for people to answer on my last proposal in https://mailman.boum.org/pipermail/tails-ux/2016-June/003246.html, I think you could implement something like:

https://mailman.boum.org/pipermail/tails-ux/attachments/20160629/62e60034/attachment-0003.png

Maybe:

  • Use a more visible help button, see #10990. Maybe try the one I uploaded there right now.
  • Rephrasing

Done.

  • "Clone current Tails" → "Clone the current Tails"
  • "Use downloaded Tails ISO image" → "Use a downloaded Tails ISO image"
  • "Target Device" → "Target USB stick"
  • "Erase & Reinstall" → "Reinstall (delete all data)"

Done.

  • I'm not sure whether "Installation Instructions" should be OS dependent and point to https://tails.boum.org/install/debian/usb/#install-tails in Debian; or point to a special page starting directing on this step (with one version for PC and another on for Mac once we get there). What do you think?

I have used this one https://tails.boum.org/install/os/index.en.html, that gives the possibility to chose between different
OS.

#14 Updated by sajolida 10 months ago

  • Target version deleted (Tails_2.9.1)

#15 Updated by sajolida 10 months ago

  • Assignee changed from sajolida to kurono
  • QA Check changed from Ready for QA to Dev Needed

#16 Updated by kurono 9 months ago

  • Assignee changed from kurono to sajolida
  • QA Check changed from Dev Needed to Ready for QA

Details in the mail thread.

#17 Updated by sajolida 6 months ago

#18 Updated by kurono 6 months ago

  • Assignee changed from sajolida to kurono
  • QA Check changed from Ready for QA to Dev Needed

#19 Updated by kurono 6 months ago

  • Assignee changed from kurono to sajolida
  • QA Check changed from Dev Needed to Ready for QA

#20 Updated by sajolida 5 months ago

  • Assignee changed from sajolida to kurono
  • QA Check changed from Ready for QA to Dev Needed

#21 Updated by kurono 4 months ago

  • Assignee changed from kurono to sajolida
  • QA Check changed from Dev Needed to Ready for QA

#22 Updated by sajolida 4 months ago

  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)
  • Feature Branch deleted (kurono/feature/9005-Improve-tails-installer)

Not all the subtasks of this tickets were dealt with by kurono/feature/9005-Improve-tails-installer.

#23 Updated by sajolida 3 months ago

#24 Updated by sajolida 3 months ago

#25 Updated by anonym 21 days ago

  • Assignee set to kurono
  • Target version set to Tails_3.3
  • QA Check set to Info Needed

kurono, it would be great if you could tell me what you intend to do about the children of this ticket in the close future. I would like a "deadline" where I know I have to start working on these things, in case you don't find the time. Since this must be ready + reviewed + tested before 2017-11-13 (the day before Tails 3.3), it would be great if this date was no later than the 24th of October (but the earlier the better for me), so I would have enough time to get all this merged in time.

Currently all the tickets are assigned to me, since I'm responsible for them to be finished in time for Tails 3.3. Feel free to steal any or all of them, whatever you think you can handle before the deadline!

#26 Updated by intrigeri 20 days ago

anonym:

kurono, it would be great if you could tell me what you intend to do about the children of this ticket in the close future. I would like a "deadline" where I know I have to start working on these things, in case you don't find the time. Since this must be ready + reviewed + tested before 2017-11-13 (the day before Tails 3.3), it would be great if this date was no later than the 24th of October (but the earlier the better for me), so I would have enough time to get all this merged in time.

tl;dr: I've arrived at the same conclusion (modulo 1 day) by taking this question from another perspective, i.e. mine as the likely reviewer :)

Ideally, this work should be ready for the first review round ~2 weeks before 3.3 i.e. ~October 30: it took 11 days to make the branch ready for 3.2, and that timing was very stressful at least for me (as the reviewer), and possibly for anonym as well. The timing I'm asking for is similar to what we do for major releases (stuff must be ready before the freeze), which I think is suitable here since the subtasks will change the code quite a bit, and branches against Tails Installer generally take more than one review round because the code base is so messy & hard to get right. Giving anonym a week to do the work (in the worst case), this implies he should know what part he has to do it himself no later than October 23.

#27 Updated by sajolida 15 days ago

#28 Updated by kurono 7 days ago

intrigeri wrote:

anonym:

kurono, it would be great if you could tell me what you intend to do about the children of this ticket in the close future. I would like a "deadline" where I know I have to start working on these things, in case you don't find the time. Since this must be ready + reviewed + tested before 2017-11-13 (the day before Tails 3.3), it would be great if this date was no later than the 24th of October (but the earlier the better for me), so I would have enough time to get all this merged in time.

tl;dr: I've arrived at the same conclusion (modulo 1 day) by taking this question from another perspective, i.e. mine as the likely reviewer :)

Ideally, this work should be ready for the first review round ~2 weeks before 3.3 i.e. ~October 30: it took 11 days to make the branch ready for 3.2, and that timing was very stressful at least for me (as the reviewer), and possibly for anonym as well. The timing I'm asking for is similar to what we do for major releases (stuff must be ready before the freeze), which I think is suitable here since the subtasks will change the code quite a bit, and branches against Tails Installer generally take more than one review round because the code base is so messy & hard to get right. Giving anonym a week to do the work (in the worst case), this implies he should know what part he has to do it himself no later than October 23.

Thanks you both for your excellent review :)
  • I have added a comment to #14720 and I am analyzing a better solution.
  • I have proposed some fixes to #14721, #14722 and #14723.
  • Probably I won't have time to work on #14724, #14755 and #14810 before the the 24th of October.

Also available in: Atom PDF