community 2022 Annual Report: SIG Security

Chairs: @IanColdwater @tabbysable Liaison: @cpanato

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

A template has already been generated for your group, and is available here.

Key dates:

Initial PR to communtiy repo should be opened by March 24th, 2023
PR should be reviewed and merged by April 7th, 2023

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-security/annual-report-2022.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 [email protected]
The private mailing list [email protected] for any private or sensitive issues.

/sig security /committee steering /area annual-reports

Feb 09 '23 01:02 cblecker

@IanColdwater @tabbysable sent some slack messages and did not hear anything from you both, do y'all need any help

Mar 27 '23 07:03 cpanato

My apologies! We both got distracted this week. Will get that PR in now

Mar 27 '23 15:03 IanColdwater

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

Jun 25 '23 15:06 k8s-triage-robot

/remove-lifecycle stale

Jun 26 '23 06:06 cpanato

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

Jan 23 '24 06:01 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

Feb 22 '24 06:02 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

Mar 23 '24 07:03 k8s-triage-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/test-infra repository.

Mar 23 '24 07:03 k8s-ci-robot