Remove usage of whitelist/blacklist in favor of more culturally sensitive terms.

Description

I've seen the most usage of these terms in /filters/*. One possibility is changing these to allowlist/blocklist.

Activity

Show:
Peter Edberg
June 24, 2020, 5:42 PM

I have seen: safelist or allowlist vs blocklist or denylist

Robby Daigle
June 24, 2020, 5:45 PM

Those are good. Also includelist or excludelist work too.

Jeff Genovy
June 24, 2020, 6:10 PM

Given the existing usage (or existing filter files) we’d likely need to add aliases for the existing terms as well.

https://github.com/unicode-org/icu/blob/master/docs/userguide/icu_data/buildtool.md#locale-slicing

Markus Scherer
June 26, 2020, 5:16 PM

For data filtering, “include”/”exclude” without the “list” suffix might work and be clear.

We also have “whitelist”/”blacklist” in the spoof checker API docs (both C++ and Java).

Markus Scherer
June 26, 2020, 6:04 PM

https://developers.google.com/style/inclusive-documentation#features-and-users “Avoid using socially-charged terms for technical concepts where possible. For example, avoid terms such as blacklist, native feature, and first-class citizen, even though these terms may still be widely used. Instead of first-class, consider other terms such as: core feature, built-in, top-level. Choose the best term for your context.“

https://developers.google.com/style/word-list#blacklist

Fixed

Assignee

Markus Scherer

Reporter

Robby Daigle

Components

Labels

None

Reviewer

None

Priority

major

Time Needed

Hours

Fix versions

Configure