Inclusive language/cs

Chceme podporovat kulturu inkluzivity a součástí toho je zajistit, abychom tam, kde je to možné, používali vhodný jazyk.

I když někteří lidé mohou namítat, že tato slova pro ně nejsou urážlivá nebo že tato slova nebyla nikdy přidána s urážlivým záměrem, musí si být vědomi toho, že tato slova mohou být potenciálně urážlivá pro jiné skupiny lidí, a měli bychom se snažit je odstranit. zvyklosti.

Toto úsilí také pomáhá splnit náš závazek :

"V zájmu podpory otevřené a vstřícné komunity jsme odhodláni učinit účast na technických projektech Wikimedie s respektem a bez obtěžování pro každého [...]"



Termíny, kterým je třeba se vyhnout, a jejich alternativy
Následující seznam je neúplný. See the #Resources section below for other recommendations. We use different alternative words in different contexts, for better grammatical or technical accuracy.

It is noted that there are some cases where we may not be able to change/remove some of our usages of these words, such as until the upstream developers has fixed them and it trickles down into our deployed software. This is okay as it is out of our control. It could be worth checking with the upstream if they plan to fix similar issues in their own codebases. However, we can and should address these words in our codebases when we are able to.

How to help
If you're looking to help with this effort, is a good starting point for some discussion around the issue, and also to find specific tasks for areas of code that needs updating.

Some of these may be as simple as updating/improving comments and variable names.

Others may be more complex and need functions and hooks renaming, while following our.

Some usages may need to stay around for longer, but will generally stop being the canonical code, showing the intention for this to be removed in the near future.

Resources

 * Other organisations' related guidelines and documentation (via cdanis and ietf which list many more)
 * American Chemical Society Inclusivity Style Guide
 * Android Open Source Project's "Coding with Respect"
 * Apple's Style Guide - (section on inclusive language, entry on master/slave, entry on blacklist/whitelist)
 * Bluetooth SIG's "Appropriate Language Mapping Tables"
 * Chromium's "Inclusive Code" document
 * Google's "Writing Inclusive Documentation"
 * Google's "Developer documentation style guide word list"
 * Internet Engineering Task Force:
 * Terminology, Power, and Inclusive Language in Internet-Drafts and RFCs (draft v.4)
 * Inclusive terminology in IETF Documents (work in progress)
 * Microsoft's "Bias-free communication" document
 * Twitter Engineering
 * W3C Manual of Style
 * Inclusive Naming Initiative
 * https://www.writethedocs.org/guide/writing/reducing-bias/
 * Woke, a non-inclusive language detection tool
 * Digital Journalism Style Guide of Inclusive Language - Language Please