Feature #9005

Tails Installer without a splash screen

Added by intrigeri 2015-03-03 18:14:20 . Updated 2019-07-22 16:13:17 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Installation
Target version:
Start date:
2015-02-04
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

https://tails.boum.org/blueprint/bootstrapping/installer/#bonus_for_2015

Starter:
0
Affected tool:
Installer
Deliverable for:

Description

This covers removing the splash screen of Tails Installer and dealing with the related consequences.

Feature #8859 was about removing the splash screen but we still have some direct consequences to deal with.

Files

1.png (32169 B) kurono, 2016-05-18 16:07:05

Subtasks

Feature #8865: Implement "Install from ISO" in Tails Installer Duplicate

0
Feature #8861: Be able to launch Tails Installer from the command line Rejected

50
Feature #8860: Tails Installer should autodetect if Tails is installed on the destination device Resolved

100
Feature #8859: Get rid of the splash screen of Tails Installer Resolved

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

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

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

100
Feature #14720: Fix self.opts.partition vs. self.force_reinstall semantics Resolved

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

100
Bug #14722: Tails Installer's is_ISO_selected method is not a predicate Resolved

100
Feature #14723: Improve name of Tails Installer's device_with_persistence Resolved

100
Bug #14724: Make Tails Installer's isohybrid detection code robust Rejected

0
Bug #14755: Tails Installer treats drives differently depending on when they are plugged Resolved

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

100

History

#1 Updated by kurono 2015-07-28 08:54:59

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

As agree, I will work on this.

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

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

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

Second:

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

If I undestand correctly, it is a duplicated of:

#2 Updated by sajolida 2015-09-10 12:02:18

  • Target version changed from Hardening_M1 to 2016

#3 Updated by intrigeri 2015-10-02 17:30:47

kurono wrote:
> To begin with, it is not clear to me if we:
>
> 1. Feature Feature #8859: Get rid of the splash screen of Tails Installer.
> 2. Feature 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 2015-12-02 10:06:03

  • Assignee changed from sajolida to kurono

#5 Updated by kurono 2015-12-02 10:19:32

  • QA Check deleted (Info Needed)

#6 Updated by kurono 2016-05-18 15:42:51

  • 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 2016-05-18 16:08:25

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 2016-05-19 11:03:21

  • Assignee changed from kurono to sajolida

I’ll do that!

#9 Updated by sajolida 2016-07-15 12:57:12

  • 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 Bug #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 2016-08-02 09:31:54

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

#11 Updated by anonym 2016-09-20 16:53:44

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

#12 Updated by BitingBird 2016-10-16 04:50:52

  • 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 2016-11-25 09:23:16

  • 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 Bug #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 2016-12-12 18:35:12

  • Target version deleted (Tails_2.9.1)

#15 Updated by sajolida 2016-12-28 21:23:26

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

#16 Updated by kurono 2017-01-31 21:01:16

  • 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 2017-04-07 15:21:21

#18 Updated by kurono 2017-04-07 15:50:31

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

#19 Updated by kurono 2017-04-19 16:57:27

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

#20 Updated by sajolida 2017-05-23 17:38:44

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

#21 Updated by kurono 2017-06-08 16:55:44

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

#22 Updated by sajolida 2017-06-30 16:00:29

  • 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 2017-07-05 19:07:23

#24 Updated by sajolida 2017-07-05 19:08:38

#25 Updated by anonym 2017-09-27 17:55:24

  • 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 2017-09-28 06:04:31

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 2017-10-03 07:16:49

  • blocked by deleted (Feature #13424: Core work 2017Q3: User experience)

#28 Updated by kurono 2017-10-11 16:35:07

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 :)

#29 Updated by anonym 2017-11-15 11:30:48

  • Target version changed from Tails_3.3 to Tails_3.5

#30 Updated by kurono 2018-01-15 18:00:39

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

#31 Updated by sajolida 2018-01-19 16:03:05

  • Subject changed from Improve Tails Installer UX: phase 1 to Tails Installer without a splash screen
  • Description updated

#32 Updated by kurono 2018-02-10 09:33:24

  • QA Check changed from Info Needed to Dev Needed

#33 Updated by intrigeri 2018-03-05 07:40:33

anonym wrote:
> Currently all the tickets are assigned to me, since I’m responsible for them to be finished in time for Tails 3.3.

Coming back to this, 2 of these tickets are not fixed yet: Bug #14724 (which is a PITA wrt. my work on Feature #14595 because Bug #15031, and apparently it affects human users too) and Bug #14810 (a regression that impacts users but at least it does not harm my dev work). I’ll check with kurono what his updated ETA is and if it’s not good enough I’ll reassign these 2 tickets to anonym, who was responsible for fixing them in time for Tails 3.3.

#34 Updated by bertagaz 2018-03-14 11:32:06

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

#35 Updated by bertagaz 2018-05-10 11:09:02

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

#36 Updated by intrigeri 2018-06-26 16:27:38

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

#37 Updated by intrigeri 2018-09-05 16:26:48

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

#38 Updated by intrigeri 2018-10-24 17:03:30

  • Target version changed from Tails_3.10.1 to Tails_3.11

#39 Updated by CyrilBrulebois 2018-12-16 13:52:42

  • Target version changed from Tails_3.11 to Tails_3.12

#40 Updated by anonym 2019-01-30 11:59:11

  • Target version changed from Tails_3.12 to Tails_3.13

#41 Updated by CyrilBrulebois 2019-03-20 14:35:08

  • Target version changed from Tails_3.13 to Tails_3.14

#42 Updated by intrigeri 2019-04-13 07:17:35

  • Assignee deleted (kurono)
  • Target version deleted (Tails_3.14)

@kurono, the last subtask here (Bug #14958) is currently blocked by Bug #8862, and neither of them has any assignee nor target version, so I’m updating this ticket to better reflect the current state of things. Congrats and thanks for all the work you’ve put into this ticket & its subtasks so far!

#43 Updated by sajolida 2019-07-22 16:13:17

  • Status changed from In Progress to Resolved

I unparented Bug #14958 from this ticket so I could close it. Bug #14958 is blocked by Bug #8862 which is quite out of scope here.

I’m so glad we got rid of this splash screen! \o/