Do people really get offended or scared away if they read the word
"master" in a harmless context like "master document" or "master
revision"? Hard to believe for me but you are right that I am not concerned.
Maybe we should better hear what concerned people have to say.
Technically, getting rid of the word will definetely not be a simple
search-replace activity if you look closely... The word has many
meanings and you need to change it with regard to the context it is used
with.
Furthermore, a lot of findings are in context with fop
(<fo:simple-page-master master-name="back-first" ... ), which has to be
changed before we can change anything there.
Thanks,
Michael
Am 01.02.21 um 08:59 schrieb Benjamin Jugl:
Hi,
I would advise to review. Sure the word "master" has many meanings,
but we are not talking meaning, we are talking connotation here. And
it is not our place to say if we find it offensive, because we are not
in any position to do so.
As many US companies do this shift, I think we should also do so. They
should know best, because they are closer to the issue and have more
insight into connotation and the rest of the debate, than us.
After all it should only take a mindfully overlooked search-replace
routine, to complete this task. And it would be a shame, if we scared
of users, just because we were to reluctant to do so.
Benjamin Jugl
ecomify GmbH - www.ecomify.de <http://www.ecomify.de>
Am 30.01.21 um 20:36 schrieb Michael Brohl:
Hi Jacques,
if not used in a context with 'slave', I don't see any problem using
the word 'master'.
It's word with many different meanings in English and I do not see
any sense in changing all occurences per se.
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 30.01.21 um 10:52 schrieb Jacques Le Roux:
Hi,
After a discussion between ASF members, I saw that an effort has
been done by Infra, and I guess in some TLPs, to replace some
connoted words like blacklist and whitelist.
We have not much occurrences of these words, so I suggest that we
replace blacklist and whitelist list respectively by denylist and
allowlist as suggested by
https://english.stackexchange.com/questions/51088/alternative-terms-to-blacklist-and-whitelist#answer-51104
There is also this article:
https://developer-tech.com/news/2020/jun/15/github-replace-slavery-terms-master-whitelist/
We have only 1 occurrence of slave in our own code, that would be
easy. For master it's more annoying 1771 occurrences, so that would
need a review.
What do you think?
Jacques