-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
clean up use of word: just #26472
clean up use of word: just #26472
Conversation
kbhawkey
commented
Feb 11, 2021
- Created replacement text for the word "just" (mostly single word substitutions or removals).
- Left some instances in place.
- Related to Remove insensitive wordings from the docs like just - easy or - simple #17070.
/kind cleanup |
Deploy preview for kubernetes-io-master-staging ready! Built with commit 3ff5ec1 https://deploy-preview-26472--kubernetes-io-master-staging.netlify.app |
LGTM on the kubeadm changes. |
@@ -209,7 +209,7 @@ would have failed due to conflicting ownership. | |||
|
|||
The merging strategy, implemented with Server Side Apply, provides a generally | |||
more stable object lifecycle. Server Side Apply tries to merge fields based on | |||
the fact who manages them instead of overruling just based on values. This way | |||
which objects manage them instead of overruling based on values. This way |
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.
@apelisse .
Would you have time to clarify this sentence? I'd like to replace "the fact who manges" and "just based":
Server Side Apply tries to merge fields based on
the objects managing the fields instead of overruling fields based only on values.
or
Server Side Apply tries to merge fields based on
which objects manage the fields instead of overruling based on values.
or
Server Side Apply tries to merge fields based on
ownership of the fields instead of overruling fields based on values.
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.
Thanks for looking at this, I'm not even sure I fully understand what's meant here :-)
We've spent some time finding the right words for these concepts. In general, we consider fields to be "managed" by "managers". To avoid the repetition, "actors" is also a good option. We used "owned/owners" in the past (as well as workflows but not so much) but we've tried to remove occurrences of these from the code-base.
Server Side Apply tries to merge fields based on the actor who manages them instead of overruling based on values.
EDIT: Removed the just ;-)
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.
Thanks for reviewing!
When this isn't WIP I'll be happy to approve it, based on the PR description. |
7305ddb
to
3515d4c
Compare
Awesome work @kbhawkey! Rebase it and I'll merge. |
3515d4c
to
3ff5ec1
Compare
/lgtm |
LGTM label has been added. Git tree hash: 195ece4c6908d5355d302841cc70485f4d2de748
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |