2021 Annual Report: SIG Usability

[cblecker]

Chairs: @hpandeycodeit @morengab @tashimi
Liaison: @dims

Actions for the chair/organizer of the community group:

• Consult your community group to complete draft of report
• If needed, consult with Steering Committee liaison on any private issues or concerns that arrise while completing report
• Submit PR to git.k8s.io/community repo with copy of report, assigning your Steering Committee liaison for review
• Steering Committee reviews report, and may make comments/ask questions
• Once all comments are addressed, Steering Committee will approve report to merge
• If needed, any follow up items may be brought to the "Chairs, Tech Leads, and Organizers" meeting in April

Once all the above items are complete, this issue may be /close'd

Key dates:

• Initial PR to communtiy repo should be opened by February 14, 2022
• PR should be reviewed and merged by March 1st, 2022

More detailed information on the annual reports process is available here.

Your group's report template is available here: https://git.k8s.io/community/sig-usability/annual-report-2021.md

If you have any questions or concerns about this process, you may reach the Steering Committee via the following methods:

• Slack/E-mail your liaison directly
• The public #steering-committee channel in Slack
• The public mailing list steering@kubernetes.io
• The private mailing list steering-private@kubernetes.io for any private or sensitive issues.

/sig usability
/committee steering

[dims]

@hpandeycodeit @morengab @tashimi ping! how's the annual report going, is there a PR?

[dims]

/cc @dims

[k8s-triage-robot]

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

This bot triages issues and 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 issue is closed

You can:

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

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

/lifecycle stale

[parispittman]

/close
#5615

[k8s-ci-robot]

@parispittman: Closing this issue.

In response to this:

/close
#5615

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.