Spencer:
>>> Marc Watson:
Marc, are you on the list or do you need explicit Cc:?
>> u:
>> not use CAPS, but just bold text.
>
> I would edit the text a bit as well.
>
> Feeling like 'all data is lost' is clear enough maybe we combine the two
> a bit and have:
>
> The USB Stick that you install on is formatted and all data is deleted.
I like this one.
> Or, if there is insistence with using an explicit example. e.g.,
> persistent volume, then it could read:
>
> The USB Stick that you install on is reformatted and all data, including
> persistent volumes, is deleted.
I also like this one, maybe:
« The USB stick that you install on is reformatted and all data is
deleted, including the persistent volume. »
- Put the important "delete" before the long apposition.
- They can only be one persistent volume.
I also proposed removing "that you install on" which was added to avoid
ambiguity between the "USB stick you are cloning from" but I feel like
here there's a tension with making this sentence shorter to give more
important to data deletion. I'm not sure what's better.
>>> Please remove the input
>>> focus from Install option
>
> If accidentally selected, the destination requires further input that
> could prevent accidents.
>
> Since this is the same case for the other options, it is logical to
> order them with the first in the list emphasized, if that keyboard
> action is a must.
>
> A resolution could be to not have any option emphasized upon selecting
> 'Enter'.
I don't know for sure but maybe that's not possible. I proposed to focus
on the link to the documentation :)
> Also, from the target device dialog, it could be valuable to have some
> visual way to confirm you selected the option you intended, such as text
> that says so.
>
> And I do think a 'Back' button from the target device dialog could be
> valuable.
I think we should instead work on:
https://tails.boum.org/blueprint/bootstrapping/installer/#bonus_for_2015.
The issue here is that it's hard to find people to write the code, so if
we find some they should work on the real solution instead of the
workarounds.
And yes, I should update this blueprint and the corresponding tickets as
they are far from being clear right now.
