Skip to content

Add 2025 annual report for wg-device-management#8834

Open
alaypatel07 wants to merge 1 commit into
kubernetes:mainfrom
alaypatel07:wg-dm-annual-report-2025
Open

Add 2025 annual report for wg-device-management#8834
alaypatel07 wants to merge 1 commit into
kubernetes:mainfrom
alaypatel07:wg-dm-annual-report-2025

Conversation

@alaypatel07

Copy link
Copy Markdown

Which issue(s) this PR fixes:

Fixes # #8788

@k8s-ci-robot k8s-ci-robot added area/annual-reports Issues or PRs related to the annual reports size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 9, 2026
Many new contributors have ramped up and helped with driving the features and issues as well as promoting
DRA to GA.

2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been the only one actively reviewing PRs for the dra-example-driver, in case that's worth mentioning here.

I would also like to keep reminding driver authors to contribute their expertise back to the example driver, if this is an appropriate place for that.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @nojnhuh, PTAL updated this section

@alaypatel07 alaypatel07 force-pushed the wg-dm-annual-report-2025 branch from a89d1d8 to 85af46d Compare February 9, 2026 19:56
2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?

The [dra-example-driver](https://github.com/kubernetes-sigs/dra-example-driver) has a single active maintainer,
more help would be welcome especially around contributing the expertise from production dra drivers back into

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for including this!

one nit:

Suggested change
more help would be welcome especially around contributing the expertise from production dra drivers back into
more help would be welcome especially around contributing the expertise from production DRA drivers back into

@k8s-triage-robot

Copy link
Copy Markdown

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-contributor-experience at kubernetes/community.

/check-cla
/easycla

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Feb 9, 2026
@johnbelamaric

Copy link
Copy Markdown
Member

/approve
/lgtm

Thanks @alaypatel07 !

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 10, 2026
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: alaypatel07, johnbelamaric
Once this PR has been reviewed and has the lgtm label, please assign pacoxu for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

- [x] WG leaders in [sigs.yaml] are accurate and active, and updated if needed
- [x] Meeting notes and recordings for 2025 are linked from [README.md] and updated/uploaded if needed
- [x] Updates provided to sponsoring SIGs in 2025
- KubeCon NA maintainer track talk:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section is meant to be SIG meeting recordings where the workgroup updated the sponsoring SIG, not kubecon talks.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(could also be an email, meeting notes or other, but a kubecon talk isn't exactly outreach to the sponsoring SIGs)

@k8s-triage-robot

Copy link
Copy Markdown

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

@kubernetes-prow kubernetes-prow Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 20, 2026
@pacoxu

pacoxu commented Jun 24, 2026

Copy link
Copy Markdown
Member

/remove-lifecycle stale
@alaypatel07 Do you have time to address Ben's comments above?

@kubernetes-prow kubernetes-prow Bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/annual-reports Issues or PRs related to the annual reports cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants