New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

standardize & improve language around inter-vm file transfers #1040

Open
mfc opened this Issue Jun 29, 2015 · 11 comments

Comments

Projects
None yet
5 participants
@mfc
Member

mfc commented Jun 29, 2015

in Fedora templates, the Action Menu wording for inter-vm file transfers is a bit ambiguous and confusing:

  1. Send to VM
  2. Open in Disposable VM
  3. Move to VM

"Send to" semantically suggests the original is not kept, which is not true.

In Whonix templates the Action Menu is clearer with "Copy to" being used instead of "Send to":

  1. Move to Other VM...
  2. Copy to Other VM...
  3. Open in Disposable VM

Note the different ordering as well.

I would recommend the implementation of the Whonix template practices in the other templates, both in wording (as they are clearer) and ordering (as isolating the Disposable VM option from the others makes sense).

And it may make sense to flatten the menu by removing the Action parent, as Whonix templates has done. That would make it faster for users to select the appropriate option.

@mfc mfc changed the title from standard & improve word choice around inter-vm file transfers to standardize & improve word choice around inter-vm file transfers Jun 29, 2015

@mfc mfc changed the title from standardize & improve word choice around inter-vm file transfers to standardize & improve language around inter-vm file transfers Jun 29, 2015

@marmarek marmarek added this to the Release 3.1 milestone Sep 1, 2015

@mfc mfc added the UX label Dec 1, 2015

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Jan 14, 2016

Member

i'm pretty sure this went in the wrong direction @adrelanos.

now whonix, debian, and fedora are all unified in language (yay!) but not ordering, and the language change is the wrong one, to:

  1. send to VM
  2. move to VM

As originally mentioned "send" is used semantically incorrectly here, it needs to be "copy":

  1. copy to VM
  2. move to VM
Member

mfc commented Jan 14, 2016

i'm pretty sure this went in the wrong direction @adrelanos.

now whonix, debian, and fedora are all unified in language (yay!) but not ordering, and the language change is the wrong one, to:

  1. send to VM
  2. move to VM

As originally mentioned "send" is used semantically incorrectly here, it needs to be "copy":

  1. copy to VM
  2. move to VM
@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Jan 14, 2016

Member

Michael Carbone:

i'm pretty sure this went in the wrong direction @adrelanos.

Why me?

Member

adrelanos commented Jan 14, 2016

Michael Carbone:

i'm pretty sure this went in the wrong direction @adrelanos.

Why me?

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Jan 14, 2016

Member

Why me?

haha didn't mean for it to sound scary. the language in Whonix template-derived AppVMs changed from "Copy to Other VM..." to "Send to Other VM" and I figured you are responsible for Whonix template changes?

Member

mfc commented Jan 14, 2016

Why me?

haha didn't mean for it to sound scary. the language in Whonix template-derived AppVMs changed from "Copy to Other VM..." to "Send to Other VM" and I figured you are responsible for Whonix template changes?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 14, 2016

Member

On Thu, Jan 14, 2016 at 03:01:14AM -0800, Michael Carbone wrote:

haha, didn't mean for it to sound scary. the language in Whonix template-derived AppVMs changed from "Copy to Other VM..." to "Send to Other VM" and I figured you are responsible for Whonix template changes?

This is just part of qubes packages installed there, the same as in
other templates. Visual differences are because Whonix uses dolphin as
file manager (right?), which is configured separately from Nautilus file
manager (used by default in Fedora templates).

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Member

marmarek commented Jan 14, 2016

On Thu, Jan 14, 2016 at 03:01:14AM -0800, Michael Carbone wrote:

haha, didn't mean for it to sound scary. the language in Whonix template-derived AppVMs changed from "Copy to Other VM..." to "Send to Other VM" and I figured you are responsible for Whonix template changes?

This is just part of qubes packages installed there, the same as in
other templates. Visual differences are because Whonix uses dolphin as
file manager (right?), which is configured separately from Nautilus file
manager (used by default in Fedora templates).

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Jan 14, 2016

Member

ah thanks for the clarification. I'm highlighting the differences in wording primarily (how "send" should be "copy"), rather than order which is a second issue -- ie the order of the options is different in dolphin and nautilus in Debian-based AppVMs for instance.

Member

mfc commented Jan 14, 2016

ah thanks for the clarification. I'm highlighting the differences in wording primarily (how "send" should be "copy"), rather than order which is a second issue -- ie the order of the options is different in dolphin and nautilus in Debian-based AppVMs for instance.

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Jan 14, 2016

Member

Yes, but I wouldn't change these messages in Whonix only. Especially not
without discussing it in a ticket. These messages are defined by
packages provided by Qubes only.

Member

adrelanos commented Jan 14, 2016

Yes, but I wouldn't change these messages in Whonix only. Especially not
without discussing it in a ticket. These messages are defined by
packages provided by Qubes only.

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Jan 14, 2016

Member

Marek Marczykowski-Górecki:

Visual differences are because Whonix uses dolphin as
file manager (right?)

Yes.

Member

adrelanos commented Jan 14, 2016

Marek Marczykowski-Górecki:

Visual differences are because Whonix uses dolphin as
file manager (right?)

Yes.

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc May 5, 2016

Member

right, so it sounds like it is Dolphin menu language (provided by Qubes) that need to be improved? Whether it is Dolphin in Debian, Whonix, Fedora, etc. That will ensure the user finds the same language (and ideally same order) as in Nautilus.

Member

mfc commented May 5, 2016

right, so it sounds like it is Dolphin menu language (provided by Qubes) that need to be improved? Whether it is Dolphin in Debian, Whonix, Fedora, etc. That will ensure the user finds the same language (and ideally same order) as in Nautilus.

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos May 5, 2016

Member
Member

adrelanos commented May 5, 2016

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Oct 5, 2016

Member

I think this is a pretty easy fix, we just need the Dolphin context menu text string to be the same as the Files/Nautilus language: both "Copy To VM" (rather than "Send To VM").

Member

mfc commented Oct 5, 2016

I think this is a pretty easy fix, we just need the Dolphin context menu text string to be the same as the Files/Nautilus language: both "Copy To VM" (rather than "Send To VM").

@unman

This comment has been minimized.

Show comment
Hide comment
@unman

unman Apr 14, 2017

Member

@andrewdavidwong Confirmed issue still arises in 3.2 milestone

Member

unman commented Apr 14, 2017

@andrewdavidwong Confirmed issue still arises in 3.2 milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment