Feature #9433
Rephrase "Copy from a friend" and "Install from scratch"
0%
Description
From the user testing and the discussion on terminology we had several issues and ideas to improve on the current phrasing:
- “Scratch” was sometimes hard to understand.
- “Clone” is probably ok, by “copy” is more common.
For “Copy from a friend”:
- Clone from a friend
- Copy from Existing Tails Media
- Copy from another Tails
For “Install from scratch”:
- Install from the Internet
- Download and install
See:
Subtasks
Related issues
|
Related to Tails - |
Resolved | 2015-02-04 |
History
#1 Updated by sajolida 2015-05-20 17:31:12
- Description updated
#2 Updated by sajolida 2015-05-21 07:25:25
Tester A also suggested to change “from a friend” by “another USB”. This proves that “from a friend” is well understood as an example of use case but that “another USB” would work as well.
https://tails.boum.org/blueprint/bootstrapping/assistant/router/3rd_iteration/testing/
#3 Updated by sajolida 2015-05-21 10:24:23
- Parent task changed from
Feature #9204toFeature #9445
#4 Updated by SpencerOne 2015-05-27 17:23:37
Regarding ‘Copy’ vs ‘Clone’:
Technically, ‘Copy’ and ‘Clone’ are the same, though they do paint
different pictures in our minds. Copy feels lossy while clone feels
loss-less. ‘Copy’ needs a supporting word to communicate the quality of
the function, e.g., ‘Exact Copy’ or ‘Poor Copy’, where ‘Clone’
effectively communicates quality without such support. ‘Duplicate’
functions in a similar manner. However, a Kopimist might prefer ‘Copy’.
Also, ‘Clone’ isn’t jargon, where, at least in publishing, ‘Copy’ is.
People of all levels of technical experience will have some familiarity with the concept of ‘Clone’ either from Star Wars or cloning animals, so I think it is okay that people newly associate this concept with a computing experience, especially considering how ineffectively broad the concept of ‘Copy’ can be given all its various meanings.
Wordlife,
Spencer
#5 Updated by SpencerOne 2015-05-27 17:24:55
SpencerOne wrote:
> Regarding ‘Copy’ vs ‘Clone’:
>
> Technically, ‘Copy’ and ‘Clone’ are the same, though they do paint different pictures in our minds. Copy feels lossy while clone feels loss-less. ‘Copy’ needs a supporting word to communicate the quality of the function, e.g., ‘Exact Copy’ or ‘Poor Copy’, where ‘Clone’ effectively communicates quality without such support. ‘Duplicate’ functions in a similar manner. However, a Kopimist might prefer ‘Copy’. Also, ‘Clone’ isn’t jargon, where, at least in publishing, ‘Copy’ is.
>
> People of all levels of technical experience will have some familiarity with the concept of ‘Clone’ either from Star Wars or cloning animals, so I think it is okay that people newly associate this concept with a computing experience, especially considering how ineffectively broad the concept of ‘Copy’ can be given all its various meanings.
>
> Wordlife,
> Spencer
#6 Updated by sajolida 2015-06-06 17:46:19
- QA Check set to Ready for QA
- Feature Branch set to web/assistant
Tchou, please review commits commit:59e8d1a and commit:4b51f3d on web/assistant. I will refrained myself from creating Git branches for those things unless you tell me you’re comfortable with them :)
#7 Updated by sajolida 2015-06-06 17:47:24
- Assignee set to tchou
#8 Updated by sajolida 2015-06-07 11:02:58
Also review commit:4dc0f86 which I forgot to push yesterday.
#9 Updated by tchou 2015-06-10 10:11:54
- Assignee changed from tchou to sajolida
I think I mentioned it somewhere, but I’m not shure. Maybe we don’t need “clone” or “copy”.
At least, the user will use “Tails Installer”.
What if we’ll say something like “Install from a friend” or “Install from another Tails” ?
Or maybe we would have :
- “Get a friend’s Tails and install”
- “Download and install”
(note : you can do branches, I think I can review it quickly with the web interface)
#10 Updated by sajolida 2015-06-11 10:28:41
- QA Check changed from Ready for QA to Dev Needed
I’ll try this and report back.
#11 Updated by Anonymous 2015-06-16 04:16:10
- related to
Feature #8866: Rework the wording of Tails Installer added
#12 Updated by sajolida 2015-06-28 07:07:11
- Assignee changed from sajolida to tchou
- QA Check changed from Dev Needed to Ready for QA
Done in commit:eaa5c56, please review and close this ticket if you like it.
#13 Updated by sajolida 2015-09-24 08:42:05
- Target version set to Tails_1.7
This is 3 months old, raising priority.
#14 Updated by sajolida 2015-09-24 08:42:53
- Priority changed from Normal to Elevated
#15 Updated by Anonymous 2015-10-02 17:17:07
Hi sajolida,
I’ve read your commit, and if we want to use the same terminology as on the Installer, “Clone from another Tails” should become “Clone from another Tails device” no?
#16 Updated by sajolida 2015-10-06 09:15:40
- Assignee changed from tchou to sajolida
- QA Check changed from Ready for QA to Dev Needed
Sure, I’ve already removed one “friend” but now I see that I have another one a bit further on the same file:
https://git-tails.immerda.ch/tails/tree/wiki/src/install/inc/router/clone.mdwn?h=web/assistant
So I should work on this again.
#17 Updated by sajolida 2015-10-23 08:30:44
- Assignee changed from sajolida to tchou
- Priority changed from Elevated to Normal
- QA Check changed from Dev Needed to Ready for QA
Done in ebe5ab1. That was easy :)
#18 Updated by tchou 2015-10-27 04:37:33
- Status changed from Confirmed to Resolved
- Assignee changed from tchou to sajolida
- QA Check deleted (
Ready for QA)
ok.