Opened 3 years ago

Last modified 3 years ago

#5155 new task

Pick one name and stick with it: Management API, Control channel, command channel

Reported by: tomek Owned by:
Priority: medium Milestone: Outstanding Tasks
Component: remote-management Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

We use those three names almost interchangeably, but people who don't know they're synonyms will get confused.

We should pick one of them and stick with it. This requires documentation update, but most likely also code update (in particular, class and comment renames).

Subtickets

Change History (2)

comment:1 Changed 3 years ago by fdupont

An API is not the same than a channel so I have no problem with this: just say the management API is used over the control channel. Between control and command I prefer control but I leave this to native English speaker because it is well known that the word control has different meaning in French and English, i.e. it is a well known source of confusion.

comment:2 Changed 3 years ago by hschempf

  • Milestone changed from Kea-proposed to Outstanding Tasks

Per 9 Mar team meeting, move to outstanding

Note: See TracTickets for help on using tickets.