-
Notifications
You must be signed in to change notification settings - Fork 898
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
Re-worded "Ansible Automation Inside" to "Embedded Ansible" for standardisation #19081
Re-worded "Ansible Automation Inside" to "Embedded Ansible" for standardisation #19081
Conversation
@miq-bot add_label ivanchuk/yes |
Checked commit pemcg@6724fa4 with ruby 2.4.6, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me, and I am all for it. 👍
I am not a marking person, so if someone with more clout thinks differently, then they have priority. But to me, I am all for reducing duplicate terminology. Thanks for the PR!
Same from me. @Fryguy do you think anyone will care if we change these terms? |
I never liked the other term and the split terminology is frustrating, so I am +1 for this. |
Re-worded "Ansible Automation Inside" to "Embedded Ansible" for standardisation (cherry picked from commit 400b3a3) https://bugzilla.redhat.com/show_bug.cgi?id=1734906
Ivanchuk backport details:
|
Although the marketing term for Embedded Ansible is (was?) "Ansible Automation Inside", all references to the feature in the project and product mention "Embedded Ansible", for example the server role, and all related object types. Having pop-up notifications that mention "Ansible Automation Inside" is non-standard and confusing.
This PR standardises the text to "Embedded Ansible" and implements https://bugzilla.redhat.com/show_bug.cgi?id=1734906