Tails

#1 Updated by intrigeri 2015-02-05 09:08:35

• Type of work changed from Contributors documentation to User interface design

#3 Updated by intrigeri 2015-03-01 23:04:57

• QA Check set to Info Needed

#4 Updated by sajolida 2015-03-02 11:50:43

• blocks Feature #8557: Have Tails Installer uploaded and accepted into Debian added

#5 Updated by sajolida 2015-03-02 11:51:11

• QA Check deleted (Info Needed)

Done.

#6 Updated by intrigeri 2015-03-02 17:04:17

• Target version set to Tails_1.4

#7 Updated by sajolida 2015-04-26 08:47:19

• Description updated
• Assignee changed from sajolida to DS
• QA Check set to Ready for QA

Note that this depends on what we decide in https://mailman.boum.org/pipermail/tails-ux/2015-April/000371.html.

DS, do you might reviewing this?

#9 Updated by sajolida 2015-04-26 08:48:14

• related to Bug #5466: Link to documentation in Tails Installer does not open the documentation because it points to an old URL which is not properly redirected in Tails added

#10 Updated by sajolida 2015-04-26 08:48:43

• Description updated

#11 Updated by sajolida 2015-04-26 08:52:54

• Description updated

#13 Updated by sajolida 2015-04-27 08:22:10

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

Now that see that even my revised version is very ambiguous. I’ll try to
be more explicit.

> Inside Tails
>
> Clone and Install- means that everything from the running Tails (Persistent Volume and any other partitions) will be copied to the new device.

Actually, in this the persistent volume is not copied. The Tails
partition of the USB stick is copied but not the persistent volume. I
think that’s a problem with the current “Clone” terminology which is
ambiguous regarding what happens to the the persistent volume.

> Clone and Upgrade - means that only Tails (without Persistent Volume and any other partitions) will be copied onto the new device.

First of all, on such a Tails device you can only have two partition:
the Tails partition (Tails system) and the persistent volume so there’s
no point in talking about “any other partitions”.

This scenario “clone and upgrade” is relevant when you know someone who
did the upgrade already and you want to us her device to upgrade your
(without having to download the ISO image yourself for example).

> I’m uncertain what “Upgrading from an ISO image” is really meaning in this selection. It seems to me we’re simply burning a new DVD. We select an ISO image and then burn, correct?

“Upgrading from an ISO image” is relevant if you need have to do a
manual upgrade (for example because automatic upgrades are not available
this time for some reason, see
https://tails.boum.org/doc/first_steps/upgrade#manual) and you want to
do upgrade a Tails device not by cloning from a friend or from a DVD but
directly from the ISO image.

> There is not necessarily any upgrading going on.

You’re write. Technically speaking, this ISO image might be any Tails
ISO image (even from a previous version or actually from the same
version, so that’s not an upgrade as such) but from the point of view of
the user scenario, this will first and foremost used to perform manual
upgrades.

> Given the above premises, I suggest:
>
> Inside Tails:
>
> Copy Partial (or perhaps Copy Tails)
>
> Copy Tails without existing Persistent volume or partitions.
> The Persistent volume and any partitions on the destination device are preserved.
>
> Copy All or Copy Everything
>
> Copy Tails and existing volumes and partitions.
> All data on the destination device will be overwritten.

This scenario is not implemented yet. There are currently no options
that allow you to copy the persistent volume for example.

What we need to do is to find a way of explaining that we will install a
new Tails device by copying the Tails system (but not the persistent
volume). That’s “Clone and install”.

> Burn DVD
>
> Create a new DVD from an ISO image.

Tails Installer only works for USB sticks or SD card. There is no such
thing as burning a DVD here.

> Outside Tails - because these seem to be dealing only with an ISO image, I’m assuming they are only creating DVDs.

Yes, outside of Tails we’re only taking an ISO image as source. But
we’re not creating DVDs here. Tails Install always works on USB sticks
or SD cards. Either to install them or to upgrade them (if the user has
to go through a manual upgrade for example).

> Burn DVD
>
> Create a new DVD with a Persistent volume.

DVDs cannot have persistent volume.

> All data on the destination device will be overwritten.
>
> Upgrade (I must be misunderstanding what’s happening, as I don’t understand how we can be modifying a read only device, so I haven’t made any suggestions below.)

We’re not talking about DVDs here but about USB sticks or SD card.

Based on the misunderstood that you had, I’ll try to propose something
better :)

#14 Updated by sajolida 2015-04-27 08:51:36

• Description updated
• Assignee changed from sajolida to DS
• QA Check changed from Dev Needed to Ready for QA

Worked on an updated proposal:

• Made it clear that the persistent volume is never copied.
• Made it clear that we’re talking about USB sticks and SD cards only.
• Got rid of the term “clone”.
• Explained that you need an ISO image if outside of Tails.

Reassigning to DS for more review.

#15 Updated by sajolida 2015-04-27 08:51:57

• Status changed from Confirmed to In Progress

#16 Updated by sajolida 2015-05-05 17:30:33

• Description updated

New version available in the description:

• Clarify “running”.
• Avoid future tense.
• Use “flash media”.
• Use “persistent encrypted storage”.
• Clarify which version is going where.
• Clarify which device we are talking about.

#18 Updated by sajolida 2015-05-06 09:01:30

• Assignee changed from DS to sajolida

#19 Updated by sajolida 2015-05-06 16:21:24

• Description updated
• Status changed from In Progress to Resolved
• Assignee deleted (sajolida)
• QA Check deleted (Ready for QA)

Thanks for your review.

• I integrate the idea of formatting in both installation scenario. Still I tried to find a shorted formulation that yours because I’m afraid this screen is getting longer and longer every time.
• Regaring “update” vs “upgrade”, we’ve been using upgrade all over the place when talking about installing a new version of Tails. If I understand well an “upgrade” is bigger and more implicating than an “update”. That’s what I understand from Microsoft and Apple and what we’ve been doing so far.

So I’m now marking this ticket as resolved.

#20 Updated by sajolida 2015-05-06 16:22:46

• Description updated

#21 Updated by sajolida 2015-05-06 16:24:02

• Description updated

#22 Updated by sajolida 2015-05-06 16:25:18

• Description updated

#23 Updated by sajolida 2015-05-06 17:21:51

• Status changed from Resolved to In Progress
• Assignee deleted (None)
• Type of work changed from User interface design to Code

Actually, maybe I should assign this to u for review and implementation.

#24 Updated by intrigeri 2015-05-06 19:38:29

• Target version changed from Tails_1.4 to Tails_1.4.1

sajolida wrote:
> Actually, maybe I should assign this to u for review and implementation.

Yep. Postponing to 1.4.1, for obvious reasons.

#25 Updated by Anonymous 2015-06-16 04:15:50

• Assignee set to sajolida
• QA Check set to Info Needed

Hi sajolida,

now that you’ve also been working on the wording of the web assistant, we might need to stay consistent with both, correct? Would you be able to review the current wording and tell me if that is still what needs to be implemented or if any words need to be changed?

Thanks!

#26 Updated by Anonymous 2015-06-16 04:16:09

• related to Feature #9433: Rephrase "Copy from a friend" and "Install from scratch" added

#27 Updated by sajolida 2015-06-16 08:01:25

• QA Check changed from Info Needed to Dev Needed

It’s not consistent anymore :)

I’ll update this soon. Do you have any particular deadline?

#29 Updated by sajolida 2015-06-18 09:11:34

• Description updated

#30 Updated by sajolida 2015-06-18 09:13:35

• Description updated

#31 Updated by sajolida 2015-06-18 09:16:48

• Assignee deleted (sajolida)
• QA Check changed from Dev Needed to Ready for QA

Updated again:

- Use “flash memory” instead of “flash media”

- Explicit “destination”

- Say “encrypted persistent storage” consistently

- Clarify “another Tails”

- Say “an ISO”
- Use “cloning” in title and “copying” in explanation

u can you have a final look and mark this as resolved if you think you can use it as such?

#33 Updated by Anonymous 2015-06-19 02:53:44

• Assignee set to sajolida

What do you think?

#35 Updated by sajolida 2015-06-23 06:57:39

• Description updated
• Assignee deleted (sajolida)

Thanks for reviewing my work and proposing improvements. It’s sometimes hard for me to draw the line between word reduction and clarity. I updated the description of the ticket again (next I promise I’ll use a blueprint!). And here are a few comments about your changes:

• About “flash memory”. If you want to question this, please do in the thread so that everybody who took part can know what’s happening. Muri (I think) said that “device” was vague and hard to translate into German. BitingBird said somewhere in Redmine that “flash” could be confused for “Adobe Flash” but that specifying “flash memory” was making it less ambiguous. I’m not a super fan of “flash memory” either but it’s so far the most convincing terminology we found.
• I changed to using “the Tails system” instead of “the Tails”. I agree with you that so far we haven’t used “Tails” as a noun to refer to the “Tails operating system installed on a device” and maybe we should start now. I’ve seen many people using this shortcut in real life easily (saying “Is your Tails up-to-date?” o “I lost my Tails”) and that’s why I felt it was OK to start using it this way. I propose we use “system” instead of “device” (vague for German translator) or “instance” (vague and jargony).
• Regarding “install”. The Apple style guide says “You install items on a disk, not onto a disk.” So I stuck to “install on” everywhere but added the prepositiong as you proposed in “the flash memory that you install on”. Does that work?
• Regarding tenses. I agree that we should not simply ban the future tense and always speak in the present tense. Still, we should refer to events that will happen “at some point in time after a given action” consistently. In your proposal you’re now mixing present tense and future tense for events that will occur simultaneously. For example “The flash memory is formatted” happens at the exact same time than “all data is lost” so it feels wrong to use present tense for one and future tense for both. The same happens in “the encrypted persistent storage of the Tails system that you upgrade is preserved”, where “is preserved” happens at the same time as “you upgrade” and not at some unspecified point later on. So I’m sticking to the present tense for now as the tense to describe all the changes implied by one of each actions.
• “the one you are currently using” → done!

#36 Updated by sajolida 2015-06-23 07:00:56

• Description updated

• “an ISO image which can be downloaded from our website” → done!

#38 Updated by Anonymous 2015-06-23 09:13:14

• Assignee set to sajolida

I let you comment on my last comment one last time? :)

#39 Updated by sajolida 2015-06-24 08:35:42

• Assignee changed from sajolida to okgoogle

> I let you comment on my last comment one last time? :)

I’m not sure I can add more to the debate about future tense in a
constructive way. So I’m tentatively assigning this to Ok Google. Are
you are native? What’s your take on this? I also wrote about it to
Diddly-Squat who’s a professional in this field but I haven’t heard from
him in a while.

In the meantime, if you need to push something into Debian, feel free to
use either version (yours or mine). I don’t care that much :)

#41 Updated by sajolida 2015-06-29 02:47:02

• Target version changed from Tails_1.4.1 to Tails_1.5

#43 Updated by sajolida 2015-07-03 01:20:36

• Status changed from In Progress to Resolved
• Assignee deleted (okgoogle)
• QA Check changed from Ready for QA to Dev Needed

Thanks for your input DS. So I’m assigning this ticket to u again as requested in #40 and let embed in the code the version she thinks is best.

#44 Updated by intrigeri 2015-07-03 01:23:25

• Status changed from Resolved to In Progress

> Thanks for your input DS. So I’m assigning this ticket to u again as requested in #40 and let embed in the code the version she thinks is best.

Reopening this ticket, then.

#47 Updated by Anonymous 2015-07-03 07:54:48

• Assignee set to sajolida
• QA Check changed from Dev Needed to Info Needed

#50 Updated by sajolida 2015-08-11 04:08:22

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

#51 Updated by sajolida 2015-08-11 06:18:30

• Description updated
• Status changed from In Progress to Resolved
• Assignee deleted (sajolida)
• Target version deleted (Tails_1.6)
• QA Check deleted (Info Needed)

During the summit we agreed on always saying “USB stick” and not mention SD cards, nor use generic terms such as “removable media”, “flash memory”, or “device”.

So I updated the description of this ticket with the wording we agreed upon during the summit and can close this ticket at last!

Thanks and congrats to everybody who took part in this until the end :)

#52 Updated by intrigeri 2015-08-26 03:59:29

• Status changed from Resolved to In Progress
• Assignee deleted (None)
• Target version set to Tails_1.6

Reopening: this is the parent tickets for a few tasks that haven’t been completed yet.

#53 Updated by Anonymous 2015-09-22 15:22:00

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

#54 Updated by intrigeri 2015-10-02 17:38:03

• blocked by deleted (Feature #8557: Have Tails Installer uploaded and accepted into Debian)

#55 Updated by intrigeri 2015-11-10 06:15:41

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

#56 Updated by intrigeri 2015-11-10 06:16:24

• Status changed from In Progress to Resolved
• Target version changed from Tails_1.8 to Tails_1.7

This actually was completed in 1.7.

#57 Updated by intrigeri 2015-11-10 06:17:59

• Assignee deleted ()