Inclusive language/ja

私たちは包括的な文化を促進することを望んでおり、その一環として、できる限り適切な言葉を使用するようにすることが重要です.

一部の人々は、これらの言葉が彼らにとって不快でないと主張するか、またはこれらの言葉が不快な意図で追加されたわけではないと主張するかもしれませんが、これらの言葉が他のグループの人々にとって潜在的に不快であることを認識する必要があり、使用を避けるよう努めるべきです.

この取り組みはまた、私たちの への取り組みの一環でもあります:

"ウィキメディア技術プロジェクトへの参加を、誰にとっても敬意を持って、嫌がらせのない経験にするために、私たちは開かれた、歓迎的なコミュニティを育成することを目的としています [...]"

Terms to avoid and their alternatives
The following list is incomplete. 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