About

• Version: 1.3

• Creation date: 11/25/2020

• One line description: Modern word choice for terminology that is friendly for everyone

• Author(s): Mark Himelstein

Background

Historical word choice is no longer considered acceptable so we need to change some existing terminology in RISC-V documentation (created and owned) as well as future documentation.

Details

Employ  inclusive and friendly terminology.

1. The RISC-V Foundation, like the Linux Foundation, will use the Inclusive Naming Initiative (link) for wordlists, actions, and recommended replacements.

2. When found, we should go back and remove terms that are not inclusive. 

3. Changes should be made as soon as reasonably possible to existing documents.

4. Members can report language that needs to change to help@riscv.org at any time.

5. Use the RISC-V RISC-V Help Tickets hosted in GitHub (https://help.riscv.org)  to keep track of needed changes. Set Goal dates for completion in the issue.

6. RISC-V staff will address any necessary items  in the Chairs meeting monthly (and as appropriate to the TSC and BOD)

7. New specifications are reviewed during the Freeze and Ratification-Ready milestone work in the Status Checklist.

Exception handling

None allowed for RISC-V specifications.

When RISC-V members collaborate with third-party projects or reference third-party specifications with non-friendly terminology, these references may not be avoidable but should be used sparingly.

Should the Inclusive Naming Initiative recommended replacements not meet the needs of the RISC-V environment, alternatives should be raised to the Architecture Review Committee to receive a request and make a decision.

Additional words and replacement terms should be documented here when decided:

Version History