sajolida:
> Please make sure you've read the introduction to this discussion before
> answering this email:
>
> https://mailman.boum.org/pipermail/tails-ux/2015-April/000370.html
>
> When we first created Tails Installer, we introduced the notion of
> "cloning": creating a Tails USB stick from another Tails USB stick.
> Note, the persistent volume is not copied in this operation.
>
> Note that currently you have to go through this to create a
> full-feature Tails USB stick (for example if you want to use
> persistence). At the end of the year people running Debian and Ubuntu
> will be able to skip that step but not others.
>
> In the web assistant we will advertise this as the easiest and fastest
> way of installing Tails: if you already know someone who uses Tails you
> can clone from her.
>
> - It might be less jargon in the web assistant to call this process
> "copy from a friend", instead of "clone from a friend".
> - But on the other hand, it might be less ambiguous to call this
> action "clone" instead or only "copy" in the interface of Tails
> Installer (and it's what we're doing already).
> - Still it would be good to use the same terminology in both cases.
>
> See both screenshots in attachment. The one called
> `copy-from-a-friend.png` is a very rough wireframe from the router
> (the set of introductory questions).
>
> The term "clone" is currently not referred to very often in our
> documentation (only in /doc/first_steps/installation and
> first_steps/upgrade) and used once in the splash screen of Tails
> Installer.
>
> What do you think?
For me, "cloning" is pretty straightforward as a term whereas "copy from
a friend" is only _one_ possible scenario. It might thus lead to
misunderstandings to use this terminology in general.
Wouldn't it be possible to call the action itself "clone" and to have a
desription in the web assistant which describes this one possible
scenario instead? Like a sort of subtext?
Cheers
u.
.%20At%20the%20end%20of%20the%20year%20people%20running%20Debian%20and%20Ubuntu%0A>%20>%20will%20be%20able%20to%20skip%20that%20step%20but%20not%20others.%0A>%20>%20%0A>%20>%20In%20the%20web%20assistant%20we%20will%20advertise%20this%20as%20the%20easiest%20and%20fastest%0A>%20>%20way%20of%20installing%20Tails:%20if%20you%20already%20know%20someone%20who%20uses%20Tails%20you%0A>%20>%20can%20clone%20from%20her.%0A>%20>%20%0A>%20>%20%0A>%20>%20See%20both%20screenshots%20in%20attachment.%20The%20one%20called%0A>%20>%20%60copy-from-a-friend.png%60%20is%20a%20very%20rough%20wireframe%20from%20the%20router%0A>%20>%20(the%20set%20of%20introductory%20questions).%0A>%20>%20%0A>%20>%20The%20term%20%22clone%22%20is%20currently%20not%20referred%20to%20very%20often%20in%20our%0A>%20>%20documentation%20(only%20in%20/doc/first_steps/installation%20and%0A>%20>%20first_steps/upgrade)%20and%20used%20once%20in%20the%20splash%20screen%20of%20Tails%0A>%20>%20Installer.%0A>%20>%20%0A>%20>%20What%20do%20you%20think?%0A>%20%0A>%20For%20me,%20%22cloning%22%20is%20pretty%20straightforward%20as%20a%20term%20whereas%20%22copy%20from%0A>%20a%20friend%22%20is%20only%20_one_%20possible%20scenario.%20It%20might%20thus%20lead%20to%0A>%20misunderstandings%20to%20use%20this%20terminology%20in%20general.%0A>%20%0A>%20Wouldn't%20it%20be%20possible%20to%20call%20the%20action%20itself%20%22clone%22%20and%20to%20have%20a%0A>%20desription%20in%20the%20web%20assistant%20which%20describes%20this%20one%20possible%0A>%20scenario%20instead?%20Like%20a%20sort%20of%20subtext?%0A>%20%0A>%20%0A>%20Cheers%0A>%20u.%0A>%20%0A>%20 "Répondre à ce message")