From: matz@... Date: 2021-04-26T22:47:06+00:00 Subject: [ruby-core:103607] [Ruby master Misc#17828] Deprecate use of master and slave Issue #17828 has been updated by matz (Yukihiro Matsumoto). As basic principles: * I think `master` without corresponding `slave` is still OK (e.g. `master` branch in git). * compatibility is more important than political correctness, so we are not going to **change** any API, for example, `Socket::IFF_SLAVE`. * when we might add replacements for `slave`, they should follow standard/convention of the platform (Linux/Unix does not provide replacement for `IFF_SLAVE` yet) * we are not going to modify the past history, so that `ChangeLog` and past documents should be kept as they are. Following those principles, we can only change some variable names in `ext/pty` code & docuement at most. Matz. ---------------------------------------- Misc #17828: Deprecate use of master and slave https://bugs.ruby-lang.org/issues/17828#change-91702 * Author: yyoshida.at.work@gmail.com (Yasuhiro Yoshida) * Status: Open * Priority: Normal ---------------------------------------- In light of organizations like Basecamp and GitHub refraining from using words like "master" and "slave," it may be a good time for Ruby Core team to follow the practices. I also feel that this issue has been discussed before, and there may already be plans in place as it's a nice thing to do and there is a lot to cover that may require concerted efforts by the whole team. It would be nice if I could learn them and maybe contribute to the task. For now, I am thinking maybe I can start working on most of the documentations, comments, and even tests that have the terminology but wouldn't affect the code that is run in production. -- https://bugs.ruby-lang.org/ Unsubscribe: