WG-Device-Management: Creation

[johnbelamaric]

SIG/WG name:

WG Device Management

Onboarding Lead(s):

johnbelamaric, klueska, pohly

Offboarding Lead(s):

No response

Link to discussion:

No response

Prerequisites for new leads:

• Are a Kubernetes Org member
• Have completed the Inclusive Open Source Community Orientation course

Onboarding / Offboarding tasks:

• Updated sigs.yaml and associated generated files (ran make). NOTE: If offboarding, remember to add to emeritus.
• Updated OWNERS_ALIASES in kubernetes/org - sig-architecture: add wg-device-management gh teams org#4927
• Updated milestone maintainers team in kubernetes/org - N/A
• Checked for and updated any other potential teams in kubernetes/org - sig-architecture: add wg-device-management gh teams org#4927
• Updated OWNERS_ALIASES in kubernetes/enhancements N/A
• Updated OWNERS_ALIASES in kubernetes/k8s.io - Add WG Device Management groups k8s.io#6770
• Updated feature-approvers in OWNERS_ALIASES in kubernetes/kubernetes - N/A
• Updated membership of the leads mailing list - N/A
• Updated membership for any other mailing list / groups.
• Added to #chairs-and-techleads slack channel.
• Updated ownership of group leads mailing list - Add WG Device Management groups k8s.io#6770
• Updated ownership of group mailing list - Add WG Device Management groups k8s.io#6770
• Updated ownership of group calendar.
• Updated access/teams in 1password. (Contact ContribEx leads to complete)
• Update permissions for the corresponding Youtube playlists. (Contact YouTube moderators)

Additional information:

No response

Labels:

/sig architecture

[johnbelamaric]

/assign @johnbelamaric

[CIPHERTron]

New playlist created ➡️ https://www.youtube.com/playlist?list=PL69nYSiGNLP1kac4zsH0INEWEZlPhOhlp

[johnbelamaric]

New playlist created ➡️ https://www.youtube.com/playlist?list=PL69nYSiGNLP1kac4zsH0INEWEZlPhOhlp

Thanks!

[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.