-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
Undefined
-
---
-
---
WildFly's codebase includes various forms of problematic language. The purpose of this JIRA is to provide a recommended set of alternative language so developers can be consistent in the replacement language they use.
The resolution of this issue will consist of creation of a table in this JIRA description that will contain the recommended language. We'll pick an end date (say WF 22 Final or 23 Beta) and what we decide then will be the recommendation. If we need to add more later we can clone this.
Discussion leading to filling in the table should be done in comments or in some non-transient location like wildfly-dev or a thread in the wildfly google group.
Language | Context | Replacement |
---|---|---|
blacklist/whitelist | Any | allowlist/blocklist |
master/slave | Domain Mode | primary/secondary |
In the domain mode context, master and slave are sometimes used as adjectives and sometimes as nouns, e.g. the noun "master" as shorthand for "master Host Controller" and slave as shorthand for "slave Host Controller". For these cases, if the use of shorthand isn't important, e.g. in descriptive text or docs, then "slave" becomes "secondary Host Controller". For "master", use of "Domain Controller" is preferable in cases where the text isn't particularly about the two different flavors of Host Controllers, a "primary Host Controller" versus a "secondary Host Controller[s]". (Note that in general we've tended to use 'Domain Controller' in contexts where the master/slave relationship isn't the emphasis, so this is not new.)