This issue is related to offensive terminology being used in the buildbot repository. This submitted issue seeks to eliminate all usage of master and slave terminology from this repository along with any official reference documentation.
Background
To be more inclusive in the technical realm, repositories should not have any offensive or oppressive terminology. As of 2020, Python, Git, and Go have started these transitions in separate initiatives. Despite some perspectives that changing naming conventions to be "politically correct" is unnecessary or over-the-top, coding and language does not live in a bubble. We must to take into consideration the historical contexts of words and phrases we use. The Go team released a statement, specifically related to whitelist and blacklist, which can be applied to the why having an inclusive standard is important:
There's been plenty of discussion on the usage of these terms in tech. I'm not trying to have yet another debate. It's clear that there are people who are hurt by them 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.
Furthermore, practically changes eliminating offensive terminology can improve communication by being more explicit (e.g. whitelist vs blacklist → allowlist to blocklist). Thus, easier understanding.
Given all coders want to work in an environment that is conducive for all people to feel comfortable, we should make these changes here in this repo.
Note from maintainers
We believe those kind of issue are kind of controversial, so we'll start by linking to Buildbot's code of conduct. Please follow it in your answers.
This issue is related to offensive terminology being used in the
buildbotrepository. This submitted issue seeks to eliminate all usage of master and slave terminology from this repository along with any official reference documentation.Background
To be more inclusive in the technical realm, repositories should not have any offensive or oppressive terminology. As of 2020, Python, Git, and Go have started these transitions in separate initiatives. Despite some perspectives that changing naming conventions to be "politically correct" is unnecessary or over-the-top, coding and language does not live in a bubble. We must to take into consideration the historical contexts of words and phrases we use. The Go team released a statement, specifically related to whitelist and blacklist, which can be applied to the why having an inclusive standard is important:
Furthermore, practically changes eliminating offensive terminology can improve communication by being more explicit (e.g. whitelist vs blacklist → allowlist to blocklist). Thus, easier understanding.
Given all coders want to work in an environment that is conducive for all people to feel comfortable, we should make these changes here in this repo.
Note from maintainers
We believe those kind of issue are kind of controversial, so we'll start by linking to Buildbot's code of conduct. Please follow it in your answers.