Problem/Motivation
There has been quite a few discussion in the tech regarding the terms "whitelist/blacklist" and "master/slave" and personally I've been always on the side of the "it's just a historical term, why bother change it".
However recent events made me think quite a bit on this and I realise that, yes it's only a term, but there are indeed people which are indeed affected by this terminology and on top of that terms like "AllowList" and "BlockList" do not require prior knowledge and are more straight forward.
Some relevant changes:
- Google: Removing whitelist/blacklist and master/slave from Go
- Redis: Changing master-slave replication terms with something else
- Rails Replace use of whitelist with allowlist and blacklist with denylist
Proposed resolution
Change "whitelist" to "allowlist".
Remaining tasks
- Update the code base,
- Add update hook to preserve functionality,
- Update translations where necessary,
- Release change.
<1h3 id="summary-ui-changes">User interface changes
All references to "Whitelist" should be updated to "Allowlist"
API changes
N/A
Data model changes
N/A
Release notes snippet
Updated terminology: <em>whitelist</em> becomes <em>allowlist</em> for better clarity and as more inclusive term.
Comments
Comment #2
esolitosComment #3
svenryen commentedThanks for the patch. Are you interested in porting it to 7.x?
Comment #4
esolitosI tan surely take a look at that, should be pretty easy.
Comment #5
svenryen commentedI checked your patch, and a few cases of "whitelist" were still present in the code (mostly in strings and comments).
I also made a patch for Drupal 7, both attached.
Comment #6
svenryen commentedComment #9
svenryen commented