Uploaded image for project: 'VS Code Extension'
  1. VS Code Extension
  2. VSCODE-329

Remove Offensive Product Terminology in VSCode

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • No version
    • Affects Version/s: None
    • Component/s: Tech debt
    • None

      Goals

      • Replace all text using the updated terminology in all of MongoDB’s product user interfaces (UIs)
      • Create new API endpoints and marking the old API endpoints as deprecated
        • Completely remove deprecated API endpoints at a later date
      • Modify the output of commands such as rs.status(), db.isMaster() to use the updated terminology
      • Update all of the documentation that coincides with these changes, commands, and terminology

      Non-Goals

      • Make branch name changes from “master” to “main” - we would like to get through terminology first and then come back to this in a future effort.
      • We will not remove deprecated terms in any non-public facing areas of the Cloud repositories.
      • Our internal documentation (wiki etc.) contains usage of these deprecated terms. We would like to modernize this terminology as well, but feel it is distinct from the public facing engineering efforts being catalogued in this initiative. To reduce the number of people who need to be involved in the execution of this, we believe this would be a task that a TPM could spearhead and seek approval from owners of spaces, articles, and documents.

      Overview of Terminology Changes

      • “Master” and “Slave” = “Primary” and “Secondary”
        • db.isMaster() = db.hello()
      • “Whitelist” and “Blacklist” =
        • For Server = Allow List and Deny List
        • For Drivers = Allow List and Deny List
          • For Kafka = Allow List and Block List
        • For Atlas “IP Whitelist” = “Network Access List”
        • For ADL “White List” = “Access List” and “Whitlisted” = “Allowed”
        • For Charts “whitelist” = “list” plus the description “Do not include fields that may reveal sensitive data”

            Assignee:
            Unassigned Unassigned
            Reporter:
            maurizio.casimirri@mongodb.com Maurizio Casimirri
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: