Skip to content
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

Open
pstack2021 opened this issue Nov 3, 2022 · 6 comments
Assignees

Comments

@pstack2021
Copy link
Contributor

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

@michaelklishin
Copy link
Member

The CLI part of this will ship in 3.11.4.
We decided to not change the internally used names as they will go away after 4.0 because so will classic mirrored queues and related features.

@michaelklishin
Copy link
Member

Hmm, rabbitmq-plugins commands would still need updating even then.

@pstack2021
Copy link
Contributor Author

The CLI part of this will ship in 3.11.4. We decided to not change the internally used names as they will go away after 4.0 because so will classic mirrored queues and related features.

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.
Many thanks,
Paula.

@michaelklishin
Copy link
Member

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.

@pstack2021
Copy link
Contributor Author

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?

@michaelklishin
Copy link
Member

@pstack2021 yup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants