community icon indicating copy to clipboard operation
community copied to clipboard

REQUEST: need event's icon

Open KeyOfSpectator opened this issue 1 year ago • 8 comments

Maybe we need Event's icon.

Maybe we need Event's icon. It is not exist in icon set: https://github.com/kubernetes/community/blob/master/icons/README.md

KeyOfSpectator avatar Mar 18 '24 07:03 KeyOfSpectator

/sig ui

pranav-pandey0804 avatar Mar 27 '24 11:03 pranav-pandey0804

/sig contribex

pranav-pandey0804 avatar Mar 27 '24 11:03 pranav-pandey0804

@pranav-pandey0804: The label(s) sig/contribex cannot be applied, because the repository doesn't have them.

In response to this:

/sig contribex

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.

k8s-ci-robot avatar Mar 27 '24 11:03 k8s-ci-robot

/sig contributor-experience

pranav-pandey0804 avatar Mar 27 '24 11:03 pranav-pandey0804

Hi, which event's icon are you talking about? Please add more context to the issue.

palnabarun avatar Apr 11 '24 20:04 palnabarun

Do you mean kubecon or KCD logo? You can find it in https://github.com/cncf/artwork/tree/main/other/kubecon-cloudnativecon/ and https://github.com/cncf/artwork/blob/main/examples/other.md#kubernetes-community-days.

pacoxu avatar Apr 29 '24 06:04 pacoxu

Sorry, my bad. I m looking for the logo of the Event entity in Kubernetes.

KeyOfSpectator avatar Jul 13 '24 07:07 KeyOfSpectator

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 avatar Oct 11 '24 08:10 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

k8s-triage-robot avatar Nov 10 '24 08:11 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

k8s-triage-robot avatar Dec 10 '24 09:12 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-sigs/prow repository.

k8s-ci-robot avatar Dec 10 '24 09:12 k8s-ci-robot