-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Adjust German style guide for inclusive speech & check translated docs #5043
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Hi all, per the recommendation, please feel free to update to use "control plane" when you are ready. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Not sure if it is best placed here or at kubernetes/website.
Issue 1
The German language is in most cases ether using a masculine or feminine ending of a word.
Small example:
As shown above, in DE we can't express a role, person, job etc. in a neutral way.
ToDos:
I don't expect that we use person-oriented sentences in too many places and is most likely in the community/contribution area focused. Even more, it is important to be inclusive.
Issue 2
Check for master/slave terminology and align with the list of harmful words.
Potentially we have to do this for Germany too and write a list of harmful words.
ToDos:
cc'ed Jim as we should keep this topic in mind for kubernetes/website#22960
/cc @jimangel @rlenferink @bene2k1
/wg naming
The text was updated successfully, but these errors were encountered: