• Daniyar Kylyzhov

Google introduces mandatory inclusive terminology in all of its open-source projects


On November 10, 2020, Google announced the mandatory introduction of inclusive terminology in all open projects in which the company's specialists participate in the framework of the Google Open Source Programs Office ( OSPO ) programs. This initiative also applies to all open source projects that are used internally by Google.



Google explained that from October 2020, all new projects will be required to use inclusive terminology, and from 2021, the company's specialists will implement it in existing open OSPO projects, including TensorFlow, IoN, WebRTC. Flutter, V8, Magenta, Go, Dart, and others. Corrections to production code will be made provided they do not break backward compatibility.


Developers should no longer use the offensive terms slave, whitelist, blacklist, and graylist. Instead, use alternative neutral terms such as worker or replica, allowlist, trust list, safelist, and also blocklist, denylist, exclude list, based on context.



Google released recommendations for developers to create documentation using inclusive terminology. In it, the company advises to avoid correspondence, communication, and design of projects of offensive and offensive terms, such as crazy (crazy), insane (crazy), blind (blind), cripple (cripple), and dumb (dumb). Instead of these terms, you need to write simpler and more understandable words, for example, instead of the phrase "there are crazy samples in this data", it is better to write "there are several incomprehensible samples in the data."


Also, these guidelines address the issue of gender uniformity - you cannot write man-hours (man-hours) - you need to write person-hours (man-hours).



Google emphasizes in its recommendations to avoid violence, threats, and unnecessarily violent terms and abbreviations in the text, for example, you can no longer write the phrase "Shoot The Other Node In The Head".


If the developer cannot get away from the not recommended terms, then he should write them in a more vague form, use a different font for offensive words, highlight them in the code in quotes, and show that they are, as it were, removed from the text.


In addition, Google recommends not using the terms normal and healthy in the documentation to define people without disabilities, but rather write the phrase non-disabled person (employee without disabilities) so as not to offend people with disabilities.



Last August, Google introduced a new rule for mailing lists - "Google is out of politics". Employees are prohibited from making statements that “insult or demean” other employees, contractors, business partners, or others. The rules also prohibit participation in "raging debate over politics or the latest news story".


#Google #Replacement #Terms #OSPO #IT #OpenSource #Master

13 views0 comments

Ads

Ads

FYBERUS

  • Facebook
  • Twitter
  • Instagram

Copyright © 2020 Fyberus WebSite. A Fyberus. All rights reserved. Reproduction in whole or in part without permission is prohibited.