-
Notifications
You must be signed in to change notification settings - Fork 727
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
Phase 2 - Make updates for Inclusive Language in OSS RabbitMQ Docs - Update Code instances, then update docs #1551
Comments
The CLI part of this will ship in 3.11.4. |
Hmm, |
Hi @michaelklishin can you expand it a bit more on what you mean by this? In Summary, are you saying the OSS RabbitMQ 4.0 release will handle a lot of these inclusive language updates by default due to the fact that the internally used names will "go away" then as will CMQ and related features. What do you mean by "go away" above, are they simply being removed/replaced/renamed? We probably need an open issue to check/verify the state of inclusive language on the OSS doc site after the above has happened to see if there are additional updates we need to make in code that haven't been covered by the above?? Please let me know your thoughts. |
In 4.0, classic mirrored queues will be removed (classic unmirrored queues will not), and so on will all the unfortunate terminology they use. All of those are internal changes. When 3.12 ships we should be able to switch all CLI examples that mention "slaves" to use "mirrors" because of #6399. |
ok thanks @michaelklishin so we probably need to do an assessment after 3.12 and 4.0 ships to check what is left with regard to code updates for inclusive language, agree? |
@pstack2021 yup |
Make terminology changes for inclusive language in code instances. When the code updates are complete, update the RabbitMQ OSS docs to reflect these changes.
The details of the changes that need to happen are here: https://source.vmware.com/portal/pages/global-marketing/terminology-changes
The list of changes that need to happen in the code are tracked in this google doc which I composed when I was completing the PHASE 1 updates, I have shared this doc with @michaelklishin @acogoluegnes, and @dyozie.
For more details of the PHASE 1 part of the project which is now complete, see #1502
The text was updated successfully, but these errors were encountered: