-
Notifications
You must be signed in to change notification settings - Fork 945
Add WG Checkpoint Restore mailing lists #8762
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
Conversation
d5731fa to
4ac1f4a
Compare
4ac1f4a to
238e16e
Compare
|
do you have examples of having multiple emails per person for one of these lists? it doesn't seem typical to me and I'm not sure if there's some policy around it /lgtm |
238e16e to
538d1df
Compare
|
@haircommander I've updated the patch to use one email per person. |
Signed-off-by: Radostin Stoyanov <[email protected]>
538d1df to
a1dc7f0
Compare
|
/approve |
|
/approve |
Yes this is fine, for example multiple steering members (including myself) have a personal email included in the steering lists for reasons like employer google docs restrictions I'm not aware of any policy prohibiting it. At some point we might want to drive leads type lists from the central source of truth in kubernetes/community sigs.yaml, but I don't know anyone planning to work on this and if/when that happens there will be other cases like this. |
BenTheElder
left a comment
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.
/lgtm
/approve
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adrianreber, BenTheElder, hakman, rst0git, viktoriaas 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 |
|
/retest |
Reference: kubernetes/community#8508