- [oe] [OE-core] Inclusive Language Proposal for YP/OE
Re: [oe] [OE-core] Inclusive Language Proposal for YP/OE
toggle quoted messageShow quoted text
From: openembedded-core@... <openembedded-
core@...> On Behalf Of Enrico Scholz via
Sent: Friday, February 4, 2022 9:16 AM
To: Alexander Kanavin <alex.kanavin@...>
Cc: Jon Mason <jdmason@...>; Yocto-mailing-list
<yocto@...>; Patches and discussions about the oe-core
layer <openembedded-core@...>; OpenEmbedded
Devel List <openembedded-devel@...>
Subject: Re: [oe] [OE-core] Inclusive Language Proposal for YP/OE
Alexander Kanavin <alex.kanavin@...> writes:
For BB_DISKMON_DIRS, the actions "ABORT, STOPTASKS and WARN"
Yes; these are terms. But it should be possible to understand the meaning of
I'm not taking a stand here, but just providing the context for where
become "HALT, NO_NEW_TASKS and "WARN".I am not an native english speaker, but for "HALT" I will have to
think twice whether it will pause the operation or abort it. I would
stay at "ABORT" because it makes much more clear what happens.
the push for avoidance of 'abort' comes from:
Keep in mind that for non-native english speakers none of these words
are emotionally charged; they're just terms.
these terms without using a special "inclusivenaming"
dictionary. Else, we could just use "A", "B" and "C" for the actions above and
explain these "terms" in some documentation later.
Would CANCEL be clearer to you than HALT?
BB_HASHCONFIG_WHITELIST -> BB_HASHCONFIG_IGNORE_VARS
It is bad when a context is required to understand the meaning of a variable.
I'd say the context should make it clear that they are lists
BB_HASHBASE_WHITELIST -> BB_BASEHASH_IGNORE_VARSThe new variable names sound like boolean flags, not like lists.
MULTI_PROVIDER_WHITELIST -> BB_MULTI_PROVIDER_ALLOWED
And where do you see a context when local.conf contains
| BB_HASHCONFIG_IGNORE_VARS = "true"
Would BB_HASHCONFIG_IGNORELIST or BB_HASHCONFIG_ALLOWEDLIST make more sense to you?
Join email@example.com to automatically receive all group messages.