Open chris-short opened 8 months ago
@chris-short: The label(s) `/label area/contributor-comms
, /label sig/contributor-experiencecannot be applied. These labels are supported:
api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor. Is this label configured under
labels -> additional_labelsor
labels -> restricted_labelsin
plugin.yaml`?
/sig contributor-experience
/area contributor-comms
/assign chris-short
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Taking a stab at this, as per our last meeting. /remove-lifecycle stale
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Describe the issue
Sensitive comms are hard. They require coordination, review, good timing, and if the issue merits it, working with end user vendors. Making a process for this or at least some guidelines to help folks as much as possible during community crisises and changes.
Work across the project to create an outline and examples of what to send folks when we have project-wide impacting issues. Start in ContribEx Comms and incorporate SIG Security ideas. Then, work to get feedback from as many folks as possible.