[Tails-ux] [Tails-dev] [PATCH] Change syslinux menu entries …

Hi,

>>>>
>>>> anonym:
>>>> This seems like something we'd like our UX team to ACK before taking
>>>> action. For the record, I'm in favour of this change, and the patch
>>>> looks good.
>>>>
>>
>> Spencer:
>> How does it look? I couldn't do anything with the .bin file. No
>> mount
>> :( Suggestions are welcome :)
>>
>
> sajolida:
> The patch is changing some code in the build system. There's not much
> to
> actually "see" in it.
>

I would like to learn more (another thread).

>>>
>>> Lunar:
>>> Isn't “boot” quite jargon? How about “Start Tails”?
>>>
>
> Agree, we've always tried to avoid "boot" and use "start" instead.
> Except... when referring to this particular screen as it was displaying
> "Boot" on it :)
>

Boot, short for bootstrapping, is a non-technical term for a technical
process. Although bootstrapping is supposed to proceed without external
input, the dialog that provides menu options is necessary.

However, we can replace the dialog with a temporary display of text
instructions for hotkey access to Tails (failsafe) though a reboot is
required.

>>
>> We are using 'Start Tails' for the 'Start Tails' button in the
>> Greeter,
>> so saying that in the syslinux menu might cause issues because we
>> argued
>> that Tails had yet to be started when in the boot dialog.
>>
>
> To avoid having two objects saying "Start Tails", I would propose
> having
> on this screen:
>

>              [no title]

>

>         Tails
>         Tails (failsafe)

>

Beautiful! Because there is a text logo in addition to the title, a
decision needs made. Please choose[0] :) My preference is Option 1.

>>
>> If we need the dialog, I am all for 'Boot' and 'Boot (Failsafe)',
>> presuming that's what the patch proposes :)
>>
>
> I'm personally concerned about how to adapt our documentation. So far
> we've been referring to this screen as the "boot menu" (as it was
> displaying the word "boot"). But if we change that, then maybe we need
> to find a way of referring to it in the doc. On the other hand, we are
> referring to Tails Greeter without having the word "greeter" appear
> anywhere on the screen. So we could continue calling this screen the
> "boot menu" even if it does not display the word "boot" anywhere.
>

Since Booting happens until the runtime environment is loaded (until we
see the GNOME desktop), and there are options to select from, "Boot
Menu" is quite precise (second bootloader in the Start-up experience).
Though we are displaying "Tails Greeter" in the canvas frame (action
bar), as dialog labels are an option for us in GNOME.

However, I am not opposed to excluding the title as it could clean
things up a bit. However, having a title in the greeter and in the Boot
Menu could help with context.

Wordlife,
Spencer

[0]: TailsBootloader.png