-
Notifications
You must be signed in to change notification settings - Fork 107
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
Eliminate non-inclusive language #546
Comments
AFAIK, @ffmancera is working on the conscious language in NM side. For the non-inclusive language relied on the NM side, I will coordinate with Fernando to properly address this. Thanks for reporting the issue. |
Looks like many of these issues will be solved by adding https://github.com/linux-system-roles/network/blob/main/.mdl_style.rb#L2 etc. Use of the word "dummy" appears in many names of test devices, variables, and some files. These will preferably be renamed. However, it does appear to be used as an NM keyword, so we'll have to add a wokeignore comment for those uses. |
@liangwen12year, @richm, could you please take a look at this PR? |
#551 is merged. |
Hello, we have a project to eliminate non-inclusive language from the linux-system-roles.
Running a utility woke (now it's supported in tox. please install the latest tox-lsr and run tox -e woke), two non-inclusive words are reported - dummy, whitelist, blacklist, master, and slave.
Can we replace them with more appropriate words? We are worried some of the words are coming from the network subsystems themselves that the network role depends upon. I'd think "eliminating non-inclusive language" is a common project among us including the subsystems. How are they solving the issue? If the network subsystems are already working on them, we could follow their effort.
Can we ask you to share the network team's policy on this matter with us? Thanks!
The text was updated successfully, but these errors were encountered: