Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inclusive language check - expanded list of terms #44

Open
ajeanmahoney opened this issue Oct 29, 2024 · 2 comments
Open

Inclusive language check - expanded list of terms #44

ajeanmahoney opened this issue Oct 29, 2024 · 2 comments
Assignees

Comments

@ajeanmahoney
Copy link
Collaborator

ajeanmahoney commented Oct 29, 2024

See inclusive_script.txt for a list of items our script currently checks for. These terms should be added to the list that DraftForge currently checks.

@NGPixel
Copy link
Member

NGPixel commented Jan 28, 2025

The current implementation provides alternatives as suggestions for each matched term:

{
    triggers: ['whitelist'],
    suggestion: 'allowlist or passlist'
  },
  {
    triggers: ['blacklist'],
    suggestion: 'denylist or blocklist'
  },
  {
    triggers: ['master'],
    suggestion: 'primary, main, host, leader or orchestrator'
  },
  {
    triggers: ['slave'],
    suggestion: 'secondary, replica, target, follower or worker'
  },
  {
    triggers: ['native'],
    suggestion: 'built-in'
  },
  {
    triggers: ['grandfather'],
    suggestion: 'exemption or approve'
  },
  {
    triggers: ['he/she', 'he or she'],
    suggestion: 'they'
  },
  {
    triggers: ['cripple', 'handicap'],
    suggestion: 'impair or impeded'
  }

Do you want to provide alternatives for the terms in the txt file? Or should a different function just match these extra terms without providing suggestions?

@ajeanmahoney
Copy link
Collaborator Author

The RPC doesn't update any terms that are flagged, we just pass them along to authors with the following question:

<!-- [rfced] Please review the "Inclusive Language" portion of the online 
Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
and let us know if any changes are needed.  Updates of this nature typically
result in more precise language, which is helpful for readers.

[[ If the script flags some questionable terms or phrases, add:

For example, please consider whether the following should be updated: 
term A, term B, term C, etc.
]]

[[ If script flags any form of "tradition", frame as a clarity issue:

In addition, please consider whether "tradition" should be updated for clarity.  
While the NIST website 
<https://www.nist.gov/nist-research-library/nist-technical-series-publications-author-instructions#table1> 
indicates that this term is potentially biased, it is also ambiguous.  
"Tradition" is a subjective term, as it is not the same for everyone.
]]
-->

DraftForge doesn't need to provide alternatives to the RPC editors, and the editors don't provide alternatives to the authors unless they explicitly ask for suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants