Hello all,

The Yocto Project TSC has created a wiki page to start making notes of
offending names and possible replacements. At some point, this wiki page
should include a plan on moving forward.  Our hope is this will help
streamline the process when folks send patches to replace offending
language.
Everyone is welcome to find and make note of any offending names in the
tables on the wiki to help scope out this effort.

https://wiki.yoctoproject.org/wiki/Inclusive_language

see
https://lists.openembedded.org/g/openembedded-architecture/topic/inclusive_language_summary/75821819 
for background.

regards,
Armin
On behalf of The Yocto Project TSC.

On 7/7/21 7:30 AM, Armin Kuster wrote:

Hello all,

The Yocto Project TSC has created a wiki page to start making notes of
offending names and possible replacements. At some point, this wiki page
should include a plan on moving forward.  Our hope is this will help
streamline the process when folks send patches to replace offending
language.
Everyone is welcome to find and make note of any offending names in the
tables on the wiki to help scope out this effort.

https://wiki.yoctoproject.org/wiki/Inclusive_language

In the variables table:

PNBLACKLIST, I'd prefer PNEXCLUDELIST, or PNBLOCKLIST. (I think exclude better
captures what it does.)

Confused, where it says current name is whitelist, suggested rename is
'excludelist', isn't that the exact opposite?

SSTATE_DUPWHITELIST, this is really a list of things to ignore. So my
suggestion is SSTATE_DUPIGNORELIST.

CVE_CHECK_PN_WHITELIST, I think there is a typo in the table for the replacement
(missing an L). But like the above, I think ignore is a better word then skip
here. So my suggestion would be CVE_CHECK_PN_IGNORELIST.

--Mark

see
https://lists.openembedded.org/g/openembedded-architecture/topic/inclusive_language_summary/75821819 
for background.

regards,
Armin
On behalf of The Yocto Project TSC.

On Wed, 2021-07-07 at 10:22 -0500, Mark Hatle wrote:

On 7/7/21 7:30 AM, Armin Kuster wrote:

Hello all,

The Yocto Project TSC has created a wiki page to start making notes of
offending names and possible replacements. At some point, this wiki page
should include a plan on moving forward.  Our hope is this will help
streamline the process when folks send patches to replace offending
language.
Everyone is welcome to find and make note of any offending names in the
tables on the wiki to help scope out this effort.

https://wiki.yoctoproject.org/wiki/Inclusive_language

In the variables table:

PNBLACKLIST, I'd prefer PNEXCLUDELIST, or PNBLOCKLIST. (I think exclude better
captures what it does.)

I'd note that it does actually raise "SkipRecipe" on the recipes in question so
SKIP may actually be more consistent and help with understanding in other code.

Cheers,

Richard

On Wed, Jul 7, 2021 at 7:16 PM Richard Purdie
<richard.purdie@...> wrote:

On Wed, 2021-07-07 at 10:22 -0500, Mark Hatle wrote:

On 7/7/21 7:30 AM, Armin Kuster wrote:

Hello all,

The Yocto Project TSC has created a wiki page to start making notes of
offending names and possible replacements. At some point, this wiki page
should include a plan on moving forward. Our hope is this will help
streamline the process when folks send patches to replace offending
language.
Everyone is welcome to find and make note of any offending names in the
tables on the wiki to help scope out this effort.

https://wiki.yoctoproject.org/wiki/Inclusive_language

In the variables table:

PNBLACKLIST, I'd prefer PNEXCLUDELIST, or PNBLOCKLIST. (I think exclude better
captures what it does.)

I'd note that it does actually raise "SkipRecipe" on the recipes in question so
SKIP may actually be more consistent and help with understanding in other code.

+1
I find the whole issue almost unbelievable but hey...
A.A.

Cheers,

Richard

Greetings,

On 7/7/21 5:22 PM, Mark Hatle wrote:

In the variables table:

PNBLACKLIST, I'd prefer PNEXCLUDELIST, or PNBLOCKLIST. (I think exclude better
captures what it does.)

Confused, where it says current name is whitelist, suggested rename is
'excludelist', isn't that the exact opposite?

SSTATE_DUPWHITELIST, this is really a list of things to ignore. So my
suggestion is SSTATE_DUPIGNORELIST.

CVE_CHECK_PN_WHITELIST, I think there is a typo in the table for the replacement
(missing an L). But like the above, I think ignore is a better word then skip
here. So my suggestion would be CVE_CHECK_PN_IGNORELIST.

Instead of "includelist" and "excludelist", what about just "includes"
and "excludes"? This terminology is already used in rsync's manual (for
example), and it seems lighter and clear enough.

For example, we could replace "CECC_USER_CLASS_BL" by
"ICECC_USER_CLASS_EXCLUDES" and "ICECC_USER_PACKAGE_BL"  by 
"ICECC_USER_PACKAGE_EXCLUDES".

Any thoughts? I mentioned this on the wiki page
(https://wiki.yoctoproject.org/wiki/Inclusive_language), but don't
hesitate to revert my edits.

Cheers,

Michael.

--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com