-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Promote Claudiu Belu to SIG-Windows tech lead #6045
Comments
/sig windows |
Thanks for all the contributions to the sig @ddebroy! Congrats to @claudiubelu 🎉 |
/close Thanks again @ddebroy for all your contributions and congratulations @claudiubelu! |
@marosset: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Regarding the Inclusive Open Source Community Orientation course, I have completed it a few months ago: https://ti-user-certificates.s3.amazonaws.com/e0df7fbf-a057-42af-8a1f-590912be5460/fc599ad6-3831-44b0-9359-cfb3f0455613-claudiu-belu-the-inclusive-speaker-orientation-lfc101-certificate.pdf |
Was promoted to sig-windows tech lead: kubernetes/community#6045
Instructions from https://github.com/kubernetes/community/blob/master/contributors/chairs-and-techleads/leadership-changes.md
@ddebroy is stepping down as techlead for SIG Windows and @claudiubelu is being promoted the techlead for SIG Windows
/cc @jayunit100 @jsturtevant
This was discussed May 4th, 2021 SIG-Windows community meeting.
https://groups.google.com/g/kubernetes-sig-windows/c/FCkIz9TLMAc
(I went on parental leave shortly after the announcement and then making the actual leadership changes got dropped :( )
Discuss the proposed changes with the current leadership.
Send an email to the SIG/WG/UG mailing list and cc the [kubernetes-dev]
mailing list. At a minimum, the email should contain:
intent to step down as the current lead
if nominating another lead
or concerns (current leads + [steering-private]) about the nomination
if this was discussed in a meeting, link to meeting notes
lazy consensus deadline of at least one week
If nominating another lead, ensure that they
Once lazy consensus has been achieved, update the following
files in the respective repos:
sigs.yaml
] and use the [generator doc]to update
README.md
andOWNERS_ALIASES
filesOWNERS_ALIASES
, [milestone-maintainers team],kubernetes and kubernetes-sigs [team configs]
OWNERS_ALIASES
Update all communication properties used by the community group.
See [sig-wg-lifecycle.md] for details.
The text was updated successfully, but these errors were encountered: