SIG API Machinery: Add Stefan as tech lead for sig-api-machinery

[deads2k]

SIG/WG name:

SIG API Machinery

Onboarding Lead(s):

sttts

Offboarding Lead(s):

None

Link to discussion:

Posted 3/14

Prerequisites for new leads:

• [X] Are a Kubernetes Org member
• [x] Have completed the Inclusive Open Source Community Orientation course

Onboarding / Offboarding tasks:

• [x] Updated sigs.yaml and associated generated files (ran make). NOTE: If offboarding, remember to add to emeritus.: https://github.com/kubernetes/community/pull/7705
• [x] Updated OWNERS_ALIASES in kubernetes/org. https://github.com/kubernetes/org/pull/4832
• [x] Updated milestone maintainers team in kubernetes/org. https://github.com/kubernetes/org/pull/4832
• [x] Checked for and updated any other potential teams in kubernetes/org.
• [x] Updated OWNERS_ALIASES in kubernetes/enhancements. https://github.com/kubernetes/enhancements/pull/4553
• [x] Updated OWNERS_ALIASES in kubernetes/k8s.io. https://github.com/kubernetes/k8s.io/pull/6596
• [x] Updated feature-approvers in OWNERS_ALIASES in kubernetes/kubernetes (when applicable) https://github.com/kubernetes/kubernetes/pull/123978
• [x] Updated membership of the leads mailing list https://github.com/kubernetes/k8s.io/pull/6596
• [x] Updated membership for any other mailing list / groups.
• [x] Added to #chairs-and-techleads slack channel.
• [x] Updated ownership of group leads mailing list.
• [x] Updated ownership of group mailing list.
• [x] Updated ownership of group calendar.
• [ ] Updated access/teams in 1password. (Contact ContribEx leads to complete)

Additional information:

No response

Labels:

No response

[deads2k]

/sig api-machinery

[sttts]

Have just finished Inclusive Open Source Community Orientation course.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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-sigs/prow repository.