Cleanup VM/Qube/qube usages in UI

[rootkovska]

• "Create Qubes VM" in the Appmenu -> "Create a new qube"
• "Qube Manager" -> "Qubes Manager" (because manages the whole systems, not just qubes)?
• "{Update,Clock,net}VM" in Qubes Global Settings -> \1 qube
• "dom0" -> "admin" (ibid.)

@andrewdavidwong

[andrewdavidwong]

👌

[andrewdavidwong]

👌

[marmarta]

I'm not sure about Qube Manager -> Qubes Manager; we've had this whole discussion about how we don't want to have a single place to manage all of Qubes (like the old Qubes Manager), and that's why we're resurrecting only parts of it, those that pertain to managing qubes themselves. After all, the first proposed name was 'VM and Template Manager'.

About updatevm, clockvm, netvm: do we really want to use UpdateQube, ClockQube, NetQube? I think it looks really ugly, and also, the properties in CLI tools use the updatevm, clockvm, netvm names, so it adds a layer of confusion.

And where do you want to replace dom0 with 'admin'? 'dom0' is just a VM name at the moment, not some special value (most of the time).

[marmarta]

I'm not sure about Qube Manager -> Qubes Manager; we've had this whole discussion about how we don't want to have a single place to manage all of Qubes (like the old Qubes Manager), and that's why we're resurrecting only parts of it, those that pertain to managing qubes themselves. After all, the first proposed name was 'VM and Template Manager'.

About updatevm, clockvm, netvm: do we really want to use UpdateQube, ClockQube, NetQube? I think it looks really ugly, and also, the properties in CLI tools use the updatevm, clockvm, netvm names, so it adds a layer of confusion.

And where do you want to replace dom0 with 'admin'? 'dom0' is just a VM name at the moment, not some special value (most of the time).