All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "ito-yuichi@fujitsu.com" <ito-yuichi@fujitsu.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] cve-check: Add allowlist that is same function of whitelist.
Date: Sat, 26 Jun 2021 11:04:27 +0100	[thread overview]
Message-ID: <b7b05b428677e6d8f39c700ff4ce212a9baa8918.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210623085633.3186982-1-ito-yuichi@fujitsu.com>

On Wed, 2021-06-23 at 17:56 +0900, ito-yuichi@fujitsu.com wrote:
> The Linux team plan to removed references to racially-charged jargon from
> their code for more neutral and inclusive language.
> So replace use of "whitelist" with "allowlist" in cve-check.
> 
> First, we add CVE_CHECK_ALLOWLIST and it is considered patched as well as
> CVE_CHECK_WHITELIST.
> We plan to replace about other word later and eventualy, replace all
> "whitelist" to "allowlist".
> 
> Signed-off-by: Yuichi Ito <ito-yuichi@fujitsu.com>

The TSC did discuss this and proposed a plan on how we should go about 
addressing these issues:

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

I appreciate this patch has good intent but I would really like to
see a wider plan on how we address this rather than changing single 
variables piecemeal. 

For example we may want to standardise on the term "IGNORE" rather than
"ALLOW" or even "FILTER" or "VERIFIED" or something more specific to the meaning
of CVEs and CVE checking.

There is an opportunity to try and make the metadata and variable names
more consistent and understandable but if we just change single things at
a time this opportunity would be missed.

Cheers,

Richard


  reply	other threads:[~2021-06-26 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23  8:56 [PATCH] cve-check: Add allowlist that is same function of whitelist ito-yuichi
2021-06-26 10:04 ` Richard Purdie [this message]
2021-06-29  6:47   ` [OE-core] " ito-yuichi
2021-07-05 19:08   ` Armin Kuster
2021-07-20  6:48     ` ito-yuichi
2021-07-26  8:28       ` ito-yuichi
2021-08-06  8:38       ` ito-yuichi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b7b05b428677e6d8f39c700ff4ce212a9baa8918.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=ito-yuichi@fujitsu.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.