Skip to content
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

stop using abbreviations for default vm names #1776

Open
mfc opened this issue Feb 24, 2016 · 8 comments
Open

stop using abbreviations for default vm names #1776

mfc opened this issue Feb 24, 2016 · 8 comments
Labels
C: other localization This issue concerns translating things into different languages or adapting them to other regions. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience

Comments

@mfc
Copy link
Member

mfc commented Feb 24, 2016

we need to stop using non-intuitive abbreviations, which are:

  • confusing for new users
  • bad for localization/translation (either directly or in documentation)

anything "sys-" should instead be "system-"

  • sys-net -> system-network
  • sys-firewall -> system-firewall
  • sys-usb -> system-usb
@mfc mfc added localization This issue concerns translating things into different languages or adapting them to other regions. ux User experience labels Feb 24, 2016
@Zrubi
Copy link
Member

Zrubi commented Feb 25, 2016

Why we have to use those prefixes at all??
Wouldn't be more simple using:

  • network
  • firewall
  • usb

Thos are shorter. And sys-/system is not add anything meaningful to them.

@marmarek
Copy link
Member

Those VMs are generally something that user shouldn't (need to)
interact with in normal cases. But I agree that using name prefix for it
isn't ideal. Especially having 31 chars limit... Probably worth a tag
"system" (#865) and then other indication like separate section in Qubes
Manager ("System VMs"/"System Qubes").

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
Copy link
Member Author

mfc commented Feb 25, 2016

I like those ideas and dropping the prefixes. +1

@woju
Copy link
Member

woju commented Feb 25, 2016

On Thu, Feb 25, 2016 at 01:58:05AM -0800, Marek Marczykowski-Górecki wrote:

Probably worth a tag
"system" (#865) and then other indication like separate section in Qubes
Manager ("System VMs"/"System Qubes").

Tags aren't meant to do anything by ourselves, like separating something
in Qubes Manager. They are solely for the user. Probably better use
features (revamped services, still not implemented).

regards, .-.
Wojtek Porczyk .-^' '^-.
Invisible Things Lab |'-.-^-.-'|
| | | |
I do not fear computers, | '-.-' |
I fear lack of them. '-._ : ,-'
-- Isaac Asimov `^-^-_>

@andrewdavidwong
Copy link
Member

Personally, I like the sys- tags because they cause all system-related VMs to be sorted together lexically. I also prefer sys- over system- because I find shorter names easier to visually scan at a glance (e.g., when reading through a long list of VMs), and I find sys- to be an intuitive and unambiguous abbreviation for system in the context of Qubes.

@mfc
Copy link
Member Author

mfc commented Mar 2, 2016

Personally, I like the sys- tags because they cause all system-related VMs to be sorted together lexically

okay but "system" VMs should instead be sorted or kept in a "system vm" section of QVM based on their attribute of being "system vms", not by prefix.

@comradekingu
Copy link

Adding 'system-' to network or firewall relies on context to signify 'remote' or 'local'. Then again doing away with the prefixes and adding 'remote' or 'local' where it applies is probably the better option.

@andrewdavidwong andrewdavidwong added this to the Far in the future milestone Dec 24, 2016
@andrewdavidwong andrewdavidwong added the T: task Type: task. An action item that is neither a bug nor an enhancement. label Apr 3, 2018
@ninavizz
Copy link
Member

ninavizz commented Sep 13, 2021

Yes, to both @mfc and @andrewdavidwong's comments, above.

Screen Shot 2021-09-13 at 12 26 49 PM

There is definitely a problem of too-long prefixes in Qubes today, introducing a cognitive burden to users when seeking to parse item names in Qubes Manager and App Menu. And yet, neither utility groups qubes by "Type" or "Role," so the only way to do that grouping is by alphabetization... which the prefixes function to achieve, as a hack to the prior problem.

#6665 will solve for the App Menu need, which leaves open the need to introduce "Sort By Role" (vs by Type, which is a separate lengthy discussion) as a functionality in Qubes Manager. Which may then call into question if the API/backend already have these identifiers built-in.

Once those are built-in and this capability is built-in to Qubes Manager, I feel we can close this ticket—as it seems the broader solution, is "Stop using prefixes as a sorting mechanism for qubes, the Qube Manager and App Menu" (and possibly in relevant dropdowns).

@andrewdavidwong andrewdavidwong added C: other P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. and removed T: task Type: task. An action item that is neither a bug nor an enhancement. labels Sep 13, 2021
@andrewdavidwong andrewdavidwong removed this from the Release TBD milestone Aug 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: other localization This issue concerns translating things into different languages or adapting them to other regions. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience
Projects
None yet
Development

No branches or pull requests

7 participants