WG-Device-Management: Creation

johnbelamaric commented 6 months ago

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:

[X] Are a Kubernetes Org member
[ ] 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.
[x] Updated OWNERS_ALIASES in kubernetes/org - https://github.com/kubernetes/org/pull/4927
[X] Updated milestone maintainers team in kubernetes/org - N/A
[x] Checked for and updated any other potential teams in kubernetes/org - https://github.com/kubernetes/org/pull/4927
[X] Updated OWNERS_ALIASES in kubernetes/enhancements N/A
[x] Updated OWNERS_ALIASES in kubernetes/k8s.io - https://github.com/kubernetes/k8s.io/pull/6770
[X] Updated feature-approvers in OWNERS_ALIASES in kubernetes/kubernetes - N/A
[X] Updated membership of the leads mailing list - N/A
[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 - https://github.com/kubernetes/k8s.io/pull/6770
[x] Updated ownership of group mailing list - https://github.com/kubernetes/k8s.io/pull/6770
[x] Updated ownership of group calendar.
[ ] Updated access/teams in 1password. (Contact ContribEx leads to complete)
[x] Update permissions for the corresponding Youtube playlists. (Contact YouTube moderators)

Additional information:

No response

Labels:

/sig architecture

johnbelamaric commented 6 months ago

/assign @johnbelamaric

CIPHERTron commented 6 months ago

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

johnbelamaric commented 6 months ago

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

Thanks!

k8s-triage-robot commented 3 months ago

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 commented 2 months ago

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 commented 1 month ago

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 commented 1 month ago

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

In response to [this](https://github.com/kubernetes/community/issues/7863#issuecomment-2381582757): >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][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

kubernetes / community