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

Renamed files, directories, and replaced non-inclusive text #648

Closed
wants to merge 2 commits into from

Conversation

jwstein3400
Copy link

Made use of more inclusive terminology in place of the bias jargon.
This change has no impact on any functionality. The intention to simply swap out static text.

Resolves #647

Made use of more inclusive terminology in place of the bias jargon.
This change should have no impact on any functionality. This change
is intended to simply swap out static text.

Resolves 647
@jwstein3400 jwstein3400 marked this pull request as ready for review December 2, 2020 06:09
Copy link
Contributor

@KOLANICH KOLANICH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. blocklist is not a very correct term. The things that are in blacklists are not technically blocked in bandit.
  2. replacing master ... do you thing M. of Sc. degree should also be renamed?

Overall:

  1. It is the campaign of replacement of neutral terms with the words white and black racist (we in Russia have an idiom that can literaly be translated into English as "the thief has his hat burning", usually attributed to a folk story about an improvised guilty-knowledge test to detect thieves at market and meaning the situation when someone socially inacceptable (i.e. the thief from the story) trying to play innocent (in the story it'd be to just ignore the scream, rather that touching the hat) but fails because he is a bad actor), not the words being replaced.
  2. About the word master, it again has multiple meanings, owner of slaves is only one of them.

Copy link
Member

@ericwb ericwb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This breaks backward compatibility. Users may already be using blacklist in a automated command line or custom config file. It needs to handle both new and old terminology.

Also, there is a duplicate, earlier, and competing PR: #627

@ericwb
Copy link
Member

ericwb commented Dec 30, 2024

No activity on this PR in quite a while. Closing for now.

@ericwb ericwb closed this Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inclusive terminology
3 participants