public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Teng, Lynn L" <Lynn.L.Teng@Intel.com>
To: "rfc@edk2.groups.io" <rfc@edk2.groups.io>
Cc: "announce@edk2.groups.io" <announce@edk2.groups.io>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"discuss@edk2.groups.io" <discuss@edk2.groups.io>
Subject: Inclusive Language Update RFC
Date: Wed, 17 Nov 2021 18:46:45 +0000	[thread overview]
Message-ID: <SJ0PR11MB4975DA742D2769D439787E6FAE9A9@SJ0PR11MB4975.namprd11.prod.outlook.com> (raw)

Hello all,

We have updated the Overview section of the Inclusive Language Guidelines to clarify two things.  
1. Which version (via date) of the [[UEFI Inclusive Language Implementation Guidelines|https://uefi.org/sites/default/files/resources/UEFI_Inclusive%20Language.pdf]] we will be following so we do not have a moving target.  
2. Defining "_non-legacy_" and "_legacy_".  

***

## Overview
 
To promote a more inclusive and open ecosystem, TianoCore is dedicated to removing archaic terminology that holds negative connotation.
In collaboration with UEFI, we will be following the same [[Inclusive Language Implementation Guidelines|https://uefi.org/sites/default/files/resources/UEFI_Inclusive%20Language.pdf]] (as of Nov 1, 2021) as stated on [[UEFI.org|https://uefi.org/]].

In our plan below, we have steps for dealing with both "_non-legacy_" and "_legacy_".  For these terms we define "_non-legacy_" as UEFI BIOS/specifications and beyond, where as "_legacy_" is BIOS/specifications that predates UEFI.  There are references to legacy specifications not controlled by the TianoCore Community, and they may not follow these guidelines. In order to preserve compatibility for code that reads on legacy specifications, particularly where that specification is no longer under maintenance or development, language in this specification may appear out of sync with the guidelines. In these cases, the Community will work with other standards development bodies to eliminate such examples over time. In the meanwhile, by acknowledging and calling attention to this issue the hope is to promote discussion and action towards more complete use of Inclusive Language reflective of the diverse and innovative population of the technical community that works on standards.

 
 ## Plan
    
1. Announcement of intent, and all check-ins from here onwards will need to abide by Inclusive Language Implementation Guidelines  
2. Scrubbing of all comments, documentation, and Wiki pages  
3. Scrubbing of all non-legacy code  
4. Working with UEFI to scrub legacy code  
    
    
 ## Implementation Guidelines
    
 ### Master/Slave to not be used together nor alone.
 Alternatives:
 Master | Slave
 -------|-------
 Main | Secondary, Subordinate
 Primary | Secondary, Replica
 Host | Target
 Leader | Follower
 Orchestrator | Worker
 Initiator | Responder
 
 Or similar descriptive terminology
    
 ### Blacklist/Whitelist to not be used together nor alone.
 Alternatives:
 Blacklist | Whitelist
 ----------|----------
 Blocklist | Passlist
 Denylist | Allowlist
 Refused, Denied | Permitted
 
 Or similar descriptive terminology

***

Please provide any input you may have with regards to these changes by Nov 26th.

Thank you,  
Lynn Teng

                 reply	other threads:[~2021-11-17 18:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-list 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=SJ0PR11MB4975DA742D2769D439787E6FAE9A9@SJ0PR11MB4975.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox