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

Promote Claudiu Belu to SIG-Windows tech lead #6045

Closed
14 of 16 tasks
marosset opened this issue Sep 22, 2021 · 5 comments
Closed
14 of 16 tasks

Promote Claudiu Belu to SIG-Windows tech lead #6045

marosset opened this issue Sep 22, 2021 · 5 comments
Assignees
Labels
sig/windows Categorizes an issue or PR as relevant to SIG Windows.

Comments

@marosset
Copy link
Contributor

marosset commented Sep 22, 2021

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

      • 1-2 lines about why they are being nominated
      • contacts to privately reach out to for questions (current leads)
        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

    • are a Kubernetes GitHub org [member]
    • have completed the [Inclusive Open Source Community Orientation course]
  • Once lazy consensus has been achieved, update the following
    files in the respective repos:

    • [kubernetes/community]: [sigs.yaml] and use the [generator doc]
      to update README.md and OWNERS_ALIASES files
    • [kubernetes/org]: OWNERS_ALIASES, [milestone-maintainers team],
      kubernetes and kubernetes-sigs [team configs]
    • [kubernetes/enhancements]: OWNERS_ALIASES
  • Update all communication properties used by the community group.
    See [sig-wg-lifecycle.md] for details.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 22, 2021
@marosset
Copy link
Contributor Author

/sig windows
/assign

@k8s-ci-robot k8s-ci-robot added sig/windows Categorizes an issue or PR as relevant to SIG Windows. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 22, 2021
@jsturtevant
Copy link
Contributor

Thanks for all the contributions to the sig @ddebroy! Congrats to @claudiubelu 🎉

@marosset
Copy link
Contributor Author

/close

Thanks again @ddebroy for all your contributions and congratulations @claudiubelu!

@k8s-ci-robot
Copy link
Contributor

@marosset: Closing this issue.

In response to this:

/close

Thanks again @ddebroy for all your contributions and congratulations @claudiubelu!

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.

@claudiubelu
Copy link
Contributor

claudiubelu added a commit to claudiubelu/k8s.io that referenced this issue Oct 13, 2021
Was promoted to sig-windows tech lead: kubernetes/community#6045
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/windows Categorizes an issue or PR as relevant to SIG Windows.
Projects
None yet
Development

No branches or pull requests

4 participants