Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-33368

Drop all the offensive words from NM

XMLWordPrintable

    • NetworkManager-1.48.8-1.el9
    • 1
    • rhel-sst-network-management
    • ssg_networking
    • 25
    • 5
    • False
    • Hide

      None

      Show
      None
    • None
    • NMT - RHEL-9.5 DTM 24
    • Hide

      Given the current NetworkManager codebase, documentation, and logs contain terms identified as offensive ("master/slave", "whitelist/blacklist"),

      When a developer updates the codebase to replace all instances of "master/slave" with "controller/port" and "whitelist/blacklist" with "allowlist/denylist",

      Then, no references to the old terms should exist in the NetworkManager codebase, logs, or documentation.

      Definition of Done:

      • All internal and external documentation reflects the updated language
      • CI tests run successfully without errors related to the renamed terms
      Show
      Given the current NetworkManager codebase, documentation, and logs contain terms identified as offensive ("master/slave", "whitelist/blacklist"), When a developer updates the codebase to replace all instances of "master/slave" with "controller/port" and "whitelist/blacklist" with "allowlist/denylist", Then, no references to the old terms should exist in the NetworkManager codebase, logs, or documentation. Definition of Done : All internal and external documentation reflects the updated language CI tests run successfully without errors related to the renamed terms
    • Pass
    • Automated
    • None

      This issue is tracking the work needed to drop all offensive words ("master/slave", "whitelist/blacklist") from NM. This includes the code, logs and documentation. 

              ferferna Fernando Fernandez Mancera
              rh-ee-sfaye Stanislas Faye
              Network Management Team Network Management Team
              Matej Berezny Matej Berezny
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: