## Plan This epic details the breakdown of each search result occurrence to make the terminology conversion something that the entire team can contribute to iteratively. ## Docs with the terms `blacklist` or `whitelist` `grep -R -l -E 'whitelist|blacklist' doc/` 1. doc//security/asset_proxy.md https://gitlab.com/gitlab-org/gitlab/-/issues/219962 1. doc//security/rack_attack.md https://gitlab.com/gitlab-org/gitlab/-/issues/219963 1. doc//development/licensing.md https://gitlab.com/gitlab-org/gitlab/-/issues/219964 1. doc//development/query_count_limits.md https://gitlab.com/gitlab-org/gitlab/-/issues/219966 1. doc//development/insert_into_tables_in_batches.md https://gitlab.com/gitlab-org/gitlab/-/issues/219967 1. doc//development/import_export.md https://gitlab.com/gitlab-org/gitlab/-/issues/219969 1. doc//user/admin_area/settings/sign_up_restrictions.md https://gitlab.com/gitlab-org/gitlab/-/issues/219971 1. doc//user/admin_area/monitoring/health_check.md https://gitlab.com/gitlab-org/gitlab/-/issues/219972 1. doc//user/permissions.md https://gitlab.com/gitlab-org/gitlab/-/issues/219973 1. doc//user/gitlab_com/index.md https://gitlab.com/gitlab-org/gitlab/-/issues/219974 1. doc//user/clusters/applications.md https://gitlab.com/gitlab-org/gitlab/-/issues/219976 1. doc//user/application_security/container_scanning/index.md https://gitlab.com/gitlab-org/gitlab/-/issues/219977 1. doc//api/settings.md https://gitlab.com/gitlab-org/gitlab/-/issues/219981 1. doc//api/managed_licenses.md https://gitlab.com/gitlab-org/gitlab/-/issues/219982 1. doc//administration/index.md https://gitlab.com/gitlab-org/gitlab/-/issues/219985 1. doc//administration/monitoring/ip_whitelist.md https://gitlab.com/gitlab-org/gitlab/-/issues/219986 1. doc//administration/monitoring/index.md https://gitlab.com/gitlab-org/gitlab/-/issues/219987 1. doc//administration/monitoring/prometheus/index.md https://gitlab.com/gitlab-org/gitlab/-/issues/219988 1. doc//administration/monitoring/prometheus/gitlab_metrics.md https://gitlab.com/gitlab-org/gitlab/-/issues/219989 Fixed! 1. doc//security/webhooks.md https://gitlab.com/gitlab-org/gitlab/-/issues/219961 1. doc//development/documentation/styleguide.md https://gitlab.com/gitlab-org/gitlab/-/issues/219965 1. doc//development/secure_coding_guidelines.md https://gitlab.com/gitlab-org/gitlab/-/issues/219968 1. doc//user/markdown.md https://gitlab.com/gitlab-org/gitlab/-/issues/219970 1. doc//user/project/repository/repository_mirroring.md https://gitlab.com/gitlab-org/gitlab/-/issues/219978 1. doc//user/project/integrations/bamboo.md https://gitlab.com/gitlab-org/gitlab/-/issues/219979 1. doc//user/project/index.md https://gitlab.com/gitlab-org/gitlab/-/issues/219980 1. doc//push_rules/push_rules.md https://gitlab.com/gitlab-org/gitlab/-/issues/219990 1. doc//user/group/index.md https://gitlab.com/gitlab-org/gitlab/-/issues/219975 1. doc//administration/high_availability/sidekiq.md https://gitlab.com/gitlab-org/gitlab/-/issues/219983 1. doc//administration/high_availability/gitlab.md https://gitlab.com/gitlab-org/gitlab/-/issues/219984 For each doc, we should determine if they can be modified as-is and/or if they require a change to the product. ### Scenario 1: Whitelist/blacklist is used in the product itself, and therefore in docs as an direct reference Raise an issue (or request that a SME raise an issue) to change this in the product. Include the ~documentation label so that the docs are updated as a result of that change. Meanwhile, determine if an intermediary change to the docs is possible. (This may not be possible if the term is essential for the user's understanding of/success with the current UI, before it's updated.) ### Scenario 2: Whitelist/blacklist is used to describe functionality that isn't explicitly labeled as such in the product Use an alternate descriptive wording. Do not _necessarily_ use allowlist/denylist. For example: Before: > Please try a different browser with a less-strict adblocker and whitelist our domain and subdomains (gitlab.com, about.gitlab.com, and page.gitlab.com). After: > Please try a different browser with a less-strict ad blocker or ensure our domain and subdomains (gitlab.com, about.gitlab.com, and page.gitlab.com) are explicitly allowed to [...]. <summary>Context from issue</summary> <details>Inspired by the great presentation https://twitter.com/carolstran/status/1035547140016287746?s=12 From https://github.com/facebook/react/issues/13604#issuecomment-419884422 ([archived](https://web.archive.org/web/20180921225759/https://github.com/facebook/react/issues/13604#issuecomment-419884422)) "While the etymology of the words isn't steeped in racial undertones or history like other problematic tech word choices, there is no harm in changing them to synonyms that as just as understandable and avoid the question entirely" Possible options by @edjdev : - Allowlist - Throughlist - Goodlist - Includelist - Yeslist - Denylist - Blocklist - Poisonlist - Badlist - Excludelist - Nolist ## Proposal ~~We have 2 options.~~ We are going with option 1. 1. Allowlist and Denylist 1. ~~Safelist and Blocklist~~ </details>