Please excuse necroing this thread, but I haven't found any other discussion, I think the issue is relevant, and i would like to provide context and some explanation:

In an effort to remove words connected to slavery and racially suggestive terms, a lot of companies and projects have opted to rename and entirely remove several terms listed below:

master/slave
(Suggested replacements: main, primary, secondary, replicant, ...)

blacklist/whitelist
(Suggested replacements: denylist/allowlist)

As Filippo Valsorda put it in a ticket for the Go programming language:

It's clear that there are people who are hurt by [these terms] and who are made to feel unwelcome by their use due not to technical reasons but to their historical and social context. That's simply enough reason to replace them.

Source: Ticket 236857 | replace usages of whitelist/blacklist and master/slave

Here is a scientific paper on the general subject, released October 2018 in the "Journal of the Medical Library Association":

“Blacklists” and “whitelists”: a salutary warning concerning the prevalence of racist language in discussions of predatory publishing

Here are two useful casual reads more related to the tech industry:

GitHub plans to replace racially insensitive terms like ‘master’ and ‘whitelist’
Linux team approves new terminology, bans terms like 'blacklist' and 'slave'

Specifically for the RequestStack class, this would mean deprecating the getMasterRequest method in favor of getMainRequest, getRootRequest or similar.

Uh oh!

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions