Bug 8407 - TAG inconsistently uses VSM prefix
Summary: TAG inconsistently uses VSM prefix
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Documentation (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks: 571
  Show dependency treegraph
 
Reported: 2024-08-07 15:15 CEST by William Sjöblom
Modified: 2024-10-21 16:45 CEST (History)
0 users

See Also:
Acceptance Criteria:


Attachments

Description William Sjöblom cendio 2024-08-07 15:15:16 CEST
In the ThinLinc Administrator's Guide, we sometimes refer to the master and agent as VSM server and VSM agent. Other times, we simply call them master and agent.

It is not obvious to users that "VSM server" == "master". Hence -- we should be consistent here.
Comment 1 William Sjöblom cendio 2024-08-07 15:25:24 CEST
I see three decision points here:

- Do we use the VSM prefix or not? The internal consensus tells us to stick to "master" and "agent"

- Do we treat these as a name or not? I.e. "Master" or "master". This is also inconsistent throughout the TAG.

- How do we refer to the services (that still use the VSM prefix)? The association between "master" and "vsmserver.service" needs to be made clear, perhaps by writing "... restart the master service (vsmserver) ...".

Note You need to log in before you can comment on or make changes to this bug.